1 Installing and Configuring Oracle WebCenter Content

1.1.2.1 Installation Modules

Oracle WebCenter Content requires a Middleware home and an application server on your system. If your system does not already have Oracle WebLogic Server, you can install it in a new Middleware home directory, as described in Section 1.2.1.5, "Installing Oracle WebLogic Server and Creating the Middleware Home."

If the application server you want to use is an IBM WebSphere Application Server, see "Managing Oracle WebCenter Content on IBM WebSphere Application Servers" in the Oracle Fusion Middleware Third-Party Application Server Guide.

A Middleware home is a container for the Oracle WebLogic Server home, and, optionally, one Oracle Common home and one or more Oracle homes, with a directory structure like this:

/middleware_home
     coherence_3.7
     jdk160_29
     jrockit_160_29_D1.2.0-10
     logs
     modules
     wlserver_10.3
     oracle_common
     utils
     WC_CONTENT_ORACLE_HOME
     user_projects

1.1.2.2 Software Downloads for Oracle WebCenter Content Installation

You can also download the software you need for Oracle WebCenter Content installation from either of these web sites:

• Oracle Software Delivery Cloud at

  http://edelivery.oracle.com/

• Oracle Fusion Middleware 11g Software Downloads page on Oracle Technology Network (OTN) at

  http://www.oracle.com/technology/software/products/middleware

1.2.1.1 Disabling the 8.3 File Naming Convention on a Windows Operating System

Before you install Oracle WebCenter Content on a Windows Operating System, you need to disable the 8.3 file naming convention (maximum 8-character file name and 3-character extension).

If the WebCenter Content weblayout directory is on a file system with 8.3 semantics, the legacy 16-bit 8.3 file names will conflict with revision labels and cause file loss.

To disable the 8.3 file naming convention on a Windows Operating System:

1. Open the Windows Registry Editor (regedit), and go to the following key:

   HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/FileSystem
   

2. Set the value of the NtfsDisable8dot3NameCreation key to 1.

3. Restart the Windows operating system for the change to take effect.

1.2.1.2 Reviewing 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

  http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm

• "Oracle Fusion Middleware Supported System Configurations" contains information related to supported installation types, platforms, operating systems, databases, JDKs, and third-party products. This document is at

  http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

1.2.1.3 Installing and Configuring a Supported Database

The configuration of Oracle WebCenter Content 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 Oracle WebCenter Content 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 Oracle WebCenter Content.

The database must be compatible with RCU. This guide describes using RCU with Oracle Database. For more information, see Section 1.2.1.4, "Creating Oracle WebCenter Content Schemas with the Repository Creation Utility." For information about using Microsoft SQL Server or IBM DB2 with RCU, see the Oracle WebCenter Content Installation Guide.

The overall performance of a Content Server 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" document on Oracle Technology Network at

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

For more information about Oracle Database, see the Oracle Documentation page on Oracle Technology Network at

http://www.oracle.com/technology/indexes/documentation/index.html#database

1.2.1.4 Creating Oracle WebCenter Content Schemas with the Repository Creation Utility

Oracle WebCenter Content requires that an application schema exists in the database before configuration of the application. You must run the 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 WebCenter Content.

• Oracle WebCenter Content (WebCenter Content, which includes Oracle WebCenter Content Server)

• Oracle WebCenter Content: Inbound Refinery (Inbound Refinery)

• Oracle WebCenter Content: Imaging (Imaging)

• Oracle Information Rights Management (Oracle IRM)

• Oracle WebCenter Content: Records (Records)

To create schemas for Oracle WebCenter Content applications:

1. Unzip a ZIP file containing the Repository Creation Utility, and then start RCU with the bin/rcu or BIN\rcu.bat file:

   • UNIX path: RCU_HOME/bin/rcu

   • Windows path: RCU_HOME\BIN\rcu.bat

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

   • Oracle Software Delivery Cloud at

     http://edelivery.oracle.com/

   • Oracle Fusion Middleware 11g Software Downloads page on Oracle Technology Network (OTN) at

     http://www.oracle.com/technology/software/products/middleware

   Note:

   On a Windows operating system, do not unzip the RCU ZIP file to a directory with a name that contains spaces.

   After downloading the ZIP file, extract the contents to a directory of your choice, and then start RCU as the preceding text describes.

2. Welcome screen

   Click Next.

3. Create Repository screen

   Select Create.

   Click Next.

4. Database Connection Details screen

   Database Type: You can keep the default, Oracle Database, selected.

   For information about using Microsoft SQL Server or IBM DB2 with RCU, see the Oracle WebCenter Content Installation Guide.

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

5. 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 WebCenter Content (for Oracle WebCenter Content applications) in the Component column, and select one or more of the following applications:

   • Oracle Information Rights Management

   • Oracle WebCenter Content Server - Complete

     (for WebCenter Content)

   • Oracle WebCenter Content Server - Search Only

   • Oracle WebCenter Content: Records

   • Oracle WebCenter Content: Imaging

     (for Imaging)

   To create a schema for WebCenter Content, select Oracle WebCenter Content Server - Complete.

   If you select Oracle WebCenter Content: Imaging, you should also select Oracle WebCenter Content Server - Complete to use WebCenter Content as the Imaging repository.

   Also, for Oracle Web Services Manager (WSM) Policy Manager, expand AS Common Schemas, and then select Metadata Services.

   Your database must contain a schema for an application before you configure it.

   Note:

   Record each schema owner name from this screen because you will need it later, in the format schemaprefix_schemasuffix, to configure the corresponding application.

   For example, if you used the default prefix, DEV_, you would supply the following owner name for the Records schema in Oracle Database:

   DEV_URMSERVER
   

   Click Next. The Checking Component Prerequisites dialog box appears.

   If you have any prerequisite errors, the Select Components 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.

6. Schema Passwords screen

   For a development system, you can select Use same passwords for all schemas, near the top of the screen. Enter your password two times, in the Password and Confirm Password field.

   Or you can enter a different password for each application listed in the Component column. Enter the password for each application twice, in the Schema Password and Confirm Password columns.

   Note:

   Record all schema passwords from this screen because you will need them later to configure your applications.

   Click Next.

7. Map Tablespaces screen

   Click Next. The Validating and Creating Tablespaces dialog box appears.

   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.

8. Summary screen

   Click Create. The CREATE dialog box opens.

   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.

9. Completion Summary screen

   This screen shows the locations of the RCU log file and component (application) log files.

   Click Close.

For more information about RCU, see the Oracle Fusion Middleware Repository Creation Utility User's Guide.

1.2.1.5 Installing Oracle WebLogic Server and Creating the Middleware Home

Oracle WebCenter Content requires a Middleware home directory and an application server 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:

1. Download Oracle WebLogic Server 11gR1 (10.3.5 or 10.3.6) for your platform from either of these web sites:

   • Oracle Software Delivery Cloud at

     http://edelivery.oracle.com/

   • Oracle WebLogic Server Downloads page on Oracle Technology Network (OTN) at

     http://www.oracle.com/technology/middleware/weblogic/downloads/index.html

   The 32-bit executable files from which you can install Oracle Weblogic Server 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" document, described in Section 1.2.1.2, "Reviewing System Requirements and Certification."

2. Copy the installer file to a directory in your local system, go to that directory, and run the installer 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:

   ./wls103n_linux32.bin
   

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

   wls103I_win32.exe
   

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

   JAVA_HOME/bin/java -jar wls103n_generic.jar
   

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

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

   JAVA_HOME\bin\java -jar wls103n_generic.jar
   

3. Welcome screen

   Click Next.

4. 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 WebCenter Content.

   The default Middleware home is in the user's home directory, user_home/Oracle/Middleware on a UNIX operating system or user_home\Oracle\Middleware on a Windows operating system. For more information, see "Middleware Home and WebLogic Home Directories" in the Oracle Fusion Middleware Installation Planning Guide.

   Click Next.

5. Register for Security Updates screen

   Select whether or not to receive the latest product and security updates. If you choose not to receive anything, you need to verify your selection.

   Click Next.

6. Choose Install Type screen

   Select Typical, and click Next.

   If you are prompted for a JDK location on a 64-bit system, specify a JDK:

   1. Browse to the JDK location.

   2. Select the directory that contains the bin directory.

   3. Click Next.

7. Choose Product Installation Directories screen

   Specify a location for your Oracle WebLogic Server home directory, which
   WL_HOME represents in path names in this document. The default location for
WL_HOME follows:

   • UNIX path: MW_HOME/wlserver_10.3

   • Windows path: MW_HOME\wlserver_10.3

   For more information about home directories, see "Middleware Home and WebLogic Server Home Directories" in the Oracle Fusion Middleware Installation Planning Guide.

   You can also specify a JDK. To specify a JDK for a 64-bit operating system, you must select Custom and the installed 64-bit JDK.

   Click Next.

8. Choose Shortcut Location (Windows operating system only)

   If you are installing on a Windows operating system, you need to specify a location for creating a shortcut to Oracle products.

   Click Next.

9. Installation Summary screen

   Verify the information on this screen. If you want to change anything, click Previous to go back.

   Click Next to install Oracle WebLogic Server.

10. Installation Progress screen

    No action is required on this screen.

11. Installation Complete screen

    Deselect Run Quickstart.

    Click Done.

For more information about installing Oracle WebLogic Server, see the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

1.2.1.6 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:

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

2. 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.2.1.7 Creating a Symbolic Link to the chmod Command on a Solaris System

Before installing Oracle WebCenter Content on a Solaris operating system, you need to create a symbolic link to the chmod command.

To create a symbolic link to the chmod command:

1. Log in as the root user.

2. Execute the following command as root:

   ln -s /usr/bin/chmod /usr/local/bin/chmod
   

3. Log out, and then log back in with a different user name to start the installation.

   Running the installer as the root user is not supported.

1.2.2.1 Starting the Installer

Start the Oracle Fusion Middleware 11g WebCenter Content Installer from Disk 1 of the Oracle WebCenter Content media, as follows:

• UNIX command:
wc_content_media_loc/Disk1/runInstaller -jreLoc jre_location

  If you do not specify the JRE location, the installer either prompts you for the location or returns an error. If you get an error, retry the command with the JRE location included.

• Windows command:
wc_content_installer_loc/Disk1/setup.exe -jreLoc jre_location

  If you double-click setup.exe, the installer either prompts you for the JRE location or returns an error. If you get an error, enter the command with the JRE location included. If you are prompted for the JRE location, enter the path, and then click Enter to start the Oracle WebCenter Content installation.

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.

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

1.2.2.2 Following the Installation Instructions

The following procedure and the installation screens provide instructions for installing Oracle WebCenter Content.

To install Oracle WebCenter Content:

1. Welcome screen

   Click Next.

2. Install Software Updates screen

   Specify any software updates to install before you install Oracle WebCenter Content.

   To get updates from My Oracle Support (formerly OracleMetaLink), you can select Search My Oracle Support for Updates, specify a user name and password, and then click Search for Updates. Before you search, you can click Proxy Settings to change the settings for the proxy server and Test Connection to test the credentials.

   To get updates that you have saved to your computer, you can select Search Local Directory for Updates, specify a directory, and then click Search for Updates.

   If you do not want to update any software, select Skip Software Updates, and then click Next to continue the installation.

3. Prerequisite Checks screen

   If the installer displays an error message in the bottom section of the screen, fix the error, and then click Retry to start the prerequisite checking again for all applications. Repeat this until the prerequisite checks complete with no errors.

   If you want to stop the installation process while you fix a prerequisite error, click Abort.

   If you want to continue the installation without fixing an error, click Continue.

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

4. Specify Installation Location screen

   Oracle Middleware Home: Select the Middleware home directory (MW_HOME), which was created during the installation of Oracle WebLogic Server.

   The default Middleware home is user_home/Oracle/Middleware on a UNIX operating system or user_home\Oracle\Middleware on a Windows operating system.

   Oracle Home Directory: Specify the directory where you want to install Oracle WebCenter Content.

   • If you specify a directory that already exists, it must be empty.

   • If you specify a new directory, the installer creates it inside the Middleware home directory.

   The installation directory becomes the WebCenter Content Oracle home, represented by WC_CONTENT_ORACLE_HOME in path names. Runtime components cannot write to this directory. The default WebCenter Content Oracle home is MW_HOME/Oracle_ECM1 on a UNIX operating system or MW_HOME\Oracle_ECM1 on a Windows operating system.

   Note:

   This document refers to this directory as the WebCenter Content Oracle home (WC_CONTENT_ORACLE_HOME) to avoid confusion with the Oracle home directories of other Java components of Oracle Fusion Middleware.

   For more information, see "Oracle Home and Oracle Common Home Directories" in the Oracle Fusion Middleware Installation Planning Guide.

   Click Next to continue.

5. Application Server.

   Leave the default, WebLogic Server, selected.

6. Installation Summary screen

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

7. Installation Progress screen

   Monitor the progress of your installation.

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

8. Installation Completed screen

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

1.2.3.1 Viewing the Installation Log File

The location of the installation log file depends on your operating system:

• UNIX location: USER_HOME/oraInventory/logs/installdate_time

• Windows location: USER_HOME\oraInventory\logs\installdate_time

1.2.3.2 Checking the Directory Structure

After installation, you can verify that the directory structure is like the topology that Figure 1-1 shows.

1.3.3.1 Setting Startup Parameters for Managed Servers with the Administration Console

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, you set the value of the -Xmx parameter.

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

1. Log in to the Oracle WebLogic Server Administration Console at this 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.

2. Click Environment under Domain Structure, on the left.

3. Click Servers on the Summary of Environment page.

4. Set the memory parameters for each Managed Server:

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

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

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

      Table 1-3 Java VM Memory Parameters

      Java VM	Operating System	Parameters
      Sun	UNIX	-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
      Sun	Windows	-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m
      JRockit	UNIX	-Xms256m -Xmx1024m -XnoOpt
      JRockit	Windows	-Xms256m -Xmx1024m -XnoOpt

      
      

   4. Save the configuration changes.

5. Restart any running Managed Servers, as described in Section 1.9.3, "Restarting a Managed Server."

1.3.3.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, you set the value of the -Xmx parameter.

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

• UNIX shell script (.sh)

  export USER_MEM_ARGS="-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m"
  

• UNIX C shell script (.csh)

  setenv  USER_MEM_ARGS "-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m"
  

• Windows command script (.cmd)

  set USER_MEM_ARGS="-Xms256m -Xmx1024m -XX:CompileThreshold=8000 -XX:PermSize=128m -XX:MaxPermSize=512m"
  

1.3.4.1 Setting Up TrueType Fonts on a UNIX System

For Imaging, Inbound Refinery, and Content Server Dynamic Converter to work correctly on a UNIX operating system, you need to set up TrueType fonts on the machine where Imaging, Inbound Refinery, or the Dynamic Converter is running. If these fonts are not available on your system, you need to install them. Then you can configure Inbound Refinery with the path to the font directory, as follows. For information about configuring the path to the font directory for Imaging once the fonts are installed, see Section 1.6.3, "Configuring the GDFontPath MBean for a UNIX Operating System."

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, Imaging 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 Imaging. You can download GCC from the Sunfreeware web site at

  http://www.sunfreeware.com

  You also need to set the LD_LIBRARY_PATH environment variable to /usr/local/packages/gcc-3.4.2/lib before starting the Imaging 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

• Linux: /usr/lib/X11/fonts/TrueType

To set the path to the font directory in Inbound Refinery:

1. Log in to Inbound Refinery.

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

3. Click Options.

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

   For example:

   /usr/share/x11/fonts/FTP
   

5. Click Update.

1.3.4.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.3.5.1 Installing Libraries for Outside In Technology on UNIX Platforms

Before you start a Content Server, Inbound Refinery, or Imaging Managed Server, the libraries required for your platform need to be 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

http://www.sunfreeware.com

HPUX Itanium requires GCC package 3.3.6, which you can download through the following web site:

http://gcc.gnu.org

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 Imaging or WebCenter Content 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.

• Solaris Sparc 32-bit

  /usr/platform/SUNW,Ultra-60/lib/libc_psr.so.1 
  libICE.so.6 
  libSM.so.6 
  libX11.so.4 
  libXext.so.0 
  libXm.so.4 
  libXt.so.4 
  libc.so.1 
  libdl.so.1 
  libgcc_s.so.1 
  libgen.so.1 
  libm.so.1 
  libmp.so.2 
  libnsl.so.1 
  libpthread.so.1 
  libsocket.so.1 
  libstdc++.so.6 
  libthread.so.1 
  

• HPUX ia64

  libCsup.so.1 
  libICE.so.1 
  libSM.so.1 
  libX11.so.1 
  libXext.so.1 
  libXm.so.1 
  libXp.so.1 
  libXt.so.1 
  libc.so.1 
  libdl.so.1 
  libgcc_s_hpux64.so.0 
  libm.so.1 
  libpthread.so.1 
  libstd_v2.so.1 
  libstdc++.so.5 
  libuca.so.1 
  libunwind.so.1
  

• AIX 32-bit

  /usr/lib/libC.a(ansi_32.o) 
  /usr/lib/libC.a(shr.o) 
  /usr/lib/libC.a(shr2.o) 
  /usr/lib/libC.a(shr3.o) 
  /usr/lib/libICE.a(shr.o) 
  /usr/lib/libIM.a(shr.o) 
  /usr/lib/libSM.a(shr.o) 
  /usr/lib/libX11.a(shr4.o) 
  /usr/lib/libXext.a(shr.o) 
  /usr/lib/libXi.a(shr.o) 
  /usr/lib/libXm.a(shr_32.o) 
  /usr/lib/libXt.a(shr4.o) 
  /usr/lib/libc.a(shr.o) 
  /usr/lib/libcrypt.a(shr.o) 
  /usr/lib/libgaimisc.a(shr.o) 
  /usr/lib/libgair4.a(shr.o) 
  /usr/lib/libi18n.a(shr.o) 
  /usr/lib/libiconv.a(shr4.o) 
  /usr/lib/libodm.a(shr.o) 
  /usr/lib/libpthreads.a(shr.o) 
  /usr/lib/libpthreads.a(shr_comm.o) 
  /usr/lib/libpthreads.a(shr_xpg5.o) 
  /usr/lib/libpthreads_compat.a(shr.o) 
  

• HPUX PA/RISC 32-bit

  /lib/libCsup.2 
  /lib/libCsup_v2.2 
  /lib/libX11.3 
  /lib/libXm.4 
  /lib/libXt.3 
  /lib/libc.2 
  /lib/libcl.2 
  /lib/libm.2 
  /lib/libstd.2 
  /lib/libstd_v2.2 
  /lib/libstream.2 
  /usr/lib/libCsup.2 
  /usr/lib/libCsup_v2.2 
  /usr/lib/libX11.3 
  /usr/lib/libXm.4 
  /usr/lib/libXt.3 
  /usr/lib/libc.2 
  /usr/lib/libcl.2 
  /usr/lib/libdld.2 
  /usr/lib/libisamstub.1 
  /usr/lib/libm.2 
  /usr/lib/libstd.2 
  /usr/lib/libstd_v2.2 
  /usr/lib/libstream.2 
  /view/x_r6hp700_1111/vobs/swdev/pvt/r6hp700_1111/X11R6/lib/libICE.2
  /view/x_r6hp700_1111/vobs/swdev/pvt/r6hp700_1111/X11R6/lib/libSM.2
  /view/x_r6hp700_1111/vobs/swdev/pvt/r6hp700_1111/X11R6/lib/libX11.3
  /view/x_r6hp700_1111/vobs/swdev/pvt/r6hp700_1111/X11R6/lib/libXext.3
  /view/x_r6hp700_1111/vobs/swdev/pvt/r6hp700_1111/X11R6/lib/libXp.2
  /view/x_r6hp700_1111/vobs/swdev/pvt/r6hp700_1111/X11R6/lib/libXt.3
  

• SUSE Linux

  For an SUSE Linux operating system, the file /usr/lib/libstdc++.so.5 is required. You can find this file in the compat-libstdc++ or libstdc++33 package.

1.3.5.2 Setting Library Paths in Environment Variables on UNIX Platforms

Before Inbound Refinery or WebCenter Content Dynamic Converter uses Outside In Technology for document and image conversions, the following environment variables must be set in the or Imaging or WebCenter Content Managed Server on the specified UNIX platforms:

• Environment variables for library paths for Imaging

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

  • AIX:

    LIBPATH=DomainHome/oracle/imaging/imaging-server
    

  • HP-UX Itanium:

    LD_PRELOAD=/usr/lib/hpux64/libpthread.so.1
    LD_LIBRARY_PATH=DomainHome/oracle/imaging/imaging-server
    

• Environment variables for library paths for WebCenter Content with Dynamic Converter and Inbound Refinery

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

    Add the following line to the Inbound Refinery intradoc.cfg file at
DomainHome/ucm/ibr/bin:

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

    Then restart Inbound Refinery, as described in Section 1.9.3, "Restarting a Managed Server."

  • HP-UX Itanium:

    export LD_LIBRARY_PATH=/opt/hp-gcc/3.3.6/lib/:/opt/hp-gcc/3.3.6/lib/hpux64:$LD_LIBRARY_PATH
    

    The Dynamic Converter on HP-UX Itanium needs the 3.3.6 version of the GCC libraries installed before the WebCenter Content 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 Imaging or Inbound Refinery Managed Server or the WebCenter Content Dynamic Converter.

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

Outside In 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

http://www.microsoft.com/downloads

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.2.1 Creating a Key Store

The keytool command will generate a key store, which requires a password to open. Inside the key store, a key, oracle.irm.wrap, will be stored, and access to this key requires an additional password.

To create a key store for Oracle IRM:

1. Run the setWLSEnv script to set the environment:

   • UNIX path: MW_HOME/wlserver_10.3/server/bin/setWLSEnv.sh

   • Windows path: 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 or MW_HOME\wlserver_10.3\server\lib directory.

2. Run the keytool utility, on a single command line, to generate a Oracle IRM key store:

   keytool -genkeypair -alias oracle.irm.wrap 
         -keyalg RSA -keysize 2048 -keystore irm.jks
   

   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.

   For information about generating a Oracle IRM key store with the AES key wrapping algorithm, see "Configuring a Key Store for Oracle IRM" in the Oracle WebCenter Content Installation Guide.

3. Copy the irm.jks file to the domain's fmwconfig directory:

   • UNIX path:
MW_HOME/user_projects/domains/DomainHome/config/fmwconfig

   • Windows path:
MW_HOME\user_projects\domains\DomainHome\config\fmwconfig

1.7.2.2 Setting the Key Store Location

The Rights Server configuration needs to be updated so that Oracle IRM 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 Oracle WebLogic Scripting Tool (WLST) connect and setIRMKeyStore commands.

-Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.TrustKeyStore=KeyStoreName

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

• UNIX path:
  MW_HOME/user_projects/domains/DomainHome/config/fmwconfig

• Windows path:
  MW_HOME\user_projects\domains\DomainHome\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:

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

2. In the farm navigation tree on the left, expand Content Management and Information Rights Management, and then click IRM.

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

4. Enter JKS for the key store type.

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

   • UNIX path: MW_HOME/user_projects/domains/DomainHome
/config/fmwconfig/irm.jks

   • Windows path: MW_HOME\user_projects\domains\DomainHome
\config\fmwconfig\irm.jks

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

7. Click Apply.

To set the key store location with WLST commands:

1. Enter the following commands:

   • UNIX operating system

     WC_CONTENT_ORACLE_HOME/oracle_common/common/bin/wlst.sh
     connect('username','password','t3://adminServerHost:adminServerPort')
     setIRMKeyStore()
     

   • Windows operating system

     WC_CONTENT_ORACLE_HOME\oracle_common\common\bin\wlst.cmd
     connect('username','password','t3://adminServerHost:adminServerPort')
     setIRMKeyStore()
     

   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:

   't3://myHost.example.com:7001'
   

2. Enter the key store type and key store path when prompted.

   • 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 path: MW_HOME/user_projects/domains/DomainHome
/config/fmwconfig/irm.jceks

       Windows path: MW_HOME\user_projects\domains\DomainHome
\config\fmwconfig\irm.jceks

     • Key store path for an RSA key store:

       UNIX path: MW_HOME/user_projects/domains/DomainHome
/config/fmwconfig/irm.jks

       Windows path: MW_HOME\user_projects\domains\DomainHome
\config\fmwconfig\irm.jks

1.7.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 Rights Server.

To add key store passwords to the credential store:

• Enter the following WLST commands:

  • UNIX operating system

    WC_CONTENT_ORACLE_HOME/oracle_common/common/bin/wlst.sh
    connect('username','password','t3://adminServerHost:adminServerPort')
    createCred("IRM","keystore:irm.jks","dummy","password")
    createCred("IRM","key:irm.jks:oracle.irm.wrap","dummy","password")
    

  • Windows operating system

    WC_CONTENT_ORACLE_HOME\oracle_common\common\bin\wlst.cmd
    connect('username','password','t3://adminServerHost:adminServerPort')
    createCred("IRM","keystore:irm.jks","dummy","password")
    createCred("IRM","key:irm.jks:oracle.irm.wrap","dummy","password")
    

  Notes:

  • 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.7.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 Rights Desktop can be configured to trust the certificate.

To configure one-way SSL with a server certificate:

1. Run the setWLSEnv script to set the environment:

   • UNIX script:
     MW_HOME/wlserver_10.3/server/bin/setWLSEnv.sh

   • Windows script:
     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 or MW_HOME\wlserver_10.3\server\lib directory.

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

   java utils.CertGen -selfsigned 
                      -certfile MyOwnSelfCA.cer
                      -keyfile MyOwnSelfKey.key 
                      -keyfilepass mykeypass
                      -cn "hostname"
   

   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):

   java utils.CertGen -selfsigned 
                      -certfile MyOwnSelfCA.cer
                      -keyfile MyOwnSelfKey.key 
                      -keyfilepass mykeypass
                      -cn "myhost.us.example.com"
   

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

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

   java utils.ImportPrivateKey 
                      -keystore MyOwnIdentityStore.jks
                      -storepass identitypass
                      -keypass keypassword
                      -alias trustself
                      -certfile MyOwnSelfCA.cer.pem
                      -keyfile MyOwnSelfKey.key.pem
                      -keyfilepass mykeypass
   

   Substitute an identity store password for identitypass, a key password for keypassword, and a key-file password for mykeypass.

4. Run the keytool utility to package the key and certificate into a separate keystore called the Trust Keystore.

   In the following keytool commands (each a single command line), JAVA_HOME represents the location of the JDK. For information about the JAVA_HOME environment variable, see Section 1.2.1.5, "Installing Oracle WebLogic Server and Creating the Middleware Home."

   • UNIX operating system

     JAVA_HOME/bin/keytool -import -trustcacerts -alias trustself 
             -keystore TrustMyOwnSelf.jks 
             -file MyOwnSelfCA.cer.der -keyalg RSA
     

   • Windows operating system

     JAVA_HOME\bin\keytool -import -trustcacerts -alias trustself 
             -keystore TrustMyOwnSelf.jks 
             -file MyOwnSelfCA.cer.der -keyalg RSA
     

5. Click Next, and then follow the instructions on the wizard screens.

6. Set Up a Custom Identity Keystore and Trust Store:

   1. Log in to 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.

   2. Select Environment under your domain from Domain Structure.

   3. Select Servers from Environment.

   4. From Summary of Servers, select the server for which to enable SSL.

   5. Click the Keystores tab on the Settings for servername page.

   6. In the Keystores field, select Custom Identity and Custom Trust.

   7. Enter values in the other fields on the Keystores tab.

   8. Save the changes.

   9. Click the SSL tab.

   10. In the Identity and Trust Locations field, select Keystores.

   11. Enter values in the other fields on the SSL tab.

   12. Save the changes.

1.7.3.2 Configuring Client Machines Running Rights Desktop to Accept a Server Certificate

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

To configure client machines running Rights Desktop to accept a server certificate:

1. On each client machine that is running Rights 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 Rights Desktop, follow the procedure required for your operating system to trust the certificate.

2. On every machine running Rights 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.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.

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.

1.9.4.2 Assigning Servers to a Machine

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.

1.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 1.8, "Completing the Records Configuration."

To enable startup scripts and start Node Manager:

1. Navigate to the following directory:

   MIDDLEWARE_HOME/oracle_common/common/bin
   

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

1.10.2.1 Starting Repository Creation Utility

Insert the Repository Creation Utility DVD, and then start RCU with the bin/rcu or BIN\rcu.bat file:

• UNIX path: RCU_HOME/bin/rcu

• Windows path: RCU_HOME\BIN\rcu.bat

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

• Oracle Software Delivery Cloud at

  http://edelivery.oracle.com/

• Oracle Fusion Middleware 11g Software Downloads page on Oracle Technology Network (OTN) at

  http://www.oracle.com/technology/software/products/middleware

After downloading the ZIP file, extract the contents to a directory of your choice, and then start RCU as the preceding text describes.

1.10.2.2 Dropping Schemas

Follow these instructions to drop one or more Oracle WebCenter Content schemas with RCU:

1. Welcome screen

   Click Next.

2. Create Repository screen

   Select Drop, and click Next.

3. Database Connection Details screen

   Provide the credentials to connect to your database instance. These are the same credentials you provided on this screen when you created the Oracle WebCenter Content schemas. For more information, see Section 1.2.1.4, "Creating Oracle WebCenter Content Schemas with the Repository Creation Utility."

   Click Next. The Checking Prerequisites screen appears.

   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.

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

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

6. Completion Summary screen

   Click Close.