Configuring Oracle Managed File Transfer Domain

4 Configuring Oracle Managed File Transfer Domain

After you have installed Oracle Managed File Transfer, you can configure the domain, which you can also extend for high availability.

The configuration steps presented here assume that you have completed the installation steps covered in:

Refer to the following sections to create the database schemas, configure a WebLogic domain, and verify the configuration:

Creating the Database Schemas

Before you can configure a domain, you must install required schemas on a certified database for use with this release of Oracle Fusion Middleware.

Note:

As of Oracle Fusion Middleware 14c (14.1.2.0.0), new schemas are created with editions-based redefinition (EBR) views enabled by default. When EBR is enabled, the schema objects can be upgraded online to a future Fusion Middleware release without any downtime. For more information about using editions-based redefinition, see Using Edition-based Redefinition.

Installing and Configuring a Certified Database

Before you create the database schemas, you must install and configure a certified database, and verify that the database is up and running.

See About Database Requirements for an Oracle Fusion Middleware Installation.

Starting the Repository Creation Utility

Start the Repository Creation Utility (RCU) after you verify that a certified JDK is installed on your system.

To start the RCU:

Verify that a certified JDK already exists on your system by running java -version from the command line. For 14c (14.1.2.0.0), the certified JDK is 17.0.12 and later.

See About JDK Requirements for an Oracle Fusion Middleware Installation.
Ensure that the JAVA_HOME environment variable is set to the location of the certified JDK.
Change to the following directory:
- (UNIX) ORACLE_HOME/oracle_common/bin
- (Windows) ORACLE_HOME\oracle_common\bin
Enter the following command:
- (UNIX) ./rcu
- (Windows) rcu.bat

Navigating the Repository Creation Utility Screens to Create Schemas

Enter required information in the RCU screens to create the database schemas.

Introducing the RCU

The Welcome screen is the first screen that appears when you start the RCU.

Click Next.

Selecting a Method of Schema Creation

Use the Create Repository screen to select a method to create and load component schemas into the database.

On the Create Repository screen:

If you have the necessary permissions and privileges to perform DBA activities on your database, select System Load and Product Load. This procedure assumes that you have SYSDBA privileges.
If you do not have the necessary permissions or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option generates a SQL script that you can give to your database administrator. See About System Load and Product Load in Creating Schemas with the Repository Creation Utility.
If the DBA has already run the SQL script for System Load, select Perform Product Load.

Providing Database Connection Details

On the Database Connection Details screen, provide the database connection details for the RCU to connect to your database.

To provide the database connection details:

On the Database Connection Details screen, provide the database connection details.
For example:
- Database Type: Oracle EBR Database
- Connection String Format: Connection Parameters or Connection String
- Connection String: examplehost.exampledomain.com:1521:Orcl.exampledomain.com
- Host Name: examplehost.exampledomain.com
- Port: 1521
- Service Name: Orcl.exampledomain.com
- Username: sys
- Password: ******
- Role: SYSDBA
Click Next to proceed, then click OK in the dialog window that confirms a successful database connection.

For information about specifying connection credentials when connecting to an Oracle database, see Connection Credentials for Oracle Databases and Oracle Databases with Edition-Based Redefinition.

Specifying a Custom Prefix and Selecting Schemas

Specify a custom prefix and database schema to automatically select dependent schemas.

Select Create new prefix, specify a custom prefix, then select Managed File Transfer schema This will automatically select the other schemas as dependencies.

Tip:

Make a note of the custom prefix you choose to enter here. You will need this later on during the domain creation process.

A schema called Common Infrastructure Services is also automatically created. It is grayed out (you can’t select it or deselect it). This schema enables you to retrieve information from RCU during domain configuration. See About the Service Table Schema in Creating Schemas with the Repository Creation Utility.

The custom prefix is used to logically group these schemas together for use in this domain only; you must create a unique set of schemas for each domain as schema sharing across domains is not supported.

For more information about custom prefixes, see About Custom Prefixes in Creating Schemas with the Repository Creation Utility.

For more information about how to organize your schemas in a multi-domain environment, see Planning Your Schema Creation in Creating Schemas with the Repository Creation Utility.

Click Next to proceed, then click OK to confirm that prerequisite checking for schema creation was successful.

Specifying Schema Passwords

On the Schema Passwords screen, specify how you want to set the schema passwords on your database, then enter and confirm your passwords.

You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.

Click Next.

Completing Schema Creation

Navigate through the remaining RCU screens to complete schema creation.

On the Map Tablespaces screen, the Encrypt Tablespace check box appears only if you enabled Transparent Data Encryption (TDE) in the database (Oracle or Oracle EBR) when you start the RCU.

To complete schema creation:

On the Map Tablespaces screen, select Encrypt Tablespace if you want to encrypt all new tablespaces that the RCU creates.
In the Completion Summary screen, click Close to dismiss the RCU.

Configuring the Domain

Use the Configuration Wizard to create and configure a domain.

For information on other methods to create domains, see Additional Tools for Creating, Extending, and Managing WebLogic Domains in Creating WebLogic Domains Using the Configuration Wizard.

Starting the Configuration Wizard

Start the Configuration Wizard to begin configuring a domain.

To start the Configuration Wizard:

Change to the following directory:

(UNIX) ORACLE_HOME/oracle_common/common/bin

