problem solved. If anyone is interested, here is the solution:
PROBLEM DESCRIPTION:
BPM directives in test database are also being triggered in live environment.
Â
RESOLUTION:
BPM is looking for the \Epicor\mfgsys803\BPM folder by default. The Appservers' (mfgsys803, mfgtrain803,
mfgtest803, mfgpilot803) PROPATH are all looking to this folder for writing AND reading of the directives.
This causes a problem since the Test database will write BPM's to the same folder that the Live database
reads BPM's from.
Â
In order to change this You will want to create sub folders under \epicor\mfgsys803 to use for non-live BPM's. For instance: \Epicor\mfgsys803\TestBPM\BPM or \Epicor\mfgsys803\TrainBPM\BPM etc...
Â
! Note: It is important that the sub folder you create also has a folder within named 'BPM' specifically.
Â
We will then need to edit the PROPATH of each Appserver that you will look to separate out.
1) Open the Progress Explorer Tool
2) Navigate to Appserver and then Mfgtest803 and right click and click properties
3) In the left Tree view, click on Agent
4) Inside the PROPATH textbox you will find something similar to: C:\Epicor\mfgsys803\bpm
5) Change this entry to C:\Epicor\mfgsys803\TestBPM\BPM
Â
Everything else in the PROPATH can stay the same.
Â
The Appservers will need to be restarted for this to take effect.
Â
From this point onward all BPM's created/saved while connected to the Test slot will be put in this folder
and they won't be seen by the other databases.
----- Original Message ----
From: Dave Pfiester <dpfiester@...>
To: vantage@yahoogroups.com
Sent: Thursday, October 16, 2008 4:16:48 PM
Subject: [Vantage] Re: BPM 8.03.406
PROBLEM DESCRIPTION:
BPM directives in test database are also being triggered in live environment.
Â
RESOLUTION:
BPM is looking for the \Epicor\mfgsys803\BPM folder by default. The Appservers' (mfgsys803, mfgtrain803,
mfgtest803, mfgpilot803) PROPATH are all looking to this folder for writing AND reading of the directives.
This causes a problem since the Test database will write BPM's to the same folder that the Live database
reads BPM's from.
Â
In order to change this You will want to create sub folders under \epicor\mfgsys803 to use for non-live BPM's. For instance: \Epicor\mfgsys803\TestBPM\BPM or \Epicor\mfgsys803\TrainBPM\BPM etc...
Â
! Note: It is important that the sub folder you create also has a folder within named 'BPM' specifically.
Â
We will then need to edit the PROPATH of each Appserver that you will look to separate out.
1) Open the Progress Explorer Tool
2) Navigate to Appserver and then Mfgtest803 and right click and click properties
3) In the left Tree view, click on Agent
4) Inside the PROPATH textbox you will find something similar to: C:\Epicor\mfgsys803\bpm
5) Change this entry to C:\Epicor\mfgsys803\TestBPM\BPM
Â
Everything else in the PROPATH can stay the same.
Â
The Appservers will need to be restarted for this to take effect.
Â
From this point onward all BPM's created/saved while connected to the Test slot will be put in this folder
and they won't be seen by the other databases.
----- Original Message ----
From: Dave Pfiester <dpfiester@...>
To: vantage@yahoogroups.com
Sent: Thursday, October 16, 2008 4:16:48 PM
Subject: [Vantage] Re: BPM 8.03.406
--- In vantage@yahoogroups .com, "sgotschall" <sgotschall@ ...> wrote:
>
> Has anyone seen a BPM from one database get triggered by a different
> database?
>
> I am in our Pilot database which has no BPMs. When I enter a new
part,
> a part.update bpm is being triggered from our test database causing a
> popup message to occur in pilot. Very strange.
>
> Vantage 8.03.406
>
> Steven
>
Steve,
I once had this problem and I found that my BPM's that were in the BPM
folder on the Vantage server also fired in my other databases as well.
Are you running on Progress?
David
[Non-text portions of this message have been removed]