VA2 :) Installation Instructions Host Planning 1. Map out where the following components will be installed. a. Central Server. For simplicity, you can install it on the Siebel Gateway host. If disaster detection is the goal, a server removed from all Siebel components can be used, which requires more hardware. VA2 hosts must be NT4.0 or Windows 2000. On NT the recommended service pack is 6a, the latest available. The Central Server host should have a static IP address. b. LSM – A local server monitor will be installed on each Siebel Application Server. C. The administrative console (MMC) should be installed on the same host machine that is supporting the Central Service. Prerequisites 1. WMI - WMI should be installed on every VA2 Host. a. Windows 2000 - On Windows 2000 the WMI service is installed by default, but not turned on. WMI 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. b. Windows NT (SP 4 or greater) - The WMI components need to be downloaded from Microsoft. http://download.microsoft.com/download/platformsdk/wmicore/1.5/W9XNT4/EN-US/wmicore.EXE If the link does not work, do a search in the download section of msdn.microsoft.com for “WMI core”. Find the download for NT. 2. MMC 1.2 Microsoft Management Console a. MMC 1.2 comes default with Windows 2000 b. MMC 1.2 can be downloaded for NT 4.0 http://support.microsoft.com/default.aspx?scid=/support/mmc/mmcus12.asp 3. Database a. MSSQL Server 7 and 2000 are supported b. Oracle – Oracle 8.1.5 have been tested – any Oracle version will probably work. 4. SMTP a. Your site must have a valid SMTP Server. Microsoft Exchange has a SMTP option built in, but it must be enabled. Your SMTP authentication schema should verify by email address only. Install Steps Central Service 1. Run the 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. 2. Database script – create the VA2 repository database a. MSSQL – run the \VA2\centralservice\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 equivelant user (capable of creating databases) ii. Choose File > Open and browse to the mssql\schmVadmin21.sql file. iii. Press F5 to run the script. The output should indicate the database was successfully created. b. 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. 3. ODBC – Create an ODBC connection to the vadmin21 database 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. This website has a graphic of how to create a System DSN for MSSQL Server. You can follow the instructions, but choose VADMIN21 for the name. http://www.cyonara.com/software/btwin2k/createodbc.html For Oracle, the instructions are very similar. The Microsoft Oracle ODBC driver works if you do not want to install the Oracle Client. (Availible in MDAC). If you do install the Oracle Client, you can use the Oracle supplied ODBC driver. The setup instruction for creating an Oracle ODBC data source is essentially the same as MSSQL. 4. vconfig.txt ( \ VA2\centralservice\bin ) – This configuration file determines which ports and ODBC data source the Central Server uses. Edit and save it in this step. a. The Central Server should have a static IP address and the IP address should be changed to match the Central Server IP address. 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 step 3. d. USERNAME, PASSWORD – must be set to a valid username and password to vadmin21 database created in step 2. 5. Start the Central Server service. 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’s. Check the log files found under the \VA2\centralservice\log directory for any critical errors. 6. siebelsetup.exe ( \ VA2\centralservice\bin ) – This application takes the information from your Siebel environment and imports it into VA2. a. The easiest way to run this application is to copy the siebns.dat file into the centralservice\bin directory. Siebns.dat is found in the (gtwysrvr\ADMIN) directory on your Siebel Gateway server. b. After copying siebns.dat into the centralservice\bin directory, siebelsetup.exe can be run. Examine the Log file (siebelsetup.log) for fatal errors after running. c. Alternatively, the siebelsetup.exe can be started on command line and passed in the full path to the siebns.dat file. LSM 1. LSM – A local Service Monitor must be installed on each Siebel Server host. Run the v2setup.exe for every Siebel Application server. It will install the Local Server Monitor Service. Once the configuration file is edited and the LSM service is started, it will register itself in the VA2 repository. The Central Service Must be installed first for the LSM to register itself to correctly in the Repository. 2. Create LSM ODBC datasource. Every LSM host must have an ODBC SYSTEM data source created on it that is connected to the VA2 repository. See step 3 for the Central Server for instructions on creating ODBC data sources. 3. Edit vconfig.txt (VA2\lsm\bin). This file is the same as the Central Server’s 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 7 must be entered. 4. Start the LSM service. When the LSM service is started, it adds itself to the VA2 repository. MMC 1. VA2 Console install (Run the VA2Console\setup.exe) a. Create ODBC data source for the VA2 Console. If the VA2 Console is to be used on a Central Server or LSM, you can use the already defined ODBC data source. b. Access the console from Start > Programs > Virtual Administrator 2. 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. e. Verify the Siebel and VA2 objects have been created correctly. Post Installation Instructions After installation of the VA2 components, several important steps need be taken before the system is operational. 1. Create a host object for each intended application host or communication server host. YOU MUST ENTER AN ADMINISTRATIVE USERNAME AND PASSWORD FOR EACH HOST THAT DOESN’T HAVE ONE. 2. Create a Communication Server 3. Create an Administrator for each planned VA2 administrator. Associate a communication server with each Administrator. 4. Create a Schedule or series of schedules. Associate administrators with the desired schedules. 5. Import the default Analysis Rules and Statistic Collectors via the MMC console. After these steps are complete, the defined administrators will be capable of receiving notifications. The Central Server should be restarted after these actions.