Follow the instructions in this section to create and configure the domain for MFT, with static clusters.

Domain creation and configuration includes the following tasks.

• Task 1, "Selecting the Domain Type and Domain Home Location"

• Task 2, "Selecting the Configuration Templates"

• Task 3, "Configuring High Availability Options"

• Task 4, "Selecting the Application Home Location"

• Task 5, "Configuring the Administrator Account"

• Task 6, "Specifying the Domain Mode and JDK"

• Task 7, "Specifying the Database Configuration Type"

• Task 8, "Specifying JDBC Component Schema Information"

• Task 9, "Providing the GridLink Oracle RAC Database Connection Details"

• Task 10, "Testing the JDBC Connections"

• Task 11, "Specifying the Keystore"

• Task 12, "Selecting Advanced Configuration"

• Task 13, "Configuring the Administration Server Listen Address"

• Task 14, "Configuring Node Manager (Per Host)"

• Task 15, "Configuring Managed Servers"

• Task 16, "Configuring a Cluster"

• Task 17, "Assigning Server Templates"

• Task 18, "Configuring Dynamic Servers"

• Task 19, "Assigning Managed Servers to the Cluster"

• Task 20, "Configuring Coherence Clusters"

• Task 21, "Creating Machines"

• Task 22, "Assigning Servers to Machines"

• Task 23, "Reviewing Your Configuration Specifications and Configuring the Domain"

• Task 24, "Writing Down Your Domain Home and Administration Server URL"

Task 1   Selecting the Domain Type and Domain Home Location

You must select a Domain home directory location, optimally outside the Oracle home directory.

Oracle recommends that you locate your Domain home in accordance with the directory structure in What Are the Key Oracle Fusion Middleware Directories? in Understanding Oracle Fusion Middleware, where the Domain home is located outside the Oracle home directory. This directory structure helps avoid issues when you need to upgrade or reinstall software.

To specify the Domain type and Domain home directory:

1. On the Configuration Type screen, select Create a new domain.

2. In the Domain Location field, specify your Domain home directory.

For more information about this screen, see Configuration Type in Creating WebLogic Domains Using the Configuration Wizard

Task 2   Selecting the Configuration Templates

On the Templates screen, make sure Create Domain Using Product Templates is selected, then select the following templates:

• Oracle Managed File Transfer [mft]

  Selecting this template automatically selects the following dependencies:

  • Oracle Enterprise Manager

  • Oracle B2B Client

  • Oracle JRF

  • Oracle WSM Policy Manager

  • WebLogic Coherence Cluster Extension

For more information about the options on this screen, see Templates in Creating WebLogic Domains Using the Configuration Wizard.

Task 3   Configuring High Availability Options

This screen appears for the first time when you create a cluster that uses Automatic Service Migration or JDBC stores or both. After you select HA Options for a cluster, all subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply HA options (that is, the Configuration Wizard creates JDBC stores and configures ASM for them).

On the High Availability Options screen:

• Select Enable Automatic Service Migration with Database Basis.

• Set JTA Transaction Log Persistence to JDBC TLog Store.

• Set JMS Server Persistence to JMS JDBC Store.

Note:

Oracle recommends that you use JDBC stores, which leverage the consistency, data protection, and high availability features of an Oracle database and makes resources available for all the servers in the cluster. So, the Configuration Wizard steps assume that the JDBC persistent stores are used along with Automatic Service Migration.

When you choose JDBC persistent stores, additional unused File Stores are automatically created but are not targeted to your clusters. Ignore these File Stores.

If, for any reason, you want to use Files Stores, you can retain the default values for TLOGs and JMS persistent store options in this screen and configure them in a shared location later. See Task 12, "Selecting Advanced Configuration". Shared location is required to resume JMS and JTA in a failover scenario.

You can also configure TLOGs and JMS persistent stores manually in a post step. For information about the differences between JDBC and Files Stores, and for specific instructions to configure them manually, see Using Persistent Stores for TLOGs and JMS in an Enterprise Deployment.

Click Next.

Task 4   Selecting the Application Home Location

On the Application Location screen, specify the value of the APPLICATION_HOME variable, as defined in File System and Directory Variables Used in This Guide.

For more information about the options on this screen, see Application Location in Creating WebLogic Domains Using the Configuration Wizard.

Task 5   Configuring the Administrator Account

