I am using WmMonitor to monitor two IS instances connecting to a single broker in a single client group. The IS instance with WmMonitor has WmLogUtil installed. The second IS instance is used as JDBC adapter only. We need to have this set up so that JDBC adapter is hosted in the same machine as the database. (Similar to adapters running close to the resource).
I want to log documents published by both IS instances. However WmLogUtil throws a “null pointer exception” when logging documents published by JDBC adapter. WM Support say I need to install all publishable documents from the JDBC adapter (the second IS instance) to the IS instance which runs WmLogUtil/WmMonitor.
The problem is I can’t import all the documents published by the JDBC adapter into the monitoring IS instance to log the documents. The JDBC adapter has got a “AdapterBasicNotificationPublishDocument” as one of its publishable document. This document is closely associated with “AdapterBasicNotification” operation. To import this document I also need to import the adapter operation associated with it and also adapter connection to be able to see the fields in the document.
Basically this means having the JDBC adapter with similar configuration in the first IS as the second IS instance.This set up really negates the purpose of having a separate IS instance for the JDBC adapter.
How to log the documents published by JDBC adapter with this architecture? How do you log documents publised by multiple adapters having their own IS instances using a single IS with WmLogutil installed?
As I understand from WM support
- There is only one WmLogUtil can be installed per broker &
- The IS with WmLogUtil should have all the publishable documents.
I am running IS6.1
and Broker6.1 SP2