Monitor then fires messages at the BPM cell, using this alias. The alias, as created on the BPM cell, also known as a Java2Connectivity (J2C) Authentication Alias, is then used to map the alias to a real user only known to/by the BPM cell.
The documentation is quite explicit in this: -
Guess which fool didn't read point (C) above ?
Yes, you've guessed it.
I created an alias called EventEmitterAlias via the WAS Admin GUI ( Integrated Solutions Console ), and didn't notice that the name automatically picked up the prefix of dmgr meaning that I had an alias called dmgr/EventEmitterAlias.
So Monitor fired a message to BPM, expecting to find EventEmitterAlias, but BPM didn't know about that one.
Long story short, this led to exceptions such as: -
[5/12/14 15:22:25:971 CDT] 0000029c MDBEmitter E com.ibm.wbimonitor.mdbemitter.MDBEmitter onMessage(Message message) CWMDS6902E
: The following exception occurred when processing the XML and sending CBE:
No authentication data.
[5/12/14 15:22:26:031 CDT] 000001a6 EmitterUtils E com.ibm.wbimonitor.emitter.utils.EmitterUtils getInstance() CWMDS6818E: The Monitor emitter cannot be obtained. Will retry in 15 seconds...
: The following exception occurred when processing the XML and sending CBE:
No authentication data.
[5/12/14 15:22:26:031 CDT] 000001a6 EmitterUtils E com.ibm.wbimonitor.emitter.utils.EmitterUtils getInstance() CWMDS6818E: The Monitor emitter cannot be obtained. Will retry in 15 seconds...
in the SystemOut.log file on the BPM ( Process Center ) box.
Once one of my colleagues realised where I'd gone wrong, and we recreated the alias and restarted BPM, all was well.
This, plus my earlier LTPA issues, represents a really useful set of experiences, to which I know I'll refer back :-)
No comments:
Post a Comment