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 not already done so.
Modify Tomcat configuration file (context.xml) for database connectivity.
<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.(
localhost XE connection will look like this. jdbc:oracle:thin:@localhost:1521:XE SID based JDBC URL Syntax - jdbc:oracle:thin:@HOSTNAME:PORT:SID Service Name based JDBC URL Syntax - jdbc:oracle:thin:@//HOSTNAME:PORT/SERVICENAME |
(Optional) Modify Tomcat server.xml for port if necessary.
<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.
There are other ports referenced in the server.xml file as well. If the logs contain a port in use error, you can find the open ports on your machine and then search this file for ports that you find are in use and change them.
(Optional) Modify Tomcat Environment script (setenv.sh or setenv.bat) for FlexDeploy server side directories.
If you are setting up FlexDeploy for Trial purposes, it is good idea to leave directories as default, but if you are setting up FlexDeploy for production use, then we recommend to modify to use directory structure outside of FlexDeploy installation. |
<FlexDeploy Home>/apache-tomcat-flexdeploy/bin/setenv.sh (setenv.bat on windows)
Configure -Dflexagon.fd.install.root with directory to use as the FlexDeploy working directory (See Create Folders for FlexDeploy Server - FlexDeploy Working Directory)
Configure -Dflexagon.fd.repository.root with the directory to host the FlexDeploy artifact repository (See Create Folders for FlexDeploy Server - FlexDeploy Artifact Repository)
Below are default artifact and working directories created under FlexDeploy Home when you extracted zip file. If you want to use different directories then modify setevn.sh or setenv.bat file, otherwise skip this step.
Default setenv.bat is shown below.
Modify Tomcat Environment script (setenv.sh or setenv.bat) for JAVA_HOME.
Even when JAVA_HOME is already set in your environment, it would be a good idea to set it in this file (setenv.sh or setenv.bat) as well. Unix Example - export JAVA_HOME=/u01/java/jdk1.8.0_121 Windows Example - set JAVA_HOME=c:/installs/Java/jdk1.8.0_121 |
If you were also setting JAVA_HOME, this file would look like this.
ADF Essentials comes with the JDBC driver for Oracle 11g database (ojdbc6dms.jar). If you are using Oracle 12c database, you can download the driver (ojdbc7.jar) from the Oracle Technology Network site at Oracle 12c drivers. Delete ojdbc6dms.jar from <FlexDeploy Home>/apache-tomcat-flexdeploy/lib and place ojdbc7.jar in that same folder.
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) |
<FlexDeploy Home>/apache-tomcat-flexdeploy/bin/startup.sh (startup.bat on Windows)
After starting your server, check the <FlexDeploy Home>/apache-tomcat-flexdeploy/logs/flexdeploy.0.log file for the following error message:
If present, increase the number of processes for the database
|