 Knowledge base
|
|
|
|
|
|
|
|
 |
|
|
|
SAP XI Development
|
 |
|
 |
|
| SAP XI Certification Questions |
| XI Message Mapping
Overview PPT of XI message mapping.
Very good overview of how XI mapping works |
| SAP NetWeaver Developer’s Guide Release: SAP NetWeaver 2004s
Enabling Application-to-Application Processes
This documentation describes how to centrally design processes to integrate applications
within a company as part of the enabling application-to-application processes IT scenario.
The applications to be integrated can be SAP or non-SAP applications. |
| AdaptersAdapter for mySAP.com (for SAP R/3 V. 3.x) User Guide
This document describes installation, connector property configuration, business object development, and troubleshooting for the IBM WebSphere Business Integration Adapter for mySAP.com. |
| EDIFACT to XML - A DataDirect XML Converters Solution
Have you ever faced an EDI message exchange using SAP Exchange Infrastructure? If not, I'd say you're lucky. Because although EDI can appear trivial under certain circumstances, believe me it is not. The typical scenario could be EDI to IDoc and vice versa, for instance. Whatever format you choose on "the other side", EDI must be handled carefully, and that's not easy. I'm not an EDI expert - far from being that, actually - but I've been forced to learn some EDI basics in my last projects. The first thing that I realized was that there are a lot of EDI dialects. For instance, Odette, an EDIFACT dialect for the automotive industry, is not universally supported. Moreover, each company using EDI usually can customize EDI messages based on their needs, just as an SAP-guy can create a CIM type to extend standard IDoc types functionality. |
| Web Services Testing SAP NetWeaver Application Server, Java EE 5
One of more exciting parts of Java EE 5 specification is a heavy support for annotations that enable developers to cleanly expose already developed Java code as web services through meta data without modifying code for classes or methods.
|
| How to guides - XI for NW 2004
How to documents |
|
|
|
|
|
|
|
|
|
|
|
|
|
SAP XI Operational Management
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SAP Connectivity
|
|
|
|
|
| Interfacing with SAP R/3
One of the primary challenges of SAP implementation process has been integrating SAP with the
other applications. Be it the existing Legacy system, on which the customer has spent the money
and time building complex business specific logics into it, or the buzzword of the new era
’web-enabling’ applications, which opens up the eBusiness pathway to the whole world of
customer and partners to interact directly with the ERP system. |
| Step-By-Step Approach for Implementing XI Scenarios
In this document I have explained step-by-step how to develop “Web Service to RFC”, “HTML to Web Service” and “File to Database using BPM” scenarios |
| Extending MySap.com with Com+ and .NET |
| SAP Proxy Generator Add-in for Visual Studio 2005
SAP has no explicit plans to create a SAP.Connector compatible with Visual Studio 2005. That is the reason why Softwise has developed a SAP Proxy Generator to create proxies for SAP's BAPIS & RFC. This code generator is a Visual Studio 2005 Add-in that creates the source code, in C#, to comunicate with SAP (based on SAP.Connector.dll). This article intends to guide you through the installation and use of our tool. |
| Read Tables from SAP R/3 using SAP.NET Connector
Using SAP's .NET Connector is very easy, all it takes to manage it is a little work and effort. This article provides you an introductory example on how to use the Connector within C#. |
| Transferring data from SAP to .NET using ERPConnect
In my last customer project I had to implement a kind of "quick ordering software" for a machine manufacturer company. The goal of this project was to give the construction engineers the possibility to send an auto generated order list to the buying department. The construction department is using a PDM system based on SQL Server 2000 with an Access frontend, while the buying department and the other economic departments are using an SAP system. So the main task in my project was to implement an interface for these two systems, especially to receive the necessary data from the SAP system into my .NET application. After a short search on the internet I have found ERPConnect by Theobald Software. This tool allowed me to directly access the data from BAPIs and Tables in the SAP System I needed. |
| IDoc Connector for XML Component (BC-FES-AIT)
The IDoc Connector for XML is a COM component that provides an XML interface for working
with IDoc documents.
The IDoc Connector for XML component accepts your XML documents and sends them as
inbound IDocs to a specified R/3 system. Conversely, it can receive outbound IDocs and it
translate them into XML documents for your application to use. |
| SAP .NET Connector
The SAP .NET Connector is a programming environment inside of Visual Studio .NET that
enables communication between the Microsoft .NET platform and SAP Systems. It supports
SAP Remote Function Calls (RFC) and Web services, and allows you to write various
applications, for example, Web form, Windows form, and console applications within
Microsoft Visual Studio .NET. You can use all Common Language Runtime (CLR)
programming languages such as Visual Basic .NET, C#, or Managed C++.
This documentation presents an overview of some key features of SAP .NET Connector and
its architecture. |
| SAP connector for Microsoft.NET example
he SAP .NET Connector is a programming environment inside of Visual Studio .NET that enables communication between the Microsoft .NET platform and SAP Systems. It supports SAP Remote Function Calls (RFC) and Web services, and allows you to write various Applications, for example, Web form, Windows form, and console applications within Microsoft Visual Studio .NET. You can use all Common Language Runtime (CLR) programming languages such as Visual Basic .NET, C#, or Managed C++.
At runtime, the SAP proxies communicate with the SAP system by either the SAP RFC protocol (librfc32.dll) or via SOAP. SAP systems up to release 46D do not have SOAP support while SAP systems starting from 6.20 can use either SOAP or RFC. Non-SAP systems can be connected using SOAP. The SAP client solution is derived from the Microsoft SoapHttpClientProtocol class. The SoapHttpClientProtocol class is part of the Microsoft .NET framework and specifies the class proxies derive from when using SOAP.
This base class for SAP clients provides .NET developers with a familiar way to use SAP functionality. |
| SAP .NET Connector Installation
The SAP .Net Connector is a standalone component that is installed in addition to the SAP system. To access the installation files, see the SAP Service Marketplace at the internet address:
service.sap.com/connectors |
| SAP Automation RFC and BAPI Interfaces
The following tables list the SAP Automation tools, components, and libraries that use the RFC interfaces. The tables describe the function of these products and lists the programming language(s) with which you can use each of them.
Use the links from these tables to access the detailed documentation of the various products.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SAP XI and Biztalk
|
|
|
|
|
| Interoperability between Microsoft BizTalk Server 2004 and SAP XI 3.0
This white paper provides a concept on how to integrate Microsoft BizTalk Server 2004
and SAP XI based upon a scenario of both integration platforms acting as cooperating
systems and integrating different parts of the application landscape. The white paper
combines conceptional work on a double-hub integration architecture and practical
experiences from existing projects. A double-hub integration architecture consisting of
Microsoft BizTalk Server 2004 and SAP XI 3.0 encapsulates all SAP centric integration
scenarios and interfaces within the XI hub and all other scenarios within the BizTalk hub.
To achieve a seamless and comprehensive connection between those two hubs several
aspects regarding the different integration layers have to be considered. The white paper
covers all relevant aspects required to establish integration at transport, messaging,
process management and monitoring layer. At the transport and messaging layer
practical walkthroughs demonstrate the steps necessary to connect SAP XI and BizTalk
using the existing mechanisms and adapters. In order to provide a blue print for real-life
scenarios the tradeoff between Web Services and conventional RFC/IDoc is discussed. |
|
|
|
|
|
|
|
|
|
|
|
|
|
XI and monitoring
|
|
|
|
|
| Connecting to the Adapter Monitor
The Adapter Framework uses the adapter monitor interfaces to display the status of the adapter, its channels, and its subcomponents to system administrators |
| Connection to PMI
You have the option of connecting your adapter to the Process Monitoring Infrastructure (PMI). In the SAP environment, technical processes often extend beyond system boundaries (as is the case in Business Process Management, for instance). By connecting to PMI, you can monitor these processes.
PMI collects data from various different systems by means of PMI agents, which make their data available centrally for evaluation purposes.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SAP XI Guides
|
|
|
|
|
| A Beginner's Guide to SAP Exchange Infrastructure Settings, Part II
The second part of the XI beginner's guide walks the novice through basic settings, configurations, and mappings in SAP XI, and is also useful for Java experts who want to learn about SAP R/3 transactions involving connectivity, configurations, partner profiles, transactions and port declarations, and IDoc postings and generations. In the business scenario described in this paper, customer master data is created in SAP R/3 from a legacy source |
|
|
|
|
|
|
|
|
|
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
|
|
|
|
|
|
|
|
|