CM Install Guide

® ®
Oracle Primavera
Contract Management 13.0 Installation and
Configuration Guide for Microsoft® SQL Server
Copyright © 1996, 2009, Oracle and/or its affiliates. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are
provided under a license agreement containing restrictions on use and disclosure and are also protected by
copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or
decompilation of the Programs, except to the extent required to obtain interoperability with other independently
created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the
documentation, please report them to us in writing. This document is not warranted to be error-free. Except as
may be expressly permitted in your license agreement for these Programs, no part of these Programs may be
reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on
behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data
delivered to U.S. Government customers are "commercial computer software" or "commercial technical data"
pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As
such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and
technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement,
and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer
Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently
dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redun-
dancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes,
and we disclaim liability for any damages caused by such use of the Programs.
Oracle and Primavera are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be
trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties.
Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all
risks associated with the use of such content. If you choose to purchase any products or services from a third
party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of
third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including
delivery of products or services and warranty obligations related to purchased products or services. Oracle is not
responsible for any loss or damage of any sort that you may incur from dealing with any third party.
3
Table of Contents
Preface...................................................................................................5
Contract Management Overview .......................................................................... 6
Contract Management Documentation ................................................................. 8
About this Manual............................................................................................... 10
Contacting Customer Support............................................................................. 11
Preparing for Installation..................................................................13
Overview ............................................................................................................. 14
Creating New Databases ..................................................................................... 16
Upgrading Your Databases ................................................................................. 19
Migrating Databases ........................................................................................... 20
Configuring a JBoss Application Server............................................................. 21
Configuring a WebLogic Application Server ..................................................... 23
Configuring WebLogic for Microsoft SQL Server Databases .......27
Prerequisites ........................................................................................................ 28
Configuring the Data Source............................................................................... 29
Deploying Contract Management ....................................................................... 32
Configuring the Contract Management Port Specification................................. 33
Installing Contract Management on a Web Server ........................35
Prerequisites ........................................................................................................ 36
Installing Contract Management......................................................................... 37
Locating the Database Port Number when Using Microsoft SQL Server 
Express................................................................................................................ 43
Upgrading to Contract Management from a Previous Version .....45
Prerequisites ........................................................................................................ 46
Upgrading an Existing Stand-Alone Installation ................................................ 47
Upgrading an Existing Web Server Installation.................................................. 51
Configuring Contract Management for a WebLogic Cluster ........57
Prerequisites ........................................................................................................ 58
Configuring the Clustered Environment ............................................................. 59
Considerations for Using Contract Management in a Clustered Environment... 61
4 Table of Contents
Using XML API in a Clustered Environment..................................................... 62

Enabling nodemanager for Contract Management in a Clustered Environment 63
Viewing and Modifying Contract Management Settings ...............65
Starting the Primavera Administrator ................................................................. 66
Modifying Values of Configuration Settings ...................................................... 70
Modifying Application Server Settings .............................................................. 71
Modifying Authentication Settings ..................................................................... 73
Modifying Web Single Sign-On Settings............................................................ 75
Modifying Content Repository Settings ............................................................. 76
Modifying Database Settings .............................................................................. 79
Modifying Project Management Schedule Database Settings ............................ 84
Setting Preferences.............................................................................................. 86
Modifying Web Server Settings .......................................................................... 87
Configuration Settings for Contract Management .............................................. 88
Installing InfoMaker 10.5..................................................................99
Installing InfoMaker.......................................................................................... 100
Setting up the Database Connection to InfoMaker ........................................... 101
Installing and Configuring the Oracle Primavera SharePoint 
Connector .........................................................................................103
Prerequisites ...................................................................................................... 104
Installing the Oracle Primavera SharePoint Connector..................................... 105
Configure the Oracle Primavera SharePoint Connector URL in Primavera 
Administrator .................................................................................................... 107
Setting Up the Contract Management Environment....................109
Starting the Administration Application ........................................................... 110
Adding Contract Management Users ................................................................ 111
Setting Up Reports and Forms .......................................................................... 112
Displaying Report Titles Containing International Characters ......................... 114
Running Contract Management as a User Account .......................................... 115
Importing Users from LDAP............................................................................. 117
Reconfiguring the Contract Management Web Server ..................................... 120
Encrypting Passwords when Using a JBoss Application Server....................... 121
Configuring the Oracle Content Repository for Use with Contract
Management .....................................................................................123
Adding Users..................................................................................................... 124
Adding Metadata Properties.............................................................................. 125
Index..................................................................................................127
Contract Management 13.0 Installation and Configuration Guide for Microsoft SQL
5
Preface
Contract Management is contract-control
In this chapter software designed to help you manage your
projects more easily. From submittals to
Contract Management Overview
change orders, all the facts about contracts
Contract Management
Documentation and documents related to your project are at
About this Manual your fingertips.
Contacting Customer Support
This manual describes how to install and
configure Contract Management.
6 Preface
Contract Management Overview

Contract 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 an 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
■ Internet access
■ Firewall configured to allow only HTTP requests to the port and
TCP/IP address of the Web Server.
■ Microsoft Office, including Microsoft Word, installed on the
Contract Management Web Server and Application Server before
installing Contract Management software, to ensure the proper
functioning of the Letters module.
■ Microsoft SQL Server, installed prior to the Contract Management
installation.
The Contract Management Web Server validates Contract Management
Web users, enforces Contract Management's business rules, and
communicates with the Contract Management database server.
Preface 7
Required Folders The Contract Management Web Server requires

access to a number of folders on your LAN that contain your Contract
Management reports, forms, and attachments.
Contract Management Web Server
\Program Files\Oracle\Contract Server components

Management
Reports and Forms default folders
\Program Files\Oracle\Contract Contract Management's report

Management\Reports files
\Program Files\Oracle\Contract Contract Management's form

Management\Forms files
\Program Files\Oracle\Contract Image files used by reports and

Management\ forms.
Supported Operating Systems for Contract Management

13.0
The supported operating system information is listed in the

TestedConfigurations.htm document that is available on the physical
media or from the download location
Upgrade Information
This manual covers upgrades from Expedition Professional version 10.0

to Contract Management 13.0. For assistance in upgrading previous
versions of Expedition Professional to Contract Management 13.0,
contact Contacting Customer Support.
Upgrade existing Microsoft SQL databases before installing Contract

Management.
8 Preface
Contract Management Documentation

Contract Management documentation consists of the following:
■ Contract Management 13.0 Installation and Configuration Guide
for Oracle explains how to install and configure Contract
Management with Oracle 10.2 and 11.0 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 13.0 Installation and Configuration Guide
for Microsoft SQL Server explains how to install and configure
Contract Management with Microsoft SQL Server (2008 and 2005
Service Pack 2) and Oracle 10.2 and 11.0 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 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
functions, 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 shows 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.
Preface 9
■ Online Documentation can be accessed from the Contract

Management physical media or download location, in the folder,
\documentation. In addition to the Contract Management User’s
Guide and Installation Guide, the following documentation is
available online:
• The InfoMaker Getting Started Online Manual helps you use

InfoMaker, the report writer included with the Contract
Management software.
• Technical Bulletins provide detailed, technical documents
generated by Contacting Customer Support to answer questions
asked by users.
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.
10 Preface
About this Manual

This manual guides you through the installation of Contract
Management 13.0, 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 Describes tasks required to install Contract Management 13.0 for the
a Web Server first time.
Upgrading to Contract Management Describes tasks required to upgrade your existing installation to
from a Previous Version Contract Management 13.0.
Viewing and Modifying Contract Explains how to run the Primavera Administrator utility to modify your
Management Settings current Contract Management database and configuration settings.
Configuring WebLogic for Microsoft Explains how to install and configure the WebLogic application server
SQL Server Databases for the Microsoft SQL Server database used with Contract Management.
Installing InfoMaker 10.5 Explains how to install InfoMaker 10.5 for use with Contract
Management reports and forms.
Setting Up the Contract Explains how to add users, set up attachments, reports, and forms,
Management Environment display report titles with international characters, run Contract
Management as a user account, add new databases to the Contract
Management Web server, and reconfigure the Contract Management
Web server.
Preface 11
Contacting Customer Support

For instructions on how to submit a service request for technical support
for your products, go to:
http://www.oracle.com/primavera/support.html
This page provides the latest information for contacting support and the
support renewals process.
Contract Management databases contain calculations

called stored procedures. Although a Contract Management
database administrator has the ability to modify these
procedures, changing them is not recommended. Modifying
these procedures voids your Primavera Customer Support
agreement.
13
Preparing for Installation

This chapter describes how to complete
In this chapter required tasks before installing the current
version of Contract Management.
Overview
Creating New Databases Prior to installing the latest version of
Upgrading Your Databases Contract Management, you are required to
Migrating Databases create a new Microsoft SQL database to use
Configuring a JBoss Application with a first-time installation, upgrade
Server
existing databases, configure your
Configuring a WebLogic
Application Server application server, and install the latest J2SE.
14 Preparing for Installation
Overview
Before starting the Contract Management 13.0 installation, complete the
following tasks:
For a New Installation of Contract Management 13.0
If your Contract Management 13.0 installation is a completely new

installation, with no previous versions of the software installed
previously:
1 Create your Microsoft SQL database for a new Contract

Management installation.
See “Creating New Databases” on page 16 for information on how
to configure your Microsoft SQL database.
2 Install the J2SE development kit from http://www.java.sun.com.
This step is optional but recommended. The installation

process installs the J2SE development kit if you opt not to
install it in advance.
3 Configure your JBoss or WebLogic application server. See

“Configuring a JBoss Application Server” on page 21.
4 By this step, you have completed all installation pre-requisites, and
you can install Contract Management. For information, see
“Installing Contract Management” on page 37.
Preparing for Installation 15
For an Upgrade from a Previous Software Installation
For information about upgrading from Expedition 9.0 or a

