--- title: Enabling Camel service connections description: If your PingAuthorize implementation relies on Apache Camel, you can enable Camel for both embedded and external policy decision point (PDP) modes. component: pingauthorize version: 11.0 page_id: pingauthorize:pingauthorize_policy_administration_guide:paz_camel_enable canonical_url: https://docs.pingidentity.com/pingauthorize/11.0/pingauthorize_policy_administration_guide/paz_camel_enable.html revdate: May 14, 2025 section_ids: before-you-begin: Before you begin steps: Steps choose-from: Choose from: result: Result camel-services: Camel services camel-settings: Camel settings value-processors: Value processors --- # Enabling Camel service connections If your PingAuthorize implementation relies on Apache Camel, you can enable Camel for both [embedded](../pingauthorize_server_administration_guide/paz_config_embedded_pdp.html) and [external policy decision point](../pingauthorize_server_administration_guide/paz_config_external_pdp.html) (PDP) modes. To ensure that Camel is used with appropriate permissions and security controls, Camel services are disabled by default in the Policy Editor. Starting with PingAuthorize 10.3, you can use Camel version 4.0. * Learn how to upgrade PingAuthorize versions 10.0-10.2 using Camel 3.x in the Apache Camel 3.x to 4.0 [migration guide](https://camel.apache.org/manual/camel-4-migration-guide.html). | | | | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | If you upgrade an existing installation of PingAuthorize to version 9.3.0.0 or later, and the earlier version was configured in embedded PDP mode with a deployment package containing Camel services, the upgraded PingAuthorize server will fail to start. The following steps also resolve this issue. | ## Before you begin You must install the Policy Editor and the PingAuthorize server before enabling Camel services. ## Steps 1. In the PingAuthorize Server distribution, copy the `symphonic-camel-pdp-.jar` file from `resource/camel` to the `lib` folder. 2. In the Policy Editor distribution, copy the `symphonic-camel-pap-.jar` file from `resource/camel` to the `admin-point-application/lib` folder. 3. Enable the Camel service. ### Choose from: * Run `setup` in [non-interactive mode](../installing_and_uninstalling_pingauthorize/paz_install_pe_noninteractive.html) using the `--enableCamelService` argument. ```shell $ bin/setup demo \ --adminUsername admin \ --generateSelfSignedCertificate \ --decisionPointSharedSecret pingauthorize \ --hostname \ --port \ --adminPort \ --licenseKeyFile \ --optionsFile my-options.yml \ --enableCamelService ``` | | | | - | ----------------------------------------------------- | | | This choice will override the existing configuration. | * In your Policy Editor distribution, add the `- "camel-service"` flag to `enabledFeatures` in the `config/configuration.yml` file. ``` enabledFeatures: - "test-suite" - "entity-dependents" - "camel-service" ``` 4. Save your changes and restart the Policy Editor. ## Result Camel service connections are enabled in both external and embedded PDP modes. ## Camel services You can retrieve information from any endpoint that the [Apache Camel](https://camel.apache.org/) enterprise integration platform supports. The [list of Camel components](https://camel.apache.org/components/latest/) in the Camel documentation provides the full list of supported systems. Configure Camel components by using a combination of **URI**, **Headers**, **Body**, and **Configuration** settings. The appropriate values to provide for each setting depend on the component being used. You can make requests dynamic by interpolating attribute values into different parameters. Learn more in [Attribute interpolation](paz_attribute_interpolation.html). ### Camel settings ![Screen capture of the Camel service settings](_images/rzl1717436799828.png) | Setting | Description | | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **URI** | The identifier for the Camel endpoint. PingAuthorize can interpolate attribute values into this field. | | **Headers** | Additional information to send with the Camel service request. PingAuthorize can interpolate attribute values into this field. | | **Body** | The body to send with the Camel service request. PingAuthorize can interpolate attribute values into this field. | | **Configuration** | Some Camel components require you to configure helper components for them to work. Specify these components by using the [Groovy](https://www.groovy-lang.org/) scripting language to write a Spring Bean configuration block. Learn more about writing configurations in [Class GroovyBeanDefinitionReader](https://docs.spring.io/spring-framework/docs/4.3.13.RELEASE/javadoc-api/org/springframework/beans/factory/groovy/GroovyBeanDefinitionReader.html).PingAuthorize cannot interpolate attributes into this field. | | | | | - | -------------------------------------------------------------------------------------------------------------------------------------------------- | | | The Camel JDBC component uses the **Headers** and **Body** settings and requires a JDBC data source to be set up in the **Configuration** setting. | ### Value processors You can define value processors to transform data returned by the Camel service. Learn more in [Processors](paz_value_processing.html).