Ah, I need to close this one. The limit is from the debugger not from OD. The debugger will not show a string with more than 500 characters, it will add <value too big> once more than 500 chars are added to the string.

It works just fine outside of the debugger.

Live and learn.... never a dull moment.

Thanks for the help.

When using JSON Builder, I'm getting an error at the end of the string I'm bulding which says "<value too big>" this appears to be the result of too much data.

Example: ...... d"},"requestId":"123123","topic":"undef","persistToEDM":"true"...<value too big>

I have moved things around just to make sure it is not being caused by a specific property, at this point it seems to be a size issue.

Is there a limit to the size of the JSON structure that can be built with "JSON Builder".

Thanks.

That did it. Thank you!

When I run a voice application using the simulator I can see in the report.log and trace.log all kind of information about the application and other stuff I print via the trace node. I also have a servlet which I call at the end of the application to print all the variables from the variablenames object.

However when I deploy the application to the webapps folder in tomcat, and I point AEP to it, the application runs just fine but the report and trace log under webapps/my_app are empty. The only log collecting data is localhost_access_log.todaysdate.txt but this log only has GET and POST requests.

I have edited logging.properties and ddrt.properties to no avail.
What else needs to be edited?

Thanks.

Are there any folks here that are running/deploying OD ear(s) in WAS. We're deploying our OD applications to WAS version 8.5.

Our experience is that everything runs very smooth in the development environment (which uses TomCat) but when we export the application to WAS we get all kind of errors/issues with web services, plug ins, classes, etc. The supporting runtime and classes have also been exported and deployed.

We're starting to think that since OD is more geared to TomCat, we should be deploying to that application server instead of WAS.

I guess I should also mention that our OS is SUSE Linux Enterprise Server 12 (s390x).

Any opinions, suggestions would be greatly appreciated.

Thanks for your input.

The owner of the WS finally figure out that it was an issue on their side and the way they were parsing our payload. Once I used the HTTP monitor I could see that our headers were correct and they had to do a bit more "digging" on their side.

The CR/LF issue was resolved by me picking the variable {_JSONBody_} in the "Message Body" instead of me typing it.... oops.

Again thanks for your help.

I am trying to consume a REST web service from Context Store which works just fine from OD when I debug the application, but it breaks with I deploy the application to a WAS 8.5 application server.

Actually, I consume two services, one is a GET and the other a POST. The GET works just fine on both environments (OD and WAS), the POST breaks with an http header error, see below:

message :{org.apache.commons.httpclient.params.HttpMethodParams incompatible with org.apache.commons.httpclient.params.HttpMethodParams}

I have tried with and w/o headers and I get the same error. The body of the request is JSON so when I do use the header I set "Content-Type" to "application/json".

Any ideas? Thanks in advance.

The version of OD is 7.2.2
Thanks.

I'm trying to consume a REST web service using the REST Web service operation file.

In this file I have added to the "Message Body" the entry JSON{_JSONBody_} since I need to send json on the request body.

I have also added a header Content-Type and set it to application/json.

However, I'm having two issues, or so the Web service owners tell me.

First: The request body has a line feed and a carriage return on the json opening and closing curly bracket, they want me to remove the lf/cr from the body.

Second: The Content-Type they are getting from me is text/xml

Any idea how to resolve these two issues?

Thanks

UPDATE: I'm now being told that they are receiving "application/json" in the header from me, but their system is converting it to "text/html". They are suspecting this is happening because "the body/json is in string format"

Ah, you are right, I did not realize that. Once I started digging more into the logs, I could see a 400 back from the WS.
Thanks.

I have added a new REST web service operation using the WS operation Editor and both the REST URL and Server/Endpoint URL fields have been correctly filled in. However, at run time the call to the WS fails with a bad formated endpoint URL. the rest of the URL (query) is correct. See sample below. Not sure where this short endpoint is coming from.

REST URL (in WS operations editor)
http://unit.services.companyname.com/api/DEFAULT/AvayaContextStore/contexts/upsert/groupId?rid=restRId&release=restRelease&rules=restRules

Server/Endpoint URL (in WS operations editor)
http://unit.services.companyname.com/api/DEFAULT/AvayaContextStore/contexts/upsert/

Error I get when trying to run this service from a voice application in OD.
17/12/2020 16:36:29:004 ERROR - The system cannot infer the transport information from the Mbrshp/147896325?rid=&release=360&rules=false URL.
***** Saw exception, tracing before report
org.apache.axis2.AxisFault: The system cannot infer the transport information from the Mbrshp/147896325?rid=&release=360&rules=false URL.

Thanks.