Importing event types from IBM Integration Bus
If you have a flow in WebSphere® Message Broker or IBM® Integration Bus that emits monitoring events, you can import and use those events in Insight Designer. You use a wizard to import the event definitions, and to create the event types in the business object model (BOM). The import wizard also defines an inbound binding in a connectivity definition (.cdef) file.
Before you begin
Before you begin, you must export the message flow from WebSphere Message Broker or IBM Integration Bus. To export the message flow, complete the first step of the following task: Creating a monitor model for WebSphere Business Monitor V7 or later.
About this task
You use an import wizard to import the monitoring events into a BOM in Insight Designer. The import wizard also generates an inbound binding and the classifications and XSL transformations that classify and transform inbound monitoring events into a form that can be used by Decision Server Insights.
Procedure
- Right-click the solution project, and click Import.
- Expand Insight Designer, select Event Types from IBM Integration Bus, and click Next.
- Browse to select the file that you exported from WebSphere Message Broker or IBM Integration Bus.
- Select the events that you want to import.
- Click Next.
- Select the solution project for which you want to create the events and entities.
- Provide a name for the BOM entry.
- Either choose a name for a new binding, or select an existing binding from your solution. The wizard prompts you with a list of the bindings that are suitable for the events to be imported.
- Click Next.
- Enter a package name in which you want the selected events to be defined.
- In the XML namespace field, enter the XML namespace to which you would like your events to belong.
- Optional: Rename the events to give them more meaningful type names. You can edit the names in the right hand column of the table.
- Click Next.
- Optional: Edit the package for any additional types to be imported from the application monitoring information .zip file.
- Click Finish.
Results
- A BOM entry under the bom folder of the BOM project.
- An inbound binding in one of the connectivity definition (.cdef) files in the Connectivity Definitions folder of the solution project.
- An XSL transformation (.xsl) file for each event in the Transformations folder in the solution project.
What to do next
Define an inbound JMS endpoint in a connectivity definition file. This endpoint listens for the emitted monitoring events.
You can now use these events in your agents and global aggregates. When you export the solution connectivity, the endpoint must be configured to monitor the appropriate JMS topic in the Export Connectivity Configuration wizard. Before you deploy the solution connectivity, you must also edit the server.xml file to include the WebSphere MQ features and specify the wmqJmsClient.rar file path.