Skip Headers
Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence
11g Release 1 (11.1.1)

Part Number E15722-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

7 Setting Up Node Manager

This chapter describes how to configure Node Manager in accordance with the EDG recommendations.

Important:

Oracle strongly recommends that you read Oracle Fusion Middleware Release Notes for any additional installation and deployment considerations before starting the setup process.

This chapter contains the following topics:

7.1 About Setting Up Node Manager

Node Manager enables you to start and stop the Administration Server and the Managed Servers.

Process

The procedures described in this chapter must be performed for various components of the enterprise deployment topology outlined in Section 1.5, "Enterprise Deployment Reference Topology." The following variables are used in this chapter to distinguish between component-specific items:

The values to be used for these variables are provided in the component-specific chapters in this EDG. Note that the procedures in this chapter must be performed multiple times for each VIP-and-IP pair using the information provided in the component-specific chapters.

Recommendations

Oracle provides two main recommendations for Node Manager configuration in enterprise deployment topologies:

  1. Oracle recommends placing the Node Manager log file in a location different from the default one (which is inside the Middleware home where Node Manager resides). See Section 7.2, "Changing the Location of the Node Manager Log" for further details.

  2. Oracle also recommends using host name verification for the communication between Node Manager and the servers in the domain. This requires the use of certificates for the different addresses used in the domain. This chapter explains the steps for configuring certificates in the hosts for host name verification. See Section 7.3, "Enabling Host Name Verification Certificates for Node Manager" for further details.

Note:

The passwords used in this guide are provided only as examples. Use secure passwords in a production environment. For example, use passwords that consist of random sequences of both uppercase and lowercase characters as well as numbers.

7.2 Changing the Location of the Node Manager Log

Change the location of the Node Manager log by editing the nodemanager.properties file, located in the MW_HOME/wlserver_10.3/common/nodemanager directory. Add the new location for the log file using the following line:

LogFile=ORACLE_BASE/admin/nodemanager.log

Oracle recommends that this location be outside the MW_HOME directory and inside the admin directory for the EDG.

Restart Node Manager for the change to take effect.

7.3 Enabling Host Name Verification Certificates for Node Manager

Setting up host name verification certificates for communication between Node Manager and the Administration Server consists of the following steps:

7.3.1 Generating Self-Signed Certificates Using the utils.CertGen Utility

The certificates added in this chapter (as an example) address a configuration where Node Manager listens on a physical host name (HOST.mycompany.com) and a Managed Server listens on a virtual host name (VIP.mycompany.com). Whenever a Managed Server is using a virtual host name, it is implied that the Managed Server can be migrated from one node to another. Consequently, the directory where keystores and trust keystores are maintained ideally must reside on a shared storage that is accessible from the failover. If additional host names are used in the same or different nodes, the steps in this example will need to be extended to:

  • Add the required host names to the certificate stores (if they are different from HOST.mycompany.com and VIP.mycompany.com).

  • Change the identity and trust store location information for Node Manager (if the additional host names are used by Node Manager) or for the servers (if the additional host names are used by Managed Servers).

Follow these steps to create self-signed certificates on HOST. These certificates should be created using the network name or alias. For information on using trust CA certificates instead, see "Configuring Identity and Trust" in Oracle Fusion Middleware Securing Oracle WebLogic Server.

