Overview

MDM's webUI search is case insensitive using xmldb (eXist/Qizx), but it is case sensitive using RDBMS db.

Environment

MDM 5.2.1 using RDBMS db.

Symptoms/Description

Starting with 5.2.1, Talend MDM supports RDBMS db. The webUI search is case insensitive using xmldb (eXist/Qizx), but it is case sensitive using RDBMS db.

Resolution

• For a MySQL db, refer to Case Sensitivity in String Searches on the MySQL site.

• For an Oracle db, you can create a logon trigger such as:

  create or replace
  TRIGGER SYSTEM.SET_NLS_ONLOGON
  AFTER LOGON
  ON DATABASE
  DECLARE
      cmmd1 VARCHAR2(100);
      cmmd2 VARCHAR2(100);
  BEGIN
      cmmd1:='ALTER SESSION SET NLS_SORT=BINARY_CI';
      cmmd2:='ALTER SESSION SET NLS_COMP=LINGUISTIC';
       
       EXECUTE IMMEDIATE cmmd1;
       EXECUTE IMMEDIATE cmmd2;
      
  END SET_NLS_ONLOGON;

  Note: From 5.3.0 , there is a minor feature about the issue, refer to TMDM-5352 - Add an option to make CONTAINS operator case insensitive - CLOSED.

Overview

Due to Talend Master Data Management (MDM) licensing restrictions, you may be required to set up CPU affinity.

Prerequisite

A MDM Server service must be enabled.

Steps to proceed with systemctl

1. Edit the /etc/systemd/system/talend-mdm-7.0.1.service file, and add a new line in the Service section:

   CPUAffinity=<cpu id>

   This parameter takes a list of CPU indices or ranges separated by either whitespace or commas. CPU ranges are specified by the lower and upper CPU indices separated by a dash.

   

    

2. Reload the systemctl daemon:

   systemctl daemon-reload

   

    

3. Start the service:

   systemctl start talend-mdm-7.0.1.service

   

    

Steps to proceed with legacy service

1. Edit the /etc/init.d/talend-mdm-6.0.1 file, and update the function start():

   taskset -a -c <cpu id> ./start_mdm.sh

   This parameter is used to specify a numerical list of processors. The list may contain multiple items, separated by commas and ranges, for example, 0, 5, 7, 9-11.

   

    

2. Start the service:

   service talend-mdm-6.0.1 start

   

    

Retrieve a process's CPU affinity

1. Check the status of the service to get the PID of the MDM Server:

   systemctl status talend-mdm-7.0.1.service

   

   Or use this command:

   ps -ef |grep mdm

    

2. Use the taskset command to get the current affinity list:

   taskset -c -p <PID>

   

    

This exception happens when launching a workflow from Talend MDM. Talend MDM leverages the mdm_context variable to serialize and pass the model and entity data to the workflow engine embedded in Talend MDM. This error occurs when the workflow engine is unable to deserialize the data back into the mdm_context variable in the workflow.

Environment

This happens on Talend MDM 6.0, 6.1, and 6.2 with the Community Bonitasoft 6.5.x workflow engine. Note that this is OS independent. The Community Bonitasoft 6.5.x portal should be running on Java 7.

Symptoms/Description

You will receive the following exception as show below in the mdm log file:

