Key Capabilities
- Real-time content adaptation and security scanning
- Support for both request modification (REQMOD) and response modification (RESPMOD) modes
- TLS encryption support for secure communications
- Customizable HTTP encapsulation for legacy system compatibility
- Flexible authentication options including private certificate support
- Functions as a Transform step in the flow. Files that are flagged as needing attention yield errors, while other files proceed down the flow as usual.
Connector Configuration
This section contains all of the configurable connector properties.Settings Tab
Settings related to the core configuration of the connector.| Setting | Description |
|---|---|
| Connector Id | The static, unique identifier for the connector. |
| Connector Type | Displays the connector name and a description of what it does. |
| Connector Description | An optional field to provide a free-form description of the connector and its role in the flow. |
| ICAP URI | (Required) The ICAP Uniform Resource Identifier (URI) of the ICAP server to connect to. Must be in this format: icap://<hostname>:<port>/<service_name>. |
| Allow Script in ICAP URI | Allows for the evaluation of Script expressions in the URI. When you select this, the Script Editor button appears ( ), which enables you to build dynamic request URIs using Script. |
| ICAP Headers | Optional headers for specialized server requirements. Use this to add custom ICAP request headers that you want to include in the outgoing ICAP request. |
| Allow Script in Headers | Allows for the evaluation of Script expressions in the headers before the query is issued. For example, [_ | now('yyyy-MM-dd')] evaluates the current date, and [_message.header:headername] evaluates the headername header from the input message context. |
| TLS Configuration | Check this to enable TLS encryption for the ICAP connection. |
| TLS Server Certificate | The public key certificate used to verify the identity of an TLS/SSL server. This is only necessary if the ICAP server has enabled TLS. Set it to Any Certificate to unconditionally trust the ICAP server’s identity. Only relevant when TLS Configuration is enabled. |
| Local File Scheme | A scheme for assigning filenames to messages that are output by the connector. You can use macros in your filenames dynamically to include information such as identifiers and timestamps. For more information, see Macros. |
Advanced Tab
TLS Client Authentication
Other Settings
Proxy Settings
Logging
Miscellaneous
Automation Tab
Automation Settings
Settings related to the automatic processing of files by the connector.Performance
Alerts Tab
SLAs Tab
Transactions Tab
This tab lists all messages associated with the connector. Use the search bar to find specific messages, or click the funnel icon to apply a filter. You can filter by time, message direction, and/or status. Incoming responses appear on this tab.Events Tab
The following are available in the Response event:
- StatusCode: The ICAP response status code (such as 200, 204, or 4xx)
- _response: The ICAP response. You can use
[_response.header:xxx]to get a specific header. - _message: To refer to the input message (headers and body), and adding headers to the output.