---

Instance Configuration Options

With the options of the Instance Configuration page you can override global application settings for particular instances. To display the Instance Configuration page, go to the Detail View for the application and click the Config button next to the desired instance.

Application Start-Up / Command Line Arguments

This section allows you to change the command-line arguments that are used when the instance is started. See Setting Command-Line Arguments in Monitor for details.

For convenience, the entire set of command-line arguments passed to the instance are displayed in the blue box at the bottom of this section.

Adaptor Settings

This section is where you specify default values for individual instances of an applications. These settings override the corresponding settings made for the application and for the host on which the application instance is running.

Transport : The socket API used to contact an instance. "socket" indicates simple, cross platform, unbuffered sockets. "fsocket" specifies sockets buffered using fopen(), fread(), fwrite() & such (valid on Unix only). "winsock" specifies Win32 socket API (valid on NT only). "nssocket" indicates Netscape's NSAPI socket API (NSAPI only).

Redirection URL : If an error occurs during request processing, return a redirect (302) HTTP response with the specified URL as the location.

Timeout : Default for Send Timeout, Receive Timeout, and Connect Timeout.

Send timeout : Timeout, in seconds, before reporting a failed send() to an instance.

Receive timeout : Timeout, in seconds, before reporting a failed recv() from an instance.

Connect timeout : Timeout, in seconds, before reporting a failed connect() to an instance.

Connection pool size : Number of persistent connections to maintain with an instance.

Click Change Adaptor Settings to cause changes in any of these settings to take affect.

Graceful Shutdown

This section allows you to change the minimum active session threshold for an instance. This threshold is used when the instance begins refusing new sessions. The default is zero. If your application is usually under heavy traffic, you might not want to wait for all sessions to time-out before terminating the application.

Scheduling

This section allows you to configure the scheduling settings for a given instance. Normally you should use the Application level scheduling to create a staggered schedule of starting and stopping instances. Use the instance-specific section to create your own schedule intervals. See Automatic Scheduling for the scheduling procedure.

Monitor computes a series of shutdown dates from the desired instance lifespan or from the desired instance downtime. The scheduling algorithm causes the instance to begin refusing new sessions on regular intervals based on these two variables.