Skip navigation.
Downloads | Product Documentation | Support

Creating WebLogic Configurations Using the Configuration Wizard

# Configuring Targets

Targeting of applications (such as Web applications) and services, such as JMS and JDBC component services, to servers or clusters is optional. However, if you have added services or configured your domain to be distributed across servers or clusters, BEA recommends that you target the servers and clusters onto which you want to deploy your applications or services.

The Applications and Services Targeting Options window prompts you to decide whether you want to target the servers and clusters onto which you want to deploy applications and services. If you select No, the wizard uses the targeting settings for your configuration exactly as defined in the configuration source that you selected earlier. If you select Yes, you are prompted, in subsequent windows, to configure targets as described in the following table.

Note: The Configuration Wizard automatically modifies your existing configurations to support applications and services running in a clustered or non-clustered multi-server environment. For more information, see Autoconfiguration of Applications and Services.

For this task . . . | You . . .
--- | ---
Targeting Applications to Servers or Clusters | Specify the target servers and clusters onto which you want to deploy the application components, such as Web applications and EJB modules, that are included within your domain or imported extension templates.
Targeting Services to Servers or Clusters | Specify the target servers and clusters onto which you want to deploy the application services, such as JDBC or JMS components, or startup/shutdown classes.

## Related Topics

Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services

# Targeting Applications to Servers or Clusters

The Target Applications to Servers or Clusters window prompts you to specify the target servers and clusters onto which you want to deploy the application components, such as Web applications and EJB modules, that are included in your domain or imported extension templates.

#### To deploy application components on servers or clusters:

1. In the Target pane, select the server or cluster to which you want to deploy an application component.
2. In the left pane, select each application component to which you want to assign to the selected server or cluster. To select all application components in the list, choose Select All. To unselect all application components in the list, choose Unselect All.

The Target list corresponding to each application component is updated to reflect the servers or clusters to which the components are assigned.

Note: If you target applications to members of a cluster, they are not automatically targeted to the cluster. If you want the applications targeted to the cluster, you must specifically do so.

3. Repeat steps 1 and 2 for each application component that you want to assign to a server or cluster.
4. Click Next to proceed to the next configuration window.

## Related Topics

Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services

# Targeting Services to Servers or Clusters

The Target Services to Servers or Clusters window prompts you to specify the target servers and clusters onto which you want to deploy the application services, including JDBC or JMS components, or startup/shutdown classes.

Use the following guidelines for targeting JDBC components:

- When you target JDBC data sources and connection pools, target the data source and its related pool to the same servers and clusters.
- In a single-server configuration, assign each data source and the connection pool associated with it to the single server.
- In a configuration with an Administration Server and Managed Servers, target the data source and the connection pool associated with it to the servers on which they will be used.
- In a cluster, assign the data source and the connection pool associated with it to the cluster, rather than to individual servers in the cluster.
- You can target data source/connection pool combinations to more than one server or cluster, as long as you target them in combination. For example, you cannot target a data source to Managed Server A if the connection pool associated with it is assigned only to Managed Server B.

#### To target a service to a server or cluster:

1. In the Target pane, select the server or cluster to which you want to deploy an application service.
2. In the left pane, select each service to which you want to assign to the selected server or cluster. To select all application services in the list, choose Select All. To unselect all application services in the list, choose Unselect All.

Note: When you select or deselect application services, the wizard checks for dependencies between the configuration elements and automatically modifies the list of selected components.

The Target list corresponding to each application service is updated to reflect the servers or clusters to which the components are assigned.

Note: If you target services to members of a cluster, they are not automatically targeted to the cluster. If you want the applications targeted to the cluster, you must specifically do so.

3. Repeat steps 1 and 2 for each application service that you want to assign to a server or cluster.
4. Click Next to proceed to the next configuration window.

Note: If you are extending an existing configuration, your next step is to update your configuration as described in Creating Your WebLogic Configuration.

## Related Topics

Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services

# Autoconfiguration of Applications and Services

Whenever you switch from a single-server domain to a multiserver domain (regardless of whether it is clustered or nonclustered), the Configuration Wizard automatically modifies your existing configurations to support the applications and services running in the new environment. This process is called autoconfiguration.

Note: The rules that the Configuration Wizard uses during the autoconfiguration process are defined to ensure that the reconfigured domain configuration functions properly. Only experienced users should attempt to modify these new settings. Changing these settings may negatively impact the operation of your domain.

As described in Brief Introduction to Domains, common types of domain configurations are as follows:

- Stand-Alone Server Domain
- Domain with Managed Servers
- Domain with Managed Servers and Clusters

The Configuration Wizard performs autoconfiguration under the following circumstances:

- You change the type of domain configuration while you are creating a domain. For example, if you select a template that contains a stand-alone server domain configuration and you add Managed Servers or clusters. In that case, the applications and services that were included in your original configuration are targeted, automatically, to the Managed Servers and clusters that you have just added.
- You add an extension to an existing domain.

The Configuration Template Builder also performs autoconfiguration if you are creating a template from a stand-alone server domain and you add Managed Servers or clusters to the template.

The Configuration Wizard and Configuration Template Builder use the naming conventions listed in the following table when performing autoconfiguration.

Note: In the names of components created during autoconfiguration, `n` specifies a numeric value used to differentiate among the new component names; the value of `n` for the first component created is 1. The value is incremented by 1 for each component that is added.

For each autoconfigured component, an autoconfigured JNDI name is also created: JNDIname`_auto_`n`.`

Component | Name created during autoconfiguration
--- | ---
JMS File Store | `JMSfilestorename``_auto_``n`
JMS JDBC Store | `JMSJDBCStorename``_auto_``n`
JMS Server | `JMSservername``_auto_``n` (created when JMS servers are propagated to a cluster)
JMS Server | `JMSservername``_pinned_``n` (created when JMS servers are pinned to a specific server)
JMS Topic | `JMStopicname``_auto_``n`
JMS Queue | `JMSqueuename``_auto_``n`
JMS Distributed Topic | `dist_``JMStopicname``_auto`
JMS Distributed Topic Member | `autoJMStopicname``_OF_``autoJMSservername`
JMS Distributed Queue | `dist_``JMSqueuename``_auto`
JMS Distributed Queue Member | `autoJMSqueuename``_OF_``autoJMSservername`