Navigation: Integration → CI (Content Inspection)
Content Inspectors handle the processing in the Content Inspection module. Each Content Inspector collects files in a file pool. It then processes these files based on defined rules.
This section describes all configuration options for a Content Inspector.
Main settings
File Inspectors determine whether a Content Inspector is responsible for a specific file. The Content Inspector Manager calls File Inspectors to check each incoming file. Available types include Accept All Files, Accept Empty Files, EDIFACT, IDoc, JSON, PDF, Plain Text, Regex, Tradacoms, X12, XML, and XML V4 Inspector. You can also develop custom File Inspectors in Java via the API.
Data transmission
This section defines how the Content Inspector transmits processed files. The following transfer methods are available:
Profile: Select an active profile for data transfer. The Input Agent type is flexible, but the profile must be active.
Mail: Send files through a partner channel of type "Mail". You can compress files as ZIP or 7z archives with optional password protection.
X.400: Transmit files via an X.400 channel. You can request confirmation of receipt. X.400 also offers archive and compression settings.
ASM: Select an active ASM entry for data transfer.
Workflow: Forward files to an active workflow that allows attachments. The workflow display name starts with the prefix "CI".
Pre-execution/Post-execution
You can split or merge files before or after the Content Inspector processes them.
Splitter: Split multi-message files into individual messages. Available types include EDIFACT Message Splitter, EDIFACT UNH Message Splitter, IDoc Message Splitter, JSON Splitter, Plain Text Splitter, Tradacoms Message Splitter, X12 Message Splitter V2, XML Message Splitter, and XML Node Splitter. You can develop custom splitters in Java.
Merger: Combine multiple files from the file pool into a single output file.
File compound
File compound settings define how the Content Inspector handles its file pool. You configure the maximum number of files, the maximum waiting time, and the sort order. The Content Inspector starts processing when the waiting time runs out. Otherwise, it changes to the Overdue status.
Notification
The Notification tab lets you configure email alerts. If the Content Inspector reaches the "Overdue" status, the system sends a notification. You define the recipient, subject, and message text. The placeholder {--fileList--} inserts a list of all files in the file pool.
Exceptions
Exception periods pause the Content Inspector's timer for a defined time window. This is useful if you expect no file activity during certain hours. You specify the day, start time, and duration in minutes.
Partner relation
The Partner relation tab assigns partner channels to the Content Inspector. A File Inspector can use placeholders for additional IDs. These values come from the assigned partner channels.