Installing/Configuring Web Viewer and the CCI System Name - Important!

Products

• Output Management Document Viewer
• Output Management Web Viewer

Issue/Introduction

All of this revolves around the 12.x Web Viewer CCIClient.properties file, TCPIP.Sysid parameter, or Client System ID. A historical note about this parameter is in order here. It was always (going back to at least 2.0 Web Viewer) a requirement that every Web Viewer Server within a CCI network have a unique CCI Client Identification, System Name, or as it was later known in the Java version CCI, TCPIP.Sysid parameter or Client System ID. The 12.1 ConfigTool calls it the "Client System ID." The way this CCI System Name works is, you either leave the parameter blank (in which case it is populated by the application with a value based on the server machine name, or you manually code your own, unique value.

In shops with multiple servers with long machine names where a unique value is not assured within the first eight characters (longer System Names are truncated at 8 characters internally within the application), manually-coded, unique CCI System Names are required. The bottom line is that it is a requirement that every server within a CCI/Common Services network, have a unique CCI Client Identification, System Name, or TCPIP.Sysid parameter value, or CCI Client System Name.

There is a 12.1 Web Viewer install/configuration scenario where this CCI parameter can confound things. If Web Viewer 12.1 is installed and configured, then deployed to multiple systems with an external configuration, the TCPIP.Sysid= parameter can be propogated to all systems with the same value - as the EAR file is deployed to each additional system, the same, non-unique TCPIP.Sysid= parameter value is propagated. When each system is brought on line and/or users begin to utilize the application, CCI will be unable to identify from which system a particular communication originated.
 

Environment

Release: OUTWBV01300-12.1-Output Management-Web Viewer for AIX
Component:

Resolution

The workaround to employ in such a situation is to manually code a unique TCPIP.Sysid= parameter values for each system (run ConfigTool.jar on each system, or carefully edit the TCPIP.Sysid= parameter in the CCIClient.properties file for each system). The solution when using an external configuration is to leave the TCPIP.Sysid= parameter blank for the initial install so that when deployed to multiple servers, each Web Viewer/CCI entity will assume a unique CCI identity/System Name based on the server/machine name - provided the machine names are unique within the first eight characters.