Resource Query Node

We have the same issue. We just upgraded to IPA on Landmark 10.0.4 and no matter what we do, we can't run Resource Queries on the server. They work fine from the designer though. We have a case open with support, but they haven't figured out what the problem is yet, so you probably should do the same. If we get a resolution, I will post back.

We are on IPA Landmark 9, and we can't run them either. I have a webex with Lawson next week about this. They told me the following which I don't entirely understand, so hence the webex.

"I consulted Development about this case and they said that a fix will not be provided for 9.2.x version.
Workaround is to use rmi: to configure the lsf connection for the rmquery node only. Please create a different configuration set to be used for the rmquery node. Parameter is rmi://lsfserver:pfrmiport."

This is the error I get:

Error message: Error: Unable to lookup RMI object rmi://chslwtweb.intra.chs-mi.com:16003/dbSecurity
(nested exception: Connection refused to host: chslwtweb.intra.chs-mi.com; nested exception is:
java.net.ConnectException: Connection refused: connect)
(DB Return Code = 0)

In the flow, select the resource query node and verify that you have a 'configuration name' selected.
Then in the Landmark rich client, go to Process Server Administrator > System Configuration, and open the configuration name that was selected.
Look at the tab 'Infor Lawson', and see if you have the destination information correct (it needs to match your LSF -- NOT IPA -- server).
Also from the Landmark Rich Client, open the Process Server Administrator, and go to Process Server Administrator > Administration > Workunits.
Double-click a workunit where the resource query is failing, and on the tab strip, select the 'Log' tab. Click the open button, and it will open the workunit log file.
Find the node related to the resource query, and post that section here so we can see any errors.

John,
I don't have an 'Infor Lawson' tab but I think it uses the S3 tab. Our LSF server is chslwpweb which is what the log shows it is having problems with. Here's the log:

Workunit 18802 for process RQuery execution started @ 10/03/2013 10:10:46 AM


Activity name:Start id:1 started @ 10/03/2013 10:10:46 AM
Executing Start Activity...
Variables:
Activity name:Start id:1 completed @ 10/03/2013 10:10:46 AM

Activity name:ResourceQuery3400 id:2 started @ 10/03/2013 10:10:46 AM
Error while executing ResourceQuery activity
com.lawson.bpm.db.model.helper.LawsonDBException: Error: Unable to lookup RMI object rmi://chslwpweb.intra.chs-mi.com:16003/dbSecurity
(nested exception: Connection refused to host: chslwpweb.intra.chs-mi.com; nested exception is:
java.net.ConnectException: Connection refused: connect)
(DB Return Code = 0)
ResourceQuery3400_RETURN_MSG = Error: Unable to lookup RMI object rmi://chslwpweb.intra.chs-mi.com:16003/dbSecurity
(nested exception: Connection refused to host: chslwpweb.intra.chs-mi.com; nested exception is:
java.net.ConnectException: Connection refused: connect)
(DB Return Code = 0)
ResourceQuery3400_RETURN_CODE = -1
Activity name:ResourceQuery3400 id:2 failed @ 10/03/2013 10:10:48 AM
Error evaluating expression ResourceQuery3400_errorCode
Error evaluating expression ResourceQuery3400_informationCode
Error evaluating expression ResourceQuery3400_returnMessage
Error evaluating expression ResourceQuery3400_outputData
Executing End-ResourceQuery3400 because activity ResourceQuery3400 encontered an error
ResourceQuery3400_RECORD_COUNT = 0

Activity name:End id:3 started @ 10/03/2013 10:10:49 AM
Activity End: Executing End activity
End_errorCode = 0
End_informationCode = 0
End_returnMessage =
End_outputData =
Activity name:End id:3 completed @ 10/03/2013 10:10:49 AM

Workunit 18802 for process RQuery execution completed @ 10/03/2013 10:10:49 AM

John,
I re-read the long ongoing incident I have with Lawson. They already tried to look at the configuration and found it was correct. The webex next week is to show me how to make one specific to the Resource Query node. That's how I understand it anyway. Here's their comments about the configuration.