The following examples configure certificates for HOST.mycompany.com and VIP.mycompany.com; that is, it is assumed that both a physical host name (HOST) and a virtual host name (VIP) are used in HOST. It is also assumed that HOST.mycompany.com is the address used by Node Manager, and VIP.mycompany.com is the address used by a Managed Server or the Administration Server. This is the common situation for nodes hosting an Administration Server and an Oracle Fusion Middleware component, or for nodes where two Managed Servers coexist with one server listening on the physical host name and one server using a virtual host name (which is the case for servers that use migration servers).

  1. Set up your environment by running the WL_HOME/server/bin/setWLSEnv.sh script. In the Bourne shell, run the following commands:

    HOST> cd WL_HOME/server/bin
    HOST> ../setWLSEnv.sh
    

    Verify that the CLASSPATH environment variable is set:

    HOST> echo $CLASSPATH
    
  2. Create a user-defined directory for the certificates. For example, create a directory called 'certs' under the ORACLE_BASE/admin/domain_name/cluster_name directory. Note that certificates can be shared across WLS domains.

    HOST> cd ORACLE_BASE/admin/domain_name/cluster_name
    HOST> mkdir certs
    

    Note:

    The directory where keystores and trust keystores are maintained must be on shared storage that is accessible from all nodes so that when the servers fail over (manually or with server migration), the appropriate certificates can be accessed from the failover node. Oracle recommends using central or shared stores for the certificates used for different purposes (such as SSL set up for HTTP invocations).
  3. Change the directory to the directory that you just created:

    HOST> cd certs
    
  4. Run the utils.CertGen tool from the user-defined directory to create the certificates for both HOST.mycompany.com and VIP.mycompany.com.

    Syntax (all on a single line):

    java utils.CertGen Key_Passphrase Cert_File_Name Key_File_Name 
    [export | domestic] [Host_Name]
    

    Examples:

    HOST> java utils.CertGen welcome1 HOST.mycompany.com_cert 
    HOST.mycompany.com_key domestic HOST.mycompany.com
    
    HOST> java utils.CertGen welcome1 VIP.mycompany.com_cert 
    VIP.mycompany.com_key domestic VIP.mycompany.com
    

    Sample output for the command shown in the first example is:

    ...... Will generate certificate signed by CA from CertGenCA.der file
    ...... With Domestic Key Strength
    ...... Common Name will have Hostname HOST.mycompany.com
    ...... Issuer CA name is CN=CertGenCAB,OU=FOR TESTING ONLY,O=MyOrganization,
    L=MyTown,ST=MyState,C=US
    

7.3.2 Creating an Identity Keystore Using the utils.ImportPrivateKey Utility

Follow these steps to create an identity keystore on HOST:

  1. Create a new identity keystore called appIdentityKeyStore using the utils.ImportPrivateKey utility. Create this keystore under the same directory as the certificates (that is, ORACLE_BASE/admin/domain_name/aserver/domain_name/certs).

    Note:

    The identity store is created (if none exists) when you import a certificate and the corresponding key into the identity store using the utils.ImportPrivateKey utility.
  2. Import the certificate and private key for both HOST.mycompany.com and VIP.mycompany.com into the identity store. Make sure that you use a different alias for each of the certificate/key pairs imported.

    Syntax (all on a single line):

    java utils.ImportPrivateKey Keystore_File Keystore_Password 
    Certificate_Alias_to_Use Private_Key_Passphrase 
    Certificate_File Private_Key_File [Keystore_Type]
    

    Examples:

    HOST> java utils.ImportPrivateKey appIdentityKeyStore.jks welcome1 
    appIdentity1 welcome1 ORACLE_BASE/admin/domain_name/aserver/domain_name/
    certs/HOST.mycompany.com_cert.pem ORACLE_BASE/admin/domain_name/
    aserver/domain_name/certs/HOST.mycompany.com_key.pem
    
    HOST> java utils.ImportPrivateKey appIdentityKeyStore.jks welcome1 
    appIdentity2 welcome1 ORACLE_BASE/admin/domain_name/aserver/
    domain_name/certs/VIP.mycompany.com_cert.pem ORACLE_BASE/admin/
    domain_name/aserver/domain_name/certs/VIP.mycompany.com_key.pem
    

7.3.3 Creating a Trust Keystore Using the Keytool Utility

You only need to perform the steps in this section for the first Managed Server.