(Windows) ORACLE_HOME\oracle_common\common\bin

where ORACLE_HOME is your 14c (14.1.2.0.0) Oracle home.
Enter the following command:

(UNIX) ./config.sh

(Windows) config.cmd

Navigating the Configuration Wizard Screens to Create and Configure the Domain

Enter required information in the Configuration Wizard screens to create and configure the domain for the topology.

Note:

You can use this procedure to extend an existing domain. If your needs do not match the instructions in the procedure, be sure to make your selections accordingly, or see the supporting documentation for more details.

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:

On the Configuration Type screen, select Create a new domain.
In the Domain Location field, specify your Domain home directory.

Note:
If MFT shares the node with SOA, the Domain home directory must be different. You can use mftedg_domain here.

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

Selecting the Configuration Templates for Oracle Managed File Transfer

Use the Templates screen to select the templates you require.

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

Oracle Managed File Transfer - 14.1.2.0.0 [mft]

Selecting this template automatically selects the dependencies.

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

Configuring High Availability Options

Use this screen to configure service migration and persistence settings that affect high availability.

This screen appears for the first time when you create a cluster that uses automatic service migration, persistent stores, or both, and all subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply the selected HA options.

Enable Automatic Service Migration

Select Enable Automatic Service Migration to enable pinned services to migrate automatically to a healthy Managed Server for failover. It configures migratable target definitions that are required for automatic service migration and the cluster leasing. Choose one of these cluster leasing options:

Database Leasing - Managed Servers use a table on a valid JDBC System Resource for leasing. Requires that the Automatic Migration data source have a valid JDBC System Resource. If you select this option, the Migration Basis is configured to Database and the Data Source for Automatic Migration is also automatically configured by the Configuration Wizard. If you have a high availability database, such as Oracle RAC, to manage leasing information, configure the database for server migration.
Consensus Leasing - Managed Servers maintain leasing information in-memory. You use Node Manager to control Managed Servers in a cluster. (All servers that are migratable, or which could host a migratable target, must have a Node Manager associated with them.) If you select this option, the Migration Basis is configured to Consensus by the Configuration Wizard.

See Leasing for more information on leasing.

See Service Migration for more information on Automatic Service Migration.

JTA Transaction Log Persistence

This section has two options: Default Persistent Store and JDBC TLog Store.

Default Persistent Store - Configures the JTA Transaction Log store of the servers in the default file store.
JDBC TLog Store - Configures the JTA Transaction Log store of the servers in JDBC stores.

Oracle recommends that you select JDBC TLog Store. When you complete the configuration, you have a cluster where JDBC persistent stores are set up for Transaction logs.

For more details on persistent and TLOG stores, see the following topics in Developing JTA Applications for Oracle WebLogic Server:

JMS Server Persistence

A persistent JMS store is a physical repository for storing persistent message data and durable subscribers. It can be either a disk-based file store or a JDBC-accessible database. You can use a JMS file store for paging of messages to disk when memory is exhausted.

JMS File Store - Configures a component to use JMS File Stores. If you select this option, you can choose the File Store option in the Advanced Configuration Screen to change the settings, if required. In the File Stores screen, you can set file store names, directories, and synchronous write policies.
JMS JDBC Store - Configures a component to use JDBC stores for all its JMS servers. When you complete the configuration, you have a cluster and JDBC persistent stores are configured for the JMS servers.

Selecting the Application Home Location

Use the Application Location screen to select the location to store applications associated with your domain, also known as the Application home directory.

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

For more about the Application home directory, see About the Application Home Directory.

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

Configuring the Administrator Account

Use the Administrator Account screen to specify the user name and password for the default WebLogic Administrator account for the domain.

Oracle recommends that you make a note of the user name and password that you enter on this screen; you need these credentials later to boot and connect to the domain's Administration Server.

Specifying the Domain Mode and JDK

Use the Domain Mode and JDK screen to specify the domain mode and Java Development Kit (JDK) for your production environment.

On the Domain Mode and JDK screen:

Select Production in the Domain Mode field.
Note:

As of WebLogic Server 14.1.2.0.0, when you select Production mode, WebLogic Server automatically sets some of the security configurations of Secured Production to more secure values. However, there are certain security configurations (such as SSL/TLS) that require manual configuration. See Using Secured Production Mode in Administering Security for Oracle WebLogic Server.

If you want to disable the more secure default settings, then you may select Disable Secure Mode. This will enable the non-SSL listen ports.
If you want to retain the more secure default settings of Secured Production mode in general, but want to change which ports (listen ports, SSL listen ports, or administration ports) will be enabled by default in your domain, then you may:
- Leave Disable Secure Mode unselected, and
- Change the default port selections under Enable or Disable Default Ports for Your Domain
For more information, see Understand How Domain Mode Affects the Default Security Configuration in Securing a Production Environment for Oracle WebLogic Server.
Select the Oracle HotSpot JDK in the JDK field.

For more information about this screen, see Domain Mode and JDK in Creating WebLogic Domains Using the Configuration Wizard.

Specifying the Database Configuration Type

Use the Database Configuration type screen to specify details about the database and database schema.

On the Database Configuration type screen, select RCU Data. This option instructs the Configuration Wizard to connect to the database and Service Table (STB) schema to automatically retrieve schema information for schemas needed to configure the domain.

