VA2 J Installation Instructions


Host Planning

1.      Map out where the following components will be installed.

a.       VA2 Database (Repository): Installed on MSSQL, MSDE, Oracle, DB2 or MySql environment. MSDE is recommended. Step by step instructions for installing MSDE for VA2 available here.

b.      Central Server - The VA2 Central Server host should be on a separate machine from the Siebel Gateway and Siebel servers. For testing and development purposes the Central server can be co-located with Siebel components, such as the Siebel Server. The Central Server must be installed on NT, Windows 2000, Windows XP or Windows 2003. If the Central Server does not have a static IP address, the host name should be used in configuration files. Hardware requirements at minimal; 1 300 mhz cpu and 128 MB of RAM. VA2 does use multiple processes, so multiple CPUs will be levarged if present on the host.

c.       LSM: A Local Server Monitor will be installed on each Siebel Application Server.

d.       Siebel SADMIN adminitrative account.

e.      Administrative user: A domain account that has administrative rights to all monitored hosts should be created. The domain user account created for Siebel can usually be reused for these purposes. This administrative user account will be entered in the NT Services for the LSM and Central Service.

f.       The administrative console (MMC) should be installed on the same host machine that is supporting the Central Service.








1.      MMC 1.2+ Microsoft Management Console

a.       MMC 2.+ comes default with Windows 2000, XP, Windows 2003

b.      MMC 1.2 can be downloaded for NT 4.0



2.      Database

a.       MSSQL Server 7 and 2000, and MSDE are supported. MSDE is free, and tested with VA2 in production environments. To minimize DBA work, MSDE is recommended. Step by step instructions for installing MSDE for VA2 availible here.

b.      Oracle  Oracle 8.1.5 have been tested  any Oracle version will probably work.

c.      DB2

c.      MySQL






  1. SMTP  Mail server
    1. Your should  have a valid SMTP Email Server to use the VA2 Communication server.  Communications are to Email VA2 events or forward events to other management systems.  



  1. WMI - WMI should be installed on every VA2 Host.
    1. Windows 2000 - On Windows 2000 the WMI service is installed by default, but may not be enabled. The WMI Service must be turned on and set to Automatic startup on every VA2 host. Navigate to the windows Services, locate the Windows Management Instrumentation Service and set the startup type to Automatic. Also start the service if necessary.
    2. Windows NT (SP 4 or greater) - The WMI components need to be downloaded from Microsoft.


1.      If the link does not work, do a search in the download section of for WMI core. Find the download for NT.


Install Steps


