To upgrade GlassFish ESB, perform the following steps in the order given:
This step downloads the installation tools you will use to perform the GlassFish ESB upgrade.
In a web browser, navigate to https://open-esb.dev.java.net/Downloads.html.
Next to Full Install, select the operating system to which you are installing GlassFish ESB, and then click Download.
Save the file to a temporary folder.
Repeat the above steps to download the Components Only installer.
To begin the upgrade process, install GlassFish ESB v2.2 in a directory separate from your existing GlassFish ESB installation. Use the same port numbers as were used in your existing GlassFish ESB environment in order to avoid having to reconfigure port numbers in any of your projects.
Shut down the existing GlassFish server in order to avoid port conflicts.
Navigate to the directory where you downloaded the GlassFish ESB installers.
Follow the instructions under Installing GlassFish ESB Using the GUI Installer in Using the GlassFish ESB Installation GUI, beginning with step 3. The name of the installer file to use is glassfishesb-v2.2-full-installer-OperatingSystem.
Make sure to install GlassFish ESB v2.2 in a separate directory from your existing GlassFish ESB installation. For example, if you have GlassFish ESB installed in C:\GlassFishESB, install the new version in C:\GlassFishESBv22. You specify the location on the NetBeans IDE Installation window and the GlassFish Installation window of the installer.
GlassFish provides an upgrade utility, asupgrade, to automatically migrate configuration settings, services, and deployed applications. The following instructions describe how to perform this process from the Upgrade Wizard, but you can also use a command line interface. For more information about asupgrade, see “Upgrading Configuration, Deployed Applications, and Certificate Databases” in the Sun GlassFish Enterprise Server 2.1 Upgrade guide.
This process does not work for application configurations and variables for the HTTP Binding Component and Java EE Service Engine. These must be migrated manually.
From a command prompt, navigate to \glassfish\bin in the new GlassFish ESB v2.2 installation.
Type asupgrade.
The Upgrade Wizard appears.
In the Source Domain Directory field, browse to and select the existing GlassFish ESB directory containing the domain you want to upgrade.
Verify the Target Domains Root Directory field, and then enter the login information for the administrator user.
The default admin user name is admin, the password is adminadmin, and the master password is changeit.
Click Next.
The Upgrade Wizard migrates the previous GlassFish configuration settings to the new installation. This may take a while depending on the amount of configuration settings that need to be transferred.
When the Upgrade Wizard is finished, click Finish and then review the log file to verify there were no errors.
The log file is located under the GlassFish home directory in \glassfish\domains\upgrade.log.
Start the GlassFish 2.2 server, and recreate any application variables or application configurations for the HTTP BC and the Java EE SE.
When you are finished, shut down the application server.
At this point, the GlassFish version is correct and the settings and services are upgraded, but the runtime components are still at the previous version. You need to run the component installer to upgrade them to version 2.2.
Navigate back to the directory where you downloaded the GlassFish ESB installers.
Launch the component installer by running the file named glassfishesb-v2.2-installer-OperatingSystem.
The GlassFish ESB Installer appears.
In the lower right, click Customize.
The Customize Installation dialog appears.
Deselect Core SOA in NetBeans, and deselect JBI Component Toolings in NetBeans.
Click OK, and then click Next.
Agree to the terms of the license, and then click Next.
On the GlassFish Installation window, browse to and select the GlassFish home directory in GlassFish ESB v2.2.
Enter the Admin login information.
Click Next, and then click Install.
When the installation is complete, click Finish.
To verify the components were upgraded, do the following:
Start the upgraded GlassFish 2.2 application server.
Start the Admin Console for the upgraded server.
In the left navigation bar, expand Components under JBI, and then select any component.
Verify that the Version is 2.6.0 and the Build Number is 091207.
In the Components list, verify that there are new entries for sun-scheduler-binding and sun-iep-engine.
If you are using monitoring for BPEL processes, you need to update the monitoring database to complete the upgrade.
For MySQL databases, run the following script against the BPEL monitoring database:
CREATE TABLE MONITORBPELPROCESS ( suname varchar (256), bpelid varchar (744), genbpelevents char(1), primary key (bpelid) ) ENGINE=InnoDB; |
For Oracle or Derby databases, run the following script against the BPEL monitoring database:
CREATE TABLE MONITORBPELPROCESS ( suname varchar(256), bpelid varchar(1028), genbpelevents char(1), primary key (bpelid) ); |
The design-time components in the NetBeans IDE are now at the current version, but the projects need to be rebuilt and redeployed to pick up any changes made between GlassFish ESB versions.