Message Server 8.5 not able to connect to Log Database using JDBC DAP

[ryusuf]

Hi,

Did anyone face with an issue of Message server 8.5 losing connection to log database. I am setting up message server to write logs to log database without the legacy DBServer approach. I am using the JDBC approach in DAP.

The db_storage option in message server is set to true. The DAP is provided with DB details and is using 'sa' user to connect to the LOG database.

I get the following error in the message server log. Any suggestions would be helpful.

[sup]DBClient ODBC, Copyright (c) 1997-2014 Genesys Telecommunications Labs, Inc.
All Rights Reserved
Db Client version:        8.5.000.21
DB Common part version:    8.5.000.21
Vendor supported versions: "ODBC"
Process ID:                4092
Build on 'i686-winnt-vs8-64'
+0015  Connection to multiserver created, host 'localhost', port '52307', socket '364'
ODBC: id='3.1' req='1' Protocols versions: dbclient='00010004' dbserver='00010004' dblib='00010004'
+0000  Invalid parametr 'dbserver' value '(null)'
+0000  Database Access Point in TKVList:
+0000    section "default":
+0000      "connection_type" = "JDBC"
+0000      "dbengine" = "mssql"
+0000      "Role" = "Main"
+0000      "JdbcDebug" = "false"
+0000      "QueryTimeout" = "0"
+0000      "dbname" = "LOG"
+0000      "username" = "sa"
+0000      "password" = "***"
+0000      "dbcase" = "any"
+0000    section "dbclient":
+0000      "utf8-ucs2" = "false"
+0000      "max-binding-memory" = 250
+0000  000000000058FB60,hDBC=6057104,6057104
+0000  Could not connect to SQL Server using SQL Native Client driver. Attemting default MS SQL Server driver...
+17704  odbcerr: [Microsoft][ODBC SQL Server Driver]Dialog failed

[Microsoft][ODBC SQL Server Driver]Dialog failed
12:07:04.340 Trc 04524 Client 'DbServerThread_app' disconnected
Client MS SQL: 3.1 is being closed. Current numofclients=0
Listener (port id = internal-0-0 fd = 604) is being closed. Checking for clients on listener...
Listener with port id = internal-0-0 has been closed and deleted from list of current ports. Number of db app connections affected: 0
[glow=red,2,300]12:07:04.387 Std 04504 Connection to DB Server 'DAP_LOG_JDBC' at host 'GENCC-DB', port 1433 lost
12:07:04.387 Std 04505 Disconnected from DB Server 'DAP_LOG_JDBC'
[GCSDBStorage.cpp:301] [CGCSDBStorage] Connection with DBCluster lost. Reconnect in 1000 ms
12:07:04.387 Std 11051 Connection with DB Cluster lost[/glow]
[GLMDBStorage.cpp:1284] DEvent:  nMsgID=26 nStatus=8 nRequestID=-1
12:07:04.465 Trc 23001 Message ID 98, type 1101, from 0 should be sent to 1 clients
12:07:04.465 Trc 23002 Message ID 98, type 1101, from 0 sent to all clients with status 0
12:07:04.512 Std 05023 Process './dbclient_msql' stopped
  /./dbclient_msql         
    pid                      = 4092
    id                        = 1
    expiration_time          = 2017-11-27T12:07:34
    client copy              = 0
    DbClient name            = MS SQL: 3.1
