Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Microsoft Dynamics NAV three-tier multithreaded architecture
alok_dida
Member Posts: 73
Guys .. I know it's very basic question and I have an idea about it but still I have a doubt regarding this so I am asking here this question. Correct me if I am wrong and sorry for this.
As Microsoft Dynamics NAV is following three-tier multithreaded architecture model. As per my knowledge in 3-tier architecture Presentation Layer (in our case RTC) is not directly connected to Database. First It will connect to Business layer (in our case NAV Server) and than Business layer will communicate with Database.
Now as per my requirement I have to install Database, NAV Server and NAV Client (RTC) on different system. I am done with it successfully also.
But I have a question for you.
1)First I have installed Database on "Server1".
2)Then I have installed NAV Server on "Server2" with specifying parameters for DatabaseServer Name , Database Server Instance and Database Name.I am able to start service on Server2.
3)Now I am installing RTC on my system "System3" . I am able to install it Successfully. Now I have to connect to the Server2 service so I am changing my CustomSettings file with adding one tag ServerName and rest of all parameters(DatabaseServer Name , Database Server Instance and Database Name). I am able to implement all this things successfully.RTC successfully connected to the Database.
Now my question is why do we have to specify parameters (DatabaseServer Name , Database Server Instance and Database Name) on client system( "System3") because we already specify it at Service level? One thing is obvious in RTC we always need a Service to connect to Database and in Service we already specify parameters so why do we need all this parameters at Client level?
For my sanctification I tried to remove that parameters but it's not allow me too Start service on my system.
Can anybody tell me why it's happening ? Is it violate the three-tier multithreaded architecture definition?
As Microsoft Dynamics NAV is following three-tier multithreaded architecture model. As per my knowledge in 3-tier architecture Presentation Layer (in our case RTC) is not directly connected to Database. First It will connect to Business layer (in our case NAV Server) and than Business layer will communicate with Database.
Now as per my requirement I have to install Database, NAV Server and NAV Client (RTC) on different system. I am done with it successfully also.
But I have a question for you.
1)First I have installed Database on "Server1".
2)Then I have installed NAV Server on "Server2" with specifying parameters for DatabaseServer Name , Database Server Instance and Database Name.I am able to start service on Server2.
3)Now I am installing RTC on my system "System3" . I am able to install it Successfully. Now I have to connect to the Server2 service so I am changing my CustomSettings file with adding one tag ServerName and rest of all parameters(DatabaseServer Name , Database Server Instance and Database Name). I am able to implement all this things successfully.RTC successfully connected to the Database.
Now my question is why do we have to specify parameters (DatabaseServer Name , Database Server Instance and Database Name) on client system( "System3") because we already specify it at Service level? One thing is obvious in RTC we always need a Service to connect to Database and in Service we already specify parameters so why do we need all this parameters at Client level?
For my sanctification I tried to remove that parameters but it's not allow me too Start service on my system.
Can anybody tell me why it's happening ? Is it violate the three-tier multithreaded architecture definition?
0
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
I am a little confused, as you talk about items not needed in the client configuration file - but it is the service that you cannot successfully start.
The database name should only be necessary in the service configuration file - and not in the client configuration file. And if the database name is not in the service configuration file, then the service (on the middle tier) will not start.
Jens Møller-Pedersen [MSFT]
This posting is provided 'AS IS' with no warranties, and confers no rights.