Follow these steps to create the trust keystore on HOST1:

  1. Copy the standard Java keystore to create the new trust keystore because it already contains most of the root CA certificates needed. Oracle does not recommend modifying the standard Java trust keystore directly. Copy the standard Java keystore CA certificates located under the WL_HOME/server/lib directory to the same directory as the certificates. For example:

    HOST> cp WL_HOME/server/lib/cacerts ORACLE_BASE/admin/domain_name/aserver/domain_name/certs/appTrustKeyStore.jks
    
  2. The default password for the standard Java keystore is 'changeit'. Oracle recommends always changing the default password. Use the keytool utility to do this. The syntax is (all on a single line):

    APPHOST1> keytool -storepasswd -new New_Password -keystore Trust_Keystore 
    -storepass Original_Password
    

    For example:

    HOST> keytool -storepasswd -new welcome1 -keystore appTrustKeyStore.jks 
    -storepass changeit
    
  3. The CA certificate CertGenCA.der is used to sign all certificates generated by the utils.CertGen tool. It is located in the WL_HOME/server/lib directory. This CA certificate must be imported into the appTrustKeyStore using the keytool utility. The syntax is (all on a single line):

    HOST> keytool -import -v -noprompt -trustcacerts -alias Alias_Name 
    -file CA_File_Location -keystore Keystore_Location -storepass Keystore_Password
    

    For example:

    HOST> keytool -import -v -noprompt -trustcacerts -alias clientCACert -file 
    WL_HOME/server/lib/CertGenCA.der -keystore appTrustKeyStore.jks -storepass 
    welcome1
    

7.3.4 Configuring Node Manager to Use the Custom Keystores

To configure Node Manager to use the custom keystores, add the following lines to the end of the nodemanager.properties file located in the WL_HOME/common/nodemanager directory:

KeyStores=CustomIdentityAndCustomTrust
CustomIdentityKeyStoreFileName=Identity_Keystore
CustomIdentityKeyStorePassPhrase=Identity_Keystore_Password
CustomIdentityAlias=Identity_Keystore_Alias
CustomIdentityPrivateKeyPassPhrase=Private_Key_Used_When_Creating_Certificate

Make sure to use the correct value for CustomIdentityAlias on each node. For example, on HOST2, use appIdentity2.

For example:

KeyStores=CustomIdentityAndCustomTrust
CustomIdentityKeyStoreFileName=ORACLE_BASE/admin/domain_name/aserver/domain_name/
certs/appIdentityKeyStore.jks
CustomIdentityKeyStorePassPhrase=welcome1
CustomIdentityAlias=appIdentity2
CustomIdentityPrivateKeyPassPhrase=welcome1

The passphrase entries in the nodemanager.properties file get encrypted when you start Node Manager as described in Section 7.4, "Starting Node Manager." For security reasons, you want to minimize the time the entries in the nodemanager.properties file are left unencrypted. After you edit the file, you should start Node Manager as soon as possible so that the entries get encrypted.

7.3.5 Configuring Managed Servers to Use the Custom Keystores

You must perform the steps in this section for the Administration Server and all Managed Servers.

