一步不行吗 ?
AUTO_LOGIN ,AUTO_LOGIN local ,AUTO_LOGIN only 不同用法
+ If you are already using AUTO_LOGIN wallet on the source database, you will already have ewallet.p12 and cwallet.sso files on the source. If the source AUTO_LOGIN wallet was NOT created with LOCAL option, you can copy the autologin wallet file i.e. cwallet.sso to auxiliary along with ewallet.p12 file and no need to create the autologin wallet on auxiliary. However, if the source AUTO_LOGIN wallet was created with LOCAL option, do not copy cwallet.sso file to auxiliary server. Copy only the ewallet.p12 file to auxiliary and run Step 3 above to create cwallet.sso file explicitly for the auxiliary server.
+ In above orapki command, ensure that you correctly specify the wallet password otherwise you may get a misleading error message that the wallet file could not be found.
a)For FMW 11g components associated with a WebLogic Domain or a FMW 12c Collocated OHS install run: 2. Convert the Wallet you want to export to a Java Keystore:
For example:
3. Create a Password Protected Wallet (e.g ewallet.p12) in a new location:
For example:
4. Convert the Keystore created in Step 2. to the wallet created in Step 3:
For example:
5. At this point you now have converted your original Auto-Login (cwallet.sso) Wallet into a PKCS12 compliant Wallet (ewallet.p12 ) which can be used in any 3rd party PKCS12 aware application. |