Administration Guide › Tenant Management › How to Create a Tenant Environment › Deploy a Tenant Environment

Deploy a Tenant Environment

When you deploy a tenant environment, the hosting environment creates all the components that are required for the tenant. This process presupposes a defined hosting environment and hosting container, which are established during the CA CloudMinder installation.

Follow these steps:

1. Log in to the CSP console.
2. Verify that the Environment Base URL uses HTTPS by completing the following steps:
   1. Select Tenants, Manage Hosting Containers.
   2. Select Actions, Modify Hosting Container.
   3. On the Container Profile tab, verify that the Environment Base URL starts with https.

      If the URL begins with http, change the protocol to https, then click Submit.

3. Select Tenants, Manage Tenants.

   A list of tenant that you can administer appears.

4. Click the Create Tenant button.

   The Create Tenant screen appears.

5. Specify the following information for the tenant:

   Hosting Container

   The name of the hosting container created at installation.

   Name

   A friendly name for the tenant.

   Tag

   A unique identifier for a tenant. The tag is never changed, even if the tenant name changes. Tags can only contain lowercase, alphanumeric, and underscore characters; it cannot start with a number. For example, enter bestcola.

   State

   A flag that specifies whether the tenant is available for use. When you select Deploy, the system begins the process of deployment as soon as you save the tenant specification. The state displays as Deploying until the process of deployment completes, and then the state changes to Active.

   When the state is Inactive, nothing is deployed. In this state, you are editing the tenant data record. You can deploy a saved tenant environment at any time.

   Description

   A description for the tenant.

   Logo

   The file location for the tenant logo graphic. The tenant logo graphic appears in the upper-left corner of the Tenant Console. You select a file that is accessible from the local host. The file is uploaded to a system server database.

   Protected URL path

   A unique name that appears in the URL for accessing protected tasks in the tenant environment.

   The private alias name that you enter is appended to the base URL defined during container creation. The combination of the base URL and the private alias forms the URL address where the private environment for this tenant is located. We recommend that you enter the exact value of the tenant tag.

   For example, if you enter bestcola as the environment private alias, the tenant private URL becomes:

   https://<hostname>/iam/im/bestcola

   Users who use this URL to access the tenant environment are required to provide valid login credentials.

   Public URL path

   A unique name that appears in the URL for accessing public tasks in the environment. Public tasks do not require credentials. For example, a user who does not yet have an account can request one by using a public task.

   The public alias name that you enter is appended to the base URL defined during container creation. The combination of the base URL and the public alias forms the URL address where the public environment for this tenant is located. We recommend that you use the following format:

   public/<tag>

   Tag is the exact value of the tenant tag.

   For example, if you enter public/bestcola as the environment public alias, the tenant public URL becomes:

   https://<hostname>/iam/im/public/bestcola

   DSA Management Username

   The DSA management web services user name that is specified during installation of the directory servers.

   DSA Management Password

   The DSA management web services password that is specified during installation of the directory servers.

   Tenant DSA Router Management Username

   The DSA management web services user name that is specified during the installation of the directory router servers. Specify this value only when it is different from the directory servers.

   Tenant DSA Router Management Password

   The DSA management web services password that is specified during the installation of the directory router servers. Specify this value only when it is different from the directory servers.

   IMPS DSA Management Username

   The DSA management web services user name during the installation of the policy servers. Specify this value only when it is different from the directory servers.

   IMPS DSA Management Password

   The DSA management web services password that is specified during the installation of the policy servers. Specify this value only when it is different from the directory servers.

   IMPS Tenant Service Username

   The user name for the web service that is used to deploy tenant provisioning directories. The default is admin, unless this value changes after the installation of the policy servers.

   IMPS Tenant Service Password

   The password for the web service that is used to deploy tenant provisioning directories. This password is the same as the connector server password specified during the installation of policy servers.

   Admin Password

   The password for a system administrator account through which you can administer the tenant environment. The user name for this administrator account is automatically set to cspadmin.

6. Click Submit.

   When active, a tenant environment, deployed with a single user, is available for you to log in.  The URL has the following format:

   <hosting container env base url>/<tenant env alias>
   

   The user name is cspadmin; the password is the administrator password that was specified when the tenant was deployed. You can log in to the environment and can create a named user account for a Tenant administrator.