INTRODUCTION

Sesame Home Disclaimer Feature Tour Release Notes Bug Reports

USERS GUIDE

Help Pages How To Videos

ADMINS GUIDE

Installing Sesame Upgrading Sesame Source Code

CREDITS

People Funds History References Acknowledgments

OTHER

Publications Links Site Search Open Positions Contact Us

Upgrading Sesame

v.20160402 to v.20170204

Download the current tier1 and tier2 archives from Installing Sesame, download the

archive, and unpack them.

The archives were created with 7-Zip.

To guarantee authenticity, all the jars are signed by a 'University of Wisconsin-Madison' certificate issued by 'InCommon Code Signing CA.'

Stop the server.

If running, stop the web server.

Backup your database.

Backup your tier1 and tier2 directories.

Replace the jars in your tier1 directory with the jars from the tier1 archive.

Replace the jar in your tier2 directory with the jar from the tier2 archive.

Edit all your jnlp files, and change line

<property name="jnlp.sesame.Version" value="v.20160402"/>

to

<property name="jnlp.sesame.Version" value="v.20170204"/>

If you haven't modified your index.html file, replace it with the index.html file from the archive. Otherwise compare, and copy and paste the modifications. Or just modify the new one accordingly.

Execute the appropriate sesame_update_*.sql script.

Backup your database.

Backup your tier1 and tier2 directories.

Start the server, executing RunServer.bat or RunServer.sh

If needed, start the web server, executing RunWebServer.bat or RunWebServer.sh

From the message in console it will be clear if the server and the web server started ok or not.

Run a Sesame client application to test if everything works ok.

For what's new, see the Release Notes from 2016-04-29 to 2017-02-04 .

v.20150912 to v.20160402

Download the current tier1 and tier2 archives from Installing Sesame, download the

archive, and unpack them.

The archives were created with 7-Zip.

To guarantee authenticity, all the jars are signed by a 'University of Wisconsin-Madison' certificate issued by 'InCommon Code Signing CA.'

Stop the server.

If running, stop the web server.

Backup your database.

Backup your tier1 and tier2 directories.

Replace the jars in your tier1 directory with the jars from the tier1 archive.

Replace the jar in your tier2 directory with the jar from the tier2 archive.

Edit all your jnlp files, and change line

<property name="jnlp.sesame.Version" value="v.20150912"/>

to

<property name="jnlp.sesame.Version" value="v.20160402"/>

Edit your SesameMain.properties file, and add a line for the Sesame Web Server port, e.g. 8008,

sesame.webserverport = 8008

below the other

sesame. ...

lines.

Edit RunWebServer.bat or RunWebServer.sh, depending on your OS of choice, to match your configuration.

If you haven't modified your index.html file, replace it with the index.html file from the archive. Otherwise compare, and copy and paste the modifications. Or just modify the new one accordingly.

Execute the appropriate sesame_update_*.sql script.

Backup your database.

Backup your tier1 and tier2 directories.

Start the server, executing RunServer.bat or RunServer.sh

If needed, start the web server, executing RunWebServer.bat or RunWebServer.sh

From the message in console it will be clear if the server and the web server started ok or not.

Run a Sesame client application to test if everything works ok.

See the 'Viewing Schedules in a browser' section on the Installing Sesame page, and test if everything works ok.

For what's new, see the Release Notes from 2015-09-12 to 2016-04-29.

v.20150224 to v.20150912

Download the current tier1 and tier2 archives from Installing Sesame, download the

archive, and unpack them.

The archives were created with 7-Zip.

To guarantee authenticity, all the jars are signed by a 'University of Wisconsin-Madison' certificate issued by 'InCommon Code Signing CA.'

Stop the server.

Backup your database.

Backup your tier1 and tier2 directories.

Replace the jars in your tier1 directory with the jars from the tier1 archive.

Replace the jar in your tier2 directory with the jar from the tier2 archive.

Edit all your jnlp files, and change line

<property name="jnlp.sesame.Version" value="v.20150224"/>

to

<property name="jnlp.sesame.Version" value="v.20150912"/>

then add the

<property name="jnlp.sesame.RegisteringEnabled" value="Yes"/>

line below the other

<property name=.../>

lines in the

<resources> </resources>

section.

Edit your SesameMain.properties file, and add the

sesame.registeringenabled = true

line below the other

sesame. ...

lines.

If you haven't modified your index.html file, replace it with the index.html file from the archive. Otherwise compare, and copy and paste the modifications. Or just modify the new one accordingly.

Execute the appropriate sesame_update_*.sql script.

Backup your database.

Backup your tier1 and tier2 directories.

Start the server, executing RunServer.bat or RunServer.sh

From the message in console it will be clear if the server started ok or not.

Run a Sesame client application to test if everything works ok.

For what's new, see the Release Notes from 2015-04-15 to 2015-09-12.

v.20140525 to v.20150224

Download the current tier1 and tier2 archives from Installing Sesame, download the

archive, and unpack them.

The archives were created with 7-Zip.

To guarantee authenticity, all the jars are signed by a 'University of Wisconsin-Madison' certificate issued by 'InCommon Code Signing CA.'

Stop the server.

Backup your database.

Backup your tier1 and tier2 directories.

Replace the jars in your tier1 directory with the jars from the tier1 archive.

Replace the jar in your tier2 directory with the jar from the tier2 archive.

Edit all your jnlp files, and change line

<property name="jnlp.sesame.Version" value="v.20140525"/>

to

<property name="jnlp.sesame.Version" value="v.20150224"/>

If you haven't modified your index.html file, replace it with the index.html file from the archive. Otherwise compare, and copy and paste the modifications. Or just modify the new one accordingly.

Execute the appropriate sesame_update_*.sql script.

Backup your database.

Backup your tier1 and tier2 directories.

Start the server, executing RunServer.bat or RunServer.sh

From the message in console it will be clear if the server started ok or not.

Run a Sesame client application to test if everything works ok.

For what's new, see the Release Notes from 2014-06-13 to 2015-04-15.

v.20120708 to v.20140525

Download the current tier1 and tier2 archives from Installing Sesame, download the

archive, and unpack them.

The archives were created with 7-Zip.

To guarantee authenticity, all the jars are signed by a 'University of Wisconsin-Madison' certificate issued by 'InCommon Code Signing CA.'

Stop the server.

Backup your database.

Backup your tier1 and tier2 directories.

Replace the jars in your tier1 directory with the jars from the tier1 archive.

Replace the jar in your tier2 directory with the jar from the tier2 archive.

Edit all your jnlp files, and change line

<jnlp spec="1.0"

to

<jnlp spec="6.0+"

and line

<property name="sesame.Version" value="v.20120708"/>

to

<property name="jnlp.sesame.Version" value="v.20140525"/>

Change property name

"org.omg.CORBA.ORBInitialHost"

to

"jnlp.org.omg.CORBA.ORBInitialHost"

property name

"org.omg.CORBA.ORBInitialPort"

to

"jnlp.org.omg.CORBA.ORBInitialPort"

property name

"sesame.NameComponent1"

to

"jnlp.sesame.NameComponent1"

property name

"sesame.NameComponent2"

to

"jnlp.sesame.NameComponent2"

property name

"com.sun.CORBA.transport.ORBTCPReadTimeouts"

to

"jnlp.com.sun.CORBA.transport.ORBTCPReadTimeouts"

and property name

"sesame.InstanceName"

to

"jnlp.sesame.InstanceName"

and finally, delete the line

<property name="swing.defaultlaf" value=
"javax.swing.plaf.metal.MetalLookAndFeel"/>

If you haven't modified your index.html file, replace it with the index.html file from the archive. Otherwise compare, and copy and paste the modifications.

