As with the generic Server Integration, refer to the variables listed below in order to edit the following database script as desired. Then, execute it on the AVEVA Mobile Operator database to insert a record to the ISMGT_APP_TYPE table:

insertISMGT_APP_TYPE (APP_TYPE_PK, NAME, APP_TYPE_UI, IsCustomIntegration, IsSchedulable, RequiresServerConfiguration)

values(32050, 'DefaultTest', NEWID(), 1, 1, 1)

[app_type_pk]: A unique Integer, greater than 10000, required by the system.

[name]: A description of the Custom Tag / Server Integration.

[app_type_ui]: A GUID used by the system. This value should never change once created.

[IsCustomIntegration]: Indicates whether or not this is a custom Integration. This value should always be set to 1.

[RequiresServerConfiguration]: Indicates whether this Integration requires configuration as a Server Integration. This value should be 0 if a Custom Tag, and 1 if a Custom Server Integration (or DTS Provider).

[IsSchedulable]: Indicates whether this item can be scheduled. Set this value to 1 if it can be scheduled by iDTS and executed by DTS, or 0 otherwise (e.g., handled by an external schedule / execution handler).

Creating a DLL Within Visual Studio

1. Create a class library project with Visual Studio 2008.
2. Add references to the IntelaTrac.Sdk and the Sat.Core assembly (these are located in the "...\AVEVA\Mobile Operator\Server\SDK_Examples " directory).
3. Create a new class that inherits from DtsProvider in the IntelaTrac.Sdk namespace
   
   

      using IntelaTrac.Sdk;

    

      /// <summary>

      /// Example class of a DTS provider

      /// </summary>

      public class DTSProviderExample : DtsProvider

4. Add a unique id to your class. For example:

   privateGuid id = new Guid("XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX");

5. Override the following methods:
   1. public override string AppTypeID()
      This must return the app_type_ui that was added to the ISMGT_APP_TYPE table above.
   2. public override string Description()
      Your integration description
   3. public override string DisplayName()
      The display name in the Management Center
   4. public override Guid ID()
      The unique Guid created above
   5. public override string Manufacturer()
      Your company name
   6. public override bool SupportsMultipleConfigurations()
      True to enable the integration's configuration multiple times, otherwise false.
   7. public override bool Execute(Guid integrationConfigId) 
      This function is called during execution, passing the specific Integration configuration ID being called.
6. Compile the DLL, and copy it to the extensions subdirectory of the Management Center install directory (by default: "Program Files\AVEVA\Mobile Operator\Server\Extensions").

Configuring Your DTS Provider

1. Open the Management Center, and then Procedure Builder.
2. In Procedure Builder, select "Server Integration Configuration" from the "Edit" menu. You will see a group for your custom integration based on the name in the ISMGT_APP_TYPE table.
3. Add a configuration to the group as you would with any other server (refer to the "AVEVA Mobile Operator Management Center User's Guide" for details).
4. Save your changes and close Procedure Builder.
5. Open iDTS configuration. In the list of Configured Providers you will see your integration listed according to the Server Name entered into the Server Integration Configurations.
6. Configure the DTS Provider according to your needs, and save your changes.
   

*The DTS service requires system user credentials. The DTS and Sync Service log on should be set to system user credentials.