Red Hat's partnership with SAP goes way back and has never been stronger than it is today. Whether it is certifying RHEL for SAP applications, creating joint demos, webinars or certifying Red Hat JBoss Middleware products with SAP technologies, we are constantly improving and expanding our integration story with SAP. This article will give you an up-to-date view of our solutions with SAP. Note that this is not an "official" document of supported solutions, but a document to create awareness of the possible integration scenarios with Red Hat Middleware and SAP.
A Translator provides an abstraction layer between the JDV Query Engine and physical data source, that knows how to convert JDV issued query commands into source specific commands and execute them using the Resource Adaptor. It also have intelligence to convert the result data that came from the physical source into a form that JDV Query engine is expecting. JDV provides various pre-built translators for sources like SAP HANA, Sybase, SAP Gateway, Oracle, DB2, SQL Server, MySQL, PostgreSQL, XML, File etc. A Translator also defines the capabilities of a particular source, like whether it can natively support query joins (inner joins, cross joins etc) or support criteria.
SAP Gateway - The SAP Gateway translator allows the users to consume and update SAP data via the SAP Gateway server using the OData protocol. JDV is a producer and consumer of OData which means we not only can we consume SAP OData services, we can expose federated OData services out of the top. The US Army is using this capability and the solution was implemented by Northrup Grumman.
SAP HANA - New in JDV 6.2, the SAP HANA translator allows users to create abstraction layers of all SAP data stored in SAP HANA. Our translator is currently in the process of attaining SAP Certification for SAP HANA and we will release a whitepaper around the solution around the same time.
SAP Services registry - Although this may be a less common use case for customers given the complexity usually associated with SOAP services generated from SAP, it is still worth noting. We support the consumption of SAP services as a source.
Other SAP data source support via translators - SAP BW via the OLAP translator, Sybase, Sybase IQ, Sybase ASE, SQLAnywhere
SAP HANA as a consumer of JDV - SAP HANA has its own Data Virtualization capabilities which we can leverage and expand upon using an ODBC interface. The HANA DV capabilities (SDA - Smart data Access) are somewhat limited in breadth of source support and connectivity options, but we can immediately increase that support tenfold by connecting JDV to HANA via SDA.
SAP HANA as a data cache - JDV can use HANA as a cache to increase JDV performance as well as increase value in a companies HANA investment.
Fuse/Camel integration - There is a Camel component (Olingo) that allows consumption and updating of SAP data using OData URLs via JDV for those scenarios that may requires an ESB or an EIP platform.
Red Hat JBoss Fuse as of Version 6.2
SAP Systems via JCo - The SAP component is a package consisting of a suite of ten different SAP components. There are remote function call (RFC) components that support the sRFC, tRFC, and qRFC protocols; and there are IDoc components that facilitate communication using messages in IDoc format. The component uses the SAP Java Connector (SAP JCo) library to facilitate bidirectional communication with SAP and the SAP IDoc library to facilitate the transmission of documents in the Intermediate Document (IDoc) format.
SAP Gateway - There is a Camel component that integrates with SAP Gateway (currently supports producer endpoints only).
SAP Gateway OData Client - The Olingo2 component utilizes Apache Olingo version 2.0 APIs to interact with OData 2.0 and 3.0 compliant services. A number of popular commercial and enterprise vendors and products support the OData protocol. A sample list of supporting products can be found on the OData website. The Olingo2 component supports reading feeds, delta feeds, entities, simple and complex properties, links, counts, using custom and OData system query parameters. It supports updating entities, properties, and association links. It also supports submitting queries and change requests as a single OData batch operation. The component supports configuring HTTP connection parameters and headers for OData service connection. This allows configuring use of SSL, OAuth2.0, etc. as required by the target OData service. This component can also call JDV using the OData server capabilities that come out of the box with JDV.
This will be a living blog that I will update as technologies and use cases evolve. As more integration scenarios arise, I will add them here. If there is an integration you are interested in, please feel free to reach out to me!