This quick installation guide describes how to install and configure Oracle Enterprise Content Management Suite for a demo, test, or proof of concept (POC) system. Most of the configuration uses default values.

1.2 Meeting System Requirements and Certification

For system requirements and certification information, refer to the following documents, available on Oracle Technology Network (OTN):

"Oracle Fusion Middleware System Requirements and Specifications" contains information related to hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches. This document is at

For the 32-bit version of the product, the system on which you are installing must be a supported 32-bit system. Installing a 32-bit version of the product on a 64-bit system is not supported.

1.3 Preparing to Install

The following tasks need to be done on your system before you install and configure Oracle Enterprise Content Management Suite. Some of the tasks are required only on a Windows operating system or on a Dynamic Host Configuration Protocol (DHCP) host.

1.3.1 Installing a Database

The configuration of Oracle Enterprise Content Management Suite requires the availability of a supported database. The database must be up, and a database instance must be running before you create schemas for the suite's applications with Repository Creation Utility (RCU) and before you configure any of the applications. The database does not have to be on the same machine where you are installing the suite.

RCU is available only on a Linux or Windows operating system. You can use either the Linux-based RCU or Windows-based RCU to create schemas in any supported database.

The overall performance of an Oracle UCM system is dependent on the speed at which files that are checked into the server can be stored and retrieved. Using a database to store the files that are stored in the server requires that the database can execute both Read and Write commands at speeds similar to a file system. Oracle Secure Files meets this standard. For databases other than Oracle Database, consult your database provider to ensure that the database can achieve your storage and retrieval requirements.

For the latest information about supported databases, see the Oracle Fusion Middleware Supported System Configurations page on Oracle Technology Network at

Before you can configure an Oracle Enterprise Content Management Suite application, you need to use RCU to create a schema for it in the database. You can create the schema before or after you install Oracle WebLogic Server or Oracle Enterprise Content Management Suite. For information about how to create schemas for applications, see Section 1.4, "Creating Oracle Enterprise Content Management Suite Schemas."

1.3.3 Installing Oracle WebLogic Server in a Middleware Home

Oracle Enterprise Content Management Suite requires a Middleware home directory in which Oracle WebLogic Server is installed on your system. If your system does not already have Oracle WebLogic Server, you can install it in a new Middleware home directory, before or after installation of the database and creation of the schemas.

To install Oracle WebLogic Server in a Middleware home:

Insert the Oracle WebLogic Server DVD, or download WebLogic Server 11gR1 (10.3.3) for your platform from either of these web sites:

The 32-bit executable files are bundled with the appropriate JDK version. If you use the 64-bit installer, you will need to invoke the installer with a supported JDK for your platform. This JDK must be installed on your system before you install Oracle WebLogic Server. The JDK must be installed in a directory without spaces in the directory path (not underneath the /Program Files directory in a Windows operating system). For a list of supported JDKs for your operating system, see the Oracle Fusion Middleware Supported System Configurations, described in Section 1.2, "Meeting System Requirements and Certification."

Either run your installer file directly from the DVD, or copy the file to your local system and run it locally, after considering these notes:

Before running the installer on a UNIX operating system that is running XWindows, you need to set your system's DISPLAY environment variable to a valid X Server to redirect the display to a system with suitable graphic capabilities.

If you installed a JDK for your system, set the JAVA_HOME environment variable to the installation location.

If you are installing Oracle WebLogic Server on a 64-bit system and using a 32/64-bit hybrid JDK (such as the HP JDK for HP-UX or SUN JDK for Solaris SPARC), you need to use the -d64 flag when you run the installer.

To validate that your JAVA_HOME environment variable refers to a 64-bit JDK when you use a 32/64-bit hybrid JDK, execute either of the following commands, in which JAVA_HOME is the value of the environment variable:

JAVA_HOME/bin/java -version
JAVA_HOME/bin/java -d64 -version

To run the installer on a 32-bit Linux operating system, use this command:

./wls_linux32.bin

To run the installer on a 32-bit Windows operating system, use this command:

wls_win32.exe

To run the installer on a 64-bit UNIX operating system, use either of these commands:

JAVA_HOME/bin/java -jar wls_generic.jar

JAVA_HOME/bin/java -d64 -jar wls_generic.jar

To run the installer on a 64-bit Windows operating system, use this command:

JAVA_HOME\bin\java -jar wls_generic.jar

Welcome screen

Click Next.

Choose Middleware Home Directory screen

Select Create a new Middleware Home.

Specify a location for your new Middleware home directory, which MW_HOME represents in path names. If this directory already exists on your system, the directory must be empty. If it does not already exist, then the installer creates it.

Note:

Record this location because you will need to provide it during the installation of Oracle Enterprise Content Management Suite.

After installing the adapter, add a line immediately after the localhost line in the %SYSTEMROOT%\system32\drivers\etc\hosts file, with the following format:

IP_addresshostname.domainnamehostname

Replace IP_address with the local IP address of the loopback adapter, hostname with the name of the host, and domainname with the name of the domain.

1.3.5.3 Installing a Loopback Adapter on a Windows Operating System

On a Windows operating system, you can install a loopback adapter on the DHCP server to assign a local IP address to your computer.

To install a loopback adapter on a Windows operating system:

Open Control Panel.

Select Add Hardware.

In the "Welcome" window, click Next.

On the "Is the hardware connected?" window, select Yes, I have already connected the hardware, then click Next.

In the "The following hardware is already installed on your computer" window, in the list of installed hardware, select Add a new hardware device, then click Next.

In the "The wizard can help you install other hardware" window, select Install the hardware that I manually select from a list, then click Next.

In the "From the list of hardware types, select the type of hardware you are installing" window, select Network adapters, then click Next.

In the "Select Network Adapter" window, make the following selections:

Manufacturer: Microsoft

Network Adapter: Microsoft Loopback Adapter

Click Next.

In the "The wizard is ready to install your hardware" window, click Next.

In the "Completing the Add Hardware Wizard" window, click Finish.

Restart your computer.

Right-click My Network Places on the desktop and choose Properties. This displays the Network Connections control panel.

Right-click the connection that was just created. This is usually named Local Area Connection 2. Choose Properties.

On the General tab, select Internet Protocol (TCP/IP), then click Properties.

In the Internet Protocol (TCP/IP) Properties dialog box, click Use the following IP address, and then do the following steps:

IP Address: Enter a nonroutable IP for the loopback adapter, such as one of the following nonroutable addresses:

192.168.x.x (x is any value between 1 and 255)
10.10.10.10

Subnet mask: Enter 255.255.255.0.

Record the values you entered because you will need them later in this procedure.

Leave all other fields empty.

Click OK.

In the Local Area Connection 2 Properties dialog box, click OK.

Close the Network Connections control panel.

Restart your computer.

1.3.5.4 Removing a Loopback Adapter from a Windows Operating System

You can remove a loopback adapter through Control Panel.

To remove a loopback adapter from a Windows operating system:

Start the System control panel.

On the Hardware tab, click Device Manager.

In the Device Manager window, expand Network adapters. You should see Microsoft Loopback Adapter.

Right-click Microsoft Loopback Adapter and select Uninstall.

Click OK.

1.3.6 Installing on a Non-Networked Computer

You can install Oracle Enterprise Content Management Suite on a non-networked computer, such as a laptop. Because a non-networked computer has no access to other computers, you have to install all the components that you need on the computer.

1.3.7 Installing on a Multihomed Computer

You can install Oracle Enterprise Content Management Suite on a multihomed computer. A multihomed computer is associated with multiple IP addresses. This is typically achieved by having multiple network cards on the computer. Each IP address is associated with a host name; additionally, you can set up aliases for each host name.

The installer picks up the fully qualified domain name from the first entry in the hosts file:

UNIX operating system

/etc/hosts

Windows operating system

%SYSTEMROOT%\system32\drivers\etc\hosts

For example, the installer would pick up myhost1.example.com for configuration if your file contains the following entries:

For specific network configuration of a system component, refer to the individual component's configuration documentation.

1.4 Creating Oracle Enterprise Content Management Suite Schemas

Oracle Enterprise Content Management Suite requires that an application schema exists in the database before configuration of the application. You must run Repository Creation Utility (RCU) to create application schemas in the database, which must be up and running before you start RCU. You can create application schemas before or after you install Oracle WebLogic Server or Oracle Enterprise Content Management Suite.

To create Oracle Enterprise Content Management Suite Schemas:

Insert the Repository Creation Utility DVD, and then start RCU from the bin or BIN directory in the rcuHome directory:

UNIX operating system

cd rcuHome/bin
./rcu

Windows operating system

cd rcuHome\BIN
rcu.bat

You can also download a ZIP file containing Repository Creation Utility from either of these web sites:

For connecting to an Oracle Database instance, provide the following information:

Host Name: Specify the name of the machine on which your database resides, in the format host.example.com.

For Oracle Real Application Cluster (RAC) databases, specify the Virtual IP name or one of the node names.

Port: Specify the database listen port number. The default port number for an Oracle Database instance is 1521.

Service Name: Specify the service name for the database. Typically, the service name is the same as the global database name.

If you do not know the service name for your database, you can obtain it from the SERVICE_NAMES parameter in the database's initialization parameter file. If this file does not contain the SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the DB_NAME and DB_DOMAIN parameters. Another way to find the service name is to log in to the database and as SYS and run the following command:

show parameter service_name

For Oracle RAC databases, specify the service name of one of the nodes in this field; for example, sales.example.com.

Username: Specify the user name of the database administrator.

Specify the name of an Oracle Database user with DBA or SYSDBA privileges. The default user name with SYSDBA privileges is SYS.

Password: Specify the password for your database user.

Role: Select a database user role from the list. SYS requires the SYSDBA role.

Click Next. The Checking Global Prerequisites dialog box appears. If you have any prerequisite errors, the Database Connection Details screen displays details about the errors. Fix any errors, then click Next again.

After the checking is complete with no errors, click OK to dismiss the dialog box and go to the next screen.

Select Components screen

Near the top of the screen, select Create a New Prefix, and specify a prefix, or leave the default prefix, DEV.

For Oracle Database, the prefix can contain from 1 to 12 alphanumeric characters (0-9, a-z, or A-Z).

Expand Enterprise Content Management in the Components list, and then select one or more of the following applications:

If you have any validation errors, the Map Tablespaces screen displays details about the errors. You can track errors in log files, such as irm.log and rcu.log. This screen displays the log locations. Fix any errors, then click Next again.

After the tablespaces are created with no errors, click OK to dismiss the dialog box.

Summary screen

Click Create. The CREATE dialog box appears.

If you have any schema creation errors, the Summary screen displays details about the errors. Fix any errors, then click Next again.

After RCU creates the schema or schemas with no errors, click OK to dismiss the dialog box.

Completion Summary screen

Click Close.

Note:

The user account created for a schema has a default expiration date of six months after creation. The database administrator should change the expiration of the user account to a later date. To view the expiration data for an account, use the SQL statement SELECT * FROM all_users or SELECT * FROM dba_users.

The ECM Oracle home contains the binary and library files necessary for Oracle Enterprise Content Management Suite. ECM_ORACLE_HOME represents the ECM Oracle home in path names.

When you install Oracle Enterprise Content Management Suite, you perform a base installation of the following products in an ECM Oracle home directory (represented by ECM_ORACLE_HOME in path names) under the Middleware home directory on your system:

Oracle Universal Content Management (Oracle UCM)

Oracle Inbound Refinery (Oracle IBR)

Oracle Imaging and Process Management (Oracle I/PM)

Oracle Information Rights Management (Oracle IRM)

Oracle Universal Records Management (Oracle URM)

After installation, you can deploy one or more of these products to an Oracle WebLogic Server domain, as applications.

Note:

For document conversions on a Solaris SPARC platform, Oracle I/PM requires the GNU Compiler Collection (GCC) package 3.4.2 or later in the /usr/local/packages directory.

Install this package on the Solaris operating system that will run Oracle I/PM. You can download GCC from the Sunfreeware web site at

You also need to set the LD_LIBRARY_PATH environment variable to /usr/local/packages/gcc-3.4.2/lib before starting the Oracle I/PM Managed Server. If you are using a later version of GCC, set that version instead of 3.4.2.

1.5.1 Providing the Location of an Inventory Directory on a UNIX System

If you are installing on a UNIX operating system, and if this is the first time any Oracle product is being installed on your system with the Oracle Universal Installer, you will be asked to provide the location of an inventory directory. This is where the installer will set up subdirectories and maintain inventory data for each Oracle product that is installed on the machine.

To provide the location of an inventory directory on a UNIX system:

On the Specify Inventory Directory screen, specify the location of the inventory directory.

This screen appears only on a UNIX operating system, for the first installation by Oracle Universal Installer. The installer will use the inventory directory to keep track of all Oracle products installed on the machine.

Take the action requested in the Inventory Location Confirmation dialog box.

This dialog box asks you to run the following script as the root user:

inventory_directory/createCentralInventory.sh

If you do not have root access on the machine but want to continue with the installation, select Continue installation with local inventory.

1.5.2 Installing Oracle Enterprise Content Management Suite

You can install Oracle Enterprise Content Management Suite before or after you create schemas for the suite's applications. You can deploy and configure one or more of these applications any time later by creating or extending an Oracle WebLogic Server domain.

To install Oracle Enterprise Content Management Suite:

Start the Oracle Enterprise Content Management Suite installer, which is on Disk 1 of the suite's media.

If you are installing the suite from a ZIP file, you need to unzip the file to a directory. Disk 1 will be a subdirectory of the suite's media directory.

The installer requires the location of a Java Runtime Environment (JRE) on your system. A JRE was installed with Oracle Fusion Middleware. Table 1-2 shows the default JRE locations.

Table 1-2 Default JRE Locations

Operating System

Production Environment

Development Environment

UNIX

MW_HOME/jrockit_160_17_Rnn.n.n-nnn/jre

MW_HOME/jdk160_18/jre

Windows

MW_HOME\jrockit_160_17_Rnn.n.n-nnn\jre

MW_HOME\jdk160_18\jre

You can either use the -jreLoc option or allow the installer to prompt for the directory containing bin/java:

UNIX operating system

cd ecm_media_loc/Disk1
./runInstaller -jreLoc jre_location

Note:

Starting the installer as the user root is not supported.

Windows operating system

cd ecm_installer_loc
setup.exe -jreLoc jre_location

Welcome screen

Click Next.

Prerequisite Checks screen

After the prerequisite checking is complete with no errors, click Next.

Click Save to save the response file, and then click Install to start the installation.

Installation Progress screen

After the progress reaches 100%, click Next to go to the last screen.

Installation Completed screen

Click Save to save the installation configuration, and then click Finish.

1.6 Configuring Oracle Enterprise Content Management Suite

After you have successfully run the installer, you can deploy and configure the following Oracle Enterprise Content Management Suite products as applications:

Oracle Universal Content Management (Oracle UCM)

Oracle Inbound Refinery (Oracle IBR)

Oracle Imaging and Process Management (Oracle I/PM)

Oracle Information Rights Management (Oracle IRM)

Oracle Universal Records Management (Oracle URM)

Note:

The Oracle I/PM product deployment provides for up to 10 GB of disk space to be used to stage simultaneous document uploads through the user interface. This limit exists to provide an upper limit to thwart malicious server attacks.

To configure one or more of these applications, you can create an Oracle WebLogic Server domain, which includes a Managed Server for each deployed application and one Administration Server. Each of these servers is an Oracle WebLogic Server instance.

Note:

Each of these applications needs to run in its own Managed Server or its own cluster of Managed Servers. You cannot deploy Oracle UCM, Oracle IBR, Oracle I/PM, Oracle IRM, or Oracle URM to a Managed Server or cluster that already has another application deployed.

Before you start the Administration Server or a Managed Server, you need to perform some additional configuration and post-installation configuration tasks. This section includes descriptions of the following configuration tasks.

1.6.1 Creating an Oracle WebLogic Server Domain

You can create a domain to include a Managed Server for one or more applications (one Managed Server each) and then extend the domain with Managed Servers for one or more other applications. For example, for Oracle I/PM, you can extend the domain with Oracle SOA Suite, which includes Oracle BPEL Process Manager.

Select Generate a domain configured automatically to support the following products and one or more of these products:

Oracle Universal Records Management Server

Oracle Information Rights Management

Oracle Universal Content Management - Inbound Refinery

Oracle Universal Content Management - Content Server

Oracle Imaging and Process Management

When you select Oracle Imaging and Process Management, you should also select Oracle Universal Content Management - Content Server. Oracle I/PM automatically selects Oracle UCM RIDC. If you deselect this automatic selection, Oracle Imaging and Process Management will also be deselected.

When you select any Oracle ECM application on the Select Domain Source screen, Oracle Enterprise Manager and Oracle JRF are automatically selected. If you deselect any of these items that are automatically selected, the Oracle ECM applications will also be deselected.

Click Next.

Specify Domain Name and Location screen

Enter the name of the domain you want to create in the Domain name field.

The default location for the domain follows (MW_HOME represents the Middleware home directory):

UNIX operating system

MW_HOME/user_projects/domains/

Windows operating stem

MW_HOME\user_projects\domains\

You can specify a different location in the Domain location field.

Note:

Record the domain name and location from this screen because you will need them later to start the Administration Server.

In the Application location field, you can specify a location for any applications you are deploying. The default location follows:

UNIX operating stem

MW_HOME/user_projects/applications/

Windows operating stem

MW_HOME\user_projects\applications\

Click Next.

Configure Administrator User Name and Password screen

The User name field has the default administrator user name, weblogic, which you can change to another administrator user name.

In the User password field, enter the password for the administrator user.

Note:

Record the administrator user name and password from this screen because you will need them later to start the Managed Servers and to access the domain through the Oracle WebLogic Server Administration Console or Oracle Enterprise Manager Fusion Middleware Control.

Click Next.

Configure Server Start Mode and JDK screen

Under WebLogic Domain Startup Mode, leave Development Mode selected.

Under JDK Selection, leave Available JDKs and the default JDK selected, which is Sun SDK 160_18 for development mode or, on a 64-bit system, the JDK you installed.

Click Next.

Configure JDBC Component Schemas screen

Configure a component schema in the following fields:

Component Schema: Select a component schema row.

Vendor: Leave Oracle selected.

Driver: Leave the default driver selected.

Schema Owner: Enter the user name of the application schema owner, specified during schema creation with Repository Creation Utility (RCU).

Schema Password: Enter the schema password.

DBMS/Service: Enter the name of the database instance if Oracle's Driver (Thin) for Instance connections is selected in the Driver field, or enter the service name (global database name) if Oracle's Driver (Thin) for Service connections is selected in the Driver field.

Specify the database that contains the application schema or schemas.

For Oracle RAC databases, specify the service name of one of the nodes in this field. For example: sales.example.com.

Host Name: Specify the name of the machine on which your database resides, in the format host.example.com.

For Oracle RAC databases, specify the Virtual IP name or one of the node names as the host name.

Listen Port: Leave the default number, which is 1521 for Oracle Database, or specify the listen port for your database if it is different.

Click Next.

Test Component Schema screen

Verify that the connections to your data sources are successful, and click Next.

Select Optional Configuration screen

Select Administration Server if you want to configure SSL for the Administration Server.

If you want to change the configuration of SSL for the Administration Server, you can select SSL enabled When you select SSL enabled, the SSL port is set to 7002 by default in the SSL Listen Port field. If SSL enabled is selected, you can change the SSL listen port value.

Click Next.

Configuration Summary screen

Check your configuration and make any corrections or updates by following the instructions on the screen. When the configuration is satisfactory, click Create.

Creating Domain screen

When the domain is successfully created, click Done.

The following operations should have completed successfully:

Creation of an Oracle WebLogic Server domain, with an Administration Server

Creation of a Managed Server for each application that you selected on the Select Domain Source screen

1.6.2 Increasing the Java VM Heap Size for Managed Servers

You need to increase the size of the heap allocated for the Java Virtual Machine (VM) on which each Managed Server runs to at least 1 gigabyte. If your system does not have enough memory for 1 GB of RAM for the Java VM, then you will get an error. If you do not increase the Java VM heap size, then Oracle support and development will not accept any escalation of runtime issues, especially out-of-memory issues.

There are two common ways to adjust the runtime memory parameters for a Managed Server:

This method is required if the managed server process will be run directly from the command line. For more information about running Managed Servers from the command line, see Section 1.14, "Starting Managed Servers."

You can set server startup parameters with the Oracle WebLogic Server Administration Console. This is the preferred approach for setting startup parameters because it ensures that the parameters are correctly pushed to each server, and it avoids problems that might occur during manual editing of server startup scripts. To increase the Java VM heap size to at least 1 gigabyte, you set the value of the -Xmx parameter.

To set server startup parameters for Managed Servers with the Administration Console:

Log in to the Oracle WebLogic Server Administration Console.

Click Environment under Domain Structure, on the left.

Click Servers on the Summary of Environment page.

Set the memory parameters for each Managed Server:

Click the name of a Managed Server in the Servers table.

On the Configuration tab, in the second row of tabs, click Server Start.

In the Arguments box, paste a string that specifies the memory parameters.

Table 1-3 shows parameters to specify for Sun and JRockit Java VMs on UNIX and Windows operating systems. Other Java VMs may have different values.

1.6.2.2 Setting the USER_MEM_ARGS Environment Variable in the Startup Script for a Managed Server

You can set server startup parameter for a Managed Server by setting the USER_MEM_ARGS environment variable in its startup script. To increase the Java VM heap size to at least 1 gigabyte, you set the value of the -Xmx parameter.

To set the USER_MEM_ARGS Environment Variable in the Startup Script for a Managed Server:

Table 1-3 shows parameters to specify for Sun and JRockit Java VMs on UNIX and Windows operating systems. Other Java VMs may have different values.

1.6.3 Setting Up Fonts on a UNIX Operating System

On a UNIX system, you need to make sure TrueType fonts are set up for Oracle IBR and Oracle UCM Dynamic Converter. If you are using a language other than English, you also need to set up fonts for national language support.

1.6.3.1 Setting Up TrueType Fonts on a UNIX System

For Oracle IBR and Oracle UCM Dynamic Converter to work correctly on a UNIX operating system, you need to set up TrueType fonts on the machine where Oracle IBR or the Dynamic Converter is running. If these fonts are not available on your system, you need to install them. Then you can configure Oracle IBR with the path to the font directory.

Some standard font locations on different UNIX platforms follow:

Solaris SPARC: /usr/openwin/lib/X11/fonts/TrueType

Note:

For document conversions on a Solaris SPARC platform, Oracle I/PM requires the GNU Compiler Collection (GCC) package 3.4.2 or later in the /usr/local/packages directory.

Install this package on the Solaris operating system that will run Oracle I/PM. You can download GCC from the Sunfreeware web site at

You also need to set the LD_LIBRARY_PATH environment variable to /usr/local/packages/gcc-3.4.2/lib before starting the Oracle I/PM Managed Server. If you are using a later version of GCC, set that version instead of 3.4.2.

AIX: /usr/lpp/X11/lib/X11/fonts/TrueType

HP-UX Itanium: /usr/lib/X11/fonts/TrueType

To set the path to the font directory in Oracle IBR:

Log in to Oracle IBR.

Select Conversion Settings, then Third-Party Application Settings, and then General OutsideIn Filter Options.

Click Options.

Enter the path to the TrueType fonts in the Path to fonts field.

For example:

/usr/share/x11/fonts/FTP

Click Update.

Restart Oracle IBR.

1.6.3.2 Installing Fonts for National Language Support on a UNIX System

For languages other than English, the following installation steps need to be done on a UNIX operating system before you start a Managed Server:

Copy MW_HOME/oracle_common/jdk/jre/lib/fonts to the /jre/lib/fonts directory in the Sun JDK installation directory for the Middleware home.

Copy MW_HOME/oracle_common/jdk/jre/lib/fonts to the /jre/lib/fonts directory in the Oracle JRockit JDK directory for the Middleware home.

1.6.3.3 Installing Fonts for National Language Support on a UNIX System

For languages other than English, the following installation steps need to be done on a UNIX operating system before you start a Managed Server:

Copy MW_HOME/oracle_common/jdk/jre/lib/fonts to the /jre/lib/fonts directory in the Sun JDK installation directory for the Middleware home.

Copy MW_HOME/oracle_common/jdk/jre/lib/fonts to the /jre/lib/fonts directory in the Oracle JRockit JDK directory for the Middleware home.

Oracle UCM, Oracle IBR, Oracle I/PM, and the Oracle I/PM Advanced Viewer for clients use Outside In Technology (OIT), which requires certain libraries that are not part of Oracle ECM. Before an Oracle UCM, Oracle IBR, or Oracle I/PM Managed Server is started, you need to install the libraries for your platform. For a UNIX platform, you also need to set an environment variable to reference the libraries in the library path for the user who will start the Managed Server.

1.6.4.1 Installing Libraries for Outside In Technology on UNIX Platforms

Before you start an Oracle UCM, Oracle IBR, or Oracle I/PM Managed Server, you need the libraries required for your platform are available on your system.

Many of the required libraries are normally installed on the machine, including the C, math, X11, dynamic loader, and pthreads libraries, among others. The libgcc_s and libstdc++ libraries are part of the GNU Compiler Collection (GCC) package.

OIT requires the following libraries for the specified UNIX platform. The libraries in bold are part of the GCC package 3.4.2 or later.

Solaris Sparc 32-bit requires GCC package 3.4.2 or later, which you can download from the Sunfreeware web site at

If a libgcc_s or libstdc++ library is required for your platform, install the GCC package in the /usr/local/packages/gcc-3.4.2/lib directory in a Solaris Sparc system or the /usr/local/packages/gcc-3.3.6/lib or directory in an HPUX ia64 system, on the machine where Oracle I/PM or Oracle UCM will run. If you are using a later version of GCC, specify that version instead of 3.4.2 or 3.3.6.

OIT requires the following libraries for the specified UNIX platform. The libraries in bold are part of the GCC package.

Before Oracle Inbound Refinery or the Oracle UCM Dynamic Converter uses Outside In Technology for document and image conversions, the following environment variables must be set in the or Oracle I/PM or Oracle UCM Managed Server on the specified UNIX platforms:

Environment variables for library paths for Oracle I/PM

Solaris Sparc:

LD_LIBRARY_PATH=/usr/local/packages/gcc-3.4.2/lib

If you are using a later version of GCC, specify that version instead of 3.4.2.

The Dynamic Converter on HP-UX Itanium needs the 3.3.6 version of the GCC libraries installed before the Oracle UCM server is started.

DISPLAY environment variable

On a UNIX operating system running XWindows, when redirecting the display to a system with suitable graphic capabilities, export DISPLAY to a valid X Server before starting the Oracle I/PM or Oracle IBR Managed Server or the Oracle UCM Dynamic Converter.

1.6.4.3 Downloading Visual C++ Libraries for a Windows Operating System

OutsideIn Technology requires the Visual C++ libraries included in the Visual C++ Redistributable Package for a Windows operating system. Three versions of this package (x86, x64, and IA64) are available from the Microsoft Download Center at

Search for and download the version of the package that corresponds to the version of your Windows operating system:

vcredist_x86.exe

vcredist_x64.exe

vcredist_IA64.exe

The required version of each of these downloads is the Microsoft Visual C++ 2005 SP1 Redistributable Package. The redistributable module that Outside In requires is msvcr80.dll.

1.7 Performing Postinstallation Configuration

After installing Oracle Enterprise Content Management Suite and configuring one or more of its applications on Oracle WebLogic Server, you need to start the Administration Server, complete the application configurations, start the Managed Servers and Node Manager, and verify the configuration. The following topics describe these postinstallation tasks:

1.8 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 script (from the bin directory under the domain home directory:

UNIX operating system

cd MW_HOME/user_projects/domains/domain_name/bin
./startWebLogic.sh

Note:

On a Linux operating system, the shell is going to stay open.

Windows operating system

MW_HOME\user_projects\domains\domain_name\startWebLogic.cmd

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

Access the Oracle WebLogic Server Administration Console at

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.

1.9 Completing the Oracle UCM Configuration

You can Complete the Oracle UCM configuration on the postinstallation configuration page in Oracle Content Server. Before you can use Oracle IBR with Oracle UCM, you need to configure it for document and image conversion to work with Oracle Content Server.

This field accepts wildcards in the value, like 10.*.*.*. You can change this value later by setting SocketHostAddressSecurityFilter in DOMAIN_HOME/ucm/cs/config/config.cfg and restarting Oracle Content Server.

If you want to set up a provider from Oracle IBR back to Oracle Content Server, use the default value, 5555, for Server Socket Port, or enter an unused port number.

You can change this value later by setting IntradocServerPort in DOMAIN_HOME/ucm/cs/config/config.cfg and restarting Oracle Content Server.

This value should be the IP address of the Oracle Content Server instance or instances that will send jobs to Oracle IBR, not the IP address of Oracle IBR. (In a test or demo environment, these IP addresses could be the same.)

This field accepts wildcards in the value, like 10.*.*.*. You can change this value later by setting SocketHostAddressSecurityFilter in DOMAIN_HOME/ucm/ibr/config/config.cfg and restarting Oracle IBR.

This value is the number of the port for calling top-level services. Changing this field value changes the IntradocServerPort entry in DOMAIN_HOME/ucm/ibr/config/config.cfg. The default IntradocServerPort value is 5555.

1.11 Completing the Oracle I/PM Configuration

Oracle I/PM uses Oracle Universal Content Management (Oracle UCM) for its repository. Your system needs to have Oracle UCM configured before the configuration of Oracle I/PM.

The user who logs in first to an Oracle Imaging and Process Management (Oracle I/PM) Managed Server is provisioned with full security throughout the server. When this user first logs in, Oracle I/PM provides a user interface to complete the configuration, including connecting to a repository or repositories and, optionally, to a Business Process Execution Language (BPEL) server.

Note:

This section describes how to complete the Oracle I/PM configuration on a development system. In a production system, Oracle Enterprise Content Management Suite applications need to use an external Lightweight Directory Application Protocol (LDAP) authentication provider rather than the Oracle WebLogic Server embedded LDAP server, which is part of the default configuration. If you want to reassociate the identity store for Oracle I/PM with an external LDAP authentication provider, it is easier to do this before you complete the configuration of the Oracle I/PM Managed Server and before you connect it to the Oracle Universal Content Management (Oracle UCM) repository. For more information, see "Reassociating the Identity Store with an External LDAP Authentication Provider" in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.

You also need to set the LD_LIBRARY_PATH environment variable to /usr/local/packages/gcc-3.4.2/lib before starting the Oracle I/PM Managed Server. If you are using a later version of GCC, set that version instead of 3.4.2.

The first user to connect to the Oracle I/PM system is registered as the Oracle I/PM administrator.

1.11.2 Connecting to the Oracle UCM Repository

Before Oracle I/PM can use the Oracle UCM repository, you need to configure a connection to Oracle Content Server. You can create a connection to it from Oracle I/PM.

To connect to an Oracle UCM repository:

Open a web browser, and navigate to this web site:

http://hostname:16000/imaging

Log in with the administrator user name and password.

Navigate to the Manage Connections tray, and select Create Content Server Connection from the list.

Enter a name for the connection on the Basic Information page, and optionally a description, and then click Next.

Enter the following values on the Connection Settings page:

Repository Proxy:weblogic

Port: The IDC port of the Oracle UCM instance, 4444 by default

If the Oracle UCM server is on the same machine as the Oracle IPM server, select Use Local Content Server. If the servers are not installed on the same machine, you will need to configure the Oracle UCM machine name as part of the Content Server Pool.

Click Next.

Enter a Connection Security value for the connection.

Select which users and groups should have permission to access, modify, delete, or grant others access to this connection definition. At least one user or group must have the grant access permission.

Click Next.

At the Summary screen, click Submit.

1.11.3 Configuring the AgentUser and GDFontPath MBeans

Three agents run outside of Oracle I/PM, so they need to log into the Oracle I/PM system using a standard user in the security store. Oracle I/PM assigns security to this user name, which you need to configure as the agent user, by setting the AgentUser MBean. The user selected for the agent user is not allowed to sign on using the Oracle I/PM user interface.

For conversions to work correctly on a UNIX operating system, it needs to have TrueType fonts available. If these fonts are not available on your system, you need to install them. To set the font path on a UNIX operating system, you need to configure the GDFontpath MBean.

You can configure these MBeans through the System MBean Browser in Oracle Enterprise Manager Fusion Middleware Control.

To configure the AgentUser and GDFontPath MBeans:

Access the Oracle I/PM domain in Oracle Enterprise Manager 11g Fusion Middleware Control at the following URL:

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 the navigation tree on the left, expand Application Deployments, and then click imaging (IPM_server1).

On the Application Deployment menu, select System MBean Browser.

In the navigation tree on the System MBean Browser page, under Configuration MBeans, close the com.bea folder.

Expand the oracle.imaging folder, under Application Defined MBeans.

Expand the Server: IPM_server1 and config folders.

Click config.

Set the value of the AgentUser attribute to a user name that already exists in the Oracle WebLogic Server LDAP authentication provider, click Apply, and then click Return.

The selected user for AgentUser cannot log in to the Oracle I/PM application through its user interface.

On a UNIX operating system, set the value of the GDFontPath attribute to the location of your True Type Fonts (TTF) files; for example:

/usr/share/X11/fonts/TTF

For systems on which Oracle WebLogic Server includes a JDK, you can find some TTF files in the JDK/jre/lib/fonts directory.

Some standard font locations on different UNIX platforms follow:

Solaris SPARC: /usr/openwin/lib/X11/fonts/TrueType

Note:

For document conversions on a Solaris SPARC platform, Oracle I/PM requires the GNU Compiler Collection (GCC) package 3.4.2 or later in the /usr/local/packages directory.

Install this package on the Solaris operating system that will run Oracle I/PM. You can download GCC from the Sunfreeware web site at

You also need to set the LD_LIBRARY_PATH environment variable to /usr/local/packages/gcc-3.4.2/lib before starting the Oracle I/PM Managed Server. If you are using a later version of GCC, set that version instead of 3.4.2.

AIX: /usr/lpp/X11/lib/X11/fonts/TrueType

HP-UX Itanium: /usr/lib/X11/fonts/TrueType

Click Apply.

Restart the Oracle I/PM Managed Server.

1.12 Completing the Oracle IRM Configuration

Before logging in to the Oracle Information Rights Management (Oracle IRM) Management Console or using Oracle IRM Desktop, you need to complete the Oracle IRM configuration, as these topics describe:

1.12.1 Setting the Server URL Configuration Parameter for Oracle IRM

You can set the Server URL configuration parameter to an Oracle IRM Managed Server on the General Settings page for Oracle IRM in Fusion Middleware Control.

Caution:

The Server URL value is embedded into every sealed document, and Oracle IRM Desktop uses this value to identify and connect to an Oracle IRM server to retrieve licenses. This setting must not be changed after any documents have been sealed using this server, or no one will be able to access the documents.

To set the Server URL configuration parameter:

Start Fusion Middleware Control by navigating to the following web site:

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.

From the farm navigation tree in Fusion Middleware Control, expand Content Management and Information Rights Management, and then click irm.

From the IRM menu, select Administration and then General Settings.

Fusion Middleware Control displays the General Settings page.

In the Server URL field, enter the URL to access the Oracle IRM Managed Server.

For a simple installation where the Managed Server is directly accessible to Oracle IRM Desktop, this value will be the URL of the Managed Server; for example:

https://managedServerHost:managedServerPort/irm_desktop

The managedServerHost value is the name of the host where the Managed Server is running, such as myhost.example.com. The default SSL port for Oracle IRM (managedServerPort value) is 16101.

Click Apply.

1.12.2 Configuring a Key Store for Oracle IRM

The Oracle IRM Java EE application uses a cryptographic key to wrap (encrypt) and unwrap (decrypt) Oracle IRM sealed content keys stored in the database. This wrapping key, oracle.irm.wrap, must be generated and stored in a key store before contexts can be created.

Access to the key store requires a password, and access to the wrapping key requires an additional password. Both passwords are stored in the credential store.

When prompted for the certificate details, use the suggested default value, unknown. When prompted by keytool, choose appropriate passwords for the key store and the generated key.

Note:

You should choose the most appropriate cryptographic algorithm, key size, and key store for the target platform. For most platforms, the Advanced Encryption Standard (AES) key wrapping algorithm should be used. Other platforms require an RSA key wrapping algorithm, which this procedure uses.

1.12.2.2 Setting the Key Store Location

The Oracle IRM server configuration needs to be updated so that it can locate the key store file. You can set the key store location in the server configuration with either Fusion Middleware Control, on the Oracle IRM General Settings page, or with the WebLogic Scripting Tool (WLST) connect and setIRMKeyStore commands.

The suggested location for the key store is in a directory under the domain home:

UNIX operating system

MW_HOME/user_projects/domains/domain_name/config/fmwconfig

Windows operating system

MW_HOME\user_projects\domains\domain_name\config\fmwconfig

Placing the key store in this location ensures that the key store file is backed up when the domain and corresponding credential store files are backed up.

To set the key store location with Fusion Middleware Control:

Start Fusion Middleware Control at the following URL:

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.

From the farm navigation tree in Fusion Middleware Control, expand Content Management and Information Rights Management, and then click irm.

From the IRM menu, select Administration and then General Settings.

Enter JKS for the key store type.

In the Keystore field on the General Settings page, enter a key store path:

UNIX operating system

MW_HOME/user_projects/domains/domain_name/config/fmwconfig/irm.jks

Windows operating system

MW_HOME\user_projects\domains\domain_name\config\fmwconfig\irm.jks

On the General Settings page, you can also specify other settings for Oracle IRM.

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

You will be prompted for the key store type and key store path.

For the key store type, enter one of the following values:

JCEKS if you are using an AES key

JKS if you are using an RSA key-pair

For the key store path, enter one of the following values.

Key store path for an AES key store:

UNIX operating system

MW_HOME/user_projects/domains/domain_name/config/fmwconfig/irm.jceks

Windows operating system

MW_HOME\user_projects\domains\domain_name\config\fmwconfig\irm.jceks

Key store path for an RSA key store:

UNIX operating system

MW_HOME/user_projects/domains/domain_name/config/fmwconfig/irm.jks

Windows operating system

MW_HOME\user_projects\domains\domain_name\config\fmwconfig\irm.jks

1.12.2.3 Adding Key Store Passwords to the Credential Store

You must add passwords for the Oracle IRM key store to the credential store with WLST commands. A key store password and a password for the generated key were set when the key store was created. These passwords are required by the Oracle IRM server.

In the connect command, substitute the correct values for username and password.

In the createCred command, substitute for password the password that was used for creating the key and key store.

The "dummy" parameter passed to the createCred command is the user name parameter. The key store does not use a user name, so this value is ignored. This is why the value is set as dummy.

It is normal for the creatCred command to return the text "Already in Domain Runtime Tree". This text does not signify an error.

1.12.3 Configuring SSL for a Development Environment

For a development environment, you can configure one-way SSL with a server-specific certificate. One-way SSL means that only the server certificate passes from the server to the client but not the other way around. After you configure one-way SSL for a development environment on the server, you must configure every machine running Oracle IRM Desktop to accept the server certificate.

1.12.3.1 Configuring One-Way SSL with a Server Certificate

You can configure one-way SSL with a server certificate for the Oracle IRM Managed Server so that Oracle IRM Desktop can be configured to trust the certificate.

To configure one-way SSL with a server certificate:

Run the following script to set the environment:

UNIX operating system

cd MW_HOME/wlserver_10.3/server/bin
./setWLSEnv.sh

For the Java and Oracle WebLogic Server tools to work, you should have the weblogic.jar file in the MW_HOME/wlserver_10.3/server/lib directory.

Windows operating system

MW_HOME\wlserver_10.3\server\bin\setWLSEnv.cmd

For the Java and Oracle WebLogic Server tools to work, you should have the weblogic.jar file in the MW_HOME\wlserver_10.3\server\lib directory.

Use the CertGen utility to create a server-specific, private key and certificate, as follows (in a single command line):

For mykeypass, substitute a password for the key file, and for hostname, substitute the name of the machine where Oracle IRM is deployed. You should use the same name while accessing Oracle Web Services. For example, to generate the server certificate for a machine named myhost.us.example.com, the command would be as follows (in a single command line):

This command will generate a server certificate for the machine myhost.us.example.com.

The parameter -cn "machine-name" must be set to the fully qualified domain name of the Oracle IRM server, which is the name that Oracle IRM will use to connect to the machine. Verify that the certificate has been issued to the machine name you specified.

CertGen creates a unique and secret Private Key for Oracle IRM and a Self-Signed Root Certificate.

Run the ImportPrivateKey utility to package the Private Key and Self-Signed Root Certificate into a keystore, as follows (in a single command line):

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.

After you create a server certificate, you must install it on every machine running Oracle IRM Desktop. Then you can import the certificate into Oracle IRM Desktop so that it will trust the certificate and not show prompts when it connects to the Oracle IRM Managed Server.

On each client machine that is running Oracle IRM Desktop, double-click the certificate file to open the Certificate window, and then click Install Certificate to start the Certificate Import Wizard.

For a Windows operating system, the certificate file needs to be copied to the client machine that accesses this server through a browser.

For a UNIX operating system that is accessing a web site over SSL rather than using the IRM Desktop, follow the procedure required for your operating system to trust the certificate.

On every machine running Oracle IRM Desktop, in the Certificate Import Wizard, explicitly select a certificate store for Trusted Root Certification Authorities. The root certificate must be trusted on all client computers that will access the server.

On a Windows operating system, install the certificate under Trusted Root Certification Authorities in Internet Explorer.

1.12.4 Accessing the Oracle IRM Management Console

When the Oracle IRM Managed Server is in running mode, the Oracle IRM application is deployed and ready to be accessed through the Oracle IRM Management Console:

https://managedServerHost:managedServerPort/irm_rights

1.13 Completing the Oracle URM Configuration

To complete the configuration of Oracle URM, restart Oracle Content Server. The configuration of Oracle UCM with the Oracle URM template automatically completes the postinstallation configuration of Oracle URM, with an installation level of Minimal.

For details about the components enabled for each option, click the Info icon.

Element

Description

Installation Level

The type of configuration to be enabled. Options are:

Minimal

Typical

DoD Baseline

DoD Classified

Custom

Features

This section contains a list of features that can be enabled when using the Custom option. Default features are enabled when installation levels are chosen.

These features include:

Related Content

Audit Trigger

Subject to Review

Revision Dates

Security Markings

Email Fields

DoD Configuration

Classified Topics

FOIA/Privacy Act

Disposition Actions

This section contains the disposition actions which can be used for content. They include:

Activate

Rescind

Approve Deletion

Obsolete

Expire

Destroy

Cancel

Cutoff

1.13.2 Completing the Setup Checklist for Oracle URM

After the installation and configuration of Oracle URM on an Oracle WebLogic Server Managed Server, you need to complete the Setup Checklist page before you can set up retention policies and procedures. This page is used to set global options for aspects of the retention management system.

If the configuration tasks on this page are not completed, a warning message with a link to this page appears on the home page of the Oracle Content Server system. Click the link to display this page.

Selecting any option in this list displays a detailed explanation of the option's purpose. The options available on the page depend on your installation level:

Minimal

Typical

DoD Baseline

DoD Classified

Custom

Element

Description

Set Configuration Variables

Contains directions on how to set essential configuration variables.

Configure Installation

Used to configure optional components and metadata fields. Select from preset configurations to choose the features that are needed.

Define Defaults

Used to define the default for audit trails, template locations, and metadata for content that is automatically checked in on a periodic basis. You can configure metadata for Audit Entries and for Screening reports.

Clicking an option brings up a check in page where you can edit the fields to be used as defaults.

Configure Security Settings

Used to define the security settings including roles, rights, and access control list use. This link opens the Admin Applets. Click the User Applet to configure security.

Configure Retention Management Settings

Used to configure many of retention management options such as supplemental markings, triggers, and reports. Clicking this option displays the Configure Retention Settings page.

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:

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

1.16 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, WebLogic 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.

To test a newly set up Oracle UCM instance:

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

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.

1.17 Deinstalling Oracle Enterprise Content Management Suite

Deinstalling Oracle Enterprise Content Management Suite from your system involves the following tasks:

Use the instructions provided in this section for removing the software. If you try to remove the software manually, you may experience problems when you try to reinstall the software again at a later time. Following the procedures in this section will ensure that the software is properly removed.

1.17.1 Stopping Oracle Fusion Middleware

Before deinstalling Oracle Fusion Middleware software components, you should stop all servers and processes.

Stop each Oracle WebLogic Server Managed Server with the StopManagedWebLogic script, as follows:

If you have any prerequisite errors, the Database Connection Details screen displays details about the errors. Fix any errors, and click Next again.

After the checking is complete with no errors, click OK to dismiss the screen.

Select Components screen

Select a schema prefix, and then select the name of each schema you want to drop from the repository.

Click Next. The Checking Prerequisites screen appears.

If you have any prerequisite errors, the Select Components screen displays details about the errors. Fix any errors, and click Next again.

After the checking is complete with no errors, click OK to dismiss the screen.

Summary screen

Click Drop. A DROP screen appears.

If you have any drop errors, the Summary screen displays details about the errors. Fix them, and click Next again.

Note:

If your database is running on a Windows operating system, ensure that previous sessions accessing the tablespace are closed before the drop. After the drop, you might need to manually delete the dbf files.

After the schemas are dropped with no errors, click OK to dismiss the screen.

Completion Summary screen

Click Close.

1.17.3 Deinstalling Oracle Enterprise Content Management Suite

The deinstaller attempts to remove the ECM Oracle home from which it was started. Before you remove the Oracle home for Oracle Enterprise Content Management Suite, make sure that it is not in use by an existing domain and that you stop all running processes that use this Oracle home. After you remove the software, you will no longer be able to use your ECM Oracle home.

This procedure does not remove any Oracle WebLogic Server domains that you have created. It removes only the software in the ECM Oracle home.

To deinstall Oracle Enterprise Content Management Suite:

Start the Oracle ECM deinstaller from the bin subdirectory of the oui directory in your ECM Oracle home:

To download free release notes, installation documentation, white papers, or other collateral, visit Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done on OTN at

1.18.1 Oracle Support Services

If you purchased Oracle Product Support, you can call Oracle Support Services for assistance. Oracle Support Services include phone assistance, version updates, and access to Oracle service offerings. You have access to phone support 24 hours a day, 7 days a week. In the U.S.A., you can call Product Support at 1-800-223-1711.

Make sure you have your CSI (CPU Support Identifier) number ready when you call. Keep the CSI number for your records because it is your key to Oracle Support Services. The Oracle Store sends the CSI number to you in an email alert when it processes your order. If you do not have your CSI number and you are in the U.S.A., you can look up your CSI number by accessing the online Order Tracker, which provides detailed order information. Go to the Oracle Store and click Order Tracker, above the top navigation bar.

For Oracle Support Services locations outside the U.S.A., call your local support center for information on how to access support. To find the local support center in your country, visit the Support Web Center at

With Oracle Product Support, you have round-the-clock access to My Oracle Support (formerly OracleMetaLink), Oracle Support Services premier web support offering. My Oracle Support offers you access to installation assistance, product documentation, and a technical solution knowledge base.

It has technical forums, where you can post questions about your Oracle products and receive answers from Oracle Technical Support Analysts and other Oracle users. The questions and answers remain posted for the benefit of all users.

1.18.2 Version Updates

If you do have a currently supported license, you can place nonurgent requests for version update shipments through the iTAR feature on My Oracle Support. You will need to log the iTAR type as a U.S. Client Relations/Non-Technical Request.

You can also request Version Update shipments in the U.S.A. by calling Client Relations. When requesting a Version Update, provide the following information to the Client Relations Analyst:

CSI number

Contact information

Operating system and platform

Product name

Shipping address

Product version number

Outside the U.S.A., call your local Oracle Support Center.

1.18.3 Premium Services

For information on our Premium Services, including on-site support, OracleGOLD, remote services, and upgrade packages, visit the Support Web Center at