Monitoring from the Integration
Use any of the following to monitor the integration:
Monitoring Using WebLogic SOA Enterprise Manager
Perform the following steps to monitor through WebLogic SOA Enterprise Manager:
1. Log in to the WebLogic SOA Server Enterprise Manager, and then navigate to SOA > SOA-Infra > CCB2-MDM2.
All composite processes deployed for integration are available under the partition CCB2-MDM2.
2. Select the appropriate process to list all the instances for the processes sorted by time of execution. The instances also have the request ID as part of the flow instance name.
3. Click the appropriate process instance and it displays the flow for the process. The composite flow lists all activities in the process instance.
Monitoring Using WebLogic Logs
Login to the machine where SOA server is installed. The SOA logs are stored in: <WebLogic installation folder>/user_projects/domains/<SOA Domain name>/servers/<SOA Server name>/logs
Example: / Oracle/Middleware/Oracle_Home/user_projects/domains/soa_domain/servers/soa_server1/logs
Monitoring the Queues Using the WebLogic Console
1. Login to the WebLogic Console, and then navigate to the Services à Messaging à JMS Modules. All queues used for the integration are available in the JMS Module CCB2MDM2JM.
2. Select the appropriate queue on the list and navigate to the Monitor tab.
In this tab, the user can verify whether or not the message is stuck in the queue. The Consumers Current column indicates the number of consumers listening in the queue. Messages may be hung if there are no consumers listening to the queue. If the Consumers Current column is 0, it means no consumers are listening to the queue.
3. To check the message rolled back to the error queue, select the appropriate error queue on the list and navigate to the Monitoring tab. The user can see the message in this tab.
Data Purge
To maintain maximum system integrity, the Oracle Fusion Middleware database should be purged periodically.
Oracle SOA Suite 14c provides pre-tuned database profiles to automatically enable appropriate performance features, based on the expected data size. It also enables auto-purge to prevent bloating of the database.
For more information about purging, refer to the SOA documentation at:
https://docs.oracle.com/en/middleware/soa-suite/soa/14.1.2/index.html