Installation Guide Adapter for SAP R/3 Version 3.
DOCUMENT ID: 36350-01-0390-01 LAST REVISED: September 2002 Copyright © 1999-2002 New Era of Networks, Inc. International copyright law prohibits illegal reproduction and distribution of this document. Software described in New Era of Networks, Inc. documents is furnished under a Software License Agreement and may be copied or used only as expressly permitted under the terms of the license.
Contents About This Book ............................................................................................................................ v CHAPTER 1 Migrating to Adapter for SAP R/3 Version 3.9 .............................. 1 Process Overview ............................................................................ 1 Preparing for Upgrade...................................................................... 2 Upgrading from Version 3.0.3 to Version 3.9 ...................................
Contents CHAPTER 3 Uninstalling Adapter for SAP R/3................................................. 33 Starting the Repository................................................................... 33 Uninstalling Adapter for SAP R/3 3.9 ............................................. 34 Uninstalling Shared Components................................................... 34 Index ......................................................................................................................................
About This Book Audience The primary user of this document is the system administrator who is responsible for the installation and configuration of the server used for New Era of Networks Adapter for SAP R/3 (Adapter for SAP R/3). How to use this book This document describes how to install Adapter for SAP R/3. These instructions provide information for both a new and an upgrade installation. For a concurrent installation, contact technical support.
• JMS Driver Configuration Guide, release 2.6.1 • Tibco Driver Configuration Guide, release 2.6.1 Other related documentation is available from New Era of Networks and Sybase. Refer to documentation from each of these companies for more detail about use of applications relevant to this product.
About This Book ❖ Creating a personalized view of the Sybase web site (including support pages) Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase web pages. Conventions 1 Point your web browser to Technical Documents at http://www.sybase.com/support/techdocs/. 2 Click MySybase and create a MySybase profile.
Formatting example To indicate Type the Name of the attribute. GUI field or button name that is the recipient of a procedural action. Click Apply. If you need help Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you cannot resolve a problem using the manuals or online help, please have the designated person contact Sybase Technical Support or the Sybase subsidiary in your area.
CH A PTE R 1 Migrating to Adapter for SAP R/3 Version 3.9 This chapter explains how to migrate data from an existing database used with a previous version of Adapter for SAP R/3 to a target database. Topic Process Overview Preparing for Upgrade Page 1 3 Changes to Configuration Keys Upgrading from Version 3.0.3 to Version 3.9 3 2 Upgrading from Version 3.8 to Version 3.
Preparing for Upgrade Preparing for Upgrade Note Existing database refers to the database you are currently using. Target database refers to the database you will use with Adapter for SAP R/3 version 3.9. Before migrating formats and rules from an existing database to your target database, verify the following: • Existing database contains valid rules and formats. • Integration Server is installed.
CHAPTER 1 Migrating to Adapter for SAP R/3 Version 3.9 Upgrading from Version 3.8 to Version 3.9 Upgrading from Adapter for SAP R/3 version 3.8 to version 3.9 consists of the following steps: • Transfer user-specific configuration information from the version 3.8 configuration files to version 3.9 configuration files. You can do this manually using the sample configuration files in the SAP3_9/CFG folder or using the GUI.
Changes to Configuration Keys Version 3.0.3 Version 3.8 Version 3.9 queue.in.name=TO_SAP NNOT_TIL_OPEN_TSI=TO_S AP same as 3.8 queue.out.name=FROM_SAP NNOT_TIL_OPEN_TSI=FRO M_SAP same as 3.8 failurequeue.name=FAILURE NNOT_TIL_OPEN_TSI=FAIL URE transport.wait_time_milli same as 3.8 transport.wait_time same as 3.8 queue.exit_it_empty error.logfile transport.exit_if_empty no equivalent key same as 3.8 same as 3.8 no.special.char Default error log is NNSYMessageLog.
CHAPTER 1 Migrating to Adapter for SAP R/3 Version 3.9 Version 3.0.3 Version 3.8 Version 3.9 RFC.ClientCode RFC.UserName same as 3.0.3 same as 3.0.3 sap.client sap.user RFC.Password RFC.Language same as 3.0.3 same as 3.0.3 sap.password sap.language RFC.Trace no equivalent key same as 3.0.3 RFC.ReqWait sap.trace sap.reqWait no equivalent key no equivalent key RFC.ConnectRetries NN.retry.count sap.connectRetries sap.retry.count no equivalent key no equivalent key NN.retry.interval SAP.
Converting IDoc Formats The format conversion tool that ships with Adapter for SAP R/3 is a valuable resource for you to more easily migrate IDoc formats. Formats are dependent on the field mapping that you have done so you must also migrate those mappings. The purpose of the conversion tool is to preserve the field mappings used for output formats and transfer those current field mapping to the newly loaded format.
CHAPTER 1 ❖ Migrating to Adapter for SAP R/3 Version 3.9 To migrate IDoc formats from a 4.x Formatter database Output formats used by the Broker for IDocs sent into SAP changed between version 3.03 and version 3.8 of the SAP adapter. The segment names used to begin with E2 or Z2 and terminate with a three-digit version number. Segment names now begin with E1 or Z1 to reflect that the IDoc is inbound into SAP. Three-digit version numbers have been dropped. Note New input formats can be used as loaded.
Converting IDoc Formats 5 • The names of the two format export files created in step 1 and step 3 of this procedure. • The name that you want to use for the converted format. (This name is arbitrary). To run the conversion tool, type the command using the following as an example: sap39idoccnvtool -file= The format export files and the configuration file used to load the 3.9 schema should be placed in the SAP-3_9/bin folder. The command must be run from this same folder.
CHAPTER 1 Migrating to Adapter for SAP R/3 Version 3.9 2 Load the outbound format for the newly extended IDoc into a temporary 5.6 database using the 3.9 SAP adapter. (The example assumes an extended IDoc named ZABSEN1 was made from the base IDoc ABSEN1.) 3 Export only the outbound format of the IDoc loaded in the previous step using the NNFie utility provided with Formatter 5.x. Example: C:\sybase\bin>nnfie -e zabsen1.oc.5x.exp -m SAP.OC.
Converting IDoc Formats ❖ To update a currently used IDoc format in a 5.x Formatter database: 1 Export only the original outbound format using the NNFie utility provided with Formatter 5.x. Example: C:\sybase\bin>nnfie -e absen1.oc.5x.exp -m SAP.OC.ABSEN1 -s nnfie 2 Load the outbound format for the new version of the IDoc into a temporary 5.6 database using the 3.9 SAP adapter (the example assumes a new version of ABSEN was released - ABSEN2).
CHAPTER 1 Migrating to Adapter for SAP R/3 Version 3.9 Example Log File Source Control Record: SAP.OF.ABSEN1.CR Destination Control Record: SAP.OF.ABSEN1.CR Source Segment Name: SAP.OF.E2ABSE1 Destination Segment Name: SAP.OF.E2ABSE1 Field: Field: Field: Field: Field: Field: Field: SAP.E2ABSE1.BDEGROutMap: SAP.E2ABSE1.MOABWOutMap: SAP.E2ABSE1.ZEITYOutMap: SAP.E2ABSE1.AGRUNOutMap: SAP.E2ABSE1.BEGDAOutMap: SAP.E2ABSE1.ENDDAOutMap: SAP.E2ABSE1.
Converting IDoc Formats • The conversion tool can only convert one format at a time, so each export file must contain only one top-level format. (For example, SAP.OC.DEBMAS04) • The easiest way to provide the information necessary for a user to log into the SAP system is to use a functioning configuration file for the inbound IDoc process. The value of SAPInConfig key should be the name of this file. (For example, the Schema mode configuration file used to load the IDoc with Version 3.9.
CHAPTER 1 Migrating to Adapter for SAP R/3 Version 3.9 # database FromFormat = SAP.OC.MATMAS03^1 # name of format (loaded using new version of SAP # adapter) as seen in 5x formatter ToFormat = SAP.OC.MATMAS03.ZMATMAS_EXTENSION # # # # must provide connection parameters used by 3.9 SAP adapter to connect to SAP use inbound idoc or Schema mode configuration file to get needed params to connect to SAP SAPInConfig = in.
Converting BAPI Formats # # # # # example: name in 4x database: LEG.I.ORIGINAL_LIMITED_SIZE_NAME renamed in 5x database to LEG.I.MODIFIED_FORMAT_NAME_OF_LARGER_SIZE ToRuleInputMessage=SAP.IC.MATMAS03.ZMATMAS_EXTENSION # defaults to same name [Optional] or change rule name # RuleNameOut = # eof Converting BAPI Formats You must convert the formats for both IDocs and BAPIs when you move between versions of Adapter for SAP R/3.
CHAPTER 1 Migrating to Adapter for SAP R/3 Version 3.9 Upgrading Rules Review the rules that you are currently using with Adapter for SAP R/3. If they need to be converted for use with version 3.9: Installation Guide • For converting IDoc rules, see “Converting IDoc Formats” on page 5. • For converting BAPI rules used with 3.0.3 formats, manually convert your rules.
Upgrading Rules 16 Adapter for SAP R/3
CH A PTE R 2 Installing Adapter for SAP R/3 This chapter describes how to prepare for and run an installation on a Windows NT, Windows 2000, Solaris, AIX, or HP-UX server.
Preparation Integration Server Support Adapter for SAP R/3, version 3.9, supports the following integration servers: • e-Biz Integrator, version 3.6 • MQSeries Integrator, version 2.0.2 • WebSphere MQ Integrator, version 2.1 Note MQSeries Integrator version 2.0.2 does not support multi-byte data. Settings for Integration Servers The following combinations of integration server, OT driver, schema loader, and serializer can be used with Adapter for SAP R/3, version 3.9.
CHAPTER 2 Installing Adapter for SAP R/3 Table 2-2: Server transport support Driver Flat File Version 2.6 Supported Platforms NT, Solaris, HP-UX, AIX MQSeries MSMQ 2.6 2.6 NT, Solaris, HP-UX, AIX NT Tibco JMS 2.6.1 2.6.1 NT NT, Solaris Supported Platforms and Compilers “Supported Platforms and Compilers” on page 19 identifies the operating systems and compilers required for this product. Use this table to identify the software required for installation.
Preparation Table 2-3: Server Operating System Windows NT 4.0 (Service Pack 6a or higher) DBMS Sybase ASE 12 Sybase ASE 12.5 Compiler Microsoft Visual C++, version 6.0 Microsoft SQL Server 2000 Windows 2000 (Service Pack 2 or higher) Microsoft SQL Server 7 Oracle 8i r3 (8.1.7) Oracle 9i DB2 UDB 7.1 Solaris 8 DB2 UDB 7.2 Sybase ASE 12 Sybase ASE 12.5 Oracle 8i r3 (8.1.7) SparcWorks C++, version 6.0, update 1 Oracle 9i DB2 UDB 7.1 HP-UX 11.00 DB2 UDB 7.2 Sybase ASE 12 Sybase ASE 12.
CHAPTER 2 Installing Adapter for SAP R/3 the software, it can remain on the same server. Installation of the current release does not overwrite the previous installation and does not affect any files you might have added. CIM Repository The CIM (common information model) repository shares installation information across Sybase and New Era of Networks products, tracking version and path information for each product installation.
Preparation ❖ To start a repository If the repository is already installed, you must provide the server, port number, and user information for the existing repository. The system populates the screen with default values for the server, port number, and user information, but you can modify the values if necessary. • Use platform specific commands to start the repository: a On Windows, enter the following: cd \CIMRepository-3_0_0\bin repository.
CHAPTER 2 Installing Adapter for SAP R/3 Note Do not use spaces or special characters in your UNIX path. Disk Space and Memory Requirements Disk space NT: 183 MB for adapter and temporary directory used during installation UNIX: 208 MB for adapter and 160 MB for temporary directory Memory 256 MB for product files Required Software “Supported Platforms and Compilers” on page 19 identifies the operating systems and compilers required for this product.
Running Executables Before Installing the Adapter on Windows Running Executables Before Installing the Adapter on Windows You must run the following executables or .msi files from the Adapter for SAP R/3 Server CD before you install the Adapter for SAP R/3 on Windows. • From your CD-ROM drive, open the vbruntime-6_0 folder and doubleclick on vbrun60sp4.exe to install Visual Basic runtime. This is used by the GUI. When the install is finished, click OK.
CHAPTER 2 Installing Adapter for SAP R/3 CIMRepository The Common Information Model (CIM) Repository shares installation information across Sybase and New Era of Networks products, tracking version and path information for each product installation. If the repository is already installed, it is not necessary to install a new CIM Repository. However, the repository must be running before you can install products. After the installation has been completed, you can stop the CIM Repository to save resources.
Installing Adapter for SAP R/3 Temporary Installation Directory The installer uses a temporary location during the installation process. The default temporary location on Windows is defined in the system environment variables and is usually set to C:\temp. The default temporary location on UNIX is /var/tmp. If enough space is not available in the default temporary location, the installer may not start or may start but notify you that sufficient space is not available.
CHAPTER 2 Installing Adapter for SAP R/3 If the installation directory does not exist, you can either create the directory or the installer will create the installation directory when installation begins. If you get a memory error while installing, see “Temporary Installation Directory” on page 26. Note Before you begin the installation, the repository must be running unless you plan to install a new one.
Installing Adapter for SAP R/3 export DISPLAY= 3 To change to the /mnt_point directory, enter: %cd mnt_point 4 To start the installer, enter: %./setup The Installer Welcome window appears. 5 c Got to step 3 of the main procedure. On AIX: 1 Mount the CD-ROM. For example: pfs_mount /mnt_point 2 Set the IP address: export DISPLAY= 3 To change to the /mnt_point directory, enter: %cd mnt_point 4 To start the installer, enter: %.
CHAPTER 2 Installing Adapter for SAP R/3 %cd mnt_point 4 To start the installer, enter: %./setup The Installer Welcome window appears. 5 3 Got to step 3 of the main procedure. To initiate the installation process, click Next on the Installer Welcome window. The Installer window appears. 4 To specify an installation directory, choose one of the following: a To accept the default directory, click Next. b To use a different directory, click Browse, select the directory, and click Next.
Installing Adapter for SAP R/3 Figure 2-1: Repository Information a To install a new repository, based on requirements detailed in “CIMRepository” on page 25: 1 Choose Install a new repository. The Repository Connection Information is not visible in the Repository Information window. 2 Click Next. The Repository Installation window displays the repository components to be installed. 3 Click Next. The Repository Installation window displays the progress of the installation.
CHAPTER 2 2 Installing Adapter for SAP R/3 Accept the defaults for Repository Connection Information if possible. The defaults are shown in Figure 2-1 on page 30. Note If you use an existing repository, the repository must be running to continue the installation. 3 Click Next. The Select Products to Install widow appears. 7 From the Select Products to Install window, accept the default settings and click Next.
Understanding Environment Variables Table 2-4: //SAP-3_9 Subdirectory /bin /CFG Description contains wrapper scripts for executables and shared libraries contains sample configuration files /NNSYCatalogues /share contains ctg message and error files contains data files Understanding Environment Variables Required environment variables are set by wrapper scripts at runtime.
CH A PTE R 3 Uninstalling Adapter for SAP R/3 This chapter explains how to uninstall Adapter for SAP R/3 version 3.9. To uninstall Adapter for SAP R/3 version 3.8, use the installer that was provided with that version. Call Sybase Technical Support for instructions on uninstalling a version earlier than 3.8. Topic Starting the Repository Page 33 Uninstalling Adapter for SAP R/3 3.
Uninstalling Adapter for SAP R/3 3.9 Uninstalling Adapter for SAP R/3 3.9 A separate uninstaller is provided to remove Adapter for SAP R/3 version 3.9. The scripts to start the uninstaller are located in \SAP-3_9. ❖ • For Windows, uninstall.bat • For Unix, uninstall.sh To uninstall Adapter for SAP R/3 version 3.9: 1 Move any custom or other files that you want to save from the SAP-3_9 directory to another directory.
CHAPTER 3 Uninstalling Adapter for SAP R/3 This provides a correct version of the JRE for running the uninstallers. Note If you do not copy JRE_1_3 to a temporary location, you will not be able to uninstall all of the shared components. 2 To verify that Java version 1.3.
Uninstalling Shared Components 8 On the Feature Select window, select all items to be removed and click Next. 9 When the selected components are uninstalled, click Finish. 10 After repeating steps 5 through 9 for all of the shared products, delete the copy of JRE_1_3 that you had moved to a temporary directory. 11 Manually remove the remaining directory.
Index B book organization formats IDoc v 5 I C changes to configuration keys 3 CIM Repository 25, 30 compilers HP aC++ 20 Microsoft Visual C++ 20 SparcWorks C++ 20 VisualAge C++ 20 configuration key changes 3 conventions vii conversion tool configuration file 12 converting IDoc formats 5 D database existing 2 target 2 databases DB2 UDB 20 Microsoft SQL Server Sybase ASE 20 default directory 26 documentation set v IDocs converting format 5 integration servers e-Biz Integrator 18 MQSeries 18 MQSI 2.
R repository running 27, 29 S SAP installing 27 uninstalling 34, 35 T temporary directory 26 transport supported 18 typographical conventions vii U uninstall SAP 3.8 33 SAP 3.9 33 shared components upgrading 1 BAPI formats 14 from 3.0.3 2 from 3.
