KEMP Microsoft Dynamics AX, LoadMaster Deployment Guide

Below you will find brief information for Microsoft Dynamics AX. This document will guide you through the deployment process of Microsoft Dynamics AX using the KEMP LoadMaster, an efficient solution for load balancing and high availability for the Microsoft Dynamics AX application. The document also includes information about the configuration of Virtual Services for the Microsoft Dynamics AX application and explains how to enable subnet originating requests globally.

PDF

Document

Microsoft Dynamics AX
Microsoft
Dynamics AX
Deployment Guide
VERSION: 1.0
UPDATED: JULY 2016
Microsoft Dynamics AX
Copyright Notices
Copyright &copy; 2002-2016 KEMP Technologies, Inc.. All rights reserved.. KEMP Technologies and the KEMP
Technologies logo are registered trademarks of KEMP Technologies, Inc..
KEMP Technologies, Inc. reserves all ownership rights for the LoadMaster product line including software
and documentation. The use of the LoadMaster Exchange appliance is subject to the license agreement.
Information in this guide may be modified at any time without prior notice.
Microsoft Windows is a registered trademarks of Microsoft Corporation in the United States and other
countries. All other trademarks and service marks are the property of their respective owners.
Limitations: This document and all of its contents are provided as-is. KEMP Technologies has made efforts
to ensure that the information presented herein are correct, but makes no warranty, express or implied,
about the accuracy of this information. If any material errors or inaccuracies should occur in this document,
KEMP Technologies will, if feasible, furnish appropriate correctional notices which Users will accept as the
sole and exclusive remedy at law or in equity. Users of the information in this document acknowledge that
KEMP Technologies cannot be held liable for any loss, injury or damage of any kind, present or prospective,
including without limitation any direct, special, incidental or consequential damages (including without
limitation lost profits and loss of damage to goodwill) whether suffered by recipient or third party or from
any action or inaction whether or not negligent, in the compiling or in delivering or communicating or
publishing this document.
Any Internet Protocol (IP) addresses, phone numbers or other data that may resemble actual contact
information used in this document are not intended to be actual addresses, phone numbers or contact
information. Any examples, command display output, network topology diagrams, and other figures
included in this document are shown for illustrative purposes only. Any use of actual addressing or contact
information in illustrative content is unintentional and coincidental.
Portions of this software are; copyright (c) 2004-2006 Frank Denis. All rights reserved; copyright (c) 2002
Michael Shalayeff. All rights reserved; copyright (c) 2003 Ryan McBride. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:
1.
Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer
2.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the
following disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE ABOVE COPYRIGHT HOLDERS ''AS IS'' AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE ABOVE COPYRIGHT
HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
The views and conclusions contained in the software and documentation are those of the authors and
should not be interpreted as representing official policies, either expressed or implied, of the above
copyright holders..
Portions of the LoadMaster software are copyright (C) 1989, 1991 Free Software Foundation, Inc. -51
Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA- and KEMP Technologies Inc. is in full compliance
of the GNU license requirements, Version 2, June 1991. Everyone is permitted to copy and distribute
verbatim copies of this license document, but changing it is not allowed.
Copyright &copy; 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved.
2
Microsoft Dynamics AX
Portions of this software are Copyright (C) 1988, Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms are permitted provided that the above copyright notice
and this paragraph are duplicated in all such forms and that any documentation, advertising materials, and
other materials related to such distribution and use acknowledge that the software was developed by the
University of California, Berkeley. The name of the University may not be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.
Portions of this software are Copyright (C) 1998, Massachusetts Institute of Technology
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the &quot;Software&quot;), to deal in the Software without restriction, including without
limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the
Software, and to permit persons to whom the Software is furnished to do so, subject to the following
conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions
of the Software.
THE SOFTWARE IS PROVIDED &quot;AS IS&quot;, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Portions of this software are Copyright (C) 1995-2004, Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be
held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications,
and to alter it and redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the original
software. If you use this software in a product, an acknowledgment in the product documentation would
be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the
original software.
3. This notice may not be removed or altered from any source distribution.
Portions of this software are Copyright (C) 2003, Internet Systems Consortium
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is
hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
THE SOFTWARE IS PROVIDED &quot;AS IS&quot; AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING
ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT,
INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE
USE OR PERFORMANCE OF THIS SOFTWARE.
Used, under license, U.S. Patent Nos. 6,473,802, 6,374,300, 8,392,563, 8,103,770, 7,831,712, 7,606,912, 7,346,695, 7,287,084 and
6,970,933
Copyright &copy; 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved.
3
Microsoft Dynamics AX
Table of Contents
1
Introduction .................................................................................................................................... 5
1.1
Document Purpose ................................................................................................................. 5
1.2
Intended Audience .................................................................................................................. 5
2
Microsoft Dynamics Template ........................................................................................................ 6
3
Architecture .................................................................................................................................... 7
4
Configure Microsoft Dynamics Virtual Services .............................................................................. 8
4.1
Enable Subnet Originating Requests Globally......................................................................... 8
4.2
Microsoft Dynamics AX ERP Portal Virtual Service ................................................................. 9
4.3
Microsoft Dynamics AX HTTP (Redirect) Virtual Service....................................................... 10
4.4
Microsoft Dynamics AX AOS Virtual Service ......................................................................... 10
References ............................................................................................................................................ 12
Document History ................................................................................................................................. 13
Copyright &copy; 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved.
4
Microsoft Dynamics AX
Introduction
1 Introduction
Microsoft Dynamics AX is an Enterprise Resource Planning (ERP) software package developed for
businesses. It aims to drive sales, productivity and marketing effectiveness through social
insights, business intelligence and campaign management in the cloud, on-premises or with a
hybrid combination of both.
Such a powerful tool requires reliable and powerful support. The KEMP LoadMaster delivers an
exceptional, cost-effective and easy to use solution which, by employing Adaptive Load
Balancing, balances requests across Microsoft Dynamics.
When deployed as a pair, two LoadMasters give the security of High Availability (HA). HA allows
two physical or virtual machines to become one logical device. Only one of these units is ever
handling traffic at any particular moment. One unit is active and the other is a hot standby
(passive). This provides redundancy and resiliency, meaning if one LoadMaster goes down for
any reason, the hot standby can become active, therefore avoiding any downtime. For more
information on HA please refer to: High Availability (HA), Feature Description.
1.1
Document Purpose
This document is intended to provide guidance on how to deploy Microsoft Dynamics AX with a
KEMP LoadMaster. The KEMP Support Team is available to provide solutions for scenarios not
explicitly defined.
The KEMP support site can be found at: https://support.kemptechnologies.com.
1.2
Intended Audience
This document is intended to be used by anyone deploying Microsoft Dynamics AX with a KEMP
LoadMaster.
Copyright &copy; 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved.
5
Microsoft Dynamics AX
Microsoft Dynamics Template
2 Microsoft Dynamics Template
KEMP has developed a template containing our recommended settings for Microsoft Dynamics
AX. This template can be installed on the LoadMaster and used when creating Virtual Services.
Using a template automatically populates the settings in the Virtual Services. This is quicker and
easier than manually configuring each Virtual Service. If needed, changes can be made to any of
the Virtual Service settings after using the template.
Download released templates from the Templates section on the KEMP documentation page:
http://kemptechnologies.com/documentation/.
For more information and steps on how to import and use templates, refer to the Virtual
Services and Templates, Feature Description.
For steps on how to manually add and configure each of the Virtual Services, refer to the
Configure Microsoft Dynamics Virtual Services section of this document.
Copyright &copy; 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved.
6
Microsoft Dynamics AX
Architecture
3 Architecture
Input Devices
Internet
Firewall
KEMP LoadMasters
Microsoft Dynamics AX
Servers
SQL Database
Figi&uacute;r 3-1: MS Dynamics AX Architecture
Copyright &copy; 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved.
7
Microsoft Dynamics AX
Configure Microsoft Dynamics Virtual Services
4 Configure Microsoft Dynamics Virtual Services
The environment in which Microsoft Dynamics AX is deployed determines
which of the following set-ups should be used.
4.1
Enable Subnet Originating Requests Globally
It is best practice to enable the Subnet Originating Requests option globally.
In a one-armed setup (where the Virtual Service and Real Servers are on the same
network/subnet) Subnet Originating Requests is usually not needed. However, enabling Subnet
Originating Requests should not affect the routing in a one-armed setup.
In a two-armed setup where the Virtual Service is on network/subnet A, for example, and the
Real Servers are on network B - Subnet Originating Requests should be enabled on LoadMasters
with firmware version 7.1-16 and above.
When Subnet Originating Requests is enabled, the LoadMaster will route traffic so that the Real
Server will see traffic arriving from the LoadMaster interface that is in that network/subnet not
the Virtual Service address.
When Subnet Originating Requests is enabled globally, it is automatically enabled on all Virtual
Services. If the Subnet Originating Requests option is disabled globally, you can choose whether
or not to enable Subnet Originating Requests on a per-Virtual Service basis.
To enable Subnet Originating Requests globally, follow the steps below:
1. In the main menu of the LoadMaster WUI, go to System Configuration &gt;
Miscellaneous Options &gt; Network Options.
Figure 4-1: Subnet Originating Requests
2. Tick the Subnet Originating Requests check box.
Copyright &copy; 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved.
8
Microsoft Dynamics AX
Configure Microsoft Dynamics Virtual Services
4.2
Microsoft Dynamics AX ERP Portal Virtual Service
The following are the steps involved and the recommended settings to configure the Microsoft
Dynamics HTTPS Virtual Service:
1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual
Services &gt; Add New.
Figure 4-2: Virtual Services Parameters
2.
3.
4.
5.
6.
7.
Enter a valid IP address in the Virtual Address text box.
Enter 443 in the Port text box.
Enter a recognizable Service Name, for example MS Dynamic AX.
Ensure tcp is selected as the Protocol.
Click Add this Virtual Service.
Enter the details shown in the following table:
Section
Option
Value
Standard Options
Transparency
Persistence Mode
Persistence Timeout
Scheduling Method
Idle Connection Timeout
SSL Acceleration
Disabled
Source IP Address
30 Minutes
least connection
660
Enabled
Reencrypt
Supported Protocols
Cipher Set
TLS1.0
TLS1.1
TLS1.2
Best Practices
Content Switching
Disabled
Add HTTP Headers
Legacy Operation
(X-ClientSide)
SSL Properties
Advanced
Properties
Copyright &copy; 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved.
Comment
A wildcard certificate allows
secure connections to be
established with a request
URL in the format of
*.example.com. With this
approach, a single certificate
secures traffic for all clients in
a multi-tenant environment.
For further information on
cipher sets, please refer to
the SSL Accelerated Services,
Feature Description.
9
Microsoft Dynamics AX
Configure Microsoft Dynamics Virtual Services
Section
Real Servers
Option
Value
Comment
Redirection URL
https://%h%s
Click Add HTTP Redirector.
This option will only appear if
port 80 is free.
Real Server Check Method
Checked Port
Use HTTP/1.1
HTTP/1.1 Host
HTTP Method
HTTPS Protocol
443
Selected
ax.example.com
GET
Table 1: Microsoft Dynamics AX Virtual Service Settings
Users should note that clicking the Add HTTP Redirector button, automatically creates a redirect
Virtual Service on Port 80. This option will only appear if a port HTTP redirect does not already
exist:
8. Add the Real Servers:
a) Click the Add New button.
b) Enter the IP address of the AX Server.
c) Enter 443 as the Port.
The Real Server Port should match the Virtual Service Port.
The Forwarding method and Weight values are set by default. An
administrator can change these.
d) Click Add this Real Server. Click OK to the pop-up message.
e) Repeat steps b) to d) above to add more Real Servers as needed, based on
the environment.
4.3
Microsoft Dynamics AX HTTP (Redirect) Virtual Service
This Virtual Service is automatically created when users click the Add HTTP Redirector button
while configuring the Microsoft Dynamics AX ERP Portal Virtual Service in Section 4.2.
4.4
Microsoft Dynamics AX AOS Virtual Service
The following are the steps involved and the values required to configure the Microsoft
Dynamics AX AOS Virtual Service:
1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual
Services &gt; Add New.
Copyright &copy; 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved.
10
Microsoft Dynamics AX
Configure Microsoft Dynamics Virtual Services
Figure 4-3: Virtual Services Parameters
2.
3.
4.
5.
6.
7.
Section
Option
Standard Options
Real Servers
Enter a valid IP address in the Virtual Address text box.
Enter 2712 in the Port text box.
Enter a recognizable Service Name, for example MS Dynamic AX AOS.
Ensure tcp is selected as the Protocol.
Click Add this Virtual Service.
Enter the details shown in the following table:
Value
Transparency
Deselected
Extra Ports
1433,1812,1814,8101,8201,8202
Persistence Mode
Source IP Address
Persistence Timeout
30 Minutes
Scheduling Method
least connection
Idle Connection Timeout
660
Real Server Check Method
TCP Connection Only
Checked Port
2712
Comment
Click Set Extra Ports
Table 2: MS Dynamics AX AOS Virtual Service Settings
8. Add the Real Servers:
a) Click the Add New button.
b) Enter the IP address of the AX Server.
c) Enter 2712 as the Port.
The Real Server Port should match the Virtual Service Port.
The Forwarding method and Weight values are set by default. An
administrator can change these.
d) Click Add this Real Server. Click OK to the pop-up message.
e) Repeat steps b) to d) above to add more Real Servers as needed, based on
the environment.
Copyright &copy; 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved.
11
Microsoft Dynamics AX
References
References
Unless otherwise specified, the following documents can be found at:
http://kemptechnologies.com/documentation.
Virtual Services and Templates, Feature Description.
High Availability (HA), Feature Description
SSL Accelerated Services, Feature Description
Copyright &copy; 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved.
12
Microsoft Dynamics AX
Document History
Document History
Date
July 2016
Change
Reason for Change
Version
Resp.
Initial Draft
First draft of document
1.0
KG
Copyright &copy; 2002 - 2016 KEMP Technologies, Inc. All Rights Reserved.
13
">

