IBM WebSphere Application Server 6.1

WebSphere Application Server 6.1 is supported on Solaris, Linux, Windows, and IBM AIX 5.3 systems.

• OpenSSO Enterprise Pre-Deployment Tasks

• Post-Deployment Tasks

If the Java Security Manager is enabled, add the security permissions to the server.policy file, as described in Adding Security Permissions For a Web Container. After you edit the file, restart the web container.

OpenSSO Enterprise Pre-Deployment Tasks

• Adding GenericJvmArguments

• Adding Security Permissions

• Running the JSP Compiler

Adding GenericJvmArguments

Add the genericJvmArguments using the WebSphere Admin Console or by editing the server.xml file:

1. Open the following file:

   install_root/IBM/WebSphere/AppServer/profiles/AppSrv01/
   config/cells/cell/nodes/node/servers/server/server.xml

2. Find the jvmEntries element.

3. Add the following genericJvmArguments and save the file:

   genericJvmArguments="-DamCryptoDescriptor.provider=IBMJCE -DamKeyGenDescriptor.provider=IBMJCE"

4. Restart WebSphere 6.1 Application Server.

Adding Security Permissions

If the Java Security Manager is enabled, add the security permissions to the server.policy file, as described in Adding Security Permissions For a Web Container. After you edit the file, restart the web container.

Running the JSP Compiler

The OpenSSO Enterprise JSP files require JDK 1.5 (or later), but on WebSphere Application Server 6.1, the JDK source level for JSP files is set to JDK 1.3 by default.

To reset the JDK source level on WebSphere Application Server 6.1:

1. Open the WEB-INF/ibm-web-ext.xmi file.

   JSP engine configuration parameters are stored either in a web module's configuration directory or in a web module's binaries directory in the WEB-INF/ibm-web-ext.xmi file:

   • Configuration directory. For example:

     {WAS_ROOT}/profiles/profilename/config/cells/cellname/applications/ enterpriseappname/deployments/deployedname/webmodulename/

   • Binaries directory, if an application was deployed into WebSphere Application Server with the flag “Use Binary Configuration” flag set to true. For example:

     {WAS_ROOT}/profiles/profilename/installedApps/nodename/ enterpriseappname/webmodulename/

2. Delete the compileWithAssert parameter by either deleting the statement from the file or enclosing the statement with comment tags (<!-- ... –->).

3. Add the jdkSourceLevel parameter with the value of 15. For example:

   <jspAttributes xmi:id="JSPAttribute_1" name="jdkSourceLevel" value="15"/>

   Note: The integer (_1) in JSPAttribute_1 must be unique within the file.

4. Save the ibm-web-ext.xmi file.

5. Restart WebSphere Application Server for the new value to take effect.

For more information about the jdkSourceLevel parameter as well as other JSP engine configuration parameters, see:

http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/topic/com.ibm.websphere.nd.doc/info/ae/ae/rweb_jspengine.html

Post-Deployment Tasks

Using the ssoadm and ampassword Utilities

The setup script in ssoAdminTools.zip installs the utilities and scripts. For information, see Chapter 6, Installing the OpenSSO Enterprise Utilities and Scripts.

1. Before you run the setup script to install the utilities and scripts, modify the setup script. Before -cp ... in the last line, insert:

   -D"amCryptoDescriptor.provider=IBMJCE" -D"amKeyGenDescriptor.provider=IBMJCE"

2. Before you run ssoadm, add the following items to the ssoadm script:

   • Add xalan.jar to the classpath after openfedlib.jar. For example:

     ${TOOLS_HOME}/lib/xalan.jar

   • Add the following items before com.sun.identity.cli.CommandManager:

     -D"amKeyGenDescriptor.provider=IBMJCE" -D"amCryptoDescriptor.provider=IBMJCE"

3. Before you run ampassword, add the following items to the ampassword script before com.iplanet.services.ldap.ServerConfigMgr:

   -D"amCryptoDescriptor.provider=IBMJCE" -D"amKeyGenDescriptor.provider=IBMJCE"