# Deploying the standalone portal WAR on WAS 7

After downloading and extracting the necessary files, you can deploy the Discovery Framework as an enterprise application in WebSphere Application Server, and then install portlets, themes, and other plugins as modules in that enterprise application.

The following steps document the installation procedure by using the IBM Integrated Solutions Console for a WebSphere Application Server installed and maintained without the use of the Deployment Manager, and consisting of one cell with one node and one server. The instructions may need to be adjusted for clustered environments, environments maintained with the Deployment Manager, or for environments where administration is performed by using tools like wsadmin, rather than the Integrated Solutions Console.

The following steps assume that no other applications are deployed in the same application server. If there are other applications, ensure that no applications are bound to context root / (or that any such applications are stopped during the Discovery Framework deployment). After following these steps, you will be able to adjust the context root for the Discovery Framework application, to ensure it does not conflict with other applications.

To deploy the Discovery Framework standalone portal WAR on WAS 7:

1. Start the WAS server.
2. Log in to the WAS Integrated Solutions Console, using the appropriate administrator credentials.
3. In the WAS Integrated Solutions Console, select Applications > New Application > New Enterprise Application.
4. Click to browse to and select the Endeca Discovery Framework WAR you downloaded earlier (endeca-portal-<version>.war), and then click Next.
5. Select Choose to generate default bindings and mappings and check the following options:
   - Generate default bindings
   - Override existing bindings
6. Still in the Choose to generate default bindings and mappings section, check Use default virtual host name for Web and SIP modules, and enter `default_host` in the text field. Click Next.
7. By default, the application name is endeca-portal-<version>_war. Set the application name to a more relevant name (for example, DiscoveryFramework). All other installation options can remain unchanged. Click Next.
   Note: Do not use spaces in the application name. For example, use DiscoveryFramework instead of Discovery Framework.
8. In Map modules to servers, accept the default settings and click Next.
9. In Map context roots for Web modules, set the context root to the desired path for your Discovery Framework installation, and then click Next.
   Note: Make a note of your context root, as you will need to reference it several times during the deployment process.
10. In Install New Application, confirm that your settings are correct and then click Finish.
11. Wait for installation and, if it is successful, click Save directly to master configuration.