Portal, Express Beta Version 6.1 Operating systems: i5/OS, Linux,Windows

Defining WebSphere Application Server variables

During the security configuration process with eTrust SiteMinder, the SMConfigFile parameter in the wkplc_comp.properties file is used to specify the location of the eTrust SiteMinder TAI configuration file.

1. Choose one of the following options to define the variables:

   Option	Description
   On each node	Define the same path to the TAI configuration file
   From the deployment manager administrative console	Perform the following steps to define a WebSphere Application Server variable that can then be passed to each application server in the cluster: Click Environment > Manage WebSphere Variables. Specify WP01 as the node in the scope field, click Apply, and then click New. Enter SITEMINDER_TAI_LOCATION as the variable name and the directory path where the configuration file is located on node WP01 (such as c:\netegrity\smwastai\). Click OK. Specify WP02 as the node in the scope field, click Apply, and then click New. Enter SITEMINDER_TAI_LOCATION as the variable name and the directory path where the configuration file is located on node WP02 (such as /usr/netegrity/smwastai/). Click OK. Repeat these steps for any other nodes in the cluster. Save the changes to update the deployment manager master configuration. Edit the wkplc_comp.properties file on each node, and enter SMConfigFile=WebAgent.conf for the SMConfigFile parameter.

2. Optional: If you defined the WebSphere Application Server variable from the deployment manager administrative console, perform the following steps on each application server to create a new custom property:

   1. Click Servers > Application Server in the administrative console.
   2. Click the name of the WebSphere Portal Express application server.
   3. Click Process Definition > Java Virtual Machine > Custom properties.
   4. Click New, and enter smasa.home for the name of the new property and ${SITEMINDER_TAI_LOCATION} for the property value.
   5. Click OK, and save your changes.
   6. Repeat these steps for each application server.