Skip Headers
Oracle® Fusion Middleware Creating Domains Using the Configuration Wizard
11g Release 1 (10.3.6)

Part Number E14140-06
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

4 Configuration Wizard Screens

This chapter contains screen shots and descriptions for all of the Fusion Middleware Configuration Wizard screens.

Welcome

Description of welcome.gif follows
Description of the illustration welcome.gif

The Welcome screen displays when you start the Configuration Wizard.

Select one of the following options:

Select a WebLogic Domain Directory

Description of select_domain_dir.gif follows
Description of the illustration select_domain_dir.gif

Use the navigation tree to select a valid domain directory. A domain directory contains a config directory, which contains a config.xml file. In the navigation tree, these directories are indicated by a blue folder icon:

Surrounding text describes icon_domain_dir.gif.

Select Domain Source

Description of select_domain_src.gif follows
Description of the illustration select_domain_src.gif

Choose whether to generate a domain that is configured automatically to support selected products, or to create a domain based on an existing domain template. Each product in the displayed list is associated with a single domain or extension template (a JAR file) which configures the domain resources needed for that product.

Select one of the following options:

Select Extension Source

Description of extend_domain_source.gif follows
Description of the illustration extend_domain_source.gif

Choose whether to extend the domain by selecting one of the listed products, or by browsing to an extension template.

Specify Domain Name and Location

Description of name_location.gif follows
Description of the illustration name_location.gif

Specify the following items:

Configure Administrator User Name and Password

Description of username_password.gif follows
Description of the illustration username_password.gif

Use this screen to define the default WebLogic Administrator account for the domain. This account is used to boot and connect to the domain's Administration Server.

Configure Server Start Mode and JDK

Description of start_mode_jdk.gif follows
Description of the illustration start_mode_jdk.gif

On this screen, specify whether you want to run WebLogic in Production mode or Development mode. You also specify the location of the JDK(s) to use in this domain.

In the WebLogic Domain Startup Mode pane, select one of the following options:

For information about changing the run-time mode after you have created a WebLogic domain, see "Change to Production Mode" in the WebLogic Server Administration Console Online Help.

The following table provides more details on the differences between development mode and production mode:

Table 4-1 Differences Between Development and Production Mode

Feature Development Mode Production Mode

SSL

You can use the demonstration digital certificates and the demonstration keystores provided by the WebLogic Server security services. With these certificates, you can design your application to work within environments secured by SSL.

For more information, see "Configuring SSL" in Securing Oracle WebLogic Server.

You must not use the demonstration digital certificates and the demonstration keystores. If you do so, a warning message is displayed.

Deploying applications

WebLogic Server instances can deploy and update applications that reside in the domain_name/autodeploy directory automatically.

Oracle recommends that you use this method only in a single-server development environment.

For more information, see "Deploying Applications and Modules with weblogic.deployer" in Deploying Applications to Oracle WebLogic Server.

The auto-deployment feature is disabled. You must use the WebLogic Server Administration Console, the weblogic.deployer tool, or the WebLogic Scripting Tool.

Log file rotation

By default, when you start the WebLogic Server instance, the server automatically renames (rotates) its local server log file as SERVER-NAME.log.n. For the remainder of the server session, messages accumulate in the log file until the file grows to a size of 500 kilobytes.

For more information, see "Rotate Log Files" in the WebLogic Server Administration Console Online Help.

The default value of the Limit number of retained files setting in Logging Configuration is true. This limits the number of log files that the server instance creates to store old messages.

The server rotates the local log file after the size of the file reaches 5000 kilobytes.

When the server is configured for production mode, by default, all versions of the log files are kept. Administrators may want to customize the number of log files that are retained.

The default value of Limit number of retained files setting in Logging Configuration is false. The server creates new log files indefinitely, and you must clean up those files as you require.

JDBC system resource

The default capacity is 15 connections.

The default capacity is 25 connections.

boot.properties

A boot.properties file is created.

A boot.properties file is not created.


The JDK Selection pane lists all JDKs that are available for use in the domain. Select one of the following options:

Note:

