About ReleaseBuilder

 

+

Search Tips   |   Advanced Search

 

ReleaseBuilder generates differential update files which can be used to apply only additions, modifications, and deletions between portal instances. ReleaseBuilder operates against XML configuration interface export files.

ReleaseBuilder is a configuration management tool. It should not be used for migration purposes.

ReleaseBuilder is located in...

PortalServer/bin

Syntax is...

releasebuilder -inOld old.xml -inNew new.xml -out diff.xml

...where...

• inOld

  First of the two XML configuration files to compare. File must exist and have been generated by the XML configuration interface command.

• inNew

  Second of the two XML configuration files to compare. File must exist and have been generated by the XML configuration interface command.

• out

  File in which the differential output should be written. If not specified, the differential output will be written to the System console.

Examples

To generate the differences file containing the additions and subtractions configuration file, enter;

./releasebuilder.sh -inOld stagingserverREV1_config.xml -inNew stagingserverREV2_config.xml -out outputfile.xml

The resulting output configuration file will contain the additions and deletions to be imported onto the production portal server.

ReleaseBuilder is installed during WebSphere Portal installation along with the XML configuration interface. It can be run on the production server, although doing so impacts performance of WebSphere Portal

Unlike the XML configuration interface, ReleaseBuilder does not interact with the portal server runtime. IBM recommends that ReleaseBuilder be run on a separate, standalone machine. This system can be the staging system, or a completely separate system on which WebSphere Portal is installed

To maximize use of system resources, WebSphere Portal should not be running during ReleaseBuilder execution.

• Manual steps prior to using ReleaseBuilder
  Use these checklists to ensure that all required artifacts and configurations are moved. These checklists should be used when preparing to deploy your portal.

• Building a Release
  ReleaseBuilder allows you to compare the XML configuration files that describe your staging server (REV1) and your updated staging server (REV2) and creates an XML configuration file that contains the differences between the two servers. This output file is then used 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.

 

Parent topic

Set up WebSphere Portal

---