On the Administrator Account screen, specify the user name and password for the default WebLogic Administrator account for the domain.

Make a note of the user name and password specified on this screen; you need these credentials later to boot and connect to the domain's Administration Server.

Task 6   Specifying the Domain Mode and JDK

On the Domain Mode and JDK screen:

• Select Production in the Domain Mode field.

• In the Enable or Disable Default Ports for You Domain field, use the default values provided for Production Mode:

  • Ensure that Enable Listen Ports (non-SSL Ports) is NOT checked.

  • Ensure that Enable SSL Listen Ports is checked.

  • Ensure that Enable Administration Port (SSL Port) is checked.

    Tip:

    More information about the options on this screen, including the differences between development mode and production mode, can be found in Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.

• Select Oracle Hotspot JDK in the JDK field.

  Note:

  Ensure that it points to the folder where you have installed the JDK. See Installing the JDK Software.

Task 7   Specifying the Database Configuration Type

On the Database Configuration Type screen:

• Select RCU Data to activate the fields on this screen.

  The RCU Data option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for the schemas needed to configure the domain.

• Verify that the Vendor is Oracle and the Driver is *Oracle's Driver (Thin) for Service Connections; Versions: Any.

• Verify that Connection Parameters is selected.

Note:

If you select Manual Configuration on this screen, you must manually fill in the parameters for your schema on the JDBC Component Schema screen.

After you select RCU Data, fill in the fields as shown in the following table:

Field	Description
DBMS/Service	Enter the service name for the Oracle RAC database where you install the product schemas. For example: soaedg.example.com Be sure this is the common service name that is used to identify all the instances in the Oracle RAC database; do not use the host-specific service name.
Host Name	Enter the Single Client Access Name (SCAN) Address for the Oracle RAC database, which you entered in the Enterprise Deployment Workbook.
Port	Enter the port number on which the database listens. For example, 1521.
Schema Owner Schema Password	Enter the user name and password to connect to the database's Service Table schema. This is the schema user name and password that was specified for the Service Table component on the Schema Passwords screen in RCU. See Creating the Database Schemas. The default user name is prefix_STB, where prefix is the custom prefix that you have defined in RCU.

Click Get RCU Configuration when you finished specifying the database connection information. The following output in the Connection Result Log indicates that the operating succeeded:

Connecting to the database server...OK
Retrieving schema data from database server...OK
Binding local schema components with retrieved data...OK

Successfully Done.

Click Next if the connection to the database is successful.

For more information about the RCU Data option, see Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.

For more information about the other options on this screen, see Datasource Defaults in Creating WebLogic Domains Using the Configuration Wizard.

Task 8   Specifying JDBC Component Schema Information

Verify that the values on the JDBC Component Schema screen are correct for all schemas.

The schema table should be populated, because you selected Get RCU Data on the previous screen. As a result, the Configuration Wizard locates the database connection values for all the schemas required for this domain.

At this point, the values are configured to connect to a single-instance database. However, for an enterprise deployment, you should use a highly available Real Application Clusters (RAC) database, as described in Preparing the Database for an Enterprise Deployment.

In addition, Oracle recommends that you use an Active GridLink datasource for each of the component schemas. For more information about the advantages of using GridLink data sources to connect to a RAC database, see Database Considerations in the High Availability Guide.

To convert the data sources to GridLink:

1. Select all the schemas by selecting the checkbox in the first header row of the schema table.

2. Click Convert to GridLink and click Next.

Task 9   Providing the GridLink Oracle RAC Database Connection Details

On the GridLink Oracle RAC Component Schema screen, provide the information that is required to connect to the RAC database and component schemas, as shown in following table.

Element	Description and Recommended Value
Service Name	Verify that the service name for the Oracle RAC database is the appropriate. For example, soaedg.example.com.
SCAN, Host Name, and Port	Select the SCAN check box. In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database. In the Port field, enter the SCAN listening port for the database (for example, 1521).
ONS Host and Port	These values are not required when you are using an Oracle 12c database or higher versions because the ONS list is automatically provided from the database to the driver.
Enable Fan	Verify that the Enable Fan check box is selected, so that the database can receive and process FAN events.

For more information about specifying the information on this screen, as well as information about how to identify the correct SCAN address, see Configuring Active GridLink Data Sources with Oracle RAC in the High Availability Guide.

You can also click Help to display a brief description of each field on the screen.

