Professional Documents
Culture Documents
Contents
Introduction ......................................................................................................................................... 1 Microsoft Axapta Object Server (AOS)............................................................................................... 2 Two-Tier Architecture ..................................................................................................................... 2 AOS and Three-Tier Architecture................................................................................................... 2 Advantages of Using Three-Tier Architecture................................................................................ 3 Remote clients............................................................................................................................. 3 Performance and Hardware ........................................................................................................ 3 Opportunity for scaling ................................................................................................................ 4 Security........................................................................................................................................ 4 Limitations ................................................................................................................................... 4 Business Advantages of using AOS .............................................................................................. 4 Microsoft Axapta Enterprise Portal ..................................................................................................... 5 What is Microsoft Axapta Enterprise Portal? ................................................................................. 5 Advantages .................................................................................................................................... 6 Out of the Box.............................................................................................................................. 6 One Application ........................................................................................................................... 6 Security........................................................................................................................................ 6 Development suite....................................................................................................................... 6 Multiple devices ........................................................................................................................... 6 Features ......................................................................................................................................... 6 Style sheet editor......................................................................................................................... 6 Weblets........................................................................................................................................ 7 Web parts .................................................................................................................................... 7 Web panels.................................................................................................................................. 8 Limitations ...................................................................................................................................... 8 Business Advantages of Microsoft Axapta Enterprise Portal......................................................... 8 Microsoft Axapta Commerce Gateway............................................................................................... 8 What is Microsoft Axapta Commerce Gateway? ........................................................................... 8 When do we need this type of connection? ................................................................................... 9 The Hub and Spoke scenario...................................................................................................... 9 The Customer Vendor scenario .................................................................................................. 9 How does it work? .......................................................................................................................... 9 Advantages of Microsoft Axapta Commerce Gateway and Microsoft BizTalk Server ................... 9 System Requirements .................................................................................................................. 10 About Microsoft Business Solutions ................................................................................................. 10
Introduction
As a company grows, more demands are placed on its business applications. Business leaders and system administrators of growing companies need a solution that can support greater numbers of users and larger transaction volumes. In order to compete effectively, a companys business solution must connect not only business processes across different departments, but also customers, vendors, business partners and employees with the companys business logic and data. One of the best arguments for choosing Microsoft Business SolutionsAxapta is the solutions scalability and its ability to connect internal and remote users as well as external systems in a global environment. This document will further describe the scalability and many possibilities for advanced connectivity that are offered by Microsoft Axapta, specifically: Three-tier technology using Microsoft Axapta Application Object Server (AOS) Microsoft Axapta Enterprise Portal Microsoft Axapta Commerce Gateway This document will also describe the functionality, advantages and limitations that business partners and customers should be aware of, in order to plan and build the best solution for each customer. Each solution should be built according to the customers business needs, and should leave out unnecessary functionality in order to optimize the customers total cost of ownership (TCO). This document will also provide the technical knowledge needed for sales staff to build sales presentations based on these technologies.
Fileserver
Two-tier architecture
The architecture of two-tier Microsoft Axapta solutions consists of a database server that contains the business data, and a file server that contains application files. Separate computers run the application itself. The application is executed only on these application computers. This two-tier architecture functions well, but requires high-capability computers for the users and a strong network as well. Therefore, the two-tier architecture may not be well-suited for remote users working from a fixed location with a weak network, or for mobile users working from different locations with different network capabilities.
AOS Clients
Three-tier architecture
The difference between this installation and the two-tier solution shown above is that with three-tier architecture, part of the application is executed on the client and another part on the AOS. Therefore, all user interface-related processes are executed on the thin client computers operated by the users, and all business logic is executed on the server. For example, when a user decides to update a journal, the menus used for selecting this process are executed on the client, but the journal update process itself is executed on the server. This means that it isnt necessary to send all the data from the database through the AOS to the client to be updated, and then back again through the system to the servers.
Traffic
AOS Client
Time
Caption?
The figure shows that a solution using terminal server client will face constant strain on the network capacity over time, and each additional user will move the terminal server client curve upwards until the capacity of the network is exhausted. The AOS client, on the other hand, can cause less strain on the network because this client only uses network resources when performing some action in Microsoft Axapta. Such a network can use the same bandwidth as much as three times more efficiently. Finally, unlike the terminal server client, the three-tier Microsoft Axapta client can integrate with other applications on the local computer. Performance and Hardware Because three-tier architecture causes part of the application to be executed on the client and another part on the AOS, the client computers do not need to be as powerful as those required by a two-tier solution. But Microsoft Axapta does not require system implementers or administrators to choose between building a two or three-tier solution. Microsoft Axapta can be implemented as a combination of both architectures if desired. If powerful computers are available on the client side, they can be configured as rich clients instead of thin clients. The difference between the rich client and the thin client is that the rich client connects directly to the database used by Microsoft Axapta. Like the thin client, the rich client is also connected to the AOS, but unlike the thin client, the rich client executes both user interface commands and business logic. This way, some of the workload is distributed from the AOS to the rich client computers.
Benchmark test results can be compared for more details about system response times on a given hardware architecture for different numbers of Microsoft Axapta users. Benchmark test results will be released throughout 2004. Opportunity for scaling Microsoft Axapta supports clustering. Clustering means that as the numbers of clients are increased to the point where the AOS is about to become a bottleneck in the solution, additional AOSs can be installed to increase the available bandwidth. Installing additional AOSs is simple, and does not require the Microsoft Axapta solution to be shut down during the installation process. When using clustered AOSs, a load-balancing process helps ensure that each time a user logs on, the user will be connected to the server with the smallest number of connected clients. Clustering also reduces the chance of a total system failure. Server redundancy helps ensure that if one of the AOSs should fail, users can continue working using one of the remaining active servers. It is important to note that the functionality described above is standard Microsoft Axapta functionality, and does not require any additional software. Microsoft Axapta is designed so that customers can add client computers in different locations whenever they need to expand their number of users. Using the Web-deployed client functionality, it is possible to download Microsoft Axapta client software from any location, using a computer with an Internet connection and a browser. Once downloaded, the client software can be installed, and then the computer or computers can be connected with the AOS just like any other new user. Security In a thin client three-tier solution, the AOSs can also shield the Microsoft Axapta database from security threats, because thin clients connect with the database only through the AOS. They do not connect directly with the database as would be the case with rich clients, or with a two-tier solution. Microsoft Axapta permits data to be encrypted two ways. The first method uses Virtual Private Network (VPN), while the second method uses the Microsoft Axapta AOCP protocolan internal cryptography mechanism that is an integral part of the solution and is available at no extra cost. Both these methods use 128bit encryption. However, VPN is more advanced than the AOCP protocol. It is also possible to integrate AOS with Microsoft Active Directory, which allows companies with security policies that require Microsoft Active Directory to take advantage of AOS. Limitations When implementing Microsoft Axapta with connectivity to remote clients, it is important to ensure that latency in the network is less than 100 milliseconds. When AOS technology is integrated with Active Directory, AOSs cannot be clustered as described above.
Advantages
With Microsoft Axapta Enterprise Portal, employees can keep their own data up-to-date, which can reduce transaction costs and paperwork. Sales staff can input sales orders online and check on item availability no matter where they are located, and customers can create purchase orders without the assistance of sales support staff. Microsoft Axapta Enterprise Portal also provides many critical technological advantages. Out of the Box The Microsoft Axapta base package contains everything a company needs to develop and deploy Microsoft Axapta Enterprise Portal. All users need to access the portal is a computer with on-line access, and a Microsoft Windows operating system that includes Internet information services and Component services One Application Regardless of whether a user is accessing Microsoft Axapta as a normal client or a Web user, the solution uses only one business logic. If administrators want to apply new functionality or change existing functionality, the changes will be applied instantly across the system, and will affect all users with access to the affected functionality regardless of which type of users they are. This can reduce the time and cost for upgrades, customization, and configuration. Security All Microsoft Axapta users are attached to one or more user groups. Users are granted access to data and functionality in the system through these groups, and the same security settings apply to both Microsoft Axapta Windows client users and Web users. External Web users will normally access Microsoft Axapta through a firewall. Development suite The same development suite is used for developing Web applications as well as the rest of the Microsoft Axapta application. Experienced Microsoft Axapta developers will not need to be reeducated when learning how to create Web applications. For example, creating Web forms is similar to the procedure for creating forms for the Microsoft Axapta Windows client.
Multiple devices Microsoft Axapta Web applications use an internet browser as the user interface. These browsers can run on different devices, such as network-connected computers and mobile devices such as PDAs.
Features
Style sheet editor Administrators can use the integral Microsoft Axapta style sheet editor to design the style sheets used in their Web applications. Style sheets control details such as fonts and colors used on Web
pages, and drastically simplify Web site maintenance. Changes in a style sheet automatically and instantly change every Web page controlled by that style sheet. Weblets Weblets are used to display Microsoft Axapta objects in Web applications, so that users can access Microsoft Axapta data and functionality through Web forms and Web reports. It is possible for administrators to develop new weblets to present new functionalities.
Web parts Besides using weblets as described above, administrators can also use Web parts. A Web part is a special type of weblet, which can be used to display information and functionality from external sources and services. Displaying weather forecasts and stock quotes.
Web panels A Web panel can be described as a container. When designing a Web application, Web parts and other items used to access business data from Microsoft Axapta can be collected into Web panels. Web panels can be hidden or revealed to individual user groups through the standard security setup.
Limitations
Because Web users and Microsoft Axapta Windows clients may be accessing the same application at the same time, it is possible that the system may suffer from slow response times if the hardware has not been sized with the total number of Web and Microsoft Axapta Windows client users taken properly into account.
external users to access our system. With Microsoft Axapta Commerce Gateway, it is possible to connect Microsoft Axapta directly with other systems.
Microsoft BizTalk Server is a data and business process integration server. It exchanges documents in specific formats, executes business processes and contains tools for document and server management.
Reduced transaction costs, since no human interaction is involved in process No opportunity for human errors Improved security All aspects of the communication between both parties can be handled automatically Business partners can use different document formats, and still communicate with each other
System Requirements
To receive the advantages of Microsoft Axapta Commerce Gateway described above, it is necessary to use Microsoft BizTalk Server.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This white paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in, or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. 2003 Microsoft Business Solutions ApS, Denmark. All rights reserved. Microsoft, Great Plains, and Axapta, are either registered trademarks or trademarks of Microsoft Corporation, Great Plains Software, Inc or Microsoft Business Solutions ApS or their affiliates in the United States and/or other countries. Great Plains Software, Inc. and Microsoft Business Solutions ApS are subsidiaries of Microsoft Corporation. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. The example companies, organizations, products, domain names, email addresses, logos, people and events depicted herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, or event is intended or should be inferred.
10