Content >

EC2 Tenant

Download PDF

EC2 Tenant

This EC2 instance will host the POS tenant for the installation’s cloud-based operations. The exact nature of these operations depends on the deployment type that was selected for the client:

  • Kensium Hosted – the EC2 instance should operate as the master server for both corporate and cloud operations.
  • Client Hosted – the EC2 instance should operate as the server for cloud operations (the corporate server is located at the client site).

For more information about deployment types, review the internal POS Deployment Scenarios document.

The POS software does not differ depending on the deployment type. However, the features that are enabled in the tenant will differ.

a) POS Version

Enter the version of POS that the client should use. This should normally be the latest production version of the software.

Only use a version other than the latest production version if it is requested by the Kensium services manager.

b) EC2 Hosting Type

There are a few ways that Kensium can host the tenant for the client:

  • Shared – the tenant can be installed on an existing EC2 instance, along with tenants from other clients.
  • Shared (New) – the tenant can be located on an EC2 instance, but it must be provisioned first. Once created, the EC2 instance can also be used to host future client tenants.
  • Dedicated – the tenant should be created on a new EC2 instance. The instance will not be used to host future client tenants.

Dedicated instances should normally not be created. Only create a dedicated instance if it is requested by the Kensium services manager.

c) EC2 Instance Name

Indicate the name of the EC2 instance that will host the tenant. The EC2 instance POS version must match the the POS Version selected for the client.

Depending on the POS Version and EC2 Hosting Type you selected above, and the load on existing EC2 instances, you may need to create a new EC2 instance first.

d) Availability Zone

Enter the availability zone (AZ) where the EC2 instance is located. Confirm that this AZ matches the AZ assigned to the client.

e) Create DNS Entry

Edit the DNS zone file for fusionrms.com, and add an entry for the POS Domain name that was entered in the client pre-checklist.

Once completed, ping the domain to confirm that it resolves to the proper IP address.

f) Create Tenant

Login to the tenant manager admin page of the POS server where the client tenant should be created.

Choose Configuration / Tenants, and then add a new tenant:

  • Name – the tenant ID: enter the Organization ID, e.g. xmsqa1.
  • Description – enter the Site Title from the pre-install checklist.
  • Url Prefix – leave blank.
  • Host Name – enter the POS Domain Name from the pre-install checklist.
  • Recipe – choose POS_Tenant.
  • Database Type – choose SQL Server.
  • Table Prefix – leave blank.
  • Connection string – set to the connection string of the client’s RDS database. This should be available in the Kensium password manager.

The Name (tenant ID) must be correctly set to the organization ID. POS appends this value as the Tenant property to every log message. Only this value will differentiate the log message from other messages that are generated by other tenants on the same POS server.

For SQL Server, the connection string must be configured to support multiple active result sets. The connection string should include the following parameter: MultipleActiveResultSets=True.

Choose Create to create the tenant in an uninitialized state. Then choose Setup to complete the tenant creation – this will display another page to enter additional information:

  • Name – enter the Site Title from the pre-install checklist.
  • Default Time Zone – enter the Time Zone from the pre-install checklist.
  • Super User username: use Administrator
  • Email: use support@fusionrms.com
  • Password: create a random, secure password.
    • Use the Kensium Password Manager to create a secure password.
    • This will be saved later to the password manager.

Before creating the tenant, record your credentials.

g) Record Credentials

Record an entry into the Kensium password manager for the tenant manager credentials:

  • The entry name should follow the pattern client - Cloud RMS.
  • For example, xmsqa1 - Cloud RMS.
  • Record the login username (e.g. Administrator) and password.
  • Set the URL field to the client URL, e.g. https://xmsqa1.fusionrms.com.
  • Save the record to the Client Credentials collection in the Kensium organization.

Always use the Kensium password manager to access client credentials. Do not store or transmit these in files, email or other communications.

h) Complete Tenant Creation

After saving the tenant manager credentials, complete the tenant creation process. You should receive a success message that the tenant has been successfully configured.

If you encounter an error during this process, you can view the error details in the log server. Before retrying the tenant creation, you may also need to manually fix the tenant information.

  • Tenant information is located in the App_Data/tenants.json file.
  • If the tenant you attempted to create is already in this file, you must manually delete the tenant entry in the JSON file, and then restart the web site.
  • You may also need to delete the tenant subfolder, located in the App_Data/Sites folder.
  • Any tables that were created in the tenant database should be deleted. Alternatively, you may recreate the database.
i) Verify Installation

Verify that:

  • You can access the site via its URL, e.g. https://xmsqa1.fusionrms.com.
  • You are accessing the site via HTTPS, and there are no SSL certificate errors.
  • You can login to the /admin backend for the site.
j) Run Setup Guide

Login to the new tenant and run the Setup Guide to complete the installation.

More Info