CASI z/OS

FTPSweeper Modernization Guide

MQ, Messaging and SOAFile Transfer

FTPSweeper is a mq, messaging and soa product by CASI. Explore technical details, modernization strategies, and migration paths below.

Product Overview

FTPSweeper automates the process of searching for and retrieving files from remote FTP servers.

This capability allows users to trigger application processing automatically when files are received by FTP servers.

Modernization Strategies

Rehost

Timeline:
6-12 months

Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.

Refactor (Recommended)

Timeline:
18-24 months

Optimize application architecture for cloud while preserving business logic. Best ROI long-term.

Replatform

Timeline:
3-5 years

Complete rewrite to cloud-native architecture with microservices and modern tech stack.

Frequently Asked Questions

General

What is the primary function of FTPSweeper?

FTPSweeper automates the process of searching for files on remote FTP servers. It can save files locally, output them to JES spool, wrap them in JCL for batch submission, and trigger application processing.

What are some common use cases for FTPSweeper?

FTPSweeper can be used to periodically check FTP servers for the arrival of new files, enabling automated workflows based on file availability.

What types of file processing does FTPSweeper support?

FTPSweeper supports processing files by saving them on the host system, outputting them to JES spool, or wrapping their content in JCL for batch submission.

Technical

How is FTPSweeper configured?

While specific command syntax is not publicly available, FTPSweeper likely uses configuration files to define FTP server connection details, file search criteria, and processing actions.

What is the basic architecture of FTPSweeper?

The architecture likely involves components for FTP communication, file processing, and job submission. These components communicate through internal APIs or messaging queues.

What protocols and ports does FTPSweeper use?

FTPSweeper likely uses standard FTP protocols for communication with remote servers. The specific ports required depend on the FTP server configuration (typically port 21 for FTP and port 990 for FTPS).

Business Value

What business value does FTPSweeper provide?

By automating file transfer and processing, FTPSweeper reduces manual effort and improves the speed and reliability of data integration workflows.

How does FTPSweeper enable real-time data integration?

FTPSweeper can trigger application processing based on file arrival, enabling real-time or near real-time data integration scenarios.

Security

What authentication methods are supported by FTPSweeper?

FTPSweeper likely supports standard FTP authentication methods, such as username/password and potentially certificate-based authentication for FTPS.

How is access control managed in FTPSweeper?

Access control is likely managed through user roles and permissions, potentially using a role-based access control (RBAC) model.

What encryption is used by FTPSweeper?

Encryption is used during file transfer when using FTPS (FTP Secure), which encrypts the data in transit using SSL/TLS protocols.

Operations

What administrative interfaces are available?

Administrative interfaces likely include a command-line interface (CLI) and potentially a web-based console for configuration and monitoring.

What monitoring and logging capabilities exist?

Monitoring and logging capabilities likely include detailed logs of file transfers, processing actions, and any errors encountered.

What are the main configuration parameters?

Configuration parameters likely include FTP server connection details, file selection criteria (e.g., file name patterns, date ranges), and processing options.

Ready to Start Your Migration?

Download our comprehensive migration guide for FTPSweeper or calculate your ROI.

Calculate ROI