Mass remove candidates or suppliers and their identities from LSF

, ,

Candidates and suppliers from Landmark applications should not be synced to LSF. Services which allow users to register externally are services that should NOT be synced. If they were synced to LSF, follow the steps below to remove user and identity records from LSF.

Configure sync service lists to exclude candidates from sync – This process should be used if possible
Use Configure Services for Synchronization menu in ISS

Manual Sync service list configuration – This process may be used if not all services are shown in ISS
Export list of all services from LMK
 secadm -p <secadmpassword> service list
 The list outputs to the screen –copy the list from the screen into a text document
Determine which services from each system you DO want synced

Configure sync service lists for LSF and LMK in the LSF by adding the following lines to LAWDIR/system/lsservice.properties file:

 fed.LSFSERVERNAME.DOMAIN.COM;40000;40001;LSF. syncServiceList=YourListofLSFServicesToSync,SeparatedByCommas,NoSpaces fed.LMKSERVERNAME.DOMAIN.COM;10888;11888;LANDMARK. syncServiceList=YourListofLMKServicesToSync,SeparatedByCommas,NoSpaces

 Save changes and close lsservice.properties
Restart LSF and WAS

Configure tuning for sync*

  1. Add the following line to the LAWDIR/system/lsservice.properties

file: Nthread=5

This value can be any number between 2 and 10. You can tweak the Nthread parameter until you find the optimized setting for your system. Do not go above 10 unless directed by Infor.

  1. Adjust lase GRID node max heap to at least 3096

From the Grid Management main page go to Configuration Manager->Applications->Application->Landmark and the select the environment.
Select “Edit Properties.”
Under Grid Defined Properties -> Node Memory, select “Max Heap.”
Adjust the lase node memory to 3096 and then click Save
It may be set higher if number of users/identities indicates
-Restart the node for this environment or restart Landmark.

 

Infor, AWS research points to uneven ERP modernization and widening governance gaps

Many organizations adopt cloud ERP (enterprise resource planning) without the strategic governance needed to realize full value, leaving aging systems with declining satisfaction and hidden technical debt that internal reviews often miss. Achieving true ERP agility requires disciplined, reusable integration and strong data-quality standards to reduce costs and fully leverage cloud ecosystems. In a recent article on ERP Today, ERP writer and content director Tarsilla Moura reports on research by Infor, AWS, and Radar Group showing that many organizations are modernizing ERP in name only, with cloud adoption outpacing the strategic governance needed to drive real business value. The study finds that while 42% of organizations run ERP in the cloud, only 64% have a defined cloud strategy, leaving others to make ad-hoc decisions that increase costs and reduce control.

ERP systems often sit in a “mid-life comfort zone,” averaging 6.4 years old, with technical debt growing and satisfaction declining as systems age. Investment trends show that while overall technology budgets are rising, ERP spending lags, and initiatives like AI and ML are being pursued without the governance and integration readiness needed to unlock their full potential.

The research emphasizes that modernization is more than cloud hosting. ERP must be treated as a strategic business platform, supported by governance, integration standards, security models, and outcome-based KPIs. Recommendations include defining a clear ERP and cloud strategy, establishing decision rights, adopting a roadmap tied to business outcomes, and leveraging external assessments to expose blind spots.

Integration discipline emerges as the critical factor for ERP agility. Fragmented integrations drive costs and slow change, even in cloud-first environments. Treating integration as a product function—with reusable patterns, deprecation plans, and strong data-quality standards—ensures ERP can scale with business needs and fully leverage cloud ecosystems.

For IT leaders and ERP managers, the takeaway is clear: cloud adoption alone isn’t enough. Without structured governance and disciplined integration, ERP risks remaining a platform in place rather than a driver of operational improvement.

 

For Full Article, Click Here

Change the Passwords in install.cfg

, ,

The passwords in install.cfg are encrypted in later versions of lawson.  If these passwords change, it would be ideal to also change them in install.cfg so the next update doesn’t run into any issue. To do this, follow the instructions below:

First, Open a command line utility with Lawosn env variables set.

Then type in the command java -cp %GENDIR%/java/thirdParty/installer.jar com.lawson.delivery.secure.PasswordAdministrator -s %LAWDIR%/system/install.cfg

