Home | Table of ContentsIBM Websphere
Prev Installation Next

IBM Websphere

Installation of CloverETL Server

  1. get the web archive file (clover.war) with CloverETL Server application which is built for Websphere

  2. check prerequisites

    • JDK or JRE version 1.6.x or higher

  3. deploy WAR file

    • go to section Applications → New Application → New Enterprise Application

  4. change class loader setting

    CloverETL requires different class-loader settings in WebSphere 6 and WebSphere 7. In WebSphere 7, it is by default Classes loaded with parent class loader first, whereas in WebSphere 6, the default value must be changed to Classes loaded with application class loader first

    • change Applications → Clover → Manage Modules → clover.war → Class loader Order → Classes loaded with application class loader first

  5. configure system property on Websphere 6

    Websphere 6 sets system property "javax.xml.transform.TransformerFactory" to the value "com.ibm.xtq.xslt.jaxp.compiler.TransformerFactoryImpl". This setting overrides default value used by CloverETL Server which is vital for webservice API. So please set explicitly correct value in the Websphere admin console.

    [Note]Note

    It is not necessary to set this in Websphere 7. You can skip the workaround below and advance to the next step.

    • go to Integrated Solutions Console

      ( http://localhost:9060/ibm/console/)

    • go to Servers → Application servers → [server1] (or the other server of correct name) → Java and Process Management → Java Virtual Machine

    • In this section add "-Djavax.xml.transform.TransformerFactory=org.apache.xalan.processor.TransformerFactoryImpl" to the input labelled "Generic JVM arguments"

    • Then submit the form by "OK" button, then commit changes by "save" link. This change needs restart of Websphere to take effect.

    • You can check whether its properly is set or not in CloverETL Server web GUI, in the section "monitoring", "System properties" tab. There should be "javax.xml.transform.TransformerFactory" system property with correct value.

  6. configure logging

    Websphere loggers do not use log4j by default which may cause CloverETL Server logging to be ill-configured. As a result, some CloverETL Engine messages are missing in graph execution logs. Thus it is recommended to configure Websphere properly to use log4j. Add this config file to the Websphere directory: AppServer/profiles/AppSrv01/properties/commons-logging.properties Content of the file should be like this: 

    			priority=1
			org.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.LogFactoryImpl
			org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4JLogger

    Afterwards, copy jar files from the clover.war/WEB-INF/lib archive to the AppServer/lib directory. Copy all files like commons-logging-*.jar and log4j-*.jar.

  7. try if the server is running

    Provided you set clover.war as application running with "clover" context path. Notice the port number has changed:

    http://localhost:9080/clover

Installation of CloverETL Server license

CloverETL Server requires a valid license for executing graphs. You can install CloverETL Server without license, but no graph will be executed.

  1. get file license.dat

  2. set CloverETL Server parameter license.file to the path to the license.dat file

    There are more ways how to do this. The most direct way is to set environment property clover_license_file. (See Chapter 16, Configuration for description of all possibilities).

    • go to Integrated Solutions Console

      ( http://localhost:9060/ibm/console/)

    • go to Servers → Application servers → [server-name] → Java and Process Management → Process Definition → Environment Entries

    • create system property named clover_license_file whose value is the absolute path to license.dat on the file system

    • Then you have to let CloverETL Server know the license has changed. Go to web GUI → Monitoring → License. Then click the Reload license button. Or you can restart CloverETL Server application.

[Note]Note

CloverETL license can be changed any time by replacing file license.dat. Then you have to let CloverETL Server know the license has changed.

  • Go to web GUI → monitoring section → license tab

  • Then click the button reload license.

  • Or you can restart CloverETL Server application.

Prev Up Next
Jetty Home | Table of Contents Glassfish / Sun Java System Application Server