Creating message queues for WebSphere

If you deploy Infor EAM server on a WebSphere platform and your Infor EAM server supports Infor EAM Mobile or is used as a Databridge server or for any other application that requires messaging services, you need to configure the WebSphere environment to enable java messaging service (JMS) and create messages queues.

You must determine the number of message queues required for your messaging services application, such as Infor EAM Mobile or Databridge. However, by default you must create the following four JMS queues: WS_REQUESTQUEUE, WS_REQUESTQUEUE_1, WS_REQUESTQUEUE_2, and WS_REQUESTQUEUE_3.

In a typical WebSphere environment, the JMS configuration includes these tasks:

• Specifying the messaging configuration scope
• Creating a service bus and adding bus member
• Starting the messaging engine
• Adding message destination queues
• Creating JMS Connection Factory
• Creating JMS Queues

The following detailed instructions will enable you to complete the necessary JMS configuration for simple deployment scenarios of Infor EAM in a WebSphere environment with the WebSphere Default Messaging provider. More advanced deployment scenarios can be achieved based on your specific WebSphere environment and your objectives, based on factors such as high availability and load balancing capabilities provided by WebSphere messaging. However, these advanced deployments are beyond the scope of this guide.