10 Verifying the Installation and Configuration

This chapter explains how to verify successful installation and complete the configuration of Oracle Enterprise Content Management Suite applications, in these topics:

Starting the Administration Server
Starting Managed Servers
Starting Node Manager
Increasing the Java Heap Size for a Managed Server
Verifying the Installation

10.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 Oracle UCM Managed Server as an administrator before you can access Oracle Content Server through the web interface for Oracle UCM.

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.

10.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 Oracle I/PM Managed Server and logging in for the first time, see Section 7.1, "Completing the Oracle I/PM Configuration," and do not start the Managed Server until you have completed the tasks before Section 7.1.2, "Starting the Oracle I/PM Managed Server and Accessing the Web Client."
Before logging in to the Oracle IRM Management Console for the first time or using Oracle IRM Desktop, see Section 8.1, "Performing Postinstallation Configuration."
On a Windows operating system that has User Account Control (UAC) enabled, you need to start the Oracle WebLogic Server Administration Server and Oracle UCM Managed Server as an administrator before you can access Oracle Content Server through the web interface for Oracle UCM.

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 Oracle UCM Managed Server, as described in the following procedure. For information about accessing Oracle Content Server, see Section 10.6, "Verifying the Installation."

To start a Managed Server:

Start the Administration Server (see Section 10.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 (Oracle Universal Content Management)
- IBR_server1 (Oracle Inbound Refinery)
- IPM_server1 (Oracle Imaging and Process Management)
- IRM_server1 (Oracle Information Rights Management)
- URM_server1 (Oracle Universal Records Management)
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 example, the following script would start an Oracle I/PM 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 an Oracle IRM Managed Server on the local host:
```
MW_HOME\user_projects\domains\domain_name\bin\ startManagedWebLogic.cmd IRM_server1
```

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.

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

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.

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.

10.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 Fusion Middleware System Administrator's Guide for Oracle 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

10.4 Starting Node Manager

Starting Node Manager on a machine that hosts one or more Managed Servers enables you to 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.

Before you start Node Manager, be sure to complete the Oracle URM setup checklist, described in Section 9.1, "Completing the Oracle URM Configuration."

To start Node Manager:

Start Node Manager with the startNodeManager script.

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

Windows script: WL_HOME\server\bin\startNodeManager.cmd
Edit the nodemanager.properties file to change the entry StartScriptEnabled=false to StartScriptEnabled=true.
Restart Node Manager.

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 Oracle UCM Managed Server as an administrator before you can access Oracle Content Server through the web interface for Oracle UCM. If you want to use Node Manager to start the Oracle UCM 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.
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, as described in Section 10.1, "Starting the Administration Server."
Open another Command Prompt window with the Run As Administrator option.
Start Node Manager in it, as described in the preceding procedure.
Access the Oracle WebLogic Server Administration Console, as described in Section 10.6, "Verifying the Installation," click Servers, and start the Oracle UCM Managed Server.

For more information about Node Manager, see Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.

10.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 ECM 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 10.3, "Restarting a Managed Server."

10.6 Verifying the Installation

To verify the installation of Oracle Enterprise Content Management Suite, 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 Enterprise Management Suite applications.
To test a newly set up Oracle UCM instance by accessing Oracle Content Server:
```
http://managedServerHost:managedServerPort/cs
```
Log in with the user name and password for Oracle WebLogic Server. The default port number for Oracle UCM is 16200.
To test a newly set up Oracle IBR instance:
```
http://managedServerHost:managedServerPort/ibr
```
Log in with the user name and password for Oracle WebLogic Server. The default port number for Oracle IBR is 16250.
To test a newly set up Oracle I/PM instance:
```
http://managedServerHost:managedServerPort/imaging
```
Log in with the user name and password for Oracle WebLogic Server. The default port number for Oracle I/PM is 16000.

To test a newly set up Oracle IRM instance:

https://managedServerHost:managedServerPort/irm_desktop

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