0Agenda:
1. Introduction to Deployments: Deployment is a way of processing your code with the JVM Server and serving the request from the client with the output of the processed content. We have memory terms for the JVM Server where the application code will use that to process the java codes written and it will hold the objects in the memory to serve the request. You can deploy an ear file or a war file or a sar file or a jar file to your Application Server. You need to specify a target for these deployments which are JVM servers.
2. Two Method of content Addition: Content is nothing but the ear or war or sar or jar files. These are archives which would be loaded into the server's which is hosting the website.
You can deploy the application in two methods:
i. Archived Form: It will all be packed into one file.
ii. Exploded Form: It's unsafe as you can lose files here. Because it would be in a file and folder format.
Content can be added from the,
a. Local system: Your using a desktop to access the dmgr console. So you can upload the archive from your desktop which will transfer to the server with network's help.
b. In the Server: You would have copied the content already to the servers. And you browse it from the server itself.
3. Types of Deployment:
Deployment can be a:
i. Fresh Installation
ii. Update
iii. Uninstall
iv. Rollback
v. Remove a file
vi. Export
vii. Stop
viii. Start
4. Deployment Home folders: If your uploading the content from a desktop, it will copy the content into the installable Apps folder. And once the installation of the application is completed. It will move it to the installedApps folder. The archive which your deploying will be copied to all the Nodes which you have targeted under the installedApps folder.
5. Modules on deployment: Map the modules while you're deploying the application.
i. War file: Map one JVM Server for one war file module.
ii. Ear file: Map another JVM Server for the other Ear file module.
6. Targets: Targeting the JVM Server / Clusters.
7. Deployment Desc: Web.xml inside the WEB-INF folder of the war file. There the developer would have mentioned different context root for different modules.
8. Application Security: Securing your application when it’s the client enters the website. Add SSO here so that it will check the windows login and authenticate you inside.