return org.talend.mdm.workflow.client.MDMContextImpl.deserialize(mdmContextBytes).extractCompressedSchema(schemaStr);> depends on org is neither defined in the script nor in dependencies. ( )
    at org.bonitasoft.engine.expression.impl.GroovyScriptExpressionExecutorCacheStrategy.evaluate(GroovyScriptExpressionExecutorCacheStrategy.java:140)
    at org.bonitasoft.engine.expression.impl.ExpressionServiceImpl.evaluate(ExpressionServiceImpl.java:86)
    at org.bonitasoft.engine.core.expression.control.api.impl.ExpressionResolverServiceImpl.evaluateExpressionWithResolvedDependencies(ExpressionResolverServiceImpl.java:215)
    at org.bonitasoft.engine.core.expression.control.api.impl.ExpressionResolverServiceImpl.evaluateExpressionsFlatten(ExpressionResolverServiceImpl.java:120)
    at org.bonitasoft.engine.core.expression.control.api.impl.ExpressionResolverServiceImpl.evaluate(ExpressionResolverServiceImpl.java:83)
    at org.bonitasoft.engine.bpm.model.impl.BPMInstancesCreator.createDataInstances(BPMInstancesCreator.java:582)
    at org.bonitasoft.engine.execution.ProcessExecutorImpl.initialize(ProcessExecutorImpl.java:394)
    at org.bonitasoft.engine.execution.ProcessExecutorImpl.start(ProcessExecutorImpl.java:743)
    at ... 32 more. ( )
    at  Caused by: groovy.lang.MissingPropertyException.: No such property: org for class: BScript1 ( )
    at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50)
    at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231)
    at BScript1.run(BScript1.groovy:4)
    at org.bonitasoft.engine.expression.impl.GroovyScriptExpressionExecutorCacheStrategy.evaluate(GroovyScriptExpressionExecutorCacheStrategy.java:134)
    at ... 39 more. ( )

Resolution

Make sure you have at least one TalendMDMContextConnector in the entire workflow as shown below. You cannot have an mdm_context object without having a TalendMDMContextConnector. This error will happen if you remove all TalendMDMContextConnector in all the steps of your workflow.

Related Jira Issues

TMDM-10105 - [Workflow] Dependencies required for mdm context are brought by MDM connectors' dependencies - New

Overview

Using some Firefox versions in Talend 6.0.1 can cause the menus to become unresponsive or not work.

Resolution

Use a supported browser for Talend 6.0.1.

Compatible Web browsers

Please refer to the table below for a summary of supported Web browsers. 

^{1. Talend maintenance releases will support the most recent browser version at the time of the release.}

Overview

This article describes how to change Talend MDM (Master Data Management) server default ports.

Environment

This article applies to MDM Server from version 5.1 onwards.

Description

