This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Remedy Action Request System 9.1 ... Configuring after installation Configuring AR System servers

Changing a server name when using a duplicated or migrated environment

Best Practice

BMC recommends using the Renaming the AR System server utility to change the server name of BMC Remedy AR System server.

BMC Remedy AR System Server changing server name checklist

Update the Customization Comments column and check the tasks as you complete them.

Download checklist

This section describes the configuration procedures required to change the server name of a BMC Remedy Action Request System (BMC Remedy AR System) server when you upgrade from versions earlier than 9.0.

The steps involve updating one or more of the following items:

  • (Windows only) Registry information using regedit
  • Configuration files using a text editor
  • Form data using a BMC Remedy AR System client, such as a browser

Server-Name is the alias name by which an AR System server recognizes itself. You might need to change a Server-Name alias because:

Use caseDescription
Use case 1You are setting up a staging server (as part of the upgrade process) by installing all of the products first and then restoring the database from the production server. The database might contain references to the production server, which might not be applicable to the staging environment. In this case, you need to change only the form data.
Use case 2You are setting up a staging server (as part of the upgrade process) by restoring the database first and then installing the original BMC Remedy AR System ARServer version (this is called a Database-Only installation). In this case, you need to change only the form data.
Use case 3The Server name is changing due to a policy or host name change. In this case, you must change the Registry (on Windows), the configuration files, and the form data.

Note

The steps describe both Microsoft Windows and UNIX environments. In some cases (such as working with the Registry), the steps apply only to Windows.

