Knowledge Base >> Configure alarmVM to use Non-default SQL Server Instance

Configure alarmVM to use Non-default SQL Server Instance - Confio Article 1611

Confio Article: 1611 Published: Sep 07 2011 5:53 PM
Version: 2.4+ Topic(s): VMware
Product(s): Ignite
Database(s): VMware

Configure alarmVM to use Non-default SQL Server Instance

 

Background

alarmVM uses a SQL Server repository for alarm data storage. The repository configuration settings are found in the files:

  • [program files]\Confio\VMsuite\vms\tomcat\confio_config\repo.properties
  • [program files]\Confio\VMsuite\vms\tomcat\confio_config\repo.create.properties

 

These files have default setting to create a repository database as follows:

  • Instance: In the CONFIO instance on localhost (defined by the repo.host property in repo.properties)
  • User: Uses a sysadmin user to create a "repository user" (credentials for the sysadmin are defined by the repo.user and repo.password properties in repo.properties)
  • Database: Creates an alarmVM main database called "alarmVM".  For SQL Server Express repositories, alarmVM will create "child" databases called "alarmVM_<id>" to store alarm metric data. (defined by the repo.create.database property in repo.create.properties)
  • Files: Datafile and Logfile directories default to the location of the SQL Server master database.
  • Flag: Once the repository has been created, the repo.created property in repo.properties is set to "yes".

  

Using another SQL Server Instance

The simplest way to retarget alarmVM at a different SQL Server Instance is to:

  

  1. Stop the alarmVM service:
  • In the Windows Services application, look for a service called "Confio VM Suite Server"
  • Stop the service
      
  1. Change the following repo.properties values:
  • repo.host=<host name> or <host name>\\<instance name>  (note that you need a double backslash)
  • repo.port=<port number>  (not needed if you specify an instance name)
  • repo.user=<sysadmin user>
  • repo.password=<sysadmin password in plain text>  (note: this will be encrypted during repository creation)
  • (optional) repo.dataFile=<directory to store datafiles>
  • (optional) repo.logFile=<directory to store logfiles>
      
  1. Check the new instance for a database with the same name as the repo.create.database property in repo.create.properties.  If one is found then edit repo.create.properties:
  • repo.create.database=<unique name of "main" database>  (e.g. alarmVM2)
      
  1. Start the "Confio VM Suite Server" service

   

 

How to start over with a new repository in the same SQL Server Instance

The simplest way to create a new repository in the same same SQL Server Instance is to:

  

  1. Stop the alarmVM service:
  • In the Windows Services application, look for a service called "Confio VM Suite Server"
  • Stop the service
      
  1. Change the following repo.properties values:
  • repo.created=no
  • repo.user=<sysadmin user>
  • repo.password=<sysadmin password in plain text>  (note: this will be encrypted during repository creation)
  • (optional) repo.dataFile=<directory to store datafiles>
  • (optional) repo.logFile=<directory to store logfiles>
      
  1. Change the following repo.create.properties value:
  • repo.create.database=<unique name of "main" database>  (e.g. alarmVM2)
      
  1. Start the "Confio VM Suite Server" service

 

 

 

 

Tags: repository setup sql server create repo.propertie alarmVM new repo.create.properties