Using Camel to connect policy information points (PIPs) to PingAuthorize has been deprecated and is no longer supported. You should use HTTP services instead, where applicable.
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 that is used. See the documentation on the Camel website for the particular component that you want to use.
You can make requests dynamic by interpolating attribute values into different parameters. See Attribute interpolation.
URIs identify Camel endpoints. As well as identifying the system, URIs can specify configuration options for components. For information about configuring a URI for the component to which you want to connect, go to the Apache Camel website. The system can interpolate attribute values anywhere in the field.
You can send additional information to the external policy information provider by using Camel headers. If the component to which you will connect uses headers, you can read more about them in the instructions for your component on the Apache Camel website. The system can interpolate attribute values anywhere in the field.
Some Camel components operate on a message body, which you can provide by using this setting. If the component to which you will connect requires a message body, you can read more about it in the instructions for your component on the Apache Camel website. The system can interpolate attribute values anywhere in the field.
Some Camel components require you to configure helper components for them to work. Specify these components by using the Groovy scripting language to write a Spring Bean configuration block. For information about writing such a configuration, go to Class GroovyBeanDefinitionReader.
The system cannot interpolate attribute values into the configuration.
The Camel JDBC component makes use of the Headers and Body settings, and requires a JDBC data source to be set up in the Camel Configuration setting.