Chapter 11   Administering Message Driven Beans


To deploy and run message-driven beans on iPlanet Application Server, you must first setup the Java Message Service (JMS) provider to enable clients to connect to a message-driven bean.

The message-driven bean acts as a JMS message listener, and therefore a messaging middleware needs to be configured to enable deployment of message-driven beans. Currently, only the Java Message Queue is supported in this version of iPlanet Application Server.

This chapter contains the following topic:

• Configuring a JMS Provider

• Administering Message Driven Beans

  
  

  ---

  Note	The message-driven bean functionality in iPlanet Application Server is meant for developer use only. It has not been tested or certified for production environments.

  ---

  
  

For more information on deploying message-drivem beans, see iPlanet Application Server Developer's Guide and the Deployment Tool online help.

Configuring a JMS Provider

---

To configure a JMS provider, you must first install the messaging middleware. By default, iPlanet Application Server uses the iPlanet Message Queue (iMQ) for Java, 2.0 SP1. iMQ for Java, 2.0 SP1 is bundled on the iPlanet Application Server installation CD. If you don't have the installation CD, you can download it from http://www.iplanet.com/products/iplanet_message_queue/home_message_queue.html.

You can use iMQ for Java, 2.0 SP1, which is supplied with iPlanet Application Server, or use a third party product.

• To Configure iMQ for Java

• To Configure Third Party JMQ

To Configure iMQ for Java

Before starting the configuration of iMQ for Java 2.0 SP1, ensure that iPlanet Message Queue for Java, 2.0 SP1 is installed on your machine.

Follow these steps to setup a JMS provider and a message queue to enable support for message-driven beans:

1. Start iASAT.

2. Click the Messaging icon on the menu bar.

   
   
   

3. Click JMS Providers in the left pane.

4. Click Add in the right pane.

5. Enter the particulars for your environment.

   All fields are mandatory. You need to specify the following:

   • JMS Server Name

   • JMS Server Host

   • JMS Port Number

   • Initial Context Factory Class Name

     This can be specified in terms of LDAP URL, filesystem path, etc.

   • JMS ClassPath

   • Naming Context Provider URL

   • JMS Server User Name

   • JMS Server User Password

   The following figure shows a sample configuration:

   
   
   

6. Click OK to commit the changes.

7. Create an entry for the Queue in the directory server.

   If you are using a filesystem context factory name, then specify the path to the file.

   
   
   

   For information on creation an organizational Unit, see iPlanet Directory Server 5.0 docuemntation.

8. Use the tools availablle with iMQ for Java 2.0 to create the Queue Connection Factory object, QCF. in the directory server under ou=JMQ.

   A sample file is shown below:

   cmdtype=add

   obj.type=qf

   obj.lookupName=cn=QCF

   objstore.attrs.java.naming.factory.initial=\com.sun.jndi.ldap.LdapCtxFactory

   objstore.attrs.java.naming.provider.url=\ldap://border.india.sun.com:389/ou=JMQ,o=NetscapeRoot

   objstore.attrs.java.naming.security.principal=cn=Directory Manager

   objstore.attrs.java.naming.security.credentials=netscape

   objstore.attrs.java.naming.security.authentication=simple

9. Use iPlanet Console to ensure that the cn=QCF object in the directory has read, compare and Search permissions.

   Now that your JMS provider is configured you can start using message-driven beans in your applications.

To Configure Third Party JMQ

Follow these steps to configure a third party Java messaging middleware. Ensure that the message queue you plan to use, conforms to Chapter eight, "JMS Application Server Facilities", of the JMS specification.

Follow these steps to configure a third party JMS provider:

1. Manually create the Factory Context and configuration parameters in the iPlanet Directory Server, under ou=JMQ,o=NetscapeRoot.

2. If you have already configured iPlanet Message Queue for Java 2.0, SP1, delete the following iMQ specific entries from the iPlanet Registry:
   • ServerHost

   • ServerPort

   • Username

   • Password

   These values are only valid for iPlanet Message Queue. Use the Factory settings sepecified for your JMQ.

Administering Message Driven Beans

---

Message-driven beans can now be administered through the iPlanet Application Server Administration Tool. You can change the properties of each individual message-driven bean in a module.

To Administer Message Driven Beans

Follow these steps to modify the properties of a deployed message-driven bean:

1. Start iASAT.

2. Click Application on the menu bar.

   In the left pane all the deployed applications are displayed.

3. Select the message-driven bean you want to modify.

4. In the right pane, select MDBs tab.

   The following dialog box will be displayed:

   
   
   

The following fields can be modified:

• MDB Name

• Enabled Flag

  If the flag is disabled, KJS will not load the message-driven bean at startup.

• Destination Name

• Destination Type

  Can be Queue or Topic.

• Acknowledgement Mode

• Max Message Limit

• Max Pool Size

• Min Pool Size

• Durable Name

  This property can be set for Topic Subscription only.

• Click Apply Changes to commit the changes you have made.

• Restart iPlanet Application Server to enable the changes.