LWSNQRY

LWSNQRY tab does not include Productline selection. I created a Production version of Rich Client. I defined the configuration for the data area. I created IPD connection for Production. Yet when I attempt to create a LWSNQRY node data area information does not display. Any Thoughts?

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

jreese

I am assuming you are not seeing this when you click on the build on the Query Node. I believe you may be missing some file access in the GEN database. I had similar issues where I wasn't seeing the tables and the fields properly and had to add the TITLE and EXECUTABLE files to the security profile in GEN on Lawson Security. Never had an issue seeing the Product lines but sounds like it might be a similar issue.

russel-cornelson

I would create a file called C:Users<username>lawson-httpclient-trace.log and replicate the issue hitting the build button. The designer makes web servlet calls in the background to get the names of the product lines

bhillz

Is this the general location for enabling log files (i.e. C:Users<username><some_trace_log>) or is it windows version dependent? Could it be in the C:Users<username>appdata... ree?

Are there other files that can be created to enable other logging? Does the existence of the file enable additional debug/tracing of execution.

2582_2920_BI-231_ApplicationStudio_02_Working_with_Hyperblocks.mp4

russel-cornelson

Sorry for the delay, I didn't spot your reply when it came in.

The lawson-httpclient automatically looks in the home directory for the user for the existance of lawson-httpclient-trace.log and it's mere existence does indeed enable this debug logging. For AIX its your home directory as well which can be different depending where you are. Essentially the system should automatically create lawson-httpclient-error.log; if you see that file you are in the right directory to create the trace.log file.

There isn't any other trace logging that can be enabled for the lawson-httpclient unfortunately. The downside of this logging is that it does not show much information in respect to the HTTP request/response ... only the header which renders it useless in some scenarios depending what you are troubleshooting.

In those cases, I have configured Fiddler to use a reverse proxy by modifying the Fiddler script. It works something like this:

1. you change the IPA configuration to point at http://localhost:8888

2. So your flow/designer will now try to call localhost:8888 which is Fiddler's loopback port.

3. You modify the fiddler script:

OnBeforeRequest

If the oSession.host is equal to localhost:8888; change the oSession.host = http://myserver:port that the call should goto

OnBeforeResponse

If the oSession.host is equal to http://myserver:port; change the oSession.host = http://localhost:8888

This would allow you to capture the traffic in Fiddler that normally does not get captured. I hope this helps.

Copyright © 2025 Infor. All rights reserved.