- Stop all the Applications Manager processes.
For directions on stopping and starting the processes, see topics 1.8 Starting and Stopping the Applications Manager Processes in UNIX and 1.9 Starting and Stopping the Applications Manager Processes in Windows.
- Before changing the password on the Oracle side, change the name/password for your database login in Applications Manager. If the password is already changed, you will need to go into SQL*Plus and update the so_ids table. To change the database login, issue the following SQL statements. You may not need to set a connect string.
update so_ids set so_login = '<new_DB_login>' where so_login = '<old_DB_login>';
update so_ids set so_passwd = '<new_DB_password>' where so_login = '<new_DB_login>';
update so_ids set so_encrypted = 'N' where so_login = '<new_DB_login>';
- Change the password in Oracle.
- Edit the automation engine line in the Masters.properties file in the data directory. The automation engine line uses the format <Master name>=<IP address> <login name> <port> <SID> <Encrypted Y/N> ENC:<encrypted user name>\=\= ENC:<encrypted password>\=\=.
#Mon Aug 22 13:58:56 PDT 2011
V80LINUX=172.16.147.6 172.16.147.6 1521 XE N <Oracle login> <password>
- If the database login name was changed, edit the O~DBLOGIN~ line in the ISAIMPORT.dat file in the map directory. A sample is shown below:
- Start the Applications Manager processes. Starting the processes will encrypt the Masters.properties file.
- From the command prompt, issue the following command to encrypt the password in the so_ids table: