From REST or HTTP Service

This option allows the addition of a proxy project to existing backend REST or HTTP services which can be used for request types: REST or HTTP respectively.

Adding a REST/HTTP Service project

To add a REST/HTTP Service project, click the Addicon and click the From REST/HTTP Service option.

Providing Basic Attributes

Enter values for attributes following descriptions in the table below.

Property	Description
Project display name	Provide a name to represent and identify the 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.
Use proxy as endpoint	Use this option if proxy requests are not to be forwarded to the target.
Target backend service URL	URL of the service provider from where data is to be fetched after implementing the policies that are defined.
Target method	HTTP method used by the back end Service to send requests by using the following methods: GET: Requests data from a specified resource POST: Submits data to be processed to a specified resource PUT: Uploads a representation of the specified URI DELETE: Deletes the specified resource PROXY: The same method that the client uses to invoke the proxy server will be used to invoke the target server. PATCH: Requests a set of modifications in the request entity to be applied for the resource recognized by the Request-URI. Executing partial changes in the resource helps improve interoperability and prevent errors. HEAD: Asks for a response identical to a GET request, but without the response body. HEAD is much faster than GET, as the amount of data transferred is less. It's often used by clients who use caching, to see if the document has changed since it was last accessed. TRACE: Returns a diagnostic trace that logs data from the request-response cycle. This method is generally used for diagnostics, debugging and troubleshooting purposes.
Proxy context path	This is a text used to combine with the version number to act as an identifier to map a deployed project. The proxy resolves context path mappings prior to applying any matching policies (explained in subsequent topics). Proxy Context Path combined with version number must be unique for every project. Different versions of the same project (same project name with different version number) can have the same Context Path.
Proxy method	HTTP method used by the application to send requests to the proxy by using the methods GET/POST/PUT/DELETE/PATCH/HEAD/TRACE as explained previously. Refer to the descriptions for each method in the Target method row above.

After entering the above details, you may click Finish to create the project, or click Next to:

Add Security policy or add Quota policy.
Attach an existing product to this new project.

API Customization - Enabling Security and Quota

Generally, policies are created for a project after adding the project, while Security policy and Quota policy can be created while creating a project as well. To do this, click Next and select the attributes as described in the table below.

Property

Description

Secure API with

Enables security to the requests with the following security options:

None: No authentication checks will be done.
API Keys: Checks for the authentication key which gets generated for an API Product.
OAuth 2.0 access tokens: Protocol used for authentication and authorization.

Enforce Quota

Whether or not to enable the default Quota policy.

After entering the above details, click:

Finish to create the project
Next to attach a product to this new project.

To amend the basic details entered, click the Previous button to move back to the first screen.

Product Mapping - Attaching a Product to the Project

Select a product to attach to the project from the existing projects listed under the Attach to API products drop-down and click Finish to save the project. The project gets added to the API Projects screen.

The project gets added to the API Projects