Note:

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

After selecting RCU Data, specify details in the following fields:

Field	Description
Host Name	Enter the name of the server hosting the database. Example: `examplehost.exampledomain.com`
DBMS/Service	Enter the database DBMS name, or service name if you selected a service type driver. Example: `orcl.exampledomain.com`
Port	Enter the port number on which the database listens. Example: `1521`
Schema Owner Schema Password	Enter the username and password for connecting to the database's Service Table schema. This is the schema username and password entered for the Service Table component on the Schema Passwords screen in the RCU (see Specifying Schema Passwords). The default username is `prefix_STB`, where `prefix` is the custom prefix that you defined in the RCU.

For an Autonomous Transaction Processing database (both Autonomous Transaction Processing-Dedicated (ATP-D) and Autonomous Transaction Processing Shared (ATP-S)), specify the connection credentials using only the Connection URL String option, and enter the connect string in the following format described in Connection Credentials for an Autonomous Transaction Processing Database.

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

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

Successfully Done.

For more information about the schema installed when the RCU is run, see About the Service Table Schema in Creating Schemas with the Repository Creation Utility.

See Database Configuration Type in Creating WebLogic Domains Using the Configuration Wizard .

Specifying JDBC Component Schema Information

Use the JDBC Component Schema screen to verify or specify details about the database schemas.

Verify that the values populated on the JDBC Component Schema screen are correct for all schemas. If you selected RCU Data on the previous screen, the schema table should already be populated appropriately.

@TNS_alias?TNS_ADMIN=<path of the wallet files, ojdbc.properties, and tnsnames.ora>

In the connect string, you must pass TNS_alias as the database service name found in tnsnames.ora, and TNS_ADMIN property to the location of the wallet files, ojdbc.properties, and tnsnames.ora.

Example connect string for Autonomous Transaction Processing-Dedicated (ATP-D) database:

@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/

Example connect string for Autonomous Transaction Processing Shared (ATP-S) database:

@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/

For high availability environments, see the following sections in High Availability Guide for additional information on configuring data sources for Oracle RAC databases:

See JDBC Component Schema in Creating WebLogic Domains Using the Configuration Wizard for more details about this screen.

Testing the JDBC Connections

Use the JDBC Component Schema Test screen to test the data source 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.

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

Specifying the Path to the Keystore Certificate or Key

Use the Keystore screen to specify either the path to the trusted certificate for each keystore, or the path to each keystore’s private key and other private key information.

When you click in the Trusted Certificate, Private Key, or Identity Certificate fields, a browse icon appears to the right of the field. Click this icon to browse to the appropriate file.

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

Selecting Advanced Configuration

Use the Advanced Configuration screen to complete the domain configuration.

On the Advanced Configuration screen, select:

Administration Server

Required to properly configure the listen address of the Administration Server.
Node Manager

Required to configure Node Manager.
Topology

Required to configure the Oracle Managed File Transfer Managed Server.

Optionally, select other available options as required for your desired installation environment. The steps in this guide describe a standard installation topology, but you may choose to follow a different path. If your installation requirements extend to additional options outside the scope of this guide, you may be presented with additional screens to configure those options. For information about all Configuration Wizard screens, see Configuration Wizard Screens in Creating WebLogic Domains Using the Configuration Wizard.

Configuring the Administration Server Listen Address

Use the Administration Server screen to select the Listen Address and configure the Administration Server ports.

Note:

The default port values will vary depening on how you conifigured your domain. The Enable SSL Listen Port is enabled by default, but the default values may change. For a list of default values, see Port Numbers by Product and Component.

Provide a name for the Administration Server. The name field must not be null or empty and cannot contain any special characters.
Select the drop-down list next to Listen Address and select the IP address of the host where the Administration Server will reside or use the system name or DNS name that maps to a single IP address. Do not use All Local Addresses.
Verify the port settings. When the domain type is set to Production, then the Enable SSL Listen Port option is enabled by default. Do not specify any server groups for the Administration Server.

Note:

You can change the port values as needed, but they must be unique. If the same port numbers are used for different ports, you will not be able to navigate to the next step in the Configuration Wizard.

For more information, see Specifying the Listen Address in Creating WebLogic Domains Using the Configuration Wizard.

Configuring Node Manager

Use the Node Manager screen to select the type of Node Manager you want to configure, along with the Node Manager credentials.

Select Per Domain Default Location as the Node Manager type, then specify Node Manager credentials.

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

For more information about Node Manager types, see About Node Manager in Administering Node Manager for Oracle WebLogic Server.

Configuring Managed Servers for Oracle Managed File Transfer

Use the Managed Servers screen to configure Managed Servers.

On the Managed Servers screen, a new Managed Server named mft_server1 is automatically created by default.

To configure Managed Servers for Oracle Managed File Transfer:

In the Listen Address drop-down list, select the IP address of the host on which the Managed Server will reside or use the system name. Do not use All Local Addresses.
Verify your port selections. If you selected Production mode with Secure Mode enabled, Enable SSL Port is selected by default. The default port and this port will be auto-incremented so that the ports do not conflict with any additional managed servers you add. This is true for Listen Ports and Administration Ports. You can edit any and all port values based on your configuration and machines being used.

Note:

You can change the port values as needed using an integer in the range of 1 and 65535, but they must be unique. If the same port numbers are used for different ports, you will receive a port conflict error and you will not be able to start the server.

Oracle recommends that you enable SSL ports for added security. If, however, you want to change the port setting to use the less secure Listen Port, then disable the Enable SSL Port and check the Enable Listen Port option. The default Listen Port will increment with each additional managed server.
In the Server Groups drop-down list, make sure that MFT-MGD-SVRS is selected. This server group ensures that Oracle Managed File Transfer and Oracle Web Services Manager (OWSM) services are targeted to the Managed Servers you are creating.

There is another server group called MFT-MGD-SVRS-ONLY that targets only Oracle Managed File Transfer 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.

Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group. A given application service group may be mapped to multiple server groups if needed. Any application services that are mapped to a given server group are automatically targeted to all servers that are assigned to that group. For more information, see Application Service Groups, Server Groups, and Application Service Mappings in Domain Template Reference.
Configuring a second Managed Server is one of the steps needed to configure the standard topology for high availability. If you are not creating a highly available environment, then this step is optional.

Click Add and select MFT-MGD-SVRS to create a second Managed Server named mft_server2.

For more information about the high availability standard topology, see About the Fusion Middleware Standard HA Topology in High Availability Guide.

For more information about the next steps to prepare for high availability after your domain is configured, see Preparing Your Environment for High Availability.

These server names are referenced in examples throughout this document; if you choose different names be sure to replace them as needed.

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

Configuring a Cluster for Oracle Managed File Transfer

Use the Clusters screen to create a new cluster.

On the Clusters screen:

Click Add.
Specify SOA_cluster1 in the Cluster Name field.
Leave the Cluster Address field blank.

By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, see Considerations for Choosing Unicast or Multicast in Administering Clusters for Oracle WebLogic Server.

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

Defining Server Templates

If you are creating dynamic clusters for a high availability setup, use the Server Templates screen to define one or more server templates for the domain.

To add Server Templates:

Note:

Click Add to create new_ServerTemplate_1. The server template name will increment automatically when an additional server template is added (new_ServerTemplate_2).
For Secure Production Mode, verify that the Enable SSL Port option is selected. The default SSL Listen Port does not increment automatically when a new server template is added. You can change the default to Enable Listen Port, but Oracle recommends that retain the default to enable SSL. Enabling Listen Port disables SSL Listen Port.

Note:

You can change the port values as needed using an integer in the range of 1 and 65535, but they must be unique. If the same port numbers are used for different ports, you will receive a port conflict error and you will not be able to start the server.
The Administration Port does not increment when an additional server template is added.

Note:

If the Listen ports are disabled, then instead of seeing a number you will see Disabled.

For steps to create a dynamic cluster for a high availability setup, see Using Dynamic Clusters in High Availability Guide.

Configuring Dynamic Servers

If you are creating dynamic clusters for a high availability setup, use the Dynamic Servers screen to configure the dynamic servers.

If you are not configuring a dynamic cluster, click Next to continue configuring the domain.

Note:

When you create dynamic clusters, keep in mind that after you assign the Machine Name Match Expression, you do not need to create machines for your dynamic cluster.

To create a dynamic cluster for a high availability setup, see Using Dynamic Clusters in High Availability Guide.

Assigning Oracle Managed File Transfer Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign Managed Servers to a new configured cluster. A configured cluster is a cluster you configure manually. You do not use this screen if you are configuring a dynamic cluster, a cluster that contains one or more generated server instances that are based on a server template.

Note:

All Managed Servers of a component type in the domain must belong to that cluster. For example, Oracle Managed File Transfer domains support only a single Oracle Managed File Transfer cluster inside each domain.

For more on configured cluster and dynamic cluster terms, see About Dynamic Clusters in Understanding Oracle WebLogic Server.

On the Assign Servers to Clusters screen:

In the Clusters pane, select the cluster to which you want to assign the Managed Servers; in this case, mft_cluster1.
In the Servers pane, assign mft_server1 to mft_cluster1 by doing one of the following:
- Click once on mft_server1 to select it, then click the right arrow to move it beneath the selected cluster (mft_cluster1) in the Clusters pane.
- Double-click on mft_server1 to move it beneath the selected cluster (mft_cluster1) in the Clusters pane.
Repeat to assign mft_server2 to mft_cluster1.

The following image shows a generic example of the Clusters pane after Managed Servers are assigned to clusters.

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

Configuring Coherence Clusters

Use the Coherence Clusters screen to configure the Coherence cluster.

Leave the default port number as the Coherence cluster listen port. After configuration, the Coherence cluster is automatically added to the domain.

Note:

Setting the unicast listen port to 0 creates an offset for the Managed Server port numbers. The offset is 5000, meaning the maximum allowed value that you can assign to a Managed Server port number is 60535, instead of 65535.

For Coherence licensing information, see Oracle Coherence Products in Licensing Information.

Creating a New Oracle Managed File Transfer Machine

Use the Machines screen to create new machines in the domain. A machine is required so that Node Manager can start and stop servers.

If you plan to create a high availability environment and know the list of machines your target topology requires, you can follow the instructions in this section to create all the machines at this time. For more about scale out steps, see Optional Scale Out Procedure in High Availability Guide.

