What is the base architecture for new 3 tier system

themave

Ok, as an end user what is going to be the base systems I need to run the new 3 tier architecture. Say a minimum setup needed.

A machine for SQL Server 2005
A machine for the Application server
A machine of (what else)
What other base machines are needed.

I understand depending on number of users ect, you will need to scale up.

kine

1) DB Server (MS SQL 2005) - data storage
2) Service tier server (one or more, running IIS with mid-tier) - data processing
3) Client workstations or terminal server - running "Rich client" - data presentation
4) Optionally - Sharepoint server for Sharepoint client

Marije_Brummel

AFAK the servicetier will run on WCF (Windows Communication Foundation).

ara3n

Yes there was a post in here from MS that it's based on WCF.
Will it still run on IIS? or will it be separate service?

Marije_Brummel

I was very supprised that Darren posted that since I thought it was not public yet.

The story I know is that WCF gave better performance than IIS so they went that way instead of IIS.

I'll send Darren an email with a link to this post.

Waldo

As Darren said 'because of the possibility to use the WCF protocols'

Anyway, this is the link:
http://www.mibuso.com/forum/viewtopic.php?t=19597&start=15

ara3n

Well having a separate service will make the installation a lot easier. I'm guessing that's why they could install it in demo in 45 sec.

kine

Ok, it looks like good news for me... but what I know about WCF is nearly ''.

claband

I can clarify the confusion around IIS and WCF. The Navision Server will not be hosted in IIS but as a Windows Service. As will Business Web Services. The services are built on WCF which in part is done from a performance perspective but also for simplicity

/Claus

claband

Adding to that there is no requirement for IIS from NAV.

Marije_Brummel

Thanks Claus!

Alex_Chow

Should there be a disclaimer saying that it's "subject to change without prior notice"?

NavStudent

Alex Chow wrote:

Should there be a disclaimer saying that it's "subject to change without prior notice"?

Are you going to sue him?

Jokes aside.


Moving from away from IIS to WCF must be the reason for the delay.
But I'm sure there were 100 other reasons as well.