Customization and Maintenance › Mobile Dashboard Customization › Deploy Mobile Dashboard on a Standalone Server

Deploy Mobile Dashboard on a Standalone Server

By default, the Mobile Dashboard installs with the UI Server and also runs on it. An enterprise with strict firewall and port requirements may need to deploy the Mobile Dashboard manually on a standalone server within a DMZ. In this dual-firewall deployment, the UI Server remains in the protected Intranet, while the Mobile Dashboard is accessible to clients from the Internet. Open ports 7070 and 7403 on the firewall that separates the DMZ from general user access.

Note: You can only deploy Mobile Dashboard on standalone servers that run supported systems. For more information about supported systems, see the Operating System Support section of the Release Notes.

To accomplish this configuration, manually move the Mobile Dashboard installation on the UI Server to the server in the DMZ.

Note: This procedure is only necessary in the special case described.

Follow these steps:

1. Open ports 7070, 7403, 7090, and 7493 on the firewall that separates the UI Server and SA Manager from the DMZ.

   These ports are the default access ports for the SA Manager and UI Server. To change the ports for accessing these components behind the firewall, see Step 6.

2. Stop the CA SOI User Interface service on the intranet UI Server.
3. Create a root directory for the CA SOI files on the Mobile Dashboard server. For example:

   C:\Program Files\CA\SOI
   

4. Copy the content from following directories from the UI Server to the Mobile Dashboard server in the DMZ.

   Note: The listed directories are all relative to the SOI_HOME installation path on the UI Server which you created on the Mobile Dashboard server in Step 3. Create the following intermediate folders on the Mobile Dashboard server, if necessary:

   • jsw\bin
   • jsw\lib
   • jsw\conf
   • jre
   • SamUI\bin
   • SamUI\common
   • SamUI\conf
   • SamUI\registry
   • SamUI\server
   • SamUI\shared

     Important! Do not create intermediate folders for webapps and work subfolders.

5. Copy SOI_HOME\SamUI\webapps\mobile.war from the UI Server to the same location on the Mobile Dashboard server.

   Note: For the sake of compatibility, you can also copy SOI_HOME\SamUI\webapps\ssamobile.war if you maintain an older version.

   • (Optional) If you access the UI Server running in your intranet differently from the intranet and the DMZ, using different addresses/ports, complete the following steps:
   1. Open the SOI_HOME\SamUI\conf\soi_conf\mobile.properties file in a text editor.
   2. Edit the following information as necessary and save and close the file:
      • The name and port in the headlessUrl property for accessing the UI Server from behind the firewall. You can specify HTTP or HTTPS for the protocol, as long as the appropriate ports are open behind the firewall.

        Note: The headlessUrl property is represented as headlessUrl=http://<serverUrl>:<port>/rest (for example, headlessUrl=http://localhost:7070/rest) in the file.

6. Open a command prompt on the Mobile Dashboard server, navigate to SOI_HOME\jsw\bin, and run the following commands:

   SAM_Services.cmd install ui
   

   SAM_Services.cmd start ui
   

   The necessary CA SOI services are installed and started on the Mobile Dashboard server.

7. Start the CA SAM User Interface service on the UI Server.

   The Mobile Dashboard is deployed on a standalone server and configured to communicate with the UI Server and SA Manager behind a firewall.

8. Open port 7403 (or the defined nondefault port for accessing the UI Server) on the firewall that separates the DMZ with the Mobile Dashboard server from general internet access.

   Note: Depending on your network configuration, you may also need to configure Network Address Translation (NAT) to forward requests from the Internet to the server inside a DMZ.

   External clients can now access the Mobile Dashboard from the Internet using the following URL:

   http://MobileDashboardServer:port/mobile
   

   Note: If you configured NAT to forward requests to the Mobile Dashboard server, use the server name and port configured in the NAT configuration in the URL.