previous version, contact Contacting Customer Support.

For information about migrating Oracle or Microsoft SQL
Server databases, contact Oracle Primavera Support.
1 Upgrade existing GROUP and ADMIN databases. See “Upgrading

Your Databases” on page 19.
2 Install the J2SE development kit from http://www.java.sun.com.
This step is optional. The installation process installs the

J2SE development kit if you opt not to install it in advance.
3 Configure your JBoss or WebLogic application server. See

“Configuring a JBoss Application Server” on page 21, or
“Configuring a WebLogic Application Server” on page 23.
Configuring the application server is required for all

installations (new or upgrade).
4 By this step, you have completed all upgrade prerequisites, and you
can install Contract Management. For information, see “Upgrading
to Contract Management from a Previous Version” on page 45.
Creating New Databases

For a new installation of Contract Management 13.0 used with a
Microsoft SQL database, you must create the database before installing
the software application.
When creating Microsoft SQL Server databases, the

databases are created in the Microsoft SQL server default
data file location. This cannot be changed. It is important to
ensure that the drive on which the databases will reside has
sufficient space to accommodate them.
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.
Prerequisites Before creating the databases:
1 You must have the Microsoft SQL Server Client installed.

2 If you will use a named instance, you must create that instance
before continuing with the following procedures.
Open the Database Setup Wizard
1 From your Contract Management physical media or download

location, run setup.exe.
The Considerations.htm file and the Welcome to Primavera
Contract Management dialog box are displayed.
2 Read or close the Considerations.htm file.
3 In the Welcome to Primavera Contract Management dialog box,
click Configure Primavera Contract Management Databases.
4 In the Welcome to Primavera Contract Management dialog box,

click Database Configuration Utility to launch the Database
Wizard.
Create a New Database
1 In the Install or Upgrade Primavera Contract Management

applications dialog, click the Install Database option, click
Microsoft SQL Server/SQL Express as the Server type, and click
the Next button.
2 In the Select application database dialog, select the type of database
to create: Group Database or Administration Database, and click
the Next button.
3 In the Connection Information dialog:
a) Enter the DBA user name. This is the name of the database
administrator.
b) Enter the DBA password. This is the password of the database
administrator.
c) Enter the Database host address. This is the database host
machine where Microsoft SQL Server runs. This can be the host
name or IP address.
d) Enter the Database host port. The default is 1433.
f) Click the Next button.
4 In the Configure Microsoft SQL Server/SQL Express Database
dialog, enter the following if you are not choosing the defaults:
a) Enter the Database name you are creating.
b) Enter the Data file path. This is where the path to where the
database server stores data. It is used primarily for export.
c) Enter the Log file path.
d) Select the Database code page from the drop-down list. This is
the language for the database.
e) Click the Next button.
5 In the Configurations Options dialog:
a) Mark the Load sample data checkbox to include sample data
when the database is created, or leave it blank to create the
database without sample data.
b) If the database will be in a multi-byte language (Chinese or

Japanese), mark the Use unicode checkbox.
c) Click the Install button
6 In the Finish dialog box, do one of the following:
a) Click Next return to the Install or Upgrade Primavera Contract
Management applications dialog to create another database.
Repeat steps 1 through 6 to create another database.
b) Click Finish if you are finished creating databases.
Upgrading Your Databases

Use the procedures in this section to upgrade your existing Microsoft
SQL Server GROUP and ADMIN databases to ensure that they will
work properly following installation. This procedure also applies when
installing a Service Pack.
Before upgrading the database in your production

environment:
- Back up your databases, reports, and forms. 
- Complete the upgrade in a test environment.
Upgrade an Existing Contract Management Database If you

have not previously started the database wizard, see “Open the Database
Setup Wizard” on page 16.
1 In the Install or Upgrade Primavera Contract Management

applications dialog, click the Upgrade Database option, click
Microsoft SQL Server/SQL Express as the Server type, and click
the Next button.
2 In the Connection Information dialog box:
a) Enter the Administrative user name. This is the user name of the
database administrator.
b) Enter the Administrative password. This is the password of the
database administrator.
c) Enter the Database host address. This is the database host
machine where the Microsoft SQL server runs.
d) Enter 1433 as the Database host port.
e) Enter the Database name.
f) Click the Next button.
3 In the Ready to Begin Upgrading Data dialog, click Yes, upgrade
my database, and click the Upgrade button.
4 When the Finish dialog displays, do one of the following:
a) Click the Next button to return to the Install or Upgrade
Primavera Contract Management applications dialog to upgrade
another database. Repeat steps 1 through 4 of this procedure to
upgrade the database.
b) Click the Finish button when finished upgrading the databases.
Migrating Databases
Contract Management 12.1 and previous versions supported Oracle,
Microsoft SQL, and Sybase Adaptive Server Anywhere (ASA)
databases. Contract Management 13.0 no longer supports the Sybase
ASA database.
Customers must migrate their Sybase databases to a supported platform

before upgrading to Contract Management 13.0 or later. For information
on migrating Sybase databases, see the Migration from Sybase
Installation Instructions.pdf document available from your Contract
Management physical media or download location.
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.
For information on For information about migrating Admin and Group databases from
contacting Oracle
Primavera Customer
Oracle to Microsoft SQL, or from Microsoft SQL to Oracle, for
Support, see “Contacting Contract Management, contact Oracle Primavera Support.
Customer Support” on
page 11.
Configuring a JBoss Application Server

If you will use a WebLogic JBoss 5.0.1.GA must be installed if you will use JBoss as your
application server, instead
application server. Follow the directions in this section to install and
of a JBoss application
server, see “Configuring a configure JBoss 5.0.1.GA.
WebLogic Application
Server” on page 23.
Download the JBoss zip file To download JBoss 5.0.1 GA,
compiled/packaged for JDK6, do the following from the http://jboss.org
web site:
1 Go to Projects, Servers, and choose Application Servers.

2 Click the Downloads link to display the JBoss Application Servers
window.
3 Find 5.0.1.GA on the JBoss Application Servers window, and click
the Download link.
4 From the list of JBoss 5.0.1.GA downloads, click the jboss-
5.0.1.GA-jdk6.zip link to download the file.
5 Unzip the downloaded JBoss file to the <JBOSS INSTALL
LOCATION> (for example, C:\jboss-5.0.1.GA). The path name
cannot contain any spaces.
Do not download the files into a directory that is in the

existing Contract Management directory path.
Create a Domain Specific to Contract Management
1 Go to <JBOSS INSTALL LOCATION>\server.

2 Choose the folder default.
3 Press Ctrl-C to copy the folder, and then press Ctrl-V. This creates a
folder named Copy of Default.
4 Rename the Copy of Default folder to cm, which is the JBoss
domain specific to Contract Management.
5 Save and close the file.
Edit the run.bat file
1 Go to <JBOSS INSTALL LOCATION>\bin, right-click on run.bat,

and choose edit.
2 Replace the line: 


set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m 

with the following:
set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx1024m 
-XX:PermSize=128m -XX:MaxPermSize=128m
The preceding is case-sensitive, and should be all on the

same line. Because of the format restrictions of this
document, it had to be shown on two lines.

Edit the jbossjta-properties.xml file You must do the following to
edit the jbossjta-properties.xml file. These steps are required.
1 Go to the following location:

<JBOSS INSTALL LOCATION>\server\cm\conf
2 Right-click on jbossjta-properties.xml, and choose edit.

3 Find the following:

<properties depends="arjuna" name="jta">
4 Under that line, add the following:
<property name="com.arjuna.ats.jta.allowMultipleLastResources"
value="true" />
Details about the preceding parameter can be found on the

following web site:
http://www.jboss.org/community/docs/DOC-11443.
Configuring a WebLogic Application Server

Follow the instructions in this section if you will use WebLogic as your
application server.
Prerequisites Complete the following steps:
1 Install WebLogic 10gR3, Enterprise.

2 Install JDK 1.6.0_14.
Create a new domain specific to Contract Management Do
the following to create a new domain specific to Contract Management.
This domain will use JDK1.6.0_14, and will contain the Contract
Management configuration files.
Do not create the domain in a directory that is in the existing

Contract Management directory path.
1 Go to Start, Oracle WebLogic, WebLogic Server (10g3), Tools, and

click ConfigurationWizard 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 In the Configure Administrator Username and Password
window, enter the user name and password information and click
Next.
5 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.
6 In the Customize Environment and Services Settings window,
click Next.
7 In the Create WebLogic Domain window, enter the domain and
location information and click Create.
8 In the Creating Domain window, mark Start Admin Server and
click Done.
9 When prompted, enter the username and password that you entered
in step 4.
Configure the WebLogic Server Do the following to configure the

WebLogic server:
1 On the server where you installed WebLogic, in the

<domain_home>\bin directory, open the startWebLogic.cmd file
in a text editor (such as Notepad).
1 in a text editor (such as Notepad).
2 Insert one of the following statements after 'call
"%DOMAIN_HOME%\bin\setDomainEnv.cmd"' to update the
PATH variable:
a) If you are using Sun JVM, enter the following:
set PATH=%DOMAIN_HOME%\bin;%PATH%
b) If you are using BEA JRockit JVM, enter the following.

set PATH=%DOMAIN_HOME%\bin;%JAVA_HOME%
\jre\bin\jrockit;%PATH%
The preceding is case-sensitive, and should be all on the

same line. Because of the format restrictions of this
document, it is shown on two lines.
3 Update the SAVE_JAVA_OPTIONS variable as follows to support

JDK 1.6.0_14, to update java.library.path:
set SAVE_JAVA_OPTIONS=
-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 
-Djava.library.path="%PATH%" %JAVA_OPTIONS%
4 For WebLogic 10g only, update SAVE_CLASSPATH as follows to

