Functionality

The job file is provided in the directory SPOOLOUT by the third-party application. This directory is periodically browsed by the ixi-UMS FAPI Connector for files that correspond with the determined file filter. The data part can be passed on in the job file or as attachment. The ixi-UMS FAPI Connector converts the header part into ixi-UMS format. In the process, not available yet required header information is extended with the default information.

Example:

Header passed on to the ixi-UMS FAPI Connector:

@@RECIPIENT:+49 8142 47989798

@@RECIPIENT:+49 30 798946

@@SENDER:meier@firma.de

@@PRIORITY:2

@@COVER:

@@ATTACHMENT:f:\attachments\welcome.doc;0

@@SENDER_DDI:789

Header like passed on to the subsequent ixi-UMS Enterprise component by the ixi-UMS FAPI Connector:

MAIL FROM:meier@firma.de

RCPT TO:fax#+49 8142 47989798

RCPT TO:fax#+49 30 798946

Importance:normal

X-IFAXDATA-HeaderFile:

X-IFAXDATA-FaxEnabled:1

X-IFAXDATA-FaxLocal:1

X-IFAXDATA-FaxCountryWide:0

X-IFAXDATA-FaxInternational:0

X-IFAXDATA-Department:

X-IFAXDATA-DChID:789

X-IFAXDATA-SenderID:

X-MaxPages:

X-COVERINFO-Businessphone1:

X-COVERINFO-BusinessFax:

X-COVERINFO-Company:

X-COVERINFO-Address:

X-COVERINFO-Department:

If one of the "Must"-fields is not available or if the conversion cannot be executed successfully, the job is classified as error job and is provided in the subdirectory ERROR together with an error report.

The data part of the fax message can be passed on as attachment or in the job file as ASCII-text or HTML-format. The data part is embedded in Mime-format.

When multiple messages are stated in one job file, an individual outbound message file is generated for every job.

After that, the file is passed on to the ixi-UMS Render Connector and processed.