Skip to main content

Settings in All Business Operations

Provides reference information for settings that are available in all business operations.

Summary

All business operations have the following settings:

Group Settings Notes
Informational Settings Comment, Category, Class Name, Description, Adapter Class Name, Adapter Description, Business Partner See these settings for business services
Basic Settings Enabled  
Additional Settings Schedule, Pool Size  
Additional Settings Reply Code Actions See this setting for business processes
Additional Settings Retry Interval, Failure Timeout  
Additional Settings SendSuperSession  
Additional Settings Throttle Delay See this setting for business services
Alerting Control Alert Retry Grace Period  
Alerting Control Queue Count Alert, Queue Wait Alert See these settings for business processes
Alerting Control Alert On Error, Inactivity Timeout See these settings for business services
Development and Debugging Foreground, Log Trace Events, Archive IO See these settings for business services

Alert Retry Grace Period

Common to business processes and operations. Specifies an optional grace period during which errors relating to external connections do not trigger alerts (even if Alert On Error is True).

If the error condition still exists after the alert period expires, the business operation triggers an alert; otherwise no alert is triggered.

Business services have a similar setting.

Failure Timeout

Total number of seconds to keep trying to connect with a destination outside InterSystems IRIS. After this number of seconds has elapsed, the business operation discards the message data and returns an error code. To ensure that no message is ever skipped, enter a Failure Timeout value of –1, which means never time out. Use a setting of –1 when complete data delivery is critical, for example in healthcare applications.

Retry Interval

Number of seconds to wait between attempts to connect with a destination outside InterSystems IRIS.

SendSuperSession

The SendSuperSession property controls whether outbound adapters include the SuperSession property in the outgoing message. The SuperSession property is used to associate messages that cross from one namespace to another. The HTTP and SOAP outbound adapters support SuperSession and automatically write the SuperSession value to the outgoing HTTP header. Although the other outbound adapters do not automatically support SuperSession, you can add custom code that inserts the SuperSession value into the outgoing message. For details, see SendSuperSession.

FeedbackOpens in a new tab