If you select a JDK that is included in the installer, the Configuration Wizard creates server startup scripts to invoke the JDK. If you select a JDK that is not supplied by the installer, the Configuration Wizard does not configure the startup scripts; you must change the startup scripts manually. For more information about startup scripts, see Performance and Tuning for Oracle WebLogic Server.

Select only those JDKs that are supported on the platform you are using. For a list of the JDKs that are supported for a specific platform, see Oracle Fusion Middleware Supported System Configurations at http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html. The default selection reflects the JDK that best meets the requirements of your environment, based on the platform on which you are installing the WebLogic domain.

Configure JDBC Component Schema

JDBC Component Schema screen, GridLink version
Description of the illustration jdbc_comp_schema_gl.gif

For some Fusion Middleware components (for example, SOA and Web Center Spaces), JDBC data sources might be defined as part of the component's database schema, which are loaded (during installation) by using the Repository Creation Utility (RCU).

When you create a WebLogic domain for such components by using the Configuration Wizard, you can configure the JDBC component schema settings, such as database driver, schema owner, password, and so on.

The JDBC component schemas associated with the products for which you are creating the domain (for example, SOA) are listed in the lower half of the screen.

Select the schemas for which you want to specify data source settings by selecting the check box adjacent to each schema name.

To convert one or more schemas to GridLink RAC schemas, select the check boxes adjacent to the name of the those schemas, and select the Convert to GridLink option. Click Next when done. When you click Next, the Configure GridLink RAC Component Schema screen is displayed.

To convert one or more of the schemas to Oracle RAC multi data source schemas, select the check boxes adjacent to the name of the those schemas, and select the Convert to RAC multi data source option. Click Next when done. When you click Next, the Configure RAC Multi Data Source Schema screen is displayed.

Note:

When you select multiple component schemas, the text Varies among component schemas might be displayed in certain fields, indicating that the current values of those fields are different across the selected component schemas. If you change the values in such fields, the new values are applied uniformly across the selected component schemas.

The default values of component schema parameters such as vendor, driver, host name, and port number depend on the values that are specified in the application templates.

The values that you specify are displayed in the appropriate columns in the schema list, for the selected schemas.

Configure GridLink RAC Component Schema

Configure GridLink RAC Component Schema screen
Description of the illustration cfggridlink.gif

Use this screen to configure the component schemas that are included in your WebLogic domain as GridLink RAC data sources. A GridLink data source is a single data source that represents a service that responds to Fast Application Notification (FAN) events.

The component schemas that you opted to configure as GridLink RAC data sources in the Configure JDBC Component Schema screen of the wizard are listed in the lower half of the screen.

In the schema list in the lower half of the screen, select the schemas to configure as GridLink RAC data sources by selecting the check box adjacent to each schema name.

Note:

When you select multiple data source schemas, the text "Varies among component schemas" might be displayed in certain fields, indicating that the current values of those fields are different across the selected schemas. If you go ahead and change the values in such fields, the new values are applied uniformly across the selected schemas.

The values that you specify are displayed in the appropriate columns in the schema list, for the selected schemas.

To add another row to the Service Listener table, click anywhere in the table, and then click Add.

To add another row to the ONS Host table, click anywhere in the table, and then click Add.

To delete a row from the Service Listener table, click anywhere in the row, and then click Delete.

To delete a row from the ONS Host table, click anywhere in the row, and then click Delete.

For more information about GridLink data sources, see "Using Gridlink Data Sources" in Configuring and Managing JDBC Data Sources for Oracle WebLogic Server.

Configure RAC Multi Data Source Schema

Description of rac_comp_schema.gif follows
Description of the illustration rac_comp_schema.gif

Use this screen to configure the component schemas that are included in the WebLogic domain as Oracle RAC multi data sources.

The component schemas that you opted to configure as Oracle RAC multi data sources in the Configure JDBC Component Schema screen of the wizard are listed in the lower half of the screen.

In the schema list in the lower half of the screen, select the schemas to configure as Oracle RAC multi data sources by selecting the check box adjacent to each schema name.

Note:

When you select multiple data source schemas, the text "Varies among component schemas" might be displayed in certain fields, indicating that the current values of those fields are different across the selected schemas. If you go ahead and change the values in such fields, the new values are applied uniformly across the selected schemas.

