Connecting to an SAP system in .NET Encoding data matrix barcodes in .NET Connecting to an SAP system

Connecting to an SAP system generate, create data matrix none in .net projects Microsoft Office Word Website This scenario VS .NET ECC200 shows how SAP can be integrated using the Trivadis Integration Architecture Blueprint. We are making an exception in this case by considering a specific product as a candidate for integration, identifying the corresponding integration platforms, and including them in the scenario.

By doing this, we can show how the Integration Architecture Blueprint is used in practice, using some vendor products for the building blocks.. [ 161 ]. Implementation scenarios The image bel ow shows how an orchestration using Microsoft BizTalk and SAP can be combined. On the one hand, a simple SAP service is accessed using a Remote Function Call (RFC), and on the other hand, an SAP business process is implemented using the SAP Exchange Infrastructure (SAP XI) to access the SAP system. The SAP business process is callable as a service and is used from the BizTalk orchestration.

. Trigger: The visual .net barcode data matrix application sends an SOAP request. Primary flow: 1.

The SOAP request initiates a new instance of a BizTalk process. 2. The process either implements a call directly in SAP in the form of an SAP RFC call, or starts another business process which is made available by SAP XI through an SOAP call.

3. The SAP XI business process is initiated and sends two calls to the SAP system. One takes the form of a SAP RFC call, and the other uses a web service interface made available by SAP.

. Modernizing an integration solution This section ECC200 for .NET uses an example to illustrate how an existing integration solution that has grown over time can be modernized using SOA methods, and the scenarios from the previous sections..

[ 162 ]. 4 . The example i s a simplified version of a specific customer project in which an existing solution was modernized with the help of SOA. The task of the integration solution is to forward orders entered in the central ERP system to the external target applications..

Initial situation The current s olution is primarily based on a file transfer mechanism that sends the new and modified orders at intervals to the relevant applications, in the form of files in two possible formats (XML und CSV). The applications are responsible for processing the files independently. At a later date, another application (IT App in the following diagram) was added to the system using a queuing mechanism, because this mechanism allowed for the guaranteed exchange of messages with the application by reading new orders, and sending appropriate messages through the queue in the form of a transaction.

The following diagram shows the initial situation before the modernization process took place:. [ 163 ]. Implementation scenarios The extractio data matrix barcodes for .NET n and file creation logic is written in PL/SQL. A Unix shell script is used to send the files through the File Transfer Protocol (FTP), as no direct FTP call was possible in PL/SQL.

Both a shell script and the PL/SQL logic are responsible for orchestrating the integration process. Oracle Advanced Queuing (AQ) is used as the queuing infrastructure. As PL/ SQL supports sending of AQ messages through an API (package), it was possible to implement this special variant of the business case entirely in PL/SQL, without a call to a shell script being needed.

In this case, the integration is bi-directional. This means that when the order has been processed by the external system, the application must send a feedback message to the ERP system. A second queue, which is implemented in the integration layer using PL/SQL, is used for this purpose.

. Sending new orders Trigger:. New orders ad ded to the master system (ERP-App) are periodically sent to interested external systems.. The job sched VS .NET ECC200 uler triggers an event every 30 minutes for each external system that has to be integrated. Flow: 1.

The event triggered by the job scheduler starts a shell script, which is responsible for part of the orchestration. 2. The shell script first starts a PL/SQL procedure that creates the files, or writes the information to the queue.

3. The PL/SQL procedure reads all the new orders from the ERP system"s database, and enriches them with additional information about the product ordered and the customer. 4.

Depending on the external target system, a decision is made as to whether the information about the new order should be sent in the form of files, or messages in queues. 5. The target system can determine in which format (XML or CSV) the file should be supplied.

A different PL/SQL procedure is called depending on the desired format. 6. The PL/SQL procedure writes the file in the appropriate format using a PL/SQL tool (in other words, the built-in package UTL_FILE) to the database server.

The database server is used only for interim storage of the files, as these are uploaded to the target systems in the next step.. [ 164 ].
Copyright © . All rights reserved.