"Your configuration was correct. The problem is that your webserver is different from your appserver, and LPD is trying to go to your webserver:16003 to get your RM attributes, when it should be trying to go to your appserver:16003. We tried adding a new S3 Node with your appserver under the system configuration, but it failed and you can delete it."

John, this is an example of the return from the Resource Query node on IPA 10. I did also check the configurations and everything is pointing to the appropriate location. The strange thing is that the Resource Update transactions work fine using the same configuration.

Activity name:ResourceQuery7840 id:3 started @ 10/03/2013 08:38:54 AM
Error while executing ResourceQuery activity
java.lang.IllegalArgumentException: String "FALSE" is not valid boolean value.
ResourceQuery7840_RETURN_MSG = String "FALSE" is not valid boolean value.
ResourceQuery7840_RETURN_CODE = -1
Activity name:ResourceQuery7840 id:3 failed @ 10/03/2013 08:38:54 AM
Error while executing ResourceQuery activity
java.lang.IllegalArgumentException: String "FALSE" is not valid boolean value.
Activity ResourceQuery7840: Error evaluating expression: ResourceQuery7840_errorCode
Activity ResourceQuery7840: Error evaluating expression: ResourceQuery7840_informationCode
Activity ResourceQuery7840: Error evaluating expression: ResourceQuery7840_returnMessage
Activity ResourceQuery7840: Error evaluating expression: ResourceQuery7840_outputData

Can you post the resource query string?
put it between tags:
[ CODE ] [ /CODE ] (i.e. remove the spaces between the brackets

Here you go:

It looks like your query is to retrieve the employee number for anyone in either the "IS Super User" or "FIN AP Coordinator" roles?

Correct, it should return the userid, name, and employee number for anyone in those two roles.

Bob and Amy,
Are you on LSF 9 or LSF 10?

My environment is LSF 9 (9.0.1.10 Env, 9.0.1.3 Apps) and IPA 10.0.4

Bob on Process Server Administrator > System Configuration, on the 'Infor Lawson', and for that configuration, are you using Web or EJB?

Posted By Lynne on 10/03/2013 09:37 AM
 "Your configuration was correct. The problem is that your webserver is different from your appserver, and LPD is trying to go to your webserver:16003 to get your RM attributes, when it should be trying to go to your appserver:16003. We tried adding a new S3 Node with your appserver under the system configuration, but it failed and you can delete it."

Lynne, I remember running into that issue (web server / app server different host names and/or IP ports) during the Infor 10 beta, and after quite a few webex sessions  ( and a lot of "encouragement" from me ), finally got them to fix it. I'm guessing that whatever they had to do was pretty complicated, which is why they aren't back-porting the fix to LPA 9...

We are using a Web connection for our Infor Lawson connection. We did try both using the normal https URL for the S3 app server as well as an RMI call but received the error both ways.

On a side note, support was finally able to reproduce it so they created JT-505973 and sent it to engineering.

Bob, couple other questions:
1. is your LSF federated with your Landmark/IPA?
2. When you last updated IPA, was the "packageLPSClientJars" post-install process done?
3. what platform is your LSF and your Landmark / IPA?

1. We did not federate LSF and Landmark; we did not want Landmark to own authentication, and we were told by our installer that we would have to do more environment patching on LSF9.0.1.10 in order to use ISS. So we decided to leave them separate until we get to LSF10 next year.
2. The post-install process was done
3. We are running LSF and Landmark on the same AIX 7.1 server with WebSphere 7

I just found out that the RM Query is a bug JT-505973.  I am cannot wait for the fix so I change the flows I needed to to Query nodes on the landmark gen instance. 

I had to set up a new configuration with a jdbc connect for this one.

SELECT   ACTOR, CIEMAILADDRESS
FROM     ACTOR
WHERE    ACTOR = ''

Worked for me as a work around.

Bob,
I had the same problem with a client, we upgraded to 10.0.5 and that error disappeared but instead we get a different error because the RM query builder inserts lawson user and I had to remove lawson and that fixed the query.