If you want to use Open API 3.0 with HTTP/2 agents, you require an Open API profile configuration. You select the profile that you configure in the HTTP/2 Server agent configuration. In the Open API profile configuration, you import your OpenAPI specification file and view any other included files defined by the specification.
| Note | ||
|---|---|---|
| ||
All schemas that require a UDR must be named. Due to a limitation in the third party parsing library used by OpenAPI, unnamed schemas cannot be detected and will not generate a corresponding UDR. Therefore, you must name all schemas that require a UDR. |
| Note | ||
|---|---|---|
| ||
For the old Open API Profile used for the REST Server and Client agents in versions before 8.1.8.0, see /wiki/spaces/MD82/pages/3783710. |
...
| Warning | ||
|---|---|---|
| ||
If you have been using the Open API Profile before version 8.1.8.0 and are using OpenAPI 2.0. You must convert from OpenAPI 2.0 to OpenAPI 3.0, before using the Open API Profile from version 8.1.8.0 onwards. |
Configuration Tab
| Setting | Description | |||||
|---|---|---|---|---|---|---|
| Open API file | Import the OpenAPI specification file from where the desktop client is running. Upon successful import, the contents of the file will be displayed in the box below.
|
...
| Note | ||
|---|---|---|
| ||
To refresh the content of the imported API file or the contents of other included files, the imported file will have to be imported once again. |
View Included Files Tab
| Setting | Description |
|---|---|
| Included Files | A list of files that are referenced in the imported OpenAPI specification file will be shown here. Selecting from this list will have its contents be displayed in the box below. |
...