TIBCO ActiveMatrix Adapter for SAP · TIBCO ActiveMatrix Adapter for SAP Installation Related...

TIBCO ActiveMatrix® Adapter for SAP

InstallationSoftware Release 6.0February 2009

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN LICENSE.PDF) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIB, TIBCO, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now, TIBCO ActiveMatrix BusinessWorks, TIBCO Rendezvous, TIBCO Administrator, TIBCO Designer, TIBCO Runtime Agent, TIBCO Hawk, TIBCO Enterprise Message Service, TIBCO Designer Add-in for TIBCO Business Studio, TIBCO ActiveMatrix Service Grid, TIBCO ActiveMatrix Service Bus, TIBCO ActiveMatrix BusinessWorks Service Engine, and TIBCO Business Studio are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT 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.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 1999-2009 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viTIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viThird Party Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiTerminology and Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xHow to Contact TIBCO Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Chapter 1 Installing TIBCO ActiveMatrix Adapter for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Preparing your Environment for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2SAP System Application Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Pre-Installation Worksheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Installer Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Uninstalling an Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Installation Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Microsoft Windows Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9UNIX Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Installation History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Adapter Components and Compatible Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Adapter Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Required and Optional TIBCO Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installation on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Installing the Adapter on Microsoft Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Combining Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Installation on UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Installing the Adapter on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Combining Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Post Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Permission Requirements on UNIX Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Prerequisites for Running the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

TIBCO ActiveMatrix Adapter for SAP Installation

iv | Contents

Setting Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Installation FAQs and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Frequently Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Running Out of Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Installation Errors on HP-UX 11.00 64 bit Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Configuring TIBCO Hawk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Cannot Install the Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 2 Preparing the SAP System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Designtime Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Runtime Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Outbound Messaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Inbound Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Configurations in the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Creating a Logical System for an Adapter Instance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Creating a Logical System for the SAP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Establishing the Distribution Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Defining RFC Destinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Defining Partner Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Maintaining Partner Profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Defining an Extended IDoc Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55


| v

Preface

This document describes supported features, platforms, installation, configuration, and overall architecture of TIBCO ActiveMatrix Adapter for SAP.

Topics

• Related Documents, page vi

• Terminology and Acronyms, page x

• How to Contact TIBCO Customer Support, page xii


vi | Preface

Related Documents

This section lists documentation resources.

TIBCO Product DocumentationThe following documents form the TIBCO ActiveMatrix Adapter for SAP Documentation set:• TIBCO ActiveMatrix Adapter for SAP Concepts Read this manual before reading

any other book in the documentation set. This book describes the adapter, adapter features, and the applications that the adapter interacts with.

• TIBCO ActiveMatrix Adapter for SAP Installation Read this manual to learn how to install TIBCO ActiveMatrix Adapter for SAP.

• TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment This manual explains how to create and configure standalone adapter projects. Information on deploying adapter projects is also included.

• TIBCO ActiveMatrix Adapter for SAP Examples This manual provides instructions to run the examples that demonstrate use of the adapter.

• TIBCO ActiveMatrix Adapter for SAP Release Notes Read this document for information about new features, deprecated features, and open and closed issues.

Other TIBCO Product DocumentationYou may find it useful to read the documentation for the following TIBCO products..

• TIBCO Designer™

• TIBCO Administrator™

• TIBCO ActiveMatrix BusinessWorks™

• TIBCO Rendezvous®

• TIBCO Enterprise Message Service™

• TIBCO Hawk®

• TIBCO Adapter™ SDK• TIBCO Runtime Agent™


Related Documents | vii

Third Party Documentation• SAP R/3: Implementation Guide by Bradley D. Hiquet, available from

Kelly-Lacey & Associates Inc. This is “A Manager’s Guide to Understanding SAP” that emphasizes the user’s point of view. Printed in 1998 by Macmillan Technological Publishing.

• SAP R/3 Business Blueprint by Thomas Curran and Gerhard Keller. Printed in 1998 by Prentice Hall PTR.

• SAP R/3 System, A Client/Server Technology by Rudiger Buck-Emden. This is a general technical overview that is easy to read. Printed in 1996 by Addison-Wesley.


viii | Preface

Typographical Conventions

The following typographical conventions are used in this manual

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_HOME

Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco.

Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. The directory into which such products are installed is referenced in documentation as ENV_HOME. The value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand pathname


Typographical Conventions | ix

Key combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use


x | Preface

Terminology and Acronyms

Term Definition

ABAP Advanced Business Application Programming is a language in SAP used to write SAP specific code.

ALE/IDoc Application Link Enabling/Intermediate Documents.

API Application Program Interface.

Application Server The server on which the SAP processes run.

BAPI Business API (Functionally equivalent to RFC).

CIF Certified Intermediate Format.

Component A self-contained replaceable functional unit of the adapter that provides a set of interfaces. TIBCO ActiveMatrix Adapter for SAP has two kinds of components; r3Outbound and r3Inbound. r3Outbound encapsulates functionality for outbound communication with the SAP system while r3Inbound encapsulates the functionality for inbound communication with the SAP system.

EDI Electronic Data Interchange.

EMS Enterprise Message Service

Gateway Server A server used to exchange data with the SAP system.

Inbound Instance An adapter configuration listening for messages inbound to SAP. Inbound instances transfer messages from the TIBCO environment to SAP.

Interface A functional sub-unit of the adapter that exposes one or more adapter services. For example, the RFCServer interface exposes RFC/BAPI Request-Response Invocation services.

JMS JAVA Messaging Service

MBCS Multi-byte character string.

One Way Invocation protocol

One way invocation protocol allows you to invoke the BAPI/RFC in the SAP system without waiting for a reply from the system.

Outbound Instance An adapter configuration listening for messages outbound from SAP. Outbound instances transfer messages from SAP to the TIBCO environment.


Terminology and Acronyms | xi

RV TIBCO Rendezvous™ protocol; also in certain contexts refers to reliable message quality of service, as opposed to certified message.

RFC The SAP Remote Function Call Interface.

RFC Client A SAP term for any program that can post RFCs/BAPIs/IDocs from an external system into the SAP system.

RVCM TIBCO Rendezvous certified message quality of service.

RFC Server A SAP term for any external program that can accept and process RFCs/BAPIs/IDocs from the SAP system.

RVDQ TIBCO Rendezvous distributed queue.

SAP Native data All SAP data that the adapter interacts with. It consists of RFC data types. This includes IDocs received as RFC tables in an RFC function call.

SSL Secure Sockets Layer.

TID Transaction ID. A globally unique identifier used by transactional RFCs to ensure exactly-once execution of a transaction.

TIDManager Transaction Identifier Manager.

Term Definition


xii | Preface

How to Contact TIBCO Customer Support

For comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows.

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you can request one.


http://www.tibco.com/services/support

https://support.tibco.com

Installing TIBCO ActiveMatrix Adapter for SAP | 1

Chapter 1 Installing TIBCO ActiveMatrix Adapter for SAP

This chapter explains how to install TIBCO ActiveMatrix Adapter for SAP on Microsoft Windows and UNIX systems.

Topics

• Preparing your Environment for Installation, page 2

• Installer Overview, page 7

