71 mxprima install

Tivoli® IBM Maximo Adapter for Primavera

Installation Guide

Version 7.1

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 13.

This edition applies to version 7, release 1, modification 0 of IBM Maximo Adapter for Primavera and to allsubsequent releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2008.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Preparing for installation . . 1Configuring Primavera API on WebSphereApplication Server . . . . . . . . . . . . 1Configuring Primavera API on WebLogic Server . . 2

Chapter 2. Installing Maximo Adapter forPrimavera . . . . . . . . . . . . . . 5Enabling the product license . . . . . . . . . 5

Chapter 3. Deploying the EAR files . . . 7

Chapter 4. Configuring the adapter . . . 9Configuring connection details . . . . . . . . 9Configuring the adapter parameters . . . . . . 9Configuring logging . . . . . . . . . . . 11Enabling work location resource scheduling . . . 11

Notices . . . . . . . . . . . . . . 13Trademarks . . . . . . . . . . . . . . 14

Index . . . . . . . . . . . . . . . 17

© Copyright IBM Corp. 2008 iii

iv IBM Maximo Adapter for Primavera: Installation Guide

Chapter 1. Preparing for installation

Ensure that you meet the requirements and have the information needed to installIBM® Maximo® Adapter for Primavera.

Installation requirements

Before you install Maximo Adapter for Primavera, you must have Maximo AssetManagement 7.1 installed on the same server.

Supported versions

The following versions of Primavera products are supported:v Primavera Project Manager 6.2v Primavera Project Manager 6.1v Primavera Integration API 6.2v Primavera Integration API 6.1 Service Pack 2

Information needed for the installation

You need a Maximo administrator login.

The installation program requires access to middleware servers that are installedwith Maximo Asset Management to automate the deployment of the processsolution package. Before installing, ensure you have all the administrative user IDsand passwords for the middleware servers.

Server data backups

When you install Maximo Adapter for Primavera, the configuration and content ofyour application, database, and directory servers are modified.

Before you run the installation program, create backups of the application,database, and directory servers.

Configuring Primavera API on WebSphere Application ServerIf you use WebSphere® Application Server, make the following changes to thePrimavera Integration API before you install Maximo Adapter for Primavera. Thesechanges are needed to deploy the Maximo EAR file.

Before you begin

For local mode, the Primavera Integration API must be installed on the sameserver as the Maximo application server.

For remote mode, the Primavera Integration API client must be installed on thesame server as the Maximo application server.

© Copyright IBM Corp. 2008 1

Procedure1. From the WebSphere console, add to the Classpath field the paths to the

Primavera API files. For remote mode, enter the path to the intgclient.jar file.For local mode, enter the paths to all jar files from the Primavera API lib folder.

For: Add these paths:

Remote mode Primavera API root\clientlib\intgclient.jar.

Local mode usingPrimavera IntegrationAPI 6.2

Primavera API root\lib\activation.jar;Primavera APIroot\lib\commons-lang.jar;Primavera APIroot\lib\commons-logging.jar;Primavera APIroot\lib\intgserver.jar;Primavera APIroot\lib\jdom.jar;Primavera API root\lib\log4j.jar;Primavera API root\lib\mail.jar;Primavera APIroot\lib\ojdbc5.jar;Primavera API root\lib\serializer.jar;Primavera API root\lib\spring.jar;Primavera API root\lib\sqljdbc.jar;PrimaveraAPI root\lib\stax-api-1.0.1.jar;Primavera APIroot\lib\wstx-asl-3.1.2.jar;Primavera APIroot\lib\xalan.jar;Primavera API root\lib\xercesImpl.jar;Primavera API root\lib\xml-apis.jar;

Local mode usingPrimavera IntegrationAPI 6.1 SP2

