Archive for category: Articles

At times, you may get the following errors rebuilding the search index for Infor Security Services (ISS):

JVMDUMP039I Processing dump event “systhrow”, detail “java\lang\OutOfMemoryError” at 2023/03/25 19:35:53 – please wait.

To resolve these errors, do the following:

Adjust the JVM max memory size for ssoconfig in the GENDIR\java\command\ssoconfig.properties to 4096m

Before: ljx.vm.options=-Xmx512m

After: ljx.vm.options=-Xmx4096m

Next, save and close the file

This change is dynamic and does not require a restart, but you must exit ssoconfig for it to take effect.

After the change is completed and you’ve exited from the ssoconfig menu, you can now go back into ssoconfig -c  to choose the rebuild the search index.

This article shows you a step by step guide on how to resolve the following Lawson error:

“loadResource(): returned identity [User:] already exists“

We need to run a list-based sync but first let’s explain what it is.

How list-based sync works:
Initially, an XML file containing all the records to be synchronized is required for executing the procedure. Later, the ssoconfig utility is employed to import the file. As a result of the sync command, all the relevant data related to actors/users, identities, and their associated roles (and services if required) is transferred from the “original system” (the one with updated data) to the “target system” (the one in need of an update).

Note: Please keep in mind that when synchronizing, if a service is present on the original system but not on the target system, it will be generated on the target system. It is important to note that syncing of services is a one-time process.

By default, during synchronization, Actor Roles are included with other user information and combined. For instance, if an Actor record in the LSF has one role “NormalUser,” and the same Actor is present in Landmark with two roles “NormalUser” and “BenefitsClerk,” then after synchronization, both systems would display “NormalUser” and “BenefitsClerk” for that actor. However, if you prefer to prevent the merging of Actor Role attributes, you can override the default setting in the input file. In this case, you will be asked to decide between Update Local or Update Remote action for each difference, similar to other attributes.

Create the XML input file (default behavior for Actor Roles)

Prepare an XML file in the suitable format for importing. The following example depicts the standard approach, where Actor Roles are combined during synchronization.

Example File:

XML input file in which you specify behavior of Actor Roles

This instance contains the “mergeActorRoles” attribute, which is present in the file and set to “false.” Consequently, the roles will not be merged, and the specified action in the XML file will be followed instead.

NOTE:  If you require the merging of roles for some Actor records, you should adjust the “mergeActorRoles” attribute to “true.”

Example file:

Run the import command using the ssoconfig utility

1. Execute the import command using the ssoconfig utility. Open a command window and enter the following command:

ssoconfig -S PWD <full_path_and>InputFileName

In this command, replace PWD with the security administrative password and <full_path_and>InputFileName with the name of the input file that you created in the previous step.

Once entered, a notification will confirm that the synchronization process has begun.

2. To monitor the synchronization progress, navigate to the Check Background Sync Status option within the Manage Federation sub-menu.

Validate results.

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!