Abstract: In a database system, an archive table data specifies a pre-defined archive time period based on which a periodic archive procedure is performed and a pre-defined purge time period based on which a periodic purge procedure is performed. Based on the periodic archive time period being reached, a new partition is created in a transaction database, which is used as a live partition into which the database stores transaction records which are new; and an expired transaction database partition is moved to the archive database using a database partition feature whereby data in the partition is moved as a whole. Based on the periodic purge time period being reached, an expired archive database partition is removed from the archive database using the database partition feature, wherein data is deleted as a whole from the archive database based on the archive database partition being removed.

Abstract: A file is transferred between client and server. The client determines file transfer resources and good time slots available at the client, and communicates a file transfer plan to upload the file to the server; the file transfer plan specifies the file resources available at the client and time slots. The server acknowledges the file transfer plan, possibly with adjustments to the available time slots, and the server communicates a postbox indicating the location where the file is to be uploaded. The client executes a file transfer process specified in the file transfer plan, based on the file transfer resources available at the server and client, to upload the file to a respective location specified by the postbox. There may be plural uploads of parts of the file, at different available time slots, and/or different combinations of file transfer resources specified in the acknowledged file transfer plan.

Abstract: A file is transferred between client and server. The client determines file transfer resources and good time slots available at the client, and communicates a file transfer plan to upload the file to the server; the file transfer plan specifies the file resources available at the client and time slots. The server acknowledges the file transfer plan, possibly with adjustments to the available time slots, and the server communicates a postbox indicating the location where the file is to be uploaded. The client executes a file transfer process specified in the file transfer plan, based on the file transfer resources available at the server and client, to upload the file to a respective location specified by the postbox. There may be plural uploads of parts of the file, at different available time slots, and/or different combinations of file transfer resources specified in the acknowledged file transfer plan.

Abstract: Certain example embodiments relate to techniques for addressing resource utilization issues in network components (e.g., file transfer servers running out of memory, for example) by identifying and predicting scenarios that are likely to cause problems, and handling them gracefully, without having to deny service completely. Based on current runtime status information and a prediction of how a given request will impact the server and/or the network, a determination is made regarding whether that request is to be accepted by the server. If the total resource usage of the server exceeds or is likely to exceed a threshold: the speed at which requests being processed are being handled is controlled, such that (a) speeds of all but some of the requests are throttled, (b) throttled requests are neither terminated nor allowed to timeout, (c) as non-throttled requests are completed, requests that are throttled have their speeds increased in a predetermined manner.

Abstract: In a database system, an archive table data specifies a pre-defined archive time period based on which a periodic archive procedure is performed and a pre-defined purge time period based on which a periodic purge procedure is performed. Based on the periodic archive time period being reached, a new partition is created in a transaction database, which is used as a live partition into which the database stores transaction records which are new; and an expired transaction database partition is moved to the archive database using a database partition feature whereby data in the partition is moved as a whole. Based on the periodic purge time period being reached, an expired archive database partition is removed from the archive database using the database partition feature, wherein data is deleted as a whole from the archive database based on the archive database partition being removed.

Abstract: Certain example embodiments relate to techniques for addressing resource utilization issues in network components (e.g., file transfer servers running out of memory, for example) by identifying and predicting scenarios that are likely to cause problems, and handling them gracefully, without having to deny service completely. Based on current runtime status information and a prediction of how a given request will impact the server and/or the network, a determination is made regarding whether that request is to be accepted by the server. If the total resource usage of the server exceeds or is likely to exceed a threshold: the speed at which requests being processed are being handled is controlled, such that (a) speeds of all but some of the requests are throttled, (b) throttled requests are neither terminated nor allowed to timeout, (c) as non-throttled requests are completed, requests that are throttled have their speeds increased in a predetermined manner.

Abstract: Certain example embodiments relate to data transfer techniques. A server receives from a client, using a standard communication protocol, a file operation command that relates to a data transfer and indicates data to be transferred and/or a preference for how to transfer data. If the server and client do not have implemented thereon complementary plugins configured to facilitate the data transfer in accordance with the file operation command, the data transfer takes place between the server and client using the standard communication protocol. If the server and client have implemented thereon complementary plugins configured to facilitate the data transfer in accordance with the file operation command, the data transfer takes place using (a) a common communication protocol that is implemented by the complementary plugins but different from the standard communication protocol, and/or (b) data selected and/or transformed by the server-side plugin and understandable by the client-side plugin.

Abstract: Certain example embodiments described herein relate to a File Metadata Handler that helps an integrated managed file transfer solution perform processing in connection with complex distributed file systems, while still cooperating with more straightforward and/or conventional file systems, servers, and/or the like. The File Metadata Handler of certain example embodiments may be able to work with, or take the place of, a more conventional file handler adapter, e.g., to provide possibly required pre-processing and/or additional file processing at runtime for more complex file systems, transport protocols, and/or the like.

Abstract: Certain example embodiments described herein relate to a File Metadata Handler that helps an integrated managed file transfer solution perform processing in connection with complex distributed file systems, while still cooperating with more straightforward and/or conventional file systems, servers, and/or the like. The File Metadata Handler of certain example embodiments may be able to work with, or take the place of, a more conventional file handler adapter, e.g., to provide possibly required pre-processing and/or additional file processing at runtime for more complex file systems, transport protocols, and/or the like.