| Issue Number | 3641 |
|---|---|
| Summary | CdrServer control table management |
| Created | 2013-08-15 10:38:45 |
| Issue Type | Bug |
| Submitted By | alan |
| Assigned To | alan |
| Status | Closed |
| Resolved | 2013-08-27 18:06:15 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.111964 |
In the past, configuration changes used to modify the operation of the CdrServer or our many Python clients were made by modifying data in the database, modifying files, setting environment variables, modifying scripts, or even recompiling the CdrServer. With our new hands-off server operations, none of these methods are possible without putting in formal requests to CBIIT and waiting for the requests to be approved and carried out.
From early on in our CDR design we envisioned a mechanism for managing configuration/control data using a database table created for the purpose. However we never needed it the way we do now and never developed software to use or manage it.
This issue is being created to produce improvements in the CdrServer to support the use of the table.
I have attached a file with high level design concepts for the changes.
I've completed a first draft of the server code and gotten a clean compile. No testing yet.
The first thing I'll do on Thursday is write the database modification script and test it so that we can include it in the patch sent to CBIIT. Then I'll start testing the code. Testing should get easier when the Python client is ready.
The first application I have in mind for this is control the ODBC database connection parameters in order to try out changes, for example in timeout length and connection pool size, and to control the types of logging that we do. My goal is to enable us to tweak the CdrServer <-> SQL Server connection parameters and logging in order to get more information from DEV about the problem and, if necessary, to reduce the severity of the problems on PROD.
This will be included in the patch going out this week.
| File Name | Posted | User |
|---|---|---|
| ControlTable1.txt | 2013-08-15 10:38:45 |
Elapsed: 0:00:00.001591