ESourcing InstallationGuide

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
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Audience for this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Topic Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 1: E-Sourcing Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2: Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 3: Contract Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 4: Deploying SAP E-Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 3 3 3 3 3
1 Installing the E-Sourcing Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-installation Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Universal Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 1: Install Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 2: Verify Security Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 3: Setup LDAP Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Oracle Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 1: Identify Oracle Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 2: Create Oracle Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 3: Create Oracle Service Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 4: Connect Oracle Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 5: Install Oracle Toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 6: Install Oracle JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 7: Verify Analytics Support Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DB2 Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 1: Identify Database Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 2: Create a Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 3: Create a Buffer Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 4: Create Tablespace(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 5: Create a Temporary Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 6: Create a Database Service Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 7: Create a Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Task 8: Install JDBC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 6 6 6 7 7 7 7 7 7 7 7 8 8 8 8 8 8 8 9 9 9 9
Confidential
Table of Contents
Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Installing the E-Sourcing Binary Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Configuring the Software for Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Updating the Java Home Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Installing the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Creating or Updating Database Login Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Updating the EAR File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Including Custom Jar Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Defining the Application Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Set Session Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Post-installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Task 1: Add SAP-Required Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Task 2: Define Java Memory and Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Task 3: Define JAXP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Task 4: Configure JMS Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Configuring JMS Queues and JNDI Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Defining System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Task 5: Update Session Timeout (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Task 6: Upgrade Database Schema from Previous Release. . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Task 7: Deploy the Application EAR File to the Application Server . . . . . . . . . . . . . . . . . . . 19 Task 8: Generate License File for E-Sourcing Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Task 9: Verify Production Readiness Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2 Installing the E-Sourcing Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Pre-installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Recommended Server Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Runtime Environment Variables and ClassPath. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Homogeneous JVM Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Configuring JMS Queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Creating New JMS Message Queues and JNDI Aliases . . . . . . . . . . . . . . . . . . . . . . . . . 24 Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Installing the Optimizer License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Deploying the Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Post-installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Identifying the Optimization Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
ii
Confidential
SAP E-Sourcing Software Installation and Configuration Guide
Table of Contents
3 Installing Contract Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Pre-installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Post-installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring SAP E-Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 28 29 31 31
4 Deploying SAP E-Sourcing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Access and Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contexts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Master Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSV File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Working with the Deployment Workbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building a Simple Custom Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gathering Critical Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customizing Data Input Workbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a Cluster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a Context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Company Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 34 35 35 36 40 40 41 43 44 44 45 45 46 46 47
Appendix A: Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WebLogic Native I/O Performance Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WebLogic Socket Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WebLogic Execution Threads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sun JVM Threading Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sun JVM Heap Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 50 50 51 51 51
Appendix B: Running Multiple Instances on a Single Machine . . . . . . . . . . . . . . . . . . . . . . . 53 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Confidential
iii
Table of Contents
SAP E-Sourcing Multi-Instance Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Future Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Troubleshooting Multiple Instance Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Application Server Vendor-Specific Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 JBoss 3.2.7/Jetty 4.2.22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Installing the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Changing Ports on One Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Applying a Service Name for All FCI Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Changing FCI System Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Restarting the Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Appendix C: Security Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Data Storage Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Network and Communication Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Traces and Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Appendix D: Operation and Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Backup Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Component Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Online and Offline Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Restore Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Appendix E: Object Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Mechanics of Object Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Object Migration Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Object Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Object Creation or Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Custom Sourcing Object List Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Object Migration Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Import Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Best Practice Use of Object Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
iv
Confidential
Table of Contents
Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tracking Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting Object Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Export Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Import Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
75 75 76 77 77 77
Confidential
Table of Contents
vi
Confidential
Welcome to Sap E-Sourcing Software
Preface
SAP E-Sourcing is an enterprise software solution that automates the entire sourcing process, including expenditure analysis, supplier selection, vendor management, and compliance. 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. The preface covers the following topics: Audience for this Guide on page 2 Topic Organization on page 3
Confidential
Audience for this Guide
Preface
Audience for this Guide

The audience for this guide is any person who is involved in the installation, deployment, and configuration of the E-Sourcing environment. Additional configuration information is provided in the Setup section of the Online Help.
Overview
Depending on the license and distribution media, 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. Items in bold are required.
System Configuration Components
Confidential
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. In addition to a J2EE-compliant application server, the E-Sourcing configuration requires an Oracle database, an LDAP directory, and an SMTP server. Optionally, the sourcing application can leverage an external HTTP web server and a Symantec AntiVirus Scan Engine server. This chapter describes how to install the SAP E-Sourcing platform.
Chapter 2: Optimizer
The SAP Optimizer is also a J2EE application that requires a J2EE-compliant application server that supports the EJB2.0 spec. The E-Sourcing application makes requests to the Optimizer service. The Optimizer has no direct end-user interface. The Optimizer is typically deployed on a separate physical application server from the E-Sourcing application. This prevents the computation-intensive processing of the Optimizer from impacting the performance of user interaction with the E-Sourcing application. This chapter describes how to install the Optimizer application.
Chapter 3: Contract Generation

Contract generation is a Microsoft .NET service. This service processes requests from the E-Sourcing application. The Service generates Contract documents in Microsoft Word format. This service requires the Microsoft .NET application framework and should be deployed on a server independent of any J2EE application component. However, it may be deployed with other .NET services. This chapter describes how to install the contract generation service.
Chapter 4: Deploying SAP E-Sourcing

After installing the SAP E-Sourcing components and services, a number of deployment tasks must be performed to get the system up and running. This chapter describes these tasks in detail.
Confidential
Topic Organization
Preface
Confidential
1
Installing the E-Sourcing Platform
This chapter describes how to install SAP E-Sourcing Platform on Windows 2000 and Solaris. It also describes the preliminary installations and configurations that are required before you install the E-Sourcing software. 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
Overview
1 Installing the E-Sourcing Platform
Overview
Before you can install the SAP E-Sourcing software, you must install software on the application server and the database server, and configure a number of database settings on the database server. To install SAP E-Sourcing, 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, you will also need to implement the SAP E-Sourcing application as defined in the Online Help under Setup. Although the configure utility creates a baseline database for a new installation, this baseline database lacks the business-specific data required for a fully functioning system. The Setup section of the Online Help describes how to define clusters for load balancing, support a multiple-enterprise context, and define master data and user accounts. You can define this data interactively or via a deployment workbook. The deployment workbook is an Excel spreadsheet that you use to define the data and then import it into the application. Instructions for its use are included in Chapter 6: Deploying SAP E-Sourcing. Performance note: As with other web-enabled applications, the performance of the E-Sourcing client is highly dependent upon the network infrastructure between the web browser client and the application server. E-Sourcing performance may suffer if sufficient bandwidth is not provided.
Pre-installation Procedure
The following items must be configured before installing the E-Sourcing software.
Universal Tasks
Task 1: Install Java Runtime Environment
Identify and install a supported J2EE application server with recommend Java Runtime Environment (JRE). See the Supported Configurations link in the online Reference Guide (RG) for more information.
Task 2: Verify Security Settings
Verify that the Java Runtime Environment is configured with Java Cryptography Extension (JCE), and Java Secure Socket Extension (JSSE). These are defined by the following properties in the java.security property file:
Confidential
security.provider.n Task 3: Setup LDAP Directory
Identify and install the supported LDAP Directory for end users of the application. The application can be configured to support multiple directories. For example, different directory configurations can be used for internal buyers and vendors, and external buyers and vendors.
Oracle Tasks
Task 1: Identify Oracle Server
Identify the Oracle server to create an application database schema. The database server must be configured for UTF-8 data encoding to support alternate/multiple languages.
Task 2: Create Oracle Schema
Create an Oracle 9i schema. The schema should be configured for a minimum of 5G. Actual database storage requirements can vary with use. Sizing worksheets are available to assist in more detailed sizing.
Task 3: Create Oracle Service Account
Identify and create an Oracle Service account. This may be the schema owner account. The service account must be assign the default roles of CONNECT and RESOURCE. The Service account must be granted CONNECT, RESOURCE, UNLIMITED TABLESPACE, CREATE DIMENSION, CREATE MATERIALIZED VIEW, and QUERY REWRITE.
Task 4: Connect Oracle Schema
Obtain the connection information for the Oracle schema from your database administrator. You will need the Server Hostname, SID, Oracle username, and Oracle password to configure the application.
Task 5: Install Oracle Toolkit
Verify and Install Oracle DBMS_OBFUSCATION_TOOLKIT. The toolkit supports DES encryption, which is required by the application to encrypt sensitive data stored in the database. This toolkit should be available on your Oracle distribution or can be downloaded from http://otn.oracle.com.
Task 6: Install Oracle JDBC Driver
Locate the Oracle 9i JDBC driver. This should be available on your Oracle distribution or can be downloaded from http://otn.oracle.com. Note that this is a new version of the JDBC driver.
Confidential
Note:
If you are upgrading from Sourcing 2.x, you must obtain this new JDBC driver.
Task 7: Verify Analytics Support Settings
Verify the Oracle server settings to support SAP E-Sourcing Analytics. The server settings are:
STAR_TRANSFORMATION_ENABLED = TRUE OPTIMIZER_MORE = CHOOSE QUERY_REQRITE_ENABLED = FALSE COMPATIBLE = 8.1.0 (or greater) QUERY_REWRITE_INTEGRITY = TRUSTED
DB2 Tasks
Task 1: Identify Database Server
Identify a database server running DB2 9.1 for Linux, Unix, and Windows.
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.
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.
Task 4: Create Tablespace(s)
SAP E-Sourcing supports up to three tablespaces to contain tables, indexes, and blobs, respectively. You must create at least one tablespace associated with the buffer pool created in Step 3. You may create two additional tablespaces if you wish to maintain your tables, indexes, and blobs in individual tablespaces. All tablespaces must be created in association with the database created in Step 2.
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.
Task 6: Create a Database Service Account
SAP E-Sourcing uses a database user account to connect to the database. Minimally, this account must be granted the following database privileges:
Confidential
Installation Procedure
CONNECT, CREATETAB, BINDADD Additionally, grant use of the tablespaces created in Step 4 to this database user account.
Task 7: Create a Schema
Create a schema associated with the database created in Step 2. The authorization (owner) of this schema must be the database user account created in Step 6.
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. The two files required are: db2jcc.jar and db2jcc_license_cu.jar. These two files are typically found in the IBM/sqllib/java directory on the system where db2 is installed. The JDBC driver can also be downloaded from the IBM website.
The two primary steps of the installation procedure are:
1 2
Installing the E-Sourcing and third-party binary files. Configuring the software for deployment.
Application and software data are commingled within the same database schema. Software configuration settings are found in the FCI.HOMEDIR/config directory of the local file system (fcisystem.properties and fcilocal.properties).
Note:
Installing the E-Sourcing Binary Files

The installation procedure for SAP E-Sourcing is called Setup. To install SAP E-Sourcing: Run the setup command. You will see the E-Sourcing Install wizard.
For Windows installation, run the following:

setup.exe
For Solaris installation, run the following:

setup.bin
For Linux installation, run the following:

setupLinux.bin
Note:
The installer performs a full search for the JVM. This may take a while in some cases; you can specify the location of the JVM by using the following:
Confidential
-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. Specify the directory location for the FCI software. This will be the FCI home directory.
Note: The path for the FCI home directory must be all lower case or the installation/upgrade will not be successful.
Select the appropriate database: Oracle or DB2.
If you select Oracle, you see a page asking you to provide the Oracle JAR file (normally oracle.jar). If you select DB2, you see a page asking you to provide the two DB2 JAR files (db2cc.jar and db2cc_license_cu.jar).
Specify a single or multibyte database character set.
Configuring the Software for Deployment

The configuration process is launched after successful installation of the E-Sourcing binary files. The configuration tool can also be executed after the installation to reconfigure the application. This is often done to rebuild the EAR file after the inclusion of custom jar files or the application of a software patch. To manually execute the configure utility: For Windows installation, run the following: <FCIHOMEDIR>\bin\configure.exe For Solaris installation, run the following: <FCIHOMEDIR>/bin/configure.bin For Linux installation, run the following: <FCIHOMEDIR>/bin/configureLinux.bin
Note: Again, the installer will perform a full search for the JVM. You can specify the location of the JVM by using the following: -is:javahome /yourpathname
The configure utility can perform the following functions.
10
Confidential
Updating the Java Home Directory
The configure tool will provide a default Java home directory. You can select a different Java directory to be used by FCI standalone tools. The Java home directory used by the application will be defined by the J2EE application server. It is recommended that you specify the JVM that will be used to run your application server here. This is because a keystore is installed into the database using JCE. 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. SAP does provide a mechanism for reinstalling the keystore should this situation occur.
Installing the Database
The database install option allow you to install a baseline database. If this is a new installation, you can install the baseline database. Installing the baseline will overwrite any existing data in the database.
Creating or Updating Database Login Information
The configuration utility stores database login information in the fcisystem.properties file. For Oracle: Enter the following database login information: Driver Class (required): oracle.jdbc.driver.OracleDriver URL to connect to the database and the username and password to connect to the database schema (required). Modify the URL to include the host name, port, and SID for your server. 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). This is the connection information you obtained during the pre-installation procedure. Schema (typically, the user name -- required for upgrade, recommended but not required for installation) Optionally, the names of custom database tablespace(s) used for storing tables (Table Space), indexes (Index Space), and blobs (Blob Space). If you leave these fields blank, the default Oracle settings are used.
Confidential
11
For DB2: Enter the following database login information: Driver Class (required): com.ibm.db2.jcc.DB2Driver URL to connect to the database and the username and password to connect to the database schema (required). Modify the URL to include the host name, port, and database for your server. 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). Schema (required) The names of database tablespaces used for storing tables (Table Space), indexes (Index Space), and blobs (Blob Space) (required)
Updating the EAR File
The SAPEAR files are built and stored in the <FCIHOMEDIR>/fsapp directory.
Including Custom Jar Files
If you select this option, the tool allows you to provide any custom jars into the fci custom directory. These files will automatically be included in the generated EAR file.
Defining the Application Context
Select this option if you would like to change the context root for SAP E-Sourcing. The default context is '/', meaning that the application will respond to servlet requests that come in as http://webserver/servlet. If you run in a non-default context, say /sourcing, the application will only respond to requests that come in as http://webserver/sourcing/servlet.
Set Session Timeout
The deployment descriptor for the SAP E-Sourcing application defaults to a 30-minute session timeout. Select this option to change this setting.
12
Confidential
Post-installation Procedure
In some cases, this setting may be overridden by a session timeout that is set at the application server level. For example, WebSphere has a session timeout property at the application server level. In this situation, do one of the following: Using the WebSphere admin console, use the application server property to control session timeout. Using the WebSphere admin console, disable the timeout at the application server level. Configure the SAP application timeout setting to override the application server setting via the Session Management page for SAP E-Sourcing.
Once the E-Sourcing application has been installed and configured, 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. Define Java virtual memory and configuration settings. Define JAXP settings. Configure JMS messaging. Optionally, update the default session timeout. Upgrade the database schema from previous release. Deploy the application EAR file to the application server. Generate license file. Verify production readiness criteria.
Task 1: Add SAP-Required Libraries

