Issue Number | 3637 |
---|---|
Summary | Server Name Replacement |
Created | 2013-08-01 18:03:52 |
Issue Type | Task |
Submitted By | Englisch, Volker (NIH/NCI) [C] |
Assigned To | Englisch, Volker (NIH/NCI) [C] |
Status | Closed |
Resolved | 2013-08-27 16:27:10 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/ocecdr/issue.111265 |
There are several reports for which we missed to set the hostname for the production server (NCIWS-p193-v) with the CNAME or a different indicator (CBIIT-PROD) before the migration. I'm collecting these reports in this issue to be fixed.
1) Monthly ICRDB Status Report
This report is ready to go to PROD. It has been fixed and tested on
DEV and could go into our next patch.
ICRDBStatsReport.py - R11919
Here is another link in an email that wasn't correctly adjusted for the CBIIT environment. The link points to the GatekeeperStatus.py report and is submitted as part of
R11953: PublishingService.py
Erika, is it possible to add this issue to the patch? It's addressing minor changes to correct server names or paths in report URLs. Everything listed has already been completed in DEV.
The Env-Tier prefix wasn't displayed for our PubStatus email notifications. This has been fixed in DEV:
R11937: PubStatus.py
Volker, I added this to the CDR Migration Patch 3.0.1. Please add in your story points. Thanks, Erika
The following module will have to be updated on PROD to fix the port
number change on different tiers:
d:\cdr\lib\python\cdrdb.py
More updates for our patch:
The following file needs to be updated on the FTP app server:
~cdroperator/prod/docs/ftp_memo.cdrxml
Here is another file that needs to be updated in PROD in order to prevent error messages when sending emails via the publishing process (eval(DL)) .
R11970: cdrpub.py
Closing out the issue. No more additional quick fixes for this patch.
The last change added for cdrpub.py has been verified.
Elapsed: 0:00:00.001595