;C:\SAP\sapjvm_8\binto the system
connectivity, although it can be configured to use a specific instance. Configuring the connectivity instance
manifest.yamlinto a local file. The template should be copied twice into a production and non production versions.
<company-name>token on line 4 needs to be replaced with your company name in all lowercase without spaces.
random-routeneeds to be removed if deploying to a production space.
Routes__ConnectivityInstancemust contain the instance name of the connectivity service to access in the space the Link app will be deployed.
manifest.yamltemplate will need to be created and configured to match the virtual systems in cloud foundry. Under the env node of the file, configure the routes entries for each sap virtual host. The format for each route is
Routes__<name>__, with an entry for each Token and Url.
cf pushin the directory where the configured
manifest.yamlis located to deploy to cloud foundry. After deployment the application will be accessible as a route in cloud foundry, this route plus the configured token parameter can be used to access the connected SAP system.
cf pushis executed will have all files bundle up and pushed to cloud foundry. Use an empty directory with only the
manifest.yamlfile to avoid unnecessary uploads.
cf logs linkTo view detailed logs uncomment the env node
Logging__LogLevel__Default: Traceby removing the leading
#, the redeploy with
3de65974f59e200ef27e8ecfb84437f7, the deployment to cloud foundry assigned route of
enosix-link.cfapps.us10.hana.ondemand.comthus the url to access the
sap-ecc-devsystem will be:
https://enosix-link.cfapps.us10.hana.ondemand.com/3de65974f59e200ef27e8ecfb84437f7- [sapcc] ->