Configuring Oracle Enterprise Content Management Suite 4-15
The following operations should have completed successfully:
■
Extension of an existing Oracle WebLogic Server domain to include the application or applications that you selected on the Extend Domain Source screen
■
Creation of a Managed Server for each application that you selected
■
Deployment of each application to its Managed Server An application is not active until its Managed Server is started. Before you start a
Managed Server, see the rest of the configuration information in this chapter and in the configuration chapter for your application. For more information, see
Section 10.2, Starting Managed Servers.
4.4 Extending a Domain in an SSL Environment
If your Oracle WebLogic Server domain connects to a database through an SSL port, you need to back up your data source and SSL parameters and remove the SSL
configuration from the data source before running Fusion Middleware Configuration Wizard to extend the domain. After you have successfully extended the domain, you
can restore the SSL configuration to your data source.
To extend a domain in an SSL environment with Fusion Middleware Configuration Wizard:
1.
In the Oracle WebLogic Server Administration Console, select your data source, and save a backup of all SSL parameters.
Back up the URL, javax.net.ssl.trustStorePassword, javax.net.ssl.trustStore, javax.net.ssl.trustStoreType, and any
other SSL parameters that have been configured for the data source.
2.
Temporarily replace the SSL configuration for the data source with a non-SSL configuration.
Use a non-SSL URL and remove all SSL properties. You should end with something like this configuration:
■
URL: : jdbc:oracle:thin:myhost.example.com:1521:db11107
■
Properties:
– user=MAR20SSL_OCS
– oracle.net.CONNECT_TIMEOUT=10000
– sendStreamAsBlob=true
3.
Using Fusion Middleware Configuration Wizard, extend the domain, as described in
Table 4–3 .
4.
After successfully extending the domain, restore the SSL configuration to your data source. You should end with something like this configuration:
■
URL: jdbc:oracle:thin:DESCRIPTION=ADDRESS_
LIST=ADDRESS=PROTOCOL=TCPSHOST=myhost.example.comPORT=2490CONNECT _DATA=SERVICE_NAME=db11107.example.comSECURITY=SSL_SERVER_CERT_
DN=CN=myhost.example.com,OU=QA,O=ECM,L=RedwoodShores,ST=California,C=US
4-16 Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite
■
Properties:
– javax.net.ssl.trustStorePassword=DemoTrustKeyStorePassPhr
ase
– user=MAR20SSL_OCS
– javax.net.ssl.trustStore=mw_homewlserver_
10.3serverlibDemoTrust.jks
– oracle.net.CONNECT_TIMEOUT=10000
– javax.net.ssl.trustStoreType=JKS
– javax.net.ssl.trustStoreType=JKS
– sendStreamAsBlob=true
5.
If during step 3 you updated your domain with a new product that creates its own data source, you may need to add SSL configuration to it as well.
4.5 Increasing the Java VM Heap Size for Managed Servers
