Content >

POS Tenant Manager

POS Tenant Manager

After POS has been successfully installed into the EC2 instance, the default tenant must be configured. The default tenant is configured with the sole job of managing other tenants.

There are several tasks to configure the tenant manager database and the tenant manager itself.

a) Database Version

The tenant manager can use either SQL Server 2019 Express or SQL Server 2019 Web. Traffic to this database will be very low.

b) RDS Instance Name

Indicate the name of the RDS instance that will host the tenant manager database.

An example RDS instance name is db-POS-01.

c) Availability Zone

Enter the availability zone (AZ) where the RDS instance is located. Confirm that this AZ matches the AZ of the EC2 instance.

d) Create Database

Create a new database on the RDS instance. The name should be based on the EC2 instance hostname:

  • Follow the pattern POS_host
  • For example, POS_POS01
  • The name should be lower-case.

To access the RDS instance, you may need to configure a rule for your IP address in the SG-POS-OPS security group for the MSSQL port. If so, remember to add your name beside the rule to make it easier to update the rule later if your IP address changes.

e) Create Database User

Create a new database login on the RDS instance’s SQL Server:

  • Specify the login name.
    • The login name should follow the pattern pos_host_user.
    • For example, POS_POS01_user.
  • Use SQL Server authentication.
  • Create a random, secure password.
    • Use the Fusion 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.

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

f) Create Default Tenant

Use your web browser to browse the POS server home page (e.g. You should a Setup page that will configure the default tenant. Enter the following values:

  • Name: a friendly name based on the host name; for example POS 01.
  • Recipe: use POS Manager.
  • Default time zone: set to Dallas/Merida (GMT +5).
  • Database type: SQL Server
  • Table prefix: leave empty.
  • Connection string: set the connection string to the database you created above.
    • Use the full public hostname of the RDS instance as the data source.
    • Use the name of the database you created above.
    • Use the database user and password you created above.
    • Example: Data;Database=POS_POS01;User ID=POS_POS01_user;Password=XXXXXXXXX
  • Super User username: use Administrator
  • Email: use
  • Password: create a random, secure password.
    • Use the Fusion Password Manager to create a secure password.
    • This will be saved later to the password manager.

Before creating the tenant, record your credentials.

See Default Tenant Setup for more information and overview about how to configure the tenant’s default tenant.

g) Record Credentials

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

  • The entry name should follow the pattern host – Tenant Manager.
  • For example, POS01 – Tenant Manager.
  • Record the login username (e.g. Administrator) and password.
  • Set the URL field to the tenant manager URL, e.g.
  • Important: in the Notes field, record the database connection string you used to configure the tenant. This is the only place where the database password is stored!
  • Save the record to the Production Operations collection in the Fusion organization.

Always use the Fusion 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.
i) Verify Installation

Verify that:

  • You can access the default (tenant manager) site via its URL, e.g.
  • You are accessing the site via HTTPS, and there are no SSL certificate errors.
  • You can login to the /admin backend for the default site.
j) Run Setup Guide

Login to the admin console for the new tenant, and run the Setup Guide.

When prompted for organization options, for the tenant role select Tenant Manager.

After successful completion of the tenant manager, the default tenant will be configured so that you create additional tenants – one for each organization that will be supported by the server.