Oracle® Fusion Middleware

2.1 Verifying System Requirements and Certification

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

• Oracle Fusion Middleware System Requirements and Specifications:

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

  This document contains information related to hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches.

• Oracle Fusion Middleware Certification

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

  This document contains information related to supported installation types, platforms, operating systems, databases, JDKs, and third-party products.

2.2 Installing and Configuring a Database

Installation of Oracle WebCenter requires the availability of a database. This database must be up and running, and does not have to be on the same system where you are installing the components. The database must also be compatible with Repository Creation Utility (RCU), which is used to create the schemas necessary for Oracle WebCenter components.

For the latest information about certified databases, visit the Oracle Fusion Middleware Certification document at following URL:

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

After you have installed a database, make sure that it is configured correctly by referring to the "Repository Creation Utility (RCU) Requirements" section in the System Requirements and Specifications document:

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

2.3 Creating Operating System Users for IBM DB2 Databases

If you are not using an IBM DB2 database, you can skip this section.

IBM DB2 databases authenticates its database users using equivalent operating system users. Therefore, prior to running RCU, one operating system user must be created for each schema. The operating system user name must match the schema owner name and must contain only lowercase letters; no all-uppercase or mixed-case names are allowed. For example, if you plan to create a schema named DEV_PT using RCU, then the operating system user must be named dev_pt (all lowercase letters).

Table 2 in Section 2.4, "Creating Schemas for Oracle WebCenter" shows the operating system users that should be created for Oracle WebCenter. Refer to your system documentation for information about how to create operating system users.

2.4 Creating Schemas for Oracle WebCenter

Oracle WebCenter requires that certain schemas exist in the database prior to installation. You must run Repository Creation Utility (RCU) to create the schemas in the database.

First, you must obtain the latest version of RCU. To do so, go to the Oracle Fusion Middleware 11gR1 Software Download page on Oracle Technology Network:

http://www.oracle.com/technology/software/products/middleware/htdocs/111110_fmw.html

Look for Repository Creation Utility in the "Required Additional Software" table. After downloading the .zip file, extract the contents to a directory of your choice; this directory will be referred to as the RCU_HOME directory.

Follow the instructions below to start RCU and create the schemas:

1. Start RCU from the RCU_HOME/bin (on Linux operating systems) or RCU_HOME\bin (on Windows operating systems) directory:

   On Linux operating systems:

   ./rcu
   

   On Windows operating systems:

   rcu.bat
   

2. Welcome Screen

   Click Next.

3. Create Repository Screen

   Select Create.

   Click Next.

4. Database Connection Details Screen

   If you are using an Oracle database, provide the following credentials:

   • Host Name: Specify the name of the machine on which your database resides in the format host.domain.com. For Oracle RAC databases, specify the Virtual IP name or one of the node names as the host name.

   • Port: Specify the database listen port number. The default port number for Oracle databases is 1521.

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

     If you are unsure what the service name for your database is, you can obtain it from the SERVICE_NAMES parameter in the database's initialization parameter file. If the initialization parameter 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.mydomain.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 the database user's role from the drop-down list. The SYS user requires the SYSDBA role.

   If you are using a Microsoft SQL Server database, provide the following credentials:

   • Unicode Support: Select Yes or No from the drop-down list.

   • Server Name: Enter the host name, IP address, or complete server name in host\server format of the server where your database is running.

   • Port: Specify the database listener port number.

   • Database Name: Specify the name of your database.

   • Username: Specify the name of a user with DBA or SYSDBA privileges.

   • Password: Specify the password for your database user.

   If you are using an IBM DB2 database, provide the following credentials:

   • Server Name: Enter the host name, IP address, or complete server name in host\server format of the server where your database is running.

   • Port: Specify the database listener port number.

   • Database Name: Specify the name of your database.

   • Username: Specify the name of a user with DB Owner privileges.

   • Password: Specify the password for your database user.

   Click Next. A "Checking Prerequisites" screen will appear. If there are errors, some details about the error will be displayed on the Database Connection Details Screen. Fix the error messages and click Next again.

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

