Thanks Keith.
I agree there must both be other values that could be supplied by default and other users that have solved this problem before. I too would like to know how others have addressed it.
For the time being this problem has been made moot. For other reasons, I have decided to change how I am approaching the related actions/flows, and eliminated the dependency on running a REST API call against CARA from within CARA.
That being said, for the benefit of others, how I solved it before changing direction was as follows:
- Created a ServerType: CARAMgtServer
- Assigned CARA management server agent to new server type, (Our CARA management server is hosted on Linux)
- Mapped CARAMgtServer to the relevant process.
- Created a command line action that ran this command "hostname -I", and captured StdOut to a parameter.
- Added that action to the relevant process.
- Flagged that action to "execute on a different server", and selected the CARAMgtServer
When the command line action runs, it runs on the CARA Management Server (ROC host) and captures the servers ip address to a parameter. I could then use that parameter later in a REST call action.
BTW Keith-Puzey-CA, I think I still like your idea of querying the database better than what I just described and would look into it if I still needed that solution.