WAS v8.5 > Script the application serving environment (wsadmin) > Welcome to scripting for Messaging resourcesConfigure messaging with wsadmin scripting
Use these topics to learn about configuring messaging with wsadmin. We can configure the message listener service, Java Messaging Service settings, queue and connection factories, and WebSphere MQ settings. We can use wsadmin to configure various messaging connections and settings.
- Configure the message listener service.
The message listener service is an extension to the JMS functions of the JMS provider. It provides a listener manager that controls and monitors one or more JMS listeners, which each monitor a JMS destination on behalf of a deployed message-driven bean.
- Configure Java Messaging Service (JMS) providers, destinations, and connections.
The application server supports asynchronous messaging through the use of a JMS provider and its related messaging system. We can use wsadmin to configure new JMS providers, destinations, and connections.
A JMS destination is used to configure the properties for the associated messaging provider. Connections to the JMS destination are created by the associated 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.
- Configure queue and topic connection factories for the application server. Use queue and topic connection factories to create connections between providers and destinations. A queue connection factory creates a connection to the associated JMS provider of the JMS queue destinations, for point-to-point messaging. A topic connection factory creates a connection to the associated JMS provider of JMS topic destinations, for publish and subscribe messaging.
- Configure WebSphere MQ settings. A WebSphere MQ server represents either a WebSphere MQ queue manager or a WebSphere MQ queue sharing group. It is used by service integration bus messaging to define properties used for connecting to WebSphere MQ. Setting up a WebSphere MQ server involves using the dmgr console to create the server definition, add it to a service integration bus, and create a WebSphere MQ queue type destination.
Subtopics
- Configure resources for the default messaging provider using wsadmin
We can use these commands to manage JMS resources for the default messaging provider.- Configure resources for WebSphere MQ messaging provider
We can use these commands to manage JMS resources for the WebSphere MQ messaging provider.- Configure the message listener service using scripting
Use scripting to configure the message listener service.- Configure new JMS providers using scripting
We can use wsadmin and scripting to configure a new JMS provider.- Configure new JMS destinations using scripting
We can use scripting and wsadmin to configure a new JMS destination.- Configure new JMS connections using wsadmin.sh
Use the wsadmin scripting tool to configure a new JMS connection.- Configure new queue connection factories using scripting
We can use scripting and wsadmin to configure new queue connection factories in WAS.- Configure new topic connection factories using scripting
Use scripting and wsadmin to configure new topic connection factories.- Configure new queues using scripting
We can use scripting to configure a new queue.- Configure new topics using scripting
We can configure new topics using wsadmin and scripting.- JCAManagement command group for AdminTask
We can use the Jython or Jacl scripting languages to configure messaging with scripting. The commands and parameters in the JCA management group can be used to create and manage resource adapters, Java EE Connector Architecture (J2C) activation specifications, administrative objects, connection factories, administrative object interfaces, and message listener types.
Related
Use wsadmin scripting
Get started with wsadmin scripting
createSIBJMSConnectionFactory command
createSIBJMSActivationSpec command
createSIBJMSQueue command
createSIBJMSTopic command