Updating configuration batch and script files

A number of script and batch files must be updated to reflect your environment before you can enable application security.

Before you begin

Configuration batch and script files can be run against WebSphere® Application Server V6.0.2 and V6.1. Because WebSphere Application Server V6.0.2 and V6.1 have different classpaths, you must specify the WebSphere Application Server classpath before you run your script using commenting.

In the following example, the wsdl2tam.sh script is set to run against WebSphere Application Server V6.1:

# The required WAS 6.0.2 jars.

# export WAS_JARS=$WAS_HOME/lib/j2ee.jar:$WAS_HOME/lib/wsdl4j.jar

# The required WAS 6.1 jars.

export WAS_JARS=$WAS_HOME/lib/j2ee.jar:$WAS_HOME/plugins/
	com.ibm.ws.runtime_6.1.0.jar

To run this script against WebSphere Application Server V6.0.2, uncomment the earlier WAS-JARS export line and comment the current WAS_JAR export line; for example:

# The required WAS 6.0.2 jars.

  export WAS_JARS=$WAS_HOME/lib/j2ee.jar:$WAS_HOME/lib/wsdl4j.jar

# The required WAS 6.1 jars.

# export WAS_JARS=$WAS_HOME/lib/j2ee.jar:$WAS_HOME/plugins/
	com.ibm.ws.runtime_6.1.0.jar

Note: If you installed the Web services security management component on z/OS®, the HFS in which these files were installed might be read-only. If so, copy the files that require updates from the read-only location (such as /usr/lpp/FIM/wssm/etc) to your own Tivoli® Federated Identity Manager directory before making the changes.