In this video, Emmanuel Henri introduces the sample project you are going to use to test for your deployments.
- [Instructor] Before we get to prep our project and get started with a local deployment, let's explore the building blocks of a deployment and what is needed to give you the best chance of success in your deployment. When you deploy your application, typically you'll package them into a file that is very similar to a zip file. For a Jave EE application you'll package it in a file called a Java archive, or JAR, J-A-R. If your project is a web archive, you'll package it into a WAR file, W-A-R, and finally, for an enterprise archive, a E-A-R file. You package your modules into one of these formats and the extension name provides a clue of what type of project is archived inside the file, as simple as it gets. Then you can use this file to deploy to the local server, or a cloud provider. In some cases you may need to include what we call a deployment descriptor, which is an XML file that includes deployment settings, or the application module, or a component. You use this file to describe deployment or runtime settings and specs that can be used when deployment is executed, or the application runs on the server. This packaging approach allows Java EE applications to be contained into a single file with instructions as to how to deploy, or run them. And is easily sharable across developers or when it comes time to deploy.
- Deployment options
- Setting up your deployment
- Deploying locally with glassfish
- Deploying to Azure and AWS
- Deploying to Docker containers