To install the patch [UNIX]:

1. Change directory to the root directory of the Data Management Server 
   installation. This is the directory named 'dmserver' created during 
   installation. For example, if you installed Data Management Server in 
   /opt/sas94/SASHome/DataFluxDataManagementServer/2.9, run this command:
 
       cd /opt/sas94/SASHome/DataFluxDataManagementServer/2.9/dmserver

2. Stop the server if it is running. Run the command:

       ./bin/dmsadmin stop

3. (AIX only) Run this command:

       ./bin/uncache_libs

   or ask your sysadmin to run the slibclean command on the system.

4. Optionally, make backup copies of the files affected by this patch. If
   you decide to make backup copies, make sure you place the copied files in a 
   different directory than the original files. Renaming the files in the 
   original directory may lead to unexpected errors in the software. See the 
   end of this text file for a list of affected files.

5. Run this command:
   
       gzip -d -c PATH_TO/J6K007XX.tar.gz | tar xvf -

   replacing PATH_TO with the correct path to the patch file and XX with
   the platform abbreviation (r6, la, etc.).

6. Run the following script to delete the empty jar files created by the
   patch:

       sh bin/fix21367.sh

7. If you stopped the server in step 2, restart it. Run the command:

       ./bin/dmsadmin start

To install the patch [Windows]:

1. If you have multiple instances of the server installed on the machine, 
   determine the name of server instance you will be patching. This was chosen
   during the initial installation, and defaults to 'server1'. 

2. Stop the DataFlux Data Management Server service for the instance if it is 
   running. You can check the status of the service using the Services applet 
   on the Windows Control Panel (may be found under Administrative Tools). The
   instance name is included the display name in the applet, for example:

       DataFlux Data Management Server (server1)

3. Optionally, make backup copies of the files affected by this patch. If
   you decide to make backup copies, make sure you place the copied files in a 
   different directory than the original files. Renaming the files in the 
   original directory may lead to unexpected errors in the software. See the 
   end of this text file for a list of affected files.

4. Unzip the archive J6K007wn.zip (32-bit server) or 
   J6K007x6.zip (64-bit server) into the root directory of 
   your Data Management Server instance. This is typically:

      C:\Program Files\SASHome\DataFluxDataManagementServer\2.9

   If you chose a different location for SASHome or the Data Management Server
   instance, adjust the path accordingly.

5. Run the following script to delete the empty jar files created by the
   patch. From a command prompt running as Administrator, run the script:

      bin\fix21367.bat

   in the installation root directory (this is the same directory used in step
   4). For example:

      cd "C:\Program Files\SASHome\DataFluxDataManagementServer\2.9"
      bin\fix21367.bat

6. If you stopped the Data Management Server service in step 2, restart it.

The following files will be installed or updated by this patch:

    [aix64]
    bin/fix21367.sh
    lib/java_support/log4j-1.2-api-2.13.jar
    lib/java_support/log4j-1.2-api-2.17.jar
    lib/java_support/log4j-api-2.13.jar
    lib/java_support/log4j-api-2.17.jar
    lib/java_support/log4j-core-2.13.jar
    lib/java_support/log4j-core-2.17.jar

    [hpux-i64]
    bin/fix21367.sh
    lib/java_support/log4j-1.2-api-2.13.jar
    lib/java_support/log4j-1.2-api-2.17.jar
    lib/java_support/log4j-api-2.13.jar
    lib/java_support/log4j-api-2.17.jar
    lib/java_support/log4j-core-2.13.jar
    lib/java_support/log4j-core-2.17.jar

    [lin64]
    bin/fix21367.sh
    lib/java_support/log4j-1.2-api-2.13.jar
    lib/java_support/log4j-1.2-api-2.17.jar
    lib/java_support/log4j-api-2.13.jar
    lib/java_support/log4j-api-2.17.jar
    lib/java_support/log4j-core-2.13.jar
    lib/java_support/log4j-core-2.17.jar

    [sol64]
    bin/fix21367.sh
    lib/java_support/log4j-1.2-api-2.13.jar
    lib/java_support/log4j-1.2-api-2.17.jar
    lib/java_support/log4j-api-2.13.jar
    lib/java_support/log4j-api-2.17.jar
    lib/java_support/log4j-core-2.13.jar
    lib/java_support/log4j-core-2.17.jar

    [solaris-x64]
    bin/fix21367.sh
    lib/java_support/log4j-1.2-api-2.13.jar
    lib/java_support/log4j-1.2-api-2.17.jar
    lib/java_support/log4j-api-2.13.jar
    lib/java_support/log4j-api-2.17.jar
    lib/java_support/log4j-core-2.13.jar
    lib/java_support/log4j-core-2.17.jar

    [win32]
    bin/fix21367.bat
    lib/java_support/log4j-1.2-api-2.13.jar
    lib/java_support/log4j-1.2-api-2.17.jar
    lib/java_support/log4j-api-2.13.jar
    lib/java_support/log4j-api-2.17.jar
    lib/java_support/log4j-core-2.13.jar
    lib/java_support/log4j-core-2.17.jar

    [win64]
    bin/fix21367.bat
    lib/java_support/log4j-1.2-api-2.13.jar
    lib/java_support/log4j-1.2-api-2.17.jar
    lib/java_support/log4j-api-2.17.jar
    lib/java_support/log4j-api-2.13.jar
    lib/java_support/log4j-core-2.13.jar
    lib/java_support/log4j-core-2.17.jar