Sei sulla pagina 1di 4

10/15/2014

Changing a server name when using a duplicated or migrated environment - BMC Remedy Action Request System 8.1 - BMC Documentation
Support Login

Solutions & Services

BMC Remedy Action 8.1

About BMC

Products

Partners

Worldwide

Support

Education

Search all online product documentation

Communities

Login

Changing a server name when using a duplicated or migrated environment


Added by Lisa Greene, last edited by Hemant Baliwala on Aug 27, 2014

This section describes the configuration procedures required to change the server name of a BMC Remedy Action Request System (BMC Remedy AR System) server. 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 new BMC Remedy AR System
environment (this is called an accelerated 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.

Use
case
4

You are moving the server into a server group and using a new Server-Name alias. 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 sever name of BMC Remedy Action Request components and applications.

Use case 1

Use case 2

Use case 3

Use case 4

The following table lists steps for renaming BMC Remedy AR system sever 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.

Update the Server Login List field in the AR System User Preference form.

Update the Server field in the Report form.

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 occurences of each record in the AR System Web Services Registry form.

Help file paths


6

Update all server name occurences in the SHARE:Application_Properties form where the Property Name field has an entry of Help File Path.

https://docs.bmc.com/docs/display/public/ars81/Changing+a+server+name+when+using+a+duplicated+or+migrated+environment

1/4

10/15/2014

Changing a server name when using a duplicated or migrated environment - BMC Remedy Action Request System 8.1 - BMC Documentation

BMC Atrium Core


7

Atrium Integration Engine


1. Update the server name in the Help File path from the BMC Atrium Integration Engine Console. You can also reset user name and passowrd if
changed.
2. Run REPAIoption for aiexfer.

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.
8. Delete all the schedules and then reschedule the jobs after restoring the database.

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

10

Atrium Impact Simulator


Update the charAISCellHost and iAISCellPort fields in the AIS:GlobalPreferences form.

BMC Remedy IT Service Management


11

Update the Server field the AST:ARServerConnection form.

12

Update the ARServerName field in the AST:ComplianceARBased_Advanced form.

13

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

14

For Atrium Impact Simulator, update the charAISCellHost and iAISCellPort fields in the AIS:GlobalPreferences form.

15

Update the Record Server field in the SYS:Escalation form.

16

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.)

17

Update the Server field in the CAI:AppRegistry form.

BMC Service Request Management


18

Update the AppInstanceServer and SRServer fields in the SRM:AppInstanceBridgeform.

19

Update the Mid Tier path field in the SYS:System Settings form.

20

Update the Hostname field in the PDL:ApplicationSettings form.

21

Update the Server field in the Configure Advanced Interface Informantion form.

BMC Service Level Management


22

Update the Mid Tier field the SLM:Config Preferences form.

Service Management Process Model


23

Update the Host and Port fields in the SYS:Integration Management form.

Related topics
Duplicating the production server database for upgrades with overlays
Duplicating the production server database for upgrades without overlays
Your Rating:
Results:
1 rates
John Stamps likes this.

Labels

https://docs.bmc.com/docs/display/public/ars81/Changing+a+server+name+when+using+a+duplicated+or+migrated+environment

2/4

10/15/2014

Changing a server name when using a duplicated or migrated environment - BMC Remedy Action Request System 8.1 - BMC Documentation
names

environment

configuration

servers

11 Child Pages
Configuring the AR System server to rename the server
Updating the server name in application forms to rename the server
Configuring the BMC Remedy Mid Tier to rename the server
Configuring the BMC Remedy Email Engine to rename the server
Configuring the BMC Remedy Flashboards server to rename the server
Configuring the BMC Remedy AR System Web Services registry to rename the server
Updating help file paths to rename the server
Configuring BMC Atrium Integration Engine to rename the server
Configuring BMC Remedy IT Service Management to rename the server
Configuring BMC Service Request Management to rename the server
Configuring Atrium Integrator to rename the servers

Yann Baum gartner

Jul 05, 2013

Using the Developper Studio you also need to change the WSDL URLs of the Web Services.

Saverio Aversa

Jul 09, 2013

Great Jose Pedro!!!!

Hem ant Baliw ala

Jul 09, 2013

Ashley Hall

Jul 09, 2013

The 'Update Checklist' download doesn't seem to have a file attached to the download link? I click the link, nothing happens.

Hem ant Baliw ala

Jul 09, 2013

Hi Ashley,
I have fixed the issue. You can now download the checklist.
Thanks,
Hemant

Ronald Kuschm ider

Aug 26, 2014

You need to add something about deleting the records from ft_pending and deleting entries from ft_schedule that do not match the servers in the new
server group. This is ion the case of migrating to a new server group. Then you need to reindex fts.

Hem ant Baliw ala

Aug 27, 2014

Hi Ronald,
Thanks for your comment.
I have updated use case 3 and 4.
Thanks,
Hemant

Log in or register to comment.

https://docs.bmc.com/docs/display/public/ars81/Changing+a+server+name+when+using+a+duplicated+or+migrated+environment

3/4

10/15/2014

Changing a server name when using a duplicated or migrated environment - BMC Remedy Action Request System 8.1 - BMC Documentation

Copyright 1991 2014 BMC Softw are, Inc. Copyright 1991 - 2014 BladeLogic, Inc. BladeLogic and the BladeLogic logo are trademarks or registered trademarks of BladeLogic, Inc. in the U.S. and/or
certain other countries. BMC Softw are Confidential. BladeLogic Confidential. Legal notices
Click here for the provisions described in the BMC License Agreement and Order related to third party products or technologies included in the BMC product.

Company

Resources

Social

About BMC

Leadership
Team

Communities Analyst
Reports

Facebook

News

Careers

BMCtv Videos

Events

Contact

Success
Stories

Legal

Corporate
Quality

Reference
Books

Manage Your
Preferences

Connections

Google+

Twitter

YouTube

LinkedIn

Support

Partners

Worldwide BMC
Blogs

Slideshare

Copyright 2005-2014 BMC Software, Inc. Use of this site signifies your acceptance of BMC's
Terms of Use, Privacy Policy and Cookie Notice. BMC, BMC Software, the BMC logos, and
other BMC marks are trademarks or registered trademarks of BMC Software, Inc. in the U.S.
and/or certain other countries.
Manage Cookies

https://docs.bmc.com/docs/display/public/ars81/Changing+a+server+name+when+using+a+duplicated+or+migrated+environment

4/4

Potrebbero piacerti anche