append the jar files required to run reports, and then go to step 6:
set SAVE_CLASSPATH=%DOMAIN_HOME%\lib\mail.jar;
%DOMAIN_HOME%\lib\pbjdbc12105.jar;
%DOMAIN_HOME%\lib\sqljdbc.jar;%CLASSPATH%
5 For WebLogic 11g only, update the SAVE_CLASSPATH as

follows, and then go to step 6:
set SAVE_CLASSPATH=%DOMAIN_HOME%\lib\mail.jar;
%DOMAIN_HOME%\lib\pbjdbc12105.jar;%DOMAIN_HOME
%\lib\sqljdbc.jar;%DOMAIN_HOME%\lib\log4j.jar;
%DOMAIN_HOME%;%CLASSPATH%
6 Save the changes you made to the startWebLogic.cmd file.
7 After configuring the WebLogic application server, continue with

the steps in one of the following sections:
• “Installing Contract Management on a Web Server” on page 35.
• “Upgrading to Contract Management from a Previous Version”
on page 45.
27
Configuring WebLogic for Microsoft

SQL Server Databases
Use this chapter to configure WebLogic
In this chapter when using Contract Management with
Microsoft SQL Server databases.
Prerequisites
Configuring the Data Source
Deploying Contract Management
Configuring the Contract
Management Port Specification
28 Configuring WebLogic for Microsoft SQL Server Databases
Prerequisites
Do 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 23.
2 In the Primavera Administrator utility, set the properties for the
content repository (Oracle, Apache Jackrabbit, or Microsoft
SharePoint). For more information, see “Viewing and Modifying
Contract Management Settings” on page 65
3 Start WebLogic from <domain_home>\startWebLogic.cmd.
4 Login to admin console at url (for example: http://localhost:7001/
console).
5 Click Lock & Edit.
6 Select Data Sources from Services\JDBC.
7 Click New in the Data Sources dialog box.
8 See “Configuring the Data Source” on page 29 to complete the
WebLogic Data Source configuration.
Configuring WebLogic for Microsoft SQL Server Databases 29
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 Project Management Schedule
database as part of your Contract Management system installation.
Complete all the following procedures for each database:
■ Once for each GROUP database. You are required to have at least
one group database, however, you may have previously configured
more than one.
Through the Contract Management installation wizard, you can
create the default databases, CMDEMO and CMPROJ, with sample
data.
■ Once for the ADMIN database, also referred to as EXPADMIN.
■ Once for the Project Management 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's MS SQL Server
Driver (Type 4) Version: 2005.
5 Click Next. The Transaction Options dialog box displays.
Set Transaction Options
1 For the EXPADMIN or PMDB databases, and for the GROUP

databases (CMDEMO or CMPROJ), unmark the Supports Global
Transactions checkbox.
2 Click Next. The Connection Properties dialog box displays.
Set Connection Properties
1 Set the Database Name field to one of the following:

• Database name for the Contract Manager database for the
ADMIN or GROUP databases (CMDEMO or CMPROJ).
• Name of the Project Management 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.
4 Set the Database User Name field to:
• expadmin for the EXPADMIN database.
• exp for each GROUP database (CMDEMO or CMPROJ).
• privuser of the PMDB.
5 Set the Password field to:
• expadmin for the ADMIN 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.
8 Continue with the steps in Test the Database Connection.
Test the Database Connection
1 Click Test Configuration to verify that connection is successful.

2 Click Next. The Select Targets dialog box Displays.
3 Continue with the steps in Select Targets.
Select Targets
1 Check <server_name>, where <server_name> is the target server

for WebLogic.
2 Click Finish.
3 After you have finished setting up all data sources for WebLogic,
deploy Contract Management from the WebLogic Server
Administration Console. See “Deploying Contract Management”
on page 32.
Deploying Contract Management

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.
2 Click Lock & Edit.
3 Click Deployments from 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
C:\Primavera\Contract Management\Ear folder, and click Next.
in the Choose targeting style section, click Install this deployment
as an application, and click Next.
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 In the Summary of Deployments section of the right hand pane,
click Start under Deployments, and choose Servicing all requests
from the drop-down list.
10 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
When Contract Management is not running under the default port (80),
you must manually update the configuration file containing the port
designation.
1 Navigate to one of the following locations:

• For JBoss, this is:

<Domain_Home>\lib\ext\com\primavera\exponline\common
• For WebLogic, this is:

<Domain_Home>\com\primavera\exponline\common
2 Open the following file in a text editor:

exponline.properties
3 Update the following line:

WebPort=80
4 Replace the port number with the appropriate port number.
35
Installing Contract Management on

a Web Server
This chapter describes how to install
In this chapter Contract Management 13.0 using the multi-
user, Web-based installation process, and
Prerequisites
with the option to connect to a Project
Installing Contract Management
Management schedule database.
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 Contract
Management from a Previous Version” on
page 45.
36 Installing Contract Management on a Web Server
Prerequisites
Prior to completing the procedures presented in this chapter, complete
all procedures in the “Preparing for Installation” on page 13. After
completing all pre-installation tasks, you are ready to install your
Contract Management software.
Installing Contract Management on a Web Server 37
Installing Contract Management

Start the Installation
Before you begin the installation, you must configure your

application server. This is described in “Configuring a JBoss
Application Server” on page 21, and in “Configuring a
WebLogic Application Server” on page 23.
1 From the Contract Management physical media or download

A document titled “Important Information” is displayed.
2 Read the document, and then close it by clicking the X in the upper
right-hand corner.
3 In the Welcome to Contract Management dialog box, select Install
Primavera Contract Management.
4 Select Web Server Installation, and click Next. This installs the
Contract Management software. The Contract Management
database must already be created.
5 On the “Welcome to InstallShield Wizard for Oracle Primavera
Contract Management” dialog, click Next.
The stand-alone User Installation option will only install

Oracle XE. This option is not available for Microsoft SQL
Server.
Select Your Application Server Location and Domain
1 In the Select the Web Server Type dialog box, select one of the
following options, and click Next:
• JBoss – Go to step 2 after you click Next.
• WebLogic – Go to step 3 after you click Next.
2 To select the JBoss location and domain:
a) In the Choose JBoss \bin folder dialog box, click Browse, go to
the <JBOSS INSTALL LOCATION>\bin folder.
b) Click Next.
c) In the Choose JBoss Server Folder dialog box, click Browse,
navigate to the location where you created the cm domain.
d) Click Next, and then go on to “Configure the Database

Connection” on page 38.
3 To select the WebLogic location and domain:
a) Click Browse to navigate to the location of the home folder in
which to store the configuration files.
b) Click Next, and then go on to Configure the Database
Connection.
Configure the Database Connection
1 In the Contract Management Database To Be Used dialog box,

select Microsoft SQL Server, and click Next.
The InstallShield wizard detects the Microsoft SQL database server
installed on your system prior to the installation, and prompts you
to enter the Microsoft SQL Server database administrator (SA)
password.
2 In the Enter the Microsoft SQL Server Information dialog box,
enter the following information, and click Next:
• Group database – The name of the database to connect to (for
example, CMPROJ or CMDEMO). This field is pre-filled with
the name of the database you configured prior to installation.
After installation you can configure additional project groups
via the Server Configuration in the Primavera Contract
Management Administration application.
• Computer – The name of the host where the projects reside.
This can be an alphanumeric name or an IP address.
• Port – The port number on the host where the database resides.
This field is pre-filled with the default port number, 1433.
3 In the Enter the Contract Management Database User Information
dialog box, enter the following information, and click Next (or
click Browse and select a new location before entering the infor-
mation),
• User name – The user name used to access the database.
• Password – The password used to access the database.
4 Continue with the steps in “Select a Connection to a Schedule
Database” on page 38.
Select a Connection to a Schedule Database In the Primavera
Schedule Database to be Used dialog box, select one of the following
options and click Next:
■ None (no scheduling tool used). Use this option when you will not
connect to the Project Management schedule database. Continue
with the steps in “Choose the Destination Location of Contract
Management Files” on page 40.
■ Connect to the Project Management Schedule Database on
Oracle. Continue with the steps in “Enter the Information about the
Schedule Database on Oracle” on page 39.
Microsoft SQL. Continue with the steps in “Enter Information
about the Schedule Database on Microsoft SQL Server” on
page 39.
Enter the Information about the Schedule Database on
Oracle
1 In the Primavera Schedule Database dialog box, enter the following

database server information:
• SID Name – The name of the Oracle database on the Project
Management system.
• Computer Name – The name of the host on which the database
resides. This can be either the alphanumeric name or the IP
address.
• Port – The number of the port on the Project Management host.
The default is 1521.
2 The next dialog box prompts you to enter the User Name and
Database Password of the Oracle database on the Project
Management host.
• Enter the User Name. The default is privuser.
• Enter the Database Password, and click Next.
3 Continue with the steps in “Configure the Schedule Database
Connection with Contract Management” on page 40.
Enter Information about the Schedule Database on Microsoft
SQL Server
1 In the Primavera schedule database dialog box, enter the following

database server information, and click Next:
• Database Name – The name of the Project Management
database to which you are connecting.
• Computer Name – The name of the host on which the Project

Management database resides. This can be either the
alphanumeric name or the IP address.
• Port – The port number of the Project Management database
host to which Contract Management connects.
2 Continue with the steps in Configure the Schedule Database
Connection with Contract Management.
Configure the Schedule Database Connection with Contract
Management
1 Enter the User Name and Database Password of the Project