Execute the appropriate sesame_update_*.sql script.

Backup your database.

Backup your tier1 and tier2 directories.

Start the server, executing RunServer.bat or RunServer.sh

From the message in console it will be clear if the server started ok or not.

Run a Sesame client application to test if everything works ok.

For what's new, see the Release Notes from 2012-08-03 to 2014-06-13.

v.20110111 to v.20120708

Download the current tier1 and tier2 archives from Installing Sesame, download the

archive, and unpack them.

The archives were created with 7-Zip.

To guarantee authenticity, all the jars are signed by a 'University of Wisconsin-Madison' certificate issued by 'InCommon Code Signing CA.'

Stop the server.

Backup your database.

Backup your tier1 and tier2 directories.

Replace the jars in your tier1 directory with the jars from the tier1 archive.

Replace the jar in your tier2 directory with the jar from the tier2 archive.

Edit all your jnlp files, and change the value in

<property name="sesame.Version" value="v.20110111"/>

line to

<property name="sesame.Version" value="v.20120708"/>

and change the j2se version in line that starts with

<j2se version="1.5+"

to

<j2se version="1.6+"

and finally, add the line

<property name="sesame.InstanceName" value="MyInstanceName"/>

above the line containing the version number

<property name="sesame.Version" value="v.20120708"/>

If you haven't modified your index.html file, replace it with the index.html file from the archive. Otherwise copy and paste the Jafar related parts.

Copy the jafar.jnlp file from the archive to the directory that contains the other jnlp files, and modify it accordingly.

Execute the appropriate sesame_update_*.sql script.

Backup your database.

Backup your tier1 and tier2 directories.

Start the server, executing RunServer.bat or RunServer.sh

From the message in console it will be clear if the server started ok or not.

Run a Sesame client application to test if everything works ok.

For what's new, see the Release Notes from 2011-01-11 to 2012-08-03.

v.20100901 to v.20110111

Download the current tier1 and tier2 archives from Installing Sesame, download the

archive, and unpack them.

The archives were created with 7-Zip.

To guarantee authenticity, all the jars are signed by a 'University of Wisconsin-Madison' certificate issued by 'Thawte Code Signing CA.'

Stop the server.

Backup your database.

Backup your tier1 and tier2 directories.

Replace the jars in your tier1 directory with the jars from the tier1 archive.

Replace the jar in your tier2 directory with the jar from the tier2 archive.

Edit all your jnlp files, and change the value in

<property name="sesame.Version" value="v.20100901"/>

line to

<property name="sesame.Version" value="v.20110111"/>

Edit the sheherazade.jnlp file, and change the max-heap-size value in

<j2se version="1.5+" max-heap-size="256m"/>

line to

<j2se version="1.5+" max-heap-size="1024m"/>

Edit RunServer.bat or RunServer.sh, depending on your OS of choice, and increase the maximum heap size by adding

-Xmx1024m

before the

-cp

runtime parameter.

Execute the appropriate sesame_update_*.sql script.

Backup your database.

Backup your tier1 and tier2 directories.

Start the server, executing RunServer.bat or RunServer.sh

From the message in console it will be clear if the server started ok or not.

Run a Sesame client application to test if everything works ok.

For what's new, see the Release Notes from 2010-09-01 to 2011-01-11.

v.20100308 to v.20100901

Download the current tier1 and tier2 archives from Installing Sesame, download the

archive, and unpack them.

The archives were created with 7-Zip.

To guarantee authenticity, all the jars are signed by a 'University of Wisconsin-Madison' certificate issued by 'Thawte Code Signing CA.'

Stop the server.

Backup your database.

Backup your tier1 and tier2 directories.

Replace the jars in your tier1 directory with the jars from the tier1 archive.

Replace the jar in your tier2 directory with the jar from the tier2 archive.

Edit all your jnlp files, and change the value in

