Browse Prior Art Database

Enhancements for Dynamic Mutation of Custom Attributes in File Transfer System

IP.com Disclosure Number: IPCOM000249298D
Publication Date: 2017-Feb-15
Document File: 3 page(s) / 27K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is an enhancement to the Managed File Transfer (MFT) application that enables it to determine during routing whether any custom attributes have been defined for the routing and are used in the filename regex pattern and/or in defining the receiver endpoint. This enhancement enables the modification of the attributes at runtime for dynamic and static routing for the MFT application.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 53% of the total text.

1

Enhancements for Dynamic Mutation of Custom Attributes in File Transfer System

The Managed File Transfer (MFT) application allows the creation of routing rules by assigning custom attributes. These attributes can be used in the manner of regular expressions that define the output delivery file name. These expressions can use one or more attribute(s) to define the file name.

For example, four attributes are defined:  documentType  documentID  extension  receiverDestination

The filename received (stored in theFileName attribute) can be defined in the receiver file layer: ${theFileName}_${documentType}_${documentID}.${extension}.

The fourth custom attribute, which defines the location for file delivery, can be defined using the default expression: ${receiverDestination}.

The existing MFT application provides the following features:  Custom attributes can be defined during design time, but have to be assigned

values that cannot be changed at run time and remain static throughout the entire file routing

 Custom process can be defined and executed during run time by the MFT application, but it is only possible to invoke it if the routing channel is dynamic and not valid for static routing

 The custom attributes are not visible during run time to the custom process and therefore cannot be modified

 The custom attributes are all “read only” after the channels are created

Using a custom attribute enables the creation of the routing to use custom defined information that does not relate in any way to the sender, receiver, or filename of the file. When a routing is created for a sender or combination of the sender and sender filename pattern, the values for the custom attributes are also provided and stored by the application for each routing channel defined.

The issue is that the values of these custom attributes are hard-coded, stored in the MFT tables, and are immutable during run time. The custom attributes cannot be changed at routing time; therefore, customers create dynamic routing channels and use a custom process invoked by this channel. This process then defines the receiver during routing to rename and route/deliver the files to the appropriate receiver.

The novel contribution is an enhancement to the MFT application that enables it to determine during routing whether any custom attributes have been defined for the routing and are used in the filename regex pattern and/or in defining the receiver

2

endpoint. If either of these is true, it invokes a custom process responsible for modifying the values for the custom attributes. This process computes values during routing based on various parameters and replaces the values in the custom attributes. The MFT application then determines the file routing based on the new values stored in the custom attributes by the process. The...