Log in to the computer on with the tc Server installation where you will run the Insight Dashboard as tcserver. On Unix, if you have disabled interactive login, log in as the root user and use su - tcserver to become the user.

From the VMware Download page, navigate to the VMware vFabric tc Server download page.

Download Spring Insight Operations, for example:

Unpack the Insight Dashboard archive into the templates directory of the directory of the tc Server installation, such that the insight-dashboard directory is a subdirectory of it, for example:

/opt/vmware/vfabric-tc-server-standard-2.7.0.RELEASE/templates/insight-dashboard

Note: If you acquired tc Server as part of vFabric Suite, the dashboard template may already exist in the templates directory, in which case you need not re-install it.

On the RHEL VM where you will install the Dashboard template, start a terminal either as the root user or as an unprivileged user using sudo.

Depending on the version of the vFabric Suite you are using, install the appropriate repository RPMs:

If necessary, use sudo to run the preceding commands if you are not logged in as the root user.

Use the yum search vfabric command to view the list of vFabric components that you can install from the VMware repository, as in the following example. Note the names of the vFabric tc Server, Insight Dashboard, and Insight Agent RPMs.

prompt# yum search vfabric
...
======================================== Matched: vfabric =========================================
vfabric-eula.noarch : VMware vFabric 5.1 End User License Agreement
vfabric-gemfire.noarch : VMware vFabric GemFire
vfabric-hyperic-agent.noarch : VMware vFabric Hyperic Agent
vfabric-hyperic-server.x86_64 : VMware vFabric Hyperic Server
vfabric-insight-agent.noarch : com.springsource.insight.dist.vfabric:agent-rpm
vfabric-insight-dashboard.noarch : com.springsource.insight.dist.vfabric:dashboard-rpm
vfabric-rabbitmq-java-client-bin.noarch : The RabbitMQ Java Client Library
vfabric-rabbitmq-server.x86_64 : The RabbitMQ server
vfabric-sqlfire.noarch : VMware vFabric SQLFire
vfabric-tc-server-standard.noarch : VMware vFabric tc Server Standard
vfabric-web-server.x86_64 : VMware vFabric Web Server

Log in as the root user (or as another user with sudo privileges) to the RHEL VM (which already has tc Server Standard installed) where you are going to install Insight Operations.

Start a terminal.

Use the yum to install the dashboard RPM

prompt# yum install vfabric-insight-dashboard

yum will install the insight-dashboard template in the /opt/vmware/vfabric-tc-server-standard-version/templates directory.

Enter y at the prompt to begin the installation.

If you have not already accepted the VMware license terms you are prompted to, and must do so to continue.

A Complete! message appears when the installation is complete.

In a terminal window, change to the tc Server home directory. For example:

/opt/vmware/vfabric-tc-server-standard-2.7.0.RELEASE/

Create a tc Server instance with tcruntime-instance.sh or tcruntime-instance.bat, using the insight-dashboard template. For example, to create an instance named "myDashboard" on a Unix system, enter the following command:

./tcruntime-instance.sh create myDashboard -t insight-dashboard

(For information about thetcruntime-instance command and supported command options, see the tcruntime-ctl Command Reference section in Getting Started with tc Server. )

Start the Spring Insight Dashboard instance with the tcruntime-ctl.sh or tcruntime-ctl.bat command.

(For information about thetcruntime-ctl command and supported command options, see the tcruntime-ctl Command Reference section in Getting Started with tc Server. )

Open the Insight Dashboard user interface in a web browser at http://myDashboardServer:8080/insight.

Log in using one of the preconfigured user accounts with a username-password combination listed in the following table. (Users with the insight_admin role can use dashboard administrative functions and support tools.)

Edit the CATALINA_HOME/conf/tomcat.users file. This is the initial content of the file:

<?xml version="1.0"?>
<tomcat-users>
    <role rolename="insight"/>
    <role rolename="insight_admin"/>
    <user password="insight"
          roles="insight"
          username="spring"/>
    <user password="insight"
          roles="insight,insight_admin"
          username="admin"/>
</tomcat-users>

Edit or add <user> elements for the users you wish to authenticate, setting the password, roles, and username attributes for each user. Include the insight role for all users and add the insight_admin role for users who should have administrator capabilities.

After saving changes to tomcat.users, restart the Spring Insight Operations Dashboard, using the tcruntime-ctl restart command.

