This article explains the changes coming to the Talend Cloud console with the new release of Fall '18.
Talend has merged Talend Integration Cloud functionality with the Talend Management Console Application. What does that mean? It means, Cloud merged all management functions into a single application, improving the flow of deploying Jobs and Data Services. Some of the new functionality and application improvements include:
New access to Operations, Environments, Promotions, and Configurations: they are now all in one application.
New terminology in the Cloud UI:
Flows are now called Tasks.
Jobs are now called Artifacts.
Execution Plans are now called Plans.
New view changes in the Management Console tab. Note that existing flows will be automatically migrated to TMC.
New view changes in the Engines tab.
The Talend Management Console - Fall '18 Release video reviews the changes and demonstrates the new UI, so you know what to expect.
New view changes to the Management Console tab
See the different environments in the space along the top of the tab. Note that existing flows are automatically migrated to TMC. You can change between the different environment tabs to see what type of Jobs and Flows exist within each environment.
Click Tasks to view and modify existing Tasks previously created in TIC.
To create a new Task or Plan, select the Add drop-down button, complete the information according to your specifications, then click the green Go Live button.
After the Task or Plan finishes, you can review the Run process and logs. By selecting the pencil icon next to Execution or Configuration, you can edit the Runtime settings and the Task and Plan parameters.
New view changes to the Engines tab
Found within the Remote Engine view, Talend introduces Run Profiles.
These enable and disable data services functionality in the remote engine.
In addition to running Batch Integration Jobs, you can also run Routes in Microservices. You can select to run, one, both, or none of the two options.
The INFO tab displays the pairing key, and allows you to select the appropriate link to the version of Remote Engine required on your end.
... View more
Another good thing to check related to the memory settings is the setenv.bat (Windows) or the setenv.sh (Linux) to see if the relevant parameters are set correctly for their environment. If they are small or the default values, increase these. The parameters are below: -Xms -Xmx -XX:MaxMetaspaceSize It is found in the path: C:\Talend\6.x.x\tac\apache-tomcat\bin OR <TomcatPath>/bin Documentation: https://help.talend.com/reader/vuI_X~V6unFjTgNxRMPcLw/Ij~7tBlW8im63rAGnGHT3A
... View more
How to update the auto-refresh rate and reload page settings for the TAC Project Authorization page and the Job Conductor Page.
You need to go into the TAC database and locate the table configuration for both the Project Authorization Page and the Job Conductor Page.
Go into the TAC db.
Select the current TAC Schema.
Go into the Configuration table.
Run the following query:
"select * from configuration where `key` like '%refresh%';"
This will show the variables within the TAC db that control the auto-refresh rate of the Project Authorization page, and those that control the refresh page setting for Job Conductor, as shown below:
The variable that controls Project Authorization is admin.userProjectAuthorization.conf.uiAutoRefreshFrequency and for Job Conductor, it is scheduler.conf.uiAutoRefreshFrequency.
Set the variables according to your requirements. For example:
Setting admin.userProjectAuthorization.conf.uiAutoRefreshFrequency to 90 causes it to refresh every 90 seconds. 0 or -1 doesn't stop the auto-refresh because it is a full-time refresh, and will instead ensure it auto-refreshes every 1 second.
By default, scheduler.conf.uiAutoRefreshFrequency is set to 0 or 1 to ensure it refreshes every 1 second. Change it as necessary for your environment.
... View more
While installing MDM, you may encounter the following error message:
Could not find the feature Talend MDM - Bonita BPM Integration (Required). (org.talend.mdm.bos.feature.group) in the following repositories [https://update.talend.com/Studio/...../6.4.1].
If you manually navigate to this location, there are no files to download using the installer and the zip file.
After performing the installation of Talend Studio, the error message Installation BPM is REQUIRED. Click here to complete the installation appears. At this point, Talend checks for updates. All updates are successful except BPM, which was not updated successfully. Selecting it again or trying to install additional packages does not work.
This may be due to one of the following causes:
An error in the way you configured your proxy with Studio
Corruption in the p2 Studio repository
Network errors prohibiting the file from downloading correctly
Contact Talend Support for a new p2.zip file.
Back up the Studio directory.
Extract the Zip file into the Studio directory.
In Studio, navigate to Help > Install Additional Packages > Talend MDM - Bonita BPM Integration (Required), then click Next.
Select Local Folder, then select your new p2 folder where the Zip file was extracted.
... View more
Attempting to generate or deploy a new Job in TAC results in the following error:
Connection to Generator Failed (CommandLine)
This error can occur for various reasons; common possibilities are:
Files in the commandline-workspace directory are not accessible to the CommandLine service. This can occur if the CommandLine is started under different OS user accounts, like root.
A corrupted version of a project, Job, or dependencies is in the commandline-workspace directory, preventing the CommandLine from generating the Job.
The CommandLine was not started, or is not running properly.
See the CommandLine log (Cmdline_Install_Dir/studio/commandline-workspace/.metadata/.log) for details.
Delete the commandline-workspace directory, and restart the CommandLine service.
Stop the CommandLine by running stop_cmdline.sh or stop_cmdline.bat, for example:
sudo service talend-cmdline-6.4.1 stop
Delete the commandline-workspace directory, for example:
rm -rf TALEND_HOME/cmdline/studio/commandline-workspace
Then restart your CommandLine service, for example:
sudo service talend-cmdline-6.4.1 start
... View more