Archive for category: Frontpage Article

You are here: / / Frontpage Article

ISS: How to review logs after running an Infor Security Services (ISS) sync

, ,

You will want to start by reviewing the security_provisioning.log(s) in your LAWDIR/system directory.

 

All transactions completed in ISS related to user maintenance, federation, and synchronization, are logged in the LAWDIR/system/security_provisioning.log(s).

Please note, the log may take a few minutes to complete after the sync completes in the browser. Once the logs have completed, best practice is to copy the log(s) to a new directory so that they are not overwritten while you are researching the sync errors.

Open the most recent provisioning log and go to the bottom of the log. If nothing has been done in ISS since the sync completed you should see a message similar to the one below followed by a list of records that failed:
Thu Apr 26 16:56:01.282 CDT 2018 – default-457261151: Sync Analysis for object type IDENTITY completed with status=true
Thu Apr 26 16:56:01.282 CDT 2018 – default-457261151: Sync Analysis successfully completed for object type IDENTITY
Thu Apr 26 16:58:52.073 CDT 2018 – 1360326122: Sync Execution successfully completed for Task ID[4,963] with failed transactions for Sync Records:

The list of records that failed is limited to one section of the sync. You will see a list of either roles, actors, services, domains, endpoints endpoint groups or identities, depending on which section of the sync had failed records. This is because once the sync completes the analysis or execution of the section with the failed records the sync process will not continue. You must address the failed records to continue the sync.

Alternately you can search the log for the word “completed” to find the most recent section of the sync process that completed. There will be a completed message for each section of the sync.

 

Examples of completed messages without failed records:

Thu Jan 28 10:50:29.536 GMT-06:00 2021 – default-1845137754 – L(4) : Sync Execution task for [ROLE] with Task ID [1207] started.
Thu Jan 28 10:50:29.536 GMT-06:00 2021 – default-1504145202 – L(4) : Setting progress percentage [-1]
Thu Jan 28 10:50:29.537 GMT-06:00 2021 – default-1504145202 – L(4) : Success updating task [1207]
Thu Jan 28 10:50:29.537 GMT-06:00 2021 – default-1504145202 – L(4) : Starting Sync Execution using pagesize [500] and Nthread [5]
Thu Jan 28 10:50:29.551 GMT-06:00 2021 – default-1504145202 – L(4) : Retrieved 0 ROLE for execution
Thu Jan 28 10:50:29.551 GMT-06:00 2021 – default-1504145202 – L(4) : Sync Execution Successful for ROLE
Thu Jan 28 10:50:29.551 GMT-06:00 2021 – default-1504145202 – L(4) : SyncExecution execution time for [ROLE] took [0] seconds to complete

Thu Jan 28 10:55:33.485 GMT-06:00 2021 – default-863748063 – L(4) : Sync Execution task for [DOMAIN] with Task ID [1219] started.
Thu Jan 28 10:55:33.500 GMT-06:00 2021 – default-1293059945 – L(4) : Setting progress percentage [-1]
Thu Jan 28 10:55:33.500 GMT-06:00 2021 – default-1293059945 – L(4) : Success updating task [1219]
Thu Jan 28 10:55:33.502 GMT-06:00 2021 – default-1293059945 – L(4) : Starting Sync Execution using pagesize [500] and Nthread [5]
Thu Jan 28 10:55:33.506 GMT-06:00 2021 – default-1293059945 – L(4) : Retrieved 0 DOMAIN for execution
Thu Jan 28 10:55:33.506 GMT-06:00 2021 – default-1293059945 – L(4) : Sync Execution Successful for DOMAIN
Thu Jan 28 10:55:33.506 GMT-06:00 2021 – default-1293059945 – L(4) : SyncExecution execution time for [DOMAIN] took [0] seconds to complete

 

Examples of completed messages with failed records:

Thu Jan 4 07:19:55.755 EST 2018 – default- 2123289590: SyncAnalysis for ACTOR have 2 error records
Thu Jan 4 07:19:55.755 EST 2018 – default- 2123289590: Sync Analysis for object type ACTOR completed with status=true
Thu Jan 4 07:19:55.842 EST 2018 – 2123289590: Sync Analysis completed for object type ACTOR with failed Sync Records:
ACTOR=user1;
ACTOR=user2;

Tue Apr 19 10:18:33.128 CDT 2018 – default-1441714547: SyncAnalysis for ENDPOINT have 7 error records
Tue Apr 19 10:18:33.128 CDT 2018 – default-1441714547: Sync Analysis for object type ENDPOINT completed with status=true
Tue Apr 19 10:18:33.130 CDT 2018 – 1441714547: Sync Analysis completed for object type ENDPOINT with failed Sync Records:
HTTPPORT=82,SSODOMAIN=CSEMSS_EXTERNAL,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=1448;
HTTPPORT=81,SSODOMAIN=CS_INTERNAL,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=443;
HTTPPORT=81,SSODOMAIN=CS_INTERNAL,FQDN=WFHPROD-LM01.COM,HTTPSPORT=1443;
HTTPPORT=85,SSODOMAIN=TC_LDAP_BIN_EXT,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=1447;
HTTPPORT=85,SSODOMAIN=TC_LDAP_BIN_EXT,FQDN=WFHPROD-LM01.COM,HTTPSPORT=1447;
HTTPPORT=9080,SSODOMAIN=CS_INTERNAL,FQDN=WFHPROD-MSCM01.COM,HTTPSPORT=8443;
HTTPPORT=21442,SSODOMAIN=CS_INTERNAL,FQDN=WFHPROD-IES01.COM,HTTPSPORT=9443;

Tue Apr 3 10:51:21.774 EDT 2018 – default-471380075: SyncAnalysis for IDENTITY have 4 error records
Tue Apr 3 10:51:21.774 EDT 2018 – default-471380075: Sync Analysis for object type IDENTITY completed with status=true
Tue Apr 3 10:51:21.774 EDT 2018 – 471380075: Sync Analysis completed for object type IDENTITY with failed Sync Records:
IDENTITY=USER:DOMAIN\user1,SERVICE=SSOP,ID=user1;
IDENTITY=USER:DOMAIN\user2,SERVICE=SSOP,ID=user2;
IDENTITY=USER:user1@domain.com,SERVICE=THICKCLIENTLDAPLS,ID=user1;
IDENTITY=USER:user2@domain.com,SERVICE=THICKCLIENTLDAPLS,ID=user2;

To find the exceptions for the failed records you will need to search within the log(s) each failed record. For each failed record you will search for the value from the list without the semicolon at the end of the line:
For failed record ACTOR=user1; you will would search for “ACTOR=user1”
For failed record HTTPPORT=82,SSODOMAIN=CSEMSS_EXTERNAL,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=1448; you would search for “HTTPPORT=82,SSODOMAIN=CSEMSS_EXTERNAL,FQDN=WFHPROD-LSF01.COM,HTTPSPORT=1448”
For failed record IDENTITY=USER:DOMAIN\user1,SERVICE=SSOP,ID=user1; you would search for “IDENTITY=USER:DOMAIN\user1,SERVICE=SSOP,ID=user1”

 

XM ER Not Showing – Expense Report

, ,

Recently a user submitted an error that could be useful for anyone else who encounters it.

 

Problem

The user is reporting they are not seeing Expense Reports in Lawson XM. They are receiving emails.

 

Solution

While this could be an alerting problem, we have a quick fix for user error.

 

The user needs to log into Mingle. Once logged in and in XM, simply click on the filter option at the top right of the screen. Here, you must make sure you clear your filters as shown below:

Log back in and you should not have the missing error again.

Migrating Lawson On-Premise to Infor Cloudsuite

, ,

