Understanding Password Encryption in Template File

Sensitive data, like passwords, can be encrypted so that these properties are not exposed if you share the template file among multiple environments and multiple development or testing teams.

The following properties are currently identified as being sensitive data:

• userpass

• env.nodex_search_admin_password

• env.default_local_node_pass

• env.gateway_password

• env.ib_appserver_domain_password

• env.gateway_keystore_password

• env.nodex_search_read_password

• env.search_call_back_password

To encrypt sensitive data, run the PTEM_CONFIG Application Engine program with the property encrypt_password set to True in the template file. This will generate a new template file named <original template file name>_encrypted in the location of the original template file.

The encrypted template file can be used as input to run the PTEM_CONFIG Application Engine program by providing the property decrypt_password=true in the template file, which internally decrypts the sensitive properties for configuring the environment.