Configuring environments without the IBM App Connect Enterprise runtime component installed

Install and run Java™ independent programs that use the IBM® DFDL API on systems that do not have the IBM App Connect Enterprise runtime component installed.

To install and run IBM DFDL independent programs in an environment that does not have the IBM App Connect Enterprise runtime component installed, complete the following steps:

1. Ensure that the target system has a compatible Java Runtime Environment (JRE) installed.
   Because you are not installing the IBM App Connect Enterprise runtime component, which includes a JRE, you must use an alternative option. For more information about Java support, see IBM App Connect Enterprise system requirements.
2. Copy the following files from a system that has the IBM App Connect Enterprise runtime component installed, to the target system:
   1. ibm-dfdl-java.zip from install_dir\server\tools, where install_dir is the directory that you specified as the installation directory for IBM App Connect Enterprise.
   2. Your Java independent program that uses the IBM DFDL API.
3. On the target system, extract the contents of ibm-dfdl-java.zip to a location of your choice; for example, C:\dfdl.

   Important: Extracting the contents of ibm-dfdl-java.zip installs license and entitlement files onto the target computer for use by IBM License Metric Tool (ILMT). You can use ILMT to monitor the usage of IBM (and other) software products.

   The extracted contents of ibm-dfdl-java.zip include a Software Identification (SWID) tag for Production-Advanced mode and a SWID tag for DFDL. The following SWID tags are detected by ILMT:

   • ibm.com_IBM_App_Connect_Enterprise-12.0.3.swidtag
   • ibm.com_IBM_Data_Format_Description_Language_-_FREE-1.1.3.swidtag

   If your IBM App Connect Enterprise installation is in Production-Advanced mode, no further action is needed. However, you must update the SWID tag in the directory where ibm-dfdl-java.zip is extracted so that ILMT reflects the correct license for the edition of IBM App Connect Enterprise that you have purchased if either of the following is true:

   • You have purchased a different edition of IBM App Connect Enterprise.
   • You change the operation mode to one of the following modes:
     • Production-Standard
     • Non-Production

   You can update the SWID tag by performing the following steps:

   1. On a machine on which you have installed IBM App Connect Enterprise, change to the swidtag directory to view the SWID tag files. The SWID tag file has the suffix swidtag if the operation mode is active or the suffix deactivated if the operation mode is inactive. If you are intending to change the operation mode, see Operation modes prior to changing the operation mode to ensure that the correct SWID tag is activated.
   2. Copy the active SWID tag file from the swidtag directory to the directory where ibm-dfdl-java.zip is extracted:
      • ibm.com_IBM_App_Connect_Standard-12.0.3.swidtag (Production-Standard mode)
      • ibm.com_IBM_App_Connect_Enterprise_for_NON-PRODUCTION-12.0.3.swidtag (Non-Production mode)
   3. Delete the Production-Advanced mode SWID tag, ibm.com_IBM_App_Connect_Enterprise-12.0.3.swidtag, from the directory where ibm-dfdl-java.zip is extracted.

   For more information about ILMT, see the IBM License Metric Tool website

Update the class path environment variable:

4. Add all of the JAR files that are required for IBM DFDL.
   For example:

   set CLASSPATH = %CLASSPATH%;C:\dfdl\lib\ibm-dfdl.jar

   Repeat this step for each JAR file in your extract_dir\lib directory, where extract_dir is the directory to which you extracted ibm-dfdl-java.zip. Alternatively, to add all of the required JAR files, run the dfdlprofile utility that is provided in your extract_dir\bin directory.
5. If you want to run and explore the IBM DFDL sample, add the dfdlsample_java.jar JAR file in your extract_dir\samples directory.
   For example:

   set CLASSPATH = %CLASSPATH%;C:\dfdl\samples\dfdlsample_java.jar

6. Add your DFDL independent program JAR file.
7. Add any other JAR files and directories that you require.