The JobStep JobFileRequestRouter is used in conjunction with the BackendObjectRetrieverEx and the webservice event listener.
I allows a file to be handed over to eBiss via a standardised webservice interface which can be implemented in an external client.

The request can either contain the payload in a direct manner or contain a reference to the files location. In the second case, the JobFileRequestRouter itself will access the files content.

The message can then be processed as usual, delegated to another job or forwarded to another instance of the eBiss webservice via use of the JobRequestForwarder.

The associated event lister can be configured in this way:

Das interface is defined as follows:

Sends a local file (accessible for the eBiss service)

Parameter: JFEReq

1. RecipientId string, http address of the receiver
2. SenderId string (optional), http address of the sender
3. RequestDateTime DateTime, timestamp of the request
4. TimeOutSecs int, timeout in seconds
5. TraceLog bool, flag to return log information in the response
6. FileName string, full path and name of the file
7. DeleteFile bool, should the file be deleted if it is processed positively

Sends data that is directly contained in the Content field of the request.

Parameter: JFEReq

1. RecipientId string, http address of the receiver
2. SenderId string (optional), http address of the sender
3. RequestDateTime DateTime, timestamp of the request
4. TimeOutSecs int, timeout in seconds
5. TraceLog bool, flag to return log information in the response
6. Content byte[], message content

In both cases, the result is of type JEResp

1. ResultMessageState int, the end status of the message (eBiss MessageState as integer)
2. TaskCode int, eBiss error code as integer
3. TaskInfo string, additional information about the error
4. LogInfo string, detailed log of the processing, if requested in the request

The service can be called like this:

eBiss.CommandClient ––JobFileRequest [URL defined in the listener] [Full file path] [Recipient ID]