Panagon IS and CS Communications CS (Content Services) uses default MS SQL Server or Oracle protocols. IS (Image Services) uses FileNET Courier protocols. Web Services uses these protocols to communicate with back-end libraries, and uses http or https to communicate with clients.

What is FileNET Courier? Courier is a protocol family that sits on top of the client & server’s IP stacks. “Client” refers to Panagon Web Services, Panagon IDM, or WFD thick client software. Clients send requests to the IS servers and get responses using Remote Procedure Calls or RPCs. Courier is made up of COR, PEP, & NCH.

Courier Protocols COR – Courier Remote Procedure Calls NCH – Network Clearing House * PEP – Packet Exchange Protocol * * These last two are UDP based. Since many client’s security policies restrict the use of UDP, Image Services can be run without them.

Courier Remote Procedure Calls Connection oriented – runs on top of server TCP port 32769 through COR_Listen or OCOR_Listen. Acts as a foundation for request and response sequences, or RPCs. Connections range from nine frames to several thousand frames in length.

COR Frame Structure

Packet Exchange Protocol Used by IS Document Services (ds_notify) to notify a client that an object has been retrieved from optical and is ready for display. Used by clients to discover the NCH Server, unless they are configured to use a “4-part” NCH domain name. PEP runs “on top” of UDP – port 32770 for NCH, variable port for ds_notify.

Network Clearing House Acts as name-to-address database for all FileNET IS systems. Can be found using PEP broadcast at client startup, or “directed” PEP if 4-part NCH name is used. NCH is accessed via COR RPCs once a client is logged on. NCH_daemon on Root “listens” on UDP port 32770.

Thick-client / IS Communications Examples include Capture, Panagon desktop, Workforce Desktop, and custom WAL apps

Thin-client / IS Communications Web Services acts as a Courier gateway, so clients can stick to basic web protocols.

TCP Ports