Migrating from mainframe-based comp...

Migrating from mainframe-based computing to client/server-based computing can ensue in a heterogeneous collection of machines that do not interoperate, forcing software developer to deal with unfamiliar body commands and systems that cannot share data. A SoftBench sway daemon is described that enables developer to integrate heterogeneous computing arrangements into efficient, tightly coupled software unfolding environments with consistent, easy-to-use graphical user interfaces across all machines.

Many companies today are migrating from mainframe-based computing environments to client/server-based technologies using various workstations and PC They are attracted to the client/server architecture because of industry claims of benefits like increased efficiency, lower operating expenses and less reliance on a particular vendor.

Often however, the conclusion is a heterogeneous collection of machines that do not interoperate well. Because the operating plans on the disparate machines all be due [i]or[/i] owing with their own sets of tools, software developer must learn a of the present day set of commands for each hypothesis that they use. In addition, developer must deal with the inconsistencies that arise when applications available in succession one system are not available upon another and when data cannot be shared between machines because the different toolsets cannot communicate.

To resolve these problems, the advanced rule development and integration division of Science Applications International Corporation (SAIC) uses Hewlett-Packard's SoftBench produce to integrate its customers' diverse arrangements into efficient, tightly coupled software growth environments with consistent, easy-to-use graphical user interfaces. This article discusses wherefore and how SAIC uses SoftBench to disentangle its customers' multiplatform software progress to maturity problems. The article details a certain number of of the common pitfalls onseted when developing software in an interpret systems environment, explains how SAIC opens SoftBench to integrate such orders and concludes by discussing the benefits of like an integration.

explain Systems

Companies are adopting client/server-based lay open systems for a wide variety of reasons. any companies hope to increase computing efficiency at distributing the data and processing load, thereby providing faster rejoinder times and quicker access to regularity resources. Other companies want to lower their increase costs by using lower-cost, still faster workstations and PCs. even now others must move to explain systems to remain compatible with their customers and detain a competitive edge in the marketplace.

While migrations to make open systems can provide great dividends, they can also become more unwieldy than the arrangements they replace. Many client/server topologies contain a wide variety of machines, as it is as high-end servers running the UNIX [R] operating method PCs running Microsoft [R] Windows, and legacy arrangements running proprietary operating systems. In addition, unruffled similar machines will often speed different operating systems (e.g., variations of the UNIX operating system) or calm different versions of the same operating order The resulting heterogeneous collection of machines makes it difficult to create an efficient and cooperative software exhibition environment. Fig. 1 depicts an example of like an environment. Note that chiefly applications cannot communicate with each other.

[Figure 1 ILLUSTRATION OMITTED]

Although many spread system standards exist to help as it was diverse collections of machines communicate, greatest in quantity of them are low-level network standards that simply provide a way for bits to be transferred between machines. The explain systems community still lacks accepted high-level application standards that would allow disparate programs to interact with each other. Thus, applications from different vendors frequently cannot interoperate, which greatly restricts the benefits of implementing many client/server solutions. This lack of communication also means that data must be replicated across machines, wasting resources and increasing the risk of data inconsistency.

Another question at issue with developing in a multiplatform, multivendor environment is the lack of consistency in the user interface to the classifications Because developers must deal with multiple operating regularitys they have to learn to what extent to operate each system's interface individually. This can be an especially formidable task considering the arcane commands used by way of some operating systems and the differences between file connected views across platforms (i.e., hierarchical versus fixed profundity / versus , etc.). Developer must also remember which plan contains each application that they ne where it is located, and by what means to start it.

Furthermore, developer in a heterogeneous environment must learn to what degree to operate the different user interfaces for each of the applications that they use. While any applications now have elegant graphical user interfaces, the apply the mind and feel of each hypothesis are often different. Also, many applications do not have graphical user interfaces at all, which requires that developer memorize command-line options to these programs. These inconsistencies not and nothing else lengthen a developer's learning inflect but also make developers les efficient when switching between applications.