Discover how a bimodal integration strategy can address the major data management challenges facing your organization today.
Get the Report →Connect to Cvent from a Connection Pool in WebLogic
Use the CData JDBC Driver for Cvent to connect to Cvent data from Web applications running on WebLogic.
The CData JDBC Driver for Cvent enables you to follow standard procedures to integrate Cvent data into Java Web applications. This article shows how to deploy the CData JDBC Driver for Cvent in WebLogic Server.
Deploy the JDBC Driver in WebLogic Server
To deploy the driver, add the driver JAR to your classpath. The .lic file must be located in the same folder as the JAR. These files are located in the lib subfolder of the installation directory.
If you want to add the driver to all domains, prepend the path to the JAR to the WEBLOGIC_CLASSPATH environment variable in WL_HOME\common\bin\commEnv.cmd/sh. This script is located in WL_HOME\common\bin\. For example:
set WEBLOGIC_CLASSPATH=your-installation-directory\lib\cdata.jdbc.cvent.jar;%WEBLOGIC_CLASSPATH%
In WebLogic 12.2.1 if you want to add the driver to a specific domain, you can simply place the driver JAR and .lic file into DOMAIN_HOME\lib; for example, ORACLE_HOME\user_projects\domains\MY_DOMAIN\lib. These files will be added to the server classpath at startup.
Earlier versions require that you manually add the driver to the classpath: Prepend the following to the PRE_CLASSPATH environment variable in setDomainEnv.cmd/sh. This script is located in the bin subfolder of the folder for that domain.
set PRE_CLASSPATH=your-installation-directory\lib\cdata.jdbc.cvent.jar;%PRE_CLASSPATH%
After making these changes, restart the server.
Create a JDBC Data Source for Cvent
After deploying the driver, log into the WebLogic Administration Console and create the connection.
- In the Domain Structure tree, click Services -> Data Sources -> New -> Generic Data Source.
-
On the JDBC Data Source Properties page, enter the following information:
- Name: Enter a user-friendly name; for example, cventjdbc.
- JNDI Name: Enter the path the JDBC data source will be bound to; for example, jdbc/Cvent.
Database Type: Select Other.
-
Click Next to use the default options. On the last page, enter the following information and click Test Configuration:
- Driver Class Name: Enter the driver class, cdata.jdbc.cvent.CventDriver.
URL: Enter the JDBC URL. A typical JDBC URL is below:
jdbc:cvent:OAuthClientId=MyOAuthClientId;OAuthClientSecret=MyOAuthClientSecret;InitiateOAuth=GETANDREFRESH
Before you can authenticate to Cvent, you must create a workspace and an OAuth application.
Creating a Workspace
To create a workspace:
- Sign into Cvent and navigate to App Switcher (the blue button in the upper right corner of the page) >> Admin.
- In the Admin menu, navigate to Integrations >> REST API.
- A new tab launches for Developer Management. Click on Manage API Access in the new tab.
- Create a Workspace and name it. Select the scopes you would like your developers to have access to. Scopes control what data domains the developer can access.
- Choose All to allow developers to choose any scope, and any future scopes added to the REST API.
- Choose Custom to limit the scopes developers can choose for their OAuth apps to selected scopes. To access all tables exposed by the driver, you need to set the following scopes:
event/attendees:read event/attendees:write event/contacts:read event/contacts:write event/custom-fields:read event/custom-fields:write event/events:read event/events:write event/sessions:delete event/sessions:read event/sessions:write event/speakers:delete event/speakers:read event/speakers:write budget/budget-items:read budget/budget-items:write exhibitor/exhibitors:read exhibitor/exhibitors:write survey/surveys:read survey/surveys:write
Creating an OAuth Application
After you have set up a Workspace and invited them, developers can sign up and create a custom OAuth app. See the Creating a Custom OAuth Application section in the Help documentation for more information.
Connecting to Cvent
After creating an OAuth application, set the following connection properties to connect to Cvent:
- InitiateOAuth: GETANDREFRESH. Used to automatically get and refresh the OAuthAccessToken.
- OAuthClientId: The Client ID associated with the OAuth application. You can find this on the Applications page in the Cvent Developer Portal.
- OAuthClientSecret: The Client secret associated with the OAuth application. You can find this on the Applications page in the Cvent Developer Portal.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Cvent JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.cvent.jar
Fill in the connection properties and copy the connection string to the clipboard.
- Database User Name: Enter the username, if not specified in the JDBC URL.
- Password: Enter the password, if not specified in the JDBC URL.
After selecting the server where you want to deploy the JDBC data source, you can now connect to Cvent data.
More WebLogic Integration
The steps above show how configure the driver in a simple connection pooling scenario. For more use cases and information, see the JDBC sections in the WebLogic Data Sources chapter of the Oracle Fusion Middleware documentation.