Note: This article is meant for use by *system administrators* wanting to implement the Jet Remote Data Service (JRDS) data source available in Jet Reports (versions 2015 Update 1 and higher) for connecting to their Dynamics GP data.
If you are a Jet *user* and want to configure the Jet Excel add-in to use an existing Jet Remote Data Service data source for Dynamics GP, see the GP JRDS User Guide and contact your system administrator for details.
What is the Jet Remote Data Service?
The Jet Remote Data Service (JRDS) data source presents a three-tier architectural design with a service component that is hosted within Internet Information Services (IIS). It provides a fast, secure connection method for environments where Jet users have Excel installed locally and their Dynamics GP system is hosted on a different domain .
A brief clarification of terms:
| "Jet Remote Data Service (JRDS)"
This refers specifically to the service component of the new data source
| "JRDS Data Source"
This refers to the complete three-tier architectural components of the new data source.
Host Server requirements:
- Dynamics GP 2013 or later
- SQL Server and its corresponding SQL Server client must be installed
- Internet Information Services (IIS) with an SSL/TLS certificate
- PowerShell 4.0 (or higher)
- The name of the host server must be exposed through DNS if users will access it via a URL.
- The service must have access to a SQL account or Windows Login which has ‘read’ access GP's SQL database.
Note: The recommended best practice is to set up a single new user account with read access to the database. Then, use the Jet Administration Console to create a data source using the credentials for this new account, and share that data source with any Jet users who will need to use the data source. In this way, Jet users have access to the data without having to know the credentials associated with the new user account.
End user (client) requirements
- Jet Reports (or Jet Express) 2015 Update 1 or higher
To connect to their service end users will need to know
- The URL or IP address of the Host Server
- The Port configured for use with the JRDS
- The Instance Name of the Service Instance
- Their GP username, domain and password
The Jet Remote Data Service
The JRDS consists of an Application Container and one or more Service Instances.
In multi-tenant environments, each hosting client must have a distinct service instance with its own data source settings. This ensures that no hosting client can access data from another hosting client.
The Application Container
|The Application Container is the term used to refer to the IIS website that will host the Service Instance(s). The Application Container is associated with a port during installation.|
|The Application Container must include one or more Service Instances. Each Service Instance must be uniquely named and provides access to a single GP data source.
In a multi-tenant environment all clients may connect to their data via the same port, but each client will connect to their own service instance.
The Jet Remote Data Service Administration Shell
The Jet Remote Data Service is installed and configured using the Jet Remote Data Service Administration Shell , which is a PowerShell management module.
|The MSI file can be used (with the Windows Installer for other installation tool) to install the Administration Shell into a “Jet Remote Data Service” directory in the appropriate “Program Files” directory.
Along with the Administration Shell, the MSI also installs the service assemblies and a shortcut in the Start Menu (to access the administration shell).
Click DOWNLOAD to download a zip file containing both the 32-bit and 64-bit installer:
The bit-level you install should match the bit-level of the version of the operating system (usually 64-bit for recent versions of Windows Server)
There are two ways to initialize the management module. The first is to use the shortcut called “Jet Remote Data Service Administration Shell”. This must be run as administrator and will open an instance of Powershell as shown below in Figure 3.
Alternatively, the initialization script (JetRemoteDataServiceAdministrativeShell.ps1) can be found in the Management folder of the install directory and run manually via the PowerShell prompt running as administrator .
Installing a Jet Remote Data Service
The Jet Remote Data Service Administration Shell provides a set of PowerShell cmdlets which are used to create, configure and remove Application Container and Service Instances. Each of the available cmdlets and their common uses are listed below.
This command creates the Application Container and must be called prior to calling other Jet cmdlets.
The parameter ‘-Port’ is required, which indicates the port that will be used for the website address binding.
This command must be called prior to calling New-JetGPRemoteDataServiceInstance
New-JetRemoteDataService -Port 443
Note - this port will need to have an inbound Windows firewall rule in place. Jet Reports recommends that port 443 be used.
This creates a new, empty website in IIS that is named “Jet Remote Data Service Container” which serves as the container for service instances of the JRDS.
|Parameter||Description||Type of Value||Example Value or Description|
|-Port||The port to be used by the Jet Remote Data Service||Numeric||443|
The command does support other parameters, For additional details, you can use the PowerShell "get-help" cmdlet
Jet cmdlets also support the common parameters: Verbose, Debug, ErrorAction, ErrorVariable, WarningAction, WarningVariable, OutBuffer, and OutVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216)
This command creates a GP service instance of the JRDS.
This command can be used multiple times to create multiple Service Instances. The New-JetRemoteDataService command must be called prior to running this command.
New-JetGPRemoteDataServiceInstance -InstanceName "Customer" –Server “Jet-Test” -WindowsAuthenticationType $false -UserID "JETSA" -Password "m!saP@$$w0rd!"
When a new service instance is created:
- An instance directory is created in the IIS website root directory that contains a symbolic link to the installed service assemblies and a “Web.config” file. This new directory is loaded into the Application Container as a virtual directory whose path is the name of the instance, and within that virtual directory the symbolic link is loaded as an application.
- The instance application will be given its own Application Pool within IIS. This results in an instance-specific IIS process being created for each service hosted in the Application Container.
(A virtual directory in the Application Container is mapped to a distinct instance directory and the link to the service assemblies is located as an application)
The figure above shows a virtual directory inside of the Application Container and the location of the actual directory in the file system. Within that instance directory a symbolic link is pointing to the location of the service assemblies, which in this example is the default installation directory.
These parameters can be used with the New-JetGPRemoteDataServiceInstance or the Set-JetGPRemoteDataServiceInstance commands:
|Parameter||Description||Type of Value||Example Values or Description|
|-InstanceName||The name of the new Service Instance||Text||"Customer"|
|-DynamicsDB||The DYNAMICS database name||Text||"XYZ-DYNAMICS"|
|-WindowsAuthentication||A value indicating whether to use Windows Authentication for connecting to the Dynamics DB database||Boolean||
The UserID used to authenticate with the specified DynamicsDB database
This UserID must have read permissions to the GP SQL database
|-Password||The password used to authenticate the UserID with the DynamicsDB||Text||"PaSSw0rd"|
|-Server||The SQL server on which the DynamicsDB database resides||Text||"Jet-Test"|
(parameters in RED are required)
If WindowsAuthentication is set to $false then the credentials specified for UserID and Password will be used when the JRDS service connects to the DynamicsDB database. The credentials specified on the Jet Data Source settings will be used for authenticating the client with the JRDS.
If WindowsAuthentication is set to $true then the credentials specified in the Jet Data Source settings will be used for authenticating both the client with the JRDS, as well as the JRDS with the DynamicsDB.
- All switches are proceeded by a dash ( - )
- There is no space between the dash and the switch name
- There is always a space between the switch and its value
- For boolean (True/False) switches, the value is in lowercase and preceded by the dollar symbol ( $ )
- Text (alpha-numeric) values are enclosed within double quote marks
- Numeric values have no special formatting
This command is used to modify the data source settings of an existing Service Instance. The only required parameter is ‘-InstanceName’ which indicates the instance of the service whose settings are to be configured. In this example, the setting ‘-DynamicsDB’ is modified:
Set-JetGPRemoteDataServiceInstance -InstanceName "Customer" -DynamicsDB "XYZ-Dynamics"
Parameters Supported: See the list for the New-JetGPRemoteDataServiceInstance cmdlet
This command is used to remove an instance of the JRDS. The only required parameter is ‘-InstanceName’ which indicates the instance to remove from the Application Container.
Remove-JetRemoteDataServiceInstance -InstanceName "Customer"
This command is used to remove the Application Container. No parameters are necessary.
Configuring User and Group Access
By default, all users are authorized to access the JRDS.
The full set of allowed and denied users can be viewed with the Get-JetRemoteDataServiceInstance command and noting the values shown for Authorized Users, Authorized Groups, Denied Users, and Denied Groups.
For details about how to configure JRDS access for specific users and/or groups, see the article Configuring user and group access to the JRDS
End-to-end Configuration of the Jet Remote Data Service
Using the tools discussed above, we’ll now look at a step-by-step walkthrough of setting up the Jet Remote Data Service and a data source connection to it in Jet Reports.
An important distinction to remember is the difference between
- The JRDS instance configuration to the database, and
- The configuration in Jet to connect to the JRDS
Individuals in charge of configuring the JRDS in IIS will need to configure the JRDS instance's connection to the database.
Jet users will then need to configure their connection to the JRDS
Creating and configuring an instance of the JRDS
Hosting providers will need to configure the following items.
Here is an example of creating a new service instance for a customer named “Customer” using port 443 on a server named “Jet-Test”:
Important Manual Step
There is a manual step when creating the Application Container which must only be done once.
When the Application Container is created, no SSL/TLS certificate is configured for it. In order to complete this step, IIS Manager must be opened and the binding on the site entitled “Jet Remote Data Service Container” must be configured to use an SSL/TLS certificate, as shown below
(configuring the SSL/TLS certificate for use with the Application Container)
Configuring the data source connection in the Jet Excel add-in
The first step in the Jet Excel add-in is to create a new data source of the type “Dynamics GP" with a connection type of "Remote Data Service”. Next, the authentication needs to be configured. The user can authenticate against the JRDS using specified Windows credentials.
It is expected that users will be given a username, domain, and password to use for authentication.
Finally, the connection information for the instance of the JRDS must be configured:
Note that the server is the one which is hosting IIS and the JRDS, the port is the one which was entered into PowerShell when creating the Application Container, and the instance is the name entered into PowerShell when creating the service instance.
The dropdown to select the company will populate when opened if the settings are correct.