Installation and Upgrading

The following are known issues for installation and upgrading:

• Issue 1981

  When you perform a side-by-side upgrade of GlassFish ESB, the upgrade tool (asupgrade) does not migrate application variables and application configuration.

  To work around this issue, perform the upgrade and then recreate the application variables and application configurations in the new domain for GlassFish ESB 2.1.

• When using GlassFish ESB with JDK 1.6.0_13 or 1.6.0_14, several of the wizards used to develop application will not work correctly and may have problems importing XSDs from files. In addition, the GlassFish ESB Installer fails to install on Windows when using JDK 1.6.0_13 or 1.6.0_14.

  To work around this issue, install a different version of JDK 1.6.

• The Healthcare Pack Installer requires JDK 1.6.0_04 or later, excluding JDK 1.6.0_13 and 1.6.0_14.

• The Platinum Pack silent installation does not allow you to select which components to install. It only performs a complete installation of the Platinum Pack components.

• You cannot change the master password when you perform an installation. The default master password is changeit. You can change the master password if necessary using the following command:

  asadmin change-master-password new-password

  Substitute the actual password for new-password.

• Before running the component installer against existing NetBeans and GlassFish environments on Mac OS, you need to modify the netbeans.conf file by uncommenting and updating the value of the netbeans_jdkhome property. This should point to the JDK home directory. For example, netbeans_jdkhome="/Library/Java/Home"

• When you run the component installer against an existing GlassFish environment, you cannot specify which domain to install the components to. If there is more than one domain, the components are installed to all domains.

• The component installer does not currently support installing components to a remote domain.

• Installing the Healthcare Pack to a clustered environment fails.

  To work around this issue, remove the encoder shared library from the cluster before running the Healthcare Pack Installer.

• If you are upgrading to GlassFish ESB 2.2 and are using BPEL monitoring, you need to manually add two tables to the monitoring database. Here are the SQL Commands to use:

  For MySQL Databases:

  CREATE TABLE MONITORBPELPROCESS ( suname varchar (256), bpelid varchar (744), genbpelevents char(1), primary key (bpelid) ) ENGINE=InnoDB;

  For Oracle and Derby Databases:

  CREATE TABLE MONITORBPELPROCESS ( suname varchar(256), bpelid varchar(1028), genbpelevents char(1), primary key (bpelid) );