The Challenge
Working with the Integrated File System (IFS) on IBM i is nothing new—but exposing those file operations as APIs has usually meant extra effort. Teams often rely on scripts, custom logic, or external tools just to handle fairly simple read and write use cases.
What’s New
Rocket API 10.6.3 introduces native IFS support, making it much easier to turn file operations into APIs.
Two additions make this possible:
- IFS Connector – Connects securely to the IBM i file system
- IFS Microflows – Handle reading and writing files with configurable options like append mode and access control
There’s also support for mapping the entire request body directly to a microflow, which simplifies writing incoming API request straight to a file.
How It Works
The setup is quick:
- Create an API library
- Configure the IFS connector
- Import and define an IFS microflow (file path, options)
- Expose it via REST (for example, POST for write)
- Publish and deploy
Within a few steps, file-based operations are available as APIs.
Why It Matters
This removes a lot of the friction around IBM i integrations:
- No external dependencies
- Less custom code
- Faster API development
It’s especially useful for common scenarios like file-based integrations or lightweight data pipelines.
See It in Action
🎥 Watch the demo to see - How quickly IFS-based APIs can be configured and deployed using Rocket API
Closing Thought
IFS support in Rocket API 10.6.3 isn’t about adding complexity—it’s about removing it. If you’re already working with file-based workflows on IBM i, this is a straightforward way to bring them into your API landscape.
