Successful Talend Cloud Installation, Download, Configuration, Development and Deployment Steps
  • In order to launch Talend cloud either we need a license or we can take a free trail for 14 days.
  • Following is the URL to sign up for free trail.
  • https://iam.us.cloud.talend.com/idp/trial-registration
  • Once registration is complete, we will receive an email to verify the details and some additional information need to provide. Once registration is complete, we can login from following URL-



  • Once you login into Talend Cloud you will see the dashboard as below screen.


  • Here you can select any application according to your requirement but first of all you need to do some configuration in Management console, So I am going to select Management console.
  • In management console we need to follow below steps.


Step 1: Add and Pair Engine



  • By default, there is a Talend Cloud Engine to run your Talend Jobs once you publish the job into Talend Cloud, but this is a common server and will take lot of time to execute a job. Also, this is not accessible to users for manual file upload, download etc.
  • So, for running our Talend Jobs we need to set up a remote engine on a dedicated server (on premises or cloud). For downloading the Remote Engine, we need to go into downloads, also you can download Studio from this section.



  • Once Download is complete extract zip for Remote Engine and Studio into different Folders and follow the below procedure for Installing the Remote Engine manually
  • Extract the archive file to a directory of your choice (<RemoteEngineInstallationDirectory>).
  • Edit the <RemoteEngineInstallationDirectory>/etc/org.talend.ipaas.rt.pairing.client.cfg file.
  • Set the pairing.service.url parameter according to the region of your Talend Cloud account:pairing.service.url=https://pair.<region>.cloud.talend.com
  • The region is reflected in your Talend Cloud URL following this pattern: <region>.cloud.talend.com. For example, if your URL is https://us.cloud.talend.com, you must enter the corresponding AWS USA East value.
  • More information in Talend Cloud regions and URLs with a list of the URLs to use for each data center.
  • Browse to the bin folder of the Remote Engine installation directory, then launch the trun.bat file as an administrator.
  •  Install the wrapper:
  •  karaf@root()> feature:install wrapper
  • Set up the installation of the service, using Talend-Remote-Engine as the service name:
  • karaf@root()> wrapper:install -n Talend-Remote-Engine
  • The following files are created in the <RemoteEngineInstallationDirectory>\bin folder:
  • Talend-Remote-Engine-wrapper.exe
  • Talend-Remote-Engine-service.bat
  • The Talend-Remote-Engine-wrapper.conf file is created in the <RemoteEngineInstallationDirectory>\etc folder. 
  • Start the Command Prompt as an administrator.
  • Browse to the bin folder of the Remote Engine installation directory then type the following command:
  • Talend-Remote-Engine-service.bat install
  • Now your Talend Remote Engine Windows service is running.
  • Optional: If needed, you must configure the proxy settings before pairing the Remote Engine.


Step 2: Add Projects and Users/Collaborators in the project




  • For adding a project click on add project and provide the Name, GIT URL, Owner and Project description. For adding more people into this project, you can visit Collaborators section.


Step 3: Create Sample Job in your Studio and publish in Talend Cloud
  • For development of jobs we need to start studio. For first time we need to provide TMC URL, username and password in splash screen.





  • Once configuration is complete select your project and click on finished.



  • Now you can create a sample job in Studio and once done right click on the job and select publish to cloud to publish the job to Talend Cloud.


  • Select the workspace an click on Finish.


  • To check the job that was published to cloud from the studio, click on MANAGEMENT in management console. The jobs published can be seen as Artifacts and jobs that got executed can be seen as Tasks

  • Click on Artifacts to check if the job got published into the cloud.


  • As we can see, there are two Artifacts in the console. sample_job that got published from the Talend Studio
We will learn how to configure Artifact Repository, Environment, Promotions, User, Roles and many more things in next part of this tutorial.





Comments

  1. Great read! Thank you for such useful insights. Visit here for latest tech courses on TALEND BIG DATA ONLINE TRAINING

    ReplyDelete

Post a Comment

Popular posts from this blog

Migrate your data in Google Cloud Storage using Power of Talend

Talend Open Studio Errors (Compile and Run)