Process Mapping Logo

Process Mapping - Forums

Sharing 19 years of knowledge and experience

 
Metastorm BPM forums
Sign up Latest Topics
 
 
 


Reply
  Author   Comment  
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #1 
I have just been forced to create a new database as the old one got stuffed. I have now fixed the old one, and I want to move back to that one.

Typically we have a plethora of databases as we have several clients and work on different systems at any time. The easy way in the past has been to have separate databases. I have resisted doing this in version 9 as I can see is not so simple. Just how difficult it really is, I was soon to discover.

It always used to be easy. In version 5 there was one registry setting. In version 6 there were 2 settings AND an admin tool then to do it all for you. Same in version 7.

In version 9? Well, there is the deployment service. You cannot deploy to different databases, only to different services (ie different servers unless you want to set up a new deployment service yourself). There is no way I can see to set a single deployment service to change database connection.

OK, I can edit some XML (although I loathe doing so, and loathe even more the absurd belief that this is an acceptable way to change simple configuration settings). This means I can change my deployment service to point to different database. Not ideal, but it works OK.

Next: The engine. Where to set that? Well, the doco happily states that you can do this from the admin tools. Just register the server, right-click on the engine and select 'database'. Well, I can't see any 'database' option. I'd be interested in seeing if others can or cannot see the option - do let me know.

OK, so we dive into the Metastorm BPM Engine User Interface™ (the registry), and what do we find? No less than seven entries for this one setting. That's SEVEN (7). I mean, is that overkill, massive redundancy, registry bloat or what?

OK, so I change all the initial catalog setting to the original database. Start the engine. Fails. Why?
Quote:
ODBC database connection string points at different database to Database connector.


OK, so we trawl through the Metastorm BPM Engine User Interface™ once more and find a lonely ODBC DSN pointing to the new database. Go to the system tools to examine said DSN. It's just not there. No such DSN is set up. WTF?

OK, so I guess it is some kind of 'stealth' or perhaps a 'ninja' ODBC DSN. I set up a non-ninja ODBC DSN pointing to the original database and change the registry setting to point to that. Start my engine. Fails. Error this time:
Quote:
Cannot open database connection - DSN=Metastorm1;UID=sa;PWD=**********; Reason: The specified DSN contains an architecture mismatch between the Driver and Application.


Excellent. So I look in the documentation to see what I should be setting it to, as the ninja setting can't be seen to compare with. How much reference is there to a DSN in the admin guide? These:
Quote:
Database parameters define how the process engine connects to the Metastorm database.  Two types of connection
are required:
 
•  ODBC, which uses a DSN that has already been set up using the ODBC Data Source Administrator.
•  OLE DB connection string.

Quote:
\SOFTWARE\Metastorm\e-
work\Engine\Database
Connection ODBC;
DSN=Metastorm;
UID=[DBUserName];
PWD=[DBUserPassword];


I see no reference to how to set up the DSN at all.

So now we have to dick with XML, 7 registry settings, and a 'ninja' DSN. All hail 'Progress', folks!

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #2 
OK, I found the 'ninja' ODBC, changed it, and the engine starts. The reason it was hidden is that wonderful wow6432node branch in the registry. Obviously stuff in there does not show up the ODBC editor, bit I have to wonder how you are supposed to edit them. Perhaps Microsoft have taken a leaf out of Metastorm's book and have 'improved' the user interface?

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #3 
Hah!

And then I have to change the admin services xml as well.

I forgot to mention that in Windows 7, you have to run the notepad 'as administrator' (even if you are one) just to edit these files (or you cannot save them), and in that mode, even drag & drop of files to the notepad does not work.

So far, that is two XML files, 7 registry settings, and a 'ninja' ODBC. (sung to the tune 'twelve days of Christmas', perhaps?)

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
Nappy

Avatar / Picture

Guru
Registered:
Posts: 1,087
Reply with quote  #4 
Sounds like they send seperate groups away to make parts of V9 and then mashed it all together. And they all had their own way to connect.

Next time it's probably faster to build a small tool that does all the changes.
Although i'm not sure what language you need to tackle the ninja ;)

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.

PS that's for V6/7 for V9 the problem is V9 at the moment ;)
0
greenej77

Member
Registered:
Posts: 19
Reply with quote  #5 
From your 'ninja' ODBC description, I'd guess you're running a 64-bit version of Windows.  For some reason Metastorm seems to use the 32-bit version of ODBC which can be viewed using Windows\SysWOW64\odbcad32.exe.

This won't help with the two XML files and 7 registry settings, but at least it'll let you update the ODBC connection.
0
Jerome

Avatar / Picture

Guru
Registered:
Posts: 5,507
Reply with quote  #6 
Thanks for that!

__________________
Post an example, and we will have a much better idea what the problem is. In about 90% of posts, the problem is one of communication. Examples bridge that gap.
0
kaan

Member
Registered:
Posts: 45
Reply with quote  #7 
Here is a consolidated list of components to update in case of a change in the database server/name:

FILES
- C:\Program Files\Metastorm\BPM\Administrative Tools\Service\Web.config
- C:\Program Files\Metastorm\BPM\Deployment\DeploymentService.exe.config

REGISTRY
- HKEY_LOCAL_MACHINE\SOFTWARE\Metastorm\e-work\Engine\Database
- 2 keys in HKEY_LOCAL_MACHINE\SOFTWARE\Metastorm\e-work\Engine\Database Connectors\Oracle DBC
- 2 keys in HKEY_LOCAL_MACHINE\SOFTWARE\Metastorm\e-work\Engine\Database Connectors\SQL Server DBC
- 2 keys in HKEY_LOCAL_MACHINE\SOFTWARE\Metastorm\e-work\InstallInfo

ODBC Connection

I hope this helps,
Kaan
0
PresuminEd

Avatar / Picture

Member
Registered:
Posts: 25
Reply with quote  #8 

Quote:
Originally Posted by kaan

REGISTRY

- HKEY_LOCAL_MACHINE\SOFTWARE\Metastorm\e-work\Engine\Database
- 2 keys in HKEY_LOCAL_MACHINE\SOFTWARE\Metastorm\e-work\Engine\Database Connectors\Oracle DBC
- 2 keys in HKEY_LOCAL_MACHINE\SOFTWARE\Metastorm\e-work\Engine\Database Connectors\SQL Server DBC

More accurately:

 

- 2 keys in HKEY_LOCAL_MACHINE\SOFTWARE\Metastorm\e-work\Engine\Database Connectors\Oracle DBC

 

OR

 

- 2 keys in HKEY_LOCAL_MACHINE\SOFTWARE\Metastorm\e-work\Engine\Database Connectors\SQL Server DBC

 

Depending on how the "Current" value is set here:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Metastorm\e-work\Engine\Database

 

Cheers,

Ed.

 


__________________
Any comments I make are mine alone, and do not necessarily reflect the views of my employer...May contain nuts...Open other side up...Contents may have settled during transportation...
0
JoeOmerta

Veteran
Registered:
Posts: 210
Reply with quote  #9 
I just moved sql servers and had to update the ODBC connections.  Everything went smoothly until the process engine wouldn't start, then i found this registry key...  HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI\Metastorm

It's a 64 bit server but it looks like the ODBC gui doesn't show the 64 bit strings like Jerome said above.  Not sure if this is the same key Jerome was talking about but figured i'd throw it in here for future reference if anyone gets the dreaded "ODBC database connection string points at different database to Database connector."
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:


Create your own forum with Website Toolbox!