Click Next.

If you are unsure of the service name for your database, you can obtain it from the SERVICE_NAMES parameter in the initialization parameter file of the database. If the initialization parameter file does not contain the SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the DB_NAME and DB_DOMAIN parameters.

For an Autonomous Transaction Processing-Dedicated (ATP-D) database, you must use only one of the database service names, <databasename>_tpurgent or <databasename>_tp, specified in tnsnames.ora.

To create schemas on an Autonomous Transaction Processing database (both Autonomous Transaction Processing-Dedicated (ATP-D) and Autonomous Transaction Processing-Dedicated (ATP-D)), you can specify the connection credentials using only the Connection String option. In this screen, a warning message is displayed. You can ignore the warning and continue with the schema creation. For more information, see SYS DBA Privileges Warning After Applying Patches.

To provide the database connection details:

Select Create new prefix, specify a custom prefix, then select the Oracle Internet Directory schema. This action automatically selects the following schemas as dependencies:

• Common Infrastructure Service (STB)

If you are configuring Oracle Internet Directory in a collocated mode, the following dependant schemas are selected:

• Oracle Platform Security Services (OPSS)

• Audit Services (IAU)

• Audit Services Append (IAU_Append)

• Audit Services Viewer (IAU_Viewer)

• WebLogic Services (WLS)

• Common Infrastructure Service (STB)

The schema Common Infrastructure Services is automatically created. This schema is dimmed; you cannot select or deselect it. This schema enables you to retrieve information from RCU during domain configuration. For more information, see Understanding 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. Schema sharing across domains is not supported.

Click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.

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.

For an Autonomous Transaction Processing-Dedicated (ATP-D) database, in the Map Tablespaces screen you must override the default tablespaces and the temporary tablespaces, and also override the additional tablespaces, if applicable. See Map Tablespaces.

When you reach the Completion Summary screen, click Close to dismiss the RCU.

To specify the Domain type and Domain home directory:

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

• Oracle Internet Directory (Standalone) - [oid]

For collocated mode, select the following templates:

• Oracle Internet Directory (Collocated) - [oid]

  Selecting this template automatically selects the following as dependencies:

  • Oracle Directory Services Manager - [oid]

  • Oracle JRF - [oracle_common]

  • WebLogic Coherence Cluster Extension - [wlserver]

  • Oracle Enterprise Manager - [em]

• Oracle Directory Integration Platform - [dip]

  Optional. Select this template if you're using OID and ODIP in the same domain.

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

On the Domain Mode and JDK screen:

• Select Production in the Domain Mode field.

• Disable secured mode for the domain by selecting the Disable Secure Mode check-box.

• Select the Oracle HotSpot JDK in the JDK field.

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.

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

For an Autonomous Transaction Processing database (both Autonomous Transaction Processing-Dedicated (ATP-D) and Autonomous Transaction Processing-Dedicated (ATP-D)), specify the connection credentials using only the Connection URL String option and enter the connect string in the following format:

jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=/<$ORACLE_HOME>/network/admin

In the connect string, you must pass TNS_alias as the database name found in tnsnames.ora, and TNS_ADMIN property to <$ORACLE_HOME>/network/admin, which is the location of the wallet files, ojdbc.properties, and tnsnames.ora.

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

jdbc:oracle:thin:@dbname_medium?TNS_ADMIN=/users/test/network/admin

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

jdbc:oracle:thin:@dbname_tp?TNS_ADMIN=/users/test/network/admin

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 .

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.

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 the Connection URL String option only, and enter the connect string specified in tnsnames.ora that is present in /<$ORACLE_HOME>/network/admin, which is the location of the wallet files, for your service name or TNS_alias.

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

jdbc:oracle:thin:@(DESCRIPTION=(CONNECT_TIMEOUT=120)(RETRY_COUNT=20)(RETRY_DELAY=3)
(TRANSPORT_CONNECT_TIMEOUT=3)(ADDRESS_LIST=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=<protocol_name>)
(HOST=<host_name>)(PORT=<port_number>)))(CONNECT_DATA=(SERVICE_NAME=<service_name>.atp.oraclecloud.com)))

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

jdbc:oracle:thin:@(DESCRIPTION=(CONNECT_TIMEOUT=120)=(RETRY_COUNT=20)(RETRY_DELAY=3)(ADDRESS=(PROTOCOL=<protocol_name>)
(PORT=<port_number>)(HOST=<host_name>))(CONNECT_DATA=(SERVICE_NAME=<service_name>.adb.oraclecloud.com))
(security=(ssl_server_cert_dn="CN=example.com, 
OU=<organizational_unit>, O=<organization>, L=<city>, ST=<state>, C=<country>")))

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

• Configuring Active GridLink Data Sources with Oracle RAC

• Configuring Multi Data Sources

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

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.

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

  Select Topology to configure machines and assign the Administration Server to a machine. Note that you cannot configure the oid system component using the Configuration Wizard. The oid instance is configured after the domain configuration. See Performing the Initial Oracle Internet Directory Setup.

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.

1. Provide a name for the Administration Server. The name field must not be null or empty and cannot contain any special characters.
2. 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.
3. 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.

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.

If you do not plan to create a WebLogic managed server during installation, click Next and proceed. A WebLogic managed server is not required for OID and Oracle Directory Services Manager (ODSM) gets deployed on the administration server.

If you plan to create a WebLogic managed server during installation, ensure that you associate the Server Groups to the managed server. This step deploys the ODSM/oiddms on the administration server.

If you do not select any server groups for the managed server and ODSM/oiddms are deployed on the managed server, then use the Administration Server Console to remove oiddms from the managed sever and deploy them on the administration server.

Click Next.

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.

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

On the Assign Servers to Machines screen:

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.

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.