Note:

You must specify the host name, instance name, and port number of at least one database instance.

To add a database instance, click Add. Specify the host name, instance name, and port.

The values that you specify are displayed in the appropriate columns in the schema list, for the selected schemas.

Test Component Schema

Description of jdbc_comp_schema_test.gif follows
Description of the illustration jdbc_comp_schema_test.gif

Use this screen to test the configurations that you specified for the data sources in the previous screen.

Select the check boxes adjacent to the names of the schemas to test, and then click Test Connections.

The wizard tests the configuration for each schema by attempting to connect to a URL that is constructed by using the driver, host, port, and other information that you specified while configuring the schema.

The result of the test is indicated in the Status column. Details are displayed in the Connection Result Log section.

Configure JDBC Data Source

Description of jdbc_ds_grid.gif follows
Description of the illustration jdbc_ds_grid.gif

A JDBC data source contains a pool of database connections that are created when the data source instance is created—when it is deployed or targeted, or at server startup. Applications look up a data source on the JNDI tree, and then request a connection. When the applications no longer need the connections, they return the connections to the connection pool in the data source.

Use this screen to configure the JDBC data sources defined in your domain source.

The JDBC data sources associated with the products for which you are creating the domain are listed in the lower half of the screen.

To convert one or more of the data sources to GridLink RAC data sources, select the check box adjacent to the name of the data source, and select the Convert to GridLink option. When you click Next, the Configure GridLink RAC Data Sources screen is displayed.

To convert one or more of the data sources to Oracle RAC multi data sources, select the check box adjacent to the name of the required schema, and select the Convert to RAC multi data source option. When you clickNext, the Configure Oracle RAC Multi Data Sources screen is displayed.

Select the data source(s) for which you want to specify settings by selecting the check box adjacent to each data source name.

Notes:

When you select multiple data sources, the text Varies among data sources might be displayed in certain fields, indicating that the current values of those fields are different across the selected data sources. If you change the values in such fields, the new values are applied uniformly across the selected data sources.

The default values of data source parameters such as vendor, driver, host name, and port number depend on the values that are specified in the application templates.

The values that you specify are displayed in the appropriate columns in the data source list, for the selected data source.

Configure GridLink RAC Data Sources

Configure GridLink RAC Data Sources screen

Use this screen to configure the data sources that are included in your WebLogic domain as GridLink RAC data sources. A GridLink data source is a single data source that represents a service that responds to Fast Application Notification (FAN) events.

The data sources that you opted to configure as GridLink RAC data sources in the Configure JDBC Data Source screen of the wizard are listed in the lower half of the screen.

In the schema list in the lower half of the screen, select the data sources to configure as GridLink RAC data sources by selecting the check box adjacent to each data source name.

Note:

When you select multiple data sources, the text "Varies among component schemas" might be displayed in certain fields, indicating that the current values of those fields are different across the selected data sources. If you go ahead and change the values in such fields, the new values are applied uniformly across the selected data sources.

The values that you specify are displayed in the appropriate columns in the data source list, for the selected schemas.

To add another row to the Service Listener table, click anywhere in the table, and then click Add.

To add another row to the ONS Host table, click anywhere in the table, and then click Add.

To delete a row from the Service Listener table, click anywhere in the row, and then click Delete.

To delete a row from the ONS Host table, click anywhere in the row, and then click Delete.

For more information about GridLink data sources, see "Using Gridlink Data Sources" in Configuring and Managing JDBC Data Sources for Oracle WebLogic Server.

Configure Oracle RAC Multi Data Sources

Description of rac_multi_data_source.gif follows
Description of the illustration rac_multi_data_source.gif

Use this screen to configure the data sources (that are included in the domain) as an Oracle RAC data sources.

The data sources that you opted to configure as Oracle RAC data sources on the Configure JDBC Data Source screen are listed in the lower half of the screen.

Select the data source(s) for which you want to specify settings by selecting the check box adjacent to each data source name.

Note:

When you select multiple data sources, the text Varies among data sources might be displayed in certain fields, indicating that the current values of those fields are different across the selected data sources. If you change the values in such fields, the new values are applied uniformly across the selected data sources.

