![]() If you are upgrading from a version of OSM higher than 7.0, delete the OSM WebLogic Server application components (including oms.ear and cartridge_management_ws.ear) and any automation plug-in. Stop the OSM WebLogic application component oms.ear using the WebLogic console, and then delete the oms.ear file. Archive the WLS_home directory as well if it is not located in the MW_home directory. If you are upgrading the existing OSM 7.2 WebLogic domain, archive the MW_home directory including all subdirectories. If you are creating a new WebLogic domain, back up the existing WebLogic server domain directory, custom SDK files, and scripts to a directory outside of your OSM installation. The OSM installer cannot rectify this problem on its own. The OSM installer stops the OSM schema upgrade if it encounters any issues. ![]() Upgrade and redeploy cartridges to the OSM 7.4.1 serverįor current version and patch information, see OSM Compatibility Matrix. ![]() Upgrade the development environment, including Oracle Communications Design Studio, Ant, GraphViz, OSM SDK, and OSM Tools The post upgrade process includes these tasks: Upgrade the Oracle Database (if applicable) Upgrade or create a new WebLogic domain (if applicable) Upgrade the Oracle WebLogic Server core software (if applicable) Gather a list of components installed in your current OSM systemÄocument the configuration selections made when installing your current OSM system The upgrade process includes these tasks: Implementing and testing the upgrade on the production system Implementing and testing the upgrade on a development system Upgrading OSM consists of the following process:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |