Migration made simpler

A key advantage of the Java platform has always been code portability. "Write once. Run Anywhere." That was the core promise of the Java Enterprise Edition specifications.

Over the years, however, vendors have continued to innovate on the Java EE platform, creating extensions that, while useful, were often proprietary and available only in the containers provided by that vendor. In some cases the vendors created proprietary security, persistence, or availability APIs, and customers using these extensions would find themselves locked into vendor-specific containers.

To avoid this trap, customers can adhere strictly to the APIs and practices defined in the specification and/or use vendor-neutral deployment methods and tools. But there are times when looming deadlines or vendor documentation can lead developers off this straight and narrow path. Organizations must then weigh the costs of ongoing vendor license and maintenance fees against the one-time costs of migrating to a new platform. Hub City Media can help make the latter solution more practical.

A Flexible approach to Java EE Migration

To reduce the time, risk and cost of migration, HCM has developed a specialized methodology for porting Java EE applications. Using this methodology, HCM determines the extent to which proprietary extensions were used, tailors a migration plan accordingly, and expertly carries out the migration.

HCM's proven methodology is modular and adaptable. It comprises six main activities that can be deployed all together or in the combination that best meets customer needs:

• Discovery: HCM analysts review the function and current operational characteristics of your application to create a migration strategy and a testing strategy if necessary. We'll also develop a deployment and system design to serve as a blueprint for the eventual production environment into which the application will be deployed.
• Static code analysis: We scan your base code using automated tools to detect proprietary APIs, deployment descriptors and bad code idioms. These issues are documented and then resolved.
• Build environment remediation: If required, we'll create a new build environment to deploy the application across containers. The application port continues using this build system.
• Application testing: At the end of the port, we test the application using the defined testing strategy. Any migration-related deviation is detected and corrected.
• Deployment migration: We then migrate the tested application into the existing or parallel production environment.
• System transition: We work with you to review all documentation and prepare guides to serve as your "owner's manuals" for the new environment.

Contact us to learn more about HCM's Java EE Application Migration Methodology.