12:07:05.450 Trc 04500 Connecting to DB Server 'DAP_LOG_JDBC' at host 'GENCC-DB', port 1433
[GCSDBServer.cpp:104] [CGCSDBServer::connect] ASYNC mode
[GCSDBServer.cpp:126] [CGCSDBServer::connect]  DOpenServerX: login="sa", password="************", dbname="LOG",server=""
12:07:05.465 Std 05022 Process './dbclient_msql' started
GServer: new_client: fd=316, found server=192
'./dbclient_msql' registered; protocol version '1.4' id '4.1'
ODBC: id='4.1' req='-1'
DBClient ODBC, Copyright (c) 1997-2014 Genesys Telecommunications Labs, Inc.
All Rights Reserved
Db Client version:        8.5.000.21
DB Common part version:    8.5.000.21
Vendor supported versions: "ODBC"
Process ID:                1956
Build on 'i686-winnt-vs8-64'
+0015  Connection to multiserver created, host 'localhost', port '52323', socket '348'
ODBC: id='4.1' req='1' Protocols versions: dbclient='00010004' dbserver='00010004' dblib='00010004'
+0000  Invalid parametr 'dbserver' value '(null)'
+0000  Database Access Point in TKVList:
+0000    section "default":
+0000      "connection_type" = "JDBC"
+0000      "dbengine" = "mssql"
+0000      "Role" = "Main"
+0000      "JdbcDebug" = "false"
+0000      "QueryTimeout" = "0"
+0000      "dbname" = "LOG"
+0000      "username" = "sa"
+0000      "password" = "***"
+0000      "dbcase" = "any"
+0000    section "dbclient":
+0000      "utf8-ucs2" = "false"
+0000      "max-binding-memory" = 250
+0000  00000000008BFB60,hDBC=4615312,4615312
+0000  Could not connect to SQL Server using SQL Native Client driver. Attemting default MS SQL Server driver...
+17751  odbcerr: [Microsoft][ODBC SQL Server Driver]Dialog failed

12:07:23.310 Trc 04524 Client 'DbServerThread_app' disconnected
Client MS SQL: 4.1 is being closed. Current numofclients=0
Listener (port id = internal-0-0 fd = 192) is being closed. Checking for clients on listener...
Listener with port id = internal-0-0 has been closed and deleted from list of current ports. Number of db app connections affected: 0
[GLMDBStorage.cpp:1252] Error 30 returned by DBServer
[GLMDBStorage.cpp:1257] [Microsoft][ODBC SQL Server Driver]Dialog failed
12:07:23.326 Std 04504 Connection to DB Server 'DAP_LOG_JDBC' at host 'GENCC-DB', port 1433 lost
12:07:23.326 Std 04505 Disconnected from DB Server 'DAP_LOG_JDBC'
12:07:23.326 Trc 04524 Client 'DbServerThread_app' disconnected
[GCSDBStorage.cpp:301] [CGCSDBStorage] Connection with DBCluster lost. Reconnect in 1000 ms
12:07:23.326 Std 11051 Connection with DB Cluster lost
[GLMDBStorage.cpp:1284] DEvent:  nMsgID=26 nStatus=8 nRequestID=-1
12:07:23.404 Trc 23001 Message ID 99, type 1101, from 0 should be sent to 1 clients
12:07:23.404 Trc 23002 Message ID 99, type 1101, from 0 sent to all clients with status 0
12:07:23.435 Std 05023 Process './dbclient_msql' stopped
  /./dbclient_msql         
    pid                      = 1956
    id                        = 2
    expiration_time          = 2017-11-27T12:07:53
    client copy              = 0
    DbClient name            = MS SQL: 4.1
12:07:24.388 Trc 04500 Connecting to DB Server 'DAP_LOG_JDBC' at host 'GENCC-DB', port 1433
[GCSDBServer.cpp:104] [CGCSDBServer::connect] ASYNC mode
[GCSDBServer.cpp:126] [CGCSDBServer::connect]  DOpenServerX: login="sa", password="************", dbname="LOG",server=""
12:07:24.404 Std 05022 Process './dbclient_msql' started
GServer: new_client: fd=192, found server=332
'./dbclient_msql' registered; protocol version '1.4' id '5.1'
ODBC: id='5.1' req='-1'
DBClient ODBC, Copyright (c) 1997-2014 Genesys Telecommunications Labs, Inc.
All Rights Reserved
Db Client version:        8.5.000.21
DB Common part version:    8.5.000.21
Vendor supported versions: "ODBC"
Process ID:                2800
Build on 'i686-winnt-vs8-64'
+0015  Connection to multiserver created, host 'localhost', port '52339', socket '352'[/sup]

[catanirex]

Do not create a jdbc dap... Create a normal.

[cavagnaro]

  MessageServer support JDBC??

[ryusuf]

Message server 8.5 supports JDBC DAP because as per version 8.5 documentation, Genesys is getting rid of DBServer.

If anyone has done this approach do let me know please.

[Kubig]

MessageServer does not support JDBC at all

[cavagnaro]

