Content >

POS Tenant

Download PDF

POS Tenant

The final step for POS site installation is to create the POS tenant.

a) POS Version

Ensure the POS version of the new tenant has the same version number as the organization’s other tenants.

b) Create Database User

If applicable, consult with the organization’s IT department to determine if there are security policies that they follow that govern access to their database systems.

If, for example, the organization uses Windows Active Directory for authentication, you should use Active Directory for authentication.

Otherwise, you may need to use SQL Server authentication. If this is the case, it’s good practice to create a new database login on SQL Server that is dedicated for the use of POS:

  • Specify the login name.
    • The login name should follow the pattern POS_siteid_user.
    • For example, POS_corp_user or POS_store1_user.
  • Use SQL Server authentication.
  • Create a random, secure password.
    • Use the Kensium Password Manager to create a secure password.
    • This will be saved later to the password manager.
  • Uncheck Enforce password expiration.
  • Set the default database to the client’s database you just created, e.g POS_POS01.
  • Map the database login to a new user on the client database (with the same name), and give that user dbowner role membership.
  • Record the username and password in the Kensium Password Manager.

The client’s database user should only have access to their client database. The user must not be able to access other client databases.

c) 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 Site ID, e.g. corp or store1.
  • Description – enter the Site Title from the pre-install checklist.
  • Host Name
    • This is the preferred way of identifying the new tenant on the organization’s network.
    • It requires a new A record entry in the organization’s DNS server for the tenant.
    • Set this value if the organization can create a new entry in their DNS server for the tenant.
  • Url Prefix
    • Use this approach if it is not possible nor pragmatic to create a new DNS A record for the tenant.
    • Set the prefix to the site ID, e.g. corp or store1.
  • Host Name – enter the POS Domain Name and Site 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 Register database, using the appropriate database account. This should be available in the Kensium password manager.

The Name (tenant ID) must be correctly set to the site 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 within the organization.

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 and Site ID 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@fusionPOS.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.

d) Record Credentials

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

  • The entry name should follow the pattern organization – SiteId POS.
  • For example, xmsqa1 – corp POS or xmsqa1 – store1 POS.
  • Record the login username (e.g. Administrator) and password.
  • Set the URL field to the client URL, e.g. http://corp or http://store1.
  • 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.

e) 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.
f) Verify Installation

Verify that:

  • You can access the site via its URL, e.g. http://corp.
  • If you are accessing the site via HTTPS, there are no SSL certificate errors.
  • You can login to the /admin backend for the site.
g) Run Setup Guide

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