Configure deployment attributes for a message-driven bean

Use this task to configure the message-driven beans deployment attributes for an enterprise bean, to override the deployment attributes defined within the application EAR file.

This task description assumes that you have an EAR file, which contains an application enterprise bean developed as a message-driven bean, that can be deployed in WebSphere Application Server.

Note: After deployment code has been generated for an application, the deployable archive is renamed with the prefix Deployed_ . Any subsequent changes to the archive from within the Application Assembly Tool are applied to the version of the archive that existed prior to code generation. To see changes reflected in your application, regenerate deployment code and re-install the deployable archive.

To configure the message-driven beans deployment attributes for an enterprise bean, use the the application assembly tool to configure the deployment attributes of the application to match the listener port definitions:

 

  1. Launch the Application Assembly Tool.

  2. Create or edit the application EAR file. For example, to change attributes of an existing application, click File-> Open then select the the EAR file.

  3. In the navigation pane, select the message-driven bean instance; for example, expand ejb_module_instance-> Message-driven beans then select the bean instance. A property dialog notebook for the message-driven bean is displayed in the property pane.

  4. Specify general deployment properties.

    1. In the property pane, select the General tab.

    2. Specify the following properties:

       

      Transaction type

      Whether the message bean manages its own transactions or the container manages transactions on behalf of the bean. All messages retrieved from a specific destination have the same transactional behavior. To enable the transactional behavior that you want, configure the JMS destination with the same transactional behavior as you configure for the message bean.

       

      Bean

      The message bean manages its own transactions

       

      Container

      The container manages transactions on behalf of the bean

  5. Specify advanced deployment properties.

    1. In the property pane, select the Advanced tab.

    2. Specify the following properties:

       

      Message selector

      The JMS message selector to be used to determine which messages the message bean receives; for example: 

      JMSType='car' AND color='blue' AND weight>2500

      The selector string can refer to fields in the JMS message header and fields in the message properties. Message selectors cannot reference message body values.

       

      Acknowledge mode

      How the session acknowledges any messages it receives.

      This property applies only to message-driven beans that uses bean-managed transaction demarcation Transaction(type is set to Bean ).

       

      Auto Acknowledge

      The session automatically acknowledges a message when it has either successfully returned from a call to receive, or the message listener it has called to process the message successfully returns.

       

      Dups OK Acknowledge

      The session lazily acknowledges the delivery of messages. This is likely to result in the delivery of some duplicate messages if JMS fails, so it should be used only by consumers that are tolerant of duplicate messages.

      As defined in the EJB specification, clients cannot use using Message.acknowledge() to acknowledge messages. If a value of CLIENT_ACKNOWLEDGE is passed on the createxxxSession call, then messages are automatically acknowledged by the appserver and Message.acknowledge() is not used.

       

      Destination type

      Whether the message bean uses a queue or topic destination.

       

      Queue

      The message bean uses a queue destination.

       

      Topic

      The message bean uses a topic destination.

       

      Subscription durability

      Whether a JMS topic subscription is durable or non-durable.

       

      Durable

      A subscriber registers a durable subscription with a unique identity that is retained by JMS. Subsequent subscriber objects with the same identity resume the subscription in the state it was left in by the earlier subscriber. If there is no active subscriber for a durable subscription, JMS retains the subscription's messages until they are received by the subscription or until they expire.

       

      Nondurable

      Non-durable subscriptions last for the lifetime of their subscriber object. This means that a client sees the messages published on a topic only while its subscriber is active. If the subscriber is not active, the client is missing messages published on its topic.

      A non-durable subscriber can only be used in the same transactional context (for example, a global transaction or an unspecified transaction context) that existed when the subscriber was created. For more information about this context restriction, see The effect of transaction context on non-durable subscribers.

  6. Specify bindings deployment properties.

    1. In the property pane, select the Bindings tab.

    2. Specify the following property:

       

      Listener port name

      The name of the listener port for this message-driven bean.

  7. To apply the changes and close the Application Assembly Tool, click OK. Otherwise, to apply the values but keep the property dialog open for additional edits, click Apply.

  8. (Optional)  

    To see changes reflected in your application, regenerate deployment code and reinstall the deployable archive.

Message-driven beans - an overview
Deploying an enterprise application to use message-driven beans
The effect of transaction context on non-durable subscribers

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.