Page Comparison

To use the AgileZen connector, add the <agilezen.init> element in your configuration before carrying out any other AgileZen operations. 

Before you start performing various operations with the connector, make sure to import the AgileZen certificate to your ESB client keystore.

Follow the below mentioned steps to add valid certificate to access AgileZen API over https into the ESB client keystore:

1. Extract the certificate from browse by navigating to ' https://agilezen.com ' and click the lock icon on the address bar to view the certificate.
2. Place the downloaded certificate into "AgileZen_CONNECTOR_HOME/src/test/resources/keystores/products" folder.
3. Navigate to "AgileZen_CONNECTOR_HOME/src/test/resources/keystores/products/" using command prompt and execute the following command.

4. This command will import AgileZen certificate in to keystore. Give "wso2carbon" as password.To import the certificate give "wso2carbon" as password. Press "Y" to complete certificate import process.

   Code Block
   keytool -importcert -file CERT_FILE_NAME -keystore wso2carbon.jks -alias -alias "CERT_NAME"

AgileZen uses  API keys to associate requests with the users that are making them. API keys are identified by a token, which is just a unique series of letters and numbers. For more information on authentication, see http://dev.agilezen.com/concepts/authentication.html.

<agilezen.init>
    <apiUrl>{$ctx:apiUrl}</apiUrl>
    <apiKey>{$ctx:apiKey}</apiKey>
    <format>{$ctx:format}</format>
	<enrichments>{$ctx:enrichments}</enrichments>
</agilezen.init>

Properties

• apiUrl:  Base end point URL of the AgileZen API.
• apiKey:  API key to access data of the AgileZen account.
• format:  The format of the response expected from the AgileZen API.
• enrichments:  Addtional data about an entity which the user expects to be returned with the response.

Now that you have connected to AgileZen, use the information in the following topics to perform various operations with the connector. After you have completed your configurations, see Testing the AgileZen Integration .