The best practice for upgrading a PAS for OpenEdge instance is to create a new instance that is based on OpenEdge Release 12, and to merge changed files into that new instance. You then take the old instance out of service. Note that if the new instance is configured with the same port number as the old instance, then you must stop the old instance before you are able to start the new one.

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

  1. Create a new PAS for OpenEdge instance by entering the following command:

    pasman create

    This command creates a default ABL application that uses the ROOT web application.

  2. Deploy upgraded web applications by entering the following command. If you are not using the PAS for OpenEdge instance name as the default ABL application name, then make sure that you specify the ABL application name correctly.

    tcman deploy

  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 that are specified in the /path-to-old-instance/ablapps/abl-app-name/conf/oeablSecurity.properties file into the /path-to-new-instance/ablapps/abl-app-name/conf/oeablSecurity.properties file.
    3. Copy ABL application lifecycle scripts from the /path-to-old-instance/bin directory to the /path-to-the-new-instance/bin directory. 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 the /path-to-old-instance/bin directory to the /path-to-the-new-instance/bin directory. This includes the your-name_setenv.{bat|sh} script.
    5. Copy or merge any other product shell scripts in the /path-to-old-instance/bin directory to the /path-to-new-instance/bin directory.
    6. Copy any source or rcode file from the /path-to-old-instance directory to the /path-to-new-instance directory.
    7. Copy any other installation- or application-specific folders from the /path-to-old-instance directory to the /path-to-new-instance directory.
  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 entering the following command:

      /path-to-old-instance/bin/tcman.{bat|sh} feature

    2. Make any changes by entering the following command:

      /path-to-new-instance/bin/tcman.{bat|sh} feature feature-name={on|off}

  6. Make sure the ROOT web application is not in use, and then remove it by entering the following command:

    tcman undeploy ROOT

    A best practice is to 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.