Viewing Application Endpoints

To view the endpoint of an application:

    Procedure
  1. Log in to TIBCO Control Plane and navigate to the Data Plane details page.
  2. On the Applications tab, click a running TIBCO BusinessWorks Container Edition application from the listed apps.
  3. Click the Endpoints tab. All the endpoints are shown.

The Internal URL is used to invoke endpoints of service applications from another application. For more information, see Application to Application communication using Internal URL.

The app's endpoint visibility can be private or public. By default, all the endpoints are private.

Note: For public endpoints to work over the Nginx ingress, add config use-forwaded-headers to True in Nginx ConfigMap ingress-nginx-controller under Namespace ingress-nginx.

Changing Endpoint Visibility

To change an app's endpoint visibility to private or public:

    Procedure
  1. Log in to TIBCO Control Plane and navigate to the Data Plane details page.
  2. On the Applications tab, click a running TIBCO BusinessWorks Container Edition application from the listed apps.
  3. Click the Endpoints tab.

  4. Click Set Endpoint Visibility to change from Private to Public or vice versa. Select the Ingress Controller Name option that you want to change.
    You are shown a warning that this can cause a service outage for the clients.

  5. Click Save Changes or Cancel.

Note: The Visibility toggle button is now available individually for all Service Port options.

Application to Application communication using Internal URL

You can invoke the endpoints of service applications using the internal URLs.

    Procedure
  1. Go to the service application having an endpoint and select the Internal URL button to copy its internal URL. For example, bw-cldhe2qo25gi896buhs0.bw-qa-pol-tru-app-ns.svc.cluster.local:9473.
  2. Navigate to TIBCO Business Studio for BusinessWorks and create a client application. Configure the Invoke activity or HTTP Client Shared Resource and provide the internal URL and append the service path at the end of the URL. For example, http://bw-cldhe2qo25gi896buhs0.bw-qa-pol-tru-app-ns.svc.cluster.local:9473/resource/test.
  3. Create a container application EAR and deploy the application to the platform and then scale the application.
ResultAfter deploying, the application can invoke the endpoint of a service application.