FlexDeploy provides a file distribution for Tomcat which simplifies the installation process. This distribution contains Tomcat, the FlexDeploy WAR, and the base configurations, leaving only a few simple steps to complete the install. The distribution contains the following components.
If you wish to use an existing Tomcat server, or to use a different version of Tomcat other than 8.5.11, please see Installing FlexDeploy on existing Tomcat.
Setup the database for FlexDeploy, if you have not already done so.
Modify the following Tomcat configuration files as follows:
<FlexDeploy Home>/apache-tomcat-flexdeploy/conf/context.xml
Replace **CONNECT_STRING** with JDBC connect string of your database containing the FlexDeploy schemas
Replace **FD_ADMIN_PASSWORD** with the password of the FD_ADMIN database user. You would have supplied password when you ran Database installation scripts.
For example, a localhost XE connection will look like this. jdbc:oracle:thin@localhost:1521:XE
<FlexDeploy Home>/apache-tomcat-flexdeploy/conf/server.xml
By default, the Tomcat server is configured to run on port 8000. If this port is in use, change to some other unused port. Search for <Connector port="8000" protocol="HTTP/1.1" if you want to change it
<FlexDeploy Home>/apache-tomcat-flexdeploy/bin/setenv.sh (setenv.bat on windows)
Replace **FLEXDEPLOY_WORKING_DIR** with directory to use as the FlexDeploy working directory (See Create Folders for FlexDeploy Server - FlexDeploy Working Directory)
Replace **FLEXDEPLOY_ARTIFACT_DIR** with the directory to host the FlexDeploy artifact repository (See Create Folders for FlexDeploy Server - FlexDeploy Artifact Repository)
If JAVA_HOME isn't already set in your environment, it would be a good idea to set it in this file as well. Otherwise, it can be set manually before starting the server. |
For example below, we created artifacts and work directories under C:/installs/FlexDeploy
For this example (Windows) we modified setenv.bat as shown below.
If you were also setting JAVA_HOME, this file would look like this.
If adding another JDBC driver, be sure to remove the default one which comes with the ADF Essentials libraries (ojdbc6dms.jar). If you leave multiple JDBC drivers in the lib folder, you could encounter the following exception on startup: java.lang.SecurityException: sealing violation: package oracle.jdbc is sealed at java.net.URLClassLoader.getAndVerifyPackage(Unknown Source) at java.net.URLClassLoader.definePackageInternal(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$100(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) |