Windows 8 and the Microsoft Dynamics GP Web Client Series - Part 2a

Windows 8 and the Microsoft Dynamics GP Web Client Series
Part 2a

This series narrate my personal experiences of installing Microsoft Dynamics GP 2013 Beta and the Web Client in an unsupported environment. The following installation steps are for testing purposes only and were done on a test box. If you are to test, please make sure your machine is not a production box.

"While it's not supported, it doesn't mean it won't work. It only means we haven't tested it"...
                                                                                                      Microsoft Dynamics GP Support
Yesterday, we walked through a few pre-requisites needed for the installation of the Microsoft Dynamics GP 2013 Web client on single Windows 8 machine - from now on, the road warrior laptop. It is worth noting that I also made some of the Silverlight registry changes to allow the Web Client to access local resources (printers, SmartLists, and access to temp folders) from within the browser. You can read more about these changes and download the registry entry for Silverlight in Aaron Donat's new article over at Developing for Dynamics GP.

Microsoft Dynamics GP Web Client and Silverlight Security Requirements

Today, I will cover some of the issues I experienced through attempts at running the Web Client without having ASP.NET 4.5 running on IIS 8.0 - as mentioned before, at first, it was not quite obvious ASP.NET 4.5 was not installed on IIS.8

Installing Microsoft Dynamics GP 2013

Prior to installing the Web Client, the installation process takes us through Microsoft Dynamics GP 2013 and the Web Client Runtime service installation.

The main setup window (launched with Setup.exe) allows you to install Microsoft Dynamics GP 2013, along with some of the traditional products, plus the Web Client, Tenant Services, and the Web Services Management Tools, three new components for GP 2013.


You can find more information about the Web Client architecture in Aaron Donat's article over at Developing for Dynamics GP:

Dynamics GP 2013 Web Client Infrastructure Overview

The first things you will notice during the installation process is the Bootstrapper Setup window, which will automatically install Dexterity Shared Components 12.0.


Bootstrapper Setup window
At the features level, you will have a choice of installing the Web Client Runtime service. This feature is a MUST prior to installing the Web Client itself. More information about the Web Client Runtime can be found in Aaron's infrastructure article above.

Select Features window.

New for GP 2013 is the ability to name the system database. For those of us "old timers", you also have a choice of continuing to use the DYNAMICS system database name as a default choice. For more information on the named system database feature, take a look at my article Microsoft Dynamics GP "12" Named System Database Architecture.

Named System Database
Once the application is installed, you should now be able to return to the Windows 8 start screen and see the launch icons there.


A peek into the Microsoft Dynamics GP 2013 installation folder, confirms we now have a WebClient folder with all the assemblies, extensions, and providers that in conjunction form the Web Client Runtime service.

Web Client Runtime files
Following this first part, the rest is just running Microsoft Dynamics GP Utilities and let the program take care of creating the system database and adding the Fabrikam company. Practically nothing has changed in the Utilities process.

Next, I will cover the Web Client installation.
Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.IntellPartners.com/

Comments

Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more