Primavera API root\lib\activation.jar;Primavera APIroot\lib\bcprovjdk14- 119.jar;Primavera APIroot\lib\commons-lang.jar;Primavera APIroot\lib\commons-logging.jar;Primavera APIroot\lib\intgserver.jar;Primavera APIroot\lib\jdom.jar;Primavera API root\lib\k3.jar;Primavera API root\lib\log4j.jar;Primavera APIroot\lib\mail.jar;Primavera API root\lib\ojdbc14.jar;Primavera API root\lib\serializer.jar;Primavera API root\lib\spring.jar;Primavera API root\lib\sqljdbc.jar;PrimaveraAPI root\lib\xalan.jar;Primavera API root\lib\xercesImpl.jar;Primavera API root\lib\xml-apis.jar

2. For local mode, enter the following in the Generic JVM arguments field:-Dprimavera.bootstrap.home=Primavera API root

3. Set the API URL field on the Labor record to point to the Primavera IntegrationAPI URL.v For remote mode, enter the computer name and port for the API URL, in the

form pcname:port. The default port is 9099.v For local mode, enter localhost.

Configuring Primavera API on WebLogic ServerIf you use BEA WebLogic Server, make the following changes to the PrimaveraIntegration API before you install Maximo Adapter for Primavera. These changesare needed to deploy the Maximo EAR file.

Before you begin

For local mode, the Primavera Integration API must be installed on the sameserver as the Maximo application server.

2 IBM Maximo Adapter for Primavera: Installation Guide

For remote mode, the Primavera Integration API client must be installed on thesame server as the Maximo application server.

About this task

For this procedure, use the correct file extension and slash for your operatingsystem.

Procedure1. Using a text editor, open the startWebLogic file in the BEA

dir\user_projects\domains\Maximo Server directory.2. Search for set CLASSPATH=.3. Add the paths to the Primavera API files between the equal sign and

%SAVE_CLASSPATH%. For remote mode, add the path to the intgclient.jar file.For local mode, add the paths to all jar files from the Primavera API lib folder.

For: Add these paths:

Remote mode Primavera API root\clientlib\intgclient.jar;

Local mode usingPrimavera IntegrationAPI 6.2

Primavera API root\lib\activation.jar;Primavera APIroot\lib\commons-lang.jar;Primavera APIroot\lib\commons-logging.jar;Primavera APIroot\lib\intgserver.jar;Primavera APIroot\lib\jdom.jar;Primavera API root\lib\log4j.jar;Primavera API root\lib\mail.jar;Primavera APIroot\lib\ojdbc5.jar;Primavera API root\lib\serializer.jar;Primavera API root\lib\spring.jar;Primavera API root\lib\sqljdbc.jar;PrimaveraAPI root\lib\stax-api-1.0.1.jar;Primavera APIroot\lib\wstx-asl-3.1.2.jar;Primavera APIroot\lib\xalan.jar;Primavera API root\lib\xercesImpl.jar;Primavera API root\lib\xml-apis.jar;

Local mode usingPrimavera IntegrationAPI 6.1 SP2

Primavera API root\lib\activation.jar;Primavera APIroot\lib\bcprovjdk14- 119.jar;Primavera APIroot\lib\commons-lang.jar;Primavera APIroot\lib\commons-logging.jar;Primavera APIroot\lib\intgserver.jar;Primavera APIroot\lib\jdom.jar;Primavera API root\lib\k3.jar;Primavera API root\lib\log4j.jar;Primavera APIroot\lib\mail.jar;Primavera API root\lib\ojdbc14.jar;Primavera API root\lib\serializer.jar;Primavera API root\lib\spring.jar;Primavera API root\lib\sqljdbc.jar;PrimaveraAPI root\lib\xalan.jar;Primavera API root\lib\xercesImpl.jar;Primavera API root\lib\xml-apis.jar:

For example: set CLASSPATH=Primavera API root\clientlib\intgclient.jar;%SAVE_CLASSPATH%

4. For local mode:a. Search for Dweblogic.Name=%SERVER_NAME%.b. Add the following JVM argument at the end of the line, as follows:

Dweblogic.Name=%SERVER_NAME% -Dprimavera.bootstrap.home=Primavera APIroot

5. Save and close the file.

Chapter 1. Preparing for installation 3

6. Set the API URL field on the Labor record to point to the Primavera IntegrationAPI URL.v For remote mode, enter the computer name and port for the API URL, in the

form pcname:port. The default port is 9099.v For local mode, enter localhost.


