Monthly Archives: April 2022

TCC

TCC 22a.1 – Issues With TCC_Touchpoints

So they’ve upgraded saxon8.jar to saxon10.jar (the XSLT and XQuery processor) but the framework (TCC_Touchpoints) that the majority of installs use have the reference to saxon8.jar hardcoded in the init.bat/.sh files. Not sure that hard coded is the right word as you can change it but it’s another thing that would have been nice to know.

So the quick takeaway is that if you are using TCC_Touchpoints at all in your integrations, a change is going to have to be made to the touchpoints itself before it can work at all with TCC 22a.1. Initial testing with this fixed allows for a successful run but it no longer displays the workflow progress of the job.

TCC

TCC 22a.1 – Released! And it’s broke…

So it seems that Oracle has release the much awaited TCC 22a.1 to fix the log4j issue. But it seems to have an issue when the TaleoConnectClient.bat is called which is the case for every scheduled integration. Someplace there is a call to saxon8.jar when this release ships with saxon10.jar. While you’ll be able to run the integration in the GUI, once you try to run a CLI job you’ll get something like this:

C:\onedrive_tt\Client\TCC_Touchpoints\bin\Windows>test22-candidateExport.bat > batchRun.txt
Error: Unable to access jarfile C:\TCC\TaleoConnectClient22a1\lib\saxon8.jar
Error: Unable to access jarfile C:\TCC\TaleoConnectClient22a1\lib\saxon8.jar
Error: Unable to access jarfile C:\TCC\TaleoConnectClient22a1\lib\saxon8.jar
Error: Unable to access jarfile C:\TCC\TaleoConnectClient22a1\lib\saxon8.jar
Error: Unable to access jarfile C:\TCC\TaleoConnectClient22a1\lib\saxon8.jar
Error: Unable to access jarfile C:\TCC\TaleoConnectClient22a1\lib\saxon8.jar
Error: Unable to access jarfile C:\TCC\TaleoConnectClient22a1\lib\saxon8.jar

C:\onedrive_tt\Client\TCC_Touchpoints\bin\Windows>CLS
### ERROR - The default endpoint must be defined with a vaild host. ###
Press any key to continue . . . 

Issue was found the issue last week on 4/7, will try to get a case open on it. In any case a work around is to actually put the saxon8.jar in the lib so it will run but it won’t log or return anything so you have to check the profiler.