Difference between revisions of "I2Rest Server"
Line 13: | Line 13: | ||
*** Hardware SSL protection | *** Hardware SSL protection | ||
*** Native calls for existing RPGLE code | *** Native calls for existing RPGLE code | ||
+ | *** NEW! Support for packed HTTP requests/responses using gzip/deflate encoding (premium only) | ||
---- | ---- |
Latest revision as of 12:44, 2 July 2021
- Ready to use IBM i native REST JSON Web Server
- Any non-interactive RPGLE program can become fully functional OpenAPI in a minutes
- Automatic creation of Swagger 2.0 and OpenAPI 3.0 API description files
- Native OAuth2 server implementation
- Authorization code/Device/Client credentials/Refresh token flows
- Pluggable security model
- Simple, performant and lightweight (black box – interaction only via REST)
- No Java, No PASE
- Native IBM i implementation
- Security/ authentication
- Hardware SSL protection
- Native calls for existing RPGLE code
- NEW! Support for packed HTTP requests/responses using gzip/deflate encoding (premium only)
Please follow our quick start guide with basic instructions how to start serving your first API using i2Rest Server:
- i2Rest Server installation guide
- i2Rest Server configuration in two steps
- How to start i2Rest Server instance
- How to test basic implementation
Our advanced level guide will show you everything you need to use all i2Rest Server capabilities
For further information, please look at
- i2Rest Server architecture
- i2Rest Server configuration options
- i2Rest Server APIs
- i2Rest Server how to convert programs to APIs
- i2Rest Server performance
- i2Rest Server and IBM IWS
- Category:API CookBook
And do not hesitate to contact us!