Front-end processor

<h2 id="ip-networking">IP networking</h2>
<p>FEPs are responsible for linking client applications and their associated networks to host computer based applications. With the advent of the Internet and of <a href="/facts/Internet_Protocol/Qq6VeEal">IP</a> as a universal protocol, it is often assumed that there is no longer any need for FEPs,<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> which traditionally handled SNA traffic. This may be true where FEPs provide only straight connectivity (and assuming IP address never changes). However, FEPs also perform other vital functions, that are closely linked to transaction applications, including message and transaction switching, <a href="/facts/Multiplexing/YE7hK8cw">multiplexing</a>, transaction security, <a href="/facts/Quality_of_service/joz9VkUm">quality of service</a> guarantors, and end-to-end transaction management and reporting. The need for these functions is especially important in mission-critical transaction environments such as banking, government, point-of-sale, security, and healthcare applications. In these environments, FEP functionality is more necessary than ever before.
</p><p>Although the IBM Corporation withdrew its <a href="/facts/IBM_37xx/1gkAqaBm">3745/3746</a> Communications Front End Processors from marketing in 2003, the company continues to maintain the estimated 20,000 installed front-end processors.  IBM also provides microcode enhancement features.  Smaller companies have filled the void created by IBM's action, providing machines, features, parts and services worldwide.
</p>
<h2 id="see-also">See also</h2>
<ul><li><a href="/facts/Interface_Message_Processor/NNUx01pg">Interface Message Processor</a></li></ul>

<h2 id="external-links">External links</h2>
<ul><li><a href="http://www.subnet.com/products/substation-server.aspx">Front End Processors for Substations</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Telfer, Angus (15 February 2002). "Front-End Communications Processors" (PDF). Inetco. Archived from the original (PDF) on 22 March 2003. <a href="https://web.archive.org/web/20030322140807/http://www.inetco.com/docs/pdfs/fep02.pdf" target="_blank">https://web.archive.org/web/20030322140807/http://www.inetco.com/docs/pdfs/fep02.pdf</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Newport, C.B; Ryzlak, J (1972). "Communication processors". Proceedings of the IEEE. 60 (11): 1321. doi:10.1109/PROC.1972.8900. <a href="/wiki/Doi_(identifier)" target="_blank">/wiki/Doi_(identifier)</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>"IBM FRONT-END PROCESSOR REPLACEMENT SOLUTION". Cisco Systems. Archived from the original on 21 November 2003. <a href="https://web.archive.org/web/20031121214306/http://www.cisco.com/en/US/netsol/ns340/ns394/ns74/ns322/networking_solutions_package.html" target="_blank">https://web.archive.org/web/20031121214306/http://www.cisco.com/en/US/netsol/ns340/ns394/ns74/ns322/networking_solutions_package.html</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
</ol>

Front-end processor open-in-new

Front-end processor