Contents Prerequisites... 5 Installing Contract Management Web Services... 11

Installing and Configuring Contract Management Web Services July 2014

Contents Prerequisites... 5 Base Contract Management Installation... 5 Java Runtime Environment Requirements... 5 Contract Management Application and Server Requirements... 5 Creating a WebLogic Domain for Contract Management Web Services... 5 Download the wsdl4j-1.6.2.jar... 8 Installing Contract Management Web Services... 11 Install Contract Management Web Services... 11 Configuring the WebLogic Application Server for Contract Management Web Services 13 Configure the WebLogic Application Server for Contract Management Web Services... 13 Set the Application Server Memory Parameters... 14 Configuring the WebLogic Domain for Contract Management Web Services... 19 Configuring an Oracle Database Data Source... 19 Configure JDBC Properties for an Oracle Database Data Source... 19 Configuring the Microsoft SQL Server Database Data Source... 21 Configure JDBC Properties for a Microsoft SQL Server Database Data Source... 21 Deploying the WebLogic Domain for Contract Management Web Services... 23 Adding Contract Management Web Services as a WebLogic Application... 23 Starting the Contract Management Web Services Application in WebLogic... 24 Create an Endorsed Folder... 24 Configuring Contract Management for a WebLogic Cluster... 25 Clustering: Configuring the Environment... 25 Configure the Admin and Managed Servers for Contract Management Web Services. 25 Adjust the Java Home variable on all Managed Servers... 26 Clustering: Start the WebLogic Domains... 26 Clustering: Configure the Data Sources... 27 Clustering: Configure JDBC Properties for an Oracle Database Data Source... 27 Clustering: Configure JDBC Properties for a Microsoft SQL Server Database Data Source... 29 Clustering: Deploy Contract Management Web Services... 30 Adding Contract Management Web Services as a WebLogic Application... 31 Starting the Contract Management Web Services Application in WebLogic... 32 Clustering: Considerations for Using Contract Management Web Services in a Clustered Environment... 32 Configuring Contract Management Web Services... 35 Starting the Contract Management Administration Application... 35 Configuring Authentication Mode for Contract Management Web Services... 35 3

Installing and Configuring Contract Management Web Services Configuring Username Token Profile Settings for Contract Management Web Services. 36 Configuring SAML Token Profile Settings for Contract Management Web Services... 36 Configuring Message Protection Settings for Contract Management Web Services... 37 Using LDAP with Contract Management Web Services... 38 For More Information... 41 Contract Management Documentation... 41 Contacting Customer Support... 42 Legal Notices... 44 4

Prerequisites This chapter describes how to complete the required prerequisites before installing the current version of Contract Management Web Services. In This Section Base Contract Management Installation... 5 Java Runtime Environment Requirements... 5 Contract Management Application and Server Requirements... 5 Creating a WebLogic Domain for Contract Management Web Services... 5 Download the wsdl4j-1.6.2.jar... 8 Base Contract Management Installation Before you can install and deploy Contract Management Web Services, you must first ensure you have: 1) Installed and configured Contract Management 14.1, Business Intelligence Publisher Edition against the database you intend to use (Oracle and Microsoft SQL Server are supported). 2) Deploy Contract Management14.1, Business Intelligence Publisher Edition on a WebLogic 11g domain. Refer to the following guides for further information these items: Installing and Configuring Primavera Contract Management 14.1 for Oracle Installing and Configuring Primavera Contract Management 14.1 for Microsoft SQL Server Java Runtime Environment Requirements Before installing Contract Management Web Services, you need to install a tested and supported JDK. You should deploy the EAR file in a supported application server running a supported JDK. Contract Management Application and Server Requirements After determining your Contract Management implementation plan, ensure your hardware and software can support it. For the full list of system requirements, versions, and tested configurations, see the Tested Configurations document. Creating a WebLogic Domain for Contract Management Web Services To create a WebLogic Domain: 1) Run the WebLogic Configuration Wizard. 5

Installing and Configuring Contract Management Web Services 2) In the Welcome window: a. Select Create a new WebLogic domain. b. Click Next. 3) In the Select Domain Source window, click Next to accept the default selections. 4) In the Specify Domain Name and Location: a. Enter the domain name. b. Enter the domain location. c. Click Next. 5) In the Configure Administrator User Name and Password window: a. Enter the user name and password information. b. Click Next. 6) In the Configure Server Start Mode and JDK window: a. Select Production Mode in the left pane. b. Select an appropriate JDK in the right pane. c. Click Next. 7) In the Select Optional Configuration window: a. Select the Administration Server and the Managed Servers, Clusters and Machines options. b. Click Next. 8) (Optional) In the Configure the Administration Server window, select the SSL enabled option and set the SSL listen port if you are enabling Secure Sockets Layer communication. See http://download.oracle.com/docs/cd/e12840_01/wls/docs103/secmanage/ssl.html for more details on setting SSL for WebLogic. 9) In the Configure Managed Servers window: a. Click Add. b. Enter the Name and select the Listen address information. c. (Optional) Select the SSL enabled option and set the SSL listen port. d. (Optional) Add or delete other managed servers. e. Click Next. 10) (Optional) In the Configure Clusters window: Note: Do not add clusters if you are not using multiple WebLogic server instances for scalability. a. Click Add. b. (Required) Enter the name of the cluster. c. (Optional) Enter the following information: Cluster messaging mode, Multicast address, Multicast port, Cluster address. d. (Optional) Add or delete other configured clusters. 6

