Third-Party File Requirements

To use ldt Solutions with various third-party applications, you must make JAR files from the third-party application available to ldt.
dts105-10-4
To use
DevTest
Solutions with various third-party applications, you must make JAR files from the third-party application available to
DevTest
.
For information about adding user-specific JAR and ZIP files to the classpath, see Adding User-specific JAR and ZIP Files to the Workstation Classpath.
Unless otherwise specified in the following sections, you can use any of these approaches:
  • Place the files in the
    LISA_HOME\hotDeploy
    directory
  • Place the files in the
    LISA_HOME\lib
    directory
  • Define the
    LISA_POST_CLASSPATH
    variable
The following example shows the
LISA_POST_CLASSPATH
variable on a Windows computer. The files in this example are WebSphere MQ files.
LISA_POST_CLASSPATH="C:\Program Files\IBM\MQSeries\Java\lib\com.ibm.mq.allclient.jar;C:\Program Files\IBM\MQSeries\Java\lib\com.ibm.mq.commonservices.jar;C:\Program Files\IBM\MQSeries\Java\lib\javax.jms-api-2.0.jar"
CA does
not
provide the third-party files that are listed in this page.
The JAR files must support Java 8.
The
hotDeploy
directory can be in a location other than
LISA_HOME
. For an explanation of what files may be in a separate data directory, see Installation Options.
2
ActiveMQ File Requirements
To use CA 
DevTest
 Solutions with various third-party applications, ensure that JAR files from the third party are available to 
DevTest
:
  1. Ensure that the following file exists in the LISA_HOME\hotDeploy directory:
    activemq-client-X.X.X.jar
  2. The functioning of activemq-client JAR file depends on hawtbuf JAR file. An appropriate version of hawtbuf JAR file is also required for 
    DevTest
     to work with ActiveMQ broker. You can find the relevant version of hawtbuf JAR file for the ActiveMQ client jar version in ActiveMQ::Client. The correct version of hawtbuf JAR file version is mentioned in the Compile Dependencies for the corresponding activemq-client version. Place the hawtbuf JAR file in the LISA_HOME\hotDeploy directory. 
Apache Kafka
DevTest Solutions
 requires Apache Kafka version 0.8.2 or later. Kafka 1.1.0 requires the following jars from KAFKA_HOME/libs directory:
  • kafka-clients-1.1.0.jar
  • lz4-java-1.4.jar
  • slf4j-log4j12-1.7.25.jar
  • snappy-java-1.1.7.1.jar
See the Apache Kafka documentation for more information about the JAR files that you might need.
The
LISA_HOME\hotDeploy
option is not supported for Apache Kafka. You must place these files in the  
LISA_HOME\lib
 directory.
JCAPS File Requirements
If you are using the JCAPS Messaging (Native) step, see the JCAPS documentation for information about the JAR files that you might need.
If you are using the JCAPS Messaging (JNDI) step, the
com.stc.jms.stcjms.jar
file is required. See the JCAPS documentation for information about other JAR files that you might need.
The JAR files are available in the
lib
directory of the JCAPS installation.
JMS Messaging File Requirements
If you are using the JMS Messaging (JNDI) step, see the JMS provider documentation for information about the JAR files that you might need.
Oracle OC4J File Requirements
The following JAR files are required:
  • dms.jar
  • oc4j.jar
  • oc4jclient.jar
See the OC4J documentation for more information about JAR files that you might need. The JAR files are available in the
lib
directory of the OC4J installation.
RabbitMQ Requirements
Copy the JAR file to the 
LISA_HOME\lib
 directory or define the 
LISA_POST_CLASSPATH
 variable. Do not copy the file to the 
LISA_HOME\hotDeploy
 directory.
The following JAR file is required:
  • amqp-client-x.x.x.jar
SAP File Requirements
The following JAR files are required:
  • sapjidoc3.0.8/sapidoc3.jar - required for the SAP IDoc steps and virtualization
  • sapjco3.0.9/sapjco3.jar
  • sapjco3.0.9/
    platform
    / a native library file of the platform, where
    platform
    is your computer system (osx_64, windows_x86, and others) - required for the SAP RFC step and the SAP IDoc steps and virtualization
SAP IDoc Virtualization Requirements
  1. Create an RFC Destination of type T on both the client and server SAP systems.
    DevTest
    uses this RFC Destination to receive IDocs from both systems.
  2. Update the outbound partner profile on the client and server SAP system. Update the outbound parameter in the partner profile for the respective IDoc type to send to the port number associated with the RFC Destinations that are created in Step 1. This allows
    DevTest
    to receive IDocs from the client and server SAP systems.
  3. Create and import the connection property files in your project under the Data directory.
    1. Create the RFC Connection (with properties from .jcoServer) for the client RFC Destination created in Step 1.
    2. Create the System Connection property file (with properties from .jcoDestination) for the client SAP system.
    3. Create the RFC Connection (with properties from .jcoServer) for the server RFC Destination created in Step 1.
    4. Create the System Connection property file (with properties from .jcoDestination) for the server SAP system.
