Application ADMIN Notes

This post covers common tasks for OTM application administrators — finding the installation path, restarting the application, applying Oracle patches, and resetting admin passwords.

OTM installation path:

To find the OTM home directory, log in to the OTM application and access the PropertiesServlet:

Click List to display the current G-Log properties. Note the following property — this is the base OTM installation path:

This is referred to as $OTM_HOME throughout this post. The actual path differs per installation depending on where your system administrator placed the OTM software.

Key directories:

Restart OTM application:

First, initialize the OTM environment variables:

cd $OTM_HOME/install
./gc3env.sh

When stopping OTM, bring the web tier down first (to stop user traffic), then the app tier. When starting, reverse the order — app first, then web.

Stop the web tier:

cd $OTM_HOME/install/ohs
./glogweb-wl stop

Stop the app tier:

cd $OTM_HOME/install/weblogic
./glogapp-wl stop

Start the app tier:

cd $OTM_HOME/install/weblogic
./glogapp-wl start

Confirm the app tier is up:

cd $OTM_HOME/logs/weblogic
tail -f console.log.0

Wait for the following message in the log:

OTM Event: serverReady

Start the web tier:

cd $OTM_HOME/install/ohs
./glogweb-wl start

Confirm the web tier is up:

cd $OTM_HOME/logs/tomcat
tail -f console.log.0

Look for a message like:

INFO: Server startup in xxxxxx ms

Once both tiers are up, users can log in to the application.

Run Oracle SR scripts:

Place the script (e.g. otm_analyzer.sql) in $OTM_HOME/glog/oracle/script8, then connect to the GLOGOWNER schema via SQL*Plus and run it:

sqlplus glogowner/glogowner@OTMDB

@otm_analyzer.sql

Output is typically generated in the same folder.

Reset GLOGDBA password:

OTM connects to the database using the GLOGDBA schema password. If you change this password, you must update the G-Log properties file with the new Base64-encoded value.

On the OTM app server, generate the Base64-encoded password:

java glog.util.appclass.Base64Encoding <new_password>

Copy the output text, prefix it with {e, and set it as the value of otm.db.password in the G-Log properties file:

Restart both the app and web tiers after saving the file.

Recompile OTM DB invalid objects:

cd $OTM_HOME/glog/oracle/script8
sqlplus glogowner/glogowner@OTMDB

@recompile_invalid_objects.sql

Verify no invalid objects remain:

SELECT object_name, owner, object_type, status
FROM   all_objects
WHERE  owner  = 'GLOGOWNER'
AND    status = 'INVALID';

Reset OTM application ADMIN passwords:

OTM ships with default ADMIN accounts such as DBA.ADMIN that have full access to all OTM data and configuration. To reset their passwords:

cd $OTM_HOME/glog/oracle/script8
./update_password.sh

Change passwords for the following users (recommended default: CHANGEME, or a password of your choice):

• system
• guest
• DBA.ADMIN
• GUEST.ADMIN
• GLOG.ADMIN
• SERVPROV.ADMIN

Apply Oracle patches:

1. Download the patch from Oracle (.jar file extension) to your desktop.
2. Copy the file to $OTM_HOME/temp on both the app server and web server.
3. Bring down the OTM app and web tiers.
4. On each server, switch to $OTM_HOME/temp and run:

java -jar <filename.jar>

The installer will prompt for the OTM Home directory and, in some cases, DB connection details if the patch updates database entries.

5. If the patch install summary shows a message about running a DB script, also run:

cd $OTM_HOME/glog/oracle/script8
sqlplus /nolog @run_patch.sql

6. Start the OTM app tier, then the web tier, following the restart steps above.
7. After a successful patch install, an entry is written to:

$OTM_HOME/glog/config/glog.patches.properties