WID 6012.9 Export/Import JMS Binding

WID 6012.9 Export/Import JMS Binding How to

WID V6.0.1.2, Interim Fix 009

Contact us...

How to export a component using JMS Binding

This is the completed export nodes using various export bindings. You use exports to make your services available to other components in external modules.
Right-click the component you want to export and select Generate Export > JMS Binding.
Select Configure new messaging provider resources to automatically define Server resources during project deployment (i.e, Websphere Integration Developer 6.01.2 will define the server resources when you initially deploy the project). Set the Serialization type to JMS TextMessage
WID automatically defined the following JMS export settings. The following resources will be setup by default when you deploy the project to the Server.

How to import a component using JMS Binding

This is the completed import node using JMS bindings. You use imports to invoke another component located in another module.
Drag the service (Export node) from the other module (i.e, the ServiceProvider module) and drag it to the module (i.e ServiceConsumer module) that wants to use it.
This is an informational message. Note: Deploy the external module first before deploying the invoking module. Click OK to continue.
WID automatically defined the following JMS import settings. Review and compare the Export/Import settings automatically defined by WID 6012.	Export Import

JMS resources generated by Websphere Integration Developer

Resources are generated by default by WID 6.0.1.2 when you select Configure new messaging provider resources during the configuration of JMS Export Service. We will look at the following resources (CCambil) generated by WID: Resources > JMS Providers > Default messaging Service integration > Buses
Default Messaging Provider A JMS provider enables messaging based on the Java Messaging Service (JMS). It provides J2EE connection factories to create connections for JMS destinations. This panel is used to manage the default messaging provider and its JMS resources. Select Server : Server1 and click Apply. We will look at the following resources: JMS connection factory JMS queue JMS activation specification
JMS connection factory A JMS connection factory is used to create connections to the associated JMS provider of JMS destinations, for both point-to-point and publish/subscribe messaging. Use connection factory administrative objects to manage JMS connection factories for the default messaging provider.
JMS Queue A JMS queue is used as a destination for point-to-point messaging. Use JMS queue destination administrative objects to manage JMS queues for the default messaging provider.
JMS activation specification A JMS activation specification is associated with one or more message-driven beans and provides the configuration necessary for them to receive messages.
Service Integration - Buses A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of interconnected servers and clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members. Click on SCA.APPLICATION.widCell.Bus to display messaging bus for Service.
SCA.APPLICATION.widCell.Bus A service integration bus supports applications using message-based and service-oriented architectures. A bus is a group of interconnected servers and clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members. Click on Destinations to display destinations.
Destinations A bus destination is a virtual place, within a service integration bus, to which applications attach as producers, consumers, or both to exchange messages.