Changing a server name when using a duplicated or migrated environment
Best Practice
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 case | Description |
---|---|
Use case 1 | You 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 2 | You 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 3 | The 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.
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:
- Select serverName from the
servgrp_board
table. - Select serverName from the
servgrp_config
table. - Select serverName from the
servgrp_resources
table. - Restart AR System Services.
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.
Related topics
Setting up systems for a staged upgrade
in BMC Remedy ITSM Deployment documentation.
Comments
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
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
Which is it?
Hello Tony,
We will verify this and update the topics soon.
Thanks,
Prachi
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
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.
Thank you for bringing this to our notice. I have made the change.
Thanks,
Prachi
Me again
Use Case 3 Step 30 - SRS:CFGAdvancedInterface
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.
Hello Louise,
I will verify this and update the topic soon.
Thanks,
Prachi
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
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
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.
Hello Wendy,
Thank you for bringing this to our notice. I have made the change.
Thanks,
Prachi
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
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
Hello, SmartIT/Mongo DB cloning procedure is missing here.
Maria
Hello Maria,
Sorry for responding late. I will check with SME and will inform you.
Regards,
Anagha
Anagha do you have any updates yet since it has been three months since your last reply?
What about the procedure to MyIT / Smart IT server and Mongo databases???
Hello Jesus,
Thanks for your query. I will check this with MyIT and Smart IT SMEs and will write back to you.
Regards,
Anagha
step 18 - wrong title, SYS:System Settings has no MidTier path
Step 13 - delete it, AIS:GlobalPreferences no longer exists
step 9 - same, useless if form no longer exists
step 8 and 12 are useless together, same entries
What about SRD:STAGE:MasterDataMappingList for SRM?
and my last vote today ;) I miss RKM and SLM information
Hello Stefan,
Thank you for your feedback. I will update the topic.
Regards,
Anagha
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
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
Hello Foued Ben hadj ali,
Apologies for the inconvenience. I will check your query with the SME.
Regards,
Anagha
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
Step 20 Form is called SRS:CFGAdvancedInterface not Configure Advanced Interface Information
Hello Jay,
Thanks for your feedback on the documentation.
We are working on your query.
Regards,
Anagha
Hello Jay,
Apologies for the delayed response.
We have updated the topic.
Regards,
Anagha
Minor edit: Step 7 substep 3. UDM:ExecutionInstanceform. Should be a space between UDM:ExecutionInstance and form. Thanks.
Hello Brian,
Thanks for bringing this to our notice.
We have corrected the form name.
Regards,
Anagha