To install Studio, you deploy the .ear file into the WebLogic domain. For a development environment, you can use the autodeploy function. In a production environment, you must use the WebLogic Administration Console.
To deploy the Studio .ear file:
This version of the file is at the top level of the .zip file, and contains the complete set of Studio default settings.
For example:
liferay.home=/localdisk/liferay
The property is at the beginning of the file.
When setting the portal.ctx value, do not include a trailing slash. For example, use this value:
portal.ctx=/mycompany/portal
Do not use this value:
portal.ctx=/mycompany/portal/
If your data sources are connected to a secured Endeca Server, then this directory will contain the associated Java Keystore (JKS) files.
For details on connecting data sources to a secured Endeca Server, see the Oracle Endeca Information Discovery Studio User's Guide.
The startup script is in the bin subdirectory of the domain directory.
For a development environment, you can use the autodeploy option to deploy the file. For example, for Linux:
cp endeca-portal-weblogic-2.4.ear <DomainDirectory>/autodeploy
Where <DomainDirectory> is the path to the domain directory.
For a production environment, you need to use the WebLogic Administration Console to deploy the file:
The deployment may take several minutes. Make sure you do not try to log in to Studio before the deployment is complete.
Note that when you deploy the .ear file, you are deploying the complete set of standard Studio components. To remove components, or add custom components, you need to update the .ear file. For information on adding components to and removing components from the .ear file, see the Oracle Endeca Information Discovery Studio Developer's Guide.
By default, WebLogic uses port 7001.
You should see the Studio welcome page.