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
- To implement the bug fix, make the new version of the application
available to users of the platform.
- 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.
- In the application descriptor editor, click the Make Available button on the Overview tab.
- 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.
- 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.
- Optional: Back out the bug fix by making the
new version of the application unavailable again.
- In the CICS Cloud perspective in CICS Explorer®, open the new version
of the application in the application descriptor editor.
- Click the Make Unavailable button
on the Overview tab.
- Click OK to make the application
version unavailable.
- 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.
- 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.
- 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.
- 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.
- In the Cloud Explorer view, locate the older version
of the installed application in either the Platform hierarchy or the
Application hierarchy.
- Right-click the application name and click Make Unavailable, then click OK to make the older version of the application unavailable.
- Refresh the Cloud Explorer view, and check that the
status of the older version of the application is now displayed as
ENABLED, UNAVAILABLE.
- Right-click the application name and click Disable, then click OK to disable
the older version of the application.
- 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.