You are on page 1of 88

SAP® E-Sourcing 2007

Installation and Configuration Guide

Confidential and Proprietary

© Copyright 2007 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, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. 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. 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. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, E-Sourcing 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. Published in the U.S.A.

SAP AG 400 Technology Square, Floor 9 Cambridge, MA 02139 September 2007

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 7: Create a Schema . . . . . . . . . Task 4: Create Tablespace(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 1: Install Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 3 3 3 3 3 1 Installing the E-Sourcing Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 2: Verify Security Settings . . . . Task 8: Install JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 6: Install Oracle JDBC Driver . . . . . . . . . . . . . . . . . Oracle Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 4: Deploying SAP E-Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Universal Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 3: Create a Buffer Pool . . . . . . . . . . . . . . . . . . 5 Overview. . . . . . . . . . . . Chapter 2: Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Table of Contents Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 7: Verify Analytics Support Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 3: Setup LDAP Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-installation Procedure. . DB2 Tasks . . . . . 1 Audience for this Guide . . . . . . . . . . Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 2: Create a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 2: Create Oracle Schema . . . . . . . . . . . . . . . . . . . . . . 6 6 6 6 7 7 7 7 7 7 7 7 8 8 8 8 8 8 8 9 9 9 9 Confidential i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1: E-Sourcing Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 5: Create a Temporary Tablespace . . . . . . . . . . . . . . . Topic Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 5: Install Oracle Toolkit . . . . . . . . . . . . . . . . . . . . . Task 1: Identify Database Server . . . . . . . . . Task 6: Create a Database Service Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 3: Create Oracle Service Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3: Contract Generation . . . . . . . . . . . . . . . . . Task 1: Identify Oracle Server . . . . . . . . . . . Task 4: Connect Oracle Schema . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Task 6: Upgrade Database Schema from Previous Release. . . . . . . . . . . . . 19 Task 7: Deploy the Application EAR File to the Application Server . . . . . . . . . . . . . . . . . . . 15 Configuring JMS Queues and JNDI Aliases . . . . . . . . . 11 Creating or Updating Database Login Information . . . . . . . . . . . . . . . . . . . . . . . 20 2 Installing the E-Sourcing Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Including Custom Jar Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Updating the EAR File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Installing the Optimizer License . . . . . . 25 Deploying the Optimizer . 9 Configuring the Software for Deployment . . . . . . . . . 21 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Defining the Application Context . . . . . 26 ii Confidential SAP® E-Sourcing Software Installation and Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Task 8: Generate License File for E-Sourcing Explorer . . . . . . . . . . . . . . . . . . . . . . . . . 15 Task 3: Define JAXP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Runtime Environment Variables and ClassPath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Task 4: Configure JMS Messaging . . . 14 Task 2: Define Java Memory and Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Creating New JMS Message Queues and JNDI Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Configuring JMS Queues. . . . . 22 Pre-installation Procedures . . . . 20 Task 9: Verify Production Readiness Criteria . . . . . . . . 10 Updating the Java Home Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Table of Contents Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Homogeneous JVM Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Post-installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Task 1: Add SAP-Required Libraries . . . . . 16 Defining System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Set Session Timeout . . 13 Post-installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Installing the E-Sourcing Binary Files. . . . . . . . . . . . . . . . . 26 Identifying the Optimization Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Installing the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Task 5: Update Session Timeout (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Recommended Server Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WebLogic Socket Readers . . . . . . . . . . . . . . . . . . . . Access and Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Overview. . . . . . . . . . . . . 27 Pre-installation Procedures . . . . . . . . . . . . . . . . . 34 34 35 35 36 40 40 41 43 44 44 45 45 46 46 47 Appendix A: Performance Tuning . . . . . . . . . . . . . . . . . . . . . . 54 SAP® E-Sourcing Software Installation and Configuration Guide Confidential iii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring SAP E-Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gathering Critical Information . . . . . . . . . . . . . . . . . . . 33 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contexts . . . . . . . . . . . . . . . . . WebLogic Execution Threads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with the Deployment Workbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 50 50 51 51 51 Appendix B: Running Multiple Instances on a Single Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a Cluster. . . . . . . . . . Customizing Data Input Workbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Company Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the installation . . . . . . . . . . . . WebLogic Native I/O Performance Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sun JVM Threading Model . . . . Sun JVM Heap Size . . . . . . CSV File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building a Simple Custom Enterprise . . . . . . . Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 28 29 31 31 4 Deploying SAP E-Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Table of Contents 3 Installing Contract Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Procedures . .

. . . . . . . . . . . . . . . . . . . . . 74 Best Practice Use of Object Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Object Migration Output . . . . . 67 Restore Process . . . . . . . . 67 Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . 54 Future Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Application Server Vendor-Specific Instructions . . 75 Introduction . 63 Appendix D: Operation and Maintenance . . . . . . . . . . . . . . . 72 Custom Sourcing Object List Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Component Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Network and Communication Security . 75 iv Confidential SAP® E-Sourcing Software Installation and Configuration Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . 57 Troubleshooting Multiple Instance Configuration . . . . . . . . . . . 58 Applying a Service Name for All FCI Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Object Creation or Update . . . . . . . . . . . . . . 63 Traces and Logs. . . . . .7/Jetty 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 JBoss 3. . . . . . . . . . . . . . . . . . . . . . . 57 Installing the Software . . . . . . . . . . . . . . . . . . 70 Mechanics of Object Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Online and Offline Backup . . . . . . . . . . . . . . . . . . . . . 69 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Changing Ports on One Server. 71 Object Migration Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Table of Contents SAP E-Sourcing Multi-Instance Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Data Storage Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Appendix C: Security Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 . . . . . . . . . . . . . . . . . . . . . . . . . . .2. . . . . . . . . . . . . . . 58 Changing FCI System Properties . . . 58 Restarting the Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Backup Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Appendix E: Object Migration . . . . . . 74 Import Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . Import Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Table of Contents Environments. . . . . . . . . . . . . . . . . . . . . . . . . . Export Data . . . . . . . . . Tracking Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 75 76 77 77 77 SAP® E-Sourcing Software Installation and Configuration Guide Confidential v . . . . . . . . . Troubleshooting Object Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents vi Confidential SAP® E-Sourcing Software Installation and Configuration Guide .

including expenditure analysis. and compliance. The preface covers the following topics: Audience for this Guide on page 2 Topic Organization on page 3 Confidential 1 . vendor management. supplier selection.Welcome to Sap E-Sourcing Software Preface SAP® E-Sourcing is an enterprise software solution that automates the entire sourcing process. It allows your organization to create a disciplined process for the way you buy goods and services. This guide defines the basic steps for installing and deploying SAP E-Sourcing components.

Overview Depending on the license and distribution media. and configuration of the E-Sourcing environment.Audience for this Guide Preface Audience for this Guide The audience for this guide is any person who is involved in the installation. Items in bold are required. deployment. the SAP E-Sourcing installation can include the following components: E-Sourcing Platform Optimizer Contract Generation Exchange Calendar Synchronization The figure below provides an overview of the SAP E-Sourcing components and the required and optional services. System Configuration Components 2 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . Additional configuration information is provided in the Setup section of the Online Help.

and an SMTP server. This chapter describes how to install the Optimizer application. The Optimizer has no direct end-user interface. This chapter describes these tasks in detail.NET application framework and should be deployed on a server independent of any J2EE application component. Chapter 4: Deploying SAP E-Sourcing After installing the SAP E-Sourcing components and services. However. The E-Sourcing application makes requests to the Optimizer service. Chapter 2: Optimizer The SAP Optimizer is also a J2EE application that requires a J2EE-compliant application server that supports the EJB2.0 spec.NET services. This chapter describes how to install the contract generation service. it may be deployed with other . This chapter describes how to install the SAP E-Sourcing platform. This service processes requests from the E-Sourcing application. an LDAP directory. The Optimizer is typically deployed on a separate physical application server from the E-Sourcing application. the sourcing application can leverage an external HTTP web server and a Symantec AntiVirus Scan Engine server.Preface Topic Organization Topic Organization Chapter 1: E-Sourcing Platform The SAP E-Sourcing platform is a J2EE application that provides the core sourcing functionality. Optionally. a number of deployment tasks must be performed to get the system up and running. The Service generates Contract documents in Microsoft Word format. This service requires the Microsoft . In addition to a J2EE-compliant application server. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 3 . the E-Sourcing configuration requires an Oracle database.NET service. Chapter 3: Contract Generation Contract generation is a Microsoft . This prevents the computation-intensive processing of the Optimizer from impacting the performance of user interaction with the E-Sourcing application.

Topic Organization Preface 4 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .

It also describes the preliminary installations and configurations that are required before you install the E-Sourcing software.1 Installing the E-Sourcing Platform This chapter describes how to install SAP E-Sourcing Platform on Windows 2000 and Solaris. This chapter covers the following topics: Overview on page 6 Pre-installation Procedure on page 6 Installation Procedure on page 9 Post-installation Procedure on page 13 Confidential 5 .

Pre-installation Procedure The following items must be configured before installing the E-Sourcing software. you must install software on the application server and the database server. Although the configure utility creates a baseline database for a new installation. Universal Tasks Task 1: Install Java Runtime Environment Identify and install a supported J2EE application server with recommend Java Runtime Environment (JRE). To install SAP E-Sourcing. Task 2: Verify Security Settings Verify that the Java Runtime Environment is configured with Java Cryptography Extension (JCE). The Setup section of the Online Help describes how to define clusters for load balancing.Overview 1 Installing the E-Sourcing Platform Overview Before you can install the SAP E-Sourcing software.security property file: 6 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . you must perform three sets of tasks: Pre-installation procedures Automatic installation and configuration of the software Post-installation procedures If this is a new installation. The deployment workbook is an Excel spreadsheet that you use to define the data and then import it into the application. See the Supported Configurations link in the online Reference Guide (RG) for more information. support a multiple-enterprise context. and configure a number of database settings on the database server. You can define this data interactively or via a deployment workbook. this baseline database lacks the business-specific data required for a fully functioning system. These are defined by the following properties in the java. and define master data and user accounts. you will also need to implement the SAP E-Sourcing application as defined in the Online Help under Setup. the performance of the E-Sourcing client is highly dependent upon the network infrastructure between the web browser client and the application server. and Java Secure Socket Extension (JSSE). E-Sourcing performance may suffer if sufficient bandwidth is not provided. Instructions for its use are included in Chapter 6: Deploying SAP E-Sourcing. Performance note: As with other web-enabled applications.

You will need the Server Hostname.provider. The application can be configured to support multiple directories. Oracle Tasks Task 1: Identify Oracle Server Identify the Oracle server to create an application database schema. The toolkit supports DES encryption. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 7 . Note that this is a new version of the JDBC driver. Task 2: Create Oracle Schema Create an Oracle 9i schema. Task 3: Create Oracle Service Account Identify and create an Oracle Service account. Oracle username. The schema should be configured for a minimum of 5G. and QUERY REWRITE. which is required by the application to encrypt sensitive data stored in the database. This should be available on your Oracle distribution or can be downloaded from http://otn. This may be the schema owner account. Actual database storage requirements can vary with use. RESOURCE.1 Installing the E-Sourcing Platform Pre-installation Procedure security. Task 6: Install Oracle JDBC Driver Locate the Oracle 9i JDBC driver. and Oracle password to configure the application. SID.com. CREATE DIMENSION. different directory configurations can be used for internal buyers and vendors. Task 4: Connect Oracle Schema Obtain the connection information for the Oracle schema from your database administrator. CREATE MATERIALIZED VIEW. and external buyers and vendors. The Service account must be granted CONNECT. The database server must be configured for UTF-8 data encoding to support alternate/multiple languages. Sizing worksheets are available to assist in more detailed sizing. Task 5: Install Oracle Toolkit Verify and Install Oracle DBMS_OBFUSCATION_TOOLKIT.com.oracle. This toolkit should be available on your Oracle distribution or can be downloaded from http://otn. For example.n Task 3: Setup LDAP Directory Identify and install the supported LDAP Directory for end users of the application.oracle. The service account must be assign the default roles of CONNECT and RESOURCE. UNLIMITED TABLESPACE.

Task 6: Create a Database Service Account SAP E-Sourcing uses a database user account to connect to the database. respectively. and blobs in individual tablespaces.1 for Linux. Task 2: Create a Database The Database must be configured to use the UTF-8 character encoding as its default character encoding. We recommend installing SAP E-Sourcing in its own database to simplify maintenance.x. you must obtain this new JDBC driver. Task 3: Create a Buffer Pool SAP E-Sourcing requires use of a buffer pool having a 32K page size. Create a buffer pool associated with the named database created in Step 2. this account must be granted the following database privileges: 8 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . Minimally. Task 7: Verify Analytics Support Settings Verify the Oracle server settings to support SAP E-Sourcing Analytics. and Windows. You must create at least one tablespace associated with the buffer pool created in Step 3. The server settings are: STAR_TRANSFORMATION_ENABLED = TRUE OPTIMIZER_MORE = CHOOSE QUERY_REQRITE_ENABLED = FALSE COMPATIBLE = 8. Unix.0 (or greater) QUERY_REWRITE_INTEGRITY = TRUSTED DB2 Tasks Task 1: Identify Database Server Identify a database server running DB2 9. and blobs.1.Pre-installation Procedure 1 Installing the E-Sourcing Platform Note: If you are upgrading from Sourcing 2. indexes. You may create two additional tablespaces if you wish to maintain your tables. Task 5: Create a Temporary Tablespace You must create a system temporary tablespace with a 32K page size for use by SAP E-Sourcing associated with the database created in Step 2. All tablespaces must be created in association with the database created in Step 2. Task 4: Create Tablespace(s) SAP E-Sourcing supports up to three tablespaces to contain tables. indexes.

You will see the E-Sourcing Install wizard. Software configuration settings are found in the FCI. CREATETAB. These two files are typically found in the IBM/sqllib/java directory on the system where db2 is installed. run the following: setup.properties and fcilocal.exe ■ For Solaris installation. Note: Installing the E-Sourcing Binary Files The installation procedure for SAP E-Sourcing is called Setup. run the following: setupLinux.properties). Task 8: Install JDBC Driver SAP E-Sourcing requires installation of the IBM DB2 JDBC driver on the application server in a location which can be referenced during the E-Sourcing installation process. To install SAP E-Sourcing: Run the setup command. The authorization (owner) of this schema must be the database user account created in Step 6. ■ For Windows installation.bin Note: The installer performs a full search for the JVM. The JDBC driver can also be downloaded from the IBM website.bin ■ For Linux installation.1 Installing the E-Sourcing Platform Installation Procedure CONNECT. This may take a while in some cases. Configuring the software for deployment. grant use of the tablespaces created in Step 4 to this database user account. run the following: setup. Installation Procedure The two primary steps of the installation procedure are: 1 2 Installing the E-Sourcing and third-party binary files.jar.HOMEDIR/config directory of the local file system (fcisystem. Task 7: Create a Schema Create a schema associated with the database created in Step 2. you can specify the location of the JVM by using the following: SAP® E-Sourcing Software Installation and Configuration Guide Confidential 9 . Application and software data are commingled within the same database schema. The two files required are: db2jcc. BINDADD Additionally.jar and db2jcc_license_cu.

Specify the directory location for the FCI software.jar). To manually execute the configure utility: For Windows installation. Note: The path for the FCI home directory must be all lower case or the installation/upgrade will not be successful. Configuring the Software for Deployment The configuration process is launched after successful installation of the E-Sourcing binary files.jar and db2cc_license_cu. The configuration tool can also be executed after the installation to reconfigure the application. This will be the FCI home directory. If you select DB2. you see a page asking you to provide the two DB2 JAR files (db2cc. 10 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . run the following: <FCIHOMEDIR>\bin\configure. You can specify the location of the JVM by using the following: -is:javahome /yourpathname The configure utility can perform the following functions.bin For Linux installation. ■ Specify a single or multibyte database character set.bin Note: Again. Select the appropriate database: Oracle or DB2.Installation Procedure 1 Installing the E-Sourcing Platform -is:javahome /yourpathname The first step of the installation procedure is responsible for the deployment of the software binaries and requires that you do the following: Accept the license terms of the software. run the following: <FCIHOMEDIR>/bin/configure.jar). you see a page asking you to provide the Oracle JAR file (normally oracle. run the following: <FCIHOMEDIR>/bin/configureLinux. ■ If you select Oracle.exe For Solaris installation. This is often done to rebuild the EAR file after the inclusion of custom jar files or the application of a software patch. the installer will perform a full search for the JVM.

If you leave these fields blank. Modify the URL to include the host name. you can install the baseline database.properties file.jdbc. and blobs (Blob Space).driver. This application will not start up if the JVM that built your database and the JVM that starts the application do not contain the same version of JCE. It is recommended that you specify the JVM that will be used to run your application server here. the names of custom database tablespace(s) used for storing tables (Table Space). the default Oracle settings are used. This is because a keystore is installed into the database using JCE.1 Installing the E-Sourcing Platform Installation Procedure Updating the Java Home Directory The configure tool will provide a default Java home directory.required for upgrade. Installing the Database The database install option allow you to install a baseline database. If this is a new installation. You can select a different Java directory to be used by FCI standalone tools. recommended but not required for installation) Optionally. SAP does provide a mechanism for reinstalling the keystore should this situation occur. the user name -. The URL must be in the following format: jdbc:oracle:thin:<hostname>:<port>:<SID> For example: jdbc:oracle:thin:@localhost:1521:XE Username and Password: the user ID and password of the Oracle account used by the application to access the database (required). Schema (typically.OracleDriver URL to connect to the database and the username and password to connect to the database schema (required). indexes (Index Space). The Java home directory used by the application will be defined by the J2EE application server. Creating or Updating Database Login Information The configuration utility stores database login information in the fcisystem. For Oracle: Enter the following database login information: Driver Class (required): oracle. This is the connection information you obtained during the pre-installation procedure. Installing the baseline will overwrite any existing data in the database. port. and SID for your server. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 11 .

The URL must be in the following format: jdbc:db2:<hostname>:<port>/<database> For example: jdbc:db2://localhost:5912/ES Username and Password: the connection information you obtained during the pre-installation procedure (required).db2. Schema (required) The names of database tablespaces used for storing tables (Table Space).ibm. and database for your server. Select this option to change this setting. the tool allows you to provide any custom jars into the fci custom directory. and blobs (Blob Space) (required) Updating the EAR File The SAPEAR files are built and stored in the <FCIHOMEDIR>/fsapp directory. Set Session Timeout The deployment descriptor for the SAP E-Sourcing application defaults to a 30-minute session timeout. port. say /sourcing. the application will only respond to requests that come in as http://webserver/sourcing/servlet. meaning that the application will respond to servlet requests that come in as http://webserver/servlet. If you run in a non-default context.jcc.Installation Procedure 1 Installing the E-Sourcing Platform For DB2: Enter the following database login information: Driver Class (required): com. These files will automatically be included in the generated EAR file. indexes (Index Space).DB2Driver URL to connect to the database and the username and password to connect to the database schema (required). Defining the Application Context Select this option if you would like to change the context root for SAP E-Sourcing. Modify the URL to include the host name. 12 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . Including Custom Jar Files If you select this option. The default context is '/'.

Generate license file. Optionally. Define Java virtual memory and configuration settings. Using the WebSphere admin console. WebSphere has a session timeout property at the application server level. Verify production readiness criteria. update the default session timeout. Configure the SAP application timeout setting to override the application server setting via the Session Management page for SAP E-Sourcing. Deploy the application EAR file to the application server. Configure JMS messaging. do one of the following: Using the WebSphere admin console. use the application server property to control session timeout. Post-installation Procedure Once the E-Sourcing application has been installed and configured. The libraries required by the SAP E-Sourcing application are packaged in the EAR file that is deployed by the application server. For example. In this situation. Upgrade the database schema from previous release. disable the timeout at the application server level. the following post-installation tasks must be performed: 1 2 3 4 5 6 7 8 9 Add SAP-required libraries to server class path. this setting may be overridden by a session timeout that is set at the application server level. the mechanism used by the application server to load SAP® E-Sourcing Software Installation and Configuration Guide Confidential 13 . Define JAXP settings. However.1 Installing the E-Sourcing Platform Post-installation Procedure In some cases. Task 1: Add SAP-Required Libraries Note: The following applies to non-JBoss deployments only.

jar <FCIHOMEDIR>/lib/batik-all.jar.jar Note that the FCI_CLASSPATH environment variable must still be added to the server’s classpath environment variable.jar. Task 2: Define Java Memory and Configuration Settings Define the initial and maximum Java heap size using the –Xms<size> and –Xmx<size> options on the Java command line. if using the upp.jar <FCIHOMEDIR>/lib/endorsed/serializer.jar <FCIHOMEDIR>/lib/endorsed/xml-apis.c:/fci/lib/cocoon-fci.jar <FCIHOMEDIR>/lib/fop.c:/fci/lib/soap.jar (WebSphere only.04.username_regex property to implement a single sign-on solution) <FCIHOMEDIR>/lib/jcschart.jar.jar (WebLogic only) For example.jar.jar <FCIHOMEDIR>/lib/jakarta-oro-2.c:/fci/lib/batik-all.jar.jar <FCIHOMEDIR>/lib/soap.jar <FCIHOMEDIR>/lib/mail.dirs=<FCIHOMEDIR>/lib/endorsed 14 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .jar.c:/fc i/lib/jcschart.c:/fci/lib/mail.jar <FCIHOMEDIR>/lib/avalon-framework.c:/ fci/lib/avalon-framework.c:/fci/lib/saxon.c:/fci/lib/fcifopext. The following libraries must be added to the application server’s classpath: <FCIHOMEDIR>/lib/activation.c:/fci/lib/fop.jar.Post-installation Procedure 1 Installing the E-Sourcing Platform XML parsers requires some of the libraries to be available to the application server.jar. Add the following Java configuration setting: -Djava.jar.c:/fci/lib/activation.jar <FCIHOMEDIR>/lib/endorsed/xercesImpl.jar.c:/fci/lib/ssce.jar <FCIHOMEDIR>/lib/fcifopext.endorsed.extservletauthenticator.ja r.jar <FCIHOMEDIR>/lib/endorsed/xalan. if you define <FCIHOMEDIR> to be c:/fci.jar <FCIHOMEDIR>/lib/ssce. you might define an FCI_CLASSPATH variable with the following values: SET FCI_CLASSPATH= c:/fci/lib/xercesImpl.

The following JAXP properties must be defined to allow SAP E-Sourcing to use the required processors: javax.transform.xerces. By default.DocumentBuilderFactoryIm pl javax. The Java API for XML Processing (JAXP) provides a mechanism for defining the XML and XSL processors used by the E-Sourcing application. the JMS server must be configured and started on the application server.SAXParserFactoryImpl javax. JMS Messaging is also used for communication between E-Sourcing applications.xerces. using the Java –D<name>=<value> option. Task 4: Configure JMS Messaging SAP E-Sourcing utilizes JMS messaging for communication between the E-Sourcing application server and the Optimizer.apache.xml. File storage is the recommended configuration for SAP E-Sourcing JMS queues. Establish paging storage for queues. Enable transaction support (XA). Configuring JMS Queues and JNDI Aliases The following JMS queues and JNDI aliases should be set up on the application server to support JMS messaging: SAP® E-Sourcing Software Installation and Configuration Guide Confidential 15 .SAXParserFactory=org.processor.apache. SAP E-Sourcing ships with the required XML and XSL processors.jaxp.xalan.TransformerFactoryImpl ---.xml.apache.parsers. perform the following steps: Create the JMS Server. The JMS communication requires additional configuration of the J2EE application server.1 Installing the E-Sourcing Platform Post-installation Procedure Task 3: Define JAXP Settings Note: The following applies to non-JBoss deployments only.parsers.TransformerFactory=org. For the application server that will run the JMS Server.jaxp. Establish persistent storage for the queues. or using an application-server-specific mechanism for defining JAXP settings. the JMS server is generally not started.this one changed The JAXP settings can be defined in a JAXP specific property file. Prior to configuring the JMS queues. This can be either file or database storage.DocumentBuilderFactory=org.xml.

naming.interfaces.commomn. The values of these properties differ between application servers.HaltAllocationQueue JNDI: fs.naming.AllocationRequestQueue Queue: fs.JmxQueue Integration API Queue: fs.ibm.queue.factory.queue.services.IapiEventQueue Optimization (see the Installing the SAP Optimizer chapter for more details) Queue: fs.optimization.jnp.optimization.QueueConnectionFactory Defining System Properties You must next define a number of SAP system properties.HaltAllocationQueue Create the following JMS Connection Factories: JNDI Name: fs.AllocationRequestQueue JNDI: fs.NamingContextFactory NetWeaver: com.engine.QueueConnectionFactory JNDI Name: fs. JMX (E-Sourcing Server Management) Queue: fs.websphere.jmx_queue JNDI: fs. The following are the default values for WebSphere. and JBoss: initial JNDI Context system.WLInitialContextFactory WebSphere: com.WsnInitialContextFactory JNDI Naming Factory 16 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .queue.AllocationStatusQueue Queue: fs.queue.java. WebLogic.optimization.initial = The Class Name of the initial context factory implementation ■ ■ ■ ■ JBoss: org.jndi.sap.jndi.destination.j2ee.AllocationStatusQueue JNDI: fs.jndi.Post-installation Procedure 1 Installing the E-Sourcing Platform Note: The setup of these queues depends on the application server.IapiEventQueue JNDI: fs.destination. Most will auto-prefix queue names with “queue/”.optimization.InitialContextFactoryImpl WebLogic: weblogic.

ibm.destination.queue.providers WebLogic: weblogic.initial jndi. If the above values were not used.destination.1 Installing the E-Sourcing Platform Post-installation Procedure system.common.tm. the values will have to be set manually by logging into the system context and setting each property manually.InitialContextFactoryImpl com.java.factories WebSphere: com.queue.JmxQueue jmsqueues/default/fs.pkgs = Packages to search for application server impl classes ■ ■ ■ ■ JBoss: org.jndi.jndi. J2EE configuration parameters must match the NetWeaver configuration above to use this import script.url Value jmsfactory/default/fs.queue.naming.providers localhost:50004 SAP® E-Sourcing Software Installation and Configuration Guide Confidential 17 .jndi.ws.naming JNDI Provider system.jnp.jboss.) ■ ■ ■ ■ JBoss: localhost:1099 NetWeaver: localhost:50004 WebLogic: t3://localhost:7001 WebSphere: corbaloc:iiop:localhost:2809 A Dbimport script exists that automates setting the J2EE system properties.url = Indicates the transport layer that should be used. File: fciinstall.j2ee. The following properties will be automatically installed.j2ee.url.common.java.java.naming.jndi.pkgs jndi.naming. (These are the defaults.queue.naming:org.url.tm.jar/scripts/dev/import_netweaver_system_properties. Start DbImporter.naming. Change localhost to the application server that is running the J2EE Services.services.provider.naming.factory.engine. J2EE System Properties: J2EE System Properties (NetWeaver) ■ ■ ■ Field jms.sap.java.queueconnectionfactory jms.provider.factory.interfaces NetWeaver: com.iapi_event_queue jndi.QueueConnectionFactory jmx_queue jmsqueues/default/fs.java.IapiEventQueue com.jmx_queue jms.factory.sap.jndi.xml.sap.jndi.

status_destination jndi. The default value is typically 20-30 minutes.config.pkgs jndi. Task 6: Upgrade Database Schema from Previous Release If this is an upgrade from a previous installation of SAP E-Sourcing an upgrade of the database schema may be required.optimization.AllocationStatusQueue com.config.engine. If you wish the application to have a different timeout value.xml file.sap. The deployment descriptor for the SAP E-Sourcing application is located in the <FCIHOMEDIR>/deploy/web.sap. The following provides an example <session-config> specifying a 30-minute session timeout: <session-config> <session-timeout>30</session-timeout> </session-config> Note that any change to the application deployment descriptor requires that the EAR file be rebuilt using the configure utility.naming.factory.request_destination optimization.java.AllocationRequestQueu e jmsqueues/default/fs.optimization.url jmsqueues/default/fs.halt_destination optimization.naming.factory.tm.services.initial jndi.naming.optimization.config.Post-installation Procedure 1 Installing the E-Sourcing Platform Optimizer System Properties: Field Value optimization.optimization.java.jndi.providers localhost:50004 Task 5: Update Session Timeout (Optional) The application server is responsible for the timeout of inactive user sessions.java.config.queue_connection_fact jmsfactory/default/fs. 18 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . The release notes will also provide details of how to apply the upgrade.HaltAllocationQueue jmsqueues/default/fs.jndi.QueueConnectionFacto ory ry optimization.InitialContextFactoryImpl com.provider. Refer to the release notes to determine whether an upgrade of the database schema is required. you can add a <session-config> node to the <web-app> node within the application deployment descriptor.url.

The file must be installed on each server. click Remove. If it is. If the application server supports auto deployment you can simply copy the fcsourcing./go 2 3 4 5 6 7 Navigate to Server-->Services-->Deploy--> Runtime tab--> Applications button. Once it is started. consult your application server documentation. you may need to undeploy the application before redeploying the new EAR file.com/fcsourcing). File: <BASE>/fsapp/fcsourcing. Task 8: Generate License File for E-Sourcing Explorer For the E-Sourcing Explorer to function. The EAR can now be deployed to the application server. each application server must be licensed to run the Explorer applet. Verify that the application is not already deployed (at sap. They will be used to generate a license file.1 Installing the E-Sourcing Platform Post-installation Procedure Task 7: Deploy the Application EAR File to the Application Server The Enterprise Application Archive (EAR) file is located in the <FCIHOMEDIR>/fsapp directory. Click Deploy & Start. verify that the application is running at the following location: http://<hostname>:50000/esourcing/fsbuyer/portal/login To deploy on a different application server.ear Click OK. Start the Visual Administrator by entering the following commands: cd /usr/sap/<SAPSID>/<JC00>/j2ee/admin . To deploy on a NetWeaver application server: 1 Start the Visual Administrator as follows: a b Log on to your host as user <sapsid>adm. The IP addresses of all application servers that host SAP E-Sourcing should be collected. If the application was previously deployed. You can also deploy the E-Sourcing application using the administrative console for the server. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 19 .ear file into the application server’s deployment directory.

select System Information from the System Management drop-down list and click OK. 20 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . Click Setup at the top of the page. The Audit page includes a set of criteria and indicates whether the criteria have been met. To verify the production readiness. perform the following steps: Log into the system as a user with system administrative permission. Under System Administration.Post-installation Procedure 1 Installing the E-Sourcing Platform Task 9: Verify Production Readiness Criteria Once the application has been deployed. Click the Audit tab. the production readiness can be verified from the System Information page in Setup.

2 Installing the E-Sourcing Optimizer This chapter describes how to configure and deploy the Optimization module and how to configure SAP E-Sourcing to use it. This chapter covers the following topics: Overview on page 22 Pre-installation Procedures on page 22 Installation Procedures on page 25 Post-installation Procedures on page 26 Confidential 21 .

3 Jetty 3. Technically.3.3. see the JBoss Configuration Guide: http://www.Overview 2 Installing the E-Sourcing Optimizer Overview The following examples are based on the JBoss server. the system will still function if the Optimizer is run on the same machine in a different Java VM.3-1 Optimizer J2EE Application Server 22 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .4.52 IBM HTTP (Apache) Server 4. but this is strongly discouraged.jboss. Recommended Server Topology The following figure shows the recommended server topology.org/online-manual/HTML/ Pre-installation Procedures The Optimizer must be installed on a machine that is physically separate from the SAP E-Sourcing server. set up the standard SAP E-Sourcing environment.19 JDBC Sourcing Database Http Client SSL Web Server Http LDAP J2EE Application Server LDAP Directory JDBC SMTP JMS SMTP Gateway Windows 2000 JBOSS 2. Before deploying the Optimization module.1. but can be extrapolated to other application servers. Recommended Server Topology Windows 2000 IBM Global Security Toolkit 5.0. Note: For more information on the JBoss software.

The Optimizer will not function if this is not the case. these queues should be used only for SAP E-Sourcing. Note: The alias is the coded name that is used for locating each queue. However. Below is a list of the required queues and the JNDI aliases that should be created for each queue. JMS Queue and JNDI Alias Mappings Resource fs.optimization.AllocationStatusQueue fs.AllocationStatusQueue fs.HaltAllocationQueue fs. The Optimizer requires the same command line arguments and classpath parameters as the E-Sourcing server. Having both an actual queue and an alias is the best practice for working with JMS. Furthermore. There should not be a single queue with multiple aliases.HaltAllocationQueue App Server QueueConnectionFactory Type Queue Queue Queue Connection Factory JNDI Alias fs.2 Installing the E-Sourcing Optimizer Pre-installation Procedures Runtime Environment Variables and ClassPath Follow the steps outlined in the SAP Required Libraries and Java Memory Settings sections of the Post-installation Procedures in Chapter 1: Installing the E-Sourcing Platform.AllocationRequestQueue fs. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 23 .optimization.optimization. Below are the instructions for some common management interfaces.QueueConnectionFactory Creating New JMS Message Queues and JNDI Aliases The process of creating new message queues and aliases varies from application server to application server. Configuring JMS Queues The Optimization module uses JMS to facilitate communication between the SAP E-Sourcing server and the Optimization server.optimization. Homogeneous JVM Environment The Optimization server must be run with the same version and vendor for JVM software as the SAP E-Sourcing server. the aliases are not strictly required if the queues themselves use the coded names. It is also very important that each queue be distinct. This requires that several messaging queues must be configured before the Optimizer can be used successfully.AllocationRequestQueue fs.

jcml“.jboss.name=fs.jboss.naming.AllocationStatusQueue"/> <mbean code="org.NamingAlias" name="DefaultDomain:service=NamingAlias.server. below. enter the queue name and click the CreateQueue button.Pre-installation Procedures 2 Installing the E-Sourcing Optimizer JBoss Management Console Assuming JBoss is running.QueueManager" name="JBossMQ:service=Queue.BEGIN FS OPTIMIZATION ALIASES --> <mbean code="org.mq.jcmi file: 1 Locate the Message Queue section by searching for QueueManager.fromName=fs.AllocationRequestQueue"/> <mbean code="org. JBoss Configuration File: jboss.mq.jcml For general information on modifying this file. Replace localhost with the hostname of the Optimization server.mq.server.name=fs. To modify the jboss. You must manually modify the JBoss Configuration file. and paste the following under the existing queue declarations: <!-.QueueConnectionFactory</attribute> </mbean> <mbean code="org.fromName=fs. see the JBoss Configuration Guide: http://www.naming.jboss.BEGIN FS OPTIMIZATION QUEUES --> <mbean code="org.HaltAllocationQueue"/> <!-.server.Queue ConnectionFactory" <attribute name="ToName">ConnectionFactory</attribute> <attribute name="FromName">fs.Alloc ationStatusQueue"> 24 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . Browse to the JBossMQ section and click on the link service=Server Scroll down to the “Description of createQueue” section. you can reach the management console by browsing to http://localhost:8082/. Note: At the time this document was written. ■ For each of the Optimizer queues.jboss.org/online-manual/HTML/ For SAP E-Sourcing. you must cut and paste two sections into this file.QueueManager" name="JBossMQ:service=Queue.QueueManager" name="JBossMQ:service=Queue.jboss.name=fs.optimization.END FS OPTIMIZATION QUEUES --> 2 Locate the naming alias section (search for NamingAlias) and paste the following under the existing aliases: <!-.jboss.optimization.NamingAlias" name="DefaultDomain:service=NamingAlias. See “JBoss Configuration File: jboss.optimization. the JBoss management console did not provide a mechanism for creating JNDI aliases.

naming. Deploying the Optimizer To deploy the Optimizer for JBoss: After Message Queues and JNDI aliases are created. Note: The Optimizer will not function without a valid license.NamingAlias" name="DefaultDomain:service=NamingAlias.AllocationStatusQueue</attribute> </mbean> <mbean code="org. The Optimizer is deployed to ${JBOSS_HOME}/deploy.optimization.AllocationRequestQueue</attribute> <attribute name="FromName">fs.AllocationRequestQueue</attribute> </mbean> <mbean code="org.optimization.HaltA llocationQueue"> <attribute name="ToName">queue/fs.jboss. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 25 .fromName=fs.optimization.jboss. This is not necessary when working with the management console.NamingAlias" name="DefaultDomain:service=NamingAlias. Installation Procedures Installing the Optimizer License Refer to the licensing information that shipped with the Optimization module.optimization.HaltAllocationQueue</attribute> <attribute name="FromName">fs.fromName=fs. you must restart JBoss.Alloc ationRequestQueue"> <attribute name="ToName">queue/fs.naming.AllocationStatusQueue</attribute> <attribute name="FromName">fs.optimization.HaltAllocationQueue</attribute> </mbean> <!-.2 Installing the E-Sourcing Optimizer Installation Procedures <attribute name="ToName">queue/fs. launch the Optimizer installer and direct it to your JBoss home directory.END FS OPTIMIZATION ALIASES --> Note: If you directly edit the configuration files.

Typically.naming.use_local_jndi If set to TRUE. this is org.naming. For JBoss. such as RFx and Auctions.interfaces. JMS. In general.NamingContextFactory. ■ optimization. this should be hostname:1099.jndi.naming. 26 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .jnp.factory. For JBoss. Enable the optimization functions for each specific module.pkgs. For JBoss.jndi.naming. This is equivalent to the standard J2EE property.url The JNDI provider URL for your application server. ■ optimization.properties file in the classpath whenever accessing a JNDI resource. ■ optimization.java. Select the table entry for JNDI and review the following settings: ■ optimization.jboss. Browse to the System Properties page and search for JNDI. you must configure SAP E-Sourcing to indicate that it is available for use.java.interfaces. and so forth.pkgs This refers to the packages in which your application server stores remote interfaces for JNDI.java. This is equivalent to the standard J2EE property. Perform the following two post-installation tasks: Identify the Optimization server.factory.naming.factory. where hostname is the name of the machine that holds the JNDI lookup information for the Optimizer. jndi. SAP E-Sourcing uses the standard jndi.naming.naming.factory.provider. This is equivalent to the standard J2EE property.url.java.java. this is the hostname of the Optimizer server unless you are running with a JMS clustering environment.initial This is the fully qualified class name of the JNDI InitialContext factory for your application server. this should always be set to FALSE. Identifying the Optimization Server To identify the Optimization server: 1 2 3 Log on to SAP E-Sourcing using the SystemContext (/fssystem/portal/login).provider.jnp.java.naming:org.Post-installation Procedures 2 Installing the E-Sourcing Optimizer Post-installation Procedures After the Optimizer is deployed.url. jndi. jndi.jndi.url. this would be org.initial.

3
Installing Contract Generation
This chapter describes how to install Contract Generation on a Windows 2000/2003 Server. It also explains the preliminary installations and configurations required before you install. This chapter covers the following topics: Pre-installation Procedures on page 28 Installation Procedures on page 28 Post-installation Procedures on page 29

Confidential

27

Pre-installation Procedures

3 Installing Contract Generation

Pre-installation Procedures
The contract generation service is a Microsoft .NET service. A typical installation would install the service on a separate machine independent of the application server. However, the service can be installed on any server that meets the requirements. The following must be installed and configured before installing the contract generation service: Microsoft Windows 2000/2003 server Internet Information Services (IIS) Microsoft .NET Framework 2.0 Run Windows Update and install all patches and updates, including those for Windows, IIS, and the .NET framework. Read the following article to understand how to install and configure Office applications to run as a specific user: http://support.microsoft.com/default.aspx?scid=kb;EN-US;288367 Note: When performing this configuration, you do not need to perform step 18, which describes how to set up an NT service. Install Microsoft Word 2003 as follows:
n n n

Run the Office 2003 setup and select only the Word 2003 option for installation. Select Choose Advanced Customization of Application. On the following page, expand and select all the available nodes in the tree, especially all the .NET Programmability Support nodes.

There is a known issue with the following Microsoft Office Update: Applying this update prevents the contract generation service from working. Excel 2002 Update: October 16, 2002 Prevents users from unintentionally updating links to external data within Microsoft Excel spreadsheets. http://www.microsoft.com/downloads/details.aspx?FamilyID=09708964-A8D6-4F4 E-9D82-280E08F36E8A&displaylang=en DO NOT apply this update to the server running the contract generation service.

Installation Procedures
You must have administrator privileges to install the contract generation service. Be sure to log in as a member of the administrator group. The Setup program for contract generation is provided on the distribution media. Once the prerequisites have been met, simply run the install program WordServiceInstaller.msi.

28

Confidential

SAP® E-Sourcing Software Installation and Configuration Guide

3 Installing Contract Generation

Post-installation Procedures

You will be prompted to enter the Virtual Directory and Site where the web service should be installed. This information will be required to properly configure the FCI application to communicate with the service.

Post-installation Procedures
1

Log into the Web Service machine as the OfficeAutomationUser and start Microsoft Word. In Word, do the following:
a

Set the default file format to the format that is appropriate for your deployment. You can find this setting by clicking the following: Tools -> Options -> Save - Default Format -> Save Word Files As Add the FCI Schema to the Schema library. Click the Add Schema button, browse to the directory where the web service is installed, and select the fci.xsd file. You can find the Schema library by clicking the following: Tools -> Templates and Add-ins -> XML Schema Set the default Web encoding to Unicode (UTF-8). You can find this setting by clicking the following: Tools -> Options -> General -> Web Options -> Encoding

b

c

2

Create the fci directory on the server. Create logs and temp subdirectories under the fci directory. It is recommended that you create this directory directly under the main drive (for example, C:\FCI, C:\FCI\logs, C:\FCI\temp). Locate the web config file under the following directory: inetpub\wwwroot\<virtual directory>\ and set the fciDir application key value to the fci directory you just created under the <appSettings> section (for example, check and set the first node to <add key=”fciDir” value=”c:\FCI”/> Change the values for the other appSettings section parameters in the web.config file as follows:
n

3

4

showWord: Make MS Word visible or not. Normally set it to false in deployment and true in debug. logLevel: Indicate the level of detail in the log information. Set either to debug or info level. wordRunNumber: The contract generation server will regularly shut down MS Word and restart it after the specified number of operations to improve the Word performance. requestTimeout: the contract generation server can only process one request at a time. Other requests are queued. If a request has been in the queue a specified length of time, it will time out. Set the timeout number in seconds.

n

n

n

SAP® E-Sourcing Software Installation and Configuration Guide

Confidential

29

Post-installation Procedures

3 Installing Contract Generation

n

A timeout mechanism is used to catch Word message box exceptions. For example, if Word cannot open a document in 30 seconds, it is assumed that Word is frozen by a message box waiting for user interaction, which is not supported. In this case, an exception will be thrown and Word will be restarted. Common Word operations such as open file, save file and insert file are monitored.
n n n n n

openFileTimeout: maximum time (in seconds) allowed to open a file using Word. saveFileTimeout: maximum time (in seconds) allowed to save a file using Word. closeFileTimeout: maximum time (in seconds) allowed to close a file using Word. insertFileTimeout: maximum time (in seconds) allowed to insert a file using Word. compareDocsTimeout: maximum time (in seconds) allowed to compare two Word documents using Word.

5

To clean up obsolete Word instance and the temporary directories, it is necessary to impersonate the automation user with the buildin ASPNET account. DPAPI is used to encrypt the identity sections in ASP.NET 2.0 to protect sensitive account information. Please refer to the following link: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/paght000005.asp In summary, the steps are as follows:
a b

Create a new Web site named MachineDPAPI. Ensure that this directory is configured as a virtual directory. Add a Web.config configuration file to this directory. Add the following content to the file, substituting the correct username and password: <?xml version="1.0"?> <configuration> <identity impersonate="true" userName="domain\automationUserAccount here" password="account password here" /> </configuration>

c

Open the .NET 2.0 command prompt (start->All Programs->Microsoft .NET Frameword SDK 2.0->SDK Command Prompt, or open the Command Prompt and cd to directory Windows\Microsoft.NET\Framework\v2.0.xxx on the Windows 2003 server) and enter the following command: aspnet_regiis -pe "identity" -app "/MachineDPAPI" -prov "DataProtectionConfigurationProvider" You should see the output as:

30

Confidential

SAP® E-Sourcing Software Installation and Configuration Guide

dll in the Run dialog box on the Start menu. It is recommended that you change this default value to a value in the 50-100MB range. Verifying the installation Verify the installation by typing the following URL into your browser: http://<host_name>:<port>/<virtual directory>/wordservice. The dll is correctly included in the setup and will be written to the web application folder during installation.dll.NET version is 2. Configuring SAP E-Sourcing Log into the E-Sourcing Application as the System Manager and set the following: On the System Property List page. The [filepath] should be similar to: \inetpub\wwwroot\wordservice.com/en-us/library/e1f13641. Succeeded! d 6 Open this Web. do the following: a b Locate the maxRequestLength property in the web.config file before the AUTHENTICATION section.asmx SAP® E-Sourcing Software Installation and Configuration Guide Confidential 31 .config file and change the value as desired (the value is displayed in KB and is 4096 by default.. To register it properly. Under ASP.NET2.asmx You see a Service Description page for the FCI Word Automation web service.aspx for other httpRuntime schema node settings.NET. edit the contractgen.0 framework is selected for the installed WordService web site. The SOAP messages built during contract generation can easily exceed this limit. but it is not being registered with the OS. ensure that ASP. refer to http://msdn2. not 1.xxx..xxx. 7 Make sure . Right-click WordService.0.) Optionally.3 Installing Contract Generation Post-installation Procedures Encrypting configuration section. Click OK to save the changes if needed.1.serviceurl with the following: http://<host_name>:<port>/<virtual directory>/wordservice. Go to the IIS manager-><Locale computer name>->Web Sites-> Default Web Sites. The default POST limit for IIS is 4MB. as follows: a b c d 8 The contract generation web service makes use of a Microsoft dll called Dsofile.microsoft. perform the following steps: n Type regsvr32 [filepath]\dsofile.config file and copy the generated identity section to the WebService Web. To change this value.

Post-installation Procedures 3 Installing Contract Generation 32 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .

4 Deploying SAP E-Sourcing This chapter describes how to deploy SAP E-Sourcing. This chapter covers the following topics: Overview on page 34 Access and Login on page 34 Clusters on page 35 Contexts on page 35 Master Data on page 36 Building a Simple Custom Enterprise on page 44 Confidential 33 .

The second task is to install the master data that will be shared by all sourcing companies within the enterprise. portal and instructions defined in the following sections of this manual. This data is generally installed using the built-in enterprise administration account (although ongoing maintenance should be handled by actual activated users).The first task when developing a new E-Sourcing enterprise is to define the system-level components that will ultimately manage your data and user deployment. An enterprise consists of at least one cluster and one context. Define Cluster Define Context Define Numbering Tables Define Extensions Enterprise Master Data Installed as Enterprise Administrator Define Accounts System Setup Data Installed as System Administrator Define Activities Define Cost Centers Sourcing Company Master Data Installed as a valid account Define Materials System setup phase . This phase is distinguished from the second phase because it must be applied to each installed company with its own context. Most master data falls in this category. Enterprise setup phase . Contexts serve to create a logical definition of how data should be shared or not shared in a complex business environment. contexts manage access to information across a corporate deployment. Company setup phase . 34 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . In short.The last phase of any deployment is to install master data specific to each company.Overview 4 Deploying SAP E-Sourcing Overview The following diagram outlines the basic deployment process. Access and Login SAP E-Sourcing provides the following default system administrator login IDs and passwords for access during implementation. Clusters serve to map users to a deployment instance when an environment contains multiple instances of E-Sourcing. Define Contexts and Clusters using the default system administrator login.

Clusters define how one sourcing context is differentiated from another. and global system properties. Used to bootstrap the enterprise by installing everything from numbering tables to accounts. Once real accounts are installed. see the Setup section of the Online Help. A cluster defines how end users access the E-Sourcing application. System Administrator Access Name System Administrator Enterprise Administrator Login ID system enterprise Usage Use for creating and managing contexts. This is most commonly used in a complex or global environment when international requirements or corporate divisions require that master data is managed separately. Define Contexts and Clusters using the login and passwords defined below. The system requires that at least one cluster exist within an enterprise. and serve as the root of the entire deployment. For example. Contexts Contexts define how master data and security are managed across a complex enterprise. Create your initial cluster by logging into the administration portal page as the system administrator and selecting Cluster Configuration from the Setup page. disable the use of the system accounts after creating custom accounts specific to your organization.. clusters. Contexts provide the ability to logically separate and duplicate master data components so that they can be managed differently across a conglomerate. Use Contexts to restrict a series of master data components from being shared across an enterprise. you define a cluster to map a large volume of related users to a specific instance of a deployment when multiple instances exist within the same server. For more information about clusters. they should be used for any remaining configuration. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 35 .4 Deploying SAP E-Sourcing Clusters Note: System Administrator rights are required to create initial Contexts and Clusters. Note: To ensure that your system remains secure. Clusters A cluster is a logical group of machines. At least one sourcing context must be set up for an enterprise.

For more information about contexts. see the Setup section of the Online Help. Create and configure contexts by logging in as the system administrator (system account) and clicking Enterprise Contexts on the Setup page. Default value list types. Hierarchical contexts can be used to keep one company's sourcing data separate from another’s. time zones. A data classification of Configurable indicates that default data is provided but can be customized for deployment. even within an enterprise. The following table lists the master data object types requiring definition for the enterprise. such as countries. Default list of extendible enterprise-level objects. etc. For example. For simplicity. where nnnn increments for each new rfp created. an RFP might follow the format: RFP-nnnn. the examples in this chapter all employ single-context configurations. Enterprise Master Data Contents Data Classification Description Defines the format of IDs. Master Data Define the components of master data that exist within each context after contexts and clusters have been defined. Value List Types Value List Values Units of Measure Currencies Configurable Configurable Configurable Configurable 36 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .Master Data 4 Deploying SAP E-Sourcing There are two primary benefits of sourcing contexts: A sourcing context is the vehicle used to distinguish one enterprise from another in the system database. This list identifies the allowed kinds of references. Lists those enterprise-level objects which can be extended. A data classification of Custom indicates that no default data is provided and the deployment must provide the data. Configurable Default list of objects that can Configurable used referenced in an extension. Standard units of measure used throughout the system A list of all currencies used by your organization Numbering table definitions for Configurable enterprise-level objects. Default value list values. One type of extension allows a reference to another type of object.

Types define what set of Auction features are available. Types define what set of RFx features are available. Identifies the security profiles installed with the system. Defines the rights for each security profile. etc. Used to define categories of scheduled tasks. years. Types define what set of Project features are available. Types define what set of Demand features are available. Defines information about quarters. Sets up the default collaborators and security when new documents are created. Channels available on a user's desktop. Time Periods Reporting Calendars Collaborator Roles Document Security Templates Shared Discussions Workbench Channels Workbench IFrames Workbench Channel Configurations Data Classification Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Configurable Description Default values for any currency conversion rates Lists the allowable kinds of document links. A list of discussion forums available as a channel and not relating to a specific document. Defines the role (rights and responsibilities) of a person/group on a specific document instance. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 37 . Lists scheduled/background tasks. Used for managing how data is reported with relation to the calendar. Used to define terms on contracts Types define what set of contract features are available.4 Deploying SAP E-Sourcing Master Data Enterprise Master Data Contents Currency Conversions Document Link Definitions Scheduled Task Types Scheduled Tasks Metrics Contract Terms Contract Types Project Types RFx Types Auction Types DA Types Security Profiles Rights on security profiles. Data to create iFrames Channel configuration parameters. Used to define metrics for scorecards.

Used for the LDAP directory configuration TBD The locations of plants. TBD Typically this data set consists of industry standard category codes. business units. such as UN-SPSC or SIC codes. The actual extensions on enterprise-level objects. Use to define departments. if used by your organization This data set describes all internal purchasing categories used by the buyer. Used during vendor self-registration. etc. companies and other organizational elements.Master Data 4 Deploying SAP E-Sourcing Enterprise Master Data Contents Workbench Pages Data Classification Configurable Description Pre-defined desktop pages. Workbench Page Configurations Configurable Configuration Properties Enterprise Extensions Directory Configurations Geographies Locations Payment Terms External Categories Configurable Custom Custom Custom Custom Custom Custom Internal Categories Vendors Custom Custom Vendor Extensions in List Form Custom Companies Registration Categories Custom Custom Organizational Units Custom 38 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . including mail. Used by all components of the system for purchasing actions such as Auctions and RFP's Defines mapping from arbitrary category names to actual internal or external categories. Various deployment settings. The actual extensions on enterprise-level objects. etc. Vendor data is used in all components for various purchasing actions. Further definition of the organizational hierarchy. Channel content and placement settings for predefined pages.

Sets up the default collaborators and security when new documents are created.4 Deploying SAP E-Sourcing Master Data Enterprise Master Data Contents Groups Contacts Accounts Terms Templates Data Classification Custom Custom Custom Custom Description Arbitrary groups of buy-side users. Used for general accounting purposes Used for accounting purposes to assign cost on a center by center basis. List of company-scoped objects which have extensions. List of extensions on individual object types. Company Master Data Contents UFNs System Answered Sources Data Classification System Configurable Description Metadata for RFx utility functions. Used for all vendors to distinguish the various contacts at each vendor Handles all user accounts for the system. so this data must only be created once. Company Extension Definitions Configurable Document Security Templates Contract Generation Phases Contract Generation Tags Company extensions masterdata. Standard terms and conditions phrases to which a vendor must agree before accessing an event. This data must be created once for each sub-context. After configuring the enterprise master data. This example only uses a single context. Defines the available sources of system answered questions. Used to define Phases for Contract Generation library documents Used to define Tags for Contract Generation. you must next configure the company master data.Activity Cost Centers Cost Center Groups Entities Configurable Configurable Configurable Custom Custom Custom Custom Custom Used for accounting purposes for purchasing by division SAP® E-Sourcing Software Installation and Configuration Guide Confidential 39 .

For initial deployment of the system. Installing Master Data provides the following means to install master data: Manual entry via Setup Import via CSV file Import via deployment workbook Enterprise master data can be defined manually by logging in (as the enterprise administrator) and creating objects from within the Setup module. 40 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . facilities. Choose the item of interest. To access this file. At this point.Master Data 4 Deploying SAP E-Sourcing Company Master Data Contents GL Accounts Plants Materials Category Managers Data Classification Custom Custom Custom Custom Description Used for general accounting purposes Plants. An empty CSV in the correct format can be downloaded from the application using the import facility. The following mechanisms are used to determine the format of the CSV files: The online Reference Guide (RG) includes information for each object that can be imported as a CSV. Select Import Data from Setup and attempt to upload any file with the . The system will recognize that you are interested in CSV files and prompt for the type of object to be imported. a sample CSV called template.csv extension.csv can be downloaded. click CSV View. The users who are responsible for certain categories. along with example data. it is recommended that the deployment workbook be used to ensure that all required data is imported into the system. The Enterprise QuickStart. then click Next. CSV File Format Most organizations will choose to import a large number of the master data objects via standard CSV files. Standard materials for use in line items.xls file can be downloaded from the online Reference Guide (RG). You must log in as a sourcing administrator (a real user) in order to configure company master data. This file includes every master data element in the correct format. Once the object is found in the Reference Guide. click RG at the top of the screen and then click Enterprise Deployment Workbook.

Click OK. Log into the enterprise. Under System Administration. select the object type and click Next. Using a client application distributed with the system. go to the Import Data page as follows: a b c 3 Click Setup. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 41 . using the web-based UI. On the Setup page. Click Finish to view the results. If users have not been added. which allows data to be imported outside of the web environment. select Import Data from the Import and Export Tools drop-down list. Indicate whether you want to wait for the import to finish or perform the import in the background and click Next. is as follows: 1 2 Open a browser and select the login page: http://yourhost/fsbuyer/portal/login. log in as a user with administrative rights.4 Deploying SAP E-Sourcing Master Data Importing Master Data Master data files (CSV or XLS) can be imported in two ways: Using the standard web user interface. use the enterprise administrator built-in account. For CSV files. Specify whether you want to upload the file to the server or whether the file is already located on the application server and click Next. The standard way to import master data files. If application users have already been created. 4 5 6 7 8 9 Select Create to start the import wizard. Use the Upload Import File picker to load the CSV or Deployment Workgroup file to import.

whichever is appropriate for your operating system.bat or dbinstall. The DB Importer tool will open.csh. If system users have already been created. If users have not been added. Choose the destination context (for example. and go to the bin directory. do the following: 1 2 Locate the home directory. Click the Lookup icon for the File field and select the file to import. typically c:/fci or d:/fci.Master Data 4 Deploying SAP E-Sourcing To install master data via the client DB Install tool. 3 4 5 Click the Lookup icon for the Context field. Acme Enterprise) where the data should be inserted or updated. 42 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . Use the Username and Password text fields to set the login parameters. log in as a user with administrative rights. use the enterprise administrator built-in account. Run the program dbinstall.

After a few minutes. Two example deployment workbooks ship with the system: Enterprise Deployment Workbook Company Deployment Workbook SAP® E-Sourcing Software Installation and Configuration Guide Confidential 43 . Working with the Deployment Workbooks To facilitate the import of data. the import will complete. 8 Close the DB Import tool. The Script tab should show nothing but green check marks.4 Deploying SAP E-Sourcing Master Data The Import Settings now appear as follows: 6 7 Click Run. SAP E-Sourcing provides the ability to import Microsoft Excel files containing one or more master data imports. Click the Status tab to see the progress of the import. E-Sourcing provides an alternative to CSV files for import. The system can handle these Excel files directly without first forcing the user to export the data to a raw CSV file.

The deployment workbooks are included in the online Reference Guide (RG). The current implementation methodology recommends defining these attributes prior to going live to maximize efficiency. The Help Sheet describes the rules that must be observed. The same importing process supports both CSV files and Excel workbooks. Groups. but there are limitations to what Excel constructs are supported. and Users Sell-side organizational data: Vendors and Contacts Commodity Information: Internal and External Categories. Keep the following in mind when using deployment workbooks: The Configuration Sheet controls the import process. Data attributes may be modified or added throughout the live of the implementation using the Setup module. preserve the original workbook templates by saving them with a new name. When starting a new deployment project. This ensures continuity if additional deployments are required in the future. Note: This guide assumes that the default values are accepted for the remaining data types. Import data using your modified templates only. Gathering Critical Information For each deployment. The system can import the workbooks directly. Refer to the Help Sheet for input specifications of Configuration Sheet columns. Companies. 44 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .Building a Simple Custom Enterprise 4 Deploying SAP E-Sourcing The deployment workbooks can be downloaded from the web user interface by anyone with system administrator access rights. gather critical information. Building a Simple Custom Enterprise This section illustrates the steps needed to deploy a custom enterprise that leverages much of the setup information in the deployment workbooks. Business Units. including (but not limited to): Buy-side organizational data: Locations.

Apply the same process to org_units. If you want to build all custom data in the UI. Open the file and find the sheet labeled locations. enter manager. Edit this sheet as necessary. Provide at least one external category. 2 Click Cluster Configurations on the Setup page and then click Create. you can use any id. Edit it as necessary. enter system.) Select Login. Be aware that a hierarchy is being established.id (for example. Only one location is required. Note: Configuring a cluster can be a complicated task. See the Help page for instructions on how to skip a specific worksheet. the PARENT column in the business_units page should include a valid EXTERNAL_ID from the companies sheet. accounts. The steps below assume a basic knowledge about clusters and system administration.cluster. Configuring the hierarchy correctly requires that the child reference the parent correctly.4 Deploying SAP E-Sourcing Building a Simple Custom Enterprise Customizing Data Input Workbooks The easiest way to get started is to modify the default deployment workbooks. (You may have to see your system administrator for an updated password. For example. Note: Installing a Cluster 1 Log into the system as follows: a b c For Username. Customize default workbooks using the following procedures: 1 2 3 4 5 6 Download the Enterprise Deployment workbook. Find the sheet labeled external_categories. See the Setup section of the Online Help for more information about setting up clusters. simply deactivate the import of the above data types in the deployment workbook. Provide at least one internal category. For Password. Edit it as necessary. Find the sheet labeled companies. groups. Find the sheet labeled internal_categories. etc. 3 Configure the cluster with the following parameters: n Cluster Identity: acme. Edit it as necessary. you can use any name you wish) n SAP® E-Sourcing Software Installation and Configuration Guide Confidential 45 . but it can't have spaces or special characters) Display Name: ACME Cluster (for example.

Select a service and make sure the Is Active checkbox is selected. Default Cluster: ACME Cluster (the one created above) n n 3 4 Click Save Document. Note: Installing a Context 1 2 Click Enterprise Contexts on the Setup page and then click Create. For the Password. any id will do it can't have spaces or special characters) Sys Admin Password: Enter something you can remember. Click Setup to return to the Setup page. go to the Import Data page as follows: a b c 46 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . type the value you entered when you created the context. The steps above will set the public hostname of the cluster to "*". Make sure that only one cluster is configured with the "*" token. This may take several minutes. Create a new context with the following parameters: n n Display Name: ACME E-Sourcing Context (as an example. The system creates a new Enterprise E-Sourcing context to hold your data. 3 On the Setup page. enter the name of your host.id (as an example. This is a special token which matches any HTTP request to the server. type enterprise. Log out. any name will do) External ID: acme. Log into the new enterprise as follows: a b c For the Username. select Import Data from the drop-down list.context. 4 5 Click Save Document. Under Import and Export Tools. Click Login. Click Setup.Building a Simple Custom Enterprise 4 Deploying SAP E-Sourcing n n Hostname: * Add your host to the cluster member list. Open a new browser and go to the login page: http://yourhost/fsbuyer/portal/login. Installing Master Data 1 2 Close your browser. Click OK. In the Service Hostname box.

Click Save Document. Attach your logo image to the company using the Logo Attachment field. type enterprise. Follow the prompts in the import wizard. 8 9 10 Look at the property list. select it and click Edit. Use the Import wizard Upload Import File picker to load your enterprise workbook. 3 Open the company list as follows: a b c 4 5 6 7 Select the enterprise company from the list and click Edit Document. For the Password. Repeat the import wizard for each company workbook. Log out. follow these steps: 1 2 Go to the login page: http://yourhost/fsbuyer/portal/login. select Companies from the drop-down list. You are now ready to return to the login page and log in as one of the users you have added. Set the Property Value to the following: SAP® E-Sourcing Software Installation and Configuration Guide Confidential 47 . click Create.4 Deploying SAP E-Sourcing Building a Simple Custom Enterprise 4 5 6 7 8 Select Create to start a new import job. Log into the new enterprise as follows: a b c For the Username. Otherwise. Installing the Company Logo To upload the company logo. Set the Property Set to userinterface. Click OK. Click Setup. If there is an entry for buylogoimage. Under Organization and Accounting Information. select System Properties from the drop-down list. Click OK. Under Configuration. type the value you entered when you created the context. Go to the System Properties page as follows: a b c Click Setup. Click Login.

13 Log out.id> specifies the External ID from the company where the logo is attached <image. Reload the property cache as follows: a b c d Click Setup. select System Information from the drop-down list.gif> Where this is true: n n <company.gif 11 12 Click Save Document.gif> specifies the name of the image which was attached to the company An example would be: /images/companylogo/acme/acme_logo. Under Administrative Reports. 48 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .Building a Simple Custom Enterprise 4 Deploying SAP E-Sourcing /images/companylogo/<company. Click the Cache tag and select Refresh for the properties cache.id>/<image. The new company logo is displayed. Click OK.

Appendix A: Performance Tuning This appendix describes performance tuning for version 3.01. This appendix covers the following topics: Overview on page 50 WebLogic Native I/O Performance Pack on page 50 WebLogic Socket Readers on page 50 WebLogic Execution Threads on page 51 Sun JVM Threading Model on page 51 Sun JVM Heap Size on page 51 Confidential 49 .1.

The socket reader parameter specifies the percentage of execution threads that can be used as socket readers.1. This allows 80 percent of the execution threads to be used as socket readers. a majority of the threads are set to handle server requests.2 on the Solaris 8 Platform. it is likely to be enabled.4 compliant JVM that has been certified with WebLogic 8. Since this is the default setting for the WebLogic server. You can change this value in the WebLogic Admin Console under Server\Configuration\Tuning. This value should be changed to reflect the fact that most execution threads are used as socket readers. The Native I/O performance pack is a platform-optimized socket multiplexor that has demonstrated major performance improvements over the native Java implementations. The recommended value is 80 percent. The default value for this setting is 33 percent.Overview Appendix A: Performance Tuning Overview The following are the recommended performance configurations for SAP E-Sourcing 3. 50 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . Note that these configurations were tested in the SAP QA LAB on a Sun E450 with 2G of memory. WebLogic Socket Readers Within the SAP E-Sourcing application. These recommendations assume the use of the 1. The following configurations are recommended for this environment: WebLogic Native I/O Performance Pack WebLogic Socket Readers WebLogic Execution Threads Sun JVM Threading Model Sun JVM Heap Size WebLogic Native I/O Performance Pack Verify that the server is using the Native I/O Performance pack. You can verify this setting in the WebLogic Admin Console under Server\Configuration\Tuning.

The one-to-one model allows each Java thread to map to its own kernel thread. 25 threads may be a more appropriate number. Since the activity to process a user's request often results in database activity. add the following lines to the WebLogic startup script: # switch to the alternate 1:1 threading library in Solaris 8 if [ -n "${LD_LIBRARY_PATH}" ].Appendix A: Performance Tuning WebLogic Execution Threads WebLogic Execution Threads The SAP E-Sourcing application currently uses the default execution threads. Set the following parameter in the WebLogic startup script to enable AggressiveHeap: SAP® E-Sourcing Software Installation and Configuration Guide Confidential 51 . as they can conflict with AggressiveHeap. The goal of these settings is to optimize the JVM for long-running server applications that allocate a substantial amount of memory. You should monitor CPU load and verify that the load is not exceeding the CPU capacity. You should remove any previous memory settings such as minimum and maximum heap size. The default thread count is 15 in development mode and 25 in production mode. which is the one-to-one model. then LD_LIBRARY_PATH="/usr/lib/lwp:${LD_LIBRARY_PATH}" else LD_LIBRARY_PATH="/usr/lib/lwp" Fi Sun JVM Heap Size Application performance is directly related to the amount of memory available and the performance of the garbage collector. To enable the alternative thread model. Sun JVM Threading Model Two different threading models are available to the JVM under Solaris. Solaris 8 provides the option to use the “alternative” thread model. For a dual processor machine. The AggressiveHeap option allows the JVM to inspect the machine resources and various Java memory parameters such as heap size. The alternate thread library provides better utilization of the multiple CPUs. These models are known as the many-to-many model and the one-to-one model. The many-to-many model is the default prior to Solaris 9. You can change this value in the WebLogic Admin Console by right-clicking the server name and selecting View execute threads. The recommended value for this setting is 50. the default thread count does not effectively use the CPU resources of the machine.

Sun JVM Heap Size Appendix A: Performance Tuning MEM_ARGS="-XX:+AggressiveHeap 52 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .

Appendix B: Running Multiple Instances on a Single Machine This appendix describes how to set up multiple instances of SAP E-Sourcing to run on a single machine. This appendix covers the following topics: Overview on page 54 Assumptions on page 54 SAP E-Sourcing Multi-Instance Configuration on page 54 Future Upgrades on page 57 Troubleshooting Multiple Instance Configuration on page 57 Application Server Vendor-Specific Instructions on page 57 Confidential 53 .

this multiple instance configuration may present a performance degradation or a performance optimization. SAP E-Sourcing Multi-Instance Configuration The following configuration steps must be taken to enable multiple instances of SAP E-Sourcing to run on the same physical machine. The steps required to configure the system properties in each instance of SAP E-Sourcing are described here.. Depending on the proprietary resource management of a customer’s chosen application server vendor.e.. so that multiple instances can run safely on one physical machine. 54 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . The decision to use this configuration should be based upon the application server vendor’s claims for performance.e. Please consult the literature from your application server vendor to configure multiple instances of the Java Virtual Machine (i. a customer may want to be able to run the current version of the software for training purposes while also running the next version of the software in a staging environment. as described in the literature provided by your application server vendor. the application server's resource management will greatly influence the success of this configuration. Independent of these steps. For example. one used per instance of SAP E-Sourcing). It is recommended that any machine that will be used to run multiple instances of SAP E-Sourcing have at least 4GB of RAM. Assumptions This appendix assumes that you have experience with deploying SAP E-Sourcing and that you understand the performance implications of running multiple instances of the Java Virtual Machine on one physical application server. create a separate SAP home directory ( <FCI_HOME> ) for each instance of SAP E-Sourcing that you intend to run on that server. a customer may want to leverage some untapped capacity on application server boxes. In another example. it may be desirable to run more than one instance of SAP E-Sourcing on a single machine. This appendix describes the steps required to configure SAP E-Sourcing to operate successfully within a multiple instance configuration. the application server itself must be configured to launch multiple instances of SAP E-Sourcing (i. 1 SAP Home Directories: On each physical application server. In either case.Overview Appendix B: Running Multiple Instances on a Single Machine Overview In some customer environments. via the console window in your application server management software).

daemons.listen. there will exist a unique fcilocal.properties: system.service.listen. However. In this example. add the following to C:\fci_instanceB\home\config\fcilocal.properties file located under <FCI_HOME>\config. each of these files must be edited to add a unique value for the following properties: PROPERTY system. the following files would exist: ■ ■ ■ C:\fci_instanceA\home\config\fcilocal.listen.port=5030 Please note that when only one instance of SAP E-Sourcing is running.name=FCI-Instance-A system.service.name= VALUE <user-defined unique name> system.properties By default.name=FCI-Instance-B system. To prevent multiple instances from choosing the same port.service.daemons.events.Appendix B: Running Multiple Instances on a Single Machine SAP E-Sourcing Multi-Instance Configuration For example. it is recommended that you enter a unique port number in each of the files as described above. one machine would have the following home directories if intending to run three concurrent instances of SAP E-Sourcing: ■ ■ ■ C:\fci_instanceA\home C:\fci_instanceB\home C:\fci_instanceC\home 2 3 SAP Installation: Perform a complete product install to each of the directories created in step (1) above. these files will be empty. add the following to C:\fci_instanceA\home\config\fcilocal. add the following to C:\fci_instanceC\home\config\fcilocal.properties C:\fci_instanceB\home\config\fcilocal.properties: system.events.port=5029 In the example.port=5028 In the example. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 55 .daemons.port= <user-selected available port> In the example.daemons. SAP System Properties: For each installation instance of SAP E-Sourcing.events. Note also that the service name is just a description and need not match any particular directory name.events.properties: system. it would choose a default port number for the events daemon.service.listen.properties C:\fci_instanceC\home\config\fcilocal.name=FCI-Instance-C system.

From SetUp >> System Setup >> Configuration Dropdown >> Cluster Information List. Make sure to enter the correct host names. Reboot the Application Server: The Application Server must be restarted to respond to any changes in the startup script and to respond to the new information in each fcilocal. the services will be listed automatically. Add the new member services to the cluster by the name that was entered as the service name in the fcilocal.Future Upgrades Appendix B: Running Multiple Instances on a Single Machine 4 Application Server Startup script: If the Application Server startup script contains the java option -DFCI. you must upgrade each of your multiple installation directories with the new release and repeat all subsequent steps described in this document.HOMEDIR=/<path_to_FCI_HOME>. the following new cluster members would be added: FCI-Instance-A FCI-Instance-B FCI-Instance-C This list is used to determine the actual host to which the user request will be redirected. Cluster Configuration: After restarting the Application Server. During load balancing. this step can be skipped. 56 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . edit your cluster information as follows: a b 5 6 Select the cluster containing the physical machines that have just been reconfigured to run multiple instances of SAP E-Sourcing. it must be modified to point to the appropriate <FCI_HOME> for each instance of SAP E-Sourcing.properties file. Note that if the cluster is set to Automatically Add New Services to this Cluster. Future Upgrades Note that the release upgrade steps provided with each new SAP E-Sourcing release will not remind you to carry forward this multiple instance configuration. modify the Cluster Configuration through the SAP E-Sourcing UI.properties file. To maintain this configuration with future releases. users will be distributed across all available members in the list. In the example. If the startup script does not use this parameter.

7 with Jetty 4.22 is supported with the Sun 1. verify that all of the above steps have been followed after each upgrade to a new released version of SAP E-Sourcing.22 http://www.jboss.4.org JBoss 3.jetty. Installing the Software 1 2 Install the Sun 1.4.2.Appendix B: Running Multiple Instances on a Single Machine Troubleshooting Multiple Instance Configuration Troubleshooting Multiple Instance Configuration If you receive errors indicating that services cannot be found or ports cannot be reserved.7/Jetty 4.2.2.2. JBoss 3.2 JDK.2 JVM.22 on the machine. These steps assume that you have installed SAP E-Sourcing and have built a database using the Sun 1.2.2.4. One will not need to be touched. These instructions should be reviewed in conjunction with the literature available to you from JBoss. Install x number of separate instances of JBoss3. Application Server Vendor-Specific Instructions The following section is intended as a reference for those customers who have configured multiple instances of SAP E-Sourcing to run on a JBoss/Jetty application server.7-Jetty4. All other instances will need a number of port changes. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 57 .2 JDK on the machine.org http://www.

name=MACHINE-CUSTOMER-TRAINING On the staging instance. Instance 1 Installed to Classloading Port JNDI Jetty Port RMI Port RMI Object Port Server Bind Port AJP13 Listener FCI Daemon Port FCI Installed To C:\jboss\jbossa 8083 1099 8090 1098 4444 4445 8009 5026 C:\fcia Instance 2 C:\jboss\jbossb 8084 1100 8091 1097 5555 5556 8010 5027 C:\fcib Instance 3 C:\jboss\jbossc 8085 1101 8092 1096 6666 6667 8011 5028 C:\fcic Instance 4 C:\jboss\jbossd 8086 1102 8093 1095 7777 7778 8012 5029 C:\fcid Applying a Service Name for All FCI Instances Add an entry in FCI_HOME/config/local.name=MACHINE-CUSTOMER-STAGING Changing FCI System Properties 1 Start E-Sourcing on any servers whose ports you changed.properties: system.Application Server Vendor-Specific Instructions Appendix B: Running Multiple Instances on a Single Machine Changing Ports on One Server The following table provides a guide to the necessary port changes. 58 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .properties to identify a unique service name for each service. The ports in the chart below are determined by simply adding 1to the JBoss standard ports.properties: system. add the following line to local. In some cases. you might make the following changes: On the training instance. if one instance is for training and one is for staging. add the following line to local. you may need to use port numbers other than those documented here.service. For example.service.

Modify the following two system properties: a b Set the port in the jndi.daemons. Make sure there are no startup errors in the fci log that was created and in the jboss server logs that can be found in their respective jboss homes under jboss/server/default/log. Set your cluster up to point to a unique external hostname (if appropriate).listen.Appendix B: Running Multiple Instances on a Single Machine Application Server Vendor-Specific Instructions 2 3 Log in as the “system” user. 5 Restarting the Servers 1 2 3 Stop any instances of JBoss that are running. there is no need to set this.provider. 4 If the public port on which an external webserver will listen is not port 80. Start up all instances. If your webservers will listen on port 80.port to be the appropriate Daemon Port for the instance.naming.url property to be the new JNDI port you set.events.java. set the system. Set the system.default_port property to the correct port number. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 59 .

Application Server Vendor-Specific Instructions Appendix B: Running Multiple Instances on a Single Machine 60 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .

Appendix C: Security Information This appendix outlines security information for SAP E-Sourcing. This appendix covers the following topics: Data Storage Security on page 62 Network and Communication Security on page 63 Traces and Logs on page 63 Confidential 61 .

all E-Sourcing data is stored in a database behind a firewall. 62 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .Data Storage Security Appendix C: Security Information Data Storage Security For a hosted environment. The following diagram depicts the E-Sourcing network topology.

HOMEDIR> is the directory in which WebLogic is installed. There is a set of log files by date.Appendix C: Security Information Network and Communication Security Network and Communication Security The application is protected from the internet by a firewall.SERV ER>\*. Log file permissions can be restricted at the filesystem level to be accessible only by the application server.SERVER> is the name of the server to which E-Sourcing has been deployed. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 63 .NAME> is the name of the E-Sourcing server's domain that was assigned when WebLogic was configured. and <DEPLOYED.HOMEDIR>\user_projects\domains\<ESOURCING. which is located at FCI.log Where <WEBLOGIC.log Where <NETWEAVER_INSTALLATION_DIR< is the directory in which NetWeaver is installed and <SAPSID> is the SAP system ID (use all caps). (FCI.PROFILE>\logs\<DEPLOYED. All end-user connectivity within the application in the E-Sourcing hosting facility is accomplished using 128-bit SSL Traces and Logs E-Sourcing traces are stored in the application log file.NAME>\myserver\ myserver. The application server also has additional sets of logs that can provide tracing information. and <DEPLOYED.log Where <WEBSPHERE.HOMEDIR>\server\<DEPLOYED.HOMEDIR\logs by default.HOMEDIR>\profiles\<ESOURCING. WebSphere <WEBSPHERE. JBoss <JBOSS. and <ESOURCING. <ESOURCING. The application will only serve up a log file to users who have been granted permission in the application.SERVER> is the name of the server to which E-Sourcing has been deployed.HOMEDIR is determined at installation time).HOMEDIR> is the directory in which JBoss is installed. The default location for each application server is as follows: WebLogic <WEBLOGIC.HOMEDIR> is the directory in which WebSphere is installed.SERVER>\log\*. NetWeaver <NETWEAVER_INSTALLATION_DIR>/<SAPSID>/JC00/j2ee/cluster/server0/log/applicati ons.0.log Where <JBOSS.PROFILE> is the profile name used when setting up WebSphere with E-Sourcing.

but not immediately. This is typically followed by a trace in the log. 64 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . CRITICAL: An error occurred which may have left the application in an unusable state. DEBUG: Debug messages. WARNING: Application encountered a problem but was able to recover. Log levels are as follows: INFO: An normal informational event. ERROR: An error occurred in the application. Action may be required.HOMEDIR\logs.Traces and Logs Appendix C: Security Information Logs are stored in FCI. Enables traceability of the application. ALERT: An error occurred that requires immediate action.

Appendix D: Operation and Maintenance This appendix outlines operation and maintenance information for SAP E-Sourcing. This appendix covers the following topics: Backup Recommendations on page 66 Restore Process on page 67 Starting and Stopping on page 67 Confidential 65 .

Nightly database backups are performed. Weekly database backups are sent off-site and stored for one month. The backup and restore strategy for your system landscape should not only consider SAP systems but should also be embedded in overall business requirements and incorporate your company's entire process flow. In addition to these backups. the backup and restore strategy must cover disaster recovery processes. see the documentation for your application server. The following is a sample backup strategy for E-Sourcing: Databases are real-time mirrored for high availability. 66 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . Monthly database backups are sent off-site and stored for one year.sap. with the exception of the configuration files located in FCI_HOME/config that detail how to access the database. Application configuration files are backed up and stored nightly. It is most important in this context that you ensure that backup devices are not lost together with normal data storage (separation of storage locations). all data is contained in the database. Use your organization’s standard backup procedures as defined by your corporate backup policies.com: SAP NetWeaver-->SAP NetWeaver 7. Application log files are backed up nightly and are stored for at least 90 days. Therefore. ensure that you have access to the installation media in the event that you need to recover.properties files. to back up E-Sourcing. In addition. For information about backup and restore for NetWeaver Application Server for Java. do the following: Back up the E-Sourcing database. In the E-Sourcing application. see the SAP Help Portal at help. Back up the FCI_HOME/config/*. For information about backup and restore for other application servers.Backup Recommendations Appendix D: Operation and Maintenance Backup Recommendations You need to regularly back up your system landscape to ensure that you can restore and recover it in the case of failure. such as the loss of a data center through fire.0 (2004s)-->select language-->SAP Library-->SAP NetWeaver Library--> Administrator's Guide-->Technical Operations Manual for SAP NetWeaver--> Administration of SAP NetWeaver Systems-->AS Java (Application Server for Java)--> Management--> Tasks-->Backing up and Restoring AS Java.

) Please refer to the documentation provided by your application server vendor for details on the recommended procedures used to start and stop your application server. No special measures must be taken to perform an online backup of E-Sourcing. based upon the organization’s internal processes and requirements in terms of system uptime.properties files from backup and place them in the FCI_HOME/config directory. (For a complete list of supported configurations. If the database connection information has changed. Restore the fcisystem. Reinstall the E-Sourcing application on an application server that is configured to run E-Sourcing. Start up and access the E-Sourcing application.properties and fcilocal. see the online Reference Guide: click the RG link in the E-Sourcing application and click Supported Configurations on the Index page. Refer to the appropriate sections of this guide for installation and configuration details.Appendix D: Operation and Maintenance Restore Process Component Copy Component copy functionality is not natively present in the E-Sourcing application. 3 4 5 Starting and Stopping SAP E-Sourcing is supported on multiple application servers and operating systems. use the FCI_HOME/bin/configure utility to establish connectivity to the new database. Promoting objects from system to system is typically handled through our Object Migration capabilities. and using the standard procedures for your database. Please refer to your database documentation and corporate backup policies for details about both types of backup. Restore Process A database administrator should perform the following procedures to restore the E-Sourcing system in the event that this is necessary: 1 2 Restore the database backup using the standard processes defined by your database vendor. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 67 . See the Object Migration appendix of this guide for further details. Online and Offline Backup Backups can be taken either online or offline at a customer’s discretion.

it will launch automatically when the application service is launched. You do not need to manually stop the individual E-Sourcing components. If you have installed and deployed the E-Sourcing Contract Generation service. For more information on Contract Generation. you should first inactivate it by remove it from the cluster to prevent additional users from being redirected to it. see Chapter 1: Installing the E-Sourcing Platform and Chapter 4: Deploying SAP E-Sourcing. see Chapter 2: Installing the E-Sourcing Optimizer. For more information on IIS. it will launch automatically when the application server is launched.sap. see the SAP Help Portal at help. For details about start/stop in another application server. that cluster member can be stopped without interrupting any end-user sessions. For details on installation and deployment. do the following: 1 Start the J2EE engine. 3 4 To stop E-Sourcing. see the documentation for your application server. Note that if an application instance has more than one cluster member.com: SAP NetWeaver-->SAP NetWeaver 7. If you have installed and deployed the Optimizer service. When all users are logged off. and you want to shut down one of the members. ■ 2 If you have installed and deployed the E-Sourcing Java application. 68 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . see Chapter 3: Installing Contract Generation. see the Microsoft IIS documentation. you are using the native load-balancing capabilities that ship with E-Sourcing. ■ For details about start/stop in NetWeaver. Load Balancing For details about load balancing in E-Sourcing. see the E-Sourcing Online Help: Setup --> System Setup --> Configuration --> Cluster Configuration.Load Balancing Appendix D: Operation and Maintenance To start E-Sourcing.0 (2004s)-->select language-->SAP Library-->SAP NetWeaver Library--> Administrator's Guide-->Technical Operations Manual for SAP NetWeaver--> General Administration Tasks--> Starting and Stopping SAP NetWeaver ABAP and Java. For details on the Optimizer. start the Microsoft IIS service and it will launch automatically. simply shut down the application server.

This appendix covers the following topics: Overview on page 70 Mechanics of Object Migration on page 71 Best Practice Use of Object Migration on page 75 Troubleshooting Object Migration on page 77 Confidential 69 .Appendix E: Object Migration This appendix outlines object migration for SAP E-Sourcing.

The object migration technology in E-Sourcing is a capability that allows businesses to easily move master data from one instance of E-Sourcing to another instance by exporting specified data from one installation and importing that data into a second installation. It is assumed that the reader of this document is familiar with E-Sourcing and how it is typically deployed by customers. 70 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .Overview Appendix E: Object Migration Overview This document provides the reader with a detailed description on the capability within SAP E-Sourcing known as Object Migration.

For example. However. Import Data is used to load data into E-Sourcing and Export Data is used to extract data from E-Sourcing. The object migration methodology is based on the concept that one or more business objects within E-Sourcing will be moved between systems. While the data associated with a vendor may span many database tables within the E-Sourcing schema. the user need only know that they want to export a Vendor business object. This option provides the user with extensive flexibility as custom queries can be developed and used with this option. or multiple datasets (NOTE: Selecting all datasets is typically used to perform a complete migration of sourcing objects from a staging to a production environment during system implementation.Appendix E: Object Migration Mechanics of Object Migration Mechanics of Object Migration Introduction The object migration capabilities are accessed from the Setup > System Administration > Import/Export Tools area within E-Sourcing. A single object migration package may contain multiple instructions. Object Migration Packages Object migrations are typically setup by creating a package. Instructions can specify one of the following: Single Sourcing Object: A Single Sourcing Object instruction allows the user to select a single object for export. The user can choose from a single dataset containing a defined set of object types. to understand the contents of a dataset. Dataset: A Dataset instruction allows building of a set of sourcing object types for export. Sourcing Object List: A Sourcing Object List instruction allows the user to export a list of objects based on the results of an E-Sourcing Picker Query. nor should existing datasets be modified. E-Sourcing represents an instance of a Vendor as a business object.) New datasets should not be added by the user. For example. each with its own type. Such a model necessitates that the user have a sound understanding of the business objects and their relationships within E-Sourcing. but does not require that database table structures be understood. the user would select Projects for the Object Type and then select the project template named above. all vendors could be exported by using the E-Sourcing query FCI-Vendors-OML (the FCI-Vendors-OML query is a picker query defined to return all vendors in the system). to export the E-Sourcing Project Template named Contract Renegotiation. E-Sourcing allows the user to select from a list of Object Types and then select a specific object instance. A package consists of one or more instructions that tell the object migration tool what to export. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 71 . users can interrogate the E-Sourcing Query Group associated with the dataset (see the query groups with omlgroup in their name). For example. All object instances of all object types configured as members of the dataset will be exported.

however. That is. If. users of the object export capability must be careful to consider inter-object dependencies when building export packages. However. More information is provided below on common object dependencies. the data is maintained on a separate page. a fairly simple object in E-Sourcing is the Vendor. The referenced objects must be migrated separately. only the vendor need be migrated. defined elsewhere in the system. a business object may be the parent of many subordinate objects (children) and may also refer to other business objects. A good rule of thumb is that if the data is maintained while editing the object. That is. As a rule. For objects that do not include an external id data member. Object Creation or Update When objects are moved from one system to another. the list of Internal Categories. as is the case with internal categories. This technique is utilized for higher-level objects such as document templates. only the object itself and its children will be exported. For example. 72 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . If. if the source system has an object instance with the same external id as the object being migrated. the object will be updated. if a new vendor is created and it refers to a new internal category. The vendor object consists of header level data such as the vendor name and address. Object Dependencies Most business objects within E-Sourcing follow typical relational constructs. Generally. The vendor object also has subordinates. a new vendor is created that refers to an existing internal category. External id matching is utilized for most master data type classes. the object is a reference. it is part of that object. Failure to include any referenced objects in the export package which do not already exist on the target system will result in the subsequent import failing. the object migration capabilities must determine whether to update an existing object or create a new object from scratch. If a match is not found. object matching is typically performed using the UNIQUE_DOC_NAME data member.Mechanics of Object Migration Appendix E: Object Migration Object migration packages may be executed multiple times by adding to the Exports list. the instructions within an object migration package can not be changed after the first export has been performed. when an object is exported. is a collection contained within the vendor object. Therefore. for example. For example. the object migration will attempt to match on it. then the system will attempt to create a new instance of the object. if an object being migrated contains an EXTERNAL_ID data member. however. An example reference to another business object is the actual Internal Category which is referenced by each element in the internal category collection. both the vendor and category must be migrated to the target system.

Custom Sourcing Object List Queries The best practices for use of object migration. which are detailed below. to export a set of named project templates. the internal query name is FCI-ProjectTemplates-OML. 'Template 2'. Using the standard E-Sourcing export query definitions as a template and creating new ones from them to constrain the list of objects to be exported is an excellent way to create custom export packages that are limited to a set of defined objects. which may not be getting changed as part of the creation. NOTE: Use of the export package instruction type.FCI_PRO_PROJECTS WHERE IS_TEMPLATE = 1 AND CONTEXTID=<%CONTEXT(projects. as is demonstrated above. This is merely one example of a way to customize the export processing. The Sourcing Object List instruction type used in conjunction with custom E-Sourcing picker queries is a good way to accomplish the creation of a custom export package. In the example.projects)%> <%ORDERBY%> 2 3 to: SELECT <%RESULTS%> FROM <%SCHEMA%>. a better approach is to construct a new query that only exports those objects.FCI_PRO_PROJECTS WHERE IS_TEMPLATE = 1 AND CONTEXTID=<%CONTEXT(projects. suggest that users create custom export packages with only those objects that must be migrated from one system to another. Duplicate the Query Definition and give it a new internal name such as CUSTOM-NamedProjectTemplates-OML Modify the Query String portion of the new Query Definition to explicitly query for the project templates to be exported. Such changes could result in creation of new objects when that was not the intent. and is a good approach when the number of objects to export is limited. could also have achieved the same thing as the aforementioned approach. the following approach could be taken: 1 Find the standard E-Sourcing Query Definition object that is used for object export (query definitions with an internal name that begins with FCI. change the query string from: SELECT <%RESULTS%> FROM <%SCHEMA%>. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 73 . and therefore. with a Sourcing Object List instruction that executes the query definition previously defined. Single Sourcing Object. when many objects of the same object type are going to be exported. could cause a unique key constraint error. However.and ends with -OML are the standard export queries).projects)%> AND DISPLAY_NAME IN ('Template 1'. 'Template 3') <%ORDERBY%> 4 Create a new export package. Failures can also occur if other members of the object represent the unique key.Appendix E: Object Migration Mechanics of Object Migration Alterations to the external id data member are not recommended as such changes could have undesirable effects on the object migration. For example. For example.

Use of multiple export packages and. The OMA file contains a number of XML files. a single import package enables E-Sourcing to properly handle dependencies between objects. can be unzipped. The E-Sourcing import data tool handles this for the user as long as all of the objects are contained in a single OMA file. One of them contains metadata about the objects exported. Importing data requires that objects be created in a proper order so that dependencies between objects are properly handled. 74 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . That is.oma extension (aka: an OMA file). Users need only access the Import Data tool and upload the OMA file. therefore. therefore.Mechanics of Object Migration Appendix E: Object Migration Object Migration Output The output generated from an object export is a file with a . The XML format is a proprietary SAP E-Sourcing format. the OMA file may be downloaded to a computer and imported into another instance of E-Sourcing. use of a single export package and. Import Data After data is exported. The file conforms to the ZIP file specification and. which is strongly discouraged. the others represent the actual contents of the individual object instances. therefore. multiple imports requires that the user ensure that objects are imported in the proper order. It is generally recommended that the import be run in the background and progress monitored by refreshing the page.

It is recommended that one user (the E-Sourcing system administrator) be charged with maintaining the list of changes that will be included in a release package. A brief description of the change (or a reference to a requirements document that describes the change) This information will be used by the system administrator to develop the final export package for the release. Tracking Changes In order for the partial object migration to be successful. Such a strategy requires that developmental changes occur in a STAGING system where the users can freely modify and test changes without impacting PRODUCTION users. in which only selected objects are migrated from one system to another. Customers that also deploy a TEST environment may utilize it to validate the object migration packages. before moving objects from STAGING to PRODUCTION. The system administrator should work with all E-Sourcing developers and keep a list with the following information: The object type being migrated (e. Environments Most E-Sourcing customers deploy two environments: STAGING and PRODUCTION.) The name of the object. and promote releases of application functionality. At the time of release (when the changes will be promoted to the PRODUCTION system for use). This approach provides an additional check in that it allows users to confirm that the contents of the export package are complete and that they will import into the PRODUCTION system without error (NOTE: this is based on the assumption that the STAGING and TEST environments were initially set up with a copy of the PRODUCTION database). develop. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 75 . development is performed in the STAGING system and objects are exported from it and loaded into PRODUCTION.. changes to the STAGING system must be tracked. etc. That is. These practices allow E-Sourcing users to plan. they can be exported from STAGING and loaded into the TEST environment. using traditional project management techniques.g. Under this configuration. an object migration should be performed which moves only those objects required for the release. Project Template.Appendix E: Object Migration Best Practice Use of Object Migration Best Practice Use of Object Migration Introduction The use of a “partial object migration” strategy is recommended. Query. Query Group.

particularly for lower level objects such as localized resources and query definitions is a valuable way to ensure that the proper objects are migrated. It is recommended that all localized resources added to the STAGING system for customization purposes utilize a bundle named custom.Best Practice Use of Object Migration Appendix E: Object Migration Naming Conventions The use of naming conventions. This technique simplifies the object migration strategy by allowing the entire custom bundle to be exported. 76 Confidential SAP® E-Sourcing Software Installation and Configuration Guide . Although it is recommended that individual queries and query groups be migrated using the sourcing object list technique. It is also recommended that custom queries and query groups have an internal name that begins with CUSTOM-. naming objects this way simplifies searches and query management. without a need to track each individual localized resource change.

For example. If errors are encountered during the export. Import Data Importing data errors most commonly occur because dependent objects do not exist in the system to which the data is being imported. if a new RFx Template is imported into a system that depends on a new RFx Question Library that is not imported.Appendix E: Object Migration Troubleshooting Object Migration Troubleshooting Object Migration Export Data In most cases. object migration exports should work without error. the E-Sourcing log files (accessed from the System Information area of the Setup page) should be consulted. Dependency errors such as the above can be corrected by re-creating the export package with all of the required objects and performing the import another time. Contact SAP Technical Support for assistance in reviewing the logs. SAP® E-Sourcing Software Installation and Configuration Guide Confidential 77 . then an error will be reported in the trace file for the import.

Troubleshooting Object Migration Appendix E: Object Migration 78 Confidential SAP® E-Sourcing Software Installation and Configuration Guide .