Install MSSQL

Oracle® Primavera®

Contract Management 14.0, Business Intelligence Publisher Edition Installation and Configuration Guide for Microsoft® SQL Server

Copyright © 1996, 2012, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trade-marks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

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.

The platform-specific hardware and software requirements included in this document were current when this document was published. However, because new platforms and operating system software versions might be certified after this document is published, review the certification matrix on the My Oracle Support Web site for the most up-to-date list of certified hardware platforms and operating system versions. The My Oracle Support Web site is available at the following URL:

http://support.oracle.com/

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 documen-tation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

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

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.

To view the list of third party technology disclosures related to this product, please see the Commercial Notices and Disclosures document for the release.

3

Table of Contents

Preface...................................................................................................7Contract Management Overview .......................................................................... 8Contract Management (v14.0) Media Pack ........................................................ 10Contract Management Documentation ............................................................... 11About this Manual............................................................................................... 13Contacting Customer Support............................................................................. 15

Preparing for Installation..................................................................17Overview............................................................................................................. 18Defining the JAVA_HOME Environment Variable............................................. 19Creating New Databases ..................................................................................... 21Migrating Databases ........................................................................................... 23Upgrading Your Databases ................................................................................. 24Configuring a WebLogic Application Server ..................................................... 26Using United Kingdom Terminology ................................................................. 30

Installing Contract Management on an Application Server ..........31Prerequisites ........................................................................................................ 32Installing Contract Management...................................................................... 33

Upgrading to Primavera Contract Management 14.0, Business Intelligence Publisher Edition ...............................................................................37

Overview............................................................................................................. 38Prerequisites ........................................................................................................ 39Upgrade to WebLogic 11g from a JBoss-Based System .................................... 40Upgrade to WebLogic 11g from a WebLogic 10g-Based System ...................... 43Upgrade to Primavera Contract Management 14.0, Business Intelligence Publisher Edition from a WebLogic 11g-Based System.................................................................. 46

Configuring WebLogic for Microsoft SQL Server Databases .......49Prerequisites ........................................................................................................ 50Configuring the Data Source............................................................................... 51Deploying Contract Management ....................................................................... 54Configuring the Contract Management Port Specification................................. 55

4 Table of Contents

Configuring Contract Management for a WebLogic Cluster ........57Prerequisites ........................................................................................................ 58Configuring the Clustered Environment ............................................................. 59Considerations for Using Contract Management in a Clustered Environment... 61Using the XML API in a Clustered Environment ............................................... 62Enabling Node Manager for Contract Management in a Clustered Environment63

Viewing and Modifying Contract Management Settings ...............65Starting the Administration Config Utility ......................................................... 66Modifying Values of Configuration Settings ...................................................... 68Modifying Authentication Settings ..................................................................... 69Modifying Web Single Sign-On Settings............................................................ 71Modifying Autovue Integration Settings ............................................................ 72Modifying BI Publisher Settings......................................................................... 73Modifying Configuration Management Settings ................................................ 74Modifying Content Repository Settings ............................................................. 75Modifying Database Settings .............................................................................. 78Modifying P6 EPPM Schedule Database Settings.............................................. 83Setting Preferences.............................................................................................. 85Modifying User Productivity Kit Settings .......................................................... 86Modifying Web Server Settings .......................................................................... 87Configuration Settings for Contract Management .............................................. 88

Connecting Contract Management with P6 EPPM......................101Prerequisites ...................................................................................................... 102Configuring Schedule Database Information for Microsoft SQL Server ......... 103Configuring Your Simple Mail Transfer Protocol Server ................................. 104Configuring the Port Number for Microsoft SQL Server ................................. 105Locating the Database Port Number when Using Microsoft SQL Server ........ 106

Setting Up the Contract Management Environment....................107Starting the Administration Application ........................................................... 108Adding Contract Management Users ................................................................ 109Viewing Reports and Forms in Contract Management Using BI Publisher ..... 110Importing Users from LDAP............................................................................. 116Configuring Oracle Access Manager for Contract Management...................... 119

Installing and Configuring the Oracle Primavera SharePoint Connector121Prerequisites ...................................................................................................... 122Installing the Oracle Primavera SharePoint Connector..................................... 123Configure the Oracle Primavera SharePoint Connector URL in Administration Config Utility125

Connecting Oracle Universal Content Management to Contract Management127

Configuring UCM to Work with Contract Management .................................. 128

Contract Management Installation and Configuration Guide for Microsoft SQL Server

Table of Contents 5

Index..................................................................................................131


6 Table of Contents


7

Contract Management is contract-control

software designed to help you manage your

projects more easily. From submittals to

change orders, all the facts about contracts

and documents related to your project are at

your fingertips.

This manual describes how to install and

configure Contract Management.

In this chapter

Contract Management Overview

Contract Management (v14.0) Media Pack

Contract Management Documentation

About this Manual

Contacting Customer Support

Preface

8 Preface

Contract Management OverviewContract Management is a browser-based product that enables project users to interactively review, update, and comment on documents on which they need to take action. With the help of a Web browser, Contract Management grants real-time access to a Contract Management project database across an intranet or the Internet.

Contract Management Database Server The database server stores your project data. Web clients access project data through the Contract Management Web Server. You can run Contract Management with a Microsoft SQL or Oracle database.

Microsoft SQL Server is not provided as part of the Contract Management installation. To use Contract Management with a Microsoft SQL database, install Microsoft SQL before installing Contract Management.

Requirements of the Contract Management Web and Application Servers

■ Firewall configured to allow only HTTP requests to the port and TCP/IP address of the Web Server.

■ Microsoft SQL Server, installed prior to the Contract Management installation.

■ An Oracle Business Intelligence Publisher environment to support report and form functionality and to create and modify letter templates. See the documentation included with BI Publisher.

The Contract Management Web Server validates Contract Management Web users, enforces Contract Management's business rules, and communicates with the Contract Management database server.

Supported Operating Systems for Primavera Contract Management 14.0, Business Intelligence Publisher Edition

The supported operating system information is listed in the Tested Configurations document that is available on the physical media or from the download location.


Preface 9

Upgrade Information

This manual covers upgrades to Primavera Contract Management 14.0, Business Intelligence Publisher Edition from product versions 11.0 and later. For assistance in upgrading from versions previous to 11.0, contact Customer Support.

Upgrade existing Microsoft SQL databases before installing Contract Management.


10 Preface

Contract Management (v14.0) Media PackThis media pack includes the Contract Management Application zip file. This zip file includes:

■ All files necessary to install Primavera Contract Management.

■ All manuals and technical documents related to the installation, administration, and use of Primavera Contract Management.

The Primavera Contract Management Media Pack is delivered on the Oracle Software Delivery Cloud.


Preface 11

Contract Management DocumentationContract Management documentation consists of the following:

Contract Management Installation and Configuration Guide for Oracle Explains how to install and configure Contract Management for Oracle and to convert data from previous versions of Contract Management. The network or database administrator responsible for the initial installation of Contract Management, ongoing maintenance of the system and database, and general troubleshooting should read this manual.

Contract Management Installation and Configuration Guide for Microsoft SQL Server Explains how to install and configure Contract Management for Microsoft SQL Server and to convert data from previous versions of Contract Management. The network or database administrator responsible for the initial installation of Contract Management, ongoing maintenance of the system and database, and general troubleshooting should read this manual.

Contract Management Online Help This is an integrated comprehensive online help system that supplements the printed documentation. The help system is available while using the software for quick access to information about fields, commands, and dialog boxes. Help also includes step-by-step procedures for performing tasks, and supplies answers to common questions. The Table of Contents provides a starting point for many major topics. You can also use Help’s powerful Search and Index features to find topics related to any text you enter. Click How To for a list of all procedures contained in Help.

Contract Management User’s Guide Explains how to manage and monitor paperwork from initial contracts through the last change order. All individuals who use Contract Management should read this guide, even if they are already familiar with previous versions of Contract Management.

Contract Management Web Services Administrator’s Guide Provides information on the services and operations supported by Contract Management Web Services.

Contract Management Web Services Programmer’s Guide Provides information on how to use Contract Management Web Services.


12 Preface

Other Documentation The Contract Management physical media or download location contains additional information in the folder \documentation.

■ Tested Configurations Lists the configurations that have been tested and verified to work with Primavera Contract Management 14.0, Business Intelligence Publisher Edition. The network administrator/database administrator and Contract Management administrator should read this document.

Several areas of Contract Management can be customized, such as the Control Center, document names, and document field labels. The examples throughout this manual and in Help use the default settings shipped with Contract Management.


Preface 13

About this ManualThis manual guides you through the installation of Primavera Contract Management 14.0, Business Intelligence Publisher Edition, whether you are installing Contract Management for the first time or upgrading from a previous version of Contract Management. Anyone who is responsible for installing Contract Management should read this manual. Whether you are a network administrator or user, this manual contains the information you need to set up Contract Management in your environment.

Chapter Contents

Preparing for Installation Describes tasks required to be completed prior to your Contract Management installation.

Explains how to migrate or upgrade your existing databases before upgrading your software, or to create new databases and install the J2SE before installing Contract Management for the first time, and how to configure your Web server before upgrading your existing Contract Management installation.

Installing Contract Management on an Application Server

Describes tasks required to install Primavera Contract Management 14.0, Business Intelligence Publisher Edition for the first time.

Upgrading to Primavera Contract Management 14.0, Business Intelligence Publisher Edition

Describes tasks required to upgrade your existing installation to Primavera Contract Management 14.0, Business Intelligence Publisher Edition.

Configuring WebLogic for Microsoft SQL Server Databases

Explains how to install and configure the WebLogic application server for the Microsoft SQL Server database used with Contract Management.

Configuring Contract Management for a WebLogic Cluster

Describes tasks required to configure Contract Management for a WebLogic Cluster environment.

Viewing and Modifying Contract Management Settings

Explains how to run the Administration Config utility to modify your current Contract Management database and configuration settings.

Connecting Contract Management with P6 EPPM

Explains how to set up Contract Management to communicate with P6 Enterprise Project Portfolio Management.


14 Preface

Setting Up the Contract Management Environment

Explains how to add users; set up attachments, reports, and forms; add new databases; and reconfigure Contract Management.

Installing and Configuring the Oracle Primavera SharePoint Connector

Explains how to install and configure the Oracle Primavera SharePoint Connector to enable Microsoft SharePoint to integrate with Contract Management.

Connecting Oracle Universal Content Management to Contract Management

Explains how to configure the Oracle content repository for use with Contract Management.

Chapter Contents


Preface 15

Contacting Customer Support

Contract Management databases contain calculations called stored procedures. Although a Contract Management database administrator has the ability to modify these procedures, Oracle Primavera does not recommend changing them. Modifying these procedures voids your Oracle Primavera Customer Support agreement.

For instructions on how to contact Customer Support, please visit My Oracle Support at:

http://support.oracle.com

This page provides the latest information for contacting support and the support renewals process.

Contract Management integrates with different Oracle applications; when you create a Service Request, be sure to open the request with the proper Support team. To ensure you reach the proper Support team, enter the correct product information when you create the Service Request. Each product has its own support line.

■ Use the Primavera Contract Management support line when you are having installation, configuration, connection, or application issues related to Contract Management.

■ Use one of the following support lines when you are having installation or configuration issues that do not relate to Contract Management.

• Oracle WebLogic Server

• Oracle Server

• Oracle Business Intelligence Publisher

• Repository Creation Utility

• Oracle Universal Content Management

• Oracle Access Manager

• Primavera P6 Enterprise Project Portfolio Management

• Oracle AutoVue


16 Preface

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/us/support/contact-068555.html or visit http://www.oracle.com/us/corporate/accessibility/support/index.html if you are hearing impaired.

Another great support tool is the My Oracle Support Communities at http://communities.oracle.com.


17

This chapter describes how to complete

required tasks before installing the current

version of Contract Management.

In this chapter

Overview

Defining the JAVA_HOME Environment Variable

Creating New Databases

Migrating Databases

Upgrading Your Databases

Configuring a WebLogic Application Server

Using United Kingdom Terminology

Preparing for Installation

18 Preparing for Installation

OverviewBefore starting the Contract Management installation, complete the appropriate tasks in this chapter. For the full list of tested configurations, see the Tested Configurations document in the Documentation folder of the Contract Management physical media or download.

To install or upgrade Contract Management, perform the following prerequisites:

1 Create or upgrade your Contract Management databases. See “Creating New Databases” on page 21 or “Upgrading Your Databases” on page 24.

Before running the dbsetup file when creating or updating a database, you must define a valid JAVA_HOME environment variable. If the variable is not yet defined, see “Defining the JAVA_HOME Environment Variable” on page 19.

2 Configure your Application Server. This is required for all new Contract Management installations, and for all upgrade installations. See “Configuring a WebLogic Application Server” on page 26.

When you are finished with these installation prerequisites, you can install or upgrade Contract Management. For information, see “Installing Contract Management” on page 33 or “Upgrading to Primavera Contract Management 14.0, Business Intelligence Publisher Edition” on page 37.

For information about upgrading from Expedition Professional 10.0 or a previous version, contact Customer Support.

If you want to use United Kingdom contracting terminology with Contract Management, see “Using United Kingdom Terminology” on page 30.