To add a new database instance, click Add, and then specify the host name, instance name and port number.

Test JDBC Data Sources

Description of test_jdbc_ds.gif follows
Description of the illustration test_jdbc_ds.gif

Use this screen to test the data source connections you configured on the Configure JDBC Data Source and Configure Oracle RAC Multi Data Sources screens.

Notes:

In order to test the database connections, the database to which you are connecting must be running.

If you do not want to test the connections at this time, do not select any data sources. Click Next to continue.

Select the check box for each data source you want to test, and then click Test Connections.

The wizard tests the configuration for each selected data source by attempting to connect to a URL that is constructed by using the driver, host, port, and other information that you specified while configuring the data source.

The result of the test is indicated in the Status column. Details are displayed in the Connection Result Log section.

Run Database Scripts

Description of run_db_scripts.gif follows
Description of the illustration run_db_scripts.gif

A domain template might contain a set of SQL files organized by database type. If the domain template contains SQL files, you can run them while creating the WebLogic domain, in the Run Database Scripts screen. Database content for each of the data sources defined in your WebLogic domain is set up by using pre-existing SQL or database loading files.

Note:

No databases are defined in the WebLogic Server Base Domain (wls.jar) template. If you selected only the WebLogic Server Base Domain template as the basis for the WebLogic domain, the Configure JDBC Data Sources and the Run Database Scripts screens are not displayed.
  1. In the Available JDBC Data Sources section, select the data source for which you want to run the scripts. The scripts that can be executed are displayed in the Available SQL Files and Database Loading Options section.

  2. Select the database version from the DB Version drop-down list.

  3. Click Run Scripts.

    All the scripts displayed in the Available SQL Files and Database Loading Options section for the selected data source are executed, and the results are displayed in the Results section. To capture test output in a log file, select the Log File check box and specify the location of the log file.

  4. Repeat steps 1 through 3 for each data source for which you want to execute SQL scripts.

  5. Click Next.

Configure Keystore Credentials

This screen displays one set of Enter Keystore Password/Confirm Password fields for each product that requires a keystore password to be set.

For each set of password fields, enter and confirm the password you want to use for the keystore.

Note:

The keystore password for each product listed on this screen is required to use these products. Note the passwords you enter and provide them to anyone who is authorized to use these products.

Select Optional Configuration

Description of optional_config.gif follows
Description of the illustration optional_config.gif

Select all categories (if any) for which you want to perform advanced configuration. For each category you select, the appropriate configuration screen is displayed to allow you to perform advanced configuration. If you do not select any items on this screen, the Configuration Summary screen is displayed next.

Notes:

The categories that are listed on this screen depend on the resources defined in the templates you selected for the domain.

The Administration Server and RDBMS Security Store options are not available when you are extending a domain.

Configure Administration Server

Description of admin_server.gif follows
Description of the illustration admin_server.gif

The Administration Server is the central point from which you manage your domain. You can access the Administration Server by using the URL protocol://listen-address:listen-port. The protocol can be any of the following: t3, t3s, http, https.

From this screen, you can configure or change the following Administration Server settings. Required fields are indicated by an asterisk (*).

Specifying the Listen Address

This section provides guidelines for specifying the listen address for the Administration Server. These guidelines also apply to all Managed Servers.

If you select localhost as the listen address for a server instance, remote processes cannot connect to that server instance. Only processes on the machine that hosts the server instance can connect to the server instance. If the server instance must be accessible as localhost (for example, if you create administrative scripts that connect to localhost), and it must also be accessible by remote processes, select All Local Addresses. The server instance determines the address of the machine and listens on it.

Table 4-2 describes the behavior of each listen address type.

Table 4-2 Specifying the Listen Address

Listen Address Type Behavior

All Local Addresses or a DNS name

On multi-homed Windows machines, a server instance binds to all available IP addresses.

An IP address or a DNS name

  • To connect to the server instance, processes can specify either the IP address or the corresponding DNS name.

  • Processes that specify localhost fail to connect.

  • You must update existing processes that use localhost to connect to the server instance.

  • For connections that specify the IP address for the listen address and a secured port for the listen port, host name verification must be disabled.

