7 Setting Up Node Manager for an Enterprise Deployment

This chapter describes how to configure Node Manager in accordance with enterprise deployment recommendations.

This chapter includes the following topics:

Section 7.1, "Prerequisites for Setting Up Node Manager"
Section 7.2, "Setting Up Node Manager for CRMHOST2"
Section 7.3, "Creating the Identity Keystore on CRMHOST2"

7.1 Prerequisites for Setting Up Node Manager

Before setting up Node Manager, ensure the following:

You are starting with a clean machine, if it is the first time it is being setup
The /etc/hosts file has proper entries. To verify, ping this machine with the fully qualified name of the machine.
The user created on CRMHOST2 should be the same as the user on CRMHOST1
The directory structure /u01/oracle (ORACLE_BASE) is mounted to same shared file system as CRMHOST1
The directory structure /u02/local/oracle/config on CRMHOST2 has been created
The initial Oracle Fusion Customer Relationship Management deployment on CRMHOST1 has already been done and verified by provisioning

7.2 Setting Up Node Manager for CRMHOST2

Do the following:

Run the following command:

CRMHOST2> cd ORACLE_BASE/config/nodemanager

In the nodemanager directory, copy the content of the node-specific directory to CRMHOST2. In this case, CRMHOST1 is the node-specific directory.
```
CRMHOST2> cp -r CRMHOST1 CRMHOST2
```
Change directory to CRMHOST2. You should see the following files:
```
nm_data.properties   nodemanager.log   startNodeManagerWrapper.sh
nodemanager.domains  nodemanager.properties
```
Note:

Manually delete any lock files that may be present. For example, nodemanager.log.lck.
In the nodemanager.domains file, edit all the domain paths that are local to CRMHOST2. For example, CRMDomain=/u02/local/oracle/config/domains/CRMHOST2/CRMDomain.

Note:

Because BIDomain is a bit different, an example path would be BIDomain=/u02/local/oracle/config/domains/CRMHOST1/BIDomain.
In the startNodeManagerWrapper.sh file, change NM_HOME to ORACLE_BASE/config/nodemanager/CRMHOST2.
In the nodemanager.properties file:
- Add or modify the following lines:
```
KeyStores=CustomIdentityAndCustomTrust
CustomIdentityKeyStoreFileName=ORACLE_BASE/config/keystores/CRMHOST2_fusion_identity.jks
CustomIdentityPrivateKeyPassPhrase=keypassword
CustomIdentityAlias=CRMHOST2_fusion
```
  Note:
  
  keypassword is the password given in the ORACLE_BASE/products/provisioning/plan/provisioning.plan file.
  
  Since the passwords in the response and plan files are encrypted, take note of or save the Node Manager password you enter when creating the provisioning response file. For more information, see Section 5.3.2.5, "Installation Location Screen."
- Ensure that the path to the local machine /u02/local/oracle/nodemanager/ exists, and that the LogFile value is pointing to /u02/local/oracle/nodemanager/CRMHOST2.log.
- Ensure that the path for DomainsFile and NodeManagerHome are correct for CRMHOST2.

7.3 Creating the Identity Keystore on CRMHOST2

Provisioning has created the identity keystore CRMHOST1_fusion_identity.jks for CRMHOST1. Subsequently, the identity keystore CRMHOST2_fusion_identity.jks must be created for CRMHOST2.

Do the following to create the keystore:

Change directory to ORACLE_BASE/config/keystores.

Ensure the CRMHOST1_fusion_identity.jks and fusion_trust.jks files are present.
Back up fusion_trust.jks to fusion_trust.jks.org.
Run the following command to set the CLASSPATH:
```
CRMHOST2> source ORACLE_BASE/products/fusionapps/wlserver_10.3/server/
bin/setWLSEnv.sh
```
Ensure that the CLASSPATH has been set:
```
CRMHOST2> which keytool
```
The output should point to the ORACLE_BASE/products/fusionapps/jdk6/jre/bin/keytool.
Run the following command to create the keypair for CRMHOST2_fusion_identity.jks:
```
CRMHOST2> keytool -genkeypair -keyalg RSA -alias CRMHOST2_fusion -keypass 
keypassword -keystore CRMHOST2_fusion_identity.jks -storepass keystorepassword 
-validity 180 -dname 'CN=CRMHOST2, OU=defaultOrganizationUnit, O=defaultOrganization, C=US' 
```
where
- keystorepassword is the password given in the ORACLE_BASE/products/provisioning/plan/provisioning.plan file
- keypassword is the password given in the ORACLE_BASE/products/provisioning/plan/provisioning.plan file
Notes:
- It is recommended to keep the commands in a file and then execute it.
- Since the passwords in the response and plan files are encrypted, take note of or save the Node Manager password you enter when creating the provisioning response file. For more information, see Section 5.3.2.5, "Installation Location Screen."

Run the following command to export the certs:

CRMHOST2> keytool -exportcert -alias CRMHOST2_fusion 
-keystore CRMHOST2_fusion_identity.jks  
-storepass keystorepassword -rfc -file /tmp/appIdentityKeyStore.jks

Note:

If the alias CRMHOST2_fusion exists, run this command to delete it:

keytool -delete -alias CRMHOST2_fusion -keystore fusion_trust.jks 
-storepass keystorepassword

The following command will display the certificates in the trust keystore:

keytool -list -keystore fusion_trust.jks -storepass 
keystorepassword

Run the following command to import the certs:

CRMHOST2> keytool -importcert -noprompt -alias CRMHOST2_fusion -file 
/tmp/appIdentityKeyStore.jks -keystore fusion_trust.jks -storepass 
keystorepassword

Verify that the file CRMHOST2_fusion_identity.jks has been created in the directory ORACLE_BASE/config/keystores directory.

Start Node Manager on CRMHOST2 by running the following command:

ORACLE_BASE/config/nodemanager/CRMHOST2/startNodeManagerWrapper.sh &