Procedure to Copy Lawson Portal Bookmarks from/to Different Servers or Environments
Bookmark data is stored in three places:
-Database tables in the LOGAN product line (listed below)
-LAWDIR/persistdata/lawson/portal/data/users/<user>.xml files
-LAWDIR/persistdata/lawson/portal/data/roles/<role>.xml files
Reminder that the <user>.xml files in LAWDIR/persistdata/lawson/portal/data/users contain references (bookmark subscriptions and/or locks) to the bookmark IDs in the original bookmark data. You must EITHER delete the “to” environment or copy from the “from” environment to the “to” environment, before you begin. Skipping this step will lead to orphaned references within the .xml files, errors in the Preferences > Content screen.
Also, the Portal role files in the “Manage Roles” screen under Portal Administration in Portal/Ming.le must EITHER have all bookmark locks removed in the “to” environment, or the files should be copied from the “from” environment to the “to” environment, because they contain references to the bookmark IDs in the original bookmark data.
PROCEDURES
Update the <user>.xml files in the “to” environment:
Copy the <user>.xml files from LAWDIR/persistdata/lawson/portal/data/users directory to the “to” environment. Or you can remove all of the <user>.xml files in the “to” environment; they will be recreated when the user logs in and receives or assigns content. DO NOT DELETE THE default.xml file in LAWDIR/persistdata/lawson/portal/data/users.
Update the <portalrole>.xml files in the “to” environment:
Copy the <portalrole>.xml files from LAWDIR/persistdata/lawson/portal/data/roles directory to the “to” environment. Or you can remove all of the bookmark locks in the “to” environment’s <portalrole>.xml files and reapply the locks later.
Backup and delete existing data in the “to” environment:
Perform the following tasks in the “to” environment, where the bookmark data will be copied to.
Back up and delete the LOBKMARK records (in the LOGAN product line/data area).
Back up and delete the LOGRPBKMRK records (in the LOGAN product line/data area).
Back up and delete the LOUSRBKOPT records (in the LOGAN product line/data area).
Back up and delete the LOUSRBKMRK records (in the LOGAN product line/data area).
Back up and delete the LOBKCONFIG records (in the LOGAN product line/data area).
Back up and delete the SISETUP records (in the LOGAN product line/data area).
Create dump files of the existing data in the “from” environment:
Perform the following tasks in the “from” environment, where the bookmark data will be copied from.
dbdump -d logan lobkmark > lobkmark.dmp
dbdump -d logan lobkconfig > lobkconfig.dmp
dbdump -d logan sisetup > sisetup.dmp
dbdump -d logan logrpbkmrk > logrpbkmrk.dmp
dbdump -d logan lousrbkmrk > lousrbkmrk.dmp
dbdump -d logan lousrbkopt > lousrbkopt.dmp
If the “from” and “to” environments are on separate servers, copy the .dmp files to the “to” server.
Load the data from the dump files in the “to” environment:
Perform the following tasks in the “to” environment, where the bookmark data will be copied to.
dbload logan lobkmark lobkmark.dmp
dbload logan lobkconfig lobkconfig.dmp
dbload logan sisetup sisetup.dmp
dbload logan logrpbkmrk logrpbkmrk.dmp
dbload logan lousrbkmrk lousrbkmrk.dmp
dbload logan lousrbkopt lousrbkopt.dmp
Update the <portalrole>.xml files in the “to” environment:
Reapply bookmark locks if you removed them previously. If you copied the files over, you can skip this step.
Refresh the IOS cache:
Run IOSCacheRefresh (“Refresh IOS Cache” admin task).
Verify bookmark data is not corrupt:
Log into Portal and go to Bookmark Manager (“Manage Bookmarks” admin task). Add a new Top-Level bookmark. Then verify that you can see it at the top of the list of bookmarks in the Bookmark Manager. This is confirmation that the bookmarks are loaded properly and the data is not corrupted. If you don’t see it at all or it was added under another bookmark, then your bookmark data is corrupt and Support should be engaged.
Test the data from a user perspective:
Log into Portal as a user (or have a user test) and verify that the bookmarks in the “to” environment look the same as the “from” environment. If you copied the <user>.xml files over, the user shouldn’t notice any differences.
LSU Shreveport Partners with Infor to Create Better Experiences for Faculty and Students
NewsInfor recently announced that Louisiana State University Shreveport (LSUS) has partnered with Infor Hospitality to create better experiences for students and faculty on its campus. Through mobile ordering with Infor OrderNow and traditional point-of-sale (POS) terminals, this goal can be achieved throughout their over 200-acre campus. With students frequenting the dining areas every day, Infor Hospitality will deliver the tools needed to create the best possible platform to serve guests with efficiency, accuracy, and timeliness. Per the press release, LSUS was looking for a reputable technology partner with a solution that could easily integrate with LSUS’s current campus card management system to enable accessibility, continuity and visibility. Through seamless integrations, student and faculty will be able to easily view and track their balances or even split payments. Infor OrderNow has the ability to integrate with kitchen display solutions to enable a more efficient ordering process, as well as multiple payment options to make frictionless and secure payments. In addition, as part of the Infor Hospitality CloudSuite, Infor POS will help LSUS control incoming data from multiple revenue centers as transactions will securely integrate to leading payment platforms and loyalty applications, making for an easy-to-use, operationally versatile solution. The centralized management structure allows users to analyze performance at a single location in real time, allowing for greater efficiency and more informed decision making. Further, Infor OrderNow will provide LSUS with mobile ordering functionality, providing an alternative to counter-based ordering. And, because an app download is not required, it can be quickly and easily adopted by students and faculty for immediate uptake via QR code with campus management credentials.
For Full Article, Click Here
AS400 Debug Online Programs
Articles, Frontpage Article, NewsTo debug online programs through command-line entry, follow these steps:
CALL LAWENV
Note: If you need to include modules in the compile, use qcompile -Dm productline systemcode programcode .
Example (IBM i command line):
CALL TMCONTROL PARM(’-rp’ LAWAPP9 PR14)
Find the appropriate LATMProgramName job in the appropriate subsystem, and then select option 5 (Work with). Select option 1 to confirm that it is the correct job. If it is correct, return to the previous screen and note the job number, user name, and job name (which will be LATMProgramName).
Note: You can also use the WRKSBS command to find the appropriate subsystem and then LATMProgramName job.
STRSRVJOB JobNumber/UserName/JobName
ENDDBG
then
ENDSRVJOB
Weekly Patch Notification: December 31, 2022
Articles, Frontpage Article, PatchesIPA Variable Assignments Lost After Wait Node
Articles, Frontpage Article, NewsThere exists a scenario in IPA where variable values are lost after a wait node, if the variable is set using javascript as opposed to the straight assignment feature. This article will describe the workaround for this scenario.
In this sample, the first assign node uses javascript to set the variable apples. The 2nd assign node (after the wait node) sets the debug string variable to the value of the apples variable.
This excerpt from the work unit log shows that the variable debug is set to a blank value. This is because the value of the variable apples is lost after the wait.
To ensure that the variable value is not lost after a wait node, simply set the value of the variable to itself using the traditional variable assignment. This can be done any time after the javascript setting, and before the wait node.
As you can see, the debug variable is now successfully set to the value of the apples variable.
Four Predictions For AI In 2023
NewsAs artificial intelligence (AI) continues to establish itself in the technology space, its subset – machine learning (ML) is making strides to help set a pace for greater success. From major corporations to startups, ML teams are continuously working to deploy products that improve the way we work and live. Aparna Dhinakaran CPO at Arize AI, shares an article on Forbes predicting key AI trends we’ll see in 2023.
While any technology can be unpredictable, there is much to be optimistic about when it comes to the future of AI and ML.
For Full Article, Click Here
Top 5 Cybersecurity Trends to Keep an Eye on in 2023
NewsEven before the start of the pandemic, cyber crime threats have loomed over us. Now more than ever businesses must be prepared for ransomware and malware attacks to their databases. Security expert Mahima Jaiswal, shares an article on Security Boulevard forecasting the top 5 cybersecurity trends to look out for in 2023.
Jaiswal concludes as technology continues to evolve, cybersecurity threats and trends will also change. Businesses must stay ahead of the curve by keeping track of these trends and being prepared for any and all threats.
For Full Article, Click Here
How to setup Lawson Security to give user different security access in 2 different productlines in same environment at the same time
Articles, Frontpage Article, NewsYou might be wondering if it is possible in LSF to a give a person access to 2 different data areas (productlines) with 2 different roles at the same time.
So let’s say if user1 is in data area 1 and has the security access associated with the role that has access to data area (1) and then again user1 also is in data area 2 they have the security access associated with the role that has access data area (2).
More discreet way of putting it:
User1 >> DataArea1 >> ReadOnlyRole access in DataArea1.
User1 >> DataArea2 >> ChangeAccessRole access in DataArea2.
The best way to set this up is to separate the two DataSources so they each have their own Productline and their own separate security profiles. That’s it!
User1 >> DataArea1 >> ReadOnlyRole is in SecurityProfile1 which is set to DataArea1.
User1 >> DataArea2 >> ChangeAccessRole is in SecurityProfile2 which is set to DataArea 2.
Good luck!
ScandiNova Set for Powers Ahead with the Infor Cloud
NewsInfor recently announced that Swedish ScandiNova Systems AB (ScandiNova) has selected Infor CloudSuite Industrial Enterprise to help unify and standardise its operational and manufacturing processes. The system will be deployed by local Infor partner Midport Scandinavia and will be on the multi-tenant cloud, powered by Amazon Web Services (AWS). Per the press release, ScandiNova’s rapid growth is what prompted the need to deepen the use of enterprise resource planning (ERP) and business intelligence. Additionally, the company was looking for a solution to bring a commonality to its processes across all business sites, planning to unify and standardize systems to create a platform from which to pursue further growth. ScandiNova selected Midport with the Infor CloudSuite industry-leading manufacturing ERP system based on Infor LN because of the solution’s ability to handle complex processes and its industry-specific functionality set it apart from the competition, representing a truly global solution that can deliver the level of business agility that ScandiNova seeks to achieve. Further, a multi-tenant cloud deployment was also a crucial factor in ScandiNova’s decision, ensuring the business can benefit from continuous updates with minimal administrative burden on the in-house IT team, as well as enabling the swift on-boarding of new entities.
For Full Article, Click Here
Weekly Patch Notification: December 24, 2022
Articles, Frontpage Article, PatchesCopying Portal Bookmarks
Articles, Frontpage Article, NewsProcedure to Copy Lawson Portal Bookmarks from/to Different Servers or Environments
Bookmark data is stored in three places:
-Database tables in the LOGAN product line (listed below)
-LAWDIR/persistdata/lawson/portal/data/users/<user>.xml files
-LAWDIR/persistdata/lawson/portal/data/roles/<role>.xml files
Reminder that the <user>.xml files in LAWDIR/persistdata/lawson/portal/data/users contain references (bookmark subscriptions and/or locks) to the bookmark IDs in the original bookmark data. You must EITHER delete the “to” environment or copy from the “from” environment to the “to” environment, before you begin. Skipping this step will lead to orphaned references within the .xml files, errors in the Preferences > Content screen.
Also, the Portal role files in the “Manage Roles” screen under Portal Administration in Portal/Ming.le must EITHER have all bookmark locks removed in the “to” environment, or the files should be copied from the “from” environment to the “to” environment, because they contain references to the bookmark IDs in the original bookmark data.
PROCEDURES
Update the <user>.xml files in the “to” environment:
Copy the <user>.xml files from LAWDIR/persistdata/lawson/portal/data/users directory to the “to” environment. Or you can remove all of the <user>.xml files in the “to” environment; they will be recreated when the user logs in and receives or assigns content. DO NOT DELETE THE default.xml file in LAWDIR/persistdata/lawson/portal/data/users.
Update the <portalrole>.xml files in the “to” environment:
Copy the <portalrole>.xml files from LAWDIR/persistdata/lawson/portal/data/roles directory to the “to” environment. Or you can remove all of the bookmark locks in the “to” environment’s <portalrole>.xml files and reapply the locks later.
Backup and delete existing data in the “to” environment:
Perform the following tasks in the “to” environment, where the bookmark data will be copied to.
Back up and delete the LOBKMARK records (in the LOGAN product line/data area).
Back up and delete the LOGRPBKMRK records (in the LOGAN product line/data area).
Back up and delete the LOUSRBKOPT records (in the LOGAN product line/data area).
Back up and delete the LOUSRBKMRK records (in the LOGAN product line/data area).
Back up and delete the LOBKCONFIG records (in the LOGAN product line/data area).
Back up and delete the SISETUP records (in the LOGAN product line/data area).
Create dump files of the existing data in the “from” environment:
Perform the following tasks in the “from” environment, where the bookmark data will be copied from.
dbdump -d logan lobkmark > lobkmark.dmp
dbdump -d logan lobkconfig > lobkconfig.dmp
dbdump -d logan sisetup > sisetup.dmp
dbdump -d logan logrpbkmrk > logrpbkmrk.dmp
dbdump -d logan lousrbkmrk > lousrbkmrk.dmp
dbdump -d logan lousrbkopt > lousrbkopt.dmp
If the “from” and “to” environments are on separate servers, copy the .dmp files to the “to” server.
Load the data from the dump files in the “to” environment:
Perform the following tasks in the “to” environment, where the bookmark data will be copied to.
dbload logan lobkmark lobkmark.dmp
dbload logan lobkconfig lobkconfig.dmp
dbload logan sisetup sisetup.dmp
dbload logan logrpbkmrk logrpbkmrk.dmp
dbload logan lousrbkmrk lousrbkmrk.dmp
dbload logan lousrbkopt lousrbkopt.dmp
Update the <portalrole>.xml files in the “to” environment:
Reapply bookmark locks if you removed them previously. If you copied the files over, you can skip this step.
Refresh the IOS cache:
Run IOSCacheRefresh (“Refresh IOS Cache” admin task).
Verify bookmark data is not corrupt:
Log into Portal and go to Bookmark Manager (“Manage Bookmarks” admin task). Add a new Top-Level bookmark. Then verify that you can see it at the top of the list of bookmarks in the Bookmark Manager. This is confirmation that the bookmarks are loaded properly and the data is not corrupted. If you don’t see it at all or it was added under another bookmark, then your bookmark data is corrupt and Support should be engaged.
Test the data from a user perspective:
Log into Portal as a user (or have a user test) and verify that the bookmarks in the “to” environment look the same as the “from” environment. If you copied the <user>.xml files over, the user shouldn’t notice any differences.