Prerequisites e. Click Next. Note: For information on setting up clusters, use Oracle's WebLogic Server documentation: http://download.oracle.com/docs/cd/e11035_01/wls100/cluster/setup.ht ml. 11) (Optional) In the Assign Servers to Clusters window, assign a server to a cluster. 12) Click Next. Note: Select the Cluster in the right pane, then select the Server in the left pane. Assign the server to the cluster by clicking the right arrow button. 13) In the Configure Machines window: a. Select the Machine or Unix Machine tab. b. If you select the Machine tab: 1. Click Add. 2. (Required) Enter a machine name. 3. (Optional) Select the Node manager listen address from the list. Note: If you specify an address for a machine that hosts the Administration Server and you need to access the WebLogic Server Node Manager, you must disable the host name verification. 4. (Optional) Enter the Node manager listen port. 5. (Optional) Add or delete configured machines. c. If you select the Unix Machine tab: 1. (Required) Enter a valid machine name. 2. (Optional) Select the Post bind GID enabled option to enable a server running on this machine to bind to a UNIX group ID (GID) after it finishes all privileged startup actions. 3. (Optional) Enter the Post bind GID where a server on this machine will run after it finishes all privileged startup actions. If you do not enter a GID, the server will continue to run under the group where it was started. For this setting to work, you must select the Post bind GID enabled option. 4. (Optional) Select the Post bind UID enabled option to enable a server running on this machine to bind to a UNIX user ID (UID) after it finishes all privileged startup actions. 5. (Optional) Enter Post bind UID where a server on this machine will run after it finishes all privileged startup actions. If you do not enter a UID, the server will continue to run under the account where it was started. For this setting to work, you must select the Post bind UID enabled option. 6. (Optional) Add or delete configured machines. 7

Installing and Configuring Contract Management Web Services d. Click Next. Notes: You might want to create machine definitions for the following situations: (1) The Administration Server uses the machine definition, with the Node Manager application, to start remote servers. (2) WebLogic Server uses configured machine names when determining the server in a cluster that can handle certain tasks, such as HTTP session replication. The WebLogic Server then delegates those tasks to the identified server. You must configure machines for each product installation that runs a Node Manager process. The machine configuration must include values for the listen address and port number parameters. 14) In the Assign Servers to Machines window: Note: A machine is a physical server that will host a WebLogic managed server. Depending on your resource needs and data load, the machines may be in the same physical server where the WebLogic Admin Server is installed or in separate physical servers. a. In the Machine list, select the machine where you want to assign a WebLogic Server instance. b. Assign WebLogic Server instances to the selected machine. The name of the WebLogic Server instance is removed from the Server list and added below the name of the target machine in the Machine list. c. Repeat steps a and b for each WebLogic Server instance you want to assign to a machine. d. Review the machine assignments. If necessary, you can remove a WebLogic Server instance from a machine, and the WebLogic Server instance will be removed from the Machine list and restored to the Server list. e. Click Next. 15) In the Configuration Summary window, click Create. If given the option, you can click Done now. Otherwise, continue to the next step. 16) If you are using Windows, in the Creating Domain window: a. Select Start Admin Server. b. Click Done. 17) When prompted, enter the administrator user name and password that you entered above. Download the wsdl4j-1.6.2.jar If you plan to install Web Services, you must download the wsdl4j-1.6.2.jar on your machine. To download the jar: 1) Go to http://mirrors.ibiblio.org/pub/mirrors/maven2/wsdl4j/wsdl4j/1.6.2/. 8

Prerequisites 2) Select the wsdl4j-1.6.2.jar. 3) Save the file to your machine. 4) Note the location where you save the jar file. 9

Installing Contract Management Web Services Before beginning this installation, you must install and configure: Contract Management. Refer to Installing and Configuring Primavera Contract Management 14.1 for Oracle and the Installing and Configuring Primavera Contract Management 14.1 for Microsoft SQL Server guides detailed information. Java 1.6.X. on the server on which you are installing Contract Management Web Services. A WebLogic 11g domain for Contract Management Web Services. Refer to Configuring the WebLogic Domain for Contract Management Web Services (on page 19) for details on this step. Download the wsdl4j-1.6.2.jar. Then follow the instructions in this section to install Contract Management Web Services. In This Section Install Contract Management Web Services... 11 Install Contract Management Web Services Note: Before running the Contract Management installer, ensure that you are logged in as a user that can write to the <Weblogic_Domain_Home> folder. If necessary, adjust the permissions to this folder to allow write access. You must adjust permissions if WebLogic was installed by a different user instead of the current user. 1) From the Contract Management Web Services physical media or download location, run setup.exe. The Oracle Universal Installer dialog box will open. 2) On the Welcome page, click Next. Note: Click Next on each wizard dialog box to advance to the next step. 3) On the Specify Home Details screen, enter a name and path for the installation. You can install over an existing Contract Management Web Services directory from a previous installation or install in a new directory. If the directory you specify does not exist, the installer will create it during the installation process. 4) On the Information screen, click Next if you have installed and configured all of the listed items. If you have not yet installed and configured all of the items, click Cancel to end the installation for Contract Management Web Services and install the necessary components before resuming. 5) On the Java Home Location screen, browse to the installation location for Java. 11

Installing and Configuring Contract Management Web Services 6) On the Specify the wsdl4j-1.6.2 Directory screen, specify the path to the wsdl4j-16.2 jar file on the local machine. 7) On the Choose <Application Server> Domain Home screen, browse to the location of the domain for Contract Management Web Services. For example, C:\Oracle\Middleware\user_projects\domains\cmws. 8) On the Summary screen, check the summary. Click Install if the summary is accurate. 9) On the End of Installation screen, click Exit. Note: Do not change the location of the htmltemplates folder in the Contract Management Web Services home directory. If you have made any customizations to the templates in Contract Management home directory, copy the changed files to the htmltemplates folder in Contract Management Web Services home directory. 12

