[TME10}[ITM] omnibus SitForwarder

Hello Yoga,

Make sure all the omnibus triggers .sql supplied have been run, if in 
doubt run again, no harm, the way an event is put into cache is by running 
a script via PA which Rafael mentioned - so Omnibus must be able to do 
that which means all the PA setup needs to have been done and shown to 
work - try getting a PA status to check.
Is the Sitforwarder process running, even though it may create a running 
file confirm to see if there is the process there?
That sitforwarder process waits for entries into that intermediate cache, 
then makes a SOAP connection back to TEMS, the test.sh is a check to see 
if that can be done if all defaults used.
Lastly, the node name used in the config when setting up SUF, must be the 
same as is contained in the event message, not short name in event, config 
as fqdn or vice versa....

        Dave.

6.2.3 FP2 is the latest, major changes at 6.2.3 FP1....







Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]