RIM projects are used to create APIs from an RIM file format which is a conceptual level language that API projects can be created from RIM file(s) using this option. RIM specification allows you to quickly and easily create define REST APIs as per HATEOS principles.
| Tip |
|---|
For more information about RIM file formatspecification, refer the link: https://github.com/temenostech/IRIS/wiki/introduction#overview |
...
Property | Description | ||
|---|---|---|---|
| Display Name | A name to act as Project ID to identify the RIM project. | ||
| Version | Revision number of the project, for example, 1.0 for a project being newly added and 1.1 or 2.0 for the next revision. | ||
| Proxy Context Path | A text used to combine with the version number to act as an identifier to map with a particular deployed project. The proxy resolves context path mappings prior to applying any matching policies (explained in subsequent topics).
| ||
| Target Base Path | Target server URL where the app needs to use the service. | ||
| Load .rim/.zip | Click Choose File button to browse and choose the RIM file or the VIP ZIP file where RIM files are compressed. If the RIM files are part of directory structure, they can be zipped retaining the folder structure and the zip file can be provided as input. |
When a RIM file or ZIP containing RIM files is loaded, the different resources that are part of the RIM(s) provided are listed. API Author can choose the resources which have to be part of the project being defined.
| Note |
|---|
After clicking next from here, you may perform API Customization and Product Mapping in the subsequent screens. Refer the respective sections in From REST/HTTP Service section. |
...