Bug 849786

Summary:	Documentation incorrectly suggests that sslservlet should be used for the agent's communication transport - rhq.communications.connector.transport
Product:	[JBoss] JBoss Operations Network	Reporter:	Larry O'Leary <loleary>
Component:	Documentation	Assignee:	Deon Ballard <dlackey>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Mike Foley <mfoley>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	JON 3.1.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-01 00:33:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Larry O'Leary 2012-08-20 21:08:58 UTC

Description of problem:
Agent configuration described in https://access.redhat.com/knowledge/docs/en-US/JBoss_Operations_Network/3.1/html/Admin_Configuring_JON_Servers_and_Agents/configuring-ssl.html#JBoss_ON_and_SSL-Encryption suggests using `sslservlet` as the transport however this transport is invalid. On the JON/RHQ agent, the only supported transports are `socket` and `sslsocket`. In the case of enabling SSL/TLS on the agent, sslsocket should be used. The only place `sslservlet` can be used is for the `rhq.agent.server.transport` property.

Version-Release number of selected component (if applicable):
JON 3.1.0

Additional info:
By using `sslservlet` for `rhq.communications.connector.transport` as indicated in step 2.c. the result is the agent will fail to start due to the invalid transport being used.

Comment 1 Deon Ballard 2013-03-01 00:33:19 UTC

Mass closure.