Application Integration

Jacques van Wijk

jacquesvw@fenestrae.com

Faxination Web Service Connector

Use Faxination 2016 as a development platform for sending and

receiving both fax and mobile messages

Provides a Web Service Enhancements v3 interface (legacy)

Provides a Windows Communication Foundation interface

Can also consume a web service that you’ve created for inbound

messages and notifications

Requires the Windows Server web services role (IIS)

http://<servername>/fenmessagedotnet3/fenmessage.asmx

Faxination Web Service Connector

http://<servername>/fenmessagedotnet3/fenmessage.asmx

Faxination Web Service Connector

Faxination Web Service Connector: Outbound

Web Service

Application

Internet Information

Server

Faxination Web

Service Connector

Faxination Kernel

Faxination Queue

Faxination Device

Faxination Web Service Connector: Outbound

Web Service

Application

Internet Information

Server

Faxination Web

Service Connector

Faxination Kernel

Faxination Queue

Faxination Device

Faxination Web Service Connector: Outbound

Web Service

Application

Faxination Web

Service Connector

(Client)

Faxination Kernel

Faxination Queue

Faxination Device

With registered Service

Faxination Web Service Connector: Inbound

Web Service

Application

Faxination Web

Service Connector

(Client)

Faxination Kernel

Faxination Queue

Faxination Device

Web Service Application

Faxination REST Connector

Representational State Transfer

Can be consumed by any client, even a web browser

Lower bandwidth, no SOAP envelopes/headers

Simple noun/verb/resource structure

Each API call has both a JSON and an XML version

Internet Information Services (IIS) is not used

http://<servername>:18385/FaxRESTConn/Messaging

http://<servername>:18385/FaxRESTConn/Messaging/help

Faxination REST Connector: Outbound

RESTApplication

Faxination REST

Connector

Faxination Kernel

Faxination Queue

Faxination Device

Faxination REST Connector: Inbound

RESTApplication

Faxination REST

Connector

Faxination Kernel

Faxination Queue

Faxination Device

Faxination Inbound Directory Connector

Associate inbound routing codes with local or UNC paths

Can be used exclusively, or combined with other inbound routes to

mailboxes, SharePoint, SAP, etc.

Each inbound route can have its own file type (TIF, PDF, PDF/OCR) and file

name template

Each inbound route can enable/disable a secondary message properties file

The contents of the message properties file can also be customized using an

XML Stylesheet

Document Management

SystemUNC Path

Faxination Inbound Directory Connector

Faxination Inbound Directory

Connector

Faxination Queue

Faxination Kernel

Faxination Device

Faxination Host

Host 2 Host

Thank youJacques van Wijk (jacquesvw@fenestrae.com}