This information is only valid for CAST Dashboard ≥ 2.x when using a ZIP file deployment (i.e. without Apache Tomcat).
The following situations require some small changes to the Dashboard deployment process so that each Dashboard deployment does not conflict with another:
- when multiple standalone 2.x Dashboards need to be run from the same server
- when embedded AIP Console Dashboards (from v. 1.25) need to be run on the same machine as standalone 2.x ZIP dashboards
Step 1 - Change the port on which the Dashboard is running
By default the ZIP Dashboards are preconfigured to run on the following ports to accept incoming connections:
If you want to run multiple ZIPs on the same server, you must ensure that each Dashboard uses a unique port. You can change the port in the following file:
Locate the following lines in the file:
server.port line (standalone dashboards only), modify the port number and save the file:
Restart the application to ensure the changes are taken into account.
If you change the port number for your embedded dashboards, you will need to update the configuration in AIP Console, see Administration Center - Settings - Dashboard Integration:
Step 2 - Change Microsoft Windows service name
If you are deploying the dashboards on Microsoft Windows and you intend to run them via a Microsoft Windows service, you must make some changes BEFORE you install the services so that each service is unique. For each service that you want to install, perform the following actions:
Modify the dashboard-service-install.bat file
Open the following file with a text editor:
Change the following lines to something unique, for example, add a digit for each dashboard:
Save the file.
Rename the .exe files to match SERVICE_NAME
Now rename the following .exe files to match EXACTLY the name you chose for SERVICE_NAME in dashboard-service-install.bat:
Step 3 - Run the dashboard-service-install.bat
The final step is to run the following file to install the Microsoft Windows Service for your dashboard:
Ensure that the service has been installed and run it to check that the dashboard launches correctly.