02 - Characteristics of Microsoft BackOffice
by Greg Sullivan
- Microsoft BackOffice design goals - Explore the technical underpinnings of Microsoft BackOffice and learn the foundation of its existence.
- How Microsoft BackOffice serves as a network operating system - Learn the important characteristics of a network operating system and how Microsoft BackOffice fulfills this need.
- What Microsoft BackOffice services are and how they work - Become acquainted with the most important and basic concept in Microsoft BackOffice - services.
- Why Microsoft BackOffice is a solid platform for the future - Understand why Microsoft BackOffice is a safe bet for your organization.
- What Microsoft BackOffice is from your perspective - Learn why Microsoft BackOffice is important to you as an information systems manager, administrator, developer, or user.
This chapter presents a brief overview of Microsoft BackOffice's characteristics. By the end of this chapter, you will have a fundamental knowledge of the architecture of Microsoft BackOffice and how its design fulfills a variety of needs in modern computing.
Understanding the architecture of Microsoft BackOffice and the design principles upon which it is built puts you in the best position to take full advantage of its capabilities. As you learn more about the various roles of Microsoft BackOffice, keep in mind its place in the evolution of computing as you learned in Chapter 1.
The characteristics of Microsoft BackOffice apply to enterprise computing environments of today, as well as the future.
Microsoft BackOffice is based on current technologies with an eye toward the future. Microsoft continues to invest heavily in BackOffice as they move toward an object-based, distributed enterprise computing platform. In fact, the Business Systems Division (BSD) of Microsoft (the group responsible for Microsoft BackOffice) is their largest division with well over 1,000 people and accounts for a large percentage of Microsoft's research and development investment. This parallels their continued investment in desktop computing tools and platforms.
Interestingly, even though Microsoft BackOffice is based on current and leading edge concepts such as object-oriented technology and distributed computing, you will rarely find such a reference in Microsoft marketing materials. Their marketing approach tends to focus on the benefits and value of Microsoft BackOffice as opposed to its technical underpinnings.
Microsoft prefers to avoid technical terms such as object-oriented technology and distributed computing when describing BackOffice even though these concepts form a basis for their product strategy.
Design Goals of Microsoft BackOffice
Many design goals of Microsoft BackOffice are based on the need to create value for the product. The Microsoft BackOffice design goals are shown together in figure 2.1.
Fig. 2.1 - The design goals of Microsoft BackOffice are important to understand.
It is important to understand the technical aspects underlying each of these design goals. The following sections describe the important design goals of Microsoft BackOffice and the technical significance of each.
Portable
The Windows NT operating system is designed to be portable, which implies Windows NT will operate on a variety of hardware platforms. The operating system itself is written primarily in C and C++ to ensure portability of the base source code. The small amount of the operating system written in Assembler also is designed to be portable to other platforms.
This approach makes it possible to port Windows NT to a number of processors relatively easily; consequently, users of Windows NT have choices when acquiring hardware. Windows NT is available for computer systems using the following processors:
- Intel x86, Pentium, and compatibles
- MIPS
- Digital Alpha AXP
- PowerPC
MIPS, Digital Alpha AXP, and PowerPC are examples of reduced instruction set computing (RISC) processors, which Windows NT supports.
As shown in figure 2.2, Windows NT is written without exploiting any features specific to a particular processor family. It uses only characteristics available on any processor, such as support for virtual memory and 32-bit memory addressing.
Fig. 2.2 - One of the design goals of Microsoft BackOffice is to support portable applications across multiple processor platforms.
The design of Windows NT and the development tools provided by Microsoft, make it possible to write a 32-bit Windows application with source code that is largely the same for all the different processor platforms supported by Windows NT. The application source modules need to be recompiled for the different target platforms, but significant customization for each platform is not required.
In spite of this fact, Microsoft does not offer every BackOffice server application for each processor platform supported by Windows NT. Table 2.1 summarizes the availability of various Microsoft BackOffice components on each of the supported processors.
| Intel | MIPS | Digital Alpha AXP | PowerPC | |
|---|---|---|---|---|
| Windows NT | x | x | x | x |
| Internet Information Server | x | |||
| Exchange Server | x | |||
| SQL Server | x | x | x | |
| SNA Server | x | |||
| SMS | x |
Microsoft claims Microsoft BackOffice products will be supported on additional platforms as market demand dictates.
Scalable
Scalable operating systems and applications are essential in today's computing world. It is not unusual for application scope to increase suddenly and significantly in a short period of time. Applications must be designed and created such that these spikes can be addressed by straightforward adjustments to the computing hardware. This is more desirable, and typically more affordable, than re-creating an entire business application to accommodate more data.
An operating system is said to be scalable if it automatically takes advantage of additional processors. In other words, an application designed to take advantage of the operating system should receive performance gains, or be able to process additional data without performance degradation, with only a change to the number of processors, and no change to its source code or configuration. Windows NT is a scalable operating system on computers with multiple, identical processors.
There are two ways to "add processors" in the world of Microsoft BackOffice and Windows NT. Processors can be added in either of the following ways:
- To the local computer provided it accommodates additional processors
- By allowing a local process to utilize processors of other computers on the network
One common way to increase computing power is to purchase hardware that supports additional processors. Depending on the version of Windows NT you have purchased and installed, and the computer upon which you are running Windows NT, improving performance may be as simple as installing more processors. Before exploring the alternative to plugging in more processors, it is useful to understand exactly how, when, and where Windows NT supports multiple processors (see fig. 2.3).
Fig. 2.3 - With Windows NT Server automatic support for multiple processors, it is possible for the same application to access a much larger database, experiencing little or no performance degradation, simply by adding more processors.
Windows NT will run on computers that have more than one processor. The retail version of Windows NT Workstation uses up to two processors, and Windows NT Server uses up to four. These are the retail versions you will receive if you purchase either product off the shelf.
Some original equipment manufacturers (OEMs) offer versions of Windows NT that support as many as 32 processors.
The capability to execute the operating system and applications on multiple processors at the same time is known as symmetric multiprocessing (SMP). The SMP capability of Windows NT is designed into its foundation; it is built directly into the operating system kernel in ensure optimal SMP is achieved on each platform Windows NT supports.
In a computer with multiple processors, Windows NT is responsible for distributing processes to be executed on all the available processors (see fig. 2.4). This includes operating system processes such as service request managers and memory management functions. Microsoft has constructed the operating system such that process overhead is held to the bare minimum to reserve as much processor time as possible for applications.
Fig. 2.4 - Windows NT operates under a symmetric multiprocessing scheme on multiprocessor computers.
Applications designed to operate on Windows NT or in a Microsoft BackOffice environment should follow the design recommendations of Microsoft closely. Well-designed applications enjoy the benefits of SMP without undergoing significant overhauls each time processing loads increase.
All Microsoft BackOffice products are designed and developed as 32-bit Windows applications that automatically take advantage of the SMP capability of Windows NT.
Among the most important of these recommendations is designing applications into separate executable components, known as threads. Applications written for 32-bit versions of Windows and Windows NT can break down processes into threads and, therefore, become known as multithreaded applications. When Windows NT detects a multithreaded application is executing and detects the presence of multiple processors, it distributes the application threads across all available processors. Again, operating system threads are also distributed because Windows NT is SMP-based.
The products included in Microsoft BackOffice are implemented as multithreaded services that exploit additional processors on a server for performance gains.
Currently, Windows NT scales well in the neighborhood of four to eight processors. It has been tested successfully on multiprocessor computers with up to 16 processors. The theoretical limit is 32 processors. Said another way, Windows NT has the capability to work on 32 processors, has been tested on 16 processors, but retains a practical limitation somewhere in the neighborhood of six processors. Figure 2.5 depicts Windows NT processor effectiveness.
Fig. 2.5 - One way to characterize Windows NT multiprocessor capabilities is by describing its behavior at various numbers of processors.
To say an operating system or application "scales up to" n processors, implies that after the nth processor is added, the operating system or application receives no additional performance improvements.
When additional processors are added to a computer system, there will not necessarily be a proportionate gain in performance. In fact, at some point you will experience no additional performance improvements. This is due to factors other than processor utilization. For example, on Intel-based personal computers (PCs), the speed with which data is transferred from the processor to memory is fully tapped at four processors. This is why the retail versions of Windows NT only support up to four processors. OEMs design special computers to overcome this problem and offer OEM-specific versions of Windows NT as the base platform.
To enable Windows NT to take advantage of additional processors, you need to set it up to use its multiprocessor kernel.
Performance results are not necessarily proportionate to the number of processors.
The other way additional processors allow Windows NT to realize performance gains is by providing a means for process execution to be distributed across the network. In other words, processors throughout the network, not just on the local computer, are utilized for process execution (see fig 2.6). Windows NT and Microsoft BackOffice rely heavily on a concept known as remote procedure calls (RPC) to make this possible.
Not surprisingly, each Microsoft BackOffice product uses RPC to interact with client workstations on the network.
Fig. 2.6 - Windows NT uses remote procedure calls to distribute process execution to other computers on the network as another means for achieving multiprocessing capabilities.
RPC supports the message-based aspect of the client-server process model. By allowing processes to be executed anywhere on the network, you can optimize overall processor utilization. Consequently, you can take advantage of every available processor on the network. This can be achieved without sacrificing the advantage of multiple processors in any single computer on the network. Moreover, the advantage of RPC does not diminish in a well-designed application as more processors are added to the network.
Applications must be designed specifically to utilize RPC to gain any advantage from the distribution of process execution across the network. Distributed process execution is another way in which Windows NT is scalable.
Open
There is an ongoing, and healthy, debate about what constitutes an open operating system. Microsoft and Windows NT enthusiasts claim Windows NT is an open operating system. Proponents of rival operating systems frequently disagree. It is accurate to say, however, Microsoft has supported industry standards. Admittedly, some of these standards were defined by Microsoft. They also offer developer tools, documentation, publications, and conferences aimed at helping information systems professionals develop applications for the Microsoft BackOffice environment. Whether this constitutes being open is perhaps moot.
Microsoft BackOffice integrates with other server applications that may run on the network, including applications competitive with Microsoft BackOffice products.
Microsoft claims each BackOffice product complies with every major open computing standard. Again, some of these standards are established by Microsoft, whereas others are influenced by Microsoft's involvement in the standard-setting organizations. Table 2.2 describes the most significant interfaces supported by Microsoft BackOffice.
| ODBC | Open Database Connectivity (ODBC) from Microsoft is an industry standard application programming interface (API) that provides access for client applications to databases. Nearly every leading database vendor supports ODBC interfaces. |
| OLE | Object Linking and Embedding (OLE) from Microsoft describes how software components work together using object technology. OLE forms the basis for the concept of document-centric computing. It is based on Microsoft's open Common Object Model (COM). |
| SNA | System Network Architecture (SNA) from IBM is an open standard that describes how PCs, IBM minicomputers, and IBM mainframes communicate with one another. SNA includes an API that allows developers to access data on each type of computer. |
| MAPI | Messaging API (MAPI) from Microsoft is an open API that provides messaging services for building client-server applications. |
| TAPI | Telephony API (TAPI) from Microsoft supports the integration of electronic data with voice communications, known as computer-telephone integration (CTI). |
| ISAPI | Internet Services API (ISAPI) from Microsoft and Process Software exposes the Microsoft Internet Information Server (IIS) to software developers. This API allows developers to integrate Internet services into their applications. |
In addition to supporting these open interfaces, Windows NT Server supports many of the most popular network protocols, including:
- Transmission Control Protocol/Internet Protocol (TCP/IP)
- NetBIOS Extended User Interface (NetBEUI)
- File Transfer Protocol (FTP)
- Apple File Protocol (AFP)
- Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX)
- Open Data Services (ODS)
- Simple Network Management Protocol (SNMP)
- Simple Mail Transfer Protocol (SMTP)
UNIX interoperability is available through support of the open interfaces and protocols mentioned earlier. X-Window System products can execute on Windows NT. Additionally, numerous third-party vendors offer products that bring Microsoft BackOffice and UNIX closer together. Some of these products are based on the open interfaces, whereas others are based on licensing agreements between Microsoft and the third-party companies. One such example is Microsoft's Windows Interface Source Environment (WISE), which is licensed to a few third parties in the UNIX market. WISE permits Windows-based applications to be supported in UNIX environments while preserving interoperability with Microsoft BackOffice.
Secure
In this brave, new world of computing in which data, processes, and information objects are distributed across local area networks (LANs) and wide area networks (WANs), security concerns abound. This is especially true considering the connection many organizations now, or soon will, have to the outside world via the Internet. These physical connections increase the opportunity for security violations.
As an information systems professional, you must be serious about securing the information processed by your systems. Secure transmission, controlled access, and assigned authorizations are important aspects of a secure computing environment (see fig. 2.7). Organizations should also construct well-conceived security models and measure their effectiveness through frequent auditing.
Fig. 2.7 - Microsoft BackOffice provides support for addressing the three major aspects of security: access, transmission, and authorization.
Microsoft BackOffice facilitates the implementation of a comprehensive security plan. It addresses the need to control access and usage of services, as well as resources. Securing services and resources protects your processes, computers, peripheral devices, software, and information. Although Microsoft BackOffice provides the tools for an effective security plan, full security cannot be achieved without the intelligent application of these tools, disciplined management, and the appropriate controls.
The Microsoft BackOffice security model is fully integrated. This implies users have a single security entry point into the Information Network with only one user name and password to remember. Service and resource access and authorizations are assigned by administrators to each user. Users have the convenience of easy entry with the comfort of knowing their information is safe.
Robust
Is Microsoft BackOffice suitable for mission-critical application deployment? The answer to this question lies in its robustness. Software is said to be robust if it does the following:
- Traps software and hardware exceptions
- Does not harm another application in the event of a failure
- Recovers from errors gracefully
- Provides an overall level of stability
Most software products have difficulty laying claim to robustness in their first release. Stability remains elusive regardless of the volume of testing prior to release. However, over a period of time the software developer improves the product based on how it behaves for customers.
Microsoft is no exception to this principle. Many information systems managers await the second release of a software product prior to implementing it in their organization. They receive some additional comfort from the fact that the initial problems with the software have been repaired.
As each new version of the software is released it gets closer to the goal of true robustness. Microsoft BackOffice is now in its third release. As such, it possesses a level of robustness suitable for mission-critical applications with few exceptions.
Consistent
An obvious design goal of Microsoft BackOffice is the desire for consistency. On the surface, this design goal is observed first as you view the user interfaces for each product and the associated services and administrative tools. A consistent, graphical user interface has been achieved across all Microsoft BackOffice products. This "look and feel" is also consistent with other Microsoft operating systems and the Microsoft Office family of desktop products.
As important, Microsoft BackOffice appears consistent to administrators and developers. Administrators are presented with a consistent set of administration tools. Some tools deal with the administration of multiple services at the same time. Ease of administration is a key advantage given the diversity and flexibility of Microsoft BackOffice services.
Over the next year or two Microsoft plans to further integrate BackOffice administration tools. Gradually all administration tools will migrate to the new, Windows 95 user interface and will become easier to use due to the inclusion of more administrative aids.
The programming interface available to developers is also constructed in a consistent manner. The Windows NT application programming interface (API) is known as Win32. Win32 is the basis upon which all Microsoft BackOffice products are developed. Moreover, it is available to you for development of applications or services. Because Win32 is a part of Windows NT, it is available to developers of client applications and server processes. This provides all Microsoft BackOffice developers the advantage of a consistent programming interface.
Another important way in which Microsoft has achieved consistency is the manner in which Windows NT ports to various processors. They have taken care to use only processor features available on all the processors supported by Windows NT. It is conceivable that Microsoft will never exploit processor-specific features. In this manner, Microsoft will avoid the version fragmentation that has plagued UNIX over the years.
Integrated
You have already seen how the Microsoft BackOffice security model delivers, in part, the design goal of integration. This is but one of the many ways in which integration is accomplished.
Microsoft BackOffice products are designed also to integrate well with:
- Windows NT
- Other networks
- The Internet
- Desktop computers
Windows NT serves as the basis for a complete network operating system. You learn more about Microsoft BackOffice as a network operating system later in this chapter. With Windows NT as a foundation, Microsoft BackOffice provides a full set of integrated network services.
Microsoft BackOffice products also tend to integrate well with each other. An example of this is the dependency Microsoft SMS has on Microsoft SQL Server. Microsoft SQL Server also has built-in integration with Microsoft Internet Information Server. Curiously though, Microsoft Exchange Server does not use Microsoft SQL Server as its database. Instead, it uses an internal Microsoft database engine.
Integration with Other Networks
In addition to the network services provided, Microsoft BackOffice integrates well with many other popular networks. Connectivity is provided from your computing desktop to Novell NetWare, UNIX, LAN Manager, AppleTalk, DEC PATHWORKS, IBM LAN Server, Network File System (NFS), and Banyan VINES. This level of support for other network operating systems ensures that Microsoft BackOffice integrates into heterogeneous computing environments. For more information on how Microsoft BackOffice acts as a network operating system, see "A Network Operating System" later in this chapter.
Perhaps the hottest topic in technology circles today is the Internet. Microsoft BackOffice comes complete with an Internet Server component. This service allows your network and organization to integrate with the world via the Internet. Microsoft BackOffice also facilitates the delivery of Internet connectivity to the desktops on your network.
Finally, Microsoft BackOffice is designed to tightly couple with desktop computers. This, after all, is the sole reason for the existence of Microsoft BackOffice. Its primary job is to deliver data to the computing desktops in the form of meaningful information. Microsoft has designed BackOffice consistent with desktop design goals to ensure seamless integration of all computers on the network and the Internet, as shown in figure 2.8.
Fig. 2.8 - Microsoft BackOffice products integrate well with each other, and together they integrate well with other networks, such as Novell and the Internet.
Extensible
The basic architecture of Microsoft BackOffice ensures that new services can be added and existing services can be enhanced. The capability to add new services and enhance existing services is known as extensibility.
Microsoft continues to invest in the development of new products and services in the BackOffice family. Their Internet Server is a good example of a recent addition to the product suite. Additionally, Microsoft continues to provide enhanced versions of the core BackOffice products. Exchange Server is a good example of a recent product upgrade.
Building your own services is a convenient way to customize Microsoft BackOffice for your organization.
In addition to the products and services available from Microsoft, a market exists for third-party BackOffice products. Microsoft has released a sufficient amount of technical information about the way in which BackOffice services are built and executed to enable developers to create their own services. Consequently, companies have entered into the business of developing and selling BackOffice add-on services. These services can be managed by the same administrative tools used to manage services from Microsoft.
Microsoft and third parties will continue to build new, and enhance existing, services.
You may also build your own services or modify existing services. This is the essence of client-server computing. A combination of purchased services and "home-grown" services is typical in today's computing environments. Armed with a consistent set of APIs and an appropriate set of development tools, developers can influence the behavior of existing services. Administrators also possess flexibility in setting the behavioral characteristics of services.
A Network Operating System
Microsoft BackOffice is used in a networked computing environment. This typically includes desktop PCs, or clients, and larger computers, called servers. The servers are shared resources in a network just as other peripheral devices and mainframe computers.
The servers must run a network-capable operating system. Popular network operating systems include UNIX, Novell NetWare, and Windows NT. Client PCs can run a wider variety of operating system software including DOS, Windows, Windows for Workgroups, Windows NT Workstation, Windows 95, UNIX, OS/2, and Macintosh.
The various network operating systems offer different sets of network services. Some services are available on all network operating systems; others are not. Network services built in to Microsoft BackOffice include:
- File access
- Print management
- Resource sharing
- Remote administration
- Security
- Dial-up access
- Internet access
- Server-based applications
Some common services are described in the following sections.
The Basics - File and Printer Sharing
In a networked environment, it is possible to share resources (such as printers and files) containing important information. This has been the main reason for installing traditional LANs in corporate environments.
Resource Sharing
In addition to file and printer sharing, it is possible to share other resources on a network. It is common, for example, to share a "pool" of modems so that a group of people can take turns using them to establish a phone link to remote locations. Sharing peripheral devices such as modems and printers results in more efficient utilization of hardware. Consequently, computer equipment investments can be leveraged across multiple users.
Server-Based Applications
In addition to sharing information and peripheral devices such as printers, a logical next step in the evolution of LAN-based computing is to share processing power. This has been previously described as client-server computing. Network operating systems such as Windows NT provide the basis for the client-server process model. RPC is one of the many capabilities of Windows NT that allows client processes to communicate with server processes. These underpinnings permit the creation of server-based applications that are sharable simultaneously among many clients.
A Flexible Set of Services
A key design element of Windows NT is the concept of a service. A service, in a Windows NT networking environment, is a special type of server-based application. Service is an appropriate name for this type of application because its typical role is to offer services (the traditional meaning of the word) to users on the network.
Microsoft BackOffice can be viewed as a set of services made available to computers attached to a network. Typically the consumers, or clients, of these services are desktop computers in an office environment. The following are some of the services provided by Microsoft BackOffice:
- Database management
- Inventory of computers connected to the network
- Software installation
- Mainframe and minicomputer connectivity
- Electronic messaging
- Workgroup application support
This represents only a partial list of the available services, but it should give you a flavor of the capabilities of Microsoft BackOffice. Each component of Microsoft BackOffice is explored in detail in the chapters to follow.
Services have the following characteristics:
- They execute in the background. In other words, they do not generally open a window or update the display in any way while they are running.
- They can be automatically started when the computer is turned on.
- They keep running even as users log on and log off the computer.
- They can be started, stopped, or paused by using standard Windows NT tools. You can control services on the computer using the Services applet in the Control Panel. With one of Windows NT Server's administration tools, called Server Manager, you can control services on any Windows NT computer for which you are an administrator. See the next section, "Starting, Stopping, and Pausing Services," for more information.
Pausing a service allows users actively using the service to continue, but no new users can connect to the service. For example, pausing the Server service on a Windows NT server prevents any new users from connecting to shared resources. - Many services have full-featured administrative programs that allow you to perform advanced configuration and management in addition to the simple start, stop, and pause described earlier. All of Microsoft BackOffice's components (SQL Server, SNA Server, SMS, and Exchange Server) have powerful administrative programs.
- It is possible to create an account specifically for use by a service and give it appropriate security permissions for its work.
The service architecture supported by Windows NT is a powerful, extensible way to develop the server component of client-server applications. Windows NT services are somewhat similar to daemons in UNIX environments or NetWare Loadable Modules (NLMs) in a Novell NetWare environment. You learn the basics of controlling services in the next two sections.
Starting, Stopping, and Pausing Services
In later chapters, you learn how to use the various administrative applications that allow you to configure and control Windows NT Server and Microsoft BackOffice. For now, it is useful to understand that some standard administrative utilities come with Windows NT Server that allow you to control Windows NT itself. These utilities also allow you to control applications and services operating on a Windows NT server.
Shown in figure 2.9 is the Windows NT Server Manager, one of these administrative utilities. The Server Manager can be used to control services on computers anywhere on the network as long as you have the necessary administrative rights. Server Manager was designed as a tool to let you manage remote servers without having to physically visit a computer and log on.
Fig. 2.9 - Use the Windows NT Server Manager to select any computer on the network you would like to administer.
Changing Startup Options for Services
You can also use Server Manager to change the startup options for a service. Most often, services are set to automatically start when the computer is turned on and Windows NT is loaded. Alternatively, you can set the service startup option to Manual. To start the service, an administrator must follow the procedure for starting services (or an equivalent procedure). You can also completely disable a service if you do not want any of its components to be active, or allow it to be started accidentally.
Use Windows NT Server Manager to stop, start, and configure Microsoft BackOffice services.
Exploring Further Development
Windows NT and the Microsoft BackOffice suite of server-based applications create a powerful platform upon which additional product development can take place. It is safe to assume that Microsoft will continue to develop and deliver BackOffice service-based applications. See Chapter 31, "Building Applications with Microsoft BackOffice,". for more information.
Many software products have been created to run in a Microsoft BackOffice environment, and more are being created every day. These products may be shrink-wrapped applications that appeal to a wide audience, or they may be highly customized applications designed to meet specific requirements at a single organization.
Additional techniques must be learned to create a service, register it with Windows NT security, and execute it in a network environment. It is beyond the scope of this book to discuss development of Microsoft BackOffice services. However, it is important to know how the acquisition, development, and administration of these services affect you.
Microsoft BackOffice from Your Perspective
Now that you are familiar with the design goals of Microsoft BackOffice, its role as a network operating system, its flexible set of services, and its basis as a platform for future information processing, what does it all mean to you? This, of course, depends on your role in information systems. If you are an information systems manager, administrator, or developer, you will find that Microsoft BackOffice offers you many benefits.
As a Manager
Information systems managers, as well as business executives, can realize many benefits from Microsoft BackOffice. Clearly, the most advantage is gained when the entire Microsoft BackOffice product suite is implemented. This is true in small, medium, and large organizations due to the economies of scale and product synergy realized as a result of the consistent and integrated foundation Microsoft BackOffice provides. Some benefits Microsoft BackOffice provides to managers include the following:
- Competitive Pricing. By bundling several integrated products into a single package, Microsoft BackOffice offers a new level of affordability to the marketplace for these types of products.
- Operational Savings. Consistency and integration yield time and money savings to the organization. This is a result of the reduced cost-of-learning curves associated with implementing more than one Microsoft BackOffice product.
- Security. Security is built into the foundation of Microsoft BackOffice. Coupled with a secure physical environment and secure business processes, Microsoft BackOffice gives you the comfort of knowing your information, and the information of your users, is protected.
- Current Technologies. Microsoft BackOffice is based on the sound and popular computing trend toward object technology. As more software developers accept this approach to software development, it is possible for an organization to realize significant savings in software development costs. It is also reasonable to expect the quality of software to be higher. Although some of these savings remain several months, or even years away, it is important to know Microsoft BackOffice fully supports object technology now and will continue to support it in the future.
- Network Management. The cost of administering large networks of PCs and servers is rarely understood in detail. This job has been plagued with hidden costs and missed user expectations. Microsoft BackOffice gives you an excellent means to control the hidden costs associated with large network management through SMS. SMS also addresses the needs of those responsible for asset management by automatically tracking software and hardware inventories.
- Standards. Organizations that set standards for software and hardware usage realize savings in time and money. In large networks, it has been difficult to impose standards due to the complexities associated with tracking user configurations and massive deployment of new versions of software when an upgrade becomes available. SMS now provides a convenient facility for establishing software and hardware standards and monitoring their effectiveness.
- User Support. Many organizations offer internal technical support to their users. SMS provides a convenient facility that allows a help desk person to assist a user on the network by directly manipulating the user's PC. This includes direct control of the keyboard and mouse. A help desk person can observe a user as the problem is experienced and, by taking control of the input devices, demonstrate correct operation while the user watches. This same capability allows hardware problems to be diagnosed remotely. All this leads to reduced costs for supporting the PC network and its users.
- Future. Industry experts and research organizations frequently discover new ways in which technology can be applied to solve business problems. It is important that your organization is in the best possible position to apply these ideas as the need arises. Microsoft BackOffice is designed to accommodate deployment of new ideas in information systems. As a manager, it is comforting to know a Microsoft BackOffice Information Network is built to support the next wave of new ideas. Examples of current concepts enabled by Microsoft BackOffice include:
- Data warehousing
- Systems and network management
- Consistently distributed objects
- Decision support systems (DSS)
- Executive information systems (EIS)
Overall, you can expect to have a more satisfied user community as a result of a successful Microsoft BackOffice implementation. Information Network users have better information and higher levels of integration. This permits them to make better decisions and be more responsive to the pressures arising from increasingly shorter business cycles.
As an Administrator
Information systems administration teams require tools to facilitate the delivery of information to the enterprise computing desktops. Microsoft BackOffice, along with its add-ons and desktop solutions, represent a comprehensive set of tools that facilitate administration. The types of administrators needed and how the team works together are covered in Chapter 3, "Preparing to Implement Microsoft BackOffice." The following list explains how system, network, database, and other administrators benefit from Microsoft BackOffice:
- Consistency. Each Microsoft BackOffice product comes with its own administrative tool set. Administrators faced with the task of managing more than one product are presented with a consistent user interface across all the tools. This results in reduced learning curves as additional products are implemented.
- Integration. All Microsoft BackOffice products share common systems management, registry, performance monitoring, and configuration tools. Again, learning curves are held to a minimum as each new product is introduced into your Information Network.
- Overlap. Microsoft intentionally leverages other BackOffice products in their design. A good example of this is the dependency SMS has on SQL Server. SMS stores its information about your network in a SQL Server database. This reduces the time necessary to administer SMS as the database administration is already being performed as a part of the SQL Server installation. Microsoft pledges to follow this pattern with future BackOffice products.
- Tracking. Each Microsoft BackOffice product contains an event log to record program execution and client activity. You may configure the event logs to support your specific needs. These event logs can be used, among other things, to troubleshoot problems with the network, applications, or users.
- Remote Access. Administration can be performed remotely via Remote Access Server (RAS). RAS, which comes with Windows NT Server, allows you to access the network through dial-up connections. Every administrative tool can be executed in this manner.
- Version Control. Software distribution has become a labor-intensive task. Visiting every user's PC and performing the appropriate action for something as simple as a software version upgrade is now a formidable task in many organizations. Microsoft BackOffice facilitates the automated management of software version control throughout the network via SMS. SMS allows you to control all the software on the network and desktop PCs from a central location.
- Hardware Inventory. In addition to managing software distribution, SMS deals with hardware issues. SMS can track hardware inventory, configuration parameters, and assist in diagnosing hardware problems. All this can be done from your administration workstation.
Microsoft understands BackOffice products will only be as successful as the administrators managing the Information Network. For this reason, they have focused on easing the burden of administration by building a consistent set of graphical administration tools. The strength of the administration tool set will only improve as Microsoft and third-party developers continue to enhance the administrative capabilities of BackOffice.
See "Organize Administration Teams," (Ch. 3)
As a Developer
Software development is currently undergoing a fundamental transition. The industry is headed toward component-based software derived from the principles of object-oriented technology. Even though you will rarely hear object technology mentioned when discussing BackOffice with Microsoft, it is clearly based on object-oriented concepts.
Software development teams of the future will contain component builders and solution builders. Component builders will create the basic software objects that become the building blocks for applications. Solution builders will assemble these building blocks into software solutions.
Microsoft BackOffice does not diminish the need for developers to understand the principles of the underlying technologies.
Microsoft has stated their intention to move toward a component-based architecture for all of BackOffice. To the developer, this means Microsoft BackOffice will appear to you as a large set of building blocks from which you can choose software components when assembling an application. In addition to the many advantages brought about by object technology, Microsoft BackOffice provides many other benefits to developers, whether you are a component builder or a solution builder. Following is a list of advantages Microsoft BackOffice offers to developers:
- Open API. As previously mentioned, Microsoft BackOffice is based entirely on the Win32 API. This API is published and available to you for development of your own applications. Moreover, every aspect of Microsoft BackOffice is based on the same programming model.
- Open Object Model. All of Microsoft BackOffice is based on the same object model. The COM specification is also available to developers. Understanding these standards will put you in the best possible position to develop stable and sustainable applications.
- Consistent. The same programming model, APIs, and object model apply to client and server development in the world of client-server. Avoiding the cost of relearning any one of these as you shift from client development to server development contributes to more stability in the software and a more effective and efficient development environment.
- Distributed Computing. Microsoft BackOffice is a basis for the development of distributed applications. You have already seen how the Information Network distributes processes, data, and information objects. Combining Microsoft BackOffice with any number of sophisticated development tools on the market positions you to design, build, and implement truly distributed applications.
- Object-Oriented Technology. Applying the principles of object-oriented technology, it is possible for you to develop applications faster through the planned reuse of software components. Another benefit of software reuse is an increased level of stability in the applications. Applications built for the Information Network that follow the programming model and object model set forth by Microsoft are assured of measuring up to industry standards. This means your applications will be built by assembling software components originating from Microsoft, third-party vendors, and yourself.
- Inter-Process Communications. The means by which a developer instructs an application to communicate with another application is built into Microsoft BackOffice. Because the products are so tightly integrated, communicating with one is the same as communicating with any other. The same applies to your own applications. Simplifying inter-process communications significantly reduces the complexities associated with client-server development.
- Customizable. Microsoft BackOffice supports the use of customizable tools such as Microsoft Visual Basic, Microsoft Visual C++, and Microsoft Office. These tools, and others similar to them, arm you with everything you need to influence the operational characteristics of the Information Network. Providing this low level of control is a great benefit to developers, whether they are component builders or solution builders.
- Performance Tuning. In this world of distributed processes, it is often difficult to predict exactly how an application will perform once it is constructed. Some techniques are beginning to appear that allow performance to be modeled in complex computing environments as a part of design work steps. Nevertheless, it will always be necessary to rearrange process models after construction to optimize application performance. This process is often referred to as performance tuning. Microsoft BackOffice has an architecture that permits experimentation with the division of processes.
Even as software development tools have become incredibly powerful, the act of software development remains difficult. Software developers face innumerable complexities with each new application. Microsoft BackOffice assists developers by simplifying many tasks associated with software development - without sacrificing flexibility.
As a Computer User
In addition to being a manager, administrator, or developer, you are also a computer user on the network. What does Microsoft BackOffice mean to you as a computer user? What does it mean to the users of your network, servers, or applications? Even though this book is not intended for users of Microsoft BackOffice, it will be helpful for you to understand the many benefits to users, whether you are a manager, administrator, or developer. The advantages of Microsoft BackOffice to users include the following:
- Single Password. Users are required to remember only one user name and password in a Microsoft BackOffice environment. Integrated security makes it less frustrating for users in complex Information Networks.
- Location Independence. Users can operate their software and manipulate their data on their desktop PCs at the office, as well as their home or on the road. Remote access appears to the user just as office access. Microsoft has designed all BackOffice products to operate remotely as effectively as they do in the office. This allows traveling personnel to access information regardless of their location. It also allows companies to establish a telecomputing employment practice on a permanent or temporary basis.
- Consistent Interface. Client and server applications in the Microsoft BackOffice environment share the same user interface. This makes it easier for users to move from role to role with minimal impact to their work demands.
- Desktop Integration. PCs throughout your organization are equipped with various software packages. Perhaps your organization has selected, and enforces the use of, a standard set of personal productivity tools. Microsoft BackOffice is designed to integrate with these desktop information utility tools. In fact, the primary purpose of Microsoft BackOffice is to facilitate information delivery to the PCs on the Information Network. This high level of integration improves accessibility of data throughout the enterprise.
From Here...
The availability of more and better information supports the ultimate goal of any information systems group: to provide users with all the information required to seamlessly support their decision-making processes. Most organizations today are under constant pressure to make better and faster decisions. Facilitating the delivery of information to the decision makers promotes an effective decision-making environment.
To this end, this chapter gave you a first look at the technical foundation upon which Microsoft BackOffice is designed and built. This included examining the role of Windows NT Server as a network operating system and gaining an understanding of services, the most basic principle of Microsoft BackOffice. To bring it all together, you learned what Microsoft BackOffice means to you as an information systems manager, administrator, developer, or user.
- For the final steps in preparation of your Microsoft BackOffice implementation, see Chapter 3, "Preparing to Implement Microsoft BackOffice."
- For a thorough discussion of implementation planning, see Chapter 4, "Becoming Part of the Enterprise."
- To get started implementing Microsoft BackOffice, see Chapter 5, "Implementing Windows NT Server."
- To further explore the network implications of Windows NT Server, see Chapter 6, "The Role of the Network Administrator."
