Adding a Repository Daemon to a secondary server.
search cancel

Adding a Repository Daemon to a secondary server.


Article ID: 54410


Updated On:


CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service CA Service Desk Manager CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager



This walkthrough shows how to set up the Repository Daemon on a secondary server using the command

Adding a Repository Daemon to a secondary server is useful for users to access Attachments on the secondary server/s that they have access to. Not all users will have, or should have, access to the repository daemon running on the primary server.


WARNING: Use caution as incorrect use of the pdm_edit procedure can permanently disable the Service Desk system. Backup the Service Desk file system on all Service Desk servers before implementing this procedure.

TIP: Check with pdm_status that the expected number of repository daemons exists before starting this procedure and output this to a file: pdm_status > pdm_status_<DATE HERE>.txt


In this example, there is an existing repository daemon on the primary server. The task shows adding a new repository daemon to the secondary server.

The primary server is "bso698-vm92" and the secondary server is "bso698-vm93."

  1. Switch to the $NX_ROOT/samples/pdmconf directory on the primary server, and enter the following command to start the pdm_edit utility:


    <Please see attached file for image>

    Figure 1

  2. Press Y, <Enter> if the operating system is Windows.

    <Please see attached file for image>

    Figure 2

  3. Read through the displayed warning message carefully and continue if it is okay to proceed.

    <Please see attached file for image>

    Figure 3

  4. The main menu is displayed as per below. Choose "Edit Repository Daemon."

    <Please see attached file for image>

    Figure 4

  5. You may see the Repository Daemon already configured on the primary server, as below. Press "A" to Add a new repository daemon and <Enter>.

    <Please see attached file for image>

    Figure 5

  6. Type the name of the target secondary server for the new repositary daemon after the prompt "Hostname[primary]:" in the following screenshot. ie Type "bso698-vm93" and <Enter>.

    <Please see attached file for image>

    Figure 6

  7. You may see a Repository Daemon configured on both the primary and secondary server, as here. Press Enter key to back to the main menu.

    The following screenshot shows that a secondary server repository daemon has been configured to "bso698-vm93".

    NOTE: The screenshot below may be confusing. The text "bso698-vm03 primary" indicates that there is a repository daemon on both servers "bso698-vm93" and on "primary". It does not mean that bso698-vm03 is a primary, rather, it is a list of all repository daemons.

    <Please see attached file for image>

    Figure 7

  8. Enter X to save and exit.

    This process creates a file named pdm_startup.rmt that stores your new configuration values.

  9. Read through the warning message and select a file to use as a template.

    <Please see attached file for image>

    Figure 8

  10. Follow the steps stated in CHECKLIST carefully to complete the configuration.

    TIP: Copy the screen output at this point in case the command window is accidentally closed.

    <Please see attached file for image>

    Figure 9

  11. Run pdm_status and confirm the Repository Daemon is running on both the primary and secondary servers.

    TIP: It is good to verify the pdm_status before beginning this procedure to confirm that the expected state of the setup exists.

    <Please see attached file for image>

    Figure 10

For more information please refer to the following technical document: TEC481388.


Release: CACMDB99000-11.1-CMDB


1558714010476000054410_sktwi1f5rjvs16t9o.gif get_app
1558714008559000054410_sktwi1f5rjvs16t9n.gif get_app
1558714006569000054410_sktwi1f5rjvs16t9m.gif get_app
1558714004577000054410_sktwi1f5rjvs16t9l.gif get_app
1558714002676000054410_sktwi1f5rjvs16t9k.gif get_app
1558714000818000054410_sktwi1f5rjvs16t9j.gif get_app
1558713998476000054410_sktwi1f5rjvs16t9i.gif get_app
1558713996509000054410_sktwi1f5rjvs16t9h.gif get_app
1558713994514000054410_sktwi1f5rjvs16t9g.gif get_app
1558713992332000054410_sktwi1f5rjvs16t9f.gif get_app