<property name="sesame.Version" value="v.20100308"/>

line to

<property name="sesame.Version" value="v.20100901"/>

Execute the appropriate sesame_update_*.sql script.

Backup your database.

Backup your tier1 and tier2 directories.

Start the server, executing RunServer.bat or RunServer.sh

From the message in console it will be clear if the server started ok or not.

Run a Sesame client application to test if everything works ok.

For what's new, see the Release Notes from 2010-05-09 to 2010-09-01.

v.20090525 to v.20100308

Download the current tier1 and tier2 archives from Installing Sesame, download the

archive, and unpack them.

The archives were created with 7-Zip.

To guarantee authenticity, all the jars are signed by a 'University of Wisconsin-Madison' certificate issued by 'Thawte Code Signing CA.'

Stop the server.

Backup your database.

Backup your tier1 and tier2 directories.

Replace the jars in your tier1 directory with the jars from the tier1 archive.

Replace the jar in your tier2 directory with the jar from the tier2 archive.

Edit all your jnlp files, and change the value in

<property name="sesame.Version" value="v.20090525"/>

line to

<property name="sesame.Version" value="v.20100308"/>

Execute the appropriate sesame_update_*.sql script.

Backup your database.

Backup your tier1 and tier2 directories.

Start the server, executing RunServer.bat or RunServer.sh

From the message in console it will be clear if the server started ok or not.

Run a Sesame client application to test if everything works ok.

v.20090204 to v.20090525

Download the current tier1 and tier2 archives from Installing Sesame, download the

archive, and unpack them.

The archives were created with 7-Zip.

To guarantee authenticity, all the jars are signed by a 'University of Wisconsin-Madison' certificate issued by 'Thawte Code Signing CA.'

Stop the server.

Backup your database.

Backup your tier1 and tier2 directories.

Replace the jars in your tier1 directory with the jars from the tier1 archive.

Replace the jar in your tier2 directory with the jar from the tier2 archive.

Edit all your jnlp files, and change the value in

<property name="sesame.Version" value="v.20090204"/>

line to

<property name="sesame.Version" value="v.20090525"/>

then add the

<property name="swing.defaultlaf" value=
"javax.swing.plaf.metal.MetalLookAndFeel"/>

line below the other

<property name=.../>

lines in the

<resources> </resources>

section.

If you haven't modified the sesame_home.html file in your tier1 directory, replace it with the sesame_home.html file in the tier1 archive. Otherwise, transplant the Bazaar related sections.

Copy the bazaar gifs from the tier1 archive to your tier1 directory.

Copy the bazaar.jnlp file from the tier1 archive to your tier1 directory, and modify it to become similar to your existing jnlp files.

Execute the appropriate sesame_update_*.sql script.

Backup your database.

Backup your tier1 and tier2 directories.

Start the server, executing RunServer.bat or RunServer.sh

From the message in console it will be clear if the server started ok or not.

Run a Sesame client application to test if everything works ok.

v.20081021 to v.20090204

Download the current tier1 and tier2 archives from Installing Sesame, download the

archive, and unpack them.

The archives were created with 7-Zip.

To guarantee authenticity, all the jars are signed by a 'University of Wisconsin-Madison' certificate issued by 'Thawte Code Signing CA.'

Stop the server.

Backup your database.

Backup your tier1 and tier2 directories.

Replace the jars in your tier1 directory with the jars from the tier1 archive.

Replace the jar in your tier2 directory with the jar from the tier2 archive.

Edit all your jnlp files, and add the

<property name="sesame.Version" value="v.20090204"/>

line below the other

<property name=.../>

lines in the

<resources> </resources>

section.

Execute the appropriate sesame_update_*.sql script.

Backup your database.

Backup your tier1 and tier2 directories.

Start the server, executing RunServer.bat or RunServer.sh

From the message in console it will be clear if the server started ok or not.

Run a Sesame client application to test if everything works ok.