Configuring deployment attributes for a message-driven bean against a listener port

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

Before you begin

You should only configure your application against a listener port for compatability with existing message-driven bean applications, or because you are using the WebSphere MQ messaging provider. Otherwise, you should configure your application against JCA 1.5-compliant resources.

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

About this task

You configure the deployment attributes of an application by using an assembly tool. Detailed steps given in this task are for Rational® Application Developer, but other tools have very similar steps.

Procedure

  1. Start your assembly tool.
  2. Edit the application EAR file. For example, use the Rational Application Developer import wizard to import the EAR file into the assembly tool. To start the import wizard:
    1. Click File-> Import-> EAR file
    2. Click Next, then select the EAR file.
    3. Click Finish
  3. Open the deployment attributes for editing. In the Java EE Hierarchy view, right-click the EJB module for the message-driven bean then click Open With > Deployment Descriptor Editor. 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 Beans 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.
      Bean
      The message bean manages its own transactions
      Container
      The container manages transactions on behalf of the bean
  5. Under Activation Configuration, review the properties.
    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 Message.acknowledge() to acknowledge messages. If a value of CLIENT_ACKNOWLEDGE is passed on the createxxxSession call, then messages are automatically acknowledged by the application server 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.
    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 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.

    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.

    For more details about these properties, see Message-driven bean deployment descriptor properties.

  6. Specify bindings deployment properties.
    1. Under WebSphere Bindings, specify the following property:
      Listener port name
      Type the name of the listener port for this message-driven bean.
  7. Save your changes to the deployment descriptor.
    1. Close the deployment descriptor editor.
    2. When prompted, click Yes to indicate that you want to save changes to the deployment descriptor.
  8. Verify the archive files.
  9. From the popup menu for the project, click Deploy to generate EJB deployment code.
  10. Optional: Test your completed module on a WebSphere Application Server installation. Right-click a module, click Run on Server, and follow the instructions in the displayed wizard.
    Note: Run on Server works on the Windows®, Linux/Intel, and AIX® operating systems only. You cannot deploy remotely to a WebSphere Application Server installation on a UNIX® operating system such as Solaris.
    Important: Use Run on Server for unit testing only. When an application is published remotely, the assembly tool overwrites the server configuration file for that server. Do not use on production servers.

What to do next

After assembling your application, use a systems management tool to deploy the EAR file onto the application server that is to run the application; for example, using the administrative console as described in Deploying and managing applications.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 12:02:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-zos&topic=tmb_depa2
File name: tmb_depa2.html