Review these topics for the various topologies with the directory servers and replication servers either installed on the same host or different hosts.

Various topologies are possible as explained in the following topics:

• About Topology with the Replication Servers and Directory Servers on the Same Host.

• Upgrading a Topology with the Replication Servers and Directory Servers on the Same Host

• About Topology with Replication Servers and Directory Servers on Different Hosts.

• Upgrading a Topology wIth Replication Servers and Directory Servers on Different Hosts

In a topology that does not include any proxy server instances, you must update your client applications so that they point to an alternative directory server each time you take a directory server down for an update.

The following diagram shows a replicated topology that does not include a proxy server. This topology assumes that the directory servers and replication servers are installed on the same ORACLE_HOME directory.

In this diagram, Group 1 and Group 2 refer to configured replication groups. See About Replication Groups in Administering Oracle Unified Directory.

Figure 6-3 Replicated Oracle Unified Directory Topology Without Proxy Servers

To update a topology that does not include a proxy server:

1. Change your client application configuration so that applications do not access directory server A directly.
2. Stop directory server A. The replication server on this host is stopped and updated at the same time.
3. Update directory server A, following the steps in Upgrading an Existing Oracle Unified Directory Server Instance.
4. Restart directory server A.
5. Test that your directory service is working properly before upgrading successive servers.
6. Change your client application configuration so that applications do not access directory server B directly.
7. Stop directory server B.
8. Update directory server B, following the steps in Upgrading an Existing Oracle Unified Directory Server Instance.
9. Follow steps 1-8 for each replication group in the topology.

The version of Oracle Unified Directory Services Manager (OUDSM) described in this guide is 12c (12.2.1.3.0). When you update the Oracle Unified Directory software to 12c (12.2.1.3.0), OUDSM is also updated to this same release.

Oracle Unified Directory Services Manager stores only the directory instance connection details and administrator configurations. The 12c (12.2.1.3.0) upgrade using the Fusion Middleware Reconfiguration Wizard does not support migration of Oracle Platform Security Services (OPSS) to a file-based store. You will not be able to migrate those stored OUDSM configurations from 11g OUDSM domain instance to 12c. You will have to manually add or copy those configurations in the newly created 12c OUDSM domain instances.

1. Install the collocated 12c (12.2.1.3.0) Oracle Unified Directory before upgrading your existing Oracle Unified Directory Services Manager 11g (11.1.2.2.0 or 11.1.2.3.0).

   See Installing the OUD/OUDSM Software.

2. Backup your existing environment.
3. Create a new domain in 12c using the WebLogic Scripting Tool.

   See Creating a Domain for OUDSM Using the WebLogic Scripting Tool.

4. Copy the connection details and administrator configurations files from 11g domain (if any) to the newly created domain in 12c.

   cp -r $11gDOMAIN_HOME/config/fmwconfig/odsm $12cDOMAIN_HOME/config/fmwconfig/

You can upgrade Oracle Unified Directory Services Manager from 11g to 12c using the Fusion Middleware Reconfiguration wizard. The valid starting points for this upgrade are 11g (11.1.2.2.0) and 11g (11.1.2.3.0).

1. Install the collocated 12c (12.2.1.3.0) Oracle Unified Directory before upgrading your existing Oracle Unified Directory Services Manager 11g (11.1.2.2.0 or 11.1.2.3.0)

   See Installing the OUD/OUDSM Software.

2. Create the required schemas before upgrade.

   If you are upgrading from Oracle Unified Directory Services Manager 11g, you must create the required 12c schemas before you begin the upgrade. The schema required for Oracle Unified Directory is Oracle Platform Security Services (OPSS). Selecting the Oracle Platform Security Services schema will automatically select the dependent schemas.

   See Creating Database Schemas for the Infrastructure Domain Using the Repository Creation Utility.

3. Create a backup of the domain directory:
   1. Shutdown the Administration Server for the ODSM 11g Domain:
      To stop the Administration Server, use the stopWebLogic script:

      • (UNIX) EXISTING_DOMAIN_HOME/bin/stopWebLogic.sh
      • (Windows) EXISTING_DOMAIN_HOME\bin\stopWebLogic.cmd

      When prompted, enter your user name, password, and the URL of the Administration Server.
   2. Copy the source domain to a separate location to preserve the contents.

      (Windows) copy C:\domains\myoudsmdomain to C:\domains\myoudsmdomain_backup

      (UNIX) cp -rf myoudsmdomain /domains/myoudsmdomain_backup

   3. Verify that the backed up versions of the domain are complete.
   If domain reconfiguration fails for any reason, you must copy all files and directories from the backup directory into the original domain directory to ensure that the domain is returned entirely to its original state before reconfiguration.
4. Run the Reconfiguration Wizard by entering the following command:

   On UNIX and Linux systems:

   $ Oracle12cHome/oracle_common/common/bin/reconfig.sh
   

   On Windows systems:

   Oracle12cHome\oracle_common\common\bin\reconfig.cmd

5. Use the Select Domain screen to specify the location of the domain you want to upgrade or click Browse to navigate and select the domain directory. Click Next.
6. The Reconfiguration Setup Progress screen shows the progress of the setup process. When complete, click Next.

   During this process:

   • The reconfiguration templates for your installed products, including Fusion Middleware products, are automatically applied. This updates various domain configuration files such as config.xml, config-groups.xml, and security.xml (among others).

   • Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

   • The domain upgrade is validated.

