Creating a Document Repository on a Secondary Server.

Document ID : KB000053156
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

A Document Repository is used to store Service Desk Attachments.

By default, the repositories are located on the primary server. No extra configuration is required to make them work. However, it may be desirable to store a repository on a secondary server for better efficiency or security.

To place the repository on a remote server requires installing a secondary server with a running repository daemon (rep_daemon) according to the following instructions.

Solution:

Prerequisites for the Remote Document Repository Server
The system requirements for remote Document Repository server are:

  • Secondary server with repository daemon running, as the physical location of the remote document repository.
  • Tomcat and Upload Servlet.

Instructions to Configure Repository Daemon on a Secondary Server
Warning: Incorrect use of the pdm_edit process can disable your system. Take a file system backup of all files that are replaced during the pdm_edit process prior to starting. This includes but is not limited to the /pdmconf directory, /www directory and NX.ENV files. A full list of files that may be updated by the process is produced upon exiting the pdm_edit process. These files require manual copying before they take effect, so there is time at this point to take a backup of the affected areas.

  1. Start the pdm_edit process.
    From a command prompt on the primary server change to the Service Desk home directory and then the samples/pdmconf directory:

    nxcd
    cd samples/pdmconf
    pdm_perl pdm_edit.pl

    Answer the next two questions to come to the main pdm_edit menu. Both answers are typically "Yes" for a Windows system.

  2. Chose "r" to "Edit (R)epository Daemon."

    1. Edit (O)bject servers.
    2. Edit WEB (D)irectors.
    3. Edit (W)EB engines.
    4. Edit (T)NG Converters (NT_ONLY).
    5. Edit U(N)I Converters (UNIX_ONLY).
    6. Move Login (U)ser Validation.
    7. Edit (L)DAP Virtual DB.
    8. Edit (R)epository Daemon.
    9. Edit (C)hange Impact Analyzer.
    10. Edit (A)liases.
    11. Edit (K)nowledge Daemons.
    12. Help.
    13. Views.
    14. Quit NO SAVE.
    15. Save.
    16. Save and quit.

      Please enter selection: r

      Repository Daemons: primary

      (A)dd, (D)elete, <CR> return

  3. (A)dd the name of the secondary server and <Enter> to return to the main menu.
    Note: The name of the secondary server must match the NX_LOCAL_HOST on the secondary server and should maintain the same case.

  4. Choose "X" to Save and Exit. This produces a saved file called pdm_startup.rmt file.
    This will be the replacement for $NX_ROOT/pdmconf/pdm_startup.tpl.
    Note: All editing so far has taken place in the $NX_ROOT/pdmconf/samples directory. The live directory is just $NX_ROOT/pdmconf.
    Take a copy of the instructions produced at this point and take any backups required if not already done.

  5. Rename the current $NX_ROOT/pdmconf/pdm_startup.tpl file.

  6. Copy the replacement $NX_ROOT/samples/pdm_startup.rmt file to $NX_ROOT/pdmconf/pdm_startup.tpl.

  7. Start the Secondary Server, which starts the proctor on the secondary server.
    Note: On Windows NT the proctor is a service and on Linux it is pdm_proctor_nxd.

  8. Start the Primary Server and use pdm_status or slstat to see if the new repository daemon appears.

    pdm_status | find "rep"
    slstat | find "rep"

    Sample slstat output:
    rep_daemon:My2ndSrv 44 47 Mon Mar 02 15:49:04 2009

  9. Log in as a Service Desk Administrator and change the Server Name and the Upload path to point to the remote machine where the new repository daemon is running. Administration, Attachments Library, Repositories, right-click Repository, Edit.

  10. Log into the secondary server and test attachments against this new/updated repository.

See also the Service Desk r11 and r12 Administration Guides.