SAP NetWeaver Gateway Installation Guide

S AP N e t W e a v e r G a t e w a y 2 . 0 SP02

SAP NetWeaver Gateway

Copyright
Copyright 2011 SAP AG. All rights reserved. SAP Library document classification: PUBLIC 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. This documentation outlines our general product direction and should not be relied on in making a purchase decision. This documentation is not subject to your license agreement or any other agreement with SAP. SAP has not obligation to pursue any course of business outlined in this document or to develop or release any functionality mentioned in this documentation. This documentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This documentation is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this documentation, except if such damages were caused by SAP intentionally or grossly negligent. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. 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.

(C) SAP AG

SAP NetWeaver Gateway 2.0 SP02

SAP NetWeaver Gateway SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. 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.

(C) SAP AG

SAP NetWeaver Gateway 2.0 SP02

SAP NetWeaver Gateway

Icons in Body Text

Icon Meaning Caution Example Note Recommendation Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions
Type Style Example text Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation. Example text EXAMPLE TEXT Emphasized words or phrases in body text, graphic titles, and table titles. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.

Example text

Example text <Example text>

EXAMPLE TEXT

(C) SAP AG

SAP NetWeaver Gateway 2.0 SP02

SAP NetWeaver Gateway

Table of Contents
SAP NetWeaver Gateway Installation Guide................................................................................ 6 Installation Prerequisites .......................................................................................................... 6 Installing SAP NetWeaver Gateway Components..................................................................... 7 Support Package Migration ...................................................................................................... 8

(C) SAP AG

SAP NetWeaver Gateway 2.0 SP02

SAP NetWeaver Gateway

SAP NetWeaver Gateway Installation Guide

SAP NetWeaver Gateway is provided as an SAP NetWeaver Application Server ABAP (AS ABAP) add-on that you install on top of your existing SAP Business Suite or application platform. To ensure that SAP NetWeaver Gateway functions smoothly in an ABAP environment, a number of installation and configuration steps need to be performed. This chapter will look at all aspects concerning the installation of SAP NetWeaver Gateway: Installation Prerequisites [Page 6] Installing SAP NetWeaver Gateway Components [Page 7] If you want to migrate from one support package to another see Support Package Migration [Page 8].

More Information
For information on the system landscape and the different installation or deployment options offered by SAP NetWeaver Gateway, see Deployment Options [External]. For information on the software maintenance tools and processes see Software Maintenance [External].

Installation Prerequisites
Hardware The minimum hardware requirements for SAP NetWeaver Gateway are as follows: Requirements Processor Random Access Memory (RAM) Hard Disk Capacity Specification Dual Core (2 logical CPUs) or higher, 2 GHz or higher 8 GB or higher 80 GB primary, or higher

Software The minimum software requirements for SAP NetWeaver Gateway are as follows: Requirements SAP NetWeaver Stack Database/s (Server MS) Specification SAP NetWeaver 7.0 Enhancement Package 2 Support Package Stack 7 or higher (>=7.02 SPS07) Databases as supported according to the SAP NetWeaver 7.02 Product Availability Matrix (PAM). For more information, see http://service.sap.com/pam

(C) SAP AG

SAP NetWeaver Gateway 2.0 SP02

SAP NetWeaver Gateway

Requirements SAP Backend SAP Business Suite system

Specification

More Information
Keep in mind the security issues described in SAP NetWeaver Gateway Security Guide [External]. In addition, make sure that you read and implement the latest version of the SAP notes that apply to the software requirements listed above. You can find these notes at: http://service.sap.com/notes.

Installing SAP NetWeaver Gateway Components

Install the SAP NetWeaver Gateway components using the SAP Add-On Installation Tool (SAINT), which lets you import the SAP NetWeaver Gateway installation packages from your DVD or the SAP Service Marketplace into your SAP system landscape. On the SAP Service Marketplace you will find the SAP NetWeaver Gateway download package in the SAP Software Download Center: Go to http://service.sap.com/swdc and navigate to Installations and Upgrades Browse our Download Catalog SAP NetWeaver and complementary products SAP NetWeaver Gateway SAP NetWeaver Gateway 2.0 . The following SAP NetWeaver Gateway components must be installed on your SAP NetWeaver Gateway system: Framework components: o o GW_CORE 200 IW_FND 250

Note that WEBCUIF 701 is a prerequisite of IW_FND 250. Content components: The content is provided in predefined groups. Examples of such content are customer, account, and leave request grouped under CRM (Customer Relationship Management). System integrators, other vendors, and other SAP development teams can also provide similar content. The sub components contained in this package are as follows: o o IW_CNT 200 IW_CBS 200

(C) SAP AG

SAP NetWeaver Gateway 2.0 SP02

