• View
• Edit
• History
• Print
• Backlinks

Registering data source

ProReports system mainly supports two data sources:

• JDBC data sources - when generating report it is established one connection that in closed after report is generated
• JNDI data sources - advised with bulk report generation - connection based on connection pool thanks to which we can save time, because in this case it isn't necessary creating connection to database each time.

Registering JDBC data source

To register JDBC data source you can use following option: Resources->Add datasource in option: Resources->List of datasources:

Selecting one of two possible option leads to displaying form in which you have to determine:

• source type - select JDBC
• source name - any descriptive name
• JDBC driver class - JDBC driver class of defined source
• name of user
• user password
• so called connectstring - URL used to access specified database

After registering new data source you can check correctness of connection using option Test:

If everything works fine message Connection OK will be shown. Otherwise different message may appear that will inform you about error, e.g.:

In that case you have to check where all values have been set.

Registering JNDI data source

Registering JNDI data source is divided into 3 steps:

• registering source in configuration file:

<server_directory>/etc/jetty.xml

• registering source in files:

<server_directory>/webapps-plus/rep/WEB-INF/web.xml
<server_directory>/webapps-plus/utf/WEB-INF/web.xml

• registering source in ProReports system database (option like in JDBC)

Registering in file jetty.xml

At the end of the file (but before </Configure>) you have to add section:

<New id="DBNAME" class="org.mortbay.jetty.plus.naming.Resource">
<Arg>jdbc/DBNAME</Arg>
<Arg>
<New class="com.mchange.v2.c3p0.ComboPooledDataSource">
<Set name="driverClass">CLASSJDBC</Set>
<Set name="jdbcUrl">CONNECTSTRING</Set>
<Set name="user">USER</Set>
<Set name="password">HASLO</Set>
<Set name="minPoolSize">0</Set>
<Set name="maxPoolSize">15</Set>
<Set name="maxIdleTime">120</Set>
<Set name="checkoutTimeout">20000</Set>
</New>
</Arg>
</New>

where values DBNAME, CLASSJDBC, CONNECTSTRING, USER and HASLO have to be replaced with correct values for defined database.

Examople (for INFORMIX database):

<New id="DBprod" class="org.mortbay.jetty.plus.naming.Resource">
<Arg>jdbc/DBprod</Arg>
<Arg>
<New class="com.mchange.v2.c3p0.ComboPooledDataSource">
<Set name="driverClass">com.informix.jdbc.IfxDriver</Set>
<Set name="jdbcUrl">jdbc:informix-sqli://192.168.1.5:9012/base_production:informixserver=on1_prd1;
DBDATE=Y4MD-;IFX_LOCK_MODE_WAIT=10;CLIENT_LOCALE=pl_PL.8859-2;DB_LOCALE=pl_PL.8859-2;</Set>
<Set name="user">test</Set>
<Set name="password">test123</Set>
<Set name="minPoolSize">0</Set>
<Set name="maxPoolSize">15</Set>
<Set name="maxIdleTime">120</Set>
<Set name="checkoutTimeout">20000</Set>
</New>
</Arg>
</New>

Registering in file web.xml

In files:

<server_directory>/webapps-plus/rep/WEB-INF/web.xml
<server_directory>/webapps-plus/utf/WEB-INF/web.xml

needs to be registered another section named resource-ref:

<resource-ref>
<res-ref-name>jdbc/DBNAME</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>

where value DBNAME has to be correlated with value from file jetty.xml

Example:

<resource-ref>
<res-ref-name>jdbc/DBprod</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>

Registering in ProReports database

After modifying *.xml files and restarting ProReports server you have to register JNDI source in system database. This can be achieved using the same path as with registering JDBC source - meaning Resources->Add data source or key New data source in Resources->Data source list:

While registering JNDI source we have to basically enter 3 values:

• type - choose JNDI
• name - any name
• JNDI name - name corelated with definitions in *.xml files (look DBNAME) always starts with java:comp/env/jdbc/

Remaining fields are not enabled and therefore they don't need to be filled.

Similar to JDBC data source you can perform connection check (click here to see how to do that).

Other data sources

Web Services

Data files