Preparing for Installation 19

Defining the JAVA_HOME Environment VariableYou must define a valid JAVA_HOME environment variable before running dbsetup.bat (dbsetup.sh in a non-Windows system). To define the variable, follow the instructions below for either a Windows or Linux system.

Install and Define a JAVA_HOME Environment Variable for Windows

1 Install the Sun Java Runtime Environment 6 Update 24 from http://www.oracle.com/technetwork/java/archive-139210.html.

2 Once the JRE is installed, right-click My Computer on your desktop and select Properties. This will launch the Windows System Properties dialog box.

3 In the System Properties dialog box, click the Advanced tab and then click Environment Variables.

4 In the System variables section of the Environment Variables dialog box, determine whether a JAVA_HOME variable with a valid JRE path exists.

• If a valid variable exists, you do not need to define the variable and you are finished with this task. Close out of System Properties.

• If a valid variable does not exist, click New in the System variables section and continue to step 5.

5 In the New System Variable dialog box, enter the following information:

• Variable name: JAVA_HOME

• Variable value: <path to JRE installation>

For example: c:\program files\java\jre6

6 Click OK in the New System Variable, Environment Variables, and System Properties dialog boxes.

Install and Define a JAVA_HOME Environment Variable for Linux

1 Install the Sun Java Runtime Environment 6 Update 24 from http://www.oracle.com/technetwork/java/archive-139210.html.



2 Once the JRE is installed, open a terminal window and change to the directory containing dbsetup.sh.

3 In the terminal window, run the following command:

export JAVA_HOME=<path to JRE>

For example: export JAVA_HOME=/usr/java/jre6

You can now run the Primavera Database Setup wizard. Please note that execute permissions for dbsetup.sh are required to run this wizard.



Creating New DatabasesIf you are installing Contract Management for the first time, use the Database Setup Wizard to create a new Microsoft SQL database prior to the installation.

Creating databases through the Database Wizard generates a log file that may be stored locally or on a network drive depending on how you run the Database Wizard.Running the Database Wizard from the Content Management physical media causes this log file to be written to the local Temp directory on your computer. To run the Database Wizard from a network drive, you must have write access to the network drive in order for the log file to be written to the network drive. Otherwise, the file is written to the local Temp directory on your computer.

If you want United Kingdom sample data, copy the two .jar files in <database_setup_folder>\UkSampleData and paste them into <database_setup_folder>\lib before running dbsetup.

Create a New Database

You must define a JAVA_HOME environment variable before running the Primavera Database Setup wizard. If the variable does not exist, see Configuring a WebLogic Application Server for instructions before continuing.

1 From the location where you unzipped the Contract Management folder from the Oracle Software Delivery Cloud, open the database folder and click dbsetup.bat (dbsetup.sh in a non-Windows system) to run the Primavera Database Setup wizard.

2 On the Contract Management page, select the Install and Microsoft SQL Server options to create a new database for Microsoft SQL Server. Click Next.

3 On the Select application database page, select the type of Microsoft SQL database to create: Group Database or Administration Database, and click Next.



If you have not already done so, you must create an Administration Database to store user accounts and account permissions.

4 On the Connection Information page, enter the following information and click Next:

a) Enter the DBA user name. This is the system user account name. The default is sa.

b) Enter the DBA password. This is the system user account password.

c) Enter the Database host address. This is the name or IP address of the database host machine where Microsoft SQL Server runs.

d) Enter the Database host port. The default is 1433.

5 On the Configure Microsoft SQL Server page, enter the following information and click Next:

a) Enter the Database name. This is the name for the database you are creating.

b) Enter the Data file path. This is the path where the database server stores data.

c) Enter the Log file path. This is the path where the database server stores log files.

d) Select Database Default from the Database code page list. This is the language used for the database.

6 On the Configurations Options page:

a) Select the Load sample data option to include sample data when the database is created, or leave it blank to create the database without sample data.

b) Select the Use unicode option if the database will be in a multi-byte language (Chinese for example).

c) Click the Install button.

7 On the Finish page, click Finish if you are done upgrading or installing databases or click Next to continue with another installation or upgrade.



Migrating DatabasesContract Management 12.1 and previous versions supported Sybase Adaptive Server Anywhere (ASA). As of 13.0, Contract Management no longer supports Sybase.

Customers must migrate their Sybase databases to a supported platform before upgrading to Contract Management 14.0, Business Intelligence Publisher Edition or later. For information on migrating Sybase databases, contact Customer Support.

You must define a JAVA_HOME environment variable before running the Primavera Database Setup wizard. If the variable does not exist, see Configuring a WebLogic Application Server for instructions.

When migrating the databases, first migrate the Admin database, and then migrate each Group database. The same procedure is used to enter source database information for both the Admin and Group databases.

To migrate Admin and Group databases from Oracle to Microsoft SQL, or from Microsoft SQL to Oracle, use the migrate.bat utility in the \database folder to convert platforms.

For information on contacting Oracle Primavera Customer Support, see “Contacting Customer Support” on page 15.



Upgrading Your DatabasesIf you are upgrading to Primavera Contract Management 14.0, Business Intelligence Publisher Edition and you previously had version 11.0 or later, use the Database Setup Wizard to upgrade your GROUP and ADMIN databases to ensure that they will work properly following installation. If you are upgrading from version 10 or earlier, contact Customer Support for instructions.

This procedure also applies when installing a Service Pack.

Before upgrading the database in your production environment:- Back up your databases, reports, and forms. - Oracle Primavera recommends that you first complete the upgrade in a test environment.

If you want United Kingdom sample data, copy the two .jar files in <database_setup_folder>\UkSampleData and paste them into <database_setup_folder>\lib before running dbsetup.

Upgrade an Existing Contract Management Database

You must define a JAVA_HOME environment variable before running the Primavera Database Setup wizard. If the variable does not exist, see Configuring a WebLogic Application Server for instructions before continuing.

1 From the location where you unzipped the Contract Management folder from the Oracle Software Delivery Cloud, open the database folder and click dbsetup.bat (dbsetup.sh in a non-Windows system) to run the Primavera Database Setup wizard.

2 On the Contract Management page, select the Upgrade Database option and the Microsoft SQL Server option. Click Next.

3 On the Connection Information page, enter the following information and click Next:

a) Enter the Administrative user name. This is the system administrator account name. The default administrator account is sa.



b) Enter the Administrative password. This is the password of the database administrator account.

c) Enter the Database host address. This is the name or IP address of the database host machine where Microsoft SQL Server runs.

d) Enter the Database host port. The default is 1433 for Microsoft SQL Server.

e) Enter the Database name. This is the name of the Microsoft SQL Server database to be upgraded.

4 On the Finish page, click Finish if you are done upgrading or installing databases or click Next to continue with another installation or upgrade.



Configuring a WebLogic Application ServerFollow the instructions in this section to configure WebLogic 11g for Contract Management. For the full list of tested configurations, see the Tested Configurations document in the Documentation folder of the Contract Management physical media or download.

Prerequisites Complete the following steps:

1 Install WebLogic 11g.

2 If using a Sun Java Development kit, install the Java Development Kit 6 Update 24 from http://www.oracle.com/technetwork/java/archive-139210.html.

Create a new domain specific to Contract Management Do the following to create a new domain specific to Contract Management. This domain will use the selected JDK, and will contain the Contract Management configuration files.

Do not create the domain in a directory that is in an existing Contract Management directory path.

1 Go to Start, All Programs, Oracle WebLogic, WebLogic Server, Tools, and click Configuration Wizard to run the WebLogic Configuration Wizard.

2 In the Welcome window, select Create a new WebLogic domain and click Next.

3 In the Select Domain Source window, click Next to accept the default selections.

4 On the Specify Domain Name and Location page, enter the Domain Name and Location and click Next.

5 In the Configure Administrator User Name and Password window, enter the user name and password information and click Next.

6 In the Configure Server Start Mode and JDK window, select Production Mode in the left pane. Select an appropriate JDK in the right pane and click Next.

7 On the Select Optional Configuration page, click Next.

8 On the Configuration Summary page, verify that the configuration is correct and click Create.



9 In the Creating Domain window, clear the Start Admin Server option and click Done.

Configure the WebLogic Domain Do the following to configure the WebLogic domain.

1 Make a backup copy of the startWebLogic file in case you need to undo any changes.

• In Windows, the file is named startWebLogic.cmd and is located in: weblogic_home\user_projects\domains\your_domain\bin\

• In Unix, the file is named startWebLogic.sh and is located in: weblogic_home/user_projects/domains/your_domain/bin/

2 Right-click the start WebLogic file and select Edit.

3 Locate the line that looks like the following:

• In Windows: set SAVE_CLASSPATH=%CLASSPATH%

• In Unix: SAVE_CLASSPATH="${CLASSPATH}"

4 Replace the above line with one of the following:

• In Windows: set SAVE_CLASSPATH=%DOMAIN_HOME%\lib\ojdbc6.jar;%DOMAIN_HOME%\lib\sqljdbc.jar;%CLASSPATH%;.

• In Unix: SAVE_CLASSPATH="${DOMAIN_HOME}/lib/ojdbc6.jar:${DOMAIN_HOME}/lib/sqljdbc.jar:${DOMAIN_HOME}:."

5 Save the changes to the startWebLogic file and close it.

6 Make a backup copy of the setDomainEnv file.

• In Windows, the file is named setDomainEnv.cmd and is located in: weblogic_home\user_projects\domains\your_domain\bin\

• In Unix, the file is named setDomainEnv.sh and is located in: weblogic_home/user_projects/domains/your_domain/bin/

7 Right-click the setDomainEnv file and select Edit.

8 Locate the line that begins with one of the following:

• In Windows: call "%WL_HOME%\common\bin\commEnv.cmd"

• In Unix: $WL_HOME/common/bin/commEnv.sh

9 Add new memory settings to maximize performance:

■ If using the Sun JDK:



Add new memory settings to maximize performance and increase the JVM MaxPermSize setting to avoid Out-of-Memory errors. (The MaxPermSize setting should be set to at least 256m.) To do this, add a USER_MEM_ARGS line so you can set the following values for NewSize, MaxNewSize, MaxPermSize, SurvivorRatio, total Initial size (-Xms), and Maximum heap size (-Xmx):

-XX:NewSize=256m -XX:MaxNewSize=256m -XX:MaxPermSize=256m -XX:SurvivorRatio=8 -Xms1024m -Xmx1024m

Add the line immediately below the line you located (all one line):

• In Windows, the line should look similar to the following:

set USER_MEM_ARGS=-XX:NewSize=256m -XX:MaxNewSize=256m -XX:MaxPermSize=256m -XX:SurvivorRatio=8 -Xms1024m -Xmx1024m

• In Unix, the line should look similar to the following:

USER_MEM_ARGS="-XX:NewSize=256m -XX:MaxNewSize=256m -XX:MaxPermSize=256m -XX:SurvivorRatio=8 -Xms1024m -Xmx1024m"

■ If using the JRockit JDK:

Add new memory settings to maximize performance. To do this, add a USER_MEM_ARGS line so you can set the following values for the total Initial (-Xms) and Maximum heap (-Xmx) size:

-Xms2048m -Xmx2048m

Add the line immediately below the line you located (all one line):

• For Windows:

set USER_MEM_ARGS=-Xms1024m -Xmx1024m

• For Unix:

USER_MEM_ARGS="-Xms1024m -Xmx1024m"



10 Save the changes to the setDomainEnv file and close it. (A WebLogic Server restart is required for changes to take effect.)



Using United Kingdom TerminologyIf you want to use United Kingdom contracting terminology with Contract Management follow the instructions below before installing Contract Management.

After you have downloaded Oracle Primavera Contract Management 14.0, Business Intelligence Publisher Edition and unzipped it:

1 Unzip the Primavera Contract Management Database Setup Version 14.0 file.

2 Copy the Contract_Management_14_Database\UKSampleData\DBS_EXP_14_00_00.jar file and the Contract_Management_14_Database\UKSampleData\DBS_EXPADM_14_00_00.jar file to <Folder into which you unzipped the file>\Contract_Managment_14_Database\lib folder.

The Contract_Management_14_Database\lib folder was created when you unzipped the Primavera Contract Management Database Setup Version 14.0 file.zip file.

3 When you are finished you can install the product if you have completed all other installation prerequisites.


31

This chapter describes how to install

Primavera Contract Management 14.0,

Business Intelligence Publisher Edition.

The instructions in this chapter only apply to

installations where there is no previous

version of Contract Management installed.

For information about installing Contract

Management when upgrading from a

previous version, see “Upgrading to

Primavera Contract Management 14.0,

Business Intelligence Publisher Edition” on

page 37.

In this chapter

Prerequisites

Installing Contract Management

Installing Contract Management on an Application Server

32 Installing Contract Management on an Application Server

PrerequisitesPrior to completing the procedures presented in this chapter, complete all procedures in the “Preparing for Installation” on page 17. After completing all pre-installation tasks, you are ready to install your Contract Management software.


Installing Contract Management on an Application Server 33

Installing Contract ManagementBefore you begin Before beginning this installation, you must install and configure:

• WebLogic application server—see “Configuring a WebLogic Application Server” on page 26

• Microsoft SQL Server database—see “Creating New Databases” on page 21

Install Contract Management

