SMP3 - Admin / Architect:

[Former Member]

Hi, I have a question on SMP3 and Administration/Architecture...:In the current state of SMP3 and SAP Gateway 2.  How does the depreciation of the included SMP3 gateway affect current installations.  For instance,  do I now have to install SMP3 with OData connections to the Netweaver 7.4 Gateway 2.0 or does the current SMP3 still contain the integrated gateway?  If so please point to the documentation that explains the connection between the external Gateway 2.0.

[Former Member · Accepted solution]

As a follow on to the post.  The IGW integration gateway has been depreciated and no longer supported due to:

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.

http://scn.sap.com/docs/DOC-49861

How does this affect SMS 3.0 going forward?

Russ...

[Jitendra_Kansal · Accepted solution]

As a follow on to the post.  The IGW integration gateway has been depreciated and no longer supported due to: 
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.

oops you have misunderstood it. There is no plan of depreciating IGW AFAIK. IGW is a service running within SMP server. As mentioned by Midhun, The designer tool (part of IGW) can be installed as a plugin in Eclipse.

This plugin was part of GWPA (GateWay Productivity Accelerator) and could be installed in Eclipse JUNO. SAP has official ended the support of Eclipse Juno in the end of June 2014. See this announcement.

Now, GWPA has been superseded by "SAP Mobile Platform Tools" and it can be installed in Eclipse Kepler.

SMP 3.0 (on-premise) is alive and so IGW.

Regards,

JK

[Former Member]

Thanks, clearly a mistake on my part.

Russ...

[agentry_src]

Discussion successfully moved from SAP for Mobile to SMP Developer Center as the more appropriate venue for this question.

Regards, Mike (Moderator)

SAP Technology RIG

[Jitendra_Kansal]

How does the depreciation of the included SMP3 gateway affect current installations.

What exactly you meant by? can you put more points on this.

Integration Gateway (IGW) is an inbuilt service running with SAP Mobile platform server. When you install SMP3 server, IGW service is automatically activated. IGW will help you to expose non-sap/SAP based information (from sources like SOAP WS, REST service, JDBC,JPA, SAP Gateway) into OData services and you can mash-up among them in a single OData URL.

If you want to connect OData services (have already been exposed via SAP GW 2.0) to SMP3 server, you can directly add the odata endpoint in SMP3 admin cockpit and access it from mobile device. ( no need to use IGW in this case)

Regards,

JK

[midhun_vp]

Hi Russell,

To develop an app using SMP 3 with all benefits of SMP you need an Odata service; This services will be consumed in the mobile apps.

If you have an existing Odata service you can configure it in SMP server and use it for development of mobile app. You can get these service from a Gateway or any other sources. SMP don't bother about the source.

If your backend is not capable of exposing an Odata service (ex. Oracle) you could use Integration Gateway that will convert non Odata service to Odata service (ex.JDBC > Odata). Hence you could use this Odata service to develop your apps.

Integration Gateway is a component that comes with SMP 3. When you are installing SMP 3, by default IGW will be installed with it.

IGW has a designer tool and runtime. Runtime is part of SMP 3 server. You could install designer tool in your Eclipse as a plugin. Using this tool you could create Odata Models and deploy it to SMP server.

Regards,Midhun

SAP Technology RIG