is part of Professional services group of IBM/Kenexa, based out of IBM Visakha Hills Lab in Visakhapatnam. He was earlier part of WebSphere development at IBM India Software Labs in Bangalore. Prior to this, he was a consultant at WebSphere BPM Practice. He is a Certified SOA Solution Designer(2007), Certified SOA Associate, co-author of WebSphere InterChange Server Migration Scenarios redbook. He is Member, Board of Studies, Dept of CSE, College of Engineering, Andhra University. He blogs here and tweets, sharing his Social Experience, as the scroll of Life unrolls in the Eternal Enterprise!
Couple of days back, I got a query from my customer on how to re-configure BPC in WPS (v6.1.2). The reason to do is at the time of profile creation the embedded derby database was used for the BPEDB. As its not a scalable DB, we had to point to another DB, Oracle in this case. Though this won't be a regular scenario, thought it would be helpful to point the same here. Even this might be useful when there is a change in DB vendor in your location and want to migrate to a new DB. Here are the steps:
First you need to stop and undeploy all your business process and human task applications.
Then run this nice bpeunconfig.jacl
under (WPS_install_dir)\ProcessChoreographer\config. More on the same in WPS infocenter
After successful running of the script (which undeploys the BPC related apps and resources), re-start the server and BPC is now available for new/fresh configuration.