8.11.1 Modify OFSAA Infrastructure Config Schema Password in a Non Wallet-Based Setup

To change the Config Schema password, perform the following steps:

1. Shutdown the OFSAAI App service:
   cd $FIC_APP_HOME/common/FICServer/bin
   ./stopofsaai.sh
2. Change the Config Schema User Password in the database.
3. Delete the $FIC_HOME/conf/Reveleus.SEC file.
4. Navigate to the $FIC_HOME/utility/updateatomicpwd/bin Directory and execute the Utility as shown in the following:
   Syntax:
   ./rotateAtomicDBPwd.sh <CONFIG/ATOMICALIASNAME> <DB_USER> <DB_PASS>
   For example,
   ./rotateAtomicDBPwd.sh CONFIG acte_ofsaaconf password123
   The execution of the Utility generates the Reveleus.SEC File in the $FIC_HOME/conf/ Directory and a new Encrypted Schema Password is reflected in the DB_MASTER and AAI_DB_AUTH_ALIAS Tables in the row which displays the Config Schema.

   Note:

   If you do not delete the existing Reveleus.SEC File, then a backup of the file is saved with the Reveleus.SEC_cfgbkp name before generating the new Reveleus.SEC File.
5. Restart the Infrastructure Server.
6. If you are using Apache Tomcat as the Web server, update the <Context> -> Resource tag details in the Server.xml file from the $CATALINA_HOME/conf directory. For Tomcat, both Config Schema (FICMASTER resource) and Atomic Schema (<INFODOM_NAME> resource) exist.
   If you are using WebSphere as a Web Server:
   1. Log in to the WebSphere Administration Console, from the left side menu.
   2. Navigate to Resources >JDBC >Data Sources. A list of data sources are populated on the right side.
   3. Select the appropriate Data Source and edit the connection details. (In this case, both Config and Atomic Data Sources must be modified).
   If you are using WebLogic as a Web Server:
   1. Log in to the WebLogic Administration Console, from the left side menu
   2. Under Domain Structure list box, expand the appropriate Domain and navigate to Services > JDBC >Data Sources. A list of data sources are populated on the right side.
   3. Select the appropriate Data Source and edit the connection details. (In this case, both Config and Atomic Data Sources must be modified).
7. Post successful startup of the service, if required, the Infrastructure Server may be shut down and restarted in the background using nohup mode.