1 From the Contract Management physical media or download location, run setup.exe (runInstaller.sh for Linux operating systems). The Oracle Universal Installer dialog box will open.

2 On the Welcome page, click Next.

3 On the Specify Home Details page, enter a name and a path for the installation and click Next. To accept the default name and path, click Next.

You can install over an existing Contract Management directory from a previous installation or install in a new directory. If the directory you specify does not exist, the installer will create it during the installation process.

4 On the Available Product Components page, select the Oracle Configuration Management option if you want to install support for this tool. The Primavera Contract Management14.0 option is automatically selected. Click Next.

If you install support for the Oracle Configuration Management (OCM) tool, the files necessary to support this tool’s collection tasks are copied to the Contract Management home directory. A remote machine running OCM can then capture configuration information for the machine running Contract Management.

5 On the Information page, click Next if you have installed and configured all of the listed items. If you have not yet installed and configured all of the items, click Cancel to end the installation for Contract Management and install the necessary components before resuming.

6 On the Java Home Location page, enter or browse to the installation location for Java and click Next.



7 On the Weblogic Domain Location page, enter or browse to the WebLogic domain location and click Next.

8 On the Database Type page, select the SQL Server option and click Next.

9 On the Primavera Contract Management Database Server page, click Next after you enter the following database server infor-mation:

• Database Host Name – The name of the host on which the database resides. This can be either the fully qualified host name or the IP address.

Do not use localhost (IP 127.0.0.1) here as it will prevent you from being able to view reports from Oracle Business Intelligence Publisher.

• Database Port – The port number on the host where the database resides. This field is pre-filled with the default port number, 1433.

• User Name – The user name used to access the database. The default is exp.

• Password – The password used to access the database. The default is sql.

10 On the Primavera Contract Management Admin Database page, enter the name of the admin database and click Next. The default name is expadmin.

11 On the Primavera Contract Management Group Database page, decide whether you want to configure a new group database or bypass the configuration and click Next. If you select the Bypass configuration of a new group database option, skip to step 13.

Select the Configure a new group database option if this is a new installation of Contract Management. A new group database must be configured for new installations. If this is not a new installation and you select to configure a new group database, previous group database configurations are overwritten.

12 On the Primavera Contract Management Group Database Infor-mation page, enter the Group Database Name and click Next. The default name is CMDEMO.

13 On the Summary page, check the summary. Click Install if the summary is accurate.


Installing Contract Management on an Application Server 35

14 When the message saying that the installation is complete displays, click Finish.

15 On the End of Installation page, click Exit.




37

This chapter describes how to upgrade to

Contract Management 14.0, Business

Intelligence Publisher Edition.

In this chapter

Overview

Prerequisites

Upgrade to WebLogic 11g from a JBoss-Based System

Upgrade to WebLogic 11g from a WebLogic 10g-Based System

Upgrade to Primavera Contract Management 14.0, Business Intelligence Publisher Edition from a WebLogic 11g-Based System

Upgrading to Primavera Contract Management 14.0, Business Intelligence Publisher Edition

38 Upgrading to Primavera Contract Management 14.0, Business Intelligence Publisher Edition

OverviewFor Primavera Contract Management 14.0, Business Intelligence Publisher Edition, the only supported application server is WebLogic 11g. When upgrading to version 14.0 from a previous version (11.0 or later), there are three possible upgrade scenarios:

■ The application server is JBoss.

■ The application server is WebLogic 10g.

■ The application server is WebLogic 11g.


Upgrading to Primavera Contract Management 14.0, Business Intelligence Publisher Edition 39

PrerequisitesPrior to completing the procedures presented in this chapter, complete all procedures in “Preparing for Installation” on page 17.

For information about upgrading to Primavera Contract Management 14.0, Business Intelligence Publisher Edition from Expedition Professional 10.0 or previous versions, see “Contacting Customer Support” on page 15.



Upgrade to WebLogic 11g from a JBoss-Based SystemBackup Certain Files and Folders There are certain files to backup before installing WebLogic 11g and Contract Management. You will restore these files after you install Contract Management.

The path names in this section should all be on one line. Format restrictions of this document may prevent them from doing so.

1 Back up the following files if you are using customized languages:

• <JBoss_Domain_Home>\lib\resource_strings.jar

• <JBoss_Domain_Home>\lib\ext\com\primavera\exponline\common\explang.xml

2 Backup the following file for reference if you modified it. Any customizations to this file may be applied to the new version of the exponline.properties file:

<JBoss_Domain_Home>\lib\ext\com\primavera\exponline\common\exponline.properties

3 Backup the Report images in case you need to re-add them in BI Publisher. To find the path to the images location:

a. Run the Administration Config utility.

b. Click Contract Management Settings.

c. Expand Preferences, and look for ReportImagesLocation. Back up all the image files in that location.

4 Back up the following folder:

<Contract_Management_Install_Home>\htmltemplates

Uninstall Contract Management After backing up the files and folders, uninstall your existing Contract Management application.

1 Click Start, and select Control Panel.

2 Select Add or Remove Programs.

3 Select Contract Management, and click Remove.



See “Configuring WebLogic for Microsoft SQL Server Databases” on page 49 for information on configuring WebLogic for Contract Management.

Install WebLogic 11g, and Create a Contract Management-Domain After uninstalling Contract Management, install WebLogic 11g. For information on installing WebLogic 11g, see the documentation that came with the product. Also see “Configuring WebLogic for Microsoft SQL Server Databases” on page 49.

Once WebLogic 11g is installed, create a Contract Management domain in WebLogic.

Rename the <Contract Management_Install_Home> Folder After Contract Management uninstall completes, rename the <Contract Management_Install_Home> folder. For example:

Rename the following:

C:\Program Files\Oracle\Contract Management

To be:

C:\Program Files\Oracle\Contract Management13_old

For information on installing Contract Management, see “Installing Contract Management on an Application Server” on page 31.

Install Contract Management Install Contract Management. When the Specify Home Details screen displays, enter the original path to the <Contract Management_Install_Home> folder. For example:


Overwrite Certain Files with the Backup Files After installing and configuring Contract Management, you can overwrite certain files with the backed up copies. This is the case if you modified the files.

1 If you modified the following resource_strings.jar file from this location (which you previously backed up):

<JBoss_Domain_Home>\lib\resource_strings.jar

Overwrite the resource_strings.jar file in the following location with a copy of the backed up version of the resource_strings.jar file:

<WebLogic_Domain_Home>\lib\resource_strings.jar

The resource_strings.jar file contains all the languages available for your installation of Contract Management. If you added additional languages, continue to use your existing resource_strings.jar file. However, it must be updated by your translation provider to be fully compatible with Contract Management.



2 If you modified the following explang.xml file from this location (which you previously backed up):

<JBoss_Domain_Home>\lib\ext\com\primavera\exponline\common\explang.xml

Overwrite the explang.xml file in the following location with a copy of the backed up version of the explang.xml file:

<WebLogic_Domain_Home>\com\primavera\exponline\common\explang.xml

3 If you modified the following exponline.properties file from this location (which you previously backed up):

<WebLogic_Domain_Home>\lib\ext\com\primavera\exponline\common\exponline.properties

Apply any customizations from the backed up copy to the new version of the exponline.properties file in the following location:

<WebLogic_Domain_Home>\com\primavera\exponline\common\exponline.properties

Do not overwrite the whole file. Merely apply the customizations you made to the backed up copy to the new file.

4 If you modified any templates in the following original folder from this location (which you previously backed up):


Overwrite the contents of the following folder (created during installation of Contract Management) with the contents of the backed up folder:


Deploy Contract Management Once you finish restoring files, deploy Contract Management, see “Deploying Contract Management” on page 54. When Contract Management is up and running properly, you can remove the old Contract Management folder (for example, C:\Program Files\Oracle\Contract Management13_old).



Upgrade to WebLogic 11g from a WebLogic 10g-Based System

Backup Certain Files and Folders There are certain files to backup before installing WebLogic 11g and Contract Management. You will restore these files after you install Contract Management.



• <WebLogic_Domain_Home>\lib\resource_strings.jar

• <WebLogic_Domain_Home>\lib\ext\com\primavera\exponline\common\explang.xml

2 Backup the following file for reference if you modified it. Any customizations to this file must be applied to the new version of the exponline.properties file:














See “Configuring WebLogic for Microsoft SQL Server Databases” on page 49 for information on configuring WebLogic for Contract Management.

Install WebLogic 11g, and Create a Contract Management-Domain After uninstalling Contract Management, install WebLogic 11g. For information on installing WebLogic 11g, see the documentation that came with the product. Also see “Configuring WebLogic for Microsoft SQL Server Databases” on page 49.

Once WebLogic 11g is installed, create a Contract Management domain in WebLogic.

Rename the <Contract Management_Install_Home> Folder After WebLogic uninstall completes, rename the <Contract Management_Install_Home> folder. For example:



To be:






1 If you modified the resource_strings.jar file, overwrite it in the following location with a copy of the backed up version of the resource_strings.jar file:



2 If you modified the explang.xml file, overwrite it in the following location with a copy of the backed up version of the explang.xml file:
















Upgrade to Primavera Contract Management 14.0, Business Intelligence Publisher Edition from a WebLogic 11g-Based System

This section describes the tasks to perform before installing Contract Management when you already have WebLogic 11g installed.

Backup Certain Files and Folders There are certain files to backup before installing Contract Management. You will restore these files after you install Contract Management.



• <WebLogic_Domain_Home>\lib\resource_strings.jar

• <WebLogic_Domain_Home>\lib\ext\com\primavera\exponline\common\explang.xml

2 Backup the following file for reference if you modified it. Any customizations to this file must be applied to the new version of the exponline.properties file:














See “Configuring WebLogic for Microsoft SQL Server Databases” on page 49 for information on configuring a domain for Contract Management.

Create a Contract Management Domain After uninstalling Contract Management, create a Contract Management domain in WebLogic.

Rename the <Contract Management_Install_Home> Folder After WebLogic uninstall completes, rename the <Contract Management_Install_Home> folder. For example:



To be:






1 If you modified the resource_strings.jar file, overwrite it in the following location with a copy of the backed up version of the resource_strings.jar file:



2 If you modified the explang.xml file, overwrite it in the following location with a copy of the backed up version of the explang.xml file:















49

Use this chapter to configure WebLogic

when using Contract Management with

Microsoft SQL Server databases.

In this chapter

Prerequisites

Configuring the Data Source

Deploying Contract Management

Configuring the Contract Management Port Specification

Configuring WebLogic for Microsoft SQL Server Databases

50 Configuring WebLogic for Microsoft SQL Server Databases

PrerequisitesDo the following before configuring WebLogic.

1 Make sure that you have met all the prerequisites for using WebLogic with Contract Management. For information, see “Configuring a WebLogic Application Server” on page 26.

2 In the Administration Config utility, set the properties for the content repository (Oracle or Microsoft SharePoint). For more information, see “Viewing and Modifying Contract Management Settings” on page 65.

3 Start WebLogic from <domain_home>\startWebLogic.

4 Login to admin console at url (for example: http://localhost:7001/console).

5 Click Lock & Edit.

6 Select Data Sources from Services.

7 Click New\Generic Data Source in the Data Sources dialog box.

8 See “Configuring the Data Source” on page 51 to complete the WebLogic Data Source configuration.


Configuring WebLogic for Microsoft SQL Server Databases 51

Configuring the Data Source Overview This section describes how to set up the data source for WebLogic when the Contract Management database is a Microsoft SQL database, and if you have configured a P6 EPPM Schedule database as part of your Contract Management system installation.

Complete all the following procedures for each database:

■ Once for the GROUP database. You are required to have at least one group database.

Through the Contract Management installation wizard, you can create one of the default databases, CMDEMO or CMPROJ, with sample data.

■ Once for the ADMIN database, also referred to as EXPADMIN.

■ Once for the P6 EPPM Schedule database if it is configured with your system. This database is referred to as the PMDB.

In this section, CMDEMO and CMPROJ are used as the group database names. While they are the default GROUP database names, they are provided only as examples of possible GROUP database names.

Configure JDBC Data Source Properties Complete the following steps in the JDBC Data Source Properties dialog box:

1 Set the Name field to one of the following (depending on which data source your are setting up:

• CMDEMO for the CMDEMO database

• CMPROJ for the CMPROJ database

• EXPADMIN for the EXPADMIN database

• PMDB for the PMDB



2 Set the JNDI Name field to jdbc/<database_name>, where <database_name> is:

• CMDEMO for the CMDEMO database

• CMPROJ for the CMPROJ database

• EXPADMIN for the EXPADMIN database

• PMDB for the PMDB

3 Set the Database Type field to MS SQL Server.

4 Set the Database Driver field to:

Microsoft SQL Server Driver (Type 4) Versions 2005 and later

5 Click Next. The Transaction Options dialog box displays.

Set Transaction Options

1 If you are configuring the Admin or P6 EPPM database, clear the Supports Global Transactions option, and click Next.

2 If you are configuring a project database:

a) Select the Supports Global Transactions option.

b) Click the One-Phase Commit radio button.

c) Click Next. The Connection Properties dialog box displays.

Set the Connection Properties

1 Set the Database Name field to one of the following:

• The Database name for the Contract Management ADMIN database. This is EXPADMIN.

