What is so different about the EPO XML Connector? What are the main advantages? The differencies start with the idea behind it: “Allowing any system to integrate directly with SAP without the need of a middleware system and using the powerful SAP NetWeaver application server (ABAP) to implement it. This allows making SAP integration fundamentally easier”.
It is one of the rare combinations of business advantages with technical excellence. For example the use of existing SAP NetWeaver technology means a decisive cost advantage and allows most stable integrations on a high performance server. Another example of this combination: There is no need of a middleware server and software, which must be highly available and is cost intensive for several reasons.
How is the architecture? What is technically different to EAI or SOA integration servers? First, it is not an extra EAI server and that makes one main difference. It is an ABAP add-on to the SAP NetWeaver application server, which has got all functions of a full integration server. So it enables direct integrations with SAP without the need of a middleware server or a translating software piece.
Next the preferred message format is XML.
Another main difference is, that the communication protocol http can be used from end to end (by using the web server functionality of SAP NetWeaver). Most other EAI servers connect to SAP with the SAP’s RFC protocol and therefore need a translation for this.
Another difference is, that the communication layer used for integration (http, https, file, ftp, e-Mail) does not imply any difference on the core implementation.
The core implementation (BAPI or function module call, Call transaction, Batch Input, SQL statement etc.) is done in ABAP with all SAP workbench features available. No SAP business logic is swapped to middleware or the integrated system.
SAP standard for web services (SAP inbound) and proxies (SAP outbound) is fully supported.
What steps are involved to create a new integration? 1. Installation of the EPO XML Connector (one time task)
2. Configuration of the service (every single interface we call “service”)
3. Implementation of the core for the service: This can range from publishing a BAPI as web service, calling a function module, writing a Call Transaction or Batch Input etc. for SAP inbound and for SAP outbound this can be calling the EPO Client (a single function module) or calling the method SAP Client after generating the proxy class from a WSDL. The EPO XML Connector is delivered with templates, which can be copied.
4. Testing the integration and go-live.
How compatible is this concept with SOA? The EPO XML Connector should fit very well into your SOA strategy, because you connect your SAP systems directly to your SOA layer. It creates itself a SOA layer directly out of SAP ABAP, which can be used to build a enterprise wide SOA architecture.
How does this fit into our IT architecture? The EPO XML Connector will solve your issues with SAP integration. It will give you more options to build your IT architecture.
Why do I NOT need a middleware server/software? When you integrate with MS Excel, will you order a middleware server for MS Excel? No, you won’t. The same answer is now possible for SAP with the EPO XML Connector. It contains all integration features you need right now and much more. It is an ABAP add-on - a similar thing to a MS Excel “add-in” or “plug-in”. Tip: Check out XML Transmitter Office (a MS Excel add-in) for integrating MS Excel with SAP.
Can your connector be used to replace the SAP Business Connector? Yes. EPO Consulting has got a lot of experience with the SAP Business Connector. To be able to replace it with the EPO XML Connector, was one of the targets when designing and implementing the EPO XML Connector.
What disadvantages does your connector have compared to SAP XI/PI? The EPO XML Connector is built on another concept and therefore it is hard to compare. The EPO XML Connector is more of a complementary product to SAP XI/PI. Currently we are not planning to deliver adapter packages e.g. for translating industry specific legacy message formats (non XML). However we do deliver integration packages for independent software vendors like Metastorm BPM and we will bring out more (working together with software vendors and customers). The concept of the EPO XML Connector allows itself to integrate any system and any message format.
We have got SAP XI. Can I use it together with SAP XI/PI? Yes. You can create SAP integration with the EPO XML Connector which uses SAP XI (SAP <-> EPO XML Connector <-> SAP XI) and you can also create direct SAP integration.
We have got an integration server (Tibco, BEA, Webmethods, …). Why should I use the EPO XML Connector? You can bring better quality into your SAP integration. Instead of using SAP’s RFC protocol, you will connect with http(s) and XML to SAP. Business logic will be implemented in SAP. The interfaces will be simpler on the EAI server.
What functions and features will be added with new releases of the EPO XML Connector? The EPO XML Connector will be further developed by EPO Consulting over the years. Currently we do not want to publish the next developments. However we invite our customers and potential customers to suggest new functions and features for development. E-Mail this to:
We are an independent software vendor. Can we use the EPO XML Connector to connect our software product to SAP? Yes. With the EPO XML Connector you can build a direct integration with SAP. The integration can be certified with SAP (“SAP certified interface”).
Do you offer a maintenance contract? Yes. It includes free upgrades and support.
How much does the EPO XML Connector cost? Please contact EPO Consulting or one of our partners.
How does the XML Transmitter product family fit into SAP integration? XML Transmitter Office: This MS Excel add-in can be used to create "one-click" integrations from MS Excel to SAP. You can send XML files from MS Excel directly to SAP. XML Transmitter: This strong .NET program allows you to test and develop web services. EPO Consulting is using it to create integration with SAP. You can import WSDL from SAP and test SAP web services instantly. You can apply stylesheets. This and many more functions make the XML Transmitter the perfect application for web service developments. XML Transmitter PRO: This is an XML server running on Microsoft windows plattforms. You can set folder and files (including masking) to be watched. New and/or changed files will be automatically forwarded to a defined "destination". The destination can be your SAP system. So you can use it to automate your SAP integration. To give one example: You can generate XML files with some application and store those XML files in a "watched" folder. The XML Transmitter PRO will forward those files to their destination (SAP) according to the schedule.