Skip Headers
Oracle® WebCenter Content Installation Guide
11g Release 1 (11.1.1)

Part Number E14495-08
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

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:

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.

To start the Administration Server:

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

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

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

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:

To start a Managed Server:

  1. Start the Administration Server (see Section 9.1, "Starting the Administration Server").

  2. 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 an 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 "Managing System Processes" in Oracle Fusion Middleware Administering Oracle WebCenter Content.

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

  1. Stop the Managed Server with the stopManagedWebLogic script.

    • UNIX script:
      DomainHome
      /bin/stopManagedWebLogic.sh UCM_server1

    • Windows script:
      DomainHome\bin\stopManagedWebLogic.cmd UCM_server1

  2. Stop the Administration Server with the stopWebLogic script.

    • UNIX script: DomainHome/bin/stopWebLogic.sh

    • Windows script: DomainHome\bin\stopWebLogic.cmd

  3. Start the Administration Server with the startWebLogic script.

    • UNIX script: DomainHome/bin/startWebLogic.sh

    • Windows script: DomainHome\bin\startWebLogic.cmd

  4. 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 WebLogic Server instances remotely, monitor them, and automatically restart them after an unexpected failure. You can configure Oracle WebCenter Content Managed Servers, the WebLogic Server Administration Server, and Node Manager to work together in a 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:

This section describes how to configure a machine in a 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. By default the local host is preconfigured and named LocalMachine.

To configure a machine through the Fusion Middleware Configuration Wizard:

  1. When you get to the Select Optional Configuration screen in the Fusion Middleware Configuration Wizard, be sure to select Managed Servers, Clusters and Machines.

  2. On the Configure Machines screen, click Add.

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

To configure a machine through the WebLogic Server Administration Console:

  1. Log in to the WebLogic Server Administration Console.

  2. Under Domain Structure on the left, expand Environment, and click Machines.

  3. On the Summary of Machines screen, click New.

  4. On the Machine Identity step, specify values for the following items:

    • Name

    • Machine OS

  5. Click Next.

  6. On the Node Manager Properties step, specify values for the following items:

    • Type

    • Listen Address

    • Listen Port

    Optionally, configure the debug settings.

  7. Click Finish.

9.4.2 Assigning Servers to a Machine

Each machine definition can manage zero or more servers. 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:

  1. On the Assign Servers to Machines screen, select one or more servers in the Server area

  2. Click the right arrow button to assign the selected server or servers to a machine.

  3. Click Next when you are done.

To assign servers to a machine through the WebLogic Server Administration Console:

  1. Log in to the WebLogic Server Administration Console.

  2. Under Domain Structure on the left, expand Environment, and click Machines.

  3. Click the machine name to which you would like to assign a server.

  4. In the resulting Settings screen, click the Servers tab under Configuration.

  5. Click Add.

  6. In the Add a Server to Machine screen, under Identify a Server, choose a server to add from the list of available servers. (Optionally, you can create a new server.)

  7. Click Next or Finish.

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:

  1. Navigate to the following directory

    MW_HOME/oracle_common/common/bin
    

    MW_HOME is the directory where Oracle Fusion Middleware is installed.

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

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

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.4.4 Using Node Manager to Manage Servers

You can use Oracle Node Manager to start and stop Oracle WebLogic Server instances remotely, monitor them, and automatically restart them after an unexpected failure through the WebLogic Server Administration Console.

  1. Log in to the WebLogic Server Administration Console.

  2. Under Domain Structure on the left, expand Environment, and click Servers.

  3. Click the Control tab.

  4. Select one or more servers to control.

  5. Click a button corresponding to a control function.

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 for a Managed Server by setting the USER_MEM_ARGS environment variable in its startup script or command file.

To increase the Java VM heap size, you set the value of the -Xmx parameter. For more information, see Section 3.5.2, "Setting the USER_MEM_ARGS Environment Variable for 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.