You should have at this point downloaded VA2 ( and unzipped it into a temporary location.  The paths for install below are referring to the unzip location.  The folders in the unzipped directory should include:









Database install instructions - VA2 Repository


  1. Run Database script: create the VA2 repository database from the \dbinstall\[dbtype]\schmVadmin21.sql script.  Use the DB version for your environment. If you dont have a DB environment you can easily use, try the Step by step instructions for installing MSDE for VA2 available here.


    1. MSSQL: run the \dbinstall\mssql\schmVadmin21.sql script from Query Analyzer. Make sure to use a login with sufficient privileges to create a database. A new database will be created called vadmin21.

                                                               i.      Start Query Analyzer: log in with sa or equivalent user (capable of creating databases)

                                                             ii.      Choose File > Open and browse to the \dbinstall\mssql\schmVadmin21.sql file.

                                                            iii.      Press F5 to run the script. The output should indicate the database was successfully created.



    1. Oracle and DB2 may require DBA involvement to install your VA2 repository. The SQL statements necessary to create the tables for Oracle and DB2 are included in the install. Generally, you can provide the DBA with included scripts and ask them to create a repository for you, and provide a username and password so you can set up the ODBC data sources required by VA2. The following steps will may be required for Oracle and DB2:

1.      Create a schema and users for a VA2 database

2.      Create a table space for VA2. (Default 10mb will be sufficient. However, DB usage will vary depending on the number of events generated by the system and the Statistics collected for historical analysis.) Auto extend table spaces are recommended.

3.      Run the scripts to create the tables for VA2, included int the \VA\centralservice\dbinstall\mydatabsetype\schmVadmin21.sql


    1. Oracle: Ask a DBA to run the \VA2\centralservice\dbinstall\oracle\schmVadmin21.sql script to create the appropriate tables. The DBA will have to create an appropriate user and table space.
    2. DB2:  Ask a DBA to run the VA2\centralservice\dbinstall\db2\schmVadmin21.sql script to create the appropriate tables.
    3. MySql: Mysql is the widely used open source fully relational database. VA2 includes Mysql schema statements, and all VA2 components use ANSI standard SQL compatible with Mysql. ODBC drivers can be downloaded for Mysql and will be required for running VA2. The Mysql script may need to be adjusted to change the varchar datatypes to text to support the 2000+ character fields prior to creating the schema.


  1. ODBC:  Create an ODBC connection to the vadmin21 database just created in step 1 on the Central Server machine. The ODBC name is optional, but if you give it the name VADMIN21 it will save a step or two later. MAKE SURE YOU CREATE THE ODBC AS A SYSTEM DSN. A ODBC connection to your Vadmin21 database will have to be created on every host, and every client that uses MMC. Refer to the graphical walkthrough of how to create ODBC Data sources if necessary.




You will want to install the MMC on the same machine targeted for the VA2 Central Service.  You can also install it on any administrators PC. For each machine where you install the VA2 MMC, you will have to create an ODBC data source to connect to the VA2 Repository as noted in the Database section..


1.      VA2 Console install

a.       Run setup.exe in  \va2snapinmmc directory.  Walk through the Setup Steps to install the MMC console.


b.      Access the console from Start > Programs > VA2 MMC.


c.       A VA2 option box will pop up the first time you run it. You must enter a valid ODBC data source and user name and password for the console, created in the database section.


If you are able to successfully set the ODBC password and browse the folders in the VA2 MMC (there will be very little data), you are ready for the next step  install the Central Service.


Central Service


Before installing the Central Service, ensure that you have created the VA2 Repository Database, and you have created an ODBC data source on the VA2 Central Server machine as seen in the steps above.


  1. Run the \centralservice\v2lcentralservice.exe on the Central Server host. This will install the Central Service as a NT Service and create a user directory (default install path is \Program Files\VA2\centralservice). The Central Server is installed under the Local Service Account - this should be changed to a domain user and password who has Administrative Rights to the machine and other machines monitored by VA2.  However, if you do not have an administrative account with these rights, the VA2 service can run with the local account during setup.   Do not start the service until step 5.



  1. vconfig.txt ( c:\program files\VA2\centralservice\bin ) :  This configuration file determines which ports and ODBC data source the Central Server uses. Edit and save it in this step.  Example below are typical values, with some notes after them.



a.       CENTRALSERVER: Change this to be the Machine name of the host or a static IP address. It must match the values in future LSM config files.

b.      The Ports can be left as default values unless there is some network/conflicting application reason you can not use those ports.

c.       VODBC: Set to the ODBC name created in that connects to the VA2 repository.

d.      USERNAME, PASSWORD:  Username and password Created for the VA2 Repository  database.

e.       Set DBTYPE parameter. Valid entries include MSSQL, ORACLE, DB2 and MYSQL. (Default is MSSQL)

f.        Save and close the vconfig.txt file.


  1. Importing Siebel Data


The siebelsetup.exe application takes the information from your Siebel environment and imports it into VA2.  Before you run it you should locate your siebns.dat.  siebns.dat is found in the (\gtwysrvr\ADMIN) directory on your Siebel Gateway server.  You will need you Siebel Username and Password for this step. This Username and Password must have administrative rights in Siebel. Use the SADMIN account - DO NOT USE THE SIEBEL DATABASE OWNER ACCOUNT.


    1. Copy the siebns.dat file into the c:\program files\VA2\centralservice\bin directory.
    2. Run siebelsetup.exe ( c:\program files\VA2\centralservice\bin )
    3. The setup program will ask you for a Siebel Username and Password. 
    4. Alternatively, the siebelsetup.exe can be started on command line and passed in the following parameters. Make sure to se the SADMIN account - DO NOT USE THE SIEBEL DATABASE OWNER ACCOUNT.


    1. Examine the Log file (siebelsetup.log) for fatal errors after running.



  1. Start the Central Server service. Navigate to Start > Settings > Control Panel > Administrative Services > Services. When the Central Server service is started, it adds itself to the VA2 repository. It must be started prior to the installation of the LSM.


  1. Check the log files found under the \VA2\centralservice\log directory for any critical errors. Critical Errors include the failure of TCP/IP port initialization, or ODBC problems. The service will die shortly after it starts if it runs into a critical error.


  1. You can also run the MMC, and verify that there are now Software Management systems imported into the VA2 Repository.  However, no Siebel information will be collected until the LSM is installed and configured.



LSM:  A Local Service Monitor must be installed on each Siebel Server host (or other host monitored by Siebel).  It is responsible for communicating with Siebel, tracking performance and monitoring log files.  It sends its information back to the VA2 repository and the VA2 Central Service for analysis.


1.      Create LSM ODBC datasource to connect to the VA2 repository. 


2.      Run the \lsm\v2lsmsetup.exe for every Siebel Application server. It will install the Local Server Monitor Service. Edit the vconfig.txt file below before starting the LSM agent.


3.      Edit vconfig.txt (c:\program files\VA2\lsm\bin). This file is similar to the Central Servers vconfig.txt. For the LSM, the IP address and Port that the Central Server is running on must be entered. The ODBC data source created in step 2 must be entered.  Most of the parameters wont need to be changed, but make sure you change the CENTRALSERVER parameter to equal the host name or static IP address of the VA2 Central Server.  Also, the ODBC username and password should be set.


    1. The CENTRALSERVER parameter for each LSM must match the CENTRALSERVER parameter created for the Central Service. If the CENTRALSERVER = HOSTA the LSM should set CENTRALSERVER = HOSTA. Do not interchange IP addresses and hostnames.
    2. Modify the port numbers if you modified this when setting up the Central Service, otherwise should not need to be changed.
    3. VODBC: Set to the ODBC name created in step 2 for the LSM machine.
    5. Set DBTYPE parameter. Valid entries include MSSQL, ORACLE, DB2 and MYSQL. (Defalut is MSSQL)
    6. Save and close the vconfig.txt file



4.      Start the LSM agent.  Open the log files in c:\program files\VA2\lsm\log and look for obvious error messages. 


At this point, VA2 should be collecting Siebel information.

Verification Steps


Verify the Siebel and VA2 objects have been created correctly. Open the VA2 MMC.  You should see 2 Software management systems, including a Virtual Administrator 2 system, and Software Management System representing your Siebel system. Under each software management system the objects can be expanded.

The most common install problem is not useing the correct Siebel username and password. The Siebel username should be a SADMIN account, or any administrative account with access to the Siebel Server Administration screens. This Username and Password must have administrative rights in Siebel. Use the SADMIN account - DO NOT USE THE SIEBEL DATABASE OWNER ACCOUNT. If you did not enter a Siebel Username and Password with siebelsetup.exe, need to verify it, or did not enter it correctly, see the setting siebel password guide.


You may want to refer to the MMC verification steps. It has a graphical version of the instructions below. Note that the problem with the Snapin.dll should have been corrected with the current MMC version. MMC verification



Post Installation Instructions


After installation of the VA2 components, several important steps need be taken before the system is operational. You may want to refer to the MMC verification steps before proceeding further: MMC verification


1.      ODBC Datasources  VA2 can access any ODBC data source. The requirement for that is the ODBC Data source is present on the VA2 Central Server machine. VA2 siebelsetup imports an ODBC name to connect to your Siebel environment. For this reason, if your VA2 Central Server Machine is not the same machine as your Siebel Server, you should recreate an ODBC data source on the VA2 Central Server to connect to your Siebel environment. To find out what name of ODBC to use, edit the siebeldata object in VA2. If the MMC console is running on the Central Server, you can verify the ODBC datasource is setup correctly.




2.      If you are using Oracle, read the Oracle notes below. Note, when creating a new ODBC datasource, the VA2 central server should be restarted.




See the documentation and tutorials on the documentation page to begin setting up your VA2 environment.


Oracle Install notes


1.      The ODBC Driver Siebel uses for Oracle systems is provided by Merant Corporation. The license is limited to Siebel and can not be used by VA2. Siebelsetup.exe imports the ODBC definition into the VA2 repository. You should create a new ODBC Data source that connects to your Oracle Siebel environment on the Central Server machine. The Microsoft driver for Oracle works, as well Oracle ODBC driver provided by an Oracle client. Once establishing an ODBC data source using a useable driver, change the Data source imported to use the new ODBC driver.