Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

---

 

Build a Release

 

+

Search Tips   |   Advanced Search

 

Overview

ReleaseBuilder allows you to compare the XML configuration files between servers and create an XML configuration file that contains the differences.

This delta XML file is used to import only the differences from prod server into stage server.

Running ReleaseBuilder on a production server is not advised because ReleaseBuilder will consume resources and affect portal services to users.

Before running, move required artifacts and configuration.

 

Two servers, both with Portal

1. Install Portal on prod server and stage server

2. Develop a release on the prod server.

3. Build the release on the prod server.

4. Empty portal contents on stage server...

   WPSconfig.sh|bat action-empty-portal

5. Import release into stage server.

 

Two servers, one with Portal, one without

1. Export the release of the prod server.

2. Install an empty stage server using one of the following two methods:

   • Install the stage server with the flag...

     -W emptyPortal.active=True

   • After installing and configuring the stage server, run task...

     WPSconfig.sh|bat action-empty-portal

3. Import the production release onto the stage server.

4. Develop and build a new release on the stage server.

5. Export that new release from the stage server.

6. Use ReleaseBuilder to generate the differential between the two releases.

7. Import the differential onto the prod server.

 

Export stage server configuration

1. Export the entire portal configuration of the stage server.

   cd portal_server_root/bin

   xmlaccess.sh -in ExportRelease.xml -user wpsadmin -password password -url http://stageserver.example.com:port/wps/config -out stageserverREV1_config.xml

2. Develop and test new functions and portlets on the stage server.

3. Export stage server configuration

   cd portal_server_root/bin

   xmlaccess.sh -in ExportRelease.xml -user wpsadmin -password password -url http://stageserver.example.com:port/wps/config -out stageserverREV2_config.xml

4. Copy WAR files for custom portlets from the stage server to the installation directory...

   portal_server_root/deployed/archive

   ...on the prod server.

   On Windows the name of the WAR file must be 25 characters or less.

5. Stop the WebSphere Portal Express server:

   cd app_server_root/bin
   stopServer.sh WebSphere_Portal -profileName wp_profile -user wpsadmin -password admin_password

6. Generate the differences file...

   cd portal_server_root/bin directory.

   releasebuilder.sh -inOld stageserverREV1_config.xml -inNew stageserverREV2_config.xml -out outputfile.xml

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

7. The outputfile.xml which contains the differences between REV1 and REV2 portal server is then used to import these differences onto the prod server.

   xmlaccess.sh -in outputfile.xml -user wpsadmin -password password -url http://productionserver.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.

   See...

   • The XML configuration interface
   • XML configuration interface: reference

8. Stop and restart the WebSphere Portal Express server:

   cd app_server_root/bin
   stopServer.sh WebSphere_Portal -profileName wp_profile -user wpsadmin -password admin_password
   startServer.sh WebSphere_Portal -profileName wp_profile

 

Parent topic:

Staging to production

 

Related concepts
About ReleaseBuilder Staging the portal to production

 

Related reference

Manual steps prior to using ReleaseBuilder

 

Related information
Working with the XML configuration interface

---