IPA/LPA connection to LSF and configuration sets

This is also in the technology group. Sorry about reposting but didn't realize this group existed.

I've gone through the GRID, LANDMARK, IPA/LPA, IPD, and obviously the LSF install. Now I'm trying to validate the connection documented in InfoCenter using IPD to create a test flow and WKWF. I get this error log entry--I get the same log entry if I try to release a requisition in RQ10 or RQC:
[2015-10-06 08:01:18] [LPSJNIUtil] Exception encountered while calling Java, sta
ck trace follows:
com.lawson.bpm.eprocessserver.interfaces.LPSConnectionException: Null proxy for
class: com.lawson.bpm.eprocessserver.interfaces.LPSDatabaseBridgeForLSF, data ar
ea: lawprod
at com.lawson.bpm.eprocessserver.interfaces.LPSGridSession.checkForNullP
roxy(LPSGridSession.java:239)
at com.lawson.bpm.eprocessserver.interfaces.LPSGridSessionForLSF.isServi
ceExistAndEnabled(LPSGridSessionForLSF.java:184)

--In the trouble shooting section is says you don't have a valid IPA data area when this error is returned. lawprod is my LSF dataarea. So this should be the IPA/LPA_dataarea? Is this from the configuration sets? We have main and system. I updated main with the Infor Lawson Connection under the Infor Lawson Tab. This is where it's really confusing to me. They talk about the two connection types: Web/EJB and that Web is for connecting to IPD and EJB is for connecting to IPA. I assumed web and defined data area as LSF data area and web root as LSF URL which is the way I read the documentation. Should I be using IPA_dataarea here and IPA URL? Or Mingle URL OR LSF URL. It's not clear to me. Also should I be defining EJB or should that be defined in the lsservice.properties file? Instead of using "main" and/or "system" should I have used a new configuration set like "MyConfiguration"?

Find more posts tagged with

Comments

jreese

Not sure if our issue was the same one you are having now, but looking at old emails from when we had issue getting the two environments to communicate with each other and not being able to trigger a flow from LSF, it looks like they had to point the LSF Environment away from the OS Java. PFlow, lase and WebSphere were set to run on the WebSphere's JDK. Don't have anymore details just the entry from the email as to what they did to resolve the issue.

0904080939293831.xls

alfred-chua

Since "lawprod" is your LSF/PFI data area, there would also need to be a corresponding "lawprod" data area on the Landmark/IPA side. If you are able to get on a command prompt on the Landmark env, please run this cmd: "listprod -ad" and that will show the data areas that are available to confirm that "lawprod" is present.

The "configuration sets" / "connections" are not involved while LSF tries to connect to Landmark. Those are used when a process starts to execute.

mbozenik

The PFI tables are in the LPA_LAWPROD dataarea and all the LSF/Apps are in the LAWPROD dataarea.

listprod -ad returns gen and lpa_lawprod

I guess I have to figure out where the log file is pulling the reference to lawprod and update that. I assumed it was the configuration set. In pfserv config lpa_lawprod was used.

russel-cornelson

This error can occur for a variety of reasons.

1) If your LSF productline name is not the same as IPA's data area

2) When you set up the system, and run "pfserv config lps" you may have selected the wrong URL or port for LPS. Check LAWDIR/system/bpm.properties and ensure that:

lpsPort = GRID_PORT (from Landmark LASYSDIR/install.cfg)

Adding a couple screenshots

GMT20200514-185124_MT-Cloud-S.m4a

mbozenik

I miss read the instructions and created a separate dataarea for IPA/LPA. I assume the next step is perl remove-lpa.pl lpa_lawprod. Then remove enterpriseapp lpa_lawprod lpa via WAS and uninstall. Then start over. Do I need to flush out the database as well or will the remove-lpa.pl do that for me? When running perl install-lpa.pl lawprod and it asks for the oracle userid when connecting to the database should I use the oracle userid that was used for Lawson apps? I had created a separate user here as well and now I'm thinking I should have used the one used for LSF/Apps.

mbozenik

Here's another question. During the landmark install and the LPA install they both prompt for Oracle user IDs. Should these oracle user IDs be the same and should they match the oracle user ID used for LSF?

aszeglin

You're using the same DBSERVER/ORA_SERVER as LSF, same product line name, but can have a different schema built within. As for the user, I think we have a separate user. My Oracle DBA helped me out with the specifics. But the permissioning and creation of the schema should be done before the install of the PL.

mbozenik

Yes. That's what I did, but now I'm having second thoughts.

Current install.

LSF user/schema lsfprod and oracle db name lawprod
landmark user/schema lmrkprod and oracle db name lawprod
LPA/IPA user/schema ipaprod and oracle db name lawprod

It looks like landmark and LPA/IPA have the same schema structure. It looks like I should have used the same schema for both landmark and LPA/IPA. The landmark schema has the additional tables for Landmark plus all the PFI tables that the IPA schema has. Just curious if I should have combined the two. What is the best practice? It even looks like I could have used the same user/schema for all three of them, but I doubt that is recommended.

mbozenik

Finally got it working. The test flow I created didn't have the process linked to the service. So the configuration sets weren't an issue. Making sure the dataarea between IPA and LSF was key, but in the end it was the test flow. The schema names aren't an issue, although I don't know why we have all the PFI tables defined twice. Once in the landmark/gen dataarea and the ipa dataarea.

Copyright © 2025 Infor. All rights reserved.