Changing a Server's Hostname

Changing a server's hostname is an uncommon task but may be necessary for the following reasons:

Company branding
Domain change
Restoring of a primary Unified Assurance server from a redundant backup
Repurposing servers for development, staging or production purposes

Best Practices

If HostFQDN was and should continue to be the same as web FQDN, see Changing the WebFQDN, using the new HostFQDN wherever it mentions the new WebFQDN.
Redundancy Wizard requires all MySQL data files to be in the same directory. Symbolic links or data directory mounts spanning multiple drive partitions are not supported and manual resynchronization of replication is required. Contact Oracle Support for guidance before changing the HostFQDN or WebFQDN if you have a non-standard database installation.

Prerequisites

Before changing the HostFQDN or WebFQDN, update DNS information, flush caches, and wait for TTL.

Changing the HostFQDN

Repeat the following on all servers:
1. Stop all Unified Assurance applications on all servers using broker control and init scripts:
```
cd $A1BASEDIR/
bin/BrokerControl --batch stopall
service assure1-web stop
service assure1-broker stop
service assure1-db stop
```
2. Update system host and domain information with new HostFQDN in the following Linux core files:
  - /etc/sysconfig/network
  - /etc/resolv.conf
3. If the HostFQDN of the primary or backup presentation server is changing:
  1. On each server partner, update the following Unison configuration file with the new HostFQDN of the partner:
    - $A1BASEDIR/etc/unison/Packages.prf
    - $A1BASEDIR/etc/unison/Repos.prf
  2. On server of the HostFQDN that is changing, regenerate SSL Host certificate:
```
$A1BASEDIR/bin/CreateSSLCertificate --Type Host --CN <HostFQDN> --Force 
```
On the primary presentation server:
1. Regenerate the Web SSL certificate:
```
$A1BASEDIR/bin/CreateSSLCertificate --Type Web --CN <WebFQDN> --AltCN <PriPres HostFQDN> [--AltCN <BakPres HostFQDN>] --Force
```
2. Replace any instances of the old HostFQDN in the following files:
  - $A1BASEDIR/etc/httpd.conf
    
    For example:
```
<VirtualHost _default_:443>
    DocumentRoot /opt/assure1/www
    ServerName   [WEBFQDN]:443
    ServerAlias  [NEW HOSTFQDN]:443
```
  - $A1BASEDIR/etc/Assure1.conf
3. Copy $A1BASEDIR/etc/Assure1.conf from the primary presentation server to all other servers.
4. Copy the following files from the primary presentation server to any external or redundant presentation servers:
  - $A1BASEDIR/etc/ssl/Web.crt.pem
  - $A1BASEDIR/etc/ssl/Web.key.pem

Repeat the following on all internal and external presentation servers:

Start Apache:
```
service assure1-web start
```
Start the Database:
```
service assure1-db start
```
Connect to the primary Assure1 schema.

Update the Servers record:

UPDATE Servers SET ServerHostFQDN = "<NEW-HOST-FQDN>" WHERE ServerHostFQDN = "<OLD-HOST-FQDN>";

Update the Devices records:

UPDATE Devices SET DNSName = "<NEW-HOST-FQDN>" WHERE DNSName = "<OLD-HOST-FQDN>";
UPDATE Devices SET CustomName = REPLACE(CustomName, "<OLD-HOST-FQDN>", "<NEW-HOST-FQDN>") WHERE DNSName = "<NEW-HOST-FQDN>";

Update the CoreDatabases records:

UPDATE CoreDatabases SET DBHost = "<NEW-HOST-FQDN>" WHERE DBHost = "<OLD-HOST-FQDN>";
UPDATE CoreDatabases SET DatabaseName = REPLACE(DatabaseName, "<OLD-HOST-FQDN>", "<NEW-HOST-FQDN>") WHERE DBHost = "<NEW-HOST-FQDN>";

Update application configurations of type Host or DSN:

UPDATE BrokerComponentConfig 
    SET BrokerComponentConfigValue = REPLACE(BrokerComponentConfigValue, "<OLD-HOST-FQDN>", "<NEW-HOST-FQDN>") 
WHERE BrokerComponentConfigTypeID IN (8, 19);

Start the broker:
```
service assure1-broker start
```

On the primary presentation server:
1. Log in to Unified Assurance user interface.
2. From the Configuration menu, select Notifications, then select Profiles.
3. Replace the old HostFQDN with the new one in all Notification Profiles.
On presentation and database servers where the HostName changed, run Redundancy Wizard with the SyncData option as the root user:
```
cd $A1BASEDIR/bin/redundancy/
./RedundancyWizard --SyncData
```

Changing the WebFQDN

Repeat the following on all servers:
1. Stop all Unified Assurance applications on all servers using broker control and init scripts.
```
cd $A1BASEDIR/
bin/BrokerControl --batch stopall
service assure1-web stop
service assure1-broker stop
service assure1-db stop
```
2. Update system host and domain information with new HostFQDN in the following Linux core files:
  - /etc/sysconfig/network
  - /etc/resolv.conf
On the primary presentation server:
1. Regenerate the SSL certificate.
```
 /opt/assure1/bin/CreateSSLCertificate --Type Web --CN <WebFQDN> --AltCN <PriPres HostFQDN> [--AltCN <BakPres HostFQDN>] --Force
```
2. Replace any instances of the old WebFQDN in the $A1BASEDIR/etc/httpd.conf file, except in ServerAlias under VirtualHost, which should remain HostFQDN.
```
<VirtualHost _default_:443>
  DocumentRoot /opt/assure1/www
  ServerName   [NEW WebFQDN]:443
  ServerAlias  [HostFQDN]:443
```
3. Copy the following files from the primary presentation server to any external or redundant presentation servers:
  - $A1BASEDIR/etc/ssl/Web.crt.pem
  - $A1BASEDIR/etc/ssl/Web.key.pem

Repeat the following on all internal and external presentation servers:

Start Apache.
```
service assure1-web start
```
Start the database:
```
service assure1-db start
```
Connect to the primary Assure1 schema.

If the HostFQDN should be the same as the new WebFQDN, update the ServerHostFQDN record:

UPDATE Servers SET ServerHostFQDN = "<NEW-WEB-FQDN>" WHERE ServerHostFQDN = "<OLD-WEB-FQDN>";

Update the Servers record:

UPDATE Servers SET WebFQDN = "<NEW-WEB-FQDN>" WHERE WebFQDN = "<OLD-WEB-FQDN>";

Update the Devices record:

UPDATE Devices SET DNSName = "<NEW-WEB-FQDN>" WHERE DNSName = "<OLD-WEB-FQDN>";
UPDATE Devices SET CustomName = REPLACE(CustomName, "<OLD-WEB-FQDN>", "<NEW-WEB-FQDN>") WHERE DNSName = "<NEW-WEB-FQDN>";

Update the CoreDatabases record:

UPDATE CoreDatabases SET DBHost = "<NEW-WEB-FQDN>" WHERE DBHost = "<OLD-WEB-FQDN>";

Update any application configurations of type Host or DSN matching old FQDN:

UPDATE BrokerComponentConfig 
   SET BrokerComponentConfigValue = REPLACE(BrokerComponentConfigValue, "<OLD-WEB-FQDN>", "<NEW-WEB-FQDN>") 
 WHERE BrokerComponentConfigTypeID IN (8, 19);

Repeat the following on all servers:

Update the rules checkout paths to point to the new WebFQDN. Not all checkout directories are used on a database or collection server.

for CHECKOUT in config core diagrams files
do
  if [ -d /opt/assure1/var/checkouts/$CHECKOUT ] ; then
      cd /opt/assure1/var/checkouts/$CHECKOUT &&  /opt/assure1/vendor/svn/bin/svn --config-dir /opt/assure1/etc/svn relocate https://<NEW-WEB-FQDN>/repos/$CHECKOUT/
  fi
done

Start the broker.
```
service assure1-broker start
```

On the primary presentation server:
1. Log in to Unified Assurance user interface.
2. From the Configuration menu, select Notifications, then select Profiles.
3. Replace the old WebFQDN with the new one in all Notification Profiles.
On presentation and database servers where WebFQDN was changed, if HostFQDN is the same as WebFQDN, run Redundancy Wizard with the SyncData option as the root user:
```
cd $A1BASEDIR/bin/redundancy/
./RedundancyWizard --SyncData
```

Title and Copyright Information

Implementation Guide

G10620-01