Running the SVC Client Utility Tool

Once you have upgraded to AgilePoint BPMS v5.0 R2, you must run the SVC Client Utility Tool on each instance of AgilePoint Enterprise Manager in your environment.

This topic provides the standard instructions for running the SVC Client Utility on any ASP.NET web application.

Prerequisites

AgilePoint Server running in Windows Service mode.
You have applied the AgilePoint BPMS v5.0 R2 upgrade on all applicable AgilePoint machines.
You have updated your AgilePoint Server instances.
Create a backup copy of the configuration file for the application you are configuring before using this utility.
If you are using SharePoint or AgileForms Server on a machine that is not the AgilePoint Server machine (typically the case), copy the web.config file from the SharePoint or AgileForms machine to AgilePoint Server machine. The following are the default locations of the target web.config files:
- SharePoint - c:\inetpub\wwwroot\wss\VirtualDirectories\[port number]
- AgileForms - [AgileForms Server installation folder]\Webroot

Navigation

Do one of the following:

On the AgilePoint Server machine, navigate to [AgilePoint Server Installation]\SVCUtilityTool\AgilePointWindowsServiceClientUtilityTool.exe
Open the AgilePoint installation file, and click Utilities and Other Support Files > AgilePoint Windows Service Client Utility Tool.

Instructions

In the AgilePoint Windows Service Client Utility Tool dialog box, complete the following fields:
- Service Address – The URI for the Windows Service for which you are creating the binding. The information required to build this URI is provided in the AgilePoint Server Manager window.
- HTTP - http://[APServer Machine Name]: [Http Port]/AgilePointServer
  When you create the bindings for the web application, the settings are automatically configured in the web.config file for both HTTP and TCP protocols. By default, the HTTP bindings are used. However, you can switch to TCP by modifying the following properties in the web.config:
  - Change the following so value="NetTcpBinding_IWCFWorkflowService"
```
<add key="WorkFlowBindingUsed" value="WSHttpBinding_IWCFWorkflowService" />
```
  - Change the following so value="NetTcpBinding_IWCFEventServices"
```
<add key="EventServicesBindingUsed" value="WSHttpBinding_IWCFEventServices" />
```
  - Change the following so value="NetTcpBinding_IWCFAdminService"
```
<add key="AdminBindingUsed" value="WSHttpBinding_IWCFAdminService" />
```
- Target Config – The file name and location of the configuration file for the application you are configuring. This is required for SharePoint Integration. For other applications, you only need to run this utility if you are prompted.
  - SharePoint Integration – The web.config for the SharePoint web application you want to bind.
  - Enterprise Manager – The web.config for the Enterprise Manager web application.
  - Data Services – DataServicesWindowsService.exe.config in the Data Services installation folder. The default location is C:\Program Files\AgilePoint\AgilePoint Data Services\
  - AgileForms - The web.config file in the AgileForms installation folder. The default location is C:\Program Files\AgilePoint\AgileForms Server\Webroot
  - Deployment Service - apds.exe.config file in the Deployment Service installation folder. The default location is C:\Program Files (x86)\AgilePoint\AgilePoint Deployment Service\
Click Settings to configure the following fields:
- Max Buffer Size
- Max Buffer Pool Size
- Max Received Message Size
- Max String Content Length
- Max Array Length
Guidance for modifying these values can be found at the following articles on MSDN:
- http://msdn.microsoft.com/en-us/library/ms731361(v=VS.100).aspx
- http://msdn.microsoft.com/en-us/library/ms731325(v=VS.100).aspx
If you are using SharePoint or AgileForms Server on a machine that is not the AgilePoint Server machine, copy the modified web.config file back to its original location on the SharePoint or AgileForms Server machine.