Configuring the WebLogic Application Server for Contract Management Web Services Follow the instructions in this section to configure WebLogic 11g for Contract Management Web Services on the server where you plan to install Contract Management Web Services. For the full list of tested configurations, see the Tested Configurations document. 1) Install WebLogic 11g. 2) If using a Sun Java Development kit, install a tested and supported JDK. In This Section Configure the WebLogic Application Server for Contract Management Web Services13 Set the Application Server Memory Parameters... 14 Configure the WebLogic Application Server for Contract Management Web Services Do the following to configure the WebLogic server for Contract Management Web Services: 1) On the server where you installed WebLogic, in the <Contract_Management_Web_Services_Domain_Home>\bin directory, open the startweblogic.cmd file (Windows) or startweblogic.sh file (Linux) in a text editor (such as Notepad). 2) Update the SAVE_CLASSPATH variable as follows: Windows Operating System with an Oracle Database Enter a line similar to the following (all one line): set SAVE_CLASSPATH=%DOMAIN_HOME%\lib\mail.jar;%DOMAIN_HOME%\lib\ojdbc6.jar;%CLASSPATH%;. Windows Operating System with a Microsoft SQL Server Database Enter a line similar to the following (all one line): set SAVE_CLASSPATH=%CLASSPATH%;%DOMAIN_HOME%\lib\mail.jar;%DOMAIN_HOME %\lib\sqljdbc.jar;. Linux Operating System with an Oracle Database Enter a line similar to the following (all one line): SAVE_CLASSPATH="${DOMAIN_HOME}/lib/mail.jar:${DOMAIN_HOME}/lib/ojd bc6.jar:${classpath}:." Linux Operating System with a Microsoft SQL Server Database Enter a line similar to the following (all one line): 13

Installing and Configuring Contract Management Web Services SAVE_CLASSPATH="${CLASSPATH}:${DOMAIN_HOME}/lib/mail.jar:${DOMAIN_ HOME}/lib/sqljdbc.jar:." Note: The preceding is case-sensitive, and should be all on the same line. 3) Update the JAVA_OPTIONS variable as follows: Windows Enter a line similar to the following (all one line): set JAVA_OPTIONS=%SAVE_JAVA_OPTIONS% -Djavax.xml.soap.MessageFactory=com.sun.xml.messaging.saaj.soap.ve r1_1.soapmessagefactory1_1impl -Djavax.xml.soap.SOAPConnectionFactory=weblogic.wsee.saaj.SOAPConn ectionfactoryimpl -Dcmws.install.home=<CM_WS_HOME> Linux Enter a line similar to the following (all one line): JAVA_OPTIONS="${SAVE_JAVA_OPTIONS} -Djavax.xml.soap.MessageFactory=com.sun.xml.messaging.saaj.soap.ve r1_1.soapmessagefactory1_1impl -Djavax.xml.soap.SOAPConnectionFactory=weblogic.wsee.saaj.SOAPConn ectionfactoryimpl -Dcmws.install.home=<CM_WS_HOME>" Notes: The preceding is case-sensitive, and should be all on the same line. Replace <CM_WS_HOME> in the preceding line with the location in which Contract Management Web Services is installed. For example c:/cmwebservices_1. 4) Save the changes you made to the startweblogic.cmd file (Windows) or startweblogic.sh file (Linux). Set the Application Server Memory Parameters Oracle recommends setting the following memory parameters for the typical Contract Management Web Services environment. 1) Determine which JDK you are using for your Contract Management Web Services domain. 2) Determine whether the application server that is hosting the Contract Management Web Services domain is running on a 64 bit operating system. If the application server is running on a 64 bit operating system, determine whether the application server is using the 64 bit mode when hosting the Contract Management Web Services domain: a. Locate and open the following file Windows <WebLogic_Home>\wlserver_10.3\common\bin\commEnv.cmd Linux <WebLogic_Home>/wlserver_10.3/common/bin/commEnv.sh 14

Configuring the WebLogic Application Server for Contract Management Web Services b. Search for the following line and note whether the value of <setting> is true or false: Windows set JAVA_USE_64BIT=<setting> Linux JAVA_USE_64BIT=<setting> c. Close the commenv.cmd / commenv.sh file. 3) Locate and open the following file: Windows <Contract_Management_Web_Services_Domain_Home>\bin\setDomainEnv.cmd Linux <Contract_Management_Web_Services_Domain_Home>/bin/setDomainEnv.sh 4) If you are using the Sun JDK on a 32 bit operating system or a 64 bit operating system on which the JAVA_USE_64BIT parameter is set to false, make the following edits to the setdomainenv.cmd / setdomainenv.sh file: a. Search for the following line: Windows set MEM_ARGS_32BIT=%WLS_MEM_ARGS_32BIT% Linux MEM_ARGS_32BIT="${WLS_MEM_ARGS_32BIT}" b. Replace the line above with the following lines: Windows @REM set MEM_ARGS_32BIT=%WLS_MEM_ARGS_32BIT% set MEM_ARGS_32BIT=-XX:NewSize=256m -XX:MaxNewSize=256m -XX:SurvivorRatio=8 -Xms1024m -Xmx1024m Linux # MEM_ARGS_32BIT="${WLS_MEM_ARGS_32BIT}" MEM_ARGS_32BIT="-XX:NewSize=256m -XX:MaxNewSize=256m -XX:SurvivorRatio=8 -Xms1024m -Xmx1024m" c. Search for the following line: Windows set MEM_MAX_PERM_SIZE_32BIT=-XX:MaxPermSize=128m Linux MEM_MAX_PERM_SIZE_32BIT="-XX:MaxPermSize=128m" d. Replace the line above with following lines: Windows @REM set MEM_MAX_PERM_SIZE_32BIT=-XX:MaxPermSize=128m set MEM_MAX_PERM_SIZE_32BIT=-XX:MaxPermSize=256m Linux # MEM_MAX_PERM_SIZE_32BIT="-XX:MaxPermSize=128m" MEM_MAX_PERM_SIZE_32BIT="-XX:MaxPermSize=256m" 15

