Loading

Monday, June 9, 2008

How To - 10.1.3 OWSM: Changing database location for monitoring data

To change the database where OWSM monitoring metrics are stored, follow these steps.
  1. Load OWSM schema in the target database by running irca script.
  2. Go to ORACLE_HOME/owsm/config/coreman directory, and put new database details in the following properties
    • monitor.repository.* in monitor-config-installer.properties
    • monitor.repository.* in collector-config-installer.properties
  3. Obfuscate the passwords in the above mentioned files using wsmadmin tool
    ORACLE_HOME/owsm/bin/wsmadmin encodePasswords ORACLE_HOME/owsm/config/coreman/monitor-config-installer.properties monitor.repository.password
  4. Redeploy the monitor application by running
    ORACLE_HOME/owsm/bin/wsmadmin deploy monitor
Monitoring metrics will be sent to the newly configured database.

How To - 10.1.3 OWSM: Changing database location for Log policy step

When you configure Log policy step in the policy pipeline to log the SOAP message, the message is stored in OWSM database. You may want to log the message for audit, non-repudiation or debugging.
Anyways, if you want to relocate your SOAP message logging to another database, then follow these steps.
  1. Load OWSM schema in the target database by running irca script.
  2. Login to OWSM Control, go to Policy Management, and click on Edit button for the gateway or agent where you have the Log policy step.
  3. Modify cfluent.messagelog.db.* properties, click the save button, and finally click the commit link.
With the next request received by the gateway/agent message logs will be stored in the new database.

Tuesday, June 3, 2008

FAQ - OWSM 10.1.3 : Does OWSM support FCF with Oracle RAC database?

OWSM supports connections to Oracle RAC database (which is typically used in HA situations) using the multi node syntax for entering jdbc url viz. host1:port^host2:port. But, it doesn't support fast connection failover (FCF) yet.
Note: OWSM uses its own connection pooling mechanism to connect to the database instead of using the application server connection pool.