Redistributing Your Application

An application that is developed using the AVEVA Historian SDK can be redistributed by packaging the redistributables that are provided with the SDK. The redistributables can be found in C:\Program Files (x86)\ArchestrA\Toolkits\Redist\HistorianSDK <version number>, unless the default location is changed during installation.

• HistorianSDK <version number>
  • X64
    • HCALManaged.msm
    • HCBE.msm
    • HDPAPI.msm
    • HistorianMessages2.msm
    • LoggerIndCompRefMSM.msm
    • NCHContract.msm
    • Storage.msm
  • X86
    • HCALManaged.msm
    • HCBE.msm
    • HDPAPI.msm
    • HistorianMessages2.msm
    • LoggerIndCompRefMSM.msm
    • NCHContract.msm
    • OCMCIndCompRefMSM.msm
    • Storage.msm

SDK applications also require the Operations Control Management Console and Operations Control Logger. These components are distributed as standalone installers, included in subfolders of the SDK installation media. These should be included with your SDK application, and installed on the target system prior to installing your SDK application. You can find the standalone installers in the following locations:

• Operations Control Management Console
  • <SDK media root>\InstallFiles\Redist\OperationControlManagementConsole\OperationControlManagementConsole.exe

• Operations Control Logger
  • <SDK media root>\InstallFiles\Redist\OperationControlLogger\OperationControlLogger.exe

A clear understanding of creating an MSI is essential for packaging the developed SDK application. Before packaging the application, you should be familiar with how to create an MSI using WIX or any other tool used to create an MSI. For more information, see  Creating a WiX Based MSI Package Using Visual Studio.

The SDK Application can be developed in two different versions: 32-bit and 64-bit.

A 64-bit SDK application needs to consume the following 64-bit and 32-bit merge modules during packaging so that the application functions correctly when it is installed on a different computer:

• X64
  • HCALManaged.msm
  • HCBE.msm
  • HDPAPI.msm
  • HistorianMessages2.msm
  • LoggerIndCompRefMSM.msm
  • NCHContract.msm
  • Storage.msm
• X86
  • OCMCIndCompRefMSM.msm

A 32 bit SDK application needs to consume the following merge modules during packaging so that the application functions correctly when it is installed on a different computer:

• X86
  • HCALManaged.msm
  • HCBE.msm
  • HDPAPI.msm
  • HistorianMessages2.msm
  • LoggerIndCompRefMSM.msm
  • NCHContract.msm
  • OCMCIndCompRefMSM.msm
  • Storage.msm