RHEL: Installing vFabric Components from the VMware YUM Repository

If your guest operating system is Red Hat Enterprise Linux (RHEL), VMware recommends that you use yum to install vFabric components.

After you install the vFabric License Server in your vCenter environment, the high-level steps for installing vFabric components using RPMs are as follows:

  1. Read the important information about using RPMs to install vFabric components.

  2. Install the vFabric repository RPMs so that your yum command can find the vFabric component RPMs.

  3. Perform any required pre-installation tasks.

  4. Install one or more vFabric component from RPM on one or more virtual machines (VM). The vFabric License Server automatically keeps track of the number of VMs on which you install the components.

  5. Perform any required post-Installation tasks.

Important Information About Installing Using RPMs

When you install vFabric components on RHEL from the VMware RPM repository, the components are installed into different directories and are owned by different users in different groups. For example, the vFabric Web Server installation is owned by the root user and the vFabric Hyperic Server installation is owned by the hyperic user, which is a non-interactive user created by the RPM install.

The following table lists the vFabric components that you can install from the VMware RPM repository and their corresponding RPM package name, which you will need when you use the yum install command. The table also includes important post-installation information, such as the installation owner and group, and the directory in which the yum command installed the component. You need this information later when you start to actually use the component.

In the table, the RPM package name for each component does not include the architecture suffix, such as .noarch or .x86_64, but rather, just the base name, which is what you need to install the component.

Table 2. vFabric Components and RPM Package Information

vFabric ComponentRPM Package NameInstallation DirectoryUserGroupNotes
vFabric tc Server (Spring Edition)vfabric-tc-server-standard/opt/vmware/vfabric-tc-server-standardroottc-serverIn addition to features provided in the tc Server Standard Edition package, the vFabric Platform offering (tc Server Spring Edition) includes commercial support for tc Server and Spring Framework, as well as access to Spring Insight Operations.

The RPM install also adds a tc-server non-interactive user that you can use to create tc Runtime instances and so on.

Spring Insight Operations (Dashboard)vfabric-insight-dashboard/opt/vmware/vfabric-tc-server-standard/templates/insight-dashboardroottc-serverSpring Insight (Dashboard) is installed as a template of vFabric tc Server. This means that it has a dependency on tc Server, and if you install Spring Insight (Dashboard) using yum without previously installing tc Server, then the install of Insight will automatically install tc Server for you.

You can use the tc-server non-interactive user to create tc Runtime instances that use the Spring Insight templates; this user is added by the RPM install of tc Server.

Spring Insight Operations (Agent)vfabric-insight-agent/opt/vmware/vfabric-tc-server-standard/templates/insight-agentroottc-serverSpring Insight (Agent) is installed as a template of vFabric tc Server. This means that it has a dependency on tc Server, and if you install Spring Insight (Agent) using yum without previously installing tc Server, then the install of Insight will automatically install tc Server for you.

You can use the tc-server non-interactive user to create tc Runtime instances that use the Spring Insight templates; this user is added by the RPM install of tc Server.

vFabric Web Servervfabric-web-server/opt/vmware/vfabric-web-serverrootroot 
vFabric GemFirevfabric-gemfire/usr/lib/vmware/gemfiregemfiregemfireThe /usr/lib/vmware/gemfire directory is a symbolic link to a sibling versioned directory, such as /user/lib/vmware/vFabric_GemFire_66.
vFabric SQLFirevfabric-sqlfire/opt/vfabric/sqlfiresqlfiresqlfireSQLFire requires a Java JDK or JRE. Either be sure your VM has one already installed, or install one.
vFabric Hyperic (Agent)vfabric-hyperic-agent/opt/hyperic/hyperic-hqee-agenthyperichyperic 
vFabric Hyperic (Server)vfabric-hyperic-server/opt/hyperic/server-currenthyperichypericThe /opt/hyperic/server-current directory is a symbolic link to a sibling versioned directory, such as /opt/hyperic/server-4.6-EE.

You can change the parent /opt/hyperic directory using the HQ_SERVER_INSTALL_PATH property in the properties file. See Pre-Installation Instructions for vFabric Hyperic Server.

