Skip to Content

Default language.

Information
This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Storing shared library files on the mid tier

For a plug-in (such as CI Viewer, which is packaged with ) to work, the plug-in's installer copies the required native libraries to the  installation folder. When  is upgraded or re-installed, these shared library files are deleted, and you must re-copy the required native libraries to the  installation folder.

To avoid re-copying the required native libraries, store each library file as an entry in the Data Visualization System Files form in . When the  process starts, a service looks for this form on all of the servers registered as Data Visualization servers, and workflow copies the library files to the . If the file is already available in the  installation directory and the modified date matches the last-modified date of the entry in the Data Visualization System Files form, the file is not re-copied.

The Data Visualization forms are installed with the .

To store native library files for plug-ins

  1. Open the Data Visualization System Files form.
    data-visual_system.gif

  2. In the Name field, enter the file's name.

    This name must exactly match the name of the file that is attached at the bottom of the form. If the name does not match, the data visualization field will show an error message when the application within the field is run.

  3. Enter a description.
  4. Enter the status.
     The options are Active or Inactive. If the status is Inactive, the file is not copied during an upgrade or re-installation.
  5. Select the platform:
    • Windows
    • Solaris
    • Linux
    • AIX
    • HP UX

    • All — This option is used for .jar files, which are used on multiple platforms.
       The  copies only those files that match the platform you select, except for the All option, which copies .jar files.

      Entries are indexed by the Name and Platform fields.

  6. In the Version field, enter the version number of the binary file that you are saving.
     Use the following format:
    majorVersion. minorVersion. subminorVersion. patch
     For example, for version 2.0.01, patch 002, enter:
    2.0.01.002
     You can omit the trailing numbers. For example, for version 2.1.00.000, you can enter:
    2.1
     If the same file is available on a different server with a later version,  matches the version string. Then, it uses the latest version.
  7. Add the file to the attachment field.
  8. Click Save.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

AR System 22.1