Creating a JDBC Data Source

You can create a JDBC data source to connect from your Java application. Creating a JDBC data source based on the CData JDBC Driver for Sage Intacct consists of three basic steps:

• Add the driver JAR file to the classpath. The JAR file is located in the lib subfolder of the installation directory. Note that the .lic file must be located in the same folder as the JAR file.
• Provide the driver class. For example:
  

  cdata.jdbc.sageintacct.SageIntacctDriver

• Provide the JDBC URL. For example:
  

  jdbc:sageintacct:User='myusername';CompanyID='TestCompany';Password='mypassword';SenderID='Test';SenderPassword='abcde123';
  
  or
  
  jdbc:cdata:sageintacct:User='myusername';CompanyID='TestCompany';Password='mypassword';SenderID='Test';SenderPassword='abcde123';

  The second format above can be used whenever there is a conflict in your application between drivers using the same URL format to ensure you are using the CData driver. The URL must start with either "jdbc:sageintacct:" or "jdbc:cdata:sageintacct:" and can include any of the connection properties in name-value pairs separated with semicolons.

Connecting to Sage Intacct

To connect to Web Services, you will first need to enable the Web Services subscription. Navigate to Company > Admin Tab > Subscriptions and enable Web Services.

Intacct also recommends creating a Web Services-only user, which can be done by navigating to Company > Admin Tab, and clicking on the + sign beside Web Services users.

You can establish a connection to Sage Intacct using either the embedded credentials or with your own credentials.

Authenticating to Sage Intacct

To authenticate, set CompanyID and set User and Password to the credentials you use to log on to Sage Intacct. In addition, you will need to either set your own SenderID and SenderPassword, or use the embedded credentials in the CData JDBC Driver for Sage Intacct.

Embedded Credentials

The driver has embedded Web Services credentials that will be used when reading data from Intacct.

You can connect using embedded credentials as follows:

• Ensure that you have not specified a SenderID or SenderPassword.
• In your Web Services dashboard, navigate to Company > Company Info > Security tab.
• Add "CData" to your Web Services authorizations. This is case-sensitive. This can be done by navigating to Company -> Company Info (Configuration -> Company in new UI) -> Security -> Web Services Authorizations / Edit.

Note: As opposed to using custom credentials, the embedded credentials are read-only.

Connect using Custom Credentials

You can use your own Web Services credentials to write data to Intacct. Set the following to connect to data:

• SenderID: Set this to the Web Services Sender ID assigned to you by Sage Intacct.
• SenderPassword: Set this to your registered Web Services password.

Okta

Set the AuthScheme to Okta. The following connection properties are used to connect to Okta:

• User: Set this to the Okta user.
• Password: Set this to Okta password for the user.
• SSOLoginURL: Set this to the login url used by the SSO provider.

The following SSOProperties are needed to authenticate to Okta:

• IntacctUserID: Set this value to the Intacct User ID that is mapped to the Okta user you set in the User connection property.
• APIToken (optional): Set this to the API Token that the customer created from the Okta org. It should be used when authenticating a user via a trusted application or proxy that overrides Okta client request context.

The following is an example connection string: AuthScheme=Okta; SSOLoginURL='https://example.okta.com/home/appType/0bg4ivz6cJRZgCz5d6/46'; User=oktaUserName; Password=oktaPassword; SSOProperties='IntacctUserID=intacct_user';