|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 Chapter 10, Troubleshooting for a possible solution.
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.
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/).
Go to→ → → → → →
Change the value in the Maximum heap size field to 2048 MB. The default value (256 MB) is insufficient for ETL transformations.
Figure 7.3. Adjusting Maximum heap size limit
Add the following parameters into the Generic JVM arguments field to set the perm space limit and direct memory limit:
Java runtime settings:
Go to→ → → → and select version 1.8 as the default SDK.
Save the changes to configuration and restart the server so that they take effect.
Go to the download section of your CloverDX account
and download the
clover.war (web archive)
file containing CloverDX Server for WebSphere.
Go to Integrated Solutions Console (default URL: http://localhost:9060/ibm/console/).
Go to CloverDX Server WAR archive and deploy it to the application server, but do not start it yet.→ → , select the
Configure application class loading.
Go to Class loader order select Classes loaded with local class loader first (parent last).→ → → and under
Save the changes to the Server configuration and start the clover_war application.
Log in CloverDX Server.
Please note that some CloverDX features using third party libraries do not work properly 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 Chapter 15, List of Configuration Properties and Chapter 42, 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
The properties file is loaded from a location which is specified by 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 Chapter 14, System Database Configuration.)
Set a system property (or environment variable)
pointing to the properties file.
Go to Integrated Solutions Console (default URL:http://localhost:9060/ibm/console/).
Go to→ → → → → → .
Create a system property named
whose value is a full path to the properties file (e.g.
cloverServer.properties) on your file system.
Restart IBM WebSphere for changes to take effect.
Continue with: Chapter 8, Postinstallation Configuration