Configuring the Message Driven Bean in WebSphere Application Server

To enable an e-mail listener to use Java™ Messaging Service (JMS) queues, you must configure a Java component called a Message Driven Bean that ships with the system. The Message Driven Bean must be configured through a deployment descriptor file that is part of your installation. Configuring the Message Driven Bean involves removing comment lines from specific sections within the deployment descriptor files of the system.

Before you begin

To complete this task, you need access to the following two files: ejbjar.xml deployment descriptor file in the applications/maximo/mboejb/ejbmodule/META-INF file path and ibm-ejb-jar-bnd.xmi in the /applications/maximo/mboejb/ejbmodule/META-INF file path.

Procedure

  1. In your installation folder, locate the deployment descriptor file called ejbjar.xml under the file path applications/maximo/mboejb/ejbmodule/META-INF.
  2. Open the file in a text editor and make the following changes:
    1. Locate the following section and remove the comment lines (<!– and –>):
       Email Listener JMS is not deployed by default
      <message-driven id="MessageDriven_LSNRMessageBean">
      <ejb-class>psdi.common.emailstner.LSNRMessageBEAN</ejb-class>
      <transaction-type>Container</transaction-type>
      <message-destination-type>javax.jms.Queue</message-destination-type>
      </message-driven>-->
    2. Locate the following section and remove the comment lines (<!– and –>):
       Email Listener JMS is not deployed by default
      <container-transaction>
      <method>
      <ejb-name>LSNRMessageBean</ejb-name>
      <method-name>*</method-name>
      </method>
      <trans-attribute>Required</trans-attribute>
      </container-transaction>-->
  3. Save the changes that you made to the descriptor file.
  4. Locate the file called ibm-ejb-jar-bnd.xmi under the file path /applications/maximo/mboejb/ejbmodule/META-INF folder.
  5. Open the file in a text editor, locate the following section, and remove the comment lines (<!– and –>):
    <!– Email Listener JMS is not deployed by default
    <ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding"
    xmi:id="MessageDrivenBeanBinding_2"
    activationSpecJndiName="lsnrjmsact">
    <enterpriseBean xmi:type="ejb:MessageDriven" 
    href="META-INF/ejbjar.xml#MessageDriven_LSNRMessageBean"/>
    </ejbBindings>-->
  6. Save the changes that you made to the file, then rebuild and redeploy the Enterprise Application Archive (EAR).

What to do next

After you configure the MDBs for e-mail listeners, you can activate workflow processes for e-mail listeners.


Feedback