Capturing events to the same database as the event runtime

To capture events to the same database as the event runtime for later event replay and analysis, you can use the Event Capture widget or the WebSphere® Application Server administrative scripting tool, wsadmin.

• Capturing events by using the Event Capture widget:
  1. Access the Event Capture widget (see Accessing Event Widgets for more information).
  2. Click Start Capture. If event capture does not start because event capture is already in progress, it is most likely that another user on this computer has initiated event capture.
  3. Once event capture is in progress, ensure your application is running and leave a sufficient period for the events you want to capture to arrive at Decision Server Events.
  4. Stop event capture by opening the Event Capture widget and clicking Stop Capture.
• Capturing events using wsadmin:
  1. Change to the was_install_dir/bin directory and start the wsadmin scripting tool. For more details of the use of wsadmin, see Using the wsadmin scripting tool.

     wsadmin

  2. Run the wbeStartEventCapture administrative command which has the following optional parameters:

     server

     The name of the WebSphere Application Server server on which to capture events. The name must be specified in conjunction with the node.

     node

     The name of the WebSphere Application Server node on which to capture events. The name must be specified in conjunction with the server.

     cluster

     The name of the WebSphere Application Server cluster on which to capture events. Neither a server name nor a node name can be specified.

     If none of these optional parameters are specified, then the server to which the wsadmin session is connected is used.

     If event capture does not start because event capture is already in progress, it is most likely that another user on this computer has initiated event capture.

  3. Once event capture is in progress, ensure your application is running and leave a sufficient period for the events you want to capture to arrive at Decision Server Events.
  4. To stop capture, change to the was_install_dir/bin directory and start the wsadmin scripting tool:

     wsadmin

     Run the wbeStopEventCapture administrative command which has the same optional parameters as the wbeStartEventCapture administrative command.
  5. In addition, in a script environment, you might want to determine whether event capture is in progress. To do this, run the wbeGetEventCaptureStatus administrative command which has the same optional parameters as the wbeStartEventCapture administrative command.

wsadmin -lang jython