This document describes how the web server can be moved to a separate machine when the application and web servers are installed on the same machine. The original machine on which the application and web servers are installed can have other Cisco Interaction Manager components, such as file server and services server, installed on it. However, the new machine on which you plan to install the web server cannot have any other Cisco Interaction Manager components installed on it.
Cisco recommends that you have knowledge of Installing Cisco Unified Web and E-Mail Interaction Manager .
The information in this document is based on the Cisco Interaction Manager Release 4.2(1) or higher (up to 4.2(5)a).
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Refer to the Cisco Technical Tips Conventions for more information on document conventions.
If your installation includes only one web application server, complete these steps in order to separate the primary web and application servers:
Note: This procedure does not impact Cisco Interaction Manager Release 4.3(1) because no manual steps are required with the 4.3(1) installation.
This section describes these pre-installation tasks that you must complete before you separate the primary web and application servers:
You must acquire new hardware for installing the separate web server. For detailed hardware requirements, refer to Cisco Unified Web and E-Mail Interaction Manager Solution Reference Network Design Guide . For software requirements, refer to Cisco Unified Web and E-Mail Interaction Manager System Requirements .
Stop all application servers and the services server. In distributed-server installations, these servers are on different machines. On the services server machine, open the Windows Task Manager, and verify that all javaw and java processes (the services) are stopped.
Complete these steps in order to separate the primary web server from the primary application server:
Install the web server on the new machine. For detailed information, refer to the Cisco Unified Web and E-Mail Interaction Manager Installation Guide .
During installation, the program asks for information about the application server. Provide the details of the primary application server for which you are creating the web server.
Update the Common.messaging.applethost setting in the egpl_pref_globalsettings table with the DNS host name of the primary web server. Run this query on the master and active databases:
update egpl_pref_globalsettings set setting_act_val = 'Web Server DNS host name' where setting_name = 'Common.messaging.applethost'
Where Web Server DNS host name is the DNS host name of the new primary web server.
In order to separate the secondary web server from the secondary application server, you must install the web server on the new machine. For detailed information, refer to the Cisco Unified Web and E-Mail Interaction Manager Installation Guide .
During installation, the program asks for information about the application server. Provide the details of the secondary application server for which you are creating the web server.
Start the Cisco Interaction Manager Service
In the Windows Services panel, start Cisco Service in order to start all Cisco Interaction Manager services. If it is a distributed-server installation, first start the Cisco Service on the services server and then on each application server. After starting the Cisco Service, wait five minutes before you attempt to log in to the product.
The Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers.
Refer to Cisco Technical Tips Conventions for information on conventions used in this document.