Creating WebLogic Configurations Using the Configuration Wizard
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
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.
Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services
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.
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.
Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services
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:
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.
Note: If you are extending an existing configuration, your next step is to update your configuration as described in Creating Your WebLogic Configuration.
Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application 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:
The Configuration Wizard performs autoconfiguration under the following circumstances:
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.
|
|
|
|
![]() ![]() |
![]() |
![]() |