JEE Application Development
The customer wanted to add speed and precision to developing, testing, and deploying Java Enterprise/Websphere application changes all while maintaining quality and system integrity. A project was created to speed the majority of the ancillary processes, which are routine but time consuming, freeing personnel to concentrate on areas that required critical thinking and expertise.
The Java Development Team members (Devs) perform their code development and check in their code into Harvest. The Devs then deploy a project that use the Odyssey Harvest Task Agent to get the latest code view, the Odyssey Delete Task Agent to delete the build area, the Odyssey File Management Task Agent to copy from the view to the build area, the Odyssey Java Compile Task Agent to compile the Java source code, the Odyssey WAR Task Agent to create the deployable file, and the Odyssey Websphere Task Agent to deploy the WAR file to a Websphere Dev QA server.
Dev QA tests the changes in the Dev environment. If it passes their tests, Dev QA deploys a project to begin the next phase. This project is much like the previous one, but has differences in approvals and environments. Because this is leaving Development and proceeding to UAT, the project requires one or more approvals, and Odyssey notifies the Approvers that Dev QA has requested deployment to UAT. The Approvers then review the request and approve (or reject) the deployment. Once again, the project re-builds, migrates and redeploys the WAR to the appropriate Websphere UAT server.
UA tests the changes in the UAT environment. If it passes their tests, UAT deploys a project to begin the next phase. This project is much like the previous two, but has differences in approvals and environments Because this is leaving UAT and proceeding to Production, the project requires one or more approvals, and Odyssey notifies the Approvers that UAT has requested deployment to Production. The Approvers then review the request and approve (or reject) the deployment. Once approved, the project re-builds, migrates and re-deploys WAR to the appropriate Production Websphere server(s). Because this involves more servers and desktops than before, tracking is performed individually per installation.