Adding a Repository Daemon to a secondary server.

Products

• 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

Issue/Introduction

Description:

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

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.

Solution:

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

EXAMPLE

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:
   
   pdm_perl pdm_edit.pl
   
   

   <Please see attached file for image>

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

   <Please see attached file for image>

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

   <Please see attached file for image>

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

   <Please see attached file for image>

   
   
   
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>

   
   
   
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>

   
   
   
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>

   
   
   
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>

   
   
   
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>

    
    
    
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>

    

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

Environment

Release: CACMDB99000-11.1-CMDB
Component: