Jump to content
JasperReports Library 7.0 is now available ×
  • This documentation is an older version of JasperReports Server Installation Guide. View the latest documentation.

    Configuring Other Database Connections

    Defining a JNDI Name and Sample Data Sources for MySQL

    To define the JDBC data source and expose it through JNDI:

    1. Click the name of the JDBC provider that you just created. For example, PostgreSQL JDBC Provider.
    2. Click Data sources in the Additional Properties of the JDBC provider details panel.
    3. To create a new data source, click New. The new data source wizard appears.
    4. Enter the data source name: jasperserver
    5. Enter the JNDI name: jdbc/jasperserver
    6. Click Next, choose Select an existing JDBC provider, then select PostgreSQL JDBC Provider or MySQL JDBC Provider from the drop-down list.
    7. Click Next and accept the default helper class (com.ibm.websphere.rsadapter.GenericDataStoreHelper). Select the check box to use this data source in container managed persistence (CMP).
    8. Click Next and select the Setup security aliases:

    Field Name

    PostgreSQL Value

    MySQL Value

    Component-managed authentication alias

    <node>/postgresql_jasperdb

    <node>/mysql_jasperdb

    Mapping configuration alias

    DefaultPrincipalMapping

    DefaultPrincipalMapping

    Container-managed authentication alias

    <node>/postgresql_jasperdb

    <node>/mysql_jasperdb

    9. Click Next, review the summary information, and click Finish.

    To set the connection pool size:

    1. In the list of JDBC data sources, click the newly created jasperserver data source to edit it.
    2. Click Additional Properties > Connection Pool Properties.

    You'll see that Maximum Connections is set to 10 by default.

    3. Set Maximum Connections to 50. You may want to set it to a higher value if necessary.
    4. Click Save.

    To define custom properties:

    1. In the list of JDBC data sources, select the check box for the newly created jasperserver data source and click Test Connection.

    In the Messages area a success or failure message appears. The failure message gives you information about which custom properties you need to define. For example, in the case of PostgreSQL 9.0 and MySQL, a message indicates that the error is related to a null database name.

    2. Navigate to the jasperserver data sources General Properties page.
    3. In Additional Properties on the right side of the General Properties page, click Custom properties.
    4. Scroll down the list of properties and select databaseName. Set the value to jasperserver.
    5. Create a new property called url. Enter the following value and save the change:

    jdbc:mysql://localhost/jasperserver?useUnicode=true&characterEncoding=UTF-8

    6. Click Save directly to the master configuration.

    To create optional sugarcrm and foodmart data sources:

    1. If you plan to run the sample reports, use the values in the following table to create the foodmart and sugarcrm JNDI data sources.
    Field Name Value

    Data source name

    foodmart

    sugarcrm

    JNDI name

    jdbc/foodmart

    jdbc/sugarcrm

    2. Click Save directly to the master configuration.
    3. Set the connection pool size as described in To set the connection pool size.

    Next, deploy the WAR file in WebSphere as described in Deploying the WAR File in WebSphere.

    Defining a JNDI Name and Sample Data Sources for DB2

    To define the JDBC data source and expose it through JNDI:

    1. Click the name of the JDBC provider you just created. For example, TIBCO JDBC Provider - DB2 or DB2 Universal JDBC Provider.
    2. Click Data sources under the Additional Properties of the JDBC provider details panel.
    3. To create a new data source, click New. The new data source wizard appears.
    4. Enter the data source name: jasperserver
    5. Enter the JNDI name: jdbc/jasperserver
    6. Click Next.
    7. (If you're using the TIBCO JDBC Provider, skip to step 9.) If you're using the vendor's DB2 driver, choose Select an existing JDBC provider, then select DB2 Universal JDBC Provider from the drop-down list.
    8. Click Next and enter these values:
    Field Name Value

    Driver type

    4

    Database name

    jsprsrvr

    Server name

    localhost

    Port number

    50000

    9. Select Use this data source in CMP and click Next.
    10. On the Setup security aliases page, enter the following value for Component-managed authentication alias:

    <node>/db2admin_user

    11. Click Next, review the summary information, and click Finish.

    To set the connection pool size:

    1. In the list of JDBC data sources, click the newly created jasperserver data source to edit it.
    2. Click Additional Properties > Connection Pool Properties.

    You'll see that Maximum Connections is set to 10 by default.

    3. Set Maximum Connections to 50. You may want to set it to a higher value if necessary.
    4. Click Save.

    To define custom properties:

    1. In the list of JDBC data sources, select the check box for the newly created jasperserver data source, and click Test Connection.
    2. In the Messages area a success or failure message appears. The failure message gives you information about which custom properties you need to define.
    3. Edit the following properties, adding any that are missing, then save the changes:

    Properties for TIBCO JDBC Driver for DB2

    Property Name Value alternateID JSPRSRVR

    batchPerformanceWorkaround

    true

    databaseName

    JSPRSRVR

    serverName

    localhost portNumber 50000

    note-icon-ns_28x28.png.6e14628732ba67dd7b77f6db2799a0f4.png

    To see a list of all properties available for the TIBCO JDBC driver for DB2, see the Progress DataDirect documentation at http://media.datadirect.com/download/docs/jdbc/alljdbc/help.html and navigate to User's Guide > DataDirect Connect Drivers > DB2 Driver  > Connection Properties.

    Properties for Vendor JDBC Driver for DB2

    Property Name Value

    currentSchema

    JSPRSRVR

    fullyMaterializeLobData

    true

    fullyMaterializeInputStreams

    true

    progressiveStreaming

    2

    progressiveLocators

    2

    4. Go back to the list of JDBC data sources, select the check box for the jasperserver data source, and click Test Connection.

    To create optional sugarcrm and foodmart data sources:

    1. If you plan to run the sample reports, use the following values to create the foodmart and sugarcrm JNDI data sources.

    Field Values for Optional Data Sources for Vendor DB2 Drivers with WebSphere

    Field Name

    Value

    Data source name

    foodmart

    sugarcrm

    JNDI name

    jdbc/foodmart

    jdbc/sugarcrm

    Component-managed authentication alias

    <node>/db2admin_user

    Database name

    foodmart

    sugarcrm

    Driver type

    4

    Server name

    localhost

    Port number

    50000

    Use this data source in CMP

    selected

    Custom Properties for TIBCO JDBC Driver for DB2 with WebSphere

    Property Name

    Value

    alternateID FOODMART SUGARCRM batchPerformanceWorkaround

    true

    databaseName FOODMART SUGARCRM serverName

    localhost

    Custom Properties for Vendor's Driver for DB2 with WebSphere

    Property Name

    Value

    currentSchema

    FOODMART

    SUGARCRM

    resultSetHoldability

    1

    2. Click Save directly to the master configuration.
    3. Set the connection pool size as described in To set the connection pool size.

    Next, deploy the WAR file in WebSphere as described in Deploying the WAR File in WebSphere.

    Defining a JNDI Name and Sample Data Sources for Oracle

    To define the JDBC data source and expose it through JNDI:

    1. Click the name of the JDBC provider you just created. For example, TIBCO JDBC Provider - Oracle or Oracle JDBC Driver.
    2. Click Data sources in the Additional Properties of the JDBC provider details panel.
    3. To create a new data source, click New. The new data source wizard appears.
    4. Enter the data source name: jasperserver
    5. Enter the JNDI name: jdbc/jasperserver
    6. Click Next.
    7. (If you're using the TIBCO JDBC Provider, skip to step 9.) If you are using the vendor's Oracle driver, choose Select an existing JDBC provider, then select Oracle JDBC Driver from the drop-down list.
    8. Click Next and enter the following values:
    Field Name Value

    URL

    jdbc:oracle:thin:@localhost:1521:orcl

    Data store helper class name

    Oracle11g data store helper

    Use this data source in CMP

    selected

    9. Click Next and in Setup security alias, set Component-managed authentication alias to the following value:

    <node>/jasperserver_user

    10. Click Next, review the summary information and click Finish.

    To set the connection pool size:

    1. In the list of JDBC data sources, click the newly created jasperserver data source to edit it.
    2. Click Additional Properties > Connection Pool Properties.

    You'll see that Maximum Connections is set to 10 by default.

    3. Set Maximum Connections to 50. You may want to set it to a higher value if necessary.
    4. Click Save.

    To define custom properties:

    1. In the list of JDBC data sources, select the check box for the newly created jasperserver data source and click Test Connection.

    In the Messages area a success or failure message appears. The failure message gives you information about which custom properties you need to define.

    2. Navigate to the jasperserver data sources General Properties page.
    3. In Additional Properties on the right side, click Custom properties.
    4. Edit the following properties, adding any that are missing, then save the changes. The following table shows how to set the custom properties if you're using the TIBCO JDBC driver for Oracle:

    Custom Properties for TIBCO JDBC Driver for Oracle

    Property Name Value serverName localhost SID ORCL

    portNumber

    1521

    CatalogOptions 0 batchPerformanceWorkaround true

    note-icon-ns_28x28.png.daf8e15c363866f13e22e462a30ab889.png

    To see a list of all properties available for the TIBCO JDBC driver for Oracle, see the Progress DataDirect documentation at http://media.datadirect.com/download/docs/jdbc/alljdbc/help.html and navigate to User's Guide > DataDirect Connect Drivers > Oracle Driver  > Connection Properties.

    5. Go back to the list of JDBC data sources, select the check box for the jasperserver data source, and click Test Connection.

    To create optional sugarcrm and foodmart data sources:

    1. If you plan to run the sample reports, use the following values to create the foodmart and sugarcrm JNDI data sources:
    Field Name

    Value

    Data source name

    foodmart

    sugarcrm

    JNDI name

    jdbc/foodmart

    jdbc/sugarcrm

    Component-managed authentication alias

    <node>/foodmart_user

    <node>/sugarcrm_user

    Property Name

    Value

    portNumber

    1521

    serverName

    localhost

    2. Click Save directly to the master configuration.
    3. Set the connection pool size as described in To set the connection pool size.

    Next, deploy the WAR file in WebSphere as described in Deploying the WAR File in WebSphere.

    Defining a JNDI Name and Sample Data Sources for SQL Server

    To define a JDBC provider:

    1. Click the name of the JDBC provider you just created. For example, Microsoft SQL Server JDBC Driver.
    2. Click Data sources under the Additional Properties of the JDBC provider details panel.
    3. To create a new data source, click New. The new data source wizard appears.
    4. Enter the data source name: jasperserver
    5. Enter the JNDI name: jdbc/jasperserver
    6. Click Next.
    7. (If you're using the TIBCO JDBC Provider, skip this step.) If you're using the vendor's SQL Server driver, choose Select an existing JDBC provider, then select Microsoft SQL Server JDBC Driver from the drop-down list.
    8. Click Next and in Setup security alias, set Component-managed authentication alias to the following value:

    jasperserver_user

    9. Click Next, review the summary information and click Finish.

    To set the connection pool size:

    1. In the list of JDBC data sources, click the newly created jasperserver data source to edit it.
    2. Click Additional Properties > Connection Pool Properties.

    You'll see that Maximum Connections is set to 10 by default.

    3. Set Maximum Connections to 50. You may want to set it to a higher value if necessary.
    4. Click Save.

    To define custom properties:

    1. In the list of JDBC data sources, select the check box for the newly created jasperserver data source, and click Test Connection.

    In the Messages area a success or failure message appears. The failure message gives you information about which custom properties you need to define.

    2. Navigate to the jasperserver data sources General Properties page.
    3. In Additional Properties on the right side of the page, click Custom properties and define properties. The following table shows how to set properties if you are using the TIBCO JDBC driver for SQL Server

    Custom Properties for TIBCO JDBC Driver for SQL Server

    Property Name Value batchPerformanceWorkaround true databaseName jasperserver serverName localhost

    portNumber

    1433

    note-icon-ns_28x28.png.986f1b8fc4db99f6e3dc7f5cf3b9c84b.png

    To see a list of all properties available for the TIBCO JDBC driver for SQL Server, see the Progress DataDirect documentation at http://media.datadirect.com/download/docs/jdbc/alljdbc/help.html and navigate to User's Guide > DataDirect Connect Drivers > Microsoft SQL Server Driver  > Connection Properties.

    To create optional sugarcrm and foodmart data sources:

    If you plan to run the sample reports, use the following values to create the foodmart and sugarcrm JNDI data sources:

    1. In the list of JDBC data sources, click the link for the newly created jasperserver data source.
    2. Click Save directly to the master configuration.
    3. Set the connection pool size as described in To set the connection pool size.

    Next, deploy the WAR file in WebSphere as described in Deploying the WAR File in WebSphere.


    User Feedback

    Recommended Comments

    There are no comments to display.



    Guest
    This is now closed for further comments

×
×
  • Create New...