GIS Administrators

To get started using the GIS Task components, you'll need to perform the following steps after the gbaMS Web Install from a workstation with gbaMS version 6.75 installed (with Admin Tools).

Important: All of the steps described below are required in order to use the gbaMS ArcGIS Server Tasks.

1. After creating an ArcGIS Server application using the ESRI tools, you'll need to add two connection strings to web.config. This file can be found in the root folder of the application created by ArcGIS Server Manager. For example: C:\Inetpub\wwwroot\*name of application* (the name of the application can differ for each client; It can be customized through ArcGIS Server Manager).
   • By default, we've included the same user ID and password that are used by the gbaMS Web Gateway Account; however, you can set up your own custom ID and password if desired.
   • If you set up your own ID and password, the user account needs to have access to the gbaMS database and have execute permissions to use the stored procedures. For SQL Server, the user must have access to: spGBA_CONNECTSTRINGSLoadAll. For Oracle, the user must have access to the PKG_CONNECTSTRINGSLOAD ALL package.
2. Next, go to IIS (internet Information Services), browse to the application you've just created, and complete the following:
   • Right click to access Properties.
   • On the Directory Security tab, select Edit under "Anonymous Access and Communication Control".
   • Turn off Anonymous Access (uncheck the box).
   • Turn on Integrated Windows Authentication (check the box).
   • Click OK.

     

     Note: You'll need to complete step 2 for each ArcGIS Server application that you've created.

3. Then, in ArcGIS Server Manager, you'll need to add the two gbaMS ArcGIS Server tasks to the application using the Select Tasks tab:
   • gbaMS Customer Search
   • gbaMS Open Module

     Note: Several additional steps are required to use the two gbaMS GIS Server tasks. Follow the links for information on the Customer Search Tool and the gbaMS Open Module Tool.

     

4. In order for the application to function properly, you'll need to edit the web.config file for the deployed application and add the following to the file:
   • For SQL Server:

     <connectionStrings>

     <add name="GBAUserConnectionString" connectionString="Data Source=[insert sql server instance name here];Initial Catalog=GBAUser;User ID=gbams_web_gateway;Password=[put gateway password here]" providerName="System.Data.SqlClient"/>

     </connectionStrings>

   • Or for Oracle:

     <connectionStrings>

     <add name="GBAUserConnectionString" connectionString="Data Source=[oracle server instance here];User ID=gbams_web_gateway;Password=[gateway password here]" providerName="Oracle.DataAccess.Client"/>

     </connectionStrings>

     These get inserted directly above the </configuration> line which is the last line in the file.

5. Finally, make certain that your users' Windows accounts are set up in the UI Admin program in the User Manager.