Installing and Configuring Contract Management Web Services 5) If you are using the Sun JDK on a 64 bit operating system on which the JAVA_USE_64BIT parameter is set to true, make the following edits to the setdomainenv.cmd / setdomainenv.sh file: a. Search for the following line: Windows set MEM_ARGS_64BIT=%WLS_MEM_ARGS_64BIT% Linux MEM_ARGS_64BIT="${WLS_MEM_ARGS_64BIT}" b. Replace the line above with the following lines: Windows @REM set MEM_ARGS_64BIT=%WLS_MEM_ARGS_64BIT% set MEM_ARGS_64BIT=-XX:NewSize=256m -XX:MaxNewSize=256m -XX:SurvivorRatio=8 -Xms1024m -Xmx1024m Linux # MEM_ARGS_64BIT="${WLS_MEM_ARGS_64BIT}" MEM_ARGS_64BIT="-XX:NewSize=256m -XX:MaxNewSize=256m -XX:SurvivorRatio=8 -Xms1024m -Xmx1024m" 6) If you are using JRockit on a 32 bit operating system or a 64 bit operating system on which the JAVA_USE_64BIT parameter is set to false, make the following edits to the setdomainenv.cmd / setdomainenv.sh file: a. Search for the following line: Windows set MEM_ARGS_32BIT=%WLS_MEM_ARGS_32BIT% Linux MEM_ARGS_32BIT="${WLS_MEM_ARGS_32BIT}" b. Replace the line above with the following lines: Windows @REM set MEM_ARGS_32BIT=%WLS_MEM_ARGS_32BIT% set MEM_ARGS_32BIT=-Xms1024m -Xmx1024m Linux # MEM_ARGS_32BIT="${WLS_MEM_ARGS_32BIT}" MEM_ARGS_32BIT="-Xms1024m -Xmx1024m" 7) If you are using JRockit on a 64 bit operating system on which the JAVA_USE_64BIT parameter is set to true, make the following edits to the setdomainenv.cmd / setdomainenv.sh file: a. Search for the following line: Windows set MEM_ARGS_64BIT=%WLS_MEM_ARGS_64BIT% Linux MEM_ARGS_64BIT="${WLS_MEM_ARGS_64BIT}" 16

Configuring the WebLogic Application Server for Contract Management Web Services b. Replace the line above with the following lines: Windows @REM set MEM_ARGS_64BIT=%WLS_MEM_ARGS_64BIT% set MEM_ARGS_64BIT=-Xms1024m -Xmx1024m Linux # MEM_ARGS_64BIT="${WLS_MEM_ARGS_64BIT}" MEM_ARGS_64BIT="-Xms1024m -Xmx1024m" 8) Save the changes to the setdomainenv.cmd / setdomainenv.sh file. 9) Restart the WebLogic domain. 17

Configuring the WebLogic Domain for Contract Management Web Services In This Section Configuring an Oracle Database Data Source... 19 Configuring the Microsoft SQL Server Database Data Source... 21 Configuring an Oracle Database Data Source This section describes how to set up the data source on your WebLogic domain for Contract Management Web Services when the Contract Management database is an Oracle database. Complete all the following procedures for each database: Once for the GROUP database. Once for the ADMIN database, also referred to as EXPADMIN. Note: In this section, CMPROJ is used as the group database name. It is provided only as an example of a possible GROUP database name. Configure JDBC Properties for an Oracle Database Data Source Complete the following steps to configure the JDBC Data Source Properties. Note: Data Source names are case sensitive and must match the data source. 1) Login to WebLogic Admin console. 2) In the Change Center pane, click Lock & Edit. 3) In the Domain Structure pane, click Service, Data Sources. 4) In the Summary of Data Sources pane, select New, Generic Data Source. 19

Installing and Configuring Contract Management Web Services 5) In the Create a New JDBC Data Source pane: a. Set the Name field (depending on which data source your are setting up). For example, these might be: CMPROJ for the CMPROJ database EXPADMIN for the EXPADMIN database Note: JNDI field names are case sensitive, and must match the name you used for JNDI. b. Set the JNDI Name field to jdbc/<database_name>. For example, <database_name> might be: CMPROJ for the CMPROJ database EXPADMIN for the EXPADMIN database 6) Set the Database Type field to Oracle and click Next. 7) In the Database Driver field: If using Oracle 10g, select Oracle's Driver (Thin) Versions:9.0.1, 9.2.0, 10 and click Next. If using Oracle 11g, select Oracle's Driver (Thin) for Instance Connections: Versions:9.0.1, 9.2.0, 10, 11 and click Next. 8) In the Transaction Options screen: To set transaction options for a single project group: If you are configuring the Admin or P6 EPPM database, clear the Supports Global Transactions option, and click Next. If you are configuring a project database: 1. Select the Supports Global Transactions option. 2. Click the One-Phase Commit radio button. 3. Click Next. The Connection Properties dialog box displays. To set transaction options for multiple project groups: 1. Select the Supports Global Transactions option. 2. Select Emulate Two-Phase Commit. 9) In the Connection Properties screen: a. Set the Database Name field to the SID of the Oracle database. For example: ORCL. b. Set the Host Name field to <database_hostname>, where <database_hostname> is the name or IP address of the host where you installed each database. c. Set the Port field to <database_port>, where <database_port> is the port number of the host where you installed each database. d. Set the Database User Name field. You set these when you created the databases. For example: expadmin for the EXPADMIN database. cmproj for the CMPROJ database. e. Set the Password field. You set these when you created the databases. 20

