Académique Documents
Professionnel Documents
Culture Documents
---> In WAS 5.1 version MESSAGING QUEUE(MQ) is used for sending the messages
---> But in WAS 6.1 version JMS (JAVA MESSAGING SERVICE) is used for sending the messages to the clients/end users
Def of SIB : The service integration bus is a JMS provider that provides reliable message transport and uses intermediary
----> The service integration bus is often referred to as just a bus. When used to host JMS applications, it is often referred to as
a messaging bus.
---> Its capabilities are fully integrated into product architecture, including the security, system administration, monitoring, and
----> Next
Def of Messaging Engine : The component that manages bus resources. It provides a connection point for clients to produce or
---> JMS support enables applications to exchange messages asynchronously with other JMS clients by using JMS
destinations (queues or topics). Applications can use message-driven beans to automatically retrieve messages from JMS
destinations and JCA (JAVA CONNECTOR ARCHITECTURE) endpoints without explicitly polling for messages.
---> Next
----> Next
----> Next
----> Finish
----> Save
Def of Destination : The place within the bus to which applications attach to exchange messages. Destinations can represent
Web services endpoints, messaging point-to-point queues, or messaging publish and subscribe topics. Destinations are created
on a bus and hosted on a messaging engine.
----> Next
----> Finish
----> Save
----> JMS
----> Server 1
--> The default messaging provider uses the service integration bus for transport.
--->The default message provider provides point-to-point functions, as well as publish and subscribe functions.
----> My Bus
----> ok
----> Save
PackageReceivedQName--->ok--->Save
Step 6 : Activation Specification :
----> Next
----> Save
./launchClient.sh/opt/jms-eq/packageReceivedClient.ear