Note: The following applies to non-JBoss deployments only.
The libraries required by the SAP E-Sourcing application are packaged in the EAR file that is deployed by the application server. However, the mechanism used by the application server to load
Confidential
13
XML parsers requires some of the libraries to be available to the application server. The following libraries must be added to the application servers classpath: <FCIHOMEDIR>/lib/activation.jar <FCIHOMEDIR>/lib/avalon-framework.jar <FCIHOMEDIR>/lib/batik-all.jar <FCIHOMEDIR>/lib/endorsed/serializer.jar <FCIHOMEDIR>/lib/endorsed/xalan.jar <FCIHOMEDIR>/lib/endorsed/xercesImpl.jar <FCIHOMEDIR>/lib/endorsed/xml-apis.jar <FCIHOMEDIR>/lib/fcifopext.jar <FCIHOMEDIR>/lib/fop.jar <FCIHOMEDIR>/lib/jakarta-oro-2.04.jar (WebSphere only, if using the upp.extservletauthenticator.username_regex property to implement a single sign-on solution) <FCIHOMEDIR>/lib/jcschart.jar <FCIHOMEDIR>/lib/mail.jar <FCIHOMEDIR>/lib/soap.jar <FCIHOMEDIR>/lib/ssce.jar (WebLogic only) For example, if you define <FCIHOMEDIR> to be c:/fci, you might define an FCI_CLASSPATH variable with the following values:
SET FCI_CLASSPATH= c:/fci/lib/xercesImpl.jar;c:/fci/lib/fop.jar;c:/fci/lib/fcifopext.jar;c:/ fci/lib/avalon-framework.jar;c:/fci/lib/batik-all.jar;c:/fci/lib/saxon.ja r;c:/fci/lib/soap.jar;c:/fci/lib/mail.jar;c:/fci/lib/activation.jar;c:/fc i/lib/jcschart.jar;c:/fci/lib/cocoon-fci.jar;c:/fci/lib/ssce.jar
Note that the FCI_CLASSPATH environment variable must still be added to the servers classpath environment variable.
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. Add the following Java configuration setting:
-Djava.endorsed.dirs=<FCIHOMEDIR>/lib/endorsed
14
Confidential
Task 3: Define JAXP Settings

Note: The following applies to non-JBoss deployments only.
The Java API for XML Processing (JAXP) provides a mechanism for defining the XML and XSL processors used by the E-Sourcing application. SAP E-Sourcing ships with the required XML and XSL processors. The following JAXP properties must be defined to allow SAP E-Sourcing to use the required processors: javax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryIm pl javax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl javax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl ---- this one changed The JAXP settings can be defined in a JAXP specific property file, using the Java D<name>=<value> option, or using an application-server-specific mechanism for defining JAXP settings.
Task 4: Configure JMS Messaging

