CDR Tickets

Issue Number 3599
Summary Modify CreateNewFilter Tool
Created 2013-03-22 17:06:08
Issue Type Improvement
Submitted By Englisch, Volker (NIH/NCI) [C]
Assigned To Englisch, Volker (NIH/NCI) [C]
Status Closed
Resolved 2013-09-20 12:39:04
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.107927
Description

BZISSUE::5298
BZDATETIME::2013-03-22 17:06:08
BZCREATOR::Volker Englisch
BZASSIGNEE::Bob Kline
BZQACONTACT::Volker Englisch

The CreateNewFilter.py tool connects from our development server to the production server in order to get the properly sequenced CDR-ID when creating a brand new filter.
This tool will no longer work once we're using the CBIIT environment and will need to be modified.

Comment entered 2013-04-30 17:28:03 by Kline, Bob (NIH/NCI) [C]

BZDATETIME::2013-04-30 17:28:03
BZCOMMENTOR::Bob Kline
BZCOMMENT::1

I think we should be able to connect to the production CDR server over port 2019 to create a new CDR Filter document. If that turns out not to be true, I guess I can't do anything about it without CBIIT's permission anyway (and if we can't connect to the CDR server over port 2019, the game is up anyway). Right?

Comment entered 2013-09-20 12:39:04 by Kline, Bob (NIH/NCI) [C]

This has been adapted for the CBIIT environment and checked into version control. Please test (you can run this from the PROD bastion host, though you might want to delete the resulting docs, unless you've got a new filter you need to create for real). You might want to create another issue to replace the other filter storing tools with something which works on the CBIIT servers as well.

Comment entered 2013-12-13 08:07:16 by Kline, Bob (NIH/NCI) [C]

Assigned to you for testing, Volker.

Comment entered 2013-12-19 18:07:16 by Englisch, Volker (NIH/NCI) [C]

I tested this on DEV from the CDR server and on STAGE from the bastion host successfully. I didn't want to test this on PROD by creating a bogus filter (we already have enough of those :-) ).

Elapsed: 0:00:00.001727