Hi Gatekeepers,
I've been getting to grips with the Eclipse plug-in(s) for Gateway. Already confused as the previous and current plugin versions are packaged differently, so I ended up with a few duplicate feature names but different look & feel in Eclipse depending on the one I picked.
What I did notice in common with both application builder versions is that they hardcode(?) the absolute service address into the application package.
That leads to a few problems:
1 - it may not allow my development GW address if I am running the SDK on localhost due to Same Origin policy error. In which case I need a reverse proxy address as the service address (not tried this) or I need to manually edit the stored location (as done above).
2 - if I am sharing this project to other development bodies, they may have a different proxy defined if using localhost.
3 - when this is deployed to a SAP AS and served from there, what happens when it needs to be transported through to PRD? How do we re-route the service call?
The address value is stored in 'connectivity.js' in the Webcontent hierarchy. It is therefore technically viable to edit it in a target environment after loading. Is this the procedure for carrying out such a change? I'm not a Jscript or Web developer by trade so I don't know if this is a normal expectation with a standard cutover activity when the transport package is a web related offering.
I was expecting something more like a property list in a bundle where the protocol, server, port and service node are maintained separately. This would then be an in-system configuration which is maintained by web/Basis admin.
Not going to be transporting any time soon but it would be nice to head off any tricky obstacles like this.
Regards
Ron Sargeant.