• Installation Registry, page 9

• Adapter Components and Compatible Software, page 11

• Installation on Microsoft Windows, page 13

• Installation on UNIX Systems, page 17

• Post Installation, page 20

• Installation FAQs and Troubleshooting, page 24

This software may be available on multiple operating systems. However, not all operating system platforms for a specific software version are released at the same time. Please see Table 4 on page 13 and Table 5 on page 17 for the availability of this software version on a specific operating system platform.


2 | Installing TIBCO ActiveMatrix Adapter for SAP

Preparing your Environment for Installation

The most time-consuming part of an adapter installation is the collection of environment information and parameters. This section helps you complete this process. It provides a checklist of parameters you should obtain from various system administrators within your organization before installing the adapter. Note that obtaining an SAP system account can take some time depending on your corporate policies — so plan in advance!

Operating System RequirementsObtain the following information from the administrator of the machine on which you plan to install the adapter:

Do you have the required credentials to run the installer?

• On Microsoft Windows, administrator privileges are required to install.

• On UNIX systems, you can install as root or a regular user. See Installer Account on page 17 for details.

• Note that the TIBCO Runtime Agent (TRA) must be installed prior to installing the adapter and the adapter installation always places files under the TIBCO root directory that was set when the TRA was installed.

There should be enough space on the disk or partition to install the adapter. The adapter needs space in your temp area and the directory where it is installed.

• See Installation Registry on page 9 for details about temp folder space requirements on Microsoft Windows and UNIX systems.

• See Table 4 on page 13 for Microsoft Windows installations

• See Table 5 on page 17 for Unix System installations.

You must have write permissions to these directories to install the adapter. In addition, on UNIX systems certain other permissions must be set to run the adapter. See Permission Requirements on UNIX Systems on page 20 for details.

• To run the adapter you must have permissions to access the project where adapter configuration is stored.

• Depending on whether a repository server is used, and whether TIBCO Administrator is used to set access permissions, you may need an account identified by Administrator. See the TIBCO Administrator User’s Guide for details.


Preparing your Environment for Installation | 3

Determine how the adapter installation files are to be transferred to this system. The installation files can be downloaded from download.tibco.com (if you have an account setup to download).

SAP System Application Requirements• Determine which SAP application versions are supported.

See TIBCO ActiveMatrix Adapter for SAP readme.txt for supported SAP vserions.

• It is recommended that the SAP GUI be installed on the machine for troubleshooting and testing purposes.

• Download and install the following SAP Software libraries on the machine where the adapter is being installed.

a. Design-time adapter components require the SAP Java Connector.

Download the SAP Java Connector from the following URL: http://service.sap.com/connector

b. Run-time adapter components require the RFC library.

Download the SAP RFCSDK Unicode version of the libraries from the following URL:

http://service.sap.com/connector

A valid SAP Service ID is required. For more information, contact your SAP BASIS administrator.

The TIBCO ActiveMatrix Adapter for SAP run-time and design-time can be run using the libraries available with SAP JCO 2.1.6.

The TIBCO ActiveMatrix Adapter for SAP run-time on Microsoft Windows platform for Unicode support can be run using the libraries available with RFCSDK Unicode 6.40. It is recommended that you use the same versions.



Pre-Installation Worksheet

Use this form to capture the information you will need to collect before starting installing the TIBCO ActiveMatrix Adapter for SAP.

Adapter Machine Information

Field Name Field Description Field Value

Hostname

(Example: adapter1.tibco.com)

Name of the machine on which the adapter is being installed.

IP address

(Example: 192.168.12.12)

IP address of the machine on which the adapter is being installed.

User account

(Example: administrator)

User account to be used for the installation.

User domain (if Windows)

(Example: ENGR2)

Network domain to which the user belongs.

User password

(Example: admin)

User Password

Disk/path on which to install adapter

(Example: /opt/tibco)

How will machine be accessed

[ ] directly [ ] terminal server [ ] xterm [ ] telnet

[ ] other: ………………………

How will installation files be transferred to machine

[ ] CD-drive [ ] internet download

[ ] FTP to machine [ ] network disk mounting


Pre-Installation Worksheet | 5

SAP R/3 Outbound Connection Information

SAP R/3 Inbound Connection Information

• Dedicated Application Server Connection Information


SAP Gateway Host:

(Example: athps5)

Name of the machine on which the SAP gateway server is running.

SAP Gateway Service:

(Example: sapgw00)

Gateway service to connect to, on the gateway server.

Program ID:

(Example: idocpub)

Program name to which the RFC destination is mapped.


User account for adapter

(Example: jsmith)

SAP client account to be used by the adapter.

Password for adapter

(Example: 1$todo)

Password for the above account.

Application Server hostname

(Example: sapserver1.tibco.com)

Name of the SAP application server to connect to.

System No

(Example: 00)

System number for the application server.

Client

(Example: 210)

Number assigned to the SAP client to which this user belongs.

R/3 Logon Language

(Example: EN)

Language to be used to logon to the SAP system for this client.



• Load-balanced Connection Information

SAP Client Software

Specify where the software for the SAP GUI can be found within your organization:

[ ] It's already installed on adapter machine.

Location on disk: ………………………….

[ ] Installation files are available via :

FTP (Server : ………… User : ………… Password: ……… )

Disk mount (full path : ………………………………………..)

CD provided during install by (name/extension) : ………………………..


User account for adapter

(Example: jsmith)

SAP user account to connect from the adapter.

Password for adapter

(Example: abc$&)

Password for the above account.

Group Name:

(Example: PUBLIC)

SAP logon group name to be used for load balancing.

Messaging Server Name

(Example: msgsvr1)

Name of the central SAP instance to connect to for load balancing.

System Name:

(Example: TIBCO)

SAP System ID to be used for load balancing.


Installer Overview | 7

Installer Overview

The installer allows you to run in different modes. Each mode is supported on all platforms.

• GUI mode

• Console mode

• Silent mode

GUI Mode

In GUI mode, the installer presents panels that allow you to make choices about product selection, product location, and so on. You can invoke the installer by clicking on the executable.

Console Mode

Console mode allows you to run the installer from the command line. This is useful if your machine does not have a GUI environment.

Silent Mode

Silent mode either installs using default settings or uses a response file that was saved during an earlier installation. Silent mode installs without prompting you for information.

• If no response file has been recorded earlier and you invoke the installer with the -silent argument, the default installation parameters are used.

• If a response file exists, and the installer is started with -options <responseFileName> as an argument, the installer uses the values specified by the user when the response file was generated.

Uninstalling an AdapterIf another product is dependent on the product you wish to uninstall, you are informed that you must uninstall the other product first.

Microsoft Windows

Use one of the following options to uninstall the Adapter from the Microsoft Windows platform:



• Click Start>Programs>TIBCO>TIBCO ActiveMatrix Adapter for SAP version_number > Uninstall

• Navigate to the _uninst directory located in the Adapter installation directory and invoke the Tibuninstall.exe program.

• Click Start>Programs>TIBCO>TIBCO Installation Manager

• Use Add/Remove Programs from the Control Panel.

UNIX

