Kbase P158563: Can OpenExplorer configurations be migrated to newer versions of OpenEdge Explorer?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/20/2010 |
|
Status: Unverified
GOAL:
Can OpenEdge Explorer configurations be migrated to newer versions of OpenEdge Explorer?
GOAL:
Can OpenEdge Explorer 10.2A be migrated to OpenEdge Explorer 10.2B?
GOAL:
Can OpenEdge Explorer 10.2A be upgraded to OpenEdge Explorer 10.2B?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
FIX:
There is no update option on the installation of OpenEdge Explorer install. However, it is possible to migrate the previous OpenEdge Explorer configuration to the Newer Release.
When transitioning from OpenEdge Explorer to a newer version of OpenEdge Explorer, the following must hold true for this process to work.
The older version files mentioned below, must be available either from an existing install or from backup files that were taken and the new version of OpenEdge and OpenEdge Explorer must be installed.
To migrate from an older version of OpenEdge Explorer like 10.2A to a new version of OpenEdge explorer do the following:
1. After installing the New OpenEdge Explorer release, shut down the AdminServer and backup the OpenEdge $DLC/properties folder.
2. For managed databases copy the conmgr.properties file from current-version $DLC/properties directory to the new OpenEdge $DLC/properties folder to move all managed databases to the new installation for OpenEdge.
3. For scripted databases copy the smdatabase.properties from current-version $DLC/properties directory to the new $DLC/properties folder to move all local scripted databases to the new installation for OpenEdge.
4. Copy the ubroker.properties file from the current-version $DLC/properties directory to the new $DLC/properties folder to move all associated resources to the new installation for OpenEdge.
5. Any port changes made to the OpenEdge $DLC/AdminServerPlugins.properties for the AdminServer should be made to the manually to the new version if changes are required (not using default ports for the AdminServer).
6. Start the AdminServer.
7. Start the OpenEdge Explorer, if autostart is not set.