In the past two years, I wrote a few posts that explained the nature of the managed approuter and when it can be helpful to use this feature (here and here). In parallel, we created a GitHub repository that contains sample projects and diagrams to make the differences between both options more tangible. Overall, there’s a lot of content that explains why it makes sense to favor the managed over the standalone approuter. (I highly recommend that you make yourself familiar with the linked resources above if you don’t know them yet). Once you read the content, you have a good understanding of the managed approuter’s advantages. And with this, it makes sense that the managed option is the default setup for newly generated SAP Fiori apps in the SAP Business Application Studio.
But, naturally, many developers are new to SAP Business Application Studio and SAP BTP, which can cause confusion about the standalone approuter (as they only know the managed approuter). For those developers, I compiled this short FAQ to help them understand the differences when you come “from the other direction”:
Q1: Is the managed approuter a service in SAP BTP?
No, the managed approuter is not a service. It is a feature of various SaaS subscriptions that SAP provides in SAP BTP. Both the SAP Launchpad service and the SAP Cloud Portal service come with that feature. This is why you don’t find the managed approuter in the Discovery Center.
Q2: Why don’t I see my app in the Cloud Foundry space?
A: Cloud Foundry spaces only contain applications that consume runtime memory. HTML5 applications won’t show up here as they are a set of static content files (.html, .js, .css) that are run by the browser. In SAP BTP, HTML5 Applications are stored in HTML5 Application Repository service. During runtime, HTML5 Application files are served to the browser by the managed or standalone approuter.
If you have a standalone approuter, you will see it in the space, unlike the HTML5 Applications hosted in HTML5 Application Repository. These applications can be visualized using HTML5 Applications UI (in the SAP BTP Cockpit) or via cf html5-list.
Q3: I used the default option (managed approuter) when I created the SAP Fiori app, and I could deploy it. But now I get the following error “Error No client with requested id”. (or here)
A: This most likely means you didn’t subscribe to the correct subscription service. As mentioned above, here are two services: The SAP Launchpad Service and the SAP Cloud Portal service, both of which should work for what you want to do. Make sure you are subscribed to these subscriptions. Depending on your account, you might also see service instances with these names. Please don’t use service instances for this; they won’t help you here!
The URL of the managed approuter contains either
cpp (pointing to the SAP Cloud Portal service) or
launchpad(pointing to the SAP Launchpad service). Both segments are substitutable, but you need to verify to use the segment of your enabled subscription.
Q4: Can I change the URL of the managed approuter?
A: Th default URL is determined by the subscription service and your subaccount subdomain. But you can change the URL in production accounts via the custom domain service.
A: Instance-level destinations should be used from now on forward as they avoid subaccount-wide access and enable better mta lifecycle handling. Note that when undeploying with instance-level destination, the destination configurations get deleted as well, unlike subaccounts destinations.
A: You can subscribe to these products just to get managed approuter functionality (no need to model launchpad tiles, etc.); just run the applications from HTML5 Application UI. If you do not want to use Launchpad/Portal because of the cost, consider the cost (application runtime, maintenance, upgrades) of a standalone approuter. We recommend using a standalone approuter only if you need to implement approuter extensibility for some special use cases.
A: The SAP Business Application Studio offers a shortcut for the default option that uses the managed approuter. Look at this video which explains the longer flow (create empty MTA, add managed approuter, add Fiori app). Follow this flow but select the “standalone” approuter when prompted. I also added a few screenshots below that you can follow to see all the needed steps.
Q8: Can I change the URL of the standalone approuter?
A: Yes. The default URL can be customized via the “host” property of the mta.yaml file. The
*.cfapps.eu10.hana.ondemand.com-suffix is usually given, but you can change this as well with a custom domain.
Attachment to question 7:
Now you are ready to build and deploy the project with the standalone approuter.