Manager database to which you are connecting, and click Next.
The User Name displayed is privuser.
The next dialog box prompts you to enter the URL to the Web
server configured with the schedule database.
2 If you are not using P6 Web Access, click Next to accept the default
URL and continue. Otherwise, do the following:
• In place of the <P6 Web Access server address> part of the
URL, enter the name of the Project Management web server
host. Use the format hostname:portnumber.
• Remove the angle brackets, and leave the rest of the path intact.
• Enter the URL, and then click Next. For example: 

http://<HOST>:<PORT>/primaveraweb/comp/showproject

In the preceding example, replace <HOST> with the host name,
and replace <PORT> with the port number of the Project
Management web server host. The brackets are not part of the
name.
3 Continue with the steps in Choose the Destination Location of
Contract Management Files.
Choose the Destination Location of Contract Management
Files
In the Choose Destination Location dialog box, complete one of the

following tasks:
■ Click Next to install Contract Management in the default location,

C:\Primavera\ContractManagement.
■ Click Browse, select a new location, and click Next.
Configure Locations for Reports and Forms
1 In the Contract Management Reports Folder dialog box, click Next

to accept the default location for the Contract Management reports.
2 In the Contract Management Forms Folder dialog box, click Next
to accept the default location for the Contract Management forms.
3 In the Contract Management Reports and Forms Images Folder
dialog box, click Next to accept the default location for the
Contract Management reports and forms images.
4 Continue with the steps in “Configure Your SMTP Server” on
page 41.
Configure Your SMTP Server
In the Enter your SMTP Server dialog box, enter the name of your
SMTP server and click Next.
Complete the Installation
1 In the Start Copying Files dialog box, review the information, and
click Next.
2 If none of the following steps are required to be completed, a
message displays that the installation is complete. Click Finish.
Otherwise:
• If the J2SE Development kit is not already installed on your
system, the installation wizard prompts you to install it. Click
Next.
• If you previously installed Microsoft SQL Server Express, the
Enter Port Number to Use for Contract Management dialog box
displays. Type the port number used by the MSSQL database to
connect to Contract Management, and click Next. See
“Locating the Database Port Number when Using Microsoft
SQL Server Express” on page 43 for information about deter-
mining the port number.
The Setup Status dialog box display. Messages display to inform
that the EXPADMIN, CMDEMO, and CMPROJ databases are
created.
3 When the message displays that the installation is complete, click

Finish.
Locating the Database Port Number when Using

Microsoft SQL Server Express
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
Express 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.dialog box. 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.
45
Upgrading to Contract Management

from a Previous Version
This chapter describes how to upgrade an
In this chapter existing Contract Management installation.
Prerequisites For information on installing Contract

Upgrading an Existing Stand- Management 13.0 when there are no
Alone Installation
previous versions installed, see “Installing
Contract Management on a Web Server” on
page 35.
46 Upgrading to Contract Management from a Previous Version
Prerequisites
Prior to completing the procedures presented in this chapter, complete
all procedures in the “Preparing for Installation” on page 13. After
completing all pre-installation tasks, you are ready to upgrade your
Contract Management software.
Contract Management 13.0 no longer supports the Sybase Adaptive

Server Anywhere database. However, you can migrate an existing
Sybase ASA database to Oracle or to Microsoft SQL Server. You must
do this in your current version of Contract Management before you
upgrade to Contract Management 13.0.
For information about upgrading to Contract Management

13.0 from Expedition 9.0 or previous versions, contact
Contacting Customer Support.
Upgrading to Contract Management from a Previous Version 47
Upgrading an Existing Stand-Alone Installation

See “Configuring a JBoss Before You Begin Before you can upgrade the Contract
Application Server” on Management software for an existing stand-alone installation, you must
page 21 for JBoss
application server first install the JBoss application sever, and then specify a JBoss domain
installation information. specific to Contract Management.
See “Upgrading Your You must also upgrade your Contract Management databases.
Databases” on page 19 for
information on upgrading
your Contract Management Start the Installation
databases.

A document called “Important Information” is displayed. Read the
document, and then close it by clicking the X in the upper right-
hand corner.
2 In the Welcome to Contract Management dialog box, click Install
3 Select Upgrade Installation.
4 In the Welcome to the InstallShield Wizard for Contract
Management dialog box, click Next.
5 In the Question dialog box, click Yes to upgrade the existing Stand-
alone Web Server application to Contract Management 13.0.
Select Your JBoss bin folder Location and Domain
1 In the Choose JBoss Bin Folder dialog box, click Browse, and
navigate to the <JBOSS INSTALL LOCATION>\bin folder.
2 Choose the location of the bin folder, and click Next.
3 In the Choose JBoss Server Folder dialog box, click Browse, and
4 Choose the location of the cm folder, and click Next.
Read the Contract Management Database Upgrade
Reminder When the Primavera Contract Management Database
Upgrade Reminder dialog box displays, do one of the following:
• If you have already upgraded your databases, click Next.

• If you have not upgraded your databases, click Cancel. Then,
upgrade the databases, and start the upgrade installation again.

P6 Schedule Database to be Used dialog box, select one of the following
connect to the Project Management schedule database. Complete
the steps in “Configure Your SMTP Server” on page 50.
Oracle. Complete the steps in the Enter the Information about the
Schedule Database on Oracle section later on this page.
Microsoft SQL. Complete the steps in the “Enter Information
about the Schedule Database on Microsoft SQL Server” on
page 49.
Oracle

• SID Name – Name of the Oracle database on the Project
Management system.
• Computer Name – Name of the host on which the database
address.
• Port – Number of the port on the Project Management host. The
default is 1521.
Management database to which you are connecting.
3 Next, Configure the Schedule Database Connection with Contract
Management.

SQL Server

• Database Name – Name of the Project Management database
to which you are connecting.
• Computer Name – Name of the host on which the Project
• Port – Port number of the Project Management database host to
which Contract Management connects.
2 Next, configure the schedule database connection with Contract
Management.
Management



name.
3 Next, Configure Your SMTP Server.
1 In the Enter your SMTP Server dialog box, enter the name of your
SMTP server and click Next.
click Next.
2 When a message displays that the installation is complete. Click
Finish.

Upgrading an Existing Web Server Installation

Before You Begin Depending on which type of Web server you will
use, you must perform a number of preliminary steps before you can
upgrade the Contract Management software.
See “Configuring a JBoss ■ If you will use a JBoss Web server, you must first install the JBoss
Application Server” on application sever, and then specify a JBoss domain specific to
page 21.
See “Configuring a ■ If you will use a WebLogic Web server, you must first install
WebLogic Application WebLogic in a domain specific to Contract Management.
See “Upgrading Your You must also upgrade your Contract Management databases.
Databases” on page 19 for
information on upgrading
your Contract Management Start the Installation
databases

A document called “Important Information” is displayed. Read the
document, and then close it by clicking the X in the upper right-
hand corner.
2 In the Welcome to Contract Management dialog box, click Install
3 Select Upgrade Installation.
5 In the Question dialog box, click Yes to upgrade the existing Web
Server application to Contract Management 13.0.
Select Your Application Server Location and Domain
For information on configuring your application Web server

see “Configuring a JBoss Application Server” on page 21,
or “Configuring a WebLogic Application Server” on
page 23.
1 If your application Web server is JBoss, do the following to select

the JBoss location and domain:
a) In the Choose JBoss Bin Folder dialog box, click Browse, go to
the <JBOSS INSTALL LOCATION>\bin folder.
b) Click Next.
c) In the Choose JBoss Server Folder dialog box, click Browse,

d) Click Next, and go to Configure the Database Connection.
2 If your application Web server is WebLogic, do the following to
select the WebLogic location and domain:
a) Click Browse to navigate to the location of the home folder in
which to store the configuration files, and click Next.
b) Click Next, and go to Configure the Database Connection.
Configure the Database Connection
1 In the Contract Management Database To Be Used dialog box,

select Microsoft SQL Server/SQLServer 2005 Express
(recommended).
The InstallShield wizard detects the Microsoft SQL database server
installed on your system prior to the installation, and prompts you
to enter the Microsoft SQL Server database administrator (SA)
password.
2 Click Next.
3 In the Enter the Microsoft SQL Server Information dialog box,
enter the following information, and click Next:
• Group database name – Name of the database to connect to
(for example, CMPROJ or CMDEMO). This field is pre-filled
with the name of the database you configured prior to
installation. After installation you can configure additional
project groups via the Server Configuration in the Primavera
Contract Management Administration application.
• Computer name – Name of the host where the projects reside.
This can be an alphanumeric name or an IP address.
• Port – Port number on the host where the database resides. This
field is pre-filled with the default port number, 1433.
4 In the Enter the Contract Management Database User Information
dialog box, enter the following information and click Next (or click
Browse and select a new location first before entering the
information and clicking Next):
• User name – The user name used to access the database.

• Password – The password used to access the database.

Schedule Database to be Used dialog box, select one of the following
connect to the Project Management schedule database. Go to
“Configure Your SMTP Server” on page 55.
Oracle. See “Enter the Information about the Schedule Database on
Oracle” later on this page.
Microsoft SQL. Go to “Enter Information about the Schedule
Database on Microsoft SQL Server” on page 53.

Oracle

• SID Name – Name of the Oracle database on the Project
Management system.
• Computer Name – Name of the host on which the database
address.
• Port – Number of the port on the Project Management host. The
default is 1521.
Management host.
3 Continue with the steps in Configure the Schedule Database
Connection with Contract Management.

SQL Server

• Database Name – Name of the Project Management database

to which you are connecting.
• Computer Name – Name of the host on which the Project
• Port – Port number of the Project Management database host to
which Contract Management connects.
2 Continue with the steps in “Configure the Schedule Database
Connection with Contract Management” on page 49.

Management



name.
Choose the Destination Location of Contract Management
Files
1 In the Choose Destination Location dialog box, complete one of the

