Version

    Oracle WebLogic Server

    Installation of CloverDX Server on Oracle WebLogic
    Configuration of CloverDX Server on Oracle WebLogic
    [Important]Important

    Before installation, check the software requirements, currently supported Oracle WebLogic versions and required Java version in the Software Requirements section.

    If you encounter any problems during the installation, see Chapter 10, Troubleshooting for a possible solution.

    Installation of CloverDX Server on Oracle WebLogic

    1. Download and install Oracle WebLogic from the official download page.

      WebLogic has to be running and a domain has to be configured. You can check it by connecting to Administration Console: http://localhost:7001/console/. Username and password are specified during installation.

    2. It is strongly recommended to adjust the default limits for Memory allocation (see the Memory Settings section).

      You can set the initial and maximum memory heap size by adjusting the "Xms" and "Xmx" JVM parameters and classloaders memory limit by adjusting the "XX:MaxMetaspaceSize" parameter:

      • Unix-like systems:

        Edit the start script and add: 

        export JAVA_OPTIONS='$JAVA_OPTIONS -Xms512m -Xmx2048m -XX:MaxMetaspaceSize=512m'

      • Windows system:

        See WebLogic Server Performance and Tuning.

    3. It is strongly recommended to double-check any third-party JDBC drivers you are planning to use with CloverDX Server, as many of them come pre-installed with WebLogic Server (but in outdated versions) and consider updating to a more recent version. See Using Third-Party JDBC Drivers for guidelines.

      For example, if using MySQL 5 as a system database, it is recommended to update to MySQL JDBC driver of version >= 5.1.48.

    4. Go to the download section of your CloverDX account and download the clover.war (web archive) file containing CloverDX Server for Oracle WebLogic Server.

    5. Change HTTP Basic Authentication configuration

      • When WebLogic finds an "Authentication" header in an HTTP request, it tries to find a user in its own realm. This behavior has to be disabled so CloverDX could authenticate users itself.

      • Edit the configuration file [domainHome]/config/config.xml and add: 

        <enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth-credentials>

        into <security-configuration> element (just before the end tag).

    6. Deploy clover.war (or an application directory).

      Use the WebLogic Server Administration Console. See the Oracle Fusion Middleware Administrator's Guide for details.

    7. Configure a license and other properties. See Configuration of CloverDX Server on Oracle WebLogic for details.

    8. Log in CloverDX Server.

      1. Type http://localhost:7001/clover in the browser.

      2. Activate the CloverDX Server.

      3. Use the default administrator credentials to access the web GUI:

        Username: clover

        Password: clover

    Configuration of CloverDX Server on Oracle WebLogic

    [Tip]Tip

    The default installation (without any configuration) is only recommended for evaluation purposes. For production use, at least a dedicated, system database and SMTP server configuration is recommended.

    For an easy configuration of CloverDX Server, use a Setup GUI in which you can configure various properties, including the connection to the database, username and password, path to the license file, private properties, Clusters and much more (see Chapter 17, List of Configuration Properties and Chapter 51, Cluster Configuration). We recommend you place the file in a specified location and specify the path to the file with a system property.

    The content of such a file (example with a PostgreSQL database): 

    datasource.type=JDBC
jdbc.driverClassName=org.postgresql.Driver
jdbc.url=jdbc:postgresql://127.0.0.1/clover_db?charSet=UTF-8
jdbc.username=yourUsername
jdbc.password=yourPassword
jdbc.dialect=org.hibernate.dialect.PostgreSQLDialect
    Properties File in Specified Location

    1. Create the cloverServer.properties file in a directory readable by WebLogic. (If you need an example of connection to any of the supported database systems, see Chapter 16, System Database Configuration.)

      The configuration file should contain DB datasource configuration, SMTP connection configuration, etc. For details, see Part III, “Configuration”.

    2. Set the clover_config_file system property (or environment variable) pointing to the configuration properties file.

      • Set the JAVA_OPTIONS variable in the WebLogic domain start script [domainHome]/startWebLogic.sh 

        JAVA_OPTIONS="${JAVA_OPTIONS} -Dclover_config_file=/path/to/clover-config.properties

    3. Restart WebLogic for changes to take effect.

    Note: When CloverDX Server is deployed on WebLogic and JNDI Datasource pointing to Oracle DB is used, there must be an extra configuration property in the configuration file: 

    quartz.driverDelegateClass=org.quartz.impl.jdbcjobstore.oracle.weblogic.WebLogicOracleDelegate
    [Note]Note

    Continue with:  Chapter 8, Postinstallation Configuration