Difference between revisions of "I2Rest vs IWS"
(Created page with "{{DISPLAYTITLE:i2Rest Server and IBM IWS}} i2Rest Server functionality is very similar to IBM Integrated Web Services. Both products allow you to turn RPGLE...") |
|||
| Line 36: | Line 36: | ||
|style="padding: 5px"|Authorization code, Client credentials, Refresh token, Device code | |style="padding: 5px"|Authorization code, Client credentials, Refresh token, Device code | ||
|style="padding: 5px"|None | |style="padding: 5px"|None | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
Revision as of 17:58, 14 June 2021
i2Rest Server functionality is very similar to IBM Integrated Web Services. Both products allow you to turn RPGLE programs into services without modifications. However, the i2Rest Server is an independent product that differs significantly from the IBM IWS
In short, there are two main differences:
- Full support of OAuth2 authorization flows
- Higher performance
These differences are shown in more detail in the table below.
| i2Rest Server | IBM Integrated Web Services | |
| Architecture & implementation details | ||
| Server engine | Native implementation of high performant multi threaded HTTP(s) web server (based on gSOAP toolkit) | IBM HTTP(s) Server for IBM i, based on Apache Tomcat |
| Development language | IBM ILE C | Java |
| OpenAPI specification support | 2.0 (swagger), 3.0 (OpenAPI) | 2.0 (swagger) |
| User authentication | None, OAuth2 token (Bearer), HTTP Basic, SSL certificate | None, HTTP Basic |
| User authorization | Provided by OS + OAuth2 scopes or custom authorization model | Provided by OS |
| Supported OAuth2 flows | Authorization code, Client credentials, Refresh token, Device code | None |