following tasks:
• Click Next to install Contract Management in the default

location, C:\Primavera\ContractManager.
• Click Browse, select a new location, and click Next.
Configure Locations for Reports and Forms
1 In the Contract Management Reports Folder dialog box, click Next

to accept the default location for the Contract Management reports.
2 In the Contract Management Forms Folder dialog box, click Next
to accept the default location for the Contract Management forms.
3 In the Contract Management Reports and Forms Images Folder
dialog box, click Next to accept the default location for the
Contract Management reports and forms images.
4 Continue with the steps in Configure Your SMTP Server.
1 In the Enter your SMTP Server dialog box, complete one of the
following tasks:
• Click Next to accept the default SMTP server, mail.
• Enter the name of your SMTP server and click Next.
click Next.
2 If none of the following steps are required to be completed, a
message displays that the installation is complete. Click Finish.

Otherwise:
• If the J2SE Development kit is not already installed on your
system, the installation wizard prompts you to install it. Click
Next.
• If you previously installed Microsoft SQL Server Express, the
Enter Port Number to Use for Contract Management dialog box
displays. In this dialog box, enter the port number used by the
MSSQL database to connect to Contract Management. Click
Next.
To locate the port number assigned during installation, see

“Locating the Database Port Number when Using Microsoft
SQL Server Express” on page 43.
The Setup Status dialog box displays. Messages display to inform

that the EXPADMIN, CMDEMO, and CMPROJ databases are
created.
3 When the message displays that the installation is complete, click
Finish.
57
Configuring Contract Management

for a WebLogic Cluster
Use this chapter if you will use Contract
In this chapter Management in a WebLogic cluster
environment.
Prerequisites
Configuring the Clustered
Environment
Considerations for Using
Contract Management in a
Clustered Environment
Configuring the Clustered
Environment
58 Configuring Contract Management for a WebLogic Cluster
Prerequisites
Consult the WebLogic documentation for information on setting up a
WebLogic cluster. This can be found at the following web site:

http://edocs.bea.com/wls/docs103/index.html
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.
Contract Management Installation and Configuration Guide for Microsoft SQL

Configuring Contract Management for a WebLogic Cluster 59
Configuring the Clustered Environment

See “Configuring a 1 Make changes to the startManagedWebLogic.cmd, instead of to
WebLogic Application startWebLogic.cmd, as specified in “Configuring a WebLogic
Application Server” on page 23.
It is recommended that you echo classpath and

Java_options to ensure that the changes you make in step 1
are accurately made.
See “Prerequisites” on 2 On each managed server machine, configure a domain specific to

page 58. 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 the
startManagedWebLogic.cmd 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 On the server where you installed WebLogic, copy all the files in
the <Contract Management_domain_home>\lib folder into the
<Contract Management_domain_home>\lib folder on each of the
managed server machines.
6 On the server where you installed WebLogic, copy the <Contract
Management_domain_home>\com folder 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 “Deploying Contract
Management” on page 32.
When selecting target servers for Contract Management,

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 Jackrabbit

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

In a clustered environment, it is recommended 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 XML API in a Clustered Environment

Passing the JSESSIONID If using 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 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, and 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 the Save button to save the settings.
7 In the Change Center, click the Release Configuration button.

Enabling nodemanager for Contract Management in a

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
Viewing and Modifying Contract

Management Settings
This chapter describes how to view and
In this chapter: modify Contract Management configuration
settings in the Primavera Administrator.
Starting the Primavera
Administrator
Run this utility to change application server,
Modifying Values of Configuration
Settings database, or authentication configuration
Modifying Application Server settings, or general preferences.
Settings
Modifying Authentication Settings
Modifying Content Repository
Settings
Modifying Database Settings
Modifying Project Management
Schedule Database Settings
Setting Preferences
Modifying Web Server Settings
Configuration Settings for
Contract Management
66 Viewing and Modifying Contract Management Settings
Starting the Primavera Administrator

As the system administrator, you can use the Primavera Administrator
application to view and modify Contract Management configurations.
Content Displayed in the Primavera Administrator Contract

Management system configurations, including settings for the database
server, application server, authentication, the content repository, and
preferences, are stored in the Contract Management database that you
specified during installation.
Only experienced administrators should use the Primavera

Administrator to modify configuration settings.
Access to the Primavera Administrator You must run the

Primavera Administrator locally. See “Run the Primavera
Administrator” on page 69.
Contract Management 13.0 Installation and Configuration Guide for MS SQL

Viewing and Modifying Contract Management Settings 67
Components of the Primavera Administrator The Primavera

Administrator presents configuration settings in a tabbed dialog box.
Tree View presents the current configurations and settings in an

expandable and collapsible hierarchy.
Click to display a hierarchical

view of the configuration data. Provides help for the
current view.
When marked,
presents
information in a
tool tip when you
linger your mouse
pointer over a
setting.
To change a
setting value,
triple-click on the
setting name, and
type a new value.
In Windows, you
can also press F2
to change to Edit
To return a setting
to its default value,
right-click it and
select Revert to
default value.

Table View presents the current configurations and settings in a table,

organized alphabetically in ascending or descending order.
To sort content of a column, click a

column heading. Sorting can help you
distinguish similar settings contained
in multiple configurations.
Click to display
configuration
settings in a table
To change a value, click the
format.
setting, and enter a new value.

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

deletions.
Run the Primavera Administrator
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 to run Primavera Administrator.
Show Tool Tips To display brief setting descriptions in Tree or Table

view in Primavera Administrator, do the following:
1 Mark the Show tool tips check box.

A check mark is displayed in the check box.
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.
4 Click Save Changes.
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 Application Server Settings

After Contract Management is installed, you can change application
server settings.
For example, if during installation, you configured a multi-user

Web-based installation of Contract Management with a WebLogic
server that was later configured to use a different path, or you can
change the path to the server.
Or, if the application server you configured during installation became

unavailable during temporary maintenance, you can change the
application server path to enable your clients to use a different server.
Change Application Server Settings in Tree View
1 Expand the tree to the Application Server folder by selecting

Contract Management 13.0 Settings > Application Server.
2 Triple-click the app_server_name attribute and select one of the
following options:
• JBoss
• WebLogic
3 Triple-click the Domain Home attribute, delete the current value,
and enter the path of the JBoss or WebLogic server.
Change Application Server Settings in Table View
1 In the Setting Name column, locate Application Server

\app_server_name.
2 In the Value column, double-click in the corresponding cell.
The cell displays the type of application server you selected during
the Contract Management installation.
3 Select one of the following options from the pull-down menu:
• JBoss
• WebLogic
4 In the Setting Name column, locate Application
Server\DomainHome.

5 In the corresponding cell of the Value column, delete the current

value, and change the path of the application server.

Modifying Authentication Settings

Contract 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 13.0 Settings >Authentication.
b) Triple-click Mode: LDAP.
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 13.0 Settings>
Authentication > LDAP > Connection Information.
b) Triple-click and enter a value for each of the following required
fields:
• LDAP Host Name
• LDAP Port Number
• LDAP User Name
• LDAP Server Password
• LDAP Base Domain Name (DN)
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 FieldMaps by selecting Contract

Management 13.0 Settings >Authentication > LDAP >
Connection Information>FieldMaps.
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
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 as for Tree View.
2 Enter values for all required fields.
3 Click Save Changes when finished.

Modifying Web Single Sign-On Settings

These settings are necessary to enable Contract Management users and
Project Management users to use a single sign-on to communicate with
the Microsoft SharePoint content repository.
For 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 Content Repository folder by selecting

Contract Management 13.0 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 Content Repository Settings

You can modify settings of your pre-configured Oracle, JackRabbit, or
Microsoft SharePoint content repository. You can also change the type
of content repository and all related attributes. For information about the
settings in this section, see “Configuration Settings for Contract
Changing Content Repository Settings in Tree View
1 Expand the tree to the Content Repository folder by selecting

Contract Management 13.0 Settings > Content Repository.
2 Select the type of content repository:
a) Triple-click CRType.
b) From the pull-down menu, select Oracle, Jackrabbit, or
SharePoint.
3 Set the repository attributes for the type of repository you chose.
For Oracle:
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 Jackrabbit:
• URL
• Database User Name
• Database Password
• Repository Home
• Admin User Name
• Admin Password
For Microsoft SharePoint:
• Login Name
• Password
• Authentication Mode
• Host Name
• Domain Name
• Domain Library 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/CRType field.
2 Click in the corresponding cell of the Value column, and select
Oracle, Jackrabbit, or SharePoint from the pull-down menu.
3 Set the content repository settings.
a) If you are using an Oracle content repository, in the Setting
Name column find the path that starts with Content
Repository/Oracle/, and then in the Value column enter the
values for the settings.
b) If you are using a Jackrabbit content repository, in the Setting
Name column find the path that starts with Content
Repository/Apache Jackrabbit/, and then in the Value column
enter the values for the settings.

c) If you are using a Microsoft 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 Settings

In the Primavera Administrator, you can complete the following tasks:
■ Change Contract Management Database Settings

■ Change ADMIN Database Settings
■ Change GROUP Database Settings
■ Add a New GROUP Database Instance
■ Delete a GROUP Database Instance
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 “Contract Management Configuration”
section of the Web & Application Server Configuration for Contract
Management 13.0 document.
In Tree View:
1 Expand the tree to the Database folder by selecting Contract

Management 13.0 Settings >Database.
2 Triple-click and enter a value for each of the following options:
• database_port
• database_host_name
• DatabaseSiteName

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 as 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.

However, you can configure Contract Management to run
with multiple instances of the GROUP database. For
information, see “Add a New GROUP Database Instance” on
page 82.
In Tree View:
1 Expand the tree to the ADMIN folder by selecting Contract

