Guest

Cisco Unified E-Mail Interaction Manager

CIM Version 9 Hostname Change FAQ

CIM Version 9 Hostname Change FAQ

Document ID: 116520

Updated: Sep 27, 2013

Contributed by Maria Jose Mendez Vazquez, Cisco TAC Engineer.

   Print

Introduction

This document describes how to change the hostname on Cisco Interaction Manager (CIM) Version 9.

How do you change the hostname on CIM Version 9?

If the hostname is changed for any servers on CIM Version 9, you must verify that the proper changes to the database and file system entries are made.

Database Entries

  1. This query shows the entries that you must modify in the egpl_config_property table on the active database. Replace the old hostname with the new hostname in these entries:

      select * from EGPL_CONFIG_PROPERTY where
       NAME in ('archive.db.server.1'
    , 'discoveryaddress'
    ,'DSMController.hostName'
    ,'jmsserver.url'
    ,'Event.log.remote.file.dir'
    ,'Event.log .thread.socket.hostname' ;
    ,'Task.Attachment.WebTemp'
    ,'weblogic.server.port'
    ,'webtemp.webdir'
    ,'iks.server.url'
    ,'replication.url');
  2. This query shows the entries that you must modify in the egpl_dsm_host table on the master database. Replace the old hostname with the new hostname in these entries. If a split-setup is used, where the database server is on a different machine, do not modify the entries for the database servers. The egpl_dsm_host entries are also referenced by other monitoring tables, so you must modify those as well.

    SELECT * FROM EGPL_DSM_HOST;
    SELECT * FROM EGPL_DSM_HOST_MONITOR;
    SELECT * FROM EGPL_DSM_INSTANCE_MONITOR;
    SELECT * FROM EGPL_DSM_PROCESS_MONITOR

File System Entries

These files contain the old hostname, which you must replace with the new host name manually:

  • In the eService > bin > platform > windows startup files:

    • egainstart.bat - On the application, messaging, and services servers.
    • egainstop.bat - On the application, messaging, and services servers.
    • setenv_<host name>.bat - On the file server. You must also modify the name of this file with the new hostname.
    • setenv_jms.bat - On the file server.
  • On the web server, these files contain the hostname of the corresponding application server:

    • {INSTALLATION_DIR} > eService > installation > egain-plugin > workers.properties - From JBoss.
    • {INSTALLATION _DIR} > eService > installation > egain-plugin > iisproxy.ini - From WebLogic.
  • In the eService.ear on the file server, navigate to {INSTALL_DIR} > installation > ear. Then, navigate to Community.war > WEB-INF > config > jforum-custom.conf. This file contains the hostname of the first web server.

  • The EAR > egpl_application_ejb_common.jar file inside the eService.ear folder contains the hostname of the messaging servers:

    • /META-INF/jboss-ejb3.xml - If you use JBoss, this change is not required with Versions 11.0.2 and later.
    • /META-INF/weblogic-ejb-jar.xml - If you use WebLogic, a Java Messaging Services (JMS) cluster URL is present on JMS-clustered setups.
  • In the EAR and SERVICES_SERVER > lib > configurations.zip files, and in the FILE_SERVER > installation > data access folder, you must modify the egpl_ds_connpool_map.xml file with the new hostname of the database server.
Updated: Sep 27, 2013
Document ID: 116520