If you want to run multiple MDM server instances on the same machine, you need to change the MDM default ports. You can choose from three predefined ports in the ${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml file:

• ports-default
• ports-01
• ports-02

The MDM default port is ports-01, and its HTTP port is 8180.

Resolution

To change the MDM default port, follow these steps:

1. Modify the file jboss-4.2.2.GA\server\default\conf\jboss-service.xml as follows:

   <mbean code="org.jboss.services.binding.ServiceBindingManager"
          name="jboss.system:service=ServiceBindingManager">
       <attribute name="ServerName">ports-02</attribute>
       <attribute name="StoreURL">${jboss.home.url}/server/default/conf/bindings.xml</attribute>
       <attribute name="StoreFactoryClassName">
           org.jboss.services.binding.XMLServicesStoreFactory
       </attribute>
   </mbean>
   

2. Modify the mdm.conf file as follows:

   http.server.port=8280

   If you use the Qizx database (deprecated), you must also update the following URL to take into account the new port number:

   qizx.server.url=http://localhost:8280/qizx/api

You may want to browse the JBoss documentation for information about running multiple instances of JBoss on the same machine, or see the same question answered on Stack Overflow.

Overview

Talend MDM (Master Data Management) provides a beforeSaving_xxx process to validate the data when you update a Talend MDM record. Furthermore, it is possible to change the XML record in beforeSaving_xxx by providing one special output variable, output_item. This article explains how to do it.

Environment

This procedure applies to Talend MDM v5.1.x or higher.

Resolution

In a beforeSaving_xxx process, there is a special output variable, output_report, used to show the update report message as in the formatted string below:

<report> <message type="info|error"> xxx report message xxx </message> </report>

• info: validation OK.
• error: validation failed.

There is another output variable, output_item, used to change the XML record as in the formatted string below:

<exchange> <item> xxx the updated xml record string xxx </item> </exchange>

Here is an example of how to change the XML record in a beforeSaving_xxx process:

The beforeSaving_Entity_3 process contains 2 steps: Change and Check.

1. Change the step as below:

   

2. Check the step as below:

   

Steps to reproduce the issue

1. Import mdmitems.zip (attached) to the Studio, then deploy all items to MDM server.
2. Import jobs.zip (attached) to the Studio, then deploy the 2 Jobs to the MDM server.
3. Log in to the Web User Interface, create one Entity_3 record, and save it.
4. Update Field_2 and Field_3, then Save. The Date will be updated with the value of the current time.

The files jobs.zip and mdmitems.zip are exported from Talend 5.3.1.

Related Jira Issues

TMDM-1816 - Let a before saving process alter the item before it is committed to the db - Closed

Overview

Talend MDM Web UI may generate an exception showing that the connected user does not have sufficient rights to delete an item. This error is due to an incorrect configuration or a misuse of the user profiles. This article gives a detailed description of the issue, of the different default roles in MDM, and provides information on how to avoid this issue.

Symptoms

In the Web User Interface of Talend MDM, the following exception appears when trying to delete a record:

You can find a detailed stack trace in the log file, stored in Talend MDM server installation path\jboss-4.2.2.GA\server\default\log\server.log.

The main reason for this exception is that the connected user has a role which does not permit him to delete a record. This error is therefore expected in normal operating conditions of Talend MDM, as it helps prevent a user with insufficient rights (or a wrong role) to perform certain actions.

Often, this error is actually related to a misconfiguration of the user profile.

Note: Talend MDM allows a user to hold multiple roles, but the most restrictive one will apply in the Web UI.

In this example, the most restrictive role is System_View.

So even if the user also has a System_Interactive role that would allow him to perform the delete operation, the System_View role will apply in the Web UI.

Resolution

There are a number of default roles that you can assign to a user in the Web UI. When defining a new user in the Web UI, you must be sure to select one of the default roles for this user.

The MDM server is delivered with the following default roles: System_Admin, System_Interactive, System_Web, and System_View.

Try to select only one system role and one customized role. Below are the steps to define correct roles for a specific user:

1. Connect to the Web UI portal as an admin user.
2. Go to the Administration tab and select Manage users.
3. Select the defined user and go to the Roles tab.
4. Select two roles for the user: one system role and one customized role.

   

Overview

The Talend MDM (Master Data Management) Staging Area stores non-validated data. How can you validate the data in the Staging Area? You can do it using a Talend Job and the Web User Interface, as shown below:

Environment

This procedure applies to versions of Talend MDM before 6.0.

Resolution

Talend MDM provides a REST API to perform a staging area validation. You can POST the REST URL, as follows:

1. Create a Job, add a tRESTClient component onto the design workspace, and set the HTTP Method to POST.

2. In the URL field, type one of the following URLs:

   • Before 6.0, the URL is:

     http:/ /localhost:8180/datamanager/services/tasks/staging/TestDataContainer/?model=TestDataModel

   • After 6.0, the URL is:

     http:/ /localhost:8180/talendmdm/services/rest/tasks/staging/Product

     

      

3. Run the Job by pressing F6. The Job invokes the Staging Area validation and the Talend MDM server console outputs the following:

4. In the Staging Area view of the Web User Interface, you will find 17 records that passed the validation.

Steps to reproduce the issue

1. Import mdmitems.zip (attached) to the studio, deploy all the items to MDM servers.
2. Import jobs.zip (attached) to the studio, run the Job loadjob to load the data into the datacontainer Entity in the Staging Area.
3. Run the Job tRestClient, it will invoke the Staging Area validation and move the data to the master area.

Overview

Talend MDM permits you to export master records from the Web UI. By default, the configuration allows you to export a maximum of 1000 rows from the Web UI, but it is possible to modify the parameter for this option.

Description

You can export master records using the Export button in the Data Browser tab in the Web UI.

By default, the connected user can only export a maximum of 1000 records, but it is possible to modify the parameter for this condition in the installation_path/mdm/jboss-4.2.2.GA/server/default/conf/mdm.conf file.

Modify the max.export.browserecord parameter in this file to increase the maximum of exported records.

#Browse Record web ui max export records count
max.export.browserecord=100000