5. Select Components Screen

   Near the top of the screen, select Create a New Prefix. If you are the only user of the database instance, you may use the default prefix DEV. If you are sharing the database instance with other Oracle Fusion Middleware users, refer to "Creating Custom Schemas and Tablespaces" in Oracle Fusion Middleware Repository Creation Utility User's Guide for more information about creating and using custom prefixes.

   In the table that lists the available components, select WebCenter Suite. All of the product schemas within this component, including all the dependent schemas, are automatically selected.

   Table 1 lists the required schemas for Oracle WebCenter components for Oracle and Microsoft SQL Server databases:

   Table 1 Required Schemas for Oracle WebCenter Components on Oracle and Microsoft SQL Server Databases

   Component	Schema Owner	Dependencies
   WebCenter Spaces	prefix_WEBCENTER	prefix_MDS (Metadata Services)
   Portlet Producers	prefix_PORTLET	None.
   Discussions	prefix_DISCUSSIONS	None.
   Discussions Crawler	prefix_DISCUSSIONS_CRAWLER	prefix_DISCUSSIONS (Oracle Discussions)
   Wiki and Blogs	prefix_WIKI	None.
   Oracle Content Server 10g	prefix_OCSERVER	None.

   
   

   Table 2 lists the required schemas for Oracle WebCenter components for IBM DB2 databases:

   Table 2 Required Schemas for Oracle WebCenter Components on IBM DB2 Databases

   Component	Schema Owner	Dependencies	Required Operating System Users
   WebCenter Spaces	prefix_WC	prefix_MDS (Metadata Services)	prefix_wc prefix_mds
   Portlet Producers	prefix_PT	None.	prefix_pt
   Discussions	prefix_DS	None.	prefix_ds
   Discussions Crawler	prefix_DC	prefix_DS (Oracle Discussions)	prefix_dc prefix_ds
   Wiki and Blogs	prefix_WK	None.	prefix_wk
   Oracle Content Server 10g	prefix_CS	None.	prefix_cs

   
   

   Note:

   You must remember or make a note of these schema names and the prefix value from this screen; you will need them later when you are configuring your components. You will need to provide the schema name in the format prefix_schemaname.

   Click Next. A "Checking Prerequisites" screen will appear. If there are errors, some details about the error will be displayed on the Select Components Screen. Fix the error messages and click Next again.

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

6. Schema Passwords Screen

   Near the top of the screen, select Use same password for all schemas.

   In the Password field, enter your password. Enter your password again in the Confirm Password field.

   Note:

   You must remember or make a note of the schema passwords from this screen; you will need them later when you are configuring your components.

   Click Next.

7. Map Tablespaces Screen

   Click Next. A "Creating Tablespaces" screen will appear. If there are errors, some details about the error will be displayed on the Map Tablespaces Screen. Fix the error messages and click Next again.

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

8. Summary Screen

   Click Create. A "CREATE" screen will appear. If there are errors, some details about the error will be displayed on the Summary Screen. Fix the error messages and click Next again.

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

9. Completion Summary Screen

   Click Close.

For more information about Repository Creation Utility, refer to Oracle Fusion Middleware Repository Creation Utility User's Guide.

2.5 Installing Oracle WebLogic Server and Creating the Middleware Home

Oracle WebCenter requires an Oracle WebLogic Server on your system. If you do not already have one, follow the instructions in this section to install Oracle WebLogic Server.

1. Download the latest installer from the following URL:

   http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html 
   

   You are looking for the following executable files:

   • wls_1033_linux32.bin (for 32-bit Linux systems)

   • wls_1033_solaris32.bin (for 32-bit Solaris systems)

   • wls_1033_win32.exe (for 32-bit Windows systems)

   • wls_1033_generic.jar (for all 64-bit platforms)

   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. Refer to the Oracle Fusion Middleware certification document for a list of supported JDKs for your platform:

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

2. Run the installer you just downloaded. Some notes for running the installer:

   • Before running the installer, set the DISPLAY environment variable on your system.

   • Replace JAVA_HOME with the installation location of the supported JDK you installed for your platform.

   • If you are installing a 64-bit Oracle WebLogic Server on a 64-bit platform, use the -d64 flag when using 32/64-bit hybrid JDKs (such as the HP JDK for HP-UX and SUN JDK for Solaris SPARC).

     Execute JAVA_HOME/bin/java -version (or JAVA_HOME/bin/java -d64 -version on 32/64-bit hybrid JDKs) to ensure that your JAVA_HOME refers to a 64-bit JDK.

   To run the installer on a 32-bit Linux operating system:

   ./wls_1033_linux32.bin
   

   To run the installer on 32-bit Windows operating systems:

   wls_1033_win32.exe
   

   To run the installer on 64-bit UNIX operating systems:

   JAVA_HOME/bin/java -jar wls_1033_generic.jar
   

   or

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

   To run the installer on 64-bit Windows operating systems:

   JAVA_HOME\bin\java -jar wls_1033_generic.jar
   

3. Welcome Screen

   Click Next.

4. Choose Middleware Home Directory Screen

   Select Create a new Middleware Home.

   Specify the desired location of your new Middleware home directory. If this directory already exists on your system, it must be an empty directory. If this directory does not already exist, then it will be created for you.

   Note:

   You must remember or make a note this location; you will be asked for it later when you are installing Oracle WebCenter.

   For more information about the Middleware home directory, refer to "Middleware Home and WebLogic Home Directories" in Oracle Fusion Middleware Installation Planning Guide.

   Click Next.

5. Register for Security Updates Screen

   Select whether or not you want to receive the latest product and security updates. If you choose not to receive anything, you will be asked to verify your selection before continuing.

   Click Next.

6. Choose Install Type Screen

   Select Typical.

   Click Next.

7. Choose Product Installation Directories Screen

   Specify the desired location for your WebLogic Server home directory.

   For more information about the WebLogic home directory, refer to "Middleware Home and WebLogic Home Directories" in Oracle Fusion Middleware Installation Planning Guide.

   Click Next.

8. Choose Shortcut Location (Windows only)

   If you are installing on a Windows system, you will be asked to specify a location where you would like Windows to create a shortcut to Oracle products.

   Click Next.

9. Installation Summary Screen

   Click Next.

10. Installation Progress Screen

    No action is required on this screen.

11. Installation Complete Screen

    De-select Run Quickstart.

    Click Done.

For more information about installing WebLogic Server, refer to Oracle WebLogic Server Installation Guide.

2.6 Installing and Configure Java Access Bridge (Windows Only)

If you are installing on a Windows machine, you have the option of installing and configuring Java Access Bridge for Section 508 Accessibility. This is only necessary if you require Section 508 Accessibility features:

1. Download Java Access Bridge from the following URL:

   http://java.sun.com/javase/technologies/accessibility/accessbridge/
   

2. Install Java Access Bridge.

3. Copy the access-bridge.jar and jaccess-1_4.jar from your installation location to the jre\lib\ext directory.

4. Copy the WindowsAccessBridge.dll, JavaAccessBridge.dll, and JAWTAccessBridge.dll files from your installation location to the jre\bin directory.

5. Copy the accessibility.properties file to the jre\lib directory.

For more information about Java Access Bridge, refer to "Install and Configure Java Access Bridge (Windows Only)" in Oracle Fusion Middleware Administrator's Guide.

2.7 Installing on DHCP Hosts

If you are installing Oracle WebCenter on a DHCP host, you must follow the configuration steps in this section for your platform.

127.0.0.1 hostname.domainname hostname
127.0.0.1 localhost.localdomain localhost

/bin/ping hostname.domainname

IP_address   hostname.domainname   hostname

2.8 Installing on a Non-Networked Computer

You can install Oracle Web Tier 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 2.7, "Installing on DHCP Hosts" to install a loopback adapter and modify the hosts file on your system.

2.9 Installing on a Multihomed Computer

You can install Oracle WebCenter 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 hostname.

The installer picks up the fully qualified domain name from the first entry in /etc/hosts (on UNIX operating systems) or %SYSTEMROOT%\system32\drivers\etc\hosts (on Windows operating systems) file. So if your file looks like the following:

127.0.0.1 localhost.localdomain localhost
10.222.333.444 myhost1.mycompany.com myhost1
20.222.333.444 devhost2.mycompany.com devhost2

myhost1.mycompany.com would be picked for configuration.

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

3.1 Starting the Installer

To start the installer on UNIX operating systems:

./runInstaller -jreLoc JRE_LOCATION

To start the installer on Windows operating systems:

setup.exe -jreLoc JRE_LOCATION

The installer requires the full path to the location of a Java Runtime Environment (JRE) on your system. When you installed Oracle WebLogic Server, Section 2.5, "Installing Oracle WebLogic Server and Creating the Middleware Home"), a JRE was installed on your system. You can use this location (the location of the jre directory) to start the installer. The default location for the JRE is MW_HOME/jdk160_18 (on UNIX operating systems) or MW_HOME\jdk160_18 (on Windows operating systems), where MW_HOME is the Middleware home directory.

On 64-bit platforms, the JRE location is the JAVA_HOME you used to install Oracle WebLogic Server. Refer to Section 2.5, "Installing Oracle WebLogic Server and Creating the Middleware Home" for more information.

3.2 Installation Screens

To install Oracle WebCenter:

1. Welcome Screen

   Click Next.

2. Prerequisite Checks Screen

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

3. Specify Installation Location Screen

   Oracle Middleware Home: Specify the location where WebLogic Server was installed.

   Oracle Home Directory: Specify the location where you want to install the software:

   • If you specify a directory that already exists, it must be an empty directory and it must be inside the Oracle Middleware home.

   • If you specify a new directory, it will be created inside the Oracle Middleware home.

   This will be your Oracle home directory. Runtime components cannot write to this directory.

   Note:

   For the remainder of this document, this directory will be referred to as your WebCenter Oracle home to avoid any confusion with the Oracle home directories of other Oracle Fusion Middleware products.

   For more information about the Middleware home and Oracle home directories, refer to "Oracle Fusion Middleware Directory Structure" in Oracle Fusion Middleware Installation Planning Guide.

4. Specify UCM Configuration Options Screen

   Deselect Install and Configure Oracle Universal Content Management.

   Click Next.

5. Installation Summary Screen

   Click Install.

6. Installation Progress Screen

   Click Next when the installation is complete.

7. Installation Complete Screen

   Click Finish.

6.1 Launching the Servers

To get your deployments up and running, you must start the Administration Server and various Managed Servers:

1. To start the Administration Server, run the startWebLogic.sh (on UNIX operating systems) or startWebLogic.cmd (on Windows operating systems) script in the directory where you created your new domain.

   On UNIX operating systems:

   MW_HOME/user_projects/domains/domain_name/startWebLogic.sh
   

   On Windows operating systems:

   MW_HOME\user_projects\domains\domain_name\startWebLogic.cmd
   

   This information was provided on the Specify Domain Name and Location Screen in the Configuration Wizard.

2. To start the Managed Servers, run the startManagedWebLogic.sh (on UNIX operating systems) or startManagedWebLogic.cmd (on Windows operating systems) script in the bin directory inside the directory where you created your domain.

   This command also requires that you specify a server name. The servers that need to be started are:

   • WLS_Spaces (Oracle WebCenter Spaces)

   • WLS_Portlet (Oracle WebCenter Portlets)

   • WLS_Services (Oracle WebCenter Web 2.0 Services)

   For example, to start the Oracle WebCenter Spaces server on a UNIX operating system:

   MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.sh WLS_Spaces
   

   On Windows operating systems:

   MW_HOME\user_projects\domains\domain_name\bin\startManagedWebLogic.cmd WLS_Spaces 
   

Before the server is started, you will be prompted for the WebLogic Server username and password. These were provided on the Configure Administrator Username and Password Screen in the Configuration Wizard.

If you do not know the names of the managed servers that need to be started, you can view the contents of the following file on UNIX operating systems:

MW_HOME/user_projects/domains/domain_name/startManagedWebLogic_readme.txt

On Windows operating systems:

MW_HOME\user_projects\domains\domain_name\startManagedWebLogic_readme.txt

Or, you can access the Administration Server console at the following URL:

http://host:admin_server_port/console

Supply the username and password that you specified on the Configure Administrator Username and Password Screen of the Configuration Wizard.

For more information about starting and stopping servers, see "Starting and Stopping Servers" in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server.

6.2 Starting Managed Servers from the Administration Console

In order to start a managed server from the Administration Console, you must first create a machine, then associate the managed server with that machine:

1. Login to the Administration Console.

2. Navigate to Environment > Machines.

3. Click New.

4. Enter a machine name (for example, Machine-WC).

5. In the Administration Console, navigate to Environment > Servers and select the managed server for which you want to associate this machine (Machine-WC). Use the drop-down list to associate the managed server with the machine.

After this procedure, the managed server will start successfully and be accessible.

6.3 Starting Node Manager

Starting Node Manager on a machine that hosts Managed Servers allows 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:

1. On UNIX operating systems, run the WebCenter_ORACLE_HOME/common/bin/setNMProps.sh script.

   On Windows operating systems, run the WebCenter_ORACLE_HOME\common\bin\setNMProps.cmd script.

   This script appends the required properties to the nodemanager.properties file. These properties can also be appended manually, or provided as command-line arguments.

   Note:

   The StartScriptEnabled=true property is required for Managed Servers to receive proper classpath and command arguments.

   The file containing the properties is nm.required.properties.

2. On UNIX operating systems, start Node Manager by running the MWHome/wlserver_10.3/server/bin/startNodeManager.sh script.

   On Windows operating systems, start Node Manager by running the MWHome\wlserver_10.3\server\bin\startNodeManager.cmd script.

For more information about Node Manager, refer to Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server.

6.4 Verifying the Installation

Start your browser and enter the following URLs:

• To access the Administration Server:

  http://host:admin_server_port
  

  This information was visible on the Creating Domain Screen (the last screen) of the Configuration Wizard.

• To access the Administration Server console:

  http://host:admin_server_port/console
  

  You will be prompted for the username and password credentials that you specified on the Configure Administrator Username and Password Screen of the Configuration Wizard.

• To access Enterprise Manager:

  http://host:admin_server_port/em
  

  You will be prompted for the username and password credentials that you specified on the Configure Administrator Username and Password Screen of the Configuration Wizard.

• To access WebCenter Spaces:

  http://host:port/webcenter
  

  The default port number for WebCenter Spaces is 8888.

• To access WebCenter Rich Text Portlet:

  http://host:port/richtextportlet/
  

  To access WebCenter WSRP Tools:

  http://host:port/wsrp-tools/
  

  To access WebCenter OmniPortlet and Web Clipping Portlets:

  http://host:port/portalTools/
  

  The default port number for WebCenter Portlets is 8889.

• To access WebCenter Discussions:

  http://host:port/owc_discussions
  

  The default port number for WebCenter Discussions is 8890.

• To access WebCenter Wiki and Blog Server:

  http://host:port/owc_wiki
  

  The default port number for WebCenter Discussions is 8890.

7.1 Stopping Oracle Fusion Middleware

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

1. Stop the WebLogic Managed Servers.

   On UNIX operating systems:

   MW_HOME/user_projects/domains/domain_name/bin/stopManagedWeblogic.sh managed_server_nanme admin_url username password
   

   On Windows operating systems:

   MW_HOME\user_projects\domains\domain_name\bin\stopManagedWeblogic.cmd managed_server_nanme admin_url username password
   

2. Stop WebLogic Administration Server.

   On UNIX operating systems:

   MW_HOME/user_projects/domains/domain_name/bin/stopWeblogic.sh username password admin_url
   

   On Windows operating systems:

   MW_HOME\user_projects\domains\domain_name\bin\stopWeblogic.cmd username password admin_url
   

For both commands, specify the admin_url using the following format:

http://admin_server_host.admin_server_domain:admin_server_port

For more information about starting and stopping Oracle Fusion Middleware, refer to "Starting and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide.

For more information about starting and stopping servers, see "Starting and Stopping Servers" in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server.

7.2 Removing the Oracle WebCenter Schemas

Run the Repository Creation Utility (RCU) to drop the WebCenter schemas from your database.

./rcu

rcu.bat

7.3 Deinstalling Oracle WebCenter

Deinstalling Oracle WebCenter involves removing the WebCenter Oracle home and the Oracle Common home directories.

The deinstaller will attempt to remove the Oracle home from which it was started. This procedure will not remove any WebLogic domains that you have created - it only removes the software in the Oracle home.

Before you choose to remove any Oracle home, make sure that it is not in use by an existing domain, and also make sure 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.

./runInstaller -deinstall

setup.exe -deinstall

./runInstaller -deinstall

setup.exe -deinstall

7.4 Deinstalling Oracle WebLogic Server

To deinstall Oracle WebLogic Server:

1. Start the deinstaller from the WebLogic_Home/uninstall (on UNIX operating systems) or WebLogic_Home\uninstall (on Windows operating systems) directory. You specified the location of the WebLogic home directory on the Choose Product Installation Directories Screen in Section 2.5, "Installing Oracle WebLogic Server and Creating the Middleware Home".

   On UNIX operating systems:

   ./uninstall.sh
   

   On Windows operating systems:

   uninstall.cmd
   

   You must specify the absolute path to your JRE_LOCATION; relative paths will not work.

   On Windows systems, you can also start the deinstaller from the Start menu by selecting Programs > Oracle WebLogic > Uninstall Oracle WebLogic.

2. Welcome Screen

   Click Next.

3. Choose Components Screen

   By default, all components are selected.

   Click Next.

4. Uninstalling WebLogic Platform Screen

   Click Done.

5. Manually remove the Middleware home directory.

   For example, if your Middleware home directory was /home/Oracle/Middleware on a UNIX operating system:

   > cd /home/Oracle
   > rm -rf Middleware
   

   On a Windows operating system, if your Middleware home directory was C:\Oracle\Middleware, use a file manager window and navigate to the C:\Oracle directory, then right-click on the Middleware folder and select Delete.

7.5 Deinstalling Oracle JDeveloper

If you have installed Oracle JDeveloper on your system, refer to Oracle Fusion Middleware Installation Guide for Oracle JDeveloper for instructions on how to remove this software from your system.

7.6 Removing the Program Groups (Windows Only)

On Windows operating systems, you must also manually remove the program groups from the Start Menu\Programs folder. As an example (the folder names and program group names on your system may be different), you might remove the following from C:\Documents and Settings\All Users\Start Menu\Programs:

• Oracle Fusion Middleware 11.1.1.3.0

• Oracle WebCenter 11g - Home1

• Oracle WebLogic

7.7 Rebooting Your System (Windows Only)

On Windows operating systems, you should reboot your computer after you have finished removing all your programs to ensure proper cleanup.

8.1 Oracle Support Services

If you purchased Oracle Product Support, you can call Oracle Support Services for assistance. Oracle Support Services include phone assistance, version updates and access to our 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 our online Order Tracker which provides detailed order information. Go to the Oracle Store and click on Order Tracker located 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.

At the Support Web Center you will find information on Oracle Support Services, such as:

• 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 options include:

• Technical Assistance Request (TAR) access

• Patch Downloads

• Bug Database Query Access

• Product Life-Cycle Information

You can access My Oracle Support at http://metalink.oracle.com.

8.2 Version Updates

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://oraclestore.oracle.com.

If you do have a currently supported license, you can place non-urgent 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

• Platform

• Product Name

• Shipping Address

• Product Version Number

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

8.3 Premium Services

For information on our Premium Services, including onsite 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.

8.4 Quick Reference

For quick access to additional information, refer to Table 3: