Build a release

Overview

Use ReleaseBuilder to compare the XML configuration files that describe a portal environment (version1) and a newer version of the portal environment (version2), and to create an XML file that contains the differences between the old and the new. We use this output file to import only the differences from version2 onto a target server. Features that are unchanged from version1 to version2 are not affected by the import.

The XML files from version1 and the XML files from version2 refer to two exports taking from the SAME portal server. Building a release means to generate an XML file containing the modifications made to the source server between version1 and version2. ReleaseBuilder is not designed to determine the differences between two separate Portal servers.

There are additional considerations for virtual portals.

Build and promote a release

1. Configure environments to allow all of the required artifacts and the configuration to be moved.

2. On the source server, export the entire configuration to srcv1.xml.

   cd  WP_PROFILE/PortalServer/bin 
   ./xmlaccess.sh -in ExportRelease.xml  \
                  -user wpsadmin  \
                  -password mypassword  \
                  -url http://host.example.com:port/wps/config  \
                  -out srcv1.xml
   

3. Develop new functions and portlets on the source server.

4. On the source server, export the entire configuration to srcv2.xml.

   cd WP_PROFILE/PortalServer/bin 
   ./xmlaccess.sh -in ExportRelease.xml  \
                  -user wpsadmin  \
                  -password wpsadmin_pwd  \
                  -url http://host.example.com:port/wps/config  \
                  -out srcv2.xml
   

   Do not include users, users' access control, or any other user configurations.

5. Copy required *.war files from source to target server. From source server run...
   scp WP_PROFILE/PortalServer/deployed/archive/mywars*.war user@host:/path/to/PortalServer/deployed/archive

   This directory will always be located in the original WP_PROFILE, even if the target server has additional Portal profiles created after installation.

6. Generate the differences between source server configurations version1 and version2:

   1. To free resources, stop the portal server on the staging system. (Optional)

   2. Generate the differences file, outputfile.xml, containing additions and deletions...

      cd WP_PROFILE/PortalServer/bin 
      ./releasebuilder.sh -inOld srcv1.xml  \
                          -inNew srcv2.xml  \
                          -out outputfile.xml
      

      IBM recommends, for CPU and memory load reasons, to not releasebuilder.sh

   3. Restart the portal server on the staging system.

7. Import outputfile.xml into the target server....

   ./xmlaccess.sh -in outputfile.xml  \
                  -user wpsadmin  \
                  -password wpsadmin_pwd  \
                  -url http://target.example.com:port/wps/config
   

If portlet parameters are deleted from a configuration, the output script generated by ReleaseBuilder does not remove those parameters on the target system.

XML files generated by ReleaseBuilder do not have any transaction levels set. To set a transaction level edit the XML file generated by ReleaseBuilder and add the transaction level to the XML file.

Parent

ReleaseBuilder
Build a Release for virtual portal installations
Checklist for ReleaseBuilder

+

Search Tips   |   Advanced Search