Creating an API Based on Slack: Error while publishing product

[mphlippen]

In the journey "Developing with SAP Integration Suite", unit "API Provisioning", lesson "Creating an API Based on Slack" I get an error in "Task 6: Create a Product From Your API". 

When I want to publish the product I get this error message:

The "Show details" are not really helpful:

Note: There are some discrepancies between the screenshots in the task (or the steps in the Exercise) to how the Integration Suite actually looks. I guess the screenshots were made with an older version. So I might be missing something here...

I noticed however, that the step with the API Business Hub Enterprise feature is missing entirely in the Exercise and this step really confuses me as I only get a "Login" button there, that is actually a "Logout" button. So I guess this could be related to my problem here?

What I see when clicking on API Business Hub Enterprise:

And what the "Login"-Button actually does:

In any case, I cannot proceed with the lessons as I cannot publish the product.

Thanks for help & Kind regards!

[Margit_Wagner]

Hi @mphlippen,
We have received your request and are in the process of evaluating the problem.
Please allow for a delay in our response.
Kind regards
Margit

[mphlippen]

Hi @Margit_Wagner,

Thanks for the reply. Do you have any news for me? I'd like to proceed with the tasks 🙂

Or can I ignore the issue (for now) and proceed with the next lesson regardless?

Thanks & Regards!

[jannes_schofeld · Accepted solution]

Hi @Jarmo_Tuominen and @Tiwari ,

please have a look at the following GitHub repository that we have created for the course: https://github.com/SAP-samples/extension-suite-learning-journey

The main branch contains the initial state of the project, with versions of dependencies defined in the package.json and package-lock.json, that should work. Apart from that, the repository contains solution branches for each of the exercises. So there are 2 things that you could try to get to a working state again:

Option 1:

• Replace the package.json and package-lock.json in your existing project with the respective files from the repository.
• Then run command npm ci within the root of your project.

Option 2:

• Create a new folder  / workspace in your SAP Business Application Studio dev space (Open folder projects, within projects, create a new folder, e.g. risk-management-repo)
• Switch into the new folder risk-management-repo and run command git clone https://github.com/SAP-samples/extension-suite-learning-journey
• Now you can run command git checkout <branch> where you replace <branch> with any of the provided solution branches, e.g. solution/4_add_an_external_service
• Run npm ci once
• Use this as the base to go through the remaining exercises.

Please let me know if you need further assistance.

Best regards,

Jannes

[Tiwari · Accepted solution]

