Changing the server IP address and host name

Complete the following steps as the root user on the Cloud APM server:

1. Stop all of the server components by entering the following command in the /usr/bin directory:

   
   apm stop_all

2. Start the kafka and server1 components by entering the following commands:

   apm start kafka
   apm start server1 

3. Change the IP address and host name of the server that is used to start the Cloud APM console. This is the address that users enter to start the console from their web browsers. Change to the install_dir/ccm directory and run the following command:

   configure_server_address.sh

   You are prompted for the following values:

   • Fully qualified domain name, for example: myserver.example.com.
   • Short host name
   • IP address

   Tip: The fully qualified domain name and short host name are resolved using DNS. If your system does not have good DNS resolution, enter the IP for all three values.
4. Update the server agent file names. The server agents include the Synthetic Events agent, the Transaction Events agent, and optionally, the Bluemix® Integration agent. Change to the install_dir/serveragents/bin directory and run the following command:

   update_config_files.sh

5. Change the Cloud APM server references on the local Db2® server to the new IP address and host name:
   1. Update the DB2SYSTEM registry variable for the local Db2 server to match the new host name of the Cloud APM server:

      
      source /home/db2apm/sqllib/db2profile
      db2set -g DB2SYSTEM=host_name

      where host_name is the new host name of the server.
   2. On your local Db2 server, modify the host name on the Cloud APM server by editing the /home/db2apm/sqllib/db2nodes.cfg file and replacing the old server host name with the new server host name.
   3. On your local Db2 server, update the Db2 administrator's configuration file by entering the following commands:

      
      su - db2apm -c 'db2 update admin cfg using DB2SYSTEM host_name'
      su - db2apm -c 'db2 update admin cfg using SMTP_SERVER host_name' 

      where host_name is the new host name of the server.
6. Verify that the server agents that were installed with the Cloud APM server are configured to use localhost to communicate with the server.
   Open the install_dir/serveragents/config/global.environment file and locate the IRA_ASF_SERVER_URL and IRA_API_DATA_BROKER_URL properties. Complete one of the following steps:

   • If the properties specify localhost in the URL string, no change is required.
   • If the properties contain the IP address of the Cloud APM server, which is likely if you configured the agents to communicate using HTTPS, change the IP addresses to localhost.
7. Restart the server components by entering the following command in the /usr/bin directory:

   
   apm restart_all

8. Override the host name of the Cloud APM server in the Central Configuration Services component.
   1. If you are not already logged in to the Cloud APM console, log in now.
      (See Starting the Cloud APM console.)
   2. Click System Configuration > Advanced Configuration and click Agent Central Configuration.
   3. In the Host Name Override field, enter the new IP address or fully qualified host name of the Cloud APM server.
   After you click Save, the new host name is updated in the Central Configuration Services component.
9. On the systems where your agents are installed, connect the agents to the new server IP address and host name.
   See Configuring agents to connect to a different server or to use HTTPS communication.
10. If you have reports packages for the Response Time Monitoring Agent and the WebSphere® Applications agent installed, you must reinstall the reports packages for both agents.
    For more information, see Installing reports. Restart the Tivoli Common Reporting server, complete the steps in the sub topics under Restarting Jazz for Service Management application servers.