SAP E-Sourcing utilizes JMS messaging for communication between the E-Sourcing application server and the Optimizer. JMS Messaging is also used for communication between E-Sourcing applications. The JMS communication requires additional configuration of the J2EE application server. Prior to configuring the JMS queues, the JMS server must be configured and started on the application server. By default, the JMS server is generally not started. For the application server that will run the JMS Server, perform the following steps: Create the JMS Server. Establish persistent storage for the queues. This can be either file or database storage. 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:
Confidential
15
Note:
The setup of these queues depends on the application server. Most will auto-prefix queue names with queue/.
JMX (E-Sourcing Server Management)

Queue: fs.destination.queue.jmx_queue JNDI: fs.queue.JmxQueue
Integration API
Queue: fs.destination.queue.IapiEventQueue JNDI: fs.queue.IapiEventQueue
Optimization (see the Installing the SAP Optimizer chapter for more details)
Queue: fs.AllocationStatusQueue JNDI: fs.optimization.AllocationStatusQueue Queue: fs.AllocationRequestQueue JNDI: fs.optimization.AllocationRequestQueue Queue: fs.HaltAllocationQueue JNDI: fs.optimization.HaltAllocationQueue
Create the following JMS Connection Factories:

JNDI Name: fs.optimization.QueueConnectionFactory JNDI Name: fs.commomn.QueueConnectionFactory Defining System Properties
You must next define a number of SAP system properties. The values of these properties differ between application servers. The following are the default values for WebSphere, WebLogic, and JBoss: initial JNDI Context system.j2ee.jndi.java.naming.factory.initial = The Class Name of the initial context factory implementation

JBoss: org.jnp.interfaces.NamingContextFactory NetWeaver: com.sap.engine.services.jndi.InitialContextFactoryImpl WebLogic: weblogic.jndi.WLInitialContextFactory WebSphere: com.ibm.websphere.naming.WsnInitialContextFactory
JNDI Naming Factory
16
Confidential
system.j2ee.jndi.java.naming.factory.url.pkgs = Packages to search for application server impl classes

JBoss: org.jboss.naming:org.jnp.interfaces NetWeaver: com.sap.tm.jndi.providers WebLogic: weblogic.jndi.factories WebSphere: com.ibm.ws.naming
JNDI Provider system.j2ee.jndi.java.naming.provider.url = Indicates the transport layer that should be used. (These are the defaults. Change localhost to the application server that is running the J2EE Services.)

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. J2EE configuration parameters must match the NetWeaver configuration above to use this import script. If the above values were not used, the values will have to be set manually by logging into the system context and setting each property manually. Start DbImporter. File: fciinstall.jar/scripts/dev/import_netweaver_system_properties.xml. The following properties will be automatically installed. J2EE System Properties:
J2EE System Properties (NetWeaver)
Field jms.common.queueconnectionfactory jms.destination.queue.jmx_queue jms.destination.queue.iapi_event_queue jndi.java.naming.factory.initial jndi.java.naming.factory.url.pkgs jndi.java.naming.provider.url
Value jmsfactory/default/fs.common.QueueConnectionFactory jmx_queue jmsqueues/default/fs.queue.JmxQueue jmsqueues/default/fs.queue.IapiEventQueue com.sap.engine.services.jndi.InitialContextFactoryImpl com.sap.tm.jndi.providers localhost:50004
Confidential
17
Optimizer System Properties:
Field
Value
optimization.config.queue_connection_fact jmsfactory/default/fs.optimization.QueueConnectionFacto ory ry optimization.config.halt_destination optimization.config.request_destination optimization.config.status_destination jndi.java.naming.factory.initial jndi.java.naming.factory.url.pkgs jndi.java.naming.provider.url jmsqueues/default/fs.optimization.HaltAllocationQueue jmsqueues/default/fs.optimization.AllocationRequestQueu e jmsqueues/default/fs.optimization.AllocationStatusQueue com.sap.engine.services.jndi.InitialContextFactoryImpl com.sap.tm.jndi.providers localhost:50004
Task 5: Update Session Timeout (Optional)

The application server is responsible for the timeout of inactive user sessions. The default value is typically 20-30 minutes. If you wish the application to have a different timeout value, you can add a <session-config> node to the <web-app> node within the application deployment descriptor. The deployment descriptor for the SAP E-Sourcing application is located in the <FCIHOMEDIR>/deploy/web.xml file. 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.
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. Refer to the release notes to determine whether an upgrade of the database schema is required. The release notes will also provide details of how to apply the upgrade.
18
Confidential
Task 7: Deploy the Application EAR File to the Application Server

The Enterprise Application Archive (EAR) file is located in the <FCIHOMEDIR>/fsapp directory. The EAR can now be deployed to the application server. If the application server supports auto deployment you can simply copy the fcsourcing.ear file into the application servers deployment directory. You can also deploy the E-Sourcing application using the administrative console for the server. If the application was previously deployed, you may need to undeploy the application before redeploying the new EAR file. 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. Start the Visual Administrator by entering the following commands: cd /usr/sap/<SAPSID>/<JC00>/j2ee/admin ./go
2 3 4 5 6 7
Navigate to Server-->Services-->Deploy--> Runtime tab--> Applications button. Verify that the application is not already deployed (at sap.com/fcsourcing). If it is, click Remove. Click Deploy & Start. File: <BASE>/fsapp/fcsourcing.ear Click OK. Once it is started, verify that the application is running at the following location: http://<hostname>:50000/esourcing/fsbuyer/portal/login
To deploy on a different application server, consult your application server documentation.
Task 8: Generate License File for E-Sourcing Explorer

For the E-Sourcing Explorer to function, each application server must be licensed to run the Explorer applet. The IP addresses of all application servers that host SAP E-Sourcing should be collected. They will be used to generate a license file. The file must be installed on each server.
Confidential
19
Task 9: Verify Production Readiness Criteria

Once the application has been deployed, the production readiness can be verified from the System Information page in Setup. To verify the production readiness, perform the following steps: Log into the system as a user with system administrative permission. Click Setup at the top of the page. Under System Administration, select System Information from the System Management drop-down list and click OK. Click the Audit tab. The Audit page includes a set of criteria and indicates whether the criteria have been met.
20
Confidential
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
Overview
2 Installing the E-Sourcing Optimizer
Overview
The following examples are based on the JBoss server, but can be extrapolated to other application servers. Before deploying the Optimization module, set up the standard SAP E-Sourcing environment. Note: For more information on the JBoss software, see the JBoss Configuration Guide: http://www.jboss.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. Technically, the system will still function if the Optimizer is run on the same machine in a different Java VM, but this is strongly discouraged.
Recommended Server Topology

The following figure shows the recommended server topology.
Recommended Server Topology
Windows 2000 IBM Global Security Toolkit 5.0.3.52 IBM HTTP (Apache) Server 4.3.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.4.3 Jetty 3.1.3-1 Optimizer
J2EE Application Server
22
Confidential
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. The Optimizer requires the same command line arguments and classpath parameters as the E-Sourcing server.
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 Optimizer will not function if this is not the case.
Configuring JMS Queues

The Optimization module uses JMS to facilitate communication between the SAP E-Sourcing server and the Optimization server. This requires that several messaging queues must be configured before the Optimizer can be used successfully. Below is a list of the required queues and the JNDI aliases that should be created for each queue.
Note: The alias is the coded name that is used for locating each queue. Having both an actual queue and an alias is the best practice for working with JMS. However, the aliases are not strictly required if the queues themselves use the coded names. It is also very important that each queue be distinct. There should not be a single queue with multiple aliases. Furthermore, these queues should be used only for SAP E-Sourcing. JMS Queue and JNDI Alias Mappings Resource fs.AllocationStatusQueue fs.AllocationRequestQueue fs.HaltAllocationQueue App Server QueueConnectionFactory Type Queue Queue Queue Connection Factory JNDI Alias fs.optimization.AllocationStatusQueue fs.optimization.AllocationRequestQueue fs.optimization.HaltAllocationQueue fs.optimization.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. Below are the instructions for some common management interfaces.
Confidential
23
JBoss Management Console Assuming JBoss is running, you can reach the management console by browsing to http://localhost:8082/. Replace localhost with the hostname of the Optimization server. Browse to the JBossMQ section and click on the link service=Server Scroll down to the Description of createQueue section.
For each of the Optimizer queues, enter the queue name and click the CreateQueue button.
Note: At the time this document was written, the JBoss management console did not provide a mechanism for creating JNDI aliases. You must manually modify the JBoss Configuration file. See JBoss Configuration File: jboss.jcml, below.
JBoss Configuration File: jboss.jcml For general information on modifying this file, see the JBoss Configuration Guide: http://www.jboss.org/online-manual/HTML/ For SAP E-Sourcing, you must cut and paste two sections into this file. To modify the jboss.jcmi file:
1
Locate the Message Queue section by searching for QueueManager, and paste the following under the existing queue declarations:
 <mbean code="org.jboss.mq.server.QueueManager" name="JBossMQ:service=Queue,name=fs.AllocationStatusQueue"/> <mbean code="org.jboss.mq.server.QueueManager" name="JBossMQ:service=Queue,name=fs.AllocationRequestQueue"/> <mbean code="org.jboss.mq.server.QueueManager" name="JBossMQ:service=Queue,name=fs.HaltAllocationQueue"/> 
