Talend-error "Cannot connect to server" while trying to run a job from TAC

I recently ran into this error and did not a find an ounce of help on the Talend-forge. I ran into this error after changing the IP of Job-Execution Server. The TAC seemed to connect to it okay because I could generate and DEPLOY to the server. However, when I try to run a job is when I was running into this issue.

However, restarting the JobServer, Commanline and TAC will save you huge trouble when ever you have config changes on any one piece of the puzzle.

In my particular issue, since I was able to generate a job, the problem is not with the commandline but with the JobServer. So restarting the JobServer saved me!

Happy Talending,
Praveena

Talend Error - Unable to generate a job on TAC

Check to see if the user under the Settings --> Users --> SVN credentials are properly configured and saved.

You run into the, "Unable to generate a job"  error even when you do not have compilation issues is due to connectivity to the SVN.

Happy Talending!

Praveena

Talend - Cannot import jobs Error

Sometimes, when you login into a project, you might not be able to import jobs to a project. The import option is completely grayed out in the "Project" Menu or the context menu of Jobs. This happens if you are not authorized as a user in the project on TAC. To solve this problem, request your Talend Administrator to authorize you as a user of this project.

Login into TAC.
Under Settings Menu ---> Choose Project Authorization --> Add a user to the project that you need IMPORT permissions on. You could drag-and-drop the users to a project on this page.

Happy Talending!
Praveena

How to run Jobs remotely on TIS?

If you have JobServer installed on your box, then running Jobs remotely involves two steps.

1) Configure your TIS to point to the remote Job Server
2) Run the Talend Job fro the studio on the remote Job Server.

Once you configure your remote job server in the TIS preferences, you can run the job remotely by configuring the Target Exec tab of "Run" Talend Job.

I do not have Job Server installed. But if you do, you could run the Talend Job from your local studio on a remote server. Very handy!

Happy Talending!
Praveena

How to capture Talend Job Activity into databases - Activity Monitoring Console

It is often useful to capture the statistics of a job to monitor the job performance and error codes. Talend has three ways to capture this information.

1. On console
2. In FileSystem
3. On Databases

My personal choice is to capture the logging information in a database since it will be very useful to store history and easy to track the trends of the job activity with a query. This could be very handy to identify any performance bottlenecks.

So here are the table definitions for the logs, stats and volume catchers used by the AMC. You can easily get these definitions by exporting the meta-data from tlogcatcher, tflowmeter and tstatcatcher to Generic Schemas in the repository and reusing them later. Here they are served without going through the pain of creating the metadata again :)

Create these tables on your database and configure your project to capture this information in the database so that the AMC can retrieve this info from database and display it for you.

CREATE TABLE [dbo].[logCatcher](

[moment] [datetime] NULL,

[pid] [varchar](20) NULL,

[root_pid] [varchar](20) NULL,

[father_pid] [varchar](20) NULL,

[project] [varchar](50) NULL,

[job] [varchar](255) NULL,

[context] [varchar](50) NULL,

[priority] [int] NULL,

[type] [varchar](255) NULL,

[origin] [varchar](255) NULL,

[message] [varchar](255) NULL,

[code] [int] NULL

) ON [PRIMARY]

GO

CREATE TABLE [dbo].[flowMeter](

[moment] [datetime] NULL,

[pid] [varchar](20) NULL,

[father_pid] [varchar](20) NULL,

[root_pid] [varchar](20) NULL,

[system_pid] [bigint] NULL,

[project] [varchar](50) NULL,

[job] [varchar](50) NULL,

[job_repository_id] [varchar](255) NULL,

[job_version] [varchar](255) NULL,

[context] [varchar](50) NULL,

[origin] [varchar](255) NULL,

[label] [varchar](255) NULL,

[count] [int] NULL,

[reference] [int] NULL,

[thresholds] [varchar](255) NULL

) ON [PRIMARY]

GO

CREATE TABLE [dbo].[statCatcher](

[moment] [datetime] NULL,

[pid] [varchar](20) NULL,

[father_pid] [varchar](20) NULL,

[root_pid] [varchar](20) NULL,

[system_pid] [bigint] NULL,

[project] [varchar](50) NULL,

[job] [varchar](50) NULL,

[job_repository_id] [varchar](255) NULL,

[job_version] [varchar](255) NULL,

[context] [varchar](50) NULL,

[origin] [varchar](255) NULL,

[message_type] [varchar](255) NULL,

[message] [varchar](255) NULL,

[duration] [bigint] NULL

) ON [PRIMARY]

GO

These table definitions are for SQL Server.

Happy Talending!

Praveena

Diff Tool in Talend - Compare Jobs

Often times, we need to do a comparison between different versions of Talend Jobs. It could be for troubleshooting purposes or for logging the "Release Notes" for developers to help with maintenance.
A very useful feature for diffing purposes is "Talend's Compare Job" available only in TIS. This could save lot of time for developers to understand what has changed (especially with minor changes) without even opening the job.

Screenshots follow.

The save to HTML file is very useful when we are trying to log all the changes in a release by running the diff on the DELTA of files that have been modified in a release.

Happy Talending!
Praveena

Talend Migration from 4.X to 5.X

Recently, we started working on Talend Migration from 4.X to 5.X. One biggest surprise we encountered was, the Talend migration of jobs happens automatically without a message for confirmation.

Something in lines of "The migration is about to start. Do you want to proceed, Yes/No"

This means that if you opened a Talend 4.X job in TIS/TOS 5.X studio, the job is automatically migrated to 5.X. Since, we had an unplanned/accidental migration, we had to revert the code back to 4.X in sub-version. But we had several issues when reverting the code back. This post is to share our experiences about the migration.

Cannot find Talend.Project error. Classic error!! If you look in your subversion, you would see the talend.project file but the studio complains that it cannot find it. We still do not know which one action solved this error but doing the following helped us resolve the error.

1. Release all the locks in Talend using TAC.
2. Make sure that the project url to subversion is reachable.
3. Make sure that the account used to add a project in subversion has sub-version access privileges to the project.
4. Make sure that the project references has the authorization set up properly.
5. Make sure that the subversion url is valid and the credentials are good.
6. Make sure each user in the TAC has an svn login configured.

Cannot give a detailed screenshots for this exercise but let me know if you run into a similar issue during migration. Would be happy to help!

Error - Talend.Project doesn't exist

Happy Talending!

Praveena