Anyone has a T-Server Installation guide?

[HGinc]

Hi all,

We are in the process of installing a T-Server. We understand that there are series of servers, such as db server, config server, configuration manager, LCA .. etc, need to be installed before the T-Server can work properly.

We haven't found a installation guide from Genesys site, but it seems they should have a document for this complicate task. Anyone know if such document exist?

Could anyone perhaps give us some installation tips?

Thank you,
Alex

[cavagnaro]

You can find this on support site, and if you have access to it, otherwise talk to the people who installed the platform on your site. This task should be done by genesys certified techs or at least with basic training

[HGinc]

I tried looking for it in the support site, but I didn't find a useful document of it. I will look for it again.
No one from Genesys is installing this for us, we are just trying to install this T-Server by ourselves. 

[cavagnaro]

So i guess you have received Genesys training...I find this very strange really. Because if you had received training installing this TServer is part of the training and access to the documents are easy because a CD with all data is delivered, also you get an ID to access to support.genesyslab.com and the documents are easy to find.
Genesys never delivers software to anyone without training, and if you are an end user who is trying to trick your provider then I must warn you that you may face a lot of issues and lost all warranty on your installation. Using TServer will impact directly on your licenses.

[Adam G.]

I agree with Cav. You're better off getting some training or an experienced person to do the job for you. Or even both as you'll learn a lot from an experienced professional. It worries me that you may not even have an a basic design of what you're trying to build.

If your installation is quite small you could try Genesys Express as it installs all your required components using a single installer, but you still need a basic understanding of Genesys to even use it.

Pavel

[HGinc]

Hi cavagnaro,

No, I am not trying to trick anyone here. I am just a developer who is trying to integrate with Genesys T-Server.
We are in Genesys's developer program, and we bought SDK from Genesys as well. (no CD thought, we downloaded the SDK with permission)

Well, I'd like to have a qualified Genesys technician to install the system for me, but my boss asks me to install this, so I have to install it, yeah? 

Anyway, I have installed a MS-SQL 2005 on a box while installed a T-Server and a config server on the other box.
It seems like the config server is having trouble connecting to the MS-SQL database. I think the problem is from the following error messages.

[code]
+0094  Could not connect to SQL Server using SQL Native Client driver. Attemting default MS SQL Server driver...
+0110  odbcerr: [Microsoft][ODBC SQL Server Driver]Dialog failed
+0110  MSG_ERROR status='30' msg='[Microsoft][ODBC SQL Server Driver]Dialog failed '
[/code]

I think the correct way is to let config server connect to the SQL database through SQL Native Client Driver, but I am not quite sure what is missing here.

I have attached the log with the error messages. Any help is appreciated.

Thank you,
Alex

[bcyk]

HGinc


It's sad to know your situation; having very little knowledge on a system but being 'forced' to do.
It sounds like someone arming a knife and is asked to kill enemies with machine guns in a war!

Genesys framework and solutions are great software but quite complex.
Basic understanding on framework is essential.
Installation and configuration wizards fool people that deployment a solution is easy for anyone who types!
The fact is that wizards do help to speed up installation and configuration but it is not all; detail options and third component (e.g., the target PABX in particular) tuning are required to implement a 'working' system.

In Genesys developer program, there should have some 'materials' to cover simulated environment setup and configuration.
If not, it is suggested to get minimum additional training or 'tools'.
I guess your task is focused at client/server applications, the client of T-server. Genesys framework installation and configuration are not the primary business.

The 'bad' news is that simulated switch does not give full event messages as in real switch; the simulated switch is Avaya G3 non-EAS. There are other simulated switches such as Nortel but they are chargeable items. Different T-servers for particular switches/PABXs behave different. Agent mode operations, for examples, are completely different in Avaya, Nortel and Alcatel although same set of Genesys functions with possibly different options values are called.


It is suggested to browse documents "Genesys Rough Guides" posted in this web site.
Relevant documents are
    001 - ROUGH GUIDE TO THE GENESYS SOLUTIONS SUITE v7.x.pdf
    002 - ROUGH GUIDE TO SCI AND MANAGEMENT FRAMEWORK v7.x.pdf
    003 - ROUGH GUIDE TO CME AND SOLUTIONS FRAMEWORK v7.x.pdf
They are named "ROUGH GUDE"; for detail information, you need official Genesys manuals/guides (with correct versions!) for detail configuration.

Manual manuals and materials are copyrighted and cannot be posted here.
Again, you should get required manuals from Genesys or reseller.

In your case, there is configuration error in Configuration layer in which it includes:
    - database server (3-party component; MSSQL in your case)
    - License Manager (3-party component; FlexLM, required for T-server in your case)
    - Valid Genesys License file (you MUST have it to run t-server)
    - Genesys DB server (master configuration db server)
    - Genesys Configuration server
      Client program: Genesys configuration manager, client of Genesys Configuration Server.

[MSSQL] ---- [Genesys DB server] ---- [Genesys configuration server] -----> (Genesys configuration manager)
                                                        |
                                                        +---- [T-server] ----- client programs (via SDK)
Management layer components (SCS, SCI, message server, db server for message server, ....) are skipped here
Media layer: T-server for voice interaction


Genesys DB server:
  - uses TCP/IP protocol to connect to MSSQL database server
        - MSSQL port 1433
  - supports generic main program entry for different database system
  - supports multiple threading (per connected client)
  - reads text configuration options (as in configuration layer)
    --> this is one of check points in your case; [b]file name = dbserver.cfg[/b]


