Go To TechNet Home Page
| Updated: March 12, 1996 | Go To TechNet Home Page |
David Ostroff is a BackOffice Product Manager in the Microsoft Business Systems Division, has experience as a System Engineer concentrating on messaging platform and senior consultant for Microsoft Consulting Services.
What is BackOffice?
BackOffice Family
Why Windows NT Server
Solution Development Platform
BackOffice Audiences
BackOffice Plans
BackOffice Resources
Microsoft(R) BackOffice is an integrated family of server software built on the Microsoft Windows NT(TM) Server operating system. This family is the core of an information network, which provides traditional file and print services plus rich new network services on which you can build a new generation of information applications. These information applications are client/server solutions that help companies improve decision-making and streamline business processes. They allow desktops to access and integrate information from a variety of sources with unparalleled ease and price/performance.
Since Bill Gates introduced the vision of Information at Your Fingertips at Comdex 1990, Microsoft has been focused on providing easier and more powerful ways to access and manipulate information. Microsoft BackOffice is the result of over four years of work to realize this vision.
Microsoft BackOffice is an integrated family of applications built on the foundation of the sophisticated Windows NT Server operating system. Because its unique open architecture is designed to integrate easily with a wide range of existing systems, new services and capabilities can be added with a minimum of difficulty. It offers a powerful, secure, reliable, and open infrastructure to connect the enterprise.
Whether companies are developing new client-server business applications or downsizing existing applications, Microsoft BackOffice can be used as the hub of an information network to build custom solutions. It can also be used to add new functionality to existing minicomputer and mainframe systems and to evolve these to pure client-server or distributed applications as business needs dictate. In addition, Microsoft BackOffice provides small companies a way to build business applications that previously could not be considered because of expense and complexity.
BackOffice is the information server on which you build information solutions that form the hub of a new kind of network-- the information network. Information networks improve business decisions and streamline business processes.
Microsoft BackOffice is an integrated family of server software built on the Microsoft Windows NT Server operating system. The family consists of Windows NT Server as the network foundation; Microsoft SQL Server(TM) for managing and storing data; Microsoft SNA Server for host connectivity; Microsoft Systems Management Server for managing PCs and servers; and Microsoft Mail Server for distributing information. Mail Server will provide a direct upgrade path to Microsoft Exchange Server.
Microsoft BackOffice consists of the following products:
A common set of management tools is available within Windows NT Server. This decreases the need to learn different tools across a variety of environments. Administrators can centrally manage all shared resources and server applications through a single set of Windows-based management tools, both locally and remotely.
The management tools available include:
The Administration tools available include:
Server and server applications offer a Windows-based setup and follow a similar installation and setup process so you don't have to learn different programs. During the setup process, autodetection will detect, list and recommend network protocols, network cards, and peripherals such as CD-ROM drives. When in Windows NT Server and BackOffice server applications, on-line help is available. Windows client setup can also be automated.
Network client configuration utilities let you install client software automatically over the network. Below describes how to automate setup in the following BackOffice server applications
Dynamic tracing, event log and self-diagnostics are available for troubleshooting and support.
Remote configuration across bridges and routers, via Remote Access Control (RAS) is also available. RAS supports, Asynchronous., X.25, or ISDN, as well as SNA over RAS.
Users get a single user login to shared resources and server applications including SQL Server, SNA Server and System Management Server, both locally and remotely. Also, with Exchange when it ships. This will reduces administrator overhead. Administrators don't need to maintain separate user account databases for sharing resources and server applications.
Windows NT Server security ensures a single-network logon throughout the enterprise whether users are connected directly or dialed into the network Monitor and audit remote dial-in connections through the Event Viewer through RAS. Instead of using Windows NT Server security authentication, you can choose your own authentication package to integrate RAS more tightly into your existing security system.
Windows NT Server offers support for C-2 Level Security. Data encryption and authentication is supported for data transfer.
Microsoft Windows NT(TM) has built-in support for major network topologies including Ethernet (and variations such as 10BaseT), Token Ring, and Arcnet, with built-in support for major network protocols, including TCP/IP, IPX/SPX, NETBEUI, DECNet(R), XNS(R), OSI, Server Message Block (SMB), Netware Control Protocol (NCP), and AppleTalk(R). Windows-based desktops can be seamlessly connected not only to Microsoft network servers based on Windows NT Advanced Server, but also to Novell Netware (versions 2.x, 3.x and 4.x), Banyan Vines, IBM OS/2 LAN Server(R), LAN Manager, DEC PathWorks(R), Network File System (including Sun(R) NFS running on UNIX systems), and the Apple Macintosh.
SNA Server supports all major SNA connectivity options for IBM mainframe and AS/400(R) host-based systems. Windows NT Server supports multiple desktop client platforms including MS&hyph;DOS, Windows, Windows NT, Apple Macintosh, IBM OS/2 2.x, and all varieties of UNIX.
SQL Server and various Microsoft Solution Developers and Providers partners, including MDI and Information Builders, offer gateway connectivity to a variety of data formats including Oracle, DB2, Informix, Ingres, Btrieve, VSAM and IMS files.
The Services for NetWare outlined below provide seamless integration between Novell(R) NetWare and Windows NT environments.
Connects Windows NT Server to NetWare servers
The Client Service for NetWare in Windows NT Workstation allows a Windows NT Workstation-based computers to connect to files and printers on the NetWare servers. Windows NT Workstation-based computers can store and print information on NetWare servers, and have access to many of the most commonly used NetWare-aware applications such as NetWare SAA and Lotus Notes(R). Users who have supervisor rights will also be able to run the administrative utilities commonly used in managing NetWare servers, such as SysCon and PConsole.
The Client Service for NetWare integrates the Windows NT and NetWare environments. It can be configured so that a single logon can provide access to a computer running the Windows NT Workstation, NetWare file and print servers, or Windows NT Server operating systems.
Clients connected to Windows NT Server can access files and printers on the NetWare server
The Gateway Service for NetWare provides local and remote users who are connected to Windows NT Server access to the files and printers on NetWare servers. It is an ideal integration tool for companies who have systems which run on both NetWare and Windows NT in a heterogeneous server environment. The network administrator controls who and how many people have access to the gateway so only those with permission can use file and print resources on designated NetWare servers.
Customers use the Gateway Service for NetWare to isolate IPX/SPX traffic and ease the transition to TCP/IP as well as run Microsoft Remote Access Service. Users with Microsoft Windows For Workgroups, MS-DOS, or the Windows NT platform can use Remote Access Service and still maintain connectivity to a NetWare server.
The Gateway Service for NetWare is installed as a service on the Windows NT Server. It is available to authorized users as long as the system is running and requires no special intervention once it is configured.
Add Windows NT Server as an application with no change to NetWare Clients or network
NetWare clients can access server applications such as Microsoft SQL Server, SNA Server and others running on Windows NT Server without changing their client software by using NWLink the IPX/SPX compatible transport which comes standard with Windows NT.
Windows NT Server will automatically check the network during installation to see which transport is currently running on the network. If it finds SPX/IPX, the server will automatically default to the NWLink (IPX/SPX) transport.
The Migration Tool for NetWare in Windows NT Server aids network administrators by copying user accounts and files from NetWare 2.x and 3.x servers to a Windows NT Server-based computer while maintaining security. It has the capabilities of both an integration and migration tool.
Provides an easy way to migrate Windows NT Servers to achieve a single network logon
In a migration environment, the Migration Tool for NetWare allows the administrator great flexibility in transferring user accounts and data to the Windows NT platform. Users can migrate a single NetWare server to a single Windows NT Server, multiple NetWare servers to a single Windows NT Server, or many other configurations allowing for the redistribution of information across the servers in your network. Since there are some security differences between NetWare and Windows NT Server, the Migration Tool includes a trial migration process that generates detailed log files. These files eliminate the guess work and assist the administrator in keeping track of any changes that may occur during the migration process.
The Migration Tool for NetWare simply copies the users, groups, files, and directories to the Windows NT Server without affecting the NetWare server. Server applications such as SQL Server, SNA Server and Exchange Server share the same user account database as Windows NT Server. Therefore, you can use the migration tool to automatically copy user accounts from the NetWare server and mirror those NetWare accounts on the Windows NT Server, saving the administrator valuable time with the initial server setup.
Sold separately from Windows NT Server, Microsoft File and Print Service for NetWare makes it easy to bring Windows NT Server functionality into a NetWare network. File and Print Service for NetWare makes a Windows NT Server machine a fully NetWare 3.x compatible file and print server. This means that Windows NT Server can supply both the file and print services customers use today plus the advanced application, communication, and management services Windows NT Server is known for - all without modifying the existing NetWare network, client software or user login scripts.
In addition, NetWare administrators will be able to manage Windows NT Server easily. Windows NT Server already integrates seamlessly with SNMP-based management solutions such as Novell's NetWare Management System. In addition, third-party tools, such as McAfee's NetTools, are available today for Windows NT Server. Frye Utilities for Networks (including StatRack), Saber's Enterprise Application Manager (and other tools), and Symantec's Norton AntiVirus are also being ported to Windows NT Server.
In Windows NT Server 3.5, Microsoft included the Migration Tool for NetWare. The Migration Tool for NetWare automatically migrates NetWare user and group accounts, files and directories, and security and permissions to Windows NT Server. With the release of File and Print Service for NetWare, Microsoft has enhanced its Migration Tool for NetWare to migrate NetWare user login scripts. By automatically migrating these components, Migration Tool for NetWare saves administrators the time and effort of recreating user accounts, files, directories, permissions, and login scripts thereby making the transition to Windows NT Server extremely easy.
TCP/IP, a de facto standard for UNIX networking, is included in Windows NT Server to help you create heterogeneous networks. Configuring of Windows NT Server for TCP/IP after installation allows you to set the IP address, subnet mask and broadcast parameters with DHCP/WINS graphical interface. Windows NT includes the most common TCP/IP utility: File Transfer Protocol (ftp and tftp). This familiar UNIX utility provides easy file transfer between Windows NT and UNIX hosts. With Windows NT, you can set up an anonymous ftp server as well as connecting to UNIX-based hosts. For terminal access to a UNIX host, the familiar Windows terminal "applet" has been upgraded to provide Telnet capability. Through a DCE-compatible remote procedure call (RPC) mechanism, Windows Sockets and built-in TCP/IP support, client can be connected to any version of UNIX.
Users get network connectivity between Windows family and UNIX systems through technologies and products like Network File System (NFS), LAN Manager for UNIX (LMU), TCP/IP, and the X Window System(TM) protocol. Microsoft has made the Windows application program interfaces (APIs) available to developers on UNIX systems through the Windows Interface Source Environment (WISE) licensing program. With WISE products, users will be able to run shrink-wrapped Windows applications on UNIX systems. Microsoft's object technology, OLE, will also become available on UNIX systems through WISE. Users and developers get cross-platform database services between Windows family and UNIX systems through Open Database Connectivity (ODBC) and Open Data Services. Users can send and receive email between the Windows family and UNIX systems using products like Microsoft Mail and Microsoft Exchange Server. System managers can manage heterogeneous systems using Microsoft Systems Management Server and third party Windows family based Simple Network Management Protocol (SNMP) management software such as OpenView and NetView(R).
Access to BackOffice services such as SQL Server through Open Database Connectivity (ODBC), Mail & Exchange through Messaging API (MAPI), SNA through the WOSA SNA APIs, Systems Management Server through DMI offers integration with Windows and Microsoft Office desktop applications. This offers companies the necessary tools to build networked applications through standard, network independent interfaces and services.
The Windows Open Services Architecture (WOSA) is a major focus of Microsoft's goal to provide an open environment for the development and use of Windows-based applications. Far broader than an API, WOSA is an architecture that promotes the easy integration of Windows and Windows-based applications within heterogeneous enterprise-wide computing environments. WOSA provides seamless access to three categories of information resource services: common application services, communication services and vertical market services. WOSA's component services are defined in cooperation with hardware manufacturers, corporate developers, and independent software vendors through the Open Process program. The WOSA effort has the backing of hundreds of industry members. Microsoft has adopted de jure specifications for WOSA where relevant.
Pictured above are two components of WOSA, Open Database Connectivity (ODBC) and the Messaging API (MAPI). Through a consistent and open architecture, Windows-based applications can transparently access key services across multiple vendor implementations. These services can span different hardware and operating system environments.
OLE offers object-enabling system software. OLE is based on the Component Object Model (COM), an underlying system software object model that allows complete interoperability between components that are written by different companies even when programmed in different languages. These components can be purchased, replaced, enhanced and reused at any time during the business-system life cycle.
The primary responsibility of the Component Object Model is to ensure that software components behave in a well-known and consistent manner without constricting how programmers implement different components. The Component Object Model accomplishes this by defining a binary interface for objects that is independent of any programming language. Objects conforming to the Component Object Model can communicate with each other without being programmed with specific information about each other's implementations.
Objects that are written to support the Component Object Model are collectively called component objects. Every feature of OLE depends on the Component Object Model to provide basic inter-object communication. OLE is a set of object services built on top of the Component Object Model. OLE provides a robust platform for building custom business applications that can be easily integrated with other business applications as well as with packaged software, whether the applications execute on a single machine or are distributed across a network.
Besides the OLE Component Object Model itself, there are many additional OLE features that directly benefit both users and corporate developers. Some of the major features of OLE are listed below.
Through Windows NT Server, corporations can choose to deploy Windows-based applications not only on thousands of different brands of Intel x86-based PCs, but also on computers based on RISC chips that include the DEC Alpha AXP(R) and the MIPS(R) Rx400 family today; with the PowerPC(TM) and other RISC chips in the near future. Additionally, with seamless symmetric multiprocessing (SMP) support, the Windows family brings incredible scalability for any business solution based on the standard Win32(R) API. Through complete source-code portability for all Win32-based (32-bit) applications, Windows-based solutions can be scaled from CISC-based (Intel x86 and Pentium) and RISC-based computers incorporating from one to 32 CPUs (with support for even more processors soon).
Under the new Microsoft pricing policy for Windows NT Server, SQL Server, SNA Server, Systems Management Server and BackOffice (and eventually Exchange), servers and clients are licensed independently.
These two licenses are :
This model has a number of advantages, including:
By integrating the various interfaces, gateways and services available, information from various BackOffice and third party repositories can be accessed and made available to the desktop. Below lists some data repositories that can be accessed and made available to the BackOffice family of products:
ODS Gateway's to variety of data formats
MAPI connects to various back-ends
SNA Server APIs accesses information on IBM platform
By integrating these services between the BackOffice family of products, below lists some examples of additional functionality available:
MAPI integration with SQL Server provides:
Systems Management Server integration with SQL Server provides:
Systems Management Server integration with any BackOffice application
SNA integration with SQL Server provides:
SNA integration with any BackOffice application:
Systems Management Server Integration with SNA provides:
SNA Integration with SQL
SQL Integration with any BackOffice application
Consistent development environment. The same Win32 and OLE component software technology is shared between the client, the server, and the server applications. This consistency lowers development, support and training costs. Over 250 development tools and over 120,00 developers for OLE. C, C++, Visual Basic and VBA from Microsoft can all be used to develop solutions that leverage the processing and can be partitioned during development to offer optimal performance on the client and server once deployed.
Leverage over 1000 off-the-shelf applications and tools to build or buy customized solutions more quickly and with greater flexibility. This allows existing applications, thousands of general purpose and vertical Windows applications, to be implemented to meet business demands. Use wide of off -the-shelf tools and applications on both the client and the server for faster deployment and greater flexibility.
Support for Microsoft's strategic object technology (OLE 2) and standard API set (Win32) means your investment is protected in the future.
Deploying software has been made easier with the automated client setup and installation available within Windows NT Server. This process can be improved by leveraging Systems Management Server.
Since Systems Management Server works over a LAN and WAN, hardware and software inventories can be quickly completed and software installation and file distribution can be offered automatically. Systems Management Server also provides Provide Program Description Files (PDF's), which are Pre-packaged scripts for server component or client installation. This offers the ability to deploy custom installation either locally and over the network. Software distribution and installation capabilities make it easy to install applications, patches, or virus-checking software once on a PC, then automatically distribute to other PCs on the local network and at remote sites.
Windows NT Server offers SNMP and DMI clients and servers support of industry standard management. This offers administrators the ability to extend management and support of Windows NT Server
With the remotable registry configuration and console, local and remote client user profile can be easily accessed and maintained.
The Administration tools available within Windows NT Server offers administrators the ability to conduct proactive and maintenance support. For instance the performance monitor can be used to monitor potential bottleneck areas.
Including Systems Management Server, the Network Protocol Analyzer can be used to troubleshoot this bottleneck areas. Through the event log available with Windows NT Server, troubleshooting can be performed without involving end user to explain exactly what series of events caused particular problems. With Systems Management Server, the Remote Troubleshooting functionality can be utilized to repair the problem from a remote site.
BackOffice family of products integrate with Windows NT tools, offering access to User Manager, Server Manager, Performance Monitor and event logs.
The security database (SAM) available within Windows NT Server offers centralized management for all clients, servers and server applications for local and remote users. The user and server manager within Windows NT Server offer centralized management of user profiles, as well as ability to start and stop services in use.
Network configuration is simplified for administrators using TCP/IP Dynamic Host Configuration Protocol (DHCP) and Windows Internet Naming Service (WINS).
Systems Management Server extends the management of Windows NT Server and software inventory automatically collects detailed configuration information about all PCs on the network. It will determine how many copies of a software package are installed in your organization, what PCs need hardware upgrades, or which PC has a specific network address. When managing applications that run from servers, Systems Management Server gives users a standard set of applications from any PC anywhere on the network. Systems Management Server makes it easier to use application metering packages and match the number of an application's users to the number of software licenses you have.
The System Integrator or Analyst has the opportunity to build additional functionality with each BackOffice family product. Below are some example:
SQL Server offers the following development tool:
Mail and Exchange offers the following development tool sets:
SNA Server offers the following development tool sets:
Systems Management Server offers the following development tool sets:
Windows NT Server offers the following development tool sets:
Below provides requirements for any Solution Developer, ISV or IHV who vend applications and hardware that are compatible and exploitive of the Microsoft Windows NT Server Platform and the BackOffice set of applications: Mail/Exchange, SQL, Systems Management Server, and SNA. There are two groups of ISV's that fall under this single initiative:
|
Windows NT Server Explotive Applications &boxf; Good Win32 Application &boxf; High Performance &boxf; Network Independent &boxf; Secure &boxf; Remotely Administerable |
SNA Exploitive &boxf; Support Server Points of Light on the Server &boxf; Use appropriate APPC verbs &boxf; Use the MS Link Service &boxf; Practice Fairness in Session Management &boxf; Exploit WLUA and WHLLAPI |
|
Systems Management Server Deployable Client and Server Applications &boxf; Permit UI-less Installation &boxf; Support De-installation &boxf; Report status and inventory via a MIF &boxf; Provide an Systems Management Server PDF file with the application |
Systems Management Server Integrated Applications &boxf; Extend the console to provide application specific data in inventory and trouble shooting |
|
Exchange Client Applications &boxf; Use MAPI for send and post &boxf; Build custom forms for application specific messages &boxf; Provide custom properties for view in documents |
Exchange Server Applications &boxf; Integrate with Exchange Administration &boxf; Provide Mailbox for Server Application &boxf; Integrate with Exchange Admin &boxf; Preserve Messaging Data in Transmission |
|
SQL Client Applications &boxf; Exploit ODBC 2.0 &boxf; Support NT integrated security &boxf; Support OLE Automation Interface for automating common administrative tasks |
SQL Server Applications &boxf; Use ODS &boxf; Extend Admin |
A Unified BackOffice SDK will be available over MSDN Level II in Q1 95. This will include BackOffice family SDKs, development information for SQL Server version 6.0 and Exchange, information and code for BackOffice Compliance Program and Cross Server application code
Initial Combined BackOffice Server Product available in Q2/3 of 1995 will include SQL Server version 6.0, SNA 2.11, Systems Management Server 1.0, Mail 3.2b, NT Server 3.51, Mail NT MMTA.
Future releases of BackOffice will include Exchange and Cairo technologies, as well as continue to leverage interfaces and services available through WOSA, Win32 and OLE.
Additional means of continuing to learn about BackOffice family of products are:
(C) 1995 Microsoft Corporation.
THESE MATERIALS ARE PROVIDED "AS-IS," FOR INFORMATIONAL
PURPOSES ONLY.
NEITHER MICROSOFT NOR ITS SUPPLIERS MAKES ANY WARRANTY, EXPRESS
OR IMPLIED WITH RESPECT TO THE CONTENT OF THESE MATERIALS OR THE
ACCURACY OF ANY INFORMATION CONTAINED HEREIN, INCLUDING, WITHOUT
LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. BECAUSE SOME STATES/JURISDICTIONS DO
NOT ALLOW EXCLUSIONS OF IMPLIED WARRANTIES, THE ABOVE LIMITATION
MAY NOT APPLY TO YOU.
NEITHER MICROSOFT NOR ITS SUPPLIERS SHALL HAVE ANY LIABILITY FOR
ANY DAMAGES WHATSOEVER INCLUDING CONSEQUENTIAL INCIDENTAL, DIRECT,
INDIRECT, SPECIAL, AND LOSS PROFITS. BECAUSE SOME STATES/JURISDICTIONS
DO NOT ALLOW THE EXCLUSION OF CONSEQUENTIAL OR INCIDENTAL DAMAGES
THE ABOVE LIMITATION MAY NOT APPLY TO YOU. IN ANY EVENT, MICROSOFT'S
AND ITS SUPPLIERS' ENTIRE LIABILITY IN ANY MANNER ARISING OUT
OF THESE MATERIALS, WHETHER BY TORT, CONTRACT, OR OTHERWISE SHALL
NOT EXCEED THE SUGGESTED RETAIL PRICE OF THESE MATERIALS.
 |
Click Here to Search TechNet Web Contents | TechNet CD Overview | |
Microsoft TechNet Credit Card Order Form At this time we can only support electronic orders in the US and Canada. International ordering information. |
| Go To TechNet Home Page |
©1996 Microsoft Corporation |  Go To Microsoft Home Page |