Now that you've tested your new proxy, you're almost ready to add a policy to it. Before you do that, though, change your proxy's target endpoint to one that returns some data.
Recall that in Step 1: Create an API proxy, you set the
target endpoint (in the Existing API field) to
Well, that endpoint doesn't return any interesting data, so now you'll change the endpoint to one that returns
To change your proxy's target endpoint:
- Sign in to the Apigee UI.
- Select Develop > API Proxies.
- Select your proxy from the list to display the API proxy details. If you don't see your proxy in the list, be sure that you selected the right organization, as described in Switching between organizations.
Click the Develop tab:
This takes you to the API Proxy Editor. The Proxy Editor lets you see the structure of your API proxy and configure its flow. (A flow is just the stepwise path an API proxy request takes through the Apigee platform. Other tutorials will cover the concept of flows.)
- In the Navigator pane, select Target Endpoints >
Apigee displays the endpoint settings in the Code pane:
<TargetEndpoint name="default"> <Description/> <FaultRules/> <PreFlow name="PreFlow"> <Request/> <Response/> </PreFlow> <PostFlow name="PostFlow"> <Request/> <Response/> </PostFlow> <Flows/> <HTTPTargetConnection> <Properties/> <URL>https://mocktarget.apigee.net</URL> </HTTPTargetConnection> </TargetEndpoint>
The target endpoint is defined by the
Change the URL to "https://mocktarget.apigee.net/xml". (Append "/xml" to the existing URL.)
The new URL returns a small block of XML in the body of the response.
Your endpoint configuration should now look like the following:
... <HTTPTargetConnection> <Properties/> <URL>https://mocktarget.apigee.net/xml</URL> </HTTPTargetConnection> ...
To save your changes to the proxy configuration, click the Save button.
Apigee saves your changes in a new proxy revision.
- To deploy the new revision, select Deploy to: test and click Deploy 2.
- In the confirmation dialog, click Deploy.
If there is an error, Apigee will save your changes but not deploy the proxy. In the case of an error:
- Fix your proxy configuration. Apigee may provide syntax guidance as a pop-up.
- Manually deploy your changes to the
testenvironment by clicking Deployment > test if Apigee does not automatically deploy it.
You can check if your proxy was deployed successfully by selecting the Deployment drop-down above the Flow editor. A green button indicates that the proxy was deployed to that environment successfully:
Test your changes by sending a request to your proxy, just like you did in Step 3: Test your new proxy. For example:
curl https://apitest.acme.com/getstarted | xmllint --format -
This time, the mocktarget endpoint returns XML in the body of the response:
<?xml version="1.0" encoding="UTF-8"?> <root> <city>San Jose</city> <firstName>John</firstName> <lastName>Doe</lastName> <state>CA</state> </root>
Now that the API proxy returns XML data, in the next step you will add a policy that converts XML to JSON.