Locate the naming alias section (search for NamingAlias) and paste the following under the existing aliases:
 <mbean code="org.jboss.naming.NamingAlias" name="DefaultDomain:service=NamingAlias,fromName=fs.optimization.Queue ConnectionFactory" <attribute name="ToName">ConnectionFactory</attribute> <attribute name="FromName">fs.optimization.QueueConnectionFactory</attribute> </mbean> <mbean code="org.jboss.naming.NamingAlias" name="DefaultDomain:service=NamingAlias,fromName=fs.optimization.Alloc ationStatusQueue">
24
Confidential
Installation Procedures
<attribute name="ToName">queue/fs.AllocationStatusQueue</attribute> <attribute name="FromName">fs.optimization.AllocationStatusQueue</attribute> </mbean> <mbean code="org.jboss.naming.NamingAlias" name="DefaultDomain:service=NamingAlias,fromName=fs.optimization.Alloc ationRequestQueue"> <attribute name="ToName">queue/fs.AllocationRequestQueue</attribute> <attribute name="FromName">fs.optimization.AllocationRequestQueue</attribute> </mbean> <mbean code="org.jboss.naming.NamingAlias" name="DefaultDomain:service=NamingAlias,fromName=fs.optimization.HaltA llocationQueue"> <attribute name="ToName">queue/fs.HaltAllocationQueue</attribute> <attribute name="FromName">fs.optimization.HaltAllocationQueue</attribute> </mbean>  Note: If you directly edit the configuration files, you must restart JBoss. This is not necessary when working with the management console.
Installing the Optimizer License
Refer to the licensing information that shipped with the Optimization module.
Note: The Optimizer will not function without a valid license.
Deploying the Optimizer

To deploy the Optimizer for JBoss: After Message Queues and JNDI aliases are created, launch the Optimizer installer and direct it to your JBoss home directory. The Optimizer is deployed to ${JBOSS_HOME}/deploy.
Confidential
25
Post-installation Procedures
After the Optimizer is deployed, you must configure SAP E-Sourcing to indicate that it is available for use. Perform the following two post-installation tasks: Identify the Optimization server. Enable the optimization functions for each specific module, such as RFx and Auctions.
Identifying the Optimization Server

To identify the Optimization server:
1 2 3
Log on to SAP E-Sourcing using the SystemContext (/fssystem/portal/login). Browse to the System Properties page and search for JNDI. Select the table entry for JNDI and review the following settings:
optimization.naming.use_local_jndi If set to TRUE, SAP E-Sourcing uses the standard jndi.properties file in the classpath whenever accessing a JNDI resource. In general, this should always be set to FALSE.
optimization.jndi.java.naming.factory.initial This is the fully qualified class name of the JNDI InitialContext factory for your application server. For JBoss, this is org.jnp.interfaces.NamingContextFactory. This is equivalent to the standard J2EE property, jndi.java.naming.factory.initial.
optimization.jndi.java.naming.factory.url.pkgs This refers to the packages in which your application server stores remote interfaces for JNDI, JMS, and so forth. For JBoss, this would be org.jboss.naming:org.jnp.interfaces. This is equivalent to the standard J2EE property, jndi.java.naming.factory.url.pkgs.
optimization.jndi.java.naming.provider.url The JNDI provider URL for your application server. For JBoss, this should be hostname:1099, where hostname is the name of the machine that holds the JNDI lookup information for the Optimizer. Typically, this is the hostname of the Optimizer server unless you are running with a JMS clustering environment. This is equivalent to the standard J2EE property, jndi.java.naming.provider.url.
26
Confidential
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
3 Installing Contract Generation
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.
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
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.
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
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
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.
Confidential
29
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.
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>
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
Encrypting configuration section... Succeeded!

d 6
Open this Web.config file and copy the generated identity section to the WebService Web.config file before the AUTHENTICATION section.
The default POST limit for IIS is 4MB. The SOAP messages built during contract generation can easily exceed this limit. It is recommended that you change this default value to a value in the 50-100MB range. To change this value, do the following:
a b
Locate the maxRequestLength property in the web.config file and change the value as desired (the value is displayed in KB and is 4096 by default.) Optionally, refer to http://msdn2.microsoft.com/en-us/library/e1f13641.aspx for other httpRuntime schema node settings. Go to the IIS manager-><Locale computer name>->Web Sites-> Default Web Sites. Right-click WordService. Under ASP.NET, ensure that ASP.NET version is 2.0.xxx, not 1.1.xxx. Click OK to save the changes if needed.
Make sure .NET2.0 framework is selected for the installed WordService web site, as follows:
a b c d
The contract generation web service makes use of a Microsoft dll called Dsofile.dll. The dll is correctly included in the setup and will be written to the web application folder during installation, but it is not being registered with the OS. To register it properly, perform the following steps:
n
Type regsvr32 [filepath]\dsofile.dll in the Run dialog box on the Start menu. The [filepath] should be similar to: \inetpub\wwwroot\wordservice.
Verifying the installation

Verify the installation by typing the following URL into your browser: http://<host_name>:<port>/<virtual directory>/wordservice.asmx You see a Service Description page for the FCI Word Automation web service.
Configuring SAP E-Sourcing

Log into the E-Sourcing Application as the System Manager and set the following: On the System Property List page, edit the contractgen.serviceurl with the following: http://<host_name>:<port>/<virtual directory>/wordservice.asmx
Confidential
31
32
Confidential
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
Overview
4 Deploying SAP E-Sourcing
Overview
The following diagram outlines the basic deployment process.
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 - 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. Clusters serve to map users to a deployment instance when an environment contains multiple instances of E-Sourcing. Contexts serve to create a logical definition of how data should be shared or not shared in a complex business environment. In short, contexts manage access to information across a corporate deployment. Define Contexts and Clusters using the default system administrator login, portal and instructions defined in the following sections of this manual. Enterprise setup phase - The second task is to install the master data that will be shared by all sourcing companies within the enterprise. Most master data falls in this category. This data is generally installed using the built-in enterprise administration account (although ongoing maintenance should be handled by actual activated users). Company setup phase - The last phase of any deployment is to install master data specific to each company. This phase is distinguished from the second phase because it must be applied to each installed company with its own context.
Access and Login

