Skip Headers
Oracle® Fusion Middleware Administering Oracle WebCenter Content
11g Release 1 (11.1.1)

Part Number E26692-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
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

4 Managing System Processes

This chapter describes how to start and stop an Oracle Content Server instance, how to start Content Server administration applications, and how to use a command-line tool to configure system variables.

This chapter includes the following topics:

4.1 Introduction to Starting, Stopping, and Restarting Content Server

There are several methods for starting, stopping, and restarting the Content Server instance. Which method you choose depends on your requirements, your authorization, and the task you want to complete. For example, when certain configuration changes are made to the Content Server instance, such as when components are enabled or disabled, the instance must be restarted. Available methods include:

Note:

In earlier releases, the Content Server's Admin Server could be used to start, stop, and restart the Content Server instance. This functionality has been replaced as of 11g Release 1 (11.1.1), although other functions can still be managed with the Admin Server.

4.2 Using Fusion Middleware Control to Start and Stop Content Server

Oracle Enterprise Manager Fusion Middleware Control can be used by administrators to manage multiple domains, including an Oracle WebLogic Server server running a WebCenter Content domain with the Content Server instance. This method of starting and stopping the Content Server instance also provides access to information about the Content Server on which the instance is deployed.

The Content Server instance is initially started during the process of installing and deploying the instance on a Content Server on an Oracle WebLogic Server domain. You might want to start the Content Server instance at other times, for example, to start the instance after it has been stopped when changing a Content Server configuration setting.

The Content Server instance can be stopped and restarted for several reasons, including changing the configuration, such as enabling or disabling a server component.

4.2.1 Using Fusion Middleware Control to Start Content Server

To start the Content Server instance:

  1. In the Fusion Middleware Control navigation tree, expand the appropriate domain name (for example, Farm_base_domain).

  2. Expand WebCenter, then Content, then Content Server, then Oracle Universal Content Management - Content Server.

  3. Select the Content Server instance name (for example, Oracle Universal Content Management - Content Server (UCM_server1)).

  4. In the Content Server home page, from the Content Server menu choose Control, then Start.

For more information, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.

4.2.2 Using Fusion Middleware Control to Stop Content Server

To stop the Content Server instance:

  1. In the Fusion Middleware Control navigation tree, expand the appropriate domain name (for example, Farm_base_domain).

  2. Expand Oracle WebCenter Content, then Content, then Content Server.

  3. Select the Content Server instance name (for example, Oracle Universal Content Management - Content Server (UCM_server1)).

  4. In the Content Server home page, from the Content Server menu choose Control, then Shut Down....

For more information, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.

4.2.3 Using Fusion Middleware Control to Restart Content Server

To restart the Content Server instance:

  1. In the navigation tree, expand the appropriate domain name (for example, Farm_base_domain).

  2. Expand Oracle WebCenter Content, then Content, then Content Server.

  3. Select the Content Server instance name (for example, Oracle Universal Content Management - Content Server (UCM_server1)).

  4. In the Content Server home page, from the Content Server menu choose Control, then Shut Down....

  5. Confirm that the Content Server instance is shut down.

  6. From the Content Server menu choose Control, then Start.

For more information, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.

4.3 Using WebLogic Server to Start and Stop Content Server

The Oracle WebLogic Server Administration Console is available to Content Server administrators because they must have administrative privileges to manage WebCenter Content with the Content Server instance. The Node Manager must be configured and running in order to start or stop the WebCenter Content managed server with the Content Server instance.

The Content Server instance is initially started during the process of installing and deploying the instance on a WebCenter Content server in an Oracle WebLogic Server domain. You might want to start the Content Server instance at other times, for example, to start the instance after it has been stopped when changing a Content Server configuration setting.

The Content Server instance can be stopped and restarted for several reasons, including changing the configuration, such as enabling or disabling a server component.

4.3.1 Using WebLogic Server Administration Console to Start Content Server

To start the Content Server instance:

  1. On the Administration Console home page, in the Domain Configurations area, choose Environment, then Servers.

  2. On the Configuration tab for the Summary of Servers page, select the name of the WebCenter Content server for the Content Server instance.

  3. In the Settings for server_name section, click the Control tab.

  4. On the Start/Stop tab, in the Server Status area, select the server name (for example, UCM_server1), then click Start.

For more information, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.

4.3.2 Using WebLogic Server Administration Console to Stop Content Server

