Think of it this way, most translators have some sort of integrated communications package that can be customized to meet the connection needs of the organization. In my experience, it is the EDI folks that are responsible for this package, not the network people. In the case I am thinking of, the communications package is separate from the translator and installed on separate servers. The software and servers are already integrated with internal/external firewalls and proxies and EDI only contacts network for firewall rule changes. EDI also provides all internal automation of data decryption (in the case of encrypted ftp), routing and monitoring. They are considered part of the EDI group, mainly because of providing all of the behind the scenes data movement of EDI documents, but this team is not involved in EDI translation. I know am using "EDI" very loosely here but that is how it is viewed. The majority of data movement involves 75% pass-thru and the rest is EDI translated data. In this case, the requirement is that connections be setup in a test/development environment and in a production environment. This is the first time I have run across this scenario, mainly because it requires the double setup and testing of connections with the external trading partners with no real value. Has anyone else run into this scenario and can you give me an idea of how how duties were distributed and connections were maintained given the rule that those who work on the development servers cannot touch the production servers? ----- Original Message ---- From: Bud Blankenship <[EMAIL PROTECTED]> To: erica_wiley <[EMAIL PROTECTED]>; [email protected] Sent: Saturday, November 18, 2006 8:24:13 AM Subject: Re: [EDI-L] EDI in a Gov Agency
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 ____________________________________________________________________________________ Sponsored Link Degrees online in as fast as 1 Yr MBA, Bachelor's, Master's, Assoc http://yahoo.degrees.info [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/
