Erica,
I would think that the establishment of any communication from an agency to
the outside would be the resposibility of a network support team, where all of
the engineers can 'touch' everything. They are not developers, but take
requests from development personnel to config new comms. Audit trail, you know.
Bud/Customs
erica_wiley <[EMAIL PROTECTED]> wrote:
I am curious if anyone out there has worked with EDI Communications
within a Federal Government environment? If so, what has been your
experience with the standard governement IT policy that those who work
in development cannot touch the production environment and vice versa?
How did you go about setting up EDI communications, such as AS2, under
this constraint?
---------------------------------
Sponsored Link
Degrees online in as fast as 1 Yr - MBA, Bachelor's, Master's, Associate -
Click now to apply
[Non-text portions of this message have been removed]
...
Please use the following Message Identifiers as your subject prefix: <SALES>,
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>
Job postings are welcome, but for job postings or requests for work: <JOBS> IS
REQUIRED in the subject line as a prefix.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/EDI-L/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/EDI-L/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