Configuring the WebLogic Domain for Contract Management Web Services For example: expadmin for the ADMIN database. cmproj for the CMPROJ database. f. Confirm the password. g. Click Next. 10) In the Test Database Connection screen: a. Click Test Configuration to verify that connection is successful. b. Click Next. 11) In the Select Targets screen: a. Select <server_name>, where <server_name> is the target server for WebLogic. b. Click Finish. 12) In the Change Center pane, click Activate Changes. Configuring the Microsoft SQL Server Database Data Source This section describes how to set up the data source on your WebLogic domain for Contract Management Web Services when the Contract Management database is a Microsoft SQL database. Configure JDBC Properties for a Microsoft SQL Server Database Data Source Complete the following steps in the JDBC Data Source Properties dialog box for each database: Once for the GROUP database. Once for the ADMIN database, also referred to as EXPADMIN. Notes: In this section, CMPROJ is used as the group database name. It is provided only as an example of a possible GROUP database name. Data Source names are case sensitive and must match the data source. 1) Login to WebLogic Admin console. 2) In the Change Center pane, click Lock & Edit. 3) In the Domain Structure pane, click Service, Data Sources. 4) In the Summary of Data Sources pane, select New, Generic Data Source. 5) In the Create a New JDBC Data Source pane: a. Set the Name field (depending on which data source your are setting up). For example, these might be: CMPROJ for the CMPROJ database EXPADMIN for the EXPADMIN database Note: JNDI field names are case sensitive, and must match the name you used for JNDI. 21

Installing and Configuring Contract Management Web Services b. Set the JNDI Name field to jdbc/<database_name>. For example, <database_name> might be: CMPROJ for the CMPROJ database EXPADMIN for the EXPADMIN database 6) Set the Database Type field to MS SQL Server and click Next. 7) In the Database Driver field, select Microsoft's MS SQL Server Driver (Type 4) Versions: 2005 and later and click Next. 8) In the Transaction Options screen: To set transaction options for a single project group: If you are configuring the Admin or P6 EPPM database, clear the Supports Global Transactions option, and click Next. If you are configuring a project database: 1. Select the Supports Global Transactions option. 2. Click the One-Phase Commit radio button. 3. Click Next. The Connection Properties dialog box displays. To set transaction options for multiple project groups: 1. Select the Supports Global Transactions option. 2. Select Emulate Two-Phase Commit. 9) In the Connection Properties screen: a. Set the Database Name field to one of the following: The Database name for the Contract Management ADMIN database. This is EXPADMIN. The Database name for the Contract Management GROUP database. This is CMPROJ. b. Set the Host Name field to <database_hostname>, where <database_hostname> is the host where you installed Microsoft SQL Server. If the SQL instance is not a default instance, set the Host Name field to <database_hostname>\<instance_name>. c. Set the Port field to <database_port>, where <database_port> is the port number of the host where you installed Microsoft SQL Server. d. Set the Database User Name field. You set these when you created the databases. For example: exp for the EXPADMIN database. exp for the CMPROJ database. e. Set the Password field. You set these when you created the databases. For example: sql for the ADMIN database. sql for the CMPROJ database. f. Confirm the password. g. Click Next. 10) In the Test Database Connection screen: 22

Deploying the WebLogic Domain for Contract Management Web Services a. Click Test Configuration to verify that connection is successful. b. Click Next. 11) In the Select Targets screen: a. Select <server_name>, where <server_name> is the target server for WebLogic. b. Click Finish. 12) In the Change Center pane, click Activate Changes. Deploying the WebLogic Domain for Contract Management Web Services Adding Contract Management Web Services as a WebLogic Application To add P6 as a WebLogic application: 1) Launch the WebLogic Administration Console. Note: You can open the Administration Console via a web browser using this address: http://serverip:listenport/console. The default listenport is 7001. 2) In the Welcome window, log in using the user name and password that you created when you created your WebLogic domain. 3) In the Change Center pane of the Administration Console, click Lock & Edit. 4) In the Domain Structure pane, click Deployments. 5) In the Summary of Deployments pane, in the Control tab, click Install. 6) In the Install Application Assistant pane: a. Navigate to the <CM_WS_INSTALL_HOME>\server\ folder. b. Select the cmws.ear file. c. Click Next. 7) In the Install Application Assistant pane: a. Select Install this deployment as an application. b. Click Next. 8) In the Install Application Assistant pane: a. Click the server or cluster where you want to deploy the application. b. Click Next. 9) In the Install Application Assistant pane, click Next to accept the default options. 10) Review the configuration settings you have chosen, then click Finish to complete the installation. 11) In the Settings for cmws window, click Save. 23

Installing and Configuring Contract Management Web Services 12) Proceed to Starting the Contract Management Application in WebLogic. Starting the Contract Management Web Services Application in WebLogic To start the Contract Management application in WebLogic: 1) In the Change Center pane, click Activate Changes. 2) In the Domain Structure pane, click Deployments. 3) In the Summary of Deployments pane, select cmws. 4) In the Summary of Deployments pane, in the Control tab: a. Click the down arrow to the right of the Start button. b. Click Servicing all requests. 5) In the Start Application Assistant pane, click Yes. 6) In the Summary of Deployments pane, view the link in the State column of the row that contains 'expedition.' Wait a few minutes, then click Refresh. The expedition State column should show Active. 7) Verify that the State column for both files shows Active. 8) Logout of the Administration Console. Create an Endorsed Folder Follow the steps below to create an endorsed folder: 1) Locate the folder that contains the JDK you used when you created the WebLogic domain for Contract Management Web Services. This folder is known as <JDK_HOME>. If it does not already exist, create the following endorsed folder: <JDK_HOME>/jre/lib/endorsed. 2) In the <CM_WS_INSTALL_HOME>/endorsed folder, locate the saaj-impl.jar file 3) Copy the saaj-impl.jar file to the endorsed folder in <JDK_HOME>. 4) Restart the WebLogic domain. 24

