A custom domain is a unique name that identifies your website. There are scenarios where you do not want to expose the default domain provided by webMethods.io Integration. In such cases, you can customize the default tenant URL or domain and access the tenant using your own domain.
Use custom domains if you want to make your application accessible on your own domain. Custom domains direct requests to your own URL.
How It Works
You can request for a custom domain name for your tenant, for example, if your company domain is abc.com, you can have the domain name as https://subdomain.abc.com. Contact Software AG Global Support for details on how to enable and configure the custom domain capability.
Steps to configure custom domains
Determine the number of domains to be configured for your account and the list of custom domains. The domain names are owned by you.
Decide the SSL certificate needed, which depends on whether you want to protect a single domain, multiple subdomains of a domain, or multiple domain names.
Share the number of domains to be configured for your account and the list of custom domains with Software AG.
Software AG will create a certificate signing request (CSR) and will provide you the details.
Based on the CSR, get the SSL certificates from a Certificate Authority (CA) and determine the number and type of domains you want to be protected by the certificates.
Send the SSL certificates to Software AG to configure the certificates on the custom domain load balancer.
Software AG will send you the CNAME. Using the CNAME, configure your DNS to point to the custom domain load balancer.
After the configuration is complete, you can start using the custom domain to access webMethods.io Integration. Note: Contact Software AG Global Support and the Software AG Cloud Operations teams for information on allowing the custom domain network load balancer (NLB) IPs and the ports to open. Click here for more information.
Checks for existing assets after configuring custom domains
External end points will change after the custom domain is configured, so you need to inform your partners about the new domain.
Verify all assets that expose end point URLs, for example, REST APIs, SOAP APIs, FlowServices over HTTP, webhooks, and so on.
Few assets, for example, SOAP APIs and REST APIs may not work after the custom domain change. Modify or recreate those assets to support the new custom domain for external use.
External authentication mechanisms like OAuth will not be available.
If you are an existing customer, you need to delete the triggers created earlier and create new triggers.
Verify and update the REST Connector and SOAP Connector account details. It is recommended to recreate REST connectors and SOAP connectors with the new custom domain end points.
Reconfigure the webMethods Integration Server settings to use the On-Premises Connector.