The following section provides information about procedures you need to perform to change the server name of BMC Remedy Action Request components and applications. 


    The following table lists steps for renaming BMC Remedy AR System server if you are setting up a staging server by installing all the products first and then restoring the database from the production server.

     

    Sr.No

    Steps
    BMC Remedy AR System
    1 Update the Server field in the AR System Searches Preference form.
    2 Update the Server Login List field in the AR System User Preference form.
    3 Update the Server field in the Report form.
    4 Update the AR System Server Group Operation Ranking form.
    You must delete records from the servgrp_board table where the serverName column does not match the servers in the new server group.
    5 You must delete records from the ft_pending and ft_schedule tables that do not match the servers in the new server group.
    BMC Remedy Email Engine
    4 Update the Email Server Name/IP field in the AR System Email Mailbox Configuration form.
    BMC Remedy Web Services registry
    5 Update all server name occurrences of each record in the AR System Web Services Registry form.
    Help file paths
    6 Update all server name occurrences in the SHARE:Application_Properties form where the Property Name field has an entry of Help File Path.
    BMC Atrium Core
    7

    Atrium Integrator

    1. Update the Host field in the UDM:Config form.
    2. Update the Server Name and RAppPassword field in UDM:RAppPassword form.
    3. Remove all existing entries from the UDM:ExecutionInstance form.
    4. For the executed jobs, remove the old server entry from the UDM: PermissionInfo form.
    5. Change the server name in the Atrium Integrator console.
    6. Update the server name in Atrium Integrator Spoon.
    7. Update the new server name in Job scheduler.
    8. Delete all the schedules and then reschedule the jobs after restoring the database.
    8

    Update the ARServerName field in the BMC.CORE.CONFIG:BMC_FederatedDataInterface form.
    9

    Atrium Impact Simulator

    Update the charAISCellHost and iAISCellPort fields in the AIS:GlobalPreferences form.
    BMC Remedy IT Service Management

    10

    		 Update the Server field the AST:ARServerConnection form.
    11 Update the ARServerName field in the AST:ComplianceARBased_Advanced form.
    12 Update the ARServerName field in the BMC.CORE.CONFIG:BMC_FederatedDataInterface form.
    13 For Atrium Impact Simulator, update the charAISCellHost and iAISCellPort fields in the AIS:GlobalPreferences form.
    14 Update the Record Server field in the SYS:Escalation form.
    15 Update the URL field in the SYS:Attachments form.
    (If the out-of-box data for survey is modified by replacing the <arserver> or <midtierserver> placeholders with the host names, only then change these values to the correct server host name.)
    16 Update the Server field in the CAI:AppRegistry form.
    BMC Service Request Management
    17 Update the AppInstanceServer and SRServer fields in the SRM:AppInstanceBridge form. 
    18 Update the Mid Tier path field in the SYS:System Settings form.
    19 Update the Hostname field in the PDL:ApplicationSettings form.
    20

    Update the Server field in the SRS:CFGAdvancedInterface form
    BMC Service Level Management
    21 Update the Mid Tier field the SLM:ConfigPreferences form.
    Service Management Process Model
    22 Update the Host and Port fields in the SYS:Integration Management form.

    The following table lists steps for renaming BMC Remedy AR System server if you are setting up a staging server by restoring the database first and then installing the new BMC Remedy AR System environment.

    After you restore the database, clean up the Server Group tables by removing any records with old server names. Perform the following steps:

    1. Select serverName from the servgrp_board table.
    2. Select serverName from the servgrp_config table.
    3. Select serverName from the servgrp_resources table.
    4. Restart AR System Services. 


    Sr.No

    Steps
    BMC Remedy AR System
    1 Update the Server field in the AR System Searches Preference form.
    2 Update the Server Login List field in the AR System User Preference form.
    3 Update the Server field in the Report form.
    4
    • Update the AR System Server Group Operation Ranking form.
    • Replace all old server names with the new server names.
    • If the old environment had more servers than the new environment, remove any records that are left with the original server names
    5 You must delete records from the ft_pending and ft_schedule tables that do not match the servers in the new server group.
    BMC Remedy Email Engine
    4 Update the Email Server Name/IP field in the AR System Email Mailbox Configuration form.
    BMC Remedy Web Services registry
    5 Update all server name occurrences of each record in the AR System Web Services Registry form.
    Help file paths
    6  Update all server name occurrences in the SHARE:Application_Properties form where the Property Name field has an entry of Help File Path.
    BMC Atrium Core
    7

    Atrium Integrator

    1. Update the Host field in the UDM:Config form.
    2. Update the Server Name and RAppPassword field in UDM:RAppPassword form.
    3. Remove all existing entries from the UDM:ExecutionInstance form.
    4. For the executed jobs, remove the old server entry from the UDM: PermissionInfo form.
    5. Change the server name in the Atrium Integrator console.
    6. Update the server name in Atrium Integrator Spoon.
    7. Update the new server name in Job scheduler.
    8 

    Update the ARServerName field in the BMC.CORE.CONFIG:BMC_FederatedDataInterface form.
    9

    Atrium Impact Simulator

    Update the charAISCellHost and iAISCellPort fields in the AIS:GlobalPreferences form.
    BMC Remedy IT Service Management
    10 Update the Server field the AST:ARServerConnection form.
    11 Update the ARServerName field in the AST:ComplianceARBased_Advanced form.
    12 Update the Record Server field in the SYS:Escalation form.
    13 Update the URL field in the SYS:Attachments form.
    (If the out-of-box data for survey is modified by replacing the <arserver> or <midtierserver> placeholders with the host names, only then change these values to the correct server host name.)
    14 Update the Server field in the CAI:AppRegistry form.
    BMC Service Request Management
    15 Update the AppInstanceServer and SRServer fields in the SRM:AppInstanceBridgeform. 
    16  Update the Mid Tier path field in the SYS:System Settings form.
    17 Update the Hostname field in the PDL:ApplicationSettings form.
    18  Update the Server field in the Configure Advanced Interface Information form.
    BMC Service Level Management
    19 Update the Mid Tier field the SLM:Config Preferences form.
    Service Management Process Model
    20 Update the Host and Port fields in the SYS:Integration Management form.
    AR System Monitor
    21 Delete records with the incorrect Host Name in the AR System Monitor form.

    The following table lists steps for renaming BMC Remedy AR System server if the server name changed due to a policy or host name change.

     

    Sr.No

    Steps
    BMC Remedy AR System
    1 Update the ar.conf file.
    2 Update the -x <newServerName> string in the armonitor.cfg file.
    3 Update the server_name field in the pluginsvr_config.xml file.
    4 Update the Windows Registry.
    5 Update the UNIX environments.
    6 Update the Server field in the AR System Searches Preference form.
    7 Update the Server Login List field in the AR System User Preference form.
    8 Update the Server field in the Report form.
    9

    Update the AR System Server Group Operation Ranking form.
    You must delete records from the servgrp_board table where the serverName column does not match the servers in the new server group.
    10 You must delete records from the ft_pending and ft_schedule tables that do not match the servers in the new server group.
    BMC Remedy Mid Tier
    11 Using the BMC Remedy Mid Tier Configuration Tool, update the AR Server Settings, General Settings, and Report Settings.
    12 Clean up files in BMC Remedy Mid Tier.
    BMC Remedy Email Engine
    13 Update oldServerName with newServerName in the EmailDaemon.properties email server configuration file.
    14 Update the Email Server Name/IP field in the AR System Email Mailbox Configuration form.
    BMC Remedy Flashboards
    15 Update the ARServerName property in the server.conf file in the Flashboards folder.
    BMC Remedy Web Services registry
    16 Update all server name occurrences of each record in the AR System Web Services Registry form.
    Help file paths
    17 Update all server name occurrences in the SHARE:Application_Properties form where the Property Name field has an entry of Help File Path.
    BMC Atrium Core
    18

    Atrium Integrator

    1. Update the Host field in the UDM:Config form.
    2. Update the Server Name and RAppPassword field in UDM:RAppPassword form.
    3. Remove all existing entries from the UDM:ExecutionInstanceform.
    4. For the executed jobs, remove the old server entry from the UDM: PermissionInfo form.
    5. Change the server name in the Atrium Integrator console.
    6. Update the server name in Atrium Integrator Spoon.
    7. Update the new server name in Job scheduler.
    19 Update the ARServerName field in the BMC.CORE.CONFIG:BMC_FederatedDataInterface form.
    20

    Atrium Impact Simulator

    Update the charAISCellHost and iAISCellPort fields in the AIS:GlobalPreferences form.
    BMC Remedy IT Service Management
    21 Update the Server field the AST:ARServerConnection form.
    22 Update the ARServerName field in the AST:ComplianceARBased_Advanced form.
    23 Update the ARServerName field in the BMC.CORE.CONFIG:BMC_FederatedDataInterface form.
    24 For Atrium Impact Simulator, update the charAISCellHost and iAISCellPort fields in the AIS:GlobalPreferences form.
    25 Update the Record Server field in the SYS:Escalation form.
    26 Update the URL field in the SYS:Attachments form.
    (If the out-of-box data for survey is modified by replacing the <arserver> or <midtierserver> placeholders with the host names, only then change these values to the correct server host name.)
    27 Update the Server field in the CAI:AppRegistry form.
    BMC Service Request Management
    28 Update the AppInstanceServer and SRServer fields in the SRM:AppInstanceBridge form.  
    29 Update the Mid Tier path field in the SYS:Application Settings form.
    30 Update the Hostname field in the PDL:ApplicationSettings form.
    31 Update the Server field in the Configure Advanced Interface Information form.
    BMC Service Level Management
    32 Update the Mid Tier field the SLM:Config Preferences form.
    Service Management Process Model
    33 Update the Host and Port fields in the SYS:Integration Management form.

    Related topics

    Setting up systems for a staged upgrade  in BMC Remedy ITSM Deployment documentation.

    Was this page helpful? Yes No Submitting... Thank you
    Last modified by Anagha Deshpande on Jul 27, 2020
    names servers environment configuration rename server_name server replace databases update applications registry atrium_integration_engine email_engine occurrences updating changing migrated duplicate checklist staging udm_rapppassword ar_conf pluginsvr_config armonitor search preference unix windows_registry form report aiexfer udm_config _interface_information advanced_interface_information config_preferences mid-tier path appregistry escalation permissioninfo globalpreferences sys_attachments user_preferences configuration_tool server_settings general_settings report_settings emaildaemon email_mailbox_configuration server_config flashboards help_file atrium_core aie atrium_integrator atrium_integrator_spoon best_practices

    Comments

    1. Tony Worthington

      Hello -

      Finding a contradiction on whether renaming a server in the lower level environments when using the accelerated method is required.

      This link https://docs.bmc.com/docs/display/public/brid91/Setting+up+upgrade+servers says 

      Also, after you change the host name, follow the process outlined in Changing a server name when using a duplicated or migrated environment   in the BMC Remedy AR System documentation. 

      However, this link https://docs.bmc.com/docs/display/public/brid91/Upgrading+from+a+version+7.6.04+or+8.0.xx#Upgradingfromaversion7.6.04or8.0.xx-Setuptheupgradedevelopmentserver says

      Tip

      To avoid the server rename activity, you can keep the server name same as the production server. Keep the same name on the upgrade development, QA, and staging production server.

       

      Which is it?


      Mar 04, 2016 08:47
      1. Prachi Kalyani

        Hello Tony,

        We will verify this and update the topics soon.

        Thanks,

        Prachi

        Mar 07, 2016 10:47
      1. Amit Durgapal

         Hello Tony,

        Customers can have their own reasons to change the server name of the machine on which they back up or restore their database while upgrading using accelerated method. If situations require changing the server name, you need to follow the procedures for renaming the BMC Remedy AR System Server.

        Regards,

        Amit

        Mar 08, 2016 03:50
    2. Igor Rabatic

      Hi,

      Use Case 3, Step 28 - description should state SRM:Application Settings instead of SYS:System Settings. The link does redirect to the correct instructions though.

      Jun 29, 2016 03:48
      1. Prachi Kalyani

        Thank you for bringing this to our notice. I have made the change.

        Thanks,

        Prachi

        Jul 18, 2016 03:35
    3. Igor Rabatic

      Me again (smile) Use Case 3 Step 30 - SRS:CFGAdvancedInterface

      Jun 29, 2016 03:52
    4. Louise Van hine

      You missed one:  AR System Configuration Component.  I found this when I saw that the CMDB:Administration console contained the old server name.  This form needs to be added to the forms list.

      Jun 29, 2016 08:12
      1. Prachi Kalyani

        Hello Louise,

        I will verify this and update the topic soon.

        Thanks,

        Prachi

        Jul 18, 2016 03:50
        1. Jerome Razen

          Hello

          Louise is right: It seems "AR System Configuration Component" and "AR System Configuration Setting" should be part of the to-do list above. They're part of the Centralized Configuration, for which there's a backup/restore feature, as described here.

          Also, I'd add the following step to the list above:

          "Delete the contents of the DB-table SERVGRP_BOARD before the initial start of the ARServer."

          This table holds servergroup information. In our case it held information from both the old and the new environment, even though we had modified the entries in the servergroup ranking form. This led to servergroup issues. Truncating the table and restarting the ARServer solved the issue.

          Thanks,

          Jérôme

           

          Nov 02, 2016 07:45
      1. Anagha Deshpande

        Hello Louise,

        Apologies for the late response.

        The forms are not mentioned because we edit the ar.cgf file via a Centralized Configuration interface. The AR System server takes care of updating the component names.

        Regards,

        Anagha

        Aug 01, 2018 04:45
    5. Wendy Stubenhofer

      Use Case 1, step 22 appears to have a typo.  It currently says SLM:Config Preferences but it should be SLM:ConfigPreferences without the space.

      Jul 15, 2016 08:31
      1. Prachi Kalyani

        Hello Wendy,

        Thank you for bringing this to our notice. I have made the change.

        Thanks,

        Prachi

        Jul 17, 2016 11:32
    6. Tosho Zaprianov

      Hello,

      Can you provide information about the server entries in AR System Configuration Component, AR System Configuration Setting and AR System Configuration Component-Setting Mapping.

      I've been struggling to find a complete guide how to rename the server references. There are several pages in the BMC Docs site and each one says something different.

       

      Thanks,

      Tosho

      Nov 16, 2016 06:30
      1. Anagha Deshpande

        Hello Tosho,


        Apologies for the late response.

        The forms are not mentioned because we edit the ar.cgf file via a Centralized Configuration interface. The AR System server takes care of updating the component names.

        Refer to Renaming the AR System server topic for information about renaming the AR System Server.

        Regards,

        Anagha

        Aug 01, 2018 04:48
    7. Maria Blajevitch

      Hello, SmartIT/Mongo DB cloning procedure is missing here.

      Maria

      Jan 03, 2017 04:04
      1. Anagha Deshpande

        Hello Maria,

        Sorry for responding late. I will check with SME and will inform you.

        Regards,

        Anagha

        Jun 15, 2017 11:20
        1. Rick Westbrock

          Anagha do you have any updates yet since it has been three months since your last reply?

          Sep 20, 2017 04:12
    8. Jesus Arias camacho

      What about the procedure to MyIT / Smart IT server and Mongo databases???

      Oct 27, 2017 02:16
      1. Anagha Deshpande

        Hello Jesus,

        Thanks for your query. I will check this with MyIT and Smart IT SMEs and will write back to you.

        Regards,

        Anagha

        Oct 31, 2017 12:59
    9. Stefan Hall

      step 18 - wrong title, SYS:System Settings has no MidTier path

      Feb 27, 2018 06:30
    10. Stefan Hall

      Step 13 - delete it, AIS:GlobalPreferences no longer exists

      Feb 27, 2018 06:35
      1. Stefan Hall

        step 9 - same, useless if form no longer exists

        Feb 27, 2018 06:37
    11. Stefan Hall

      step 8 and 12 are useless together, same entries

      Feb 27, 2018 06:39
    12. Stefan Hall

      What about SRD:STAGE:MasterDataMappingList for SRM?

      Feb 27, 2018 08:25
    13. Stefan Hall

      and my last vote today ;) I miss RKM and SLM information

      Feb 27, 2018 09:05
      1. Anagha Deshpande

        Hello Stefan,

        Thank you for your feedback. I will update the topic.

        Regards,

        Anagha

        Feb 27, 2018 09:26
        1. Anagha Deshpande

          Hello Stefan,

          Apologies for the late response.

          BMC recommends using the Renaming the AR System server utility to change the server name of BMC Remedy AR System server.

          Please refer to the above documentation.

          Regards,

          Anagha

          Aug 01, 2018 04:51
    14. Foued Ben hadj ali

      Hi i believe there is a step missing, i just followed the above document after copying prod db to dev db but at the end i wasn't able to run DMT in dev. There was an error saying "Check UDM Config" as it couldn't find prod server name in udm:config.

      The step missing is, from my point of view, to delete at the db level an entry in the table "servgrp_board", once i deleted the entry with prod server name i was able to connect to dmt in dev.

      Regards

      Aug 04, 2018 03:57
      1. Anagha Deshpande

        Hello Foued Ben hadj ali,

        Apologies for the inconvenience. I will check your query with the SME.

        Regards,

        Anagha 

        Aug 05, 2018 11:44
        1. Anagha Deshpande

          Hello Foued Ben hadj ali,

          Apologies for the delayed response.

          We have added the step to delete records from the servgrp_board table.

          Regards,

          Anagha


          May 22, 2019 03:53
    15. Jay Parker

      Step 20 Form is called SRS:CFGAdvancedInterface not Configure Advanced Interface Information

      Nov 18, 2019 03:35
      1. Anagha Deshpande

        Hello Jay,

        Thanks for your feedback on the documentation.

        We are working on your query.

        Regards,

        Anagha

        Nov 22, 2019 03:57
        1. Anagha Deshpande

          Hello Jay,

          Apologies for the delayed response. 

          We have updated the topic.

          Regards,

          Anagha

          Jun 17, 2020 03:30
    16. Brian Gillock

      Minor edit: Step 7 substep 3. UDM:ExecutionInstanceform. Should be a space between UDM:ExecutionInstance and form. Thanks.

      May 18, 2020 09:31
      1. Anagha Deshpande

        Hello Brian,

        Thanks for bringing this to our notice.

        We have corrected the form name.

        Regards,

        Anagha

        May 29, 2020 04:27
    Monitoring service operations
    Configuring the AR System server to rename the server
    © Copyright 1991-2020 BMC Software, Inc. © Copyright 1991-2020 BladeLogic, Inc.
    Legal notices

    Powered by Atlassian Confluence and Scroll Viewport

    © Copyright 2005-2020 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.