¶ … enterprise wide networking has been the topic of discussion. Advances in technology and networking systems have caused organizations to develop new management techniques for enterprise wide networks. The purpose of this paper is to discuss the Management of enterprise-wide networking. We will focus on four aspects of enterprise wide networking including; legacy systems, Internet Security, offshore development and support and Mobile computing. We will investigate how each of these aspects is handled within an enterprise.
Legacy Systems
Legacy systems were once popular in the business world but have become less popular in recent years. (Sinn 2003) legacy system is loosely defined as "a software platform developed in a procedural language such as Cobol or RPG, hosted on a mainframe or an IBM iSeries. In most cases the maintenance costs of the system tend to increase over time while the available technical expertise around it decreases (Ludin 2004)."
Many enterprises are developing ways to modernize legacy systems while others have decided to abandon them altogether. (Sinn 2003) An article in the Weblogic's development Journal explains that there is emerging a new trend whereby CIO's are recognizing the need to incorporate legacy systems with weblogic to produce an IT system that is unified to meet all the needs of the enterprise (Ludin 2004). In addition, many enterprises realize that streamlining their processes will allow the enterprises to prove their customers with value added services (Ludin 2004). This means that some essential enterprise processes must be re-hosted from the old legacy systems to the newer WebLogic platforms. In doing this, managers are able to modernize their legacy systems (Ludin 2004).
The article goes on to explains that the modernization of a legacy system is absolutely necessar if the enterprise is going to maintain a competitive advantage. The author asserts that the legacy systems are also becoming obsolete because the expertise that it takes to run these system is becoming scarce (Ludin 2004).. In addition, the new processes that are needed to meet business obligations in the 21st century require more than legacy systems can offer. The author asserts that the cost associated with legacy systems are the prime reason why many organizations desire to simply modernize the systems as opposed to getting rid of them all together. The article explains,
In most cases the maintenance costs of the system tend to increase over time while the available technical expertise around it decreases. Another way of defining a legacy system is the moment where the system cannot service new business requirements because of limitations such as technology and would therefore require modifications far beyond maintenance. However, most organizations have invested enormous amounts of intellectual property and money in these systems and expect to capitalize their return on investment, not counting that most of their mission-critical business processes run on them (Ludin 2004).
Ludin (2004) asserts that there are six solid reasons why an enterprise would choose to modernize a legacy system. These six reasons include;
Cobol programming is antiquated and not suitable in current enterprise application developments. So then the maitenance cost of legacy systems exeed the costs associated with modernizing the systems (Ludin 2004).
Modernizing a legacy system is not as expensive as completely replacing the system because the process is less disruptive. In addition, the enterprise can continue to balance the overall infrastructure during the modernization (Ludin 2004).
WebLogic Platform presents the necessary tools for creating component-based and service-oriented architectures, that are needed for e-business (Ludin 2004).
Certain WebLogic tools enhance productivity far beyond the Cobol development environments (Ludin 2004).
The J2EE platform and Java programming language encourage software reuse and facilitate medium to long-term system maintenance (Ludin 2004).
Lastly, a WebLogic Server allows additional services including security, scalability, and availability that would be difficult to implement if it had to be created from scratch (Ludin 2004).
Ludin (2004) explains that there are two approaches that can be utilized to modernize a legacy system. These approaches include a white box approach or a black box approach. The white box approach ensures that "the inner workings of the legacy code are studied. For example, Cobol modules are examined in order to grasp the underlying business processes and rewrite them as EJB components. Often, the white-box approach might be required to provide true added value and move beyond enterprise application integration (Ludin 2004)."
On the other hand, the black box approach does not concern itself with the inners workings of the legacy system. Instead the black box approach utilizes system interfaces and provides...
Our semester plans gives you unlimited, unrestricted access to our entire library of resources —writing tools, guides, example essays, tutorials, class notes, and more.
Get Started Now