Archive for category: Frontpage Article

To adjust the maximum heap size of a node in Landmark Grid, you first need to be logged into the Grid Management Console. From there, follow these steps:

1. Click the Configuration Manager link  (the gears icon located at top right corner).
2. Next, click “Applications”.
3. Select your Landmark deployed application.
4. Click “Edit Properties”.
5. Under Grid Defined Properties,  click “Max Heap”.
6. Select the “All” Radio Button.
7. Find the node you wish to adjust, and click on value it is currently assigned.
8. In the popup window, enter a new value and click save.
9. In the top left corner of the screen, click save again to apply the changes.
10. Click the home link in top right corner.
11. Click the stop link (black box in top right corner of the node you adjusted)
12. The system will shutdown that JVM then, automatically restart it for your change to take affect.

And you’re done. Good luck!

Follow these steps to edit the domain name on the ADFS instance:

Update the Domain Name

1. Open the ADFS Management application from the ADFS server.
2. On the right, select “Edit Federation Service Properties”.
3. Change the Federation service name and identifier to reflect the new domain name.

Regenerate the Token Certificates

4. Open a PowerShell session on the ADFS Server
5. Run “Update-ADFSCertificate”, which will generate a new token-decrypting and token-signing certificate.
6. The old certificate will remain primary on the instance and cannot be deleted until a new primary is selected.
7. In PowerShell, run the command “set-ADFSProperties -AutoCertificateRollover $false”
8. Now you can right-click the secondary (new) certificates and set them as primary.
9. Delete the old certificates.
10. Reset the rollover option in PowerShell: “set-ADFSProperties -AutoCertificateRollover $true”

Deploy the new Server Certificate

11. Get the Thumbprint value on the new certificate for the new domain.
12. In PowerShell, run command “set-ADFSSslCertificate -thumbprint <value you saved in step 11>”
13. Bounce the ADFS service

Your ADFS domain/URL has been updated!

 

To clear an existing sync lock in order to rerun the sync from the beginning again

From ssoconfig -c:

Login to the Infor Security Services web page

On the menu bar navigate to Federation > Manage Locked Process

If there is a process listed, make a note of the process that is locked

From the command line, run the ssoconfig utility. Type ssoconfig -c

At the prompt, enter the ssoconfig password

Select Manage Locked Processes

Select the number of the process that needs to be unlocked

Once it has been cleared, a message will appear that the process has been cancelled

Select the number that corresponds to Exit to return to the ssoconfig menu

Select EXIT at the ssoconfig utility

From the ISS web page:

Login to the Infor Security Services web page

On the menu bar navigate to Federation > Manage Locked Process

If there is a process listed, kindly check the box and hit the “unlock” button (Note: There may be more than one locked process, but you only need one to unlock, and all will be unlocked).

 

These 5 tips could make applying patches that much less stressful and are also good practice in general.

 

Tip 1: Check existing patch logs to see if a patch has already been applied previously and current versioning. This is good to check after a patch has been applied as well.

These logs can be found and generated here in LID:

perl %GENDIR%\bin\patches_installed_report <productline>

perl %GENDIR%\bin\source_versions_report <productline>

 

Tip 2: Restart the LSF server (or services) to ensure no processes are being held up and when it boots up, turn off Websphere LSF Appserver service before applying a patch to ensure users cannot log on, especially if patch needs to be applied during or close to work hours.

 

Tip 3: Run dbdef command to make sure there is a connection to the database before patching

 

Tip 4: When activating or staging multiple patches, run this command to speed up the post compile process:

qcontrol -jlocal,4  – This will set the servers cores to 4 when processing form compiles. Set it back to 2 when done. You can also check the status of the compiled jobs with command: qstatus | head -5

 

Tip 5: If a Plus dictionary is created after patching, its typically good practice to compile the entire product line with the command: cobcmp (be aware this can take up to 20-30 minutes to complete, tip 4 helps with this). This ensures that all programs are functioning correctly before passed to testers.

 

Bonus Tip: Verify security is on before sent to the testers!  Hope these were helpful.

 

If you require assistance with applying patches for your v10 system, it is common for organizations to engage Lawson consultant teams for managed services, which are available at a fixed monthly rate. These consultant teams possess significant knowledge and expertise and are suitable for larger organizations. Additionally, smaller organizations that do not require a full-time Lawson employee on-site may also find this service advantageous. Nogalis offers this service, and you can contact us through our contact page for further details.