Enter the Lawson configuration password

Next, View or edit passwords.  You can show them in clear text by clicking the “Yes” radio button.

Click finish when done

Restart Lawson services, or reboot the server. This should make the necessary changes and prevent any issues.

The High Cost of Standing Still with Legacy ERP in Uncertain Conditions

Distributors that hold onto outdated enterprise resource planning (ERP) systems may feel they’re avoiding risk, but the hidden costs of inaction steadily erode visibility, agility, and margins—making a structured, phased modernization approach the key to turning that risk into long-term resilience. In a recent article on MDM.com, author Jon Byrd highlights this particular challenge that many distributors quietly face.

 

While keeping an aging ERP in place can feel like the “safer” choice, Byrd argues that inaction is far from neutral. Support fees climb, specialized expertise becomes harder to find, and outdated hardware lingers long past its intended lifespan. But the financial hit is only part of the story. Legacy systems limit real-time visibility, making it harder to respond quickly to supplier price shifts or margin pressures — a problem every IT director or operations leader has felt at some point. Integration challenges compound the issue. Modern capabilities like AI-driven insights, digital sales platforms, and advanced analytics don’t plug neatly into old architectures. IT teams end up maintaining brittle workarounds that consume time and budget while still failing to deliver true agility. Slow reporting cycles further drag down decision-making, often leaving organizations reacting well after competitors have moved. Add to that the looming issue of end-of-support timelines — and the security risks or pricey extended-support agreements that follow — and the “do nothing” strategy quickly starts siphoning value.

Byrd also acknowledges the real risks of ERP modernization: data inconsistencies, process redesign, employee resistance, and replacing heavily customized legacy functions. But distributors succeeding with cloud ERP approach the shift as a structured journey: upfront assessments, phased rollouts, strong data governance, and rigorous testing. The takeaway: legacy ERP doesn’t just limit growth — it actively erodes competitiveness. With customer expectations rising and uncertainty persisting, modernizing intentionally isn’t just an IT initiative; it’s a strategic necessity.

 

For Full Article, Click Here

How to include Report ID in LBI Maintain Reports

, ,

Follow these simple steps to learn how to include Report ID in LBI Maintain Reports

  1. First, go into Tools when logged in as an admin and select “Reporting Services My Reports”.
  2. Under the “All” section in the Report Lists on the left side dash, click “Edit List” on the top right of the screen.

  3. Next, under “List Options” select “Columns”.
  4. Then select “Report Id” and click the right arrow in the middle of the screen:
  5. Click “Save and Exit” and then go to “Maintain Reports” in the Reporting Services Administration Report Management Menu.
  6. Now you’ll see all the Report ID’s on the right hand column:

 

That’s all there is to it!

Infor Named a Leader for Fifth Consecutive Year in 2025 Gartner® Magic Quadrant™ for Cloud ERP

Infor has been named a Leader for the fifth consecutive year in Gartner’s 2025 Magic Quadrant for Cloud ERP for Product-Centric Enterprises. The recognition underscores Infor’s consistent strength in delivering cloud-native, industry-tailored ERP solutions.

In Gartner’s 2025 Critical Capabilities report, Infor earned highest scores in three of seven use cases: Process Manufacturing, Project/Asset-Intensive Manufacturing, and ERP for Lower Midsize Enterprises ($50M–$250M). It also secured a #2 ranking in Discrete Manufacturing, maintaining top-tier status there for six consecutive years.

Rick Rider, Infor’s SVP of Product Management, emphasized that these honors reflect the company’s focus on modernizing operations with solutions like Infor Leap and Industry AI Agents, which help customers leverage cloud ERP while unlocking new efficiencies and growth opportunities.

Gartner’s analysis also highlighted market trends shaping ERP evolution, including generative and agentic AI, low-code development, process mining, and tighter integration capabilities. These features are increasingly crucial for organizations seeking agility, operational insight, and competitive advantage.

For IT leaders, ERP managers, and system administrators, Infor’s continued recognition signals a stable, innovation-driven partner capable of supporting complex manufacturing and distribution environments while staying ahead of emerging technology trends.

 

For Full Article, Click Here

