9 Verifying the Oracle WebCenter Content Configuration

This chapter explains how to verify the configuration of Oracle WebCenter Content and its applications.

This chapter includes the following sections:

Section 9.1, "Starting the Administration Server"
Section 9.2, "Starting Managed Servers"
Section 9.3, "Restarting a Managed Server"
Section 9.4, "Using Node Manager with Oracle WebCenter Content"
Section 9.5, "Increasing the Java Heap Size for a Managed Server"
Section 9.6, "Verifying the Configuration of Oracle WebCenter Content"

9.1 Starting the Administration Server

Before you can start a Managed Server for an application, you need to start the Administration Server for the Oracle WebLogic Server domain.

Note:

On a Windows operating system that has User Account Control (UAC) enabled, you need to start the Administration Server and the WebCenter Content Managed Server as an administrator before you can access Content Server through the web interface for WebCenter Content.

Open a Command Prompt window with the Run As Administrator option (right-click Command Prompt on the Start menu, or right-click the C:\windows\system32\cmd.exe file, and choose Run As Administrator). You should see "Administrator" in the title bar of the Command Prompt window.

Then you can use this window to start the Administration Server, as described in the following procedure.

To start the Administration Server:

Run the startWebLogic script (from the bin directory under the domain home directory):
- UNIX script: MW_HOME/user_projects/domains/DomainHome/bin /startWebLogic.sh [http://admin_url]
  
  Note:
  On a Linux operating system, the shell is going to stay open.
- Windows script: MW_HOME\user_projects\domains\DomainHome \bin\startWebLogic.cmd [http://admin_url]
The directory path to the Middleware home (MW_HOME) and the name of the domain (DomainHome) were provided on the Specify Domain Name and Location screen in Fusion Middleware Configuration Wizard.

The value of admin_url is the Administration Server URL. If the Administration Server does not use the default port, 7001, you need to specify a value for admin_url, such as http://localhost:8001/.
For a production system, supply the Oracle WebLogic Server user name and password.

Supply the values that were specified on the Configure Administrator User Name and Password screen in the configuration wizard.
Access the Oracle WebLogic Server Administration Console at the following URL:
```
http://adminServerHost:adminServerPort/console
```
For adminServerHost, specify the name of the computer that hosts the Administration Server for your domain. For adminServerPort, specify the listen port number for the Administration Server. The default number is 7001. For example:
```
http://myHost.example.com:7001/console
```
To log in, supply the user name and password that were specified on the Configure Administrator User Name and Password screen in the configuration wizard.

9.2 Starting Managed Servers

You can start each Managed Server in your Oracle WebLogic Server domain from the bin directory under your domain home directory:

UNIX path: MW_HOME/user_projects/domains/DomainHome/bin
Windows path: MW_HOME\user_projects\domains\DomainHome\bin

The directory path to the Middleware home (MW_HOME) and the name of the domain (DomainHome) were provided on the Specify Domain Name and Location screen in Fusion Middleware Configuration Wizard.

Important:

Before starting an Imaging Managed Server and logging in for the first time, see Section 6.1, "Completing the Initial Imaging Configuration," and do not start the Managed Server until you have completed the tasks before Section 6.1.2, "Starting the Imaging Managed Server and Accessing the Web Client."
Before logging in to the Oracle IRM Management Console for the first time or using Content application server Desktop, see Section 7.1, "Completing the Initial Oracle IRM Configuration."
On a Windows operating system that has User Account Control (UAC) enabled, you need to start the Oracle WebLogic Server Administration Server and WebCenter Content Managed Server as an administrator before you can access Content Server through the web interface for WebCenter Content.

Open a Command Prompt window with the Run As Administrator option (right-click Command Prompt on the Start menu, or right-click the C:\windows\system32\cmd.exe file, and choose Run As Administrator). You should see "Administrator" in the title bar of the Command Prompt window.

Then you can use this window to start the WebCenter Content Managed Server, as described in the following procedure. For information about accessing Content Server, see Section 9.6, "Verifying the Configuration of Oracle WebCenter Content."

To start a Managed Server:

Start the Administration Server (see Section 9.1, "Starting the Administration Server").
Run the startManagedWebLogic script:
- UNIX script: MW_HOME/user_projects/domains/DomainHome/bin /startManagedWebLogic.sh server_name [admin_url]
- Windows script: MW_HOME\user_projects\domains\DomainHome \bin\startManagedWebLogic.cmd server_name [admin_url]
This script requires that you specify a server name, such as one of these names:
- UCM_server1 (WebCenter Content)
- IBR_server1 (Inbound Refinery)
- IPM_server1 (Imaging)
- IRM_server1 (Oracle IRM)
- URM_server1 (Records)
The Managed Servers names are in the startManagedWebLogic_readme.txt file. To view the server names on a UNIX operating system, issue this command:
```
cat MW_HOME/user_projects/domains/domain_name/startManagedWebLogic_readme.txt
```
To view the server names on a Windows operating system, double-click this file:
```
MW_HOME\user_projects\domains\domain_name\startManagedWebLogic_readme.txt
```
The value of admin_url is the Administration Server URL. If the Administration Server does not use the default port, 7001, you need to specify a value for admin_url, such as http://localhost:8001/.

You will be prompted for the Oracle WebLogic Server user name and password before the server starts. These were provided on the Configure Administrator User Name and Password screen in the configuration wizard.

For example, the following script would start an Imaging Managed Server on a UNIX operating system:

cd MW_HOME/user_projects/domains/domain_name/bin
./startManagedWebLogic.sh IPM_server1 http://localhost:8001/

On a Windows operating system, the following script would start a Oracle IRM Managed Server on the local host:

MW_HOME\user_projects\domains\domain_name\bin\

startManagedWebLogic.cmd IRM_server1

To avoid prompts for a user name and password on startup after you start a Managed Server the first time, you can create a boot.properties file in the domain-home/servers/server-name/security/ directory. This file would include the following lines:

username=USERNAME
password=PASSWORD

The boot.properties file will be encrypted the first time that the Managed Server is started.

For information about stopping and starting a Managed Server with Oracle Enterprise Manager Fusion Middleware Control, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.

9.3 Restarting a Managed Server

Before changes to the configuration of a Managed Server can take effect, you need to restart it. You can restart a Managed Server with the Administration Console, shutdown and startup scripts, or Fusion Middleware Control.

The following example shows how to restart a Managed Server with the stopManagedWebLogic and startManagedWebLogic scripts. For more information, see "Restarting Content Server" in Oracle WebCenter Content System Administrator's Guide for Content Server.

To restart a Managed Server with scripts on the command line:

Stop the Managed Server with the stopManagedWebLogic script.
- UNIX script: DomainHome/bin/stopManagedWebLogic.sh UCM_server1
- Windows script:
  DomainHome\bin\stopManagedWebLogic.cmd UCM_server1
Stop the Administration Server with the stopWebLogic script.
- UNIX script: DomainHome/bin/stopWebLogic.sh
- Windows script: DomainHome\bin\stopWebLogic.cmd
Start the Administration Server with the startWebLogic script.
- UNIX script: DomainHome/bin/startWebLogic.sh
- Windows script: DomainHome\bin\startWebLogic.cmd
Start the Managed Server with the startManagedWebLogic script.
- UNIX script: DomainHome/bin/startManagedWebLogic.sh UCM_server1
- Windows script:
  DomainHome\bin\startManagedWebLogic.cmd UCM_server1

9.4 Using Node Manager with Oracle WebCenter Content

The Oracle WebLogic Server Node Manager enables you to start and stop Oracle WebLogic Server instances remotely, monitor them, and automatically restart them after an unexpected failure. You can configure Oracle WebCenter Content Managed Servers, the Administration Server, and Node Manager to work together in an Oracle WebLogic Server domain. Node Manager is installed on all the machines that host any server instance.

Before you can use Node Manager to start and stop Oracle WebCenter Content Managed Servers in a domain, you need to do these configuration tasks:

Configure at least one machine for the domain.
Assign the Administration Server and Managed Servers (such as AdminServer, IPM_server1, and UCM_server1) to one or more machines.
Enable Node Manager to use the Oracle WebCenter Content startup scripts by setting the StartScriptEnabled property in the nodemanager.properties file to true.

This section describes how to configure a machine in an Oracle WebLogic Server domain, assign the Administration Server and Managed Servers to a machine, and enable Node Manager to use startup scripts before you start it. For information about creating or extending a domain to configure Oracle WebCenter Content, see Chapter 3, "Configuring Oracle WebCenter Content Applications."

9.4.1 Configuring a Machine

The Administration Server uses a machine definition and the Node Manager application to start remote servers. During the initial configuration of Oracle WebCenter Content, you can configure machines through the Fusion Middleware Configuration Wizard. After the initial configuration, you can configure machines through the Oracle WebLogic Server Administration Console.

To configure a machine through the Fusion Middleware Configuration Wizard:

When you get to the Select Optional Configuration screen in the Fusion Middleware Configuration Wizard, be sure to select Managed Servers, Clusters and Machines.
On the Configure Machines screen, click Add.
Specify values for these fields:
- Name
  
  Enter a valid machine name, such as Linux-Box. The machine name identifies the machine within the Oracle WebLogic Server domain; it does not have to match the network name for the machine. The name must be unique within the domain.
- Node manager listen address
  
  Select a value from the drop-down list for the listen address used by Node Manager to listen for connection requests. By default, the IP addresses defined for the local system and localhost are shown in the drop-down list. The default value is localhost.
  
  If you specify an IP address for a machine that hosts the Administration Server and you need to access Node Manager, you must disable host name verification. For more information, see "Using Host Name Verification" in Oracle Fusion Middleware Securing Oracle WebLogic Server.
- Node manager listen port
  
  Enter a valid value for the listen port used by Node Manager to listen for connection requests. The valid listen port range for Node Manager is from 1 to 65535. The default value is 5556.

9.4.2 Assigning Servers to a Machine

During the initial configuration of Oracle WebCenter Content, you can assign the Administration Server and Managed Servers to one or more machines through the Fusion Middleware Configuration Wizard.

After the initial configuration, you can assign Managed Servers to machines through the Oracle WebLogic Server Administration Console.

To assign servers to a machine through the Fusion Middleware Configuration Wizard:

On the Assign Servers to Machines screen, select one or more servers in the Server area
Click the right arrow button to assign the selected server or servers to a machine.
Click Next when you are done.

9.4.3 Enabling the Use of Startup Scripts Before Starting Node Manager

Before you start Node Manager the first time, you can run the setNMProps.sh script to set the StartScriptEnabled property to true. This setting is required for Node Manager to start the Managed Servers with startup scripts. You must use the StartScriptEnabled property to avoid class-loading failures and other problems.

If you enable Node Manager to use startup scripts on a machine that hosts one or more Managed Servers that are assigned to a machine, you can start and stop the Managed Servers remotely using the Administration Console or the command line. Node Manager can also automatically restart a Managed Server after an unexpected failure.

For a Records Managed Server, before you start Node Manager, be sure to complete the Records setup checklist, described in Section 8.1, "Completing the Initial Records Configuration."

To enable startup scripts and start Node Manager:

Navigate to the following directory
```
MIDDLEWARE_HOME/oracle_common/common/bin
```
MIDDLEWARE_HOME is the directory where Oracle Fusion Middleware is installed.
Run the setNMProps.sh script to set the StartScriptEnabled property to true before starting Node Manager:

./setNMProps.sh

This is a one-time action. After you run this script, you can skip this step before starting Node Manager again.
Start Node Manager with the startNodeManager script.

UNIX script: WL_HOME/server/bin/startNodeManager.sh

Windows script: WL_HOME\server\bin\startNodeManager.cmd

WL_HOME is the directory where Oracle WebLogic Server is installed.

Note:

On a Windows operating system that has User Account Control (UAC) enabled, you need to start the Oracle WebLogic Server Administration Server and the WebCenter Content Managed Server as an administrator before you can access Content Server through the web interface for WebCenter Content. If you want to use Node Manager to start the WebCenter Content Managed Server, you also need to start Node Manager as an administrator, with the following procedure:

Run DomainHome\ucm\cs\bin\Installer.exe DisableNtfs8dot3 to disable the 8-dot-3 naming convention on the Windows operating system.

On a Windows 7 operating system, instead of running this script, you need to change the Registry key directly, as described in Section 2.1.1, "Disabling the 8.3 File Naming Convention on a Windows Operating System."
Restart the machine.
Open a Command Prompt window with the Run As Administrator option (right-click Command Prompt on the Start menu, or right-click the C:\windows\system32\cmd.exe file, and choose Run As Administrator). You should see "Administrator" in the title bar of the Command Prompt window.
Start the Oracle WebLogic Server Administration Server.

For more information, see Section 9.1, "Starting the Administration Server."
Open another Command Prompt window with the Run As Administrator option.
Start Node Manager, as described in Section 9.4.3, "Enabling the Use of Startup Scripts Before Starting Node Manager."
Access the Oracle WebLogic Server Administration Console, click Servers, and start the WebCenter Content Managed Server.

For information about accessing the Administration Console, see Section 9.6, "Verifying the Configuration of Oracle WebCenter Content."

For more information about Node Manager, see Managing Server Startup and Shutdown for Oracle WebLogic Server and Node Manager Administrator's Guide for Oracle WebLogic Server.

9.5 Increasing the Java Heap Size for a Managed Server

The default Java heap size is 512 MB for an Oracle WebLogic Server Managed Server. For better performance with the JRockit JDK, increase the heap size for each Managed Server in an Oracle WebCenter Content domain to 1 GB (1024 MB). If you use Node Manager to start the Managed Servers, you can specify a heap size as a Java argument on the Server Start tab of the Settings page for each Managed Server in the Administration Console.

To increase the Java heap size for a Managed Server in the Administration Console:

Log into the Administration Console.
If you have not already done so, in the Change Center on the upper left, click Lock & Edit.
In the navigation tree on the left, expand Environment, and click Servers.
In the Servers table, click the name of the server instance you want to configure.
On the Configuration tab, click Server Start.
In the Arguments field, specify the following Java option:
```
-Xmx1024m
```
Click Save.
To activate the change, in the Change Center on the upper left, click Activate Changes.
Restart the Managed Server, as described in Section 9.3, "Restarting a Managed Server."

9.6 Verifying the Configuration of Oracle WebCenter Content

To verify the configuration of Oracle WebCenter Content, start a web browser, and enter the following URLs to test access to the Administration Server, Administration Console, and Fusion Middleware Control, as well as to applications in your Oracle WebLogic Server domain.

To access the Administration Server:
```
http://adminServerHost:adminServerPort
```
For adminServerHost, specify the name of the computer that hosts the Administration Server for your domain. For adminServerPort, specify the listen port number for the Administration Server. The default number is 7001. For example:
```
http://myHost.example.com:7001
```
To log in, supply the user name and password that were specified on the Configure Administrator User Name and Password screen in the configuration wizard.
To access the Administration Console:
```
http://adminServerHost:adminServerPort/console
```
For adminServerHost, specify the name of the computer that hosts the Administration Server for your domain. For adminServerPort, specify the listen port number for the Administration Server. The default number is 7001. For example:
```
http://myHost.example.com:7001/console
```
To log in, supply the user name and password that were specified on the Configure Administrator User Name and Password screen in the configuration wizard.
To access Fusion Middleware Control:
```
http://adminServerHost:adminServerPort/em
```
For adminServerHost, specify the name of the computer that hosts the Administration Server for your domain. For adminServerPort, specify the listen port number for the Administration Server. The default number is 7001. For example:
```
http://myHost.example.com:7001/em
```
To log in, supply the user name and password that were specified on the Configure Administrator User Name and Password screen in the configuration wizard.

In Fusion Middleware Control, you can configure the pages for Oracle WebCenter Content applications.
To test WebCenter Content by accessing Content Server:
```
http://managedServerHost:managedServerPort/cs
```
The default port number for WebCenter Content is 16200.

The first user to log in to Oracle WebCenter Content Server must be the administrator of the Oracle WebLogic Server domain, to complete the configuration of Content Server. For more information, see Section 4.2, "Completing the Initial WebCenter Content Configuration," and "Introduction to Content Server Administration," "Managing Security and User Access," and "Starting, Stopping, and Restarting Content Server" in Oracle WebCenter Content System Administrator's Guide for Content Server.
To test a newly set up Inbound Refinery instance:
```
http://managedServerHost:managedServerPort/ibr
```
Log in with the user name and password for Oracle WebLogic Server. The default port number for Inbound Refinery is 16250.
To test a newly set up Imaging instance:
```
http://managedServerHost:managedServerPort/imaging
```
Log in with the user name and password for Oracle WebLogic Server. The default port number for Imaging is 16000.

To test a newly set up Oracle IRM instance:

https://managedServerHost:managedServerPort/irm_desktop

To test a newly set up Records instance:
```
http://managedServerHost:managedServerPort/urm
```
Log in with the user name and password for Oracle WebLogic Server. The default port number for Records is 16300.