Developing an enterprise application to use extended messaging

This topic describes how to develop an enterprise application to use extended messaging.

Why and when to perform this task

This task description assumes that developers are using the WebSphere Studio Application Developer to develop the application code (receiver and sender beans).

To develop an enterprise application to use extended messaging, complete the following steps:

Steps for this task

  1. Creating the Enterprise Application project.
    Because the sender and receiver beans used for extended messaging are EJB 2.0 enterprise beans, you must first have created a J2EE 1.3 Enterprise Application project for which extended messaging beans will be created.
    1. Ensure that you have selected 1.3 as the highest J2EE version that is to be used in WebSphere Studio.
      For example: Window-> Preferences... J2EE preferences-> Select the highest J2EE version that is to be used-> 1.3
    2. Create a J2EE 1.3 Enterprise Application project, as described in the WebSphere Studio article Target can be accessed only when this topic is installed in a WebSphere Studio doc plug-in   Creating an Enterprise Application project .
  2. Creating the application code.

    To create the application code, use WebSphere Studio to generate the sender and receiver beans needed by the application, by completing one or more of the following subtasks as described in the WebSphere Studio Extended Messaging documentation:

    The result of this stage is an enterprise bean, containing code automatically generated for extended messaging, that can be assembled into an .EAR file for deployment.
  3. Assembling and packaging the application for deployment.

    You can use WebSphere Studio to assemble and package the application for deployment.

    The following aspects are specific to extended messaging:

    1. Configure a message selector for a receiver bean.
    2. Associate the JNDI names for sender and receiver beans with output and input ports.
    3. Specify the timeout for a sender bean response.
    4. Configure that a sender bean is to handle late responses and identify the listener port to be used for late responses.

Results

The result of this task is an .EAR file, containing an application enterprise bean with code for extended messaging, that can be deployed in WebSphere Application Server.

What to do next

For information about deploying an application to use extended messaging, see Deploying an enterprise application to use extended messaging

Related concepts
Extended messaging - overview
Related tasks
Designing an enterprise application to use extended messaging
Deploying an enterprise application to use extended messaging
Configuring extended messaging service resources
Troubleshooting extended messaging
Using extended messaging in applications



Searchable topic ID:   tmc_devap
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/cmm/tasks/tmc_devap.html

Library | Support | Terms of Use | Feedback