Use one of the following options to uninstall the Adapter from the supported UNIX platform:

• Navigate to the _uninst directory located in the Adapter installation directory and invoke the Tibuninstall.bin program.

• Run TIBCO Installation Manager which is located in the <install-path>/tibco/TibcoInstallationManager.bin.


Installation Registry | 9

Installation Registry

The installer maintains an installation registry. The registry location depends on platform. This section explains where the registry files are located. The files have vpd as a prefix, which stands for Vital Product Database. Note that the installer does not recognize TIBCO ActiveEnterprise 4.x products.

Microsoft Windows PlatformsActiveEnterprise products maintain the installation registry in the SystemDrive:\WINDOWS directory. The following files represent the installation registry:

SystemDrive:\WINDOWS\vpd.propertiesSystemDrive:\WINDOWS\vpd.properties.tibco.systemName

Installer Disk Space Requirements in Temporary Area

The entire package is extracted into a temp folder, typically SystemDrive:\Temp or SystemDrive:\Documents and Settings\<user_name>\Local Settings\Temp

The installer requires 66 MB of free space in the temp directory.

UNIX PlatformsThe installation registry is maintained in the following files in the user's home directory:

User_Home_Directory/vpd.propertiesUser_Home_Directory/vpd.properties.tibco.systemName

If installation is performed by super-user (root), the installation registry is maintained as follows:

• On Solaris and HP-UX, in the root user’s home directory (which is /) has two vpd files.

• On Linux, in the /root directory has two vpd files.

• On AIX, in the /usr/lib/objrepos directory has two vpd files.

Do not edit, modify, rename, move, or remove any of the registry vpd files.



Installer Disk Space Requirements in Temporary Area

The installer first extracts a Java Virtual Machine (JVM) in a temporary directory and uses this JVM to launch itself. The size of the extracted JVM differs from platform to platform.

On UNIX platforms the following disk space is required in the temporary area:

• On Solaris, 91 MB of free disk space in /var/tmp

• On HP-UX, 120 MB of free disk space in /var/tmp

• On AIX, 118 MB of free disk space in /tmp

• On Linux, 125 MB of free disk space in /tmp

If your system does not have sufficient free disk space in the above temporary area, you can still run the installer with a different temporary area by using the following option when starting the installer:

<install_package_name>.bin -is:tempdir /new_tmp

where /new_tmp has sufficient free disk space.

Disk Space Requirement in User's Home Directory

On UNIX platforms when a regular (non-root) user installs a TIBCO product, the installation registry (two vpd files) is maintained in the user's home directory. As more products are installed, entries are added into these vpd files.

The user's home directory must at least have 500 KB of free disk space.

Installation HistoryThe installer and uninstaller create a file called TIBCOInstallationHistory.xml in the same location where the installation registry is created. Each time an installation and uninstallation is performed, entries are appended to the file.

On Microsoft Windows: SystemDrive:\WINDOWS\TIBCOInstallationHistory.xml

On UNIX: Users_Home_Directory/TIBCOInstallationHistory.xml

The file TIBCOInstallationHistory.xml therefore contains the record of all installation and uninstallation activities of all products, features and components.

Do not edit, modify, rename, move, or remove the TIBCOInstallationHistory.xml file.


Adapter Components and Compatible Software | 11

Adapter Components and Compatible Software

You can install different adapter components on different machines. For example, you can run the runtime adapter on one machine and install the design-time components on another machine. This allows you to configure an adapter on one machine and run it on another.

Adapter ComponentsTable 2 describes the adapter components on the adapter installation package.

Required and Optional TIBCO ProductsDepending on the tasks you wish to perform, you must install one or more other TIBCO products. The next table describes required and optional products and their purpose. For the supported versions of the listed products, refer TIBCO ActiveMatrix Adapter for SAP readme.txt.

Table 2 TIBCO Adapter components

Component Description

Runtime This process does the actual work of passing and converting data to and from the vendor application.

This component includes the runtime adapter and the TID Manager.

Designtime Adapter-specific GUI that is loaded in TIBCO Designer (see next section for details) at configuration time.

This component includes the palette and samples that demonstrate how TIBCO ActiveMatrix Adapter for SAP interacts with TIBCO ActiveMatrix BusinessWorks.

Documentation This component is required for context senstitive help.



Table 3 Compatible products

Component Purpose

TIBCO Runtime Agent Required. TIBCO Runtime Agent supplies a number of TIBCO and third-party libraries used by the adapter and other TIBCO products both at design-time and runtime. This includes RVD libraries, SDK libraries etc. For example maverick50.dll.

You must install TIBCO Runtime Agent on each machine that hosts an adapter. TIBCO Runtime Agent must be installed before you install the adapter.

TIBCO Administrator Required for deployment. TIBCO Administrator includes the following modules:

• User Management. Management of authentication, roles and users, that is, connecting roles (groups) and users to access control lists (ACLs). This includes security for server-based projects at design-time and for deployed applications at runtime.

• Resource Management. Monitoring of machines and of all running applications in a TIBCO administration domain. Alerts can be created, for example, to notify an administrator if the number of processes or disk usage exceeds a certain number.

• Application Management. Uploading of Enterprise Archive (EAR) files, creation, configuration, deployment, and monitoring of applications. This console is also used to start and stop applications.

TIBCO Administrator is available as a separate installation and can be installed after installing the adapter.

TIBCO ActiveMatrix BusinessWorks

Optional. TIBCO ActiveMatrix BusinessWorks is a scalable, extensible, and easy to use integration platform that allows you to develop integration projects. TIBCO Adapters are typically part of integration projects created using TIBCO ActiveMatrix BusinessWorks.

TIBCO ActiveMatrix BusinessWorks is available as a separate installation and can be installed after installing the adapter.

TIBCO Enterprise Message Service

Optional. TIBCO Enterprise Message Service allows you to use the Java Messaging Services (JMS) as the message transport for your adapter.

TIBCO Enterprise Message Service is available as a separate installation and can be installed after the adapter is installed.


Installation on Microsoft Windows | 13

Installation on Microsoft Windows

Before starting the installation, review the topics in this section to determine that your system meets the basic requirements and that you have the prerequisite software installed.

Memory requirement for the adapter installation is approximately 256 MB.

The following is a list of prerequisites for installing the adapter on Microsoft Windows systems. See Installer Disk Space Requirements in Temporary Area on page 9 for additional disk space requirements.

Table 4 Supported platforms, service packs and disk space for Microsoft Windows

Supported SAP Application Versions

TIBCO ActiveMatrix Adapter for SAP readme.txt lists the SAP supported versions.

Installer Account

You must have administrator privileges for the machine on which the adapter is installed.

If you do not have administrator privileges, the installer will exit. You must then log out of the system and log in as a user with the required privileges, or request your system administrator to assign the privileges to your account.

Installing from Network Drive

If you intend to install the product on a network drive, you must ensure that the account used for installation has permission to access the network drive.

A set of Non-Unicode binaries with adr3.exe as the executable exists to connect to Non-Unicode systems only. To connect to both Unicode and Non-Unicode versions of the adapter, you must use adr3u.exe as the executable.

