There are alternatives to expensive, closed source Java EE application servers for hosting your applications. Lower cost open source Java EE application servers, many with support for the dynamic languages, are mature and capable to host mission critical applications and services. Realizing the benefits of these containers requires migrating your applications from your current application server (e.g. Oracle/BEA WebLogic, WebSphere, or others), and it's important to weigh costs and effort against potential ROI before you begin. In order to help businesses quantify those factors, Hub City Media (HCM) has created a Java EE Migration Assessment service that can quickly determine the effort required to migrate your applications to this innovative and cost-effective platform.

How does the assessment work?

HCM's Java EE Migration Assessment begins with a review of how your applications are built, deployed and managed in your current application environment. The assessment includes direct inspection of application code; review of documentation, deployment methods, and operational procedures plus interviews with subject matter experts and stakeholders. The goal is to provide a realistic Statement of Work (SOW) for migrating to an alternative application server.

What's included?

Each assessment covers estimating the migration of up to three customer applications. Each assessment involves three main phases:

1. Initiate - The project's goals, tasks, milestones, and deliverables are reviewed. Roles and responsibilities are assigned. The general timeline is established. A communications plan is set. The HCM Project Manager creates a Review Checklist of the documents, systems, source code, processes to be reviewed, and interviews to be conducted during the Review phase. The HCM Project Manager creates a project plan, which will be utilized by both teams to schedule events and resources.
2. Review - Review of the customer's applications based on the following sources of information:
   • Any documentation that exists for the application, the systems environment, application specifications, designs, or operations guides.
   • Application source code, configuration files and build system scripts.
   • Interviews with key personal responsible for the development, deployment, maintenance and business function of the application.
3. Report - During this phase, HCM will create the project SOW based on Review findings. The SOW will contain a service description, technical scope, and scope limitations for the application migration project. It will also include a summary of HCM's methodology, project terms, payment schedules, expense estimates, and other terms and conditions.

Typical steps in a Java EE migration project

1. Migrating the application source code and dependent resource configuration so the application will deploy and function on another application server
2. Creating a suitable system architecture for development, testing and production
3. Remediating the build environment, if required, to provide a more reproducible build process
4. Updating procedures for deploying applications into the new server infrastructure
5. Updating management procedures for monitoring and managing the applications in production

Why consider open source application servers at all?

1. Reduced cost.  Most of these alternative app servers, e.g., GlassFish or JBoss, have much lower TCO than closed source app servers
2. Leverage the power of open source: increased security, faster bug-fixes, cutting-edge functionality.
3. Commercial and community support.  Customers using commercially supported open source can take advantage of broader community support.  You get the best of both worlds.
4. Scratch your own itch. You have access to the source code.  If you need to enhance, alter, or correct features in the product you can do that yourself.  Even if it's just to understand how it works.