Chapter 2. Installing Maximo Adapter for Primavera

Install and deploy Maximo Adapter for Primavera through the process solutioninstallation program.

Before you beginv If you use IBM WebSphere Application Server, ensure that the middleware

servers are started. Start all middleware servers before you run the installationprogram. The installation program attempts to connect to the middlewareservers by using the middleware login information that you specify.

v If you use BEA WebLogic Server, ensure that the application server(MAXIMOSERVER) is stopped. If the application server is running, stop theserver and wait a few minutes before you start the installation program. If theapplication server is not stopped, the installation process stops.

Procedure1. Insert the Maximo Adapter for Primavera DVD in the DVD drive. The

launchpad starts automatically. If the Windows® autorun feature is disabled,you can start the launchpad by running the launchpad.exe program from theroot directory of the product DVD.

2. In the Welcome window, select the language for the installation, then clickInstall the product on the left side of the screen.

3. Click the link under 1. Install IBM Maximo Adapter for Primavera.4. In the next installation windows, click OK or Next.5. In the Software License Agreement window, select I accept the terms in the

license agreement, then click Next.6. In the Middleware Login Information window, enter the login credentials for

the middleware servers, then click Next.7. In the Package Options windows, clear the Supported Package Options check

boxes to have the EAR files redeployed and the Maximo database updated bythe installation program.

8. In the Pre-install Summary window, click Next. The Deployment Progresswindow shows the progress of the installation.

9. When the installation is complete, in the Package Successfully Deployedwindow, click Done.

Enabling the product licenseYou must enable the license before you can use the product.

Procedure1. From the launchpad, click the link under Enable IBM Maximo Adapter for

Primavera License for usage.2. Follow the steps in the wizard. When the installation is complete, in the

Package Successfully Deployed window, click Done.


What to do next

If you use BEA WebLogic Server, manually redeploy the EAR files. Otherwise,configure the adapter.


Chapter 3. Deploying the EAR files

If you use BEA WebLogic Server, you must deploy the EAR files from theWebLogic Server Console after you install Maximo Adapter for Primavera.Deploying the EAR files starts the application server.

Before you begin

To view the WebLogic Server Console, you must have a Java™ Virtual Machineinstalled.

Procedure1. Start the BEA WebLogic Server.

a. Change to the mydomain directory: drive_letter:\BEA_installation_location\user_projects\domain\mydomain (Windows) or /home/mxadmin/bea/user_projects/domains/mydomain (UNIX®).

b. Enter startWebLogic.cmd (Windows) or ./startWebLogic.sh (UNIX).Message ″Server started in RUNNING mode″ displays when the WebLogicServer starts running.

2. Start the Administration Console by typing the following URL in the addressbar of your browser : http://<host name>:7001/console

3. Follow the instructions in the WebLogic Console help to deploy maximo.earand then maximohelp.ear.


Chapter 4. Configuring the adapter

Configure the parameters for connection with Primavera. Optionally, configureMaximo Adapter for Primavera parameters and logging for your environment, andenable work location resource scheduling to work with multiple locations.

Configuring connection detailsConfigure Primavera connection details in the Labor (PV) application in Maximo.Any Maximo labor record with the Primavera Connection Details fields completedcan transfer data between Maximo and Primavera P6.

Procedure1. In Maximo, select Go To → Administration → Resources → Labor (PV), then

select the Primavera tab.2. In the User Name and Password fields, specify the credentials that the adapter

uses to sign into Primavera P6. This user name must exist in the Primavera P6application and must have Primavera API privileges.

3. In the API URL field, type the URL of the RMI Primavera API server. Theformat is: <hostname>:<port>, where <hostname> can be localhost, the remotehost name, or the host IP address in dotted decimal format.

4. In the Primavera DB Name field, type the name of the database to use withPrimavera P6.

5. To test the connection, click the Test Connection button.

Configuring the adapter parametersConfigure the Maximo Adapter for Primavera parameters in Maximo as requiredfor your environment.

Procedure1. In Maximo, select Go To → System Configuration → Platform Configuration →

