Automate generation of boilerplate API and Consumer RPGLE & SQL code from any integration requirementmore
Add RPGLE business logic to layered architecture for low code maintenance without limiting flexibility.more
Wizards & GUI to build & edit API specs & export to API Developer Portal & Confluence documentation.more
REST4i is one of the slickest tools I have seen on the IBM i in many years.
I've been an RPG programmer for a long time, and it (REST4i) taps into the power of the IBM i like no other tool I've seen.
REST4i has worked even better than we could have hoped for. Our API strategy has leaped years ahead.
We had our first REST service running on our IBM i within an hour of downloading REST4i.
Generate REST API and Consumer programs from all typical requirement definitions.
RPGLE logic generated includes, data-structures/defintions, parsers, JSON/XML writing, assignments, SQL/IO, error-handling, logging, analytics, SSL/TLS, OAuth/JWT, mapped to API Payloads, Parameters and all REST Methods
Generators exposed as IBM i commands & REST API's, with customizable templates and examples for each typical use case.
Web based GUI for editing, collaboration, documentation, with exit-points for integration with mainstream work-flow, DEVOps and API management systems: Jira/GitHub/Mulesoft/API Connect/SCM etc.
Rest4i has layered RPGLE architecture that hides commonly-used communication, security and parsing logic in the copied/generated programs.
Developers need only use RPG ILE & SQL for their primary purpose and proven skill set: Business Logic and Input/Output of mission critical data
For more advanced developers, Rest4i embeds a rich set of RPGLE functions and source to allow extension to even the most sophisticated, and complex requirements.
Interactive documentation of API & consumer specification, with built-in testing capabilities.
Automatically generated from your OpenAPI (formerly known as Swagger) Specification, with the visual documentation used for back-end generation and client side consumption.view
Generate editable developer and user documentation into standard user templates. Separate into environments for multiple user groups
One web UI for internal developer collaboration & one for self-service API developer and consumer documentationview
From your Open API specs, generate beautiful, interactive documentation in your Confluence pages
Integrate API, application and business documentation into a single portal for partner, internal developer, or external consumption of your API'sview
A Rich web UI to manage, edit & generate RPGLE code from Open-API (Swagger) specifications & definitions.
REST API (developed on IBM i using iCore) that uses OAS3 (SWAGGER), definitions to generate RPGLE API's and Consumers
IBM i commands, examples & templates in RPGLE, for each typical use case for manually building API's and Consumers.
Eclipse/RDi plug-in from Remain-Software.A full OAS3 spec compliant OpenAPI development environment.
It includes a rich editor with API testing, import, export and code generation (using Rest4i Accelerator REST API) & contains built-in documentation for all parts of the spec.
Eclipse/RDi plug-in from Midrange-Dynamics.
Integrated with MDCMS Object Request user actions in MDOpen RDi Plug-in, iCore's IBM i commands are exposed in a rich, Eclipse-UI environment
A set of RPGLE REST API's integrated with Rest4i Accelerator, over MDCMS (built using iCore), that expose key integration points in the MDCMS flow, & change management data and processes.
No middleware, code abstractions, or connectivity drivers. Lean, performance optimized code structure for parsing and translations = lightening quick response times
Layered code architecture using typical RPGLE constructs and concepts, hides complex code while standardizing flow where possible. Low code maintenance without limiting flexibility
Structured code makes development and maintenance of code consistent, easier to learn and debug. Changes are quicker to design, code & test. Also allows automated-unit testing.
Structured code architecture makes code generation possible. Accelerate development effort rather than replacing it. Templates allow scalable flexibility without limitations
Structured code architecture makes code documentation easier and facilitates LXR-Auto documentation. API docs are critical for benefits associated with self-service economies
LXR follows industry standards by default. This lowers risk during code transformation and improves re-usability. It also makes training of new staff more cost-effective & efficient