Installing an enterprise application refers to making its physical
      file or directory known to WebLogic Server. An enterprise application
      can be installed as an archived EAR file or as an exploded directory.
      After you have installed the enterprise application, you can start it so
      that users can begin using it.
      To install an enterprise
      application:
     
    - If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
 
      - 
        In the left
        pane of the Console, select Deployments.
      
 
      - 
        On the Configuration page, click
        Install.
      
 
      - 
        Using the
        Install Application Assistant, locate the 
EAR file or exploded
        directory that corresponds to the enterprise application you want to
        install. If you specify an exploded directory, WebLogic Server
        installs all components it finds in and below the specified directory.
        Select the circle to the left of the application.
       
      - 
        Click
        Next.
      
 
      - 
        Select Install this deployment as an
        application.
         
          
If you have created additional Managed Servers or clusters, you
          can also select Install this deployment as an
          application, but target the modules individually. Select
          this option if, for example, you want to target all Web applications
          in the enterprise application to one Managed Server and all EJBs to
          a different Managed Server. If you have not created additional
          Managed Servers or clusters, you will not see this option.
        
       
      - 
        In Scope, select whether you want to install the
        enterprise application globally, to a resource group template, or to a
        resource group at the domain or partition level.
      
 
      - 
        Click Next.
         
          
If you previously selected the option to target the entire
          enterprise application to the same server or cluster, the
          Select Deployment Targets window appears.
          Note: If you have not created Managed Servers or
          clusters, other than the current Administration Server, you will not
          see this assistant page.
        
       
      - 
        Follow these steps:
        
          - 
            Select the Managed Servers or clusters to which you want to
            deploy the entire enterprise application.
          
 
          - 
            Click Next.
          
 
        
         
          If you previously selected the option to target individual
          modules of the enterprise application to their own server or
          cluster, then the Select Modules to Target
          window appears with a table that contains a list of all the modules,
          the type of module (such as EJB or Web application), and the Managed
          Server, cluster, or JMS server (for application-scoped JMS modules)
          to which it is currently targeted, if any. Follow these steps:
        
        
          - 
            Select the modules which you want to target to a particular
            Managed Server, cluster or JMS server.
          
 
          - 
            Click Next.
          
 
          - 
            Select the Managed Server, cluster, virtual host, or JMS
            server to which you want to target the modules.
          
 
          - 
            Click Next. The install assistant
            takes you back to the table of modules, but now the Selected
            Targets column for the modules you just targeted shows the current
            target.
          
 
          - 
            Repeat the preceding steps until you have targeted all the
            modules as you wish.
          
 
          - 
            Click Next with no modules
            selected to proceed to the next assistant page.
          
 
        
       
      - 
        Optionally update settings about the deployment. These settings
        include:
        
          - The deployed name of the enterprise application. The default
          deployment name is the name of the enterprise application EAR file
          or exploded directory.
 
          - For any Web application or EJB modules, the security model
          that is applied. See Manage security for Web
  applications and EJBs for
          detailed information about the models.
 
          - How the source files (EAR or exploded directory contents)
          are made available to all targeted Managed Servers and clusters. See
          Controlling
          Deployment File Copying with Staging Modes for detailed
          information about the deployment staging modes.
 
          - How the deployment plan source files are made available to
          all targeted Managed Servers and clusters.
 
        
         
          Typically, the default values are adequate.
        
       
      - 
        Click Next.
      
 
      - 
        Review the configuration settings you have chosen and specify
        whether you want to immediately update the application's configuration
        after you install it.
         
          
Note: If you install an application that follows the
          below directory structure and there is no deployment plan in the
          /plan directory, WebLogic server automatically
          creates a deployment plan for you.
          app-root
          /app
          /plan
        
       
      - 
        Click Finish to complete the installation.
      
 
      - 
        If you choose to immediately go to the deployment's configuration
        screen, select the pages to set additional configuration settings for
        the enterprise application. If you choose to change this information
        later, the Console returns you to the Deployments table, which
        should now include your newly installed enterprise application.
      
 
    - To activate these changes, in the Change Center of the Administration Console, click Activate Changes. 
Not all changes take effect immediately—some require a restart (see Use the Change Center).