You must create a properties file before you can install vFabric Hyperic Server using an RPM. See Pre-Installation Instructions for vFabric Hyperic Server.

vFabric RabbitMQvfabric-rabbitmq-server/user/lib/rabbitmqrabbitmqrabbitmqYou must install Erlang before you can install vFabric RabbitMQ. See Pre-Installation Instructions for vFabric RabbitMQ.

Install the vFabric Repository RPMs

Installing the vFabric repository RPMs makes it easy for you to browse the vFabric RPMs available in the VMware repositories. There are two vFabric repositories, both located on repo.vmware.com:

  • vfabric-5-repo: Contains the vFabric component RPMs that are certified for vFabric 5.

  • vfabric-all-repo: Contains additional vFabric component RPMs that have released after vFabric Platform 5 released, such as maintenance releases of components. These RPMs may not necessarily be certified to work with those of vFabric 5 (stored in the vfabric-5-repo repository). Additionally, the RPMs in vfabric-all-repo might be used by customers who have not bought a vFabric 5 Standard or Advanced license.

If you are using only RPMs certified for vFabric 5 Advanced or Standard, then you install only vfabric-5-repo. If, however, you are upgrading a vFabric component to a version that has not yet been officially certified for vFabric 5, then install both repositories.

Procedure

  1. On the RHEL VM, start a terminal either as the root user or as an unprivileged user using sudo.

  2. Run the rpm command to install vfabric-5-repo, and optionally vfabric-all-repo, from the VMware repository:

    prompt# rpm -Uvh http://repo.vmware.com/pub/rhel5/vfabric/5/vfabric-5-repo-5-2.noarch.rpm
    prompt# rpm -Uvh http://repo.vmware.com/pub/rhel5/vfabric-all/vfabric-all-repo-1-1.noarch.rpm

    You install the vFabric repository RPMs on each RHEL VM on which you want to install one or more vFabric components.

  3. Use the yum search vfabric command to view the list of vFabric components that you can install from the VMware repository. For example (with sample output):

    prompt# yum search vfabric
    
    Loaded plugins: rhnplugin, security
    vfabric-5                                                 | 1.9 kB     00:00 
    vfabric-5/primary_db                                      |  11 kB     00:00     
    ======================================== Matched: vfabric =========================================
    vfabric-5-repo.noarch : vFabric repository configuration
    vfabric-all-repo.noarch : vFabric All Repository Configuration
    vfabric-eula.noarch : vFabric End User License Agreement
    vfabric-gemfire.noarch : VMware vFabric GemFire
    vfabric-sqlfire.noarch : VMware vFabric SQLFire
    vfabric-hyperic-agent.noarch : VMware vFabric Hyperic Agent
    vfabric-hyperic-server.x86_64 : VMware vFabric Hyperic Server
    vfabric-insight-agent.noarch : VMware Spring Insight Agent
    vfabric-insight-dashboard.noarch : VMware Spring Insight Dashboard
    vfabric-rabbitmq-server.noarch : The RabbitMQ server
    vfabric-tc-server-standard.noarch : VMWare vFabric tc Server Standard
    vfabric-web-server.x86_64 : VMWare vFabric Web Server

Pre-Installation Instructions

The following sections describe required pre-installation instructions for some vFabric Components:

If the component you are installing using RPMs is not listed, then there are no pre-installation requirements for it.

Pre-Installation Instructions for vFabric Hyperic Server: Create Properties File

The installation of vFabric Hyperic Server typically requires that a user enter values for a number of configuration properties. To automate this request for input when you install from an RPM, you create a properties file that contains values for all the properties required by the vFabric Hyperic Server installation process.

Hyperic Server stores its meta-data in a database. Hyperic provides an internal PostgreSQL database that you can use for initial testing purposes, but VMware recommends that for production purposes you use a remote external database, such as MySQL or Oracle. See the Hyperic documentation for instructions on setting up an external database for use with Hyperic by searching the vFabric Hyperic X.X section of this Documentation Center.

