Data source connected systems contain authentication and connection information for data sources, allowing you to connect supported databases to Appian.
This page provides details about data source connected systems. For information that pertains to all connected systems, see Connected System Object.
When you create a connected system, you can choose any Appian-supported database to connect to. The following data sources are available when creating a connected system:
You can also connect to data sources in the Admin Console. Most of the time, you will want to use a connected system. However, there are certain cases where you will need to use the Admin Console.
We highly recommend using data source connected systems to take advantage of the following benefits:
If you are using a plug-in that needs to connect to a data source, you can reference that data source by using the a!getDataSourceForPlugin function.
If you decide to migrate your data sources from the Admin Console to a connected system, keep in mind that you will have to update any objects that refer to the data source.
These objects include:
Additionally, if you are using the data source for the default Quick Apps data source in the Admin Console, you will have to update that data source in the Admin Console.
If you are using the Appian Cloud database, members of the Database Administrators group can create new schemas in the database which generates credentials. You can use these credentials to create MariaDB data source connected systems to connect to the newly created schemas. You can then give certain developers access to certain schemas.
For example, you may want to restrict access to human resources data to developers who are specifically working on human resources applications. Furthermore, you may want to give developers access to this data in development environments, but restrict access in testing and production environments.
To learn more about creating schemas in the Appian Cloud database to control access to data, see Appian Cloud Database Administration.
Keep the following caveats in mind when deploying data source connected systems between environments.
If your application includes a data source connected system, the data source connected system object must exist in the target environment before you can run database scripts against it. Furthermore, when a data source connected system object is a part of a direct deployment, you cannot run database scripts for that data source in the same deployment.
As a result, there are additional considerations for direct deployments if you're creating or updating a data source connected system object and deploying database scripts at the same time.
For these specific deployments, perform the following two-part process:
If you are using additional schemas in the Appian Cloud database to control access to data, each schema has a different database user. This database user doesn't have access to other schemas in the environment, but it does have access to the default "Appian" schema.
Compare and deploy uses the database user for the Data Source that is selected. Therefore, if you are using compare and deploy to run SQL scripts, make sure you don't try to update any additional schemas.
Data source connected systems have the following properties:
|Name||The name of the data source that will appear in the Appian design objects, such as data store objects.|
|Description||Supplemental information about the connected system.|
|Connection URL*||The URL for the data source. Should include: the hostname, port, and database name of the data source. However, the exact syntax will vary by database type. If you do not know the URL for the data source, consult your database administrator. Refer to Configuring Relational Databases for special considerations when configuring databases for use with Appian.|
|Username*||The username for connecting to the data source.|
|Password*||The password for connecting to the data source. The password will be stored in an encrypted format.|
|Maximum Connection Pool Size*||The maximum number of active connections to the database that can be allocated from this data source at the same time. The default is 200.
Since there is a limited number of connections that applications can make to the database, this field prevents one connected system from hogging the entire connection pool. You can raise or lower this number to control the number of connection pools for a data source.
For example, if you have a data source for an application with low usage, you can lower this number to further limit the number of connection pools for the application. This would prevent the application from taking up too many resources.
*This value is included in import customization files so that you can specify a different value for each environment.
On This Page