• The Database name for the Contract Management GROUP database. The default values are CMDEMO and CMPROJ.

• The Name of the P6 EPPM Schedule Database for the PMDB.

2 Set the Host Name field to <database_hostname>, where <database_hostname> is the host on which Microsoft SQL Server is installed.

3 Set the Port field to <database_port>, where <database_port> is the port number of the host on which Microsoft SQL Server is installed. The default port number is 1433.

4 Set the Database User Name field. These were determined when you created the databases. For example, these might be:



• exp for the EXPADMIN database

• exp for each GROUP database (CMDEMO or CMPROJ)

• privuser of the PMDB

5 Set the Password field. These were determined when you created the databases. For example, these might be:

• sql for the EXPADMIN database

• sql for each GROUP database (CMDEMO or CMPROJ)

• privuser for the PMDB

6 Confirm the Password.

7 Click Next. The Test Database Connection dialog box displays.

Test the Database Connection

1 Click Test Configuration to verify that connection is successful.

2 Click Next. The Select Targets dialog box Displays.

Select Targets

1 Check <server_name>, where <server_name> is the target server instance for Contract Management.

2 Click Finish.



Deploying Contract Management

You cannot perform the steps in this procedure until after you have installed Contract Management. You must also restart the WebLogic application server before continuing.

When you finish setting up both the CMDEMO and EXPADMIN data sources for WebLogic, complete the following steps from the WebLogic Server Administration Console:

1 In the WebLogic Server Administration Console, click Activate Changes.


3 Click Deployments in the left hand pane.

4 Click Install in the Deployments section of the right hand pane.

5 In the Install Application Assistant section of the right hand pane, in the Location section, choose the expedition.ear file from the <Contract Management home>\Ear folder, and click Next.

6 In the Install Application Assistant section of the right hand pane, in the Choose targeting style section, click Install this deployment as an application, and click Next.

7 In the Install Application Assistant section of the right hand pane, in the Optional Settings section at the top of the pane, click Finish.

8 In the WebLogic Administration Console window, the Summary of Deployments displays in the right hand pane. In the left hand Change Center pane, click Activate Changes at the top of the pane.

9 Restart the WebLogic server instance, and log back into the Administration Console site.


11 In the Summary of Deployments section of the right hand pane, select the expedition deployment option, click Start under Deployments, and choose Servicing all requests from the drop-down list.

12 In the Start Application Assistant in the right hand pane, click Yes to confirm that you want to start the deployment.

The steps in this section provide the preferred method of deploying Contract Management.



Configuring the Contract Management Port Specification

You cannot perform the steps in this procedure until after you have installed Contract Management.

When Contract Management is not running under the default port (80), you must manually update the configuration file containing the port designation.

You must set the Web server WebPort option to the appropriate value. Log on to the Administration Config utility, and do the following:

1 Expand the tree to the Web Server folder by selecting Contract Management Settings > Web Server.

2 Triple-click, and enter a value for each of the following options:

• CharacterEncoding

• CompressionEnabled

• ExpeditionWebServiceName

• WebApplicationName — This is exponline.

• WebProtocol

• WebPort

• WebServerName

• sessiontimeout

• xmlsessiontimeout

3 Update the following line, and replace the port number with the appropriate port number.WebPort=7001

7001 is the default WebPort for WebLogic

4 Click Save Changes.


57

Use this chapter if you will use Contract

Management in a WebLogic cluster

environment.

In this chapter

Prerequisites

Configuring the Clustered Environment

Considerations for Using Contract Management in a Clustered Environment

Using the XML API in a Clustered Environment

Enabling Node Manager for Contract Management in a Clustered Environment

Configuring Contract Management for a WebLogic Cluster

58 Configuring Contract Management for a WebLogic Cluster

PrerequisitesConsult the WebLogic documentation for information on setting up a WebLogic cluster. This can be found at the following web site: http://download.oracle.com/docs/cd/E17904_01/wls.htm

On the WebLogic Admin server:

1 Configure a domain specific to WebLogic, and install Contract Management on that server.

2 Create the required number of managed servers (nodes), and associate machines with each of the managed servers.

3 Do not install Contract Management on any of the managed servers.


Configuring Contract Management for a WebLogic Cluster 59

Configuring the Clustered Environment1 Make changes to startManagedWebLogic.cmd (startManaged-

WebLogic.sh in a non-Windows system).

Oracle Primavera recommends that you echo classpath and Java_options to ensure that the changes you make in step 1 are accurate.

2 On each managed server machine, configure a domain specific to Contract Management that is identical to the one that you created for the Admin server.

3 On each managed server machine, make the same changes to startManagedWebLogic.cmd (startManagedWebLogic.sh in a non-Windows system) that you made in step one of this procedure.

4 On the server where you installed WebLogic, copy all the files in the <Contract Management_domain_home>\bin folder into the <domain_home>\bin folder on each of the managed server machines.

5 Copy all the files in the <Contract Management_domain_home>\lib folder on the admin server machine into the <Contract Management_domain_home>\lib folder on each of the managed server machines.

6 Copy the <Contract Management_domain_home>\com folder from the admin server machine to each of the managed server machines.

7 Start the Admin server, and each managed server machine.

8 Deploy the expedition.ear file on each managed server machine. This file is located in the <Contract Management home> folder.

9 Deploy Contract Management as described in “Configuring the Contract Management Port Specification” on page 55.

When selecting target servers for Contract Management, the datasources target should be all servers in cluster.

After you finish steps 1 through 9, do the following:

1 Ensure that each managed server has an independent Oracle Content Server home.

2 Ensure that reports and forms locations are shared from a single location.



3 Copy the <Contract Management home>\HtmlTemplates directory to all managed server machines in the same path. These must be synchronized when any modifications are made to them.

4 If you are adding attachments and are using the “not connected to server” configuration, all attachment directory setups must be either a UNC path or a mapped drive. For mapped drives, all managed servers must have the same mapping to the server.



Considerations for Using Contract Management in a Clustered Environment

In a clustered environment, Oracle Primavera recommends that the following operations only be performed when no users (except the user performing these operations) are logged into Contract Management:

■ Single Project Restore

■ Project Delete

■ Modifying, adding, or deleting custom fields

■ Modifying, adding, or deleting cost code definitions



Using the XML API in a Clustered EnvironmentPassing the JSESSIONID If using the XML API in a clustered environment, when any client application sends a request to the server, the first server response will contain a cookie called JSESSIONID.

The client application must store the cookie, and then must send that cookie with each subsequent request to the server.

Choosing an Affinity algorithm When using the XML API in a clustered environment, you must choose an Affinity algorithm.

1 On the WebLogic Server Administration Console, in the Change Center, click the Lock & Edit button.

2 In the Environment section of the Home Page, click Clusters.

3 On the Summary of Clusters page, click the link for the appropriate cluster.

4 On the Settings for <cluster name> page, click the Configuration tab then click the General subordinate tab.

5 From the drop-down list next to Default Load Algorithm, choose an affinity algorithm. It must be an Affinity algorithm (for example, random-affinity).

6 Click Save to save the settings.

7 In the Change Center, click Release Configuration.



Enabling Node Manager for Contract Management in a Clustered Environment

Edit the nodemanager.properties file on each node. This file is in the following location:

“%WL_HOME%\wlserver_10.3\common\nodemanager.cmd”

Set the following:

■ Set StartScriptEnabled=true

■ Set StartScriptName=startManagedWebLogic.cmd


65

This chapter describes how to view and

modify Contract Management configuration

settings in the Administration Config utility.

Run this utility to change database,

authentication configuration, or general

preferences settings.

In this chapter:

Starting the Administration Config Utility

Modifying Values of Configuration Settings

Modifying Authentication Settings

Modifying Web Single Sign-On Settings

Modifying Autovue Integration Settings

Modifying BI Publisher Settings

Modifying Configuration Management Settings

Modifying Content Repository Settings

Modifying Database Settings

Modifying P6 EPPM Schedule Database Settings

Setting Preferences

Modifying User Productivity Kit Settings

Modifying Web Server Settings

Configuration Settings for Contract Management

Viewing and Modifying Contract Management Settings

66 Viewing and Modifying Contract Management Settings

Starting the Administration Config UtilityAs the system administrator, you can use the Administration Config utility to review and modify Contract Management configurations.

Content Displayed in the Administration Config utility Contract Management system configurations, including settings for the database server, authentication, content repository, and preferences, are stored in the Contract Management database that you specified during installation.

Only experienced administrators should use the Administration Config utility to modify configuration settings.

Real Application Clusters When using Real Application Clusters (RAC) with Contract Management, only one database instance will be used for the Administration Config utility. Contract Management reports and forms use that same database instance. If the node on which that instance resides fails, the Contract Management reports and forms will not work as there is no fail-over to another node. You can either bring the failed node back up, or reconfigure the database instance settings to use another node. See the Contract Management Installation and Configuration Guide (for Oracle or Microsoft SQL Server) for information on configuring database instance settings.

Access to the Administration Config utility You must run the Administration Config utility locally. After launching the Administration Config utility, you will be prompted for an Admin Superuser name and password. See “Run the Administration Config utility” on page 67.

Components of the Administration Config utility The Administration Config utility presents configuration settings in a tabbed dialog box.

Tree View presents the current configurations and settings in an expandable and collapsible hierarchy. Select the Show tool tips option to display information in tool tips when your mouse pointer lingers over a setting. To change a setting value, triple-click the setting name and enter a new value. In Windows, you can also press F2 to edit the setting value. To return a setting to its default value, right-click it and select Revert to default value.


Viewing and Modifying Contract Management Settings 67

Table View presents the current configurations and settings in a table, organized alphabetically in ascending or descending order. To sort the content of a column, click the column heading. Sorting can help you distinguish similar settings contained in multiple configurations. To change a value, click the Value field for a configuration and enter a new value.

The Log displays a history of configuration changes, additions, or deletions.

Run the Administration Config utility

1 Navigate to the folder where you installed Contract Management. By default, this is:

\Program Files\Oracle\ContractManagement

2 In the folder where you installed Contract Management, navigate to the \Utility\CMAdminConfig folder:

\Program Files\Oracle\ContractManagement\Utility\CMAdminConfig

3 Double-click admincm.cmd (admin.sh in a non-Windows system) to run the Administration Config utility.

Show Tool Tips To display brief setting descriptions in Tree or Table view in the Administration Config utility, do the following:

1 Select the Show tool tips option.

2 Position the mouse over a setting.

A popup is displayed that contains a description of the setting.



Modifying Values of Configuration Settings

Factory Default configuration settings are preset and cannot be changed. You can modify all custom configurations.

Reset a Configured Value to a Default

1 Expand the tree to the value you want to change.

2 Right-click the value.

3 Select Revert to default value.

The configured value is reset to the default.

Change a Configured Value in Tree View

1 Expand the tree to the value you want to change.

2 Triple-click the value.

3 Enter a new value.


Change a Configured Value in Table View

1 Click column headings to sort information in columns and scroll to the value you want to change.

2 In the Value column, click in the cell that contains the value to be changed.

3 Do one of the following:

• Delete the current value from the cell, and enter a new value.

• If a menu is displayed, select a new value.




Modifying Authentication SettingsContract Management provides native, proprietary authentication that is installed by default. After the installation, you can configure Lightweight Directory Access Protocol (LDAP) authentication if you prefer.

In addition to these settings for enabling LDAP authentication, you can set values of mapped database fields per user.

For more information about each of these settings, refer to the Authentication Settings section in, “Configuration Settings for Contract Management” on page 88.

Configure LDAP Authentication in Tree View

1 Select the mode of authentication:

a) Expand the tree to the Authentication folder by selecting Contract Management Settings >Authentication.

b) Triple-click Mode.

c) From the pull-down menu, select LDAP.

2 Set LDAP attributes:

a) Expand the tree to the Connection Information folder by selecting Contract Management Settings> Authentication > LDAP > Connection Information.

b) Triple-click, and enter a value for each of the following required fields:

• Host Name

• Port Number

• Username

• Password

• Base Distinguished Name

The following fields are only required if you are using SSL:

• SSL Certificate Store

• SSL Store Password

3 Set LDAP user field mappings as appropriate for your site.



Mapped DatabaseField: LOGIN_NAME is a required field for which you must enter a value. All other fields are optional. Set them as appropriate for your site.

a) Expand the tree to a FieldMap folder by selecting Contract Management Settings > Authentication > LDAP > LDAP to DB Field Mappings > FieldMap.

b) Expand each FieldMap folder.

c) Triple-click each appropriate LDAP Attribute field, delete the current value, and enter the value of each field in the text box.

For information about each of the LDAP attribute fields in the FieldMap folders, see “Configuration Settings for Contract Management” on page 88.


Configure LDAP Authentication in Table View In Table View, when the Setting Name column is sorted alphabetically in descending order, for example, from Z to A, the list of Mapped Database Fields are displayed under the LDAP Attribute fields, for which values are required.

When the Setting Name column is sorted in ascending order, for example from A to Z, the list of Mapped Database Fields are displayed above the LDAP Attribute fields.

To set values in Table view:

1 Locate the appropriate paths to the folders in the table that corre-spond with those described for Tree View.

2 Enter values for all required fields.

3 Click Save Changes when finished.



Modifying Web Single Sign-On SettingsFor more information about each of these settings, refer to the Web Single Sign-On section in, “Configuration Settings for Contract Management” on page 88.

Changing Web Single Sign-On Settings in Tree View

1 Expand the tree to the Web Single Sign-On folder by selecting Contract Management Settings > Authentication > Web Single Sign-On.

2 Triple-click and enter values for each of the following:

• User Name Header Key

• Context Path Override

• Server and Port Override


Changing Web Single Sign-On Settings in Table View You can also enter the Web Single Sign-On settings in the Table View, rather than using the Tree View.

1 In the Setting Name column, locate the three Authentication/Web Single Sign-On fields.

2 Click in the corresponding cell of the Value column for each one, and enter the correct value.




Modifying Autovue Integration SettingsThese settings are necessary to enable Contract Management users to view documents using Autovue. For information about each of these settings, refer to the Autovue Integration section in, “Configuration Settings for Contract Management” on page 88.

Changing Autovue Integration Settings in Tree View

1 Expand the tree to the Autovue Integration Settings folder by selecting Contract Management Settings > Autovue Integration Settings.

2 Triple-click, and enter values for each of the following:

• URL

• Enable


Changing Autovue Integration Settings in Table View You can use the Table View, if you prefer, to enter the Autovue Integration settings, instead of the Tree View.

1 In the Setting Name column, locate the two Autovue Integration Settings fields.

2 Click in the corresponding cell of the Value column for each one, and enter the correct value.




Modifying BI Publisher SettingsYou must connect Oracle Business Intelligence Publisher to Contract Management to view and print reports and documents. BI Publisher should be configured after installing Contract Management. For information about the settings in this section, see “Configuration Settings for Contract Management” on page 88.

In Tree View:

1 Expand the tree to the BI Publisher folder by selecting Contract Management Settings > BI Publisher.


• Username

• Password

• WebService URL


In Table View:






Modifying Configuration Management SettingsYou can determine whether to gather client configuration information. For information about the settings in this section, see “Configuration Settings for Contract Management” on page 88.

In Tree View:

1 Expand the tree to the Configuration Management folder by selecting Contract Management Settings > Configuration Management.


• Configuration Capture

• Configuration Capture Time


In Table View:






Modifying Content Repository SettingsYou can modify settings of your pre-configured Oracle or Microsoft SharePoint content repository. You can also change the type of content repository and all related attributes.

Content Repository Authentication Modes Contract Management offers two content repository authentication modes:

■ Single user authentication

■ Multiple user authentication

In single user authentication mode, all Contract Management users access the repository using a single administrator user login that is set during repository configuration. In multiple user authentication mode, each Contract Management user is authenticated based on their individual login.

Single user authentication mode is the default mode. It is useful when you want users to have full access to the content repository through Contract Management without having to maintain an equivalent list of users for both Contract Management and the repository. This allows a repository administrator to maintain one set of credentials for the repository without having to share those credentials with all users. Single user authentication is also useful for quickly setting up test repositories that testers can access with minimal fuss.

Multiple user authentication mode provides increased security by restricting content repository access on an individual user basis. Because it uses native auditing fields, it also allows a clear audit of who has created and modified files.

When using multiple user authentication mode, you should disable Oracle Universal Content Management Guest Access. If Guest Access is enabled and the guest user is not part of the Contract Management security group, that user will not be able to access Contract Management repository functionality.

For information about the other settings in this section, see “Configuration Settings for Contract Management” on page 88.



Changing Content Repository Settings in Tree View

1 Expand the tree to the Content Repository folder by selecting Contract Management Settings > Content Repository.

2 Select the type of content repository:

a) Triple-click Type.

b) From the pull-down menu, select Oracle Content Server or Microsoft SharePoint.

3 Set the repository attributes for the type of repository you chose.

For Oracle Content Server:

Triple-click, delete the current value, and enter a value for each of the following options:

• Oracle Host Name

• Port

• Oracle Home

• Oracle Security Group

• Oracle Security Account

• Oracle Document Type

• Metadata Prefix

• Admin User

• Authentication Mode

For Microsoft SharePoint:

Triple-click, delete the current value, and enter a value for each of the following options:

• Login Name

• Password

• Authentication Mode

• Host Name

• Domain Name

• URL

• Web Service URL

• External Document Library URL




Changing Content Repository Settings in Table View You can also enter the Content Repository settings in the Table View, rather than using the Tree View.

1 In the Setting Name column, locate the Content Repository/Type field.

2 Click in the corresponding cell of the Value column, and select Oracle Content Server or Microsoft SharePoint from the pull-down menu.

3 Set the content repository settings.

• If you are using an Oracle content repository, in the Setting Name column find the path that starts with Content Repository/Oracle Content Server/, and then in the Value column enter the values for the settings.

• If you are using a SharePoint content repository, in the Setting Name column find the path that starts with Content Repository/Microsoft SharePoint/, and then in the Value column enter the values for the settings.




Modifying Database SettingsIn the Administration Config utility, you can complete the following tasks:

■ Change Contract Management Database Settings

■ Change ADMIN Database Settings.

■ Change GROUP Database Settings

■ Add a New GROUP Database

■ Delete a GROUP Database

For information about the settings in this section, see “Configuration Settings for Contract Management” on page 88.

Change Contract Management Database Settings During installation, you set the type of database to use with the Contract Management application. Following installation, you can change the following database settings:

■ Port number over which the database receives data from the Contract Management application.

■ Host name of the database, for example, if you move the database to another server.

■ Site name of the database. For more information, see DatabaseSiteName in the Database section of “Configuration Settings for Contract Management” on page 88.

In Tree View:

1 Expand the tree to the Database folder by selecting Contract Management Settings > Database Settings.

2 Triple-click and enter a value for each of the following options:

• Type

• Port

• Host Name

• Site Name



For information about the port number currently used, run the Registry Editor in Windows: select Start> Run, and in the Open field of the Run dialog box, enter regedit, and click OK. For a Microsoft SQL database, expand HKEY_LOCAL_MACHINE>SOFTWARE>Microsoft>Microsoft SQL Server>Primavera>MSSQLServer>SuperSocketNetLib. Click the Tcp folder. The setting of the TcpPort registry key displays the port number used by the Contract Management database.


In Table View:


1 Locate the appropriate paths to the folders in the Table View that correspond with those described for Tree View.



4 Change ADMIN Database Settings.

You can change ADMIN database settings in Tree View and Table view.

You can configure Contract Management to run with only one instance of the ADMIN database. Therefore, you cannot duplicate or create new instances of the ADMIN database.

In Tree View:

1 Expand the tree to the ADMIN folder by selecting Contract Management Settings > Database Settings > Database Groups > ADMIN.


• DBName

• JNDIName

• Name

• Password

• Report Location



• UserName

The Name field value cannot be changed.


In Table View:

1 Locate the appropriate paths to the folders in the Table View that correspond with those described as for Tree View.



Change GROUP Database Settings

In Tree View:

1 Expand the tree to the ADMIN folder by selecting Contract Management Settings > Database Settings> Database Groups > GROUP:<database_name>.

If multiple instances of the GROUP database exist, the folder name includes the number of each instance. For example, in the folder name GROUP[1]:<database_name>, the [1] indicates that multiple instances of the database exist and that the first instance is selected.


• DBName

• JNDIName

• Name

• Password

• Report Location

• Letter Template Location

• UserName


In Table View:



If multiple instances of the GROUP database exist, the folder name includes the number of each instance. For example, in the folder name GROUP[1]:<database_name>, the [1] indicates that multiple instances of the database exist and that the first instance is selected.





Add a New GROUP Database To add a new GROUP database to a configuration, you can:

■ Duplicate an existing database in the Tree View.

■ Copy a database folder, paste it, and change settings of the new database.

■ Right-click the Database Groups folder, and select Add Database Group.


To add a new GROUP database by copying or duplicating an existing one:

1 Expand the tree to the GROUP database you want to duplicate.

For example, select Contract Management Settings > Database Settings > Database Groups > GROUP[1]:cmdemo.

2 Right-click the folder of the database you want to duplicate.

3 Do one of the following:

• Select Duplicate.

• Right-click and select Copy, and then right-click and select Paste.

4 Enter a unique name for the new instance and edit other settings as required.



For information about changing GROUP database settings in the Tree View or in the Table View, see “Change GROUP Database Settings” on page 80.


To add a new database without copying or duplicating an existing one:

1 Expand the Database Settings folder, right-click the Database Groups folder, and click Add Database Group to open the Configure Group Database dialog box.

2 On the Configure Group Database dialog box, enter the following information:

• Name

• Database Name (SID)

• Username

• Password

• Report Location

• Letter Template Location

3 Click OK.

Delete a GROUP Database You can delete a group database in the Tree View.

1 Expand the tree to the GROUP database you want to delete.

For example, select Database Settings > Database Groups > GROUP[1]:cmdemo.

2 Right-click the folder of the database instance to delete.

3 Select Delete.




Modifying P6 EPPM Schedule Database SettingsAfter installation, you can configure the settings that enable a connection between a P6 EPPM Schedule Database and Contract Management. For information about the settings in this section, see “Configuration Settings for Contract Management” on page 88.

You can configure Contract Management to run with only one instance of the P6 EPPM Schedule Database.

Change P6 EPPM Schedule Database Settings

In Tree View:

1 Expand the tree to the Project Management folder by selecting Contract Management Settings > Database Settings > Project Management.

2 Select the database type.

a) Triple-click Type.

If no P6 EPPM Schedule Database was configured during installation, this field value is set to null.

b) Select the database type: mssql or oracle.


• Type

• Name

• Host Name

• Port Number

• SID (Oracle Only)

• User Name

• Password

• URL – The format of the URL is:

http://<p6_server_host_name>:port>/p6/comp/showproject

• Encryption Key

In the URL, substitute the actual IP address for the <IP address of > variable.



The preceding URL should be all on one line. Format restrictions of this document prevent it from appearing on one line.

4 Right-click on the Encryption Key field.

a) From the pop-up list, click Generate encryption key. This displays the Generate encryption key dialog.

b) In the Generate encryption key field, enter the Pass phrase used to generate the encryption key. This has to be the same Pass phrase set up for P6 Web Access.

In order for Contract Management to seamlessly exchange data with a P6 EPPM schedule without having to logon to each application, you must use the Pass phrase. It must be the same one used when setting up P6 Web Access.

c) Click the Key field beneath the Generate encryption key field, and the key will be displayed. Click OK.

To use the default settings, choose Revert to default values from the popup menu described in step 4 a).


In Table View:




Click Save Changes when finished.



Setting PreferencesAfter installation, you can modify preferences including your mail server, paths to templates used in Contract Management, and the location in which to store report images. For information about the settings in this section, see “Configuration Settings for Contract Management” on page 88.

In Tree View:

1 Expand the tree to the Preferences folder by selecting Contract Management Settings > Preferences.


• Grid To Excel

• Include URL in Mail

• Install Path

• Print Debug Level

• Alerts Refresh Interval

• Widgets Refresh Interval

• SMTP Server

• Template Path


In Table View:






Modifying User Productivity Kit SettingsIn the User Productivity Kit (UPK) section, you can turn on the UPK function and set its location. UPK is an Oracle product that you can purchase and then use to create instructions (tutorials) to demonstrate how to perform tasks in other Oracle products. When you purchase the User Productivity Kit, and configure it to recognize Contract Management content, you can create tutorials to demonstrate Contract Management functionality.


In Tree View:

1 Expand the tree to the User Productivity Kit folder by selecting Contract Management Settings > User Productivity Kit.


• Enable User Productivity Kit

• User Productivity Kit URL


In Table View:






Modifying Web Server SettingsSetting up your Web server is a prerequisite to installing your Contract Management software. After installation, you can change previously configured Web server settings if required. For information about the settings in this section, see “Configuration Settings for Contract Management” on page 88.

In Tree View:

1 Expand the tree to the ADMIN folder by selecting Contract Management Settings > Web Server.


• CharacterEncoding

• CompressionEnabled

• ExpeditionWebServiceName

• WebApplicationName — This is exponline.

• WebProtocol

• WebPort

• WebServerName

• sessiontimeout

• xmlsessiontimeout


In Table View:






Configuration Settings for Contract ManagementYou can review and modify configuration settings in the Tree View or Table View. Configuration settings are stored in the Contract Management database.

You can specify durations (time-related values).

Contract Management Settings

Setting Name and Description Default Valid Ranges/Values

Authentication

Authentication/ModeThe method used for client authentication.

NATIVE or LDAP Native, LDAP

Authentication > LDAP > Connection Information

Authentication/LDAP/Connection Information/Host NameLDAP server host name.

— —

Authentication/LDAP/Connection Information/Port NumberPort number for authentication via the LDAP server.

389 —

Authentication/LDAP/Connection Information/UsernameUser name for authentication via the LDAP server.

— —

Authentication/LDAP/Connection Information/PasswordPassword for authentication via the LDAP server.

— —

Authentication/LDAP/Connection Information/Base Distinguished NameBase domain name of the LDAP server.

— —

Authentication/LDAP/Connection Information/SSL Certificate StoreThe full path to the keystore that holds the SSL certificate for the LDAP server.

— —

Authentication/LDAP/Connection Information/SSL Store PasswordThe password for the keystore that holds the SSL certificate.

— —




Authentication > LDAP > LDAP to DB Field Mappings

Authentication/LDAP/LDAP to DB Field Mappings/FieldMap/MappedDatabaseField:EMAILEmail address of the user to be authenticated.

— —

Authentication/LDAP/LDAP to DB Field Mappings/FieldMap/MappedDatabaseField:EXTENSIONWork telephone extension of the user to be authenticated.

— —

Authentication/LDAP/LDAP to DB Field Mappings/FieldMap/MappedDatabaseField:FAXFax number of the user to be authenticated.

— —

Authentication/LDAP/LDAP to DB Field Mappings/FieldMap/MappedDatabaseField:FIRST_NAMEFirst name of the user to be authenticated.

— —

Authentication/LDAP/LDAP to DB Field Mappings/FieldMap/MappedDatabaseField:FULL_NAMEFull name of the user to be authenticated.

— —

Authentication/LDAP/LDAP to DB Field Mappings/FieldMap/MappedDatabaseField:JOB_TITLEJob title of the user to be authenticated.

— —

Authentication/LDAP/LDAP to DB Field Mappings/FieldMap/MappedDatabaseField:LAST_NAMELast name of the user to be authenticated.

— —

Authentication/LDAP/LDAP to DB Field Mappings/FieldMap/MappedDatabaseField:LOGIN_NAMELogin name of the user to be authenticated.

— —

Authentication/LDAP/LDAP to DB Field Mappings/FieldMap/MappedDatabaseField:MOBILEMobile (cellular) telephone number of the user to be authenticated.

— —




Authentication > LDAP > LDAP to DB Field Mappings

Authentication/LDAP/LDAP to DB Field Mappings/FieldMap/MappedDatabaseField:TELEPHONEPersonal telephone number of the user to be authenticated.

— —

Authentication > LDAP

Authentication/LDAP/Last LDAP SearchThe last search done using the LDAP tool to locate Contract Management users to import.

— —

Authentication >Web Single Sign-On

Authentication/Web Single Sign-On/User Name Header KeyThe string in the HTTP header that identifies the user name.

— —

Authentication/Web Single Sign-On/Context Path OverrideThe base URL for Contract Management.

Authentication/Web Single Sign-On/Server and Port OverrideThe server name and port to direct the URL to.

Autovue Integration Settings

Autovue Integration Settings/URLThe URL of the host where the vuelink for the Content Repository is installed. For example:For SharePoint:

http://<hostname>/<CM Sharepoint_site>/_layouts/1033/vue.aspx

For Oracle Content Server: http://<hostname>/idc/jsp/autovue/csiApplet.jsp

Note: Each URL should appear on one line. Format restrictions of this document prevent some of them from doing so.

— Oracle or SharePoint

Autovue Integration Settings/EnableUsed to enable or disable Autovue Integration.

true or false




BI Publisher

BI Publisher/UsernameContract Management uses this to access an account in BI Publisher that has rights to run reports. The account is created on the BI Publisher server specifically for Contract Management to use.

— —

BI Publisher/PasswordContract Management uses this to access an account in BI Publisher that has rights to run reports. The account is created on the BI Publisher server specifically for Contract Management to use.

— —

BI Publisher/WebService URLDetermines the Business Intelligence server to which Contract Management connects. The URL should point to the WSDL. For example:http://host:port/xmlpserver/services/PublicReportService? wsdl

— —

Configuration Management

Configuration Management/Configuration CaptureUsed to turn automatic configuration capture for Oracle on or off.

Configuration Management/Configuration Capture TimeUsed to set the time to start the automatic configuration capture for Oracle.

Content Repository>Type

Content Repository/TypeType of content repository used with Contract Management. Options include Oracle or SharePoint.

Oracle or SharePoint

Content Repository>Oracle Content Server

Content Repository/Oracle Content Server/Oracle Host NameThe IP address or the machine name for the content repository host.

— —

Content Repository/Oracle Content Server/PortThe port number where the content repository resides.

— —





Content Repository/Oracle Content Server/Oracle HomeThe root level folder for the content repository.Create a root level folder in UCM beneath Contribution Folders. The Oracle Home field must contain both Contribution Folders and the root you create. The root path must start and end with a \ character. For example: \Contribution Folders\OraclePrimavera\

— —

Content Repository/Oracle Content Server/Oracle Security GroupSet by the Oracle Administrator.

— —

Content Repository/Oracle Content Server/Oracle Security AccountSet by the Oracle Administrator.

— —

Content Repository/Oracle Content Server/Oracle Document TypeSet by the Oracle Administrator.

— —

Content Repository/Oracle Content Server/Metadata Prefix

Cm Cm

Content Repository/Oracle Content Server/Admin UserThe administrator user name required for accessing the content repository for administrative and maintenance purposes. This user name must exist on the content repository server, and must have administrative privileges.

— —





Content Repository/Oracle Content Server/Authentication ModeThe authentication mode used for access to the Oracle Universal Content Management server. If these conditions are not met, content repository functions will not be available to Contract Management users.

Use Single User to always log into Oracle with the Admin User name. In this mode, no matter which user logs onto Contract Management, the Modified By and Created By columns for versions and attachments in the Oracle Content Server will be the same user name specified in the Administration Config utility Tool Settings.

Use Multiple Users to logon to Oracle with the credentials of the user logged into Contract Management. In this mode, the Modified By and Created By columns for versions and attachments in the Oracle Content Server will be the same user name used to logon to Contract Management. Therefore, Contract Management should be configured to use the same active directory or LDAP server as the Oracle Content Server. If you choose Multiple User, all Contract Management content repository-related user names must match the equivalent Oracle UCM user name. For example, a Contract Management user named “Joe” must have an equivalent user named “Joe” in the Oracle UCM.

Single Single UserMultiple User

Content Repository>Microsoft SharePoint

Content Repository/Microsoft SharePoint/Login NameThe name required for logging onto the content repository.

— —

Content Repository/Microsoft SharePoint/PasswordThe password required for logging onto the content repository.

— —





Content Repository/Microsoft SharePoint/Authentication ModeThe authentication mode used for access to the Microsoft SharePoint server. If these conditions are not met content repository functions will not be available to Contract Management users.

Use Single User to always log into SharePoint with the Admin User name. In this mode, no matter which user logs onto Contract Management, the Author column for versions and attachments in SharePoint will be the same credentials specified in the Administration Config utility Tool Settings.

Use Multiple Users to logon to SharePoint with the user name of the user logged into Contract Management. In this mode, the Modified By and Created By columns for versions and attachments in Microsoft SharePoint will be the same user name used to logon to Contract Management. Therefore, Contract Management should be configured to use the same active directory or LDAP server as the SharePoint Server. If you choose Multiple User, all Contract Management content repository-related user names must match the equivalent SharePoint user name. For example, a Contract Management user named “Joe” must have an equivalent user named “Joe” Microsoft SharePoint.

Single User Single UserMultiple User

Content Repository/Microsoft SharePoint/Host NameThe name of the host on which the content repository resides.

— —

Content Repository/Microsoft SharePoint/Domain NameSharePoint authentication domain name.

— —

Content Repository/Microsoft SharePoint/URLThe URL of the Microsoft SharePoint document library used by Contract Management. This document library is internal to Contract Management.

— —

Content Repository/Microsoft SharePoint/Web Service URLThe URL of the Oracle Primavera SharePoint connector. This enables Contract Management and P6 EPPM to use a single sign-on to communicate with the Microsoft SharePoint repository.

— —





Content Repository/Microsoft SharePoint/External Document Library URLThe path to the document library that is external to Contract Management. Users can browse this library for documents to attach to Contract Management documents.

— —

Database Settings

Database Settings/Database TypeDatabase type.

— —

Database Settings/Port NumberPort number used by the MSSQL or Oracle database configured for use with Contract Management.

MSSQL: 1433Oracle: 1521

—

Database Settings/Host NameName of the computer on which the Contract Management database resides. This can be the host name or the IP address.

— —

Database Settings/Site NameA string of up to four characters that is used to make the primary keys unique for each company site.

Database Settings > Database Groups > ADMIN

Database Settings/Database Groups/ADMIN/DBNameName of the ADMIN database as it is displayed within the related database management application, for example, if your ADMIN database is a Microsoft SQL database, the DBName is the name of the database as it displays in Microsoft SQL Server Management Studio Express.

— —

Database Settings/Database Groups/ADMIN/JNDINameJava Naming Directory Interface (JNDI) name of the ADMIN database that enables clients to identify and locate it.

— —

Database Settings/Database Groups/ADMIN/NameAdministrator user name for accessing the ADMIN database.

— —

Database Settings/Database Groups/ADMIN/PasswordPassword for accessing the ADMIN database.

— —

Database Settings/Database Groups/ADMIN/ReportLocationThe location for Contract Management reports.

— —




Database Settings > Database Groups > ADMIN

Database Settings/Database Groups/ADMIN/UserNameThe user name used by Contract Management to access the Contract Management ADMIN database.

— —

Database Settings > Database Groups > GROUP

