RE: [TME10}[ITM] omnibus SitForwarder

Dave,

I have updated with status except the last check mentioned by you. Not clear about the last  check.
Since I have installed NC as Netcool, I  installed SUF as Netcool.

Is the Sitforwarder process running, even though it may create a running file confirm to see if there is the process there?

/opt/IBM/SitForwarder/persistence
[netcool@tctivst2r6ap03 persistence]$ ls -la
total 16
drwxrwxr-x  2 netcool netcool 4096 Nov 23 13:24 .
drwxrwxr-x 12 netcool netcool 4096 Nov 22 15:46 ..
-rw-rw-r--  1 netcool netcool    0 Nov 23 13:24 running
-rwxr-xr-x  1 netcool netcool  166 Nov 23 11:27 situpdate.conf
-rw-rw-r--  1 netcool netcool  126 Nov 23 13:23 situser.conf

As  you notice, it only shows running but no PID is shown

When I do ps -aef, I can see the PID:
netcool   9850     1  0 13:24 pts/1    00:00:00 /opt/IBM/SitForwarder/jre/bin/java -Djlog.logCmdPort=0 -Dsuf.config.path=/opt/IBM/SitForwarder/persistence -Xrs -cp /opt/IBM/SitForwarder/jars/situpdate.jar:/opt/IBM/SitForwarder/jars/jlog.jar com.tivoli.candlenet.SituationUpdateForwarder start OMNIBUS


try getting a PA status to check

PA Status, stop and start all work fine

[netcool@tctivst2r6ap03 bin]$ ./nco_pa_status
Login Password:
-------------------------------------------------------------------------------
Service Name         Process Name         Hostname   User      Status      PID
-------------------------------------------------------------------------------
Core                 ObjectServer         tctivst2r6ap03.tiv.ecap.cciioroot      RUNNING    8709


,the test.sh is a check to see if that can be done if all defaults used

Earlier, was giving IP, I changed it and gave FQN. Test.sh gives the output as expected

[netcool@tctivst2r6ap03 bin]$ ./test.sh
Successfully connected to Tivoli Enterprise Monitoring Server tctivt2r6ra02-mgt.ecap.cciio

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

Not clear

Thanks

Yoga Iyengar
Desk: (301)-977-7884 Ext. 199
Email: [email protected]<mailto:[email protected]>
10480 Little Patuxent Parkway, Suite 1100
Columbia, MD  21044

From: [email protected] [mailto:[email protected]] On Behalf Of Dave Scarr
Sent: Friday, November 23, 2012 10:35 AM
To: [email protected]
Subject: [TME10] [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]