Ts Install Admin Guide
Ts Install Admin Guide
Limitation of liability This document is provided “as-is”. Information and views expressed in this document, including
URL and other Internet Web site references, may change without notice. You bear the risk of
using it.
Some examples depicted herein are provided for illustration only and are fictitious. No real
association or connection is intended or should be inferred.
Intellectual property This document does not provide you with any legal rights to any intellectual property in any
Microsoft product.
You may copy and use this document for your internal, reference purposes.
Trademarks Microsoft, Microsoft Dynamics, Visual Basic, Visual Studio, BizTalk Server, Windows, Windows
Vista, and Windows Server are trademarks of the Microsoft group of companies.
Warranty disclaimer Microsoft Corporation disclaims any warranty regarding the sample code contained in this
documentation, including the warranties of merchantability and fitness for a particular purpose.
License agreement Use of this product is covered by a license agreement provided with the software product. If you
have any questions, please call the Microsoft Dynamics GP Customer Assistance Department at
800-456-0025 (in the U.S. or Canada) or +1-701-281-6500.
ii T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C O N T E N T S
Symbol Description
The light bulb symbol indicates helpful tips, shortcuts,
and suggestions.
Margin notes summarize Margin notes call attention to critical information and
important information. direct you to other areas of the documentation where
a topic is explained.
Convention Description
Part 1, Multitenant Basics Bold type indicates a part name.
Chapter 1, “Overview” Quotation marks indicate a chapter name.
Installing tenant services Italicized type indicates a section name.
using System.IO; This font is used to indicate script examples.
Microsoft Message Acronyms are spelled out the first time they’re used.
Queuing (MSMQ)
TAB or ALT+M Small capital letters indicate a key or a key sequence.
2 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
IN T RO D U C T IO N
Product support
Microsoft Dynamics GP technical support can be accessed online or by telephone.
Go to www.microsoft.com/Dynamics and click the CustomerSource or
PartnerSource link, or call 888-477-7877 (in the US and Canada) or 701-281-0555.
6 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
Chapter 1: Tenant Services Overview
Microsoft Dynamics GP Tenant Services are Windows Communication Foundation
(WCF) services that help you to host Microsoft Dynamics GP for more than one
organization in your data center. The following topics introduce Microsoft
Dynamics GP Tenant Services:
You install Tenant Services when you want your data center to host Microsoft
Dynamics GP for more than one organization. Each organization is called a tenant.
Hosting multiple tenants enables several organizations to share servers and other
resources.
Tenant Services helps you to isolate the data and configuration information for each
tenant. As a result, a user is not aware that there are other users from other
organizations that are also working with Microsoft Dynamics GP in a shared data
center.
For example, a user views data and performs operations using the Microsoft
Dynamics GP web client. The user is unaware that people from other organizations
are also using the shared web client infrastructure to work with other tenants.
Getting started
How you start depends on your role:
System administrator
If you are the system administrator, complete the following:
• Review Chapter 10, “Maintenance,” to learn what you can do to change, repair,
or remove an existing Tenant Services installation.
Software Developer
If you are a developer and you want to create a multitenant application, complete
the following:
• Determine which Tenant Service endpoint you want your application to target.
To get tenant information, you can use the Tenant Discovery Service or the
Tenant Public Discovery Service.
If your application will run on a different network than where you installed
Tenant Services, you have to use the Tenant Public Discovery Service.
If your application will run on the same network where you installed Tenant
Services, you can use the Tenant Discovery Service. Applications that run on
the same network can also use the Tenant Management Service.
8 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 1 T E N A N T S E R V I C ES O V E R V I E W
• Discuss the installation procedure with the system administrator to learn what
security and port settings were used during the Tenant Services installation. If
you plan to use the Tenant Public Discovery Service, verify that the service was
installed.
• You first install Tenant Services. Tenant Services are WCF services that enable
Microsoft Dynamics GP multitenant applications to logically isolate data and
configuration information for each tenant.
• You install Microsoft Dynamics GP for each tenant organization. When you
install Microsoft Dynamics GP you have to specify a separate, named system
data base for each tenant organization.
• You install the Tenant Manager snap-in and the Web Management Console.
You use the Tenant Manager to add and configure tenants and multitenant
applications. The Tenant Manager uses Tenant Services to perform operations
on tenants, applications, and users.
The following sections describe the key structural concepts in a Microsoft Dynamics
GP multitenant environment.
Tenant
A tenant is an organization that can use a multitenant application to access
Microsoft Dynamics GP. You use the Tenant Manager snap-in to create tenants. Each
tenant has a unique name. For more information about how to add a tenant, see To
add a tenant.
You assign a multitenant application to a tenant. You also assign a tenant user to a
tenant. The tenant users assigned to a tenant can use all the multitenant applications
for that tenant.
Application
A multitenant application is a client that connects to a shared service. You use a
multitenant application to perform operations that use Microsoft Dynamics GP data
for a specified tenant. The install includes the following multitenant applications:
You first have to use the Tenant Manager snap-in to add the application to your
multitenant environment. You then use Tenant Manager to assign the application to
the tenant.
After you assign an application to a tenant, you use the Tenant Manager to populate
the application properties. The application properties enable you to configure the
service for the specified tenant. For example, you use application properties to
specify how to connect the web client to Microsoft Dynamics GP. For more
information about how to add and configure applications, see Chapter 8,
“Configuring Applications.”.
User
A user is a person that can perform operations with tenants and multitenant
applications. There are two types of users:
• Service administrators
• Tenant users
Service Description
administrator type
Delegating user The log on identity for the service that the multitenant application
uses. For example, the login for the application pool for the
Dynamics GP Web Client must be a delegating user.
The delegating user enables the service to work on behalf of the
logged in user. For example, access to a Tenant Services operation
is based on the credentials of the logged in user and not the service
identity.
You cannot use the same login for both a delegating user and a
service administrator. A delegating user should not be assigned to a
tenant. You can have more than one delegating user.
Service administrator A user that can add, update, or remove tenants, tenant users,
multitenant applications, and service administrators. To add a
service administrator, you have to add the login ID of the person to
the Users list in Tenant Manager.
A service administrator should not be assigned to a tenant. You can
have more than one service administrator. You cannot use the same
login for both a delegating user and a service administrator.
12 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 2 T E N AN T S ER V IC E S AR C HI TE C T U R E
For more information about users, see To add users for service administrators and To
add a tenant user for tenant users.
Client
SSL
Tenant Services
Server
Multitenant
service Tenant Tenant Tenant
Management Discovery Public
Service Service Discovery
Service
SQL
Server
GP DYNGPDISCOVERY
To start a multitenant application, you have to login to the client with the
credentials of a tenant user. You must also have permissions to access Microsoft
Dynamics GP data. The multitenant service uses the Tenant Discovery Service to
determine whether your login ID is a tenant user. If you are not a tenant user, access
to the multitenant service is denied.
If your login is a tenant user, the multitenant application needs to identify the
tenant you want to work with. To help specify the tenant, you see the following
behaviors:
• If your login is associated with a single tenant, you are logged in to that tenant.
You do not need to perform any additional action.
• If your login is associated with more than one tenant, you can get a list of
available tenants. You can then choose the tenant that you want to log in to.
After you choose the tenant, the multitenant service gets configuration information
that enables the service to work with Microsoft Dynamics GP data for the specified
tenant. You can now use the client to perform operations for the specified tenant.
Tenant Services
Microsoft Dynamics GP Tenant Services includes three Windows Communication
Foundation (WCF) services. These services enable you to add, view, and update
tenants, users, and multitenant applications. The following table describes the WCF
services.
DYNGPDISCOVERY database
Information about tenants, users, and multitenant applications is stored in a SQL
Server database. The default name for the database is DYNGPDISCOVERY. You
14 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 2 T E N AN T S ER V IC E S AR C HI TE C T U R E
can specify a different name during installation. You can place the Tenant Services
database on the same SQL Server you use for Microsoft Dynamics GP.
To add, update or remove records from the database, you use the Tenant Manager
snap-in and the Web Management Console..
Security
The diagram shows that the client communicates with the multitenant service over
a network. To help secure the information in the messages between the client and
the service, you have to use security certificates and Secure Sockets Layer (SSL). You
use SSL to encrypt the messages.
The Tenant Discovery Service and Tenant Management Service do not require
security certificates and SSL. However, it is recommended that you use SSL with
these services whenever possible.
If you use the Tenant Public Discovery Service, you are required to have a security
certificate and SSL. You use the Tenant Public Discovery Service when your
multitenant application is on a different network than where you installed tenant
services.
To get information from any of the Tenant Services, you must provide an
authenticated Windows login. Your login ID is used to determine what tenants and
services you can access.
Client
SSL SSL
SQL Server
DYNGPDISCOVERY GP
To begin, you use a web browser to start the Dynamics GP web client. The browser
contacts the GP web site on your IIS web server. You are prompted to enter your
login credentials and click Sign In. The service behind the GP web site queries the
Tenant Discovery Service to determine whether your login credentials are
authorized to use the web client. The service is called the Session Central Service.
The Session Central Service then determines whether you were previously using
the web client. If an existing web client session is found, you can choose to
reconnect.
If you choose to start a new web client, the Session Central Service uses the Tenant
Discovery Service to get the list of tenants that you can access. The list is retrieved
from the DYNGPDISCOVERY database. You then have to specify the tenant you
want to use:
• If the query returns one tenant, the web client defaults to use that tenant.
• If the query returns more than one tenant, you will see a list of tenants in the
browser. You click the tenant name, and then click Create New Session.
After you choose the tenant, the Session Central Service uses the Tenant Discovery
Service to get web client configuration information for that tenant. The
configuration information includes how to connect to Microsoft Dynamics GP for
the tenant. The Session Central Service uses the configuration information to start
another service called a session runtime process.
The Session Central Service returns the URL for the session runtime process to the
browser. The browser uses that URL to connect to the session runtime process and
the web client appears. For more information about the web client, see the Web
Client Installation and Administration Guide.
In a single tenant environment where Tenant Services are not installed, you will find a file
named TenantConfiguration.xml at the root of the GP web site on the IIS web server. The
file contains default tenant information that is automatically used when you login to the web
client.
16 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 2 T E N AN T S ER V IC E S AR C HI TE C T U R E
The following illustration shows the architecture of the Tenant Manager. Notice
how the Tenant Manager uses Tenant Management Service and Tenant Discovery
Services to get and save information about tenants, multitenant applications, tenant
users, and service administrators in the DYNGPDISCOVERY database.
Internet
Explorer Web
management
console
Tenant
Manager
SSL
IIS
TenantProxy
Service
WCF Services
Tenant Tenant
Management Discovery
Service Service
SQL
Server
DYNGPDISCOVERY
You might also notice that the Tenant Manager uses a service named Tenant Proxy
Service. The Tenant Proxy Service is an intermediate service that helps the
Silverlight Tenant Manager application to use the operations of the WCF Tenant
Services.
• Deployment configurations
• User accounts
• Signed security certificates
Deployment configurations
Which configuration you choose will depend on what types of integration you
need, and the server resources you have available.
Scale-out
A scale-out configuration is a multiserver deployment configuration. Typically, you
use the scale-out configuration to support the Microsoft Dynamics GP Web Client.
To create a multitenant environment, you have to add Tenant Services to the scale-
out configuration.
You use the scale-out configuration when you expect to host more than one
organization and a large number of users. To obtain optimal performance, you
should use the scale-out configuration whenever possible.
The following illustration shows a basic scale-out configuration that you would use
for Microsoft Dynamics GP Web Client. Notice that Tenant Services is installed on a
separate server, and accesses the SQL Server over the local network.
SQL Server
+
Tenant Services data
Microsoft Dynamics GP data
Typically, you install Tenant Services onto a separate server. However, you can put
Tenant Services on any server that can be accessed by the other servers in your
deployment.
In addition, you can install Tenant Services on more than one server. The separate
Tenant Services installs use the same SQL Server database. This would enable you
to load-balance Tenant Services and to provide additional reliability.
Also notice how the scale-out configuration includes a separate IIS server and a
session host server.
• Easier maintenance. You make changes to the tenant services without having to
take your multitenant environment offline.
In multiserver configuration you can use a firewall to shield the tenant services
from outside access. In the web client example, access to the tenant services is
provided by the Session Central Service on the web server.
For additional security you can also have a firewall between the tenant service, the
session host server and the SQL Server. The firewall can provide additional security
by further restricting access to the SQL Server.
Single-server
An alternate configuration adds Tenant services to a single-server deployment. In
this configuration, you install Tenant Services on the same server as Microsoft
Dynamics GP and the SQL Server. The following illustration shows the
configuration for a single server:
IIS Server
SQL Server
+
Microsoft Dynamics GP data
Tenant Services data
+
Tenant Services
Session Central Service
Session Service
Microsoft Dynamics GP
20 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 3 T E N A N T S E R V I C E S P R E P A R A T I O N
User accounts
You will need at least two user accounts during the installation of tenant services.
For the multiple-server installation, you have to use domain accounts. For the
single-server installation, you can use machine accounts. Ideally, these user
accounts should have limited privileges, and a password that does not expire.
Create the user accounts before you start installing the Microsoft Dynamics GP
Tenant Services. You must have user accounts for the following:
Tenant Manager
If you install the Microsoft Dynamics GP Web Management Console and the Tenant
Manager snap-in, you have to specify a login ID for the IIS application pool. You
can use the same user account that you use for the service login IDs.
The user account that you specify for the application pool will be added as a
delegating user for Tenant Services. You should not use this login for a service
administrator, tenant administrator, or tenant user.
You cannot use the login of a service administrator as a delegating user. If you try to use the
same login for both, you will not be able to use the Tenant Manager snap-in of the Web
Management Console.
The easiest way to implement SSL for Tenant Services is to get a signed security
certificate. To get a signed security certificate, you purchase it from a third-party
supplier. When you use a third-party signed security certificate the third-party
handles the certificate validation when users connect to the site. No additional
action is needed by the users.
The following sections describe the types of signed security certificates that you can
use.
• GPTenantServices.contoso.com
You would typically use this type of certificate when installing your multitenant
environment in a single machine configuration. This is the least expensive type of
certificate to purchase.
Multiple domain
This type of security certificate is issued for a set of specific machines. You must
know the machine names at the time that you purchase the security certificate. For
example, you could get a security certificate issued that you use with the following
machine names:
• GPTenantServices.contoso.com
• GPweb.contoso.com
• GPServiceHost1.contoso.com
• GPServiceHost2.contoso.com
You would typically use the multiple domain certificate when installing Tenant
Services in a scale-out configuration. The certificate would contain an entry for each
machines that will be part of your configuration. This security certificate is more
expensive because the same certificate can be used on multiple machines.
Wildcard
This type of security certificate is not issued for specific machines. Instead, it is
issued for a specified domain. The security certificates can be used for any machines
that follow the naming convention of the domain. For example, if you purchased a
wildcard certificate for the *.contoso.com domain, any machine in that domain
(such as GPTenantServices.contoso.com) could use the wildcard certificate.
You would typically use the wildcard certificate when installing a multitenant
Microsoft Dynamics GP environment in the scale-out configuration. The wildcard
certificate is especially useful when you expect to add additional machines to the
configuration but do not know the names at the time you are purchasing the
certificate. The extra flexibility does come with a cost. Wildcard certificates are the
most expensive signed certificate.
The certificate must list “Server Authentication” as one of its intended purposes. To view
the intended purpose, use the Certificates snap-in for the Microsoft Management Console
and view the Intended Purpose column.
22 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
PART 2: INSTALLATION
Part 2: Installation
This portion of the documentation explains how to install the Microsoft Dynamics
GP Tenant Services. The following information is discussed:
• Chapter 4, “Prerequisites,” describes the software required and the actions you
must perform before you install the Microsoft Dynamics GP Tenant Services.
24 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
Chapter 4: Prerequisites
Before installing Microsoft Dynamics GP Tenant Services, there are several
prerequisites you must check. This portion of the documentation describes the
software requirements and the additional steps to perform before installing Tenant
Services. The following topics are discussed:
• Operating system
• User accounts
• Security group
• SQL Server
• Security Certificates
• Internet Information Services (IIS)
Operating system
To install Microsoft Dynamics GP Tenant Services, the computer must be running
the 64-bit version of Windows Server 2008 R2 (Standard or Enterprise) or later..
User accounts
You will have to have domain user accounts that you can use during the install.
Before you begin the install, you need to create the following accounts:
In addition, you will use this login when you first open the Web Management
Console. You can then use the Tenant Manager snap-in to add other service
administrator accounts.
You should not use the same account that you use to install Tenant Services.
The log on account for the application pool has to be a delegating user. You
cannot have an account that is both a service administrator and delegating user.
Security group
Security groups are used to specify which users are allowed to access the Microsoft
Dynamics GP Web Management Console. You use the security group to grant your
tenant service administrator access to the Tenant Manager snap-in. You also have to
add tenant administrator accounts to the group.
You can also use a domain group to specify who has access to the Tenant Manager snap-in.
You should add the login IDs of the service user accounts that you created
earlier to the group.
SQL Server
Identify the SQL Server you want Tenant Services to use. Tenant Services stores
information about tenants, users, and multitenant applications in a database. When
you configure Tenant Services, you will specify the SQL Server where you want to
add the database.
You need Microsoft SQL Server 2008 or higher. SQL Server can be on the same
machine where you install Tenant Services or on a separate machine within the
domain. In addition, you can use the same SQL Server that you use for Microsoft
Dynamics GP data.
26 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 4 PR ER EQ U I SIT E S
Security Certificates
Get the security certificates for your servers. The following steps describe how to
determine what security certificates you need and where to place the files.
Component Description
Tenant Services If you will install Tenant Services to a separate machine in a
scale-out configuration, you have to obtain a security
certificate for that machine.
If you will install Tenant Services in a single-server or similar
configuration and you already have a security certificate for
that server, you do not need another.
Web Management If you will install the Web Management Console and the
Console with the Tenant Tenant Manager snap-in on a separate web server, you have to
Manager snap-in obtain a security certificate for that machine.
If you will install the Tenant Manager on the web server you
use for the web client, you do not need another security
certificate.
The Web Management Console requires a web server where you have installed IIS
7.5 or later. If you plan to install the Microsoft DynamicsGP web client, you can also
use that web server to host the Web Management Console.
To install IIS on a Windows Server 2008 R2 machine, complete the following steps:
2. Click Roles.
7. Click Install.
In the Confirm Installation Selections window, click Install. The specified role
and role services are added to the server.
8. Click Close.
After the installation is complete, click Close.
28 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
Chapter 5: Tenant Services Installation
This portion of the documentation describes how to install Microsoft Dynamics GP
Tenant Services. The following information is discussed:
30 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 5 T EN AN T S E R V I C E S I N S T A L L A T IO N
You can also start the install by opening the AdProd folder on the install media,
expand TenantServices, and then double-click TenantServices.
2. Install prerequisites.
If you see a window that prompts you to install prerequisite components, click
Install. If you previously installed Tenant Services, Microsoft Dynamics GP, or
another product, you might not see this window.
Name Description
Tenant Discovery Service Installs the Tenant Discovery Service. The default is to install
this service.
Tenant Management Installs the Tenant Management Service. The default is to
Service install this service.
Tenant Public Discovery Installs the Tenant Public Discovery Service. The public
Service discovery service is optional. The default is to not install this
service.
You install the Tenant Public Discovery Service when you have
multitenant applications other than Microsoft Dynamics GP
that get tenant information from outside your domain.
When you click a button for a feature, a pop-up menu of options appears. Refer
to the following table for information about each option.
To include a feature, click the button and select “Run from My Computer” To
exclude a feature, click the button and select “Not Available”
Setting Description
Port The default port value is 48630. If the port is in use, the next available
port is selected. In addition, you can enter the port number that you
want the service to use.
32 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 5 T EN AN T S E R V I C E S I N S T A L L A T IO N
Setting Description
Certificate Specify a security certificate when you want the connections to the
service to use SSL. A certificate is optional. The default value is Not
Selected. If you do not specify a certificate, SSL will not be used to
encrypt messages to and from the service.
To review information about available certificates, click the certificate in
the drop-down list, and then click the View button. A dialog window
opens that provides detailed information about the certificate.
Host name The fully qualified domain name of the server where you have installed
the security certificate.
Domain Enter the domain name associated with login ID you want to use with
the service.
User name Specify the login name for the service.
Password Enter the password for the specified login ID.
Setting Description
Port The default port value is 48631. If the port is in use, the next available
port is selected. In addition, you can enter the port number that you
want the service to use.
Certificate Specify a certificate when you want the connections to the service to use
SSL. A certificate is optional. The default value is Not Selected. If you do
not specify a certificate, SSL will not be used to encrypt messages to and
from the service.
To review information about available certificates, click the certificate in
the drop-down list, and then click the View button. A dialog window
opens that provides detailed information about the certificate.
Host name The fully qualified domain name of the server where you have installed
the security certificate.
Domain Enter the domain name associated with login ID you want to use with
the service.
User name Specify the login name for the service.
Password Enter the password for the specified login ID.
Setting Description
Port The default port value is 48632. If the port is in use, the next available
port is selected. In addition, you can enter the port number that you
want the service to use.
Certificate If you install the public discovery service, you have to use SSL. SSL
insures that messages to and from the service are encrypted.
Specify the security certificate you want the service to use. If you do not
specify a certificate, you will not be able to proceed with the install.
To review information about available certificates, click the certificate in
the drop-down list, and then click the View button. A dialog window
opens that provides detailed information about the certificate.
Host name The fully qualified domain name of the server where you have installed
the security certificate.
Domain Enter the domain name associated with login ID you want to use with
the service.
User name Specify the login name for the service.
Password Enter the password for the specified login ID.
34 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 5 T EN AN T S E R V I C E S I N S T A L L A T IO N
You use the Tenant Services Config Wizard to specify the database for Tenant
Services. The wizard enables you to specify the Microsoft SQL Server and database
you want to use for the tenant service. To use the wizard, complete the following
steps:
4. Specify the type of authentication you use with the SQL server.
The default uses Windows Trusted Authentication. You can use Windows
Trusted Authentication when your login has permissions to add a database to
the specified SQL server.
If you click to use SQL Authentication, you have to provide the Login ID and
password you want to use to connect to the specified SQL server.
Click Next.
36 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 5 T EN AN T S E R V I C E S I N S T A L L A T IO N
6. Click Exit.
Click Exit to close the wizard. The Tenant Services database is installed and
ready to use.
If you have Workflow for SharePoint 2010 installed on the same system that is running the
Tenant Services, you must install the updated workflow components first.
In the Command Prompt window, change folders to the location where you
found the upgrade install file.
• Server name
• Database name
• Type of authentication
For more information about the wizard, see Configure the Tenant Services
database.
After you upgrade the Tenant Services, you should also upgrade the Tenant
Manager snap-in and the Microsoft Dynamics GP Web Management Console. To
learn more about the Tenant Manager upgrade, see Upgrading an earlier installation
in the Tenant Manager Installation section.
What to do next
After you install and configure Microsoft Dynamics GP Tenant Services, consider
taking the following steps:
• Install or upgrade the Tenant Manager snap-in for the Microsoft Dynamics GP
Web Management Console. You use the Tenant Manager to create, update, and
remove tenants, users, and multitenant applications. For information about
how to install the Tenant Manager snap-in, see Chapter 6, “Tenant Manager
Installation”.
38 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
Chapter 6: Tenant Manager Installation
This portion of the documentation describes how to install the Microsoft Dynamics
GP Web Management Console and the Tenant Manager. You use the Tenant
Manager to view and update tenants, users, and multitenant applications in a
multitenant environment.
You can also add the Tenant Manager to an existing Web Management Console.
You use Add/Remove Features to add the Tenant Manager to the Web
Management Console.
The following information describes how to install the Web Management Console
and the Tenant Manager:
40 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 6 TE N A N T M A N A G E R I N S T A L L A T I O N
If you add Tenant Manager to an existing Web Management Console, do not make
changes that set Session Central, Web Site, Web Client Session Manager, or Session
Server to Not Available. You should leave the existing values.
Specify the install location for the Web Management Console. You can use the
default location or specify another folder. Click Next.
Enter the URL for the discovery and management services. The URL should use
the format of the following URLs.
• https://<servername>:<port>/TenantDiscoveryService
• https://<servername>:<port>/TenantManagementService
To get the URL for the Tenant Discovery Service you can use the
Microsoft.Dynamics.MultitenantService.Discovery.config file. The baseAddress node
contains the URL of the service. The file is found in the c:\Program Files\Microsoft
Dynamics\Tenant Services\DiscoveryService folder on the server where you installed
Tenant Services. To get the URL for the Tenant Management Service, you can use the
Microsoft.Dynamics.MultitenantServices.Management.config file. The file is found in
the c:\Program Files\Microsoft Dynamics\Tenant Services\ManagementService
folder.
42 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 6 TE N A N T M A N A G E R I N S T A L L A T I O N
Enter the domain, name, and password for login identity you want to use for
the application pool. Click Next.
Specify the type of authentication you use with the SQL Server. If the user
installing the Web Management Console has sufficient privileges, you can use
Windows Trusted Authentication. Otherwise, you should use SQL
Authentication and supply a SQL Login ID and Password for a SQL user
account with sufficient privileges. Click Next.
To start the wizard, double click the application. The following window
appears.
2. Specify the type of authentication you use with the SQL server.
The default uses Windows Trusted Authentication. You can use Windows
Trusted Authentication when your login has permissions to add a database to
the specified SQL server.
If you click to use SQL Authentication, you have to provide the Login ID and
password you want to use to connect to the specified SQL server.
Click Next.
44 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 6 TE N A N T M A N A G E R I N S T A L L A T I O N
To upgrade the Tenant Manager snap-in, you run the Web Client upgrade. The
upgrade can also make changes to any of the following components that are
installed on the server:
Important: For the Microsoft Dynamics GP 2013 R2 release, the Web Client upgrade does
not use a patch (.msp) file. Instead, you must run the WebClient.exe application found in the
\AdProd\WebClient\ folder of the Microsoft Dynamics GP 2013 R2 installation media to
perform the upgrade. After the upgrade has completed, continue with step 5 in the following
procedure.
In the Command Prompt window, change folders to the location where you
found the upgrade install file.
• Server name
• Database name
• Type of authentication
For more information about the Web Client Configuration Wizard, see
Configure the Web Management Console database.
Repeat this step on any machine where you use the web browser to view the Web
Management Console. If you do not clear the cache, you might not see the upgrade or
you might encounter an error while trying to open the Tenant Manager snap-in.
For more information about the Web Client upgrade, see the Microsoft Dynamics
GP Web Client Install and Administration Guide.
46 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 6 TE N A N T M A N A G E R I N S T A L L A T I O N
https://ServerName:PortNumber/WebManagementConsole
https://gpweb.contoso.com/WebManagementConsole
http://<servername>:<port>/TenantManagementService
The navigation pane shows a list that includes Tenants, Users, Applications,
and Exceptions. To view or update manage tenants, you use the buttons in the
ribbon.
What to do next
After you install and configure Microsoft Dynamics GP Tenant Services, consider
taking the following steps:
48 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 6 TE N A N T M A N A G E R I N S T A L L A T I O N
• Learn about actions you will need to take to configure and maintain the
Microsoft Dynamics GP Tenant Services components that you installed. Details
are found in Part 3, Configuration and Administration.
• Chapter 7, “Configuring Users,” describes how you add and maintain service
administrator and delegating users.
52 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
Chapter 7: Configuring Users
After installing Microsoft Dynamics GP Tenant Services, you can add or update
information about the users you want to administer Tenant Services. To view, add,
update, or remove users, you use the Tenant Manager snap-in of the Web
Management Console. To complete any of the following procedures, you have to
log in to the Tenant Manager snap-in as a service administrator.
The following sections describes how to add, configure, and remove service
administrators and delegating users:
• To add users
• To update a user
• To remove a user
To add users
The following steps describe how to add a service administrator or delegating user.
5. Click Add.
Click Add in the ribbon of the Web Management Console. The Add User
window opens.
Field Description
Name Specify a name for the user.
Authentication Type Specify the authentication type. Windows authentication is the
only supported type.
Identity Specify the login ID of the user. You should use the format of
domain\alias or alias@domainname.
User Type Specify whether the user is a service administrator or a
delegating user. A service administrator has access to all
tenants, users, and multitenant applications. A delegating user
is used to ‘work on behalf’ of another user. The default value is
service administrator.
Status Specify whether the user is active. Click Inactive if you do not
want the specified login to have access to Tenant Services.
The default value is Active.
Get protected application Specify whether application properties that are marked as
settings Protected are retrieved for the user.
7. Click Save.
To add the user, click the Save button.
To update a user
The following steps describe how to update an existing service administrator or
delegating user.
54 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 7 C O N F I G U R I N G U S E R S
Field Description
Name Specify a name for the user.
Authentication Type Specify the authentication type. Typically, you use Windows
authentication.
Identity Specify the login ID of the user. You should use the format of
domain\username.
User Type Specify whether the user is a service administrator or a
delegating user. A service administrator has access to all
tenants, users, and multitenant applications. A delegating user
is used to ‘work on behalf’ of another user.
Status Specify whether the user is active. Click Inactive if you do not
want the specified login to use tenant services or the Web
Management Console.
The default value is Active.
Get protected application Specify whether application properties that are marked as
settings Protected are retrieved for the user.
The default value is unmarked.
5. Click Save.
To update the properties for the user, click the Save button.
To remove a user
You can remove a service administrator or delegating user from your multitenant
environment.
Take care when removing delegating users that you do not delete a login that is in use with
an application pool. If you remove the user, the application pool will no longer be able to use
any of the tenant services.
4. Click Delete.
Click the Delete button in the tenant manager ribbon of the Web Management
Console. The user is removed from the list of users.
56 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
Chapter 8: Configuring Applications
After installing Microsoft Dynamics GP Tenant Services, you can specify the
multitenant applications you want your tenants to use. To add, update, or remove a
multitenant application, use the Tenant Manager snap-in of the Web Management
Console. To complete any of the following procedures, you have to log in to the
Tenant Manager snap-in as a service administrator.
The following sections describes how to add, update, export, import, and remove
multitenant applications:
• To add an application
• To update an application
• To export application information
• To import an application
• To remove an application
To add an application
You have to specify the application properties for the multitenant application. You
use the application properties to specify the instance of Microsoft Dynamics GP for
a tenant.
https://ServerName:PortNumber/WebManagementConsole/
3. Click Add.
Click the Add button in the tenant manager ribbon of the Web Management
Console. The Add Application window opens.
To add another multitenant application, click Add other application, and then
type the name of the application.
If you specified to add the default applications, you do not have to add application
properties. Continue to the next step.
Click the Add button. An application property is added. Provide the following
information.
Property Description
Configuration Name Type the name for the property. The name will appear when
you have to configure the multitenant application for a tenant.
Internal Specify whether the property is an internal property. The
default is to mark the checkbox.
Protected Specifies that the property will not be retrieved unless the user
account has been configured to display protected properties.
Password Specifies that the property is a password value and will be
encrypted when it is stored.
6. Click Save.
To save the application information you added, click Save. The new multitenant
application appears in the list of applications in the Web Management Console.
To update an application
The following steps describe how to add or remove an application property for an
existing multitenant application.
https://ServerName:PortNumber/WebManagementConsole/
58 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 8 C O N F I G U R I N G A PP L I C A T I O N S
3. Click Edit.
Click the Edit button in the ribbon of the Web Management Console. The
Application Properties window opens.
To remove a property, click the property name in the list of properties and then
click the Delete button. The property is removed from the list.
Take care when removing application properties. If you remove an application property,
the multitenant application may no longer run for any tenant. Changes to applications
should be completed by the person that added the application.
5. Click Save.
To save the change you made, click Save. The Application Properties window
closes.
https://ServerName:PortNumber/WebManagementConsole/
4. Click Export.
Click the Export button in the Tenant Manager ribbon of the Web Management
Console. The Application Properties window opens.
7. Click Save.
The Save As window closes and the file appears in the folder that you specified.
To import an application
If you have an .adf file that contain configuration information for a multitenant
application, you can import the application to Tenant Services. You have to first put
the .adf file in a folder that is accessible from your Tenant Services machine.
https://ServerName:PortNumber/WebManagementConsole/
3. Click Import.
Click the Import button in the ribbon of the Web Management Console. The
Open window appears.
60 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 8 C O N F I G U R I N G A PP L I C A T I O N S
To remove an application
You can remove a multitenant application from Tenant Services.
When you remove the multitenant application, the application can no longer be used for any
of the tenants for which the application has been configured. You should not delete a
multitenant application until you confirm that no tenants are using that application.
https://ServerName:PortNumber/WebManagementConsole/
4. Click Delete.
Click the Delete button in the tenant manager ribbon of the Web Management
Console. The multitenant application is removed from the list of applications.
The following sections describes how to add, configure, and remove tenants, tenant
users, and multitenant applications:
For example, the default name for the first instance of Microsoft Dynamics GP is
GP2013. You can use this instance with the first tenant in your multitenant
environment.
You also have to specify a name for the system database for the new instance. The
following illustration shows how to specify the SQL Server and the name of the
system database for the Contoso instance of GP.
To add a tenant
This section of the documentation shows how to add a tenant. The sections that
follow show how to add a tenant user and a multitenant application to the tenant.
To add a tenant, you have to log in as a service administrator to the Tenant Manager
snap-in of the Web Management Console.
https://ServerName:PortNumber/WebManagementConsole/
64 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 9 C O N F I G U R I N G T E N A N T S
3. Click Add.
Click Add in the ribbon of the Web Management Console. The Add Tenant
window opens.
Property Description
Name Specify the name for the tenant.
Description Specify a brief description for the tenant.
Status Specify whether the tenant is active or inactive. If the the
tenant is inactive, the multitenant application will not be
accessible.
5. Click Save.
To save your tenant, click the Save button. The Add Tenant window closes.
2. Click the Add button above the Add the tenant users section.
Click Add (the green plus) to create a new tenant user in the list of tenant users.
Property Description
Name Specify a name for the tenant user.
Identity Specify the login ID for the tenant user. The login ID can use
the domainname\alias or alias@domainname format. Use the
format that the user will enter when logging in to the
multitenant application.
Admin Specify whether the tenant user is a tenant administrator. A
tenant administrator can use the Tenant Manager snap-in of
the Web Management Console to add or remove tenant users.
To add a tenant administrator, mark the checkbox. To give a
tenant administrator access to the Web Management Console,
you also have to add the login ID for that user to the security
group being used for the Web Management Console.
Status Specify whether the user is active or inactive. An inactive user
cannot use the multitenant applications.
The default value is Inactive.
To add more tenant users, click the Add button and repeat this step.
4. Click Save.
When you have added all the tenant users, click Save.
66 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 9 C O N F I G U R I N G T E N A N T S
To associate a multitenant application with a tenant, you have to first add the application to
your multitenant environment. To learn more about how to add a multitenant application,
see To add an application on page 57.
If you install the Microsoft Dynamics GP default applications you will see the
following list:
The following illustration shows the properties for the Microsoft Dynamics GP
Web Client application.
For example, the following table show the properties and configuration values
for the Microsoft Dynamics GP Web Client. For more information about how to
install and configure the Web Client application, see Chapter 12, “Configuring
the Web Client.”
Name Value
DynamicsexeLocation c:\Program Files (x86)\Microsoft Dynamics\GP2013\
DynamicssetLocation c:\Program Files (x86)\Microsoft Dynamics\GP2013\Dynamics.set
DexiniLocation c:\Program Files (x86)\Microsoft Dynamics\GP2013\Data\Dex.ini
HeartbeatTimeout 0.20:00:00
RuntimeLogEnabled false
CustomRuntimeSettings ScriptLogEnabled=false|TimingLogEnabled=false|SqlLogEnable
d=false
SQLUserName The name for the SQL login that was specified to be used for the
web client when the Microsoft Dynamics GP web client runtime
was installed.
SQLPassword The password for the SQL login being used for the web client.
3. Click Save.
To save the application information for the tenant, click the Save button.
68 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 9 C O N F I G U R I N G T E N A N T S
To complete the following procedures, you have to log in to the Tenant Manager
snap-in as a service administrator.
https://ServerName:PortNumber/WebManagementConsole/
4. Click Edit.
Click Edit in the ribbon of the Web Management Console. The Tenant
Properties window opens. You can change the value of the following
properties:
Property Description
Name Specify the name for the tenant.
Description Specify a brief description for the tenant.
Status Specify whether the tenant is active or inactive. If the the
tenant is inactive, the multitenant application will not be
accessible.
Remove a tenant
You can remove an existing tenant from a multitenant environment. To remove a
tenant, you have to log in to the Tenant Manager as a service administrator.
https://ServerName:PortNumber/WebManagementConsole/
4. Click Delete.
Click the Delete button in the tenant manager ribbon of the Web Management
Console. The tenant is removed from the list of tenants.
To complete the following procedures, you have to log in to the Tenant Manager
snap-in as a service administrator or a tenant administrator.
70 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 9 C O N F I G U R I N G T E N A N T S
• To make a tenant user inactive, click the drop down list and select Inactive.
The specified user will no longer be able to use the multitenant applications
for the tenant.
• To make the tenant user active, click the drop down list and select Active.
The specified user can now use the multitenant applications associated
with the tenant.
If you do not specify a property value, the tenant user defaults to the application
property settings that you specified when you configured the multitenant application
for the tenant.
For example, you set the RuntimeLogEnabled property of the Web Client
application to true. The change enables logging for that tenant user. Activity by
other tenant users is not recorded in the log file.
8. Click Save.
3. Click Delete.
Click the delete button (the red X) above the list of tenant users. The specified
tenant user is removed from the list. That user will no longer be able to login to
that tenant.
To complete the following procedures, you have to log in to the Tenant Manager
snap-in as a service administrator.
4. Click Save.
To save the tenant information, click the Save button of the Tenant Properties
window.
72 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 9 C O N F I G U R I N G T E N A N T S
For example, the following illustration shows how to change the value of the
Heartbeat Timeout property for the Microsoft Dynamics GP Web Client
application for the specified tenant. Notice how the other properties keep their
existing values.
4. Click Save.
To save the changes, click the Save button of the Tenant Properties window.
• To add a feature, click the drop down list and click Run from My Com-
puter.
• To remove a feature, click the drop down list and click Not Available.
Click Next.
Setting Description
Port Each service has a default port. If that port is in use, the next available
port is selected. In addition, you can enter the port number that you
want the service to use.
Certificate Specify a security certificate for the service. The security certificate
enables the service to use SSL. The default value is Not Selected.
A security certificate is optional for the Tenant Discovery Service and the
Tenant Management Service. If you do not specify a certificate, SSL will
not be used to encrypt messages to and from that service. A security
certificate is required for the Tenant Public Discover Service.
To review information about available certificates, click the certificate in
the drop-down list, and then click the View button. A dialog window
opens that provides detailed information about the certificate.
Host name The fully-qualified domain name of the server where you have installed
the security certificate.
Setting Description
Domain Enter the domain name associated with login ID.
User name Enter the login ID you want the service to use.
Password Enter the password for the specified login ID.
Click Next.
If you added a service, you might need to run the Microsoft Dynamics GP
Tenant Services Configuration Wizard. You use the wizard to specify the SQL
Server name, your tenant services database, and the authentication type. For
more information about how to use the wizard, see Configure the Tenant Services
database.
Completing a repair
If the Microsoft Dynamics GP Tenant Services becomes damaged, the repair
operation may help resolve the issue. The Repair wizard fixes the following:
2. Click Repair.
Setting Description
Domain Enter the domain name associated with login ID you want the service to
use. The domain of the existing account appears in the text box. You can
keep the existing domain or enter new domain information.
User name Specify the login ID you want the service to use. The name of the
existing account appears in the text box. You can keep the existing login
ID or enter a new login ID.
Password Enter the password for the specified login ID.
Click Next.
76 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 1 0 M A I N T E N A N C E
4. Ready to repair.
Click Repair to begin. The repair might run for several minutes.
5. Repair complete
When the Repair Complete window appears, click Exit to close the wizard.
When you remove Tenant Services, the DYNGPDISCOVERY database is not removed. To
remove the database, you have to use SQL Server Management Studio.
2. Click Remove.
Click Remove.
The login you used may not have sufficient privileges to initialize the service on the
server. Use Local User and Groups in Server Manager and add the login to the
Administrators group. Try starting each service again. The services should start and
run.
This error can occur when ASP.NET has not been successfully installed on the
server. To correct the specified issue, open a command prompt with administrator
privileges and navigate to the following folder:
c:\Windows\Microsoft.NET\framework64\v4.0.30319\
aspnet_regiis -i
The command installs the specified .NET framework and should eliminate the error
message. After you complete the install, you should run the IIS reset command
(iisreset) to restart the web server.
When you install Tenant Services, your login is added as a service administrator for
Tenant Services. However, you also need to supply a login for the application pool
for the Web Management Console. The specified login is added as a delegating user
for Tenant Services.
A login cannot be both a service administrator and a delegating user. Be sure that
you used a different login for the application pool. If you used the same login for
the application pool identity that you use to install Tenant Service, you might not be
able access the Tenant Manager console.
To use the Tenant Manager in the Web Management Console, be sure that you login
with the ID of the service administrator. Verify that you are logged in with the login
ID you used to install Tenant Services or another ID that is specified as a service
administrator.
Verify the Microsoft Dynamics GP Tenant Management Service is running. You will
not be able to use Tenant Manager until the service is started.
Verify the Microsoft Dynamics GP Tenant Discovery Service is running. You will
not be able to use the application until the service is running.
80 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 1 1 TR O U B L E S H O O T I N G
To view detailed error information, click the error in the list you want to view more
information. Click the Error Details button at the bottom of the page. The Error
Details shows more complete information and additional details about the error.
Microsoft.Dynamics.MultitenantServices.Discovery.config.
Be sure to make a copy of the configuration file before you make any changes to the
file. You can use the saved copy to restore the original configuration settings for the
service.
You can use this setting when you are debugging an issue to get the complete error
message. You will see more information about the exception which can help you
identify the cause of the exception.
When you are done, set the value of the includeExceptionDetailInFaults attribute to
false. If you do not restore the original settings, everyone who uses the service will
get the detailed error messages.
• Microsoft.Dynamics.MultitenantServices.Discovery.config
• Microsoft.Dynamics.MultitenantServices.Management.config
• Microsoft.Dynamics.MultitenantServices.Discovery.Public.config
The previous section provides the typical location of each configuration file.
You can have the Web Client tenant application produce the following logs:
Name Description
Runtime log The primary log you use to record and view web client activity. The
log records information about service calls, client actions,
generated macro lines, and Dexterity callbacks.
Script log Enables the Dexterity script log you can use when you debug
sanScript code
82 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 1 1 TR O U B L E S H O O T I N G
Name Description
Sql log Enables the same type of logging that you get when you enable
SQL logging in the Dex.ini file. The log contains information about
the connection to the SQL server and the queries to that server.
Timing log The log you use to record the timing information for messages,
script execution, callbacks, and other events. You enable this log to
gather information you can use to monitor performance for an
event or action.
To enable logging, the Web Client application includes the following properties:
Property Description
RuntimeLogEnabled This property enables you to create the runtime log for a tenant.
The default value for the property is false. To start the Runtime log,
set the property to true.
CustomRuntimeSettings This property enables you to create more detailed log information
for scripts, SQL server activity, and the time for specified actions
and events. The property includes a parameter for each type of log.
The parameters are named ScriptLogEnabled, TimingLogEnabled,
and SqlLogEnabled.
The default value for the each parameter is false. To start a log, you
set the value for that log parameter to true.
You can determine what information goes into a log file by where you enable the
log.
• If you set the property to true in the Application Settings of the Tenant
Properties window, the log contains information for all Web Client users for the
tenant.
• If you set the property to true in the Application Settings section of the Tenant
Users window, the log contains information for the specified tenant user.
After you enable logging, you can find the generated log in the following location:
When you have completed your analysis, be sure to return the value of the log
properties to false.
• Chapter 12, “Configuring the Web Client,” describes how you configure the
Microsoft Dynamics GP Web Client application for a tenant.
• Chapter 13, “Configuring Web Services,” describes how you specify web
service and tenant configuration information. The Web Services for Microsoft
Dynamics GP Configuration Wizard uses this configuration information to add
web services access to the tenant.
86 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
Chapter 12: Configuring the Web Client
This portion of the documentation describes how you use the Tenant Manager to
make the Dynamics GP Web Client available for use with tenants. The
documentation also describes how you provide information that is used to
configure the web client for a specified tenant.
In addition, you should have already added the tenant. To add a tenant, you use the
Tenant Manager snap-in. For information about how to add a tenant, see To add a
tenant on page 64.
To add the Dynamics GP Web Client to the tenant, you use the Tenant Manager
snap-in to supply important configuration information. The following table shows
the information you will need to gather:
File Description
Dynamics.exe The Dynamics executable file from the Microsoft Dynamics GP
instance for the tenant. You need to specify the path to the folder
where the file was installed. For example:
c:\Program Files (x86)\Microsoft Dynamics\GP2013\
Dynamics.set The Dynamics set file from the Microsoft Dynamics GP instance for
the tenant. You need to specify the file and its location. For
example:
c:\Program Files (x86)\Microsoft Dynamics\GP2013\Dynamics.set
Dex.ini The Dex initialization file from the Microsoft Dynamics GP instance
for the tenant. You need to specify the file and its location. For
example:
c:\Program Files (x86)\Microsoft Dynamics\GP2013\Data\Dex.ini
SQLUserName The name for the SQL login that was specified to be used for the
web client when the web client runtime was installed for the
Microsoft Dynamics GP instance.
SQLPassword The password for the SQL login being used for the web client for
the Microsoft Dynamics GP instance.
The following steps describe how to add the Microsoft Dynamics GP Web Client to
the list of applications in the Tenant Manager snap-in:
In addition, your login must have authorization to use the Microsoft Dynamics
GP Web Management Console. Your login must be a member of the security
group you specified during the install of the Tenant Manager.
https://ServerName:PortNumber/WebManagementConsole/
Replace ServerName with the name of the server that is running the Web
Management Console. If the web site isn’t using port 80, supply the PortNumber
as well.
5. Click Add.
Click the Add button in the ribbon of the Web Management Console. The Add
Application window opens.
88 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 1 2 C O N F I G U R I N G T H E W E B C L I EN T
7. Click Save.
To verify the changes, click Applications in the Tenant Manager navigation
pane. You should see Microsoft Dynamics GP Web Client and Web Services for
Microsoft Dynamics GP in the list.
The following steps describe how to configure the web client for a tenant:
In addition, your login must have authorization to use the Microsoft Dynamics
GP Web Management Console. Your login must be a member of the security
group you specified during the install of the Tenant Manager.
https://ServerName:PortNumber/WebManagementConsole/
Replace ServerName with the name of the server that is running the Web
Management Console. If the web site isn’t using port 80, supply the PortNumber
as well.
You have to specify the value for each application property. The following table
shows the properties and describes how to specify a value for each property:
90 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 1 2 C O N F I G U R I N G T H E W E B C L I EN T
8. Click Save.
To save the application configuration information, click the Save button.
What to do next
You can add the users that you want to access the Web Client as tenant users for the
tenant. For information about how to add a tenant user, see To add a tenant user on
page 65.
In addition, you should have already added the tenant. To add a tenant, you use the
Tenant Manager snap-in. For information about how to add a tenant, see To add a
tenant on page 64.
To add Web Services for Microsoft Dynamics GP to the tenant, you use the Tenant
Manager snap-in to supply important configuration information. The following
table shows the information you will need to gather:
The following steps describe how to add Web Services for Microsoft Dynamics GP
to the list of applications in the Tenant Manager snap-in:
In addition, your login must have authorization to use the Microsoft Dynamics
GP Web Management Console. Your login must be a member of the security
group you specified during the install of the Tenant Manager.
https://ServerName:PortNumber/WebManagementConsole/
Replace ServerName with the name of the server that is running the Web
Management Console. If the web site isn’t using port 80, supply the PortNumber
as well.
94 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 1 3 C O N F I G U R I N G W E B S E R V I C E S
5. Click Add.
Click the Add button in the ribbon of the Web Management Console. The Add
Application window opens.
7. Click Save.
To verify the changes, click Applications in the Tenant Manager navigation
pane. You should see Microsoft Dynamics GP Web Client and Web Services for
Microsoft Dynamics GP in the list.
The following steps describe how to add web services configuration information for
a tenant:
In addition, your login must have authorization to use the Microsoft Dynamics
GP Web Management Console. Your login must be a member of the security
group you specified during the install of the Tenant Manager.
https://ServerName:PortNumber/WebManagementConsole/
Replace ServerName with the name of the server that is running the Web
Management Console. If the web site isn’t using port 80, supply the PortNumber
as well.
96 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
C H A P T E R 1 3 C O N F I G U R I N G W E B S E R V I C E S
You have to specify the value for each application property. The following table
shows the properties and describes how to specify a value for each property.
8. Click Save.
The values for the application properties are saved.
What to do next
Run the Web Services for Microsoft Dynamics GP Configuration Wizard, which can
be found on the server where you initially installed web services. You need to run
the wizard for each tenant that you configured to use web services. When you run
the wizard, you will be asked to specify the tenant. For more information about the
Web Services Configuration Wizard, see the Web Services Installation and
Administration Guide.
You can add the tenant users that you want to access web services for the tenant.
For information about how to add a tenant user, see To add a tenant user on page 65.
To enable a tenant user to access web services, you will also need to use the
Dynamics Security Console to add the user, specify a company, and assign a
security role. For more information, see the “Role assignments” section of the Web
Services Installation and Administration Guide.
98 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
APPENDIX
Appendix
The following appendix is included for this documentation:
• Appendix A, “Scale Groups,” explains how scale groups can be used to further
configure a multitenant configuration of Microsoft Dynamics GP.
100 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
Appendix A: Scale Groups
The scale groups feature introduced in Microsoft Dynamics GP 2013 R2 works in
conjunction with tenant services to provide enhanced flexibility when deploying
several installations of the Microsoft Dynamics GP web client. The primary users of
this feature will be organizations that host multiple installations of Microsoft
Dynamics GP.
Tenant 1
Tenant 2
Tenant 3
Tenant 4
Tenant 5
GP Instance 1
GP Instance 2
GP Instance 3
GP Instance 4
GP Instance 5
Session Host
The Session Host server has the five instances of Microsoft Dynamics GP installed.
The Tenant Services server has a tenant defined for each GP instance. When a user
logs in to the web client, Session Central will direct the user to the appropriate GP
instance, based on the tenant configuration specified in Tenant Services.
This configuration works well, but two issues are commonly encountered. The first
issue occurs when the limit of 51 Microsoft Dynamics GP instances is reached on the
Session Host server. The only solution is to install another deployment group
consisting of a Web Server, a Session Central server, and a Session Host server.
The second issue occurs when a specific tenant has the requirement to support more
concurrent web client sessions. You can address this need by adding additional
Session Host servers. However, recall that each session host machine in the
installation must have the same set of GP instances. That means that you must
install and manage all of the GP instances on the additional session host machine,
even though only one tenant requires the additional capacity.
Tenant 1
Tenant 2
Tenant 3
Tenant 4
Tenant 5
In this example, two scale groups (Scale Group A and Scale Group B) are defined.
Tenants 1, 2, and 3 are assigned to Scale Group A. Tenants 4 and 5 are assigned to
Scale Group B. Scale Group A has one session host machine, while Scale Group B
has two session host machines.
Let’s examine how scale groups help to solve the two common issues encountered
in the non-scale groups configuration. First, the 51 instance limit is no longer an
issue. If a session host machine has reached the limit, you can simply create a new
scale group and add another session host machine to the new scale group. The new
tenant can be assigned to the new scale group. There is no need for an additional
web server and session central server.
Scale groups also help solve the second issue because they provide flexibility when
you need to scale out a tenant. In this example configuration, let’s assume that
Tenant 4 needed additional processing capability. An additional session host
machine was added to Scale Group B. Because only tenants 4 and 5 are assigned to
Scale Group B, the additional session host machine had to have only GP Instances 4
and 5 installed on it. Session Host 1 and the tenants assigned to it were unaffected
by the change to scale out Tenant 4.
102 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
A P PE N D I X A S C A L E G R O U P S
By automatically considering new session host machines and tenants are part of the Default
Group scale group, the default functionality of the system is the same as it was before scale
groups were available.
Removing assignments
Several PowerShell cmdlets are available to remove assignments that have been
made. For example, the following command removes the scale group assignment
for Tenant 01. Tenant 01 will then be assigned to the Default Group scale group.
104 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E
Glossary Tenant administrator
A specified tenant user that can add other
tenant users to a tenant.
Application
A client application that you can associate Tenant Manager
with one or more tenants. You use the A Silverlight application that is used to
application to perform operations that use perform administrative tasks for the
Microsoft Dynamics GP data. Microsoft Dynamics GP Tenant Services. The
Tenant Manager is a snap-in that appears in
Application Programming the Web Management Console.
Interface (API)
A set of functions or features you access to
Tenant user
A user that is assigned to a tenant. When you
programmatically use or manipulate a
assign a user to a tenant, that person is
software component or application.
authorized to use any of the configured
Delegating user multitenant applications for that tenant.
The user account that you use to call Tenant
Services operations on behalf of another
Windows Communication
specified user. The operation returns tenant Foundation service (WCF)
information based on the specified user or Windows Communication Foundation. This
service administrator parameter that is is a framework included in the .NET
provided with the call. Framework that can be used to build
services that allow applications to exchange
Integrated security data. WCF supports several standard
The SQL server security option that protocols and authentication methods.
leverages Windows authentication to supply
the user’s login credentials. It allows a Web client
network user to access a SQL server database The Microsoft Dynamics GP web client
without supplying separate login provides access to Microsoft Dynamics GP
credentials. through the Internet Explorer web browser.
The user experience and functionality
Security certificate provided by the Microsoft Dynamics GP
A document that helps a client and service to web client closely matches the experience of
more securely communicate across a using the Microsoft Dynamics GP desktop
network. You can use a security certificate to client.
help secure the Tenant Discovery Service,
Tenant Management Service, and the Tenant Web Management Console
Public Discovery Service. In addition, you A Silverlight application that is used to
can use a security certificate to help secure perform administrative tasks. The Web
the web site that hosts the Web Management Management Console can include the Tenant
Console and the Tenant Manager snap-in. Manager snap-in.
Services
Microsoft Windows services are long-
running applications that perform some
system function. Services typically do not
display any user interface.
Tenant
An organization that uses an instance of
Microsoft Dynamics GP. A tenant identifies
the users and applications that are associated
with the specified instance of Microsoft
Dynamics GP.
service administrator (continued) Tenant Manager Installation, chapter web client (continued)
prerequisites 25 39-49 application properties 89
update properties 54 tenant public discovery service, settings chapter 87-91
service login ID, user account 21 34 configuration 89-91
services tenant services defined 105
see also Discovery Service, architecture diagram 13 logs 82
Management Service, Public described 7, 14 preparations 87
Discovery Service listed 14 web management console
APIs, described 16 prerequisites 25 application pool ID 21
defined 105 procedure for modifying 75-76 configuration wizard 44-46
described 14 procedure to remove 77 defined 105
troubleshooting 80 procedure to repair 76-77 described 81
troubleshooting configuration files 81 start the services 79 HTTP error 79
URL 80 support 3 install 41
software developer, responsibilities 8 user accounts 25 prerequisites 27
SQL Server, required 26 uses 7 procedure to add SSL 40
SSL Tenant Services Basics, part 6-22 web services
configure web management console Tenant Services Overview, chapter 7-9 add the application 93-95
40 tenant user application properties 96
defined 105 defined 105 chapter 93-98
security certificates 21 described 12 configuration 95-97
support, for Microsoft Dynamics GP 3 procedure to add a tenant user 65-66 defined 105
symbols in documentation 2 remove 71 preparations 93
system administrator, responsibilities 8 tenant user properties 70 windows services, see services
updating 70
T troubleshooting X
technical support, for Microsoft Dynamics chapter 79-83 XML, defined 105
GP Tenant Services 3 event log 81
tenant login problems 80
add tenant user 65 services 80
change application configuration tenant applications 80
72-73 tenant services do not start 79
change tenant properties 69 web management console 79
defined 105
delete 69 U
described 11 uninstall
multitenancy 11 described 77
procedure to add a tenant 64-65 removing Tenant Services 77
procedure to add an application 67 user accounts
procedure to configure an application create accounts 25
67-68 for install 20
remove an application 72 requirements 21
select an application 67 service administrator 21, 25
update tenant users 70 service login ID 21
updating 69 services 25
tenant administrator tenant services 25
defined 105 web management console 21
described 12 users 12
tenant discovery service, settings 32 add delegating users 53
tenant management service, settings 33 add service admininstrator 53
tenant manager 16 deleting 55
defined 105 described 12
described 16 multitenancy 12
diagram 16 procedure to add users 53-54
initialization procedure 46-48 procedure to update properties 54-55
installation procedure 41-43
procedure for security certificate W
39-40 warning symbol 2
service URL 80 WCF, defined 105
troubleshooting 80 web client
add the application 87-89
108 T E N A N T S E R V I C E S I N S T A L LA T I O N A N D A D M I N I S T R A TI O N G U I D E