Creating the PdPerm.properties file

The PdPerm.properties file configures the Access Manager Java Run Time Environment (AMJRTE). You must create the PdPerm.properties file before you configure IBM® Security Access Manager for authentication, authorization, Credential Vault, or user provisioning. Run the run-svrssl-config task to create the files. This task also creates the keystore file that is used to encrypt communication with Security Access Manager.

About this task

Cluster note: Complete these steps on every node in the cluster.

Procedure

  1. Use a text editor to open the wkplc_comp.properties file in the wp_profile_root/ConfigEngine/properties directory.
  2. Enter the following parameters in the wkplc_comp.properties file; go to the AMJRTE connection parameters heading:
    Cluster note: Complete this step on all nodes in the cluster. The following parameters must match on all nodes in the clustered environment. The one exception is the wp.ac.impl.PDServerName parameter.
    1. For wp.ac.impl.PDAdminId, type the user ID for the administrative Security Access Manager user.
    2. For wp.ac.impl.PDPermPath, type the fully qualified path and file name where the PdPerm.properties file is created.
    3. For wp.ac.impl.PDServerName, type the unique application name that is used to create a server in the Security Access Manager Policy server. The application name is an arbitrary name but must be unique for this server instance. You might want to use the node name for this HCL server instance.
      Cluster note: The wp.ac.impl.PDServerName parameter represents an individually configured AMJRTE connection to Security Access Manager. Therefore, each node in the cluster must specify a unique value for the wp.ac.impl.PDServerName parameter before you run the run-svrssl-config task. If the cluster has four nodes, set this parameter differently on each node; for example, amwp81, amwp82, amwp83, and amwp84.
    4. For wp.ac.impl.SvrSslCfgPort, type the configuration port for the application name. The property is ignored by the SvrSslCfgPort.
    5. For wp.ac.impl.SvrSslCfgMode, type the configuration mode of the SvrSslCfg command. The only valid value is remote.
    6. For wp.ac.impl.TamHost, type the host name of the Security Access Manager Policy server that is used when you run PDJrteCfg.
    7. For wp.ac.impl.PDPolicyServerList, type the host name, port, and priority combinations for your Security Access Manager Policy servers that are used when you run SvrSslCfg.
    8. For wp.ac.impl.PDAuthzServerList, type the host name, port, and priority combination for your Security Access Manager authorization servers.
    9. For the wp.ac.impl.PDKeyPath, type the fully qualified path and file name of the location for the keystore file. This file is created when you run the run-svrssl-config task. The keystore file holds the keys that are used to encrypt communication between the Portal node and the Security Access Manager server.
  3. Save your changes to the properties file.
  4. Open a command prompt and change to the wp_profile_root/ConfigEngine directory.
  5. Run the following task to create the PdPerm.properties file:
    • AIX® HP-UX Linux™ Solaris: ./ConfigEngine.sh run-svrssl-config -Dwp.ac.impl.PDAdminPwd=password -DWasPassword=password
    • IBM i: ConfigEngine.sh run-svrssl-config -Dwp.ac.impl.PDAdminPwd=password -DWasPassword=password
    • Windows™: ConfigEngine.bat run-svrssl-config -Dwp.ac.impl.PDAdminPwd=password -DWasPassword=password
    Note: If the configuration task fails, validate the values in the wkplc_comp.properties file.
    The following files are created:
    • PdPerm.properties
      Note: This file is in the directory path you specified for the wp.ac.impl.PDPermPath parameter.
    • pdperm.ks
      Note: This file is in the directory path you specified for the wp.ac.impl.PDKeyPath parameter.