Changing the AIX environment of a custom server

Sometimes the default AIX environment (as set by Blueworx Voice Response) conflicts with the needs of a particular custom server. To get round this problem, you could change the environment before Blueworx Voice Response starts, but sometimes this conflicts with the requirements of Blueworx Voice Response itself. Instead you can change the AIX environment in which a custom server runs, and you can do this without changing any of the code in the custom server itself.

To change the environment for a particular custom server, create a file called custom_server_name.environ in the subdirectory for that custom server (where custom_server_name is the name of the custom server). The subdirectory is named $CUR_DIR/ca/custom_server_name_dir.

In each line of this file, specify an environment variable that you want setting or changing. For example, FVCX0100=A. Each line in the file can contain a maximum of 2048 characters.

Before Blueworx Voice Response starts the custom server, it passes each line of this file to the AIX putenv() subroutine call. (For more information on this call, see the AIX: Technical Reference: Base Operating System and Extensions Volume 2).

The AIX environment is changed only when:

  1. Starting the custom server using the Custom Server Manager window
  2. Starting the custom server from another custom server using the CA_Start_CA() subroutine
  3. Using csRunAction through SNMP

If the custom server is started directly using the command line, a script, or a program, the environment is not changed.

Note:
  1. You do not need to change the code in your custom server. The AIX environment is changed only if the .environ file exists.
  2. Alarm 25022 is generated if there is a problem reading the .environ file.
Parent topic: Developing a custom server