SAP E-Sourcing provides the following default system administrator login IDs and passwords for access during implementation.
34
Confidential
Clusters
Note:
System Administrator rights are required to create initial Contexts and Clusters. Define Contexts and Clusters using the login and passwords defined below.
System Administrator Access Name System Administrator Enterprise Administrator Login ID system enterprise Usage Use for creating and managing contexts, clusters, and global system properties. Used to bootstrap the enterprise by installing everything from numbering tables to accounts. Once real accounts are installed, they should be used for any remaining configuration.
Note:
To ensure that your system remains secure, disable the use of the system accounts after creating custom accounts specific to your organization,.
Clusters
A cluster is a logical group of machines. A cluster defines how end users access the E-Sourcing application. For example, 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. The system requires that at least one cluster exist within an enterprise. Clusters define how one sourcing context is differentiated from another, and serve as the root of the entire deployment. Create your initial cluster by logging into the administration portal page as the system administrator and selecting Cluster Configuration from the Setup page. For more information about clusters, see the Setup section of the Online Help.
Contexts
Contexts define how master data and security are managed across a complex enterprise. Use Contexts to restrict a series of master data components from being shared across an enterprise. Contexts provide the ability to logically separate and duplicate master data components so that they can be managed differently across a conglomerate. This is most commonly used in a complex or global environment when international requirements or corporate divisions require that master data is managed separately. At least one sourcing context must be set up for an enterprise.
Confidential
35
Master Data
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. Hierarchical contexts can be used to keep one company's sourcing data separate from anothers, even within an enterprise. For simplicity, the examples in this chapter all employ single-context configurations. Create and configure contexts by logging in as the system administrator (system account) and clicking Enterprise Contexts on the Setup page. For more information about contexts, see the Setup section of the Online Help.
Master Data
Define the components of master data that exist within each context after contexts and clusters have been defined. The following table lists the master data object types requiring definition for the enterprise. A data classification of Configurable indicates that default data is provided but can be customized for deployment. A data classification of Custom indicates that no default data is provided and the deployment must provide the data.
Enterprise Master Data Contents Data Classification Description Defines the format of IDs. For example, an RFP might follow the format: RFP-nnnn, where nnnn increments for each new rfp created. Lists those enterprise-level objects which can be extended. One type of extension allows a reference to another type of object. This list identifies the allowed kinds of references. Default value list types. Default value list values, such as countries, time zones, etc. 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 list of extendible enterprise-level objects. Configurable
Default list of objects that can Configurable used referenced in an extension. Value List Types Value List Values Units of Measure Currencies Configurable Configurable Configurable Configurable
36
Confidential
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. 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. Used to define categories of scheduled tasks. Lists scheduled/background tasks. Used to define metrics for scorecards. Used to define terms on contracts Types define what set of contract features are available. Types define what set of Project features are available. Types define what set of RFx features are available. Types define what set of Auction features are available. Types define what set of Demand features are available. Identifies the security profiles installed with the system. Defines the rights for each security profile. Defines information about quarters, years, etc. Used for managing how data is reported with relation to the calendar. Defines the role (rights and responsibilities) of a person/group on a specific document instance. Sets up the default collaborators and security when new documents are created. A list of discussion forums available as a channel and not relating to a specific document. Channels available on a user's desktop. Data to create iFrames Channel configuration parameters.
Confidential
37
Master Data
Enterprise Master Data Contents Workbench Pages Data Classification Configurable Description Pre-defined desktop pages. Channel content and placement settings for predefined pages. Various deployment settings, including mail, etc. The actual extensions on enterprise-level objects. Used for the LDAP directory configuration TBD The locations of plants, companies and other organizational elements. TBD Typically this data set consists of industry standard category codes, such as UN-SPSC or SIC codes, if used by your organization This data set describes all internal purchasing categories used by the buyer. Vendor data is used in all components for various purchasing actions. The actual extensions on enterprise-level objects. 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. Used during vendor self-registration. Further definition of the organizational hierarchy. Use to define departments, business units, etc.
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
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 all vendors to distinguish the various contacts at each vendor Handles all user accounts for the system. Standard terms and conditions phrases to which a vendor must agree before accessing an event.
After configuring the enterprise master data, you must next configure the company master data. This data must be created once for each sub-context. This example only uses a single context, so this data must only be created once.
Company Master Data Contents UFNs System Answered Sources Data Classification System Configurable Description Metadata for RFx utility functions. Defines the available sources of system answered questions. List of company-scoped objects which have extensions. Sets up the default collaborators and security when new documents are created. Used to define Phases for Contract Generation library documents Used to define Tags for Contract Generation. List of extensions on individual object types. Used for general accounting purposes Used for accounting purposes to assign cost on a center by center basis.
Company Extension Definitions Configurable Document Security Templates Contract Generation Phases Contract Generation Tags Company extensions masterdata.Activity Cost Centers Cost Center Groups Entities Configurable Configurable Configurable Custom Custom Custom Custom Custom
Used for accounting purposes for purchasing by division
Confidential
39
Master Data
Company Master Data Contents GL Accounts Plants Materials Category Managers Data Classification Custom Custom Custom Custom Description Used for general accounting purposes Plants, facilities. Standard materials for use in line items. The users who are responsible for certain categories.
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. You must log in as a sourcing administrator (a real user) in order to configure company master data. For initial deployment of the system, it is recommended that the deployment workbook be used to ensure that all required data is imported into the system.
CSV File Format
Most organizations will choose to import a large number of the master data objects via standard CSV files. 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. Once the object is found in the Reference Guide, click CSV View. An empty CSV in the correct format can be downloaded from the application using the import facility. Select Import Data from Setup and attempt to upload any file with the .csv extension. The system will recognize that you are interested in CSV files and prompt for the type of object to be imported. Choose the item of interest, then click Next. At this point, a sample CSV called template.csv can be downloaded. The Enterprise QuickStart.xls file can be downloaded from the online Reference Guide (RG). This file includes every master data element in the correct format, along with example data. To access this file, click RG at the top of the screen and then click Enterprise Deployment Workbook.
40
Confidential
Master Data
Importing Master Data
Master data files (CSV or XLS) can be imported in two ways: Using the standard web user interface. Using a client application distributed with the system, which allows data to be imported outside of the web environment. The standard way to import master data files, using the web-based UI, is as follows:
1 2
Open a browser and select the login page: http://yourhost/fsbuyer/portal/login. Log into the enterprise. If application users have already been created, log in as a user with administrative rights. If users have not been added, use the enterprise administrator built-in account. On the Setup page, go to the Import Data page as follows:
a b c
Click Setup. Under System Administration, select Import Data from the Import and Export Tools drop-down list. Click OK.
4 5 6 7 8 9
Select Create to start the import wizard. 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. Use the Upload Import File picker to load the CSV or Deployment Workgroup file to import. For CSV files, select the object type and click Next. Indicate whether you want to wait for the import to finish or perform the import in the background and click Next. Click Finish to view the results.
Confidential
41
Master Data
To install master data via the client DB Install tool, do the following:
1 2
Locate the home directory, typically c:/fci or d:/fci, and go to the bin directory. Run the program dbinstall.bat or dbinstall.csh, whichever is appropriate for your operating system. The DB Importer tool will open. Click the Lookup icon for the File field and select the file to import.
3 4 5
Click the Lookup icon for the Context field. Choose the destination context (for example, Acme Enterprise) where the data should be inserted or updated. If system users have already been created, log in as a user with administrative rights. If users have not been added, use the enterprise administrator built-in account. Use the Username and Password text fields to set the login parameters.
42
Confidential
Master Data
The Import Settings now appear as follows:
6 7
Click Run. Click the Status tab to see the progress of the import. After a few minutes, the import will complete. The Script tab should show nothing but green check marks.
Close the DB Import tool.
Working with the Deployment Workbooks
To facilitate the import of data, E-Sourcing provides an alternative to CSV files for import. SAP E-Sourcing provides the ability to import Microsoft Excel files containing one or more master data imports. The system can handle these Excel files directly without first forcing the user to export the data to a raw CSV file. Two example deployment workbooks ship with the system: Enterprise Deployment Workbook Company Deployment Workbook
Confidential
43
Building a Simple Custom Enterprise
The deployment workbooks can be downloaded from the web user interface by anyone with system administrator access rights. The deployment workbooks are included in the online Reference Guide (RG).
When starting a new deployment project, preserve the original workbook templates by saving them with a new name. Import data using your modified templates only. This ensures continuity if additional deployments are required in the future. Keep the following in mind when using deployment workbooks: The Configuration Sheet controls the import process. Refer to the Help Sheet for input specifications of Configuration Sheet columns. The system can import the workbooks directly, but there are limitations to what Excel constructs are supported. The Help Sheet describes the rules that must be observed. The same importing process supports both CSV files and Excel workbooks.

This section illustrates the steps needed to deploy a custom enterprise that leverages much of the setup information in the deployment workbooks.
Note: This guide assumes that the default values are accepted for the remaining data types.
Gathering Critical Information

For each deployment, gather critical information, including (but not limited to): Buy-side organizational data: Locations, Companies, Business Units, Groups, and Users Sell-side organizational data: Vendors and Contacts Commodity Information: Internal and External Categories. The current implementation methodology recommends defining these attributes prior to going live to maximize efficiency. Data attributes may be modified or added throughout the live of the implementation using the Setup module.
44
Confidential
Customizing Data Input Workbooks

The easiest way to get started is to modify the default deployment workbooks. Customize default workbooks using the following procedures:
1 2 3 4 5 6
Download the Enterprise Deployment workbook. Open the file and find the sheet labeled locations. Edit this sheet as necessary. Only one location is required. Find the sheet labeled external_categories. Edit it as necessary. Provide at least one external category. Find the sheet labeled internal_categories. Edit it as necessary. Provide at least one internal category. Find the sheet labeled companies. Edit it as necessary. Apply the same process to org_units, groups, accounts, etc. Be aware that a hierarchy is being established. Configuring the hierarchy correctly requires that the child reference the parent correctly. For example, the PARENT column in the business_units page should include a valid EXTERNAL_ID from the companies sheet.
If you want to build all custom data in the UI, simply deactivate the import of the above data types in the deployment workbook. See the Help page for instructions on how to skip a specific worksheet.
Note:
Installing a Cluster
1
Log into the system as follows:

a b c
For Username, enter system. For Password, enter manager. (You may have to see your system administrator for an updated password.) Select Login.
Click Cluster Configurations on the Setup page and then click Create.
Note: Configuring a cluster can be a complicated task. See the Setup section of the Online Help for more information about setting up clusters. The steps below assume a basic knowledge about clusters and system administration.
Configure the cluster with the following parameters:

