Siebel Open UI, Tools, Scripting and EAI (MOSC)

MOSC Banner

Custom WfProcMgr for Custom AOM Due to Integration Workspace

edited Dec 20, 2019 2:36PM in Siebel Open UI, Tools, Scripting and EAI (MOSC) 4 commentsAnswered

We are in parallel development on 19.9 using Integration Workspace.  We have 2 sets of URLs pointing to custom AOMs which in turn are pointing to their respective Integration Workspaces.  Problem is that, since our code is not yet on the Main workspace, we cannot execute Workflow Process Manager as it does not recognize the changes that are still on the Int WS.

So partial solution, we cloned WfProcMgr to WfProcMgr1 and WfProcMgr2, each cloned version pointing to their corresponding Int WS.  Then on our BS Scripts, we point to their respective WfProcMgr flavor.  This approach works.

However, when we migrate to another environment where there's no Int WS, but only Main WS, we have to make sure that we point back to the original WfProcMgr.  This could be very risky as we might miss some script or what not.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center