WebSphere WebSphere Application Server Version 6.1.x Feature Pack for Web Services Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Enabling CMP entity beans and messaging engine data stores to share database connections

Use this task to enable container-managed persistence (CMP) entity beans to share the database connections used by the data store of a messaging engine. This has been estimated as a potential performance improvement of 15% for overall message throughput, but can only be used for entity beans connected to the application server that contains the messaging engine.

About this task
To enable CMP entity beans to share the database connections used by the data store of a messaging engine, complete the following steps:

Procedure

  1. Configure the data store to use a data source that is not XA-capable. For more information about configuring a data store, see Configuring a JDBC data source for a messaging engine.
  2. Select the Share data source with CMP option.

    This option is provided on the JMS connection factory or JMS activation specification used to connect to the service integration bus that hosts the bus destination that is used to store and process messages for the CMP bean.

    For example, to select the option on a unified JMS connection factory, complete the following steps:

    1. Display the default messaging provider. In the navigation pane, expand Resources > JMS > JMS Providers.
    2. Select the default provider for which you want to configure a unified connection factory.
    3. Optional: Change the Scope check box to set the level at which the connection factory is to be visible, according to your needs.
    4. In the content pane, under Additional Properties, click Connection factories
    5. Optional: To create a new unified JMS connection factory, click New.

      Specify the following properties for the connection factory:

      Name
      Type the name by which the connection factory is known for administrative purposes.
      JNDI name
      Type the JNDI name that is used to bind the connection factory into the name space.
      Bus name
      Type the name of the service integration bus that the connection factory is to create connections to. This service integration bus hosts the destinations that the JMS queues and topics are assigned to.
    6. Optional: To change the properties of an existing connection factory, click one of the connection factories displayed. This displays the properties for the connection factory in the content pane.
    7. Select the check box for the Share data source with CMP field
    8. Click OK.
    9. Save your changes to the master configuration.
    The JMS connection factory can only be used to connect to a "local" messaging engine that is in the application server on which the CMP beans are deployed.
  3. Deploy the CMP beans onto the application server that contains the messaging engine, and specify the same data source as used by the messaging engine. You can use the administrative consoles to complete the following steps:
    1. Optional: To determine the data source used by the messaging engine, click Servers > Application servers > server_name > Messaging engines > engine_name > Data store The Data source name field displays the name of the data source; by default:
      jdbc/com.ibm.ws.sib/engine_name
    2. Click Applications > Install New Application
    3. On the first Preparing for application install page, specify the full path name of the source application file (.ear file otherwise known as an EAR file), then click Next
    4. On the second Preparing for application install page, complete the following steps:
      1. Select the check box for the Generate Default Bindings property. Data source bindings (for EJB 1.1 JAR files) are generated based on the JNDI name, data source user name password options. This results in default data source settings for each EJB JAR file. No bean-level data source bindings are generated.
      2. Under Connection Factory Bindings, click the check box for the Default connection factory bindings: property, then type the JNDI name for the data source and optionally select a Resource authorization value.
      3. Click Next
  4. If your application uses EJB modules that contain Container Managed Persistence (CMP) beans that are based on the EJB 1.x specification, for Step: Provide default data source mapping for modules containing 1.x entity beans, specify a JNDI name for the default data source for the EJB modules. The default data source for the EJB modules is optional if data sources are specified for individual CMP beans.
  5. If your application has CMP beans that are based on the EJB 1.x specification, for Step: Map data sources for all 1.x CMP, specify a JNDI name for data sources to be used for each of the 1.x CMP beans. The data source attribute is optional for individual CMP beans if a default data source is specified for the EJB module that contains CMP beans. If neither a default data source for the EJB module nor a data source for individual CMP beans are specified, then a validation error displays after you click Finish (step 13) and the installation is cancelled.
  6. Complete other panels as needed.
  7. On the Summary panel, verify the cell, node, and server onto which the application modules will install:
    1. Beside Cell/Node/Server, click Click here.
    2. Verify the settings on the Map modules to servers page displayed. Ensure that the application server that is specified contains the messaging engine and its data store.
    3. Specify the Web servers as targets that will serve as routers for requests to this application. This information is used to generate the plug-in configuration file (plugin-cfg.xml) for each Web server.
    4. Click Finish.
Results

For more information about installing applications, see Installing application files with the console.


Task topic

Terms of use | Feedback


Timestamp icon Last updated: 27 November 2008
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.wsfep.multiplatform.doc/tasks/tjn0007_.html

Copyright IBM Corporation 2004, 2008. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)