Porting Enterprise Apps from UNIX to Linux

By Martyn Honeyford
2005-04-17

Testing

Porting a new product to a new platform requires that the product be tested extensively. Some of the areas that can require special attention are interprocess communication, packaging, intersystem communication (client-server between AIX and Linux or Solaris and Linux), persistent storage (because of endian-ness), data-exchange formats, and so on.

It is possible that external documentation might change, so a thorough documentation review should be carried out.

The test-case porting to Linux needs to be staged properly along with the development work. A list of intermediate deliverables to be tested should be prepared before moving on to full product testing. This will help you find problems at earlier stages of product development. (For more on highly effective general testing methods, see reference to XP in the Resources section.)

Tutorial Pages:
» A Practical Checklist, Tips, and Insight Drawn from Experience
» Get the Build System Working
» Decide on a Viable Operating Environment
» Architecture-Specific Changes
» Choose an IPC Mechanism
» Select the Threading Model
» File System, Usage Parameters, Stacks
» Memory Maps and Using Shared Memory Segments
» Signaling
» Configure Kernel Karameters
» Parser Tools like lex/yacc
» Globalization Issues
» Security Concerns
» Locating Installed Packages and Variable Data
» Testing
» There's a Port in Every Storm
» Resources

First published by IBM DeveloperWorks

Related Tutorials:
» How to Install PHP 5 on Linux
» How to Install Apache 2 on Linux
» How to Install MySQL 5.0 on Linux
» SMB Caching
» Mound --Bind
» Tar Wild Card Interpretation