7 Verifying the Installation and Configuration

This chapter explains how to verify successful installation and complete the configuration of Oracle Enterprise Content Management Suite applications.

This chapter includes the following sections:

Section 7.1, "Starting the Administration Server"
Section 7.2, "Starting Managed Servers"
Section 7.3, "Starting Node Manager"
Section 7.4, "Verifying the Installation"

7.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.

To start the Administration Server:

Run the startWebLogic.sh script (UNIX system) or startWebLogic.cmd script (Windows system) from the bin directory under the domain home directory.

The default domain home directory is MW_HOME/user_projects/domains/domain_name (UNIX system) or MW_HOME\user_projects\domains\domain_name (Windows system). Your domain name and directory path were provided on the Specify Domain Name and Location in Fusion Middleware Configuration Wizard.

Note:
On a Linux operating system, the shell is going to stay open.
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: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.

7.2 Starting Managed Servers

You can start each Managed Server from the bin directory inside your domain home directory, which is MW_HOME/user_projects/domains/domain_name (UNIX system) or MW_HOME\user_projects\domains\domain_name (Windows system). This information was provided on the Specify Domain Name and Location screen in the configuration wizard.

Important:

Before starting an Oracle I/PM Managed Server and logging in for the first time, see Section 5.1, "Completing the Oracle I/PM Configuration After First Login," and do not start the Managed Server until you have completed the tasks before Section 5.1.4, "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 6.1, "Performing Postinstallation Configuration."

To start a Managed Server:

Start the Administration Server (see Section 7.1, "Starting the Administration Server").
Run the startManagedWebLogic.sh script (UNIX system) or startManagedWebLogic.cmd script (Windows system) from the bin directory in the domain home directory.

This command requires that you specify a server name, such as one of these:
- IPM_server1 (Oracle Imaging and Process Management)
- IRM_server1 (Oracle Information Rights Management)
For example, the following UNIX command would start an Oracle I/PM Managed Server:
```
MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.sh IPM_server1
```
The following Windows command would start an Oracle IRM Managed Server:
```
MW_HOME\user_projects\domains\domain_name\bin\startManagedWebLogic.cmd IRM_server1
```

If you selected production mode, 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 names of the Managed Servers 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 11g Fusion Middleware Control, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.

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 filed would include the following lines:

username=USERNAME
password=PASSWORD

7.3 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.

To start Node Manager:

Set the Node Manager properties with a script.

On a UNIX operating system, run this script:
```
ECM_ORACLE_HOME/common/bin/setNMProps.sh
```
On a Windows operating system, run this script:
```
ECM_ORACLE_HOME\common\bin\setNMProps.cmd
```
Start Node Manager with a script.

On a UNIX operating system, run this script:
```
WL_HOME/server/bin/startNodeManager.sh
```
On a Windows operating system, run this script:
```
WL_HOME\server\bin\startNodeManager.cmd
```

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

7.4 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 WebLogic 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: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: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: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 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_rights
```
Log in with the user name and password for Oracle WebLogic Server. The default port number for Oracle IRM with SSL enabled is 16101.