Connect to Sage US from a Connection Pool in WebLogic

Use the CData JDBC Driver for Sage US to connect to Sage US data from Web applications running on WebLogic.

The CData JDBC Driver for Sage US enables you to follow standard procedures to integrate Sage US data into Java Web applications. This article shows how to deploy the CData JDBC Driver for Sage US in WebLogic server.

Install the JDBC Driver in WebLogic Server

Add the driver JAR and license file to the classpath your application will be using. 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, add the JAR to the WEBLOGIC_CLASSPATH environment variable. add the following line to the commEnv.cmd/sh script in WL_HOME\common\bin\.

set WEBLOGIC_CLASSPATH=your-installation-directory\lib\cdata.jdbc.sage50us.jar;%WEBLOGIC_CLASSPATH%

If you want to add the driver to a specific domain, you will need to add the JAR to the PRE_CLASSPATH environment variable. Add the following line to the setDomainEnv.cmd/sh script in the bin subfolder of the folder for that domain:

set PRE_CLASSPATH=your-installation-directory\lib\cdata.jdbc.sage50us.jar;%PRE_CLASSPATH%

Create a JDBC Data Source for Sage US

After installing the driver, create the connection.

  1. In the Domain Structure tree, click Services -> Data Sources -> New -> Generic Data Source.
  2. On the JDBC Data Source Properties page, enter the following information:
    • Name: Enter a user-friendly name; for example, sage50usjdbc.
    • JDBC Name: Enter the path the JDBC data source will be bound to; for example, jdbc/Sage50US.
    • Database Type: Select Other.

  3. 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.sage50us.Sage50USDriver, in this property.
    • URL: Enter the JDBC URL. A typical JDBC URL is below:

      jdbc:sage50us:ApplicationId=8dfafu4V4ODmh1fM0xx;CompanyName=Bellwether Garden Supply - Premium;

      The Application Id and Company Name connection string options are required to connect to Sage as a data source. You can obtain an Application Id by contacting Sage directly to request access to the Sage 50 SDK.

      Sage must be installed on the machine. The Sage.Peachtree.API.dll and Sage.Peachtree.API.Resolver.dll assemblies are required. These assemblies are installed with Sage in C:\Program Files\Sage\Peachtree\API\. Additionally, the Sage SDK requires .NET Framework 4.0 and is only compatible with 32-bit applications. To use the Sage SDK in Visual Studio, set the Platform Target property to "x86" in Project -> Properties -> Build.

      You must authorize the application to access company data: To authorize your application to access Sage, restart the Sage application, open the company you want to access, and connect with your application. You will then be prompted to set access permissions for the application in the resulting dialog.

      While the compiled executable will require authorization only once, during development you may need to follow this process to reauthorize a new build. To avoid restarting the Sage application when developing with Visual Studio, click Build -> Configuration Manager and uncheck "Build" for your project.

    • 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 Sage US 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.

 
 
ダウンロード