Before you begin recording, you must also create and import the connection property files in your project under the
Data
directory. You need these files to start JCo servers to receive IDocs from and forward IDocs to the client and server SAP systems. You need the RFC Connection (with properties from .jcoServer) and System Connection (with properties from .jcoDestination) property files. You need these files to start JCo servers to receive IDocs from and forward IDocs to the client and server SAP systems. Consult the SAP administrator about populating these property files.
SAP RFC Virtualization Requirements
  1. Create an RFC Destination of type T on the client SAP system.
    DevTest
    uses this RFC Destination to intercept remote function calls that the client system makes.
  2. Update the ABAP code that makes the remote function call to use the new destination.
  3. Create and import the connection property files in your project under the Data directory. Consult the SAP administrator about populating these property files.
    1. Create the RFC Connection (with properties from .jcoServer) for the client RFC destination that was created in Step 1. This file MUST NOT specify jco.server.repository_destination.
    2. Create the Repository Connection property file (with properties from the .jcoDestination) for the system that acts as the RFC repository. This is typically the same as the system on which the RFC was run.
    3. Create the System Connection property file (with properties from the .jcoDestination) for the system where the RFC runs. If this is the same as the Repository connection, only one properties file is needed.
SonicMQ File Requirements
The following JAR files are required:
  • mfcontext.jar
  • sonic_Client.jar
  • sonic_XA.jar
The JAR files are available in the
lib
directory of the SonicMQ installation.
TIBCO File Requirements
The requirements for TIBCO vary depending on the application.
Copy the JAR files to the
LISA_HOME\lib
directory or define the
LISA_POST_CLASSPATH
variable. Do not copy the files to the
LISA_HOME\hotDeploy
directory.
TIBCO Rendezvous Messaging
The following JAR files are required:
  • tibrvj.jar
  • tibrvjms.jar
  • tibrvjsd.jar
  • tibrvjweb.jar
  • tibrvnative.jar
  • tibrvnativesd.jar
TIBCO Rendezvous .dll files are also required. Copy all .dll files from the TIBCO Rendezvous
bin
directory to the
LISA_HOME\bin
directory. Reference the
LISA_HOME\bin
location in your path environment.
In addition, add the TIBCO Rendezvous
bin
directory to your
PATH
environment variable.
TIBCO EMS Messaging or TIBCO Direct JMS
The following JAR files are required:
  • tibcrypt.jar
  • tibjms.jar
  • tibjmsadmin.jar
  • tibjmsapps.jar
  • tibrvjms.jar
TIBCO Hawk Metrics
The following JAR files are required:
  • console.jar
  • talon.jar
  • util.jar
TIBCO Rendezvous and/or TIBCO EMS JAR files, depending on which transport TIBCO Hawk is using, also must  be copied to the
LISA_HOME\lib
directory.
WebLogic File Requirements
The
weblogic.jar
file is required. If you are using security or JMX, other JAR files might be required.
See the WebLogic documentation for more information about JAR files that you might need. The JAR files are available in the
lib
directory of the WebLogic installation.
webMethods File Requirements
The following JAR files are required:
  • (webMethods Integration Server 8.2) Copy the wm-isclient.jar from your webMethods installation to your DevTest installation_directory\lib\shared directory.
  • (webMethods Integration Server 7.1 and later) installation_directory\lib\shared\wm-isclient.jar
  • (webMethods Integration Server 7.0 and earlier) installation_directory\lib\client.jar
  • wm-enttoolkit.jar
  • wmbrokerclient.jar
  • wmjmsadmin.jar
  • wmjmsclient.jar
  • wmjmsnaming.jar
The JAR files are available in the
lib
directory of the webMethods installation.
WebSphere MQ File Requirements
Copy the JAR files to the
LISA_HOME\lib
directory or define the
LISA_POST_CLASSPATH
variable. Do not copy the files to the
LISA_HOME\hotDeploy
directory.
If the operating system is a Japanese version, use the files that are listed for WebSphere MQ 7.
The JAR files are available in the
MQ_HOME\java\lib
directory.
WebSphere MQ 5.2
The following JAR files are required for WebSphere MQ 5.2:
  • com.ibm.mqjms.jar
  • com.ibm.mqbind.jar
  • com.ibm.mq.pcf.jar
  • com.ibm.mq.jar
  • connector.jar
WebSphere MQ 6
The following JAR files are required for WebSphere MQ 6:
  • com.ibm.mq.jar
  • com.ibm.mq.pcf.jar
  • com.ibm.mqjms.jar
  • connector.jar
  • dhbcore.jar
WebSphere MQ 7
The following JAR files are required for WebSphere MQ 7:
  • com.ibm.mq.commonservices.jar
  • com.ibm.mq.headers.jar
  • com.ibm.mq.jar
  • com.ibm.mq.jmqi.jar
  • com.ibm.mq.pcf.jar
  • com.ibm.mqjms.jar
  • connector.jar
  • dhbcore.jar
WebSphere MQ 8 and 9
The following JAR files are required for WebSphere MQ 8 and 9:
  • com.ibm.mq.allclient.jar
  • com.ibm.mq.commonservices.jar
Alternately, you can use the following JAR files:
  • com.ibm.mq.commonservices.jar
  • com.ibm.mq.headers.jar
  • com.ibm.mq.jar
  • com.ibm.mq.jmqi.jar
  • com.ibm.mq.pcf.jar
  • com.ibm.mqjms.jar
In addition, if you are using WebSphere MQ in JMS mode, the javax.jms-api-2.0.jar file is required.