Database Settings > Database Groups > GROUPNote: If more than one GROUP database instance is configured, the database instance name displays as GROUP[#]: <database_name> in the Administration Config utility.

— —

Database Settings/Database Groups/GROUP/DBNameName of the GROUP database as it displays within the related database management application. For example, if your GROUP database is a Microsoft SQL database, the DBName is the name of the database as it displays in Microsoft SQL Server Management Studio Express.

— —

Database Settings/Database Groups/GROUP/JNDINameJava Naming Directory Interface (JNDI) name of the database that enables clients to identify and locate it.

— —

Database Settings/Database Groups/GROUP/NameAdministrator user name for accessing the GROUP database.

— —

Database Settings/Database Groups/GROUP/PasswordPassword for accessing the GROUP database.

— —

Database Settings/Database Groups/GROUP/Report LocationThe location for Contract Management reports.

— —

Database Settings/Database Groups/GROUP/Letter Template LocationThe folder in which Contract Management will search for letter templates.

— —

Database Settings/Database Groups/GROUP/UserNameThe user name used by Contract Management to access the Contract Management GROUP databases.

— —




Database Settings > Project Management

Database Settings/Project Management/TypeType of P6 EPPM Schedule Database configured to exchange data with Contract Management, if one was configured during installation.

null — Indicates that no P6 EPPM Schedule Database was configured.

mssql — Indicates that a Microsoft SQL P6 EPPM Schedule Database was configured with Contract Management.

oracle — Indicates that an Oracle P6 EPPM Schedule Database was configured with Contract Management.

Database Settings/Project Management/NameName of P6 EPPM Schedule Database configured to exchange data with Contract Management, as the name displays in the database management application.

— —

Database Settings/Project Management/Host NameName of the host on which the P6 EPPM Schedule Database resides.

— —

Database Settings/Project Management/Port NumberThe port number of the P6 EPPM Database.

— —

Database Settings/Project Management/SID (Oracle Only)Unique identifier of an Oracle P6 EPPM Schedule Database.

— —

Database Settings/Project Management/User NameUser name required to access the P6 EPPM Schedule Database.

— —

Database Settings/Project Management/PasswordPassword required to access the P6 EPPM Schedule Database.

— —

Database Settings > Project Management

Database Settings/Project Management/URLURL of the remotely-based, Web-accessible P6 EPPM Schedule Database.

— —

Database Settings/Project Management/Encryption KeyUsed to enable seamless integration between Contract Management and the P6 EPPM Database. Set by right-clicking the field name. See step 4 in “Change P6 EPPM Schedule Database Settings” on page 83.

— —




Preferences

Preferences/Grid To ExcelPath to the gridtoexcel.xsl file that stores data derived from Contract Management. For more information, see the Web & Application Server Configuration for Contract Management 14.0 document.

— —

Preferences/Include URL in MailDetermines whether to include the URL in mail messages.

yes yesno

Preferences/Install PathThe Contract Management install directory path.

— —

Preferences/Print Debug LevelIndicates the amount of detail printed to the Contract Management log. Smaller numbers indicated less detail.

— —

Preferences/Alerts Refresh IntervalHow often to refresh alerts. This number is listed in milliseconds.

— —

Preferences/Widgets Refresh IntervalHow often the Control Center items should check the server for updates. This number is listed in milliseconds.

— —

Preferences/SMTP ServerName of the SMTP mail server for outgoing mail.

— —

Preferences/Template PathTemporary folder used by Contract Management templates.

— —

User Productivity Kit

User Productivity Kit/Enable User Productivity KitUsed to enable or disable tutorials in the content.

— truefalse

User Productivity Kit/User Productivity Kit URLPoints to the UPK content.

— —

Web Server

Web Server/CharacterEncodingType of character encoding used by the configured Web Server.

UTF-8 See “Modifying Web Server Settings” on page 87.




Web Server

Web Server/CompressionEnabled true — Indicates that file compression is enabled on the host where the Web server resides.

false — Indicates that file compression is not enabled on the host where the Web server resides.

See “Modifying Web Server Settings” on page 87.

Web Server/ExpeditionWebServiceNameName of the service for which the Web server is configured.

— See “Modifying Web Server Settings” on page 87.

Web Server/WebApplicationNameName of the application for which the web server is configured.


Web Server/WebProtocolProtocol of the Web server.


Web Server/WebPortPort configured for use by the Web server.

80 See “Modifying Web Server Settings” on page 87.

Web Server/WebServerNameThe Web server host name.

— —

Web Server/sessiontimeoutHow long a user can be inactive before being disconnected from Contract Management. This number is listed in milliseconds.


Web Server/xmlsessiontimeoutHow long a user can be inactive before being disconnected from functionality which involves xml. This number is listed in milliseconds.



101

Use this chapter to configure Contract

Management to communicate with P6

EPPM.

In this chapter

Prerequisites

Configuring Schedule Database Information for Microsoft SQL Server

Configuring Your Simple Mail Transfer Protocol Server

Configuring the Port Number for Microsoft SQL Server

Locating the Database Port Number when Using Microsoft SQL Server

Connecting Contract Management with P6 EPPM

102 Connecting Contract Management with P6 EPPM

PrerequisitesSee “Preparing for Installation” on page 17.

You must first install Contract Management, making certain that you complete all prerequisite tasks.


Connecting Contract Management with P6 EPPM 103

Configuring Schedule Database Information for Microsoft SQL Server

If you will be connecting to a Schedule Database, follow the instructions below.

Enter Information about the Schedule Database

1 Launch the Administration Config utility. See “Run the Adminis-tration Config utility” on page 67.

2 Click the Tree View tab.

3 On the Tree View tab, expand the tree to the Project Management folder by selecting Contract Management Settings > Database Settings > Project Management.

4 In the Project Management folder, enter database server infor-mation in each field. See “Configuration Settings for Contract Management” on page 88.

5 Click Save Changes when you are finished.


104 Connecting Contract Management with P6 EPPM

Configuring Your Simple Mail Transfer Protocol ServerEnter Information about the SMTP Server



3 On the Tree View tab, expand the tree to the Preferences folder by selecting Contract Management Settings > Preferences.

4 In the Preferences folder, triple-click the SMTP Server field and enter the name of your SMTP server. Click Next.



Connecting Contract Management with P6 EPPM 105

Configuring the Port Number for Microsoft SQL ServerEnter the Port Number Contract Management Will Use to Connect with Microsoft SQL Server



3 On the Tree View tab, expand the tree to the Database Settings folder by selecting Contract Management Settings > Database Settings.

4 In the Database Settings folder, triple-click the Port Number field and enter the port number. The default is 1433. Click Next.

If you installed Microsoft SQL Server Express and need help finding your port number, see “Locating the Database Port Number when Using Microsoft SQL Server” on page 106.



Locating the Database Port Number when Using Microsoft SQL Server

Port number 1433 is the default port number for MSSQL. If port number 1433 is already in use at the time of installation, Microsoft SQL Server automatically assigns a port number that can be viewed with other related information in the Microsoft SQL Server Configuration Manager.

Locate the MSSQL Port Number in Microsoft SQL Server Configuration Manager

1 From the Microsoft Windows task bar, select Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager.

2 In the SQL Server Configuration Manager (Local) tree, expand SQL Server 2005 Network Configuration.

3 Double-click Protocols for PRIMAVERA.

4 In the Protocol Name column, locate TCP/IP. Ensure that its Status is Enabled.

If the status of the TCP/IP attribute is Disabled, restart Microsoft SQL Server to generate a new IP address and port number for the Microsoft SQL database.

5 Double-click TCP/IP.

6 In the TCP/IP Properties dialog box, select the IP Address tab.

7 Scroll to the IPAll section. The TCP Dynamic Ports field displays the port number of your Microsoft SQL database for Contract Management.

8 Returning to the Contract Management installation wizard, enter the port number in the Enter Port Number to Use for Contract Management dialog box, and click Next.

107

This chapter describes how to set up the

Contract Management environment.In this chapter

Starting the Administration Application

Adding Contract Management Users

Viewing Reports and Forms in Contract Management Using BI Publisher

Importing Users from LDAP

Configuring Oracle Access Manager for Contract Management

Setting Up the Contract Management Environment

108 Setting Up the Contract Management Environment

Starting the Administration Application1 From the Windows desktop open Internet Explorer.

2 Enter the Web address for the Contract Management Administration Application as follows:

http://webservername:7001/exponline/adminlogon.jsp

Where webservername is the computer name of your Contract Management Web server.

When running Contract Management for the first time, you must have administrator rights to the machine in order to install the JRE.

3 Type your admin user name and password in the Administration login dialog box (the default user name and password are both expadmin), and click Log In.


Setting Up the Contract Management Environment 109

Adding Contract Management UsersUsers need a Contract Management user account in order to access the database. You should review your existing Contract Management user accounts to ensure they are properly configured, and add new users as necessary.

See “Starting the Administration Application” on page 108

1 Logon to the Contract Management Administration Application.

2 Click User Accounts.

3 In the User Accounts window, click Create New User to open the Create New User dialog box.

4 Type a user name for the user, and choose whether to create a completely new user, or to base the user on an existing one (which requires less data entry).

User names are not case sensitive. New user names cannot have the same spelling as any other user name regardless of how the names are capitalized.

5 Click OK to open the User Account window.

6 Fill in the information for the user account. See the online help for information about each field.

When importing users from LDAP, the LDAP user login name cannot contain any special characters (for example, ! @ $ % & * () ^ # +) or be longer than 30 characters. Contract Management will only support login names that do not contain special characters, and that are less than or equal to 30 characters in length. See “Importing Users from LDAP” on page 116.



Viewing Reports and Forms in Contract Management Using BI Publisher

For Contract Management 14.0, Business Intelligence Publisher Edition and later, reports, forms, and letter templates can be viewed in Contract Management but are created and stored in Oracle Business Intelligence Publisher. To view reports, forms, and letter templates in Contract Management, you will need to perform the following tasks:

■ Upload Sample Folders from the Contract Management Media Pack to the BI Publisher Server

■ Configure BI Publisher Settings in the Contract Management Administration Config Utility

■ Import Reports and Forms into Contract Management

It is assumed that you know how to use Oracle BI Publisher. For complete information on using this software, see the Oracle BI Publisher documentation.BI Publisher saves letters in Rich Text Format (RTF). Letters are no longer saved in native Microsoft Word format.

When using Real Application Clusters (RAC) with Contract Management, only one database will be used for the Administration Config utility. Contract Management reports and forms use that same database instance. If the node on which that instance resides fails, the Contract Management reports and forms will not work as there is no fail-over to another node. You can either bring the failed node back up, or reconfigure the database instance settings to use another node. See the Contract Management Installation and Configuration Guide (for Oracle or Microsoft SQL Server) for information on configuring database instance settings.

Before you can view reports and forms in Contract Management, ensure the following prerequisites are met:

■ Contract Management is installed and running.

■ Oracle BI Publisher is installed and running. BI Publisher should be configured after installing Contract Management. Consult the Oracle BI Publisher documentation for complete information on installing and configuring this software. The BI Publisher Quick Install Guide is available on the Oracle Technology Network at:



http://download.oracle.com/docs/cd/E21764_01/bi.1111/e16518/toc.htm

To integrate with Contract Management, the Simple Install type is satisfactory. The only required Business Intelligence installation component is BI Publisher.

When running the Repository Creation utility, you only need to select the Business Intelligence Platform component in the Oracle Business Intelligence section. If you select the Oracle Business Intelligence component automatically selects any other dependent components.

Upload Sample Folders from the Contract Management Media Pack to the BI Publisher Server

The Contract Management 14.0, Business Intelligence Publisher Edition media pack contains zip files of sample reports and forms, a sample letter template, and a sample data model. The media pack also contains sample US English and UK English files. The samples are in the media pack in Contract Management v14.0\common\Contract_Management_14_Tools\Reports and Forms. Unzip these files directly on the BI Publisher server, into a folder within Shared Folder. Be sure to maintain the folder hierarchy which is there by default in the media pack. If you change the hierarchy, map each report and form to its appropriate data model or you will not be able to view reports and forms in BI Publisher or Contract Management.

Do not move the data model.

The data model contains all the variables that can be populated by Contract Management. You can import this data model and use it as a model for any templates you create in BI Publisher. You can add custom fields to the letters module just as you can to any module in Contract Management. If you add custom fields, you must update your data models by hand in BI Publisher to add the new fields. The field names are not case sensitive. Declare the names as Text or String (not Date or another special type)—the data is automatically formatted by Contract Management prior to being sent to BI Publisher, so this type of conversion is neither necessary nor typically successful.

1 On the BI Publisher server, create a folder within Shared Folder that has the same name as the zip file you plan to extract.



Default Shared Folder: <BI Publisher WebLogic Domain Home>\config\bipublisher\repository\Reports

For example: <Shared Folder>\US Sql or <Shared Folder>\UK Sql

The folder where you extract the zip file contents must have the same name as the zip file, or the sample templates, reports, and forms contained in the zip file will not function properly. Use the same case as the zip file name as the paths are case sensitive.

2 Extract the US Sql or UK Sql zip file into the folder you created in Shared Folder.

Once the zip file contents are extracted, this folder will contain three subfolders: Reports, Forms, and Letter Templates.

For example: <Shared Folder>\US Sql\Reports

If you have any custom reports, you can also unzip these into Shared Folder.

3 When the unzip is complete, ensure that the CmLettersDataModel under the templates folder points to a valid datasource. In this case, you can leverage your CM Group Database as a datasource.

For more information on creating a datasouce, please see the BI Publisher documentation at http://download.oracle.com/docs/cd/E21764_01/bi.1111/e13880/T526690.htm.For more information on configuring a data model, please see the BI Publisher documentation at http://download.oracle.com/docs/cd/E21764_01/bi.1111/e18862/T527073T558252.htm.

Configure BI Publisher Settings in the Contract Management Administration Config Utility You must configure settings in the Administration Config Utility to enable BI Publisher to communicate with Contract Management.

1 Open the Contract Management Administration Config Utility.

2 In the Primavera Administrator dialog box, click the Tree View tab and expand Contract Management Settings > BI Publisher.



3 In the BI Publisher folder:

a. In the Username and Password fields, enter the username and password for an existing account on the BI Publisher server with rights to run BI Publisher reports.

For more information, see “Configuration Settings for Contract Management” on page 88.

b. In the WebService URL field, enter a URL that points to the Web Service Definition Language (WSDL) and click Save Changes. This URL determines the Business Intelligence server to which Contract Management connects.

For example: http://host:port/xmlpserver/services/PublicReportService?wsdl

In this example, host is the name of the host on which Web Services runs, and port is the TCP port that the website will use.

If you enter the same host:port here that you enter in the BI Publisher > Server URL field for your database instance in the Primavera P6 Administrator, then Contract Management and P6 can run reports from the same BI Publisher configuration.

4 In the Contract Management Settings folder, expand Database Settings > Database Groups. Then expand the name of your database group instance.

5 In your database group instance:

a. In the Report Location field, enter the location in BI Publisher that contains group reports.

For example (the forward slash is required): /US Sql/Reports

b. In the Letter Template Location field, enter the name of the folder in BI Publisher that contains group letter templates.

For example (the forward slash is required): /US Sql/LetterTemplates

6 Restart the Contract Management WebLogic server.

Import Reports and Forms into Contract Management To view reports and forms in Contract Management, you must import them from BI Publisher into the local Contract Management database. When the import is finished, you should be able to run reports from Contract Management.



When you specify a location in Contract Management, the application validates that this path is available on the BI Publisher server. The application does not validate whether this location has valid reports.BI Publisher does not check letter capitalization. If you provide the correct path with incorrect capitalization, Contract Management cannot fetch the report description for the advanced print popup.You can also use the Server Configuration page described in this task to upload reports and forms from the local Contract Management database to the BI Publisher server. The instructions for this function can be found in the Contract Management online help.

1 Open the Contract Management Administration Application on the same machine that the Web Server is installed on to ensure you have the correct network drive mappings.

2 In the Contract Management Administration Application, click Server Configuration.

3 On the Server Configuration page, click Add in the Project Reports, Forms, and Letter Template Locations section.

4 In the Project Reports, Forms and Letter Template Location dialog box:

a. In the Name field, enter a name to identify this set of reports and forms.

b. In the Report Location field, enter the path to the location on the BI Publisher server where the reports are stored.

This is under the Shared Folder in the Reports folder you created on the BI Publisher server. For example: <Shared Folder> /US Sql/Reports

c. In the Form Path field, enter the path to the location on the BI Publisher server where the forms are stored.

This is under the Shared Folder in the Forms folder you created on the BI Publisher server. For example: <Shared Folder> /US Sql/Forms

d. In the Letter Template Location field, enter the path to the location on the BI Publisher server where the letter templates are stored.



This is under the Shared Folder in the Letter Template folder you created on the BI Publisher server. For example: <Shared Folder> /US Sql/LetterTemplates

e. In the Projects section, click Add to assign the report and form locations to particular projects, or click Add All Projects to assign the report and form locations to all projects.

f. Click Save & Close when finished.

5 On the Server Configuration page, click the edit icon beside a group name in the Group Reports and Letter Template Location section to import multi-project reports or letter templates.

6 In the Group Reports and Letter Template Location dialog box:

See “Starting the Administration Application” on page 108.

a. In the Report Location field, enter the path to the location on the BI Publisher server where reports are stored.

This is under the Shared Folder in the Reports folder you created on the BI Publisher server. For example: <Shared Folder>/US Sql/Reports

b. (Optional) In the Letter Template Location field, enter the path to the location on the BI Publisher server where letter templates are stored if you also want to link to letter templates.

This is under the Shared Folder in the Letter Templates folder you created on the BI Publisher server. Fore example: <Shared Folder>/US Sql/LetterTemplates

c. Click OK when finished.

7 On the Server Configuration page, click Import Reports & Forms. This could take several minutes to complete. Click Save when you are finished. You should now be able to run reports from Contract Management.

To avoid a transaction timeout error when importing reports from BI Publisher, you can increase the timeout seconds in the WebLogic Console. Open the WebLogic Console. In the Domain Structure pane, expand Services and click JTA. On the JTA tab, change the Timeout Seconds field to at least 400 seconds and click Save. If you have a very high number of reports, set the timeout to 500 seconds.



Importing Users from LDAPThe LDAP server provides the central repository for user credentials. This is useful when users exchange data with multiple applications. LDAP provides one common user authentication source.

When importing users from LDAP, it is important to do the following:

■ Set up a Contract Management administrative user with the same login name that exists on the LDAP server.

■ Configure the Contract Management user import tool, and import users.

■ In the Contract Management Administration Application, complete the LDAP information for each user.

If you do not complete the steps in the following section before importing users from LDAP, you will not be able to logon to Contract Management again.

First, set up a Contract Management user for LDAP

See “Starting the Administration Application” on page 108.

1 Logon to the Contract Management Administration Application.

2 Click Administrator IDs.

3 Click Add Administrator.

4 Enter the Administrator ID. This is the same user login name that exists on the LDAP server.

The user login name cannot contain any special characters (for example, ! @ $ % & * () ^ # +) or be longer than 30 characters. Contract Management will only support login names that do not contain special characters, and that are less than or equal to 30 characters in length.

5 Enter the Password, and choose a Language from the drop-down list.

6 Click Save.

7 Close the Contract Management Administration Application.

Configure the Contract Management user import tool



1 Go to the home directory where Contract Management is installed, choose Contract Management, choose Utility, choose CMAdmin-Config, and double-click LDAPCfgWiz.cmd (LDAPCfgWiz.sh in a non-Windows system) to run the LDAP configuration wizard.

2 Enter the Contract Management user name and password, and click OK. This is the user name and password for the Contract Management ADMIN database, and was set during Contract Management installation.

3 In the LDAP Configuration dialog, enter the information that LDAP needs to access the LDAP server:

a) Enter the User name.

b) Enter the Password.

c) Enter the Host address for the LDAP server.

