Installing and configuring the Cisco ICM custom server

This section explains how to install and configure the Cisco ICM custom server which is supplied as an installp image. You use the smitty command of the System Management Interface Tool (SMIT) to install it.

When installing the Cisco ICM custom server, refer to the Installing Blueworx Voice Response Version 7 for the first time.

When you have installed the component, import the custom server and state table. Run the installation verification test to ensure that the installation was successful.

Installation prerequisites
Before you start installing the software, there are some things that you need to check. These are described here.
Installation procedure
The Cisco ICM custom server is put into the Cisco application as described in this section.
Running the installation verification test
This section describes how to run the installation verification test to check whether the Cisco ICM custom server is correctly installed. This test uses a state table to run all the custom server functions that are in simulation mode. The system uses the application launch file to test the state table see Application launch file.
Migration
The process for migration to this version of the custom server is the same as the process for installation, except that the custom server must be stopped from the Custom Server Manager window before installation.
Coexistence
This upgrade to the Cisco ICM custom server replaces the old custom server and cannot coexist with a previous version. In a cluster of Blueworx Voice Response clients, which are not part of a single system image (SSI) cluster, each client can have a different version of the custom server under the conditions described here.
SSI and HACMP error handling
If a DB2® or NFS failure occur, Blueworx Voice Response client machines handle an SSI cluster in the same way as they handle an SSI cluster that is running HACMP.
Configuring for Java
To configure Java for access to the Cisco ICM custom server, you need to edit the dtjenv file and the configuration file default.cff. The dtjenv file is used to initialize local environment variables in the Java environment. The default.cff file contains definitions of all your nodes, and all your applications, and is imported into the configuration database, config.cfd.
Deconfiguring Java
To deconfigure Java, follow the instructions in this section.