Consumption Analytics Documentation

Home > Documentation for older versions > Cloud Cruiser Express 3 > Installing Cloud Cruiser Express (public) > Configuring Windows authentication with SQL Server

Configuring Windows authentication with SQL Server

You can use Cloud Cruiser with a Microsoft SQL Server system set for Windows authentication. There are two parts to this configuration: the database connection information and the local account used by Cloud Cruiser’s application server.

To enable Cloud Cruiser to use Windows authentication
  1. If you provided your computer name as the Integrated Security Domain during installation as instructed in Installing the Cloud Cruiser Express application, skip to step 4.
  2. On the machine where Cloud Cruiser is installed open the file <install_dir>/apache-tomcat-7.0.35/webapps/ROOT/WEB-INF/classes/ in a text editor.
  3. At the end of the line that sets the jdbc.url property, append ;domain=<ccServerName> where <ccServerName> is the local name of this machine.
    This tells Tomcat to ignore the jdbc.username and jdbc.password in the file and instead attempt to log in to SQL Server as the user account on this machine that is running the Cloud Cruiser service. For example, if your SQL Server machine is named dbserver5 and your Cloud Cruiser machine is named cloudfinance , your jdbc.url property would be:
  4. Open the Services administrative tool in Windows.
  5. Double-click the Cloud Cruiser service to open its properties, then click the Log On tab.
  6. From Log on as , select This account , then in the adjacent fields provide the username and password of a local user account that has access to your SQL Server database server.
  7. Click OK to save these changes and close the Properties dialog box, then from the Action menu, choose Start .

The application server is started and connects to SQL Server with Windows authentication.

What to do next

Continue to the next section, Registering the REST API endpoint with Windows Azure Pack.

Last modified



This page has no classifications.

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