File Egress Connector

In this use case scenario, the requirement is to receive messages with a file payload through a NIO HTTP ingress connector and saving the payload file to a local directory. For statistics and monitoring purposes it’s required to extract out the client ID’s from a receiving message transport header and create a log specifying the extracted client ID value and the same client ID value should be prepended to the saving file name.

In order to implement above use case it is required to select the HTTP NIO Connector and Local File Connector dependencies from the connector list when creating the empty Ultra project. If the project is already created, it is required to add these dependencies via Component Registry. From Tools menu it is necessary to select Ultra Studio → Component Registry and from the Connectors list and Processors list, select above dependencies.

To implement above use case first it is required to create a new integration flow and add a HTTP NIO IngressConnector and then it is required to provide the parameters to the HTTP NIO IngressConnector and configure it. The incoming messages will contain a transport header denoting the sending client’s id (clientId). For monitoring purposes that client id will be logged using a Logger processing element. As it is required to prepend the same client id to the saving payload file name, in the next processing element it will be assigned to a scope variable CLIENT_ID using Add Variable processing element. Finally it will be forwarded to a File Egress Connector element that has been configured inorder to save the payload to the configured location in the local file system.

After filling out the required parameters, this configuration can be saved by clicking the Save button at the bottom of each element. Finally the complete flow with the configurations will be depicted as follows.

Scope Variable to Prepend to the File Name parameter is configured with "@{message.var.CLIENT_ID}" to modify the file name by attaching the client ID as the suffix for the original file name. Framework will replaced the "@{message.var.CLIENT_ID}" from the value of the variable with name CLIENT_ID and the receiving timestamp will also be prepended to the file name.