Broker 10.5 | webMethods Broker Documentation | Administering webMethods Broker | Using My webMethods with JMS | Managing JMS Clients: A Road Map
Managing JMS Clients: A Road Map
You can administer your JMS applications using My webMethods. The table below describes the tasks required to administer a Broker/JMS client and where to go for detailed information or instructions about the step.
Look In...
Plan and configure client groups
For the administered objects to be able to send and receive messages (or publish and subscribe to messages):
*Assign them to client groups.
*Configure the client group so that it has permissions to publish and subscribe to the appropriate document types.
*If necessary, configure basic authentication or SSL permissions for the client group (that is, its ACLs) so that the clients created by the JMS application can join the group.
For information about basic authentication or SSL permissions and client group ACLs, see Client Group ACLs.
Establish the JNDI provider
Select and configure a supported JNDI provider to use as a naming directory.
Add the connection factories
Configure the connection factories for creating connections between the JMS programs and Broker Server.
Bind the destinations
Configure the topics and queues in JNDI.
Create the destinations
Create the topics and queues.
Update client group permissions
Update the access permissions for client groups so they can publish and subscribe to the document types to use in durable subscriptions.
Create durable subscriptions
For subscriptions whose data is persisted if the subscriber is disconnected, link document type(s) to a topic.
If you are configuring the JMS client's administered objects programmatically (that is, using the WmJMSAdminFactory class) rather than administratively, you do not establish a JNDI provider or bind the administered objects to JNDI.