TAFJ Spooler Plugins
The TAFJ Spooler Plugins are used to redirect reports to a different server. Some of the jars need to be put in the shared lib classpath for the customer. This section discusses the setups for JBoss, WebSphere and WebLogic.
The following table provides the details of these JARs.
| Plug-in | JAR File |
|---|---|
|
SFTP |
jsch-<version>.jar |
|
Jackrabbit |
jackrabbit-core-<version>.jar jackrabbit-jcr-rmi-<version>.jar |
The JARs can be found in $TAFJ_HOME/3rdParty/reporting.
Setup for JBoss
In addition to the appropriate classpath setup, you need to deploy TAFJSpoolerPlugins.rar.
Setup for Websphere
In addition to the appropriate classpath setup, you need to deploy your resource adapter under Resources > Resource Adapters. The CLASSPATH must be set to ${TAFJ_HOME}/lib as WAS tries to introspect the rar classes and checks for the TAFJ logger.
The temn.tafj.spooler.conn.factory.lookup=eis/PrintHold must be set in tafj.properties.
In Enterprise Applications > TAFJJEE_EAR >ClassLoader, the Classes loaded with local class loader first (parent last) checkbox must be enabled. If not, ClassNotFound exception might be displayed when trying to load the Spooler plugin from TAFJSpoolerPlugins.jar. You need to create a J2C Connection Factory.
Setup for WebLogic
In Deployments, you need to click on Install to intall TAFJSpoolerPlugins.rar. Once the file is installed, it should run. The JNDI name does not appear at times even though it is available. This issue appears to be a WebLogic bug. You can check for JNDI name under Environment > Servers > Your server > JNDI View.
In this topic