Create the AMJRTE properties file - Tivoli Access Manager

1. Edit wkplc_comp.properties

2. Enter only the following parameters in wkplc_comp.properties under the AMJRTE connection parameters heading:

   Cluster note: The following parameters must match on all nodes in the clustered environment.

   wp.ac.impl.PDAdminId	User ID for the administrative TAM user
   wp.ac.impl.PDAdminPwd	Password for the administrative TAM user
   wp.ac.impl.PDPermPath	Location of the TAM AMJRTE properties file
   wp.ac.impl.PDServerName	Unique application name used to create a new Tivoli server in the Access Manager Policy server
   wp.ac.impl.SvrSslCfgPort	Configuration port for the application name
   wp.ac.impl.SvrSslCfgMode	Configuration mode of the SvrSslCfg command
   wp.ac.impl.TamHost	Name of the TAM Policy server used when running PDJrteCfg
   wp.ac.impl.PDPolicyServerList	Host name, port, and priority combinations for the TAM Policy servers used when running SvrSslCfg
   wp.ac.impl.PDAuthzServerList	Host name, port, and priority combination for the TAM authorization servers
   wp.ac.impl.PDKeyPath	Encryption keys used for the SSL communication between AMJRTE and TAM

   Cluster note: The wp.ac.impl.PDServerName parameter represents an individually configured AMJRTE connection to TAM. Each node in the cluster must specify a unique value for the wp.ac.impl.PDServerName parameter before running run-svrssl-config.

   For example, if the cluster has four nodes, this parameter should be set differently on each node, such as amwp81, amwp82, amwp83, and amwp84.

3. Save your changes to the properties file.
   

4. Create the AMJRTE properties file:
   cd WP_PROFILE/ConfigEngine
   ./ConfigEngine.sh run-svrssl-config -Dwp.ac.impl.PDAdminPwd=foo

   If the configuration task fails, validate the values in the wkplc_comp.properties file.

   Files created...

   WAS_HOME/tivoli/tam/PdPerm.properties
   WAS_HOME/tivoli/tam/pdperm.ks

   
   Parent: Configure TAM for non-z/OS operating systems