To create a new Oracle Managed File Transfer machine so that Node Manager can start and stop servers:

Select the Machine tab (for Windows) or the UNIX Machine tab (for UNIX), then click Add to create a new machine.
In the Name field, specify a machine name, such as mft_machine1.
In the Node Manager Listen Address field, select the IP address of the machine in which the Managed Servers are being configured.

You must select a specific interface and not localhost. This allows Coherence cluster addresses to be dynamically calculated.
Verify the port in the Node Manager Listen Port field.
Repeat these steps to add more machines, if required.

Note:

If you are extending an existing domain, you can assign servers to any existing machine. It is not necessary to create a new machine unless your situation requires it.

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

Assigning Servers to Oracle Managed File Transfer Machines

Use the Assign Servers to Machines screen to assign the Administration Server and Managed Servers to the new machine you just created.

On the Assign Servers to Machines screen:

In the Machines pane, select the machine to which you want to assign the servers; in this case, mft_machine1.
In the Servers pane, assign AdminServer to mft_machine1 by doing one of the following:
- Click once on AdminServer to select it, then click the right arrow to move it beneath the selected machine (mft_machine1) in the Machines pane.
- Double-click on AdminServer to move it beneath the selected machine (mft_machine1) in the Machines pane.
Repeat these steps to assign all Managed Servers to their respective machines.

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

Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen shows detailed configuration information for the domain you are about to create.

Review each item on the screen and verify that the information is correct. To make any changes, go back to a screen by clicking the Back button or selecting the screen in the navigation pane. Domain creation does not start until you click Create.

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

Writing Down Your Domain Home and Administration Server URL

The End of Configuration screen shows information about the domain you just configured.

Make a note of the following items because you need them later:

Domain Location
Administration Server URL

You need the domain location to access scripts that start Node Manager and Administration Server, and you need the URL to access the Administration Server.

Click Finish to dismiss the Configuration Wizard.

Starting the Servers

After configuration is complete, start Node Manager, then the WebLogic Administration Server and Managed Servers.

Note:

Depending on your existing security settings, you may need to perform additional configuration before you can manage a domain with secured production mode enabled. For more information, see Connecting to the Administration Server using WebLogic Remote Console

Windows Users Must Modify the setDomainEnv.cmd Before Starting Servers

Before starting the servers, Windows operating system users will need to modify the setDomainEnv.cmd file.

Add the following parameters:

-Dweblogic.security.SSL.trustedCAKeyStore=C:\myfiles\install\14120\wlserver\server\lib\trust.p12
        -Djavax.net.ssl.trustStore=C:\myfiles\install\14120\wlserver\server\lib\trust.p12
        -Djavax.net.ssl.trustStorePassword=trustKeyStorePassword

Remove Demotrust.jks entry from the EXTRA_JAVA_PROPERTIES section of setDomainEnv.cmd.
Save the file.

For more information on additional tools you can use to manage your domain, see Overview of Oracle Fusion Middleware Administration Tools in Administering Oracle Fusion Middleware.

For more information about Domain Mode, see Understand How Domain Mode Affects the Default Security Configuration.

Starting Node Manager

To start the per-domain Node Manager:

- (UNIX) Go to the DOMAIN_HOME/bin directory.
- (Windows) Go to the DOMAIN_HOME\bin directory.
Enter the following command:
- (UNIX) Using nohup and nm.out as an example output file:
```
nohup ./startNodeManager.sh > LOG_DIR/nm.out&
```
  where LOG_DIR is the location of directory in which you want to store the log files.
- (Windows) startNodeManager.cmd
  
  Note:
  
  On Windows operating systems, Oracle recommends that you configure Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted.
  
  See Running Node Manager as a Startup Service in Administering Node Manager for Oracle WebLogic Server.

Starting the Administration Server

The procedures in this section describe how to start the Administration Server using the WLST command line or a script. You can also use the Oracle Fusion Middleware Control and the Oracle WebLogic Server Remote Console. See Starting and Stopping Administration and Managed Servers and Node Manager in Administering Oracle Fusion Middleware.

To start the Administration Server:

Note:

When using secured production mode, you must provide additional parameters to start the Administration Server. See Connecting to the Administration Server using WLST in Administering Security for Oracle WebLogic Server.

(Optional) When using Production Mode, you can create a boot.properties file before starting the Administration Server and provide necessary permissions. This file can be created to bypass the need to provide a username and password when starting the Administration Server. For more information, see Creating a Boot Identity File for an Administration Server in Administering Server Startup and Shutdown for Oracle WebLogic Server.
Go to the DOMAIN_HOME/bin directory.
Enter the following command:
- (UNIX)
  ./startWebLogic.sh
- (Windows)
  startWebLogic.cmd
If you selected Production Mode on the Domain Mode and JDK screen when you created the domain, and you did not create the optional boot.propeties file, you see a prompt for the Administrator user login credentials as provided on the Administrator Account screen.
Open a browser and verify that the Administration Server is up and running. The default port values will vary depening on how you conifigured your domain. The Enable SSL Listen Port is enabled by default, but the default values may change. For a list of default values, see Port Numbers by Product and Component.
```
https://<Host_Name>:<port>
```
Verify that all servers in the domain have unique port values. From the WebLogic Remote Console, you can review the Local Administration Port Override fields for each managed server and verify that each has a unique value. If one or more ports is using the same value, then you must change them before starting the managed servers. For more information about changing port values, see Connect to an Administration Server in the Oracle WebLogic Remote Console.

