Table of Contents
Advertisement
Quick Links
Advertisement
Table of Contents
Summary of Contents for Sybase Adapter for SAP R/3
- Page 1 Installation Guide Adapter for SAP R/3 Version 3.9...
- Page 2 Networks HIPAA Accelerator, and Physician Access are trademarks, and CL/7, MicroScript and Transaction Distribution Manager, TDM are registered trademarks of New Era of Networks, Inc. and its subsidiaries. Sybase and the SYBASE (logo) are registered trademarks of Sybase, Inc. MQSeries is a registered trademark of International Business Machines Corporation.
-
Page 3: Table Of Contents
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 ........2 Upgrading from Version 3.8 to Version 3.9 ........3 Changes to Configuration Keys ............ - Page 4 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 ............................. 37 Adapter for SAP R/3...
-
Page 5: About This Book
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. - Page 6 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. Other sources of...
- Page 7 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. Point your web browser to Technical Documents at http://www.sybase.com/support/techdocs/...
- Page 8 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.
-
Page 9: Chapter 1 Migrating To Adapter For Sap R/3 Version 3.9
Migrating to Adapter for SAP R/3 C H A P T E R 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 Page Process Overview... -
Page 10: Preparing For Upgrade
Preparing for Upgrade Existing database refers to the database you are currently using. Note 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: •... -
Page 11: Upgrading From Version 3.8 To Version 3.9
This list contains keys that are typically used in configuration files but may not be all of the keys you have used. See the Adapter for SAP R/3 User’s Guide for a specific version for a complete list of configuration keys for that version. - Page 12 NNLogFileName same as 3.0.3 sap.logFile NN.VerboseLog same as 3.0.3 sap.verboseLog MQS.QueueManagerName NNMQS_SES_OPEN_QMGR same as 3.8 MQS.GetQueueName NNOT_TIL_OPEN_TSI same as 3.8 MQS.PutQueueName NNOT_TIL_OPEN_TSI same as 3.8 MQS.ErrorQueueName NNOT_TIL_OPEN_TSI same as 3.8 RFC.Destination same as 3.0.3 sap.destination Adapter for SAP R/3...
-
Page 13: Converting Idoc Formats
Converting IDoc Formats You must convert the formats for both IDocs and BAPIs when you move between versions of Adapter for SAP R/3. Custom formats can continue to use names that begin with unique prefixes to differentiate them from standard formats. - Page 14 The New Era of Networks utility programs msgtest.exe and ruletest.exe can be used to validate your converted messages and rules. The IDoc conversion tool for Adapter for SAP R/3 provides the tools to do the following: •...
- Page 15 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.
- Page 16 Test the format by using it as the target format for reformatting a test message. To update a newly extended IDoc format in a 5.x Formatter database: 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 Adapter for SAP R/3...
- Page 17 Test the format by using it as the target format for reformatting a test message. The way extended IDocs are treated is the major consideration for the Note conversion process between Adapter for SAP R/3 versions 3.8 and 3.9. Extended IDocs are no longer considered special situations. Installation Guide...
- Page 18 Import the format created by the conversion utility into the target database using the NNFie utility provided with Formatter 5.x. Example: C:\ConversionTests\>nnfie -i absen2.oc.conv.exp -g - s nnfie Test the format by using it as the target format for reformatting a test message. Adapter for SAP R/3...
-
Page 19: Example Log File
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: SAP.E2ABSE1.BDEGROutMap: InMap: LEG.F1 Field: SAP.E2ABSE1.MOABWOutMap: InMap: LEG.F2 Field: SAP.E2ABSE1.ZEITYOutMap: InMap: LEG.F3 Field: SAP.E2ABSE1.AGRUNOutMap: InMap: LEG.F4... -
Page 20: Example Conversion Tool Configuration File
# MUST begin at the beginning of the line, the # associated keys MUST be below the session name # and indented by spaces or tabs. Comments are # preceded by #. #-------------------------------------------------- NNConv # name of original format as seen in formatter Adapter for SAP R/3... - Page 21 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...
-
Page 22: Converting Bapi Formats
Converting BAPI Formats You must convert the formats for both IDocs and BAPIs when you move between versions of Adapter for SAP R/3. Custom formats can continue to use names that begin with user-defined prefixes to differentiate them from standard formats. -
Page 23: Upgrading Rules
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: • For converting IDoc rules, see “Converting IDoc Formats” on page 5. - Page 24 Upgrading Rules Adapter for SAP R/3...
-
Page 25: Installing Adapter For Sap R/3
Installing Adapter for SAP R/3 C H A P T E R This chapter describes how to prepare for and run an installation on a Windows NT, Windows 2000, Solaris, AIX, or HP-UX server. Topic Page Preparation Disk Space and Memory Requirements... -
Page 26: Integration Server Support
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. Table 2-1: Settings for Integration Servers Schema... -
Page 27: Supported Platforms And Compilers
CHAPTER 2 Installing Adapter for SAP R/3 Table 2-2: Server transport support Driver Version Supported Platforms Flat File NT, Solaris, HP-UX, AIX MQSeries NT, Solaris, HP-UX, AIX MSMQ Tibco 2.6.1 2.6.1 NT, Solaris Supported Platforms and Compilers “Supported Platforms and Compilers” on page 19 identifies the operating systems and compilers required for this product. -
Page 28: Installation Environment
Installation Environment Previous Releases If you have a previous version of New Era of Networks Adapter for SAP R/3 installed, it is suggested that you uninstall that version before installing the current release. However, if you plan to continue to use your older version of... - Page 29 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. If the repository is already installed, you do not need to install a new CIM Repository. However, the repository must be running before you can install products.
- Page 30 • Use platform specific commands to specify an install directory: On Windows, enter the following: setup -is:tempdir <full path to alternate temp directory> On UNIX, enter the following: setup -is:tempdir <full path to alternate temp directory> Adapter for SAP R/3...
-
Page 31: Disk Space And Memory Requirements
CHAPTER 2 Installing Adapter for SAP R/3 Do not use spaces or special characters in your UNIX path. Note 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... -
Page 32: Running Executables Before Installing The Adapter On Windows
Preparing the Installation Environment Previous versions If you have a previous version of Adapter for SAP R/3 installed, it is suggested that you uninstall that version before installing the current version. However, if you plan to continue to use your older version of the software, it can remain on the same server. -
Page 33: Cimrepository
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. -
Page 34: Temporary Installation Directory
For all installation instructions, <install dir> refers to the default installation directory. • If installing on Windows, the default is C:\Sybase. • If installing on Unix, the default is /user/u/Sybase. When installing on Unix, do not use spaces or special characters in the path. Adapter for SAP R/3... - Page 35 On Unix, type ps -ef | grep dbsrv7 To install Adapter for SAP R/3 using the InstallShield Wizard: These installation instructions assume you are logged onto the server with administrative rights/user permissions. When installing on UNIX, it is best to perform the install directly on the target machine in the Common Desktop Environment (CDE) single window mode.
- Page 36 Installing Adapter for SAP R/3 export DISPLAY=<IP address:0.0> To change to the /mnt_point directory, enter: %cd mnt_point To start the installer, enter: %./setup The Installer Welcome window appears. Got to step 3 of the main procedure. On AIX: Mount the CD-ROM.
- Page 37 To accept the default directory, click Next. To use a different directory, click Browse, select the directory, and click Next. For optimum performance, install all Sybase and New Era of Note Network products into the same directory. To configure the repository, do one of the following: If your repository is running, the Select Products To Install window appears.
- Page 38 Installing Adapter for SAP R/3 Figure 2-1: Repository Information To install a new repository, based on requirements detailed in “CIMRepository” on page 25: Choose Install a new repository. The Repository Connection Information is not visible in the Repository Information window.
- Page 39 The product installed correctly; you can ignore the errors. 10 For Windows, reboot the machine. Adapter for SAP R/3 and the Sybase shared components are located in the user specified installation directory <install dir>. The Adapter for SAP R/3 software is located in <install dir>\SAP-3_9.
-
Page 40: Understanding Environment Variables
SAP39_ROOT and CGC39_ROOT with a value of <install dir> and the variable RFC_INI with a value of <install dir>\CFG\saprfc.ini. Complete configuration information is supplied in Adapter for SAP R/3 User’s Guide and should be used after verifying the installation and before using Adapter for SAP R/3. -
Page 41: Chapter 3 Uninstalling Adapter For Sap R/3
C H A P T E R 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. -
Page 42: Uninstalling Adapter For Sap R/3 3.9
Manually remove the remaining <install dir>\SAP-3_9 directory. Uninstalling Shared Components You must first uninstall Adapter for SAP R/3 version 3.9 and any other New Era of Networks or Sybase products that use these shared components. You will receive a message when you attempt to uninstall any component that is required by another product. - Page 43 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.
- Page 44 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 <install dir> directory. Adapter for SAP R/3...
-
Page 45: Index
IDoc formats example database migration existing MQSeries Integrator target MQSI 2.0.2 databases MSMQ DB2 UDB Microsoft SQL Server Sybase ASE default directory documentation set NCF Serializer NNT56 Schema Loader e-BIz Integrator operating systems HP-UX Solaris Windows NT Flat File Installation Guide... - Page 46 27, 29 installing uninstalling 34, 35 temporary directory transport supported typographical conventions uninstall SAP 3.8 SAP 3.9 shared components upgrading BAPI formats from 3.0.3 from 3.8 rules WebSphere MQ Integrator XML Serializer Adapter for SAP R/3...