- REST Connection Supports for uploading complex XML schema definitions as a zipped archive to define data definitions for XML content during REST Adapter configuration. See Complex Schema Support.
- REST Connection Support for uploading sample XML documents to define data definitions for XML content during REST Adapter configuration. The following XML documents are supported for schema generation:
- XML with no namespace.
- XML with a homogenous namespace.
- XML files up to 3 MB in size.
- Supports configuration of the following:
- Relative resource URI.
- Support for HTTP methods GET, PUT, POST, DELETE, and PATCH.
- Template and query parameters.
- Support for a request/response payload.
- Support for JSON, XML, binary (inline and unstructured), and URL-form-encoded payloads.
- Support for homogenous JSON arrays including top-level arrays.
- Support for multidimensional JSON arrays (see Homogenous Multidimensional Array Support in JSON Documents).
- REST APIs exposed using the REST Adapterare secured using Basic Authentication, OAuth token-based authentication, and JWT-based authentication.
- REST APIs implement the HTTPS protocol, thereby enforcing all incoming requests to have transport level security.
- REST APIs exposed using the REST Adapter are protected using Basic Authentication and OAuth token-based authentication.
- Login to Integration Cloud Service and click on connections. Once it start displaying all connections. Click on create button.
- Search for REST adapter and click on select button. It will open the screen to provide the different parameter for REST.
- Provide Connection Name, and Role I have opt for trigger and invoke both. Once done click on create button.
Configurations
- In the next screen provide the information about the connection, I have used a open REST API available. If you are just doing to test or learn use the same, or can use any api available openly. Please use following page to check API available.
Security
- Please provide any user name password required to login to this API. I am using open API hence there is no security configuration required. Hence I used "No Security Policy".
No comments:
Post a Comment