System Properties.2. Select the parameter that you want to configure, then type its value in the text

box. You can configure the following parameters:

Parameter Description Valid values

mxe.primavera.status.notstarted Determines theMaximo work orderstatuses that aretranslated into aPrimavera activitystatus of notstarted.

One or more strings of<Maximo_status>.Default: <CAN><WAPPR><WMATL><WPCOND><WSCH><APPR>

mxe.primavera.status.inprogress Determines theMaximo work orderstatuses that aretranslated into aPrimavera activitystatus of inprogress.

One or more strings of<Maximo_status>.Default: <INPRG><HISTEDIT>


Parameter Description Valid values

mxe.primavera.status.completed Determines theMaximo work orderstatuses that aretranslated into aPrimavera activitystatus of completed.

One or more strings of<Maximo_status>.Default: <COMP><CLOSE>

mxe.primavera.nodesc Determines thedescription of awork order whenno description isprovided. You canalso use thisparameter to namea project when noproject descriptionis provided.

Text enclosed in doublequotation marks.Default: “NO DESCRIPTION”

mxe.primavera.cache.validatefreq Indicates thefrequency, in days,to run a fullvalidation of thePLUSVCACHEtable. The validationoccurs the first timean export or importoperation isperformed after thenumber of daysspecified. Thisparameter is used toensure thesynchronization ofresource recordsbetween Maximoand Primavera.

Numeric value. Default: 7

mxe.primavera.leadingzero Indicates whetherleading zeros onwork ordernumbers areremoved when thework orders areexported toPrimavera.

Y (default) - The leading zerosare removed.N - The leading zerosare not removed.

mxe.primavera.exportcalendars Indicates whetherMaximo calendarsare exported toPrimavera.

Y (default) - Maximo calendarsare exported.N - Maximo calendarsare not exported.

mxe.system.globallog Indicates whetherthe user name ofeach user is loggedbefore messagesrelated to that userin the adapter logfile.

Y (default) - The user nameis not logged.N (default) - The user nameis logged.


Configuring loggingConfigure logging for Maximo Adapter for Primavera using the standard Maximologging mechanism.

For information about logging configuration, refer to the Maximo documentation.

Enabling work location resource schedulingIf work location resource scheduling is enabled, you can define, schedule, andmanage resources for multiple sites.

About this task

Enabling work location resource scheduling affects all organizations, sites, andprojects.

To enable work location resource scheduling:

Procedure1. In Maximo, select Go To → Administration → Organizations (PV).2. On the Select Action menu, select Primavera Options, then System Options.3. Select the Schedule by Work Location check box and click OK.4. If you want to specify the work location prefix that is added to all craft records

exported to Primavera P6, complete the following steps for each location Thework location prefix must be unique within an organization. If you do notspecify a prefix, the site ID of the work order is added to the craft records.a. Select Assets → Locations.b. Retrieve the location record.c. On the Location tab, type a value in the Work Location Prefix field.d. Save the record.

Chapter 4. Configuring the adapter 11

Notices

This information was developed for products and services offered in the U.S.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information about theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user’s responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing 2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.


Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

U.S.A.IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. If these and other IBM trademarked terms are marked on their firstoccurrence in this information with a trademark symbol (® or ™), these symbolsindicate U.S. registered or common law trademarks owned by IBM at the time thisinformation was published. Such trademarks may also be registered or commonlaw trademarks in other countries. A current list of IBM trademarks is available onthe Web at “Copyright and trademark information” at http://www.ibm.com/legal/copytrade.shtml.

Microsoft®, Windows, Windows NT®, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems,Inc. in the United States, other countries, or both.


http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, and service names may be trademarks or service marksof others.

Notices 15

Index

Cconfiguration 9connection details 9

EEAR deploying 7

Iinstallation

information needed 1preparation 1requirements 1using PSI 5

Llicense enablement 5logging 11

Pparameters 9preparation for installation 1Primavera API configuration

on WebLogic 2on WebSphere 1

PSI (process solution installer)installation 5

Rrequirements

installation 1resource scheduling 11

Wwork location resource scheduling 11


��

Printed in USA

71 mxprima install

Documents