Skip to content

Configuring Other Database Connections

Defining a JNDI Name and Sample Data Sources for MySQL

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

  1. Click the name of the JDBC provider that you just created. For example, MySQL 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 MySQL JDBC Provider from the drop-down list.

  7. Click Next and accept the default helper class (com.ibm.websphere.rsadapter.GenericDataStoreHelper). Select the checkbox to use this data source in container managed persistence (CMP).

  8. Click Next and select the Setup security aliases:

    Field Name MySQL Value
    Component-managed authentication alias mysql_jasperdb
    Mapping configuration alias DefaultPrincipalMapping
    Container-managed authentication alias 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 can 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 checkbox 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 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&tinyInt1isBit=false&allowPublicKeyRetrieval=true

  6. Click Save directly to the master configuration.

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

  1. Click the name of the JDBC provider that you just created. For example, MySQL 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:jsSystemAnalytics

  5. Enter the JNDI name: jdbc/jasperserverSystemAnalytics

  6. Click Next, choose Select an existing JDBC provider, then select MySQL JDBC Provider from the drop-down list.

  7. Click Next and accept the default helper class (com.ibm.websphere.rsadapter.GenericDataStoreHelper). Select the checkbox to use this data source in container managed persistence (CMP).

  8. Click Next and select the Setup security aliases:

    Field Name MySQL Value
    Component-managed authentication alias mysql_jasperdb
    Mapping configuration alias DefaultPrincipalMapping
    Container-managed authentication alias 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 jsSystemAnalytics data source to edit it.
  2. Click Additional Properties > Connection Pool Properties. You can 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 checkbox for the newly created jsSystemAnalytics 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 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&tinyInt1isBit=false&allowPublicKeyRetrieval=true

  6. Click Save directly to the master configuration.

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

  1. Click the name of the JDBC provider that you just created. For example, MySQL 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: jsaudit

  5. Enter the JNDI name: jdbc/jasperserverAudit

  6. Click Next, choose Select an existing JDBC provider, then select MySQL JDBC Provider from the drop-down list.

  7. Click Next and accept the default helper class (com.ibm.websphere.rsadapter.GenericDataStoreHelper). Select the checkbox to use this data source in container managed persistence (CMP).

  8. Click Next and select the Setup security aliases:

    Field Name MySQL Value
    Component-managed authentication alias mysql_jasperdb
    Mapping configuration alias DefaultPrincipalMapping
    Container-managed authentication alias 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 jsaudit data source to edit it.
  2. Click Additional Properties > Connection Pool Properties. You can 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 checkbox for the newly created jsaudit 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 jsaudit 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

  5. For Compact installation: jasperserver

    • For Split installation: jsaudit

      1. Create a new property called url. Enter the following value and save the change:

    • For Compact installation: jdbc:mysql://localhost/jasperserver?useUnicode=true&characterEncoding=UTF-8&tinyInt1isBit=false&allowPublicKeyRetrieval=true

    • For Split installation: jdbc:mysql://localhost/jsaudit?useUnicode=true&characterEncoding=UTF-8&tinyInt1isBit=false&allowPublicKeyRetrieval=true

      1. Click Save directly to the master configuration.

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

      1. Click the name of the JDBC provider that you just created. For example, MySQL 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:jsAuditAnalytics

      5. Enter the JNDI name: jdbc/jasperserverAuditAnalytics

      6. Click Next, choose Select an existing JDBC provider, then select MySQL JDBC Provider from the drop-down list.

      7. Click Next and accept the default helper class (com.ibm.websphere.rsadapter.GenericDataStoreHelper). Select the checkbox to use this data source in container managed persistence (CMP).

      8. Click Next and select the Setup security aliases:

        Field Name MySQL Value
        Component-managed authentication alias mysql_jasperdb
        Mapping configuration alias DefaultPrincipalMapping
        Container-managed authentication alias 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 jsAuditAnalytics data source to edit it.
      2. Click Additional Properties > Connection Pool Properties. You can 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 checkbox for the newly created jsAuditAnalytics 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 jsaudit 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

    • For Compact installation: jasperserver

    • For Split installation: jsaudit

      1. Create a new property called url. Enter the following value and save the change:

    • For Compact installation: jdbc:mysql://localhost/jasperserver?useUnicode=true&characterEncoding=UTF-8&tinyInt1isBit=false&allowPublicKeyRetrieval=true

    • For Split installation: jdbc:mysql://localhost/jsaudit?useUnicode=true&characterEncoding=UTF-8&tinyInt1isBit=false&allowPublicKeyRetrieval=true

  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 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 JSPRSRVR JDBC data source and expose it through JNDI

  1. Click the name of the JDBC provider you just created. For example, 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: JSPRSRVR

  5. Enter the JNDI name: jdbc/jasperserver

  6. Click Next.

  7. For 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 the Component-managed authentication alias:

    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 JSPRSRVR data source to edit it.
  2. Click Additional Properties > Connection Pool Properties. You can 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 checkbox for the newly created JSPRSRVR 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 DB2 JDBC Driver

    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 checkbox for the JSPRSRVR data source, and click Test Connection.

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

  1. Click the name of the JDBC provider you just created. For example, 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: jsSystemAnalytics

  5. Enter the JNDI name: jdbc/jasperserverSystemAnalytics

  6. Click Next.

  7. For 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 the Component-managed authentication alias:

    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 jsSystemAnalytics data source to edit it.
  2. Click Additional Properties > Connection Pool Properties. You can 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 checkbox for the newly created jsSystemAnalytics 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 DB2 JDBC Driver

    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 checkbox for the jsSystemAnalytics data source, and click Test Connection.

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

  1. Click the name of the JDBC provider you just created. For example, 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: jsaudit

  5. Enter the JNDI name: jdbc/jasperserverAudit

  6. Click Next.

  7. For 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

    For Compact installation: JSPRSRVR
    For Split installation: JSAUDIT

    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 the Component-managed authentication alias:

    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 jsaudit data source to edit it.
  2. Click Additional Properties > Connection Pool Properties. You can 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 checkbox for the newly created jsaudit 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 DB2 JDBC Driver

    Property Name Value

    currentSchema

    For Compact Installation: JSPRSRVR

    For Split Installation: JSAUDIT

    fullyMaterializeLobData

    true

    fullyMaterializeInputStreams

    true

    progressiveStreaming

    2

    progressiveLocators

    2

  4. Go back to the list of JDBC data sources, select the checkbox for the jsaudit data source, and click Test Connection.

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

  1. Click the name of the JDBC provider you just created. For example, 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: jsAuditAnalytics

  5. Enter the JNDI name: jdbc/jasperserverAuditAnalytics

  6. Click Next.

  7. For 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

    For Compact installation: JSPRSRVR
    For Split installation: JSAUDIT

    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 the Component-managed authentication alias:

    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 jsAuditAnalytics data source to edit it.
  2. Click Additional Properties > Connection Pool Properties. You can 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 checkbox for the newly created jsAuditAnalytics 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 DB2 JDBC Driver

    Property Name Value

    currentSchema

    For Compact Installation: JSPRSRVR

    For Split Installation: JSAUDIT

    fullyMaterializeLobData

    true

    fullyMaterializeInputStreams

    true

    progressiveStreaming

    2

    progressiveLocators

    2

  4. Go back to the list of JDBC data sources, select the checkbox for the jsAuditAnalytics 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 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 DB2 Driver 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 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 jasperserver JDBC data source and expose it through JNDI

  1. Click the name of the JDBC provider you just created. For example, 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. For 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 the Component-managed authentication alias to the following value:

    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 can 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 checkbox 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. Go back to the list of JDBC data sources, select the checkbox for the jasperserver data source, and click Test Connection.

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

  1. Click the name of the JDBC provider you just created. For example, 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: jsSystemAnalytics

  5. Enter the JNDI name: jdbc/jasperserverSystemAnalytics

  6. Click Next.

  7. For 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 the Component-managed authentication alias to the following value:

    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 jsSystemAnalytics data source to edit it.
  2. Click Additional Properties > Connection Pool Properties. You can 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 checkbox for the newly created jsSystemAnalytics 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. Go back to the list of JDBC data sources, select the checkbox for the jsSystemAnalytics data source, and click Test Connection.

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

  1. Click the name of the JDBC provider you just created. For example, 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: jsaudit

  5. Enter the JNDI name: jdbc/jasperserverAudit

  6. Click Next.

  7. For 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 the Component-managed authentication alias to the following value:

    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 jsaudit data source to edit it.
  2. Click Additional Properties > Connection Pool Properties. You can 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 checkbox for the newly created jsaudit 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 jsaudit data sources General Properties page.

  3. In Additional Properties on the right side, click Custom properties.

  4. Go back to the list of JDBC data sources, select the checkbox for the jsaudit data source, and click Test Connection.

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

  1. Click the name of the JDBC provider you just created. For example, 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: jsAuditAnalytics

  5. Enter the JNDI name: jdbc/jasperserverAuditAnalytics

  6. Click Next.

  7. For 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 the Component-managed authentication alias to the following value:

    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 jsAuditAnalytics data source to edit it.
  2. Click Additional Properties > Connection Pool Properties. You can 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 checkbox for the newly created jsAuditAnalytics 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 jsaudit data sources General Properties page.

  3. In Additional Properties on the right side, click Custom properties.

  4. Go back to the list of JDBC data sources, select the checkbox for the jsAuditAnalytics 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 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 the jasperserver 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. For 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 the 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 can 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 checkbox 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.

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

  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: jsSystemAnalytics

  5. Enter the JNDI name: jdbc/jasperserverSystemAnalytics

  6. Click Next.

  7. For 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 the 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 jsSystemAnalytics data source to edit it.
  2. Click Additional Properties > Connection Pool Properties. You can 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 checkbox for the newly created jsSystemAnalytics 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.

To define the jsaudit 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: jsaudit

  5. Enter the JNDI name: jdbc/jasperserverAudit

  6. Click Next.

  7. For 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 the 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 jsaudit data source to edit it.
  2. Click Additional Properties > Connection Pool Properties. You can 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 checkbox for the newly created jsaudit 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 jsaudit data sources General Properties page.

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

  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: jsAuditAnalytics

  5. Enter the JNDI name: jdbc/jasperserverAuditAnalytics

  6. Click Next.

  7. For 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 the 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 jsAuditAnalytics data source to edit it.
  2. Click Additional Properties > Connection Pool Properties. You can 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 checkbox for the newly created jsAuditAnalytics 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 jsaudit data sources General Properties page.

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 Set the connection pool size.

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