| Oracle® Fusion Middleware Quick Installation Guide for Oracle Enterprise Content Management Suite 11g Release 1 (11.1.1) E14538-01 |
|
 Previous |
| Oracle® Fusion Middleware Quick Installation Guide for Oracle Enterprise Content Management Suite 11g Release 1 (11.1.1) E14538-01 |
|
Previous |
This quick installation guide describes how to install and configure Oracle Enterprise Content Management Suite.
This guide includes the following topics:
Section 1.4, "Creating Oracle Enterprise Content Management Suite Schemas"
Section 1.5, "Installing Oracle Enterprise Content Management Suite in a Middleware Home"
Section 1.6, "Configuring Oracle Enterprise Content Management Suite"
Section 1.9, "Deinstalling Oracle Enterprise Content Management Suite"
This guide contains instructions for installing and configuring the following Oracle Enterprise Content Management Suite products on a single host:
Oracle Imaging and Process Management (Oracle I/PM)
Oracle Information Rights Management (Oracle IRM)
The installation of Oracle Enterprise Content Management Suite is a two-step process:
Running the installer to perform a base installation of the suite's products in an ECM Oracle home, within a Middleware home
Running Fusion Middleware Configuration Wizard to deploy one or more of the suite's products as applications to an Oracle WebLogic Server domain
Table 1-1 lists the sections in the guide that provide information about the preinstallation, installation, and postinstallation tasks.
Table 1-1 Installation Roadmap
Figure 1-1 illustrates the topology that installation and configuration of these products will create on your system. Numbers in the figure show the order in which to perform certain tasks.
Figure 1-1 Installation Topology and Order of Tasks
This guide is for users who are installing Oracle Enterprise Content Management Suite for the first time to become familiar with the products in the suite, show what they can do, perform basic testing, or prepare a proof of concept (POC). For information about installing a production system, switching from test to production, or expanding a POC, see Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.
For information about installing the suite on multiple machines, reassociating the identity store with an external LDAP directory, clustering, and other optional configurations, see Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.
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
|
Note: 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. |
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.
Creating Schemas for Oracle Enterprise Content Management Suite Applications
Installing and Configuring Java Access Bridge (Windows System Only)
Oracle I/PM uses Oracle Universal Content Management (Oracle UCM) for its repository. Your system needs to have Oracle UCM 10gR3 installed before the configuration of Oracle I/PM. For information about installing Oracle UCM 10gR3, see the Oracle Universal Content Management installation documents on the Oracle Content Management 10gR3 (10.1.3) Documentation Library page on Oracle Technology Network, at the location in Section 1.2, "System Requirements and Certification."
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.
The database must be compatible with RCU. This guide describes using RCU with Oracle Database. For more information, see Section 1.4, "Creating Oracle Enterprise Content Management Suite Schemas." For information about using SQL with RCU, see Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.
|
Note: 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. |
For the latest information about supported databases, see the Oracle Fusion Middleware Supported System Configurations page 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 Database Documentation page on Oracle Technology Network at
http://www.oracle.com/technology/documentation/database.html
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."
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 the installer from the Oracle E-Delivery Web site at
http://edelivery.oracle.com/
You can download one of the following executable files:
wls1032_linux32.bin (for Linux x86 systems)
wls1032_win32.exe (for 32-bit Windows systems)
wls1032_generic.jar (for all 64-bit systems)
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, "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, set your system's DISPLAY environment variable.
Set the JAVA_HOME environment variable to the installation location of the supported JDK you installed for your system.
If you are installing Oracle WebLogic Server on a 64-bit system, use the -d64 flag when using a 32/64-bit hybrid JDK (such as the HP JDK for HP-UX and SUN JDK for Solaris SPARC).
For a 32/64-bit hybrid JDK, to validate that your JAVA_HOME environment variable refers to a 64-bit JDK, execute JAVA_HOME/bin/java -version (or JAVA_HOME/bin/java -d64 -version), in which JAVA_HOME is the value of the environment variable.
To run the installer on a 32-bit Linux operating system, use this command:
./wls1032_linux32.bin
To run the installer on a 32-bit Windows system, use this command:
wls1032_win32.exe
To run the installer on a 64-bit UNIX system, use either of these commands:
JAVA_HOME/bin/java -jar wls1032_generic.jar
JAVA_HOME/bin/java -d64 -jar wls1032_generic.jar
To run the installer on a 64-bit Windows system, use this command:
JAVA_HOME\bin\java -jar wls1032_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. |
For more information, see "Middleware Home and WebLogic Home Directories" in Oracle Fusion Middleware Installation Planning Guide.
Click Next.
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.
Choose Install Type screen
Select Typical, and click Next.
Choose Product Installation Directories screen
Specify a location for your Oracle WebLogic Server home directory, which WL_HOME represents in path names. The default location for WL_HOME is MW_HOME/wlserver_10.3 (UNIX system) or MW_HOME\wlserver_10.3 (Windows system). For more information about home directories, "Middleware Home and WebLogic Home Directories" in 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.
Choose Shortcut Location (Windows 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.
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.
Installation Progress screen
No action is required on this screen.
Installation Complete screen
Deselect Run Quickstart.
Click Done.
For more information about installing Oracle WebLogic Server, see Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.
If you are installing on a Windows operating system, you can install and configure Java Access Bridge for Section 508 Accessibility:
Download Java Access Bridge from the Java SE Desktop Accessibility page of the Sun Developer Network at
http://java.sun.com/javase/technologies/accessibility/accessbridge/
Install Java Access Bridge.
Copy the access-bridge.jar and jaccess-1_4.jar files from your installation location to the jre\lib\ext directory.
Copy the WindowsAccessBridge.dll, JavaAccessBridge.dll, and JAWTAccessBridge.dll files from your installation location to the jre\bin directory.
Copy the accessibility.properties file to the jre\lib directory.
For more information about accessibility, see "Using Oracle Fusion Middleware Accessibility Options" in Oracle Fusion Middleware Administrator's Guide.
If you are installing Oracle Enterprise Content Management Suite on a DHCP host, you must follow the configuration steps in this section for your operating system.
On a UNIX operating system, configure the host to resolve host names to the loopback IP address by modifying the /etc/hosts file to contain the following entries:
127.0.0.1 hostname.domainname hostname 127.0.0.1 localhost.localdomain localhost
To check that the host name resolves to the loopback IP address, use this command:
/bin/ping hostname.domainname
On a Windows x86 operating system, install a loopback adapter on the DHCP server (see Section 1.3.5.3, "Installing a Loopback Adapter on a Windows System"). This assigns a local IP address to your computer.
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_address hostname.domainname hostname
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.
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 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 the computer.
You can remove a loopback adapter through Control Panel.
To remove a loopback adapter from a Windows 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.
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.
In addition, you must follow the instructions in Section 1.3.5, "Configuring a DHCP Host" to install a loopback adapter and modify the hosts file on your system.
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 /etc/hosts file (UNIX system) or %SYSTEMROOT%\system32\drivers\etc\hosts file (Windows system). For example, the installer would pick up myhost1.mycompany.com for configuration if your file contains the following entries:
127.0.0.1 localhost.localdomain localhost 10.148.56.76 myhost1.mycompany.com myhost1 10.148.56.77 devhost2.mycompany.com devhost2
For specific network configuration of a system component, refer to the individual component's configuration documentation.
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 RCU home directory, represented by RCU_HOME in path names.
To start RCU on a UNIX operating system:
cd RCU_HOME/bin
./rcu
To start RCU on a Windows operating system:
cd RCU_HOME\BIN
rcu.bat
You can also download a ZIP file containing Repository Creation Utility from the Oracle Fusion Middleware 11g Software Downloads page on Oracle Technology Network 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 run RCU as the preceding text describes.
Welcome screen
Click Next.
Create Repository screen
Select Create.
Click Next.
Database Connection Details screen
Database Type: You can keep the default, Oracle Database, selected. For information about using SQL with RCU, see Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.
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.
For Oracle RAC databases, specify the service name of one of the nodes in this field; for example, sales.example.com.
Username: Specify the name of a 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.
The prefix can contain from 1 to 12 alphanumeric characters (0-9, a-z, or A-Z). No white space or special characters are allowed. RCU displays your prefix later with an underline character appended. For example, RCU would display the default prefix as DEV_.
Expand Enterprise Content Management in the Components list, then select one or more applications:
Oracle Information Rights Management
Oracle Imaging and Process Management
Also, for Oracle WSM Policy Manager, expand AS Common Schemas, and select Metadata Services.
Your database must contain a schema for an application before you configure it.
|
Note: Record each schema name from this screen because you will need it later, in the formatschemaprefix_schemasuffix, to configure the corresponding application. For example, if you used the default prefix, DEV_, you would supply the following name for the Oracle IRM schema:
DEV_ORAIRM |
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.
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.
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.
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 statementSELECT * FROM all_users or SELECT * FROM dba_users. |
For more information about RCU, see Oracle Fusion Middleware Repository Creation Utility User's Guide.
When you install Oracle Enterprise Content Management Suite, you perform a base installation of the following products in an ECM Oracle home directory under the Middleware home directory on your system:
Oracle Imaging and Process Management (Oracle I/PM)
Oracle Information Rights Management (Oracle IRM)
After installation, you can deploy either or both 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 |
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 inventory_directory/createCentralInventory.sh script as the root user.
If you do not have root access on the machine but want to continue with the installation, select Continue installation with local inventory.
You can install Oracle Enterprise Content Management Suite before or after you create schemas for the suite's applications.
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.
This installer requires the location of a Java Runtime Environment (JRE) on your system. A JRE was installed with Oracle Fusion Middleware. The default JRE location for a production environment is MW_HOME/jrockit_160_14_R27.6.5-32/jre (UNIX directory) or MW_HOME\jrockit_160_14_R27.6.5-32\jre (Windows directory), where MW_HOME is the Middleware home directory. The default JRE location for a development environment is MW_HOME/jdk160_14_R27.6.5-32/jre (UNIX directory) or MW_HOME\jdk160_14_R27.6.5-32\jre (Windows directory).
For a 64-bit installation, you can either use the -jreLoc option or allow the installer to prompt for the directory containing bin/java.
To start the installer on a UNIX operating system:
cd ecm_media_loc/Disk1 ./runInstaller [-jreLoc jre_location]
|
Note: Starting the installer as the userroot is not supported. |
To start the installer on a 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.
Specify Installation Location screen
Oracle Middleware Home: Select the Middleware home directory (MW_HOME).
Oracle Home Directory: Specify the directory where you want to install Oracle Enterprise Content Management Suite, inside the Middleware home directory:
If you specify a directory that already exists, it must be empty.
If you specify a new directory, the installer creates it.
The installation directory becomes the ECM Oracle home directory for Oracle Enterprise Content Management Suite, represented by ECM_ORACLE_HOME in path names. Run-time components cannot write to this directory.
|
Note: This document refers to this directory as the ECM Oracle home (ECM_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 Directory" in Oracle Fusion Middleware Installation Planning Guide. |
Click Next.
Installation Summary screen
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.
After you have successfully run the installer, you can deploy and configure the following Oracle Enterprise Content Management Suite products as applications:
Oracle Imaging and Process Management
Oracle Information Rights Management
To configure these applications, you can create or extend 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: 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. |
The following procedure is for creating an Oracle WebLogic Server domain. For information about extending a domain, see "Extending an Existing Domain" in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.
To configure Oracle Enterprise Content Management Suite:
Start Fusion Middleware Configuration wizard.
On a UNIX operating system:
cd ECM_ORACLE_HOME/common/bin
./config.sh
On a Windows operating system:
cd ECM_ORACLE_HOME\common\bin
config.cmd
ECM_ORACLE_HOME represents the ECM Oracle home directory, where Oracle Enterprise Content Management Suite is installed.
Welcome screen
Select Create a new WebLogic domain.
Select Domain Source screen
Select Generate a domain configured automatically to support the following products and either or both of these products:
Oracle Information Rights Management
Oracle Imaging and Process Management
When you select Oracle Imaging and Process Management or Oracle Information Rights Management on the Select Domain Source screen, Oracle Enterprise Manager and Oracle JRF are automatically selected.
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 is MW_HOME/user_projects/domains/ (UNIX system) or MW_HOME\user_projects\domains\ (Windows system). 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 is MW_HOME/user_projects/applications/ (UNIX system) or MW_HOME\user_projects\applications\ (Windows system).
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 Administration Server and to access the domain through the Oracle WebLogic Server Administration Console or Oracle Enterprise Manager 11g 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_14 for development mode.
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.
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 these options to configure the Administration Server and Managed Servers:
Administration Server
Managed Servers, Clusters and Machines
Deployments and Services
JMS File Store
RDBMS Security Store
Click Next.
Configure the Administration Server screen
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.
Configure Managed Servers screen
Each Managed Server needs a unique listen port number. For each Managed Server, you can use the default Listen port value. For increased security, you can specify a nondefault port number. Table 1-2 lists the default port values for the Managed Servers that run Oracle Enterprise Content Management Suite applications.
Table 1-2 Default Ports for Managed Servers
| Managed Server | Default Listen Port | Default SSL Port | Port Range |
|---|---|---|---|
|
Oracle I/PM |
|
|
|
|
Oracle IRM |
|
|
|
To change the SSL configuration for a Managed Server, you can select SSL enabled and set or change the SSL listen port value.
For Oracle IRM, SSL is enabled by default, with port number 16101. SSL should be enabled so that Oracle IRM Desktop does not show prompts to accept certificates when it contacts the Managed Server. The certificate used must be trusted by Microsoft Internet Explorer on computers running Oracle IRM Desktop.
Click Next.
On each of the remaining screens before Configuration Summary, you can keep the default values and click Next.
|
Notes:
|
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
Deployment of each application to its Managed Server
An application is not active until its Managed Server is started. For more information, see Section 1.7.2, "Starting Managed Servers."
After installing Oracle Enterprise Content Management Suite and configuring one or more of its applications on Oracle WebLogic Server, you need to complete the application configurations. The following topics describe these postinstallation tasks:
|
Note: This section describes postinstallation tasks for 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 your application with an external LDAP authentication provider, it is easier to do this before you complete the configuration of a Managed Server and before you connect a Managed Server to a 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. |
Before you can start a Managed Server for an application, you need to start the Administration Server for the Oracle WebLogic Server domain.
To start the Administration Server:
Run the startWebLogic.sh script (UNIX system) or startWebLogic.cmd script (Windows system) from the bin directory under the domain home directory.
The default domain home directory is MW_HOME/user_projects/domains/domain_name (UNIX system) or MW_HOME\user_projects\domains\domain_name (Windows system). Your domain name and directory path were provided on the Specify Domain Name and Location screen in Fusion Middleware Configuration Wizard.
|
Note: On a Linux operating system, the shell is going to stay open. |
Supply the Oracle WebLogic Server user name and password.
Supply the values that were specified on the Configure Administrator User Name and Password screen in the configuration wizard.
Access the Oracle WebLogic Server Administration Console at
http://adminServerHost:adminServerPort/console
For adminServerHost, specify the name of the computer that hosts the Administration Server for your domain. For adminServerPort, specify the listen port number for the Administration Server. The default number is 7001. For example:
http://myHost:7001/console
To log in, supply the user name and password that were specified on the Configure Administrator User Name and Password screen in the configuration wizard.
You can start each Managed Server from the bin directory inside your domain home directory, which is MW_HOME/user_projects/domains/domain_name (UNIX system) or MW_HOME\user_projects\domains\domain_name (Windows system). This information was provided on the Specify Domain Name and Location screen in the configuration wizard.
|
Important:
|
For Oracle I/PM transformations to work on some platforms, the following environment variables must be set before you start the Oracle I/PM Managed Server:
Environment variables for library paths
Solaris SPARC: LD_LIBRARY_PATH=/usr/local/packages/gcc-3.4.2/lib
|
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 |
AIX: LIBPATH=$DOMAIN_HOME/oracle/imaging/imaging-server
HPI: LD_PRELOAD=/usr/lib/hpux64/libpthread.so.1 and LD_LIBRARY_PATH=$DOMAIN_HOME/oracle/imaging/imaging-server
For more information, see Section 1.5, "Installing Oracle Enterprise Content Management Suite in a Middleware Home."
DISPLAY environment variable
On UNIX platforms running XWindows, when redirecting the display to a system with suitable graphic capabilities, set DISPLAY to a valid X Server.
To start a Managed Server:
Start the Administration Server (see Section 1.7.1).
Run the startManagedWebLogic.sh script (UNIX system) or startManagedWebLogic.cmd script (Windows system) from the bin directory in the domain home directory.
This command requires that you specify a server name, such as one of these:
IPM_server1 (Oracle Imaging and Process Management)
IRM_server1 (Oracle Information Rights Management)
For example, the following command would start an Oracle I/PM Managed Server on a UNIX operating system:
MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.sh IPM_server1
The following command would start an Oracle IRM Managed Server on a Windows operating system:
MW_HOME\user_projects\domains\domain_name\bin\startManagedWebLogic.cmd IRM_server1
If you selected production mode, you will be prompted for the Oracle WebLogic Server user name and password before the server starts. These were provided on the Configure Administrator User Name and Password screen in the configuration wizard.
The names of the Managed Servers are in the startManagedWebLogic_readme.txt file. To view the server names on a UNIX operating system, issue this command:
cat MW_HOME/user_projects/domains/domain_name/startManagedWebLogic_readme.txt
To view the server names on a Windows operating system, double-click this file:
MW_HOME\user_projects\domains\domain_name\startManagedWebLogic_readme.txt
For information about stopping or starting a Managed Server with Oracle Enterprise Manager 11g Fusion Middleware Control, see "Starting and Stopping Managed Servers Using Fusion Middleware Control" in Oracle Fusion Middleware Administrator's Guide.
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. |
To complete the configuration, you need to perform these tasks:
Configure Oracle Content Server 10g to Work with Oracle I/PM
Add the Administrator User and Administrators Group to Oracle UCM
Start the Oracle I/PM Managed Server and Access the Web Client
For information about optional configuration tasks, see "Completing the Oracle I/PM Configuration After First Login" in Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite.
To log in to Oracle WebLogic Server, Oracle I/PM services use the agent user, which is agentadmin by default. If you are using the Oracle WebLogic Server embedded LDAP server, you need to add this agent user, or a unique user name for the agent user, so the services can log in.
To add the Agent user to Oracle WebLogic Server:
Start the Administration Server (see Section 1.7.1).
Access the 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: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.
Click Security Realms (on the left).
In the Realms table on the Summary of Security Realms page, click myrealm in the Name column to open the Settings for myrealm page.
Go to Users and Groups, click New, and add the agentadmin user (or a unique user name).
You need to configure Oracle Content Server before it can work together with Oracle I/PM.
To configure Oracle Content Server 10g to work with Oracle I/PM:
Update the IP address filter:
On the system where Oracle UCM is installed, navigate to the installation directory.
Execute the SystemProperties application: ./bin/SystemProperties
Click the Server tab.
In the IP Address Filter field, add a vertical bar (|) followed by the IP address of the system where Oracle I/PM is installed.
The IP address is required for the Oracle I/PM system to have access to the Oracle UCM system without authentication.
Click OK.
This change will require a restart of Oracle Content Server, which you can do at the end of this procedure, after installing the Oracle UCM components.
Open the Oracle UCM Web client in a Web browser (http://hostname:port/location, such as http://myhost.mycompany.com:8000/idc), and log in.
Open the Administration tray.
Upgrade the default file store:
Under Administration, select Providers.
Select Info in the Action column of the DefaultFileStore row.
Oracle I/PM content is not accessible in a Web store. Oracle Content Server traditionally uses a weblayout directory on a file system to store content in a format for viewing in a Web browser, but this feature does not have much use in an Oracle I/PM solution and uses extra disk space. After the file store upgrade, you should disable the weblayout functionality in Oracle Content Server for any file store provider configured for use as an Oracle I/PM volume.
When asked if you want to upgrade the file store, click Upgrade, and then click Update in the Edit File Store Provider dialog box.
Oracle UCM does the upgrade automatically.
Configure system properties:
Confirm that the SearchIndexerEngineName variable matches the type of Oracle UCM system to use (DATABASE.METADATA, DATABASE.FULLTEXT, or OracleTextSearch).
Under Administration tray, select Admin Server.
Click idc.
Select General Configuration, on the left.
Select Automatically assign a content ID on check in.
Specify an Auto Number Prefix value, such as ucm1.
Set the EnableIdcProfileField variable to 1:
EnableIdcProfileField=1
Click Save.
Install Oracle UCM components:
Select Component Manager, on the left.
In the Install New Component section, click Browse.
Browse to the ECM_ORACLE_HOME/ipm/lib directory, and select IpmRepository.zip.
Click Open.
Click Install.
Click Continue.
Click here to return to the Component Manager.
Select any installed component in the Update Bundle /component/CS10gR35UpdateBundle/extras directory and IpmRepository.
Click Enable.
In the Install New Component section, click Browse.
On the Oracle Enterprise Content Management Suite media disk, select CS10gR35UpdateBundle.zip.
Click Open.
Click Install.
Click Continue.
Select any installed component in the Update Bundle /component/CS10gR35UpdateBundle/extras directory and IpmRepository.
Click Open.
Click Enable.
Fill in any necessary details for each component you selected, and then click Continue.
Click here to return to the Component Manager.
From the Options list on the left, select Start/Stop Content Server.
Select Restart.
Ensure that Oracle Content Server is running after you restart it.
You need to add the administrator user to Oracle UCM and assign it to the Administrators group before this user can perform administration tasks on Oracle UCM.
To add the administrator user and Administrators group to Oracle UCM
In the Oracle UCM Web client, select Admin Applets under Administration.
Click User Admin.
On the Security tab, select Permissions By Role.
Select Add New Role.
In the Role Name field, enter Administrators.
Click OK.
Click Close.
Click Add.
For Authorization Type: Local, click OK.
Create the administrator user, and enter the password.
Click the Roles tab.
Click Add Role.
Select Administrators, and then click OK.
Click OK.
Close the User Admin applet.
After you complete the preceding configuration tasks, you can start the Oracle I/PM Managed Server and access its Web client.
For transformations to work on some platforms, the following environment variables must be set before you start the Managed Server:
Environment variables for library paths
Solaris SPARC: LD_LIBRARY_PATH=/usr/local/packages/gcc-3.4.2/lib
|
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 |
AIX: LIBPATH=$DOMAIN_HOME/oracle/imaging/imaging-server
HPI: LD_PRELOAD=/usr/lib/hpux64/libpthread.so.1 and LD_LIBRARY_PATH=$DOMAIN_HOME/oracle/imaging/imaging-server
For more information, see Section 1.5, "Installing Oracle Enterprise Content Management Suite in a Middleware Home."
DISPLAY environment variable
On UNIX platforms running XWindows, when redirecting the display to a system with suitable graphic capabilities, set DISPLAY to a valid X Server.
To start the Oracle I/PM Managed Server and access the Web client:
Go to the bin directory under your domain home directory.
Start the Oracle I/PM Managed Server (see Section 1.7.2).
Enter the administrator user name and password.
Wait until the Oracle I/PM Managed Server is running.
Access the Web client at this URL: http://hostname:16000/imaging
Log in with the administrator user name and password.
|
Note: The first user to connect to the Oracle I/PM system is registered as the Oracle I/PM administrator. |
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: fmwadmin
Primary: localHost
Port: The IDC port of the Oracle UCM instance, 4444 by default
Click Next.
If you get the "Content Server does not have a defined document profile field" message, go to General Configuration, add the variable EnableIdcProfileField=1, and then restart Oracle Content Server.
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.
Click Next.
At the Summary screen, click Submit.
Three agents run outside of Oracle I/PM, so you 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. To set the font path on a UNIX operating system, you also need to configure the GDFontpath MBean. You can configure these MBeans through the System MBean Browser in 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:7001/cem
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 agentadmin (or to a unique user name), click Apply, and then click Return.
On a UNIX operating system, set the value of the GDFontPath attribute to the location of your TTF files; for example:
/usr/share/X11/fonts/TTF
Some standard font locations on different UNIX platforms follow:
Solaris SPARC: /usr/openwin/lib/X11/fonts/TrueType
AIX: /usr/lpp/X11/lib/X11/fonts/TrueType
HPI: /usr/lib/X11/fonts/TrueType
For systems on which Oracle WebLogic Server includes a JDK, you can find some True Type Fonts (TTF) in the JDK/jre/lib/fonts directory.
MW_HOME/jdk160_11/jre/lib/fonts
Some standard font locations on different UNIX platforms follow:
Solaris SPARC: /usr/openwin/lib/X11/fonts/TrueType
AIX: /usr/lpp/X11/lib/X11/fonts/TrueType
HPI: /usr/lib/X11/fonts/TrueType
For systems on which Oracle WebLogic Server includes a JDK, you can find some True Type Fonts (TTF) in the JDK/jre/lib/fonts directory.
Click Apply.
Restart the Oracle I/PM Managed Server.
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:
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.
|
WARNING: 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. |
For a simple installation where the Managed Server is directly accessible to Oracle IRM Desktop, this value will be the URI of the Managed Server; for example:
https://managedServerHost:managedServerPort/irm_desktop
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: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 example:
https://irm.example.com/irm_desktop
On the General Settings page, you can also specify other settings for Oracle IRM.
Click Apply.
To configure a key store for Oracle IRM, you need to create the key store and set its location and passwords.
The Oracle IRM Java EE application uses a cryptographic key to wrap (encrypt) and unwrap (decrypt) Oracle IRM key data stored in the database. This wrapping key must be generated before contexts can be created.
The suggested location for the key store is under the domain home, in the MW_HOME/user_projects/domains/domain_name/config/fmwconfig directory (UNIX system) or MW_HOME\user_projects\domains\domain_name\config\fmwconfig (Windows system). 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 create a key store for Oracle IRM:
Run the following script to set the environment.
On a UNIX operating system:
MW_HOME/wlserver_10.3/server/bin/setWLSEnv.sh
On a 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 (UNIX system) or MW_HOME\wlserver_10.3\server\lib directory (Windows system).
Run the keytool utility to generate an Oracle IRM key store, as follows:
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.
Copy the irm.jks file to the MW_HOME/user_projects/domains/domain_name/config/fmwconfig directory (UNIX system) or MW_HOME\user_projects\domains\domain_name\config\fmwconfig directory (Windows system).
You can set the key store location with either Fusion Middleware Control or WebLogic Scripting Tool (WLST) commands.
You can set the key store location on the Oracle IRM General Settings page in Fusion Middleware Control.
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: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.
In the Keystore field on the General Settings page, enter a key store path.
On a UNIX operating system:
MW_HOME/user_projects/domains/domain_name/config/fmwconfig/irm.jks
On a Windows operating system:
MW_HOME\user_projects\domains\domain_name\config\fmwconfig\irm.jks
Enter JKS for the key store type.
On the General Settings page, you can also specify other settings for Oracle IRM.
Click Apply.
You can set the key store location with the connect and setIRMKeyStore WLST commands.
To set the key store location with WLST commands:
Enter the following commands.
On a UNIX operating system:
ECM_ORACLE_HOME/common/bin/wlst.sh connect('username','password','t3://adminServerHost:adminServerPort') setIRMKeyStore()
On a Windows operating system:
ECM_ORACLE_HOME\common\bin\wlst.cmd connect('username','password','t3://adminServerHost:adminServerPort') setIRMKeyStore()
You will be prompted for the key store path and key store type.
Enter the key store path.
On a UNIX operating system:
MW_HOME/user_projects/domains/domain_name/config/fmwconfig/irm.jks
On a Windows operating system:
MW_HOME\user_projects\domains\domain_name\config\fmwconfig\irm.jks
Enter JKS for the key store type.
You must set passwords for the Oracle IRM key store with WLST commands. When the key store is created, you will be prompted for a key store password and a password for the generated key. These passwords are required by the Oracle IRM server.
To set passwords for the key store:
enter the following WLST commands.
On a UNIX operating system:
ECM_ORACLE_HOME/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")
On a Windows operating system:
ECM_ORACLE_HOME/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")
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 keystore.
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.
For a development environment, you also need to 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.
To configure one-way SSL for a development environment:
Run the following script to set the environment.
On a UNIX operating system:
MW_HOME/wlserver_10.3/server/bin/setWLSEnv.sh
On a 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 (UNIX system) or MW_HOME\wlserver_10.3\server\lib directory (Windows system).
Use the CertGen utility to create a server-specific, private key and certificate, as follows:
java utils.CertGen -selfsigned
-certfile MyOwnSelfCA.cer
-keyfile MyOwnSelfKey.key
-keyfilepass mykeypass
-cn "hostname"
For hostname, substitute the name of the machine where Oracle IRM is deployed. You should use the same name while accessing Oracle IRM Web services. For example, to generate the server certificate for a machine named myhost.us.example.com, the command would be as follows:
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. 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:
java utils.ImportPrivateKey
-keystore MyOwnIdentityStore.jks
-storepass identitypass
-keypass keypassword
-alias trustself
-certfile MyOwnSelfCA.cer.pem
-keyfile MyOwnSelfKey.key.pem
-keyfilepass mykeypass
Run the keytool utility to package the key and certificate into a separate keystore called the Trust Keystore, as follows:
keytool -import -trustcacerts -alias trustself
-keystore TrustMyOwnSelf.jks
-file MyOwnSelfCA.cer.der -keyalg RSA
On the client machine, double-click the certificate file to open the Certificate window, and then click Install Certificate to start the Certificate Import Wizard.
Install the certificate under Trusted Root Certification Authorities in Internet Explorer.
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.
Click Next, and then follow the instructions on the wizard screens.
Set Up a Custom Identity Keystore and Trust Store:
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: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.
Select Environments under your domain from Domain Structure.
Select Servers from Environment.
From Summary of Servers, select the server for which to enable SSL.
Click the KeyStores tab on the Settings for servername page.
In the KeyStores field, select Custom Identity and Custom Trust.
Enter values in the other fields on the KeyStores tab.
Save the changes.
Click the SSL tab.
In the Identity and Trust Locations field, select Keystores.
Enter values in the other fields on the SSL tab.
Save the changes.
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
Starting Node Manager on a machine that hosts one or more Managed Servers enables you to start and stop the Managed Servers remotely using the Administration Console or the command line. Node Manager can also automatically restart a Managed Server after an unexpected failure.
To start Node Manager:
Set the Node Manager properties with a script.
On a UNIX operating system, run this script:
ECM_ORACLE_HOME/common/bin/setNMProps.sh
On a Windows operating system, run this script:
ECM_ORACLE_HOME\common\bin\setNMProps.cmd
Start Node Manager with a script.
On a UNIX operating system, run this script:
WL_HOME/server/bin/startNodeManager.sh
On a Windows operating system, run this script:
WL_HOME\server\bin\startNodeManager.cmd
For more information about Node Manager, see Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.
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:7001
To log in, supply the user name and password that were specified on the Configure Administrator User Name and Password screen in the configuration wizard.
To access the Administration Console:
http://adminServerHost:adminServerPort/console
For adminServerHost, specify the name of the computer that hosts the Administration Server for your domain. For adminServerPort, specify the listen port number for the Administration Server. The default number is 7001. For example:
http://myHost:7001/console
To log in, supply the user name and password that were specified on the Configure Administrator User Name and Password screen in the configuration wizard.
To access Fusion Middleware Control:
http://adminServerHost:adminServerPort/em
For adminServerHost, specify the name of the computer that hosts the Administration Server for your domain. For adminServerPort, specify the listen port number for the Administration Server. The default number is 7001. For example:
http://myHost:7001/em
To log in, supply the user name and password that were specified on the Configure Administrator User Name and Password screen in the configuration wizard.
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.
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.
Before deinstalling Oracle Fusion Middleware software components, you should stop all servers and processes.
Stop each Oracle WebLogic Server Managed Server.
On a UNIX operating system:
MW_HOME/user_projects/domains/domain_name/bin/stopManagedWebLogic.sh managed_server_name admin_url username password
For example:
MW_HOME/user_projects/domains/ecm_domain/bin/stopManagedWebLogic.sh IPM_server1 t3://managedserver_hostname:managedserver_port weblogic password
On a Windows operating system:
MW_HOME\user_projects\domains\domain_name\bin\stopManagedWebLogic.cmd managed_server_name admin_url username password
Stop the WebLogic Administration Server.
On a UNIX operating system:
MW_HOME/user_projects/domains/domain_name/bin/stopWeblogic.sh username password
On a Windows operating system:
MW_HOME\user_projects\domains\domain_name\bin\stopWeblogic.cmd username password
For more information, see "Starting and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide.
Run the Repository Creation Utility (RCU) to drop one or more Oracle Enterprise Content Management Suite schemas from your database.
Insert the Repository Creation Utility DVD, and start RCU from the rcuHome/bin directory (UNIX system) or from the rcuHome\BIN directory (Windows system):
On a UNIX operating system:
./rcu
On a Windows operating system:
rcu.bat
If you download the Repository Creation Utility ZIP file from Oracle Technology Network, you can also start RCU as the preceding text describes.
Follow these instructions to drop one or more Oracle Enterprise Content Management Suite schemas with RCU:
Welcome screen
Click Next.
Create Repository screen
Select Drop, and click Next.
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 Enterprise Content Management Suite schemas. For more information, see Section 1.4, "Creating Oracle Enterprise Content Management Suite Schemas."
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.
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 thedbf files. |
After the schemas are dropped with no errors, click OK to dismiss the screen.
Completion Summary screen
Click Close.
The deinstaller attempts to remove the 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 WebLogic domain.
This procedure does not remove any WebLogic domains that you have created. It removes only the software in the ECM Oracle home.
You can start the deinstaller from the ECM_ORACLE_HOME/oui/bin directory (UNIX system) or ECM_ORACLE_HOME\oui\bin directory (Windows system).
On a UNIX operating system:
./runInstaller -deinstall [-jreLoc jre_location]
On a Window operating system:
setup.exe -deinstall [-jreLoc jre_location]
The value of jre_location must specify the absolute path to the Java Runtime Environment (JRE) on your system. A relative path will not work.
On a Windows operating system, you can also start the deinstaller from the Start menu by selecting Programs, then Oracle ECM 11g - Home1, and then Uninstall.
Follow these instructions to remove the installed software:
Welcome screen
Click Next.
Deinstall Oracle Home screen
Verify the ECM Oracle home you are about to deinstall, and click Deinstall to continue.
Deinstall Progress screen
This screen shows the progress and status of the deinstallation.
Deinstall Completed screen
Click Finish.
Manually remove the ECM Oracle home directory and all of its subdirectories. For example, to remove the ECM Oracle home directory MW_HOMEOracle_ECM1 from a UNIX operating system:
cd /MW_HOME
rm -rf Oracle_ECM1
To remove the ECM Oracle home directory from a Windows operating system, you can use a file manager window, navigate to the C:\MW_HOME directory, right-click the Oracle_ECM1 folder, and then select Delete.
You can also manually remove the program groups from the Start Menu\Programs folder, if they exist. For example, you might remove the following program groups from C:\Documents and Settings\All Users\Start Menu\Programs:
Oracle WebLogic (BEAHOME 1)
Oracle ECM 11g - Home1
The folder and program group names on your Windows system might be different.
For additional information, see Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite, which is available on the Oracle Fusion Middleware Documentation DVD.
Documentation is available for sale through your Oracle representative or from the Oracle Store at
http://shop.oracle.com
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
http://www.oracle.com/technology/join
If you already have a user name and password for OTN, then you can go directly to the Oracle Documentation page on OTN at
http://www.oracle.com/technology/documentation
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 e-mail 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
http://www.oracle.com/support
The Support Web Center has information about Oracle Support Services:
Contact Information
Instructions for Accessing Electronic Services
Helpful Web Sites
Support Resources
Oracle Support Portfolio
Oracle Support Services news
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.
My Oracle Support includes these options:
Technical Assistance Request (TAR) access
Patch Downloads
Bug Database Query Access
Product Life-Cycle Information
You can access My Oracle Support at
http://support.oracle.com
If you do not have a currently supported license, you can purchase the most recent version of an Oracle product from the Oracle Store at
http://shop.oracle.com
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.
For information on our Premium Services, including on-site support, OracleGOLD, remote services, and upgrade packages, visit the Support Web Center at
http://www.oracle.com/support
You can also call your Support Sales Representative in the U.S.A at 1-800-833-3536.
For quick access to additional information, see Table 1-3.
Table 1-3 Links to Additional Information and Resources
| Task | Contact Information or Web Site |
|---|---|
|
Purchase additional products, full-use licenses, version updates, and documentation in the U.S.A. |
|
|
Access technical resources for developers |
|
|
Access installation documentation |
|
|
Access information about technical support |
|
|
Locate local Oracle Support Centers outside the U.S.A. |
|
|
Locate local Oracle offices outside the U.S.A. |
|
|
Call Client Relations in the U.S.A. |
1-800-223-1711 |
|
Speak with your sales representative in the U.S.A. |
1-800-ORACLE-1 |
|
Locate TTY Access to technical support in the U.S.A. |
1-800-446-2398 |
|
 Copyright © 2004, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|