Blackberry WALLET 1.2 - RELEASE NOTES Instalační příručka Strana 68

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 88
  • Tabulka s obsahem
  • ŘEŠENÍ PROBLÉMŮ
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 67
Oracle White Paper—Oracle Portal Enterprise Deployment Guide: 11.1.1.2
sign all 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
Follow these steps to configure the Node Manager to use the custom keystores.
1. 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 APPHOST2, use "appIdentity2.
Example for Node 1:
KeyStores=CustomIdentityAndCustomTrust
CustomIdentityKeyStoreFileName=ORACLE_BASE/product/FMW/certs/appIdentityKe
yStore.jks
CustomIdentityKeyStorePassPhrase=welcome1
CustomIdentityAlias=appIdentity1
CustomIdentityPrivateKeyPassPhrase=welcome1
Note:
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
APPHOST2”
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.
65
Zobrazit stránku 67
1 2 ... 63 64 65 66 67 68 69 70 71 72 73 ... 87 88

Komentáře k této Příručce

Žádné komentáře