You can use WebLogic Remote Console to manage the deployment process of applications to WebLogic Server.
For general information on the application deployment process, see Understanding WebLogic Server Deployment in Deploying Applications to Oracle WebLogic Server.
A deployment unit refers to a Java EE application (an enterprise application or Web application) or a standalone Java EE module (such as an EJB or resource adapter) that has been organized according to the Java EE specification and can be deployed to WebLogic Server.
The following deployment units are supported:
Enterprise Application
Web Application
Enterprise JavaBean
Web Service
Java EE Library
Optional Package
JDBC, JMS, and WLDF Modules
Client Application Archive
For more information on each deployment unit, see Supported Deployment Units in Deploying Applications to Oracle WebLogic Server
An application can be installed as an archived EAR file or as an exploded directory. Installing an application makes its physical file or directory known to WebLogic Server.
This procedure applies to all of the deployment units listed in Supported Deployment Units, with the exception of Java EE libraries. For Java EE libraries, see Install a Java EE Library instead.
In the Edit Tree, go to Deployments, then App Deployments.
Select New.
Enter a name for the application.
Select the servers and clusters to which you want to deploy the application.
Make the archive file or exploded directory known to the Administration Server.
Add a deployment plan, choose another staging mode, or set application behavior at deployment.
Click Create.
You can view the status of running deployment tasks on the Monitoring Tree: Deployments: Deployment Tasks page.
Your new application appears under the App Deployment node. You can make additional changes to the application on this page.
You must start an application before it can process client requests.
You must start an application to make it available to WebLogic Server clients.
When you start an application, you can make it immediately available to clients, or you can start it in Administration Mode first to ensure that it is working as expected. Starting in Administration Mode allows you to perform final sanity checking of the distributed application directly in the production environment without disrupting clients.
In the Monitoring Tree, go to Deployments, then Application Management.
Select the application that you want to start.
Click Start and choose either:
When you stop an application, you prevent clients from accessing it. You can choose whether no clients can use it, or transition it to Administration Mode so that only administrative tasks can be performed.
Stopping an application does not remove its source files from the server; you can redeploy a stopped application to make it available to WebLogic Server clients again.
In the Monitoring Tree, go to Deployments, then Application Management.
Select the application that you want to stop.
Click Stop and choose one of:
After you deploy an application, you can configure additional settings to meet the needs of your environment.
If you haven’t already, create a deployment plan for the application. You can view the default configuration settings without creating a plan but they are read-only until you create a deployment plan. For more information, see Deployment Plans.
You cannot create a deployment plan for applications that were auto-deployed.
In the Monitoring Tree, go to Deployments, then Application Management, then myApp.
Click Create Plan.
In the Plan Path field, enter a file path for the new deployment plan. Deployment plans must be in XML format and should be called plan.xml.
If possible, you should create the new deployment plan for a single application within a plan/ subdirectory of the application’s root directory.
Click Done. WebLogic Server will create a basic deployment plan.
You can see the deployment plan for an application under Deployments: Application Management: myApplication: Deployment Plan (Advanced).
Go to Deployments, then Application Management, then myApplication, then Configuration. Explore the Configuration node and its children to see the available deployment configuration options.
The contents of the Configuration node and its children differ based on application type. For example, web applications include settings for container descriptors while resource adapters include settings for outbound connection pools.
Click Save as you make changes. Any changes that you make to the Configuration node and its children are automatically reflected in the deployment plan of the application.
Update and possibly redeploy your application to apply your changes. See Update or Redeploy an Application for instructions.
Use a deployment plan to specify deployment property values for an application.
A deployment plan is an optional document that works with or overrides your application’s deployment descriptors to configure an application for deployment to a specific WebLogic Server environment. Deployment plans are written in XML.
See Understanding WebLogic Server Deployment Plans in Deploying Applications to Oracle WebLogic Server.
You cannot create a deployment plan for applications that were auto-deployed.
For deployment plan descriptions and examples, see Understanding Deployment Plan Contents in Deploying Applications to Oracle WebLogic Server.
Generally, if you need to modify the deployment properties of an application, you should use the Configuration node (as described in Specify Deployment Properties), instead of manually editing the deployment plan.
If your changes in the deployment plan include non-dynamic changes, you must redeploy the application to propagate the changes from the deployment plan to the application.
You can manually update a deployment plan with new deployment instructions for an application.
For more information, see Manually Customizing the Deployment Plan in Deploying Applications to Oracle WebLogic Server.
In the Monitoring Tree, go to Deployments, then Application Management, then myApplication, then Deployment Plan (Advanced).
You can edit the deployment plan as a whole or the individual variable assignments within a deployment plan:
Update and possibly redeploy your application to apply your changes. See Update or Redeploy an Application for instructions.
After you make changes to a deployed application or its deployment plan, you need to update the application with the new instructions and possibly redeploy the application to make the changes available to WebLogic Server clients.
If your changes are dynamic, then you only need to update the deployment plan. However, if your changes include non-dynamic changes, you must redeploy the application to propagate the changes from the deployment plan to the application.
If you try to update a deployment plan but your changes require a redeployment, WebLogic Remote Console will prompt you to redeploy the application instead.
If the application is deployed in a production environment, review Overview of Redeployment Strategies in Deploying Applications to Oracle WebLogic Server for guidance on limiting downtime for the application.
In the Monitoring Tree, go to Deployments, then Application Management and select the application that you want to update.
Click Update/Reploy and choose one of the options:
If necessary for your selection, enter the file path to the new deployment plan.
Click Done to update or redeploy the application.
You can track the status of the application deployment. While still in the Monitoring Tree, go to Deployments, then Deployment Tasks.
After you deploy an application, you may want to confirm that it was deployed successfully.
In the Monitoring Tree, go to Environment, then Servers, then myServer, then Deployments, then Application Runtimes, then myApp, then Component Runtimes, then myServer/myApp, then Servlets.
Construct a URL using the target server address plus the ContextPath and Name values from the Servlets table. For example, for an application deployed on the Administration Server, a test URL might look like: http://adminserver:7001/myapp/welcome.
Remember to consider any changes you made to network channels that may affect the application deployment. For example, the application may be on a different port.
Enter the URL into your browser. If the page loads correctly, then your application was deployed successfully.
An installed application or module remains available in the domain to stop, restart, or update until you explicitly remove it. After you delete an application or module from a domain, you must redeploy it to make it available to a WebLogic Server client again.
To temporarily make a deployed application unavailable to WebLogic Server clients, consider stopping it instead of deleting it. See Stop an Application.
In the Edit Tree, go to Deployments, then App Deployments.
Select the application that you want to remove and click Delete.
A Java EE library can be a standalone EJB or Web application module, multiple EJB or Web application modules packaged in an enterprise application (EAR), or a single plain JAR file that is registered with the Java EE application container upon deployment. After the library has been installed and started, other deployed modules can reference the library.
Installing a Java EE library means making its physical file or directory known to WebLogic Server. A Java EE library can be installed as an archived EAR file or as an exploded directory. After you have installed the Java EE library, other deployed modules can start using it.
In the Edit Tree, go to Deployments, then Libraries.
Click New.
Enter a name for the Java EE library.
Select the servers and clusters to which you want to deploy the Java EE library. Make sure to target all of the servers and clusters to which modules or applications that will reference the Java EE library are deployed.
Make the Java EE library (an archive file or exploded directory) that you want to install known to the Administration Server.
You can install only the following types of archive files (or their corresponding exploded directories) as Java EE libraries: EJB JARs, Web application WARs, EAR files that contain EJB JARs or WARs, or plain JAR files that contain compiled classes.
Select a different staging mode.
Click Create.
Your new library appears under the Libraries node. You can make additional changes to the Java library on this page.
When you update a Java EE library, WebLogic Server redeploys the archive file or exploded directory. Update a library if you have made changes to it and you want to make the changes available to the modules and applications deployed to WebLogic Server that are using the library.
In the Monitoring Tree, go to Deployments, then Library Management.
Select the Java EE library that you want to update.
Decide how you want to update the library:
Choose Redeploy if the changes to the library are already available on the Administration Server and you only want to make those changes available to the modules and applications that are using the library.
Choose Upload and Redeploy if you want to upload a new archive file or exploded directory.
In the Source field, enter the path to the new archive file or exploded directory. Make sure the library’s latest archive is under the Administration Server’s upload directory.
Click Done.
If using JASPIC, you can specify which Authentication Configuration provider applies to a specific Web application.
The Java Authentication Service Provider Interface for Containers (JASPIC) specification defines a service provider interface (SPI). The JASPIC SPI is used by authentication providers that implement message authentication mechanisms that can be integrated in server Web application message processing.
You can review the JASPIC specification at JSR 196: Java Authentication Service Provider Interface for Containers.
If you haven’t done so already, configure JASPIC in the domain.
Ensure JASPIC is enabled in the domain. In the Edit Tree, go to Environment, then Domain. On the Security tab, click Show Advanced Fields and confirm that JASPIC Enabled is turned on.
Configure an Authentication Configuration provider.
In the Monitoring Tree, go to Deployments, then Application Management, then myWebApp.
If the application does not have a deployment plan, click Create Plan.
WebLogic Server will create a basic deployment plan for the application which you can edit using the newly created Configuration and Deployment Plan (Advanced) child nodes.
Whenever possible, use the Configuration node to edit deployment properties rather than editing the deployment plan directly. See Specify Deployment Properties.
Expand the Configuration node and go to the JASPIC Container node.
The JASPIC Container node is only available for web applications.
Enter the name of the Authentication Configuration provider that you configured and want to apply to this web application.
Click Save.
Redeploy the web application or restart the server.