Platform Hardware Platform

Disk Space (MB)

Microsoft Windows XP Professional x86 200 MB

Microsoft Windows 2003 (Enterprise Edition)



Installing on Microsoft Windows 2003 Terminal Server

There are two modes in Microsoft Windows Terminal Server: Execute and Install. Users are logged on by default in Execute mode, which allows them to run applications. To install an adapter so that everyone can use it, log on as administrator in Install mode. When the adapter is installed in the Install mode, the installation registry is maintained in SystemDrive:\WINDOWS\.

The best way to install the adapter on Microsoft Windows Terminal Server is to use the Add/Remove Programs control panel applet. This automatically sets your mode to Install during the installation and then back to Execute afterwards. Alternatively, you can manually change your mode to Install before starting the installation by typing the following at a command prompt:

C:\> change user /install

Change back to Execute mode after installation is complete by typing:

C:\> change user /execute

To check your current mode, type the following:

C:\> change user /query

Installing the Adapter on Microsoft WindowsYou can either download the adapter package or install the package from a CD. The installer prompts you to accept the license agreement. Then you can choose to perform a typical install or custom install.

• A typical install has minimal prompts and installs standard components in default locations.

• A custom install prompts you to choose which components of the product suite to install and installs only those components.

The installer checks your system for the installation home directory that was established when TIBCO Runtime Agent was installed. The adapter is installed under the installation home directory.

Use one of the following modes to install the software.

Microsoft Windows Terminal Server must be running in remote admin mode, not application sharing mode. The adapter is not supported if installed on a machine that is using Microsoft Windows Terminal Server in application sharing mode.

There must not be any spaces in the installation directory path.


Installation on Microsoft Windows | 15

Install Using GUI Mode

GUI Mode allows you to input values in panels. Double-click on the executable appropriate for your platform.

During the installation process you will be prompted for the location of the SAP JCO libraries.

Install Using Console Mode

Console mode allows you to install the software from a command line. The installer will prompt you for values. Type the following at the command prompt:

<install_package_name> -is:javaconsole -console

When running in console mode you can move through the installation process as described next:

Enter Key or 1 = Moves forward in the installer2 = Goes back to previous screen3 = Cancels the Wizard and exits the installation or uninstallation4 = Redisplays the current screen

Install Using Silent Mode

Silent mode allows you to install the software without prompts. Type the following at the command prompt:

<install_package_name> -silent

Install and Generate a Response File

You can generate a response file during any installation of the product and can use the same file in future installations. For all installation modes using response file, the options in the file determines what will be installed.

To install and generate a response file, type the following at the command prompt:

<install_package_name> -options-record C:\directory\<responseFile>

Install Using a Response File

You can use a previously generated response file for installation. For all installation modes, the response file determines what will be installed.

To install using a response file, type the following at the command prompt:

<install_package_name> -options C:\directory\<responseFileName>



Combining OptionsYou can combine the different available options. For example, to install in silent mode using a response file, use:

<install_package_name> -silent -options <responseFileName>

To install using Console mode and generate a response file, use:

<install_package_name> -is:javaconsole -console -options-record <responseFileName>


Installation on UNIX Systems | 17

Installation on UNIX Systems

Your operating system must meet the minimum patch requirements listed next. See Installer Disk Space Requirements in Temporary Area on page 10 for additional disk space requirements.

Memory requirement for the adapter installation is around 256 MB. Your operating system must meet the minimum patch requirements listed next.

Installer Account

TIBCO 6.x products can be installed by a regular (non-root) user and super-user (root). Different users can install the same product at different locations.

Product dependencies at install time are resolved at user level through the installation registry maintained at user's home directory. See Installation Registry on page 9 for more information.

Windows Environment

A window environment such as CDE (i.e. X Windows) is required to run the installer in GUI mode. It is not required for a console or silent mode installation.

Table 5 Supported platforms, patches and disk space for UNIX systems

Platform Hardware Platform Disk Space (MB)

Solaris 8, 9, 10 SPARC 200 MB

HP-UX 11i PA-RISC 200 MB

HP-UX 11i V2, V3 Itanium (ia64)

Itanium (ia64) 200 MB

AIX 5.2, 5.3 POWER 200 MB

Redhat Enterprise Linux 4.0

x86 200 MB

SUSE Enterprise Linux 9.3

x86 200 MB



Installing the Adapter on UNIXAfter running the software and accepting the license agreement, you can choose to perform a typical install or custom install.

• A typical install has minimal prompts and installs standard components in default locations.

• A custom install prompts you to choose which component of the product is to be installed and installs only those components.

The installer checks your system for the installation home directory that was established when TIBCO Runtime Agent was installed. The adapter is installed under the installation home directory.

• If installing the adapter on AIX, use a non-root user account.

Use one of the following modes to install the software. The examples assume you are installing the adapter on Solaris 8.

Install Using GUI Mode

GUI Mode allows you input values in panels. Type the following in a terminal window and press ENTER:

% ./<install_package_name>.bin

During the installation process you will be prompted for the location of the SAP JCO libraries.

Install Using Console Mode

Console mode allows you to install the software from a command line. The installer will prompt you for values. Type the following in a terminal window:

% ./<install_package_name> -is:javaconsole -console

When running in console mode you can move through the installation process as described next:

Enter Key or 1 = Moves forward in the installer2 = Goes back to previous screen3 = Cancels the Wizard and exits the installation or uninstallation4 = Redisplays the current screen

There must not be any spaces in the installation directory path.


Installation on UNIX Systems | 19

Install Using Silent Mode with Default Values

Silent mode allows you to install the software without prompts using default values. Type the following in a terminal window:

% ./<install_package_name> -silent

Install and Generate a Response File

You can generate a response file during any installation of the product and can use the same file in future installations. For all installation modes using response file, the options in the file determines what will be installed.

To install and generate a response file, type the following at the command prompt:

% .<install_package_name> -options-record /dir/<responseFile>

Combining OptionsYou can combine the different available options. For example, to install in silent mode using a response file, use: % ./<install_package_name> -silent -options /dir/<responseFileName>

To install using Console mode and generate a response file, use: % ./<install_package_name> -is:javaconsole -console -options-record /dir/<responseFileName>

The response file does not record selections at the component level It does record all other selections, for example, which products you wish to install.



Post Installation

Ensure that there is only one copy of the individual SAP JCO components on your machine. In particular, ensure that the librfc32.dll (or librfccm.so or librfccm.sl or librfccm.o) library that comes with SAP JCO 2.1.6 is the only version of librfc on the machine. This library is also packaged with the SAPGUI. Hence, if you have SAPGUI installed on the machine and the librfc library packaged by SAPGUI precedes the SAP JCO 2.1.6 librfc library, the adapter will use the wrong librfc version.

If there is a version mismatch, the following error is displayed.

For the Unicode version of the adapter on Microsoft Windows platform (adr3u.exe), ensure that you have the latest librfc32u.dll available at the SAP website.

If an older version of the librfc32u.dll is in use, the following error is displayed.

Permission Requirements on UNIX SystemsAll adapter users must have read, write, and execute permissions for the following directories:

$TIBCO_HOME/adapter/adr3/<version_number>/bin $TIBCO_HOME/adapter/adr3/<version_number>/logs$TIBCO_HOME/adapter/adr3/<version_number>/ledger$TIBCO_HOME/tra/<version_number>/logs$TIBCO_HOME/logs

See TIBCO ActiveMatrix Adapter for SAP Configuration and Deployment for information on how to enable design-time configuration with the SAP system.


Post Installation | 21

For example, if the adapter has been installed in /opt/tibco, the user who installed the adapter can make these directories writable for all other users by executing the following commands:

% chmod a+w /opt/tibco/adapter/adr3/<version_number>/bin/% chmod a+w /opt/tibco/adapter/adr3/<version_number>/ledger% chmod a+w /opt/tibco/adapter/adr3/<version_number>/logs% chmod a+w /opt/tibco/tra/<version_number>/logs

Prerequisites for Running the AdapterYou need to carry out the following tasks for successful messaging between the application and the TIBCO environment.

• Prepare the SAP system to communicate with the adapter. See Preparing the SAP System on page 29 for details.

• Set environment variables. See Setting Environment Variables on page 21.

Setting Environment VariablesThe adapter sets the environment variables differently depending on whether the adapter is installed on UNIX or Windows.

Windows

The adapter's default property file adr3.tra has a property named tibco.env.PATH. During installation, the installer updates the tibco.env.PATH in this file with the location of the TIBCO software required by the adapter.

For example, the installer writes the following for tibco.env.PATH in adr3.tra:

C:/TIBCO/adapter/adr3/<version_number>/hotfix/lib; C:/TIBCO/adapter/adr3/<version_number>/lib;C:/TIBCO/tra/<version_number>/hotfix/bin;C:/TIBCO/tra/<version_number>/bin;C:/TIBCO/tpcl/<version_number>/bin;C:/TIBCO/TIBRV/bin;C:/TIBCO/designer/<version_number>/bin

Note that the adr3.tra file is the default property file that is shipped with the adapter.

To launch your adapter configuration, make a copy of this file and update the repository and configuration url to the correct values in the copy.

When the adapter is started with this newly created custom property file, the system settings are automatically updated.



The following example illustrates the procedure to start the adapter from the command line:

1. Create an adapter configuration in TIBCO Designer and save it to a project.

2. Export the project to a .dat file using the File > Export Full Project and specify values for Project Name and Dir Name fields in the Local Repository tab.

3. Copy the default adr3.tra file to MyAdapter.tra

4. Update tibco.repourl and tibco.configurl parameters in MyAdapter.tra

5. Update application.args parameter to application.args adr3 -system:propFile <absolute path to MyAdapter.tra>

6. Start the adapter with the command adr3 --propFile MyAdapter.tra

It is assumed that MyAdapter.tra is in the adapter installation bin directory. If it is copied to any other location, provide the absolute path to this file in the command as explained in the previous step.

UNIX

A shell script adr3setenv.csh is provided with the installation. Running this file in the C-Shell updates the system path and library path settings.

The following environment variables are updated by the script:SHLIB_PATH (HP-UX)

LD_LIBRARY_PATH (Solaris and Linux)

LIBPATH (AIX)

PATH (ALL Platforms)

Note that the shell script updates the environment for the current shell session only. If you open a new shell session, run the script afresh to update.

The following example illustrates the procedure to start the adapter from the command line:

1. Create an adapter configuration in TIBCO Designer and save it to a project.

2. Export the project to a .dat file using the File > Export Full Project and specify values for Project Name and Dir Name fields in the Local Repository tab.

3. Copy the adr3.tra file to MyAdapter.tra

4. Update tibco.repourl and tibco.configurl parameters in MyAdapter.tra


Post Installation | 23

5. Update application.args parameter to application.args adr3 -system:propFile <absolute path to MyAdapter.tra>

6. Open a c-shell by typing csh at the prompt.

7. Run the script adr3setenv.csh in <install-dir>/<version_number> with the following command:source adr3setenv.csh

If the settings are updated successfully, the following message is displayed:environment variables successfully set

8. Start the adapter with the following command:

adr3 --propFile MyAdapter.tra

It is assumed that MyAdapter.tra is in the adapter installation bin directory. If it is copied to any other location, provide the absolute path to this file in the command as explained in the previous step.

The following table lists useful environment variables that you can set in the .tra file that you are using.

For the HP-UX platform, two .csh script files are available, one for the unicode system and one for the non-unicode system.

Choose the script file appropriate for your system.

Name Description Valid Values Default

RFC_TRACE Turns the RFC Trace on for all connections established by the adapter to the SAP system

0 - OFF

1 - ON

0

RFC_TRACE_DIR Defines location for RFC trace files A valid directory Working Directory

RFC_MAX_TRACE The maximal size (in megabytes) of trace files.

8 MB

RFC_INI Location of the saprfc.ini file A valid directory Working Directory

CPIC_MAX_CONV Defines the maximum number of active RFC connections at a time

A valid integer 100



Installation FAQs and Troubleshooting

This section lists some of the frequently asked questions, common errors along with their causes and solutions.

Frequently Asked Questions

Where is the installation log file located?

Install and uninstall log files are created in the TIBCO_HOME\log directory.

What should I do, if JVM crashes when I run the installer?

TIBCO product installer contains JVM 1.1.8 (except on Linux and HP platforms which bundle 1.4.2). The installer first extracts the bundled JVM into a temporary area and then uses it to launch itself. If for some reason, the JVM crashes, you could still run the installer using another JVM, preferably JVM 1.4.2 or higher. The syntax is:

<install_package_name> -is:javahome C:\j2sdk1.4.2<install_package_name> -is:javahome /opt/jre142

The executable name used in the example above is for Solaris 8.

The javahome directory must contain bin/java.exe or bin/java.

The installer will use the externally supplied JRE to launch itself.

What should I do if the adapter searches for msvcr71.dll while starting up on Microsoft Windows XP?

Place the msvcr71.dll under Windows/System32 folder. The msvcr71.dll is required for versions of SAP JCO higher than 2.1.6.

Why and how should I set the DISPLAY variable on UNIX platforms for GUI mode?

The installer in GUI mode on UNIX, must open an additional window, generally for graphics. It uses the DISPLAY environment variable to let the user know on what computer the window is to be opened. If the environment variable is not set, the installer will either wait or abort after displaying:

InstallShield WizardInitializing InstallShield Wizard...Preparing Java(tm) Virtual Machine......................................


Installation FAQs and Troubleshooting | 25

...................................

........

The DISPLAY variable must be set to the IP address or name of the computer (on which the installer graphics windows are to be displayed), followed by a screen address, which can be :0.0 . For example:

# Bourne shellDISPLAY=<ip_address>:0.0; export DISPLAY

# Korn shellexport DISPLAY=<ip_address>:0.0

# C-shellsetenv DISPLAY <ip_address>:0.0

For example, consider a scenario where you need to install the adapter on a remote HP-UX machine (named itaska). Because you have a Solaris 5.7 machine (named alaska) that has a video card and monitor installed, you can run an X-window application on it. So you decide to telnet to itaska from alaska.