[quote author=ryusuf link=topic=10769.msg48969#msg48969 date=1511790568]
Message server 8.5 supports JDBC DAP because as per version 8.5 documentation, Genesys is getting rid of DBServer.

If anyone has done this approach do let me know please.
[/quote]From where did you get this info?

Enviado de meu E6633 usando Tapatalk

[catanirex]

Message Server 8.5 has DBServer functionality built in in its libraries.
You still need to install either Microsoft SQL Server 2005 Native Client 32 or 64 bit or Oracle Client depending on which database server you have.
And then define a normal DAP for MessageServer.

SCI and Administrator still needs to access log db via a dedicated DBServer defined on DAP_Log.
GAX need to have a jdbc DAP pointing to log db.

[ryusuf]

[quote]

From where did you get this info? [/quote]


Hi Cav,

I got it from a friend of mine who attended the framework 8.5 training from Genesys. It did work in their training environment as we know that their VM would be prepacked with all the prerequisites required. And the steps mentioned there was a DAP to be created with connection type JDBC and the database details. After installing message server, initialized the scripts for LOG database and added this JDBC DAP in the connections tab of the message server.

As per the release 8.5, the new application gets rid of DBServer. So based on this, according to him the message server uses JDBC DAP for writing logs to the log database. And in order to view it in the Genesys Administrator, another DAP is required. This DAP will be using DBServer to connect to the database for reading the logs to GA which is still in relase 8.1.

[ryusuf]

[quote author=catanirex link=topic=10769.msg48979#msg48979 date=1511797448]
Message Server 8.5 has DBServer functionality built in in its libraries.
You still need to install either Microsoft SQL Server 2005 Native Client 32 or 64 bit or Oracle Client depending on which database server you have.
And then define a normal DAP for MessageServer.[/quote]

Yes this is what i was thinking on. This Native client needs to be installed on the host where database is present or on the host where message server is present? I have got a SQL server and post this installation do we need to configure anything else apart from the normal DAP?

[quote]
SCI and Administrator still needs to access log db via a dedicated DBServer defined on DAP_Log.
GAX need to have a jdbc DAP pointing to log db.
[/quote]

You are right..

[catanirex]

Native Client is needed on MessageServer host

[Kubig]

The message server does not support JDBC at all to store the log messages.

[ryusuf]

[quote author=Kubig link=topic=10769.msg48985#msg48985 date=1511859577]
The message server does not support JDBC at all to store the log messages.
[/quote]

Hi Kubig,

Maybe my understanding is wrong then. The legacy method of using dbserver to write to the log database works well. But i am trying to utilize the version 8.5 advantage in which dbserver is removed.

Kindly please let me know what is the approach to use the dbserver libraries present in message server to connect to the log database in version 8.5?

And what is the connection type 'JDBC' in the DAP used for?

[cavagnaro]

JDBC is used yes but for some components like UCS or ETL CCA.
I am aware of that idea of a dbserver-less application which is working fine with CfgServer for example, but doesn't mean JDBC is automatically supported. JDBC is used for Java based applications which MessageServer is of course not one of them.
The dbserver-less feature means you don't need to install a separate Dbserver, but still need the DAP as used for it to understand where to connect to


Enviado de meu E6633 usando Tapatalk

[ryusuf]

[quote author=cavagnaro link=topic=10769.msg48990#msg48990 date=1511869605]
JDBC is used yes but for some components like UCS or ETL CCA.
I am aware of that idea of a dbserver-less application which is working fine with CfgServer for example, but doesn't mean JDBC is automatically supported. JDBC is used for Java based applications which MessageServer is of course not one of them.
The dbserver-less feature means you don't need to install a separate Dbserver, but still need the DAP as used for it to understand where to connect to


Enviado de meu E6633 usando Tapatalk
[/quote]

i get it better now. Yes the dbserver-less feature will use the DAP. And in the DAP, we have only two connection types. One is the default connection type which needs the dbserver to be mentioned in the DAP or the JDBC connection type which is dbserver-less and requires only the db details.

So if we have to go with a dbserver-less approach we will have to choose the connection type as JDBC as per what i understood. But then like you mentioned message server is not a java based application then how do we get this working without dbserver? 

[cavagnaro]

No no, dbserver less only means you don't install a separate DBServer, that is it.
Imagine you already installed as in old versions and continue your life as usual.
JDBC is ONLY for JAVA apps, as message server is not java based then JDBC is not supported at all and will not be unless Genesys makes it a Java based application....which is very unlikely


Enviado de meu E6633 usando Tapatalk