" /> debuging SOAP request - Genesys CTI User Forum

Author Topic: debuging SOAP request  (Read 8174 times)

Offline Timur Karimov

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: 2
debuging SOAP request
« on: June 11, 2008, 11:22:50 AM »
Advertisement
Hi All

Can anyone describe me step-by-step how-to can i debug my URS strategy with SOAP-request object ?
What i try already:
turn on debug level in "log\verbose" option in my URS application object
create "web\html_log_file" option in my URS application object
create "web\html_log_file" option in my URS application object
create "web\xml_log_file" option in my URS application object

In IRD create simple test strategy what use one SOAP request to test web-services.

But one what i see - it's a single line in main URS log file
"20:09:55.393_I_I_007201946e629037 [07:39] HERE IS XDATA
    _I_E_007201946e629037 [09:04] error in strategy: 0015 Closed server
    _I_I_007201946e629037 [09:04] ASSIGN: __WEBReturn(SCRIPT) <- LIST: list
"
of course i see more another log-message, but only it about SOAP.
not a html_log_file or xml_log_file creating =( and web-services log-file complete empty too=(
what i do wrong? and waht can i do to start working my SOAP-request from URS strategy?
i will be happy even in my web-services log file i can see any request from URS.

WBR Timur I. Karimov

Offline S

  • Full Member
  • ***
  • Posts: 135
  • Karma: 1
Re: debuging SOAP request
« Reply #1 on: June 11, 2008, 01:34:12 PM »
_I_E_007201946e629037 [09:04] error in strategy: 0015 Closed server

what is that? is the webserver, you are sending these requests, running? Did u check its logs too?

Offline Timur Karimov

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: 2
Re: debuging SOAP request
« Reply #2 on: June 11, 2008, 02:10:25 PM »
[quote author=S link=topic=3051.msg12373#msg12373 date=1213191252]
_I_E_007201946e629037 [09:04] error in strategy: 0015 Closed server

what is that? is the webserver, you are sending these requests, running? Did u check its logs too?
[/quote]

webserver running. it's can be simple checked by open web-services URL from IE. and in the web-services(on a webserver side) log-files i can see it.
but when i try it from URS web-services log-file complete empty, as i wrote earlier.

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: debuging SOAP request
« Reply #3 on: June 11, 2008, 08:11:18 PM »
Timur,

It seems to me that HTTP bridge isn't enabled/available so URS complains about closed server. Please check that correct and free TCP/IP port is specified in URS options - section "web", key "http_port". If you have configured log properties for HTTP bridge correctly then new set of log files will be created after URS restart.

Very common configuration issues are:
- wrong or already used TCP/IP port assigned to HTTP bridge
- log-related keys not present in "web" section (be careful - key "verbose" is present in "web" section as well - check reference guide)

Hope it helps you
R.

Offline Timur Karimov

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: 2
Re: debuging SOAP request
« Reply #4 on: June 16, 2008, 11:32:00 AM »
tnx 2 Rene`  :) after create web\http_port option all logfiles created too and now i can see request-answer to/fromweb-services. Strange, but in the my documentation this option in section default.
well, but now i have different trouble-
i will try WEB-request where service name Execute1, 1-st param QueryName, 2-nd param QueryParam.
i use this value for created WEB-service object as key:value pairs 
QueryName=BS_Curr_Rate_Get
QueryParam=i_DN=9012420195,i_ExtParam=$SUBSYSTEM=IVR

but in xml_log i see next string
[color=red]<Execute1><QueryName>BS_Curr_Rate_Get</QueryName><QueryParam>9012420195</QueryParam><i_ExtParam>IVR</i_ExtParam></Execute1>[/color]

as we see-it's wrong. URS parser(or something) can't accept my value (i_DN=9012420195,i_ExtParam=$SUBSYSTEM=IVR) as single string. And except for that created wrong Key i_ExtParam.

what i mast do for create solid single string key:values  pairs "QueryParam:i_DN=9012420195,i_ExtParam=$SUBSYSTEM=IVR" ?!

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: debuging SOAP request
« Reply #5 on: June 16, 2008, 02:40:19 PM »
Hi Timur,

I did quick test using your case and it works correctly. Parameter's value is passed to webservice in the same way as I entered it in the strategy.

What version of URS do you have? I did my test with URS 7.6.

Could you post here your URS and XML logs?

René

Offline Timur Karimov

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: 2
Re: debuging SOAP request
« Reply #6 on: June 17, 2008, 07:55:17 AM »
[quote author=René link=topic=3051.msg12436#msg12436 date=1213627219]
What version of URS do you have? I did my test with URS 7.6.
Could you post here your URS and XML logs?
René
[/quote]

Rene, fanx again. I work with URS 7.5.002.02. log in atach

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: debuging SOAP request
« Reply #7 on: June 17, 2008, 08:37:13 AM »
Hi Timur,

I've repeated the test and the outcome is that URS parser doesn't like commas in the parameter's value (event URS 7.6). If there is comma then text following the comma is considered to be a new parameter (see logs below). It isn't correct behaviour of URS in my opinion so I would recommend you to open service request with Genesys TechSupport.

Workaround - replace commas with other character like hash (#) or pipe (|)

R.

[b]--- URS log[/b]
[font=Courier New]2008-06-17T10:24:50.718_I_I_3fff000000000001 [07:39] HERE IS XDATA
2008-06-17T10:24:50.718_H_I_ [08:0c] SOAP request 1 sent to HTTP bridge:
URL:        http://172.18.1.1/WSTestSGGU/Service.asmx
Method:    s0:HelloWorld
NameSpace:  s0=http://tempuri.org/
SOAPaction: http://tempuri.org/HelloWorld
Input:      s0:QueryName=BS_Curr_Rate_Get,s0:QueryParam=i_DN=9012420195#i_ExtParam$SUBSYSTEM=IVR,delimiter=#
Output:    HelloWorldResponse.HelloWorldResult
HTTPAuthent:1 
SOAPSecrty:
2008-06-17T10:24:50.718_I_I_3fff000000000001 [09:04] <<<<<<<<<<<<suspend interpretator(WAIT_WEBSERVICE), timers:00000
2008-06-17T10:24:51.282_H_I_3fff000000000001 [08:08] OK InfoMessage is received from server ##HTTPSERVER
  key V1 List] value: (size=94)
    key STRN [String] value: "QueryName: BS_Curr_Rate_Get, QueryParam: i_DN=9012420195#i_ExtParam$SUBSYSTEM=IVR"
2008-06-17T10:24:51.282_I_I_3fff000000000001 [09:05] >>>>>>>>>>>>resume interpretator(0)[/font]

[b]--- URS parser log[/b]
[font=Courier New]06/17/08@10:24:50: TRACE: Ref 1: 1 attempt to contact Web Service. 1 attempt(s) left
URL: http://172.18.1.1/WSTestSGGU/Service.asmx
Method: s0:HelloWorld
Namespace: s0=http://tempuri.org/
Tags: s0:QueryName=BS_Curr_Rate_Get,s0:QueryParam=i_DN=9012420195#i_ExtParam$SUBSYSTEM=IVR,delimiter=#
SOAPaction: http://tempuri.org/HelloWorld
Result: HelloWorldResponse.HelloWorldResult
HTTP Authentic: Anonymous
WS-Security: No
06/17/08@10:24:51: TRAC5: Ref 1: SOAP request:
06/17/08@10:24:51: TRAC5:    s0:QueryName = BS_Curr_Rate_Get
06/17/08@10:24:51: TRAC5:    s0:QueryParam = i_DN=9012420195#i_ExtParam$SUBSYSTEM=IVR
06/17/08@10:24:51: TRAC5:    delimiter = #
06/17/08@10:24:51: TRACE: Ref 1: SOAP response:
06/17/08@10:24:51: TRACE:        [String] HelloWorldResponse.HelloWorldResult = QueryName: BS_Curr_Rate_Get, QueryParam: i_DN=9012420195#i_ExtParam$SUBSYSTEM=IVR
06/17/08@10:24:51: TRACE: SOAP thread -1232376928: Status 'Connection Idle'[/font]

Offline Timur Karimov

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: 2
Re: debuging SOAP request
« Reply #8 on: June 17, 2008, 09:38:41 AM »
In my test i have problemnot only with comma, but and '=' (equal character) make trouble inthe parsing to.
may be i miss it in the log, but as i say early string "key=value",  where value='a=64', after parsing look like "key=64" =(

i try upgrade test lab to 7.6 version and write here result.

fanx very much, wbr Timur.

Offline Timur Karimov

  • Sr. Member
  • ****
  • Posts: 415
  • Karma: 2
Re: debuging SOAP request
« Reply #9 on: June 19, 2008, 02:02:09 PM »
Rene fanx again. We upgrade to URS 7.6 and now our solution works ok.