Dear Jannes, Now I am getting different error - Manifest applied Packaging files to upload... Uploading files... 9.24 KiB / 9.24 KiB 100.00% 1s Waiting for API to complete processing files... Staging app and tracing logs... Downloading nodejs_buildpack... Downloaded nodejs_buildpack Cell 52223b68-2a95-4e12-9fe8-6703e117c737 creating container for instance 95199459-67ec-4413-acd9-80fedb17d6ab Cell 52223b68-2a95-4e12-9fe8-6703e117c737 successfully created container for instance 95199459-67ec-4413-acd9-80fedb17d6ab Downloading app package... Downloading build artifacts cache... Downloaded app package (283K) Downloaded build artifacts cache (5.6M) -----> Nodejs Buildpack version 1.7.65 -----> Installing binaries engines.node (package.json): ^12.0.0 || ^14.0.0 || ^10.0.0 engines.npm (package.json): ^6.0.0 || ^8.0.0 || ^10.0.0 || ^12.0.0 || ^14.0.0 -----> Installing node 14.18.2 Copy [/tmp/buildpacks/092478478540c0d423f0bdd91cef63b0/dependencies/44d6aeb57b09918607f5b2b4dc626375/node_14.18.2_linux_x64_cflinuxfs3_44c618d4.tgz] npm 6.14.15 already installed with node -----> Installing yarn 1.22.17 Copy [/tmp/buildpacks/092478478540c0d423f0bdd91cef63b0/dependencies/4984aeaaf5967be21b1e442d431a1957/yarn_1.22.17_linux_noarch_any-stack_08892f64.tgz] Installed yarn 1.22.17 -----> Creating runtime environment PRO TIP: It is recommended to vendor the application's Node.js dependencies Visit http://docs.cloudfoundry.org/buildpacks/node/index.html#vendoring NODE_ENV=production NODE_HOME=/tmp/contents2921570715/deps/0/node NODE_MODULES_CACHE=true NODE_VERBOSE=false NPM_CONFIG_LOGLEVEL=error NPM_CONFIG_PRODUCTION=true -----> Building dependencies Installing node modules (package.json + package-lock.json) > @Former Member/cds-compiler@2.13.8 postinstall /tmp/app/node_modules/@sap/cds-compiler > node lib/fix_antlr4-8_warning.js postinstall cds-compiler: Successfully fixed Antlr's circular dependency > @Former Member-cloud-sdk/core@1.54.0 postinstall /tmp/app/node_modules/@sap-cloud-sdk/core > node postinstall.js ============================================ 🚀 SAP Cloud SDK Announcement The SAP Cloud SDK will release new major versions regularly starting in 2022. A beta version for version 2 is expected to be released in November 2021. We will ensure that upgrading takes less than one day of effort when using our upgrade guide. Read more in our announcement post: https://sap.github.io/cloud-sdk/docs/js/announcing-version-2 Set environment variable SAP_CLOUD_SDK_SILENT to hide this and future announcements. ============================================ added 193 packages from 243 contributors and audited 362 packages in 7.779s 41 packages are looking for funding run `npm fund` for details found 5 high severity vulnerabilities run `npm audit fix` to fix them, or `npm audit` for details **WARNING** Unmet dependencies don't fail npm install but may cause runtime issues See: https://github.com/npm/npm/issues/7494 Contrast Security no credentials found. Will not write environment files. Exit status 0 Uploading droplet, build artifacts cache... Uploading droplet... Uploading build artifacts cache... Uploaded build artifacts cache (5.6M) Uploaded droplet (41.1M) Uploading complete Cell 52223b68-2a95-4e12-9fe8-6703e117c737 stopping instance 95199459-67ec-4413-acd9-80fedb17d6ab Cell 52223b68-2a95-4e12-9fe8-6703e117c737 destroying container for instance 95199459-67ec-4413-acd9-80fedb17d6ab Waiting for app risk-management-srv to start... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... Instances starting... name: risk-management-srv requested state: started isolation segment: trial routes: risk-management-srv-sweet-impala-gz.cfapps.us10.hana.ondemand.com last uploaded: Tue 05 Apr 01:19:10 UTC 2022 stack: cflinuxfs3 buildpacks: isolation segment: trial name version detect output buildpack name nodejs_buildpack 1.7.65 nodejs nodejs type: web sidecars: instances: 0/1 memory usage: 256M start command: npm start state since cpu memory disk details #0 crashed 2022-04-05T01:19:58Z 0.0% 14.1M of 256M 159.8M of 1G Start unsuccessful TIP: use 'cf logs risk-management-srv --recent' for more information FAILED

[jannes_schofeld · Accepted solution]

Hi @Tiwari,

as you can see from the message, you can use command cf logs risk-management-srv --recent to find further information about the issue. I assume this could be related to your SAP HANA Cloud trial instance. The trial version only runs for 24 hours until it gets stopped automatically. 

In your trial account, go to your Cloud Foundry dev space. There, you find the SAP HANA Cloud item in the navigational menu on the left:

Open the Actions menu and select Open in SAP HANA Cloud Central:

If your HANA instance shows status STOPPED, open the Actions menu and select Start to restart your database (the following screenshot shows a running instance, but the instructions apply anyways):

When you have a running database, retry the deployment of your CAP application.

Best regards,

Jannes