d) Enter the Host port number of the LDAP server.

e) Enter the Base directory node. The Base directory node is the base directory where the LDAP user import tool starts looking for users.

f) Click Next when finished.

4 In the Map database fields with LDAP attributes dialog:

a) In the LDAP attribute column of the table, enter the LDAP attributes that correspond to the Contract Management database field names listed in the Database field name column of the table.

b) You must enter an LDAP attribute for the LOGIN_NAME* field name. This is a required field.

c) The LDAP attributes you enter are the attributes that exist on the LDAP server. You do not have to enter an LDAP attribute for all fields, only for required fields.

d) Click Next when finished.

5 In the Select LDAP users to be imported into Contract Management dialog:

a) Use the Search field to find the users you want to add to the Selected users table. You can search on an LDAP attribute, and can use an asterisk (*) as a search option (for example: uid=*).

b) Highlight the user you want to add, and click the right arrow button to add the user to the Selected Users table.



c) If you want to change the default group of projects available to the user, scroll to the right in the Selected Users table, find the Default Group column, and change the default.

c) Repeat steps 5a through 5c as necessary until you have added all users to the table, and then click Import when finished.

6 When the “Import Successful” message displays, click OK.

7 Click Close. When the “Configuration of the Contract Management LDAP completed successfully.” message displays, click OK.

Finish Configuring the LDAP users in Contract Management After the import completes, do the following:

1 Deploy the Contract Management service.

2 Logon to the Contract Management Administration Application with the User ID you created in step 4 of “First, set up a Contract Management user for LDAP” on page 116.

3 Click User Accounts, and select a user that you imported from LDAP.

4 Make sure that the First Name and Last Name fields contain the name of the user imported from LDAP.

5 In the Company field, enter the abbreviation of the user’s company.

6 In the Initials field, enter the initials of the user imported from LDAP.

7 Scroll to the Template section, and click Add Template.

8 In the Select Template dialog, click select next the appropriate template to apply for the user, and click Save.

9 Click either Add Project, and select the project to which the user will have access, or click Add All Projects to give the user access to all projects.

10 Click Save.

11 Repeat steps 3 through 10 for each user that you imported.



Configuring Oracle Access Manager for Contract Management

If you are using Oracle Access Manager (OAM) for single sign-on, you must configure it to work with Contract Management. Unless this is done, Contract Management “Applets” will not load correctly when logged into Contract Management configured to OAM 11.1.1.5.0.

Change the challenge parameter value in the Authentication Schemes->LDAPScheme of OAM 11.1.1.5.0 to be the following:

ssoCookie=disablehttponly




121

Use this chapter to install and configure the

Oracle Primavera SharePoint Connector to

enable Microsoft SharePoint to integrate

with Contract Management. This enables

both Contract Management and P6 EPPM to

use a single signon to communicate with the

Microsoft SharePoint Repository.

In this chapter

Prerequisites

Installing the Oracle Primavera SharePoint Connector

Configure the Oracle Primavera SharePoint Connector URL in Administration Config Utility

Installing and Configuring the Oracle Primavera SharePoint Connector

122 Installing and Configuring the Oracle Primavera SharePoint Connector

PrerequisitesSee “Preparing for Installation” on page 17.

You must first install Contract Management, making certain that you first complete all prerequisite tasks.

Contract Management 1Installation and Configuration Guide for Microsoft SQL Server

Installing and Configuring the Oracle Primavera SharePoint Connector 123

Installing the Oracle Primavera SharePoint ConnectorCreate the Web site In Internet Information Services (IIS) manager, do the following:

1 Create a new Web site.

2 Right-click the name of the Web site you created, and do the following:

a) Go to Properties, and click the Security tab.

b) Click the Edit button in the Authentication section.

c) Clear the Integrated Windows Authentication option, and click OK.

Install the software The SharePoint Connector must be installed on the same machine on which SharePoint is located.

1 From the download or physical media, open Contract Management v14.0\common\Contract_Management_14_Tools\Oracle Primavera SharePoint Connector and run setup.exe.

2 When the Select Installation Address dialog displays:

a) The name of the site that you enter must be the same as the name of the Web site you created earlier in this section.

b) For the Virtual directory and Application Pool, either accept the default values or use the fields on the dialog to change them.

3 Click Next.

4 Finish installing the Oracle Primavera SharePoint Connector.

Test the Web Services function to ensure it installed correctly

To test the Web Services function, open the URL for the Web Services. The URL should be in the following format:

http://<HOST>:<PORT>/<VIRTUAL_DIR>/WS_FPRPC.asmx

where

• <HOST> is the name of the host on which Web Service runs.

• <PORT> is the TCP port that the Web site will use. You entered this when you created the Web site.


124 Installing and Configuring the Oracle Primavera SharePoint Connector

• <VIRTUAL_DIR> is the name of the Virtual directory that you created.

• WS_FPRPC.asmx is the name of the Web Service.

This should display a list of the available functions.

Contract Management 1Installation and Configuration Guide for Microsoft SQL Server

Installing and Configuring the Oracle Primavera SharePoint Connector 125

Configure the Oracle Primavera SharePoint Connector URL in Administration Config UtilitySee “Run the Administration Config utility” on page 67.

1 Run the Administration Config utility.

2 Expand the Content Repository folder, and then expand the Microsoft SharePoint folder.

3 Triple-click Authentication Mode, and choose Multiple User or Single User. Multiple User is typically used if you are using an active directory.

4 Triple-click Document Library URL, and enter the URL for the SharePoint document repository.

5 Triple-click Web Service URL, and enter the URL for the Oracle Primavera SharePoint Connector that you previously installed.



127

This chapter describes how to configure the

Oracle Universal Content Management

repository for use with Contract

Management. Having a content repository

integrated with Contract Management can

turn cluttered, unstructured content into

organized assets by making it easier to

catalog, access, search, and reuse

documentation.

In this chapter

Configuring UCM to Work with Contract Management

Connecting Oracle Universal Content Management to Contract Management

128 Connecting Oracle Universal Content Management to Contract Management

Configuring UCM to Work with Contract ManagementBefore you configure your content repository, decide which authentication mode to use, and then configure the content repository with Contract Management. For more information on authentication modes, see “Modifying Content Repository Settings” on page 75.

Refer to the documentation included with the content repository application for detailed instructions on how to complete the guidelines in this section.

These instructions only contain information on configuring Oracle Universal Content Management (UCM) to work with Contract Management. They do not include information on installing UCM. For UCM's installation instructions, see the documentation included with Oracle UCM.

Except where noted, the guidelines below are recommendations. Depending on your organization, you can choose to use existing configurations or your own naming conventions. Refer to the documentation included with Oracle Universal Content Management for detailed instructions on how to complete the guidelines in this section.

Configure Oracle UCM

1 (required) Establish a Trusted Connection to the Contract Management database by adding the Contract Management machine name or IP address as a trusted server in the UCM server’s configuration file.

a. For UCM 10g, go to UCM_Home\config\.

For UCM 11g, go to UCM_Home\ucm\cs\config\.

b. Edit the config.cfg file.

c. Find the SocketHostAddressSecurityFilter line and add the Contract Management machine name or IP address to the end of the line.

2 (required) Create a Contract Management documents home folder on the UCM server by adding a unique path to Contribution Folders.

Example: \\Contribution Folders\Production\Oracle Primavera\


Connecting Oracle Universal Content Management to Contract Management 129

3 Create a Contract Management Security Group in UCM and grant the appropriate rights for Contract Management users. Security considerations include the following:

• Contract Management user names must match the UCM user names, unless using "Single User" for the Authentication Mode.

"Single User" Authentication Mode will log all Contract Management users into UCM via the administrative user created below and/or as specified in the Database/Instance/Content Repository setting in the Administration Config utility.

• All Contract Management-related UCM user names must have appropriate assignments to UCM Roles and Users. For a quick setup, you can simply create one Contract Management-specific Role to map to, with full privileges (Read, Write, Delete, Admin).

• All Contract Management-related UCM user names must have access to the Contract Management Security Group, either directly or through a role.

4 Create an administrative user in UCM for the Contract Management Security Group. A user account with administrative privileges is required for Contract Management document access, for making changes to Contract Management document organization, and when using "Single User" for Authentication Mode.

When using "Single User" for Authentication Mode, users will have the ability to browse for documents outside of the Contract Management documents home folder, as long as the administrative user has access to all appropriate Security Groups, including the Contract Management Security Group.

5 If you enabled Security Accounts, create a Contract Management Security Account. For example, depending on your organization, you might need to set up a Security Account for performance and storage reasons. Security considerations, similar to those made for the Security Group above, include the following:

• Contract Management user names must match the UCM user names, unless using "Single User" for the Authentication Mode.


• All Contract Management-related UCM user names must have appropriate assignments to UCM Roles and Users. For a quick setup, you can simply create one Contract Management-specific Role to map to, with full privileges (Read, Write, Delete, Admin).

• All Contract Management-related UCM user names must have access to the Contract Management Security Account.

6 Create a Document Type for Contract Management documents in UCM.

For example:

• For UCM 10g, enter the Document Type as ADACCT.

• For UCM 11g, enter the Document Type as Document.

These document types are the defaults in their repositories.

7 (required) Create the following metadata text fields, exactly as specified (including case), in UCM for Contract Management:

• CmGroupName

• CmProjectName

• CmModuleName

• CmObjectType

• CmObjectId

• CmisAttachment

Using "Cm" as a prefix is optional. You can use any prefix. If you don't use a prefix, ensure that none of the Contract Management metadata fields conflict with existing metadata fields.

8 (required) Configure the appropriate settings for the Administration Config utility. See “Configuration Settings for Contract Management” on page 88.

131

AApplication Server host components 8

BBI Publisher Settings

Modifying in Tree View 73

CCreating databases

initial steps 21Custom portlets

password encryption 88

DDatabases

creating, initial steps for 21Documentation 11

HHelp, online 11

IInstalling Contract Management

prerequisites for 18

MMicrosoft SQL Express Server installation

initial steps for 33

OOnline, help 11Operating systems supported 8Overview of Contract Management 8

PP6 Web Access

adding database instances 68configuration settings 88configure

custom portlets 88Passwords

encryptingfor custom portlets 88

Prerequisitesfor installing Contract Management 18

Primaverastarting 103, 104, 105, 123, 125

UUpgrade

important information 9Upgrade 10.0 version databases

beginning the upgrade 24Upgrade from Contract Management 11.0

for Microsoft SQL Server Web serveroverview of 37

User’s Guide 11

WWeb Server components 8WebLogic

Configure data source for Microsoft SQL Server 49

data sosurce setup 51prerequisites for 50

Index

Documents

Install MSSQL