Note:

The WebLogic Server Administration Console has been removed. For comparable functionality, you should use the WebLogic Remote Console. For more information, see Oracle WebLogic Remote Console.

Starting the Managed Servers

Starting SOA Managed Servers Using Secure Product Mode

To start the SOA Managed Servers in secure production mode, you will need to add the following parameters:

-Djavax.net.ssl.trustStore=/u01/oracle/config/keystores/soahost1/trust.p12
-Djavax.net.ssl.trustStorePassword=<your_password>

SOA Managed Servers require the Keystores: Custom Identity Key Store Pass Phrase and the Custom Trust Key Store Pass Phrase, and the SSL Server Private Key Pass Phrase to be configured before starting the server. For detailed information, see Configuring Keystores.

You can use the WebLogic Remote Console to add the required pass phrases to the SOA Managed Server:

In Edit Tree, navigate to the newly created SOA Managed server. For example, WLS_SOA1.
In the General tab, update and specify a unique number in the Local Administration Port Override field. Ensure that all the managed servers in the domain on the same machine have unique administration port values (>=1024).
Click Save.
A message confirms that the changes are added to the shopping cart.
Navigate to the Security tab, and then select Keystores.
In the Keystores tab, specify the Custom Identity Key Store Pass Phrase and Custom Trust Key Store Pass Phrase.
Click Save.
A message confirms that the changes are added to the shopping cart.
Navigate to the SSL tab and specify the Server Private Key Pass Phrase.
Click Save.
A message confirms that the changes are added to the shopping cart.
Navigate to the Shopping Cart in the top-right corner of the WebLogic Remote Console window and click Commit Changes.
Start the managed server. Once the pass phrases have been configured, add the following parameters to the command line:
Sample Command:
```
cd /domains/base_domain_1/bin
./startManagedWebLogic.sh soa_server1 https://host:<port> -Djavax.net.ssl.trustStore=/u01/oracle/config/keystores/soahost1/trust.p12 -Djavax.net.ssl.trustStorePassword=<your_password>
```

To start a WebLogic Managed Server that is not set to secure product mode, you can use the startManagedWebLogic script:

(UNIX) NEW_DOMAIN_HOME/bin/startManagedWebLogic.sh managed_server_name
(Windows) NEW_DOMAIN_HOME\bin\startManagedWebLogic.cmd managed_server_name

Note:

When using secured production mode, you must provide additional parameters to start the Managed Servers. See Starting Managed Servers using a Start Script in Administering Security for Oracle WebLogic Server.

Verifying the Configuration

After completing all configuration steps, you can perform additional steps to verify that your domain is properly configured.

To verify that the domain is configured properly, see Performing Additional Domain Configuration Tasks.

Creating a Silent Domain in MFT

Perform the following steps to create a silent domain using a sample script.

Copy the following sample script (silent_domain_creation_mft.py) into the Linux system where you want to create the domain.

import os
import sys

import com.oracle.cie.domain.script.jython.WLSTException as WLSTException

class MFT12213Provisioner:

# In this sample script, only one machine is used for all servers.
# You can add more than one machine. For example, mft_server1 - machine1, mft_server2 - machine2

    MACHINES = {
        'machine1' : {
            'NMType': 'SSL',
            'ListenAddress': '127.0.0.1',
            'ListenPort': 5658
        }
    }

    CLUSTERS = {
        'mft_cluster' : {}
    }

    SERVERS = {
        'AdminServer' : {
            'ListenAddress': '127.0.0.1',
            'ListenPort': 7001,
            'Machine': 'machine1'
        },
        'mft_server1' : {
            'ListenAddress': '127.0.0.1',
            'ListenPort': 7003,
            'Machine': 'machine1',
            'Cluster': 'mft_cluster'
        },
        'mft_server2' : {
            'ListenAddress': '127.0.0.1',
            'ListenPort': 7004,
            'Machine': 'machine1',
            'Cluster': 'mft_cluster'
        }
    }

    JRF_12213_TEMPLATES = {
        'baseTemplate' : '@@ORACLE_HOME@@/wlserver/common/templates/wls/wls.jar',
        'extensionTemplates' : [
            '@@ORACLE_HOME@@/oracle_common/common/templates/wls/oracle.jrf_template.jar',
            '@@ORACLE_HOME@@/oracle_common/common/templates/wls/oracle.jrf.ws.async_template.jar',
            '@@ORACLE_HOME@@/oracle_common/common/templates/wls/oracle.wsmpm_template.jar',
            '@@ORACLE_HOME@@/oracle_common/common/templates/wls/oracle.ums_template.jar',
            '@@ORACLE_HOME@@/em/common/templates/wls/oracle.em_wls_template.jar'
        ],
        'serverGroupsToTarget' : [ 'JRF-MAN-SVR', 'WSMPM-MAN-SVR' ]
    }

    MFT_12213_TEMPLATES = {
        'extensionTemplates' : [
            '@@ORACLE_HOME@@/mft/common/templates/wls/oracle.mft_template.jar'
        ],
        'serverGroupsToTarget' : [ 'MFT-MGD-SVRS-ONLY' ]
    }

    def __init__(self, oracleHome, javaHome, domainParentDir):
        self.oracleHome = self.validateDirectory(oracleHome)
        self.javaHome = self.validateDirectory(javaHome)
        self.domainParentDir = self.validateDirectory(domainParentDir, create=True)
        return

    def createMftDomain(self, name, user, password, db, dbPrefix, dbPassword):
        domainHome = self.createBaseDomain(name, user, password)
        self.extendDomain(domainHome, db, dbPrefix, dbPassword)


    def createBaseDomain(self, name, user, password):
        baseTemplate = self.replaceTokens(self.JRF_12213_TEMPLATES['baseTemplate'])

        readTemplate(baseTemplate)
        setOption('DomainName', name)
        setOption('JavaHome', self.javaHome)
        setOption('ServerStartMode', 'prod')
        set('Name', domainName)
        cd('/Security/' + domainName + '/User/username')
        set('Name', user)
        set('Password', password)

        print 'Creating cluster...'
        for cluster in self.CLUSTERS:
            cd('/')
            create(cluster, 'Cluster')
            cd('Cluster/' + cluster)
            for param in  self.CLUSTERS[cluster]:
                set(param, self.CLUSTERS[cluster][param])

        print 'Creating Node Managers...'
        for machine in self.MACHINES:
            cd('/')
            create(machine, 'Machine')
            cd('Machine/' + machine)
            create(machine, 'NodeManager')
            cd('NodeManager/' + machine)
            for param in self.MACHINES[machine]:
                set(param, self.MACHINES[machine][param])

        print 'Creating Servers...'
        for server in self.SERVERS:
            cd('/')
            if server == 'AdminServer':
            	cd('Server/' + server)
            	for param in self.SERVERS[server]:
            		set(param, self.SERVERS[server][param])
                continue
            create(server, 'Server')
            cd('Server/' + server)
            for param in self.SERVERS[server]:
                set(param, self.SERVERS[server][param])

        setOption('OverwriteDomain', 'true')
        domainHome = self.domainParentDir + '/' + name

        print 'Writing base domain...'
        writeDomain(domainHome)
        closeTemplate()
        print 'Base domain created at ' + domainHome
        return domainHome


    def extendDomain(self, domainHome, db, dbPrefix, dbPassword):
        print 'Extending domain at ' + domainHome
        readDomain(domainHome)
        setOption('AppDir', self.domainParentDir + '/applications')

        print 'Applying JRF templates...'
        for extensionTemplate in self.JRF_12213_TEMPLATES['extensionTemplates']:
            addTemplate(self.replaceTokens(extensionTemplate))

        print 'Applying MFT templates...'
        for extensionTemplate in self.MFT_12213_TEMPLATES['extensionTemplates']:
            addTemplate(self.replaceTokens(extensionTemplate))

        print 'Extension Templates added'

        print 'Configuring the Service Table DataSource...'
        fmwDb = 'jdbc:oracle:thin:@' + db
        cd('/JDBCSystemResource/LocalSvcTblDataSource/JdbcResource/LocalSvcTblDataSource')
        cd('JDBCDriverParams/NO_NAME_0')
        set('DriverName', 'oracle.jdbc.OracleDriver')
        set('URL', fmwDb)
        set('PasswordEncrypted', dbPassword)

        stbUser = dbPrefix + '_STB'
        cd('Properties/NO_NAME_0/Property/user')
        set('Value', stbUser)

        print 'Getting Database Defaults...'
        getDatabaseDefaults()

        print 'Targeting Server Groups...'
        serverGroupsToTarget = list(self.JRF_12213_TEMPLATES['serverGroupsToTarget'])
        serverGroupsToTarget.extend(self.MFT_12213_TEMPLATES['serverGroupsToTarget'])
        cd('/')
        for server in self.SERVERS:
            if not server == 'AdminServer':
                setServerGroups(server, serverGroupsToTarget)
                print "Set CoherenceClusterSystemResource to defaultCoherenceCluster for server:" + server
                cd('/Servers/' + server)
                set('CoherenceClusterSystemResource', 'defaultCoherenceCluster')

        cd('/')
        for cluster in self.CLUSTERS:
            print "Set CoherenceClusterSystemResource to defaultCoherenceCluster for cluster:" + cluster
            cd('/Cluster/' + cluster)
            set('CoherenceClusterSystemResource', 'defaultCoherenceCluster')
        
        print "Set WLS clusters as target of defaultCoherenceCluster:[" + ",".join(self.CLUSTERS) + "]"
        cd('/CoherenceClusterSystemResource/defaultCoherenceCluster')
        set('Target', ",".join(self.CLUSTERS))
		 
        print 'Preparing to update domain...'
        updateDomain()
        print 'Domain updated successfully'
        closeDomain()
        return


    ###########################################################################
    # Helper Methods                                                          #
    ###########################################################################

    def validateDirectory(self, dirName, create=False):
        directory = os.path.realpath(dirName)
        if not os.path.exists(directory):
            if create:
                os.makedirs(directory)
            else:
                message = 'Directory ' + directory + ' does not exist'
                raise WLSTException(message)
        elif not os.path.isdir(directory):
            message = 'Directory ' + directory + ' is not a directory'
            raise WLSTException(message)
        return self.fixupPath(directory)


    def fixupPath(self, path):
        result = path
        if path is not None:
            result = path.replace('\\', '/')
        return result


    def replaceTokens(self, path):
        result = path
        if path is not None:
            result = path.replace('@@ORACLE_HOME@@', oracleHome)
        return result