As businesses grow and technology advances, it’s not uncommon for companies to outgrow their current enterprise resource planning (ERP) software. In some cases, this may mean moving from an on-premise solution, such as Lawson, to a cloud-based platform like Infor Cloudsuite. If you’re considering making the switch, here are some steps to keep in mind.

  1. Evaluate your current system: Before making any changes, it’s important to evaluate your current system to identify what’s working well and what needs improvement. Consider factors like system performance, ease of use, functionality, and cost. This will help you determine whether Infor Cloudsuite is the right choice for your organization and identify any specific features or functions you need to ensure a successful transition.
  2. Plan your migration: Once you’ve decided to move to Infor Cloudsuite, the next step is to plan your migration. This involves determining what data needs to be migrated, setting a timeline for the transition, and identifying any potential challenges or roadblocks. It’s also important to consider how the migration will impact your business operations and develop a plan to mitigate any disruptions.
  3. Prepare your data: Before migrating to Infor Cloudsuite, you’ll need to ensure that your data is ready for the transition. This may involve cleaning up data, consolidating data sources, and preparing data for the new platform. It’s important to work closely with your IT team to ensure that data is transferred accurately and securely.
  4. Prepare interfaces: Determine which interfaces, both internal and between 3rd party vendors, will need to be rewritten, and which ones can be archived.  Work closely with IT to refactor or recreate the interfaces and prepare them for the new cloud environment.
  5. Train your staff: Moving to a new ERP platform can be a significant change for your organization, so it’s important to provide training and support to your staff. This may involve providing training on the new system, helping staff understand how to use new features, and ensuring that they have the resources they need to be successful.
  6. Go live: Once you’ve completed all of the necessary preparation and training, it’s time to go live with Infor Cloudsuite. This is a critical phase of the transition, as it’s important to ensure that the new system is fully operational and that any issues are quickly addressed. It’s also important to have a plan in place to handle any unforeseen issues or challenges that may arise during this phase.
  7. Monitor and optimize After the transition is complete, it’s important to continue monitoring the new system to ensure that it’s meeting your organization’s needs. This may involve tracking system performance, identifying areas for improvement, and making changes to optimize the system. By continually monitoring and optimizing the system, you can ensure that you’re getting the most out of Infor Cloudsuite and supporting your organization’s ongoing success.

In conclusion, moving from Lawson on-premise to Infor Cloudsuite can be a complex process, but by following these steps and working closely with your IT team and vendor, you can ensure a successful transition. By choosing a cloud-based ERP solution like Infor Cloudsuite, you can benefit from improved functionality, scalability, and cost-effectiveness, supporting your organization’s growth and success in the years to come.

 

Searching on user information via the Infor Security Services (ISS)

, ,

Search results are incorrect for user/resource information via the Infor Security Services (ISS).

However, the user search is correct in Lawson Security Administrator (LSA) tool and Infor Rich Client (IRC).

Search results in ISS are returned from a search index, not directly from LDAP as is the case with LSA or the GEN database as is the case with IRC. The search index may not be updated if changes are made outside of ISS. Changes made directly in IRC will NOT update the search index.

To resolve the issue, you need to rebuild the search index that ISS uses using ssoconfig.

Open Lawson Interface Desktop (LID) and connect to the Lawson System Foundation (LSF) server or from a command line with environment variables set:

Type ssoconfig -c and press enter

Enter your password for ssoconfig

Choose the option for Manage Search Index and press enter.

Choose the option for Build Resources Full Index and press enter.

This part can take a while, how long depends on the number of resource, identity, and service records in LDAP. You can monitor the progress of the rebuild in the LAWDIR/system/security_search.log

Wait for the menu options to come back and then choose Build Monitoring Full index.

When the menu comes back to where you can choose the build options again the rebuild has completed and you can try your search in ISS again.

Either way you rebuild the index, you can verify that the rebuild is complete by verifying the following in the LAWDIR/system/security_search.log:

Tue Mar 13 22:47:01.006 CDT 2018 – default-434727101: Done indexing identities

Tue Mar 13 22:47:01.007 CDT 2018 – default-434727101: Closing index…

Tue Mar 13 22:47:01.037 CDT 2018 – default-434727101: Activating index…

