All docs This doc
Skip to end of metadata
Go to start of metadata

Click a topic to see more information about it:


Create a custom production URL

All applications and services you deploy in WSO2 Integration Cloud have the domain set to wso2apps.com/. If you want to provide a domain name that is more representative of your company, you can  associate a custom domain name with the application .  

 Click to read more...

In the Integration Cloud, your application's production URL takes the format https://<tenant>-<applicationName>-<version>.wso2apps.com/ . The Integration Cloud a ssigns  wso2apps.com  as the domain name to all applications that you create. For example, if you create an application by the name bar and your tenant name is foo, then the production URL of your application will be  bar.foo.wso2apps.com

The original production URL will remain active even if you set up a custom production URL.

Before you (the tenant admin) change the default URL to a custom production URL, go to a d omain registrar and register a custom domain. Then, open the a pplication that you want to change the URL of and cl ick its  Custom URL menu:


Note that you need to wait until the DNS changes have been propagated to add the custom URL. If not, there will be an error.

Back to Top ^


Set the default version

You can mark one version of an application as the default in a group of different versions of the application. A default version can be invoked without specifying the version number in the URL.

 Click to read more...

To set the default version, open your application, click the Settings menu, and click the Default Version tab:


Change the application's privacy

By default, an application you create in WSO2 Integration Cloud is public and accessible via the Internet. In order to secure and limit access to your application, you can mark it private by opening the application and clicking its Settings menu.

 Click to read more...

Here are the available privacy levels you can select from:

  • Public: Endpoints are visible to the Internet via the URL <organization_name>-<application_name>.wso2apps.com. You can also access the public endpoints internally from WSO2 Cloud via the URL <organization_name>-<application_name>.wso2apps.local
  • Private: Endpoints are only visible internally from WSO2 Cloud via the URL <organization_name>-<application_name>.wso2apps.local. You can expose private endpoints to the APIs and WSO2 Identity Cloud but not to the public via the Internet.

    Note that when your application's URLs are private to WSO2 API Cloud, they are resolvable only in the API Cloud.

    Tip: Even when an endpoint is private, other applications deployed in the Cloud can still access it via its URL.

    If you want to block access, implement application-level authentication such as WS security policies for SOAP services, OAuth, JWT, and Basic Auth tokens for REST APIs, WS security policies and custom handlers for data services, interceptors for micro services etc. If you have your own security mechanism for applications, you can implement it and deploy it as a custom image on the Cloud.

To set an application's privacy, open your application, click the Settings menu, and click the Application Privacy tab:

Back to Top ^


Scale your deployment

When you create an application in WSO2 Integration Cloud, only a single instance of that application is deployed in the Cloud. In a typical production setup, you might want to increase the availability of your application by creating multiple instances of it. This way, if one instance fails, the next instance can be made available for the users of the application.

 Click to read more...

To scale your deployment, open your application, click the Settings menu, and click the Scale Deployment tab:

  • No labels