Task 10   Testing the JDBC Connections

A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.

By default, the schema password for each schema component is the password you specified while creating your schemas. If you want different passwords for different schema components, manually edit them in the previous screen (JDBC Component Schema) by entering the password you want in the Schema Password column, against each row. After you specify the passwords, select the check box that correspond to the schemas that you changed the password in and test the connection again.

For more information about the other options on this screen, see Test Component Schema in Creating WebLogic Domains Using the Configuration Wizard.

Task 11   Specifying the Keystore

Use the Keystore screen in the Configuration Wizard to specify details about the keystore to be used in the domain.

For a typical enterprise deployment, you can leave the default values. See Keystore in Creating WebLogic Domains Using the Configuration Wizard

Task 12   Selecting Advanced Configuration

To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:

• Administration Server

  This is required to properly configure the listen address of the Administration Server.

• Node Manager

  This is required to configure Node Manager.

• Topology

  This is required to add, delete, or modify the Settings for Server Templates, Managed Servers, Clusters, Virtual Targets, and Coherence.

Note:

• If any of the above options are not available on the screen, then return to the Templates screen and ensure that you have selected the required templates for this topology.

• JDBC stores are recommended and selected in Task 3, "Configuring High Availability Options" so there is no need to configure File Stores.

Task 13   Configuring the Administration Server Listen Address

On the Administration Server screen:

1. In the Server Name field, retain the default value "AdminServer".

2. In the Listen Address field, enter the virtual host name that corresponds to the VIP of the ADMINVHN that you procured in Procuring Resources for an Enterprise Deployment and enabled in Preparing the Host Computers for an Enterprise Deployment.

   For more information about the purpose of using the ADMINVHN virtual host, see Reserving the Required IP Addresses for an Enterprise Deployment.

3. In the Configure Administration Server Ports section, perform the following steps:

   1. Leave the Enable Listen Port field unchecked. The Listen Port value will be disabled in grey.

   2. Ensure the Enable SSL Listen port field is checked.

   3. Leave the default value as 7002 in the SSL Listen Port field.

   4. Leave the default value as 9002 in the Administration Port.

4. Leave the default value as Unspecified in the Server Group.

Task 14   Configuring Node Manager (Per Host)

Select Manual Node Manager Setup as the Node Manager type.

WARNING:

You can ignore the warning in the bottom pane. This guide provides the required steps for the Manual Node Manager configuration.

Tip:

For more information about the options on this screen, see Node Manager in Creating WebLogic Domains Using the Configuration Wizard.

For more information about per domain and per host Node Manager implementations, see About the Node Manager Configuration in a Typical Enterprise Deployment.

For information about Node Manager configurations, see Configuring Node Manager on Multiple Machines in Administering Node Manager for Oracle WebLogic Server.

Task 15   Configuring Managed Servers

Use the Managed Servers screen to create the Managed Servers that are required in the Managed File Transfer domain.

1. Change the default server name to WLS_MFT1 in the Server name column.

2. Click Add and repeat this process to create a second Managed Server named WLS_MFT2.

3. Use the information in Table 18-1 to fill in the rest of the columns for each MFT Managed Server.

The Managed Server names suggested in this procedure (WLS_MFT1 and WLS_MFT2) are referenced throughout this document; if you choose different names then be sure to replace them as needed,

For more information about the options on this screen, see Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.

Table 18-1 MFT Managed Server

Server Name	Listen Address	Enable Listen Port	Listen Port	Enable SSL Port	SSL Listen Port	Administration Port	Server Groups
WLS_MFT1	MFTHOST1	Unchecked	Disabled	Checked	7010	9014	MFT-MGD-SVRS
WLS_MFT2	MFTHOST2	Unchecked	Disabled	Checked	7010	9014	MFT-MGD-SVRS

The selected server group ensures that the Managed File Transfer and Oracle Web Services Manager (OWSM) software is targeted to the Managed Server.

There is another server group called MFT-MGD-SVRS-ONLY that targets only MFT but not Oracle Web Services Manager (OWSM) to the server. This is typically used if you want to have Oracle Web Services Manager (OWSM) in a different server rather than with the MFT server.

The server groups target Fusion Middleware applications and services to one or more servers by mapping defined groups of application services to each defined server group. Any application services that are mapped to a given server group are automatically targeted to all servers that are assigned to that group. See Application Service Groups, Server Groups, and Application Service Mappings in Domain Template Reference.

