In a previous article, we taught you how to bypass an error message “Internet Explorer cannot download file” on a Mobile Supply Chain Management, or MSCM, handheld. Today, we’re going to show you the simple way to to file share on MSCM handheld.
Occasionally you may need to copy the handheld CAB files to a file share so they can be loaded on the handhelds.
The local file path for MSCM up to version 11 is:
WAS_HOME\profiles\server\installedApps\cell\mscm.ear\hh.war
The local file path for MSCM starting with version 11.2 is:
WAS_HOME\profiles\server\installedApps\cell\mscm.ear\mscmwar.war\hh\installer
It’s that time again! Infor Cloud is releasing a patch bundle for 2022, which is a pre-requisite for their year-end patching. There are typically dozens (or hundreds) of patches applied during these bundles, to all the Infor applications hosted in the cloud. This can be an overwhelming prospect for users and IT staff who are tasked with testing and validation during these patches.
If you haven’t already taken the latest bundle, here are some quick tips for preparing your organization for a patch bundle:
Preparation
- Release notes: Infor always provides release notes on the patch bundle that they are implementing. These release notes will be attached to the KB article that is associated with your bundle (which should be referenced in your email communication for the bundle). If you are having trouble finding the KB article, your Infor account representative should be able to point you to it.
- Security: Occasionally the bundles will impact Lawson Security, and even more frequently they will implement new forms/fields/tables/columns that need to be secured. Run some security reports before the bundle so that they can be compared to the same reports after. Also, search your html release notes for any tokens that will be added, and determine if your organization needs to secure them.
- Reports: Run reports or queries for data validation, but also search the release notes for database changes, and make sure that you are ready to update any reports that are impacted by those changes.
MSCM
- Certificate: If you own MSCM, it is almost always going to be updated as part of the patch bundle. There is often an issue with the certificate after this update. Either the certificate is no longer valid, or it wasn’t generated during the patch. After the update, make sure you go directly to the CAB file location and that you see a valid certificate there (it’ll be named like your server). If you don’t see the file, or if you get security errors when trying to connect, open a ticket with Infor letting them know you think your cert is not valid.
- CAB files: It is best practices to delete all your CAB files from the handhelds and reinstall them after these major updates.
IPA
- Interface validation: There is a high probability that one or more of your IPA processes will be impacted by the patch bundle. It is important to test every single interface end-to-end.
- IP Designer: The IP Designer version MUST match the Landmark/IPA version exactly. So, after a patch bundle, you WILL have to download a fresh version of IPD.
Testing
- What to test: You are most likely going to need to test everything. Daily, weekly, monthly, and annual processes should be included in your testing.
- How to test: Provide users with test scripts for each function, and have a central location for users to log the results. We like to use Monday.com as our central repository for testing.
Validation
- You can use LID to validate data counts. You should also compare pre-update reports to post-update reports in all applications, including security.
Nogalis has assisted many cloud clients through the implementations of these patch bundles, and we would love to assist you as well! We have some great resources on hand who can provide managed services of your system, training, and project work. Check out our managed services program, or email our managed services and cloud expert Desi at [email protected] for inquiries about project work.
When running SRGEN in Lawson on iSeries/AS400 there are some things to consider. first, make sure you have the lawson source library LAWSRC in your library list. If the LAWSRC source library is not in your library list, your screen rules will not be updated. You should also make sure to put LAWSRC above your modification library and make sure they contain lawson source files as well as the .sr members before you run SRGEN. Lastly, the syntax for running SRGEN is CALL SRGEN PARM(LAWAPP SYSTEMCODE), where systemcode is your Lawson system code (i.e. HR). If you need to create screen rules (.sr) for multiple system codes, separate the system codes with a single space (i.e. HR GL AP IF AR).
In your organization, you may want to set the default application to Lawson Portal or MSCM for all users when they first login. To do this, follow the steps below.
First login to Infor Mingle.
Go to the user icon on the top right and select User Management
Once in user management, open the waffle icon on the top left
You should see all the Lawson apps you have access to here
In order to make Infor Lawson the default application, click and drag that icon and make sure it’s the top left most Icon.
The first icon in the top left will always load by default.
As of writing this, this should be the way to set the default app globally but can change in the future.
Reload the page and the default application should stay the same.
To Install a CTP on AS400, follow these guidelines:
Open a green screen and go to command line:
Enter the following commands:
call lawenv
qsh
cd $LAWDIR (or location of tar files)
The Versions file is EBCDIC instead of ASCII. You will use /QOpenSys/usr/bin/tar to unpack package.
Otherwise, you will get this error:
Error: Versions file is wrong CCSID.
If so, you will need to remove all untarred files from directory and start over with QOpenSys/usr/bin/tar
/QOpenSys/usr/bin/tar -xvf 9.0.1_patch_84930.tar
x 9.0.1_patch_84930.readme.html, 331911 bytes, 649 media blocks.
x Versions, 5816 bytes, 12 media blocks.
x Tasks, 3034 bytes, 6 media blocks.
x patch.tar.Z, 2483873 bytes, 4852 media blocks.
$
perl $GENDIR/bin/lawappinstall preview ProdLineName
perl $GENDIR/bin/lawappinstall update ProdLineName
perl $GENDIR/bin/lawappinstall activate ProdLineName
check for errors
ls $LAWDIR/ ProdLineName/rpg/*rpg/*SRC/*.err
Hit F3 to exit command line
Dspmsg to Display messages
If you find any failed job enter
Wrkjob # for failed job
When troubleshooting issues, you can look at the base UI of Infor applications temporarily without configurations by simply modifying the URL.
It is important to note that the URL addition must go on the Landmark URL (not Ming.le).
To open up the landmark URL, first right-click on any of the menu items on the side panel and select “Open link in new tab”.
Next, you will need to add the text &csk.disableuiconfigs=true to the URL. Keep in mind that this will only work for the HTML4 web UI.
That’s all there is to it. You’ve successfully disabled custom configurations in Infor web applications.