#############################
# Entry point to the script #
#############################

def usage():
    print sys.argv[0] + ' -oh <oracle_home> -jh <java_home> -parent <domain_parent_dir> [-name <domain-name>] ' + \
          '[-user <domain-user>] [-password <domain-password>] ' + \
          '-rcuDb <rcu-database> [-rcuPrefix <rcu-prefix>] [-rcuSchemaPwd <rcu-schema-password>]'
    sys.exit(0)


print str(sys.argv[0]) + " called with the following sys.argv array:"
for index, arg in enumerate(sys.argv):
    print "sys.argv[" + str(index) + "] = " + str(sys.argv[index])

if len(sys.argv) < 6:
    usage()

#oracleHome will be passed by command line parameter -oh.
oracleHome = None
#javaHome will be passed by command line parameter -jh.
javaHome = None
#domainParentDir will be passed by command line parameter -parent.
domainParentDir = None
#domainName is hard-coded to mft_domain. You can change to other name of your choice. Command line parameter -name.
domainName = 'mft_domain'
#domainUser is hard-coded to username. You can change to other name of your choice. Command line paramter -user.
domainUser = 'username'
#domainPassword is hard-coded to password. You can change to other password of your choice. Command line parameter -password.
domainPassword = 'password'
#rcuDb will be passed by command line parameter -rcuDb.
rcuDb = None
#change rcuSchemaPrefix to your soainfra schema prefix. Command line parameter -rcuPrefix.
rcuSchemaPrefix = 'DEV12'
#change rcuSchemaPassword to your soainfra schema password. Command line parameter -rcuSchemaPwd.
rcuSchemaPassword = 'password'

i = 1
while i < len(sys.argv):
    if sys.argv[i] == '-oh':
        oracleHome = sys.argv[i + 1]
        i += 2
    elif sys.argv[i] == '-jh':
        javaHome = sys.argv[i + 1]
        i += 2
    elif sys.argv[i] == '-parent':
        domainParentDir = sys.argv[i + 1]
        i += 2
    elif sys.argv[i] == '-name':
        domainName = sys.argv[i + 1]
        i += 2
    elif sys.argv[i] == '-user':
        domainUser = sys.argv[i + 1]
        i += 2
    elif sys.argv[i] == '-password':
        domainPassword = sys.argv[i + 1]
        i += 2
    elif sys.argv[i] == '-rcuDb':
        rcuDb = sys.argv[i + 1]
        i += 2
    elif sys.argv[i] == '-rcuPrefix':
        rcuSchemaPrefix = sys.argv[i + 1]
        i += 2
    elif sys.argv[i] == '-rcuSchemaPwd':
        rcuSchemaPassword = sys.argv[i + 1]
        i += 2
    else:
        print 'Unexpected argument switch at position ' + str(i) + ': ' + str(sys.argv[i])
        usage()
        sys.exit(1)

provisioner = MFT12213Provisioner(oracleHome, javaHome, domainParentDir)
provisioner.createMftDomain(domainName, domainUser, domainPassword, rcuDb, rcuSchemaPrefix, rcuSchemaPassword)

Open the script and change the following values:
1. ListenAdress: This is the IP address of the machine where the MFT domain should be created.
2. Prefix of RCU schema: This is hardcoded to DEV12, change this value to the specific prefix. For example, if the name of the RCU schema is SAMPLE_SOAINFRA, then the value of rcuSchemaPrefix is SAMPLE.
3. RCU schema password: This is hard coded to password. Change this value to the schema specific password.
Go to FMW_HOME/oracle_common/common/bin/
Type ./wlst.sh <script_location>/silent_domain_creation_mft.py -oh "<FMW_HOME location>" -jh "<JAVA_HOME location>" -parent "<new domain creation location>" -rcuDb "<hostname of your linux box>:<port>/<service id>"
The following is an example of the command with the required parameters:
```
Type cd $MW_HOME/oracle_common/common/bin
Type ./wlst.sh <script_name with absolute path> -oh "<oracle middleware home>" -jh  "<java home>" -parent "<domain parent directory with absolute path>" -name  "<domain_name>" -user "<domain user>" -password "domain password" -rcuDb  "<hostname>:<port>/<service>" -rcuPrefix "<soa_infra schema prefix>"  -rcuSchemaPwd "<soainfra schema password>"
```
- -oh — Middleware home path. Default is none, set a value.
- -jh — Java home path. Default is none, set a value.
- -parent — domain parent directory name with absolute path. Default is none, set a value.
- (Optional) -name — domain name. Default is soa_domain. If value is not set, default value will be used.
- (Optional) -user — domain user. Default is username. If value is not set, default value will be used.
- (Optional) -password — domain password. Default is password. If value is not set, default value will be used..
- -rcuDb — RCU database details. Default is none, set a value.
- -rcuPrefix — soainfra schema prefix. Default is DEV12. Check your soainfra prefix and set this value accordingly.
- -rcuSchemaPwd —soainfra schema password. Default is password. Check your soainfra schema password and set this value accordingly.