.ENV File Error when Deploying from BAS

[former_member846077]

Attempting to deploy a Fiori app and migrate from Web IDE to BAS. Deploying to ABAP Backend server. Connection is successfully connected to Gateway Server via Service Center in BAS. SAP UI5 Service is activated in SICF. Connection is successful in BTP Cockpit when testing Connection.

CC: jlongie

.env file is created and has Username and Password defined

Ui5-deploy.yaml file refers to credentials and is saved

Error after running script NPM RUN DEPLOY

After re-running deployment with debug script set DEBUG=ux-odata-client & npm run deploy the same error is displayed again

[former_member846077]

Hi jlongie and thank you for your response!

We had activated the /UI5/ service but did not have /ABAP_REPOSITORY_SRV activated in transaction /iwfnd/maint_service

Regarding the .env file, I read in SAP Press Book SAP Fiori: Implementation and Development the .env file goes in the webapp folder. I'll try with the .env file in the root directory after we upgrade our SAP Support Pack (mentioned below).

I'm receiving the error: SAPUI5 ABAP Repository with name Z_* does not exist in transaction /n/iwfnd/error_log

Based on KBA 3263424, this errors is resolved by implementing SAPK-75211INSAPBASIS as described in Note 3212364.

[jlong]

The .env file should be in the root of your project since the webapp folder is packaged up into a zip and deployed to your target ABAP system thus you have exposed your username and password.

The .env should be appended to both your .gitignore and if you are including it in your webapp folder, to exclude it by updating the ui5-deploy.yaml configuration to exclude this file.

I'm not familiar with the book reference but for best practice I would not include specific configurations in your webapp folder.

John

[jlong]

Hi

A few things to try;

1. env file location

Ensure the .env file is in the root folder and not in your webapp folder. When you deploy, the .env is only detected in the root folder.

2. Validate endpoint

Since you are using a destination try executing the following curl command;

curl -L "https://<destination>.dest/sap/opu/odata/UI5/ABAP_REPOSITORY_SRV/$metadata?saml2=disabled" -vs > curl-abap-output.txt 2>&1

Replace <destination> with the name of your destination. This

If using basic authentication, then update the curl command to;

curl -u <user>:<password> -L "https://<destination>.dest/sap/opu/odata/UI5/ABAP_REPOSITORY_SRV/$metadata?saml2=disabled" -vs > curl-abap-output.txt 2>&1

Review the generated txt file which in some cases will highlight the root cause.

Please also review the following link, ensuring the pre-requisties are completed;

https://ga.support.sap.com/dtp/viewer/index.html#/tree/3046/actions/45995:45996:50742:46000

John