Procedure
  1. If you want to use an external database (instead of the internal PostgreSQL database) to store Hyperic meta-data, set up the database and make note of the JDBC URL for connecting to the database as well as the database username and password.

    See the vFabric Hyperic documentation for details on how to set up a MySQL or Oracle database for Hyperic use.

  2. From the RHEL VM on which you will install vFabric Hyperic Server, log in as the root user and start a terminal window.

  3. Create a file called vfabric_hyperic_server.properties in the /etc/vmware/vfabric/hyperic directory.

    Important: You must name the file exactly as described, and put it in the exact location, for the RPM installation to work correctly.

  4. Update the file with values for all the properties required by vFabric Hyperic Server installation, as described in the vFabric Hyperic Server Properties table.

    The following example shows a properties file that configures Hyperic Server to use the local built-in PostgreSQL database:

    # Configuration of local built-in Postgresql database
    
    BUILT_IN_POSTGRESQL=yes
    HQ_ACCEPT_EULA=y
    HQ_SERVER_INSTALL_PATH=/opt/hyperic
    HQ_SENDER_EMAIL_ADDRESS=hqadmin@eng.mycompany.com
    HQ_DB_CRYPT_KEY=12345678
    HQ_ADMIN_USER=hqadmin
    HQ_ADMIN_PASSWORD=hqadmin
    HQ_ADMIN_EMAIL_ADDRESS=hqadmin@eng.mycompany.com

    The following example shows a properties file that configures Hyperic Server to use a remote MySQL database rather than the built-in PostgreSQL database:

    # Configuration of a remote MySQL database
    
    BUILT_IN_POSTGRESQL=no
    HQ_ACCEPT_EULA=y
    HQ_SERVER_INSTALL_PATH=/opt/hyperic
    HQ_SENDER_EMAIL_ADDRESS=hqadmin@eng.mycompany.com
    HQ_DB_TYPE=mysql
    HQ_JDBC=jdbc:mysql://10.11.12.1345:3306/hqdb
    HQ_DB_USERNAME=hqadmin
    HQ_DB_PASSWORD=hqadmin
    HQ_DB_CRYPT_KEY=12345678
    HQ_ADMIN_USER=hqadmin
    HQ_ADMIN_PASSWORD=hqadmin
    HQ_ADMIN_EMAIL_ADDRESS=hqadmin@eng.mycompany.com

    The following example shows a properties file that configures Hyperic Server to use a remote Oracle database:

    # Configuration of a remote Oracle database
    
    BUILT_IN_POSTGRESQL=no
    HQ_ACCEPT_EULA=y 
    HQ_SERVER_INSTALL_PATH=/opt/hyperic 
    HQ_SENDER_EMAIL_ADDRESS=hqadmin@eng.mycompany.com 
    HQ_DB_TYPE=oracle 
    HQ_JDBC=jdbc:oracle:thin:@10.11.12.1345:1522:RH19 
    HQ_DB_USERNAME=bobhq 
    HQ_DB_PASSWORD=bobhq 
    HQ_DB_CRYPT_KEY=12345678 
    HQ_ADMIN_USER=hqadmin 
    HQ_ADMIN_PASSWORD=hqadmin 
    HQ_ADMIN_EMAIL_ADDRESS=hqadmin@eng.mycompany.com 

The following table lists all the vFabric Hyperic Server properties that you can include in the properties file.

Table 3. vFabric Hyperic Server Properties

PropertyDescription
BUILT_IN_POSTGRESQLWhether Hyperic Server should use the local built-in PostgreSQL database instead of an external database.

Specify yes or no. If you specify no, make sure you also specify the HQ_DB_TYPE, HQ_JDBC, HQ_DB_USERNAME, and HQ_DB_PASSWORD properties.

