When trying to export a profiling report that is generated with a user-defined JRXML template, all JRXML templates in the DQ repository of the Studio are selected by default in the export wizard - not just the template used by the report.

This is not a bug. All JRXML templates are selected by default and exported with the report because they are needed to handle any dependencies that may exist between the JRXML files. Such dependencies cannot currently be handled otherwise.

Problem Description

When running an imported Job on a remote server, that uses a tDqReportRun component to launch a report, the generated report file is empty.

Root Cause

In this example, the Job uses a tDqReportRun component to create a project named PROJ5 and imports a project named PROJ6. In the Report filenames field of the tDqReportun properties, the name of the project is not updated.

Solution

1. When launching Talend Studio, select the existing project where the Job will be imported or create a new project, then click Finish. In this example, PROJ6 is selected.
2. Import the report, analysis, connection, and context.
3. Import the Job from the previous project into the new project.
4. Open the imported Job.
5. Double-click the tDqReportun component to open the Component view.
6. In the Report filenames field, edit the path to the report file and replace the name of the old project with the name of the current project. In this case, replace PROJ5 with PROJ6.

   

7. Run the Job.

The report file is saved in the output folder defined in the tDQReportRun basic settings.

Overview

Before you can use Talend Data Quality Portal as a web-based monitoring and reporting tool of data quality metrics, you must define the data source that holds the technical data to be used in document templates. You can test this connection before saving it.

This article shows the form of the IP address you must define in the database connection on the Administrator page of the Portal.

Environment

This article applies to Talend Data Quality Portal versions prior to 6.2.1.

Symptoms/Description

When you define the database URL or JNDI name from the Talend Data Quality Portal > Administrator page > Detail Data Source page, you may get an error when you try to test the connection before saving it if you do not use the correct form of the IP address with different web browsers. This is due to some limitations on the use of some browsers by SpagoBI.

Resolution

When you define the connection to the data source, you must use internet or public IP addresses to connect successfully using web browsers. IP addresses like 127.0.0.1 or domain aliases like localhost will not work.

The following table gives detailed descriptions of supported browsers and IP forms:

Problem Description

In the Profiling perspective of Talend Studio, once you create a report on one or several analyses, you can generate a ready-to-use Job to launch the report. However, when one or more of the connections used by the report are contextualized after the Job generation, the changes are not propagated to the Job.

Solution

To take into account the changes, perform one of the following:

• Drag and drop the context group into the Context view of the reporting Job.
• Browse the reports again to include the contexts.

Answer

By default, the Talend Data Quality Portal gets data from the data source Talend datamart. It uses data in this source to fill up documents during report execution, but you can define data sources that are different from the default one. For example, you can define the data source as JDBC to connect to other data sources on the fly.

However, when you create a MySQL data source with a JDBC connection, you must add this to the URL:

&useOldAliasMetadataBehavior=true

Below is an example URL:

jdbc:mysql:/ /172.168.33.16:3306/talend_dq?characterEncoding=UTF8&useOldAliasMetadataBehavior=true

This is because starting from the 6.0 release, Talend supports Tomcat 8 and has upgraded the MySQL driver to mysql-connector-java-5.1.33-bin.jar.

Overview

An error message may be appended to Tomcat's log file while using Talend Data Quality Portal. This article describes this error and provides solutions to eliminate it.

Symptoms/Description

When launching Tomcat to run Talend Data Quality Portal, the error message "SEVERE: No Store configured, persistence disable" may occur several times in Tomcat's log file (catalina.out).

Feb 27, 2013 10:11:59 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive SpagoBIBirtReportEngine.war
Feb 27, 2013 10:12:02 AM org.apache.catalina.session.PersistentManagerBase start
SEVERE: No Store configured, persistence disabled
Feb 27, 2013 10:12:02 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive SpagoBICommonJEngine.war
Feb 27, 2013 10:12:03 AM org.apache.catalina.session.PersistentManagerBase start
SEVERE: No Store configured, persistence disabled
...

Full log examples are attached to this article.

This error is related to Tomcat settings, and is not a bug of Talend Data Quality Portal. The error does not affect the normal use of Talend Data Quality Portal, and thus could be simply ignored. However, the error can also be eliminated by configuring Tomcat as described below.

Resolution

Depending on one whether or not you have already deployed your Talend Data Quality Portal, the procedure to remove this error from the Tomcat's log will vary slightly.

Talend Data Quality Portal is not deployed

Before Tomcat is started for the first time, Talend Data Quality Portal's war files, such as tdqportal.war, cannot be found in Tomcat installation path>/webapp/, because they haven't been deployed yet. In this case, open context.xml under Tomcat installation path/conf/ and uncomment the following line:

<!-- Uncomment this to disable session persistence across Tomcat restarts -->
<!--
<Manager pathname="" />
-->

to read:

<!-- Uncomment this to disable session persistence across Tomcat restarts -->
 
<Manager pathname="" />

Talend Data Quality Portal is already deployed

If Tomcat has already been started, then the tdqportal file and other related folders can be found under Tomcat installation path/webapp/. In this case, follow the procedure:

1. Stop Tomcat server.
2. Open the context.xml file that can be found in each of the following directories:

   Tomcat installation path/conf/
   Tomcat installation path/webapp/tdqportal/
   Tomcat installation path/webapp/SpagoBITalendEngine/
   Tomcat installation path/webapp/SpagoBIQbeEngine/
   Tomcat installation path/webapp/SpagoBIJPivotEngine/
   Tomcat installation path/webapp/SpagoBIJasperReportEngine/
   Tomcat installation path/webapp/SpagoBIConsoleEngine/
   Tomcat installation path/webapp/SpagoBICommonJEngine/
   Tomcat installation path/webapp/SpagoBIBirtReportEngine/

3. In each context.xml, replace all occurences of the following line:

   <Manager className="org.apache.catalina.session.PersistentManager" saveOnRestart="false"/>

   with this line:

   <Manager pathname="" />