Today, it is easy to find JEE developers who know the details of application development but it is hard to find someone who has good knowledge about deployment architecture that can ensure scalability, maintainability, security, and performance.

Java EE specification itself contains very little information on application deployment, leaving most of it up to individual JEE vendors. Each vendor has its own way of deploying and administering JEE applications which leads to confusion about generally good JEE Application Deployment Strategy.

A lot of questions come to mind when one starts thinking about JEE deployment like:

• Should one choose to deploy a single JEE application (EAR file) on each application server?
• Should one deploy multiple JEE applications (EAR files) on a single application server?
• Where to place application configuration data? – should it go in the database or should it go in the properties file?
• How to load configuration / properties file?
• How to configure batch components? – make them a part of EAR or keep them separate?
• What are the various re-deployment strategies?
• How are you going to perform a maintenance release?
• What are the appropriate steps one must take for hot fix release?

There are a lot of options and various possibilities. Choosing the right avenue for your environment requires extensive research and deep experience in JEE deployments. Our JEE practitioners have a vast skill set and experience in creating deployment strategies and successful implementations in various business domains. Our experts at Data Concepts can study your application to provide an optimal packaging and deployment strategy for your enterprise, based on the architecture, operating environment, business domain and scalability/performance requirements.