To stop the Content Server instance:

  1. On the Administration Console home page, in the Domain Configurations area, choose Environment, then Servers.

  2. On the Configuration tab for the Summary of Servers page, select the name of the WebCenter Content server for the Content Server instance.

  3. In the Settings for server_name section, click the Control tab.

  4. On the Start/Stop tab, inn the Server Status area, select the server name (for example, UCM_server1), then click Shutdown.

For more information, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.

4.3.3 Using WebLogic Server Administration Console to Restart Content Server

To restart the Content Server instance:

  1. On the Administration Console home page, in the Domain Configurations area, choose Environment, then Servers.

  2. On the Configuration tab for the Summary of Servers section, select the name of the WebCenter Content server for the Content Server instance.

  3. In the Settings for server_name section, click the Control tab.

  4. On the Start/Stop tab, in the Server Status area, select the server name (for example, UCM_server1), then click Shutdown.

  5. Confirm that the Content Server instance has stopped, then click Start (or Resume).

For more information, see "Starting and Stopping Oracle WebLogic Server Instances" in Oracle Fusion Middleware Administrator's Guide.

4.4 Using Scripts to Start and Stop Content Server

Scripts provide a quick method to execute actions on Oracle WebLogic servers. Before you can start a Managed Server for an application, you must start the Administration Server for the Oracle WebLogic Server domain.

The following script examples assume that the Content Server instance has been previously started as part of the software installation process. For details, see "Starting the Administration Server" and "Starting Managed Servers" in Oracle WebCenter Content Installation Guide.

Caution:

These script commands control the Oracle WebLogic Server Managed Server that includes the WebCenter Content server and the WebLogic Server Administration Server, which includes the Administration Console. If you do not want to start or stop the Oracle WebLogic Server Administration Server, then use another method to start the Content Server instance.

4.4.1 Using Scripts to Start Content Server

To start the Content Server instance:

  1. Run the appropriate type of script to start the Oracle WebLogic Server Administration Console.

  2. Run the appropriate type of script to start the Oracle WebLogic Server Managed Server with the WebCenter Content server with the Content Server instance. In the following script examples, the instance is named UCM_Server1.

Windows script:

MW_HOME\user_projects\domains\DOMAIN_HOME\bin\startWebLogic.sh
MW_HOME\user_projects\domains\DOMAIN_HOME\bin\startManagedWebLogic.sh UCM_server1

UNIX script:

MW_HOME/user_projects/domains/DOMAIN_HOME/bin/startWebLogic.sh
MW_HOME/user_projects/domains/DOMAIN_HOME/bin/startManagedWebLogic.sh UCM_server1

4.4.2 Using Scripts to Stop Content Server

To stop the Content Server instance:

  1. Run the appropriate script to stop the WebCenter Content server with the Content Server instance on the Oracle WebLogic Server Managed Server. In the following script examples the instance is named UCM_server1.

  2. Next, only if necessary, run the script to stop the Oracle WebLogic Server Administration Console.

Windows script:

MW_HOME\user_projects\domains\DOMAIN_HOME\bin\stopManagedWebLogic.sh UCM_server1
MW_HOME\user_projects\domains\DOMAIN_HOME\bin\stopWebLogic.sh

UNIX script:

MW_HOME/user_projects/domains/DOMAIN_HOME/bin/stopManagedWeblogic.sh UCM_server1
MW_HOME/user_projects/domains/DOMAIN_HOME/bin/stopWebLogic.sh

4.4.3 Using Scripts to Restart Content Server

To restart the Content Server instance:

  1. Run the appropriate script to stop the Oracle WebLogic Server Managed Server with WebCenter Content and the Content Server instance. In the following script examples the instance is named UCM_server1.

  2. Next, only if necessary, run the script to stop the Oracle WebLogic Server Administration Server.

  3. When the server or servers have stopped, if appropriate run the script to start the Oracle WebLogic Server Administration Server.

  4. Run the script to start the Oracle WebLogic Server Managed Server with WebCenter Content and the Content Server instance.

Windows script:

MW_HOME\user_projects\domains\DOMAIN_HOME\bin\stopManagedWeblogic.sh UCM_server1
MW_HOME\user_projects\domains\DOMAIN_HOME\bin\stopWeblogic.sh
MW_HOME\user_projects\domains\DOMAIN_HOME\bin\startWeblogic.sh
MW_HOME\user_projects\domains\DOMAIN_HOME\bin\startManagedWeblogic.sh UCM_server1

UNIX script:

MW_HOME/user_projects/domains/DOMAIN_HOME/bin/stopManagedWeblogic.sh UCM_server1
MW_HOME/user_projects/domains/DOMAIN_HOME/bin/stopWeblogic.sh
MW_HOME/user_projects/domains/DOMAIN_HOME/bin/startWeblogic.sh
MW_HOME/user_projects/domains/DOMAIN_HOME/bin/startManagedWeblogic.sh UCM_server1

4.5 Starting Content Server Administration Applications

You can run Content Server administration applications either as applets or in standalone mode. Running applications in standalone mode requires additional configuration for database connections.

4.5.1 Running Administration Applications as Applets

You can run several of the Content Server administration applications as applets from any web browser with access to the Content Server instance. Applets are convenient for remote administration.

Note:

The Batch Loader, Component Wizard, System Properties, and Content Server Analyzer utilities cannot be run as applets; for security reasons, they must be run in standalone mode from the computer where the Content Server instance is deployed. For details, see Section 4.5.2.

Some functions that are available in the standalone version of an application are not available from the applet version. See the documentation for each application for more information.

To run an administration application as a Java applet within a Java-enabled browser:

  1. Open a browser window.

  2. Log in to the Content Server instance as an administrator.

  3. Choose Administration, then Admin Applets.

  4. Choose an administration application from the list of applets.

4.5.2 Running Administration Applications in Standalone Mode

You can run several Content Server administration Java applications in standalone mode from the computer where a Content Server instance is deployed. Some of the applications are the same as the applets accessed using a web browser, such as Configuration Manager and Repository Manager. Some applications can only run in standalone mode, such as System Properties and Batch Loader.

Running the standalone version of an application offers greater security than browser applets, and enables you to send passwords without having them captured or copied from the web or a network.

Important:

Before you can run Content Server administration applications in standalone mode, additional configuration is required to authenticate the applications on Oracle WebLogic Server and to have a JDBC connection to the system database and access to the Oracle WebLogic Server database connection. See Section 4.5.2.3 and Section 4.5.2.5.

If a standalone application is required to connect to a SSL-enabled database where digital certificates are used for authentication, then the database root CA certificate must be imported into the standard Java key store that the application uses to check trusted sources. For configuration details, see Oracle WebCenter Content Installation Guide.

4.5.2.1 Running a Standalone Application on a UNIX System

To run a Content Server administration application in standalone mode on a UNIX operating system:

  1. Navigate to the DomainHome/ucm/cs/bin/ directory. Executable applications are listed.

  2. Enter ./application_name, where application_name is the name of an executable file. If an application is not listed, it can be entered as a parameter to the IntradocApp application, as in this example:

    % ./intradocApp workflow
    
  3. Click Enter. For all applications except for the Component Wizard and the System Properties utility, a login window opens. For the Component Wizard and the System Properties utility, the main window of the application opens.

  4. Enter the administrator login name and password.

  5. Click OK.

4.5.2.2 Running a Standalone Application on a Windows System

To run a Content Server administration application in standalone mode on a Windows operating system.

  1. Select the application or utility from the Windows Start menu:

    • To run an administration application, from the Start menu choose Programs, then Content Server, then instance, then application.

    • To run an administration utility, from the Start menu choose Programs, then Content Server, then Utilities, then utility.

    For all applications except for the Component Wizard and the System Properties utility, a login window opens. For the Component Wizard and System Properties utility, the main window of the application opens.

    Tip:

    It may take several seconds for the login window or the application window to appear, or the window may be hidden by other windows.

  2. Enter the administrator login name and password.

  3. Click OK. The main window of the application opens.

4.5.2.3 Configuring a System Database Provider for Standalone Mode

Content Server administration applications and utilities that can only run in standalone mode require specific configuration to run in an Oracle WebLogic Serverdomain with Oracle WebCenter Content and the Content Server instance. The configuration changes for a standard (non-customized) Oracle WebLogic Server connection are necessary to have the applications authenticate Oracle WebLogic Server users and to set up a JDBC connection to the Oracle WebLogic Server system database.

To configure Oracle WebLogic Server system database connections:

  1. As system administrator, use VNC (or a similar tool such as putty or Xming) to navigate to the DOMAIN_HOME/ucm/cs/bin/ directory. For example:

    MW_HOME/user_projects/domains/ucm_domain/ucm/cs/bin
    
  2. Run ./SystemProperties.

  3. In the Paths tab of the System Properties window, the Specify Database Driver Classpath check box is selected by default, so you must enter a path to a JDBC driver for your system database in the Database Driver Classpath field.

    The Oracle driver ojdbc6dms.jar is provided with the Enterprise Content Management install in the following directory.

    MW_HOME/oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar
    
  4. In the Database tab, enter all the necessary JDBC connection information in the fields for your system database (database type, database user name, database user password, and so on).

  5. Click OK. You should now be able to run a standalone application. For example, as the Administrator user you created on the Content Server instance, run ./BatchLoader.