Task 16   Configuring a Cluster

Use the Clusters screen to create a new cluster:

1. Click the Add button.

2. Specify MFT_Cluster in the Cluster Name field.

3. Leave the Cluster Address field blank.

4. Specify mft.example.com in the Frontend Host field.

5. Specify 0 as the Frontend HTTP port and 443 as the Frontend HTTPS port.

For more information about the options on this screen, see Clusters in Creating WebLogic Domains Using the Configuration Wizard.

Task 17   Assigning Server Templates

Click Next.

Task 18   Configuring Dynamic Servers

Verify that all dynamic server options are disabled for clusters that are to remain as static clusters.

1. Confirm that the Calculated Machine Names and Calculated Listen Port checkboxes on this screen are unchecked.

2. Confirm that the Server Template and Dynamic Server Groups selections are Unspecified.

3. Click Next.

Task 19   Assigning Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign Managed Servers to the new cluster.

1. In the Clusters pane, select the cluster to which you want to assign the servers; in this case, MFT_Cluster.

2. In the Servers pane, assign WLS_MFT1 to MFT_Cluster by doing one of the following:

   • Click once on WLS_MFT1 to select it, then click on the right arrow to move it beneath the selected cluster (MFT_Cluster)) in the Clusters pane.

     or

   • Double-click on WLS_MFT1 to move it beneath the selected cluster (MFT_Cluster) in the clusters pane.

3. Repeat these steps to assign the WLS_MFT2 Managed Server to MFT_Cluster.

For more information about the options on this screen, see Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.

Task 20   Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain.

In the Cluster Listen Port, enter 9991.

For Coherence licensing information, Oracle Coherence Products in Oracle Fusion Middleware Licensing Information User Manual.

Task 21   Creating Machines

Use the Machines screen to create five new machines in the domain. A machine is required in order for the Node Manager to be able to start and stop the servers.

1. Select the Unix Machine tab.

2. Click the Add button to create five new UNIX machines.

   Use the values in Table 18-2 to define the Name and Node Manager Listen Address of each machine.

3. Verify the port in the Node Manager Listen Port field.

   The port number 5556, shown in this example, may be referenced by other examples in the documentation. Replace this port number with your own port number as needed.

   Note:

   If you are installing on a host where additional domains were already configured, and you have already configured a per host Node Manager, then the address and port configured in this screen must be for the existing per host Node Manager.

Table 18-2 Values to Use When Creating Unix Machines

Name	Node Manager Listen Address	Node Manager Type	Node Manager Listen Port
MFTHOST1	The value of the MFTHOST1 host name variable or MFTHOST1 alias. For example, MFTHOST1.example.com.	SSL	5556
MFTHOST2	The value of the MFTHOST2 host name variable or MFTHOST2 alias. For example, MFTHOST2.example.com.	SSL	5556
ADMINHOST	Enter the value of the ADMINVHN variable.	SSL	5556

For more information about the options on this screen, see Machines in Creating WebLogic Domains Using the Configuration Wizard.

Task 22   Assigning Servers to Machines

Use the Assign Servers to Machines screen to assign the Administration Server and the two Managed Servers to the appropriate machine.

The Assign Servers to Machines screen is similar to the Assign Managed Servers to Clusters screen. Select the target machine in the Machines column, select the Managed Server in the left column, and click the right arrow to assign the server to the appropriate machine.

Assign the servers as follows:

• Assign the AdminServer to the ADMINHOST machine.

• Assign the WLS_MFT1 Managed Server to the MFTHOST1 machine.

• Assign the WLS_MFT2 Managed Server to the MFTHOST2 machine.

For more information about the options on this screen, see Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.

Task 23   Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen contains detailed configuration information for the domain that you are about to create. Review the details of each item on the screen and verify that the information is correct.

If you need to make any changes, you can go back to any previous screen either by using the Back button or by selecting the screen in the navigation pane.

Domain creation does not begin until you click Create.

In the Configuration Progress screen, click Next when it finishes.

For more information about the options on this screen, see Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.

Task 24   Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen shows the following items about the domain you just configured:

• Domain Location

• Administration Server URL

You must make a note of both items as you need them later; the domain location is needed to access the scripts used to start the Administration Server.

Click Finish to dismiss the Configuration Wizard.