# Editing the portal-ext.properties file for WAS 7 deployment

Before deploying your portal-ext.properties file, you must edit it.

Endeca's default version of portal-ext.properties is included in the package endeca-portal-dependencies-<version>.zip.

1. Open the portal-ext.properties file and add the following lines to the end of the file:

       # Specify a directory where Liferay will "deploy" processed plugins.
       # From this directory, WAS users will deploy WARs as modules in the
       # Discovery Framework enterprise application.
       #
       auto.deploy.dest.dir=${liferay.home}/websphere-deploy
       #
       # Set this to true to enable JMX integration in
       # com.liferay.portal.cache.EhcachePortalCacheManager.
       #
       ehcache.portal.cache.manager.jmx.enabled=false

   Note: The destination directory (specified by the `auto.deploy.dest.dir` setting) must exist before the plugin is hot-deployed. In the above example, you must manually create the websphere-deploy directory if it does not exist.
2. Find the portal.ctx property at the beginning of portal-ext.properties. Change the value of this setting to be the same context root value you used when deploying the standalone portal WAR. However, do not include a trailing slash in the portal.ctx value. For example, use this value:

       portal.ctx=/mycompany/portal

   Do not use this value:

       portal.ctx=/mycompany/portal/

3. Save the file.