Oracle Utilities Work and Asset Management Integration to Primavera P6 Enterprise Project Portfolio Management

Installation Guide Oracle Utilities Work and Asset Management v1.9.1 Primavera P6 Enterprise Project Portfolio Management v8.2

Release 11.1.0.0.0

E39818-01

March 2013

Oracle Utilities Work and Asset Management Integration to Primavera P6 Enterprise Project Portfolio Management, Release 11.1.0.0.0

E39818-01

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

Primary Author: Oracle Corporation

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

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

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

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

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

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

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

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

1 Overview

This guide describes the installation steps that must be completed before Oracle Utilities Work and Asset Management (WAM) can be integrated with Primavera P6 Enterprise Project Portfolio Management (EPPM).

Additional Resources

For more information refer to the following documents:

Task

Description

Oracle Utilities Work and Asset Management Integration to Primavera P6 Enterprise Project Portfolio Management Implementation Guide

Same folder as this document, with the distribution for this product.

Primavera P6 Enterprise Project Portfolio Management - Application version V8.2

Refer to Primavera P6 Enterprise Project Portfolio Management Installation documentation located on the Oracle Software Delivery Cloud at:

https://edelivery.oracle.com

Abbreviations

Abbreviations used in this guide are listed below:

•

P6 EPPM - Primavera Enterprise Project Portfolio Management

•

WAM - Oracle Utilities Work and Asset Management

•

DDL - Data Definition Language

•

MDS - Metadata Store

•

AIA - Oracle Application Integration Architecture

•

EBF - Enterprise Business Flow

•

SOA-Oracle Service-Oriented Architecture

1 Installation

The following sections describe the settings and requirements for a successful installation of the Oracle Utilities Work and Asset Management Integration (WAM) to Primavera P6 Enterprise Project Portfolio Management (EPPM).

Complete these installation steps before configuring the applications for integrated functionality:

•

Integration Pack Software Requirements

•

Pre-Installation Tasks

•

Installation Steps

•

Installing the Integration

•

Post-Installation Checklist

Integration Pack Software Requirements

The following software and platforms must be installed and configured before installing the integration pack.

For complete details, refer to product-specific installation guides.

Note: This integration does not require the AIA Foundation Pack to be installed.

Participating Applications

•

Oracle Utilities Work and Asset Management - Application version 1.9.1 installed on an Oracle database.

•

Primavera P6 Enterprise Project Portfolio Management - Application version 8.2 installed on an Oracle database.

Oracle SOA/Weblogic Server

•

Oracle SOA Suite 11g with Enterprise Manager 11.1.1.6 on Weblogic Server 11g (10.3.6).

Integration Pack Software Requirements

The following software and platforms must be installed and configured before installing the integration pack.

For complete details, refer to product-specific installation guides.

Note: This integration does not require the AIA Foundation Pack to be installed.

Participating Applications

•

Oracle Utilities Work and Asset Management - Application version 1.9.1 installed on an Oracle database.

•

Primavera P6 Enterprise Project Portfolio Management - Application version 8.2 installed on an Oracle database.

Oracle SOA/Weblogic Server

•

Oracle SOA Suite 11g with Enterprise Manager 11.1.1.6 on Weblogic Server 11g (10.3.6).

Integration Pack Software Requirements

The following software and platforms must be installed and configured before installing the integration pack.

For complete details, refer to product-specific installation guides.

Note: This integration does not require the AIA Foundation Pack to be installed.

Participating Applications

•

Oracle Utilities Work and Asset Management - Application version 1.9.1 installed on an Oracle database.

•

Primavera P6 Enterprise Project Portfolio Management - Application version 8.2 installed on an Oracle database.

Oracle SOA/Weblogic Server

•

Oracle SOA Suite 11g with Enterprise Manager 11.1.1.6 on Weblogic Server 11g (10.3.6).

Pre-Installation Tasks

The following tasks must be completed before installing the integration:

•

Ensure that Oracle SOA Suite 11gR1 PS5 with Enterprise Manager is installed and running.

•

Login to the WebLogic Server console to confirm there are no changes in the Pending Activation status.

•

Start the Node Manager, if not already running.