Management 13.0 Settings > Database > Database Groups >
ADMIN.
• DBName
• JNDIName

• Password
• Report Location
• UserName
The AdminName field value cannot be changed.

In Table View:
Change GROUP Database Settings
In Tree View:

Management 13.0 Settings > Database > 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
• ReportLocation
• 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 Instance To add a new database
instance to a configuration, you can duplicate an existing instance in the
Tree View. You can also copy a database folder, paste it, and change
settings of the new instance. For information about the settings in this
section, see “Configuration Settings for Contract Management” on
page 88.
1 Expand the tree to the GROUP database you want to duplicate.

For example, select Contract Management 13.0 Settings >
Database > 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 81.

Delete a GROUP Database Instance You can delete a group
database instance in the Tree View.
1 Expand the tree to the GROUP database you want to delete.

For example, select Database > Database Groups >

GROUP[1]:cmdemo.
2 Right-click the folder of the database instance to delete.
3 Select Delete.

Modifying Project Management Schedule Database

Settings
During installation, you can connect Contract Management to a Project
Management Schedule Database running on either Microsoft or Oracle.
After installation, you can configure a Project Management Schedule

Database to run with Contract Management if you chose not to
configure one while installing the software, or you can change settings
that enable the connection to the Project Management Schedule
Database. 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 Project Management Schedule Database.
Change Project Management Schedule Database Settings
In Tree View:
1 Expand the tree to the Project Management folder by selecting

Contract Management 13.0 Settings > Database > Project
Management.
2 Select the database type.
a) Triple-click Type.
If no Project Management Schedule Database was configured
during installation, this field value is set to null.
b) Select the database type: mssql or oracle.
• Name
• Host Name
• Port Number
• SID (Oracle Only)
• User Name
• Password
• URL – The format of the URL is:

http://<IP address of P6 Web Access>/primavera/

comp/showproject
In the URL, substitute the actual IP address of P6 Web Access for the
<IP address of P6 Web Access> 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 Project Management 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 underneath 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 Preferences
After 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
In Tree View:

Management 13.0 Settings > Preferences.
• GridToExcel.
• IncludeURLInMail — yes or no
• InstallPath
• PrintDebugLevel
• Report Images Location
• SMTPServer
• Standalone
• TemplatePath
In Table View:

Modifying Web Server Settings

Setting 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
In Tree View:

Management 13.0 Settings > Web Server.
• CharacterEncoding
• CompressionEnabled — true or false
• ExpeditionWebServiceName
• WebApplicationName — This is EXPONLINE.
• WebProtocol
• WebPort
• WebServerName
• sessiontimeout
• xmlsessiontimeout
In Table View:

Configuration Settings for Contract Management

You 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 13.0 Settings
Setting Name and Description Default Valid Ranges/Values
Application Server
Application Server/app_server_name JBoss —

Application server configured with Contract Management:
JBoss or WebLogic.
Application Server/DomainHome C:\jboss-5.0.1.GA\ —

Location of the application server server\cm
Authentication
Authentication/Mode NATIVE or LDAP Native, LDAP

The method used for client authentication.
Authentication > LDAP > Connection Information
Authentication/LDAP/Connection Information/LDAPHost — —
LDAP server host name
Authentication/LDAP/Connection Information/LDAPPort 389 —

Port number for authentication via the LDAP server.
Authentication/LDAP/Connection — —
Information/LDAPUserName
User name for authentication via the LDAP server.
Information/LDAPPassword
Password for authentication via the LDAP server.
Information/LDAPBaseDN
Base domain name of the LDAP server.
Authentication/LDAP/Connection Information/SSL — —
Certificate Store
The full path to the keystore that holds the SSL certificate for
the LDAP server.

Authentication > LDAP > Connection Information
Authentication/LDAP/Connection Information/SSL Store — —

Password
The password for the keystore that holds the SSL certificate.
Authentication > LDAP > Field Maps
Authentication/LDAP/FieldMaps/FieldMap/MappedData — —
baseField:EMAIL
Email address of the user to be authenticated.
Authentication/LDAP/FieldMaps/FieldMap/ — —
MappedDatabaseField:EXTENSION
Work telephone extension of the user to be authenticated.
MappedDatabaseField:FAX
Fax number of the user to be authenticated.
MappedDatabaseField:FIRST_NAME
First name of the user to be authenticated.
MappedDatabaseField:FULL_NAME
Full name of the user to be authenticated.
MappedDatabaseField:JOB_TITLE
Job title of the user to be authenticated.
MappedDatabaseField:LAST_NAME
Last name of the user to be authenticated.
MappedDatabaseField:LOGIN_NAME
Login name of the user to be authenticated.
MappedDatabaseField:MOBILE
Mobile (cellular) telephone number of the user to be
authenticated.
MappedDatabaseField:TELEPHONE
Personal telephone number of the user to be authenticated.

Authentication > LDAP
Authentication/LDAP/LastSearch — —
The 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 — —

Key
The string in the HTTP header that identifies the user name.
Authentication/Web Single Sign-On/Context Path

Override
The base URL for Contract Management.
Authentication/Web Single Sign-On/Server and Port

Override
The server name and port to direct the URL to.
Content Repository>CRType
Content Repository/CRType Jackrabbit Oracle, Jackrabbit, or

Type of content repository used with Contract Management. SharePoint
Options include Oracle, Jackrabbit, or SharePoint.
Content Repository>Oracle Content Server
Content Repository/Oracle Content Server/Oracle Host — —

name
The IP address or the machine name for the content repository
host.
Content Repository/Oracle Content Server/Port — —

The Port number where the content repository resides.
Content Repository/Oracle Content Server/Oracle Home — —
The root level folder for the content repository. This must start
and end with a \ character. For example:
\Contribution Folders\OraclePrimavera\
Content Repository/Oracle Content Server/Oracle — —

Security Group
Set by the Oracle Administrator.

Security Account

Content Repository>Oracle Content Server

Document Type
Content Repository/Oracle Content Server/Metadata Cm Cm

Prefix
Content Repository/Oracle Content Server/Admin User — —

The 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 Single User
Mode Multiple User
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 username specified in in the Primavera
Administrator 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
username 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.
Content Repository>Jackrabbit
Content Repository/Apache Jackrabbit/URL — —

Path or URL location of the content repository.
Content Repository/Apache Jackrabbit/Database User — —

Name
Username for the database used with the content repository.
Content Repository/Apache Jackrabbit/Database — —

Password
Password for accessing the database used with the content
repository.

Content Repository>Jackrabbit
Content Repository/Apache Jackrabbit/Repository Home — —

The path to the install directory of the content repository.
Content Repository/Apache Jackrabbit/Admin User Name — —

User name of the administrator who maintains the database.
Content Repository/Apache Jackrabbit/Admin Password — —

Password of the administrator who maintains the database.
Content Repository>Microsoft SharePoint
Content Repository/Microsoft SharePoint/LoginName — —

The name required for logging onto the content repository.
Content Repository/Microsoft SharePoint/Password — —

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

Mode
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 in the Primavera Administrator Tool Settings.
Use Multiple Users to logon to SharePoint with the username

of the user logged into Contract Management. In this mode,
the Modified By and Created By columns for versions and
attachments in SharePoint will be the same username 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.
Content Repository/Microsoft SharePoint/HostName — —
The name of the host on which the content repository resides.
Content Repository/Microsoft SharePoint/Domain — —

SharePoint authentication domain name.
Content Repository/Microsoft SharePoint/Document — —

Library URL
The URL of the Microsoft SharePoint document library used
by Contract Management. This document library is internal to

Content Repository>Microsoft SharePoint
Content Repository/Microsoft SharePoint/Web Service — —

URL
The URL of the Oracle Primavera SharePoint connector. This
enables Contract Management and Project Management to
use a single sign-on to communicate with the Microsoft
SharePoint repository.
Content Repository/Microsoft SharePoint/External — —
Document Library URL
The path to the document library that is external to Contract
Management. Users can browse this library for documents to
attach to Contract Management documents.
Configuration Management
Configuration Management/Configuration Capture

Used to turn automatic configuration capture for Oracle on or
off
Configuration Management/Configuration Capture
Used to set the time to start the automatic configuration

capture for Oracle.
Database
Database/Database Type — —
Database type.
Database/database_port MSSQL: 1433 —

Port number used by the MSSQL or Oracle database Oracle: 1521
configured for use with Contract Management. For more
information, see the Web & Application Server
Configuration for Contract Management 13.0
document.
Database/database_host_name — —
Name of the computer on which the Contract Management
database resides. This can be the host name or the IP address.
For more information, see the Web & Application Server
document.

Database
Database/DatabaseSiteName
A string of up to four character that is used to make the
primary keys unique for each company site. For more
information, see the Web & Application Server
document.
Database > Groups
Database > Groups > ADMIN
Database/Database Groups/ADMIN/DBName — —
Name 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/Database Groups/ADMIN/JNDIName — —
Java Naming Directory Interface (JNDI) name of the ADMIN
database that enables clients to identify and locate it.
Database/Database Groups/ADMIN/Name — —
Administrator user name for accessing the ADMIN database.
Database/Database Groups/ADMIN/Password — —
Password for accessing the ADMIN database.
Database/Database Groups/ADMIN/ReportLocation — —
The location for Contract Management reports.
Database/Database Groups/ADMIN/UserName — —
The username used by Contract Management to access the
Contract Management ADMIN database.
Database > Groups
Database > Groups > GROUP
Database > Groups > GROUP — —

