You're viewing Apigee Edge documentation.
Go to the Apigee X documentation. info
To use samples, you should also have the following:
|The samples are located on GitHub. If you do not have Git installed, please refer to GitHub's git setup instructions. If you don't want to install Git, you can browse the files and download a ZIP from https://github.com/apigee/api-platform-samples.
Python is required to run the Apigee deploy tool. Python is present in most Linux environments, on a Mac with XCode installed, on a Windows machine with Cygwin installed, and in many other places.
To obtain Python, please refer to the Python download page.
|The sample setup scripts also use
curl. Make sure
curl is installed and
available on your path (run the
which curl command to see if it's available on
|If you're running Cygwin on Windows, you may also need the
utility. (The Cygwin installer lets you install the utility.)
Download the samples
To obtain the sample files, use
git clone as the following example shows:
git clone https://github.com/apigee/api-platform-samples.git
Import and deploy the sample API proxies
Import and deploy the samples from the command line:
- After you download the samples, go to the
/setupdirectory, as the following example shows:
- In the
/setupdirectory, locate the file
- Edit this file to set your organization, the email address associated with your username, and the environment (prod or test) where you want to deploy the API proxies.
- After you edit
setenv.sh, execute the following:
This script deploys all API proxy samples to your organization. (The process takes 3-4 minutes.) Follow prompts to deploy API products, developers, and apps (which are used for OAuth).
- After the deploy script completes, navigate to the sample-proxies directory. In the
sample-proxies, you will find one directory per sample proxy. In each directory is a README.md file with information about running the sample, and two scripts that help you as you make small changes to the samples, deploy, and then invoke the sample to see what effect you change had:
invoke.sh: Execute this script to invoke the deployed version of the API proxy.
deploy.sh: Execute this script to deploy the API proxy after you make any changes.
Invoke the sample API proxies
Each sample proxy has an associated shell script that can be used to invoke the API proxy after you deploy it.
/sample-proxies/proxy_name directory, execute the
This invokes the proxy that is running in the test environment in your organization.
For troubleshooting information, see the following:
Modify and reuse the sample API proxies
Typical usage of the sample proxies is to modify, deploy, and invoke. This enables you to make small modifications, and then to see what effect they have on the response message.
To modify a sample API proxy to point at a different backend service, modify the XML configuration file in the following location:
For example, to point the API key sample at your own backend service, locate this file:
If the default configuration points to
http://mocktarget.apigee.net, such as:
<TargetEndpoint name="default"> <HTTPTargetConnection> <!-- This is where we define the target. For this sample we just use a simple URL. --> <URL>http://mocktarget.apigee.net</URL> </HTTPTargetConnection> </TargetEndpoint>
and your backend service is available at
http://api.myproject.com/, then you
modify the configuration to look like the following:
<TargetEndpoint name="default"> <HTTPTargetConnection> <!-- This is where we define the target. For this sample we just use a simple URL. --> <URL>http://api.myproject.com/</URL> </HTTPTargetConnection> </TargetEndpoint>
After you have saved your changes, deploy the API proxy as the following example shows:
The other API proxies can be modified the same way in order to use the API proxy functionality against your existing target services. In some cases, however, API proxy behavior is dependent on specific message formats, so the proxies might need additional configuration changes.