Overview

As described in Overview of document processing, the Receiver is responsible for accepting inbound documents from a specific transport. A target is an instance of the Receiver configured for a particular deployment.

Documents received at a target on the hub can come from community participants (for eventual delivery to the Community Manager) or from a Community Manager back-end application (for eventual delivery to participants).

Figure 16 shows a WebSphere Partner Gateway server with four targets set up. Two of the targets (HTTP/S and FTP/S) are for documents coming from participants. These two targets represent an HTTP URI and an FTP directory. You provide information about these targets to your participants to indicate where they should send documents to you. The other two targets (JMS and file directory) are for documents originating from the Community Manager back-end application. These targets represent a queue and a directory.

Figure 16. Transports and associated targets
This figure shows four targets defined at the hub

You set up at least one target for each type of transport over which documents will be sent to the hub. For example, you will have an HTTP target to receive any documents sent over the HTTP or HTTPS transport. If your community participants will be sending documents over FTP, you will set up an FTP target.

The Receiver component detects when a message arrives at one of the targets. Some targets detect messages by polling their transports at regular intervals or on a scheduled basis to determine if new messages have arrived. The WebSphere Partner Gateway targets that are polling-based are: JMS, FTP, SMTP, File, and FTP Scripting. The HTTP/S target is callback-based, which means that it receives notification from the transport when messages arrive. User-defined transports can be either polling-based or callback-based.

Copyright IBM Corp. 2003, 2005