Hi,
Has anyone experienced upgrading an MF agent to use SSL along with TCP? We have a client that has a Microfocus job that works fine on their on-prem server using the following connection string:
tcp:
servername:30162
When they run the same job on their new cloud server, due to tighter protocols, they use the following string:
tcpssl:
servername:30162
The on-prem agent is R11.3.4, build 45 and the cloud agent is R11.4.01, build 56.
The job runs fine under the older version but is not successful on the newer agent. The job gets submitted and the user can tell the job completes on the agent/server side, but the status of the job never changes from "READY". We can't see any difference on the receiver/transmitter between the two, other than the COMPLETE communication never gets sent back to the Master.
Just wondering if it could be the difference in the builds.