Encrypting the jndi.properties File
The user credentials in the jndi.properties file are stored in clear text format. To fix this, it is recommended that you encrypt the jndi.properties file as shown in the following procedure.
To encrypt the jndi.properties file
Set up the Siebel Server and the JMS server.
Create a named subsystem based on JMSSubsys.
Encrypt the jndi.properties file using the batch script files.
Note the following:
The batch script files include the following: EncodeJndiProperties.sh, EncodeJndiProperties.bat, Siebel.jar, and ClientAppEAIJMSBsvDll.
The batch script files use the java-based encryption utility, com.siebel.eai.jms.EncodeJndiProperties, to encrypt the jndi.properties file and set the following properties in the JMSSubsys subsystem:
JNDIEncryptionCheck. Boolean value used to verify whether the jndi.properties file is encrypted (True) or not (False). The default value for JNDIEncryptionCheck is True.
JNDIEncryptionSeed. Seed value used to encrypt and decrypt the password.
The prerequisites for running the batch scripts include:
<JNDI file name> The full path to the jndi.properties file which is to be encrypted.
<Encryption seed> The encryption seed for encrypting the jndi.properties credentials.
<Gateway Name> The gateway name.
<Gateway Port> The gateway port.
<Siebel Enterprise> The Siebel enterprise name.
<Username> The username to connect to the gateway.
<Password> The password to connect to the server.
<Name Subsystem> The named subsystem to set the seed for decryption.
The batch scripts expect the user to set the SIEBEL_ROOT and JAVA_HOME environment variables.
Check the jndi.properties file to confirm that the password is actually encrypted.
To confirm that the setup works, use the Business Service simulator to run a test to set messages to the JMS server using the named subsystem created earlier in this procedure.