Dot Net Sap Integration With Exchange Infrastructure Computer Science Essay

Dot Net Sap integrating With Exchange theme Computer Science EssayThe tomfool Connectors will the integration of different applications employ its technology with eat Systems apply the streamers. The connectors atomic number 18 means for technical interoperability of deplete Components ( write in ABAP or ABAP Objects) and other divisions (e. g. written in Java, C++, Visual Basic, .NET, etc.). There are m each types of soft touch Connectors such as soft touch .NET Connector, peter out JAVA Connector, mug DCOM Connector, SAP BUSINESS Connector. SAP Exchange Infrastructure is middleware which can be apply by various applications and technologies to immix with SAP using an open protocol and standards.SAP Exchange Infrastructure (SAP XI) is SAPs enterprise application integration (EAI) software program, a component of the Net Weaver product group gived to help the exchange of in kindation among a comp eachs internal software and remainss and those of external parti es. manage other Net Weaver components, SAP XI is compatible with software products of other companies.SAP bids XI an integration broker because it mediates amid entities with varying requirements in terms of connectivity, format, and protocols. According to SAP, XI reduces integration costs by providing a common repository for embrasures. The central component of SAP XI is the SAP consolidation Server, which facilitates interaction between diverse operating systems and applications crosswise internal and external networked computer systems.Exchange InfrastructureSAP Xi- computer architectureXI is well suited for connecting SAP systems with each other and with non-SAP. If the centralize is not on SAP systems, other solutions might be a better choice today. SAP XI provides an integrated workflow railway locomotive that in allows to define transcribers to non-XML-protocols and mappings to convert data content from fountain to target.Central XI monitoring offers the following optionsComponent monitoringMessage monitoring surgical operation monitoringAlert configurationCache monitoringBusiness dish up ManagementA crinkle process is an executable, cross-system process. In a cable process we can define all the process steps that are to be executed and the parameters relevant for controlling the process.Implement cross-component Business crop Management (BPM) when need to define, control, and monitor complex business processes that extend across enterprise and application boundaries.integration EngineThe integrating Engine is the runtime environs of the SAP Exchange Infrastructure.It enables to process XML messages exchanged between applications in confused system landscapes. Both applications of SAP components and external applications can communicate with the desegregation Engine.Using adapters, the Integration Engine can as well as process IDocs (Intermediate Documents) and RFCs (Remote crop Calls). This option is available for applications th at pay off already defined IDocs or RFCs, as well as for applications of SAP components that do not yet have access to the proxy generation functions.The following are examples of other distinguished parts of this infrastructureProxy GenerationIntegration RepositoryIntegration DirectoryThe integration processes involved can take place between confused system components within a company, as well as between business fellows outside company boundaries. transcriber RuntimeA central component of the adapter runtime is the Adapter Framework, with services for messaging, queuing, and security handling. The adapter framework supports the JCA standard (JCA J2EE Connection Architecture) and communicates with Resource Adapters, which are either a component of SAP XI or are provided by SAP quislings. All adapters shipped by SAP are resource adapters, apart from the IDoc adapter.The following adapter components are ground on the adapter frameworkAdapter Engine (J2EE) For adapter communicati on within a system network. render Connectivity Kit (J2EE) Enables business partners who do not have SAP XI installed to receive and radiate messagesSystem landscape DirectoryBusiness partners who use SAP Exchange Infrastructure (XI) can exchange messages between their system landscapes.If both business partners use SAP XI 3.0, and then we can connect the two Integration Servers to exchange data.An SAP XI 3.0 Integration Server can also send and receive SAP XI 2.0 messages. Therefore, it is also possible to integrate business partners who use SAP XI 2.0.Small business partners who do not use SAP XI can use the Partner ConnectivityKit (PCK) to exchange messages with the system landscape of a business partnerwho uses SAP XI 3.0.Partner Connectivity KitThe PCK of the smaller business partner receives a message from its system landscape and converts the format of the message to XI message protocol. The message is forwarded to the Integration Server for further processing.To forward XM L messages from the Integration Server to a murderer business system in the system landscape of the smaller business partner, the PCK of the business partner receives the message, converts into the format required by the pass receiver system, and then forwards the message. The PCK contains the following adaptersRFC Adapter commit AdapterJMS AdapterJDBC Adapter liquid ecstasy AdapterXI AdapterHow SAP XI works with .Net?If the .NET application is exposing any API in the form of Web servics, SAP XI can make a call to the web service.If .Net app is on the sending then it can call SAP XI using a HTTP call or using a Web service.WSDL (Web Services Description Language) is generated using SAP XI and then its used to generate the client proxies in VB. The ASP.NET web application interacts with SAP XI using generated VB class and SAP XIs SOAP adapter.WSDLWEBSOAPSOAPRFCUserGenerate Client proxies using WSDL in VB/CReference.csForm.aspxForm.aspx.csWebapp.dllASP.NET Web ApplnSteps for connect ing .Net with SAPConfigurations from SAP Xi side pass water request message mapping.Create response message mapping.Create interface mapping between source target.Create sender communication avenue of type SOAP adapter using the outbound synchronous interface and its namespace.Create receiver communication channel of type RFC adapter.Create receiver purpose using sender service, outbound synchronous interface, receiver R/3 business system and then form interface determination using RFC and finally create receiver agreement using receiver RFC channel.Create a WSDL for the outbound synchronous interface. Use this URL http// serverport/XISOAPAdapter/MessageServlet?channel=partyservicechannel while specify web service. Save the WSDL (Web Services Description Language) in the local system.Configurations in .Net sideOpen the development environment of Microsoft Visual Studio .NET and create a new project of type Visual Basic using the template ASP.NET Web Application.Copy the WSDL g enerated using SAP XI in the root folder of web application.Go To solution explorer References conduce Web Reference.Browse To Web services on local machines. require the service and click on Add reference.When the web reference is added for the WSDL the .VB source (proxy) is generated in the Web References folder of the web application. This proxy needs to be compiled into Dynamic Linked Library .DLL. For this, build the web application using BuildBuild Web application. The DLL is generated in webapp/bin/ folderProsMonitoring is better than any other middleware product. It offers exhaustive monitoring features like message, performance, component monitoring etc, all of which can be used to track and rectify the errors. It follows a hub and speak model.When we need to integrate with an SAP system XI has an advantage in supporting various SAP components and so on.Process functionalities inside XI to modify content in the communication channel on testify defined rules for busines s purposes.Mappings and adapters are good as comparable with any other middleware product.Synchronous Asynchronous communication is possible.ConsWeb methods are specially good if u have B2B kind of communication with their Trading Partners product.XI is lacking full-fledged Message Queue compared to other established Middleware products.It lacks in ability to process huge messages but SAP is working on that.It does not have a messaging layer exposed by APIs like IBM MQ-Series.It is not comparable to Tibco in terms of speed.SAP relies on other vendors except for a few adapters.Conclusion presently applications in Honeywell are using the various SAP connectors. Migrating the applications integration to SAP Exchange Infrastructure will get cost advantage by avoiding SAP connector licenses. SAP PI Base Engine is priced establish on the overall processed message volume expressed in Gigabytes (GB) per month. The applications will also benefit from modern integration functionalities like auction pitch assurance, once-only, ordered-delivery, prioritization, review of messages and resubmitting after correction. SAP Xi is one of the key construction blocks of enterprise SOA architecture provided by SAP.We can continue to leverage towards Honeywell SOA based IT landscape with SAP Xi.