he web application login is tenant specific. Meaning each tenant has a unique login url that the agents go to when then need to log in. The format of the url depends on whether or not a DNS server is being used.
Without DNS
If AheevaCCS V7 is installed in an environment that will relies on IP addresses rather than a DNS address the agents will need to use the format outlined below to navigate to the correct login page for the tenant. The name that is used is the "Domain" field that is defined when you create a tenant.
During installation of AheevaCCS you defined the local IP for the agent web app. If you are not using DNS the agent will need to type the IP and the tenant name as outlined below.
For example:
With DNS
If AheevaCCS V7 is installed in an environment that will rely on a DNS address the agents will need to use the format outlined below to navigate to the correct login page for the tenant. The name that is used is the subdomain which is the "Domain" field that is defined when you create a tenant (see below).
If you are using DNS the agent will need to type the subdomain (which is the "Domain" of the tenant) and the domain (this can be anything you wish) which you assigned in your DNS. From the Agent Web App (AWA) perspective you can assign any domain you wish as long as you point it at the IP of the AWA.
For example:
- In your DNS server you would create an Alias (CNAME) record. For each tenant that you have you will need to add a CNAME record. For example:
- CNAME Example 1: mycompany
- CNAME Example 2: mycompany2
Comments
0 comments
Please sign in to leave a comment.