Script Execution

Taleo Connect Client workflow execution in a production environment is run by a command line script. The command line script can be scheduled to run automaticaly.

There are three possible command line scripts to launch TCC execution. They are the same for all operating systems. The only difference being that Windows uses .bat files and Linux uses .sh files. The following files can be specified in a command line script:

• The TCC batch file that is included in the installation package.

  TaleoConnectClient.bat

• An import or export configuration file.

  <touchpoint>_<action>cfg.xml

• An import or export request file.

  <touchpoint>_<action>_ld.xml

  <touchpoint>_<action>_sq.xml

• An import or export result file.

  <touchpoint>_<action>_result_<date_time>.csv

  <touchpoint>_<action>_result.xml

  <touchpoint>_<action>_<date_time>.txt

  filename.other

The three possible command line scripts will have the following layout. The path is the absolute or relative location of the specified file.

• “path\TaleoConnectClient.bat” “path\configuration file” “path\request file” “path\result file”

  The first script is the typical use for Taleo Connect Client where both the request and response message files are specified explicitly. The workflow configuration usually contains only communication information that applies to a variety of different messages.

• “path\TaleoConnectClient.bat” “path\configuration file” “path\request file”

  The second script is typical of a scheduled integration process where the request message varies and the response message file is generated based on the timestamp.

• “path\TaleoConnectClient.bat” “path\configuration file”

  The third script is typical of a specialized workflow with extensive pre and/or post-processing that only applies to a single integration process. In this situation, the request and response files are often known and can thus be specified in the configuration itself.