Skip to main content

developerWorks >  Tivoli  >  Forums  >  IBM Tivoli Composite Application Monitoring Forum  >  developerWorks

monitor Datapower with ITCAM for SOA: nothing shows up on TEPS?    Point your RSS reader here for a feed of the latest messages in this thread


     
 
 
My developerWorks
 Welcome, Guest
Sign in or register
This question is not answered.

Reply to this Thread Reply to this Thread Post New Thread Post New Thread Watch list Watch list Forum settings Forum settings Help Help
Permlink Replies: 2 - Pages: 1 - Last Post: Nov 17, 2009 2:42 PM Last Post By: BingLiang
BingLiang

Posts: 2
Registered: Nov 04, 2009 12:02:42 PM
monitor Datapower with ITCAM for SOA: nothing shows up on TEPS?
Posted: Nov 04, 2009 12:17:18 PM 		 
Click to report abuse...   Click to reply to this thread Reply
I'm settting up a datapower monitoring environment involving three boxes, ITCAM for SOA as a middle guy between DataPower and TEPS. I'm able to run configDC and startDPDC successfully from the middle man box (which means datacollector is talking to datapower box), and from TEPS, I'm able to see the middle man box which means ITCAM for SOA is talking to TEPS. However, from TEPS, I'm not able to see anything about Datapower, no Datapower node. Anyone got experiences in settup up this kind of environment?
Thanks.
Bing
enrico.vannini

Posts: 15
Registered: Mar 14, 2006 05:17:24 AM
Re: monitor Datapower with ITCAM for SOA: nothing shows up on TEPS?
Posted: Nov 16, 2009 01:58:54 PM   in response to: BingLiang in response to: BingLiang's post 		 
Click to report abuse...   Click to reply to this thread Reply
did you solve your issue?

if not I first of all suggest to stop the TEMA and let the DPDC running.

Then on the agent go in kd4/logs dir (named something like that, where many log files are stored.
If you see some metric file created there while you have load, then it mean that the DPDC is working fine, but for some reason TEMA is not able to get those files and upload them to the TEMS.

For my experience, most likely you won't get anything there (most of the time, when no data are showed, there is something on DPDC side, rather then o TEMA side).

If anyway metric files are collected there but not showed on tep, check time stamp on all the components (DP, TEMA, TEMS), and posisbly look for historical data. I would assume there is a mismatch

If no data showed there, many things you can check on DP side:
check XML mgmt interface on DP:
o Login DP
o Objects management--> xml mgmt interface
o Check WS-management end point and AMP endpoint
o Admin State = enabled
o Check that is up
then For each domain:
o Services -> miscellaneous  web service agent
o Admin State = enabled
then Check the user group for the user that you have assigned:
o See the manual
From Administrationdevice  Time settings you can set the time zone
To set date and time: console (the icon in the main page, not on the left bar)  system control

then to check that there is proper load on DP
• Config WS proxy  WSDL  show probes  enable

check that your DPDC is actaully connected to DP:
• You can confirm that there is activity being monitored on the appliance using the WSM Agent Status and WSM Agent Subscribers pages on the DataPower WebUI. They're under Status -> Web Service in the WebUI portfolio on the left-hand side. You should see one Subscriber for each data collector that's connected to the appliance. On the WSM Agent Subscribers page, you should see the subscriber as it's subscribed to each of its configured domains. Plus, this page shows counters for the numbers of records transmitted -- I don't know exactly what the numbers mean, but if you see all zeros for a given domain, that indicates that there is no activity on that domain's subscription.

• Check the KD4.8.DataPower.operations.log.
If the file does not exist, DP data collector was not started. If there are communication errors in that file, the DC was not able to talk to the appliance; fix the configuration using kd4configdc.

• You should also check whether they're using a Web Services Proxy or a Multi-Protocol Gateway service on their appliance. ITCAM4SOA cannot see Multi-Protocol Gateway traffic unless they're using firmware 3.7.1 and have added special code to their Processing Rules.

hope it helps
BingLiang

Posts: 2
Registered: Nov 04, 2009 12:02:42 PM
Re: monitor Datapower with ITCAM for SOA: nothing shows up on TEPS?
Posted: Nov 17, 2009 02:42:40 PM   in response to: enrico.vannini in response to: enrico.vannini's post 		 
Click to report abuse...   Click to reply to this thread Reply
Thanks for the checklist.

I don't see metric files created. So the problem resides between DPDC and DP. I checked your list against DP, I do see a subscriber listed under WSM Agent Status and WSM Agent Subscribers for the domains specified in DPConfig. So DPDC is connected to DP.

However, in our KD4.8.DataPower.operations.log file, after startDPDC for a while, and from time to time, we got SocketException:

2009-11-08 11:46:07.407-05:00 main KD4WT0001I ITMDPDataCollector active, build level 200903051848.
2009-11-08 11:46:07.610-05:00 main KD4DP0006W The data collector is running. Enter STOP to stop the data collector.
2009-11-08 11:46:07.610-05:00 DPDevMgrThread KD4WT0001I ITMDPDeviceManager active, build level 200903051848.
2009-11-08 11:46:10.360-05:00 ebs01.raleigh.ibm.com:default,dp_common,ieb-issw:X150:-665803625 KD4WT0001I com.ibm.management.soa.agent.ITMCriteria active, build level 200903051848.
2009-11-08 11:46:10.375-05:00 ebs01.raleigh.ibm.com:default,dp_common,ieb-issw:X150:-665803625 KD4WT0001I DPDeviceSession active, build level 200903051848.
2009-11-08 21:46:49.935-05:00 ebs01.raleigh.ibm.com:default,dp_common,ieb-issw:X150:-665803625 java.net.SocketException: Operation timed out: connect:could be due to invalid address
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java(Compiled Code))
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java(Compiled Code))
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java(Compiled Code))
at java.net.Socket.connect(Socket.java(Compiled Code))
at java.net.Socket.connect(Socket.java(Compiled Code))
at java.net.Socket.<init>(Socket.java(Compiled Code))
at java.net.Socket.<init>(Socket.java(Inlined Compiled Code))
at com.ibm.jsse.bv.<init>(Unknown Source)
at com.ibm.jsse.JSSESocketFactory.createSocket(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.b.b(Unknown Source)
at com.ibm.net.ssl.www.protocol.http.cb.a(Unknown Source)
at com.ibm.net.ssl.www.protocol.http.cb.p(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.b.<init>(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.b.a(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.b.a(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.b.a(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.q.c(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown Source)
at com.ibm.net.ssl.www.protocol.http.cj.getOutputStream(Unknown Source)
at com.ibm.net.ssl.www.protocol.https.t.getOutputStream(Unknown Source)
at com.ibm.management.soa.agent.dp.DPSoapHttpSession.post(DPSoapHttpSession.java(Compiled Code))
at com.ibm.management.soa.agent.dp.DPDomain.pullMetrics(DPDomain.java(Compiled Code))
at com.ibm.management.soa.agent.dp.DPDeviceSession.run(DPDeviceSession.java(Compiled Code))
at java.lang.Thread.run(Thread.java:570)

Any thoughts of what went wrong here?

And, while checking your list against DP, the only thing we didn't do at this point is:

"then to check that there is proper load on DP
• Config WS proxy  WSDL  show probes  enable"

What's the rationale of that? And regardless of that, shouldn't TEPS at least display the DP domain names as node, if not the service traffic?

Thank you in advance for your further advise.

Bing
Pages: 1
Go Back Back to Thread List

Update your My developerWorks profile and start connecting with others.

Point your RSS reader here for a feed of the latest messages in all forums