Note: To resolve a DNS name to an IP address, WebLogic Server must be able to contact an appropriate DNS server or obtain the IP address mapping locally. Therefore, if you specify a DNS name for the listen address, you must either leave a port open long enough for the WebLogic Server instance to connect to a DNS server and cache its mapping or you must specify the IP address mapping in a local file. If you specify an IP address for the listen address, and a client request then specifies a DNS name, WebLogic Server attempts to resolve the DNS name. If it cannot access DNS name mapping, the request fails.

localhost

  • Processes must specify localhost to connect to the server instance.

  • Only processes that reside on the machine that hosts the server instance (local processes) can connect to the server instance.


Specifying the Listen Port

Note the following guidelines when specifying the listen port for the Administration Server. These guidelines also apply to Managed Servers.

  • Although you can specify any valid port number, if you specify port 80, you can omit the port number from the HTTP request used to access resources over HTTP. For example, if you define port 80 as the listen port, you can use the URL http://hostname/myfile.html instead of http://hostname:portnumber/myfile.html.

  • On some operating systems, port 80 can be accessed only by processes run under a privileged user or group ID. In this case, you can assign the server instance to a UNIX machine on which a post-bind UID or GID is defined.

Select JMS Distributed Destination Type

Description of jms_dd_type.gif follows
Description of the illustration jms_dd_type.gif

By default, for backward compatibility, JMS distributed destinations are automatically converted to Weighted Distributed Destination (WDD). To change a JMS distributed destination to use Uniform Distributed Destination (UDD) behavior, select UDD from the drop-down list. Oracle recommends using the UDD setting.

Note:

When you change JMS system resource behavior, the setting applies only to the current session unless the JMS system resource is assigned to a cluster. Once the JMS system resource is assigned to a cluster, the setting becomes fixed and cannot be changed.

For more information about UDD and WDD, see "Types of Distributed Destinations" in Programming JMS for Oracle WebLogic Server.

Configure Managed Servers

Description of managed_servers.gif follows
Description of the illustration managed_servers.gif

From this screen, you can add or delete Managed Servers. You can also change the settings for an existing Managed Server. Required fields are indicated by an asterisk (*).

Note:

You can create Managed Servers on remote machines by using the pack and unpack commands. For more information, see "Creating and Starting a Managed Server on a Remote Machine" in Creating Templates and Domains Using the Pack and Unpack Commands.

To delete a server, select the server and click Delete. You can delete only one server at a time.

To add a server, click Add and configure the settings for the new server. The default name for a new server is new_ManagedServer_n, where n starts at 1 and increments for each new server you add.

To switch the display from the default tabular format to a tabbed format (with one tab for each server), click Switch Display. Click Switch Display again to return to tabular format.

Configure Clusters

Description of clusters.gif follows
Description of the illustration clusters.gif

A cluster is a group of WebLogic Server instances that work together to provide scalability and high-availability for applications. By creating clusters, you can group Managed Servers such that they operate as a single unit for hosting applications and resources.

Use this screen to add or delete clusters. You can also change the settings for an existing cluster. Required fields are indicated by an asterisk (*).

To delete a cluster, select the server and click Delete. When you delete a cluster, you do not delete the servers assigned to it; the servers are merely removed from the cluster and can then be added to another cluster. You can delete only one cluster at a time.

To add a cluster, click Add and configure the settings for the new server. The default name for a new cluster is new_Cluster_n, where n starts at 1 and increments for each new cluster you add. To change the default, type the desired name in the Name column.

To switch the display from the default tabular format to a tabbed format (with one tab for each cluster), click Switch Display. Click Switch Display again to return to tabular format.

For more information about clusters, see "Setting Up WebLogic Clusters" in Using Clusters for Oracle WebLogic Server.

Assign Servers to Clusters

Description of assign_srv_to_clust.gif follows
Description of the illustration assign_srv_to_clust.gif

Use this screen to assign Managed Servers to clusters.

Note:

Only Managed Servers are displayed in the Server list box. The Administration Server is not listed because it cannot be assigned to a cluster.

