How to segregate WebIDE UI5 Project as per Development/QA/Prod

[ankesh_jindal4]

Hi Team,

I am developing side by side app from S4C(S4 HANA Cloud) to HCP(HANA Cloud Platform). In WebIde, I have created couple of app's and deployed to HANA Cloud Platform and I am referring URL which got generated in HCP in my S4C as custom tile.

My query is in S4C, we have two different instance (Q & Prod ) but in HCP, how do I segregate the UI5 app if I distiguish between Q and prod?

Please suggest?

Regards

Ankesh

[gregorw]

You should use a different subaccount that is connected to the S/4HANA Cloud Production instance. The base URL should be placed in a Destination which is named always i.e. S4C so you don't have to adjust your apps when deploying to the production subaccount.

[ankesh_jindal4]

Hi gregor.wolf2,

What would be best approach to segregate S/4HANA Cloud Production instance out of these two: 1) Create different spaces within same sub-account, 2) Create different sub-account and why?

Also,

The base URL should be placed in a Destination which is named always i.e. S4C so you don't have to adjust your apps when deploying to the production subaccount.

I faces this issue lately , In Manifest.Json, On creating Fiori-Element app, Destinations are added in front of base-url. If I remove Destination, i can't test in WebIde, if I retain destination it will give issue after deployment , how do I overcome this issue.

I guess it is not good idea to put Destination everytime I test it from WebIde and delete the destination before deploying to S/4HANA Cloud instance, Please suggest?

Regards

Ankesh

[gregorw]

Hi Ankesh,

you have you create separate Subaccounts as the destinations are maintained on the Subaccount level and not in a space. For the problem with your manifest.json and the destination you should check the Network trace in your Browser developer tools to find out what's different after deployment. Also read up on the details for the neo-app.json file. You can do many tricks there regarding request routing.

Best regards
Gregor

[geert-janklaps]

Hi,

You could use a GIT repository to keep different versions of your app. We're doing the same at our customers. We use one branch for each environment, once we move from one environment to another we merge the branches.

Another thing I can mention is that you can deploy your app directly to the S/4HANA Cloud launchpad in stead of using a custom tile with URL. If you deploy to the S/4HANA Cloud Launchpad your app will actual run inside the launchpad giving you access to additional features (e.g. in app navigation using semantic navigation) and you don't need to worry about destinations anymore.

Best regards,

Geert-Jan Klaps

[ankesh_jindal4]

Hi 8d8214c7f9734f45be69f95cc0d5aeee,1) Can you please explain bit more on GIT repository approach , I can see system is create GIt by default on deploying app, where I can create mutliple branches , I have not used GIT earlier , can you please refer me to any blog that explains the process?2) I cannot deploy app directly to S/4HANA Cloud because my app uses external API (I am doing AJAX call to ADS service on HCP) , Do you think that is feasible ? RegardsAnkesh

[geert-janklaps]

Hi,

If you're going to deploy to SAP Cloud Platform, you should use the approach mentioned by Gregor. Create a subaccount for each S/4HANA Cloud instance (typically test and production) and connect each subaccount to the right S/4HANA Cloud instance. Within each subaccount use the same name for your destinations but point the to the corresponding instance (e.g. test or production).

Best regards,

Geert-Jan Klaps