====== JobFileRequestRouter ====== The JobStep **JobFileRequestRouter** is used in conjunction with the [[en:prozessdefinition:jobs:jobsteps:kommunikation:backend: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. {{:images:jobfilerequestrouter1.png}} 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 [[prozessdefinition:jobs:jobsteps:kommunikation:jobrequestforwarder|]]. {{:images:jobfilrequestrouter2.png}} ====== Eventlistener ====== The associated event lister can be configured in this way: {{:images:jobfilerequestservice_event.png}} ====== Web interface ====== Das interface is defined as follows: ===== ExecuteFile ===== Sends a local file (accessible for the eBiss service) \\ \\ Parameter: **JFEReq** - RecipientId string, http address of the receiver - SenderId string (optional), http address of the sender - RequestDateTime DateTime, timestamp of the request - TimeOutSecs int, timeout in seconds - TraceLog bool, flag to return log information in the response - FileName string, full path and name of the file - DeleteFile bool, should the file be deleted if it is processed positively ===== ExecuteContent ===== Sends data that is directly contained in the Content field of the request. \\ \\ Parameter: **JFEReq** - RecipientId string, http address of the receiver - SenderId string (optional), http address of the sender - RequestDateTime DateTime, timestamp of the request - TimeOutSecs int, timeout in seconds - TraceLog bool, flag to return log information in the response - Content byte[], message content In both cases, the result is of type **JEResp** - ResultMessageState int, the end status of the message (eBiss MessageState as integer) - TaskCode int, eBiss error code as integer - TaskInfo string, additional information about the error - LogInfo string, detailed log of the processing, if requested in the request ===== Service call ===== The service can be called like this: eBiss.CommandClient ––JobFileRequest [//URL defined in the listener//] [//Full file path//] [//Recipient ID//]