BPM.ear file issues - LawsonGuru.com - LawsonGuru.com Forums -

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1372
Roger French	1315
mark.cook	1244

Chris12

Veteran Member

Posts: 150

7/1/2014 8:30 PM

We have an issue with displaying the recsum.htm file.
As of this time, when we click on a workunit within an inbasket we receive the "Display Exec" error followed by the 4 steps to rebuild the ear file.

After rebuilding and redeploying the ear file, the workunits are missing from the inbaskets.

When we put back the original bpm.ear file the workunits are displayed again but we receive the "Display Exec" error. I was hoping someone came across this in the past and can asist.

Have been struggling with this one for sometime.

We are on 9.0.1.8 (UNIX) .....

Thanks for any advise. Chris

Derek

Basic Member

Posts: 9

7/2/2014 11:40 AM

I haven't had this problem, but I would check for differences between the recsum.htm in the $LAWDIR/bpm/inbasketexecs and the BPM.ear in WebSphere.

John Henley

Posts: 3353

7/2/2014 12:34 PM

Chris, it sounds like something in your process for inserting the recsum.htm and/or redeploying is corrupting the bpm.ear file.
What are the steps you are using? (I recommend using a script or batch file so that it consistent and repeatable)
You should put back the original bpm.ear file, and then go thru the steps again.

Also, you don't need to uninstall/install (i.e. "redeploy") the bpm.ear file, just use the "update" option in WebSphere.

Chris12

Veteran Member

Posts: 150

7/2/2014 1:00 PM

John ... Below are the steps, we used ... this one is odd

copy the bpm.war and bpm.ear to a temp location and the use addExecsToArchive.pl to add recsum.htm, then put bpm.ear and bpm.war back and deploy.

John Henley

Posts: 3353

7/2/2014 8:11 PM

When you redeploy bpm.ear, are you uninstalling/re-installing it? or using update?

Chris12

Veteran Member

Posts: 150

7/3/2014 11:17 AM

We first just tried re-deploying ..... after several attempts at this not working, we finally tried uninstalling and reinstalling .... same results ..

John Henley

Posts: 3353

7/3/2014 4:25 PM

When you copy the bpm.war and bpm.ear to a temp location, are you running addExecsToArchive.pl from the temp location?
In other words,

cd $GENDIR\assembly\components\
mkdir tmp
cd tmp
copy ..\ear\bpm.ear .
copy ..\war\bpm.war .
perl $GENDIR\bin\addExecsToArchive.pl %LAWDIR%\bpm\inbasketexecs\recsum.htm
copy bpm.ear ..\ear
copy bpm.war ..\war
del bpm.ear
del bpm.war
cd ..
rmdir tmp

John Henley

Posts: 3353

7/3/2014 4:26 PM

After you re-deploy, run /bpm/daservlet against the BPM server, and verify the hostname and port, etc. are correct...

Chris12

Veteran Member

Posts: 150

7/7/2014 11:48 AM

Let me check the daservlet .... Chris

Chris12

Veteran Member

Posts: 150

7/7/2014 7:12 PM

Hi John ... so when we build the new bpm.ear file and redeploy the ear file into WAS .... we then run a daservlet call .... the RMIHOSTNAME appears to change to an old host name ..... Any thoughts on where they is getting read from ???

John Henley

Posts: 3353

7/8/2014 10:48 AM

Most likely from LAWDIR/system/bpm.properties

John Henley

Posts: 3353

7/8/2014 10:54 AM

I ALWAYS include this extra step in the script/process for updating/deploying the displayexecs (again, the goal is to make it consistent and repeatable).

As part of your process, add this step after copying .ear/.war files and adding the execs, but BEFORE copying them back and deploying.

perl $GENDIR/bin/updateArchive.pl
e.g.
perl $GENDIR/bin/updateArchive.pl 16003 lawson.example.com

Chris12

Veteran Member

Posts: 150

7/8/2014 11:10 AM

I see .... Also do I always have it move the ear and war file back or can I redeploy from the temp directory?

John Henley

Posts: 3353

7/8/2014 11:48 AM

Theoretically you can redeploy from anywhere, including the temp directory. However, my recommended approach is to make a backup copy of $GENDIR/assembly/components/ear/bpm.ear and $GENDIR/assembly/components/war/bpm.war within those directories ($GENDIR/assembly/components/{ear|war}, copy bpm.ear / bpm.war files to temp location, make the changes, copy back to $GENDIR/assembly/components/{ear|war}, then deploy from $GENDIR/assembly/components...
That way you have both the backup/original as well as your "customized" versions in the same place.

Chris12

Veteran Member

Posts: 150

7/8/2014 5:11 PM

Hi John ... now I am getting No Requistions Exist for the Workunit variables .... better, atleast we are getting an error message.
We are trying to get someone to put in a new req for us .... then we can test again ... just wondering if you have seen this error before.

John Henley

Posts: 3353

7/8/2014 6:46 PM

Are you able to see the workunits in the /bpm admin site?
Have you verified that the workunits (in LOGAN) and the requisition (in your apps product line) are in fact actually there?
Are you looking at all of this in your test environment, or in a production environment?
If you're in a test environment, did you perhaps refresh the apps product line data but not the LOGAN product line data, and therefore they don't match?
Lastly, are you using the delivered recsum.htm, or are you trying to do something custom with it?

fred.kobos

Advanced Member

Posts: 27

7/8/2014 7:34 PM

when you redeploy the ear file to websphere it wipes out recsum in websphere. you need to add it back into websphere

fred.kobos

Advanced Member

Posts: 27

7/8/2014 7:39 PM

L:\QIBM\UserData\WebSphere\AppServer\V7\ND\profiles\LAWWAS7\installedApps\LAWSON02_LAWDMGR\BPM-P.ear\bpm.war\htmlinbasket\inbasket\execs

Chris12

Veteran Member

Posts: 150

7/10/2014 7:05 PM

Hi John, we finally got this thing fixed .... so what did the trick was including the step:

perl $GENDIR/bin/updateArchive.pl
e.g.
perl $GENDIR/bin/updateArchive.pl 16003 lawson.example.com

After performing that and redeploying the bpm.ear file we were able to generate a new req and see the inbasket
Thanks so much!!!!

John Henley

Posts: 3353

7/11/2014 3:11 PM

I noticed a long time ago that this was required if you ever change server names or ports, etc. So just to be safe, I routinely recommend adding updateArchive.pl (it does no harm) to the deployment steps when you are using addExecsToArchive.pl to update displayexecs.
Of course, this will all change when you go to LPA/IPA

Glad you got it fixed!
Make sure you "tell your friends" where you got a solution