7. On the Reconfig Summary screen, review the detailed information of the various reconfigured templates. Click Next.
8. On the Domain Mode and JDK screen, select the JDK to use in the domain or click Browse to navigate to the JDK you want to use. Click Next.

   Note:

   You cannot change the Domain Mode at this stage.

9. On the Database Configuration Type screen, select RCU Data to connect to the Server Table (_STB) schema.

   Enter the database connection details using the RCU service table (_STB) schema credentials and click Get RCU Configuration.

   The Reconfiguration Wizard uses this connection to automatically configure the data sources required for components in your domain.

   Note:

   For new datasources where the schema was created for 12c by the RCU, the default connection data will be retrieved from the _STB schema. If no connection data for a given schema is found in the _STB schema, then the default connection data is used.

   If the check is successful, click Next. If the check fails, reenter the connection details correctly and try again.

10. On the JDBC Component Schema screen, verify that the DBMS/Service and the Host name is correct for each component schema and click Next.
11. On the JDBC Component Schema Test screen, select all the component schemas and click Test Selected Connections to test the connection for each schema. The result of the test is indicated in the Status column.

    When the check is complete, click Next.

12. The Node Manager screen is only displayed if the domain you are reconfiguring is currently using a per host Node Manager.

    On the Node Manager screen, select the Node Manager configuration to use for the reconfigured domain. The resulting configuration depends on the combination of options you select for Node Manager Type and Node Manager Configuration.

    Table 6-1 Field Descriptions for Node Manager Screen

    Option	Description
    Per Domain Default Location	If you select this option, the Node Manager home is redefined to DOMAIN_NAME/nodemanager and you cannot edit the Node Manager home.
    Per Domain Custom Location	Select this option if you want the per domain Node Manager configuration files to be created in a specific location for this domain. Specify the directory in the Node Manager Home field, or click Browse to use the navigation tree to select the location. The specified directory must be empty. The nodemanager.properties and nodemanager.domains files are created in this directory.
    Node Manager Home	If you selected the Per Domain Custom Location option, click Browse to navigate to the directory location that you want to use to store the per domain Node Manager configuration.
    Manual Node Manager Setup	If you select this option, creation of the Node Manager configuration for the domain is skipped (all remaining fields cannot be modified), and to use Node Manager in the domain, you must manually configure Node Manager as described in Completing the Node Manager Configuration. The reconfigured domain will still use a per host Node Manager configuration. You should also select this option if your existing domain is not configured to use Node Manager and you do not want to use Node Manager in the reconfigured domain. For more information about Node Manager configuration, see Administering Node Manager for Oracle WebLogic Server.
    Node Manager Configuration	Select one of the following two options. These fields are not available if you selected Manual Node Manager Setup.
    Create New Configuration	A per domain Node Manager configuration will be automatically created for the reconfigured domain using default settings in nodemanager.properties. If necessary, you can modify nodemanager.properties after the domain has been successfully reconfigured.
    Migrate Existing Configuration	The existing per host Node Manager configuration will be migrated to a per domain configuration for the reconfigured domain. This does not include environment-specific settings for ListenAddress, ListenPort, StartScriptName, JavaHome, and LogFile.
    Node Manager Home	If you selected the Migrate Existing Configuration option, enter or browse to the Node Manager home directory that you want to migrate to the reconfigured domain.
    Apply Oracle Recommended Defaults	If you selected the Migrate Existing Configuration option, select this check box to use Oracle-recommended defaults in the nodemanager.properties file. Deselect this check box to continue using the settings in the nodemanager.properties file being migrated. Oracle-recommended properties with default values are as follows: LogLimit=0 AuthenticationEnabled=true LogLevel=INFO DomainsFileEnabled=true NativeVersionEnabled=true LogToStderr=true SecureListener=true LogCount=1 StopScriptEnabled=false QuitEnabled=false LogAppend=true StateCheckInterval=500 CrashRecoveryEnabled=false StartScriptEnabled=true LogFormatter=weblogic.nodemanager.server.LogFormatter ListenBacklog=50
    Node Manager Credentials: Username, Password	Specify the username and password that you want to use to start Node Manager in the reconfigured domain.

13. On the Advanced Configuration screen, you can select all categories 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.

    Note:

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

    For this upgrade, select none of the options and click Next.

14. On the Configuration Summary screen, review the detailed configuration settings of the domain before continuing.

    You can limit the items that are displayed in the right-most panel by selecting a filter option from the View drop-down list.

    To change the configuration, click Back to return to the appropriate screen. To reconfigure the domain, click Reconfig.

    Note:

    The location of the domain does not change when you reconfigure it.

15. The Reconfiguration Progress screen displays the progress of the reconfiguration process.

    During this process:

    • Domain information is extracted, saved, and updated.

    • Schemas, scripts, and other such files that support your Fusion Middleware products are updated.

    When the progress bar shows 100%, click Next.

16. The End of Configuration screen indicates whether the reconfiguration process completed successfully or failed. It also displays the location of the domain that was reconfigured and the Administration Server URL (including the listen port). If the reconfiguration is successful, it displays Oracle WebLogic Server Reconfiguration Succeeded.

    If the reconfiguration process did not complete successfully, an error message is displayed indicates the reason. Take appropriate action to resolve the issue. If you cannot resolve the issue, contact My Oracle Support.

    Note the Domain Location and the Admin Server URL for further operations.

Oracle Unified Directory Services Manager 12c (12.2.1.3.0) is compatible with Oracle WebLogic Server 12c (12.2.1.3.0).

Oracle Unified Directory Services Manager 12c (12.2.1.3.0) is compatible with Oracle Application Development Framework 12c (12.2.1.3.0).