To maintain Landmark Security (classes and roles), in the Gen environment in Rich Client, go to Start > Configure > Security. If you don’t see the Security or Configure, you will need to have your Security Administrator give you access to it. The Infor delivered role for this is “ConfigConsoleSecurityadmin_ST”. Have that role added to your account and wait about 30 minutes for the sync to complete.
There may be multiple applications for PGP encryption keys at your organization. It is very simple to create and use the keys using the secadm tool on your Landmark server.
- On your Landmark server, open a command line tool and set your environment
- Type command secadm -m, then enter the security utilities password if prompted
- Select option “Key management” (in later versions, this is found under Service Management)
- Choose option “Generate PGP Key Pair for a service”
- Enter the service (such as SSOPV2)
- Open the Service in Rich Client and validate that the PGPPrivateKey and PGPPublicKey properties were added
Problem: Workunits for Infor Process Automation are sitting in Ready Status and not processing.
1. Via LmrkGrid (Grid Management), determine how many workunits may simultaneously process in your system. (see attached “DeterminingSimultaneous.docx”)
- Determine how many workunits are currently in a processing state.
NOTE: Please refer to attachment “DeterminingSimultaneous.docx” for instructions on determining simultaneous processes. In case you will need to engage support, you should screenshot this information to provide when you open the support incident.
– Command to count records in Ready Status: dbcount <DATAAREA> -f Status=\”1\” PfiWorkunit
– Command to count records in Processing Status: dbcount <DATAAREA> -f Status=\”2\” PfiWorkunit
– Command to count records in Completed Status: dbcount <DATAAREA> -f Status=\”4\” PfiWorkunit
It is a good idea to monitor and take counts of these records periodically. Are the number of workunits in Ready status growing? Are the number of workunits in Completed status growing? Is the number of workunits in Processing status equal to the maximum number workunits that can simultaneously process?
NOTE: If the number of workunits in Ready Status is growing and the number of workunits in completed status is not, then either:
- You have workunits that processing for a very long time holding up the system; use the Grid Management UI to determine which workunits are processing so long and determine if those are stuck in a loop; or if they are just processing normally large jobs. Consider cancelling the long running workunits, and scheduling them to run in off business hours.
- If you are on Landmark 10.1.0.x, there was a bug in this version of Landmark that periodically caused Async to stop picking up new workunits. This issue was resolved by a re-write of Asnyc and LPA nodes in 10.1.1.x Landmark versions. If you are on Landmark 10.1.0.x you should restart the Async Node, and the IPA node.
NOTE: The workunits that were already queued to an LPA node will not automatically start back up; the workunit polling frequency (default 30 minutes) will need to trigger before they are requeued to a new LPA node.
Depending on the process run, Rich Client workunit logs can grow extremely large. So large in fact that you may not be able to extract the full log from the Landmark Rich Client.
If a workunit log grows too large you may not be able to extract the full log from the Landmark Rich Client, in this case you can use the following command to extract the log from a Landmark Command Prompt.
What Is the Landmark Command Prompt?
The Landmark administrator will perform many tasks from a command prompt. When you are instructed to use a Landmark command prompt, you should be sure you are in the Landmark Environment that you want to use, and that all environment variables are set correctly.
Setting Environment Variables
Before you startBefore you perform this procedure, be sure that the /etc/lawson/environment/environmentName/config.sh file contains the appropriate settings for environment variables.
Use this procedure to export the appropriate environment variables for your Landmark Environment before issuing commands from a Landmark command prompt.
To set the Landmark Environment variables
At a command prompt, type
. cv landmark-env-name
Where landmark-env-name is the name of the Landmark Environment.
dbexport -C -f “PfiWorkunit=####” -o . -n <dataarea> PfiWorkunit
dbexport -C -f “PfiWorkunit=7000” -o . -n prod PfiWorkunit
Find the name of the Form and the Business Class that you want to add the field to (Ctrl-Shift-Click on any field on the form)
Log into Rich Client and go to Start > Configure > Application (make sure that you have been granted access to Configuration Console)
Find your Business Class, and click “User Fields” under the class
Give your user field a meaningful name (no numbers or special characters allowed, and the field name must begin with an upper-case letter)
Next, go to configured forms and find the form name that you noted earlier
If this form has never been customized, you may need to click the blank paper icon to add it to the Configured Forms list
Once the form has been added as a configured form, click on the form name, then click “Configure”
Navigate to the location where you want to add the user field
Click the blank paper and select “User Field”
Configure the user field for the form
Click “Save” and verify that the user field is now on your screen
When using Infor Cloud, the landmark rich client looks the same in dev as it does in prod. How can I easily recognize the difference between them?
Mistakes can happen when you are frequently changing between a development and production environment. It is easier to tell the difference between the environments when the productlines are installed with different names (dev and prod for example). If your environments use the same names, you can change the appearance in the rich client to help make it more obvious which environment you are using. From the Rich Client, click Start – Settings. Then select a different Theme color for the dev productline (green for example) and add DEV to the Display Name field. The other productlines on the dev system can also be selected and changed to green. Each of the productlines on the prod system can be changed to another color while also changing the Display Name to include PROD.
From the Landmark Rich Client, forms can be changed under Options – Personalize in the menu. Fields on a form can be renamed or changed in color or style. They can be hidden, marked as display only, or as required. In this example, the field “Last Employment ID Assigned” is highlighted in bold red with a shortened name. Once Personalize is selected, Form Personalization shows Actions and Fields at the top. Actions will allow restrictions for a specific condition. In this case, click on the “Last Employment ID Assigned” and then click Fields in the upper right. Select the Label tab to change the style, color, and text. Once the changes are made, the window is closed and the Form Personalization is Saved in the upper right. The changes are then seen immediately without restarting the client. To undo the changes, return to Options – Personalize in the menu, and click Reset in the upper right.
Enabling or disabling security can be done in Authorization Activation through Security System Management. This can be accessed from the landmark validation url’s or from within the rich client. The validation page can typically be found at D:\LMKDEV\gen_ValidationURLs.htm where D:\LMKDEV is the landmark installation folder. Opening the htm in a web browser will list the link for Security System Management.
From the Security System Management screen, select Authorization Activation in the upper right of the menu. It will return a list of productlines. Double clicking a productline (or Actions – Open from the menu) will return the Security Activation screen. The screen shows Security Status as a parameter with values to allow All Access, No Access, Process Rules. Select All Access to turn off the security rules and save the change. Select Process Rules to again enable security restrictions.