n
Cluster Identity: acme.cluster.id (for example; you can use any id, but it can't have spaces or special characters) Display Name: ACME Cluster (for example; you can use any name you wish)
Confidential
45
n n
Hostname: * Add your host to the cluster member list. In the Service Hostname box, enter the name of your host. Select a service and make sure the Is Active checkbox is selected.
4 5
Click Save Document. Click Setup to return to the Setup page.

The steps above will set the public hostname of the cluster to "*". This is a special token which matches any HTTP request to the server. Make sure that only one cluster is configured with the "*" token.
Note:
Installing a Context
1 2
Click Enterprise Contexts on the Setup page and then click Create. Create a new context with the following parameters:
n n
Display Name: ACME E-Sourcing Context (as an example; any name will do) External ID: acme.context.id (as an example; any id will do it can't have spaces or special characters) Sys Admin Password: Enter something you can remember. Default Cluster: ACME Cluster (the one created above)
n n
3 4
Click Save Document. The system creates a new Enterprise E-Sourcing context to hold your data. This may take several minutes. Log out.
Installing Master Data

1 2
Close your browser. Open a new browser and go to the login page: http://yourhost/fsbuyer/portal/login. Log into the new enterprise as follows:
a b c
For the Username, type enterprise. For the Password, type the value you entered when you created the context. Click Login. Click Setup. Under Import and Export Tools, select Import Data from the drop-down list. Click OK.
On the Setup page, go to the Import Data page as follows:

a b c
46
Confidential
4 5 6 7 8
Select Create to start a new import job. Use the Import wizard Upload Import File picker to load your enterprise workbook. Follow the prompts in the import wizard. Repeat the import wizard for each company workbook. Log out.
You are now ready to return to the login page and log in as one of the users you have added.
Installing the Company Logo

To upload the company logo, follow these steps:
1 2
Go to the login page: http://yourhost/fsbuyer/portal/login. Log into the new enterprise as follows:
a b c
For the Username, type enterprise. For the Password, type the value you entered when you created the context. Click Login. Click Setup. Under Organization and Accounting Information, select Companies from the drop-down list. Click OK.
Open the company list as follows:

a b c
4 5 6 7
Select the enterprise company from the list and click Edit Document. Attach your logo image to the company using the Logo Attachment field. Click Save Document. Go to the System Properties page as follows:
a b c
Click Setup. Under Configuration, select System Properties from the drop-down list. Click OK.
8 9 10
Look at the property list. If there is an entry for buylogoimage, select it and click Edit. Otherwise, click Create. Set the Property Set to userinterface. Set the Property Value to the following:
Confidential
47
/images/companylogo/<company.id>/<image.gif> Where this is true:

n n
<company.id> specifies the External ID from the company where the logo is attached <image.gif> specifies the name of the image which was attached to the company
An example would be: /images/companylogo/acme/acme_logo.gif

11 12
Click Save Document. Reload the property cache as follows:

a b c d
Click Setup. Under Administrative Reports, select System Information from the drop-down list. Click OK. Click the Cache tag and select Refresh for the properties cache.
13
Log out.
The new company logo is displayed.
48
Confidential
Appendix A: Performance Tuning
This appendix describes performance tuning for version 3.1.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
Overview
Overview
The following are the recommended performance configurations for SAP E-Sourcing 3.2 on the Solaris 8 Platform. These recommendations assume the use of the 1.4 compliant JVM that has been certified with WebLogic 8.1. Note that these configurations were tested in the SAP QA LAB on a Sun E450 with 2G of memory. 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. Since this is the default setting for the WebLogic server, it is likely to be enabled. The Native I/O performance pack is a platform-optimized socket multiplexor that has demonstrated major performance improvements over the native Java implementations. You can verify this setting in the WebLogic Admin Console under Server\Configuration\Tuning.
WebLogic Socket Readers

Within the SAP E-Sourcing application, a majority of the threads are set to handle server requests. This value should be changed to reflect the fact that most execution threads are used as socket readers. The socket reader parameter specifies the percentage of execution threads that can be used as socket readers. The default value for this setting is 33 percent. The recommended value is 80 percent. This allows 80 percent of the execution threads to be used as socket readers. You can change this value in the WebLogic Admin Console under Server\Configuration\Tuning.
50
Confidential
WebLogic Execution Threads
WebLogic Execution Threads

The SAP E-Sourcing application currently uses the default execution threads. Since the activity to process a user's request often results in database activity, the default thread count does not effectively use the CPU resources of the machine. The default thread count is 15 in development mode and 25 in production mode. The recommended value for this setting is 50. For a dual processor machine, 25 threads may be a more appropriate number. You should monitor CPU load and verify that the load is not exceeding the CPU capacity. You can change this value in the WebLogic Admin Console by right-clicking the server name and selecting View execute threads.
Sun JVM Threading Model

Two different threading models are available to the JVM under Solaris. 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. Solaris 8 provides the option to use the alternative thread model, which is the one-to-one model. The one-to-one model allows each Java thread to map to its own kernel thread. The alternate thread library provides better utilization of the multiple CPUs. To enable the alternative thread model, 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}" ]; 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. The AggressiveHeap option allows the JVM to inspect the machine resources and various Java memory parameters such as heap size. The goal of these settings is to optimize the JVM for long-running server applications that allocate a substantial amount of memory. You should remove any previous memory settings such as minimum and maximum heap size, as they can conflict with AggressiveHeap. Set the following parameter in the WebLogic startup script to enable AggressiveHeap:
Confidential
51
Sun JVM Heap Size
MEM_ARGS="-XX:+AggressiveHeap
52
Confidential
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
Overview
Overview
In some customer environments, it may be desirable to run more than one instance of SAP E-Sourcing on a single machine. For example, 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. In another example, a customer may want to leverage some untapped capacity on application server boxes. In either case, the application server's resource management will greatly influence the success of this configuration. Depending on the proprietary resource management of a customers chosen application server vendor, this multiple instance configuration may present a performance degradation or a performance optimization. This appendix describes the steps required to configure SAP E-Sourcing to operate successfully within a multiple instance configuration. The decision to use this configuration should be based upon the application server vendors claims for performance.
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, as described in the literature provided by your application server vendor. The steps required to configure the system properties in each instance of SAP E-Sourcing are described here, so that multiple instances can run safely on one physical machine. It is recommended that any machine that will be used to run multiple instances of SAP E-Sourcing have at least 4GB of RAM.
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. Independent of these steps, the application server itself must be configured to launch multiple instances of SAP E-Sourcing (i.e., via the console window in your application server management software). Please consult the literature from your application server vendor to configure multiple instances of the Java Virtual Machine (i.e., one used per instance of SAP E-Sourcing).
1
SAP Home Directories: On each 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.
54
Confidential
SAP E-Sourcing Multi-Instance Configuration
For example, 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. SAP System Properties: For each installation instance of SAP E-Sourcing, there will exist a unique fcilocal.properties file located under <FCI_HOME>\config. In this example, the following files would exist:

C:\fci_instanceA\home\config\fcilocal.properties C:\fci_instanceB\home\config\fcilocal.properties C:\fci_instanceC\home\config\fcilocal.properties
By default, these files will be empty. However, each of these files must be edited to add a unique value for the following properties: PROPERTY system.service.name= VALUE <user-defined unique name>
system.daemons.events.listen.port= <user-selected available port> In the example, add the following to C:\fci_instanceA\home\config\fcilocal.properties: system.service.name=FCI-Instance-A system.daemons.events.listen.port=5028 In the example, add the following to C:\fci_instanceB\home\config\fcilocal.properties: system.service.name=FCI-Instance-B system.daemons.events.listen.port=5029 In the example, add the following to C:\fci_instanceC\home\config\fcilocal.properties: system.service.name=FCI-Instance-C system.daemons.events.listen.port=5030 Please note that when only one instance of SAP E-Sourcing is running, it would choose a default port number for the events daemon. To prevent multiple instances from choosing the same port, it is recommended that you enter a unique port number in each of the files as described above. Note also that the service name is just a description and need not match any particular directory name.
Confidential
55
Future Upgrades
Application Server Startup script: If the Application Server startup script contains the java option -DFCI.HOMEDIR=/<path_to_FCI_HOME>, it must be modified to point to the appropriate <FCI_HOME> for each instance of SAP E-Sourcing. If the startup script does not use this parameter, this step can be skipped. 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.properties file. Cluster Configuration: After restarting the Application Server, modify the Cluster Configuration through the SAP E-Sourcing UI. From SetUp >> System Setup >> Configuration Dropdown >> Cluster Information List, edit your cluster information as follows:
a b
Select the cluster containing the physical machines that have just been reconfigured to run multiple instances of SAP E-Sourcing. Add the new member services to the cluster by the name that was entered as the service name in the fcilocal.properties file. In the example, 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. During load balancing, users will be distributed across all available members in the list. Note that if the cluster is set to Automatically Add New Services to this Cluster, the services will be listed automatically. Make sure to enter the correct host names.
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. To maintain this configuration with future releases, you must upgrade each of your multiple installation directories with the new release and repeat all subsequent steps described in this document.
56
Confidential
Troubleshooting Multiple Instance Configuration
Troubleshooting Multiple Instance Configuration

If you receive errors indicating that services cannot be found or ports cannot be reserved, verify that all of the above steps have been followed after each upgrade to a new released version of SAP E-Sourcing.
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. These instructions should be reviewed in conjunction with the literature available to you from JBoss.
JBoss 3.2.7/Jetty 4.2.22

http://www.jboss.org http://www.jetty.org JBoss 3.2.7 with Jetty 4.2.22 is supported with the Sun 1.4.2 JDK. These steps assume that you have installed SAP E-Sourcing and have built a database using the Sun 1.4.2 JVM.
Installing the Software

1 2
Install the Sun 1.4.2 JDK on the machine. Install x number of separate instances of JBoss3.2.7-Jetty4.2.22 on the machine. One will not need to be touched. All other instances will need a number of port changes.
Confidential
57
Changing Ports on One Server

The following table provides a guide to the necessary port changes. In some cases, you may need to use port numbers other than those documented here. The ports in the chart below are determined by simply adding 1to the JBoss standard ports.
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.properties to identify a unique service name for each service. For example, if one instance is for training and one is for staging, you might make the following changes: On the training instance, add the following line to local.properties: system.service.name=MACHINE-CUSTOMER-TRAINING On the staging instance, add the following line to local.properties: system.service.name=MACHINE-CUSTOMER-STAGING
Changing FCI System Properties

1
Start E-Sourcing on any servers whose ports you changed.
58
Confidential
2 3
Log in as the system user. Modify the following two system properties:
a b
Set the port in the jndi.java.naming.provider.url property to be the new JNDI port you set. Set the system.daemons.events.listen.port to be the appropriate Daemon Port for the instance.
If the public port on which an external webserver will listen is not port 80, set the system.default_port property to the correct port number. If your webservers will listen on port 80, there is no need to set this. Set your cluster up to point to a unique external hostname (if appropriate).
Restarting the Servers

1 2 3
Stop any instances of JBoss that are running. Start up all instances. 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.
Confidential
59
60
Confidential
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
Data Storage Security
Data Storage Security

For a hosted environment, all E-Sourcing data is stored in a database behind a firewall. The following diagram depicts the E-Sourcing network topology.
62
Confidential
Network and Communication Security
Network and Communication Security

The application is protected from the internet by a firewall. 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, which is located at FCI.HOMEDIR\logs by default. (FCI.HOMEDIR is determined at installation time). The application server also has additional sets of logs that can provide tracing information. The default location for each application server is as follows: WebLogic <WEBLOGIC.HOMEDIR>\user_projects\domains\<ESOURCING.NAME>\myserver\ myserver.log Where <WEBLOGIC.HOMEDIR> is the directory in which WebLogic is installed, and <ESOURCING.NAME> is the name of the E-Sourcing server's domain that was assigned when WebLogic was configured. JBoss <JBOSS.HOMEDIR>\server\<DEPLOYED.SERVER>\log\*.log Where <JBOSS.HOMEDIR> is the directory in which JBoss is installed, and <DEPLOYED.SERVER> is the name of the server to which E-Sourcing has been deployed. There is a set of log files by date. WebSphere <WEBSPHERE.HOMEDIR>\profiles\<ESOURCING.PROFILE>\logs\<DEPLOYED.SERV ER>\*.log Where <WEBSPHERE.HOMEDIR> is the directory in which WebSphere is installed, <ESOURCING.PROFILE> is the profile name used when setting up WebSphere with E-Sourcing, and <DEPLOYED.SERVER> is the name of the server to which E-Sourcing has been deployed. NetWeaver <NETWEAVER_INSTALLATION_DIR>/<SAPSID>/JC00/j2ee/cluster/server0/log/applicati ons.0.log Where <NETWEAVER_INSTALLATION_DIR< is the directory in which NetWeaver is installed and <SAPSID> is the SAP system ID (use all caps). Log file permissions can be restricted at the filesystem level to be accessible only by the application server. The application will only serve up a log file to users who have been granted permission in the application.
Confidential
63
Traces and Logs
Logs are stored in FCI.HOMEDIR\logs. Log levels are as follows: INFO: An normal informational event. Enables traceability of the application. ERROR: An error occurred in the application. This is typically followed by a trace in the log. ALERT: An error occurred that requires immediate action. CRITICAL: An error occurred which may have left the application in an unusable state. WARNING: Application encountered a problem but was able to recover. Action may be required, but not immediately. DEBUG: Debug messages.
64
Confidential
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
Backup Recommendations
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. 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, the backup and restore strategy must cover disaster recovery processes, such as the loss of a data center through fire. 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). In the E-Sourcing application, all data is contained in the database, with the exception of the configuration files located in FCI_HOME/config that detail how to access the database. Therefore, to back up E-Sourcing, do the following: Back up the E-Sourcing database. Back up the FCI_HOME/config/*.properties files. Use your organizations standard backup procedures as defined by your corporate backup policies. For information about backup and restore for NetWeaver Application Server for Java, see the SAP Help Portal at help.sap.com: SAP NetWeaver-->SAP NetWeaver 7.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. For information about backup and restore for other application servers, see the documentation for your application server. In addition to these backups, ensure that you have access to the installation media in the event that you need to recover. The following is a sample backup strategy for E-Sourcing: Databases are real-time mirrored for high availability. Nightly database backups are performed. Weekly database backups are sent off-site and stored for one month. Monthly database backups are sent off-site and stored for one year. Application configuration files are backed up and stored nightly. Application log files are backed up nightly and are stored for at least 90 days.
66
Confidential
Restore Process
Component Copy
Component copy functionality is not natively present in the E-Sourcing application. Promoting objects from system to system is typically handled through our Object Migration capabilities. 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 customers discretion, based upon the organizations internal processes and requirements in terms of system uptime, and using the standard procedures for your database. No special measures must be taken to perform an online backup of E-Sourcing. 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. Reinstall the E-Sourcing application on an application server that is configured to run E-Sourcing. Refer to the appropriate sections of this guide for installation and configuration details. Restore the fcisystem.properties and fcilocal.properties files from backup and place them in the FCI_HOME/config directory. If the database connection information has changed, use the FCI_HOME/bin/configure utility to establish connectivity to the new database. Start up and access the E-Sourcing application.
3 4 5
Starting and Stopping

SAP E-Sourcing is supported on multiple application servers and operating systems. (For a complete list of supported configurations, see the online Reference Guide: click the RG link in the E-Sourcing application and click Supported Configurations on the Index page.) 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.
Confidential
67
Load Balancing
To start E-Sourcing, do the following:

1
Start the J2EE engine.
For details about start/stop in NetWeaver, see the SAP Help Portal at help.sap.com: SAP NetWeaver-->SAP NetWeaver 7.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 about start/stop in another application server, see the documentation for your application server.
If you have installed and deployed the E-Sourcing Java application, it will launch automatically when the application service is launched. For details on installation and deployment, see Chapter 1: Installing the E-Sourcing Platform and Chapter 4: Deploying SAP E-Sourcing. If you have installed and deployed the Optimizer service, it will launch automatically when the application server is launched. For details on the Optimizer, see Chapter 2: Installing the E-Sourcing Optimizer. If you have installed and deployed the E-Sourcing Contract Generation service, start the Microsoft IIS service and it will launch automatically. For more information on Contract Generation, see Chapter 3: Installing Contract Generation. For more information on IIS, see the Microsoft IIS documentation.
To stop E-Sourcing, simply shut down the application server. You do not need to manually stop the individual E-Sourcing components. Note that if an application instance has more than one cluster member, you are using the native load-balancing capabilities that ship with E-Sourcing, and you want to shut down one of the members, you should first inactivate it by remove it from the cluster to prevent additional users from being redirected to it. When all users are logged off, that cluster member can be stopped without interrupting any end-user sessions.
Load Balancing
For details about load balancing in E-Sourcing, see the E-Sourcing Online Help: Setup --> System Setup --> Configuration --> Cluster Configuration.
68
Confidential
Appendix E: Object Migration
This appendix outlines object migration for SAP E-Sourcing. 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
Overview
Overview
This document provides the reader with a detailed description on the capability within SAP E-Sourcing known as Object Migration. 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
Mechanics of Object Migration

Introduction
The object migration capabilities are accessed from the Setup > System Administration > Import/Export Tools area within E-Sourcing. 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. 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. For example, E-Sourcing represents an instance of a Vendor as a business object. 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.
Object Migration Packages

Object migrations are typically setup by creating a package. A package consists of one or more instructions that tell the object migration tool what to export. 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. E-Sourcing allows the user to select from a list of Object Types and then select a specific object instance. For example, to export the E-Sourcing Project Template named Contract Renegotiation, the user would select Projects for the Object Type and then select the project template named above. 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. For example, 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). This option provides the user with extensive flexibility as custom queries can be developed and used with this option. Dataset: A Dataset instruction allows building of a set of sourcing object types for export. All object instances of all object types configured as members of the dataset will be exported. The user can choose from a single dataset containing a defined set of object types, 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.) New datasets should not be added by the user, nor should existing datasets be modified. However, to understand the contents of a dataset, users can interrogate the E-Sourcing Query Group associated with the dataset (see the query groups with omlgroup in their name). A single object migration package may contain multiple instructions, each with its own type.
Confidential
71
Object migration packages may be executed multiple times by adding to the Exports list. However, the instructions within an object migration package can not be changed after the first export has been performed.
Object Dependencies
Most business objects within E-Sourcing follow typical relational constructs. That is, a business object may be the parent of many subordinate objects (children) and may also refer to other business objects, defined elsewhere in the system. For example, a fairly simple object in E-Sourcing is the Vendor. The vendor object consists of header level data such as the vendor name and address. The vendor object also has subordinates; the list of Internal Categories, for example, is a collection contained within the vendor object. An example reference to another business object is the actual Internal Category which is referenced by each element in the internal category collection. A good rule of thumb is that if the data is maintained while editing the object, it is part of that object. If, however, the data is maintained on a separate page, as is the case with internal categories, the object is a reference. As a rule, when an object is exported, only the object itself and its children will be exported. The referenced objects must be migrated separately. Therefore, users of the object export capability must be careful to consider inter-object dependencies when building export packages. For example, if a new vendor is created and it refers to a new internal category, both the vendor and category must be migrated to the target system. If, however, a new vendor is created that refers to an existing internal category, only the vendor need be migrated. 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. More information is provided below on common object dependencies.
Object Creation or Update

When objects are moved from one system to another, the object migration capabilities must determine whether to update an existing object or create a new object from scratch. Generally, if an object being migrated contains an EXTERNAL_ID data member, the object migration will attempt to match on it. That is, 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 match is not found, then the system will attempt to create a new instance of the object. External id matching is utilized for most master data type classes. For objects that do not include an external id data member, object matching is typically performed using the UNIQUE_DOC_NAME data member. This technique is utilized for higher-level objects such as document templates.
72
Confidential
Alterations to the external id data member are not recommended as such changes could have undesirable effects on the object migration. Such changes could result in creation of new objects when that was not the intent. Failures can also occur if other members of the object represent the unique key, which may not be getting changed as part of the creation, and therefore, could cause a unique key constraint error.
Custom Sourcing Object List Queries

The best practices for use of object migration, which are detailed below, suggest that users create custom export packages with only those objects that must be migrated from one system to another. 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. For example, to export a set of named project templates, 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- and ends with -OML are the standard export queries). In the example, the internal query name is FCI-ProjectTemplates-OML. 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. For example, change the query string from:
SELECT <%RESULTS%> FROM <%SCHEMA%>.FCI_PRO_PROJECTS WHERE IS_TEMPLATE = 1 AND CONTEXTID=<%CONTEXT(projects.projects)%> <%ORDERBY%>
2 3
to:
SELECT <%RESULTS%> FROM <%SCHEMA%>.FCI_PRO_PROJECTS WHERE IS_TEMPLATE = 1 AND CONTEXTID=<%CONTEXT(projects.projects)%> AND DISPLAY_NAME IN ('Template 1', 'Template 2', 'Template 3') <%ORDERBY%> 4
Create a new export package, with a Sourcing Object List instruction that executes the query definition previously defined.
This is merely one example of a way to customize the export processing. 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. NOTE: Use of the export package instruction type, Single Sourcing Object, could also have achieved the same thing as the aforementioned approach, and is a good approach when the number of objects to export is limited. However, when many objects of the same object type are going to be exported, a better approach is to construct a new query that only exports those objects, as is demonstrated above.
Confidential
73
Object Migration Output

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

Introduction
The use of a partial object migration strategy is recommended, in which only selected objects are migrated from one system to another. 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. At the time of release (when the changes will be promoted to the PRODUCTION system for use), an object migration should be performed which moves only those objects required for the release. These practices allow E-Sourcing users to plan, develop, and promote releases of application functionality, using traditional project management techniques.
Environments
Most E-Sourcing customers deploy two environments: STAGING and PRODUCTION. Under this configuration, development is performed in the STAGING system and objects are exported from it and loaded into PRODUCTION. Customers that also deploy a TEST environment may utilize it to validate the object migration packages. That is, before moving objects from STAGING to PRODUCTION, they can be exported from STAGING and loaded into the TEST environment. 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).
Tracking Changes
In order for the partial object migration to be successful, changes to the STAGING system must be tracked. 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. The system administrator should work with all E-Sourcing developers and keep a list with the following information: The object type being migrated (e.g., Query, Query Group, Project Template, etc.) The name of the object. 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.
Confidential
75
Naming Conventions
The use of naming conventions, 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. This technique simplifies the object migration strategy by allowing the entire custom bundle to be exported, without a need to track each individual localized resource change. It is also recommended that custom queries and query groups have an internal name that begins with CUSTOM-. Although it is recommended that individual queries and query groups be migrated using the sourcing object list technique, naming objects this way simplifies searches and query management.
76
Confidential
Troubleshooting Object Migration

Export Data
In most cases, object migration exports should work without error. If errors are encountered during the export, the E-Sourcing log files (accessed from the System Information area of the Setup page) should be consulted. Contact SAP Technical Support for assistance in reviewing the logs.
Import Data
Importing data errors most commonly occur because dependent objects do not exist in the system to which the data is being imported. For example, if a new RFx Template is imported into a system that depends on a new RFx Question Library that is not imported, then an error will be reported in the trace file for the import. 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.
Confidential
77
78
Confidential

ESourcing InstallationGuide

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

ESourcing InstallationGuide

Enviado por

Direitos autorais:

Formatos disponíveis

SAP E-Sourcing 2007

Installation and Configuration Guide

Confidential and Proprietary

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

SAP E-Sourcing Software Installation and Configuration Guide

SAP E-Sourcing Software Installation and Configuration Guide

SAP E-Sourcing Software Installation and Configuration Guide

SAP E-Sourcing Software Installation and Configuration Guide

SAP E-Sourcing Software Installation and Configuration Guide

Welcome to Sap E-Sourcing Software

Audience for this Guide

Audience for this Guide

SAP E-Sourcing Software Installation and Configuration Guide

Chapter 3: Contract Generation

Chapter 4: Deploying SAP E-Sourcing

SAP E-Sourcing Software Installation and Configuration Guide

SAP E-Sourcing Software Installation and Configuration Guide

1 Installing the E-Sourcing Platform

SAP E-Sourcing Software Installation and Configuration Guide

1 Installing the E-Sourcing Platform

security.provider.n Task 3: Setup LDAP Directory

SAP E-Sourcing Software Installation and Configuration Guide

1 Installing the E-Sourcing Platform

Task 7: Verify Analytics Support Settings

SAP E-Sourcing Software Installation and Configuration Guide

1 Installing the E-Sourcing Platform

Installing the E-Sourcing Binary Files

For Windows installation, run the following:

For Solaris installation, run the following:

For Linux installation, run the following:

SAP E-Sourcing Software Installation and Configuration Guide

1 Installing the E-Sourcing Platform

Select the appropriate database: Oracle or DB2.

Specify a single or multibyte database character set.

Configuring the Software for Deployment

The configure utility can perform the following functions.

SAP E-Sourcing Software Installation and Configuration Guide

1 Installing the E-Sourcing Platform

Updating the Java Home Directory

SAP E-Sourcing Software Installation and Configuration Guide

1 Installing the E-Sourcing Platform

SAP E-Sourcing Software Installation and Configuration Guide

1 Installing the E-Sourcing Platform

Task 1: Add SAP-Required Libraries

SAP E-Sourcing Software Installation and Configuration Guide

1 Installing the E-Sourcing Platform

Task 2: Define Java Memory and Configuration Settings

SAP E-Sourcing Software Installation and Configuration Guide

1 Installing the E-Sourcing Platform

Task 3: Define JAXP Settings

Task 4: Configure JMS Messaging

SAP E-Sourcing Software Installation and Configuration Guide

1 Installing the E-Sourcing Platform

JMX (E-Sourcing Server Management)

Create the following JMS Connection Factories:

JBoss: org.jnp.interfaces.NamingContextFactory NetWeaver: com.sap.engine.services.jndi.InitialContextFactoryImpl WebLogic: weblogic.jndi.WLInitialContextFactory WebSphere: com.ibm.websphere.naming.WsnInitialContextFactory

JNDI Naming Factory

SAP E-Sourcing Software Installation and Configuration Guide

1 Installing the E-Sourcing Platform

system.j2ee.jndi.java.naming.factory.url.pkgs = Packages to search for application server impl classes

JBoss: org.jboss.naming:org.jnp.interfaces NetWeaver: com.sap.tm.jndi.providers WebLogic: weblogic.jndi.factories WebSphere: com.ibm.ws.naming

J2EE System Properties (NetWeaver)