test

Sun GlassFish ESB Upgrade Guide

Upgrading the Runtime Components

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.

ProcedureTo Upgrade the Runtime Components

  1. Navigate back to the directory where you downloaded the GlassFish ESB installers.

  2. Launch the component installer by running the file named glassfishesb-v2.2-installer-OperatingSystem.

    The GlassFish ESB Installer appears.

    Figure shows the GlassFish ESB Component Installer.

  3. In the lower right, click Customize.

    The Customize Installation dialog appears.

  4. Deselect Core SOA in NetBeans, and deselect JBI Component Toolings in NetBeans.

    Figure shows customization settings for the Component Installer.

  5. Click OK, and then click Next.

  6. Agree to the terms of the license, and then click Next.

  7. On the GlassFish Installation window, browse to and select the GlassFish home directory in GlassFish ESB v2.2.

  8. Enter the Admin login information.

    Figure shows the GlassFish Installation window of the Component Installer.

  9. Click Next, and then click Install.

  10. When the installation is complete, click Finish.

  11. To verify the components were upgraded, do the following:

    1. Start the upgraded GlassFish 2.2 application server.

    2. Start the Admin Console for the upgraded server.

    3. In the left navigation bar, expand Components under JBI, and then select any component.

    4. Verify that the Version is 2.6.0 and the Build Number is 091207.

    5. In the Components list, verify that there are new entries for sun-scheduler-binding and sun-iep-engine.

ProcedureTo Upgrade the BPEL Monitoring Database

If you are using monitoring for BPEL processes, you need to update the monitoring database to complete the upgrade.

  1. 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;

  2. 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)
);