State of a service. You can maintain whether or not you want the server to treat it as a “stateless” service at run time.State of a service. You can maintain whether or not you want the server to treat it as a “stateless” service at run time.Caching of service results. You can cache elements to reduce memory usage in Integration Server.Execution locale of a service. You can set the type of locale in which the Integration Server executes at run timeSaving and restoring of the pipeline. You can save the pipeline or restore a previously saved pipeline at run time.Important: | The Run time properties in the Properties view should only be set by someone who is thoroughly familiar with the structure and operation of the selected service. Improper use of these options can lead to a service failure at run time and/or the return of invalid data to the client program. |
Property | Description | ||
Stateless | Specifies whether or not Integration Server is required to maintain state information for this service for the duration of the client session. Select True if the service is a self-contained, atomic unit of work and does not need access to state information. This reduces the number of server resources it consumes at run time. Select False if the service is part of a multi-service transaction or if you are unsure of its state requirements. The default is False. | ||
Cache results | Indicates whether Integration Server stores the service results in a local cache for the time period specified in the Cache expire property. After the service executes, the server places the entire pipeline contents into a local cache. When subsequent requests for the service provide the same set of input values, the server returns the cached results instead of invoking the service again. Select True to cache the service results. Select False if you do not want to cache service results. Cache results for stateless services only. The default is False.
| ||
Cache expire | Specifies the amount of time that the pipeline contents stay in memory after they are cached. If you enable the Cache results property, type an integer in this field representing the number of minutes you want a result to remain cached. The expiration timer begins when the server initially caches the results. The server does not restart the expiration timer each time it retrieves the results from cache. The minimum cache expiration time is one minute. | ||
Reset cache | Click Reset to clear the cached results for this service | ||
Prefetch | Determines whether Integration Server automatically refreshes a cached result when it expires by re-executing the service using the same inputs. To automatically refresh this service's cached results, set Prefetch to True. (Prefetch can consume a substantial amount of server memory; consult your Server Administrator before using this option.) The cache may not be refreshed at the exact time specified in Cache expire. It may vary from 0 to 15 seconds, according to the cache sweeper thread. For details, see the watt.server.cache.flushMins setting in Integration Server. | ||
Prefetch activation | Specifies the minimum number of times that a cached result must be accessed (hit) with the same inputs in order for the server to prefetch results when it expires. If you enable Prefetch, you must specify an integer representing the minimum number of hits a cached result must receive to be eligible for prefetch. (Entries that do not receive the minimum number hits are released from memory.) The cache may not be refreshed at the exact time the last hit fulfills the Prefetch Activation requirement. It may vary from 0 to 15 seconds, according to the cache sweeper thread. For details, see the watt.server.cache.flushMins setting in Integration Server. | ||
Execution locale | Specifies the locale in which this service will be executed. | ||
Pipeline debug | Determines whether Integration Server automatically saves or restores the pipeline after the service executes. This option is useful for testing and debugging the service. Select None to run the service without saving or restoring the pipeline. This is the default. Select Save if you want to save the entire pipeline contents to a file when the service executes. To restore the pipeline from a file when the service executes, choose Restore (Override). If you want the server to merge the pipeline with one from a file when the service executes, choose Restore (Merge). When this option is selected and the input parameters in the file match the input parameters in the pipeline, the values defined in the file are used in the pipeline. If there are input parameters in the pipeline that are not matched in the file, the input parameters in the pipeline remain in the pipeline.
| ||
|
