AquaLogic Service Bus Deployment Resources

This section describes AquaLogic Service Bus deployment resources such as JMS queues, MDB applications, connection factories, and so on. It includes targeting information for deployment in a cluster configuration.

The AquaLogic Service Bus Console and the UDDI manager run on the administration server. Therefore, you must run an administration server to manage AquaLogic Service Bus and to facilitate publishing and importing to and from a UDDI registry.

The AquaLogic Service Bus metrics aggregator runs on one of the managed servers in a clustered domain. If the managed server to which the aggregator is targeted goes down, alerts will not be fired.

Resource Target—The target for a resource depends on the resource’s type.

For queues and topics, the target is a single, migratable JMS server (wlsbJMSServer), a JMS server on the administration server, or a distributed destination.

For information about migratable JMS servers and distributed destinations, see “Configuring Migratable Targets for JMS Servers” and “Configuring WebLogic JMS Clustering” in Configuring Clustered WebLogic JMS Resources in Configuring and Managing WebLogic JMS.

For all other resources (including JMS and JDBC services) the target is either the administration server or a cluster.

Resource—The name of the resource as shown in the WebLogic Server Administration Console and the individual package or service (in a resource group).

Note that some resources contain abbreviations that are a legacy from prior BEA product releases:

wl corresponds to WebLogic
wli corresponds toWebLogic Integration

Resource Target

Resource

Admin Server

httpTransport.war

AquaLogic Service Bus HTTP transport application

FileStore

rmfilestore/FileStore

JMS file store that stores persistent messages

wlsbJMSServer

weblogic.wlsb.jms.transporttask.QueueConnectionFactory

wli.reporting.jmsprovider.NonXAConnectionFactory

Connection factory used by reporting provider for transacted sessions

wli.reporting.jmsprovider.XAConnectionFactory

Connection factory used by reporting provider for non-transacted sessions

wli.reporting.jmsprovider_error.queue

For errors associated with the message reporting queue: wli.reporting.jmsprovider.queue

ALSB Test Framework²

weblogic92/integration/common/sbTestFwkEjb.ear

The test console application, accessible by users in the following AquaLogic Service Bus roles: IntegrationAdmin and IntegrationDeployer

Managed Servers in a Cluster

PolledMessageListenerMDBEJB

Listens on wlsb.internal.transport.task.queue.email. Creates the job objects corresponding to each mail message, puts them in the task queue, and processes them.

PolledMessageListenerMDBEJB

Listens on wlsb.internal.transport.queue.file. Creates the job objects corresponding to each new file, puts them in the task queue, and processes them.

PolledMessageListenerMDBEJB

Listens on wlsb.internal.transport.task.queue.ftp. Creates the job objects corresponding to each mail message, puts them in the task queue, and processes them.

WLI Aggregator³

weblogic92/integration/common/wliaggregator.ear

AquaLogic Service Bus metrics aggregator

Note:

WLI Aggregator is targeted to a single managed server.

Message Reporting Purger(PurgingMDB)

weblogic92/integration/common/msgpurger.ear

Note:

Message Reporting Purger is targeted to a single managed server. ⁴ ⁵

ALSB Resource

weblogic92/servicebus/lib/sbresourceWar/sbresource.war

Used by the UDDI subsystem to expose resources (WSDLs, policies, schemas, and so on) contained in AquaLogic Service Bus.

You can undeploy ALSB Resource from the WebLogic Server Administration Console if you do not want the AquaLogic Service Bus resources to be available via HTTP. However, in doing so, you will no longer be able to use the UDDI subsystem.

Distributed Destination

JMS Reporting Provider

weblogic92/integration/common/jmsreportprovider.ear

wlsbJMSServer_auto_1-n

(AquaLogic Service Bus JMS server on each managed server)

QueueIn

Resource for internal use

QueueIn.Quota

Resource for internal use

TemporaryTmplt

Resource for internal use

wli.reporting.jmsprovider.queue

Queue for reporting messages

wli.reporting.purge.queue

JMS queue for the Message Reporting Purger; deployed in a single managed server in a cluster⁴ ⁵

wlsb.internal.transport.poller.queue.email

Polling interval timeout event queue for email transport

wlsb.internal.transport.poller.queue.file

Polling interval timeout event queue for file transport

wlsb.internal.transport.poller.queue.ftp

Polling interval timeout event queue for FTP transport

wlsb.internal.transport.task.queue.email

Queue for jobs associated with each new email message detected during polling

wlsb.internal.transport.task.queue.file

Queue for job associated with each new file detected during polling

Distributed Destination
(continued)

wlsb.internal.transport.task.queue.ftp

(Queue for job associated with each new FTP message detected during polling)

ReportingMDB

Listens to wli.reporting.jmsprovider.queue and asynchronously persists reporting messages to the JMS Reporting Provider Data Store. The reporting action configured in the proxy service pipeline logs messages to the reporting stream while utilizing the JMS reporting provider (wli.reporting.jmsprovider.queue) to write to the queue.

jmsreportprovider.jar

¹All deployed resources can be viewed and modified in the WebLogic Server Administration Console.

²In clusters, the Test Framework EJB is deployed on the admin server and on each managed server by default. It must be deployed on the admin server if you want to test XQueries from the XQuery builders. To use the test console, a cluster address must be configured. The cluster address must contain at least one of the managed servers where the Test Framework EJB is deployed.

³For more information, see Step 4. Starting, Stopping, and Monitoring Managed Servers

⁴The AquaLogic Service Bus Message Reporting Purger runs as a singleton instance on one of the managed servers in the cluster. The Message Reporting Purger queues the purging requests and processes them one by one.

⁵For failover information in the event the managed server that hosts the Message Reporting Purger and the wli.reporting.purge.queue fails, see Message Reporting Purger.

Deployment Guide

AquaLogic Service Bus Deployment Resources