PK  \Eoa,mimetypeapplication/epub+zipPK \EiTunesMetadata.plist~ artistName Oracle Corporation book-info cover-image-hash 292703806 cover-image-path OEBPS/dcommon/oracle-logo.jpg package-file-hash 276124220 publisher-unique-id E14156-08 unique-id 833055302 genre Oracle Documentation itemName Oracle® Fusion Middleware Installation Guide for Oracle Team Productivity Center Server, 11g Release 1 (11.1.1.6.0) releaseDate 2011-10-31T06:58:42Z year 2011 PK̆PK \EMETA-INF/container.xml PKYuPK \EOEBPS/tpcig.htm Oracle® Fusion Middleware Installation Guide for Oracle Team Productivity Center Server

Oracle® Fusion Middleware

Installation Guide for Oracle Team Productivity Center Server

11g Release 1 (11.1.1.6.0)

E14156-08

November 2011

This document provides information on:

1 Oracle Team Productivity Center Server System Requirements

For the most current system requirements, please refer to the Oracle Fusion Middleware Installation Guide for Oracle JDeveloper.

2 Installing the Oracle Team Productivity Center Server

The installation software for Oracle Team Productivity Center Server is distributed as a platform-independent JAR file. Download the Oracle Team Productivity Center Server installation JAR file from the Oracle Technology Network (OTN) web site: http://www.oracle.com/technetwork/developer-tools/jdev/downloads/index.html

You can choose to install the Oracle Team Productivity Center Server either as a new installation or as an update to an existing server. The installation software is the same, but there are slight differences in the procedure for installing the server depending on whether you are creating a new installation or upgrading an existing one. Instructions for installing a new server or updating an existing one are included in Section 2.4, "Installer Screens for Server Installation".

2.1 Before You Begin

Before installing the Oracle Team Productivity Center Server, take note of the following terms that will help manage the server during and after installation:

  • Client—the set of features in Oracle JDeveloper that allow interaction with team members, selecting work items, and otherwise tracking project development.

  • Server—the software that manages the connections between the team's TPC features in Oracle JDeveloper and data repositories (such as a bug database, feature wiki, or directory of product features and specifications).

  • Connector—the element that defines the data structures and user interface between Oracle Team Productivity Center and a given data repository. For example, presenting a list of bugs from the bug tracking tool in Oracle JDeveloper requires a connector to the bug tracking tool. For more information on this, see the online help for developing a connector (look up how to craft such a link).

  • Plugin—Oracle Team Productivity Center uses a distinct plugin for each automated build system. The plugin is installed on the server for its automated build system, and sends data to Oracle Team Productivity Center.

The Oracle Team Productivity Center installation package can perform the following functions:

  • to perform the initial installation of the server

  • to install or update connectors that the existing server installation will be able to access (such as project tracking software, or a feature/specification repository)

  • to install or update plugins to external servers (such as build, test, or continuous integration servers) that the existing Oracle Team Productivity Center Server can access

  • to install or update the Hudson continuous integration server

It is possible to install the Oracle Team Productivity Center software without installing a connector at the same time. Installing a new connector can be performed at any time after the installation of the server software. Additionally, it is possible to install the Hudson continuous integration server without integrating it with Oracle Team Productivity Center.

2.2 Prerequisites for Installation

Before you run the installer, ensure that the following prerequisites are satisfied:

  • Installation requires entering a user ID and password for the database to which Oracle Team Productivity Center is to be connected. Make sure that you have all user privileges that you require for full access to this database before beginning installation. For example, if an Oracle database is used, please make sure the user has been granted Connect and Resource options.

  • Make sure to download the Oracle Team Productivity Server installation package, available from the Oracle Technology Network (OTN) web site: http://www.oracle.com/technetwork/developer-tools/jdev/downloads/index.html

  • If you are using Oracle WebLogic Server as the installation server, make sure you are using 11g Release 1 (10.3.6).

Make a note of the directory containing the downloaded installation file, called tpcinstaller.jar. Installation requires navigating to that directory and executing a command-line instruction to install Oracle Team Productivity Center.

Make sure the system on which Oracle Team Productivity Server is to be installed is running the latest JDK, as required by the Oracle Fusion Middleware Installation Guide for Oracle JDeveloper.

2.3 Starting the Installer

The Oracle Team Productivity Center Server installation package is a JAR file. The package can be installed on Windows, Linux, or Mac OS X platforms that meet the Oracle JDeveloper standard requirements. The installation system must also be running a Java EE application server, on which the Oracle Team Productivity Center server will run when installed.

Installation begins from the command line; after launching the installer, it will continue with a sequence of installation screens containing selections as the installer proceeds with the installation.

To start the installer:

  1. Navigate to the directory containing the Oracle Team Productivity Center installation file, tpcinstaller.jar.

  2. From a command line (that is, a Linux or DOS command shell), type the following command, substituting the installation system's JAVA_HOME directory where indicated:

    set JAVA_HOME=location of java_home

    For example, on a Windows system with JDK 1.6.0_21 installed in the Program Files directory on the C:\ drive, the command would be:

    set JAVA_HOME=C:\Program Files\Java\jdk1.6.0_21

  3. When the preceding command completes and the system command-line prompt is once again visible, type the following command:

    set PATH=%JAVA_HOME%\bin;%PATH%

  4. When the preceding command completes and the system command-line prompt is once again visible, type the following command:

    java -jar tpcinstaller.jar

    This launches the Oracle Team Productivity Center installer, which proceeds with a number of screens as shown in the following section.

2.4 Installer Screens for Server Installation

The installer provides several screens, which specify various parameters for the installation. Depending on whether you are installing Oracle Team Productivity Center for the first time, or updating an existing installation, the responses you give to the screens may change. Follow the instructions shown here:

  1. Welcome

    On this screen, the Oracle Team Productivity Center installer shows the list of steps you can perform.

  2. Select Installation Type

    Select the components of Oracle Team Productivity Center that you wish to install:

    • TPC Server:

      Select this option to install the Oracle Team Productivity Center Server framework and database schema.

    • Connectors:

      Select this option to install connectors for information repositories you plan to use with Oracle Team Productivity Center. You will select the individual connectors, and the source from which you wish to install them, in a later step.

    • Hudson Server:

      Select this option to install the .war file for the Hudson server. This installs the Hudson continuous integration server.

    • Test/Build Plugins:

      Select this option to install the test/build plugins. The test/build plugins integrate test and build summary information required for integrating a number of systems that plug into the Oracle Team Productivity Center, such as the build dashboard and build summary screens.

    After entering all the selections, click Next. The Oracle Team Productivity Server installer will verify the connection before proceeding to the next step.

  3. Specify Database Connection Information

    Enter the following information for this installation's database connection:

    • Connection type:

      Connect using either generic JDBC or Oracle JDBC. Selecting generic JDBC causes the installer to prompt for the driver to use.

      For purposes of this installation, select Oracle (JDBC)

    • JDBC URL:

      Type the JDBC URL for the database connection used by this server. For example:

      jdbc:oracle:thin:@192.0.2.1:1521:orcl

    • Username:

      Type the selected username for the database to which you are connecting.

    • Password:

      Type the selected user's password.

    After entering all the selections, click Next. The Oracle Team Productivity Center Server installer will verify the connection before proceeding to the next step.

    You can install TPC server and connectors to a database other than an Oracle database. For example, if you are using MySQL, you would specify the values as follows:

    • Connection Type: Generic JDBC

    • Driver Library: <JDEV_HOME>/oracle/wlserver_10.3/server/ext/jdbc/mysql/mysql-connector-java-commercial-5.0.3-bin.jar

    • Driver Class: com.mysql.jdbc.Driver

    • JDBC URL: jdbc:mysql://<host>:3306/<db_name>

  4. Installation Detection

    This screen automatically detects whether an earlier version of Oracle Team Productivity Center has been installed.

    If Oracle Team Productivity Center has not been installed previously, the screen will indicate that this is a new installation. Click Next.

    If Oracle Team Productivity Center has been installed previously, the installer will detect this, and will present options for updating the server, updating the connectors, or both. When running this installer, make sure to select only the Update type.

    Select at least one of these installation elements (if available) before the installer will continue.

    For the purpose of this instruction, select the checkbox labeled Server, then click Next.

    Instructions for installing or updating an Oracle Team Productivity Center connector are described in Section 3, "Installing an Oracle Team Productivity Center Connector".

  5. Create Administrator Account (New Installation Only)

    This step applies only to the initial installation of Oracle Team Productivity Center. If you are updating the Oracle Team Productivity Center server or connectors, use the administrator account information entered during the initial installation of Oracle Team Productivity Center.

    Installation requires creating an administrator account that will be used to seed the database with an Oracle Team Productivity Center user that has administrative privileges. The account name does not have to be the same as any existing name in the Oracle Team Productivity Center database. Be sure to follow safe, high-security password guidelines when creating your password.

    Enter the desired user name, followed by the password for the account being created. Repeat the password to confirm, then click Next.

  6. Specify Application Server Location

    Enter a fully qualified path to the location on the Java EE application server selected to run the Oracle Team Productivity Server. It is possible to type the path, copy and paste it from another location screen, or click Browse to search for the path in the local file system.

    For example, on a Windows system running the Oracle WebLogic server, enter the following application server location:

    C:\<WebLogic_Server_Home>\user_projects\domains\<Your_Domain>\autodeploy

    where <fields> represent the specific path information on the installation system.

    For example, on a Windows system running the Apache Tomcat application server version 6.0.16 from the top level of its C:\ drive, enter the following application server location:

    C:\apache-tomcat-6.0.16\webapps

    If you are updating an existing installation of Oracle Team Productivity Center, be sure to use the same path used for the previous installation.

    To select the application server type, click on the drop-down list labeled Select the application server type. Choose the appropriate server type from the list.

  7. Select Connector Source

    On this screen, specify the location of the source file for the connector. Options are to search the Oracle JDeveloper Update Centers for connectors, or to install from a local file.

    To search the Oracle JDeveloper Update Centers:

    • Select Search Update Centers.

    • Select one or more of the Update Centers displayed on the screen.

    • Click Next.

    To install from a local file:

    • Select Install From Local File, and then click Next.

    • Enter the pathname of the connector ZIP file in the local file system. For example: C:\tpc-connector-msprojectserver_bundle.zip

    • Click Next.

  8. Select Connectors

    On this screen, choose the connectors you wish to install from the list at the connector source specified in the previous step. You can select connectors individually, or choose Select All to install all connectors at the specified connector source.

    To proceed with the installation, click Next.

  9. Specify Hudson Server Location

    On this screen, enter the fully qualified path on the Java EE application server to which you wish to install the Hudson application .WAR file.

    To proceed with the installation, click Next.

  10. Select Plug-ins

    On this screen, choose from the available plug-ins for Oracle Team Productivity Center. Note in particular the information for the Hudson and CruiseControl plug-ins.

    Hudson Plug-in: Enter the fully qualified path to which you wish to install the Hudson application.WAR file.


    Note:

    The Hudson administrator must provide the password when creating the job. The Oracle Team Productivity Center Server administrator password does not display on the screen while entering the Hudson information.

    CruiseControl Plug-in: Enter the fully qualified path to which you wish to install the CruiseControl plug-in.

    To proceed with the installation, click Next.

  11. Installation Summary

    The final screen of the installation wizard displays the key information about the installation:

    • Oracle Team Productivity Center Server location

    • Database details

    • Selected connectors

    • Selected plug-ins, with the path to the installed tool location

    To complete the installation, click Finish. The wizard then displays the installation progress.

  12. After installation is complete:

    The Oracle Team Productivity Center installer only ships with the Oracle JDBC Driver. If a database other than Oracle (for example, MySQL) is used, you need to make that database's driver available for your Application Server to use. In some case, you need to copy the driver to the designated folder of your Application Server before you can bring up and connect to Oracle Team Productivity Center Server.

    For WebLogic, the MySQL JDBC driver is installed in the folder <WL_HOME>/server/lib through weblogic.jar. It will be loaded when the server starts. Therefore, you do not need to do anything for this driver. If you plan to use a JDBC driver other than Oracle and MySQL, specifically one that is not installed with the WebLogic folder, see "Third-Party JDBC Drivers Installed with WebLogic Server."


    Note:

    If you use a WebLogic domain for TPC server installation, copy the driver to your <JDEV_HOME>/user_projects/domains/<domain>/lib folder instead.

    If you are using Oracle JDeveloper Studio, MySQL JDBC driver is shipped in <JDEV_HOME>/oracle/wlserver_10.3/server/ext/jdbc/mysql/mysql-connector-java-commercial-5.0.3-bin.jar.


    Start Oracle JDeveloper and download and install the Oracle Team Productivity Center client extension. To download the extension in Oracle JDeveloper, click the Help menu, and then select Check for Updates. The online Help for Oracle Team Productivity Center contains instructions for the administrator on how to set up Team Productivity Center inside Oracle JDeveloper.

2.5 Upgrading Oracle Team Productivity Center Server with Apache Tomcat 6.0.20

When the Oracle Team Productivity Center installer is used to update a Team Productivity Center server running on Apache Tomcat version 6.0.20, any new or updated Team Productivity Center web service classes cannot be auto-deployed correctly by the server. This causes an Oracle Team Productivity Center login issue, as observed in the server's log file. Upgrading the Team Productivity Center server running on other versions of Apache Tomcat does not have this problem.This is due to an issue with Apache Tomcat 6.0.20. When using this version of Apache Tomcat, updates to Team Productivity Center web service classes are not properly re-deployed, even with autoDeploy set to "true" in the Tomcat server.xml file.To resolve this issue:

  1. Complete the Oracle Team Productivity Center update, as described in Section 2.3, "Starting the Installer" and Section 2.4, "Installer Screens for Server Installation".

  2. If the Tomcat server is running, shut it down.

  3. Delete the folder <tomcat_install_folder>\webapps\otpc.

  4. Restart the Tomcat server.

If you are using MySQL with Tomcat, download the driver from your provider, then copy the driver to your <TOMCAT_HOME>/lib folder.

If you are using Oracle JDeveloper Studio, the MySQL JDBC driver is shipped in <JDEV_HOME>/oracle/wlserver_10.3/server/ext/jdbc/mysql/mysql-connector-java-commercial-5.0.3-bin.jar.

2.6 Backward Compatibility with Previous Oracle Team Productivity Center Server and Client Versions

Backward compatibility is supported on a limited basis between Oracle Team Productivity Center Server and Oracle Team Productivity Center client software as follows:

  • If you install a newer server with older clients, you will not be able to log in to the server with the older client.

  • If you install newer clients with an older server, the clients will be able to log in to the older server.

For best results and full compatibility, it is recommended that you update both the client and the server software when you install a new version of Oracle Team Productivity Center.

3 Installing an Oracle Team Productivity Center Connector

Installing a connector begins by launching the Oracle Team Productivity Center installer, as described in Section 2.3, "Starting the Installer". When you launch the installer, select the information from the installer screens as described below.

Note that you can also use the installer to update an Oracle Team Productivity Center connector. If you install a later version of the same connector as one that has already been installed, the installer will overwrite the earlier version and install the later version in its place.

3.1 Installer Screens for Connector Installation

The installer provides several screens that specify various parameters for the installation:

  1. Select Installation Type

    This screen presents the option of installing the server alone, one or more connectors alone, or both the server and connectors. Select at least one of these installation elements before the installer will continue.

    For the purpose of this instruction, select the checkbox labeled Connectors, then click Next.

    For information on installing an Oracle Team Productivity Center server, see Section 2.4, "Installer Screens for Server Installation".

  2. Specify Database Connection Information

    Enter the following information for the selected database connection:

    • Connection type:

      Connect using either generic JDBC or Oracle JDBC. Selecting generic JDBC makes the installer prompt for the driver to use.

      For purposes of this installation, select Oracle (JDBC)

    • JDBC URL:

      Type the JDBC URL for the database connection. For example:

      jdbc:oracle:thin:@192.0.2.1:1521:orcl

    • Username:

      Type the selected username on the database.

    • Password:

      Type the user's password.

    After entering all selections, click Next. The Oracle Team Productivity Server installer will verify the connection before proceeding to the next step.

  3. Select Connector Source

    On this screen, specify the location of the source file for the connector. Options are to search the Oracle JDeveloper Update Centers for connectors, or to install from a local file.

    To search the Oracle JDeveloper Update Centers:

    1. Select Search Update Centers.

    2. Select one or more of the update centers displayed on the screen.

    3. Click Next.

    To install from a local file:

    1. Select Install From Local File, and then click Next.

    2. Enter the pathname of the connector ZIP file in the local file system. For example:

      C:\tpc-connector-msprojectserver_bundle.zip

      After making the selection, click Next.

  4. Installation Summary

    The summary screen of the installation wizard displays the key information about the installation:

    • Database connection information

    • Selected connectors, with the path to the ZIP or JAR file containing the connector components

    Once satisfied with the data, click Finish to proceed with the installation. The wizard then displays the installation progress.

The installer will unpack the compressed file and make connections to the database as required to configure this connector for use. When the installer indicates that it has completed the installation, connect to the data repository for the connector. Details for using the connector are in the Oracle JDeveloper on-line help for Oracle Team Productivity Center.

3.2 Setting Up Repositories for Default Connectors

The JIRA, Microsoft Project, and Rational Team Concert connectors to Oracle Team Productivity Center require some initial setup before Oracle Team Productivity Center can interact with them. The following three sections discuss initial setup for each of these connectors.

3.2.1 Setting Up a JIRA Repository

In order for the JIRA connector to retrieve data from the server, the JIRA server's Remote API must be enabled. To enable remote APIs please follow the following steps.

To enable the JIRA Server's Remote API:

  1. Log in to the JIRA server as administrator.

  2. Select the Administration tab.

  3. From the left pane, locate the Global Settings group, then select General Configuration.

    At the bottom of the page, select Edit Configuration.

  4. In the Options section, locate the setting Accept remote API calls and select ON.

3.2.2 Setting Up a Microsoft Project Repository

Oracle Team Productivity Center MS Project Server connector supports the two user authentications used by Project Server: windows and forms.

To configure forms authentication for Project Server 2007 please see this article on MSDN:

http://technet.microsoft.com/en-us/library/cc197472(office.12).aspx

3.2.3 Setting Up a Rational Team Concert Repository

Oracle Team Productivity Center's OSLC (Open Services Lifecycle Collaboration) connector for RTC (Rational Team Concert) supports the two user authentications used by the RTC server: basic and forms.

To configure forms authentication for RTC, please refer to article:

http://jazz.net/library/techtip/75

In case the host name of the RTC server is not accessibility can connect to the server by its IP address.

To connect to the RTC server by its IP address:

  1. Log in to the Rational Team Concert server as Administrator.

  2. Locate the Server link on top of the navigation bar.

  3. On the left pane, select Configuration > Advanced Properties.

  4. Locate the entry for com.ibm.team.repository.servlet.internal.ServletConfigurationService

  5. Double-click Host %^Name.

  6. Enter the IP address of the server in the edit box.

4 Installing Oracle Team Productivity Center Server on a Production WebLogic Server Database

Installing Oracle Team Productivity Center Server on a production Web Logic Server database requires a specific procedure.

4.1 Deploying Oracle Team Productivity Center to a Production WebLogic Server

  1. Install Oracle Team Productivity Center server.

    For information on installing an Oracle Team Productivity Center server, see Section 2.3, "Starting the Installer".

  2. Move the WebLogic Server file otpc.war

    Locate the file otpc.war that you deployed on your Web Logic Server autodeploy folder. Move it to another location in order to perform manual deployment successfully. Note the new location, as you will use it in the following step.

  3. Log in to WebLogic Server administration console

    Once the domain server is running, log in to its Admin Server Console using your WebLogic Server Administrator user name and password. You can log in either from the Fusion Middleware Start menu or from the server login page, located at http://<hostname>:<port>/console/login/LoginForm.jsp

  4. Select Deployments from the Domain Structure panel.

  5. Click the Lock & Edit button from the Change Center panel to edit the Deployments page.

  6. On the Deployments page, click Install. Specify the path to which you copied your otpc.war file, and then click Next.

  7. Verify the options shown on the Install Application Assistant page, and then click Next.

  8. Verify the optional settings, and then click Next.

  9. Click Finish when you are done with verifying or changing settings in the Install Application Assistant.

  10. Click Save on the Settings for otpc page. Wait until you get the confirmation message, Settings updated successfully from WebLogic Server.

  11. Click Activate Changes from the Change Center panel to activate deployment changes. Wait until you see the message All changes have been activated. No restarts are necessary.

  12. Select Deployments from the Domain Structure panel.

  13. Select the checkbox next to otpc Deployment on the Deployments list, then click Start. Select Service all requests, and then click Yes on the Start Deployments page.

  14. Wait for the message, otpc application has Active state. It may be necessary to refresh the WebLogic Server console before you can login to Team Productivity Center.

4.2 Installing a WebLogic Server Production Server

The final portion of the process for installing Oracle Team Productivity Center on a production WebLogic Server database is to create a WebLogic Server production domain, using the Fusion Middleware Configuration Wizard.

  1. Select Create a new WebLogic Domain, and then click Next.

  2. Select Default, and then click Next on the Select Domain Source window.

  3. Enter domain name and domain location, and then click Next.

  4. Specify WebLogic Server Administrator user name and password, and then click Next.

  5. Select Production Mode, and then click Next, Next, Create.

You can now bring up the newly created production domain yourself, or follow these steps:

  1. Select Start Admin Server, and then click Done.

  2. Type in your WebLogic Server Administrator user name and password at the startWebLogic.cmd prompt.

5 Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.


Oracle® Fusion Middleware Installation Guide for Oracle Team Productivity Center Server 11g Release 1 (11.1.1.6.0)

E14156-08

Copyright © 1997, 2011, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

PKJgOPK \EOEBPS/dcommon/oracle.gifJGIF87aiyDT2F'G;Q_oKTC[ 3-Bq{ttsoGc4I)GvmLZ).1)!ꑈ53=Z]'yuLG*)g^!8C?-6(29K"Ĩ0Яl;U+K9^u2,@@ (\Ȱ Ë $P`lj 8x I$4H *(@͉0dа8tA  DсSP v"TUH PhP"Y1bxDǕ̧_=$I /& .)+ 60D)bB~=0#'& *D+l1MG CL1&+D`.1qVG ( "D2QL,p.;u. |r$p+5qBNl<TzB"\9e0u )@D,¹ 2@C~KU 'L6a9 /;<`P!D#Tal6XTYhn[p]݅ 7}B a&AƮe{EɲƮiEp#G}D#xTIzGFǂEc^q}) Y# (tۮNeGL*@/%UB:&k0{ &SdDnBQ^("@q #` @1B4i@ aNȅ@[\B >e007V[N(vpyFe Gb/&|aHZj@""~ӎ)t ? $ EQ.սJ$C,l]A `8A o B C?8cyA @Nz|`:`~7-G|yQ AqA6OzPbZ`>~#8=./edGA2nrBYR@ W h'j4p'!k 00 MT RNF6̙ m` (7%ꑀ;PKl-OJPK \EOEBPS/dcommon/oracle-logo.jpgg:JFIFC    $.' ",#(7),01444'9=82<.342C  2!!22222222222222222222222222222222222222222222222222'7" }!1AQa"q2#BR$3br %&'()*456789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz w!1AQaq"2B #3Rbr $4%&'()*56789:CDEFGHIJSTUVWXYZcdefghijstuvwxyz ?( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( ( (QEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQE!KEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEzE7V%ȣOΏ9??:a"\fSrğjAsKJ:nOzO=}E1-I)3(QEQEQEQEQEQEQE֝Hza<["2"pO#f8M[RL(,?g93QSZ uy"lx4h`O!LŏʨXZvq& c՚]+: ǵ@+J]tQ]~[[eϸ (]6A&>ܫ~+כzmZ^(<57KsHf妬Ϧmnẁ&F!:-`b\/(tF*Bֳ ~V{WxxfCnMvF=;5_,6%S>}cQQjsOO5=)Ot [W9 /{^tyNg#ЄGsֿ1-4ooTZ?K Gc+oyڙoNuh^iSo5{\ܹ3Yos}$.nQ-~n,-zr~-|K4R"8a{]^;I<ȤL5"EԤP7_j>OoK;*U.at*K[fym3ii^#wcC'IIkIp$󿉵|CtĈpW¹l{9>⪦׺*ͯj.LfGߍԁw] |WW18>w.ӯ! VӃ :#1~ +މ=;5c__b@W@ +^]ևՃ7 n&g2I8Lw7uҭ$"&"b eZ":8)D'%{}5{; w]iu;_dLʳ4R-,2H6>½HLKܹR ~foZKZ࿷1[oZ7׫Z7R¢?«'y?A}C_iG5s_~^ J5?œ tp]X/c'r%eܺA|4ծ-Ե+ْe1M38Ǯ `|Kյ OVڅu;"d56, X5kYR<̭CiطXԮ];Oy)OcWj֩}=܅s۸QZ*<~%뺃ȶp f~Bðzb\ݳzW*y{=[ C/Ak oXCkt_s}{'y?AmCjޓ{ WRV7r. g~Q"7&͹+c<=,dJ1V߁=T)TR՜*N4 ^Bڥ%B+=@fE5ka}ędܤFH^i1k\Sgdk> ֤aOM\_\T)8靠㡮3ģR: jj,pk/K!t,=ϯZ6(((((((49 xn_kLk&f9sK`zx{{y8H 8b4>ÇНE|7v(z/]k7IxM}8!ycZRQ pKVr(RPEr?^}'ðh{x+ՀLW154cK@Ng C)rr9+c:׹b Жf*s^ fKS7^} *{zq_@8# pF~ [VPe(nw0MW=3#kȵz晨cy PpG#W:%drMh]3HH<\]ԁ|_W HHҡb}P>k {ZErxMX@8C&qskLۙOnO^sCk7ql2XCw5VG.S~H8=(s1~cV5z %v|U2QF=NoW]ո?<`~׮}=ӬfԵ,=;"~Iy7K#g{ñJ?5$y` zz@-~m7mG宝Gٱ>G&K#]؃y1$$t>wqjstX.b̐{Wej)Dxfc:8)=$y|L`xV8ߙ~E)HkwW$J0uʟk>6Sgp~;4֌W+חc"=|ř9bc5> *rg {~cj1rnI#G|8v4wĿhFb><^ pJLm[Dl1;Vx5IZ:1*p)إ1ZbAK(1ׅ|S&5{^ KG^5r>;X׻K^? s fk^8O/"J)3K]N)iL?5!ƾq:G_=X- i,vi2N3 |03Qas ! 7}kZU781M,->e;@Qz T(GK(ah(((((((Y[×j2F}o־oYYq $+]%$ v^rϭ`nax,ZEuWSܽ,g%~"MrsrY~Ҿ"Fت;8{ѰxYEfP^;WPwqbB:c?zp<7;SBfZ)dϛ; 7s^>}⍱x?Bix^#hf,*P9S{w[]GF?1Z_nG~]kk)9Sc5Ո<<6J-ϛ}xUi>ux#ţc'{ᛲq?Oo?x&mѱ'#^t)ϲbb0 F«kIVmVsv@}kҡ!ˍUTtxO̧]ORb|2yԵk܊{sPIc_?ħ:Ig)=Z~' "\M2VSSMyLsl⺿U~"C7\hz_ Rs$~? TAi<lO*>U}+'f>7_K N s8g1^CeКÿE ;{+Y\ O5|Y{/o+ LVcO;7Zx-Ek&dpzbӱ+TaB0gNy׭ 3^c T\$⫫?F33?t._Q~Nln:U/Ceb1-im WʸQM+VpafR3d׫é|Aү-q*I P7:y&]hX^Fbtpܩ?|Wu󭏤ʫxJ3ߴm"(uqA}j.+?S wV ~ [B&<^U?rϜ_OH\'.;|.%pw/ZZG'1j(#0UT` Wzw}>_*9m>󑓀F?EL3"zpubzΕ$+0܉&3zڶ+jyr1QE ( ( ( ( ( ( ( (UIdC0EZm+]Y6^![ ԯsmܶ捆?+me+ZE29)B[;я*wGxsK7;5w)}gH~.Ɣx?X\ߚ}A@tQ(:ͧ|Iq(CT?v[sKG+*רqҍck <#Ljα5݈`8cXP6T5i.K!xX*p&ќZǓϘ7 *oƽ:wlຈ:Q5yIEA/2*2jAҐe}k%K$N9R2?7ýKMV!{W9\PA+c4w` Wx=Ze\X{}yXI Ү!aOÎ{]Qx)#D@9E:*NJ}b|Z>_k7:d$z >&Vv󃏽WlR:RqJfGإd9Tm(ҝEtO}1O[xxEYt8,3v bFF )ǙrPNE8=O#V*Cc𹾾&l&cmCh<.P{ʦ&ۣY+Gxs~k5$> ӥPquŽўZt~Tl>Q.g> %k#ú:Kn'&{[yWQGqF}AЅ׮/}<;VYZa$wQg!$;_ $NKS}“_{MY|w7G!"\JtRy+贾d|o/;5jz_6fHwk<ѰJ#]kAȎ J =YNu%dxRwwbEQEQEQEQEQEQEQEQEQE'fLQZ(1F)hQ@X1KEQE-Q@ 1KE3h=iPb(((1GjZ(-ʹRPbR@ 1KE7`bڒyS0(-&)P+ ڎԴP11F)h&:LRmQ@Q@Š(((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((_ğ<+F; sU%ԑ >,BH(uSU xþ1Wϲs${wgoQn_swB/'L\ܓFgԏZ ^dj^L^NmH Ҁ6(?nƓjh%ةlΣ /F6}pj2E3HgHЌ(UQR8oX,G8OB]>o9@$xWy'ڹOM=ҼWb"٠9-*r⬻zWokeh͝(F@n~X=q+⟇1b>ƑeIX.~C,o5የ-m;D Nʬ` `+CcE??Ki!R!cxw[ jvc}&Eٱ7T)8&þ/?os$wSn^bo:-4^js4JKm!#rv89>' O59t , \8r,Vk|IgxEv((RmĜ+bkz6,u/}-|.'<VÚ~tk,^cH61¢ !;M;Ėz[#CuAƶ+j_&*/;Q8d ǹHyAsM↷7l-6rò,%Fs;A*',}'f[]tݷs~UWhk?:4JE]WpcY=" ƚw/|_xSw(kycH#r28,X7D5Kh76 mɍ~0H;6194WpGӧգ%8Z&GdPƧo6kcO5Kv`{}fyq \`@?Kv=26OޝyAe Qɼ芍H8͟2敮j#;iѻm؏6+wTx;KYY\-%'Aӣ?|=\-ٴk+٬$ɷIvQ3?(v(};Ėz[#CuAƼ?.~ XAJ)?ld5g@u`1Ԝw7Q/+@GIgZk:kHꧽlW m/uS47H] St Mw=u寋tKX|u-u } ؼc`9ܠ?+70v|8R:@ڞ0ωuh<9GF^;nTc*(r |g!?X8Oۭ"nٽmqg,__r^_ik7<4\X2HrzWşZaFw/$x%3v@y8+?]|c}il -jk&- !;; o7<# 4k+m ZY~էvFJF(F獡\WQ@W "rS?'G?~gݷsۭnxzl|SY麥ŭuHp#fS]ĀǎFHz%/H%na_˂#(!aN6HKz5|5s,'z'so [ `Pm7Ϭ>ig;ۛco޹l#f H|Oxzk6$nR{FUp 0$ hP<EuE4)-pdcw>GU$NHHFd^ƍq+ˡ\ܤ.Vn:W %pޙEy\:_5ωXi6Ir+KB27mِ䞓ú&cƚ;K?dz3˄F gv^e|>t<ɠ#7MG{;AhPϻ$W%em,qEr' ]~Jb{!}󝭓9p JvI8?Go_gٷvv3{DŽn4vwV}3&vơGEq1𶩨:w<3}0n7p1Tc#ГpmC'kxI{wG4q+) JF# c L<> $x.5?KiulԻ{t*.}3eKIoQ%v_j #Aeo%ċ dQ^oAi5{I;bHXrWnz:Y#Vatk.X/m䷑ 0WR3k=< AC&w[]Go,"*BBGBJ+|@♴'c$BZ0f-&ھgԯ}AfCU}σo)j4yo<{x{De'Lr_2i0S $Vk(C[?54?OZ]B+Uw* ejM:Wf:7jUf\n9a QzxVO?vzxѭTJVkB[Kq 9qqG=y_^4Ѵ;7Rr,'%gp -z;*Ԭխ>KIcBwn,Td(?6F 7 r{8k0W\.ņH3 p*Fu=_T~VN!PDJ\ r~*[ω,SF9,MmrfDb('kp8#ּ#GӬf'|S/ [Jnr} ݾ cpv m(|=}/u[BI &RUK.FH~O~v}8*h< $`:%:7][L!MWO''޽¼gο56m;T7dΑn]lX" H3Ԇ۹5m'V]&S2VIÈ0V#qWqxWž"^_BK+ŜkXج z,Ʊ=kVI]ʖ 3"b'8s.$xA/ 5ަ̊-|(G,@$d_ bO蚕栉$s6v]*A_|:GĽNYG-?P@|6wR;I.'5QMȚ[`%zǧ\ewWo_uſWOIր=_+G7K{ % 0V?{ExWڏo+wQK a:\xw៊un ig$Ah ĨLN01O[ͬ?CD `T…N[~L+ZAik#2pIks^}⏇,my:F#$W۞ d9m>-j0뚟|+s(UZ]6$$S96ʆ+{n+Il.9|:Lt8t7^'>q vh)n]8,fBH  \^+-{ϼ'temF;Omಣv npACZ{I/-a[Z)O 233XOk~SϢk:LIc=I.- H*}x>*,>;3%\N4oVܻEU9 g r+cz>&}s h~YK$Y~8׭4|;V݆xgyuKnEPH|c5'5;z?m&3˗c&"9r(}sYHz .${ (|}mXl{j.{ [%@+=QxPIyvDSm&z׌$pk1B _sO@ 9gwk)<(3}ؿ95_v|3B4Ԯ5TlMRňb= ?5ׁ~+[$ˬjqfv1I=vjv:T?hɑvlDF8b焼ix;H1IfSfO A fg0zveQl.hqSq_h-A82\;śl |ܠ ~euh4k 8[XSq;Q@ 2y8u?DګG<7A "I( 2O5Jt_jQ^.g3JBw3_粆<|H|avq/^IbFvW2q@%msU֭t/]3Z29P;@[ ㉵:v[ڼlU@5m'|gο5앇&/k{xyu]#5, rIxW~:4tٸ#D~]K1W~xSR En9&D ?mc)SĺڜrkCßg)!6V"K344=K|_?xgVO)~))# b#^ ѼW~qERU7L방\r21]뚕G'伊fR[$y@ OWv>qovl!b+gr2xh(((((((((((S~'Vm4Tio w  "3QxcN.uz j6 f):2Ta=r[<@}QcZ @$b9V-?ÒxmNq98@W&>%=5 ֣}>W&'T"o\'8>g>yiv6X)ч%<8\OŔ 1x1{/|Uxl}n H]^'~ U-|PQEr_wmuhT 3+k9<[h_i*pyu Q^_C:'tKtAih}I ,$*64U{g\gynhϗ`ߎv8?ޡOrh! m^EEpF yH꺭jzvvY_I8I \݇?fzIuvp$i[~B9Š+^#'I5O./n7y<={b=B"ψn %(#Ds+:n@Vs985~fGvaRݱHB(▻V Wx7]5R֯{Ř c'4Esdž] WHZ4r16ߘ N3~,E.4z4}A,[܊FGB3<@}izv&uzbD&7A!CHc@ek} y#1mdPH#8Q@%}QcZ @$b9WIcgyawݬ4 H8a~b$> ӣ×V6RJkO*"gG ;H ?Vu=;^\ԿnnnWW_o6<{=RXjZlio 5hU` `,^^U4H'fFxd 7gRG 9/h>mGplNUy'jbi`}%dٷvw}3׏m?·GN6/g_g|'z|^\!>ם'sh/X2[Gck,Zc`9^N|nkw˺5-~^f h9ʳhUW_XYvrYAwk&7_qwU_x>G$?vv/}[> KbZUkAHFU'sݟF𕦹]x":N{w:O"1%ܟ@xWo;}?AWG9=2}k+>DӬuGV}y_k{3]8,_ j"#\^>UPIKf*ŕ8b ?7??[jjvǟc}^6O[kOoJ&'Gd&6@u 6@<k?#yhOt:̌;Aln;bp4𾨺ER۽dsGBhᗂA.qIr47b0IמK–1m2mJ; &W&1? lA4<4[~]CQͤ/A'!gzxxN ˤ*ƉC|̄P+S@m-t;K@),YRĖ=I<:@ ?udĞѼ]GaY9DʞkLJr:>xLm/.T\kN ր; cS~K2Ʊ23?yC|zr:? IubXZ&]DXawmw_2_zW.d v#ʶ-4M:Xukk}ڗw<ڜq@7^/{?kwrV"}7V&>XL6(Y`q=υ>2kW1`9$Ur=  <kk7zI(F2H` 䌜'9ɮ}*FG{hƟ%kxE۰mѷ1Mqwhu yx?tr?2H'ĉticT:`09C8-a74 cH[alFIF9Y!q=ƅk<I #m8ؐ3@p3PƯ|-Ԭ巂΄"/Vlp9נW/ x@&)xw$@b.mTl;\s]EQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEQEPKggPK \EOEBPS/dcommon/cpyr.htmD Oracle Legal Notices

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Oracle Logo

PK0hPK \EOEBPS/dcommon/blafdoc.cssc@charset "utf-8"; /* Copyright 2002, 2011, Oracle and/or its affiliates. All rights reserved. Author: Robert Crews Version: 2011.8.12 */ body { font-family: Tahoma, sans-serif; /* line-height: 125%; */ color: black; background-color: white; font-size: small; } * html body { /* http://www.info.com.ph/~etan/w3pantheon/style/modifiedsbmh.html */ font-size: x-small; /* for IE5.x/win */ f\ont-size: small; /* for other IE versions */ } h1 { font-size: 165%; font-weight: bold; border-bottom: 1px solid #ddd; width: 100%; text-align: left; } h2 { font-size: 152%; font-weight: bold; text-align: left; } h3 { font-size: 139%; font-weight: bold; text-align: left; } h4 { font-size: 126%; font-weight: bold; text-align: left; } h5 { font-size: 113%; font-weight: bold; display: inline; text-align: left; } h6 { font-size: 100%; font-weight: bold; font-style: italic; display: inline; text-align: left; } a:link { color: #039; background: inherit; } a:visited { color: #72007C; background: inherit; } a:hover { text-decoration: underline; } a img, img[usemap] { border-style: none; } code, pre, samp, tt { font-family: monospace; font-size: 110%; } caption { text-align: center; font-weight: bold; width: auto; } dt { font-weight: bold; } table { font-size: small; /* for ICEBrowser */ } td { vertical-align: top; } th { font-weight: bold; text-align: left; vertical-align: bottom; } li { text-align: left; } dd { text-align: left; } ol ol { list-style-type: lower-alpha; } ol ol ol { list-style-type: lower-roman; } td p:first-child, td pre:first-child { margin-top: 0px; margin-bottom: 0px; } table.table-border { border-collapse: collapse; border-top: 1px solid #ccc; border-left: 1px solid #ccc; } table.table-border th { padding: 0.5ex 0.25em; color: black; background-color: #f7f7ea; border-right: 1px solid #ccc; border-bottom: 1px solid #ccc; } table.table-border td { padding: 0.5ex 0.25em; border-right: 1px solid #ccc; border-bottom: 1px solid #ccc; } span.gui-object, span.gui-object-action { font-weight: bold; } span.gui-object-title { } p.horizontal-rule { width: 100%; border: solid #cc9; border-width: 0px 0px 1px 0px; margin-bottom: 4ex; } div.zz-skip-header { display: none; } td.zz-nav-header-cell { text-align: left; font-size: 95%; width: 99%; color: black; background: inherit; font-weight: normal; vertical-align: top; margin-top: 0ex; padding-top: 0ex; } a.zz-nav-header-link { font-size: 95%; } td.zz-nav-button-cell { white-space: nowrap; text-align: center; width: 1%; vertical-align: top; padding-left: 4px; padding-right: 4px; margin-top: 0ex; padding-top: 0ex; } a.zz-nav-button-link { font-size: 90%; } div.zz-nav-footer-menu { width: 100%; text-align: center; margin-top: 2ex; margin-bottom: 4ex; } p.zz-legal-notice, a.zz-legal-notice-link { font-size: 85%; /* display: none; */ /* Uncomment to hide legal notice */ } /*************************************/ /* Begin DARB Formats */ /*************************************/ .bold, .codeinlinebold, .syntaxinlinebold, .term, .glossterm, .seghead, .glossaryterm, .keyword, .msg, .msgexplankw, .msgactionkw, .notep1, .xreftitlebold { font-weight: bold; } .italic, .codeinlineitalic, .syntaxinlineitalic, .variable, .xreftitleitalic { font-style: italic; } .bolditalic, .codeinlineboldital, .syntaxinlineboldital, .titleinfigure, .titleinexample, .titleintable, .titleinequation, .xreftitleboldital { font-weight: bold; font-style: italic; } .itemizedlisttitle, .orderedlisttitle, .segmentedlisttitle, .variablelisttitle { font-weight: bold; } .bridgehead, .titleinrefsubsect3 { font-weight: bold; } .titleinrefsubsect { font-size: 126%; font-weight: bold; } .titleinrefsubsect2 { font-size: 113%; font-weight: bold; } .subhead1 { display: block; font-size: 139%; font-weight: bold; } .subhead2 { display: block; font-weight: bold; } .subhead3 { font-weight: bold; } .underline { text-decoration: underline; } .superscript { vertical-align: super; } .subscript { vertical-align: sub; } .listofeft { border: none; } .betadraft, .alphabetanotice, .revenuerecognitionnotice { color: #f00; background: inherit; } .betadraftsubtitle { text-align: center; font-weight: bold; color: #f00; background: inherit; } .comment { color: #080; background: inherit; font-weight: bold; } .copyrightlogo { text-align: center; font-size: 85%; } .tocsubheader { list-style-type: none; } table.icons td { padding-left: 6px; padding-right: 6px; } .l1ix dd, dd dl.l2ix, dd dl.l3ix { margin-top: 0ex; margin-bottom: 0ex; } div.infoboxnote, div.infoboxnotewarn, div.infoboxnotealso { margin-top: 4ex; margin-right: 10%; margin-left: 10%; margin-bottom: 4ex; padding: 0.25em; border-top: 1pt solid gray; border-bottom: 1pt solid gray; } p.notep1 { margin-top: 0px; margin-bottom: 0px; } .tahiti-highlight-example { background: #ff9; text-decoration: inherit; } .tahiti-highlight-search { background: #9cf; text-decoration: inherit; } .tahiti-sidebar-heading { font-size: 110%; margin-bottom: 0px; padding-bottom: 0px; } /*************************************/ /* End DARB Formats */ /*************************************/ @media all { /* * * { line-height: 120%; } */ dd { margin-bottom: 2ex; } dl:first-child { margin-top: 2ex; } } @media print { body { font-size: 11pt; padding: 0px !important; } a:link, a:visited { color: black; background: inherit; } code, pre, samp, tt { font-size: 10pt; } #nav, #search_this_book, #comment_form, #comment_announcement, #flipNav, .noprint { display: none !important; } body#left-nav-present { overflow: visible !important; } } PKr.hcPK \EOEBPS/dcommon/doccd_epub.jsM /* Copyright 2006, 2012, Oracle and/or its affiliates. All rights reserved. Author: Robert Crews Version: 2012.3.17 */ function addLoadEvent(func) { var oldOnload = window.onload; if (typeof(window.onload) != "function") window.onload = func; else window.onload = function() { oldOnload(); func(); } } function compactLists() { var lists = []; var ul = document.getElementsByTagName("ul"); for (var i = 0; i < ul.length; i++) lists.push(ul[i]); var ol = document.getElementsByTagName("ol"); for (var i = 0; i < ol.length; i++) lists.push(ol[i]); for (var i = 0; i < lists.length; i++) { var collapsible = true, c = []; var li = lists[i].getElementsByTagName("li"); for (var j = 0; j < li.length; j++) { var p = li[j].getElementsByTagName("p"); if (p.length > 1) collapsible = false; for (var k = 0; k < p.length; k++) { if ( getTextContent(p[k]).split(" ").length > 12 ) collapsible = false; c.push(p[k]); } } if (collapsible) { for (var j = 0; j < c.length; j++) { c[j].style.margin = "0"; } } } function getTextContent(e) { if (e.textContent) return e.textContent; if (e.innerText) return e.innerText; } } addLoadEvent(compactLists); function processIndex() { try { if (!/\/index.htm(?:|#.*)$/.test(window.location.href)) return false; } catch(e) {} var shortcut = []; lastPrefix = ""; var dd = document.getElementsByTagName("dd"); for (var i = 0; i < dd.length; i++) { if (dd[i].className != 'l1ix') continue; var prefix = getTextContent(dd[i]).substring(0, 2).toUpperCase(); if (!prefix.match(/^([A-Z0-9]{2})/)) continue; if (prefix == lastPrefix) continue; dd[i].id = prefix; var s = document.createElement("a"); s.href = "#" + prefix; s.appendChild(document.createTextNode(prefix)); shortcut.push(s); lastPrefix = prefix; } var h2 = document.getElementsByTagName("h2"); for (var i = 0; i < h2.length; i++) { var nav = document.createElement("div"); nav.style.position = "relative"; nav.style.top = "-1.5ex"; nav.style.left = "1.5em"; nav.style.width = "90%"; while (shortcut[0] && shortcut[0].toString().charAt(shortcut[0].toString().length - 2) == getTextContent(h2[i])) { nav.appendChild(shortcut.shift()); nav.appendChild(document.createTextNode("\u00A0 ")); } h2[i].parentNode.insertBefore(nav, h2[i].nextSibling); } function getTextContent(e) { if (e.textContent) return e.textContent; if (e.innerText) return e.innerText; } } addLoadEvent(processIndex); PKo"nR M PK \E OEBPS/toc.ncxG Oracle® Fusion Middleware Installation Guide for Oracle Team Productivity Center Server, 11g Release 1 (11.1.1.6.0) Cover Contents Installation Guide for Oracle Team Productivity Center Server Copyright PK:PK \EOEBPS/content.opf Oracle® Fusion Middleware Installation Guide for Oracle Team Productivity Center Server, 11g Release 1 (11.1.1.6.0) en-US E14156-08 Oracle Corporation Oracle Corporation Oracle® Fusion Middleware Installation Guide for Oracle Team Productivity Center Server, 11g Release 1 (11.1.1.6.0) 2011-10-31T06:58:42Z Describes how to install the server and connectors for Oracle Team Productivity Center. Includes a list of prerequisites for the installation, and how to choose the source for the connector installation. PK~PK \EOEBPS/cover.htm  Cover

Oracle Corporation

PK@t` PK \E OEBPS/toc.htm @ Table of Contents PK H PK  \Eoa,mimetypePK \Ĕ:iTunesMetadata.plistPK \EYuMETA-INF/container.xmlPK \EJgO-OEBPS/tpcig.htmPK \El-OJOEBPS/dcommon/oracle.gifPK \EggOEBPS/dcommon/oracle-logo.jpgPK \E0hOEBPS/dcommon/cpyr.htmPK \Er.hc.OEBPS/dcommon/blafdoc.cssPK \Eo"nR M rFOEBPS/dcommon/doccd_epub.jsPK \E: QOEBPS/toc.ncxPK \E~VOEBPS/content.opfPK \E@t` /_OEBPS/cover.htmPK \E H |aOEBPS/toc.htmPK P{o