topic Re: How to make tSAPInput component work in TOS 6.0.1 under LINUX in Talend Studio

How to make tSAPInput component work in TOS 6.0.1 under LINUX

Anonymous — Sat, 16 Nov 2024 07:39:59 GMT

Hi,

I have a job using tSAPInput and working fine in TOS 4.1.2 (windows). I recently migrated to TOS for DI 6.0.1 (LINUX). I have downloaded the tSAPInput component on Talend Exchange website, added a user component folder in TOS preferences to import the custom component, imported exrternal JAR to add JCO and JCO3 modules. Everything seem to be good but when i try to run or build my job i have error messages.

I tried different release of the sapjco and sapjco3. I'm not sure of which one i have to use and if SAPJCO and SAPJCO3 installed at the same time is a good idea.

Can you help me. My server is under Linux 4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04) x86_64

Thank you for help

Yannick

Re: How to make tSAPInput component work in TOS 6.0.1 under LINUX

Anonymous — Thu, 13 Sep 2018 09:51:24 GMT

last 4 screen captures

03InstalledJRE.PNG
04JAVAExecParameters.PNG
05ErrorWhenRunning.PNG
06ErrorWhenBuilding.PNG

Re: How to make tSAPInput component work in TOS 6.0.1 under LINUX

Anonymous — Tue, 02 Oct 2018 09:48:50 GMT

Hi,

I finally figured out what was wrong with my way of integrating the tSAPinput component into TOS for DI 6.0 (LINUX). I restarted from the beginning the following procedure :

I downloaded the component on Talend Exchange, I unzipped it into a folder that i indicated in Talend's settings (Preferences/Talend/Components)
I downloaded the external jar sapjco3 for LINUX 64bits, added in .bash_profile file the 2 following lines :

export CLASSPATH = / infocentre / TalendCrontabJobs / SAPJCO / sapjco3.jar
export LD_LIBRARY_PATH = / infocentre / TalendCrontabJobs / SAPJCO /

I opened the jobs that use the tSAPinput and tSAPconnection components to select the SAP JCO release (SAPJCO3.* instead of Talend SAP API)

The compilation phase passes when i execute or build my JOB and there is no error then at runtime.
Only one version of sapjco is needed (version 3 is required).

The two blocking points were as follows:
-Not having modified the tSAPinput and tSAPconnection components to use the SAPJCO3 jar (which blocked the compilation phase)
-Did not declare paths to the SAPJCO installation folder (which caused the execution to crash)

Yannick