When you telnet to itaska, you will not get access to itaska's monitor and will be unable to display an X-window application. That is why you must set the DISPLAY variable, which instructs the X-server to redirect all windows to the computer set in the variable. Before doing so, the computer (specified in the DISPLAY variable) must give permissions to share its monitor.

alaska> xhost + # give permission for all to its share monitoralaska> telnet itaskaWelcome to HP-UX itaska 11.00User:Password:itaska> export DISPLAY=alaska:0.0 # set display on alaskaitaska> TIB_adr3-simple_<version_num>_h7_110_aCC.bin

What is uninst2 directory?

If the original uninstall directory is in use at uninstall time, it cannot be removed by the installer program. The installer then creates a second uninstall directory for the second installation. To remove the second installation, you must invoke the uninstall program from the second uninstall directory. The original uninstall directory can also be manually removed, if empty.

Running Out of Disk SpaceThe installer calculates the disk space required in product home location, for the selected components. The calculation is done before the actual installation (copying of files to system) begins. The installer will proceed only if sufficient free disk space is available in product home location.



However, if disk space is consumed by another process while the installer is copying the files, and if the required disk space is thereby reduced, the installer may fail and will then give a failure message.

Solution

While performing installation, avoid running other processes that consume disk space in product home location.

Installation Errors on HP-UX 11.00 64 bit Platform

Error message

Installation on a HP-UX 11.00 64 bit system may crash with the following error message:

Pid nnn killed due to trashed stack.Pid nnn was killed due to failure in writing the signal context.

This happens only on HP-UX 11.00 64 bit systems. It does not happen on HP-UX 11.00 32 bit system and HP-UX 11.11 (or 11.i) system.

To determine the OS version on your system, run:

uname -a

To determine the kernel bits on your system, run:

getconf KERNEL_BITS

Resolution

HP-UX kernel patch PHKL_27282, resolves the above crash.

To determine if your system has the kernel patch, run:

/usr/sbin/swlist -l product PHKL_27282

or

what /stand/vmunix | grep PHKL_27282

If your system is an HP-UX 11.00 64 bit system and it does not have the patch, first install HP-UX kernel patch PHKL_27282 and then proceed with the installation. Installation of patch PHKL_27282, will reboot your system.


Installation FAQs and Troubleshooting | 27

Configuring TIBCO Hawk

Error

TIBCO Runtime Agent includes the TIBCO Hawk Agent only. If you install the full TIBCO Hawk package after installing TIBCO Runtime Agent and do not have a Java Runtime Environment (other then the TIBCO JRE) installed, the TIBCO Hawk Configuration tool is unable to determine the Java home location and the JVM executable. The TIBCO Hawk services will not start correctly and you will be unable to start the TIBCO Hawk Display.

Resolution

1. Start the TIBCO Hawk Configuration tool. For example, on Microsoft Windows:

Start>TIBCO>TIBCO Hawk>Hawk Configuration

2. Under the General tab, click Advanced.

3. In the Java Home Directory field, provide the path to Java. For example:

C:\tibco\jre\1.4.2

4. In the JVM Executable field, provide the JVM executable. For example:

java.exe

The services will start properly and the TIBCO Hawk Display will run.

Cannot Install the AdapterOn HP-UX and AIX platforms, even though the correct version of TIBCO Runtime Agent version is already installed on the system, installation of an adapter that depends on TIBCO Runtime Agent may fail in the dependency resolution.

The TIBCO product installer maintains the registry information in the vpd.properties.tibco.systemName file. The value for systemName is determined by InetAddress.getLocalHost().getHostName(). However, the method getHostName(), returns different values based on the JRE versions used. For example, on AIX, JRE 1.3.1 returns only systemName, whereas JRE 1.4.2 returns systemName.domainName. Because of this, the installer is not able to load the correct registry file.



Resolution

On Unix platforms, the installer registry file vpd.properties.tibco.systemName is located in the user's home directory.

Case 1: If the vpd.properties.tibco.systemName file exists:

$ cd user's_home_directory$ ln -s vpd.properties.tibco.systemName

vpd.properties.tibco.systemName.domainName

For example:$ cd ~$ ln -s vpd.properties.tibco.upside vpd.properties.tibco.upside.tibco.com

where upside is systemName, and tibco.com is domainName

Case 2: If the vpd.properties.tibco.systemName.domainName file exists:

$ cd user's_home_directory$ ln -s vpd.properties.tibco.systemName.domainName vpd.properties.tibco.systemName

For example:

$ cd ~$ ln -s vpd.properties.tibco.upside.tibco.com vpd.properties.tibco.upside

where upside is systemName, and tibco.com is domainName.


| 29

Chapter 2 Preparing the SAP System

This chapter gives an overview of the minimum requirements and authorizations required to extract metadata from an SAP system during the configuration stage. The steps for customizing an SAP system for Inbound and Outbound messaging are also described.

You must enable the SAP system for messaging with the TIBCO environment by carrying out appropriate customization. No modifications or additional code is required in the SAP system itself.

Topics

• Designtime Requirements, page 30

• Runtime Requirements, page 32

• Configurations in the SAP System, page 35


30 | Preparing the SAP System

Designtime Requirements

The following are the design-time requirements:

• Obtain a valid SAP user ID and password that allows access to a dedicated SAP application server. This is necessary even if you plan to configure the adapter for Outbound messaging only. A valid user ID and password is required to extract metadata for BAPIs/RFCs/IDocs using TIBCO Designer.

• Obtain required authorization from your SAP system administrator to execute Remote Function Calls and access tables in SAP for the design-time user ID. You will not be able to successfully extract schema information in TIBCO Designer without the necessary permissions in SAP for your user-id.

Specifically, ensure that the following Remote Function Calls can be executed successfully from transaction SE37 in your SAP GUI with the test-data provided.

The SAP user ID must have permissions to execute RFCPING in the SAP system. RFCPING is used by the adapter to verify the state of connections. If you do not have execute permissions for it, a short dump is created in the SAP system.

Remote Function Call Test Input Data

RFC_GET_TABLE_ENTRIES systems TABLE_NAME = EDBAST (4.x and higher SAP systems)

TABLE_NAME = EDIDOT (for 3.x SAP systems)

RFC_GET_TABLE_ENTRIES TABLE_NAME = EDICM

RFC_GET_TABLE_ENTRIES TABLE_NAME = EDCIMT

EDI_IDOC_SYNTAX_GET PI_IDOCTYP = MATMAS01

PI_CIMTYP = <empty> or extended idoctype for MATMAS01, if any

RFC_GET_STRUCTURE_DEFINITION_P (for 4.x and higher systems) RFC_GET_STRUCTURE_DEFINITION_P

_3 (for 3.x SAP systems)

TABNAME = E1MARAM

RFC_FUNCTION_SEARCH FUNCNAME = * (or name of any RFC/BAPI)


Designtime Requirements | 31

• If you are configuring an Inbound adapter and the run-time connection parameters for the adapter are going to be different from the design-time, obtain the relevant connection information. For configuring a load-balanced inbound adapter, you will need parameters to connect to a messaging server for a specific logon group.

