Installation Guide. SAP xapp Resource and Portfolio Management (xrpm) 4.0 Java Component powered by SAP NetWeaver

Transcription

1 Installation Guide SAP xapp Resource and Portfolio Management (xrpm) 4.0 Java Component powered by SAP NetWeaver Document Version 1.00 October, 2005

2 SAP AG Neurottstraße Walldorf Germany T +49/18 05/ F +49/18 05/ Copyright 2004 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. SAP Library document classification: PUBLIC Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. Documentation in the SAP Service Marketplace You can find this documentation at the following Internet address: service.sap.com/instguides SAP Library document classification: PUBLIC

3 Terms for Included Open Source Software This SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and conditions shall apply. This software was developed using ANTLR. e. The Customer may distribute original or modified STLport sources, provided that: The conditions indicated in the above permission notice are met; The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met: SAP License Agreement for STLport SAP License Agreement for STLport between SAP Aktiengesellschaft Systems, Applications, Products in Data Processing Neurottstrasse Walldorf Germany ( hereinafter: SAP ) and you ( hereinafter: Customer ) Copyright 1994 Hewlett-Packard Company Copyright 1996,97 Silicon Graphics Computer Systems, Inc. Copyright 1997 Moscow Center for SPARC Technology. Copyright 1999,2000 Boris Fomitchev Copyright 2001 SAP AG Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. 1. Subject Matter of the Agreement a. SAP grants Customer a non-exclusive, non-transferable, royalty-free license to use the STLport.org C++ library (STLport) and its documentation without fee. b. By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this Agreement. c. The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. d. Customer shall maintain the following copyright and permission notices on STLport sources and its documentation unchanged: Copyright 2001 SAP AG Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC

4 Technology makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. SAP makes no representations about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications. 2. Support and Maintenance SAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall be not included. All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and shall be subject to a separate contract. 3. Exclusion of warranty As the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the STLport is errorfree, without material defects or suitable for a specific application under third-party rights. Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate any assurance of particular attributes. 4. Limited Liability a. Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this (i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute. b. If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstances known to it at that point in time representing a typical transfer of the software. c. In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a defect or lost profit. d. SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5,000. e. The Customer shall take adequate measures for the protection of data and programs, in particular by making backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by observing this obligation. f. The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees or agents of SAP.

5 Typographic Conventions Icons Type Style Example Text Example text EXAMPLE TEXT Example text Represents Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation Emphasized words or phrases in body text, titles of graphics and tables Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools. Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Icon Meaning Caution Example Note Recommendation Syntax

6 Contents Installation Guide SAP xrpm 4.0 Java Component Introduction Installation Step by Step Installing Installation Planning Required Documentation Hardware and Software Requirements SAP xrpm Installation Installing the SAP xrpm Java Component Installing the Business Package Connecting and Configuring Component Systems Configuring Java Component Properties...18 October

7 Installation Guide SAP xrpm 4.0 Java Component SAP xapp Resource and Portfolio Management (SAP xrpm) is designed to manage the capacity and deployment of human capital assets across multiple projects. SAP xrpm integrates information from existing project management, human resources, and financial systems to provide a complete overview of an organization s project portfolio with easy drilldown to details for portfolio managers, project managers, and resource managers. 1 Introduction Purpose This documentation describes how to install and configure the Java component of SAP xapp Resource and Portfolio Management (SAP xrpm). Implementation Considerations Before installing this component in the context of implementing a mysap Business Suite solution or one of its business scenarios, you should read the relevant Master Guide. The Master Guide is the central document for the implementation of mysap Business Suite solutions and business scenarios. It lists the components and third-party applications required by each business scenario of a mysap Business Suite solution, and refers to the required installation and upgrade guides. It also defines the installation sequence of the business scenarios of the corresponding mysap Business Suite solution. If you are installing SAP xrpm 4.0, see the Project and Portfolio Management Master Guide. You can find this document on SAP Service Marketplace at service.sap.com/instguides SAP xapps SAP xapp Resource and Portfolio Management SAP xrpm 4.0. July

8 2 Installation Step by Step Purpose You use the tables in the following sections as checklists to navigate through the installation. All necessary installation phases (planning, preparation, installation, and post-installation) are listed in these tables. the links to the general descriptions of the actions and to any additional information to help you perform the actions. This prevents you missing important information. Prerequisites Before installing the xrpm Java component (CPRXRPM_UI), you must install the following the required software components and supporting systems: - SAP NetWeaver 2004s Application Server (AS) ABAP and Java stacks - SAP Enterprise Portal (EP) - SAP xrpm 4.0 core ABAP component (CPRXRPM) Process Flow 1. Print out the relevant checklist. 2. Follow the installation sequence exactly as shown in the tables. If a step is required for your installation, follow the link for that step to the corresponding section. Perform the procedure described there. After you have successfully completed the installation step, mark the corresponding entry in the printed table with! to log the progress of your installation. Proceed with the next step listed in the table. 2.1 Installing Installation Planning Careful planning is a prerequisite for the successful installation of the system.! Action Install and configure all the required software components and supporting systems - SAP NetWeaver 2004s Application Server (AS) ABAP and Java stacks - SAP xrpm 4.0 core ABAP component: CPRXRPM - SAP xrpm 4.0 core Java component: CPRXRPM_UI - SAP Enterprise Portal (EP) Size all components accordingly Installation Process! Action 8 July 2005

9 Install the SAP xrpm UI component (CPRXRPM_UI) on SAP Enterprise Portal (EP) using the Java Support Package Manager (JSPM) Install the Business Package for Projects, Portfolio Management, and Design Collaboration (PPMDC) 4.0 on SAP Enterprise Portal (EP) using the Java Support Package Manager (JSPM) Connect the xrpm ABAP, SAP Enterprise Portal (EP) and SAP Business Warehouse (BW) systems Post-Installation Activities! Action Take any applicable security measures July

10 3 Installation Planning 3.1 Required Documentation The following sections describe the documentation you require for the installation. SAP installation notes SAPinst Troubleshooting Guide (for installations based on SAP Web AS Java only). Information in SAP Service Marketplace SAP Installation Notes You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation. Make sure that you have the up-to-date version of each SAP Note, which you can find in the SAP Service Marketplace at the Internet address: service.sap.com/notes. SAP Note Number Title Description xrpm 4.0 Master Note This note serves as a central note for SAP xrpm 4.0. Several other important notes are attached to this note, including those listed below Installation of CPRXRPM 400 on Basis Release 700 This note describes the add-on installation on SAP NetWeaver 2004s SAPinst Troubleshooting Guide The SAPinst Troubleshooting Guide provides up-to-date information about how to avoid installation failure and what to do if a failure occurs. You can find this guide and related documentation on SAP Service Marketplace at service.sap.com/instguidesnw04s Installation SAP EP SAP EP 7.0 <SR1>. SAP recommends that you read this documentation before starting the installation Information in the SAP Service Marketplace Information on the following areas is available on SAP Service Marketplace at service.sap.com. Description SAP Notes Released platforms System sizing Quick Link notes platforms sizing 10 July 2005

11 Installation documentation Security information for SAP applications Security guides. Since SAP xrpm is based on the SAP Web Application Server and the front-end application runs on the SAP Enterprise Portal, the following documents are particularly relevant: SAP Web AS Security Guide SAP Enterprise Portal 7.0 Security Guide Technical system infrastructure Network integration instguides security securityguide ti network 3.2 Hardware and Software Requirements SAP xrpm Java hardware and software requirements are in accordance with SAP NetWeaver 2004s requirements. For further information, see the relevant documentation on SAP Service Marketplace at service.sap.com/instguides SAP NetWeaver <release> Installation. You should also ensure that: SAP NetWeaver 2004s Application Server is installed and correctly configured SAP Enterprise Portal (EP) is installed and correctly configured SAP xrpm 4.0 core ABAP component (CPRXRPM) is installed and correctly configured SAP xrpm ABAP system and SAP Enterprise Portal (EP) have been registered in the System Landscape Directory (SLD) You use the SAP xrpm ABAP system as a user management engine, because user authorizations are maintained in the SAP xrpm ABAP component July

12 4 SAP xrpm Installation 4.1 Installing the SAP xrpm Java Component You use this procedure to deploy the SAP xrpm Java component (CPRXRPM_UI) on SAP Enterprise Portal (EP) using the Java Support Package Manager (JSPM). For information about the Java Support Package Manager (JSPM), see the relevant documentation on SAP Help Portal at help.sap.com Documentation SAP NetWeaver <release> Solution Lifecycle Management Software Lifecycle Management Software Maintenance Java Support Package Manager. 1. Ensure that SAP Enterprise Portal (EP) is started and successfully configured. 2. Download the SAP xrpm installation package from SAP Service Marketplace at service.sap.com/swdc. 3. Put the package in the EPS inbox /usr/sap/trans/eps/in where the JSPM searches for packages. 4. Start the JSPM to install the software component archive. 5. After successful installation, quit the JSPM. 6. Restart the SAP Enterprise Portal (EP). 4.2 Installing the Business Package You use this procedure to deploy the Business Package for Projects, Portfolio Management, and Design Collaboration (PPMDC) on SAP Enterprise Portal. 1. Ensure that SAP Web Application Server is started and successfully configured. 2. Download the Business Package for PPMDC (file BPPPMDC00_0.sca) from SAP Service Marketplace at service.sap.com/swdc. 3. Put the package in the EPS inbox /usr/sap/trans/eps/in where the JSPM searches for packages. 4. Start the JSPM to install the software component archive. 5. After successful installation, quit the JSPM. 4.3 Connecting and Configuring Component Systems You use the procedures in this section to connect the main component systems the SAP xrpm ABAP system, SAP Enterprise Portal (EP) and the SAP Business Information Warehouse (BW) system. This facilitates integration between SAP Web Application Server (AS) and SAP Enterprise Portal (EP). To do this, you must: Configure the system landscape 12 July 2005

13 Configure the portal security zone Configure single sign-on Create JCO destinations Configure runtime properties for SAP IGS Configure the logger for WebDynpro components Configure systems for SAP project system integration Configure systems for SAP cprojects integration Configuring the System Landscape You use this procedure to configure the system landscape and thus enable communication between the SAP xrpm ABAP system, the SAP Business Information Warehouse system, and the SAP xrpm WebDynpro system, on which your user interface is running. SAP xrpm needs the following systems: SAP xrpm ABAP system This system contains the add-on component CPRXRPM and uses the system alias SAP_RPM. If there is already a system definition for the Project and Portfolio Management (PPM) backend system used by cprojects, you only need to add SAP_RPM as an alias to that system definition. SAP xrpm WebDynpro system This system contains the definition for the Java WebDynpro J2EE system and uses the system alias SAP_WebDynpro. Here, you specify the URL for the J2EE WebDynpro server (the Web Application Server). SAP Business Information Warehouse (BW) system This system uses the system alias SAP_BW. Depending on the supported landscape, SAP xrpm system definitions can use either Load Balancing or a Dedicated Application Server system definition templates. When creating system definitions for the xrpm systems, the following parameters are required: System Parameters SAP_RPM Enter appropriate property values in the following fields: SAP_WebDynpro Application Host Message Server Client Group Logon Method R/3 Name Server Port System Number Enter appropriate property values in the following fields: July

14 WAS Description: <description> WAS hostname: <hostname:port> WAS path: </webdynpro/dispatcher/ WAS protocol: <http> SAP_BW Enter appropriate property values in the following fields: Application Host Message Server Client Group Logon Method R/3 Name Server Port System Number d to display the xrpm BW reports in the portal: WAS Description: <description> WAS hostname:<hostname: port> WAS protocol> WAS path: </ > WAS protocol: <http> For further information about configuring the system landscape, read the relevant documentation on SAP Help Portal at help.sap.com Documentation SAP NetWeaver <release> People Integration Portal Administration Guide System Administration System Configuration System Landscape. After completing the system definitions, see the SAP Enterprise Portal (EP) installation guide for permissions and adjust the permissions properly. The permissions for the system definitions should include a read-only End r mode for users or groups that need to access SAP xrpm roles Configuring the Portal Security Zone You use this procedure to set permissions for Microsoft Project Client upload and download to enable users without administrator rights to access these Java iviews. 1. Log on to the portal and navigate to System Administration Permissions Portal Permissions Security Zones sap.com cprxrpm low_safety. 2. Open the context menu of low_safety and select Open Permissions. 3. Search for the group Everyone, add it to the assigned permissions and check the End r column. 4. Save your changes. 14 July 2005

15 Additional Information For further information, see the relevant permission configuration documentation in the Portal Administration Guide on SAP Help Portal at: help.sap.com Documentation SAP NetWeaver <release> People Integration Portal Administration Guide System Administration Permissions, Role/r Distribution, and Object Locking Portal Permissions Security Zones Configuring Single Sign-On (SSO) You use this procedure to configure SAP xrpm single sign-on (SSO). For information about portal single sign-on (SSO) configuration, see the the relevant SAP NetWeaver 04s documentation on SAP Help Portal at help.sap.com Documentation SAP NetWeaver <release> Security r Authentication and Single Sign-On Single Sign-On in a Complex System Landscape Scenario: SSO Between Portal, WebDynpro, and ABAP Systems Creating JCO Destinations You use this procedure to establish a connection between the SAP xrpm Java component and SAP ABAP systems. 1. Ensure that the SLD Data Supplier Service in J2EE Engine Administrator Console is properly configured. 2. Log on as SAP NetWeaver WebDynpro Content Administrator at: 3. Under Deployed Content, expand sap.com and click on sap.com/xapps~cprxrpm~models. You see the component details screen on the right panel. 4. Select the JCO Connections tab. The following system destinations are defined: System Default logical system name for model instances Default logical system name for RFC metadata Name PPM_WD_MODELDATA_DEST PPM_WD_RFC_METADATA_DEST 4. To establish a connection with the xrpm ABAP system for PPM_WD_MODELDATA_DEST, choose Create. As data type, choose Application Data As destination type, choose Load-balanced Connection As user authentication, choose Ticket Single Sign-On (SSO) is required between xrpm WebDynpro and xrpm ABAP systems. July

16 5. To establish a connection with the xrpm ABAP system for PPM_WD_RFC_METADATA_DEST, repeat the same steps. o As data type, choose Dictionary Meta Data o As user authentication, choose r/password Enter the name and password of the user who has administrator permissions in the SAP xrpm ABAP system Configuring Runtime Properties for SAP IGS You use this procedure to configure runtime properties for the SAP Internet Graphics Server (IGS). Prerequisites Ensure that the SAP IGS server is installed and running. 1. Log on to the J2EE Engine Visual Administrator. 2. On the Cluster tab, navigate to <instance> Server Services Configuration Adapter. 3. Select the Runtime tab. 4. Select the Display configuration tab. 5. Navigate to webdynpro sap.com tc~wd~dispwda. 6. Switch to Edit mode and double click on Propertysheet profile. 7. Set appropriate values for the following property: Property IGSUrl Value hostname = The name of the machine where the IGS is installed, for example P12345 port = The port of the http listener. The default port is Save your changes. 9. Restart the J2EE Engine. For further information about IGS parameters, see SAP Note Configuring the Logger for WebDynpro Components You use this procedure to configure the logger for SAP xrpm WebDynpro components. Go to J2EE Visual Administrator Log Configurator and configure the logger to ensure that all logged messages from development components (DCs) prefixed with com.sap.xapps.cprxrpm are displayed in the file defaulttrace under <instance>\jc00\j2ee\cluster\server0\log. 16 July 2005

17 4.3.7 Configuring Systems for SAP Project System Integration You use this procedure to integrate the SAP project system with SAP xrpm. Prerequisites Verify that the required business object types supported by SAP xrpm are defined and linked to the business object types supported by the base project system. For further information, see the SAP xrpm Implementation Guide (IMG) in the SAP xrpm ABAP system. 1. Log on to the portal and navigate to System Administration System Configuration System Landscape. 2. Create a new system for SAP base project system integration. 3. Provide properties of the system based on the example as shown below: Property Value System Type SAP R/3 Dedicated System Alias <SID> Application Host <host name> ITS Host Name <host name> ITS Path /scripts/wgate ITS Protocol http Logon Method SAPLOGONTICKET Remote Host Type 3 SAP Client 100 SAP System ID (SID) <SID> SAP System Number 3 System Type SAP_R Configuring Systems for SAP cprojects Integration You use this procedure to integrate SAP cprojects with SAP xrpm. Prerequisites Verify that the required business object types supported by SAP xrpm are defined and linked to the business object types supported by the base project system. For further information, see the SAP xrpm Implementation Guide (IMG) in the SAP xrpm ABAP system. 1. Log on to the portal and navigate to System Administration System Configuration System Landscape. 2. Create a new system for SAP cprojects integration. July

18 3. Provide properties of the system based on the example as shown below: Property Value System Type SAP R/3 Dedicated System Alias <SID> Application Host <host name> ITS Host Name ITS Path ITS Protocol http Logon Method SAPLOGONTICKET Remote Host Type 3 SAP Client 100 SAP System ID (SID) <SID> SAP System Number 19 System Type SAP_R3 4.4 Configuring Java Component Properties Configuring the Application for Project Upload/Download You use this procedure to configure the application to be used for uploading and downloading project data. 1. Log on to the J2EE Engine Visual Administrator. 2. On the Cluster tab, navigate to <instance> Server Services Configuration Adapter. 3. Select the Runtime tab. 4. Select the Display Configuration tab. 5. Navigate to webdynpro sap.com xapps~cprxrpm~ui~pintegration Components com.sap.xapps.cprxrpm.ui.pintegration.component.projectintegrationcomp PropertySheet profile. 6. Switch to Edit mode and double click on Propertysheet profile. 7. Select DEFAULT_APPLICATION.value and enter your own custom value. 8. Choose Apply Custom Mapping Logical Systems to System Aliases You use this procedure to map the logical systems configured for base systems in the backend to the system aliases configured in the portal. 18 July 2005

19 1. Log on to the J2EE Engine Visual Administrator. 2. On the Cluster tab, navigate to <instance> Server Services Configuration Adapter. 3. Select the Runtime tab. 4. Select the Display configuration tab. 5. Navigate to webdynpro sap.com xapps~cprxrpm~common Components com.sap.xapps.cprxrpm.common.component.commoncomp Propertysheet profile. 6. Switch to Edit mode and double click on Propertysheet profile. 7. Select LogicalSystem<x>.value (where x denotes a value between 1 and 8) and enter your own custom value. 8. Choose Apply Custom. 9. Select SystemAlias<x>.value (where x denotes a value between 1 and 8) and enter the alias given in the system configuration. 10. Choose Apply Custom. July