Starting and Stopping
You can start and shut down Interaction Concentrator components by using the Management Layer, a startup file, a manual procedure, or Services Manager.
All of these methods usually require command-line parameters for a server application as well as an executable file name. The next section describes the command-line parameters that are common to most Genesys server applications. Subsequent sections describe the startup and shutdown procedures.
For information about using the Management Layer, startup files, and Services Manager for startup, see the Framework Deployment Guide.
Before You Start ICON
The following issues are important for you to consider before you attempt to start ICON.
Starting the cfg Role for an Oracle IDB
If the relational database management system (RDBMS) of the Interaction Database (IDB) that stores configuration-related data is Oracle, Genesys strongly recommends that you collect statistics on your IDB schema before you start the ICON instance that performs the cfg role. Collecting statistics before starting ICON significantly shortens the amount of time it takes to start up.
Verifying ICON Connections and Configuration
Before you attempt to start ICON, confirm that the connections and configuration options that have been configured for your ICON Application are correct for your deployment.
In general, do not change any connections on the Connections tab of the ICON Application during startup or runtime. Furthermore, do not disconnect from Configuration Server during startup.
- If ICON disconnects from Configuration Server during startup, ICON initialization will fail.
- If you remove or change other connections during startup, ICON might fail to initialize correctly.
- If you remove or change any connections during runtime, ICON functioning might be affected.
- You must restart Interaction Concentrator after a backup instance is configured of any application, such as OCS or T-Server, for which Interaction Concentration has a connection configured on the Connections tab. If you do not restart Interaction Concentrator, data from the affected application is not written to the database.
For more information about configuring connections, see the instructions for configuring the Connections tab in the procedure to configure the ICON Application object.
Do not make changes to ICON configuration options during startup. You can make changes to ICON configuration options during runtime, but in some cases you must restart ICON for the changes to take effect. For more information, see Configuration Options.
The following startup command-line parameters are supported by Interaction Concentrator:
|−host||The name of the host on which Configuration Server is running.|
|−port||The communication port that client applications must use to connect to Configuration Server.|
|−transport-port||The client-side port that ICON must use to connect to Configuration Server.|
|−transport-address||The TCP host address to be used for the transport-port.|
|−app||The exact name of an application as configured in the Configuration Database.|
|−V||The version of a component. Note that specifying this parameter does not start an application, but instead returns its version number. You can use either an uppercase letter (V) or lowercase letter (v).|
|−lmspath|| The full path to the log messages files that an application uses to generate log events. (These files are the common file named common.lms and the application-specific file with the extension *.lms.) Use this parameter when the common and application-specific log message files are located in a directory other than the application’s working directory—for example, when the application’s working directory differs from the directory to which the application was originally installed. |
Note that if the full path to the executable file is specified in the startup command line (for instance, c:\gcti\multiserver.exe), the path that is specified for the executable file is used to locate the *.lms files, and the value of the lmspath parameter is ignored.
This section provides startup instructions for ICON server. You can start ICON in any of the following ways:[+] Starting ICON with Solution Control Interface
[+] Starting ICON manually on UNIX
[+] Starting ICON on Windows
[+] Starting ICON as a Windows Service
To prevent ICON from self-starting, make sure that you clear the autorestart property in the ICON Application object.[+] Stopping ICON with Solution Control Interface (Recommended)
[+] Stopping ICON on UNIX from the command line
[+] Stopping ICON on UNIX from the console window
[+] Stopping ICON on Windows from the console window
[+] Stopping ICON as a Windows Service