Another Outage. Another Warning. Are Your Systems Built for This Reality?

 

When you look at Cloudflare’s recent outage, AWS disruptions, and airline IT incidents like Alaska Airlines earlier this year, a pattern emerges. These aren’t random glitches. They reflect deeper, systemic issues in today’s hyper-connected infrastructure—where a single misconfiguration or service failure can ripple across the entire digital ecosystem.

As organizations rely more heavily on cloud platforms, global CDNs, and centralized systems, even small failures can lead to large operational shocks. The real question is no longer if an outage will affect your business, but whether your systems are prepared to withstand it.

 

ERP Systems: The First to Feel the Impact

ERP platforms sit at the center of finance, operations, supply chain, and HR. When external or internal infrastructure breaks, ERP users often experience:

  • Authentication failures
  • Stalled workflows or batch jobs
  • Broken integrations
  • Delayed purchasing, shipping, and approvals

A brief outage elsewhere can quickly become enterprise-wide downtime.

 

Data Access & Storage: Redundancy Isn’t Enough

This year’s outages made one point clear: Data that exists but can’t be accessed is effectively down.

DNS failures, routing issues, CDN disruptions, and cloud zone outages can suddenly block:

  • File repositories
  • Data lakes
  • ERP historical records
  • Cloud storage buckets

Organizations often have backups—but no guarantee that users can reach critical data during an outage.

 

Cybersecurity: Availability Is Part of Security

The Cloudflare incident showed that security systems themselves—identity, permissions, and zero-trust rules—can become failure points. A malformed security configuration can knock systems offline just as quickly as an attack. Strong cybersecurity must include validation, testing, and controlled configuration management.

 

Backup & Recovery: Strategy vs. Reality

Many companies have backup plans, but few have tested recovery plans. Unverified failovers and outdated procedures turn minor issues into major disruptions. True resilience requires:

  • Regular recovery testing
  • Independent, isolated data archives
  • Emergency read-only access modes
  • Clear, practiced procedures

Our consulting team specializes in ERP operational resilience. We offer Managed Services, with proactive ERP monitoring, maintenance, security hardening, and rapid-response support to reduce unexpected downtime, as wel las a cloud-secure ERP Application Archive solution – APIX – that ensures ERP data remains accessible—even during cloud outages or ERP failures. If recent outages have you rethinking your resilience strategy, let’s talk. Nogalis is here to help organizations build stability into their ERP, data, and infrastructure before the next disruption hits.

GL256 No report in Print Manager

, ,

Problem:
If a GL256 was run but did not create a report in the Print Manager, but, there is a csv file, follow these simple and quick steps to change the csv output to a prt file.

 

Resolution:
First, you will need to create a GL55.1 for this report.

Navigate to the Basic Tab, then change the CSV Output parameter from Y (Yes) to N (No).

Next, Re-run the GL256 and it will produce a regular report in the Print Manager.

This should create a report in print manager with the proper output format.

That’s all there is to it!

Why 92% of Companies Lack AI-Ready Data

In her recent ERP Today article, Radhika Ojha highlights a surprising statistic: while 97% of organizations feel pressure to deploy artificial intelligence (AI) quickly, a whopping 92% aren’t ready. The reason isn’t lack of talent or infrastructure—it’s messy, siloed data. Finance, sales, HR, manufacturing, and supply chain systems often live in separate platforms that don’t communicate, making it nearly impossible for AI to deliver meaningful insights.

The Cisco AI Readiness Report shows that data is the weakest pillar for most companies. AI models need clean, unified data to work, but many organizations focus on hiring data scientists or investing in algorithms while ignoring the fragmented data in their ERP systems. Without consolidating and cleaning decades of historical records, AI initiatives can stall, and predictive insights—like customer churn or supply chain forecasting—remain out of reach.

The first step toward AI readiness, Ojha states, is aggregation. Platforms like JiVS IMP from Data Migration International can consolidate, clean, and structure data from across legacy systems, creating a single, AI-ready foundation. For ERP leaders, this means that any system migration—like SAP S/4HANA—should focus not just on moving data, but on making it usable for AI. In short, before AI can start providing real value, organizations must ensure their core ERP data is structured, accessible, and ready for intelligence.

For Full Article, Click Here