Note: If more than one GROUP database instance is
configured, the database instance name displays as
GROUP[#]: <database_name> in the Primavera
Administrator.

Database > Groups
Database > Groups > GROUP
Database/Database Groups/GROUP/DBName — —
Name 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/Database Groups/GROUP/JNDIName — —
Java Naming Directory Interface (JNDI) name of the database
that enables clients to identify and locate it.
Database/Database Groups/GROUP/Name — —
Administrator user name for accessing the GROUP database.
Database/Database Groups/GROUP/Password — —
Password for accessing the GROUP database.
Database/Database Groups/GROUP/ReportLocation — —
The location for Contract Management reports.
Database/Database Groups/GROUP/UserName — —
The username used by Contract Management to access the
Contract Management GROUP databases.The username
used by Contract Management to access the Contract
Management Admin database.

Database > Project Management
Database/Project Management/Type null — Indicates that —

Type of Project Management Schedule Database configured to no Project Management
exchange data with Contract Management, if one was Schedule Database was
configured during installation. configured
mssql — Indicates that

a Microsoft SQL
Project Management
Schedule Database was
configured with
Contract Management
oracle — Indicates that

an Oracle Project
Management Schedule
Database was
configured with
Contract Management
Database/Project Management/Name — —
Name of Project Management Schedule Database configured
to exchange data with Contract Management, as the name
displays in the database management application.
Database/Project Management/Host Name — —
Name of the host on which the Project Management Schedule
Database resides.
Database/Project Management/Port Number — —
The port number of the Project Management Database.
Database/Project Management/SID (used only for Oracle) — —
Unique identifier of an Oracle Project Management Schedule
Database.
Database/Project Management/User Name — —
User Name required to access the Project Management
Schedule Database.
Database/Project Management/Password — —
Password required to access the Project Management
Schedule Database.
Database/Project Management/URL — —
URL of the remotely-based, Web-accessible Project
Management Schedule Database.

Database > Project Management
Database/Project Management/Encryption Key — —

Used to enable seamless integration between Contract
Management and the Project Management Database. Set by
right-clicking the field name. See step 4 in “Change Project
Management Schedule Database Settings” on page 84.
Preferences
Preferences/GridToExcel — —
Path to the gridtoexcel.xsl file that stores data derived from
Contract Management. For more information, see the Web
& Application Server Configuration for Contract
Preferences/IncludeURLInMail yes —
Determines whether to include the URL in mail messages. no
Preferences/InstallPath — —
The Contract Management install directory path.
Preferences/PrintDebugLevel — —
For more information about this setting, see the Web &
Application Server Configuration for Contract
Preferences/ReportImagesLocation — —
Path to the location in which images used in reports are stored.
For more information about this setting, see the Web &
Application Server Configuration for Contract
Preferences/SMTPServer — —
Name of the SMTP mail server for outgoing mail.
Preferences/Standalone yes — Indicates a yes — Indicates a

Type of Contract Management installation. standalone installation standalone installation of
of Contract Contract Management
Management
no — Indicates a no — Indicates a
Web-based installation Web-based installation of
of Contract Contract Management
Management
Preferences/TemplatePath — —
Temporary folder used by Contract Management templates.

Web Server
Web Server/Character Encoding UTF-8 See “Modifying Web

Type of character encoding used by the configured Web Server Settings” on
Server. page 87.
Web Server/CompressionEnabled true — Indicates that See “Modifying Web

file compression is Server Settings” on
enabled on the host page 87.
where the Web server
resides.
false — Indicates that

file compression is not
enabled on the host
where the Web server
resides.
Web Server/ExpeditionWebServiceName — See “Modifying Web
Name of the service for which the Web server is configured. Server Settings” on
page 87.
Web Server/WebApplicationName — See “Modifying Web
Server Settings” on
page 87.
Web Server/WebProtocol — See “Modifying Web
Protocol of the Web server. Server Settings” on
page 87.
Web Server/WebPort 80 See “Modifying Web
Port configured for use by the Web server. Server Settings” on
page 87.
Web Server/WebServerName — —
The Web server host name
Web Server/sessiontimeout — See “Modifying Web

page 87.
Web Server/xmlsessiontimeout —. See “Modifying Web
page 87.
99
Installing InfoMaker 10.5
Use this chapter if you chose InfoMaker

In this chapter 10.5 after choosing Install Other
Applications in the Welcome to Primavera
Installing InfoMaker
Contract Management dialog box. This
Setting up the Database
Connection to InfoMaker chapter describes how to install the Sybase
InfoMaker software for use with Contract
Management reports and forms.
After InfoMaker 10.5 is installed, the

InstallShield Wizard launches the Database
Wizard to configure the connection to the
Contract Management database.
100 Installing InfoMaker 10.5
Installing InfoMaker
Do the following steps if you chose InfoMaker 10.5 after choosing
Install Other Applications in the Welcome to Primavera Contract
Management dialog box.

2 A message box displays telling you that the InfoMaker 10.5
installer will be launched. Click OK.
3 The Preparing Setup dialog box displays. If a message displays that
says, “The InfoMaker installation requires the following Adaptive
Server Anywhere component(s): Personal Server,” click OK to
continue.
4 In the Choose Destination Location dialog box, click Next to
choose the default.
5 In the Choose Destination Location for Shared files dialog box,
click Next to choose the default.
6 In the Setup Type dialog box, click Typical, and click Next.
7 In the Select Program folder dialog box, click Next to choose the
default.
8 In the Start Copying Files dialog box, review the settings. Click
Next.
9 When the InstallShield Wizard Complete dialog box displays, click
Finish. The Primavera Setup program displays. See “Setting up the
Database Connection to InfoMaker” on page 101.
Installing InfoMaker 10.5 101
Setting up the Database Connection to InfoMaker

After the InfoMaker software is installed, the InstallShield Wizard
launches the Primavera Setup program.
1 In the Choose Reports Location dialog box, click Next to choose

the default location.
2 In the Database type dialog box, select Microsoft SQL Server then
click Next.
3 In the Enter the computer name and Database Group name dialog
box, enter the following information and click Next:
• Computer – Name of the computer you are using for the instal-
lation.
• Instance – Identifier of the location where the database resides.
For example, Primavera.
• Group – Name of the database where projects reside. The
default is cmdemo.
4 In the next dialog box, enter the User ID and Password used to
access the MS SQL Server database, for example, exp for the User
ID and sql for the Password.
5 In the Review settings before configuring for InfoMaker, review the
settings, and then click Next.
6 When the InfoMaker database configuration completes, click
Finish in the InstallShield Wizard Complete dialog box.
103
Installing and Configuring the

Oracle Primavera SharePoint
Connector
Use this chapter to install and configure the
In this chapter Oracle Primavera SharePoint Connector to
enable Microsoft SharePoint to integrate
Installing the Oracle Primavera
SharePoint Connector with Contract Management. This enables
Configure the Oracle Primavera both Contract Management and Project
SharePoint Connector URL in Management to use a single signon to
Primavera Administrator
communicate with the Microsoft SharePoint
Repository.
104 Installing and Configuring the Oracle Primavera SharePoint Connector
Prerequisites
See “Preparing for You must first install Contract Management, making certain that you
Installation” on page 13. first complete all prerequisite tasks.
Installing and Configuring the Oracle Primavera SharePoint Connector 105
Installing the Oracle Primavera SharePoint Connector

Create the Web site In Internet Information Services (IIS) manager,
do the following:
1 Create a new Web site.

2 Right-click on 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) Unmark the Integrated Windows Authentication checkbox,
and click the OK button.
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, go to the Oracle Primavera

SharePoint Connector folder, 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, you can either
accept the default values or use the fields on the dialog to change
them.
3 Click the Next button.
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
This should display a list of the available functions. In the preceding
URL:
■ <HOST> is the name of the host on which Web Service runs.
106 Installing and Configuring the Oracle Primavera SharePoint Connector
■ <PORT> is the TCP port that the Web site will use. You entered this
when you created the Web site.
■ <VIRTUAL_DIR> is the name of the Virtual directory that you
created.
■ WS_FPRPC.asmx is the name of the Web Service.
Installing and Configuring the Oracle Primavera SharePoint Connector 107
Configure the Oracle Primavera SharePoint Connector

URL in Primavera Administrator
See “Run the Primavera 1 Run Primavera Administrator.
Administrator” on page 69.
2 Expand the Content Repository folder, and then expand the
Microsoft SharePoint folder.
3 Triple-click Authentication Mode, and choose Multiple User.
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.
6 Click the Save Changes button.
109
Setting Up the Contract

Management Environment
This chapter describes how start setting up
In this chapter the Contract Management application
environment.
Starting the Administration
Application
Adding Contract Management
Users
Setting Up Reports and Forms
Displaying Report Titles
Containing International
Characters
Running Contract Management as
a User Account
Importing Users from LDAP
Reconfiguring the Contract
Management Web Server
Encrypting Passwords when
Using a JBoss Application Server
110 Setting Up the Contract Management Environment
Starting the Administration Application

1 From the Windows desktop open Internet Explorer.
2 Enter the Web address for the Contract Management
Administration Application as follows:
http://webservername/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 ID and password in the Administration login

dialog box, and click Log In.
Setting Up the Contract Management Environment 111
Adding Contract Management Users

Users 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 1 Logon to the Contract Management Administration Application

Administration
Application” on page 110 2 Click User Accounts.
3 In the User Accounts window, click Create New User to open the
Create New User dialog box.
4 Type an ID 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).
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 117.
Setting Up Reports and Forms

When you install Contract Management, setup stores Contract
Management reports and forms by default in folders called Reports and
Forms on the Web Server in \Primavera\ContractManager.
To use reports and forms, the drive on which they are stored must be
available from the Contract Management Web Server. The following
instructions explain how to configure the Contract Management Web
Server to use reports and forms.
Run the Contract Management Administration Application on

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

