1 / 25

Lawson Upgrades

Lawson Upgrades. UNIX/Windows 7.2 to 8.0 ROMLUG June 5 th , 2002. Upgrade Overview. Purpose is to move application data between major releases Main considerations are Preserve data integrity Preserve existing functionality Only implement required new functionality. Terminology. Patch

giles
Download Presentation

Lawson Upgrades

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lawson Upgrades UNIX/Windows 7.2 to 8.0 ROMLUG June 5th, 2002

  2. Upgrade Overview • Purpose is to move application data between major releases • Main considerations are • Preserve data integrity • Preserve existing functionality • Only implement required new functionality

  3. Terminology • Patch • Update to fix a specific bug • Cyclical/Service Pack • Periodic update change that contains all patches • Upgrade • Major update change which requires special programs • Migration • Platform change (May also require cyclical or upgrade) • Conversion • Non-Lawson data to Lawson • Upgrade without using upgrade programs

  4. Upgrade Project Methodology

  5. Training • Application differences classes • Security • Environment • Install • Upgrade

  6. Technical Overview Version Requirements Environments Storage Requirements Customizations Security Purging

  7. Version Requirements • Environment 7.3.3+, Application 7.2.4+ • Also check for required upgrades of: • Operating System • Database • BSI Tax Factory • COBOL – new licensing for 8.0 environment • C Compiler • CCS • SEA • Perl – new to 8.0 applications

  8. Environment – 7.3 vs. 8.0 • It is highly recommended that you upgrade within one environment • If not possible, source and target environments should be the same version • If you are using multiple environments, additional setup will be required

  9. Storage Requirements • Upgrade requires 3 product lines • Production – 7.2 • Not touched in the upgrade process • Source – copy of production • Required because you must upgrade from a static product line • Can be a currently installed test product line • Target – 8.0 • Will become your future production product line • Some temporary space for dump files • Report space

  10. Purging • Purging • Purging permanently removes records • Tape file created would need conversion to load • Purging always improves an upgrade • Reduces database size • Removes older, usually converted, data • Reduces potential upgrade issues • Reduces temporary space required

  11. Customizations • Database • Modified Lawson files • Custom file • Added index • Program • Modified lawson programs • Custom programs

  12. Security • Two options • Security can be copied • Holes will be created because of new screens and fields • Needs to be thoroughly tested and adjusted • More risky • Re-implement • Allows you to more efficiently use the new functionality • Allows you to revisit your company’s security policy and implementation

  13. Product Line Setup • The following will need to be set up for new product line/database • Job definitions, including multi-step jobs • Recurring jobs • Custom menus • UNIX/Windows scripts • Reporting tools

  14. Data Upgrade Overview Data Flow Upgrade Steps Between Upgrades

  15. Upgrade Flow

  16. Upgrade Steps - Source • Setup • Enter information required by new version • Prejob • Checks for setup completion and data errors • Unload • Unloads files that require data changes to CSV • Reorg (if in same env) • Upgrades files that do not require data changes

  17. Upgrade Steps - Target • Reorg (if between envs) • Upgrades files that do not require data changes • Load • Loads CSV files that were unloaded from • Postjob • Updates flags and other fields • Some user set up required to finalize upgrade • Data verification • Compare reports from both versions

  18. Contingency Plan • Methodology includes contingency plan • Production product line is never affected • Determine “point of no return” for your system • System Parallel is an option

  19. Upgrade Tips • “dbcopy” command - used for reorgs • Can be run from command line with scripts • Multi-thread jobs • Use Lawson’s job queues to efficiently multi-thread processes • Turn off database archiving • Will speed up upgrade and prevent logs from filling up • TEST, TEST, TEST • Majority of project plan is user testing

  20. Upgrade Information Packet • Planning Your Upgrade • Checklist, Methodology, Flowchart, Disk Space, Mods • Upgrade Checklists • All steps needed to complete upgrade • Upgrade References • Menu system, setup info, prejob info, postjob info, verification reports, upgrade program info • (Database File Changes) - downloaded • All database changes

  21. Support Lawson Global Support Center Consulting Services support.lawson.com

  22. Lawson Global Support Center • Upgrade support group • Trained in upgrade procedures • Call them first • Application support groups • Do not know upgrade procedures • Call if you are in final system testing and you believe it is an application issue • Environment support group • Call with installation and operation issues

  23. support.lawson.com • Release notes • Conversion and Interface file layouts • Upgrade planning information • Frequently asked questions • Issue resolution • Updates • Partners

  24. Upgrade While Active • Requires 8.0 Environment for PROD • Only to 8.0.3 Application • Still upgrade from TEST • Triggering turned on in PROD • Copy triggered data to TEST • Upgrade only triggered data • Repeat until run time small enough

  25. Questions?

More Related