If you need to update Lawson database tables to match custom form field changes, follow these steps:
First update your .scr forms, kndef, skndef fields if creating new columns. Updated your .sr file to include any additional fields if needed.
Then in dbdef <productline>
F6 (Define) >> Files and update the database table names
Once done, follow these procedures:
You can run a bldddbdict <productline>
Then dbreorg -l <productline> to see affected tables.
Then dbreorg <productline> to complete the dbreorg.
NOTE: If DBReorg fails, make sure websphere apps are down and java processes are not running, try and restart server then perform dbreorg again if needed.
Qcompile your file and clear cache/ios cache, then test changes.
If you are getting a connection timeout when trying to run certain nodes in IPA, it could be due to your firewall blocking port.
Look for the following error message in your work unit log:
Failed with error com.lawson.bpm.db.model.helper.LawsonDBException: java.rmi.ConnectException: Connection refused to host: <ip address>; nested exception is:
java.net.ConnectException: Connection timed out: connect
RMI expects to work over the ephemeral port range, which is typically 49152 to 65535. If you do a telnet from your Landmark to Lawson server over one of those ports, and you get a timeout error, this is likely because your network admin has closed off all ports between those servers, besides the ones specified. In this case, you need to tell Lawson which port it is going to use for RMI.
In LAWDIR/system/bpm.properties, set the pflowRMIPort value to the specified port (0 is all ports). Make sure this port is also opened between the Lawson & Landmark servers by your network admin.
Reboot the Lawson server or restart services.
If you want to know how to bookmark a custom cobol ‘Vanilla’ Form, follow these simple instructions below:
This is how the custom cobol “vanilla” form in RD69 shows under ID it’s called XX3.1_TEST
So you may think you need to add it in as XX3.1_TEST when adding as a favorite or creating a bookmark.
An example:
LAWFORM|PDL=PROD10|TKN=XX3.1|ID=XX3.1_TEST
Instead, since it is the custom “vanilla” cobol program, you only need to mention the TKN, not the ID
LAWFORM|PDL=PROD10|TKN=XX3.1
That’s all there is to it! Just clear the IOS cache and browser cache, then you should be able to load the bookmark now.
If you need to update your SQL Tables after a data refresh, follow the simple steps below:
First, open up the properties for the DB that was just refreshed and you can see that the DB tables have the PROD name instead of TEST.
Next, run the following SQL query for the TEST DB:
ALTER DATABASE INFORLAWTEST10 MODIFY FILEGROUP INFORLAWPROD10_DATA NAME = INFORLAWTEST10_DATA
ALTER DATABASE INFORLAWTEST10 MODIFY FILEGROUP INFORLAWPROD10_INDEX NAME = INFORLAWTEST10_INDEX
Your SQL tables should now be updated after doing a data refresh. Continue to repeat these steps whenever you do refreshes.
ARTICLE:
When testing the FTP connection on a Lawson Back-office data source in LBI, you may receive the error message “System Directory Not Available”. You may also see this message in the SystemOut.log on the LBI server when the system is testing the connection.
Here are some troubleshooting steps when you encounter this issue:
- Open a Windows command prompt on LBI server
- ftp <lawson application hostname>
- log in as <ftp user>
- cd <application home path>
- ls (You should see the ‘system’ directory listed here. If not, that is the source of the “system directory not available” error). If you see the system directory, continue:
- cd /system/ers/backoffice/<pdl>
- get published.csv
- del published.csv
- put published.csv
- cd <application home path>/print/username/jobname/1 (use a username and job name for a published report, or any job if you have nothing published yet.)
- get <JOBNAME>.prt
- del <JOBNAME>.prt
- put <JOBNAME>.prt
NOTE you can also use an ftp client such as Filezilla to check for the file
Once you have ensured access to all of the above directories over ftp, you should find the following message when you test the FTP connection.
Intuitively you may assume that you can access scheduled processes in the Lawson Process Server Administrator main toolbar:
This becomes more frustrating because you would assume it would be under “Scheduling”. After all, this is supposed to be Infor’s convenient move away from the clunky Rich Client app.
To access your existing scheduled processes, you need to go to the top right where your user is and click there and select “My Actions”, NOTE: you’ll need to be logged in as the system user
This will take you to your Scheduled Actions as show below. Double click the Name to modify the schedule and you’re set after saving!
Here’s how to update IPA to add emails on the following error:
WU_Name.ipd
First, load the IPA and go to create process that checks for file, click on Error tab, copy TO, paste in CC but change to ManagerNoticiation.
What should happen on Error? STOP Process. (it is already on Stop Process so it will notify)
Next, click on the File tab then SAVE the changes.
Then Upload it
Next, go back to the Configuration Manager
Then go to Main and create or update ManagerNotification to include the email address(s)
Finally, look at process version
