[OO Tip] SSH using logon/shell/logoff operators ignore "sessionId"
It is expected that a Secure Shell (SSH) session using logon/shell/logoff operators should use the sessionId passed from the subflows in later versions of OO 10.01, 10.01.001 similarly to how it was handled in 9.00.
Using Operations Orchestration (OO) 10.00 the following flow design works:
- Main flow starts a subflow to create an SSH session (operation: SSH Logon found at "/Library/Operations/Remote Command Execution/SSH")
- Main flow gets the sessionId output from the subflow (SSH Shell found at "/Library/Operations/Remote Command Execution/SSH")
- Main flow starts a subflow to execute a command via the SSH session, passing along sessionId
- Main flow starts a subflow to logoff from the SSH session (SSH Logoff found at "/Library/Operations/Remote Command Execution/SSH")
After applying the 10.01 patch, this does not work anymore. It turns out that a SSH session using logon/shell/logoff operators only works in a single flow, it's not passed through from and to subflows. However, while the actual input is populated with the correct value, the sessionId is ignored.
Additionally the patch 10.01.001 shows the same behavior as 10.01.
The Session ID is not ignored, however the session context itself is not shared between parent flows and subflows. This is done intentionally, for backwards compatibility with version 9.00.
In OO version 10.00, the behavior was different from 9.00, and therefore was changed in 10.01 by design.
The reference document can be found here:
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.