HQ_ACCEPT_EULAWhether you accept the terms of the license agreement. Specify y or n.
HQ_SERVER_INSTALL_PATHAbsolute home directory of Hyperic Server, such as /opt/hyperic.
HQ_SENDER_EMAIL_ADDRESSEmail address that Hyperic Server uses as the sender for email addresses, such as hqadmin@eng.mycompany.com.
HQ_DB_CRYPT_KEYEncryption key that Hyperic Server uses to encrypt the database password.
HQ_ADMIN_USERUsername of the initial Hyperic administration user.
HQ_ADMIN_PASSWORDPassword of the initial Hyperic administration user.
HQ_ADMIN_EMAIL_ADDRESSEmail address for the initial Hyperic administration user.
HQ_DB_TYPEType of database server that the Hyperic Server will use. Possible values are postgresql, mysql, or oracle.
HQ_JDBCFull JDBC connection URL for the database used by Hyperic Server, such as jdbc:mysql://10.11.22.3333:3306/hqdb. You specify this property only if you are not using the built-in PostgreSQL database.
HQ_DB_USERNAMEUsername of the user that connects to the database. You specify this property only if you are not using the built-in PostgreSQL database.
HQ_DB_PASSWORDPassword of the user that connects to the database. You specify this property only if you are not using the built-in PostgreSQL database.

Pre-Installation Instructions for vFabric RabbitMQ: Install Erlang

You must install Erlang on the RHEL VM on which you plan to install vFabric RabbitMQ.

Procedure
  1. From the RHEL VM on which you will install vFabric RabbitMQ, log in as the root user and start a terminal window.

  2. Execute the following two commands to set up the Erlang installation:

    prompt# su -c 'rpm -Uvh http://download.fedoraproject.org/pub/epel/5/x86_64/epel-release-5-4.noarch.rpm'
    prompt# wget -O /etc/yum.repos.d/epel-erlang.repo http://repos.fedorapeople.org/repos/peter/erlang/epel-erlang.repo
  3. Install Erlang using the yum install command:

    prompt# yum install erlang

    Enter y at the prompts to start the installation. When the install successfully finishes, you will see a Complete! message.

Install vFabric Components: General Instructions

You install one or more of the vFabric Platform components on one or more virtual machines.

Prerequisites

Procedure

  1. Log in as the root user to the RHEL VM on which you are going to install the vFabric component and start a terminal.

  2. Execute the appropriate yum install component command to install the vFabric component, where component is name of the RPM package for the component.

    For the exact name of each RPM, see Important Information About Installing Using RPMs, or use the output of yum search vfabric.

    For example, to install vFabric tc Server:

    prompt# yum install vfabric-tc-server-standard

    To install the Spring Insight agent and dashboard templates:

    prompt# yum install vfabric-insight-agent vfabric-insight-dashboard

    To install vFabric Web Server:

    prompt# yum install vfabric-web-server

    The yum command begins the install process, resolves dependencies, and displays the packages it plans to install.

    If this is the first time that you install a vFabric component on the VM, the yum command also installs the vfabric-eula RPM and prompts you to accept the VMware license agreement.

    The yum command automatically choses the appropriate RPM package based on your architecture (32- or 64-bit). You can also install the RPM with a particular architecture by specifying the appropriate suffix. For example, to install the 64-bit RPM of vFabric Web Server:

    prompt# yum install vfabric-web-server.x86_64
  3. Enter y at the prompt to begin the actual installation. Depending on the component, you may be asked additional questions; answer as appropriate. If you need more detailed information, see the component documentation.

    If the installation is successful, you will see a Complete! message at the end.

What to do next

Post-Installation Instructions

The following sections describe post-installation instructions for some vFabric Components:

Post-Installation Instructions for tc Server

The yum installation of vFabric tc Server does not automatically create a tc Runtime instance, so you must manually create one before you can start deploying Web applications to it. There are many options to creating a new instance, but this section describes the simplest and quickest way.