RFC_GET_FUNCTION_INTERFACE_P (4.x and higher SAP systems) RFC_GET_FUNCTION_INTERFACE (3.x SAP systems)

FUNCNAME = <name of any RFC/BAPI>

Remote Function Call Test Input Data

Ensure that your login parameters specify the correct language. IDocs/RFCs/BAPIs specific to a particular language will not be retrieved if you login to SAP from the SAP GUI or TIBCO Designer with a different language.



Runtime Requirements

Customization required for run-time interactions with the adapter are described here. The GUI screen shots describing the customization process in this chapter use SAP version 4.6C.

Additional steps might be required, depending on pre-existing maintenance and allocations in the client SAP system. Refer to the help section in the SAP IMG (Implementation Guide) and other appropriate SAP user documentation before customizing.

Outbound MessagingThe SAP system has to be customized to send out BAPI/RFC Invocations and Intermediate Documents to the TIBCO environment. This section describes the minimum configuration to be done in the system to achieve outbound messaging.

Configuration Needed for Invoking BAPIs/RFCs from the SAP System

1. Define an RFC destination in the SAP system.

An RFC Destination should be defined and mapped to a program-id. The Outbound adapter registers on the SAP gateway with this program-id (specified in the adapter configuration) and receives BAPIs/RFCs invoked on the corresponding RFC Destination. An RFC destination allows the SAP system to invoke BAPIs/RFCs in the Outbound adapter.

For configuration details, see Defining RFC Destinations on page 42.

2. Make sure that the required authorizations for executing BAPIs and RFCs exist for the SAP username intended to be used.

Configuration Needed for Publishing IDocs from the SAP System

All required ALE outbound customizing can be done using the SAP implementation management guide (IMG, transaction SALE).

The following minimum steps must be performed to enable the transfer of SAP system IDocs to the TIBCO environment.

1. Create a logical system for the adapter. See Creating a Logical System for an Adapter Instance on page 35 for details.

2. Associate the client logical system with an SAP Client. See Creating a Logical System for the SAP Client on page 39 for details.


Runtime Requirements | 33

3. Define the customer distribution model - this defines what IDocs can be transferred in the outbound direction. See Establishing the Distribution Model on page 40 for details.

4. Define RFC destination. See Defining RFC Destinations on page 42 for details.

5. Define the Partner Profile. See Defining Partner Profiles on page 45 for details.

6. Set up (maintain) the RFC Transactional Port. See Maintaining Partner Profile on page 48 for details.

Inbound MessagingThis section describes the minimum configuration to be done in the system to achieve inbound messaging.

Configuration Needed for Invoking BAPIs/RFCs from the TIBCO environment

Ensure that the SAP client performing invocations in SAP through the adapter (that is the Inbound adapter logged on to SAP with specific client connection parameters) has authorizations to invoke BAPIs/RFCs in the SAP system.

Authorization for each business activity needs to be given to the SAP client if that activity is performed via the adapter. For instance, if the Inbound adapter is configured to create sales orders in SAP, then the SAP client needs all the required permissions to create a sales order.

Verify the authorizations by test-executing the BAPI/RFC from transaction se37 in the SAP GUI without specifying a destination.

ALE Customization for transferring IDocs from the TIBCO environment

All required ALE inbound customizing can be done using the SAP implementation management guide (IMG, transaction SALE).

The following minimum steps must be performed to enable the transfer of messages from the TIBCO environment into the SAP system as IDocs.

1. Create a logical system for the adapter. See Creating a Logical System for an Adapter Instance on page 35 for details.

2. Associate the client logical system with an SAP Client. See Creating a Logical System for the SAP Client on page 39 for details.

3. Define the customer distribution model - this defines what IDocs can be transferred in the inbound direction.

4. Define the Partner Profile. See Defining Partner Profiles on page 45 for details.



Maintain the Partner profiles. In the inbound parameters of partner profile, associate a Process Code for each IDoc type defined for the partner profile.

5. Link this process code to a Function-module, which processes the inbound IDoc.


Configurations in the SAP System | 35

Configurations in the SAP System

The following section provides the steps required to customize the SAP ALE system, using the SAP GUI version 4.6C to operate with the adapter.

The steps are listed next.

1. Creating a Logical System for an Adapter Instance

2. Creating a Logical System for the SAP Client

3. Establishing the Distribution Model

4. Defining RFC Destinations

5. Defining Partner Profiles

6. Maintaining Partner Profile

7. Defining an Extended IDoc Type

Creating a Logical System for an Adapter InstanceThe first requirement is to create an ALE logical system to represent the adapter publication service.

To create a logical system for the adapter application, follow these steps:

1. Log on to the SAP Server.

2. Run the sale transaction:

An ALE window appears with a hierarchical choice of configuration and maintenance options.

3. Navigate to, Application Link Enabling (ALE)>Basic Settings>Logical Systems>Define Logical System and click



When you click to the left of the phrase Define logical system, the following warning window appears.

4. Click to continue.



A Change View window appears like the following:

5. Click the New Entries button to create a new logical system.

An empty New Entries: Overview of Created Entries list window appears.

6. Enter the name of the new application logical system — DOCVIEW is shown below for example — under the Log.System column.

Enter a suitable description under the Name column.

7. Save the new logical system.



The Prompt for Workbench request window appears.

Assign a change request to the change using an existing change request, or create a new change request. If you want to create a new change request, complete the following step.

8. Click on Create request in the bottom button bar.

The Create Request window appears.

9. Enter a short description and save the request.

The system returns you to the Change View window.



10. Scroll down the alphabetical list to verify the creation of the new logical system.

11. Click to return to the initial window.

Creating a Logical System for the SAP ClientThe logical system for the client represents the client itself as a business entity, so that the relationship between the client and other logical systems can be set up. To create a logical system for the adapter client, follow these steps:

1. Log on to the SAP Server.

2. Run the sale transaction.

3. Navigate to

Application Link Enabling (ALE)>Basic Settings>Logical Systems> Define Logical System

4. Click the New Entries button to request the interface used to create a new logical system.



An empty New Entries window appears.

5. Enter the name of the new logical system in the top window and enter the city.

6. Choose from the Logical System pop-up, the client for which you want to create the new logical system (often the logical system you are logged into).

7. Enter a suitable description under column Short Text and choose a role, such as Test.

8. Save the new logical system.

Establishing the Distribution ModelTo make ALE work properly, your SAP system needs to know the relationship between the logical systems. You can establish these relationships through the Maintain Distribution Model dialog.

To establish the distribution model, follow these steps:

1. Run the sale transaction.

2. Navigate to Modelling and Implementing Business Processes.



3. Click the icon next to Maintain Distribution Model and Distribute Views.

The following window is displayed:

4. Go to the edit mode

5. Click the Model View button to create a model view that contains the relationships between logical systems you want to establish.

The Create Model View window is displayed.

6. Type in the name and short description for the new model view, then click

to create the model view.

7. In the Maintain Distribution Model window, click Add Message type to establish the relationship between the logical systems you created.



