Restarting the Administration Server Starting and Configuring the WLS_UCM1 Managed Server Choose Servers. The Summary of Servers page opens. Select WLS_UCM1 and then click Start.

7-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite 2. Run the following commands on both ECMHOST1 and ECMHOST2 to start Node Manager: ECMHOSTn cd WL_HOMEserverbin ECMHOSTn .startNodeManager.sh

7.5 Restarting the Administration Server

Restart the Administration Server to make these changes take effect. To restart the Administration Server, stop it first using the Administration Console and then start it again as described in Section 5.5, Starting the Administration Server on SOAHOST1.

7.6 Starting and Configuring the WLS_UCM1 Managed Server

Starting the WLS_UCM1 Managed Server Perform these steps to start the WLS_UCM1 managed server: 1. Start the WLS_UCM1 managed server using the Oracle WebLogic Server Administration Console as follows: a. Expand the Environment node in the Domain Structure window.

b. Choose Servers. The Summary of Servers page opens.

c. Click the Control tab.

d. Select WLS_UCM1 and then click Start.

2. Verify that the server status is reported as Running in the Administration Console. If the server is shown as Starting or Resuming, wait for the server status to change to Started. If another status is reported such as Admin or Failed, check the server output log files for errors. See Section 12.8, Troubleshooting for possible causes. Configuring the WLS_UCM1 Managed Server Perform these steps to configure the WLS_UCM1 managed server: 1. Log in to WLS_UCM1 at http:ECMHOST1:16200cs using your Oracle WebLogic administration user name and password to display a configuration page. Note: You must use the StartScriptEnabled property to avoid class loading failures and other problems. See also Section 12.8.3, Incomplete Policy Migration After Failed Restart of SOA Server. Note: If the UCM server is sharing the MW_HOME in a local or shared storage with SOA, as suggested in the shared storage configuration described in Chapter 2, Database and Environment Preconfiguration, it is not required to run setNMProps.sh again. In this case, Node Manager has already been configured to use a start script. Extending the Domain with Oracle UCM 7-9 2. Change the following values on the server configuration page make sure to select the Is New Content Server Instance check box to see all options: ■ Content Server Instance Folder: Set this to ORACLE_BASEadmin ecm_domainucm_clustercs. ■ Native File Repository Location: Set this to ORACLE_BASEadmin ecm_domainucm_clustercsvault. ■ WebLayout Folder: Set this to ORACLE_BASEadminecm_domain ucm_clustercsweblayout. ■ Server Socket Port: Set this to 4444. ■ Socket Connection Address Security Filter: Set this to a pipe-delimited list of localhost and the server IPs: 127.0.0.1|ECMHOST1|ECMHOST2|WEBHOST1|WEBHOST2 ■ WebServer HTTPHTTPS Address: Set this to ecm.mycompany.com:443. ■ Web Address is HTTPS: Select this check box. ■ Server Instance Label: Set this to UCM_Cluster1. ■ Server Instance Description: Set this to Cluster ucm_cluster1. ■ Auto_Number Prefix: Set this to ucm_cluster1-.

3. Click Submit when finished and restart the managed server using the Oracle

WebLogic Server Administration Console.

7.7 Updating the cwallet File in the Administration Server