Cloudhouse Alchemy Licensing and Usage Reporting components require access to certain URLs using the HTTPS protocol (TCP Port 443). The URLs required change depending on which one of the following workflows you follow:
Deploying, Running or Uninstalling Compatibility Packages
When Deploying, Running or Uninstalling a Compatibility Package, the computer on which the Compatibility Package will be deployed, run or uninstalled from, needs to be able to communicate with the following URL over HTTPS:
https://licensing.cloudhouse.com
This allows automatic usage reporting and for the Compatibility Package’s license state to be verified.
When deploying or uninstalling a Compatibility Package, if the connection to the above URL fails, the process stops and an error is displayed and written to the deploymentWorkFlowlog.txt file.
When it is the first time you run the Compatibility Package on any machine (or a token authorising a run cannot be found) and the components cannot contact the above URL then the package will not launch, an error is displayed and written to the runWorkflowLog.txt file.
Packaging, Registering or Unlocking
To Register (Lock) a Compatibility Package for use in production or to Unlock a Compatibility Package for editing, the computer/server needs to to communicate with both of the following URLs over HTTPS, in addition to the ones outlined above:
Verifying Access
You can use the Package Management executable to verify access to the necessary URLs and ports.
- Obtain the standalone Package Management executable by downloading and extracting the zip file: Cloudhouse Package Management Zip.
- Open up a command prompt and run the following command:
{DirectoryToExecutable}/Cloudhouse.Package.Management.exe –verifyExample:
C:/temp/Cloudhouse.Package.Management.exe –verifyIf the connection is valid then the following log lines will show in the console window:
2023-10-17 10:46:07,281 INFO VerificationWorkflow - Verifying connection to licensing servers.
2023-10-17 10:46:07,787 INFO VerificationWorkflow - Licensing connection was successfully verified.