Create the AMJRTE properties file
Overview
Create the AMJRTE properties files before configuring Tivoli Access Manager for authentication, authorization, credential vault, and/or user provisioning.
Create the AMJRTE properties file
Run the following steps on every node...
- Edit...
WP_PROFILE/ConfigEngine/properties/wkplc_comp.properties
- Enter the following parameters under the AMJRTE connection parameters heading:
wp.ac.impl.PDAdminId Administrative TAM user. wp.ac.impl.PDAdminPwd Administrative TAM password. wp.ac.impl.PDPermPath Location of the TAM AMJRTE properties file. Created by TAM SvrSslCfg command (which is called by Portal's run-svrssl-config utility). Contains information such as:
- Policy Server host name
- Ports
- Version of AMJRTE
- Path to encryption keys
Default: ${WasHome}/java/jre/PdPerm.properties
wp.ac.impl.PDServerName Unique application name used to create a new Tivoli server in the Access Manager Policy server. Each node in the cluster must specify a unique value before running run-svrssl-config.
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 TAM Policy servers used when running SvrSslCfg. wp.ac.impl.PDAuthzServerList Host name, port, and priority combination for TAM authorization servers. wp.ac.impl.PDKeyPath Encryption keys used for the SSL communication between AMJRTE and TAM.
- Save changes to the properties file.
- Create the AMJRTE properties file:
cd WP_PROFILE/ConfigEngine
./ConfigEngine.sh run-svrssl-config -Dwp.ac.impl.PDAdminPwd=fooIf the configuration task fails, validate the values in the wkplc_comp.properties file.
The following files are created:
- WAS_HOME/java/jre/PolicyDirector/PdPerm.properties
- WAS_HOME/java/jre/lib/security/PdPerm.ks
Parent
Configure TAM