Creating boot.properties for the Administration Server and Managed Servers on APPHOST2 Starting Node Manager on APPHOST2 Configuring the ADF Application for Replication

6-26 Oracle Fusion Middleware High Availability Guide -domain=ORACLE_BASEproductfmwuser_projectsdomainsadfdomain -template=adfdomaintemplate.jar

6.2.9.1 Creating boot.properties for the Administration Server and Managed Servers on APPHOST2

Create a boot.properties file for the Administration Server and for the Managed Servers on APPHOST2 by following these steps: 1. Create the following directories: APPHOST1 mkdir -p MW_HOMEwlsuser_projectsdomainsadfdomainserversWLS_ADF2 APPHOST2 mkdir -p MW_HOMEwlsuser_projectsdomainsadfdomainserversWLS_ ADF2security 2. Use a text editor to create a file named boot.properties in the directory created in the previous step, and enter the following lines in the file: username=adminUser password=adminUserPassword For example: username=weblogic password=weblogic

6.2.9.2 Starting Node Manager on APPHOST2

To start the Node Manager on APPHOST2, repeat the steps from Section 6.2.7.4, Starting Node Manager on APPHOST1 on APPHOST2.

6.2.9.3 Configuring the ADF Application for Replication

Use the procedures in this section to configure your application for replication. Clustering Requirement The application must be deployed to an Oracle WebLogic Cluster. This automatically establishes a replication channel for the multiple instances of the application. Oracle ADF Replication It is essential that Oracle ADF is configured properly. The following tag should be present in the adf-config.xml file, one of the Application Resources, for a stateful application: Note: When you start the Administration Server or Managed Server, the username and password entries in the file are encrypted. For security reasons, minimize the time the entries in the file are left unencrypted. After you edit the file, start the server as soon as possible in order for the entries to be encrypted. Note: In a Unicast cluster, the default replication channel is configured using the Listen address of each managed server. Therefore, the Listen address should be configured to be a specific IP address or host name, instead of being configured to listen on Any. Configuring High Availability for Oracle ADF and WebCenter Applications 6-27 adfc:adf-controller-configadfc:adf-scope-ha-supporttrueadfc:adf-scope-ha-sup portadfc:adf-controller-config Applications must also have replication enabled. Oracle WebLogic Server allows several types of persistent stores for replication. For more information on persistent stores, see the Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server manual. The ADF application can be enabled by for this by default with the following setting in the weblogic.xml file: session-descriptor persistent-store-typereplicated_if_clusteredpersistent-store-type session-descriptor The replicated_if_clustered setting disables replication for standalone application environments, and uses in-memory replication within a cluster environment. Ensure that any custom application is configured for in-memory replication.

6.2.9.4 Deploying the ADF Application