Configuring Contract Management for a WebLogic Cluster In This Section Clustering: Configuring the Environment... 25 Clustering: Start the WebLogic Domains... 26 Clustering: Configure the Data Sources... 27 Clustering: Deploy Contract Management Web Services... 30 Clustering: Considerations for Using Contract Management Web Services in a Clustered Environment... 32 Clustering: Configuring the Environment A WebLogic Server cluster consists of multiple WebLogic Server instances running simultaneously and working together to provide increased scalability and reliability. A cluster appears to clients to be a single WebLogic Server instance. A cluster is part of a particular WebLogic Server domain, which is an interrelated set of WebLogic Server resources that are managed as a unit Using Contract Management Web Services in a clustered WebLogic environment requires that you first create a WebLogic cluster for Contract Management Web Services that contains an admin domain on an admin server and a set of managed domains on managed servers. Refer to the WebLogic documentation for information on creating a WebLogic cluster that includes an admin server and set of managed servers and domains. Then use the following procedures to configure and use the WebLogic cluster for Contract Management Web Services. Configure the Admin and Managed Servers for Contract Management Web Services 1) Make the changes that are specified in Configure the WebLogic Application Server for Contract Management Web Services on Windows to the startweblogic.cmd /sh and setdomainenv.cmd /sh files on all servers in the cluster, including the admin server. 2) Install Contract Management Web Services on the admin server. 3) On each of the managed servers, perform the following activities: a. Copy all of the files in the <domain_home>\lib folder on the admin server to the <domain_home>\lib folder of the managed server machines. b. Copy the <domain_home>\com folder on the admin server to <domain_home>\com folder of the managed server machines. 4) Create an endorsed folder on the admin server and on all managed servers. a. Copy the saaj-impl.jar file from the <CM_WS_INSTALL_HOME>/endorsed folder on the Admin server to the <JDK_HOME>/jre/lib/endorsed folder on the Admin server 25

Installing and Configuring Contract Management Web Services b. Copy the saaj-impl.jar file from the <CM_WS_INSTALL_HOME>/endorsed folder on the Admin server to the <JDK_HOME>/jre/lib/endorsed folder on each of the managed servers. 5) If you have made any changes to default templates in the htmltemplates folder, copy the changed files into the Contract Management Web Services into the htmltemplates folder. Adjust the Java Home variable on all Managed Servers If a managed domain is created with a pack and unpack of the admin domain, the SUN_JAVA_HOME and BEA_JAVA_HOME variables can revert to default values. Follow this procedure to check and correct these variables: 1) Open the setdomainenv.cmd \.sh file in a text editor on all managed servers. 2) Search for following strings and ensure that these variables are set to the correct path: Windows (Sun JDK) set SUN_JAVA_HOME= Windows (JRocket JDK) set BEA_JAVA_HOME= Linux (Sun JDK) SUN_JAVA_HOME= Linux (JRocket JDK) BEA_JAVA_HOME= Clustering: Start the WebLogic Domains 1) On the admin server, navigate to the <Contract_Management_Web_Services_Domain_Home>/bin folder and execute the following command: Windows startweblogic.cmd Linux startweblogic.sh 2) On each of the managed servers, navigate to the <Contract_Management_Web_Services_Domain_Home>/bin folder and execute the following command: Windows startmanagedweblogic.cmd <managed_server_name> http://<admin_server_address>:<admin_domain_port> Linux startmanagedweblogic.sh <managed_server_name> http://<admin_server_address>:<admin_domain_port> For example: Admin server is configured as adminserver.us.oracle.com 26

Configuring Contract Management for a WebLogic Cluster Managed servers are configured as follows: managedserver1.us.oracle.com with friendly name managed1 managedserver2.us.oracle.com with friendly name managed2 3) To start managed servers with this configuration: a. On managedserver1.us.oracle.com, execute the following command: startmanagedweblogic.cmd managed1 http://adminserver.us.oracle.com:7001 b. On managedserver2.us.oracle.com, execute the following command: startmanagedweblogic.cmd managed2 http://adminserver.us.oracle.com:7001 Clustering: Configure the Data Sources Clustering: Configure JDBC Properties for an Oracle Database Data Source Complete the following steps to configure the JDBC Data Source Properties. Note: Data Source names are case sensitive and must match the data source. 1) Login to WebLogic Admin console. 2) In the Change Center pane, click Lock & Edit. 3) In the Domain Structure pane, click Service, Data Sources. 4) In the Summary of Data Sources pane, select New, Generic Data Source. 5) In the Create a New JDBC Data Source pane: a. Set the Name field (depending on which data source your are setting up). For example, these might be: CMPROJ for the CMPROJ database EXPADMIN for the EXPADMIN database Note: JNDI field names are case sensitive, and must match the name you used for JNDI. b. Set the JNDI Name field to jdbc/<database_name>. For example, <database_name> might be: CMPROJ for the CMPROJ database EXPADMIN for the EXPADMIN database 6) Set the Database Type field to Oracle and click Next. 7) In the Database Driver field: If using Oracle 10g, select Oracle's Driver (Thin) Versions:9.0.1, 9.2.0, 10 and click Next. If using Oracle 11g, select Oracle's Driver (Thin) for Instance Connections: Versions:9.0.1, 9.2.0, 10, 11 and click Next. 8) In the Transaction Options screen: 27

