
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2
certificates generated by utils.CertGen tool. Import CertGenCA.der using the following
syntax:
keytool -import -v -noprompt -trustcacerts -alias <AliasName> -file
<CAFileLocation> -keystore <KeyStoreLocation>
Configuring Node Manager to Use the Custom Keystores
To configure the Node Manager to use the custom keystores, add the following lines to the end
of the nodemanager.properties file located in the
ORACLE_BASE/product/FMW/wlserver_10.3/common/nodemanager directory:
KeyStores=CustomIdentityAndCustomTrust
CustomIdentityKeyStoreFileName=<Identity KeyStore>
CustomIdentityKeyStorePassPhrase=<Identity KeyStore Passwd>
CustomIdentityAlias=<Identity Key Store Alias>
CustomIdentityPrivateKeyPassPhrase=<Private Key used when creating Certificate>
Make sure to use the correct value for CustomIdentityAlias on each node. For example on
APPHOST1, use appIdentity1.
Example for Node 1:
KeyStores=CustomIdentityAndCustomTrust
CustomIdentityKeyStoreFileName=ORACLE_BASE/product/FMW/certs/
appIdentityKeyStore.jks
CustomIdentityKeyStorePassPhrase=welcome1
CustomIdentityAlias=appIdentity1
CustomIdentityPrivateKeyPassPhrase=welcome1
The passphrase entries in the nodemanager.properties file get encrypted when you start Node
Manager as described in the next section, “Starting the Node Manager on APPHOST1” 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.
Starting the Node Manager on APPHOST1
Run these commands to start Node Manager on APPHOST1:
APPHOST1> cd ORACLE_BASE/product/FMW/wlserver_10.3/server/bin
61
Commenti su questo manuale