Versions Compared

Old Version 15

changes.mady.by.user Amit Munwes

Saved on

compared with

New Version Current

changes.mady.by.user Avi Falah

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Verify WS-M capturing is enabled: by following the directions under WS-M setup for device and WS-M Subscriptions for All Domains (Optional) as they appear in Adding Monitored Devices

  • Verify on your IDG that the subscriptions are created: In the expected domain navigate to Status → Web Service → WSM Agent Status (see blue hilight in the screenshot below). You should see 1 Active subscriber of polled type (see red highlight).
    If payloads were captured then they will be reported as Records seen.
    Additional statistic data can be seen on WSM:

    • If Records Seen value is 0, this may mean you do not have running transactions

    • If Active Subscribers value  is 1 and the value of Polled Subscribers is 0 - ensure you have followed the next step:

    • Check that the WS-M Agent in IDG is configured correctly:

    Image RemovedImage Added

    • DPOD expects the WS-M Agent to be enabled and Capture Mode to be set to All

    • If your WS-M agent is enabled in IDG, you can create a subscription on DPOD by performing step WS-M Subscriptions for All Domains (Optional) on Adding Monitored Devices. If the Records Seen counter increases by any running transaction -  then the payload should arrive at the DPOD WS-M Agent

...

  • Verify the DPOD WS-M agent is up and running - Check System Services Status with the CLIusing Command Line Interface (CLI) (Option 3 - Check Status).

  • Verify that the DPOD WS-M agent status is green on Check System Status Using the Web Console. This means that the keep alive message are processed.

  • Inspect the WS-M logs for any exceptions. Logs may be accessed using Telnet, at the following path: /logs/wsmAgents/<Agent-name>/agent-flume_<Agent-name>.log. 
    Normal WS-M log records should show:

    Code Block
    11/10/XXXX 08:26:03,477- INFO o.m.a.f.h.NHttpFileServer [I/O-dispatch-2] wsmHttpSource1 Incoming entity content (bytes): 2908.  ← an actual payload arrived
11/10/XXXX 08:26:10,166- INFO o.m.a.f.h.NHttpFileServer [I/O-dispatch-3] wsmHttpSource1 Incoming entity content (bytes): 2220.  ← size 2220 means usually keep alive message

  • To find exceptions in your logs, enter the search term ' ERROR ' (leading and trailing space). Contact support with any exception found.

  • In some cases DPOD may filter messages out because of their size. Please see the following technote: Large Payload is not Displayed when Captured via WS-M

...