Deploying and starting Studio

Once the Tomcat configuration is complete, you can deploy and start Studio.

1. Delete the contents of the endeca-portal/apache-tomcat-<version>/webapps/ROOT directory.

   This directory contains the standard Web application that is installed with Tomcat by default. We will replace this standard web application with Studio in the next step.

2. Unzip EID_2.4.x_Studio_portal_war.zip into a temporary directory.

   This zip file contains the Studio .war file and the copyright.txt file.

3. Read the copyright.txt file and then save it to the location of your choice.
4. Unzip the contents of the .war file into endeca-portal/apache-tomcat-<version>/webapps/ROOT.
5. If using a non-root context for your deployment, rename the endeca-portal\apache-tomcat-<version>\webapps\ROOT directory to endeca-portal\apache-tomcat-<version>\webapps\<context root>.

   For multi-level context paths, use the multi-level path.

   For example: endeca-portal\apache-tomcat-<version>\webapps\ROOT to endeca-portal\apache-tomcat-<version>\webapps\mycompany\sales.

6. Copy the portal-ext.properties file from the temporary directory you created for the EID_2.4.x_Studio_portal_dependencies.zip to the endeca-portal directory.
7. Edit endeca-portal\portal-ext.properties.

   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 set earlier. 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/

8. Under the endeca-portal directory, create a data directory, and then create an endeca-data-sources directory below that.
9. In the endeca-portal directory, create a deploy directory.
10. Extract the .war files from EID_2.4.x_Studio_components.zip. Place the files into the endeca-portal\deploy directory.

    The .war files are placed at the root of endeca-portal\deploy. There should be no subdirectories.

11. To start the portal's Tomcat instance, run endeca-portal\tomcat<version>\bin\startup.bat.
    Note: Server startup can take several minutes. You can follow the log messages to ascertain when the process is complete. Do not shut down the Tomcat window while Studio is running.
12. To test that the application is running, go to the portal (http://localhost:8080/) in your browser. Log in using the following default credentials:

    Field	Value
    Login:	admin@oracle.com
    Password:	admin

    For better security, after logging in for the first time, you should probably either:

    • Change the password for this user
    • Create new administrative users for your instance, and then remove this user
13. Optionally, you can set up log4j logging. log4j provides configurable, Java-based logging in an open-source utility.
    Note: For more information about Studio logging, see the Oracle Endeca Information Discovery Studio User's Guide.