This method of deployment is convenient if you do not know the exact names of deployment units, target servers or deployed applications and it’s generally used to roll out your applications in production. From the console, select the “Deployments” option in the left menu:
Choose Install. In the next screen, you can either select the application by browsing the remote file system (Option 1) -or- upload an application from your local file system (Option 2):
Oracle WebLogic Server supports deployments that are packaged either as archive files or as exploded archive directories.
In the next screen, you can decide to install your artifact as an application or a shared library. The most common usage is the default one, that is, “Install this deployment as an application”:
Next, you should choose a target in which your application will run. In this case, the targets are two Managed Server (Remember that it’s better not to target applications to the Admin Server; the Admin Server should be used just for administrative tasks).
Finally, the next screen will allow some optional settings. If you want to get through them, see the next section named “Configuring Optional settings”. Otherwise click on Finish:
If everything was correct, the console will inform you that the deployment is now correctly installed. If you are running WLS in production mode, changes must be activated from the Change Center panel. Besides this, you need also selecting the Start drop-down list to start “Servicing all requests”. This will enable the application to serve requests in production.
From the “Configuring optional settings” window, it is possible to set some advanced settings concerning security and deployment:
The security settings are outlined in the following panel:
And here’s some explanation to it:
- DD only – (default) this option only uses the roles and policies defined in the Java EE application deployment descriptors.
- Custom roles – uses the roles and policies defined in the deployment descriptors but, rather than mapping roles to Principals in the WebLogic specific deployment descriptors, map them using the WebLogic Console.
- Custom roles and policies – uses only the WebLogic Console to define roles and policies, ignoring any roles and policies defined in the deployment descriptors.
- Advanced – uses the roles and policies defined in the deployment descriptors to seed the WebLogic security roles and policies, and uses the WebLogic Console to modify roles and policies from that point onward.
For more information have a look at the Chapter 11 which is about “Oracle WLS Security”.