Previous Topic  Next Topic

Configuring in an Integrated Environment

This topic demonstrates how to specify the dsInfo in web.xml, ejb-jar.xml, and dbconfig.xml, respectively. When integrated with an application server, by default Logi Report Server obtains the server database information from dbconfig.xml located in the <server_install_root>\bin directory. However, you can make use of a key-value pair to specify another database configuration file, or to specify the server database directly in a JDBC or JNDI data source.

Select the following links to view the topics:

• Format of the Key-Value Pair
• Specifying in the System Environment
• Specifying in dbconfig.xml
• Specifying in web.xml (for the WAR Mode)
• Specifying in ejb-jar.xml or web.xml (for the EAR Mode)

Format of the Key-Value Pair

The name of the key must be jreport.datasource.systemtables, jreport.datasource.realmtables or jreport.datasource.profile, where systemtables, realmtables and profile are Logi Report Server's inner database names for the system database, realm database and profiling database respectively. The value should be in the form of a URL as one of the following:

• Specify the path of another database configuration file:

  file:///absolute_path_of_config_file

  For example: file:///LogiReport/dbconfig.xml, or file://D:\dbconfig.xml

• Specify a JDBC data source:

  jdbc://[<jdbc-user:jdbc-password>@]<jdbc-url>[#<attribute-name=attribute-value>,]

  For example: jdbc://user:password@jdbc:odbc:jreport-realmtables#driver=sun.jdbc.odbc.JdbcOdbcDriver

• Specify a JNDI data source:

  jndi://[<jdbc-user:jdbc-passoword>@]datasource_name[#<attribute-name=attribute-value>,]

  For example: jndi://jdbc/jreport-realmtables

The server database information can be specified in several places or levels, such as the system environment using "-D" parameters, ejb-jar.xml, web.xml and dbconfig.xml. The sequence to load the information is:

system environment > ejb-jar.xml (EAR mode) > web.xml (WAR mode) > dbconfig.xml

Specifying in the System Environment

To specify the key-value pair in the system environment, add the following "-D" parameters in the Logi Report Server startup file JRServer.bat/JRServer.sh in the <server_install_root>\bin directory:

-Djreport.datasource.profiling=file:///absolute_path_of_config_file,-Djreport.datasource.systemtables=file:///absolute_path_of_config_file,-Djreport.datasource.realmtables=file:///absolute_path_of_config_file

Specifying in dbconfig.xml

You can specify either a JDBC or JNDI data source using the <datasource></datasource> tags in dbconfig.xml. Note that in dbconfig.xml, <database name> must be Logi Report Server's inner database name.

For details about configuring a JDBC data source, see Method 2: Specifying a JDBC Data Source Using the <datasource></datasource> Tags.

The following shows an example of specifying a JNDI data source:

<?xml version="1.0" encoding="UTF-8"?>
<dbconfig>
    
    <workspace name="systemRealm">
        
        <database name="systemtables">
            
        <datasource>jndi://datasource-name</datasource>
        </database>
  
    </workspace>
  
    <workspace name="defaultRealm">
  
        <database name="realmtables"> 
 
            <datasource>jndi://datasource-name</datasource>
 
        </database> 
 
    </workspace>
  
</dbconfig>

Specifying in web.xml (for the WAR Mode)

When integrating Logi Report Server in a WAR package, you can specify the key-value pair in the WEB-INF/web.xml file using the <env-entry></env-entry> or <context-param></context-param> tags. The <env-entry></env-entry> tags are more recommended since they are also supported in ejb-jar.xml if you call the Server API in your EJB.

The following example uses the <env-entry></env-entry> tags:

<web-app>
 
    ...

 
    <env-entry>
 
        <env-entry-name>jreport.datasource.realmtables</env-entry-name>
 
        <env-entry-value>jndi://java:/resource-name</env-entry-value>
 
        <env-entry-type>java.lang.String</env-entry-type>
 
    </env-entry>
 
</web-app> 

The following example uses the <context-param></context-param> tags:

<web-app>
 
    <context-param>
 
        <param-name>jreport.datasource.realmtables</param-name>
  
        <param-value>jndi://datasource_name_which_is_predefined</param-value>
 
    </context-param>
  
    ...

</web-app>

Specifying in ejb-jar.xml or web.xml (for the EAR Mode)

When Logi Report Server is used with APIs by EJBs, you can specify the key-value pair either in META-INF/ejb-jar.xml or WEB-INF/web.xml.

To specify the key-value pair in META-INF/ejb-jar.xml, use the <env-entry></env-entry> tags. For example, here is an EJB named firstEJB which creates the Logi Report Server instance. You can add the <env-entry></env-entry> tags to the EJB's configuration file META-INF/ejb-jar.xml as follows:

<ejb-jar>
 
    <enterprise-beans>
 
        <session>
  
            <ejb-name>firstEJB</ejb-name>
 
            ...
 
            <env-entry>
 
                <env-entry-name>jreport.datasource.realmtables</env-entry-name>
 
                <env-entry-value>jndi://java:/resource_name</env-entry-value>
 
                <env-entry-type>java.lang.String</env-entry-type>
  
            </env-entry>
 
        </session> 
 
        ...

    </enterprise-beans> 
 
    ...

</ejb-jar>

If the server database information is stored in a Web module, you should add the Logi Report Server context listener to WEB-INF/web.xml as follows:

<web-app>
 
    <listener>
 
        <listener-class>
 
            jet.server.servlets.JRServerContextListener
 
        </listnener-class>
  
    </listener>
 
    ... 
 
</web-app>

Previous Topic  Next Topic