You're viewing help content for version:
- 6.4
- Older Versions
AEM Forms Data Integration allows you to configure and connect to disparate data sources. The following types are supported out-of-the-box. However, with little customization, you can integrate other data sources as well.
- Relational databases - MySQL, Microsoft SQL Server, IBM DB2, and Oracle RDBMS
- AEM user profile
- RESTful web services
- SOAP-based web services
- OData services
Data integration supports OAuth2.0, Basic Authentication, and API Key authentication types out-of-the-box, and allows implementing custom authentication for accessing web services. While RESTful, SOAP-based, and OData services are configured in AEM Cloud Services, JDBC for relational databases and connector for AEM user profile are configured in AEM web console.
-
In the configuration dialog, specify the details for the database you want to configure, such as:
- Name of the data source
- Data source service property that stores the data source name
- Java class name for the JDBC driver
- JDBC connection URI
- Username and password to establish connection with the JDBC driver
Note:
Ensure that you encrypt sensitive information like passwords before configuring the data source. To encrypt:
- Go to http://[server]:[port]/system/console/crypto.
- In the Plain Text field, specify the password or any string to encrypt and click Protect.
The encrypted text appears in the Protected Text field that you can specify in the configuration.
You can configure AEM user profile using User Profile Connector configuration in AEM Web Console. Do the following:
-
In the User Profile Connector Configuration dialog, you can add, remove, or update user profile properties. The specified properties will be available for use in form data model. Use the following format to specify user profile properties:
name=[property_name_with_location_in_user_profile],type=[property_type]
Examples:
- name=profile/phoneNumber,type=string
- name=profile/empLocation/*/city,type=string
Note:
The * in the above example denotes all nodes under the profile/empLocation/ node in AEM user profile in CRXDE structure. It means that the form data model can access the city property of type string present in any node under the profile/empLocation/ node. However, the nodes that contain the specified property must follow a consistent structure.
Note: Configuration for cloud services folder is required for configuring cloud services for RESTful, SOAP, and OData services.
All cloud service configurations in AEM are consolidated in the /conf folder in AEM repository. By default, the conf folder contains the global folder where you can create cloud service configurations. However, you need to manually enable it for cloud configurations. You can also create additional folders in conf to create and organize cloud service configurations.
To configure the folder for cloud service configurations:
-
Do the following to enable the global folder for cloud configurations or skip this step to create and configure another folder for cloud service configurations.
- In the Configuration Browser, select the global folder and tap Properties.
- In the Configuration Properties dialog, enable Cloud Configurations.
- Tap Save & Close to save the configuration and exit the dialog.
RESTful web service can be described using Swagger specifications in JSON or YAML format in a Swagger definition file. To configure RESTful web service in AEM cloud services, ensure that you have either the Swagger file on your files ystem or the URL where the file is hosted.
Do the following to configure RESTful services:
-
Go to Tools > Cloud Services > Data Sources. Tap to select the folder where you want to create a cloud configuration.
See Configure folder for cloud service configurations for information about creating and configuring a folder for cloud service configurations.
-
Specify the following details for the RESTful service:
- Select URL or File from the Swagger Source drop-down, and accordingly specify the Swagger URL to the Swagger definition file or upload the Swagger file from your local filesystem.
- Select the authentication type — None, OAuth2.0, Basic Authentication, API Key, or Custom Authentication — to access the RESTful service, and accordingly provide details for authentication.
SOAP-based web services are described using Web Services Description Language (WSDL) specifications. To configure SOAP-based web service in AEM cloud services, ensure that you have the WSDL URL for the web service, and do the following:
-
Go to Tools > Cloud Services > Data Sources. Tap to select the folder where you want to create a cloud configuration.
See Configure folder for cloud service configurations for information about creating and configuring a folder for cloud service configurations.
An OData service is identified by its service root URL. To configure an OData service in AEM cloud services, ensure that you have service root URL for the service, and do the following:
Note:
For step-by-step guide to configure Microsoft Dynamics 365, online or on-premises, see Microsoft Dynamics OData Configuration.
-
Go to Tools > Cloud Services > Data Sources. Tap to select the folder where you want to create a cloud configuration.
See Configure folder for cloud service configurations for information about creating and configuring a folder for cloud service configurations.
-
Specify the following details for the OData service:
- Service Root URL for the OData service to be configured.
- Select the authentication type — None, OAuth2.0, Basic Authentication, or Custom Authentication — to access the OData service, and accordingly provide the details for authentication.
Note:
You must select OAuth 2.0 authentication type to connect with Microsoft Dynamics services using OData endpoint as the service root.
You have configured the data sources. Next you can create a form data model or if you have already created a form data model without a data source, you can associate it with the data sources you just configured. See Create form data model for details.
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.