Bug 798842

Summary:	Remove the Content Specification Server
Product:	[Community] PressGang CCMS	Reporter:	Lee Newson <lnewson>
Component:	CSProcessor	Assignee:	Lee Newson <lnewson>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.x	CC:	jwulf, sburgess
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	0.22.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-30 04:53:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	799821

Description Lee Newson 2012-03-01 03:55:23 UTC

Now that the Content Specification Server has no purpose the program can be moved to a client only based application. The reason it has no purpose is that it was originally created as a Web Service because it had to maintain a database and sensitive connection information to Skynet. This however is no longer the case.

The other reason was to help limit data access to the Skynet database when it had direct access. Now it accesses that data via a REST Interface so the controlling should be done within Skynet.

This requires creating builder and processor portable JAR files to include with the client to give it the functionality that the server had. Doing this will also help with Bugs #788328 and #771803.

This change will also affect the users as they will have to change their configuration files, so an automated function with in the client to do this would be best.

Comment 1 Lee Newson 2012-03-05 06:52:26 UTC

Done in 0.22.0.

The Server now has no use and will be closed eventually.

There are now three portable JAR files that contain the functionality that was included in the server. They are csprocessor, csbuilder and cscommons. This has also been incorporated into the new client(0.22.0) see Bug #796009. 

Due to the mass amount of changes to the client, none of the old configuration files are relevant so no script will be used to fix the configuration file. Instead a new configuration file will be included in the release and instructions setup on the docspace page on how to setup and use the new client.