Installing and Configuring Contract Management Web Services To set transaction options for a single project group: If you are configuring the Admin or P6 EPPM database, clear the Supports Global Transactions option, and click Next. If you are configuring a project database: 1. Select the Supports Global Transactions option. 2. Click the One-Phase Commit radio button. 3. Click Next. The Connection Properties dialog box displays. To set transaction options for multiple project groups: 1. Select the Supports Global Transactions option. 2. Select Emulate Two-Phase Commit. 9) In the Connection Properties screen: a. Set the Database Name field to the SID of the Oracle database. For example: ORCL. b. Set the Host Name field to <database_hostname>, where <database_hostname> is the name or IP address of the host where you installed each database. c. Set the Port field to <database_port>, where <database_port> is the port number of the host where you installed each database. d. Set the Database User Name field. You set these when you created the databases. For example: expadmin for the EXPADMIN database. cmproj for the CMPROJ database. e. Set the Password field. You set these when you created the databases. For example: expadmin for the ADMIN database. cmproj for the CMPROJ database. f. Confirm the password. g. Click Next. 10) In the Test Database Connection screen: a. Click Test Configuration to verify that connection is successful. b. Click Next. 11) In the Select Targets screen: a. Select <server_name>, where <server_name> is the target server for WebLogic. Note: When selecting target servers for datasources, the target should be "All servers in the cluster." b. Click Finish. 12) In the Change Center pane, click Activate Changes. 28

Configuring Contract Management for a WebLogic Cluster Clustering: Configure JDBC Properties for a Microsoft SQL Server Database Data Source CComplete the following steps in the JDBC Data Source Properties dialog box for each database: Once for the GROUP database. Once for the ADMIN database, also referred to as EXPADMIN. Notes: In this section, CMPROJ is used as the group database name. It is provided only as an example of a possible GROUP database name. Data Source names are case sensitive and must match the data source. 1) Login to WebLogic Admin console. 2) In the Change Center pane, click Lock & Edit. 3) In the Domain Structure pane, click Service, Data Sources. 4) In the Summary of Data Sources pane, select New, Generic Data Source. 5) In the Create a New JDBC Data Source pane: a. Set the Name field (depending on which data source your are setting up). For example, these might be: CMPROJ for the CMPROJ database EXPADMIN for the EXPADMIN database Note: JNDI field names are case sensitive, and must match the name you used for JNDI. b. Set the JNDI Name field to jdbc/<database_name>. For example, <database_name> might be: CMPROJ for the CMPROJ database EXPADMIN for the EXPADMIN database 6) Set the Database Type field to MS SQL Server and click Next. 7) In the Database Driver field, select Microsoft's MS SQL Server Driver (Type 4) Versions: 2005 and later and click Next. 8) In the Transaction Options screen: To set transaction options for a single project group: If you are configuring the Admin or P6 EPPM database, clear the Supports Global Transactions option, and click Next. If you are configuring a project database: 1. Select the Supports Global Transactions option. 2. Click the One-Phase Commit radio button. 3. Click Next. The Connection Properties dialog box displays. To set transaction options for multiple project groups: 1. Select the Supports Global Transactions option. 29

Installing and Configuring Contract Management Web Services 2. Select Emulate Two-Phase Commit. 9) In the Connection Properties screen: a. Set the Database Name field to one of the following: The Database name for the Contract Management ADMIN database. This is EXPADMIN. The Database name for the Contract Management GROUP database. This is CMPROJ. b. Set the Host Name field to <database_hostname>, where <database_hostname> is the host where you installed Microsoft SQL Server. If the SQL instance is not a default instance, set the Host Name field to <database_hostname>\<instance_name>. c. Set the Port field to <database_port>, where <database_port> is the port number of the host where you installed Microsoft SQL Server. d. Set the Database User Name field. You set these when you created the databases. For example: exp for the EXPADMIN database. exp for the CMPROJ database. e. Set the Password field. You set these when you created the databases. For example: sql for the ADMIN database. sql for the CMPROJ database. f. Confirm the password. g. Click Next. 10) In the Test Database Connection screen: a. Click Test Configuration to verify that connection is successful. b. Click Next. 11) In the Select Targets screen: a. Select <server_name>, where <server_name> is the target server for WebLogic. Note: When selecting target servers for datasources, the target should be "All servers in the cluster." b. Click Finish. 12) In the Change Center pane, click Activate Changes. Clustering: Deploy Contract Management Web Services Note: You cannot perform the steps in this procedure until after you have installed Contract Management Web Services. 1) In the WebLogic Server Administration Console, click Lock & Edit. 2) Click Deployments from the left hand pane. 3) Click Install on the Deployments dialog box. 30

Configuring Contract Management for a WebLogic Cluster 4) In the Install Application Assistant section of the right hand pane, perform the following steps: a. In the Location section, specify the path to the cmws.ear file from the <CM_WS_INSTALL_HOME> folder (For example, c:\cmwebservices_1\server\cmws.ear) and click Next. b. In the Choose targeting style section, click Install this deployment as an application, and click Next. c. In the Select deployment targets section, select the <cluster_name>, where <cluster_name> is the target cluster for WebLogic. d. Click Finish. Note: When selecting target servers for Contract Management Web Services and for datasources, the target should be "All servers in the cluster." 5) In the Settings for server section of the right hand pane, click Save 6) On 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. 7) Click Deployments from the left hand pane. 8) In the Summary of Deployments section of the right hand pane, select the cmws deployment option, click Start under Deployments, and choose Servicing all requests from the drop-down list. 9) In the Start Application Assistant in the right hand pane, click Yes to confirm that you want to start the deployment. The deployment will be pushed from Admin server to all managed servers. Adding Contract Management Web Services as a WebLogic Application To add P6 as a WebLogic application: 1) Launch the WebLogic Administration Console. Note: You can open the Administration Console via a web browser using this address: http://serverip:listenport/console. The default listenport is 7001. 2) In the Welcome window, log in using the user name and password that you created when you created your WebLogic domain. 3) In the Change Center pane of the Administration Console, click Lock & Edit. 4) In the Domain Structure pane, click Deployments. 5) In the Summary of Deployments pane, in the Control tab, click Install. 6) In the Install Application Assistant pane: a. Navigate to the <CM_WS_INSTALL_HOME>\server\ folder. b. Select the cmws.ear file. c. Click Next. 31

Installing and Configuring Contract Management Web Services 7) In the Install Application Assistant pane: a. Select Install this deployment as an application. b. Click Next. 8) In the Install Application Assistant pane: a. Click the server or cluster where you want to deploy the application. b. Click Next. 9) In the Install Application Assistant pane, click Next to accept the default options. 10) Review the configuration settings you have chosen, then click Finish to complete the installation. 11) In the Settings for cmws window, click Save. 12) Proceed to Starting the Contract Management Application in WebLogic. Starting the Contract Management Web Services Application in WebLogic To start the Contract Management application in WebLogic: 1) In the Change Center pane, click Activate Changes. 2) In the Domain Structure pane, click Deployments. 3) In the Summary of Deployments pane, select cmws. 4) In the Summary of Deployments pane, in the Control tab: a. Click the down arrow to the right of the Start button. b. Click Servicing all requests. 5) In the Start Application Assistant pane, click Yes. 6) In the Summary of Deployments pane, view the link in the State column of the row that contains 'expedition.' Wait a few minutes, then click Refresh. The expedition State column should show Active. 7) Verify that the State column for both files shows Active. 8) Logout of the Administration Console. Clustering: Considerations for Using Contract Management Web Services in a Clustered Environment Configuring the Load Balancing Refer to WebLogic documentation for information on how to configure the load balancer. Recommendations In a clustered environment, Oracle Primavera recommends that the following operations only be performed when no users (except the user performing these operations) are logged into Contract Management: Project Delete Modifying, adding, or deleting custom fields Modifying, adding, or deleting cost code definitions 32

Configuring Contract Management for a WebLogic Cluster 33

Configuring Contract Management Web Services In This Section Starting the Contract Management Administration Application... 35 Configuring Authentication Mode for Contract Management Web Services... 35 Configuring Username Token Profile Settings for Contract Management Web Services... 36 Configuring SAML Token Profile Settings for Contract Management Web Services 36 Configuring Message Protection Settings for Contract Management Web Services 37 Using LDAP with Contract Management Web Services... 38 Starting the Contract Management Administration Application Start the Contract Management Administration Application Windows 1) Locate the <CM_WS_INSTALL_HOME>\utility\CMAdminConfig folder (For example, c:\cmwebservices_1\utility\cmadminconfig). 2) Run the admincm.cmd file. 3) Enter your admin username and password on the Contract Management Administration Application Login page and click Login. Linux 1) Locate the <CM_WS_INSTALL_HOME>/utility/CMAdminConfig folder and run the dbconfigcm.sh script. 2) Run the admincm.sh script. 3) Enter your admin username and password on the Contract Management Administration Application Login page and click Login. Configuring Authentication Mode for Contract Management Web Services To set your authentication mode: 1) Open the Contract Management Administration Application. 2) Expand Web Services/Security/Authentication. 3) In the Mode field, choose the method clients use for authentication. The default is Username Token Profile. You can choose one of the following: Username Token Profile - Oracle recommends using this authentication mode. It defines how a web service client application can supply a user name and an optional password in the message request that the web service server can use to authenticate the requester's identity. 35

Installing and Configuring Contract Management Web Services SAML Token Profile - Security Assertion Markup Language (SAML) defines an XML-based mechanism for exchanging messages that contain security information in the form of assertions. Cookies - This option requires you to call the Authentication service Login operation to establish a session and obtain a cookie before you can use any other P6 web service. Note: See the P6 Web Services Programmer's Guide for more information. Configuring Username Token Profile Settings for Contract Management Web Services To set your Username Token Profile settings: 1) Open the Contract Management Administration Application. 2) Expand Web Services/Security/Authentication/Username Token Profile/Nonce. a. In the Require Nonce field, choose true to enable nonce or false to disable it. Nonce is a token that contains a random value and is used to prevent attacks. b. In the Nonce Cache Timeout field, enter the value, in the format 1d1h1m1s, for the Nonce cache timeout. The value specified indicates how long the nonce remains cached before it is deleted. The default is 600 seconds (10m). Enter anything from 5m-24d. 3) Expand Web Services/Security/Authentication/Username Token Profile/Created. a. In the Require Created field, choose true to enable the Username token timestamp or false to disable it. Requiring a Created element allows the server to determine whether the difference between two timestamps falls within an allowable window of time and can then reject any messages that exceed the window. b. In the Timeout field, enter the value, in the format 1d1h1m1s, for the Created timestamp timeout. You can specify a minimum of 300 seconds (5m). The default is 600 seconds (10m). Enter anything from 5m-24d. Configuring SAML Token Profile Settings for Contract Management Web Services To set your SAML Token Profile settings: 1) Open the Contract Management Administration Application. 2) Expand Web Services/Security/Authentication/SAML Token Profile. a. In the SAML Version field, choose the SAML version of the token. b. In the Require Signed SAML Token field, choose true to require signed SAML tokens or false to require unsigned SAML tokens. 3) Expand Web Services/Security/Authentication/SAML Token Profile/SAML Tokens. 36