To generate or stage follow-on releases of IBM
® Portal portals, configurations, and artifacts need to be moved between systems. ReleaseBuilder enables management of release configurations independent of user configurations.
Release configuration data are exported to XML files that can be imported using the XML configuration interface (XmlAccess). Using ReleaseBuilder it is possible to stage release configurations between two portals. This allows you to track which configuration entities were removed, added, or changed compared to the previous release generated from a given portal and to apply these differential updates to another portal. Detecting the differences between one configuration and another of the same portal server creates differential updates. A third configuration or "diff", generated by ReleaseBuilder, represents the changes made between the two configurations. The third configuration can be used to apply not only addition and update modifications but also deletions to the target server. This allows two portal servers, for example, a staging server and a production server, to remain in synch. ReleaseBuilder is designed to eliminate the need to generate complete XmlAccess exports to move a partial configuration or to manually create XML response files to export a partial configuration. ReleaseBuilder also helps to prevent the problem of configuration bloat on the target server.
For staging virtual portals, ReleaseBuilder supports a virtual portal mode that allows the generation of difference configurations for virtual portal scoped resources only. This mode allows you to stage virtual portals.
ReleaseBuilder is a configuration management tool. Do not use it for migration purposes.
Massively parallel portal configuration tasks, for example hundreds of administrators working in parallel, can affect the user experience and portal performance. Such tasks can be distributed to independent portal systems. ReleaseBuilder, together with the XML configuration interface, allows you to integrate the resulting configurations.
Parent topic: Administering
- ReleaseBuilder is installed when WebSphere Portal is installed along with the XML configuration interface. You can run ReleaseBuilder on the production server, although it can impact the WebSphere Portal performance.
- Unlike the XML configuration interface, ReleaseBuilder does not interact with the portal server runtime. You should run ReleaseBuilder on a separate, standalone machine. This system can be the staging system or a completely separate system where WebSphere Portal is installed.
- To maximize use of system resources, WebSphere Portal should not be running when executing ReleaseBuilder.
Checklist for ReleaseBuilder
Use these checklists to ensure that all required artifacts and configurations are moved when you prepare to deploy your portal.
Building a release
You can use ReleaseBuilder to compare the XML configuration files that describe your staging server (REV1) and your updated staging server (REV2), and to create an XML configuration file that contains the differences between the two servers. You can then use this output file to import only the differences from your staging server (REV2) onto the production server. Features that are unchanged from (REV1) on the staging server (REV2) are not affected by the import.
Building a Release for virtual portal installations
For staging virtual portals you use ReleaseBuilder with a slightly different procedure. The instructions given here prevent redundant updates of the resources shared between the virtual portals and prevent update conflicts of virtual portal scoped resources.