4.5.2.4 Configuring a JDBC Database Driver for Standalone Mode

For the Content Server instance to work with applications that only run in standalone mode (the Batch Loader, Component Wizard, System Properties, and Content Server Analyzer utilities) you must configure a JDBC driver for the system database or an external database provider. Oracle Fusion Middleware DataDirect JDBC drivers for SQL Server and DB2 databases are available to support Content Server standalone applications.

To enter configuration information using the System Properties utility:

  1. As system administrator, run ./SystemProperties from the DomainHome/ucm/cs/bin/ directory for the Content Server instance:

    • UNIX path:

      DOMAIN_HOME/ucm/cs/bin/SystemProperties
      
    • Windows path:

      DOMAIN_HOME\ucm\cs\bin\SystemProperties
      
  2. In the System Properties window, click the Database tab, then select the appropriate driver and enter the connection string, user name, and password.

    You do not need to enter a classpath or driver name, or copy any jar files.

    You can find JDBC connection string and user name information in the Oracle WebLogic Server Administration Console. Log in to the Administration Console, then select Services, then Data Sources, then CSDS (or URMDS), then Connection Pool. In the Connection Pool tab, the connection string is in the URL field, and the user name is in the Properties field. For security, the password is not displayed.

  3. In the Database tab, select the appropriate driver under Use Java Database Connectivity, and enter the connection string.

    • For Microsoft SQL Server, select DataDirect SQL Server JDBC Driver, and enter a connection string of this form:

      jdbc:weblogic:sqlserver://database_hostname:database_port_number;databaseName=database_name
      
    • For IBM DB2, select DataDirect DB2 JDBC Driver, and enter a connection string of this form:

      jdbc:weblogic:db2://database_hostname:database_port_number;databaseName=database_name
      
  4. Enter the user name and password for the database in the JDBC User Name and JDBC User Password fields.

  5. Click OK.

  6. Restart the Content Server instance.

4.5.2.5 Configuring an External Database Provider for Standalone Mode

You can create an external database provider in the Content Server instance for standalone applications to directly connect to a database with JDBC without using the System Database provider for the Oracle WebLogic Server data source.

For standalone applications to use the OracleTextSearch feature as an external search engine, you must configure the external database provider to include the JDBC connection information.

By default, the configuration of an incoming provider does not include values for JDBC Driver and JDBC Connection String. You must add these values, but be careful not to change the provider name because you cannot rename an existing provider. To change the name of a provider, you would need to delete it and then add it again.

4.6 Using the IdcShell Command-Line Tool to Run Idoc Script

The IdcShell tool enables administrators to run Idoc Script from a command line. Idoc Script is a proprietary server-side custom scripting language for the WebCenter Content system. This scripting language enables administrators to reference variables, conditionally include content in HTML pages, and loop over results returned from queries.

Idoc Script is used primarily for configuration settings and the presentation of HTML templates. Idoc variables (sometimes called configuration variables or environment variables) can be used in Idoc Script and in configuration files. For more information on configuration variables, see Oracle Fusion Middleware Configuration Reference for Oracle WebCenter Content. For more information on Idoc Script, see Oracle Fusion Middleware Developing with Oracle WebCenter Content.

The IdcShell tool also includes some additional Idoc Script functions, listed in Table 4-1, and some dynamichtml definitions, listed in Table 4-2, which are useful for managing Content Server or Inbound Refinery instances.

The IdcShell tool has built-in help, which you can access by running the command:

bin/IdcShell "include shell_help"

Table 4-1 Command-Line Idoc Script Functions

Function Description

doService(serviceName)

Executes a serviceName in the current context.

formatBinder()

Formats a DataBinder for easy reading.

getWithTrace()

Traces the get() function and reports on the source of the data.

promptUser(text, flags)

Displays text on the console and reads a user response. If flags is NO_ECHO, then it does not echo input.


Table 4-2 Dynamichtml Definitions

Dynamichtml definition Description

get_username

Prompts for a user name on the console and assigns to userName.

get_password

Prompts for a password on the console and assigned to dPassword.

set_user_password

Sets a user's password.

create_user

Creates a new user, by default with Admin role.