Copy the insight-dashboard-security-ldap-1.8.x.RELEASE.jar and insight-plugin-dashboard-security-ldap.xml files from the extras/ldap directory to the insight/dashboard-plugins/plugin-config/ directory of your Dashboard tc Runtime instance.

For example, enter the following commands, each on a single line without line breaks:

prompt$ cd /opt/vmware/vfabric-tc-server-standard-2.7.0.RELEASE/myDashboard
prompt$ cp extras/ldap/* insight/dashboard-plugins

Remove the default security-tcserver.jar.

prompt$ rm insight/dashboard-plugins/insight-dashboard-security-tcserver-1.8.x.RELEASE.jar

In insight/dashboard-plugins/plugin-config/insight-plugin-dashboard-security-ldap.xml, modify bean contextSource to point to your own LDAP server.

<bean id="contextSource" 
      class="org.springframework.security.ldap.DefaultSpringSecurityContextSource">
  <constructor-arg value="ldap://myOpenLDAPServer:389/dc=springsource,dc=com"/>
  <property name="userDn" value="cn=Manager,dc=springsource,dc=com"/>
  <property name="password" value="secret"/>
</bean>

Add userDN and password properties that the Directory Manager or other user will use to connect to the LDAP server.

<bean id="contextSource" 
      class="org.springframework.security.ldap.DefaultSpringSecurityContextSource">
  <constructor-arg value="ldap://myOpenLDAPServer:389/dc=springsource,dc=com"/>
  <property name="userDn" value="cn=Manager,dc=springsource,dc=com"/>
  <property name="password" value="secret"/>
</bean>

In the insightAuthenticationProvider bean, modify the userDnPatterns property to specify your User Base DN.

<property name="userDnPatterns">
         <list><value>cn={0},ou=Users,o=SpringInsight</value></list>
</property>

Modify the first <constructor-arg> element of the TransformingLdapAuthoritiesPopulator bean to point to your Group Base DN.

<bean class="org.springframework.security.ldap.userdetails.DefaultLdapAuthoritiesPopulator">
  <constructor-arg ref="contextSource"/>
  <constructor-arg value="ou=Groups,o=SpringInsight"/>
  <property name="groupSearchFilter" value="(|(member={0})(member={1}))"/>
</bean>

Set up the two Insight roles by modifying the map element of the second <constructor-arg> element to specify the groups for regular Insight users (Operators) and Insight administrators (Administrators).

<map>
  <entry key="Operators" value="insight"/>
  <entry key="Administrators" value="insight_admin"/>
</map>

Change to the directory where you want to create the keystore, for example CATALINA_BASE/conf.

If you do not already have a keystore file, create one with the following command:

prompt$ keytool -genkey -alias dashboard -keyalg RSA -keystore dashboard.keystore

Enter the requested information at the prompts.

This information is encoded into the certificate the command creates. Make a note of the key password for use in later commands.

The command creates the file dashboard.keystore containing one entry with the alias dashboard.

Export the dashboard certificate.

prompt$ keytool -export -alias dashboard -keystore dashboard.keystore -file dashboard_cert

At the prompt, enter the keystore password.

The file dashboard_cert is created in the current directory.

Set the Java system properties to specify the location of the dashboard.keystore file and the keystore password.

It is easiest to do this in the CATALINA_BASE/bin/setenv.sh script. Edit the setenv.sh script and add these lines above the JAVA_OPTS=... line.

SSL_KEYSTORE="/full/path/to/dashboard.keystore" # e.g. "$CATALINA_BASE/conf/dashboard.keystore"
SSL_KEYSTORE_PW="keystore_password"
SSL_OPTS="-Djavax.net.ssl.keystore=$SSL_KEYSTORE -Djavax.net.ssl.keystorePassword=$SSL_KEYSTORE_PW"

Add the SSL_OPTS environment variable to the JAVA_OPTS variable.

JAVA_OPTS="$JVM_OPTS $AGENT_PATHS $JAVA_AGENTS $JAVA_LIBARARY_PATH $SSL_OPTS"

If the Dashboard keystore is user managed, configure the dashboard's keystore and trust store locations and passwords in each agent's properties file with dashboard.connect.keyStore, dashboard.connect.trustStore, dashboard.connect.keyStorePassword, and dashboard.connect.trustStorePassword. Restart each agent after editing its properties file.