In a recent integration project I was working on, we encountered some performance issues regarding the use of the Microsoft Dynamics .net Business connector for Microsoft Dynamics AX 2009. The problem was related to an AIF created WCF service hosted in an IIS environment. The WCF service was supposed to handle many simultanously request but analyzis showed that even when eg. 100 simultanous requests was made at the same time, only a maximum of two business connectors showed up in the “online users” in AX.
To understand what was going on, a support case at Microsoft was created and below, I will summaraixe some of the information Microsft provided:
If you too are wondering why only two connections shows up in the “online users” in AX please refer to Microsofts support blog at http://blogs.msdn.com/b/emeadaxsupport/archive/2009/05/14/the-thing-about-the-net-business-connector-and-the-number-of-online-users.aspx
You should also be aware of the license information provided by Microsoft:
“License consumption for Business Connector in AX 2009
Using Business Connector from a non web based external application.
When BC (.NET Business Connector) is used in Dynamics Ax 2009, 2 sessions are created. One of them is called “Worker”, and this is the main BC session (process start). Every time there is Login call from BC a new session is created which is called “Business Connector”.
When the LogOff is called the “Business Connector” session is removed. When the BC process itself terminates then the “Worker” session is removed.
If you start a process and then login multiple times in parallel without logging off you will see 1 “Worker” session and multiple “Business Connector” sessions.
E.g. if same user logs on e.g. two times within the same process then you will have three sessions in Online Users form, 1 “Worker” and 2 “Business Connector”.
For .NET Business Connector, there is no “Business Connector Users” license enforcement done at the product level.
The customer is responsible for licensing the number of BC.net’s that they use (even though we do not enforce the license). The license agreement is a legal contract.
So from a licensing point of view:
You need “Business Connector Users” license, one for each concurrent logon by a distinct user.
Using Business Connector from a web based application (e.g. Enterprise Portal).
For EP or any Web used apps which uses LogonAs, there will be one session called “Business Connector” which will be the main session (one BC worker process connection for every worker process). This will be a persistent connection as long as the process is started & live and at least one EP page is served.
EP pages are stateless, so the web user connection is not persistent. For every page request the web user connection will be established (and a “Web user” session will be shown in “Online users” and in SysClientSessions the field Status = 1), page will be rendered and after a small time (for performance reasons), the connection will be teared off (in SysClientSessions the field Status = 0).
For EP, there is no “Enterprise Portal Users” license enforcement done at the product level.
The customer is responsible for licensing the number of BC.net’s and Web users that they use (even though we do not enforce the license). The license agreement is a legal contract.
So from a licensing point of view:
1. You need “Business Connector Users” license, one for each web server and
2. “Enterprise Portal users” (Web user) license – either concurrent user license or named user license.
Do Microsoft enforce the licenses and if so how?
With enforced license it means that you will not be able to log in if you exceed the number of logged in users.
The answer is that all licenses are enforced except for “Enterprise Portal Users” and “Business Connector Users”.
This means that if you don’t have license for a module/feature then you will not be able to use the module/feature and for normal users (Win clients) you will not be able to log inn more than the number of concurrent users that you have license for.
E.g. If you have license for 2 COM clients and you have 3 web servers and you try to log in the business connector(BC) from the third web server then the BC will not be able to log in.
For Web users there is no enforcement which means that you will be able to have more users logged in to EP than you have web user license for.”
Thanks goes to Microsofts support team that helped solving this issue.