Skip Headers
Oracle® Fusion Applications Enterprise Deployment Guide
11g Release 1 (

Part Number E16684-02
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

6 Configuring Node Manager

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

This chapter includes the following topics:

6.1 Configuring Node Manager for CRMHOST2

Do the following:

  1. Run the following command:

    CRMHOST2> cd ORACLE_BASE/products/fusionapps/wlserver_10.3/common/nodemanager
  2. In the /nodemanager directory, copy the content of the node-specific directory to CRMHOST2. In this case, CRMHOST1 is the node-specific directory.

  3. Change directory to CRMHOST2. You should see the following files:   nodemanager.log


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


    Because BIDomain is a bit different, an example path would be BIDomain=/u02/local/oracle/config/domains/CRMHOST1/BIDomain.
  5. In the file, change NM_HOME to ORACLE_BASE/products/fusionapps/wlserver_10.3/common/nodemanager/CRMHOST2.

  6. In the file:

    • 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.

    • Add or modify the following lines:



      keypassword is the password given in the provisioning plan. (Check provisioning.setup.common.core.key.password in the provisioning plan.)

6.2 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:

  1. Change directory to ORACLE_BASE/products/fusionapps/wlserver_10.3/server/lib.

    Ensure the CRMHOST1_fusion_identity.jks and fusion_trust.jks files are present.

  2. Back up fusion_trust.jks to

  3. Run the following command to set the CLASSPATH:

    CRMHOST2> ORACLE_BASE/products/fusionapps/wlserver_10.3/server/bin/

    Ensure that the CLASSPATH has been set:

    CRMHOST2> which keytool

    The output should point to the ORACLE_BASE/products/fusionapps/jdk6/jre/bin/keytool.

  4. 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' 


    • keystorepassword is the password given in the provisioning plan (check provisioning.setup.common.core.keystore.password in the provisioning plan)

    • keypassword is the password given in the provisioning plan (check provisioning.setup.common.core.key.password in the provisioning plan)


    • It is recommended to keep the commands in a file and then execute it.

    • Since the passwords in the plan are encrypted, take note of or save the passwords when you are creating the plan.

  5. 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


    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 
  6. Run the following command to import the certs:

    CRMHOST2> keytool -importcert -noprompt -alias CRMHOST2_fusion -file
    /tmp/appIdentityKeyStore.jks -keystore fusion_trust.jks -storepass 
  7. Verify that the file CRMHOST2_fusion_identity.jks has been created in the directory ORACLE_BASE/products/fusionapps/wlserver_10.3/server/lib directory.

  8. Start Node Manager on CRMHOST2 by running the following command:

    ORACLE_BASE/products/fusionapps/wlserver_10.3/common/nodemanager/CRMHOST2/ &