Skip navigation.
Downloads | Product Documentation | Support

Fast Track Deployment and Administrator Guide for BEA WebLogic Server 9.1 This page provides basic instructions for quickly deploying J2EE applications and modules, and JSP and HTML files. It also provides pointers to tools for system administrators. The deployment procedures on this page are recommended for use in development environments only; the procedures are not recommended for use in production environments. For additional information on developing and deploying applications on WebLogic Server, see Developing Applications with WebLogic Server and Deploying Applications to WebLogic Server. Complete the WebLogic Server Installation before using these Fast Track procedures.

### J2EE Deployment To deploy a J2EE application or module: Make sure that the J2EE application or module does not require additional resources such as named JDBC data sources or JMS queues. If the application requires external resources, you must configure them in the target WebLogic Server domain before deploying the application. Copy the archive file or exploded archive directory for the J2EE application or module into the `/autodeploy` directory of the examples server domain directory, `WL_HOME/samples/domains/wl_server/autodeploy`. Start the Examples WebLogic Server instance. In Windows, you can use the Start Menu shortcut: Start Examples Server. Access the application using either a Java client or the configured URI for the application. What's Going On? When running in development mode, WebLogic Server automatically deploys applications copied into the the `/autodeploy` subdirectory of the domain directory. Auto-deployment is a simple and quick method of deploying an application for testing or evaluation. See Auto-Deployment. Additional Resources Deploying Applications to WebLogic Server Developing Applications with WebLogic Server | ### JSP/HTML Deployment To deploy a simple JSP or HTML file: Make sure your JSP file does not reference a tag library or other external resources -- such resources require additional deployment steps that are beyond the scope of these Fast Track procedures. HTML files do not have this restriction. Copy your JSP or HTML file into the `WL_HOME/samples/server/examples/ build/mainWebApp` directory. Start the Examples WebLogic Server instance. In Windows, you can use the Start Menu shortcut: Start Examples Server. In a Web browser, request the JSP or HTML file using the following URL: `http://localhost:port/myFile` where: `localhost` is the host name of the machine running WebLogic Server `port` is the port number where WebLogic Server is listening for requests (7001 by default). `myF` `ile` is the full name, including the `.jsp` or `.html` extension, of the JSP or HTML file you copied in step 2. What's Going On? The JSP or HTML file has been automatically deployed from a directory preconfigured to target the Examples Server. `mainWebApp` is deployed by default and you can place your own JSP and HTML files into the `mainWebApp` exploded directory in order to quickly view or test them. Additional Resources Deploying Applications to WebLogic Server Developing Web Applications with WebLogic Server | ### System Administrator Tools System Administrators can use the following tools to get started: Administration Console The Administration Console is a browser-based Web application that allows you to configure and monitor your WebLogic Server domain, server instances, and running applications and their associated resources. You can also use the Administration Console to create new server instances and clusters and tune application descriptors. More information. After you log into the Console using the credentials you provided during installation, click the Help button or "How do I ...?" links for additional information. Configuration Wizard Use the WebLogic Server Configuration Wizard to create new domains, and to create templates for automating domain configuration. More information.