About ReleaseBuilder
Use ReleaseBuilder to stage release configurations between two portals.
ReleaseBuilder 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. A "diff", generated by ReleaseBuilder, represents the changes made between the two configurations, and can be used to apply additions, update, and deletes to the target server, allowing two portal servers, for example, a staging server and a production server, to remain in synch.
Prerequisites
- Recent technotes for XML access and Release Builder
Limitations...
- Access control settings for policies are exported only for the main policy definition (the root policy node). Access control settings for child policy definitions (policy sub-nodes) are not exported.
- The policy sub-nodes are stored in a separate file. This file can be referenced by an XML script and that link can be exported.
- The ReleaseBuilder does not support policies for portal resources.
ReleaseBuilder is a configuration management tool. Do not use it for migration purposes.
Performance benefits
Massively parallel portal configuration tasks, for example hundreds of administrators working in parallel, can impact 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.
ReleaseBuilder synopsis
The ReleaseBuilder command...releasebuilder.sh -inOld oldReleaseConfiguration -inNew newReleaseConfiguration -out output_file
...where...
-inOld oldReleaseConfiguration First of the two XML configuration files to compare. Generated using xmlaccess. -inNew newReleaseConfiguration Second of the two XML configuration files to compare. Generated using xmlaccess. -out output file File in which the differential output should be written. If not specified, the differential output will be written to the System console. The output file parameter must be an absolute or relative path of an accessible XML configuration file. The file does not need to exist. If it does not exist, it will be created. If it does exist, the existing information in the file will be overwritten.
Examples
To generate the differences file containing the additions and subtractions configuration file, enter;
./releasebuilder.sh -inOld stageConfigR1.xml -inNew stageConfigR2.xml -out diff.xml
The diff.xml file will contain the additions and deletions to be imported onto the production portal server.
Unlike the XML configuration interface, ReleaseBuilder does not interact with the portal server runtime.
See also:
Parent topic:
Installing WebSphere Portal