SMP 3.0 Simplifies Integration

Jump to: Integration Gateway | OData Services | Exchange Framework |

SMP 3.0 brings together different mobile technologies - SUP, Agentry and Mobiliser - that each implemented their own integration framework and that each came with its own capabilities and purposes.

With the consolidation of the different technologies, SMP3 introduces a much simplified and unified approach to (back-end) integration: relying on the standard OData protocol. SAP NetWeaver Gateway provides the direct OData connectivity to SAP back-ends, whereas Integration Gateway provides additional integration to 3rd party systems using protocols such as SOAP, JDBC, JPA, and more.

In his blog There is a Gateway for that ..., Mustafa Saglam addresses in more detail what the different Gateway solutions are used for.

Got a question on Integration? Ask!

Integration Gateway is a technology component that provides design-time tools and the associated run-time for modeling, composing and provisioning OData services. These can be based on one or more APIs from various SAP and non-SAP data sources.

The data sources supported as of today are SOAP, JPA and JDBC to access non-SAP data sources as well as ODC for accessing OData services provisioned via SAP Gateway.

Integration Gateway is delivered inside SAP Mobile Platform 3.0 as an on-premise solution. It is fully implemented in Java and runs on SAP Lean Java Server, a lightweight OSGi based application server.

To build the services, the Gateway Productivity Accelerator includes the Eclipse-based Toolkit for Integration Gateway, used for modeling and generating components that are deployed through Integration Gateway.

Resources

• SMP 3.0 Server Documentation on Document Exchange contains three introductory sections on Integration Gateway.

How-To Guides

• Develop and deploy an OData service to the SMP3 on an Oracle database, by Marvin Hoffmann

  • Part 1 describes how to set up the HSQLDB and how to deploy the JDBC driver to SMP3

  • Part 2 describes how to model, implement and deploy the OData service with Integration Gateway

  • Part 3 describes how to configure the Integration Gateway on SMP3 to bind the OData service to the backend and how to display the OData service

• Create an OData Service based on SAP Gateway, SOAP, JDBC and JPA Data Sources, by Bjoern Woppmann

The SCN Space for NW Gateway holds all knowledge about NW Gateway in one place. Make this a frequent stop!

Three How-To guides help with offline features for mobile apps:

1. How to Develop a Gateway Service using Code based Implementation
2. How to Develop Query Options for an OData Service Using Code-Based Implementation

SAP has officially ended the support of Eclipse Juno in June 2014. Since GWPA is only available on Juno, this tools is no longer offered by SAP.

What does that mean for you? Amit Nigam explains this how we have you covered in his blog SAP Gateway Developer Tools – Bridging the Past, Present and Future.

As as summary for the three individual components of GWPA:

• OData Modeler: We will have a new and improved tool in the Kepler release
• Provisioning Tools: Currently we have “Toolkit for Integration Gateway” which supports SMP 3.0 (more above).
  In Kepler we will have an improved toolkit called “API Toolkit for SAP Mobile Platform” - stay tuned!
• Consumption Tools: Please refer this link for more details