It’s official, you have finalized the project to move to Cloudsuite and are ready to begin your journey to the cloud. But wait! What will you do with all your Lawson legacy data? By now you probably know that you can’t take it all with you to the cloud without a massive undertaking. Even then, your data retention policies may not allow you to turn off your Lawson 10x (or 9.0.1) servers just yet. Looks like you have more work to do.
Endpoints allow for external web servers to host Lawson Portal and authenticate against the chose authentication method for the main LSF application.
To create an endpoint,
Log into ssoconfig -c
Choose option “Manage SSO Domains” > “Add new SSO Domain”
Name the domain INTERNAL
Select the primary service that you will be using for authentication (might be SSOP or your thick client service)
Give the domain a meaningful description
Go back to the main menu and select “Manage Lawson HTTP Endpoints” > “Add new HTTP Endpoint”
Enter the fully qualified domain name for your endpoint
Enter the HTTP port (if you are using SSL, enter -1)
Enter the HTTPS port (if you are not using SSL, enter -1)
Enter the domain you created above
Select “Assign HTTP Endpoint to Service”
Assign the endpoint to the chosen authentication service
Enter the ports used to create the endpoint
Enter the name of the authentication service this endpoint should use for authentication (usually SSOP or your thick client service)
Repeat these steps to assign the endpoint to the IOS service, BPM service, and LSADMIN service.
Go back to the main menu.
Go to “Manage Lawson HTTP Endpoint Groups” > “Add new HTTP Endpoint Group”
Add a group for your external service with a meaningful name
Go back to “Manage Lawson HTTP Endpoint Groups” > “Add HTTP Endpoint to Group”
Enter the group name you just created above
Enter the endpoint name
Enter the points that were configured for the endpoint
Restart Lawson
Important step!! The endpoint values are stored in the security cache, so a full recycle is required.
Smoke test
Go to https://server.domain.com/ssoconfig/SSOCfgInfoServlet
The loginurl and httpurl should match your endpoint URL. If they don’t, you’ll need to unassign and delete the endpoint, then try adding it again.
You want to work with an IT partner that has functional knowledge in addition to the technological ability to extract and re-map the data. This allows a true partnership that looks at the process from a high level and keeps an eye on the details at the same time.
You need to look for a partner that has experience extracting data from Lawson and mapping to the format needed to upload set up and transactional data to any system and taking extracted data from another system and formatting it into what Lawson needs and uploading the data. A partner who uses a repeatable process that allows for tweaking the process if needed through testing cycles and then having the final version ready when you are ready to go-live.
When considering a Merger or acquisition there are many considerations. Some of these are:
- Will there be a one-time conversion and at the end everyone will be using the same system?
- Or will there be an on-going interface between the systems for GL data only or other systems as well?
- Do you need a full training plan?
- How will the users be trained on the new system or processes?
- Make sure to start with a BRD – Business Requirement Document – so you have a road map of what is expected throughout the process. This helps both you and your partner know what is expected from both parties.
With the right partner, you can have a smooth and successful transition.
It’s official, you have finalized the project to move to Workday and are ready to begin your journey to the cloud. But wait! What will you do with all your Lawson legacy data? By now you probably know that you can’t take it all to Workday. Your data retention policies may not allow you to turn off your Lawson 10x (or 9.0.1) servers just yet. Looks like you have more work to do.
Keeping those servers around for another 7 years is not an option. You’re likely running several Windows 2012 servers, or worst yet, Windows 2008, AIX or AS400 iSeries. Not to mention the database servers, file servers, co-location, Disaster Recovery servers and more. It’s enough to keep the most seasoned IT manager awake at night. What if the hardware fails? What if the old OS has a vulnerability we can’t patch? What if our server admin who knows how to maintain Lawson leaves? All these what-ifs are just the tip of the data retention iceberg.
One option is to park the data in a data lake and bury it under a rug for the time being. But unless your users are data analysts with some sophisticated BI tools and skills, then the data lake might as well be a Crater lake.
What if there was a way to completely remove the Lawson footprint from your data center but still provide fast, secure, and intuitive access to all the data to your users in a way that didn’t require any servers or maintenance? The APIX Serverless Framework is just that solution. Based on the AWS serverless stack, APIX has opened up incredible possibilities for inquiry only applications never before possible without a substantial investment in infrastructure. Clients can now provision a web based, lightweight, data archive solution and migrate all their data within days rather than months and at a fraction of the cost of the other solutions with none of the risk. Find out how the APIX serverless framework can help you meet all your Lawson data archive needs and eliminate the legacy servers for good.
Once you convert Lawson to authenticate with AD FS, you may find that your users would really prefer to log in with their normal ID (as opposed to id@domain.com format). You can accomplish this by updating the login method on the AD FS home page.
To make these changes, begin by opening PowerShell as administrator on the AD FS server, then follow these steps.
Create a new theme based on the default theme:
new-adfswebtheme -name <custom theme name> -sourcename default
Download the new theme to a local path:
export-adfswebtheme -name <custom theme name> -DirectoryPath “<local path>”
Navigate to the onload.js file in the theme that you just downloaded. Add the following code to the onload.js file. The highlighted portion is what you will update with your company’s domain.
// Company customization
// accept sAMAccountName
// pass userprincipalName (id@company.com)
if (typeof Login != ‘undefined’){
Login.submitLoginRequest = function () {
var u = new InputUtil();
var e = new LoginErrors();
var userName = document.getElementById(Login.userNameInput);
var password = document.getElementById(Login.passwordInput);
if (userName.value && !userName.value.match(‘[@\\\\]’))
{
var userNameValue = ‘company.com\\’ + userName.value;
document.forms[‘loginForm’].UserName.value = userNameValue;
}
if (!userName.value) {
u.setError(userName, e.userNameFormatError);
return false;
}
if (!password.value)
{
u.setError(password, e.passwordEmpty);
return false;
}
document.forms[‘loginForm’].submit();
return false;
};
}
In PowerShell, upload the new onload.js file:
Set-AdfsWebTheme -TargetName TriCity -OnLoadScriptPath “c:\admin\TriCityTheme\script\onload.js”
Activate the custom theme:
Set-AdfsWebConfig -ActiveThemeName TriCity
Now, when users type in their regular username, it will be appended with “your domain\” when they click the login button. If users type in the domain themselves (“username@company.com”), the login page will accept that value and log in the user with the userPrincipalName they provided.
It’s official, you have finalized the project to move to Oracle HCM and are ready to begin your journey to the cloud. But wait! What will you do with all your Lawson legacy data? By now you probably know that you can’t take it all to Oracle HCM. In fact in most cases you’re limited to a small subset of your original data. Your data retention policies may not allow you to turn off your Lawson 10x (or 9.0.1) servers just yet. Looks like you have more work to do.
All AP payments hit the CBCHECK file. If your payment code (CB00.4) is set up to post in summary mode, (CB00.7 – under the Cash Payment button) the detailed APPAYMENT information that matches your APPAYMENT file will only be found in the CBCHECK file. There is a serial number on both the CBCHECK and the CBTRANS file. That is how you can link the two CB files for those transactions that are booked In summary. The total transaction amount will appear in the CBTRANS table with the serial number (with leading fill zeros) to be able to get to the CBCHECK detail for that total.