Procedure
  1. If you have not already done so, download and install a JDK or JRE on the RHEL VM on which you installed tc Server.

  2. Set the JAVA_HOME environment variable of the tc-server user to point to the JDK installation and update the PATH environment variable to point to the JAVA_HOME/bin directory.

  3. Log in to the RHEL VM on which you installed tc Server as the root user, and then su to the tc-server user:

    prompt# su - tc-server

    You cannot login directly as the tc-server user because interactive login for the tc-server user has been disabled.

  4. Open a terminal window and change to the /opt/vmware/vfabric-tc-server-standard directory:

    prompt$ cd /opt/vmware/vfabric-tc-server-standard
  5. Execute the tcruntime-instance.sh to create a new tc Runtime instance. Use the -i option to specify the full pathname of the directory in which the new instance will be created; be sure the tc-server user can write to this directory. For example:

    prompt$ ./tcruntime-instance.sh create -i /home/tcs/instances myserver
  6. Execute the tcruntime-ctl.sh command to start the new tc Runtime instance. Use the -n option to specify the directory in which you created the instance. For example:

    prompt$ ./tcruntime-ctl.sh -n /home/tcs/instances myserver start
  7. Confirm that the tc Runtime instance is running by invoking its Welcome page in a browser. Use the URL http://host:8080, where host is the name or IP address of the computer on which the tc Runtime instance is running (localhost if local).

What to do next

This section provides minimal information about how to get started with this vFabric component; for detailed information, see the component-specific documentation by clicking on the vFabric tc Server X.X link in the left frame of this Documentation Center.

Post-Installation Instructions for Spring Insight Operations (Agent and Dashboard)

The yum install of Spring Insight Operations (both the agent and dashboard) simply installs Insight templates into the vFabric tc Server installation. If you have not previously installed vFabric tc Server, then the Spring Insight installation also automatically installs tc Server. The yum install does not, however, create a tc Runtime instance, so you must manually create one before you can use Insight.

This section describes the simplest and quickest way to get Spring Insight Operations up and running. It describes how to create a tc Runtime instance that includes the Spring Insight dashboard on one RHEL VM, and then how to create a tc Runtime instance that includes the Spring Insight agent on a different RHEL VM, and to ensure that the agent can communicate with the dashboard.

Procedure

On the RHEL VM on which you want to run the Spring Insight dashboard:

  1. If you have not already done so, download and install a JDK or JRE, version 1.6.

  2. Set the JAVA_HOME environment variable of the tc-server user to point to the JDK installation and update the PATH environment variable to point to the JAVA_HOME/bin directory.

  3. Log in to the RHEL VM on which you want to run the Spring Insight dashboard as the root user, and then su to the tc-server user:

    prompt# su - tc-server

    You cannot login directly as the tc-server user because interactive login for the tc-server user has been disabled.

  4. Open a terminal window and change to the /opt/vmware/vfabric-tc-server-standard directory:

    prompt$ cd /opt/vmware/vfabric-tc-server-standard
  5. Execute the tcruntime-instance.sh to create a new tc Runtime instance that uses the insight-dashboard template. Use the -i option to specify the full pathname of the directory in which the new instance will be created; be sure the tc-server user can write to this directory. For example:

    prompt$ ./tcruntime-instance.sh create mydashboard -i /home/tcs/instances -t insight-dashboard \
    	     -p insight-dashboard.dashboard.jms.bind.uri=tcp://myDashboardServer:21234

    Set myDashboardServer to the hostname or IP address of the RHEL VM on which you are creating the Spring Insight dashboard.

  6. Execute the tcruntime-ctl.sh command to start the new tc Runtime instance. Use the -n option to specify the directory in which you created the instance. For example:

    prompt$ ./tcruntime-ctl.sh -n /home/tcs/instances mydashboard start
  7. Confirm that the tc Runtime instance is running by invoking its Welcome page in a browser. Use the URL http://host:8080, where host is the name or IP address of the computer on which the tc Runtime instance is running (localhost if local).

