Skip to content

ch2-deploy-private-space.adoc

Latest commit

 

History

History
186 lines (155 loc) · 6.09 KB

ch2-deploy-private-space.adoc

File metadata and controls

186 lines (155 loc) · 6.09 KB

Deploying Apps to Private Spaces

You deploy apps to a private space using Runtime Manager.

Deploy an App to a Private Space

partial$select-private-space.adoc . Click Deploy application. . On the Deploy Application page: .. Enter the name of the application.

+

Important
 partial$caveats.adoc .. Select an application file:

+

  • To upload a Mule app JAR file from your system, select Choose file > Upload file.
    File names can contain only letters, numbers, and underscores per guidelines on unique package names.

  • To choose an example app from Anypoint Exchange:

    1. Select Choose file > Import file from Exchange.

    2. On the Get from Exchange page, enter hello in the Search assets by name:

      Get from Exchange page

    3. Click Hello World and then click Select.

  1. Select the name of the private or shared space from the Deployment Target list.

  2. Configure options for deployment:

Configure Endpoints and Paths for the App

For more information, see ch2-config-endpoints-paths.adoc.

To configure endpoints for the app to enable access from the internet:

  1. Click the Ingress tab and specify the following options:

    Endpoint

    • Host: Select the domain, such as cloudhub.io, for the app from the drop-down list.

      Note
      		 If you select cloudhub.io (the default domain), you can’t select a subdomain or path.

      The administrator configures the domains and certificates (TLS context) for the private space. See ps-config-domains.adoc.

      After you select the domain for a private space, you can view the corresponding TLS context by clicking View TLS Context:

    • Subdomain: If the domain you selected includes a wildcard, you can configure the subdomain.

      Subdomains support placeholders. The default subdomain is app-name, which resolves to the name of the app that you specified in the Application Name field when you deploy the app.

    • Path: specifies the URL path to the application endpoint.

      Paths support placeholders.

    • To add an endpoint, click Add Endpoint and specify options.

    • To remove an endpoint, click the X in the endpoint row.

    Note
    		 Depending on the control plane you’re deploying to, the endpoint URL format requires the region suffix before cloudhub.io or not. For applications deployed to the US control plane, don’t add the region suffix, for example: https://.10u6w7.usa-e1.cloudhub.io. For applications deployed to any of the other control planes, add the corresponding region suffix, for example: https://.10u6w7.usa-e1.eu1.cloudhub.io.
    Path Rewrite

    If the HTTP Listener in your app listens on a different path than the path defined in Endpoints:

    1. Enable the Rewrite Request Paths option.

    2. Enter the target path expected by your app.

      Requests sent to your app use the path that you specify here.

      Check these examples to see how the private space rewrites the path:

    Application endpoint 1:

    https://sapi-one-o4azsf.2x9yyp.usa-e2.cloudhub.io/acct

    Path rewrite 1:

    /version1

    Application endpoint 2:

    https://sapi-one-o4azsf.2x9yyp.usa-e2.cloudhub.io/acct/moreInfo

    Path rewrite 2:

    /version1/moreInfo
    TLS Options

    • Forward SSL Session

      Enables SSL forwarding during a session.

      SSL forwarding is mostly used with client authentication. See anypoint-security::enable-client-authentication.adoc. SSL forwarding forwards client certificate details in HTTP request headers so they are available to the application. These fields can identify an authenticated client and allow an application to determine and use the identity.

      The following headers are available:

      Header Name Value

      x-ssl-client-verify

      SUCCESS/FAIL

      x-ssl-issuer

      Client certificate issuer

      x-ssl-client-serial

      Client certificate serial number

      x-ssl-client-dn

      Contents of the client certificate DN field

      x-ssl-client-cert

      Contents of the client certificate

    • Last-Mile Security

      Specifies that TLS termination and decryption for the forwarded HTTPS connections occurs in the application.

      This option requires that the Mule application include an SSL certificate and also requires more CPU resources.

  2. Click Deploy Application to create a new configuration for your application.
⚡