Ensure you do not make any changes to the package Directory ([Product directory]/package), or to any of the package directory contents, other than the permissible changes described in this document.

The following steps are used to access and use the custompackage Directory.

  1. To create a modified version of a file distributed in the package directory, create a copy of the file in the custompackage directory ([Product directory]/custompackage), setting up the same directory structure as under the package directory.

  2. Make the necessary modifications to that file. Use the following steps for this procedure:

  3. Identify the directory structure under the package directory containing the file that is to be modified. For example: [Product directory]/package/cisco/catos

  4. Create the exact same directory structure under the custompackage directory. For example: mkdir –p [Product directory]/custompackage/cisco/catos

  5. Copy the file to be modified from the directory structure under the package directory, to the directory structure under the custompackage directory. For example: cp [Product directory]/package/cisco/catos/devCiscoCat.dasl

  6. [Product directory]/custompackage/cisco/catos/devCiscoCat.dasl

  7. You can now make the needed changes to the file under the custompackage directory. For example: vi [Product directory]/custompackage/cisco/catos/devCiscoCat.dasl

  8. Restart the device server services. If there are multiple device servers, make the same changes individually, on all device servers; meaning the same steps must be repeated on each device server.

  9. If you are changing any of the following files, a restart the ControlDaemon.

    The following must be changed on the Application Server.

    • DevicePackageSupport.xml

      • Any of the .pkg files in the custompackage/pkgxml directory

      • For Example: service controldaemon restart (UNIX)

      • For Example: restart from the services panel on Windows (GUI)

        With this release, the addev.order changes are supported only in the package directory, as such, this file is not supported from the custompackage, and must be modified (if needed) in its original package directory location.

  10. SEARCHORDER : By default, the software will look for the driver control/data files in the custompackage first, then look in the package directory second. It is possible (although not recommended), to alter the search order to ignore either the custompackage directory or the package directory altogether. This is accomplished by modifying the PACKAGEDIR_SEARCHORDER value in the infrastructures database.

    Permissible values for PACKAGEDIR_SEARCHORDER are listed in the following three steps.

  11. Value = 1: search custompackage directory first, then package directory. This is the default, and if the PACKAGEDIR_SEARCHORDER value is not present, the system will use this value to control the directory search selection.

  12. Value = 2: Ignore the custompackage directory, and use only the package directory to locate drivers and control/data files.

  13. Value = 3: Ignore the package directory, and use only the custompackage directory to locate drivers and control/data files.

  14. To alter the setting of the PACKAGEDIR_SEARCHORDER, use the following procedure on the application server. This SEARCHORDER change propagates to all device servers.

  15. Stop all daemons and services on application servers, and device servers, and complete the steps below on the application server.

    • Store the cflist to a text file that can be edited. For Example:

      . /etc/voyence.conf
      cd [Product directory]/cgi-bin
      . /cflist.cgi > out.txt
  16. Restart the Application and Device Server Services on all the servers.