Version

    IBM WebSphere

    Installation of CloverDX Server on IBM WebSphere

    Configuration of CloverDX Server on IBM WebSphere

    Before installation, check the software requirements, currently supported IBM WebSphere version and required Java version in the Software Requirements section.

    If you encounter any problems during the installation, see Troubleshooting for a possible solution.
    Installation of CloverDX Server on IBM WebSphere

    1. Download and install IBM WebSphere from the official download page.

      Note: During installation, make sure the IBM WebSphere profile name does not contain the keyword clover, otherwise the CloverDX Server won’t start properly.

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

      You can set the limits in IBM WebSphere’s Integrated Solutions Console (default URL: http://localhost:9060/ibm/console/).

      1. Go to Servers  Server Types  WebSphere application servers  [Server_Name (default name: server1) > Java and Process Management > Process definition > Java Virtual Machine]

      2. Change the value in the Maximum heap size field to 2048 MB. The default value (256 MB) is insufficient for ETL transformations.

        websphere heapMemoryLimit
        Figure 5. Adjusting Maximum heap size limit

      3. Add the following parameters into the Generic JVM arguments field to set the perm space limit and direct memory limit:

        -XX:MaxPermSize=512M

        -XX:MaxDirectMemorySize=512M

      4. Java runtime settings:

        Go to Servers  Server Types  WebSphere application servers  [Server_Name (default name: server1) > Java SDKs] and select version 1.8 as the default SDK.

      5. Save the changes to configuration and restart the Server so that they take effect.

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

    4. Deploy the clover.war file.

      1. Go to Integrated Solutions Console (default URL: http://localhost:9060/ibm/console/).

      2. Go to Applications  New Application  New Enterprise Application, select the CloverDX Server WAR archive and deploy it to the application server, but do not start it yet.

    5. Configure application class loading.

      Go to WebSphere Enterprise Applications  clover_war (or other name of the Clover application)  Manage Modules  CloverDX  Server-specific Application Settings and under Class loading mode select Classes loaded with local class loader first (parent last).

    6. Save the changes to the Server configuration and start the clover_war application.

    7. Log in CloverDX Server.

      1. Provided you set clover.war as the application running with "clover" context path, use the following URL (notice the port number has changed):

        http://localhost:9080/clover

      2. Activate the CloverDX Server.

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

        Username: clover

        Password: clover

    When uploading a large number of files in quick succession, the server may return HTTP Status Code 408 Request Timeout. To fix it, set the Maximum persistent requests per connection property to -1 (unlimited) in the WebSphere console. For more information, see WebSphere’s HTTP transport channel settings.

    Some CloverDX features using third party libraries do not work properly on IBM WebSphere.

    • Hadoop is guaranteed to run only on Oracle Java 1.6+, but Hadoop developers do make an effort to remove any Oracle/Sun-specific code. See Hadoop Java Versions on Hadoop Wiki.
    Configuration of CloverDX Server on IBM WebSphere

    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 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 List of Configuration Properties and 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 (an example with a PostgreSQL database):

    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

    The properties file is loaded from a location which is specified by the environment/system property clover_config_file or clover.config.file.

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

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

      1. Go to Integrated Solutions Console (default URL: http://localhost:9060/ibm/console/).

      2. Go to Servers  WebSphere application servers  [Server_name > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties].

      3. Create a system property named clover_config_file whose value is a full path to the properties file (e.g. cloverServer.properties) on your file system.

    3. Restart IBM WebSphere for changes to take effect.

    arrow Continue with: Postinstallation Configuration