Postinstallation Tasks

This section provides information about any required postinstallation steps for plug-in to be compatible with TIBCO ActiveMatrix BusinessWorks™ Administration.

1. The following steps apply for openssl 0.9.8 version.
   1. From the pijdbc_YYYY-x86-x64_.tar.gz client library archive, copy the library file libRdsaWrapper64-x.*a.so in any write access directory of the container. An example of write access directory is /tmp/pi_lib/.
   2. Create and export environment variable PI_RDSA_LIB64 for the container and assign it the absolute path of the file location copied in step 1 (a) above as follows:
      export PI_RDSA_LIB64=<FULLY_QAULIFIED_PATH_WITH_FILENAME>.

      For example, FULLY_QAULIFIED_PATH_WITH_FILENAME is /tmp/pi_lib/libRdsaWrapper64-x.*a.so.

   3. In library path, check if libssl.so.0.9.8 and libcrypto.so.0.9.8 are present. If it is not present, create soft links as follows:

   File Name	Soft Link
   libssl.so.0.9.8	ln –s /lib64/libssl.so.* /lib64/libssl.so.0.9.8
   libcrypto.so.0.9.8	ln –s /lib64/libcrypto.so.* /lib64/libcrypto.so.0.9.8

2. The following steps apply for openssl 1.0.0 version or later.
   1. From the pijdbc_YYYY-x86-x64_.tar.gz client library archive, copy the library file libRdsaWrapper64-x.*b.so in any write access directory of the container. An example of write access directory is /tmp/pi_lib/.
   2. Create and export environment variable PI_RDSA_LIB64 for container and assign it the absolute path of the file location copied in step 1 (a) above as follows:
      export PI_RDSA_LIB64=<FULLY_QAULIFIED_PATH_WITH_FILENAME>.

      For example, FULLY_QAULIFIED_PATH_WITH_FILENAME is /tmp/pi_lib/libRdsaWrapper64-x.*b.so.

   3. Check if libssl.so.1.0.0 and libcrypto.so.1.0.0 is present in library path. If it is not present, create soft links as follows:

   File Name	Soft Link
   libssl.so.1.0.0	ln –s /lib64/libssl.so.* /lib64/libssl.so.1.0.0
   libcrypto.so.1.0.0	ln -s /lib64/libcrypto.so.* /lib64/libcrypto.so.1.0.0