The hostname cannot consist of more than 63 characters / Set hostname manually?

[nicorunge]

Hi all,

I deployed a multitenant bookshop application in a provider subaccount and successfully subscribed from a consumer subaccount.

But when setting the route in the provider subaccount, I run into an error.

The reason is our Org Name is 53 characters long.

xxxxxxx-xxxxxxxxxxx-xx-xxxxxxxxxx-xxxxxxxx-xxxxxxxx

The Host Name of the deployed bookshop-srv is even longer (64 characters):

xxxxxxx-xxxxxxxxxxx-xx-xxxxxxxxxx-xxxxxxxx-xxxxxxxx-boo6dfe40d1

When now subscribing from a consumer account, it adds the consumer name in front, which leads to 72 characters.

devcon1-xxxxxxx-xxxxxxxxxxx-xx-xxxxxxxxxx-xxxxxxxx-xxxxxxxx-boo36fb39a7

When I try to set this hostname as route, it leads to the previous shown error.

In the BTP Cockpit, when clicking on "Manage environment instance" and then "Update", I'm not able to change the Instance Name, but at least found this hint via the Info Button.

Seems like, whoever created the Global and Subaccount back then, didn't read this info (or the info did not exist at that point), and now we got a 53 characters long name.

I wonder what are my options? Is it possible to change the Instance Name of a Subaccount? Can I overwrite the hostname in the mta.yaml in someway?
We would like to keep the Subaccount as it already contains some Trust Configurations, destinations, roles etc.

Thankful for any hint!
Regards
Nico

[gregorw]

If you plan to use it for production I would suggest you use SAP Custom Domain Service. It also avoids the need to create the routes manually of via the API.

If it's a development environment I would suggest to re-create the Subaccount as I think it's not possible to change the subdomain name.

[Ranjith]

Dear Gregor Wolf,

We also thought about the scenario. But, it our case the global account was having more characters and client don't want any custom domain in the production env. So, I have used the below approach. Please provide you comment here.

[nicorunge]

Hi gregorw, hi rayyavu,

thank you both for your feedbar. So there are three options:

1. SAP Custom Domain Service
2. Creating a new Subaccount
3. Using a custom handler implementation.

Although option 1 is surely the best option, in my opinion it is way too expensive. At least for us in our current development phase. Option 2 is what I want to prevent, as we would need to recreate our Trust Configurations. And as we would like to stick with the default cap multitenancy implementation, we don't want to implement any custom logic. Especially when it's only needed in this specific subaccount.

I saw here, that you can define your hostname/route via mta.yaml. I tested it and it works. But when subscribing, it is requesting a route with org, space and app id. Of course, this leads to 404 Not found.

I guess when setting the route manually, you also have to change the value for the SUBSCRIPTION_URL in your mta.yaml. But so far I couldn't figure out, how it should look like. Or may be there is something totally different which has to be done.

If this all will not help, we bite the bullet and will create a new subaccount.

best regards

Nico