Installation Issues

The Sun GlassFish Web Space Server does not get installed when you use Application Server 9.1.1 Enterprise Edition as the web container.

Description:

When you install Application Server 9.1.1 Enterprise Edition and run the install.xml file from websynergy-for-gfv2.zip, you will get the following exception.

install: [mkdir] Created dir: /var/tmp/root/websynergyinstall update-glassfish: [exec] CLI168 Could not delete the following jvm options. Options do not exist: [exec] -client [exec] CLI137 Command delete-jvm-options failed. [exec] Result: 1 [exec] CLI167 Could not create the following jvm options. Options exist: [exec] -server [exec] CLI137 Command create-jvm-options failed. [exec] Result: 1 [exec] server.log-service.module-log-levels.property.debug.com.sun.portal. portletcontainer = WARNING [echo] Stopping GlassFish... [echo] Execute /opt/SUNWappserver/bin/asadmin stop-domain if install hangs. [exec] Domain domain1 stopped.

Solution:

Perform the following steps to install Sun GlassFish Web Space Server on Application Server 9.1.1 Enterprise Edition.

1. Install the Application Server 9.1.1 Enterprise Edition.

2. Download webspace-for-gfv2.zip and unzip the bundle.

3. Add the following code to the server.policy file.

   grant codeBase "file:${com.sun.aas.instanceRoot}/lib/-" { permission java.security.AllPermission; }; // permissions for WebSynergy grant codeBase "file:${com.sun.aas.instanceRoot}/applications /j2ee-modules/webspace/-" { permission java.security.AllPermission; }; grant codeBase "file:${com.sun.aas.instanceRoot}/applications /j2ee-modules/saw-web/-" { permission java.security.AllPermission; }; // Basic set of required permissions granted to all remaining code grant { ............... ............... permission java.lang.reflect.ReflectPermission "suppressAccessChecks"; };

4. Update the portal-ext.properties file (available at webspace-for-gfv2/webspace/application/distribution/deploy/webspace/WEB-INF/classes/) with the following code.

   auto.deploy.glassfish-tomcat.jee.dm.id=deployer:Sun: AppServer::localhost:4848:https

   ---

   Note –

   You need to add the above code in the portal-ext.properties file, only if the value of the security-enabled property is “true”.

   ---

5. Run the ant -f install.xml command from the webspace-for-gfv2/webspace/application directory.

Harmless warning messages appear when you run install Sun GlassFish Web Space Server on Application Server 9.1.1 Enterprise Edition.

Description:

When you run the install.xml file from Sun GlassFish Web Space Server core bundle on Application Server 9.1.1 Enterprise Edition, you will get the following warning messages, which are not harmful to your installation.

update-glassfish: [exec] CLI168 Could not delete the following jvm options. Options do not exist: [exec] -client [exec] CLI137 Command delete-jvm-options failed. [exec] Result: 1 [exec] CLI167 Could not create the following jvm options. Options exist: [exec] -server [exec] CLI137 Command create-jvm-options failed. [exec] Result: 1 [exec] server.log-service.module-log-levels.property.debug.com.sun.portal. portletcontainer = WARNING [echo] Stopping GlassFish... [echo] Execute /opt/SUNWappserver//bin/asadmin stop-domain if install hangs. [exec] Domain domain1 stopped.

The reason for these harmless warning messages is that when the installer tries to update the JVM options in GlassFish, asadmin may output warnings about JVM options that it cannot change. For example, the installer tries to replace -client with -server. However, on Application Server 9.2 Enterprise Edition, -client has already been replaced with -server. So asadmin will output warning that it cannot find -client to remove and that it cannot add -server since it is already present.

Using the Apache Ant that ships with the GlassFish web container causes error while you run the asadmin start-domain command.

Description:

If the version of the Apache Ant that ships with the GlassFish web container is in your installation path, then the ./asdamin start-domain command will fail to execute and you cannot deploy the Sun GlassFish Web Space Server.

Solution:

Download the Apache Ant 1.7 or later version and place it in the installation path. Moreover, you need to set ANT_HOME to the directory where you have placed the downloaded Apache Ant 1.7 or later version.

All the Sun GlassFish Web Space Server WAR files failed to deploy on Red Hat Enterprise Linux (RHEL)and SUSE Linux versions.

Description:

When you install the Sun GlassFish Web Space Server with GlassFish web container on the RHEL and SUSE Linux operating system versions, all the WAR files are not deployed. This issue occurs when the maximum limit for open files is not sufficient to deploy the WAR files.

Solution:

To increase the maximum limit for open files on the RHEL and SUSE Linux versions:

1. Add the following two lines to the /etc/security/limits.conf file.

   • * soft nofile 5000

   • * hard nofile 5000

2. Restart the system.

The existing parameters in the input.properties file prevents the installation of Sun GlassFish Web Space Server on a second web container instance.

Description:

When you install the Sun GlassFish Web Space Server on the GlassFish web container and try to install again on another web container, you will not be prompted to enter new parameters for the second instance. The installation procedure in the second instance considers the parameters that are already provided in the first instance. This issue prevents the installation of Sun GlassFish Web Space Server on a second web container instance.

Solution:

Remove the input.properties file from the ../etc/webspace/application/ directory and install the Sun GlassFish Web Space Server on a second web container instance.