Deploying and starting Studio

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

1. Unzip EID_3.1.x_Studio_portal_war.zip into a temporary directory.

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

2. Read the copyright.txt file and then save it to the location of your choice.
3. Assuming you are using the /eid context, unzip the contents of the .war file into endeca-portal/apache-tomcat-<version>/webapps/eid.
4. If using a different context for your deployment, unzip the .war file into endeca-portal/apache-tomcat-<version>/webapps/<context root>.

   For example, if the context is /sales, unzip the file into endeca-portal/apache-tomcat-<version>/webapps/sales

   For multi-level context paths, use the multi-level path. For example, if the context path is /mycompany/sales, unzip the file into endeca-portal/apache-tomcat-<version>/webapps/mycompany/sales.

5. Copy the portal-ext.properties file from the temporary directory you created for the EID_3.1.x_Studio_portal_dependencies.zip to the endeca-portal directory.
   This file is basically a stub configuration file you use to override default Studio configuration, for example when:

   • Changing the database used for Studio
   • Overriding Studio framework settings
   • Configuring a Studio cluster
   • Configuring a reverse proxy

   For the default Studio configuration, you do not need to make any changes to this file.

6. Under the endeca-portal directory, create a data directory, and then create an endeca-data-sources directory below that.
7. In the endeca-portal directory, create a deploy directory.
8. Extract the .war files from EID_3.1.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.

9. 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.
10. To test that the application is running, go to the portal (http://localhost:8080/<context root>) in your browser.

    For example, if you are using the recommended context path of /eid, you would go to http://localhost:8080/eid

11. Log in using the following default credentials:

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

    You are immediately prompted to change the password. The new password must contain:

    • At least 6 characters
    • At least one non-alphabetic character
12. 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 Studio Administration and Customization Guide.