Index Changes

SAP eWay on CAPS 5.X.X

User Experience


1.Installation
  • User uploads SAP adapter product SAR file to the repository
  • User copies JCO jars and libraries in system and eDesigner folders
  • User installs SAP adapter eDesigner plugin
  • User installs SAP adapter eManager web-app plugin for monitoring
2.Design time
  • User runs the SAP OTD wizard to create an ALE or a BAPI OTD
  • User uses wizard generated OTD to access exposed interfaces in Java and BPEL collaborations
  • User generates project application EAR containing SAP components (including J2EE connector and generated code and J2EE deployment descriptors)
3.Runtime
  • User copies JCO jars and libraries in system and appropriate logical host folders
  • User deploys EAR generated at design time to the Integration Server (IS)
4.Monitoring
  • User views SAP adapter configuration properties
  • User deploys/undeploys EAR generated at design time to the IS
  • User starts/stops inbound SAP adapter component
  • User views SAP related alerts
  • Alerts are generated when operations fail due to lost connections
  • User views SAP adapter log entries in the IS server logs
5.Error handling
  • Calls to methods exposed by the SAP OTDs are specified at design time. For Java collaborations, exceptions thrown from method calls can handled in
6.Performance tuning

High level Architecture – IDOC interface


1.Logical Representation
  • IDOC OTDs provide IDOC document logical representation
  • OTD structures are dynamically generated based on IDOC definition file provided at design time
2.Logical Representation
  • IDOC OTDs are used for parsing and constructing IDOC documents
3.Communication with SAP
  • Interfaces are implemented using SAP's JCO Java API
  • IDoc via BAPI : Use Transactional RFC (tRFC) mode using SAP BAPI OTDs to exchange IDOCs with SAP via ALE
4.BPEL support
  • WSDLs are generated based on BAPI metadata

High level Architecture – BAPI interface


1.Logical Representation
  • BAPI OTDs provide logical representation
  • OTD structures are dynamically generated based on BAPI metadata obtained from SAP at design time
2.Logical Representation
  • BAPI OTDs are used for performing BAPI data updates and executing BAPI calls into SAP
3.Communication with SAP
  • Use SAP's JCO Java API to implement calls to SAP BAPI in OTDs

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-1) was last changed on 29-Nov-06 10:49 AM, -0800 by jkWiki