6.2 Configuring the WebSphere Environment

6.2.1 Adding User Application Configuration Files and JVM System Properties

The following steps are required for a successful WebSphere installation:

  1. Copy the sys-configuration-xmldata.xml file from the User Application install directory to a directory on the machine hosting the WebSphere server, for example /UserAppConfigFiles.

    The User Application install directory is the directory in which you installed the User Application.

  2. Set the path to the sys-configuration-xmldata.xml file in the JVM system properties. Log in to the WebSphere admin console as an admin user to do this.

  3. From the left panel, go to Servers > Application Servers

  4. Click the server name in the server list, for example server1.

  5. In the list of settings on the right, go to Java and Process Management under Server Infrastructure.

  6. Expand the link and select Process Definition.

  7. Under the list of Additional Properties, select Java Virtual Machine.

  8. Select Custom Properties under the Additional Properties heading for the JVM page.

  9. Click New to add a new JVM system property.

    1. For the Name, specify extend.local.config.dir.

    2. For the Value, specify the name of the install folder (directory) that you specified during installation.

      The installer wrote the sys-configuration-xmldata.xml file to this folder.

    3. For the Description, specify a description for the property, for example path to sys-configuration-xmldata.xml.

    4. Click OK to save the property.

  10. Click New to add another new JVM system property.

    1. For the Name, specify idmuserapp.logging.config.dir

    2. For the Value, specify the name of the install folder (directory) that you specified during installation.

    3. For the Description, specify a description for the property, for example path to idmuserapp_logging.xml.

    4. Click OK to save the property.

      The idmuserapp-logging.xml file does not exist until you persist the changes through User Application > Administration > Application Configuration > Logging.

6.2.2 Importing the eDirectory Trusted Root to the WebSphere Keystore

  1. Copy the eDirectory™ trusted root certificates to the machine hosting the WebSphere server.

    The User Application installation procedure exports the certificates to the directory in which you install the User Application.

  2. Import the certificates into the WebSphere keystore. You can do this by using the WebSphere administrator’s console (Importing Certificates with the WebSphere Administrator’s Console) or through the command line (Importing Certificates with the Command Line).

  3. After you import certificates, proceed to Section 6.3, Deploying the WAR File.

Importing Certificates with the WebSphere Administrator’s Console

  1. Log in to the WebSphere administration console as an admin user.

  2. From the left panel, go to Security > SSL Certificate and Key Management.

  3. In the list of settings on the right, go to Key stores and certificates under Additional Properties.

  4. Select NodeDefaultTrustStore (or the trust store you are using).

  5. Under Additional Properties on the right, select Signer Certificates.

  6. Click Add.

  7. Type the Alias name and full path to the certificate file.

  8. Change the Data type in the drop-down list to Binary DER data.

  9. Click OK. You should now see the certificate in the list of signer certificates.

Importing Certificates with the Command Line

From the command line on the machine hosting the WebSphere server, run the keytool to import the certificate into the WebSphere keystore.

NOTE:You need to use the WebSphere keytool or this does not work. Also, be sure the store type is PKCS12.

The WebSphere keytool is found at /IBM/WebSphere/AppServer/java/bin.

The following is a sample keytool command:

keytool -import -trustcacerts -file servercert.der -alias myserveralias -keystore trust.p12 -storetype PKCS12

If you have more than one trust.p12 file on your system, you might need to specify the full path to the file.

6.2.3 Passing the preferIPv4Stack Property to the JVM

The User Application uses JGroups for the caching implementation. In some configurations, JGroups requires the preferIPv4Stack property to be passed to the Java VM in order to ensure that the mcast_addr binding is successful. Without this option, the following error may be observed, and caching will not work properly:

[10/1/09 16:11:22:147 EDT] 0000000d UDP           W org.jgroups.util.Util
createMulticastSocket could not bind to /228.8.8.8 (IPv4 address); make sure
your mcast_addr is of the same type as the IP stack (IPv4 or IPv6).

In WebSphere, you can pass this option to the Java VM by navigating to Application servers >yourServerName > Process definition > Java Virtual Machine and specifying -Djava.net.preferIPv4Stack=true in the Generic JVM Options.