Following up on my article about the connection of a native HANA backend to HCP we will now have a look at the process about connecting an ABAP backend.

Motivation:

Previously you needed to set up an ABAP Frontend Server (Netweaver Gateway) to provide on OData service. The ERP Backend needs the IW_BEP component used for the development of the service. And via IW_FND on the Gateway system the service was made available.

With HCP OData provisioning you don’t need to set up a Frontend Server on premise any more. So this saves you one system in your landscape.
Here I will show how to connect the ABAB backend to the HCP without Frontend Server.
You still need the IW_BEP component and the development for the OData Service.

Disclaimer: This is for demo purposes only, security topics are not discussed here.

Prerequisites:

  • You have activated you HCP account. (you can get a free trial via hanatrial.ondemand.com )
  • The backend development has been done, or you use a ready made demo serivice.
  • You have enable the OData provisioning service in your “Services” Menu.
  • You have your Hana Cloud Connector set up and running as described in my previous post.

Lets Start:

We start by accessing the ERP Backend system.
in transaction SICF we check if the iwbep node is activated:

Right click and test the service to check if the activation was successful.

Also keep the URL in your notes:

http://<server>:<port>/sap/iwbep?sap-client=100

 

We switch to the Cloud Connector Admin Console

We add a new connection:

  • Http
  • Server and port of the ABAP system (from above)
  • Virtual server (s4hanahost:8000 in my example)
  • -no principal

Then we add a new resource:

  • /sap/iwbep/

We also allow all sub path to be able to include more services.

Now we switch to the HCP Admin console:

We select Service->Odata Provisioning – Configure Odata provisioning

Here we define the Destination

The URL is:

http://s4hanahost:8000/sap/iwbep/ (according to the virtual host we have created)

The user is the ABAP Backend user

Additional property is the sap-client id

You may also need to configure the Roles for your user:

Then we switch to the actual Odata provisioning service in the HCP Cockpit:

The service is now registered:

From now on we can call it via the link “Open Service Document”

Based on this OData Service you can now create a UI5 Application as described in my previous post.

I hope you find this helpful.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Murali Shanmugham

    Hi Bernd,  Thanks for posting on this. Just letting you know that “HCI OData provisioning” has been renamed to “HCP OData provisioning”. OData Provisioning within HCI is coming soon.

    (0) 
    1. Bernd Boehm Post author

      Thanks Murali I’ll update this. Hard to keep up the pace with all the renaming 😉 The Article was finished a while back and didn’t get round to post it.

      (0) 

Leave a Reply