The best practice for upgrading a Progress Application Server (PAS) for OpenEdge instance is to create a new instance based on OpenEdge Release 13 and merge changed files into the new instance. After migration, take the old instance out of service.
Note: If the new instance uses the same port number as the old instance, stop the old instance before starting the new one.

To upgrade a PAS for OpenEdge instance, perform the following steps:

  1. Create a new PAS for OpenEdge instance by running the following command:
    pasman create
    This command creates a default ABL application that uses the ROOT web application.
  2. Deploy upgraded web applications by running the following command.
    tcman deploy
    If you are not using the PAS for OpenEdge instance name as the default ABL application name, specify the ABL application name correctly.
  3. Copy files from the old PAS for OpenEdge instance to the new instance, as follows:
    1. Copy any files and folders in all of the ablapps/abl-app-name directories, excluding the conf/oeablSecurity.properties file.
    2. Merge properties from /path-to-old-instance/ablapps/abl-app-name/conf/oeablSecurity.properties into /path-to-new-instance/ablapps/abl-app-name/conf/oeablSecurity.properties.
    3. Copy ABL application lifecycle scripts from /path-to-old-instance/bin to /path-to-the-new-instance/bin.

      This includes the following:

      • abl-app-name_setup.{bat|sh}
      • abl-app-name_startup.{bat|sh}
      • abl-app-name_started.{bat|sh}
      • abl-app-name_shutdown.{bat|sh}
    4. Copy product OS environment variable setup scripts from /path-to-old-instance/bin to /path-to-the-new-instance/bin.

      This includes the your-name_setenv.{bat|sh} script.

    5. Copy or merge any other product shell scripts in /path-to-old-instance/bin to /path-to-new-instance/bin.
    6. Copy any source or rcode file from /path-to-old-instance to /path-to-new-instance.
    7. Copy any other installation or application-specific folders from /path-to-old-instance to /path-to-new-instance.
  4. Merge properties from the older instance into the new, as follows:
    1. For OpenEdge-specific properties, use the following command:
      /path-to-new-instance/bin/oeprop -f /path-to-old-instance/conf/openedge.properties
    2. Merge any other properties file using a text merge tool.
  5. Merge PAS for OpenEdge features from the old instance to the new, as follows:
    1. Obtain the feature configuration by running the following command:
      /path-to-old-instance/bin/tcman.{bat|sh} feature
    2. Make any changes by running the following command:
      /path-to-new-instance/bin/tcman.{bat|sh} feature feature-name={on|off}
  6. Ensure the ROOT web application is not in use, then run the following command:
    tcman undeploy root
    Note: As a best practice, replace the ROOT web application with an empty or blank Java web application that satisfies Tomcat’s default web application context lookup.
  7. Test the PAS for OpenEdge instance before adding it to your production environment.