![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: E-Mail Submissions - howto required Topic Summary: Created On: 3-Nov-2003 21:04 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Not sure how much use this will be but I copy below an extract from some notes taken when I recently enabled email submission on one of our ChangeSynergy 4.2 servers (running Windows NT but the change in principle would probably apply to other platforms as well). **** ChangeSynergy: cs_app\webapps\synergy\WEB-INF\wsconfig\pt.cfg [CCM_SYSTEM]…[MAIL_FILE]: mail_file_path_and_name must be replaced by one of the mail files on the NT server (doesn’t matter which), e.g. e:\data\admin\mail\inbox\<database>\probtrac cs_app\webapps\synergy\WEB-INF\wsconfig\<lifecycle>.cfg Any problem attributes included in external CRs but not currently defined to the ChangeSynergy lifecycle must be added here (via the Lifecycle editor). Database: pt\mailpath.dft Contents must change from /usr/mail/probtrac to the mail file for that database, e.g. e:\data\admin\mail\inbox\<database>\probtrac. This constitutes the list of CRs that will be submitted. pt\dbmap.dft Without modification, this will cause each external CR submission to trigger ccm_mail into attempting to send an email to probtrac@continuus.com. This can be prevented by prefacing each line (particularly the one starting with “ChangeSynergy:”) with, e.g., x. pt\ptenvstr The value assigned to variable PT_MAIL_BACKUP_DIR must be changed from /tmp to, e.g., e:\data\admin\mail\inbox\<database>\backup. This is where the current mail file is backed up when CR submission is run. pt\mailatts New problem attributes must be added here to avoid an “Invalid attribute detected” error message during CR submission. **** The way this worked was that the incoming CRs arrived in the e:\data\admin\mail\inbox\<database>\probtrac file & then every so often a ccm pt_process_submissions command was run to process the CRs. I could also add that to make life more complicated the email inbox was actually hosted on a different Unix server & the mailfiles were then ftp-d onto the NT server. This is unnecessary if you have a half-decent mail server installed on the ChangeSynergy server (highly unlikely on NT but a given on, e.g., Solaris). | |
![]() |
|
I am looking into setting up the electronic e-mail submission feature in CS4.2
Besides 5 lines in the online documentation and one small paragraph in the readme file I can't fine any information on what I need to exactly do. I know i need to change pt.cfg and mailpath.dft - but it is not described anywhere what needs to go in there - what is considered a mailfile, how the mail can arrive on the server etc... Is someone out there that has this process setup (at least for test purposes) and can share a bit on what needs to be done? Thanks Bernd |
|
![]() |
|
![]() |
|
Not sure how much use this will be but I copy below an extract from some notes taken when I recently enabled email submission on one of our ChangeSynergy 4.2 servers (running Windows NT but the change in principle would probably apply to other platforms as well).
**** ChangeSynergy: cs_app\webapps\synergy\WEB-INF\wsconfig\pt.cfg [CCM_SYSTEM]…[MAIL_FILE]: mail_file_path_and_name must be replaced by one of the mail files on the NT server (doesn’t matter which), e.g. e:\data\admin\mail\inbox\<database>\probtrac cs_app\webapps\synergy\WEB-INF\wsconfig\<lifecycle>.cfg Any problem attributes included in external CRs but not currently defined to the ChangeSynergy lifecycle must be added here (via the Lifecycle editor). Database: pt\mailpath.dft Contents must change from /usr/mail/probtrac to the mail file for that database, e.g. e:\data\admin\mail\inbox\<database>\probtrac. This constitutes the list of CRs that will be submitted. pt\dbmap.dft Without modification, this will cause each external CR submission to trigger ccm_mail into attempting to send an email to probtrac@continuus.com. This can be prevented by prefacing each line (particularly the one starting with “ChangeSynergy:”) with, e.g., x. pt\ptenvstr The value assigned to variable PT_MAIL_BACKUP_DIR must be changed from /tmp to, e.g., e:\data\admin\mail\inbox\<database>\backup. This is where the current mail file is backed up when CR submission is run. pt\mailatts New problem attributes must be added here to avoid an “Invalid attribute detected” error message during CR submission. **** The way this worked was that the incoming CRs arrived in the e:\data\admin\mail\inbox\<database>\probtrac file & then every so often a ccm pt_process_submissions command was run to process the CRs. I could also add that to make life more complicated the email inbox was actually hosted on a different Unix server & the mailfiles were then ftp-d onto the NT server. This is unnecessary if you have a half-decent mail server installed on the ChangeSynergy server (highly unlikely on NT but a given on, e.g., Solaris). ------------------------- Russ Braithwaite Software Configuration Management Friends Provident |
|
![]() |
|
![]() |
|
Thank you so much - that does everything I need - also working fine on AIX - including the ccm pt_process_transmissions command...
|
|
![]() |
|
![]() |
|
Here I am again with an add on question:
Thank you for your help. I got it working now... almost flawless... Here is my latest challenge: I have two submit dialogs in the Lifecycle. Similar to the default lifecycle one of them bypasses the initial validation steps and is only to be used by technical staff - the other one is for user entries.... For entering in CS that is not a problem - each user only sees one of them depending on their role. For web entry I get the select a form dialog first - I don't want that. I want one of the two submit dialogs (and not the other one) to be presented for web entry and the other one to not be accesible.... |
|
![]() |
Telelogic SYNERGY
» SYNERGY/Change
»
E-Mail Submissions - howto required
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.