Configuring a REST V2 Resource
You can use the URL template-based approach to configure REST resources. In this approach, you define a URL template for client requests to use and invoke the resources.
REST resources configured using this approach, also known as REST V2 resources, are invoked with the restv2 directive. For each resource, you must define operations and attributes. Resource operations include the following:
The format of the URL that REST clients must follow when sending requests to
Integration Server acting as the REST server.
Integration Server attempts to match a request URL received from any application against the URL template defined for a REST V2 resource operation and determines whether the request URL is valid.
The HTTP methods supported by the REST resource.
The service associated with a resource operation. You can either associate an existing service with a resource operation or create a new service and associate it with the resource operation.
You can use the URL template-based approach to configure REST V2 resources. In this approach, you define a URL template that serves as a template for client requests to use and invoke the resources.
The URL template-based approach provides you greater flexibility than the legacy approach in defining REST V2 resources. For a REST V2 resource, you can define multiple operations and associate each operation with a URL template, HTTP methods, and a service. In addition, you can edit these details based on your requirements.
Note:
The supported associated services are, Flow service, Java service, C service, or Adapter service.
A REST V2 resource is represented by the
icon in the
Package Navigator view.
You
cannot configure REST V2 resources when
Integration Server is deployed in a multitenanted environment.