RELEASED: Public: May 15, 2024
Resolved issues
- Inbound shared agents aligned with new Remoting CLI options (BEE-44344)
-
Certain options for the inbound agent launcher, particularly the checkbox for WebSocket, were removed from the configuration GUI, in favor of passing the corresponding option such as
-webSocket
on the CLI. In the case of inbound shared agents, this was not sufficient since the operations center was responsible for launching the cloned agent that connects to the controller. Adding-webSocket
to the agent startup options did not work since it conflicts with the deprecated-jnlpUrl
. WebSocket shared agents can be used only by configuring this field via Configuration as Code, REST, or the CLI upload of XML.
Shared agent usage is now aligned with the new agent.jar
CLI recommendations and avoids deprecated options. You can add options, such as -webSocket
, to the command line when connecting the agent to OC, and you should do the same in the agent startup options field. For compatibility, if the deprecated webSocket
field was still defined in the agent configuration, the -webSocket
option will be added to the cloned CLI; -jnlpUrl
can still be used to connect the agent to the operations center even though it is deprecated.