To assign one or more servers to a cluster:

  1. In the Cluster list box, select the cluster to which you want to assign a Managed Server.

  2. Assign Managed Servers to the selected cluster in one of the following ways:

    • Double-click the name of the Managed Server in the Server list box.

    • Select the Managed Server and click the right arrow.

    • Shift+click to select multiple Managed Servers; then, click the right arrow.

    The name of the Managed Server is removed from the Server list box and added below the name of the target cluster in the Cluster list box.

  3. Repeat steps 1 and 2 for each Managed Server to assign to a cluster.

  4. Review the cluster assignments.

    If necessary, you can remove a Managed Server from a cluster in one of the following ways:

    • Double-click the name of the Managed Server in the Cluster list box.

    • Select the Managed Server and click the left arrow.

    The name of the Managed Server is removed from the Cluster list box and restored to the Server list box.

Create HTTP Proxy Applications

Description of http_proxy.gif follows
Description of the illustration http_proxy.gif

An HTTP proxy application acts as an intermediary for HTTP requests.

Use this screen to create an HTTP proxy application for each cluster, and specify the Managed Server on which the proxy application must be deployed.

This screen is displayed only if both of the following statements are true:

To create HTTP proxy applications:

  1. Select the Create HTTP Proxy check box next to the cluster for which you want to create the HTTP proxy application.

    A list of the Managed Servers that are not assigned to any cluster is displayed in the Proxy Server list.

  2. From the Proxy Server list, select a Managed Server on which the proxy application must be deployed.

    A proxy application named OracleProxy4_clustername_servername is created and deployed in the Managed Server.

  3. Repeat steps 1 and 2 for each cluster for which you want to create HTTP proxy applications.

Configure Machines

Description of machines.gif follows
Description of the illustration machines.gif

In a WebLogic domain, the machine definitions identify physical units of hardware and are associated with the WebLogic Server instances that they host.

Use this screen to add or delete machines, or to modify the settings for an existing machine. Each machine has the following configuration settings. Required fields are marked with an asterisk (*).

You might want to create machine definitions in situations such as the following:

Select the Machine tab (for Windows) or the UNIX Machine tab (for UNIX).

Click Add to add a new machine. The default name for a new machine is new_[Unix]Machine_n, where n starts at 1 and increments by 1 for each machine that you add.

Click Delete to delete an existing machine.

Assign Servers to Machines

Description of assign_srv_to_mach.gif follows
Description of the illustration assign_srv_to_mach.gif

Use this screen to assign WebLogic Server instances to each of the machines you defined.

  1. In the Machine list box, select the Windows or UNIX machine to which you want to assign a WebLogic Server instance.

  2. Assign WebLogic Server instances to the selected machine in one of the following ways:

    • Double-click the WebLogic Server instance in the Server list box.

    • Select the appropriate WebLogic Server instance in the Server list box and click the right arrow.

    • Shift+click to select multiple servers in the Server list box; then, click the right arrow.

    The name of the WebLogic Server instance is removed from the Server list box and added, below the name of the target machine, in the Machine list box.

  3. Repeat steps 1 and 2 for each WebLogic Server instance to assign to a machine.

  4. Review the machine assignments.

    If necessary, you can remove a WebLogic Server instance from a machine in one of the following ways:

    • Double-click the name of the appropriate WebLogic Server instance in the Machine list box.

    • Select the appropriate WebLogic Server instance in the Machine list box and click the left arrow.

    The name of the WebLogic Server instance is removed from the Machine list box and restored to the Server list box.

Target Deployments to Clusters or Servers

Description of target_deployments.gif follows
Description of the illustration target_deployments.gif

Use this screen to target applications for deployment on servers or clusters.

Applications associated with the product for which you are configuring the domain (for example, SOA) are targeted automatically to the Managed Server created for that product or to the cluster to which that Managed Server is assigned. In this screen, you can target applications to additional servers and clusters.

