iWay Application Adapter for mySAP
ERP User’s Guide
Version 6.0.1 Service Manager (SM)
iWay
Cactus, EDA, EDA/SQL, FIDEL, FOCUS, Information Builders, the Information Builders logo, iWay, iWay Software, Parlay, PC/FOCUS, RStat, TableTalk, Web390, and WebFOCUS are registered trademarks, and Magnify is a trademark of Information Builders, Inc.
Due to the nature of this material, this document refers to numerous hardware and software products by their trademarks. In most, if not all cases, these designations are claimed as trademarks or registered trademarks by their respective companies. It is not this publisher’s intent to use any of these names generically. The reader is therefore cautioned to investigate all claimed trademark rights before using any of these names other than to refer to the product described.
Copyright © 2009, by Information Builders, Inc. and iWay Software. All rights reserved. Patent Pending. This manual,
Contents
Preface...7
Documentation Conventions...8
Related Publications...9
Customer Support...9
Help Us to Serve You Better...9
User Feedback...11
iWay Software Training and Professional Services...12
1. Introducing the iWay Application Adapter for mySAP ERP...13
Features of the iWay Application Adapter for mySAP ERP...14
Supported Versions and Platforms...14
Classical SAP Technologies for ABAP...15
Integrating With SAP...16
Component Information for the iWay Application Adapter for mySAP ERP...17
Component Information Roadmap...18
iWay Service Manager...18
iWay Explorer...19
iWay Business Services Provider...19
Enterprise Connector for J2EE Connector Architecture (JCA)...19
Web Services and Java Connector Architecture Functionality...20
Web Services...20
Java Connector Architecture...20
2. Getting Started...23
Installing the iWay Application Adapter for mySAP ERP...24
Installing the SAP Java Connector (SAP JCo)...25
SAP JCo files by Platform...26
Installing SAP JCo on Windows Platforms...26
Installing SAP JCo on UNIX Platforms...27
Verifying the SAP Java Connector (SAP JCo)...27
Verifying SAP JCo on Windows Platforms...27
Verifying SAP JCo on UNIX Platforms...29
Identifying mySAP Logon Parameters...31
User Parameters...32
System Settings (Application Server) Parameters...33
System Settings (Message Server) Parameters...34
Connection Pool Parameters...35
SAP Gateway Parameters...36
ALE Parameters...37
Global Processing Parameters...38
SNC Parameters...39
Verifying Connections to mySAP...40
Verifying a mySAP Client Connection...40
Verifying a mySAP Server Connection...42
3. Configuring SAP Inbound Processing...43
Overview...44
Configuring a Logical System...45
Configuring a Distribution Model...50
Defining a Partner Profile...53
4. Creating XML Schemas for mySAP...59
Overview...60
Starting iWay Explorer (Servlet)...60
Establishing a Target for mySAP...62
Creating a New Target...62
Connecting to a Target...71
Disconnecting From a Target...74
Modifying a Target...75
Deleting a Target...76
Viewing Application System Objects...77
Creating an XML Schema...83
5. Creating and Publishing iWay Business Services...87
Understanding iWay Business Services...88
Creating iWay Business Services...88
Creating Business Services With iWay Explorer...88
Identity Propagation...97
6. Configuring the Event Adapter for SAP...99
Understanding iWay Event Functionality...100
Creating, Editing, or Deleting a Port...101
Using the Default Event Port...116
Creating, Editing, or Deleting a Channel...117
Synchronous Event Processing...129
7. Understanding SAP Events...133
Overview...134
Related Concepts and Terminology...134
Client and Server Programs...134
SAP Gateway...134
Program IDs and Load Balancing...135
Registering Your Program ID in SAPGUI...135
Testing the SAP Event Adapter...138
Application Link Enabling Configuration for the Event Adapter...140
Document Processing...140
Collected Inbound Configuration...141
Testing the SAP ALE Configuration...148
8. Configuring the Adapter in iWay Designer...151
Using the Adapter in iWay Designer...152
9. Configuring the Adapter in an iWay Environment...161
Configuring the Adapter in iWay Service Manager...162
Configuring the Adapter in Adapter Manager...165
10. Troubleshooting Guidelines...169
Identifying the Issue...170
Design Time...170
Connectivity...170
Metadata...170
RFC / BAPI...171 IDoc...171 Run Time...171 Connectivity...172 Service Scenario...172 Event Processing...172 Transactional Behavior...173 Performance Issues...173
Debugging Error Messages...174
Error Messages in iWay Explorer...175
Error Messages in SAP...177
Error Messages in JCA...178
Error Messages in iBSP...179
Adapter-Specific Error Handling...180
Gathering Information Before Calling Customer Support...182
Contacting Customer Support...184
Reader Comments...185
Preface
This documentation describes how to configure and use the iWay Transaction Adapter for CICS.
How This Manual Is Organized
This manual includes the following chapters:
Contents Chapter/Appendix
Provides an overview of the iWay Application Adapter for mySAP ERP. Describes key features and
functionality of the adapter. Introducing the iWay
Application Adapter for mySAP ERP
1
Provides a quick start guide to use the iWay Application Adapter for mySAP ERP.
Getting Started 2
Describes how to configure your SAP system for inbound (client) processing.
Configuring SAP Inbound Processing
3
Describes how to create XML schemas for SAP business objects using iWay Explorer.
Creating XML Schemas for mySAP
4
Describes how to create and publish iWay Business Services using iWay Explorer.
Creating and Publishing iWay Business Services 5
Describes how to create ports and channels to listen for SAP events using iWay Explorer.
Configuring the Event Adapter for SAP 6
Describes how to configure and test your SAP system for event processing.
Understanding SAP Events 7
Describes how the adapter can be used within an iWay Designer process flow.
Configuring the Adapter in iWay Designer
8
Contents Chapter/Appendix
Describes how the adapter can be assigned to an iWay Service Manager channel or iWay Adapter Manager listener.
Configuring the Adapter in an iWay Environment 9
Provides useful troubleshooting guidelines for the iWay Application Adapter for mySAP ERP.
Troubleshooting Guidelines 10
Documentation Conventions
The following table lists and describes the conventions that apply in this manual.
Description Convention
Denotes syntax that you must enter exactly as shown. THIS TYPEFACE or
this typeface
Represents a placeholder (or variable), a cross-reference, or an important term. It may also indicate a button, menu item, or dialog box option you can click or select.
this typeface
Indicates a default setting. underscore
Highlights a file name or command. this typeface
Indicates keys that you must press simultaneously. Key + Key
Indicates two or three choices; type one of them, not the braces. { }
Separates mutually exclusive choices in syntax. Type one of them, not the symbol.
|
Indicates that you can enter a parameter multiple times. Type only the parameter, not the ellipsis points (...).
...
Indicates that there are (or could be) intervening or additional commands.
. . .
Related Publications
To view a current listing of our publications and to place an order, visit our World Wide Web site, http://www.iwaysoftware.com. You can also contact the Publications Order Department at (800) 969-4636.
Customer Support
Do you have questions about this product?
Call Information Builders Customer Support Services (CSS) at (800) 6130 or (212) 736-6130. Customer Support Consultants are available Monday through Friday between 8:00 A.M. and 8:00 P.M. EST to address all your questions. Information Builders consultants can also give you general guidance regarding product capabilities and documentation. Be prepared to provide your six-digit site code (xxxx.xx) when you call.
You can also access support services electronically, 24 hours a day, with InfoResponse Online. InfoResponse Online is accessible through our World Wide Web site,
http://techsupport.iwaysoftware.com/. You can connect to the tracking system and known-problem database at the Information Builders support center. Registered users can open, update, and view the status of cases in the tracking system and read descriptions of reported software issues. New users can register immediately for this service. The technical support section also provides usage techniques, diagnostic tips, and answers to frequently asked questions.
To learn about the full range of available support services, ask your Information Builders representative about InfoResponse Online, or call (800) 969-INFO.
Help Us to Serve You Better
To help our consultants answer your questions effectively, be prepared to provide specifications and sample files and to answer questions about errors and problems. The following tables list the environment information our consultants require.
Platform
Operating System OS Version JVM Vendor JVM Version
The following table lists the deployment information our consultants require.
For example, JCA, Business Services Provider, iWay Service Manager
Adapter Deployment
For example, WebSphere Container
Version
Enterprise Information System (EIS) - if any EIS Release Level EIS Service Pack EIS Platform
The following table lists iWay-related information needed by our consultants. iWay Adapter
iWay Release Level iWay Patch
The following table lists the types of iWay Explorer. Specify the version (and platform, if different than listed previously) in the columns provided.
Platform Version
iWay Explorer Type Eclipse
Embedded in iWay Designer
The following table lists additional questions to help us serve you better. Error/Problem Details or Information Request/Question
Did the problem arise through a service or event?
Provide usage scenarios or summarize the application that produces the problem. When did the problem start? Can you reproduce this problem consistently? Describe the problem.
Error/Problem Details or Information Request/Question
Describe the steps to reproduce the problem. Specify the error message(s). Any change in the
application environment: software configuration, EIS/database configuration, application, and so forth? Under what circumstance does the problem not occur?
Following is a list of error/problem files that might be applicable. Input documents (XML instance, XML schema, non-XML documents) Transformation files
Error screen shots Error output files Trace files
Service Manager package to reproduce problem Custom functions and agents in use
Diagnostic Zip Transaction log
For information on tracing, see the iWay Service Manager User's Guide.
User Feedback
In an effort to produce effective documentation, the Documentation Services staff welcomes your opinions regarding this manual. Please use the Reader Comments form at the end of this manual to communicate suggestions for improving this publication or to alert us to corrections. You can also go to our Web site, http://www.iwaysoftware.com and use the Documentation Feedback form.
Thank you, in advance, for your comments.
iWay Software Training and Professional Services
Interested in training? Our Education Department offers a wide variety of training courses for iWay Software and other Information Builders products.
For information on course descriptions, locations, and dates, or to register for classes, visit our World Wide Web site, http://www.iwaysoftware.com/support/education.html, or call (800) 969-INFO to speak to an Education Representative.
Interested in technical assistance for your implementation? Our Professional Services department provides expert design, systems architecture, implementation, and project management services for all your business integration projects. For information, visit our World Wide Web site, http://www.iwaysoftware.com/support/services.html.
Introducing the iWay Application Adapter for
mySAP ERP
1
Topics: The following section provides an
overview of the iWay Application Adapter
for mySAP ERP. Features of the iWay Application Adapter for mySAP ERP
Supported Versions and Platforms Classical SAP Technologies for ABAP Integrating With SAP
Component Information for the iWay Application Adapter for mySAP ERP Web Services and Java Connector Architecture Functionality
Features of the iWay Application Adapter for mySAP ERP
The iWay Application Adapter for mySAP ERP is a remote function call adapter that provides a means to exchange real-time business data between SAP Enterprise Central Component (ECC) 5.0/6.0 systems and other application, database, or external business partner systems. The adapter enables external applications for inbound and outbound processing with SAP.
The adapter uses XML messages to enable non-SAP applications to communicate and exchange transactions with SAP using one of the following two methods.
Service Adapter. Applications use this capability when they must initiate an SAP business event.
Event Adapter. Applications use this capability if they require access to SAP data only when an SAP business event occurs.
The iWay Application Adapter for mySAP ERP provides: Support for bidirectional message interactions.
SAP object repository metadata browser support to build XML schemas and Web services to handle adapter requests or event data.
Support for Remote Function Calls (RFC), Business Application Programming Interfaces (BAPI), and Intermediate Documents (IDoc) interfaces to SAP.
Supported Versions and Platforms
The following platforms are supported by the iWay Application Adapter for mySAP ERP: Windows
Linux/Solaris/OS400 HP-UX
AIX
The iWay Application Adapter for mySAP ERP uses the SAP Java Connector (JCo) and the SAP RFC library to communicate with SAP ABAP server targets. To the extent these interfaces and their associated object types are supported, the adapter can function within the established protocols for the following object types:
SAP ALE Intermediate Document (IDOC) Remote Function Call (RFC)
Business API (BAPI)
Other connection methods and interface types are not supported. The lowest application server release supported by the iWay Application Adapter for mySAP ERP is 4.6C. For more information about specific applications or servers, please consult your iWay Software Customer Service Representative.
SAP JCo Version 2.x is required for the iWay Application Adapter for mySAP ERP. The SAP JCo files are downloaded from the SAP Service Marketplace. A valid ID is required to access the SAP service marketplace. Please contact your SAP administrator for assistance. For the current release status of the SAP Java Connector (JCo), refer to SAP Note #549268 in the SAP Service Marketplace.
SAP JCo Version 3.0 is not supported for this release of the iWay Application Adapter for mySAP ERP.
Note: SAP JCo files must match the JVM mode (32- or 64-bit). Strictly mixed mode JVM is not supported. It is possible to run the entire 32-bit stack on a 64-bit machine, but 64-bit can only be run on 64-bit machine types.
For more information on installing the mySAP ERP adapter, see Getting Started on page 23and the iWay Installation and Configuration Guide.
Classical SAP Technologies for ABAP
The iWay Application Adapter for mySAP ERP is designed to provide standard access to SAP interfaces such as Remote Function Call (RFC) modules, BAPIs (Business Application Programming Interfaces), and IDocs (Intermediate Documents), that are used to support existing business processes.
The adapter only supports Enterprise Central Components (ECC) that are accessed by classical SAP technologies. If you require support for additional SAP functionality and components, please contact your iWay Software Sales Representative.
These business components and methods are available to the adapter as requests of SAP and to the event adapter when SAP invokes its remote requests and work in the following ways:
Business Application Programming Interfaces (BAPIs) are interfaces within the business framework that are used to link SAP components to one another or to third-party components. BAPIs are called synchronously and return information.
Remote Function Call (RFC) Modules are SAP application interfaces that enable clients to invoke SAP technologies and receive responses.
Note: Depending on the release or service pack installed, certain RFCs may not exist in your particular SAP system. Therefore, the examples included in this documentation may not be relevant to your system. If this is the case, you should use the examples as a general reference for adapter functionality and choose an RFC that exists within your SAP application environment.
As described in SAP Release Note 109533, SAP Function Modules (RFCs) can be delivered with different release statuses. SAP supports only RFCs that are awarded with the Released for Customer status. There is no claim to the release independencies of the interfaces and the continued existence/functionality of the modules. For more information on the status of a specific function module, consult the SAP Service Marketplace.
Intermediate Documents (IDocs) are the "logical messages" that correspond to different business processes. They enable different application systems to be linked by a message-based interface. The IDoc type indicates the SAP format to use to transfer the data for a business transaction. An IDoc is a real business process in the form of an IDoc type that can transfer several message types. An IDoc type is described by the following components:
Control records. A control record contains data that identifies the sender, the receiver, and the IDoc structure. An IDoc contains one control record.
Data records. A data record consists of a fixed administration part and a data part (segment). The number and format of the segments can be different for each IDoc type. Status records. A status record describes the processing stages through which an IDoc passes.
The following scenario is an example of IDoc functionality and its components:
Purchase order number 4711 was sent to a vendor as IDoc number 0815. IDoc number 0815 is formatted in IDoc type ORDERS01 and has the status records "created" and "sent." The purchase order corresponds to the "logical" message ORDERS.
Integrating With SAP
You can use the iWay Application Adapter for mySAP ERP to invoke an SAP business process, for example, add/update account, or you can use the adapter as part of an integration effort to connect SAP and non-SAP systems.
All functions are processed synchronously, but all content in ALE IDocs is asynchronous. In service mode, the iWay Application Adapter for mySAP ERP can send requests to SAP using the BAPI, RFC, or ALE interfaces.
The adapter quickly and easily integrates your SAP IDocs, RFCs, and BAPIs with mission critical SAP system applications and other enterprise applications. The benefits of the adapter include:
Elimination of the requirement for custom coding. Consistent data representation.
Provides a standard XML representation of event data and request/response documents for SAP.
The developer is freed from the specific details of the SAP interface (BAPI, RFC, IDoc) and the specific configuration details of the target SAP system.
Adherence to SAP ABAP serialization rules and SAP Interface Repository standards published by SAP AG.
During event processing, the adapter receives RFCs and IDocs directly from SAP. The SAP system can be configured to send an IDoc or RFC to a logical system when a certain event occurs, in this case to the adapter. The output sent by SAP can be in any of the following forms:
An RFC request, for example, RFC_SYSTEM_INFO.
A BAPI request, for example, BAPI_COMPANYCODE_GETLIST. An IDoc.
Component Information for the iWay Application Adapter for mySAP
ERP
In this section:
Component Information Roadmap iWay Service Manager
iWay Explorer
iWay Business Services Provider
Enterprise Connector for J2EE Connector Architecture (JCA)
The iWay Application Adapter for mySAP ERP works in conjunction with one of the following components:
iWay Service Manager
iWay Business Services Provider (iBSP)
Enterprise Connector for J2EE™ Connector Architecture (JCA)
When hosted in an iWay environment, the adapter is configured through iWay Service Manager and iWay Explorer. iWay Explorer is used to configure adapter connections, create Web services, and configure event capabilities.
When the adapter is hosted in a third party application server environment, iWay Explorer (used to configure SAP connections, create Web services, and configure event capabilities) can be configured to work in a Web services environment in conjunction with iBSP or JCA. When working in a JCA environment, the connector uses the Common Client Interface (CCI) to provide fast integration services using adapters instead of using Web services.
Component Information Roadmap
The following table lists the deployment component and the location of component information for the iWay Application Adapter for mySAP ERP.
For more information, see Deployed Component
Chapter 9 of this guide
iWay Service Manager User's Guide
iWay Service Manager
Chapters 4, 5, 6, and 7 of this guide
iWay Service Manager User's Guide
iWay Explorer
iWay Installation and Configuration Guide
iWay Business Services Provider (iBSP)
iWay Installation and Configuration Guide
iWay Enterprise Connector for J2EE Connector Architecture (JCA)
iWay Service Manager
iWay Service Manager is the heart of the Universal Adapter Framework and is an open transport service bus. Service Manager uses graphical tools to create sophisticated integration services without writing custom integration code by:
Creating metadata from target applications. Transforming and mapping interfaces. Managing stateless processes.
Its capability to manage complex adapter interactions makes it ideally suited to be the foundation of a service-oriented architecture.
iWay Explorer
iWay Explorer uses a tree metaphor to introspect the SAP system metadata. The explorer enables you to create XML schemas and Web services for the associated object. In addition, you can create ports and channels to listen for events in SAP. External applications that access SAP through the iWay Application Adapter for mySAP ERP use either XML schemas or Web services to pass data between the external application and the adapter.
iWay Business Services Provider
The iWay Business Services Provider (iBSP) exposes—as Web services—enterprise assets that are accessible from adapters regardless of the programming language or the particular operating system.
iBSP simplifies the creation and execution of Web services when running: Custom and legacy applications.
Database queries and stored procedures. Packaged applications.
Terminal emulation and screen-based systems. Transactional systems.
Coupled with a platform and language independent messaging protocol called SOAP (Simple Object Access Protocol), XML enables application development and integration by assembling previously built components from multiple Web services.
Enterprise Connector for J2EE Connector Architecture (JCA)
The Enterprise Connector for J2EE Connector Architecture (JCA) enables developers of JCA-compliant applications to deploy adapters as JCA resources. The connector is supported on J2EE-compliant application servers, such as your application server.
The Connector for JCA is distributed as a standard Resource Adapter Archive (RAR) for deployment to the application server. Thus, the connector can be used in systems that are non-compliant, although services such as pooled connections are not available.
Web Services and Java Connector Architecture Functionality
In this section: Web Services
Java Connector Architecture
The following topics describe how the iWay Application Adapter for mySAP ERP can incorporate Web services and Java Connector Architecture technology.
Web Services
Web services enable SAP calls to be made across the Internet or an intranet, using specialized versions of the XML language that allow a developer to specify the parameters, connections methods, and remote calls and store them for reference in a repository. At run time, a person, an interface, or another function, can read this repository and automatically invoke the service. Web services currently do not have industry standards for transactional behavior. Web services are useful when your function calls must be made across firewall boundaries. Using Web services, you can use functions provided by external providers, assuming you know the function interface.
Web Services Example:
A Web service exposes the "cup" interface, which provides a teacup. The Acme Company exposes the "tea" Web service, which provides a brown liquid when the correct parameter "money" is provided. A cup of tea can be received by invoking the "tea" Web service and passing the "money" parameter. Additional components are not required to receive tea using the "tea" Web service.
Java Connector Architecture
Java Connector Architecture (JCA) provides a reusable component model to build and deploy multi-tier applications that are platform and vendor independent. JCA acts as a type of envelope or "container" that enables the adapter to run inside the application server and connect to SAP and immediately return the results. JCA is useful when your SAP system resides within a local intranet or is accessed directly. JCA implements JAVA Connection and Transaction models. JCA requires a resource adapter to be physically deployed on the host application server to access the remote EIS system.
For more information on event capabilities of the JCA connectors, see Configuring the Event Adapter for SAP on page 99. For more information on installing and deploying both connectors, see the iWay Installation and Configuration Guide.
Using combinations of JCA and Web services is possible. For example, a JCA application can be invoked by a Web service or a Web service may be implemented inside a JCA container. The standards and protocols are still evolving.
JCA Example
An application server, "Table" implements the "tea" container, which contains "tea, gas heat, water, and cup". A JCA container can be deployed that contains tea in the "Table" application server. If any of the elements of the "tea" container are missing, for example, "gas heat," then no tea is produced. The container must physically possess the "tea, gas heat, water, and cup" components to receive the tea.
Getting Started
2
Topics: This section provides a quick start guide
to use the iWay Application Adapter for
mySAP ERP. Installing the iWay Application Adapter for mySAP ERP
Installing the SAP Java Connector (SAP JCo)
Verifying the SAP Java Connector (SAP JCo)
Identifying mySAP Logon Parameters Verifying Connections to mySAP
Installing the iWay Application Adapter for mySAP ERP
How to:
Install the iWay Application Adapter for mySAP ERP
To install the iWay Application Adapter for mySAP ERP, you must select it during the iWay 6.0.1 installation. This section provides a quick walk through of the installation process. For more detailed information, see the iWay Installation and Configuration documentation.
How to Install the iWay Application Adapter for mySAP ERP
Procedure:
To install the iWay Application Adapter for mySAP ERP:
1. Start the iWay 6.0.1 installation by executing the iway60.exe file. The iWay 6.01 installation wizard opens.
2. Click Next.
The License Agreement pane is displayed.
3. Review the license agreement and click Yes to continue. The Customer Information pane is displayed.
4. Enter your user name, company name, and site code.
5. Select the user group that will have access to the installed product. Options include: Anyone who uses this computer (all users)
Only for me (Admin) 6. Click Next.
The Setup Type pane is displayed. 7. Click Next.
The Choose Destination Location pane is displayed.
8. Select a different destination folder on your file system for iWay 6.0.1 or accept the default (C:\Program Files\iway60\).
9. Click Next.
The Adapter Selection pane is displayed.
Important: By default, only the Technology Adapters group is selected. You must expand the ERP Adapters group and select MYSAP from the list of adapters to install the iWay Application Adapter for mySAP ERP.
10. Verify that MYSAP is selected in the ERP Adapters group.
Note: iWay Application System Adapter for SAP is included for SAP R/3 legacy support only (existing usage). All new installations using SAP are required to use the iWay Application System Adapter for MySAP, which provides support for R/3 4.6C and 4.7, and SAP ERP ECC 5 &6. MySAP and SAP targets have incompatible formats and cannot be interchanged. All targets and schemas must be recreated, since there is no migration utility between these adapters.
11. Click Next and finish the remaining steps of the iWay 6.0.1 installation according to your requirements.
For more detailed information, see the iWay Installation and Configuration documentation.
Installing the SAP Java Connector (SAP JCo)
In this section:
SAP JCo files by Platform
Installing SAP JCo on Windows Platforms Installing SAP JCo on UNIX Platforms
The SAP Java Connector (SAPJCo) is a component provided by SAP that enables the development of SAP-compatible components and applications in Java. SAP JCo is required by the iWay Application Adapter for mySAP ERP to support communication with the SAP Server in both directions: inbound calls (Java calls ABAP) and outbound calls (ABAP calls Java). This section describes how to install SAPJCo.
Note: For the current release status of the SAP Java Connector, refer to SAP Note #549268 in the SAP Service Marketplace.
A valid SAP service ID is required to access this site. To download the current version, follow the information provided on the SAP Java Connector (SAP JCo) overview page. For more information, contact your SAP BASIS Administrator.
Using the appropriate archive tool, open the archive containing the SAP Java Connector (SAP JCo) and extract the run-time files.
SAP JCo files by Platform
Since the SAP JCo library files vary by operating system, the following section provides a useful reference that lists the required files by platform.
Windows sapjco.jar sapjcorfc.dll librfc32.dll Linux/Solaris/OS400 sapjco.jar libsapjcorfc.so librfccm.so HP-UX sapjco.jar librfccm.sl libsapjcorfc.sl AIX sapjco.jar librfccm.so libsapjcorfc.so
Installing SAP JCo on Windows Platforms
On Windows, the librfc32.dll must be placed in the Windows\System32 directory. The sapjco.jar and sapjcorfc.dll files must be placed in the following directory:
<iWaySMHome>\lib
where:
<iWaySMHome>
Is the directory where iWay Service Manager is installed.
Installing SAP JCo on UNIX Platforms
On UNIX platforms, the directory in which the shared library files are located must be added to the shared library variable applicable to the operating system. The following is a list of platforms and associated variables:
AIX
LIBPATH HP-UX
SHLIB_PATH
Other UNIX Platforms LD_LIBRARY_PATH
Verifying the SAP Java Connector (SAP JCo)
In this section:
Verifying SAP JCo on Windows Platforms Verifying SAP JCo on UNIX Platforms
Once you have installed the SAP Java Connector (SAP JCo), as a best practice, you can verify the connector to make sure it is installed correctly and that all the required SAP JCo library files are available.
Verifying SAP JCo on Windows Platforms
How to:
Verify SAP JCo on Windows
This section describes how to verify SAP JCo on Windows platforms.
How to Verify SAP JCo on Windows
Procedure:
Perform the following steps to verify SAP JCo on Windows: 1. Navigate to the following directory:
<iWaySMHome>\lib
where:
<iWaySMHome>
Is the directory where iWay Service Manager is installed
2. Right-click the sapjco.jar file, select Open With from the context menu, and click Java 2
The SAP Java Connector (JCo) dialog box opens, as shown in the following image.
All the required information that pertains to the SAP Java Connector on your Windows platform is provided.
3. Once you have reviewed the SAP Java Connector files, click Close.
Verifying SAP JCo on UNIX Platforms
How to:
Verify SAP JCo on UNIX
This section describes how to verify SAP JCo on UNIX platforms.
How to Verify SAP JCo on UNIX
Procedure:
Perform the following steps to verify SAP JCo on UNIX: 1. Navigate to a UNIX command prompt.
2. Type the following command:
$ java -jar sapjco.jar -stdout
3. Press Enter on your keyboard.
All the required information that pertains to the SAP Java Connector on your UNIX platform is provided, as shown in the following example.
---| SAP Java Connector (JCo) ---| | Copyright (c) 2000-2005 SAP AG. All rights reserved.| | Version Information | ---Java Runtime:
Operating System: SunOS 5.7 for sparc
Java VM: 1.4.0-beta3 Sun Microsystems Inc. Java Codepage: ASCII
Versions: JCo API: 2.1.8 (2006-12-11) JCo middleware: 2.1.8 (2006-12-11) JCo library: 2.1.8 (2006-12-11) RFC library: 640.0.165 Paths:
JCo classes: /u4/fpgjpr/iWay60/lib/sapjco.jar JCo library: /u4/fpgjpr/iWay60/lib/libsapjcorfc.so RFC library: System-defined path
---| Manifest ---| ---Manifest-Version: 1.0
Created-By: 1.3.1_18-b01 (Sun Microsystems Inc.) Specification-Title: SAP Java Connector
Specification-Version: 2.1.8
Specification-Vendor: SAP AG, Walldorf Implementation-Title: com.sap.mw.jco
Implementation-Version: 20070108 2139 [2.1.8 (2006-12-11)] Implementation-Vendor-Id: com.sap
Implementation-Vendor: SAP AG, Walldorf Main-Class: com.sap.mw.jco.About
---$
4. Review the information for the SAP Java Connector on your UNIX platform.
Identifying mySAP Logon Parameters
In this section: User Parameters
System Settings (Application Server) Parameters System Settings (Message Server) Parameters Connection Pool Parameters
SAP Gateway Parameters ALE Parameters
Global Processing Parameters SNC Parameters
This section allows you to identify mySAP logon parameters, which are used to configure a connection to mySAP using the iWay Application Adapter for mySAP ERP. This information can be used as a reference.
User Parameters
The following table lists and describes User parameters.
Comment Example
Description Parameter
In commercial, organizational, and technical terms, a self-contained unit in an SAP system with separate master records and its own set of tables. A client can, for example, be a corporate group. 800
Identifies the SAP client.
Client
User type for dialog-free communication between systems.
"abc123" Sap login id.
User
A protected word or string of characters that identifies or authenticates a user for access to an SAP system. "xyz999"
Confidential authentication information. Password
When you log onto the SAP system, you must select a valid installed language. "E"
Language Language
In the case where two systems with different code pages exchange data with each other, and where these do not use Unicode code pages, the code page conversion is performed on the receiver system side. A valid sap code
page (normally, do not set this parameter as conversions are done automatically). If you select an unknown codepage, the RFC terminates with the error SYSTEM_FAILURE. CodePage
Comment Example
Description Parameter
Password - use the value in the supplied field.
SSO - specify the user to be
$MYSAPSSO2$ and pass the
base64 encoded ticket as the password parameter.
X509 - specify the user to be
$X509CERT$ and pass the base64 encoded certificate as the password parameter. Note: The user and password parameters that are mentioned here refer to the User and Password parameter fields in iWay Explorer. Selection see next column. How the connection is validated. Authentication Mode
System Settings (Application Server) Parameters
The following table lists and describes System Settings (Application Server) parameters.
Comment Example
Description Parameter
Application programs in an R/3 System are run on application servers. To obtain meta data information, a connection to a single application server is required. iwjpsap Connects to an ABAP application server. Application Server
An application server may have different system numbers. Use the one provided by your administrator. 00 Identifies a unique instance on the application server. System Number
System Settings (Message Server) Parameters
The following table lists and describes System Settings (Message Server) parameters.
Comment Example
Description Parameter
For load balancing purposes, application servers from one SAP system are usually configured in logon groups, where each group serves a particular kind of user. The message server is
responsible for communication between the application servers. It passes requests from one application server to another within the system. It also contains information about application server groups and the current load balancing within them. It uses this information to choose an appropriate server when a user logs onto the system. iwjpsap Connects to an ABAP application server. Message Server
Symbolic SAP system name used to identify the system.
P47 Identifies a
unique instance. R/3 Name
Logon group that the userid belongs with.
Indentifies the logon group. Server
Group
Connection Pool Parameters
The following table lists and describes Connection Pool parameters.
Comment Example
Description Parameter
A pool is a set of client-connections to a certain
destination with the same logon data. The pool automatically creates new connections to the specified remote system or returns an already existing one. The reusing of existing
connections can increase the performance of your application by avoiding logging on to the remote server. "foo" A name for a unique pool of client connections. Connection pool
Sets the maximum number of connections that can be allocated from the pool.
10 Maximum number of connections for the pool. Connection Pool Size
Connections that have not been used for at least the connection timeout interval will be closed. 5 Maximum time to keep open a free connection (in minutes). Connection Timeout
Sets the maximum time to wait in a connection request for a free connection. If the pool is
exhausted, and there is still no connection available after the specified time, a JCO.Exception with the key
JCO_ERROR_RESOURCE will be thrown. The default value is 30 seconds. 30 (seconds) Maximum wait for a free connection. Connection Wait Time
SAP Gateway Parameters
The following table lists and describes SAP Gateway parameters.
Comment Example
Description Parameter
The SAP Gateway carries out CPI-C services within the SAP world, which are based on TCP/IP. These services enable SAP Systems and external programs to communicate with one another. "isdsrv2"
Enter the name of a SAP Gateway server. SAP
GateWay Host
Service name on the gateway host.
Sapgw00 Enter the service
name (usually a compound of the service name and system number). SAP Gateway Service
Unique identifier for your
communication session specified by your system administrator. The value entered in this field must match the one exposed on the gateway. "S1PROG" A program identifier that has been specified on the SAP Gateway server (case sensitive). Program ID
ALE Parameters
The following table lists and describes ALE parameters.
Comment Example
Description Parameter
Version "3" (Release 4.0 onwards) should be selected in the port description for all R/3 partner systems with Release 4.0 or higher.
Version "2" (release 3.0/3.1) must be set in the port description for all R/3 partner systems with releases lower than 4.0. 3 Specifies the ALE version of the target system. EDI Version
You can assign segment
definitions from previous releases to an IDoc type in the current release. This may be necessary if, for example, the partner is using an older release which supports your current IDoc type but not your current segment definitions. Blank or a specific SAP release version , e.g. "46C" Specifies the version in which the IDOC definition was released. IDOC Release
IDOCDOREL uses the information in the IDOC header.
SAP release gets the information from the user account logon. USERINPUT uses the IDOC release field above to get the information.
Selection see next column.
Specifies where the adapter will get the release information. IDOC
Release Provider
Global Processing Parameters
The following table lists and describes Global Processing parameters.
Comment Example
Description Parameter
Creates error document writes an
exception document with the full error text to the output
destination.
Throws exception creates a java
exception, this may or may not display the full error text depending on the underlying component error.
Selection see next column. Specifies the error handling method of the adapter. Error Handling Off - default
Sends Commit Request to Application Server at the end of the document. If there is a commit error it will not be reflected back (Optimal performance).
On (checked) - waits for a full database server commit at the end of the document before returning. Commit errors are reflected back to the adapter level (slowest performance).
See your SAP DB admin for your site's recommended setting. Selection see next
column. Specifies the commit behavior. Commit with Wait
Off default - only hard errors are written to the trace file
(dev_rfc.trc) in append mode. ON - individual rfc*.trc and JCO*.trc are written for each request. Useful in finding errors, not recommended in a productive system.
Selection see next column. Turns on the SAP Java connectors trace behavior. TRACE
SNC Parameters
The following table lists and describes SNC parameters.
Comment Example Description Parameter Required. 1 (on) Flag for activating SNC. SNC mode
The default is the system-defined library as defined in the
environment variable SNC_LIB. C:\SAPJ2EE_Engine\SAPCryptolib\sapcrypto.dll
Specifies the path and file name of the external library. SNC library path 1: Authentication only 2: Integrity protection
3: Privacy protection (default) 8: Use the value from
snc/data_protection/use on the application server
9: Use the value from
snc/data_protection/max on the application server
Default value = 3 Selection see next
column Specifies the level of protection to use for the connection. SNC level
Although this parameter is optional, we do recommend setting it to make sure that the correct SNC name is used for the connection. p:CN=SAPJ2EE O=MyCompany, C=US Specifies SNC name. SNC name
You can find the application server's SNC name in the profile parameter snc/identity/as. p:CN=ABC, O=MyCompany C=US Specifies the application server's SNC name. SNC Partner
Verifying Connections to mySAP
In this section:
Verifying a mySAP Client Connection Verifying a mySAP Server Connection
This section allows you to verify a client and server connection to mySAP to ensure that the iWay Application Adapter for mySAP ERP is installed and configured correctly.
Verifying a mySAP Client Connection
How to:
Verify a mySAP Client Connection
This section describes how to verify a mySAP client connection.
How to Verify a mySAP Client Connection
Procedure:
To verify a mySAP client connection:
1. Create a mySAP target using iWay Explorer.
For more information on creating and connecting to mySAP targets, see Creating XML Schemas for mySAP on page 59.
2. Connect to the mySAP target. 3. Expand the mySAPTarget node.
4. Expand the Business Object Repository node.
5. Expand Financial Accounting followed by CompanyCode. 6. Select the GetList method.
7. In the right pane, move the pointer over Operations to view the context menu.
8. Select Test Run.
The Test Run dialog box opens.
Note: You must have authorization for this component in SAP to proceed. The current valid objects are:
Authorization Object:
S_RFC
RFC_TYPE = FUGR
RFC_NAME = 0002 ACTVT = 16 Authorization Object: S_TABU_DIS DICBERCLS = V_T011 ACTIVITY = 03
If the data is present on the system, a list of valid company codes is displayed.
Verifying a mySAP Server Connection
To verify a mySAP server connection, have the RFC administrator run the Test Connection function in the RFC program administration transaction.
Configuring SAP Inbound Processing
3
Topics: The following section describes how to
configure your SAP system for inbound
(client) processing. Overview
Configuring a Logical System Configuring a Distribution Model Defining a Partner Profile
Overview
During inbound processing, IDocs are transferred to the interface and stored in the R/3 System. The document data is generated in a second step, also in the course of a workflow. The upstream system transfers an IDoc to the IDoc interface through the R/3 System port. For this reason, you are not required to specify a port in the inbound partner profiles. The IDoc interface must only "recognize" the upstream system as a port. A port definition, which provides a unique ID for the upstream system, must be available for the port. The technical parameters of this port definition can (and usually are) overwritten by the upstream system. The IDoc is "accepted," that is, saved in the database, if the upstream system is recognized. If your partner is defined with the corresponding message in your partner profiles, the IDoc is then processed further. This is done independently in a second step. This ensures that the external system can receive the data quickly and reliably (automatically).SAP Remote Function calls require no system setup other than the Connection Target Parameters. If you do not intend to send IDocs to the SAP system, you may skip this chapter.
In inbound IDoc processing, the adapter reads an XML document and creates an SAP Standard format IDoc. The adapter can optionally transform incoming data into the standard format through XML transformation or SAP ALE transformation. After assembled as an IDoc, the file is sent to SAP for inbound processing. Multiple IDocs can also be assembled into a larger document for efficient processing. For more information, see the SAP documentation. ALE IDocs used for transmission of Electronic Data Interchange (EDI) messages require information about the intended target and method of transmission stored on the SAP application server.
An IDoc consists of a Header that contains sender, processing type, receiver and other information, and multiple data segments, which contain the information to be processed. To store the parameters for processing of the IDoc messages, SAP requires a "logical system" entry for each transmission system. The Logical System stores type information about the Partner and the kind of messages expected from the partner.
The Partner Profile defines the kind of message and the type of SAP function called to process that particular IDoc in an application. SAP also requires a filtering model, whether or not it is used for a particular message, called a Distribution Model that defines a message type and applies optional segment filters. After these are established, Inbound ALE/IDoc processing can begin.
The Control Section or reference structure file EDI_DC40 (defined in SAP ERP), must be completed and contains all the identifying information about the IDoc. The assembled header and data records are sent to SAP by the adapter. SAP does not require an incoming port to be specified. It takes the incoming RFC stream and assigns a port designation. In the Partner Profile, a function module must be identified to process the IDoc in the ERP system.
Usually, IDocs are written directly to the database and slowly read by the application (for example, Purchasing for Purchase Orders). This can take time depending on the type of data and the application. The adapter can "post to the database and return" or "post and wait." This is defined in the Partner Profile on the host system. In either case, you may send a status IDoc message to obtain the status of your IDoc or use appropriate transaction codes in SAP to view the IDocs online.
You must perform the following steps to configure SAP for inbound IDoc processing: 1. Configure a logical system.
2. Configure a distribution model. 3. Define an inbound partner profile.
Configuring a Logical System
How to:
Configure a Logical System
In a distributed environment, each participating system must have a unique ID to avoid confusion. In SAP, the name of the logical system is used as the unique ID. This name is assigned explicitly to one client in an SAP system.
How to Configure a Logical System
Procedure:
The following image shows the /nsale transaction in the field under the menu bar.
To configure a logical system: 1. Execute the sale transaction.
The Display IMG window opens as shown in the following image.
a. Expand Sending and Receiving Systems and then, Logical Systems. b. Select Define Logical System.
2. Click the IMG - Activity icon.
An information window appears that informs you that the table is cross-client as shown in the following image.
3. To continue, click the checkmark icon.
The Change View "Logical Systems" window opens with a list of logical systems and their names as shown in the following image.
4. Click the New entries button.
The New Entries window opens where you can type information for the logical system and its corresponding name as shown in the following image.
a. In the Log.System column, type the Logical System, for example, IWAY_IN. b. In the Name column, type a corresponding description.
5. Click Save.
The Prompt for Workbench request window opens as shown in the following image. It includes fields for View maintenance and Request as well as several buttons.
6. Click the Create Request icon.
The Create Request window opens as shown in the following image. It includes fields that are already populated (such as Owner, Status, Last Changed, Source client, and so forth), empty fields (such as Request and Project) in which to specify information about your request, and a Tasks list.
a. In the Request field, type a name.
b. In the Short description field, type a brief description of your request. 7. Click Save.
The logical system you configured, for example, IWAY_IN, appears in the list as shown in the following image.
Configuring a Distribution Model
How to:
Configure a Distribution Model
A distribution model is used to describe the ALE message flow between logical systems. Business objects are distributed to connected recipients according to a unique distribution model that can contain rules of varying complexity depending on the type of business objects involved.
How to Configure a Distribution Model
Procedure:
The following image shows the /nbd64 transaction in the field under the menu bar.
To configure a distribution model: 1. Execute the /bd64 transaction.
The Display Distribution Model window opens and displays a list of available distribution models and their descriptions as shown in the following image.
2. In the menu bar, click Distribution model.
The Distribution model menu opens as shown in the following image.
3. Select Switch processing mode.
The Display Distribution Model window switches to the Change Distribution Model. window as shown in the following image.
4. Click the Create model view button.
The Create Model View window opens and includes fields for the name of your distribution model and for Start and End dates as shown in the following image.
a. In the Short text field, type a model view name, for example, iway ale inbound. b. In the Technical name filed, type a technical name, for example, ziwayale, which
also serves as a description.
5. To enter the information, click the checkmark icon.
You are returned to the main Change Distribution Model window.
The distribution model you configured is now added to the list as shown in the following image.
6. Click the Add message type button.
The Add Message Type window opens and includes fields where you can name and specify your message type.
a. In the Sender field, type the logical system you configured, for example, IWAY_IN.
b. In the Receiver field, type the logical system you configured, for example, IWAY_OUT. To browse from a list of logical systems, you can click the icon to the right of each field.
c. In the Message type field, type the message type to use, for example, MATMAS. To browse from a list of available message types, you can click the icon to the right of the field.
7. To enter the information, click the checkmark.
You are returned to the main Change Distribution Model window. 8. Click Save.
Defining a Partner Profile
How to:
Define a Partner Profile
Partner profiles are a requirement for data exchange. You define who can exchange messages with the SAP system using a specified port.
How to Define a Partner Profile
Procedure:
The following image shows the /nwe20 transaction in the field under the menu bar.
To define a partner profile for a specific IDoc: 1. Execute the we20 transaction.
The Partner profiles window opens and displays two panes with information about the logical system as shown in the following image.
a. If no Partner profile currently exists, click the Create icon on the tool bar or press
F5.
b. Click Save once you have created your Partner profile.
2. In the left pane, expand Partner type LS and select the logical system you configured from the list, for example, IWAY_IN.
The right pane displays the details of the expanded folder including the logical system and type, language, and so forth, as shown in the following image.
Note: The Partn.number field refers to the name of the logical system.
3. Click Save.
4. From the Inbound parameters table in the lower right, click the Create inbound parameter icon.
The Partner profiles: Inbound parameters window opens as shown in the following image.
a. In the Message type field, type the message type to use, for example, MATMAS. To browse from a list of available message types, you can click the icon to the right of the field.
The Inbound options tab is selected by default.
b. In the Process code field, enter the process code you want to use, for example, MATM.
To browse from a list of available process codes, you can click the icon to the right of the field.
c. In the Processing by function module area, select one of the following options: Trigger by background program. In this case, the iWay Application Adapter for mySAP ERP writes IDocs to the SAP database, which are processed immediately. Trigger immediately. In this case, the iWay Application Adapter for mySAP ERP waits for the SAP system to process IDocs. This can take from one to fifteen minutes.
5. Click Save.
Creating XML Schemas for mySAP
4
Topics: The following section describes how to
create XML schemas for mySAP business
objects using iWay Explorer. Overview The functionality of iWay Explorer is
standard for any deployment type. This section uses the Java™ servlet
implementation of iWay Explorer to provide examples.
Starting iWay Explorer (Servlet) Establishing a Target for mySAP Viewing Application System Objects Creating an XML Schema
Overview
The iWay Application Adapter for mySAP ERP enables the processing of mySAP BAPIs, RFCs, and IDocs.
External applications that access mySAP through the adapter use either XML schemas or Web services to pass data between the external application and the adapter. You can use iWay Explorer to create the required XML schemas and Web services.
mySAP must be installed, configured, and available for client access. iWay Explorer need not reside on the same system as the application system being accessed, but network access is required.
Starting iWay Explorer (Servlet)
How to:
Start iWay Explorer
The following procedure describes how to start iWay Explorer (Servlet).
How to Start iWay Explorer
Procedure:
To start iWay Explorer:
1. Enter the following URL in your browser window:
http://hostname:port/iwae/index.html
where:
hostname
Is the name of the machine where your application server is running.
port
Is the HTTP port for the application server.
After you start iWay Explorer, the following Welcome window opens, showing the iWay Adapters, iWay Events, and iWay Business Services tabs. The iWay Adapters node is highlighted in the left pane.
The Available Hosts drop-down menu in the upper right lists the iWay Connector for JCA or Servlet iBSE instance you can access.
2. For more information on adding instances, see the iWay Installation and Configuration
Guide.
You are now ready to create new targets for mySAP.
Establishing a Target for mySAP
In this section: Creating a New Target Connecting to a Target Disconnecting From a Target Modifying a Target
Deleting a Target
To browse mySAP business objects, you must create a target for the system you intend to use. The target serves as your connection point and is automatically saved after you create it. You must establish a connection to this system every time you start iWay Explorer or after you disconnect from the system.
A list of supported application systems appears in the left pane of iWay Explorer. The list is based on the adapters that you installed and have licenses to use.
Creating a New Target
How to:
Create a New Target
To connect to an mySAP system, you must define a new target. The target holds your logon parameters for the mySAP system.
How to Create a New Target
Procedure:
The following image shows a window with a navigation pane on the left that lists supported adapters. The right pane displays information about a selected adapter.
To create a new target:
1. In the left pane, click the MySAP node.
Descriptive information (for example, title and product version) about the iWay Application Adapter for mySAP ERP appears in the right pane.
2. In the right pane, move the pointer over Operations.
The Define a new target menu option appears as well as title and product version information for the adapter in the right pane as shown in the following image.
3. Select Define a new target.
The Add a new MYSAP target pane opens on the right as shown in the following image.
a. In the Target Name field, type a name for the target, for example, mySAPTarget.
b. In the Target Description field, type a brief description (optional).
c. From the Target Type drop-down list, select the type of target to connect to. The default value is Application Server.
4. Click Next.
The Set connection info pane opens on the right. The following tabs are available: User, System, Advanced, and Security. The User tab is active as shown in the following image.
The User (required) tab enables you to provide authentication information for the mySAP system to which you are connecting.
Note: For systems based on 6.40 UNICODE, all parameter values are case sensitive. As a result, the values you specify using iWay Explorer must match those that have been configured on your system. This also applies to user names and passwords.
a. In the Client field, type the client number defined for the mySAP application for client communications.
b. In the User field, type a valid user ID for the mySAP application. c. In the Password field, type a valid password for the mySAP application. d. In the Language field type a language key.
EN (English) is the default.
e. In the Codepage field, type a character code page value.
f. From the Authentication mode drop-down list, select Password, Logon ticket (SSO2), or Logon ticket (X509).
Secure Network Communications (SNC) provides protection for the communication links between the distributed components of an ERP System. Using SNC, mySAP ERP can support products that adhere to the GSS-API Version 2 standard. SNC supports application level (end-to-end security), Smartcard authentication, and Single Sign-On (SSO).
Note: Depending on the mySAP system release, logging on using SSO or X.509 certificates is supported.
For SSO, specify the user to be $MYSAPSSO2$ and pass the base64 encoded ticket as the passwd parameter.
For X509, specify the user to be $X509CERT$ and pass the base64 encoded certificate as the passwd parameter.
For more information, see your mySAP system documentation.
5. Click the System tab.
The System tab becomes available as shown in the following image.
The System (required) tab enables you to provide the application server name, system number, and connection pooling information for the mySAP system to which you are connecting.
Note: The mySAP connection parameters are consistent with those found in your mySAP system. For more information on parameter values that are specific to your mySAP configuration, consult your mySAP system administrator.
a. In the Application Server field, type the host name or IP address for the computer that is hosting the mySAP application.
b. In the System Number field, type the system number defined to mySAP for client communications.
c. In the Connection pool name field, enter the name of your mySAP connection pool. A default value (p1) is already provided.
d. In the Connection pool size field, specify the number of client connections in a pool you want to make available to mySAP for Web service calls. A default connection pool size of 2 is available by default.
Note: A value of 1 does not create a connection pool. Instead, a single mySAP connection with sequential processing is shared. A pooled connection invokes multiple connections to SAP with parallel processing.
If you are using iWay Explorer to create Web services, the connection pool size value is used by your Web service during runtime. As a result, ensure that the connection pool size is sufficient for your purposes.
e. In the Connection timeout (min) field, specify a timeout value for your connection pool in minutes. 10 minutes is the default value.
f. In the Connection wait time (sec) field, specify a wait time for your connection pool in seconds. 30 seconds is the default value.
Connections to an ERP server take up valuable resources on both the client and the remote server. You can create a pool of connections to minimize the resource and time constraints. In estimating the size of the pool, you may calculate pool size by the amount of server resources to be consumed, the number and size of the documents to be received, and the size of your Java Virtual Machine. The section of mySAP documentation "Memory Management (BC-CST-MM)" explains in detail the resources required on the mySAP system.
6. To view the Advanced tab, click Advanced.
The Advanced tab becomes available as shown in the following image.
The Advanced tab enables you to specify your EDI and IDoc versions, and configure error handling. The following fields are available:
a. From the EDI version drop-down list, select the Electronic Data Interchange (EDI) document version you are using with the iWay Application Adapter for mySAP ERP. Version 3 is the default value.
b. In the IDOC release field, specify the IDOC versioning you want to use for your connection.
c. From the IDOC release provider drop-down list, select, IDOC DOCREL field (default),
SAP release, or user input.
d. From the Error Handling drop-down list:
If your application is Java centric, select Throws Exception so that code components can catch the exception and react accordingly.
If your application is document based, select Creates Error Document to create an XML document that contains the Java exception.
It is up to your application to read the XML document and obtain the error.
e. If a high degree of accuracy is required in your application, select the Commit with
Wait check box.
The adapter waits until all records are physically written to the database before returning from the function call. The "Commit With Wait" has a performance impact on adapter performance, so consider carefully before selecting it. The commit behavior of BAPIs is described in the mySAP documentation under "BAPI Programming Guide and Reference (CA-BFA)."
All mySAP Business Objects that change data must commit work to the database. Some BAPIs developed in version 3.1 of the ERP system use an internal commit behavior, and their commit behavior cannot be changed by the adapter. As soon as they are called, they commit the work they did.
BAPIs developed since release 3.1 use the external commit method. The adapter issues a commit command, and the commit is put in the database queue. If there is an application error in the first part of the commit, the error message "Posting could not be carried out" is returned, and the adapter rolls back the transaction. If in writing to the database, a database error occurs, a short dump is issued in the database records of mySAP, but no message is returned to the adapter about the failure.
This option is disabled by default.
f. To enable SAP traces, select the SAP trace check box 7. To view the Security tab, click Security.
