Difference between revisions of "General:Installation"

From Wiki_dbSQWare
Jump to: navigation, search
(Install sources of all modules on focal point)
Line 2: Line 2:
 
=== Prepare archive file of all modules ===
 
=== Prepare archive file of all modules ===
 
'''You must install on an Unix/Linux platform only.'''<br>
 
'''You must install on an Unix/Linux platform only.'''<br>
The unix user must have /bin/ksh as shell.<br><br>
+
The unix user must have /bin/ksh as shell.<br>
  #Create base directory of dbSQWare™
+
<br>
mkdir -p $HOME/dbSQWare
+
  #Download dbSQWare™ archive from [[Downloads | Download the latest stable versions]]
+
  #Move tgz of lastest full version
  #Move zip of lastest full version
+
  cp ~/downloads/dbSQWare_full_*.tgz $HOME/.
  cp ~/downloads/dbSQWare_full_*.zip $HOME/dbSQWare/.
 
 
#Unzip file
 
cd $HOME/dbSQWare
 
unzip dbSQWare_full_*.zip
 
 
#Delete zip file
 
rm -f dbSQWare_full_*.zip
 
 
<br>
 
<br>
  
=== Extract archives of all modules ===
+
=== Extract archive of all modules ===
 
  #gunzip and extract archive of all modules
 
  #gunzip and extract archive of all modules
  for lvsqw_Archive in `ls SQWare*.tgz`
+
  cd $HOME
do
+
gunzip -c dbSQWare_full_*.tgz |tar -xvf -
    lvsqw_Module=$(echo "$lvsqw_Archive"|sed 's,_full_v..*tgz$,,')
 
    mkdir -p $HOME/dbSQWare/$lvsqw_Module
 
    cd $HOME/dbSQWare/$lvsqw_Module
 
    echo
 
    echo "extract $lvsqw_Archive for $lvsqw_Module :"
 
    gunzip -c ../$lvsqw_Archive |tar -xvf -
 
done
 
 
   
 
   
 
  #Delete archive file
 
  #Delete archive file
  cd $HOME/dbSQWare
+
  rm -f $HOME/dbSQWare_full_*.tgz
rm -f expdb*.tgz
 
  
 
You must have:<br>
 
You must have:<br>
Line 38: Line 22:
 
$HOME/dbSQWare/SQWareRepository<br>
 
$HOME/dbSQWare/SQWareRepository<br>
 
$HOME/dbSQWare/SQWareWeb<br>
 
$HOME/dbSQWare/SQWareWeb<br>
 
 
<br>
 
<br>
  

Revision as of 22:18, 1 January 2011

Install sources of all modules on focal point

Prepare archive file of all modules

You must install on an Unix/Linux platform only.
The unix user must have /bin/ksh as shell.

#Download dbSQWare™ archive from  Download the latest stable versions
#Move tgz of lastest full version
cp ~/downloads/dbSQWare_full_*.tgz $HOME/.


Extract archive of all modules

#gunzip and extract archive of all modules
cd $HOME
gunzip -c dbSQWare_full_*.tgz |tar -xvf -

#Delete archive file
rm -f $HOME/dbSQWare_full_*.tgz

You must have:
$HOME/dbSQWare/SQWareCentral
$HOME/dbSQWare/SQWareProduction
$HOME/dbSQWare/SQWareRepository
$HOME/dbSQWare/SQWareWeb

Modules configuration

SQWareRepository

If you want use the full capability of dbSQWare, you have to install it.
If you don't install SQWareRepository you can't use SQWareCentral nor SQWareWeb.
Module SQWareProduction can only run alone.

SQWareRepository for Oracle

Install Oracle schema with script ~/dbSQWare/SQWareRepository/oracle/v*/sql/sqwora_CreateIndicatorsTbsUsers.sql
Install tables with script ~/dbSQWare/SQWareRepository/oracle/v*/sqwora_CreateIndicatorsObjectsFull.sql
Complete table tsqw_Repository with your CMDB.
Sample of insert query:

insert into tsqw_Repository ...


SQWareRepository for Sybase

Create a Sybase database to store CMDB and indicators.
Install tables with script ~/dbSQWare/SQWareRepository/sybase/v*/sqwsyb_CreateIndicatorsObjectsFull.sql
Complete table tsqw_Repository with your CMDB.
Sample of insert query:

insert into tsqw_Repository ...


SQWareRepository for MsSql

Create a MsSql database to store CMDB and indicators.
Install tables with script ~/dbSQWare/SQWareRepository/mssql/v*/sqwmsq_CreateIndicatorsObjectsFull.sql
Complete table tsqw_Repository with your CMDB.
Sample of insert query:

insert into tsqw_Repository ...


SQWareRepository for MySql

Create a MySql database to store CMDB and indicators.
Install tables with script ~/dbSQWare/SQWareRepository/mysql/v*/sqwmys_CreateIndicatorsObjectsFull.sql
Complete table tsqw_Repository with your CMDB.
Sample of insert query:

insert into tsqw_Repository ...


SQWareRepository for Ingres

Create a MySql database to store CMDB and indicators.
Install tables with script ~/dbSQWare/SQWareRepository/ingres/v*/sqwing_CreateIndicatorsObjectsFull.sql
Complete table tsqw_Repository with your CMDB.
Sample of insert query:

insert into tsqw_Repository ...


SQWareCentral

It's the focal point of dbSQWare.
You must install SQWareRepository before installing SQWareCentral.
You must install on an Unix/Linux platform only.
The unix user must have /bin/ksh as shell.

SQWareCentral core

Make a link to current version (change this link to upgrade version).

cd ~/dbSQWare/SQWareCentral
ln -s v1.2 prod

Put variable gvsqw_RootexpdbCentral into your .profile and source of SQWareCentral environnement.

export gvsqw_RootexpdbCentral=$HOME/dbSQWare/SQWareCentral/prod
. $gvsqw_RootexpdbCentral/etc/.profile

Customize variables for your own environnement:
To customize variables contain in $gvsqw_RootexpdbCentral/etc/sqwc_GlobalVar.cfg,
put them into $gvsqw_RootexpdbCentral/etc_cust/sqwc_GlobalVar.cfg.
In general case, you just have to customize gvsqw_Mail_central (email adress to send report).
For help on sqwc_GlobalVar.cfg

SQWareCentral for Oracle

Install an Oracle client and configure it to be able to connect to SQWareRepository for Oracle you have installed.

When connection to SQWareRepository is OK, customize connection variables:
To customize variables contain in $gvsqw_RootexpdbCentral/action/oracle/etc/sqwc_DbRefVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/oracle/etc_cust/sqwc_DbRefVar.cfg.
The user can only have 'select' right on SQWareRepository.
For help on sqwc_DbRefVar.cfg for oracle
To check if connection to SQWareRepository is OK for SQWareCentral, reload environnement and test list generation:

#to reload environnement
reload
#to test list generation
$gvsqw_RootexpdbCentral/action/oracle/lst/sqwc_ListeOracleInstance.ksh

The command should return the instances list that you configured in SQWareRepository for Oracle.

To customize variables contain in $gvsqw_RootexpdbCentral/action/oracle/etc/sqwc_GlobalVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/oracle/etc_cust/sqwc_GlobalVar.cfg.
In general case, you just have to customize gvsqw_UserUniqueOracle if you want to change user who owns SQWareProduction for Oracle on all host.
For help on sqwc_GlobalVar.cfg for oracle

To customize variables contain in $gvsqw_RootexpdbCentral/action/oracle/etc/sqwc_ExpVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/oracle/etc_cust/sqwc_ExpVar.cfg.
In general case, you just have to customize gvsqw_Mail_oracle (email adress to send report).
For help on sqwc_ExpVar.cfg for oracle

After that, you can put in place automatic treatment for Oracle.
You can take example on $gvsqw_RootexpdbCentral/action/oracle/etc/CrontabRef.cfg
Attention, you must first put in place SQWareProduction for Oracle before to collect indicators for example!
To be able to deploy SQWareProduction, you must set up the SSH public key of user which you have installed SQWareCentral into ~/.ssh/authorized_keys of $gvsqw_UserUniqueOracle on all Oracle hosts.
$gvsqw_RootexpdbCentral/action/oracle/lst/sqwc_ListeOracleUnique.ksh should return the host/user list.
To be able to perform centralized commands of SQWareProduction, you must set up the SSH public key of user which you have installed SQWareCentral into ~/.ssh/authorized_keys of users who owns Oracle instances.
$gvsqw_RootexpdbCentral/action/oracle/lst/sqwc_ListeOracleInstance.ksh should return the host/user/instance list.

SQWareCentral for Sybase

Install an Sybase client and configure it to be able to connect to SQWareRepository for Sybase you have installed.

When connection to SQWareRepository is OK, customize connection variables:
To customize variables contain in $gvsqw_RootexpdbCentral/action/sybase/etc/sqwc_DbRefVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/sybase/etc_cust/sqwc_DbRefVar.cfg.
The user can only have 'select' right on SQWareRepository.
For help on sqwc_DbRefVar.cfg for sybase
To check if connection to SQWareRepository is OK for SQWareCentral, reload environnement and test list generation:

#to reload environnement
reload
#to test list generation
$gvsqw_RootexpdbCentral/action/sybase/lst/sqwc_ListeSybaseDataserver.ksh

The command should return the instances list that you configured in SQWareRepository for Sybase.

To customize variables contain in $gvsqw_RootexpdbCentral/action/sybase/etc/sqwc_GlobalVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/sybase/etc_cust/sqwc_GlobalVar.cfg.
In general case, you just have to customize gvsqw_UserUniqueSybase if you want to change user who owns SQWareProduction for Sybase on all host.
For help on sqwc_GlobalVar.cfg for sybase

To customize variables contain in $gvsqw_RootexpdbCentral/action/sybase/etc/sqwc_ExpVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/sybase/etc_cust/sqwc_ExpVar.cfg.
In general case, you just have to customize gvsqw_Mail_sybase (email adress to send report).
For help on sqwc_ExpVar.cfg for sybase

After that, you can put in place automatic treatment for Sybase.
You can take example on $gvsqw_RootexpdbCentral/action/sybase/etc/CrontabRef.cfg
Attention, you must first put in place SQWareProduction for Sybase before to collect indicators for example!
To be able to deploy SQWareProduction, you must set up the SSH public key of user which you have installed SQWareCentral into ~/.ssh/authorized_keys of $gvsqw_UserUniqueSybase on all Sybase hosts.
$gvsqw_RootexpdbCentral/action/sybase/lst/sqwc_ListeSybaseUnique.ksh should return the host/user list.
To be able to perform centralized commands of SQWareProduction, you must set up the SSH public key of user which you have installed SQWareCentral into ~/.ssh/authorized_keys of users who owns Sybase instances.
$gvsqw_RootexpdbCentral/action/sybase/lst/sqwc_ListeSybaseDataserver.ksh should return the host/user/instance list.

SQWareCentral for Mssql

Install an Mssql client and configure it to be able to connect to SQWareRepository for Mssql you have installed.

When connection to SQWareRepository is OK, customize connection variables:
To customize variables contain in $gvsqw_RootexpdbCentral/action/mssql/etc/sqwc_DbRefVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/mssql/etc_cust/sqwc_DbRefVar.cfg.
The user can only have 'select' right on SQWareRepository.
For help on sqwc_DbRefVar.cfg for mssql
To check if connection to SQWareRepository is OK for SQWareCentral, reload environnement and test list generation:

#to reload environnement
reload
#to test list generation
$gvsqw_RootexpdbCentral/action/mssql/lst/sqwc_ListeMssqlInstance.ksh

The command should return the instances list that you configured in SQWareRepository for Mssql.

To customize variables contain in $gvsqw_RootexpdbCentral/action/mssql/etc/sqwc_GlobalVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/mssql/etc_cust/sqwc_GlobalVar.cfg.
In general case, you just have to customize gvsqw_UserUniqueMssql if you want to change user who owns SQWareProduction for Mssql on all host.
For help on sqwc_GlobalVar.cfg for mssql

To customize variables contain in $gvsqw_RootexpdbCentral/action/mssql/etc/sqwc_ExpVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/mssql/etc_cust/sqwc_ExpVar.cfg.
In general case, you just have to customize gvsqw_Mail_mssql (email adress to send report).
For help on sqwc_ExpVar.cfg for mssql

After that, you can put in place automatic treatment for Mssql.
You can take example on $gvsqw_RootexpdbCentral/action/mssql/etc/CrontabRef.cfg
Attention, you must first put in place SQWareProduction for Mssql before to collect indicators for example!
To be able to deploy SQWareProduction, you must set up the SSH public key of user which you have installed SQWareCentral into ~/.ssh/authorized_keys of $gvsqw_UserUniqueMssql on all Mssql hosts.
$gvsqw_RootexpdbCentral/action/mssql/lst/sqwc_ListeMssqlUnique.ksh should return the host/user list.
To be able to perform centralized commands of SQWareProduction, you must set up the SSH public key of user which you have installed SQWareCentral into ~/.ssh/authorized_keys of users who owns Mssql instances.
$gvsqw_RootexpdbCentral/action/mssql/lst/sqwc_ListeMssqlInstance.ksh should return the host/user/instance list.

SQWareCentral for Mysql

Install an Mysql client and configure it to be able to connect to SQWareRepository for Mysql you have installed.

When connection to SQWareRepository is OK, customize connection variables:
To customize variables contain in $gvsqw_RootexpdbCentral/action/mysql/etc/sqwc_DbRefVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/mysql/etc_cust/sqwc_DbRefVar.cfg.
The user can only have 'select' right on SQWareRepository.
For help on sqwc_DbRefVar.cfg for mysql
To check if connection to SQWareRepository is OK for SQWareCentral, reload environnement and test list generation:

#to reload environnement
reload
#to test list generation
$gvsqw_RootexpdbCentral/action/mysql/lst/sqwc_ListeMysqlInstance.ksh

The command should return the instances list that you configured in SQWareRepository for Mysql.

To customize variables contain in $gvsqw_RootexpdbCentral/action/mysql/etc/sqwc_GlobalVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/mysql/etc_cust/sqwc_GlobalVar.cfg.
In general case, you just have to customize gvsqw_UserUniqueMysql if you want to change user who owns SQWareProduction for Mysql on all host.
For help on sqwc_GlobalVar.cfg for mysql

To customize variables contain in $gvsqw_RootexpdbCentral/action/mysql/etc/sqwc_ExpVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/mysql/etc_cust/sqwc_ExpVar.cfg.
In general case, you just have to customize gvsqw_Mail_mysql (email adress to send report).
For help on sqwc_ExpVar.cfg for mysql

After that, you can put in place automatic treatment for Mysql.
You can take example on $gvsqw_RootexpdbCentral/action/mysql/etc/CrontabRef.cfg
Attention, you must first put in place SQWareProduction for Mysql before to collect indicators for example!
To be able to deploy SQWareProduction, you must set up the SSH public key of user which you have installed SQWareCentral into ~/.ssh/authorized_keys of $gvsqw_UserUniqueMysql on all Mysql hosts.
$gvsqw_RootexpdbCentral/action/mysql/lst/sqwc_ListeMysqlUnique.ksh should return the host/user list.
To be able to perform centralized commands of SQWareProduction, you must set up the SSH public key of user which you have installed SQWareCentral into ~/.ssh/authorized_keys of users who owns Mysql instances.
$gvsqw_RootexpdbCentral/action/mysql/lst/sqwc_ListeMysqlInstance.ksh should return the host/user/instance list.

SQWareCentral for Ingres

Install an MySql client and configure it to be able to connect to SQWareRepository for Ingres you have installed.

When connection to SQWareRepository is OK, customize connection variables:
To customize variables contain in $gvsqw_RootexpdbCentral/action/ingres/etc/sqwc_DbRefVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/ingres/etc_cust/sqwc_DbRefVar.cfg.
The user can only have 'select' right on SQWareRepository.
For help on sqwc_DbRefVar.cfg for ingres
To check if connection to SQWareRepository is OK for SQWareCentral, reload environnement and test list generation:

#to reload environnement
reload
#to test list generation
$gvsqw_RootexpdbCentral/action/ingres/lst/sqwc_ListeIngresInstance.ksh

The command should return the instances list that you configured in SQWareRepository for Ingres.

To customize variables contain in $gvsqw_RootexpdbCentral/action/ingres/etc/sqwc_GlobalVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/ingres/etc_cust/sqwc_GlobalVar.cfg.
In general case, you just have to customize gvsqw_UserUniqueIngres if you want to change user who owns SQWareProduction for Ingres on all host.
For help on sqwc_GlobalVar.cfg for ingres

To customize variables contain in $gvsqw_RootexpdbCentral/action/ingres/etc/sqwc_ExpVar.cfg,
put them into $gvsqw_RootexpdbCentral/action/ingres/etc_cust/sqwc_ExpVar.cfg.
In general case, you just have to customize gvsqw_Mail_ingres (email adress to send report).
For help on sqwc_ExpVar.cfg for ingres

After that, you can put in place automatic treatment for Ingres.
You can take example on $gvsqw_RootexpdbCentral/action/ingres/etc/CrontabRef.cfg
Attention, you must first put in place SQWareProduction for Ingres before to collect indicators for example!
To be able to deploy SQWareProduction, you must set up the SSH public key of user which you have installed SQWareCentral into ~/.ssh/authorized_keys of $gvsqw_UserUniqueIngres on all Ingres hosts.
$gvsqw_RootexpdbCentral/action/ingres/lst/sqwc_ListeIngresUnique.ksh should return the host/user list.
To be able to perform centralized commands of SQWareProduction, you must set up the SSH public key of user which you have installed SQWareCentral into ~/.ssh/authorized_keys of users who owns Ingres instances.
$gvsqw_RootexpdbCentral/action/ingres/lst/sqwc_ListeIngresInstance.ksh should return the host/user/instance list.