Deploying WebLogic Platform Applications

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
• Distribution of Production Domain Resources
• Deployment Targeting Reference - Single Cluster WebLogic Platform Domain
• Default Domain Resource Reference - By Product Component

 

---

Characteristics of a Production Deployment Domain

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

• It is created using the Configuration Wizard or WLST Offline, both of which have underlying autoconfiguration capabilities to simplify domain creation. For more information about autoconfiguration, see Autoconfiguration Using the Configuration Wizard and WLST Offline.
• It is created from the Basic WebLogic Platform Domain template.
• It has multiple Managed Servers.
• It has a single cluster to which all the Managed Servers are assigned.
• All Managed Servers in the cluster are autoconfigured as migratable.
• Other resources and services, such as JMS servers and distributed JMS queues, are autoconfigured.

 

---

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.

• Figure A-1 shows the distribution of resources across the Managed Servers and the cluster.
• Figure A-2 shows the resources targeted to the domain's Administration Server.

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

 

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

 

 

---

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:

• <MyApplication> represents the name of an application EAR file being deployed.
• <MyWebApp> represents the name of an individual Web application developed in WebLogic Workshop.
• <MyPortalApp> represents the name of an individual portal application developed in WebLogic Workshop.
• 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.
• A check mark indicates the default target for the resource, service, or application.

Table A-1 Default Targets for Resources, Services, and Applications in a Clustered Platform Domain

Item	Name		Administration Server	One Managed Server Only	Each Managed Server	Cluster
Applications
	<MyApplication>* *Target to both the Administration Server and the cluster when Portal components are included in the application.Target only to the cluster when Portal components are not included in the application. See <MyPortalApp> for Portal-only application targeting		*
	<MyPortalApp>
		EJB Components commerce.jar (if commerce services installed) content.jar content_repo.jar netuix.jar p13n_ejb.jar pipeline.jar (if pipeline services installed) prefs.jar wps.jar
		Web App Components <MyPortalApp>Admin <MyPortalApp>Datasync <MyPortalApp>
		Web Service Components <MyPortalApp>Tool <MyPortalApp>WPSTool
	paymentWSApp
		EJB Components payment
		Web Service Components payws
	taxWSApp
		EJB Components tax
		Web Service Components taxws
	WLI-AI Design-time (Present in the domain, but application components are not targeted by default)
		EJB Components WLI-AI Manager EJBs
		Web App Components wlai
	JWSQueueTransport
		EJB Components QueueTransportEJB
	WLI System EJBs
		EJB Components WLI Admin WLI Admin Helper WLI AI Message Processors WLI ebXML WLI Message Tracking WLI Process Proxy Dispatcher WLI Process Tracking WLI RosettaNet WLI Sync2Async Response Listener WLI Worklist Persistence WLI Worklist Selection
		WLI Calendar Persistence
		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/GenericStateless .workshop/worklist/EJB/ProjectBeans
		Web App Components worklist
	B2BDefaultWebAppApplication
		Web App Components B2BDefaultWebApp
	BEA_WLS_DBMS_ADK
		Web App Components BEA_WLS_DBMS_ADK_Web
		Connector Components BEA_WLS_DBMS_ADK BEA_WLS_DBMS_ADK_LOCALTX
Startup and Shutdown Classes
	WLI Post-Activation Startup Class WLI Shutdown Class WLI Startup Class
JMS Servers
	cgJMSServer_pinned_1
	cgJMSServer_auto_1 Note: Certain JMS queues are associated with only one JMS Server (that is, cgJMSServer_auto_1) that is targeted to the first Managed Server.
	cgJMSServer_auto_#
JMS Connection Factories
	cgQueue
	WLI-B2B System Topic Factory
	wli.internal.egrdbms.QueueConnectionFactory
JMS Queues
	JMS Queues—for each managed server in the cluster for each <MyWebApp> created in WebLogic Workshop where Web services are configured to support asynchronous requests. <MyWebApp>.queue.AsyncDispatcher<1...n>_# <MyWebApp>.queue.AsyncDispatcher_error<1...n>_#
	JMS Queues—for cgJMSServer_pinned_1 wli.internal.configfile.request.queue
	JMS Queues—for each managed server in the cluster cgJWSQueue_auto_# wli.b2b.failedmessage.queue_auto_# wli.b2b.mt.event.stream_auto_# wli.b2b.mt.event.stream_error_auto_# wli.internal.ai.async.request_auto_# wli.internal.ai.async.response_auto_# wli.internal.ai.event_suspend_auto_# wli.internal.b2b.ebxmlencoder.queue_auto_# wli.internal.b2b.rosettanetencoder.queue_auto_# wli.internal.egmq.queue_auto_# wli.internal.egrdbms.queue_auto_# wli.internal.instance.info.buffer_auto_# wli.internal.instance.info.buffer_error_auto_# wli.internal.msgtracking.queue_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 Queues—Unique to the JMS server on one Managed Server in the cluster (e.g., cgJMSServer_auto_1 on new_Server_1) wli.internal.egfile.queue wli.internal.egmail.queue wli.internal.egtimer.queue wli.internal.scheduling.queue wli.internal.scheduling.queue_error wli.internal.SQLStore.cleanup.documents
JMS Topics
	JMS Topics—for cgJMSServer_pinned_1 wli.internal.b2bevents.topic wli.internal.configfile.update.topic
	wli.internal.ai.event_auto_#
JMS Distributed Queues
	JMS Distributed Queues—for each <MyWebApp> created in WebLogic Workshop where Web services are configured to support asynchronous request. dist_<MyWebApp>.queue.AsyncDispatcher<1...n> dist_<MyWebApp>.queue.AsyncDispatcher_error<1...n>
	dist_cgJWSQueue_auto dist_wli.b2b.failedmessage.queue_auto dist_wli.b2b.mt.event.stream_auto dist_wli.b2b.mt.event.stream_error_auto dist_wli.internal.ai.async.request_auto dist_wli.internal.ai.async.response_auto dist_wli.internal.ai.event_suspend_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.instance.info.buffer_auto dist_wli.internal.instance.info.buffer_error_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
	dist_wli.internal.ai.event_auto
JMS JDBC Data Store
	cgJMSStore_auto_# 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.
	cgJMSStore_auto_#
JDBC Connection Pools
	bpmArchPool cgJMSpool-nonXA cgPool portalPool
JDBC Data Sources
	p13n_trackingDataSource p13nDataSource
JDBC Tx Data Sources
	bpmArchDataSource cgDataSource cgDataSource-nonXA portalFrameworkPool


 

 

---

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.

 

Contact BEA |  Feedback |  Privacy  |