Skip navigation.

Deploying WebLogic Platform Applications

  Previous Next vertical dots separating previous/next from contents/index/pdf Contents View as PDF   Get Adobe Reader

Deployment Targeting Reference

This appendix provides a comprehensive reference to the targets required for system-level applications and services to support a WebLogic Platform application in a production deployment environment. This information may be helpful for troubleshooting purposes. Topics include:


Characteristics of a Production Deployment Domain

The production deployment domain described in this section is based on the following assumptions and characteristics:


Distribution of Production Domain Resources

The following illustrations show the basic distribution of system-level resources, services, and applications in a single-cluster WebLogic Platform domain. Also illustrated is the distribution of resources for a Platform application. A Platform application is defined to be a composite of WebLogic Portal and WebLogic Integration components.

Note: Shaded areas in the illustrations represent your application and the resources that may be required to support your application in the domain.

Figure A-1 Resource Distribution Across Managed Servers in a Single Cluster WebLogic Platform Domain

Resource Distribution Across Managed Servers in a Single Cluster WebLogic Platform Domain


Note: The main difference between the resources depicted on the Managed Servers in this illustration is that only the JMS Server, cgJMSServer_auto_1, which is associated with (Migratable) Managed Server 1, includes WLI Timer Queues. These WLI Timer Queues are targeted to the JMS Server on only one Managed Server in a domain.

Figure A-2 Resources on the Administration Server in a Single Cluster WebLogic Platform Domain

Resources on the Administration Server in a Single Cluster WebLogic Platform Domain



Deployment Targeting Reference - Single Cluster WebLogic Platform Domain

The following table provides a detailed reference to the resources, services, and application targeting required for a single-cluster Platform domain. Note the following:


Default Domain Resource Reference - By Product Component

The following table provides a reference to the default resources, services, and applications provided in the Basic WebLogic Platform Domain template and their relationships to the platform's constituent product components, such as WebLogic Portal and WebLogic Integration. The table also includes references to autoconfigured resources that result from using the Configuration Wizard or WLST Offline to create a clustered domain.

Use this reference to identify resources that you may need to configure or target manually when creating a product-specific cluster in a multi-cluster domain. For example, in a multi-cluster platform domain, where you may want one WebLogic Integration cluster and a separate WebLogic Portal cluster, you may need to retarget resources for each cluster to create separate product-specific clusters. If you should need to configure other resources manually, the following table can provide a guide as to which resources need to be configured for product-specific components. For an example that shows how to configure a multi-cluster platform domain, see Example: How to Configure a Multi-Cluster Platform Domain Using WLST Offline on page 3-30.

Note: In the following table, the "#" represents an integer in the name of a resource, such as a Managed Server, JMS server, or JMS queue, that is autoconfigured by the Configuration Wizard or WLST Offline during clustered domain setup. For example, the JMS server provided in the Basic WebLogic Platform Domain template is cgJMSServer. As such, the name of the JMS server autoconfigured for the first Managed Server is cgJMSServer_auto_1; the name of the JMS server autoconfigured for the second Managed Server is cgJMSServer_auto_2, and so on. Note also, for resources that must be pinned to a specific server, such as the Administration Server, the autoconfiguration process specifies "pinned" in the name of the resource; for example, cgJMSServer_pinned_1 is the name of the JMS Server autoconfigured and pinned to the Administration Server in a cluster.

Table A-2 Default Domain Resources, Services, and Applications by Product Component



WebLogic Workshop

WebLogic Portal

WebLogic Integration

WebLogic Platform



EJB Components

  • payment

Web Service Components

  • payws


EJB Components

  • tax

Web Service Components

  • taxws

WLI-AI Design-time

EJB Components

  • WLI-AI Manager EJBs

Web App Components

  • wlai


EJB Components

  • QueueTransportEJB

WLI System EJBs

EJB Components

  • WLI Admin

  • WLI Admin Helper

  • WLI Calendar Persistence

  • WLI Process Tracking

  • WLI Worklist Persistence

  • WLI Worklist Selection

  • WLI Process Proxy Dispatcher

  • WLI Sync2Async Response Listener

  • WLI AI Message Processors

  • WLI RosettaNet

  • WLI ebXML

  • WLI Message Tracking

  • WLI AI RAR Upload

Web App Components

  • WLI-B2B HTTP Transport

  • WLI Sync2Async Transport Servlet

WLI Console

Web App Components

  • wliconsole

WLI Worklist

EJB Components

  • .workshop/worklist/EJB/ProjectBeans

  • .workshop/worklist/EJB/GenericStateless

Web App Components

  • worklist


Web App Components

  • B2BDefaultWebApp


Web App Components


Connector Components



Startup and Shutdown Classes

  • WLI Post-Activation Startup Class

  • WLI Shutdown Class

  • WLI Startup Class

JMS Servers

cgJMSServer_pinned_1 (Administration Server)

cgJMSServer_auto_# (On Managed Servers)

Note: Certain JMS queues are associated with only one JMS Server (that is, cgJMSServer_auto_1) that is targeted to the first Managed Server.

JMS Connection Factories


WLI-B2B System Topic Factory


JMS Queues


  • wli.b2b.failedmessage.queue_auto_#






  • wli.internal.b2b.ebxmlencoder.queue_auto_#

  • wli.internal.b2b.rosettanetencoder.queue_auto_#

  • wli.internal.configfile.request.queue_auto_#

  • wli.internal.egfile.queue_auto_#

  • wli.internal.egmail.queue_auto_#

  • wli.internal.egmq.queue_auto_#

  • wli.internal.egrdbms.queue_auto_#

  • wli.internal.egtimer.queue_auto_#



  • wli.internal.msgtracking.queue_auto_#

  • wli.internal.scheduling.queue_auto_#

  • wli.internal.scheduling.queue_error_auto_#

  • wli.internal.SQLStore.cleanup.documents_auto_#

  • wli.internal.sync2Async.soapResponse_auto_#

  • wli.internal.tracking.buffer_auto_#

  • wli.internal.tracking.buffer_error_auto_#

  • wli.internal.worklist.timer.queue_auto_#

  • wli.process.event.stream_auto_#

  • wli.process.event.stream_error_auto_#

  • wli.sample.egjms.queue_auto_#

JMS Topics


  • wli.internal.b2bevents.topic

  • wli.internal.configfile.update.topic

JMS Distributed Queues

  • dist_cgJWSQueue_auto

  • dist_wli.b2b.failedmessage.queue_auto






  • dist_wli.internal.b2b.ebxmlencoder.queue_auto

  • dist_wli.internal.b2b.rosettanetencoder.queue_auto

  • dist_wli.internal.egmq.queue_auto

  • dist_wli.internal.egrdbms.queue_auto



  • dist_wli.internal.msgtracking.queue_auto

  • dist_wli.internal.sync2Async.soapResponse_auto

  • dist_wli.internal.tracking.buffer_auto

  • dist_wli.internal.tracking.buffer_error_auto

  • dist_wli.internal.worklist.timer.queue_auto

  • dist_wli.process.event.stream_auto

  • dist_wli.process.event.stream_error_auto

  • dist_wli.sample.egjms.queue_auto

JMS Distributed Topics

JMS JDBC Data Store


Note: One JMS JDBC Data Store is assigned to the JMS Server (that is, cgJMSServer_pinned_1) that is targeted to the Administration Server during autoconfiguration.

JDBC Connection Pools


  • cgJMSpool-nonXA

  • cgPool


JDBC Data Sources

  • p13n_trackingDataSource

  • p13nDataSource

JDBC Tx Data Sources


  • cgDataSource

  • cgDataSource-nonXA




Skip navigation bar  Back to Top Previous Next