Architecture Considerations

If you are installing an application server or extension server (that is, Workflow or User) on a 64-bit computer, you can configure the server for either 32-bit or 64-bit operation.

When installing for the first time, you indicate your preference at installation time, whereas when upgrading, the installation maintains the existing configuration by default. In both cases, however, components that enable either 32- or 64-bit server operation are installed to your system, and you can subsequently use the Configure Server tool to change between 32- and 64-bit mode, as outlined under Change architecture mode.

If you are using a 64-bit operating system and are installing to the default installation location, do not remove (x86) from the default installation directory path. Windows detects that Workflow is a 32-bit process, and defaults to C:\Program Files (x86)\Proficy…. If you remove (x86) from the default installation location on a 64-bit operating system, your installation will fail.
Note: Client-only installations are restricted to 32-bit operation, regardless of installation location.

Default Installation Locations by Architecture Type

By default, program installation locations by architecture type are as follows:
  • 64-bit: C:\Program Files\Proficy\Proficy Workflow\Program
  • 32-bit: C:\Program Files (x86)\Proficy\Proficy Workflow\Program

Determining Current Architecture Mode

Any time after installation, you can consult the Processes tab of Windows Task Manager to ascertain the architecture mode that the Workflow Server service is currently running under. If operating in 32-bit mode, the ProficyServer.exe listing is appended with *32.

Implications for Product Options and Service Providers

The ProficyPackager and ProficyInstaller tools are available in both the 32-bit and 64-bit installation locations, and you can package and install product options from either folder. When you run Workflow application server or Workflow client, the need to update product options is automatically determined depending on where you installed the product options from. For example, if you package and install a product option from the 64-bit folder, and run the 64-bit Workflow application server, the Workflow client (which runs only in 32-bit mode) will automatically invoke the ProficyUpdater tool to update the product option in the 32-bit folder.

Product option assemblies that are loaded by the Workflow client (for example, configuration screens and displays) must target either Any CPU or x86, because Workflow client runs only in 32-bit mode.

Implications for running service providers are as follows:
  • Service providers that were built using a target architecture of Any CPU, can be run in either 32- or 64-bit mode.
  • Service providers that were built to target x86 (32-bit) architecture can be run only in 32-bit mode.
    Note: This is typically the case when the service provider references a C++/CLI library with 32-bit dependencies.
  • Service providers that were built to target x64 (64-bit) architecture can be run only in 64-bit mode.
    Note: This is typically the case when the service provider references a C++/CLI library with 64-bit dependencies.

Maintenance of Configuration Settings

After an upgrade installation on a 64-bit computer that was previously running the 32-bit version of Workflow, the server configuration file in the 32-bit location (C:\Program Files (x86)\Proficy\ProficyWorkflow\Program\ProficyServer.exe.config) retains all pre-existing system settings, whereas the configuration file in the 64-bit location (C:\Program Files\Proficy\ProficyWorkflow\Program\ProficyServer.exe.config) contains new default settings. If you want to switch from 32-bit to 64-bit operation but continue using your previously implemented configuration settings, you should migrate the settings in the 32-bit version of the configuration file to the 64-bit version.