Try OpenEdge Now
skip to main content
Installation and Configuration
Installation : Performing an OpenEdge Installation in Windows : Running the Progress Dynamics Configuration Utility : Editing the Progress Dynamics XML configuration file
Editing the Progress Dynamics XML configuration file
The DCU upgrade process is not complete at this point. The DCU must run again to apply other upgrade procedures and to update data sets for the newly created icfdb. The DCU automatically runs again when you start an administrative session. But before you can log in and start an administrative session, you must have an XML configuration file that is compatible with the newer version of Progress Dynamics.
If you did not create a new icfconfig.xml file (or edit the default) for your application, you can skip this section. You can simply use the standard OpenEdge-install-dir\gui\dynamics\icfconfig.xml file that ships with Progress Dynamics to access the upgraded Repository.
However, if you modified or changed the name of the default XML configuration file (for example, you might have a customized XML configuration file in your current directory), you must edit the XML configuration file to make it compatible with your upgraded application. For example, you must add service entries for the new managers, and change the connection parameters for your icfdb database.
You should only edit the icfconfig.xml file for the session type that you use as your administrative session type. This allows you to connect to your Repository with administration privileges. Then you can use the Dynamics Administration tool's Session menu options to modify your other session types and regenerate the icfconfig.xml file.
To edit your icfconfig.xml file:
1. Create a backup copy of icfconfig.xml before you edit it.
Caution: If you make a mistake in the following steps, you might render your icfconfig.xml file unreadable and your Progress Dynamics session might not start. Therefore, creating a backup copy that you can revert to is extremely important.
2. Open your icfconfig.xml file in a simple text editor, such as Notepad.
3. Search for the string: SessionType=ICFDev where ICFDev is the name of the session type that you use for administration tasks. This string should occur inside a session node as follows:
<session SessionType=ICFDev>
Immediately following the <session> node is a <properties> node.
4. Scan down the file until you pass the end of the properties node, which is denoted by the end properties tag (</properties>).
Immediately following the <properties> node is a <services> node. The <services> node contains the list of services that should be connected when the session starts. Among them is a <service> node for each of the databases and AppServers that are connected to this session. Each </service> node is contained within a start <service> and end </service> tag.
5. Search for a <cServiceName> tag with the value rvdb.
If it exists, remove the entire <service> node for the RVDB service type from the file.
The rvdb database was used in Progress Dynamics Version 1.1A. It became obsolete in Version 2.0A. There should be no references to it in any of your configuration files.
6. Scan down until you find the first end managers (</managers>) tag.
7. Insert the following XML statements immediately before the line noted in Step 6 of this procedure:
8. Scan down until you find a </service> node that contains a <cServiceName> tag with the value icfdb.
9. Change the database connection parameters from the values for the earlier version to the appropriate values for the newer version.
The arguments for the -db and the -S parameters should be the icfdb that you upgraded through the DCU.
The bold text in the following example shows the changes to the icfdb services entry:
  <cConnectParams>-db icfdbV21A -N TCP -H localhost
  -S icfdbV21A</cConnectParams>
Since the upgrade simultaneously opens a large number of records, it is possible that you might get an error stating that the record lock table is too small. In that case, you must set the Lock Table Entries parameter (-L) to a very large value. (A value of 500,000 should be adequate.) See OpenEdge Deployment: Startup Command and Parameter Reference for more information.
10. Save the edited icfconfig.xml file.
11. Place the icfconfig.xml file in a directory that is included in your PROPATH.