Setting Maximum Associations for Release Control Objects

To ensure that you don’t overload your system by trying to deploy too many deployment units in one process, you can set maximum limits for the number of hierarchical associations for release trains, application releases, and release packages.

By default, Serena Release Manager sets the maximum number of hierarchical associations to 50 each. For example, application releases per release train, release packages per application release, and deployment tasks per release package.

Depending on the bandwidth of your servers and the demands your deployment processes make on the participating servers, you may choose to raise or lower the maximum limit.

To change the maximum values for the associations:

  1. Navigate to the Serena Release Manager common Tomcat Web server classes folder. For example:

    C:\Program Files\Serena\common\tomcat\6.0\webapps\rlm\WEB-INF\classes

  2. Open the sbm-client.properties file.

  3. Update the value of one or more of the following entries as needed:

    # URM_RELEASE_TRAIN

    release.train.maximum.application.releases=50

    #USR_APPLICATION_RELEASE

    application.release.maximum.release.packages=50

    # USR_RELEASE_PACKAGE

    release.package.maximum.deployment.tasks=50

  4. After updating the file, restart the Serena common Tomcat service.

     

     

    CAUTION!  Do not change any other entries in the sbm-client.properties file. The other entries are used by Serena Release Manager Web services and any changes could cause Serena Release Manager to stop working correctly.