Settings Tab
Connector Details
Settings that determine how the API can be accessed.Connection
Settings related to the database connection. Click Add Connection to configure a connection.Tables Tab
The Tables tab lists all API resources exposed by the connector. Each resource is generated from a table or view present in the connected database. Adding a new table or view exposes new database data to a web API call via the connector. See API Resources for details.Stored Procedures Tab
The Stored Procedures tab lists all API actions exposed by the connector. Each action is generated from a stored procedure present in the connected database. Adding a new stored procedure exposes new database data to a web API call via the connector. See API Actions for details.Users Tab
The Users tab lists all users authorized to make API calls to the connector. It lets you:- Create users with their associated authtokens and OAuth 2.0 credentials
- Define HTTP method privileges (GET, POST, PUT, MERGE, PATCH, and DELETE)
- Specify how many requests each user can make per hour
- Specify how many concurrent requests are permitted
The request settings here override settings in the Default Rate Limits section of the Server tab.
Server Tab
Trusted IP Addresses
Default Rate Limits (Per User)
Settings restricting the number of API requests allowed. See Rate Limiting for more information.Cross-Origin Resource Sharing (CORS)
Settings governing the use of CORS to serve cross-origin resources.OData
Settings related to OData feature support.Advanced Tab
Message
Logging
Miscellaneous
Miscellaneous settings are for specific use cases.Alerts Tab
Settings related to configuring alerts. Before you can execute Service Level Agreements (SLAs), you need to set up email alerts for notifications. By default, Arc uses the global settings on the Alerts tab. To use other settings for this connector, toggle Override global setting on. By default, error alerts are enabled, which means that emails are sent whenever there is an error. To turn them off, uncheck the Enable checkbox. Enter a Subject (mandatory), then optionally enter a comma-separated list of Recipient emails.SLAs Tab
Settings related to configuring Service Level Agreements (SLAs). SLAs enable you to configure the volume you expect connectors in your flow to send or receive, and to set the time frame in which you expect that volume to be met. CData Arc sends emails to warn the user when an SLA is not met, and marks the SLA as At Risk, which means that if the SLA is not met soon, it will be marked as Violated. This gives the user an opportunity to step in and determine the reasons the SLA is not being met, and to take appropriate actions. If the SLA is still not met at the end of the at-risk time period, the SLA is marked as violated, and the user is notified again. To define an SLA, toggle Expected Volume on, then click the Settings tab.- If your connector has separate send and receive actions, use the radio buttons to specify which direction the SLA pertains to.
- In the Expect at least portion of the window:
- Set the minimum number of transactions you expect to be processed (the volume)
- Use the Every fields to specify the time frame
- Indicate when the SLA should go into effect. If you choose Starting on, complete the date and time fields.
- Check the boxes for the days of the week that you want the SLA to be in effect. Use the dropdown to choose Everyday if necessary.
- In the Set status to ‘At Risk’ portion of the window, specify when the SLA should be marked as at risk.
- By default, notifications are not sent until an SLA is in violation. To change that, check Send an ‘At Risk’ notification.
You can turn off SLA alerts if necessary. This can be useful during maintenance windows. Click Settings on the navbar, then navigate to Alerts > General Alerts. Click the tablet and pencil icon to edit, and uncheck the SLA Alerts setting.