Beruflich Dokumente
Kultur Dokumente
5.0_a
Copyleft
This documentation is provided under the terms of the Creative Commons Public License (CCPL). For more information about what you can and cannot do with this documentation in accordance with the CCPL, please read: http:// creativecommons.org/licenses/by-nc-sa/2.0/
Table of Contents
Preface .............................................. v
1. General information ................... v 1.1. Purpose ........................... v 1.2. Audience ......................... v 1.3. Typographical conventions ............................ v 2. History of changes ...................... v 3. Feedback and Support ............... vi
5.1. Configuring session timeout for the Web User Interface ............ 5.2. Configuring access control information for the Studio and the Web User Interface ................. 5.3. Changing the default ports in JBOSS ........................................ 5.3.1. Default port list ............. 5.3.2. Using an alternate binding ................................
26
26 27 27 28
Preface
1. General information
1.1. Purpose
This Installation Guide explains how to install and configure Talend MDM modules and related applications. For detailed explanation on how to use and fine-tune Talend MDM applications, please refer to the Talend Open Studio for MDM Administrator Guide and Talend MDM Web User Interface User Guide. Information presented in this document applies to Talend MDM releases beginning with 5.0.x.
1.2. Audience
This guide is devoted for administrators of Talend Open Studio for MDM and Talend MDM Web User Interface. The layout of GUI screens provided in this document may vary slightly from your actual GUI.
2. History of changes
The below table lists changes made in the Talend MDM Installation Guide. Talend Open Studio for MDM Installation Guide
History of Change Creation of an MDM Installation Guide Updates in the Talend MDM Installation Guide include: -a new hardware and software prerequisites chapter. -Slight modification and reorganization in the MDM server installation chapter. -A new section in the database management chapter to talk about managing the Talend XML database.
v 5.0_a
21/11/2011
Updates in the Talend MDM Installation Guide include: -splitting the MDM IG into two guides: one for Talend Open Studio for MDM and the other for Talend Enterprise MDM Studio. -Updated documentation to reflect new product names. For further information on these changes, see the Talend website.
vi
Hardware requirements
Working
Working
Working
Working
Working
LINUX MANDRIVA Working LINUX DEBIAN UBUNTU LINUX REDHAT LINUX CENTOS HP UX IBM AIX (32bits / 64 bits) / Working Working Working Working Working
1
1. Requires the use of an IBM JVM version 1.6+ 32bits. Only limited support is provided. Contact Support for details. 2. However the graphical mode being not supported only Commandline can be used.
Naming conventions
TMDM_TDQEEMPX-Server-All- TMDM_TDQEEMPX-Server-All- The MDM server rYYYY-VA.B.C r63143-V4.2.2.jar TAC-rYYYY-vA.B.C TAC-r63143-V4.2.2.zip Talend Administration Center: Web-based application used to administrate Talend Integration Suite projects and users.
org.talend.remote.jobserver_A.B.C_rYYYY org.talend.remote.jobserver_4.2.2_r63143.zip JobServer: Standalone execution server Soamanager-rYYYY-VA.B.C soamanager-63143-V4.2.2.jar SOA Manager: helps deploying Web services Jobs
Where: YYYY: Revision number, A.B.C.: Major. Minor. Patch: revision level if relevant. The software modules must be all in the same versions/revisions! This means that both YYYY and A.B.C must match on both: client side and server side.
Third-party softwares
By default, Talend global Installer will install the above both servers. You can still customize the install to deploy everything on just JBoss. However, this configuration requires some expertise. You are also not required to download JBoss prior to installation as the server is included in the install bundle. For further information on Talend global Installer, see the User Guide. Sun Microsystems (JDK or JRE) JVM 1.5+ (but version 1.6+ is recommended) - http://java.sun.com/javase/ downloads/index.jsp Subversion for storing your projects - http://subversion.tigris.org/ or http://www.visualsvn.com/server/ download/
-(Only Linux) A Windows Manager must be installed. -It is highly recommended that the full path to the server installation directory is as short as possible and does not contain any space character. -If you already have a suitable JDK installed in a path with a space, you simply need to put quotes around the path when setting the values for the environmental variable. To install the MDM server using a .jar file, complete the following: Unzip the server file provided by Talend. On Windows, double-click the cross-platform .jar file to run the installer. A language selection pop-up displays. On other platforms, you may execute the .jar file by right-clicking it and selecting the OpenJDK JRE or Sun's JRE. From the language selection pop-up, select an installation language from the list and click OK to close the popup and proceed to the next step. On the Talend MDM welcome page, click Next o to proceed to the next step. Read the license agreement and select the accept option. Click Next to proceed to the next step. Read the JBoss information and click Next to proceed to the next step.
Select the check boxes of the packs you want to install, and then click Next to proceed to the next step. The check boxes of required packs are already selected and unavailable (MDM in this case). If you have a JBoss application server already installed on your machine and you do not want to re-install it, clear the JBoss check box. Browse to where you want to install JBoss and the MDM server, and then click Next to proceed to the next step. A message displays to inform you about the creation of a target directory. If you want to install JBoss as a Windows service, select the Create JBoss Windows service check box and then click Next to proceed to the next step. Read the installation settings, and then click Next to proceed to the next step and start the installation. Two progress bar indicate how much of the installation has been completed.
When the progress bars indicate the end of the installation, click Next to have a confirmation message that the installation is completed successfully. Click Done to close the installer. The MDM server is installed. An MBean is provided to manage the MDM server caches and it is available in the JBoss JMX console. To run the MDM server, execute run.bat (Windows) or run.sh (Linux) in the JBoss.4.2.2.GA folder. To shut the MDM server down, press Ctrl + C in the console window, or run bin/shutdown.bat or bin/shutdown.sh.
10
12
You can simply import your Jobs if they are exported in archive files from older MDM Studios. For further information on importing/exporting items, Routes or Jobs, see Talend Open Studio for Data Integration User Guide. Deploy the Jobs to the new MDM server one by one. For further information, see the Talend Open Studio for MDM Administrator Guide. You can also copy/paste the job scripts (.war or.zip) from their corresponding folder in the old application to the same folder in the new application: jboss-4.2.2.GA/server/default/deploy for wars and jboss-4.2.2.GA/jobox/deploy for zips. But this will not import the job design that you may need at some point. Another limitation with this copy/paste mode is that it is recommended only between two MDM servers that have the same major version (first number of the unique identifier of the version). If the major versions differ, it is very likely that the MDM components will not work with the new MDM Server. If you are migrating between 2 identical versions or 2 versions where only the minor version differs, however, copying the wars or zips will be a lot faster than redeploying the Jobs.
13
On a 64 bit machine with memory aplenty, and with a 64 bit JVM of course, you can set the -Xmx to a high number, say 8 GB, and cacheSize to much more than half of that.
16
17
<?xml version="1.0" encoding="UTF-8"?> <collection xmlns="http://exist-db.org/collection-config/1.0"> <index> <!-- Range indexes --> <create qname="Id" type="xs:string"/> <create qname="AgencyFK" type="xs:string"/> <create qname="Name" type="xs:string"/> <create qname="Firstname" type="xs:string"/> <create qname="Lastname" type="xs:string"/> <!-- Full text index --> <lucene> <text qname="Product"> <ignore qname="Id"/> </text> </lucene> </index> </collection> Navigate back to the top level /db, select your data-container (e.g. Product) and run File - Reindex Collection. If you do not do this step, only new records will be indexed, so the index will be incomplete, and consequently your will be able to search only new records. You can specify range indexes for integers, decimals, dates and strings. You can also create full-text indexes. Please refer to http://exist-db.org/indexing.html. It is recommended to set the element name by QName instead of Xpath. Therefore, it is a best practice to always name the PKs the same, for instance Id, so if you set an index on this QName, all PKs will be indexed.
18
eXist creates tmp files in the first place because originally native XML databases were containers for big, if not huge XML documents, and deserializing those in memory was hardly an option. However, most of the time this use case does not apply to MDM where you will usually have numerous small documents. In addition, since eXist is an open-source database, we have modified it to optionally not create temporary files. The standard installation by the graphical installer uses this modified version by default. To activate the option, add the following options in JAVA_OPTS:
-Dorg.exist.xmldb.inMemory.remote.content=true -Dorg.exist.xmlrpc.inMemory.retrieve.content=true So at the end this is how the JAVA_OPTS variable could look like in run.bat:
19
In the Password field, enter 1bc29b36f623ba82aaf6724fd3b16718. The administrator password is specified in jboss-4.2.2.GA/bin/mdm.conf. If required, enter a favorite in the Title field, MDM DB for example, and then click the Save button to the right of the page. The new favorite is listed in the Favorites list. The next time you want to launch the administration client, you can double click this favorite to fill in the login information instead of entering it manually. Click OK to close the login page and open the administration client.
20
Standalone eXist
From this page, you can see the content of the eXist database. You can also use the button on top of the page to carry out different management options on data including creating backups.
21
Standalone eXist
If needed, change the admin password in: <cluster dbaPassword=[enter your password here] Increase the cache memory in: <db-connection cacheSize=xxM to no more than half of the allocated heap size (i.e. the previous -Xmx parameter in JAVA_OPTIONS). Increase the cache memory in: <db-connection collectioncache=yyM to no more than half of the cache and only if you are using a lot of containers/collections (heavy use of versions and revisions in Talend Open Studio for MDM. Activate automatic backups (recommended) by uncommenting the section: <job type=system name=backup Backups are triggered by default every 6 hours. This may be changed using a cron like syntax.
22
Standalone eXist
A typical value is 8088. The default value (8080) will clash with the port used by the JBoss and the MDM Server.
23
Standalone eXist
the WEB-INF/data directory to {eXist Dir}/webapp/WEB-INF/data if you want to restore the exact same database. At this point you can start up the MDM Server.
24
Change the value of the default session timeout as desired. Save your modifications. The new session timeout parameter has been set for users connecting to the Web User Interface.
5.2. Configuring access control information for the Studio and the Web User Interface
The default authorized users for Talend Open Studio for MDM and Talend MDM Web User Interface use the following authentication information: admin as the login and talend as the password for the Studio; user/ administrator as the login and user/administrator as the password for the Web User Interface. It is possible for an administrator to change this access control information, if required. To configure new logins and passwords, complete the following: Browse to the login-config.xml file in: JBoss\server\default\conf Double-click this file to open it and search for the following tag:
26
Change the default access control information in the following elements, as desired:
<module-option name="logins">admin,administrator,user</module-option> <module-option name="passwords">talend,administrator,user</module-option> Save your modifications. The new logins and passwords have been set for the Studio and the Web User Interface.
27
28