BPM's firing across databases

That seems like the definite problem, however I'm getting an error.
I did restart all the agents as well on the test server.

Our paths were:
e:\epicor\mfgsys803\custom,e:\epicor\mfgsys803\bpm,e:\epicor\mfgsys803
\Server\custom,e:\epicor\mfgsys803\Server,e:\epicor\mfgsys803

I simply changed the the "bpm" part to be "bpmtest" and created that
folder and copied the contents of the old bpm folder into the new one.

Now when I go into test and double click the method directive to open
the BPM's I get the following error.

The following application error was encountered:

Server configuration is incorrect.

Path to BPM directory is missing from the PROPATH environment
variable.

If you have no idea, I can take it up with Epicor.


--- In vantage@yahoogroups.com, "Mark Wonsil" <mark_wonsil@...> wrote:
>
> > We're running 8.03.404D, and wondering if anyone has seen this
issue?
> >
> > After I restore our live database to the test server, the BPM's
that
> > fire on the live database execute the code that's in the BPM's on
the
> > test server.
>
> Yes, we have experienced this and Epicor has a work-around. The
trouble is
> they designed BPM with a single company code in mind and not
thinking that
> people would copy live databases to test and the company field will
be
> duplicated across multiple databases.
>
> The fix is in the ProPath for each appServer's agent. Each
appServer/agent has
> a propath where it picks up which assembly to execute. The levels
usually look
> like:
>
> Mfgsys803\custom
> MfgSys803\BPM
> MfgSys803\Server\Custom
> MfgSys803\Server
> MfgSys803
>
> Since there is only one BPM folder and the two databases share the
same
> company ID, there's no way for Vantage to know which code object to
run.
>
> Epicor suggested that we create multiple BPM code folders and then
change the
> appServer PROPATH property (Agent|General) so the BPM folder for
Test was
> different than the live database.
>
> So create a folder called MfgSys803\BPMTest and then modify the
Agent
> properties for the three appServers in test to look like this:
>
> Mfgsys803\custom
> MfgSys803\BPMTest
> MfgSys803\Server\Custom
> MfgSys803\Server
> MfgSys803
>
> The same logic is true for any Super Business Objects as well,
which are
> stored in the Custom folder. I think that Epicor is trying to push
people away
> from Super Objects and towards BPM.
>
> Mark W.
>
We're running 8.03.404D, and wondering if anyone has seen this issue?

After I restore our live database to the test server, the BPM's that
fire on the live database execute the code that's in the BPM's on the
test server.

Example, I have a post-process BPM defined on RMAProc.Update that sends
an email notifying someone that a RMA changed. The email subject has a
prefix of either LIVE- or TEST- based on what server it comes from.

After the restore, changes made on the live database are sending the
email template from the TEST server. The system agent ports are all
correct, etc. Kinda stumped.
> We're running 8.03.404D, and wondering if anyone has seen this issue?
>
> After I restore our live database to the test server, the BPM's that
> fire on the live database execute the code that's in the BPM's on the
> test server.

Yes, we have experienced this and Epicor has a work-around. The trouble is
they designed BPM with a single company code in mind and not thinking that
people would copy live databases to test and the company field will be
duplicated across multiple databases.

The fix is in the ProPath for each appServer's agent. Each appServer/agent has
a propath where it picks up which assembly to execute. The levels usually look
like:

Mfgsys803\custom
MfgSys803\BPM
MfgSys803\Server\Custom
MfgSys803\Server
MfgSys803

Since there is only one BPM folder and the two databases share the same
company ID, there's no way for Vantage to know which code object to run.

Epicor suggested that we create multiple BPM code folders and then change the
appServer PROPATH property (Agent|General) so the BPM folder for Test was
different than the live database.

So create a folder called MfgSys803\BPMTest and then modify the Agent
properties for the three appServers in test to look like this:

Mfgsys803\custom
MfgSys803\BPMTest
MfgSys803\Server\Custom
MfgSys803\Server
MfgSys803

The same logic is true for any Super Business Objects as well, which are
stored in the Custom folder. I think that Epicor is trying to push people away
from Super Objects and towards BPM.

Mark W.