WLEC

You must configure a WTCServer to describe the Tuxedo /T DOMAINS connections used to link WebLogic Server to Tuxedo. You may have 0, 1, or more WTCServer configurations in your WebLogic Tuxedo Connector node depending on the number of connections you need to link to Tuxedo applications.

Table 11-11

Attribute Label	Description	Value Constraints
Name	The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration. MBean: weblogic.management. configuration. WTCServerMBean Attribute: Name
Deployment Order	A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the same type. For example, the server prioritizes and deploys all EJBs before it prioritizes and deploys startup classes. Items with the lowest Deployment Order value are deployed first. There is no guarantee on the order of deployments with equal Deployment Order values. There is no guarantee of ordering across clusters. MBean: weblogic.management. configuration. WTCServerMBean Attribute: DeploymentOrder	Minimum: MIN_ORDER Maximum: MAX_ORDER Default: DEFAULT_ORDER Dynamic: yes

Attribute Label

Description

Value Constraints

Name

The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.

MBean: weblogic.management.
configuration.
WTCServerMBean

Attribute: Name

Deployment Order

A priority that the server uses to determine when it deploys an item. The priority is relative to other deployable items of the same type. For example, the server prioritizes and deploys all EJBs before it prioritizes and deploys startup classes.

Items with the lowest Deployment Order value are deployed first. There is no guarantee on the order of deployments with equal Deployment Order values. There is no guarantee of ordering across clusters.

MBean: weblogic.management.
configuration.
WTCServerMBean

Attribute: DeploymentOrder

Minimum: MIN_ORDER

Maximum: MAX_ORDER

Default: DEFAULT_ORDER

Dynamic: yes