Configuring servers to host external components

The server that runs external components can be configured like any other server using EAServer Manager or jagtool. The external server must run on the same machine as the server that your application clients connect to. Do not manually start the external server; the primary server starts the external server automatically if it is not running when a request arrives.

When you specify an external server name for the component in EAServer Manager, EAServer Manager automatically installs the package that contains the component to the specified server if the server exists and the package is not already installed.

You can configure the properties in Table 4-4 on Components tab of the Server Properties dialog box for the server where the component is installed. These properties set the default timeouts for communication with servers that host external components. These properties can be overridden for individual components.

Table 4-4: Server properties for external component execution

Setting

Specifies

External Server Request Timeout

How long, in seconds, to wait for a response from the external server before returning an error to the client. If not set, the default is 60 seconds. If you specify the component External Request Timeout setting, it overrides this setting.

If using jagtool or an external configuration file, set the property com.sybase.jaguar.server.external.request.timeout.

External Server Start Timeout

How long, in seconds, to wait for the external server to start if it is not already running. EAServer returns an error to the client if the external server does not start in the specified time. If not set, the default is 60 seconds. If you specify the component External Server Start Timeout setting, it overrides this setting.

If using jagtool or an external configuration file, set the property com.sybase.jaguar.server.external.serverstart.timeout.