Staging subsequent portal solution releases


A subsequent solution release is staged from the integration to the staging and to the production system. The physical implementation of configuration staging through a series of systems does not really move these configurations between systems. This process is based on repeatable modifications of portal solution releases on multiple systems. For each solution release, a differential portal solution configuration is imported into the system, artifacts are managed manually by manual updates and deletions.

The following process is an example of a possible subsequent portal solution staging process. Derivations of this process are possible and expected. It focuses on configuration and artifact management.

 

Staging System

Process:

Prerequisite: Previous portal solution release (X) is installed on the staging system. The new portal solution release (Y) is available in the VCS.

Portal Operator: Check out all artifacts, including administrative portlets, for the new portal solution release from the VCS.
Portal Operator: Install new artifacts to the staging system. For portlet installation use the XML configuration interface export of all portlets.
Portal Operator: Update the modified artifacts on the staging system For portlet installation use the XML configuration interface export of all portlets.
Portal Operator: Uninstall/delete the discontinued artifacts from the staging system.
Portal Operator: Check out the description of the global settings and configurations for the new portal solution release from the VCS.
Portal Operator: Apply the portal global settings and configurations changes, as highlighted by release manager, to the staging system.
Portal Operator: Check out all of the differential portal solution configurations for the new portal solution release from the VCS.
Portal Operator: Import the differential configurations into the staging system using the XML configuration interface. Preserve the object IDs.
Test Team: Perform system, load, and acceptance tests of the release on the the staging system.

Result: The new portal solution release is available on the staging system and tested.

 

Alternative flow:

If administrator user IDs or group IDs are different on the staging system and the integration system, step 8 is replaced with steps 8.a to 8.c.

Portal Operator: Replace all user IDs and group IDs used on the integration system with corresponding IDs for the staging system in the differential portal solution configuration file.

Portal Operator: Deliver the resulting file into the VCS.

Portal Operator: Import configurations into the staging system using the XML configuration interface. Preserve the object IDs.

 

Production System

Process:

Prerequisite: The previous portal solution release (X) is installed on the production system. The new portal solution release (Y) is available in the VCS. Release has successfully passed tests on the staging system.

Portal Operator: Backup the production system (data base and file system).
Portal Operator: Check out all the artifacts, including the administrative portlets, for the new portal solution release from the VCS.
Portal Operator: Install the new artifacts to the production system. For portlet installation use the XML configuration interface export of all portlets.
Portal Operator: Update the modified artifacts on the production system. For portlet installation use the XML configuration interface export of all portlets.
Portal Operator:Uninstall/delete the discontinued artifacts from the production system.
Portal Operator: Check out the description of the global settings and configurations for the new portal solution release from the VCS.
Portal Operator: Apply the portal global settings and configurations changes, as highlighted by release manager, to the production system.
Portal Operator: Check out all the differential portal solution configurations for the new portal solution release from the VCS.
Portal Operator: Import the differential configurations into the production system using the XML configuration interface. Preserve the object IDs.
Portal Operator: Backup the production system (data base and file system).
Test Team: Perform regression tests of the release on the production system.
Portal User: Use the portal solution and customize the portal configuration, creating user data.
>

Result: The new portal solution release is available on the production system and tested.

Alternative flow:

9. If administrator user IDs or group IDs are different on the staging system and the integration system, step 9 is replaced with steps 9.a to 9.c.

9.a. Portal Operator: Replace all user IDs and group IDs used on the integration system with the corresponding IDs for the staging system in the differential portal solution configuration file.

9.b. Portal Operator: Deliver the resulting file into the VCS.

9.c. Portal Operator: Import the configurations into the staging system using the XML configuration interface. Preserve the object IDs.

 

See also

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.