Purge orders before un-deploying a cartridge in Design Studio
edited Jan 10, 2013 3:59PM in Order and Service Management (Communications Industry) (MOSC) 7 commentsAnswered
Un-deploying a cartridge has three operations -1. Delete orders from OSM schema of the to-be-undeployed cartridge
2. Delete model data from OSM schema of the to-be-undeployed cartridge
3. Remove the plugin executables of the to-be-undeployed cartridge from WebLogic server
In order to speed up cartridge undeploying, we can do the action 1 separately by using OSM SDK tool orderPurge.bat,
this is how to do it -
1. Go to this directory osm7.0.3\SDK\XMLImportExport\config
rename file config_sample.xml as config.xml
2. Open config.xml file and modify the following so your OSM schema will be pointed
<databaseConnection>
<user>ordermgmt</user>
<password>ordermgmt</password>
2. Delete model data from OSM schema of the to-be-undeployed cartridge
3. Remove the plugin executables of the to-be-undeployed cartridge from WebLogic server
In order to speed up cartridge undeploying, we can do the action 1 separately by using OSM SDK tool orderPurge.bat,
this is how to do it -
1. Go to this directory osm7.0.3\SDK\XMLImportExport\config
rename file config_sample.xml as config.xml
2. Open config.xml file and modify the following so your OSM schema will be pointed
<databaseConnection>
<user>ordermgmt</user>
<password>ordermgmt</password>
0