Been there, done that. The problem isn't cross talk across databases, it is the file path being shared between the two. Here are the details from Epicor:
The default Vantage install is such that any BPM method directives apply to ALL Vantage DBs on the server.
This means that if you develop a BPM in the TEST database, once enabled it will apply and run in the LIVE and TRAIN databases as well. It will therefore cause problems if you want to test BPMs while developing them, or if you are running several databases, each with different BPM requirements.
To enable BPM to apply to one particular DB, you need to set up the Appservers to have unique BPM folders in their PROPATH.
The steps below explain how to change the Train DB to use a different BPM folder.
1. In Progress Explorer, right click on the MFGTRAIN803 Appserver.
2. Select Properties
3. Click on Agent ' General
4. The PROPATH should be similar to the following: "E:\epicor\mfgsys803\custom,E:\epicor\mfgsys803\bpm,:\epicor\mfgsys803\Server\custom,E:\epicor\mfgsys803\Server,E:\epicor\mfgsys803"
5. Change the BPM element of this to a unique path i.e. "E:\epicor\mfgsys803\custom,E:\epicor\mfgsys803\TRAIN\bpm,:\epicor\mfgsys803\Server\custom,E:\epicor\mfgsys803\Server,E:\epicor\mfgsys803"
N.B. It is IMPERATIVE that the path ends in "BPM"
6. Repeat Steps 2 - 5 for the MFGTRAIN803ProcessServer and MFGTRAIN803TaskAgent
7. From Windows Explorer, create the directory specified in this instance "E:\epicor\mfgsys803\TRAIN\bpm"
8. Restart the Appservers. Users will need to be logged off for this.
9. Resave any BPMs created in the Train DB.
Background
When building a BPM method directive, data is stored in the Vantage DB. When a BPM directive is enabled and saved, the data is processed and a Progress program is generated to disk. The program is generated into the directory specified in the Appserver's PROPATH (folder ending in BPM). When Business Object methods are called via Web Services or a Vantage client, any BPM directives which exist for this method are located first in the propath and are therefore executed prior to base Business Object methods.
________________________________
From: andrew.tapper <atapper@...>
To: vantage@yahoogroups.com
Sent: Tuesday, December 16, 2008 12:22:13 PM
Subject: [Vantage] BPM Cross Talk between databases
Has anyone else experienced BPM methods used in a test database having
effects on methods used in the live database? Specifically I have BPMs
sending emails in both databases and if I change one in test, it screws
up the live one. (V8.03.405A)
Could it have something to do with the Method Groups? The group thing
is another one of those Vantage "features" that doesn't seem to be
completly documented in what it is or does.
Andrew
[Non-text portions of this message have been removed]
The default Vantage install is such that any BPM method directives apply to ALL Vantage DBs on the server.
This means that if you develop a BPM in the TEST database, once enabled it will apply and run in the LIVE and TRAIN databases as well. It will therefore cause problems if you want to test BPMs while developing them, or if you are running several databases, each with different BPM requirements.
To enable BPM to apply to one particular DB, you need to set up the Appservers to have unique BPM folders in their PROPATH.
The steps below explain how to change the Train DB to use a different BPM folder.
1. In Progress Explorer, right click on the MFGTRAIN803 Appserver.
2. Select Properties
3. Click on Agent ' General
4. The PROPATH should be similar to the following: "E:\epicor\mfgsys803\custom,E:\epicor\mfgsys803\bpm,:\epicor\mfgsys803\Server\custom,E:\epicor\mfgsys803\Server,E:\epicor\mfgsys803"
5. Change the BPM element of this to a unique path i.e. "E:\epicor\mfgsys803\custom,E:\epicor\mfgsys803\TRAIN\bpm,:\epicor\mfgsys803\Server\custom,E:\epicor\mfgsys803\Server,E:\epicor\mfgsys803"
N.B. It is IMPERATIVE that the path ends in "BPM"
6. Repeat Steps 2 - 5 for the MFGTRAIN803ProcessServer and MFGTRAIN803TaskAgent
7. From Windows Explorer, create the directory specified in this instance "E:\epicor\mfgsys803\TRAIN\bpm"
8. Restart the Appservers. Users will need to be logged off for this.
9. Resave any BPMs created in the Train DB.
Background
When building a BPM method directive, data is stored in the Vantage DB. When a BPM directive is enabled and saved, the data is processed and a Progress program is generated to disk. The program is generated into the directory specified in the Appserver's PROPATH (folder ending in BPM). When Business Object methods are called via Web Services or a Vantage client, any BPM directives which exist for this method are located first in the propath and are therefore executed prior to base Business Object methods.
________________________________
From: andrew.tapper <atapper@...>
To: vantage@yahoogroups.com
Sent: Tuesday, December 16, 2008 12:22:13 PM
Subject: [Vantage] BPM Cross Talk between databases
Has anyone else experienced BPM methods used in a test database having
effects on methods used in the live database? Specifically I have BPMs
sending emails in both databases and if I change one in test, it screws
up the live one. (V8.03.405A)
Could it have something to do with the Method Groups? The group thing
is another one of those Vantage "features" that doesn't seem to be
completly documented in what it is or does.
Andrew
[Non-text portions of this message have been removed]