Lawson Transaction Node

Productlines not displaying for any of my Lawson Transaction nodes. Is there away to debug to see why this is happening? Works in TEST environments without an issue.

Thanks

Gary

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

All comments

russel-cornelson

Good afternoon Gary,

How it Works

IPA Designer makes the following web call when you click the build button:

http(s)://LSFSERVER:webPort/servlet/Router/Data/Erp?PROD=GEN&FILE=prodline&field=productline&out=csv&delim=~

The designer should be connecting to grid before that and reading the Infor Lawson configuration of the main config set. The URL and username/password should be the account making the call above.

How to troubleshoot

The easiest thing to rule out is security ... build the above call using the FQDN:PORT from your Infor Lawson configuration and make the call from your browser. Ensure it makes you login, when prompted for credentials ensure you log in as the same user.

Did you get a security error? Engage your LSF Security admin to address the security error.

Did it return results? The next thing I would try is checking to see what response I am actually getting from the designer. To do this, Navigate to your C:Users<username> folder on the PC running the designer and create a file named: lawson-httpclient-trace.log

Then shut down and relaunch the Designer, duplicate the issue, and look in the above file. CTRL-F and search for FILE=prodline. What you are looking for is what HTTP Response you got, was it a 200? 404? 500?

The line will look like this, and it will appear below the line you found FILE=prodline on.

[2018-10-04 16:14:13.591] STATUS [HTTP/1.1 200 OK]

Start with that, if you can't find your answer post the results of the above steps and I can come back and update this further.

unknown

Hello, just upgraded our TEST environments to Landmark/IPD 11 and ADFS, and are experiencing a similar issue in one of our test product lines - after clicking the build button for basically any node that has one, we receive an error: "Error in Loading the Product Line Tables"

I set up a trace file following Russell's instructions above. An error log was created in addition to writing to the trace log.

The errors in the error log are:

Error when executing GET method: Connection refused: connect

And in the trace log, I am seeing something very weird (red text is mine):

executeGetMethod(): URL=http:///sso/SSOServlet?_action=PING&_updateSession=true

… as if it doesn't know the URL.

We have a case open with Xtreme but they have not been able to solve. We are supposed to go live with Landmark and ADFS next week, and we are concerned about what we are seeing in TEST. Does anyone have any suggestions? Thank you!

plancor

We are on Landmark 11 and just implemented AD FS. I do know that there were some system configuration tweaks that were required based on the new AD FS requirements. Our consultants made these changes for us, so I'm not 100% sure, but I think it involved changing the User in the Web configuration from lawson to lawson@xxxxxxxxxx. Also maybe adding the port to the Web Root URL...? Just some suggestions to look at...

jreese

I would suggest starting at the System Configurations and doing the Test Connection for each Configuration Set and tab that you have setup with a user and password. As pbelsky mentions above all of the usernames now require an @xxxxxxx to work.

unknown

Hi guys, we did get this working, so I thought I'd post our solution in case anyone else with an issue is searching these threads.

Original problem: We have multiple product lines in our test environment, and we could not get the build button in nodes like sql query, Lawson txn, etc to open a build window in any of the additional product lines - only the original product line. We received the error "Error in Loading the Product Line Tables"

Description of solution: In the rich client data area for the additional product lines, we had first copied all the connection info on the Main configuration tabs from the original product line to the additional product lines, and crossed our fingers. It didn't work. What our admin ended up doing was, in the System configuration of the additional product lines, under the Infor Lawson tab, create a Web Connection (the connection type under Main for the additional product line was already set up as an EJB), which allows you to specify the product line. After doing that, now when I open a flow in IPD in the additional product line and add a node with a builder, if I click the build button it behaves as expected.

I do have a question for the group - Is the EJB connection in the Main configuration's Infor Lawson tab for the additional product lines even necessary, i.e. could we just change it to a web connection, and set it up like what is in the System configuration, so that we would not have to specify the System configuration for those nodes? Or is that EJB needed for other things? I am a developer not an admin, so please excuse my ignorance if the answer is obvious to everyone but me. Thank you!

unknown

Forgot to specify in my post above: "...After doing that, now when I open a flow in IPD in the additional product line, choose the System configuration set, and add a node with a builder, if I click the build button it behaves as expected."

Copyright © 2025 Infor. All rights reserved.