SAP NetWeaver Gateway These installation packages have a compressed format, so first unpack them into your local file system. Next, import them using the installation tool. For detailed information on unpacking the installation packages, see Loading Installation Packages from the Application Server [External]. To install the SAP NetWeaver Gateway components: 1. Log on to the SAP system in which you want to install the SAP NetWeaver Gateway components and enter the transaction SAINT. 2. Import the installation packages. For detailed information on importing the installation packages, see Installing and Upgrading Add-ons [External]. For more information on installing the SAP NetWeaver Gateway components, see the SAP note mentioned below. Optional Installation Components If you intend to create SAP NetWeaver Gateway content with Workflow, the Backend Event Publisher or Screen Scraping you need to install the following additional components on your backend system (SAP Business Suite system): IW_BEP 200 (Backend Event Publisher) IW_BEP is available with SAP NetWeaver 7.0 SPS18 and higher. IW_SCS 200 (Screen Scraping) IW_SCS is available with SAP NetWeaver 7.0 SPS18 and higher. Instead of having a system landscape with your SAP NetWeaver Gateway system that includes the four software components mentioned above and the backend system with the two software components for the SAP Business Suite functionality, you can also have a local installation with all six software components located in the same system if all prerequisites [Page 6] are fulfilled.

More Information
For more information about SAINT, see Add-On Installation Tool [External]. For more information about installing SAP NetWeaver Gateway, see SAP Note 1569624.

Support Package Migration

If you have SAP NetWeaver Gateway 2.0 SP01 installed and want to migrate your system(s) to SAP NetWeaver Gateway 2.0 SP02 some adjustments to your settings and your coding will be necessary. These changes are relevant for the SAP Business Suite backend system (software component IW_BEP).

All SAP NetWeaver Gateway Services which have already been developed and shipped with SAP NetWeaver Gateway 2.0 SP01 are still working smoothly. No further activities are needed.

(C) SAP AG

SAP NetWeaver Gateway 2.0 SP02

SAP NetWeaver Gateway Under the following circumstances adjustments will be necessary: Migration of changes to already existing OData Channel Services (Object Model groups) Creation of new OData Channel Services These activities can be done via the Implementation Guide (IMG). The following two new IMG activities are provided: Maintain Object Models Maintain Service The former IMG activity for these steps is still available but can only be accessed in read-only mode. See also Configuration Settings for OData Channel [External].

In the following sections the migration procedure of Model Groups and Object Models is described. Note that this is only needed if you want to change existing Services.

Migration
Model Groups (Services) and Object Models which have already been defined and registered via the view cluster maintenance can be migrated to the new repository objects. Migration of Object Models This activity is done in the SAP Business Suite backend system where software component IW_BEP is deployed. 1. Start the Object Model maintenance dialog via the IMG entry Maintain Object Models. 2. Select the Object Model you want to migrate via the F4 help of the Technical Object Model Name. 3. Choose Change. 4. Choose Save. You package assignment dialog displays. 5. Assign your Object Model to a package and choose Save. 6. Specify a transport request and save your settings. Migration of Model Groups These activities are done in the SAP Business Suite backend system where software component IW_BEP is deployed and also on the SAP NetWeaver Gateway hub system if necessary.

(C) SAP AG

SAP NetWeaver Gateway 2.0 SP02

SAP NetWeaver Gateway

The migration for a Model group extracts the external name from the internal name (without namespace) and overwrites the current external name. If you want to stick to your current external name it is not possible to do a migration or keep the current definition. Instead you have to define a new model group which the technical name in the format /<namespace>/<former external name>. If the external Service name exists more than once you have to delete the old Service on the SAP NetWeaver Gateway hub system as well as on the backend system. It is required that you delete the old Service on the SAP NetWeaver Gateway hub system before you activate the new one. 1. Start the Model group maintenance dialog via the IMG entry Maintain Services. 2. Select the Object Model (Service) you want to migrate via the F4 help of the Internal Service Name. 3. Choose Extra Adjust External Name .

If the naming is ok a message displays (External Service name is fine, nothing to adjust). Proceed as follows: 1. Choose Change for the selected Internal Service Name. 2. Choose Save. You package assignment dialog displays. 3. Assign your Service to a package and choose Save. 4. Specify a transport request and save your settings. If the naming is not ok the transaction adapts the external name automatically and displays the dialog for the package assignment. 5. Assign your Service to a package and choose Save. 6. Specify a transport request and save your settings. 7. Logon to the SAP NetWeaver Gateway hub system where software component IW_FND is deployed. 8. Start the activation transaction via IMG activity Activate Services. 9. Delete the old Service. For this make sure that the correct system alias is entered in the corresponding field, select the old Service in the list and choose Delete Service. 10. Activate the new Service. For this make sure that the correct system alias is entered in the corresponding field, select the new Service in the list and choose Activate Service 11. Switch to the SAP Business Suite backend system and delete the old Service. For this enter the IMG activity Maintain Service, enter the Internal Service Name of the old Service and choose Delete Service.

(C) SAP AG

SAP NetWeaver Gateway 2.0 SP02

10