8. Give the model view a name, then establish the relationship between the adapter and the client by choosing your client logical system (example - CLIENT830) as the Sender/client and your Adapter logical system (example - DOCVIEW) as the Receiver/server. Choose a message type (example - DOCMAS).

9. Repeat the process to include the type of the message you later want to send to the TIBCO environment. For example, include MATMAS if you want to send material IDocs.

10. Click and save.

Now you have established the relationship between the logical systems. You can view it by expanding the model on the original Distribution Model screen.

Defining RFC DestinationsAn RFC destination allows the SAP system to call service functions in the Outbound Adapter configured as an IDoc publisher. RFC uses TCP/IP to interface with the Outbound Adapter.

One or more RFC destinati.ons for the Outbound Adapter processes have to be defined. Usually, only one RFC destination is used. Multiple Outbound Adapter processes can be load balanced by an SAP gateway via a single RFC destination. Multiple destinations can be useful when different destinations are to be used for different ports. The ports are in turn used for different message types.



1. Run the sale transaction and navigate to

Application Link Enabling (ALE)>Communication>Create RFC Connections

2. Click the Create button. The following window appears.

3. Specify the RFC destination. The RFC destination should have the same name as the adapter logical system you created. Choose T (TCP/IP connection) as

the connection type, and click .

4. Save the setting.



5. In the RFC Destination window, click Registration and specify the Program ID.

6. Click the Save icon. This completes definition of an RFC destination.

The Program ID must match the Program ID value in the adapter instance in the repository. It is a good idea to use a different name than that of the logical system itself. Also, it is recommended that you do not associate the name to the RFC destination or logical system.

Select the Unicode radio button to connect to the Unicode version of the adapter.

To use the adapter in the multi threaded mode, the value specified for the Max Connections parameter for the RFC destination should match the value for the Max Connections parameter set in the adapter configuration file (.dat file).

This configuration change can be done using the transaction code SMQS.



Defining Partner ProfilesThe partner profile consists of information about the partners participating in a logical system.

Given below are a couple of examples for information included in a partner profile,

• information on transferred documents

• information on whether the logical system receives or transmits data.

To set up the partner profiles, follow these steps:

1. Run the sale transaction and choose Application Link Enabling (ALE) >Modelling and Implementing Business Processes>Partner Profiles>Generate Partner Profiles.



2. In the window that appears, select the distribution model you defined earlier as the Model View and the logical system for the Adapter you defined earlier as the Partner system.

3. For all other fields, retain the default settings.

4. Choose the execute button.

5. If execution works without errors, save the partner profile by clicking the small open-folder icon. The partner profile will be created with the default port.

In case you want to change the port associated with the message type, following steps need to be carried out to create a port.



6. Enter transaction we21 or run transaction sale and navigate to Application Link Enabling (ALE) >Sending and Receiving Systems>Systems in Network>Asynchronous Processing>Maintain Ports>Define Port.

7. Click on Transactional RFC to highlight it and click the Change (Pencil) icon.



8. Click New entries on the next window.

9. Enter (or select) the name of the logical system and give a description for the new port. This completes definition of a partner profile.

If multiple logical message types are used in your environment, it is recommended that you define different ports for different message types or for groups of message types.

Maintaining Partner ProfileAn outbound partner profile must be defined for each logical message type that is to be sent to the TIBCO environment. The outbound partner profile defines the message syntax to be used for the logical message type, the transfer mode, the port to send to, and the workflow parameters (where error notifications are to be sent etc.). In the previous section (Defining Partner Profile), the partner profile is created for logical message type MATMAS. This section explains how you change the partner profile to add, delete or change the message types and associated parameters.

1. Run transaction sale and work through the hierarchy displayed to:Application Link Enabling (ALE) >Modelling and Implementing Business

The presence of the “Version” entry is important. It determines the version of IDocs transmitted, 30x or 40x. Version value of 2 causes EDI_DC (IDoc version 30X) metadata to be used for the IDoc publisher mode. Version value of 3 causes EDI_DC40 (IDoc version 40X) metadata to be used for the IDoc publisher mode.



Processes>Partner Profiles and Time of Processing>Maintain Partner Profile.

2. Choose the adapter logical system you defined earlier and LS as the partner type, then click the change (pencil) icon.

3. In the next window, enter ALE as the partner type and A (active) as the partner status.

4. Select Outbound Parameters.

5. Change the Outbound Parameters so each message type is included for your publisher.

6. Save the Partner Profile for the publisher.



Defining an Extended IDoc TypeSAP makes basic IDoc types available for use with SAP processes. You can create extensions to a basic IDoc type using the procedure described in this section.

1. To create an IDoc extension, initiate transaction WE30. The Develop IDoc Types screen is displayed. An example of this screen is shown below. Select the Extension radio button as shown below to indicate that you are going to create an extension to an existing IDoc type.

2. Enter the name of your IDoc extension in the ObjectName text box. Note that names used by SAP are case insensitive. See the following example.



3. Click the Create icon (folded paper) or enter the function F5 key to proceed with extension creation. The Create extension screen is displayed, as shown below.

4. Select the Create new radio button. This step associates the new extension with a basic IDoc type. This is done by entering the name of a basic IDoc type, such as DEBMAS03, in the Linked basic type text entry box.

5. Click the down arrow to the right of the text entry box and select the basic type from the list that is displayed. When you have entered the basic IDoc type, enter a description in the Description box. When your entries are

complete, click to proceed with the extension creation.

6. The following Create extension screen is displayed. This screen shows the initial default segments contained in the new IDoc extension, as defined by



the basic IDoc type (DEBMAS03 in the example). Add segments using this screen.

7. For example, you can add a second child segment to segment E1KNA1L by highlighting the current child segment and clicking on the Create icon (folded paper).

8. An information screen is displayed as shown in the following example. Click

to acknowledge the information.

9. The Attribute Maintenance screen is displayed as in the following example. Enter a valid existing segment type, such as ZLEON as shown in the example screen. Also enter values for the Minimum and Maximum Number



of segments that are allowed. Click .

10. The Create Extension screen is displayed again with the new child segment as shown in the example below. Save the new IDoc extension.




| 55

Index

A

add message type 41ALE

generating Partner Profiles 45in partner profile 49

API xassign client to logical system 39

C

configuration filelogical system specification 37

create Request window 38Customer Support xii

D

define Port 47distribution model 40documents related vi

E

ENV_HOME viii

G

Generate Partner Profiles 45

L

logical systemadapter application 42client (sending and receiving SAP system) 42correspondence to keyword in the publisher config-

uration file 37creating 37

for SAP client 39required 42saving new 40verifying creation 37, 40

M

maintaindistribution model 41logical systems 35Partner Profile 49

model viewadding message type 41

O

outbound partner profilemaintain 48set up 48

P

partner profileRFC port 47

Program ID 44


56 | Index

Prompt for Workbench request window 38

R

related documents viRFC

define transactional ports 47RV xiRVCM xiRVDQ xi

S

sale transaction 35, 39SAP server

logging on 35, 39

T

TIBCO_HOME viii


Date post:	02-May-2018
Category:	Documents
Upload:	dangtuyen
View:	232 times
Download:	5 times