The information in this article applies to:
Product: Metastorm BPM Process Orchestrator for Web Services
Version: 7.5.x
Issue
Resolution
The Complex Type Mapper uses one of the following registry values depending on whether SQL Server or Oracle is used:
HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Metastorm\\e-work\\Engine\\Database Connectors\\SQL Server DBC\\Connection
or
HKEY\_LOCAL\_MACHINE\\SOFTWARE\\Metastorm\\e-work\\Engine\\Database Connectors\\Oracle DBC\\Connection
Note that this registry entry is created for the Designer during installation even if the Engine is not installed. To connect the Mapper to a different database, the value in the registry must be manually edited.
If the Mapper fails to launch (no errors generated), proceed as follows:
If Oracle is used, install Metastorm BPM Process Orchestrator for Web Services 7.5.1 Hotfix 1 (7.5.1.1). This can be downloaded from the Metastorm Customer and Partner Zones.
If SQL Server is used, make sure the user listed in the registry (see above) accesses the eProcedure table as dbo (dbo.eProcedure). If this is not the case, make the necessary change or install Metastorm BPM Process Orchestrator for Web Services 7.5.1 Hotfix 1 (7.5.1.1). This hot fix executes the database query without specifying dbo as the table owner.
Offline libraries (.xel files) cannot be used with the Mapper. Access to the database must be provided.