Verifying the solution

Make the new version of the application available, and run the transaction for the application to verify that the new version of the application is now provided to the user. Then experiment with backing out the new version of the application. When you have verified the solution, make the older version of the application unavailable, and disable it.

Procedure

  1. To implement the bug fix, make the new version of the application available to users of the platform.
    1. In the Cloud Explorer view, double-click the application name for the new version of the application, to open the application in the application descriptor editor.
    2. In the application descriptor editor, click the Make Available button on the Overview tab.
    3. Click OK to make the application version available.
    Refresh the Cloud Explorer view, and check that the status of the new version of the application is displayed as ENABLED, AVAILABLE. If the status of the new version of the application has not changed to AVAILABLE, follow the troubleshooting procedure in Diagnosing application errors.
  2. In a CICS® terminal, enter the name of the transaction that you created for the application, and confirm that the output from the application includes the bug fix. The older version of the application is still available on the platform, but the user is provided with the new version when they run the transaction. With multi-versioned applications, by default, CICS provides callers with the highest version of the application that you have made available on the platform.
  3. Optional: Back out the bug fix by making the new version of the application unavailable again.
    1. In the CICS Cloud perspective in CICS Explorer®, open the new version of the application in the application descriptor editor.
    2. Click the Make Unavailable button on the Overview tab.
    3. Click OK to make the application version unavailable.
    4. Refresh the Cloud Explorer view, and check that the status of the new version of the application is now displayed as ENABLED, UNAVAILABLE.
    The Make Unavailable action operates on the application entry points. The application entry point that is declared for the PROGRAM resource in your application controls users' access to the application, so you do not need to disable or discard alternative versions of the application to prevent users from accessing them.
  4. Optional: In a CICS terminal, enter the name of the transaction that you created for the application, and confirm that the user is provided with the older version of the application, without the bug fix.
  5. Optional: Reinstate the new version of the application by making it available again, and run the transaction in a CICS terminal to verify the output.
  6. Optional: Make the older version of the application unavailable to users, then disable it. As the older version of the application is defective, it is appropriate to disable it after the new version has been verified, because it is unlikely to be required again. You can perform these actions in the Cloud Explorer view, as well as in the application descriptor editor.
    1. In the Cloud Explorer view, locate the older version of the installed application in either the Platform hierarchy or the Application hierarchy.
    2. Right-click the application name and click Make Unavailable, then click OK to make the older version of the application unavailable.
    3. Refresh the Cloud Explorer view, and check that the status of the older version of the application is now displayed as ENABLED, UNAVAILABLE.
    4. Right-click the application name and click Disable, then click OK to disable the older version of the application.
    5. Refresh the Cloud Explorer view, and check that the status of the older version of the application is now displayed as DISABLED, UNAVAILABLE.

Results

You have now demonstrated and verified that you can deploy a new version of an application to a platform without the need to disable or remove the previous version beforehand, and can make the new version of the application available to users without service interruption.


verify.html | Timestamp icon Last updated: Sunday, 4 June 2017