Accessing envrionments

HCL Mosaic environments are dedicated for each customer. Once the environments for a specific customer have been provisioned, they are accessible via a defined set of host names that are unique to each customer and environment.

Environment-specific host names used for admin, developer and practitioner access for building solutions and content on the Mosaic platform, are constructed as follows:

Label	Type	Access URL
dev	Development	dev.cust.aws.now.hclsoftware.cloud
qa	QA	qa.cust.aws.now.hclsoftware.cloud
auth	Authoring	auth.cust.aws.now.hclsoftware.cloud
prod	Production	prod.cust.aws.now.hclsoftware.cloud

where:

cust = unique customer identification label
aws = AWS account identifier in which environments are deployed

All of the provisioned service endpoints within an environment are accessed using the single host name for that environment combined with unique URI context roots and will be shared in the onboarding kit / communication.

For access to production environments by the intended internal and/or external end user population, customer-owned and managed vanity domains (and associated DNS records) will be required. For example, www.mypublicsite.com or myintranet.org, which will then be mapped to the production environment during the go-live transition.

Certificates & Renewals

As part of the onboarding process, you are required to provide HCL Software with the necessary certificates that represent one or more production domains to be used for this purpose.

You are required to maintain and provide renewed certificates to HCL Software, in a timely fashion, as necessary to sustain uninterrupted access and use of the production environment.