Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser 4 > Installing > Optional configurations > Deploying an external reporting server

Deploying an external reporting server

Table of contents
No headers

To enable clients or employees located outside your network to access reports when your Cloud Cruiser server is behind a firewall, you can deploy an external reporting server. This is an instance of Cloud Cruiser in your DMZ that is able to display reports from your Cloud Cruiser database but cannot run workbooks or batch jobs, preventing it from modifying data if it were compromised. The following diagram shows this architecture:


Diagram of reporting server architecture

Before you begin

  • Install your primary instance of Cloud Cruiser and load some charges into the database so that you have data that can be viewed in a report.
  • If you need to offer Cloud Cruiser Analytics reports to users outside your network, don't install Cloud Cruiser Analytics because this procedure modifies those requirements.
  • Ensure that the computer on which you install this instance is able to access the database server behind your firewall, and is itself accessible by computers on the Internet.

To deploy an external reporting server

  1. Install a second instance on a computer in your DMZ using the same procedure in Installing the Cloud Cruiser application, specifying fictional names for the database, administrator user, and reporting user to ensure that these values are different than those specified during the initial Cloud Cruiser installation. This prevents the installer from overwriting your original Cloud Cruiser database.
    For example, you might use ccdb1 as the database name, and ccadmin1 and ccreport1 as user names.
  2. On the reporting server, open the <installDirectory>\apache-tomcat-7.0.54\webapps\ROOT\WEB-INF\classes\ file, make the following edits, and then save the file:
    • In the jdbc.url line, replace the fictional Cloud Cruiser database name with the actual database name.
    • In the jdbc.username line, replace the fictional Cloud Cruiser administrator username with the actual administrator user name.
    • In the reporting.username line, replace the fictional Cloud Cruiser reporting username with the actual reporting user name.
  3. On the reporting server, edit the file <install_dir>/conf/ and uncomment the following line by removing the # character:
  4. Restart the application server to implement this property change.
    For instructions, see Stopping and starting the application server.
  5. Give the Report User role to each user who will log in to this reporting instance of Cloud Cruiser.
    Though both instances share the same set of users because they share the database where user accounts are stored, only users with this role can log in to the reporting instance. The admin user has the role by default.
    If you need to offer Cloud Cruiser Analytics reports to users outside your network, continue to the next step. Otherwise, you have finished.
  6. Install and configure Cloud Cruiser Analytics with the following modifications to the documented procedures:
    1. Installing Cloud Cruiser Analytics
      Install Cloud Cruiser Analytics Server on a computer in your DMZ.
    2. Configuration in Cloud Cruiser Analytics Server
      1. When setting the trusted hosts, include the IP addresses of both Cloud Cruiser servers.
      2. When opening ports, open the ports to both Cloud Cruiser servers and to client computers both inside and outside your network.
    3. Configuration in the Cloud Cruiser Portal
      Perform this procedure on both Cloud Cruiser instances.
    4. Perform the remaining procedures in Installing and configuring Cloud Cruiser Analytics with no further modifications.
  7. Configure your network firewall to allow the Cloud Cruiser Analytics Server computer to communicate with the Cloud Cruiser database server.

Your external reporting server is ready. Users who also have the Admin or Customer Budget roles can perform the same actions as on a regular Cloud Cruiser instance, but they cannot run workbooks or batch jobs.

Last modified



This page has no classifications.

 (c) Copyright 2017-2020 Hewlett Packard Enterprise Development LP