To configure the identity and trust keystores:

  1. Log in to the Oracle WebLogic Server Administration Console.

  2. In the Change Center, click Lock & Edit.

  3. Expand the Environment node in the Domain Structure window.

  4. Click Servers. The Summary of Servers page is displayed.

  5. Click the name of the server for which you want to configure the identity and trust keystores (WLS_SERVER). The settings page for the selected server is displayed.

  6. Select Configuration, and then select Keystores.

  7. In the Keystores field, change to the Custom Identity and Custom Trust method for storing and managing private keys/digital certificate pairs and trusted CA certificates.

  8. In the Identity section, define attributes for the identity keystore as follows:

    1. Custom Identity Keystore: Enter the fully qualified path to the identity keystore:

      ORACLE_BASE/admin/domain_name/aserver/domain_name/certs/
      appIdentityKeyStore.jks
      
    2. Custom Identity Keystore Type: Ensure that this field is blank. Do not keep the default value of JKS.

    3. Custom Identity Keystore Passphrase: Enter the keystore password (Keystore_Password) you provided in Section 7.3.2, "Creating an Identity Keystore Using the utils.ImportPrivateKey Utility."

      This attribute might be optional or required, depending on the type of keystore. All keystores require the passphrase to write to the keystore. However, some keystores do not require the passphrase to read from the keystore. Oracle WebLogic Server only reads from the keystore, so whether you need to define this property depends on the requirements of the keystore.

  9. In the Trust section, define properties for the trust keystore:

    1. Custom Trust Keystore: Enter the fully qualified path to the trust keystore:

      ORACLE_BASE/admin/domain_name/aserver/domain_name/certs/
      appTrustKeyStore.jks
      
    2. Custom Trust Keystore Type: This field defaults to JKS. You must explicitly remove the default value so that the field is blank.

    3. Custom Trust Keystore Passphrase: Enter the password you provided for New_Password in Section 7.3.3, "Creating a Trust Keystore Using the Keytool Utility."

      This attribute might be optional or required, depending on the type of keystore. All keystores require the passphrase to write to the keystore. However, some keystores do not require the passphrase to read from the keystore. Oracle WebLogic Server only reads from the keystore, so whether you define this property depends on the requirements of the keystore.

  10. Click Save.

  11. In the Change Center, click Activate Changes.

  12. Select Configuration, then select SSL.

  13. In the Change Center, click Lock & Edit.

  14. In the Private Key Alias field, enter the alias you used for the host name on which the Managed Server listens.

    In the Private Key Passphrase and the Confirm Private Key Passphrase fields, enter the password for the keystore that you created in Section 7.3.2, "Creating an Identity Keystore Using the utils.ImportPrivateKey Utility."

  15. Click Save.

  16. In the Change Center, click Activate Changes.

7.3.6 Changing the Host Name Verification Setting for the Managed Servers

After the steps in the previous sections have been performed, you should set host name verification for the affected Managed Servers to Bea Host Name Verifier. To do this, perform the following steps for all Managed Servers:

  1. Log in to the Administration Console.

  2. In the Change Center, click Lock & Edit.

  3. Expand the Environment node in the Domain Structure window.

  4. Click Servers. The Summary of Servers page is displayed.

  5. Select the Managed Server in the Names column of the table. The settings page for the server is displayed.

  6. Open the SSL tab.

  7. Expand the Advanced section of the page.

  8. Set Hostname Verification to BEA Hostname Verifier.

  9. Click Save.

  10. In the Change Center, click Activate Changes.

  11. Restart the Managed Server for which the changes have been applied.

7.4 Starting Node Manager

When using a common/shared storage installation for MW_HOME, Node Manager is started from different nodes using the same base configuration (nodemanager.properties). In that case, it is required to add the certificate for all the nodes that share the binaries to the appIdentityKeyStore.jks identity store. To do this, create the certificate for the new node and import it to appIdentityKeyStore.jks as described in Section 7.3.2, "Creating an Identity Keystore Using the utils.ImportPrivateKey Utility." After the certificates are available in the store, each Node Manager must point to a different identity alias to send the correct certificate to the Administration Server. To do this, set different environment variables before starting Node Manager in the different nodes:

HOST> cd WL_HOME/server/bin
HOST> export JAVA_OPTIONS=-DCustomIdentityAlias=appIdentityX

Note:

Make sure to specify the custom identity alias specifically assigned to each host. For example, specify appIdentity1 for HOST1 and appIdentity2 for HOST2.

If you are not using a common/shared storage installation for MW_HOME, run these commands to restart Node Manager on HOST:

  1. Stop the Node Manager process by using CTRL-C in the shell where it was started, or by process identification and kill in the operating system.

  2. Start Node Manager, as follows:

    HOST> cd WL_HOME/server/bin
    HOST> ./startNodeManager.sh
    

    Note:

    If you have not configured and started Node Manager for the first time, run the ORACLE_COMMON_HOME/common/bin/setNMProps.sh script. This will enable the use of the start script, which is required for Oracle Business Intelligence.