Administration
Application” on page 110. 2 Click Server Configuration to open the Server Configuration
window.
3 In the Report and Form Locations section, click Add to open the
Report and Form Location dialog box.
4 In the Location field, enter a name for the location (such as Bala
Cynwyd).
5 Click Browse next to the Report Path or Form Path field to select a
report or form location, or enter the report and form paths in their
respective fields.
• If the reports and forms are located on the same machine as the
Contract Management Web Server, the path must be a physical
path, such as C:\Primavera\ContractManager\reports. You can
click My Computer from the Browse dialog box to select the
path.
• If the attachment files are located on a network drive, the path
must be a UNC path, such as \\mycomputer\reports. You can
click My Network Places from the Browse dialog box to select
the path.
If the reports and forms are on a network drive, you must run
the Contract Management Web service as a user account.
Refer to “Running Contract Management as a User Account”
on page 115.
6 Click Import Reports and Forms to import the reports and forms.
This could take several minutes to complete.
7 Under Projects, click Add to open the Select Projects dialog box 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.
8 Click Save & Close when finished.
If your report and form titles contain international characters,

you will need to update the Web Server properties to display
the titles properly in the Advanced Print dialog box. See
“Running Contract Management as a User Account” on
page 115.
Displaying Report Titles Containing International

Characters
To display international report/form titles in the Advanced Print dialog
box, perform the following steps:
1 Stop the Contract Management service.

2 Add one of the following lines to the exponline.properties file:
• If the workstation used to create the InfoMaker reports is
running Simplified Chinese, add:
ReportEncoding=GB2312
• If the workstation used to create the InfoMaker reports is
running Traditional Chinese, add:
ReportEncoding=BIG5
• If the workstation used to create the InfoMaker report is running
Russian, add:
ReportEncoding=WINDOWS-1251
3 Start the Contract Management service.
4 Import Reports and Forms.
Running Contract Management as a User Account

If your reports, forms, attachments, and/or Brava! markups directories
are on a network drive (a drive that is accessible from but not on the
same machine as the one on which Contract Management is installed),
you must run the Contract Management service as a domain user
account instead of as a local system account. You must always use UNC
type paths (using the form of \\computer\reports) for the location of the
reports, forms, attachments, and/or the Brava! markups directory when
configuring Contract Management.
Set Up Contract Management as a User Account Using the

Services Dialog Box From the machine running the Contract
Management Web Server, do the following:
1 Click Start, and navigate to Settings > Control Panel.

2 From the Control Panel, navigate to Administrative Tools >
Services > Contract Management.
3 In the Contract Management Properties dialog box, click the Log
On tab.
4 Click the This account.
5 Enter the user’s login, password, and then enter the password again
to confirm it.
6 Click OK.
Start and Configure the Contract Management 
Administration Application
Run the Contract Management Administration Application on

the same machine that the Web Server is installed on to
ensure that you have the correct network drive mappings.
1 From the Windows desktop, open Internet Explorer and enter the
Web address for the Contract Management Administration Appli-
cation.
2 Type your administrator user ID and password in the
Administration Login dialog box; the default ID and password are
both EXPADMIN. Click Log In.
 3 Click Server Configuration. In the Server Configuration window,
 scroll down to the Report and Form Locations section. Follow the
instructions in “Adding Contract Management Users” on page 111.
You must enter the UNC path for the location, not the
mapped network drive path.
Importing Users from LDAP

The 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 1 Logon to the Contract Management Administration Application.

Administration
Application” on page 110. 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 the 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,

chose ContractManagement, choose Utililty, choose CMAdmin-
Config, and double-click LDAPCfgWiz.cmd 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 names 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 Restart 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 117.
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.
Reconfiguring the Contract Management Web Server

If you need to reconfigure the Contract Management Web Server after it
has been installed, click Start, and then navigate to Programs >
Primavera > Contract Management Utilities > Server Config. Use this
utility if you need to change any of the following items:
■ SMTP Server
■ Contract Management Web Server port number
■ Contract Management database type
■ Database server connection
■ Project Management connections
■ Minimum and maximum memory allocation for the Contract
Management Web Server
Encrypting Passwords when Using a JBoss

Application Server
If you are using a JBoss application server, and want to encrypt
passwords in the expedition-ds.xml file, the following web site contains
information to help you do so.
http://www.jboss.org/community/wiki/
EncryptingDataSourcePasswords
The preceding URL should be all on one line. The formatting

restrictions of this document prevent it from appearing on one line.
123
Configuring the Oracle Content

Repository for Use with Contract
Management
This chapter describes how to configure the
In this chapter Oracle content repository for use with
Adding Users
Adding Metadata Properties
124 Configuring the Oracle Content Repository for Use with Contract Management
Adding Users
If you are authenticating Contract Management users in native mode,
and are using the Oracle content repository, you must manually add
users to the Oracle content repository server. If you are using LDAP
authentication, this step is not necessary.
The Contract Management user login name must be the same as that
used for the Oracle content repository server.
When logging into Contract Management, the user must use

the same login name and case (upper or lower case) that
exists on the Oracle content repository server.
For information about adding users to the Oracle content repository

server, see your Oracle documentation.

Configuring the Oracle Content Repository for Use with Contract Management 125
Adding Metadata Properties

After adding the users, do the following:
1 In the Oracle content repository server, go to the Configuration

Manager utility.
2 Add the following Information Fields, and designate the Type as
Text:
• CmGroupName
• CmProjectName
• CmModuleName
• CmObjectType
• CmObjectId
• CmisAttachment
3 After you add the preceding Information Fields, click the Update
Database Design button.

127
Index
A Overview of Contract Manager 6
Application Server host components 6
P
C P6 Web Access
Creating databases adding database instances 70
initial steps 16 configuration settings 88
Custom portlets configure
password encryption 88 custom portlets 88
Passwords
encrypting
D for custom portlets 88
Databases Prerequisites
creating, initial steps for 16 for installing Contract Manager 14
Documentation 8 Primavera
starting 100, 105, 107
H
Help, online 8 R
Reports and forms
I sharing 112
InfoMaker
installation overview 57, 99, 103 S
installation, beginning 100, 105 Stand-Alone installation
installing by using the Primavera Setup for Microsoft SQL 2005 Express Server
program 101 overview of 35
online documentation 9
Installing Contract Manager
prerequisites for 14 U
Upgrade
important information 7
M Upgrade 10.0 version databases
Microsoft SQL Express Server installation beginning the upgrade 19
initial steps for 37 Upgrade from Contract Manager 11.0
for Microsoft SQL Server Web server
O initial setup steps 47
Online, help 8 overview of 45
Operating systems supported 7 for Oracle Web server
128 Index
connecting to the Project Management

schedule database running Microsoft SQL
Server 39, 49, 53
Upgrade from Expedition 10.0 to Contract Manager
installation
for Oracle Web server
not connecting to the Project Management
schedule database 41, 55
not connecting to the Project Management
schedule database running Oracle 39, 48,
53
User’s Guide 8, 9
W
Web Server components 6
WebLogic
Configure data source for Microsoft SQL
Server 27
data sosurce setup 29
prerequisites for 28

CM Install Guide

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CM Install Guide

Hochgeladen von

Copyright:

Verfügbare Formate

® ®

Using XML API in a Clustered Environment..................................................... 62

Contract Management Overview

Contract Management Database Server The database server

Microsoft SQL Server is not provided as part of the Contract

Requirements of the Contract Management Web and

Required Folders The Contract Management Web Server requires

Contract Management Web Server

\Program Files\Oracle\Contract Server components

Reports and Forms default folders

\Program Files\Oracle\Contract Contract Management's report

\Program Files\Oracle\Contract Contract Management's form

\Program Files\Oracle\Contract Image files used by reports and

Supported Operating Systems for Contract Management

The supported operating system information is listed in the

This manual covers upgrades from Expedition Professional version 10.0

Upgrade existing Microsoft SQL databases before installing Contract

Contract Management Documentation

■ Online Documentation can be accessed from the Contract

• The InfoMaker Getting Started Online Manual helps you use

Several areas of Contract Management can be customized,

About this Manual

Contacting Customer Support

Contract Management databases contain calculations

Preparing for Installation

For a New Installation of Contract Management 13.0

If your Contract Management 13.0 installation is a completely new

1 Create your Microsoft SQL database for a new Contract

This step is optional but recommended. The installation

3 Configure your JBoss or WebLogic application server. See

For an Upgrade from a Previous Software Installation

For information about upgrading from Expedition 9.0 or a

1 Upgrade existing GROUP and ADMIN databases. See “Upgrading

This step is optional. The installation process installs the

3 Configure your JBoss or WebLogic application server. See

Configuring the application server is required for all

Creating New Databases

When creating Microsoft SQL Server databases, the

Creating databases through the Database Wizard generates

Prerequisites Before creating the databases:

1 You must have the Microsoft SQL Server Client installed.

1 From your Contract Management physical media or download

4 In the Welcome to Primavera Contract Management dialog box,

1 In the Install or Upgrade Primavera Contract Management

b) If the database will be in a multi-byte language (Chinese or

Upgrading Your Databases

Before upgrading the database in your production

Upgrade an Existing Contract Management Database If you

1 In the Install or Upgrade Primavera Contract Management

Customers must migrate their Sybase databases to a supported platform

When migrating the databases, first migrate the Admin

Configuring a JBoss Application Server

1 Go to Projects, Servers, and choose Application Servers.

Do not download the files into a directory that is in the

Create a Domain Specific to Contract Management

1 Go to <JBOSS INSTALL LOCATION>\server.

1 Go to <JBOSS INSTALL LOCATION>\bin, right-click on run.bat,

2 Replace the line: 

The preceding is case-sensitive, and should be all on the

3 Save and close the file.

1 Go to the following location:

2 Right-click on jbossjta-properties.xml, and choose edit.

Details about the preceding parameter can be found on the