WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

412 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

9. Click Test connection to verify that you can connect to the WebSphere MQ queue

manager and then click Next.

10.In the Summary window, review the summary and then click Finish. The new activation

specification is created.

11.Save the changes to the configuration.

WebSphere Application Server V8.5 exposes several WebSphere MQ connection properties

to configure the WebSphere MQ resource adapter that is used by the WebSphere MQ

messaging provider. Among these properties, which affect the connection pool that is used by

activation specifications, are:

 maxConnections

 connectionConcurrency (Setting this property only affects WebSphere Application Server

V7 nodes. The property has no effect for nodes in WebSphere Application Server V8 or

later.

 reconnectionRetryCount

 reconnectionRetryInterval

To configure these properties, go to the navigation tree, and click JMS providers 

WebSphere MQ messaging provider. Under Additional properties, click Resource adapter

properties, as shown in Figure 11-21.

Figure 11-21 WebSphere MQ resource adapter properties

11.4 Configuring resources for third-party messaging providers

For messaging between application servers, most requirements can be satisfied using either

the WebSphere Application Server default messaging provider or the WebSphere MQ

messaging provider. However, if desired, you can instead use a third-party messaging

provider (that is, another company's product).

To administer a third-party messaging provider, use either the resource adapter (for a Java

EE Connector Architecture (JCA) 1.5-compliant or 1.6-compliant messaging provider) or the

client (for a non-JCA messaging provider) that is supplied by the third party.

In this section, we describe how to configure a third-party, non-JCA messaging provider using

the administrative console. You can configure any third-party non-JCA messaging provider

that supports the JMS Version 1.1 unified connection factory. For details about how to

configure third-party JCA messaging provider refer to the WebSphere Application Server

information center at the following website:

http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/topic/com.ibm.websphere.nd.doc/ae/t

mp_ep_ra.html

Chapter 11. Configuring messaging providers 413

11.4.1 Configuring JMS messaging providers

To define a new third-party messaging provider:

1. Click Resources  JMS  JMS providers. In the JMS providers window, select the

Scope (use Cell scope in this sample) and then click New.

2. Enter the following properties:

–Name

– Class path

– Native library path

– External initial context factory. This property is the Java class name of the third-party

JMS provider’s initial context factory. For example, for the ActiveMQ JMS provider, this

is org.apache.activemq.jndi.ActiveMQWASInitialContextFactory.

– External provider URL. This is the JMS provider URL for external JNDI lookups. The

external provider URL specifies how the initial context factory connects to the external

naming service. The format of the external provider URL is:

<protocol>://<host name>:<port number>

3. Click OK. A new JMS provider is created.

4. Save the changes to the configuration.

11.4.2 Configuring JMS connection factories

To configure a JMS connection factory for a third-party JMS provider:

1. Click Resources  JMS  Connection factories. In the Connection factories window,

click Scope (use Cell scope in this sample) and then click New.

2. Choose the third-party JMS provider that you created in the previous sub-section and then

click OK.

3. Enter the following basic properties:

–Name

– JNDI name

– External JNDI name

414 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile

Figure 11-22 shows the configuration for this example.

Figure 11-22 Third-party JMS connection factory properties

You can configure other properties for this connection factory if needed. For detailed

information about other properties, refer to the product information center at the following

website:

http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/topic/com.ibm.websphere.nd.doc/a

e/tmj_adm29.html

4. Click OK. The new connection factory is created.

5. Save the changes to the configuration.

11.4.3 Configuring JMS destinations

You can configure both queue and topic destinations for third-party JMS messaging

providers. In this section, we describe how to create and configure a JMS queue. For

information about creating and configuring a JMS topic, refer to WebSphere Application

Server V7 Messaging Administration Guide, SG24-7770.

To configure a JMS destination:

1. Click Resources  JMS  Queues. In the Queues window, click Scope (this sample

uses Cell scope) and then click New.

2. Select the Generic JMS provider option and then click OK.

3. Enter the following basic properties:

–Name

– JNDI name

– External JNDI name

Chapter 11. Configuring messaging providers 415

Figure 11-23 shows the configuration for this example.

Figure 11-23 Third-party JMS queue properties

4. Click OK. The new queue is created.

5. Save the changes to the configuration.

416 WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile