With the newly announced release of Microsoft Dynamics 2013 Beta to all partners, what better time to begin talking about the Dynamics GP Web Client since there is HUGE excitement around this feature. With the "BUZZ" floating around the Fargo campus this week, now is the time to start sharing the foundation of what GP Web Client really is, what are those required and deployed components and how does this product actually function. Over the next few posts, I will be covering these dependencies attempting to get you to started thinking about the GP Web Client as much as you think about Dynamics GP today. We all realize that in order to have a successful deployments, the single most important component in any deployment is the pre-planning and coordination effort. We want to help you in that planning and coordination and will do the best we can through documentation and videos. With that said, everyone's focus right now is getting the GP Web Client up running in your environment and begin understanding the requirements so you can position and sell it to our customers.
In this blog, I want to spend time talking about the components that comprise a GP Web Client deployment. Understanding the components of the Web Client will be key in your planning and troubleshooting efforts. There are 9 specific components involved with getting the GP Web Client to function. Out of those 9 components, I would like to call out 4 components that I consider KEY and are troubleshooting components. This four components are:
- Session Central Service
- Session Host
- Session Service
- Runtime Service
Below is the architecture design flow of how these components are connected with each other.
IIS/GP Web - This is the Internet Information Services website that will serve up the GP Web aspx pages and the GP Web Silverlight application. This will be the entry point for users interacting with GP Web by processing their logon information, show existing sessions, create a new session, recover an existing session, and ultimately launch the GP Web Silverlight application. The virtual directory is named GP. Other facts about this component:
- Must be deployed under a Web Site that has been enabled for SSL
- Contains 5 .aspx pages:
Logon.aspx - This is the primary login page for GP Web Client
Session.aspx - This is the page that displays existing session for the user. It allows the user to re-connect to an active session that they had disconnected from.
GPWeb.aspx - This is the page in which the Silverlight application runs in
Errors.aspx - This is the page that displays any exception that occurs within the Web Site code
Default.aspx - This is a hidden page that is used for re-direction back to the Login.aspx or Session.aspx pages
The relationship between these .aspx file is displayed below. What makes this Web Application different than others, is that there is very little interaction with IIS itself. Other than processing user login information or presenting session information back to the users, the Silverlight application has no interaction with the GP Web virtual directory.
IIS/GP Web Management - This is the Internet Information Services website that will serve up the GP Web Management Console virtual directory and run two Silverlight applications.…