Hello! I am an AI chatbot specifically trained to assist you with the KEMP Microsoft Dynamics AX Deployment Guide. I have thoroughly reviewed the document and can help you locate the exact information you need or explain the content in clear and simple terms. Whether you’re looking for guidance on specific features, troubleshooting steps, or general usage, feel free to ask your questions. The more details you provide about your concerns or needs, the more accurately and effectively I can assist you!

Show related prompts

Assistant typing

Assistant is out of keyboard. Please, try again later.

Key features

Load balancing
High Availability
Subnet Originating Requests
Virtual services
Adaptive Load Balancing

Frequently asked questions

This document provides guidance on how to deploy Microsoft Dynamics AX with a KEMP LoadMaster.

The KEMP LoadMaster is a high-performance load balancer that provides a reliable and cost-effective solution for balancing requests across Microsoft Dynamics AX.

High Availability (HA) provides redundancy and resiliency, meaning if one LoadMaster goes down for any reason, the hot standby can become active, therefore avoiding any downtime.

In the main menu of the LoadMaster WUI, go to System Configuration > Miscellaneous Options > Network Options. Tick the Subnet Originating Requests check box.

A Virtual Service is a logical representation of a service that is accessed by clients. In this document, Virtual Services will be used to configure the LoadMaster to balance requests across the Microsoft Dynamics AX servers.