0
votes

For reasons of security I cannot use the cloud connector in conjunction with the on premise system which we have. Never the less I am very comfortable using WebIDE in order to create the necessary applications. I create the applications in WebIDE using a .edmx file which represents the on premise ODATA service which i plan to use.

After the application is made. I import the archive and then make necessary modifications to the archive in HANA Studio (inside Java EE perspective).

I am doing things according to this guide: https://www.sap.com/developer/tutorials/hcp-webide-switch-live-odata.html

My understanding is that the manifest.json and neo-app.json are both to be modified pointing to the real ODATA service.

In the manifest.json:

enter image description here

According to the guide above, within the neo-app.json, I need to point it to the gateway.

Here is the information of our on premise system.

System Name: sapewp01.xxxxx.com

localURI: /sap/opu/odata/sap/zbw_odata_q3_srv/

Port: 8012 (i assume, the odata service link works on my end)

SAP Gateway (sapgw12)

Another other required information can be provided on request.

How does one change a web ide app to be able link into an on premise ODATA service, WITHOUT disrupting all the work done on webIDE?

1

1 Answers

0
votes

In the sap.app part of the manifest.json can't you just specify?

"dataSources": {
    "myService": {
        "uri": "/sap/opu/odata/sap/zbw_odata_q3_srv/",
        "type": "OData",
        "settings": {
            "odataVersion": "2.0"
        }
    }
}

At least with my experience working in Eclipse, all I had to do was have the URI to create the model. oModel = new sap.ui.model.odata.v2.ODataModel(sServiceUrl, oConfig); but this was using a legacy app, maybe Web IDE does it a different way?