On the RHEL VM on which you want to run the Spring Insight agent:

  1. If you have not already done so, download and install a JDK or JRE, version 1.6.

  2. Set the JAVA_HOME environment variable of the tc-server user to point to the JDK installation and update the PATH environment variable to point to the JAVA_HOME/bin directory.

  3. Log in to the RHEL VM on which you want to run the Spring Insight agent as the root user, and then su to the tc-server user:

    prompt# su - tc-server

    You cannot login directly as the tc-server user because interactive login for the tc-server user has been disabled.

  4. Open a terminal window and change to the /opt/vmware/vfabric-tc-server-standard directory:

    prompt$ cd /opt/vmware/vfabric-tc-server-standard
  5. Execute the tcruntime-instance.sh to create a new tc Runtime instance that uses the insight-agent template. Use the -i option to specify the full pathname of the directory in which the new instance will be created; be sure the tc-server user can write to this directory. For example:

    prompt$ ./tcruntime-instance.sh create myagent -i /home/tcs/instances -t insight-agent 
    	    -p insight-agent.dashboard.jms.connect.uri=tcp://myDashboardServer:21234

    Set myDashboardServer to the hostname or IP address of the RHEL VM on which you created the Spring Insight dashboard. This is how the Spring Insight agent knows how to connect to the dashboard.

  6. Execute the tcruntime-ctl.sh command to start the new tc Runtime instance. Use the -n option to specify the directory in which you created the instance. For example:

    prompt$ ./tcruntime-ctl.sh -n /home/tcs/instances myagent start
  7. Confirm that the tc Runtime instance is running by invoking its Welcome page in a browser. Use the URL http://host:8080, where host is the name or IP address of the computer on which the tc Runtime instance is running (localhost if local).

  8. Deploy a Web application to the tc Runtime instance on which the Spring Insight agent is running by copying its WAR file into the webapps directory of the instance, such as /home/tcs/instances/myagent/webapps.

Invoke the Spring Insight dashboard in your browser so you can start monitoring the performance of the Web application you deployed to the tc Runtime instance on which the Insight agent is running. To invoke the Insight dashboard, use the URL http://myDashboardServer:8080/insight. Login using the default Insight username/password of spring/insight.

What to do next

This section provides minimal information about how to get started with this vFabric component; for detailed information, see the component-specific documentation by clicking on the vFabric tc Server X.X link in the left frame of this Documentation Center, then on Spring Insight Operations.

Post-Installation Instructions for Web Server

The yum installation of vFabric Web Server does not automatically create a Web Server instance, so you must manually create one before you can start using it to serve up your Web pages.

Procedure
  1. Log in to the RHEL VM on which you installed vFabric Web Server as the root user and open a terminal window.

  2. Change to the /opt/vmware/vfabric-web-server directory:

    prompt# cd /opt/vmware/vfabric-web-server
  3. Run the newserver.pl command to create the new instance; the command prompts you for information about the new server.

    prompt# ./newserver.pl --server=myserver

    In the preceding example, the new instance is called myserver and its server directory is /opt/vmware/vfabric-web-server/myserver.

  4. Enter values for the newserver prompts as the command requests information about your new instance. You can use the default values for many of the prompts, or even leave them blank.

  5. Change to the instance-name/bin server directory, where instance-name refers to the name of the instance:

    prompt# cd myserver/bin
  6. Start the instance using the httpdctl command:

    prompt# ./httpdctl start

    You should see a message as follows:

    Starting Apache: 
    Server started OK
  7. Confirm that the vFabric Web Server instance started by navigating to the http://host:80 URL in your browser, where host refers to the name or IP address of the host computer (you can use localhost if your browser is on the same computer).

    If the instance started correctly, you should see its Welcome page.

What to do next

This section provides minimal information about how to get started with this vFabric component; for detailed information, see the component-specific documentation by clicking on the vFabric Web Server X.X link in the left frame of this Documentation Center.

Post-Installation Instructions for GemFire

The GemFire documentation includes tutorials and sample applications for you to get started with the component. For details, click on the vFabric GemFire X.X link in the left frame of this Documentation Center.

