Managing resources

This page applies to Apigee and Apigee hybrid.

View Apigee Edge documentation.

Note: Use local development with Apigee and Apigee hybrid 1.5 and higher.

Many policy types rely on resources. Resources are the files that implement the code or configuration to be executed by a policy when attached to an API proxy. For more information about and examples of resources, including the list of resource types supported, see About resources.

Create resources at the API proxy, shared flow, or environment level and then access them from policy, as described in the following sections. See also Managing folders and files in an Apigee workspace.

Creating a resource

To create a resource using Apigee in Cloud Code:

1. In the Apigee section, perform one of the following actions based on the level at which you want to store the resource. For more information, see Where resources are stored.

   Level	Step
   API proxy	Perform one of the following actions: Position your cursor over one of the following folders, click , and select Create resource: apiproxy-name proxy bundle apiproxy-name/apiproxy Position your cursor over the apiproxy-name/apiproxy/resources folder for the API proxy and click .
   Shared flow	Perform one of the following actions: Position your cursor over one of the following folders, click , and select Create resource: sharedflow-name shared flow bundle sharedflow-name/sharedflowbundle Position your cursor over the sharedflow-name/sharedflowbundle/resources folder for the shared flow and click .
   Environment	Perform one of the following actions: Position your cursor over the env-name environment folder, click , and select Create resource. Position your cursor over the env-name/resources folder for the environment and click .

   The Create resource wizard opens.

2. Select the resource type that you want to create from the list.
   For a description of the resource types supported, see Resource types.

   Note: You must import JAR files.

3. Enter a unique name for the resource and press Enter.

   Note: Do not specify the file extension. An extension will be appended automatically based on the resource type.

   The resource is added to the resources folder in the apiproxies, sharedflows, or environments folder in the Apigee section and opened for editing.

4. Edit the resource file, as required, and select File > Save or ⌘S to save your edits.

Importing a resource

To import a resource using Apigee in Cloud Code:

1. In the Apigee section, perform one of the following actions based on the level at which you want to store the resource. For more information, see Where resources are stored.

   Level	Step
   API proxy	Perform one of the following actions: Position your cursor over the apiproxy-name/apiproxy folder and click . Position your cursor over the apiproxy-name/apiproxy/resources folder for the API proxy and click .
   Shared flow	Perform one of the following actions: Position your cursor over the sharedflow-name/sharedflowbundle folder and click . Position your cursor over the sharedflow-name/sharedflowbundle/resources folder for the shared flow and click .
   Environment	Perform one of the following actions: Position your cursor over the env-name environment folder and click . Position your cursor over the env-name/resources folder for the environment and click .

   The Import resource wizard opens.

2. Select the resource type that you want to import from the list. For a description of the resource types supported, see Resource types.

   Note: For JAR files, select java callout jar.

3. Navigate to the file in your local directory and click Import.

4. Enter a unique name for the resource and press Enter.

   Note: Do not specify the file extension. An extension will be appended automatically based on the resource type.

   The resource is added to the resources folder in the Apigee Explorer and opened for editing.

Accessing the resource from a policy

How you access the resource from a policy depends on the resource type. For more information, refer to the Policy reference overview. For an example of accessing the resource from a policy, see Accessing the resource.