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.

1. In the Edit Tree, go to Deployments, then App Deployments.
2. Select New.
3. Enter a name for the application.
4. Select the servers and clusters to which you want to deploy the application.
5. Make the archive file or exploded directory known to the Administration Server.
   • If the application is on your file system and you need to upload it to the Administration Server, enable the Upload option. Then, beside Source, click Choose File to browse to the application's location on your system.
   • If the application is already in the file system of the Administration Server, disable the Upload option. Then, in the Source Path field, enter the file path to the application.
6. Optional: Add a deployment plan, choose another staging mode, or set application behavior at deployment.
7. Click Create.

You must start an application to make it available to WebLogic Server clients.

1. In the Monitoring Tree, go to Deployments, then Application Management.
2. Select the application that you want to start.
3. Click Start and choose either:
   • Servicing all requests: to make the application immediately available to all clients.
   • Servicing only administration request: to make the application available in Administration Mode only.

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.

1. In the Monitoring Tree, go to Deployments, then Application Management.
2. Select the application that you want to stop.
3. Click Stop and choose one of:
   • When work completes: to allow the application to finish its work and for all currently connected users to disconnect.
   • Force stop now: to stop the application immediately, regardless of the work that is being performed and the users that are connected.
   • Servicing non-administration requests: to stop the application once all its work has finished, and then put the application in Administration Mode so it remains accessible for administrative purposes.

After you deploy an application, you can configure additional settings to meet the needs of your environment.

1. 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.

   Note:

   You cannot create a deployment plan for applications that were auto-deployed.
   1. In the Monitoring Tree, go to Deployments, then Application Management, then myApp.
   2. Click Create Plan.
   3. 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.

   4. 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).
2. Go to Deployments, then Application Management, then myApplication, then Configuration. Explore the Configuration node and its children to see the available deployment configuration options.

   Note:

   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.
3. 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.
4. 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.

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.

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.

1. In the Monitoring Tree, go to Deployments, then Application Management and select the application that you want to update.
2. Click Update/Reploy and choose one of the options:
   • Update - Deployment Plan on Server: Updates the application using a new deployment plan located on the server. Use this option if all of your changes are dynamic.
   • Update - Deployment Plan on Local Machine: Updates the application using a new deployment plan located on the local machine and then uploads it to the Administration Server's upload directory. Use this option if all of your changes are dynamic.
   • Redeploy - Deployment Source and Plan on Server: Updates a deployment plan located on the server and redeploys the application. Use this option if your changes include non-dynamic changes that require the application to restart.
   • Redeploy - Deployment Source and Plan on Local Machine: Updates a deployment plan located on the local machine and redeploys the application. Use this option if your changes include non-dynamic changes that the application to restart.
3. Optional: If necessary for your selection, enter the file path to the new deployment plan.
4. Click Done to update or redeploy the application.

After you deploy an application, you may want to confirm that it was deployed successfully.

1. 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.
2. 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.

   Note:

   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.
3. 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.

1. In the Edit Tree, go to Deployments, then App Deployments.
2. 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.

1. In the Edit Tree, go to Deployments, then Libraries.
2. Click New.
3. Enter a name for the Java EE library.
4. 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.
5. Make the Java EE library (an archive file or exploded directory) that you want to install known to the Administration Server.
   • Enable Upload if the Java EE library is on your file system and you need to upload it to the Administration Server. Then, click Choose File to browse to the library's location on your system.
   • If the Java EE library is already in the file system of the Administration Server, then disable the Upload option and enter the file path to the Java EE library.

   If you specify an exploded directory, WebLogic Server installs all components it finds in and below the specified directory.

   Note:

   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.

6. Optional: Select a different staging mode.
7. Click Create.

If using JASPIC, you can specify which Authentication Configuration provider applies to a specific Web application.

1. If you haven't done so already, configure JASPIC in the domain.
   1. 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.
   2. Configure an Authentication Configuration provider.
      • To configure a WebLogic Server Authentication Configuration Provider, see Creating a WLS Authentication Configuration Provider in Administering Security for Oracle WebLogic Server.
      • To configure a Custom Authentication Configuration Provider, see Creating a Custom Authentication Configuration Provider in Administering Security for Oracle WebLogic Server.
2. In the Monitoring Tree, go to Deployments, then Application Management, then myWebApp.
3. 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.

4. Expand the Configuration node and go to the JASPIC Container node.
   The JASPIC Container node is only available for web applications.
5. Enter the name of the Authentication Configuration provider that you configured and want to apply to this web application.
6. Click Save.
7. Redeploy the web application or restart the server.

Use credential mapping to control access between WebLogic resources and remote systems. WebLogic Server allows you to restrict access on a per-application basis.

1. Determine which MBean configuration data is required to form a connection between the WebLogic resource and its security data.
   1. In the Security Data Tree, go to Realms, then myRealm, then Credential Mappers.
   2. Continue until you reach the WebLogic resource that you want to prepare for credential mappings. See Identify Resources for Credential Mapping for example node paths.
   3. Click New and make a note of all of the required attributes (fields marked by an asterisk) for which you will need to retrieve configuration data.
   4. Click Cancel.
2. In the Monitoring Tree, go to Deployments, then Application Runtime Data, then myApplication, then Component Runtimes, then myApplication.
3. In the Component Runtimes table, locate the row for the application but do not click it. Instead, right-click on the application's cell for the EIS Resource ID column and select Copy Cell to Clipboard.
4. Paste the values to a text file for use in a later step.
5. Locate any additional data (as determined in step 1) that you require to identify the resource for its credential mapping. The necessary data will differ depending on the resource type.

   For example:

   • EJBs require the EJB name. Under the Deployments node, go to Application Runtime Data, then myApplication, then Component Runtimes, then myApplication, then EJB Runtimes.
   • Resource Adapters require the Outbound Connection Pool Instance name. Under the Deployments node, go to Application Management, then myApplication, then Configuration, then Outbound Connection Pool Groups, myOutboundConnectionPoolGroup, then Outbound Connection Pool Instances.
6. Form the connection between the resource and its security data, as described in Identify Resources for Credential Mapping. To fill in the fields, use the Module, Name, and any of the other requested values that you retrieved in the previous steps.

   This process will also create the first credential mapping for the application.

7. If you want to create more credential mappings, see Add a Credential Mapping.