LCA on Database Server

[Manoj]

Hello,

I wanted to know if it is necessary to install LCA on a database server? Our practice is to keep the database server (Microsoft SQL Server) as pristine as possible which means no third party tool. We do monitor our servers and alert the on call person if the box goes down. So if the required monitoring is in place what is the impact of not having LCA installed on the DB server?

Manoj

[cavagnaro]

You need to install LCA on where Genesys DBServer is installed, not necesarilly the same PC where the SQL Server resides.

[Manoj]

What is the difference? We have all the Genesys databases on SQL Server.

[NDavid]

Genesys DB Server is the Genesys deamon that serves as interface between Genesys Apps and RDBMS.
It is recomended that Genesys DB Server processes run on the say SQL Server machine itself. If you do it this way lca is a must (if nothing else to start dbservers via SCI).

[cavagnaro]

Genesys DBServer is a Genesys component which uses a DAP component to conect to a DB Server (Oracle, SQLServer, Informix, DB2 or Sybase).

Your DBServer (Database server = Oracle, SQLServer, Informix, DB2 or Sybase) is what you have on your physical space, the CPU. It is how you call it.

So :

Genesys DBServer will connect to a DataBase Server (CPU) using configuration given on Genesys DAP.

Genesys DBServer > Genesys DAP > SQL Server

LCA (Local Control Agent) will basically monitor and control the Genesys DBServer (stop/start/status).

[Manoj]

Thanks guys. So basically unless the Genesys DBServer is the same as SQL Server box we do not need LCA on the SQL Server box. Correct?

[cavagnaro]

Yes, your SQL Server can be on CPU A totally alone and Genesys DBServer on CPU B WITH LCA installed.

[unfaced]

customers of my company often install LCA on the DB Hosts (CPU) to monitor the network connection between the Genesys Hosts and the DB Hosts. They do this like a backup Host Controll - but like Tony said is not necessary 

[Manoj]

Thank you very much guys for your quick responses.