Did anyone have expereinced with Remote job adapter? We are currently testing Tidal version 18.104.22.1689 with the remote adapter version 22.214.171.124. We have created a remote adapter connection, and remote adapter Tidal jobs. Once in a while the job runs successfully, and some other time, the same job completed abnormally with "Error Occurred" status. In addition, occasionally, the Tidal agent "Bridge" crashed which also makes the remote adapter also to crashed. I have contacted CISCO and we are working on this, but will like to know if any one have previous experienced with the "Remote job adapter" in Tidal 6X?
See attached file...
Cisco Workload Automation (formerly known as TES) Customer Advisory Community
Just curious to know if your issue has been resolved and what the fix was. Is the remote job adapter been worth the investment?
We ourselves do not use remote job adapters since we can use powershell and other remote commands in Windows to run jobs on another server that doesn't have an agent and the use remote ssh on the Linux side.
This has not been resolved yet and still an open case with Cisco. Last update I received is that it is being worked by the Cisco Development team. We are insterested in use the agentless features if possible but it looks like we might be one of the fews if any exploring this area, so we don't need to have an agent installed on the apps tier. Will give an update as it becomes available.
This document explains the logic to develop Tidal Enterprise
Orchestrator workflow to automate the process of creating vCenter
Resource Pool* vSphere Power CLI must be installed either on the TEO
server or vCenter* vMA can also be used to achieve the same...
IntorductionCisco Process Orcehstrator (CPO) ships with the webservices
adapter that can be used to make Web Service API call to REST or SOAP
based applications. Before a sample workflow to make SOAP API calls
using CPO, lets understand some of the fundam...