Tue Mar 13 22:47:01.038 CDT 2018 – default-434727101: Index activated

Tue Mar 13 22:47:04.073 CDT 2018 – default-434727101: Finished indexing

 

ISS: How to research and resolve IDENTITY record failures in the sync

, ,

For errors related to the failed IDENTITY records from an ISS sync follow these steps:

Determine which system, Lawson System Foundation (LSF) or Landmark (LMK), the identity record failed in:

After finding the exception in the log, scroll up in the log until you see a message such as this:

Getting resource from INFORBCLM01.INFORBC.COM;9906;9907;LANDMARK

or

Getting resource from INFORBCLS01.INFORBC.COM;6626;6627;LSS

or

Processing record #4,996 of LSF

or

Processing record #4,986 of LANDMARK

Messages that reference LSS or LSF indicate the issue is in LSF and the record should be reviewed in that system. Messages that reference LANDMARK indicate the issue is in LMK and the record should be reviewed in that system.

 

How to resolve Lawson XM Error – No XM User exists with User Principal Name

, ,

Lawson XM errors are never good, but can easily be resolved. For example, you make come across this Lawson XM error: “No  XM User exists with User Principal Name (UPN)” (see screen shot below)

This error can easily be resolved by checking the settings for specific permissions.

In LSF ISS you must make sure that the SSOP identity user matches the Second user Identity (IFS) in XM SAT. These parameters allow users to log in to Mingle XM via SSOP and allows users to log in to SAT. Once you confirm these permission settings, you shouldn’t have the error again.

 

Advantages to hosting ERP in AWS over Microsoft Azure

, ,

In today’s digital era, Enterprise Resource Planning (ERP) systems have become crucial for businesses of all sizes. These systems help organizations manage their day-to-day operations efficiently by providing a single source of truth for all data related to finances, inventory, customer relationship management, and more. However, choosing the right cloud provider for hosting an ERP system is critical for the success of your business. In this blog post, we will discuss the advantages of hosting an ERP system in Amazon Web Services (AWS) over Microsoft Azure.

 

Scalability

AWS is known for its scalable cloud infrastructure, which can support businesses of all sizes. As the demand for an ERP system grows, AWS can easily scale up the infrastructure to accommodate the increased traffic. AWS offers a wide range of resources such as compute, storage, and databases, which can be scaled up or down based on business needs. Microsoft Azure also offers scalability, but AWS’s scalability capabilities are considered superior.

 

Security

Security is a top concern for any business when it comes to cloud hosting. AWS has a robust security model and offers various security features such as network isolation, encryption at rest and in transit, and identity and access management. AWS also complies with various security standards such as SOC 1/2/3, PCI DSS, and HIPAA. Microsoft Azure also provides robust security features, but AWS’s security features are considered more mature and reliable.

 

Cost-effective

Cost-effectiveness is a critical factor for any business when it comes to cloud hosting. AWS offers various pricing models, including pay-as-you-go and reserved instances, which can help businesses save money on hosting an ERP system. AWS also offers various cost optimization tools such as AWS Cost Explorer, which can help businesses analyze their spending and optimize their costs. Microsoft Azure also offers cost optimization tools, but AWS’s pricing models are considered more flexible and cost-effective.

 

Reliability

Reliability is crucial when it comes to hosting an ERP system. AWS has a global infrastructure that spans across various regions, which helps ensure high availability and reliability. AWS also offers various services such as Amazon CloudWatch and Amazon Route 53, which can help businesses monitor the availability and performance of their ERP system. Microsoft Azure also offers high availability and reliability, but AWS’s global infrastructure is considered more reliable.

 

Conclusion

In conclusion, hosting an ERP system in AWS offers several advantages over Microsoft Azure. AWS offers scalability, robust security features, cost-effectiveness, and reliability. While Microsoft Azure also offers these features, AWS’s capabilities are considered superior. Therefore, businesses looking to host an ERP system in the cloud should consider AWS as their preferred cloud provider.