Host Machine FQDN change in Policy Server

Products

• CA Single Sign-On
• SITEMINDER
• CA Single Sign On Agents (SiteMinder)
• CA Single Sign On Secure Proxy Server (SiteMinder)

Issue/Introduction

Running the Policy Server needs to change the FQDN of the Server.

What should be taken care of when modifying the FQDN?

The Policy Server FQDN will be modified as:

machine1.example.com

to

machine1.example.net

Resolution

Make sure:

• The new FQDN will be resolved by DNS and / or host file;
• All components should be able to resolve the new FQDN:
  
  Web Agent;
  OneView Monitor (Web Server should be able to reply to the new FQDN);
  AdminUI connection can also rely on the Policy Server FQDN, depending on how it is registered to the Policy Server, the name of the server when connecting to the AdminUI in the server field;
  Snmp services, check that services are still available;
  For Stores, this should not be a problem as long as the Policy Server acts as a client on the communication layer.