•

Restart Enterprise Manager and WebLogic Admin server.

•

Make sure that WebLogic Admin server, SOA server, and Node Manager are up and running.

Installation Steps

Complete the following installation steps:

1.

Download the installation zip file from Oracle Software Delivery Cloud ( https://edelivery.oracle.com).

2.

Extract the zip file to get the installation folder. This folder includes subfolders such as bin, config, Install, MDS-Artifacts, and services as shown in the diagram below:

3.

Set the following environment variables for Unix and Windows OS:

Variable

Example

Unix/Linux and Windows OS

SOA_HOME

XXX/Middleware/Oracle_SOA1

ORACLE_HOME

XXX/Middleware/Oracle_SOA1

MW_HOME

XXX/Middleware

WL_HOME

XXX/Middleware

PRODUCT_HOME

Directory where WAM-Primavera.zip is extracted.Example:

Unix/Linux: PRODUCT_HOME=/slot/oracle/WAM-Primavera

Windows: PRODUCT_HOME=D:\Oracle\WAM-Primavera

Note: The syntax for PRODUCT_HOME changes depending on whether you are installing on Linux or Windows. The following sections refer to this as $PRODUCT_HOME in Linux and it should be referred to as %PRODUCT_HOME% in Windows. If you are using Windows, replace $PRODUCT_HOME with %PRODUCT_HOME% throughout the document.

The following commands (setWLSEnv.sh on Linux and setWLSEnv.bat on Windows) set the environment variables used for executing the installation scripts:

•

Unix/ Linux:source "${WL_HOME}/wlserver_10.3/server/bin/setWLSEnv.sh"

•

Windows:cd %WL_HOME%\wlsserver_10.3\server\bin\setWLSEnv.cmd

4.

Modify the $PRODUCT_HOME/config/InstallProperties.xml file and ensure that the values entered are relevant to the server where the integration product has to be installed. Use a text editor to update the InstallProperties.xml file. Login to the WebLogic console to cross verify the values being entered for these properties, as the build may fail due to inappropriate values.

5.

Modify the $PRODUCT_HOME /MDS-Artifacts/WAM-Primavera/AIAMetaData/config/ConfigurationProperties.xml. Locate the following properties and replace them with the appropriate end point URLs of Primavera.

Example:

<Property name="P6.CreateProj.EndPoint">http://adc2xxxx.us.oracle.com:8206/p6ws/services/ImportService</Property>

<Property name="P6.UpdateProj.EndPoint">http://adc2xxxx.us.oracle.com:8206/p6ws/services/ImportService</Property>

<Property name="P6.RetrieveProj.EndPoint">http://adc2xxxx.us.oracle.com:8206/p6ws/services/ExportService</Property>

<Property name="Primavera.Resource.EndPoint">http://adc2xxxx.us.oracle.com:8206/p6ws/services/ResourceService</Property>

<Property name="Primavera.Rate.EndPoint">http://adc2xxxx.us.oracle.com:8206/p6ws/services/ResourceRateService</Property>

InstallProperties.xml, ConfigurationProperties.xml files are XML files. Ensure you follow XML editing standards while editing these files. All XML elements need to be closed properly. XML element in InstallProperties.xml file does not contain any attribute.

The table below lists the properties available in the InstallProperties.xml file along with their usage. The default values are specified wherever applicable.

Note: Do not delete the WAM-Primavera directory. This directory will be used as the download location for patches.

For a Windows installation, when updating any of the properties listed in the table below, add the "/" to the path. For example: C:/WAM-Primavera

Note : If the installation fails due to of incorrect values defined in the installProperties.xml file, run uninstall, populate the correct values, and then run install again.

Property

Description

Example

SOA Information

<config>

<modulename>

Name of the integration module.

Default: WAM-Primavera

Do not change this value.

<config> <WAM-Primavera>

<WorkFlow.Notification>

<from.emailid>

Email ID which should be set in the "From" property of Workflow Notification bean.

WAM Application Information

<WAM>

<ApplicationUsername>

<ApplicationPassword>

Primavera Application Information

<Primavera>

<ApplicationUsername>

<ApplicationPassword>

<config>

<SOA>

Admin Server Information

<AdminServer>

<hostname>

Host name of the server where admin server hosting SOA suite is installed.

adminserver.example.oracle.com

<portnumber>

Port number the admin server (hosting SOA suite) is listening to.

7043

<servername>

Admin server name (hosting SOA suite)

AdminServer

<username>

User name used to log in as an Admin server (hosting SOA suite) administrator.

webLogic

<password>

Password used to log in as an Admin server (hosting SOA suite) administrator.

<domainname>

WebLogic domain name hosting SOA suite.

soa_domain

Managed Server Information

<ManagedServer>

<hostname>

Host name of the server where managed server (hosting SOA suite) is installed.

managedserver.example.oracle.com

<portnumber>

Port number the managed server (hosting SOA suite) is listening to.

8043

<servername>

Managed server name (hosting SOA suite)

Managedserver1

<username>

User name used to log in to managed server (hosting SOA suite) as an administrator.

webLogic

<password>

Password used to log in to managed server (hosting SOA suite) as an administrator.

MDS DB information

<mdsconfig>

<mdsdbusername>

User name used to log in to MDS schema.

XXX_MDS

<mdsdbuserpassword>

Password used to log in to MDS schema.

<mdsdbhostname>

Host name of the server hosting the database containing MDS schema.

db.hostname.oracle.com

<mdsdbportnumber>

Port number of the database containing MDS schema.

1521

<mdsdbsid>

SID of the database containing MDS schema.

SID

Schema Information

<config>

<WAM-P6>

<dba.dbusername>

User name used to log in as a database administrator (DBA).

This database hosts the schema required for WAM-Primavera integration.

System

<dba.dbuserpassword>

Password used to log in as a database administrator (DBA).

This database hosts the schema required for WAM-Primavera integration.

<dbusername>

User name used to log in to WAM-Primavera schema for WAM-Primavera integration.

This user can be automatically created by the install (set dbuser.createflag to true) or manually outside the install process.

Example : WAMPRIMAVERA

<dbuserpassword>

Password used to log in to WAM-Primavera schema for WAM-Primavera integration.

<dbuser.createflag>

Flag specifying whether to create a new schema or use the existing schema for WAM-Primavera integration.

If the schema is created manually outside of the installation process, then set this value to "false". Else, set the value to "true", if the installation script should automatically create the schema.

Valid values: true or false (this is case sensitive)

true

<dbhostname>

Database host name used for WAM-Primavera integration.

db.sample.oracle.com

<dbportnumber>

Database port number used for WAM-Primavera integration.

1521

<dbsid>

Database SID used for WAM-Primavera integration.

SID

Note : If the dbuser.createflag is set to false, then the schema needed for WAM-Primavera integration error handling will not be automatically created by the install. In such a case, the schema needs to be created manually before running the install. When creating the user manually, grant access rights and resource to the user.

Also note the following:

•

$PRODUCT_HOME/Install/utilant folder contains all the ant build scripts

•

$PRODUCT_HOME/bin/InstallBuild.xml is used to install WAM-Primavera integration code

•

$PRODUCT_HOME/bin/UnInstallBuild.xml is used to uninstall WAM-Primavera integration code

•

$PRODUCT_HOME/bin/DeployUndeployUtility.xml is used to deploy/ undeploy individual composite/ MDS folder and then restart the managed server.

Note: The installation and uninstallation process may take several minutes or more to complete. Stand by until the install and uninstall process is finished.

Installing the Integration

After setting the environment variables, open the Command prompt window and execute the following installation scripts in Linux and Windows respectively.

•

Linux

cd $PRODUCT_HOME/bin

ant -f InstallBuild.xml Install

-DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml -l Installation_date.log

•

Windows

cd %PRODUCT_HOME%\bin

ant -f InstallBuild.xml Install

-DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml -l Installation_date.log

During execution, the following tasks are performed to complete the installation process:

•

Creates database objects required for the WAM-Primavera module.

•

Creates JDBC Data Source for the WAM-Primavera Module.

•

Deploys DbAdapter_WAMPRIMAVERA.rar file that contains database outbound connections for middleware resources.

•

Updates MDS repository with all the artifacts.

•

Creates the application partition where the composites are going to be deployed. For example: WAM-Primavera

•

Compiles and then deploys all the composites to the Enterprise Manager.

Post-Installation Checklist

Post-installation checklist includes the following:

•

Verifying JDBC Configuration

•

Verifying Composites in the Enterprise Manager

•

Configuring Edge Applications

After running the installation scripts, you must complete the following steps to finish the installation:

1.

Restart the WebLogic Admin server and the SOA server.This task activates the processes that require a restart after installation and ensures that the installation of all artifacts is successful.

2.

Review the logs under $WL_HOME/user_projects/domains/soa_domain/servers/soa_server1/logs to check for deployment errors.

3.

Verify that all JDBC resources were created at the time of installation.

4.

Verify composites in the Enterprise Manager.

Note : If any of the composites is not deployed during installation due to environment-specific issues on Windows, try deploying the same composite using DeployUndeployUtility.xml. Refer to chapter Individual Composites for complete details.

Verifying JDBC Configuration

Perform the following steps for verifying JDBC configuration:

1.

Open the weblogic Admin Console and navigate to Home > Deployments.

2.

Verify if DbAdapter_WAMPRIMAVERA.rar is deployed, and status is Acitve.

Verifying Composites in the Enterprise Manager

Verify that the WAM-Primavera partition was created with all the composites deployed.

Perform the following steps:

1.

Login to the Enterprise Manager console.

2.

Expand Farm_soa_domain > soa > soa-infra > WAM-Primavera partition.

3.

Verify that all composites are deployed and are in an active state.

Configuring Edge Applications

Configure Oracle Utilities Work and Asset Management and Primavera P6 Enterprise Project Portfolio Management installation according to the guidelines in the Oracle Utilities Work and Asset Management Integration to Primavera P6 Enterprise Project Portfolio Management Implementation Guide.

1 Individual Composites

This section describes how to deploy and undeploy individual composites for incremental builds or patches and includes the following:

•

Undeploying Composites

•

Deploying Individual Composites

Undeploying Composites

If the composite being deployed involves changes made to the MDS artifacts, you must first undeploy the composite.

Perform the following steps:

1.

Open the command prompt window and execute the following commands for Linux and Windows respectively as shown below:

•

Linux:

cd $PRODUCT_HOME/bin

ant -f $PRODUCT_HOME/bin/DeployUndeployUtility.xml -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml UnDeployComposite

•

Windows:

cd %PRODUCT_HOME%\bin

ant - f %PRODUCT_HOME%/bin/DeployUndeployUtility.xml -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml UnDeployComposite

2.

Validate the following parameters when prompted with default values during deployment. Press ENTER to use the default prompted value.

•

Composite Name : Indicates the name of the composite to be undeployed to SOA server. This parameter does not have a default value.

•

Composite folder location : Indicates the folder name should be an absolute path, beginning with <PRODUCT_HOME>/services/industry/Utilities/<EBF/utility>.For example: If you are planning to undeploy the composite from <PRODUCT_HOME>/services/industry/Utilities/EBF, then pass <PRODUCT_HOME>/services/industry/Utilities/EBF to this property.

The default value for this property is %PRODUCT_HOME%/services/industry/Utilities/EBF, as most of the business-specific composites reside in this folder.

•

Partition Name : Indicates the SOA partition name from where the composite should be undeployed.

3.

Enter the composite name to be undeployed from the SOA partition.

Deploying Individual Composites

Deploy individual composites by performing the following steps:

1.

Open a Command prompt and execute the following commands for Linux and Windows respectively as shown below:

•

Linux:

cd $PRODUCT_HOME/bin

ant -f $PRODUCT_HOME/bin/DeployUndeployUtility.xml -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml DeployComposite

•

Windows:

cd %PRODUCT_HOME%\bin

ant -f %PRODUCT_HOME%/bin/DeployUndeployUtility.xml -DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml DeployComposite

2.

Validate the following parameters when prompted with default values during deployment. Press ENTER to use the default prompted value.

•

Composite Name : Name of the composite to be deployed to SOA server. This parameter does not have a default value.

•

Composite folder location : The folder name should be an absolute path beginning with %PRODUCT_HOME%/services/industry/Utilities/EBF/. For example: If you are planning to deploy the composite from%PRODUCT_HOME%/services/industry/Utilities/EBF, then pass %PRODUCT _HOME%/services/industry/Utilities/EBF to this property

3.

If you are planning to deploy the composite from Error Handling, then enter the following command:

% PRODUCT_HOME%/services/industry/Utilities/Utility

The default value for this property is %PRODUCT_HOME%/services/industry/Utilities/EBF. Most of the business-specific composites reside in this folder.

•

Partition Name : Indicates the SOA partition name to which the composite should be deployed. Enter the composite name to be deployed from the partition. For example: OUWAMP6CreateProjectEBF

Refer to Verifying Composites in the Enterprise Manager section for details regarding composites for WAM-Primavera P6 EPPM.

1 MDS Folders

This section describes how to deploy and undeploy individual MDS folders for incremental builds or patches.

The following topics are discussed here:

•

Undeploying the MDS Folder

•

Deploying the MDS Folder

Undeploying the MDS Folder

To undeploy a particular folder from MDS, execute the following commands, and then, pass the folder name to be undeployed.

1.

Open a Command prompt window and execute the following commands for Linux and Windows respectively as shown below. These commands undeploy a folder under $PRODUCT_HOME/MDS-Artifacts from the MDS repository.

•

Linux:

cd $PRODUCT_HOME/bin

ant -f $PRODUCT_HOME/bin/DeployUndeployUtility.xml -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml UnDeployMDS

•

Windows:

cd %PRODUCT_HOME%\bin

ant -f %PRODUCT_HOME%/bin/DeployUndeployUtility.xml -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml UnDeployMDS

2.

Validate the following parameters when prompted with default values during undeployment. Press ENTER to use the default prompted value.

•

SOA Server Hostname : Indicates the host name of the server hosting the SOA server. By default, it selects the managed server host name which is passed as InstallProperties property in ant command.

•

SOA Server Portnumber : Refers to the port number of the server hosting the SOA server. By default, it selects the managed server port number which is passed as InstallProperties property in ant command.

•

SOA Server Username : Indicates the user name used for connecting to the SOA server. By default, it selects the managed server user name which is passed as InstallProperties property in ant command.

•

SOA Server Password : Indicates the password used for connecting to the SOA server. By default, it selects the managed server password which is passed as InstallProperties property in ant command.

•

MDS Folder Name : Name of the folder to be undeployed from the MDS repository.The folder name should be a relative path inside: %PRODUCT_HOME%/MDS-Artifacts, beginning with WAM-Primavera.For example: To undeploy %PRODUCT_HOME%/MDS-Artifacts/WAM-Primavera/AIAMetaData/dvm pass WAM-Primavera/AIAMetaData/dvm as the MDS folder name.

Note: This command does not support file-level undeployment. It is used only for folder-level undeployment.

Deploying the MDS Folder

To Deploy the MDS folder, perform the following steps:

1.

Open a Command prompt window and execute the following commands in Linux and Windows respectively as shown below:

•

Linux:

cd $PRODUCT_HOME/bin

ant -f $PRODUCT_HOME/bin/DeployUndeployUtility.xml -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml DeployMDS

•

Windows:

cd %PRODUCT_HOME%\bin

ant -f %PRODUCT_HOME%/bin/DeployUndeployUtility.xml -DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml DeployMDS

2.

Validate the following parameters when prompted with default values during deployment. Press ENTER to use the default prompted value.

•

SOA Server Hostname : Indicates the host name of the server hosting the SOA server. By default, it selects the managed server host name which is passed as InstallProperties property in ant command.

•

SOA Server Portnumber : Refers to the Port number of the server hosting the SOA server. By default, it selects the managed server port number which is passed as InstallProperties property in ant command.

•

SOA Server Username : Indicates the user name used to connect to the SOA server. By default, it selects the managed server user name which is passed as InstallProperties property in ant command.

•

SOA Server Password : Indicates the password used to connect to the SOA server. By default, it selects the managed server password which is passed as InstallProperties property in ant command.

•

MDS Folder Name : Indicates the name of the folder to be deployed from the MDS repository. The folder name should be a relative path inside %PRODUCT_HOME%/MDS-Artifacts. MDS Artificats is a subfolder located inside the WAM-Primavera folder and it contains all the files that can be deployed in the MDS repository.

•

DVM changes : When new DVM values are added to the DVM file(s), the DVM folder must be updated in the MDS repository. This command deploys the changed file(s) as well as the whole DVM folder. Enter WAM-Primavera/AIAMetaData/dvm as the MDS folder name. This deploys the whole DVM folder in MDS.

•

Custom schema changes : If custom elements are added to the WAM or Primavera P6 schema or both, the ApplicationObjectLibrary folder must be updated in the MDS repository. Enter WAM-Primavera/AIAMetaData/ApplicationObjectLibrary to deploy the whole WAM and Primavera schema folders. If you want to deploy only the WAM schema folder or change OUWAM, then enter WAM-Primavera/AIAMetaData/ApplicationObjectLibrary/OUWAM. To deploy the Primavera schema folder or change Primavera, enter WAM-Primavera/AIAMetaData/ApplicationObjectLibrary/Primavera.

•

Concrete WSDL changes for extensions : If extension services need to be called by a process and the concrete WSDL is updated, then the ExtensionServiceLibrary folder must be updated in the MDS repository. Enter WAM-Primavera/AIAMetaData/ExtensionServiceLibrary to deploy the whole WAM and Primavera extension service library folders.

Note : This command does not support file-level deployment. Use it to perform only folder-level deployment.

1 Restarting the SOA Managed Server

This section describes how to restart the WebLogic managed server hosting the Service-Oriented Architecture (SOA) suite.

Perform the following steps:

1.

Open a Command prompt window and execute the following commands in Linux and Windows:

•

Linux:

cd $PRODUCT_HOME/ cd $PRODUCT_HOME/bin

ant -f $PRODUCT_HOME/bin/DeployUndeployUtility.xml -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml RestartManagedServer

•

Windows:

cd %PRODUCT_HOME%\bin

ant -f %PRODUCT_HOME%/bin/DeployUndeployUtility.xml -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml RestartManagedServer

2.

Validate the following parameters when prompted with default values during deployment. Press ENTER to use the default prompted value.

•

Admin Server Hostname : Indicates the host name of the server hosting the Admin server. By default, it selects the Admin Server host name, which is passed as InstallProperties property in ant command.

•

Admin Server Portnumber : Refers to the Port number of the server hosting Admin server. By default, it selects the Admin Server port number, which is passed as InstallProperties property in ant command.

•

Admin Server Username : Indicates the user name used to connect to the Admin server. By default, it selects the Admin Server user name, which is passed as InstallProperties property in ant command.

•

Admin Server Password : Indicates the password used to connect to the Admin server. By default, it selects the Admin Server password, which is passed as InstallProperties property in ant command.

•

Managed Server Name to be restarted : The default value is selected from the InstallProperties property.

1 Uninstalling the Integration

To uninstall the integration, perform the following steps:

1.

Restart the WebLogic Admin server and the SOA server.

2.

Set the environment variables as mentioned in the section Installation Steps .

3.

Open a Command prompt window and execute the following commands in Linux and Windows respectively:

•

Linux:

cd $PRODUCT_HOME/bin

ant -f UnInstallBuild.xml UnInstall -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml -l UnInstall.log

•

Windows:

cd %PRODUCT_HOME%\bin

ant -f UnInstallBuild.xml UnInstall -DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml -l UnInstall.log

The above commands perform the following tasks for the WAM-Primavera integration:

•

Undeploys all composites from the Enterprise Manager partition

•

Deletes the partition

•

Undeploys MDS artifacts

•

Undeploys database outbound connection pool

•

Deletes JDBC data source for the Error Handling module

•

Drops database objects created for the Error Handling module

Note: After a successful uninstall, all the JDBC resources and WAM-Primavera partitions created during installation are deleted.