To target an application deployment to a cluster or server:

  1. In the Target list box, select the cluster or server on which you want to deploy applications.

    The name of the selected target is displayed as the title of the list box on the right.

  2. In the target_name list box, select the check boxes corresponding to the applications to deploy on the selected target.

    The applications displayed here vary, depending on the products that you selected in the Select Domain Source screen, earlier in the wizard.

    Note:

    When you select a Managed Server in the Target list box, some of the check boxes in the target_name list box might be disabled, indicating applications that are already targeted at the cluster that contains the selected Managed Server.

    After you select applications, the names of the targeted clusters and servers are displayed in the Target column in the target_name list box.

  3. Repeat steps 1 and 2 for the other clusters and servers, as required.

  4. After making the required selections, click Next.

When you extend a domain, if you delete a Managed Server or cluster to which applications are currently targeted, the Configuration Wizard automatically retargets those applications as follows:

Target Services to Clusters or Servers

Description of target_services.gif follows
Description of the illustration target_services.gif

Use this screen to target services to the appropriate Managed Servers or clusters.

Services that are associated with the product for which you are configuring the domain (for example, SOA) are targeted automatically, to the Managed Server created for that product or to the cluster to which that Managed Server is assigned. In this screen, you can target services to additional servers and clusters.

To target services to Managed Servers or clusters:

  1. In the Target list box, select the cluster or server on which you want to deploy services.

    The name of the selected target is displayed as the title of the list box on the right.

  2. In the target_name list box, select the check boxes corresponding to the services to deploy on the selected target.

    The services displayed here vary, depending on the products that you selected in the Select Domain Source screen earlier in the wizard.

    Note:

    When you select a Managed Server in the Target list box, some of the check boxes in the target_name list box might be disabled, indicating services that are already targeted at the cluster that contains the selected Managed Server.

    After you select services, the names of the targeted clusters and servers are displayed in the Target column in the target_name list box.

  3. Repeat steps 1 and 2 for the other clusters and servers, as required.

  4. After making the required selections, click Next.

When you extend a domain, if you delete a Managed Server or cluster to which services are currently targeted, the Configuration Wizard automatically retargets those services as follows:

Configure JMS File Stores

Description of jms_file_stores.gif follows
Description of the illustration jms_file_stores.gif

A JMS file store is a disk-based file in which persistent messages can be saved.

Use this screen to modify the JMS file stores that are configured in your domain. It contains the following fields. Required fields are marked with an asterisk (*).

Notes:

The use of the direct-write policy is reliable in Solaris systems, but Windows systems may leave transaction data in the on-disk cache without writing it to disk immediately. This is considered unreliable, because a power failure can cause loss of on-disk cache data, possibly resulting in lost or duplicate messages. For reliable writes using the direct-write policy on Windows, either disable all write caching for the disk (enabled by default), or use a disk with a battery-backed cache. Some file systems, however, do not allow this value to be changed (for example, a RAID system that has a reliable cache).

If the JMS file store is used exclusively for paging non-persistent messages to the disk, the synchronous write policy is ignored.

To switch the display from the default tabular format to a tabbed format (with one tab for each server), click Switch Display. Click Switch Display again to return to tabular format.

Configure RDBMS Security Store Database

Description of rdbms_sec_store.gif follows
Description of the illustration rdbms_sec_store.gif

Configure the following RDBMS security store database fields. Required fields are marked with an asterisk (*).

Configuration Summary

Description of config_summary.gif follows
Description of the illustration config_summary.gif

Review the detailed configuration settings of your domain before continuing.

In the Domain Summary pane, select an item to display details about that item in the Details pane on the right.

You can limit the items that are displayed in the Domain Summary pane by selecting a filter option from the Summary View drop-down list.

If you need to change the configuration, click Previous to return to the appropriate screen.

Creating Domain

Description of creating_domain.gif follows
Description of the illustration creating_domain.gif

This screen shows the progress of the domain creation.

When the domain creation process completes, click Done to close the Configuration Wizard.

On Windows systems, if you want to start the Administration Server after closing the Configuration Wizard, select the Start Admin Server check box. This check box is not available on UNIX systems.

Extending Domain

Description of extending_domain.gif follows
Description of the illustration extending_domain.gif

This screen shows the progress of the domain extension process.

When the domain creation process completes, click Done to close the Configuration Wizard.