Post-Installation Instructions for SQLFire

  1. If you have not already done so, download and install a JDK or JRE on the RHEL VM on which you installed SQLFire.

  2. On the RHEL VM, start a terminal either as the root user or as an unprivileged user using sudo.

  3. Optionally specify that the vfabric-sqlfire process should automatically start when the operating system starts by running the following command:

    prompt# chkconfig --level 35 vfabric-sqlfire on
  4. Optionally specify the configuration of the vfabric-sqlfire process by editing the file /etc/sysconfig/sqlfire, which is the file sourced by the script that you will later use to start the SQLFire process (/etc/init.d/vfabric-sqlfire.)

    The /etc/sysconfig/sqlfire file includes many comments to help you decide if you need to modify it. The following bullets provide additional pointers:

    • If you do not modify the /etc/sysconfig/sqlfire file but simply use the one installed by default, then the vfabric-sqlfire process starts up a server instance in a multicast configuration.

    • If you want the vfabric-sqlfire process to start up using a locator-based configuration, change the LOCATOR property in the /etc/sysconfig/sqlfire file to local, as shown:

      LOCATOR=local

      This configuration allows a local locator process to start along with a local server instance. To add additional remote locators, add their IP address and port to the LOCATOR_IP_STRING as shown in the configuration file as a commented-out example.

    • If you want to start up only a local locator process and not a local server instance, set the LOCATOR property to locator_only. This sets up a redundant locator configuration; be sure you add the locator IP addresses and port numbers to the LOCATOR_IP_STRING; an example is shown in the configuration file.

    • Finally, set the LOCATOR property to remote if you want to start a local server instance that relies on having locator processes running on one or more remote hosts. Specify these remote hosts using the LOCATOR_IP_STRING property.

  5. Start the processes associated with SQLFire by running the following command:

    prompt# /etc/init.d/vfabric-sqlfire start

    By default, the process uses an evaluation license; if you have purchased a production license, see the SQLFire User's Guide for information about configuring it in the /opt/vfabric/sqlfire/vFabric_SQLFire_10/sqlfire.properties file. The RPM installation process creates a skeleton sqlfire.properties file to get you started.

    To stop, restart, and get status about the processes, pass the stop, restart, and status parameters, respectively, to the /etc/init.d/vfabric-sqlfire script:

    prompt# /etc/init.d/vfabric-sqlfire status

The SQLFire documentation includes tutorials and sample applications for you to get started with the component. For details, click on the vFabric SQLFire X.X link in the left frame of this Documentation Center.

Post-Installation Instructions for RabbitMQ

You must first start the RabbitMQ server to use it. The default configuration for the server is usually adequate to start it.

Procedure
  1. If you have not already done so, install a JDK or JRE (version 1.6) onto the RHEL VM on which you installed RabbitMQ.

  2. Log in to the RHEL VM as the root user and open a terminal window.

  3. Create a link between /usr/java/default and the directory in which you installed the JDK. For example:

    prompt# mkdir /usr/java
    prompt# ln -s /opt/java/jdk1.6.0_23 /usr/java/default

    You perform this step only once.

  4. Become the rabbitmq user using the Linux su command:

    prompt# su - rabbitmq

    You cannot login directly as the rabbitmq user because interactive login for the rabbitmq user has been disabled.

  5. Start and stop the RabbitMQ server using the /sbin/service rabbitmq-server command, passing it the appropriate option. For example:

    prompt# /sbin/service rabbitmq-server start
What to do next

This section provides minimal information about how to get started with this vFabric component; for detailed information, see the component-specific documentation by clicking on the vFabric RabbitMQ X.X link in the left frame of this Documentation Center.

Post-Installation Instructions for Hyperic Server

After you install vFabric Hyperic Server using the yum command, you start it and then invoke the Hyperic user interface in your browser to actually start using it to monitor your resources.

The yum installation of Hyperic Server configured your RHEL VM so that Hyperic Server starts automatically when the VM is booted; in particular, it created a /etc/init.d/hyperic-hq-server init script.

To start the Hyperic server manually, run the following procedure.

Procedure
  1. Log in to the RHEL VM as the root user.

  2. Open a terminal window and execute the /etc/init.d/hyperic-hq-server script, passing it the start parameter:

    prompt# /etc/init.d/hyperic-hq-server start

    The first time Hyperic Server starts it may take a few minutes to initialize, although subsequent startups will be much faster.

  3. Once the Hyperic Server starts, invoke the Hyperic user interface in your browser using the following URL:

    http://host:7080

    where host is the hostname of the RHEL VM on which you just installed Hyperic Server. If you are running your browser from the same computer on which you installed Hyperic Server, you can use localhost:

    http://localhost:7080

    Log in using the default administration username/password of hqadmin/hqadmin; be sure to change the password after you log into the Hyperic UI.

What to do next

This section provides minimal information about how to get started with this vFabric component; for detailed information, see the component-specific documentation by clicking on the vFabric Hyperic X.X link in the left frame of this Documentation Center.

Post-Installation Instructions for Hyperic Agent

The yum installation of Hyperic Agent configured your RHEL VM so that Hyperic Agent starts automatically when the VM is booted; in particular, it created a /etc/init.d/hyperic-hqee-agent init script.

Before you can start the Hyperic Agent, however, you must configure it so it can find the Hyperic Server to which you want it to connect. The following procedure describes how to do this, and then how to start the Agent manually. Subsequently, the Agent will start automatically each time you boot up the VM.

Procedure
  1. If you have not already done so, install a JDK or JRE (version 1.5 or 1.6) onto the RHEL VM on which you installed Hyperic Agent.

  2. As the root user, log in to the RHEL VM on which you installed Hyperic Agent and edit the /etc/init.d/hyperic-hqee-agent file, setting the HQ_JAVA_HOME to home directory of the JDK or JRE you want the agent to use.

  3. Edit the /opt/hyperic/hyperic-hqee-agent/conf/agent.properties file to specify how the Hyperic agent communicates with the server.

    Important: Although there are many properties you can set in this file, this procedure describes only the minimum required for the agent to communicate with your Hyperic Server.

    Uncomment the properties that begin with agent.setup, such as agent.setup.camIP, then set the values of each property as follows:

    • agent.setup.camIP: The address or hostname of the Hyperic Server.

    • agent.setup.camPort: The default value is the standard Hyperic listen port.

    • agent.setup.camSSLPort: The default value is the standard SSL Hyperic listen port.

    • agent.setup.camSecure: Whether you require that the agent use secure communications when contacting Hyperic Server. The default value is "yes" (use SSL).

    • agent.setup.camLogin: The username the agent should use when connecting to the server. If you change the value from the default value ("hqadmin"), make sure that the user account is properly configured on the Hyperic Server.

    • agent.setup.camPword: The password the agent should use, along with the username above, when connecting to the server. Make sure that the password is the one configured in Hyperic for the user account.

    • agent.setup.agentIP: The IP address or hostname that the Hyperic Server uses to contact the Agent. If you leave the default setting (*default*), the Hyperic Agent will detect an IP address on the platform and choose it as its listen address.

    • agent.setup.agentPort: The listen port that the Hyperic uses when it contacts the agent. If you leave the default setting (*default*), the Hyperic Agent will use the default listen port (either 7080 or 7443) as its listen address. If that port is unavailable, the agent will detect a free port and choose it as its listen port.

    • agent.setup.resetupTokens: Specifies whether the agent, at first startup after installation, will create a new token to use to authenticate with the server each time it starts up. Regenerating a token is useful if the Agent cannot connect to the server because the token has been deleted or corrupted.

    • agent.setup.acceptUnverifiedCertificate: Controls whether or not a Hyperic Agent (version 4.6 or later) issues a warning when the Hyperic Server presents an SSL certificate that is not in the agent's keystore and is either self-signed or signed by a different CA than the one that signed the agent's SSL certificate.

    For example:

    agent.setup.camIP=10.111.222.333
    agent.setup.camPort=7080
    agent.setup.camSSLPort=7443
    agent.setup.camSecure=yes
    agent.setup.camLogin=hqadmin
    agent.setup.camPword=hqadmin
    agent.setup.agentIP=*default*
    agent.setup.agentPort=*default*
    agent.setup.resetupTokens=no
    agent.setup.acceptUnverifiedCertificate=yes
  4. Open a terminal window and execute the /etc/init.d/hyperic-hqee-agent script, passing it the start parameter:

    prompt# /etc/init.d/hyperic-hqee-agent start
What to do next

This section provides minimal information about how to get started with this vFabric component; for detailed information, see the component-specific documentation by clicking on the vFabric Hyperic X.X link in the left frame of this Documentation Center.