How to Use Startup Files

Some Genesys applications require special scripts to start and stop the application. Refer to the deployment procedures of your specific product to determine if separate start and stop files must be configured.

For Genesys applications that require both start and stop scripts to function properly, you must configure these scripts instead of single batch files. For Application objects that have the commands start_stop.start_command and start_stop.stop_command specified in their Annex, the specified values are used to start and stop the application on the target host. If these parameters are not specified, by default, system termination signals would be sent to the running process when the stop is issued. But if the stop_command is specified, an external script will be invoked instead for those applications that require special handling for termination.

Important

For Genesys applications for which the command line, command line argument, and start_command are all specified, the value in start_command would take precedence.

If your application requires startup files, do the following:

1. Modify the application to use a start up file. [+] Show steps Prerequisites Configuration Layer components are installed and running. An Application object exists for the application that is use a startup file. You are logged in to Genesys Administrator. Steps In Genesys Administrator, open the Configuration tab of the Application object. In the Server Info section, modify the following properties: Command Line property—Instead of the application executable file or startup file name, specify the command prompt name (cmd.exe) with the full path to it. For example: D:\Windows\system32\cmd.exe Command Line Arguments property—Instead of the Configuration Server parameters and application name, specify the startup file name (startServer.bat) with the full path to it, preceded with the /c command line parameter. For example: /c D:\GCTI\MessageServer\startServer.bat Click Save to save the configuration changes.

2. Modify the startup file for each application. [+] Show steps Prerequisites The applications must be configured to use startup files, as described in the previous step. Steps Using the text-editor of your choice, open one of the following files that are located in the applications’ directories: On UNIX—run.sh On Windows—startServer.bat If necessary, modify the existing line, or insert a new line specifying the application’s executable file name with the full path to it, followed by this sequence of symbols: %1 %2 %3 %4 %5 %6 For example, for a Message Server application installed in the GCTI directory on the D drive, the content of a startup file to use with the Management Layer looks like this: D:\GCTI\MessageServer\MessageServer.exe %1 %2 %3 %4 %5 %6 Save the file.