dbserver.cfg
--------------- Start of file -----------
[dbserver]
[color=blue]host=myhost
port=4040
management-port =4041
dbprocesses_per_client=1
dbprocess_name=./dbclient_msql[/color]
#
oracle_name=./dbclient_oracle
informix_name=./dbclient_informix
msql_name=./dbclient_msql
sybase_name=./dbclient_sybase
db2_name=./dbclient_db2
#
connect_break_time=1200
tran_batch_mode=off
#
#---------- dbserver log options ----------
#
[log]
verbose = standard
standard = cfg_dbserver, network
segment = 5MB
buffering = true
expire = 20

# for Management layer components
[lca]
lcaport=4999
#
--------------- End of file -----------


Genesys Configuration server:
  - reads text configuration options (as in configuration layer) 
    --> this is one of check points in your case; [b]file name = confserv.cfg[/b]
  - contains "database connection string" (dbhost, dbserver, dbusername, dbpassword,...)
  - validates configuration requests from Genesys Configuration Manager
  - buffers configurations in memory
  - propogrates configuration changed to ALL connected clients


confserv.cfg
--------------- Start of file -----------
[confserv]
[color=blue]port =2020
management-port =2021
server = cfg_dbserver[/color]
# keep for 32 days; 32 days x 24 x 3600
history-log-keep =2764800
# scan every hour; i.e, 3600 seconds
history-log-scan = 3600
history-log-save = file
history-log-file-size =512000
history-log-file-name =histlog
encryption = false
encoding = utf-8

[log]
verbose = standard
standard = confserv, network
#all = network
print-attributes = true
segment = 5MB
buffering = true
expire = 20


[hca]
schema = none

[[color=blue]cfg_dbserver[/color]]
[color=blue]host =myhost
port =4040
dbengine =mssql
dbserver =mydbserver
dbname =mydb
username =dbusername
password =dbpassword[/color]
server =
reconnect-timeout = 10
response-timeout = 600

[soap]
# for GIS
#port = 2022
#
--------------- End of file -----------



Total costs for proper training and tools will, in the long run, be much smaller than the total time you spend (working in the 'dark').


Good luck

[HGinc]

Hi bcyk,

Eh, I try not to interpret that I am forced into this situation by my boss... 
Yes, I downloaded the ROUGH GUIDES last Thursdays, and got some useful information out of them. (mainly the architecture of the Genesys T-Server)

Anyways, I think we found out the cause of my problem last week. I put the wrong username/password in the confserv.cfg to access MS SQL... =/

Now, we am encountering another problem. It seems like when the conf_server established connection to the dbserver, it sends two SELECT queries to the MS SQL.

[code]
select so.name from sysobjects so where so.type='U' and (so.name = 'CFG_PARAMETERS' or so.name = 'cfg_parameters')
and
select address_line4, address_line5 from cfg_tenant where dbid=1
[/code]

The SQL server returns an error says "invalid object cfg_tenant" on the second query, then conf_server terminates.


Question1:
The MS-SQL server we have does not have any table, so we are wondering if there is a special genesys schema which I need to import to the MS-SQL before the dbserver and confserver can communicate with MS-SQL.

Question2:
We understand that there are several server needs to be installed to make T-Server work. Do we have to install every component to begin with? or can we install one server at a time to ensure one component is working before preceding to another?

I have attached two log files with the problem.

Thank you for your help

[cavagnaro]

Guys, not to be bad or something but I disagree to provide all installation steps. This should be done by some certified Genesys we don't know what many other issues he will face and all this info is given in trainings.
Just my thinking.

[HGinc]

Hey cavagnaro,

I am not asking for a step to step installation guides. I am just asking for help whenever I encounter a problem that I am unable to resolve. I guess the bottom line is "not all company can afford a training"

Judging by your title on the forum, you are probably well known in the forum. And I don't understand why you are denying "the poor" from gaining knowledge..

[cavagnaro]

Oh no no, I like the fact that you like to learn, however if you see in the forum we all have some level of training, unless you are a simple programmer. The fact is that even after you have installed framework comes the part of licensing, connections between components, PBX configuration on Genesys, PBX configuration side, etc etc. It is much much deeper than you are doing. Now the fact that your company has a Genesys is that it is not any company who goes and buys an Asterisk, but bets for high solution and believe me, a bad implementation can be disastrous because later if you need Genesys support they will not give it because you are not a certified. So loosing all support just because your boss is impatient or want to save some bucks (never knew a Genesys sale without an implementation project with it) can be more damage than help. So I would recommend to wait for the specialist to come in, you sit on his side and see how all this is done. Later you will understand my point of view.
I'm always glad to help whenever I can but at this point and in your situation I think it is better to not do it in behalf of your project.

[HGinc]

Yeah, we were thinking the PBX configuration can be a lot more complicated, but we are not going to connect a real PBX to the T-Server. (we don't even have a PBX to use for this project) We are just trying to connect the simulator to the T-Server so the T-Server can generate some events. So we hope it's not necessary to get a trainner yet.

Well, if we eventually failed at installing a T-Server, then so be it, but at least we tried. Does that make more sense?

Thanks

[cavagnaro]

Actually...no.
If no PBX why you have a Genesys? Sorry but too strange to me. And will not even ask about licensing.

[HGinc]

We are not buying Genesys solution, we are buying SDK which integrates with Genesys solution. It's only for developement purposes.
The reason why we want to setup this simulated environment is because we want to see what Genesys events looks like, so we can process those events with our software. Your responded to my other thread, so I thought you know already. 

[victor]

Alex,

where are you at in regards to the installation? Are you still geting tenant error?

Best regards,
Vic