- The decision to go for Windows Server 2008 x64 Standard was right
- The decision to go for SQL Server 2005 Sp2 x64 Standard in a active-passive failover cluster was probably right, except for some breaks in the database communication (exact reason still unknown)
- AIF performs better than expected even without utilizing paralell processing on several AOS instances (2 000 messages can easily be processed in a couple of minutes utilizing one uni directional channel)
- The BizTalk Adapter haven't caused us any spesific issues so far
- Pay extra attention when submitting batch jobs to the batch queue (or when constructing new batch jobs) and don't expect all logic to execute automatically under the new Batch Framework (look out for logic tied to the client tier even in the standard application and plan for adding some extra logic to keep the code compatible in both interactive and batch mode)
- Look out for hot fixes from Microsoft (check Partnersource or Customersource freqently) and plan for some delays getting a response (new installations should evaluate the roll up package released late in February)
Bottom line; the Batch Framework is worth paying special attention to during analysis, design, build and testing.
Posts
6 comments:
Hi there,
Have you used Win 2008 standard for both SQL server and AOS?
Hi,
Yes, Windows Server 2008 x64 Standard for both SQL nodes and AOS servers. No issues at this level, but you should make sure 3.party backup agents etc. are updated and certified on W2K08 Server. x64 is my preferred platform mainly because stability and scale up possibilities.
You have mentioned SQL nodes - do you run a cluster or what type of fail over setup you have?
Both for SQL database and AOS?
I guess my question is what is your disaster recovery setup?
Hi,
Yes, the database tier consists of 2 nodes in an active/passive configuration (active/active is not supported for AX 2009) in a failover cluster. The solution is hosted. In addition 2 stand alone (not load balanced) AOS servers. The customer can easily run 2 instances on either server in case of failure on one of the AOS servers and the reason for having 2 AOS is distribution of load (user load on one and integration load on the other).
In this configuration do you have any remote users? If yes what technology do you use: Citrix, RDC? My implementation will have 60 remote users. I am looking in to win 2008 RDC
Hi again,
All users are remote since the solution is hosted. Pure WTS (Windows Terminal Services) and RDP (Remote Desktop Protocol). Windows Server 2008 will do fine based on my experience. Main benefits are central deployment of the AX client and you will also have a more reliable client connection able to handle high latency connections (remember that the AX client protocol RPC is quite latency dependent). WTS with or without Citrix. 60 users will probably present you with a decision around the number of servers required and platform (x32/x64).
Post a Comment