Welcome to Serena Release Automation 4.5.1.
Please note the following important information:
- Serena Release Automation 4.5.1 supports new installations; you do not need to install a previous version before installing this version.
The following features have been added in this release.
- User Interface Enhancements
- Version Polling Improvements
- Standalone Process Import and Export
- Extended Plug-in Support
- Additional Support for PVCS Source Type
- SBM Composer REST Service Support
Provides an improved user experience with a user interface that is easier to understand and navigate
- Modification of Version Polling for certain source types:
- Specify Polling Period per component
- Specify Quiet Period per component which prevents duplicate uploads
- Allows a general polling value to be set (default 15 seconds) but can be over-ridden per component for supported types
- Increases scalability of solutions (200 components = 200 polls every 15 seconds!)
- Creates JSON export files
- Supports movement of processes from one server to another
Extended plug-in support includes the following:
- Expanded Plug-in Guide
- New Microsoft Azure plug-in
- Version number support for the existing plug-ins
- Additional steps for the Windows Service Control Manager plug-in:
Check If Service Stopped
Check If Service Running
Check If Service Stopped
- Additional steps for the IIS AppCmd plug-in:
Check If Site Exists
Check If Site is Running
Check If Site is Stopped
- Additional steps for the FileUtils plug-in:
Check If Directory Exists
- Additional step for VMware vSphere ESXi, VMware vCenter, and VMware
Revert VM to Snapshot
Additional options for the PVCS source type include:
Improved polling / configurable polling times
Improved validation of version differences
A more atomic-like commit for sources
The following sections guide you through an upgrade for this release.
- New Installations
- Pre-upgrade Steps
- Upgrading Servers from 4.5 to 4.5.1
- Upgrading Servers from 4.0.1 to 4.5.1
- Upgrading Agents
- Post-upgrade Steps (IMPORTANT!)
If this is a new installation, see "Installation and Configuration" in the Serena Release Automation User's Guide or online Help.
Before you begin the upgrade:
Download the Serena Release Automation 4.5.1 server and agent installation files from the Serena support website.
Export or save a backup of your existing processes and applications as a precautionary measure.
To upgrade your 4.5 server installation to 4.5.1:
Using the Install Wizard:
Install the 4.5.1 version of the server; the upgrade will be performed automatically.
Using a Silent Upgrade:
On UNIX systems, the command to execute a silent upgrade is the same as that for a new installation; on Windows systems the command is slightly different. The commands are as follows:
SerenaRA-server.bin -silent -options optionsFile.txt
Where optionsFile.txt is a file containing only the line:
cmd /c SerenaRA-Server.exe /s /V"/qn /L*vx "%TEMP%\silent-install.log" "Note: No PROPFILE is required.
To upgrade your 4.0.1 server installation to 4.5.1:
- Uninstall the 4.0.1 version of the server.
- Delete the files from the Serena Common Tomcat work\Catalina\localhost\serena_ra directory. For example: ..\common\tomcat\6.0\work\Catalina\localhost\serena_ra
- Install the 4.5.1 version of the server. see "Installation and
Configuration" in the
Automation User's Guide or online Help.
Important: To quickly get a new server installed while maintaining your existing settings using the Derby database, select or specify Use existing settings. For all other databases, use the Skip Database option.
To upgrade your agents to 4.5.1, go to the Agents tab, select all agents, and click the Upgrade Selected button. All existing agents using Java 6 and greater will be automatically upgraded by the server.
- Any agents using Java 6 or above can be upgraded and do not have to be uninstalled.
- You must uninstall any agents using Java 5 before installing 4.5.1 agents. Any 4.0.1 and prior agent using Java 5 cannot be upgraded. Most of the new functionality will not work with these agents because the 4.5 and above agents use Java 6 and above.
For a complete list of issues resolved in this release, refer to the Knowledge Base. You must have a support.serena.com user account to view items in the Knowledge Base. Register for a free account if you do not have already have one.
For a complete and up-to-date list of issues found in this release of Serena Release Automation, refer to the Knowledge Base.
These are the known issues that exist at the time of release:
Component version creation fails for TeamForge source type
Version creation is not working for components with TeamForge source type.
- My Reports cannot be properly deleted (DEF225575)
Reports in the My reports pane cannot be properly deleted.
- My Reports are not shown correctly in Microsoft Internet
Explorer 8 and 9 (DEF234343)
Reports in the My reports pane are not shown in Internet Explorer 8 and 9.
- The Rollback Component does not work (DEF239255)
The rollback component step in the application process does not work.
- The command line client does not work with SSO turned on
The Serena Release Automation command line client does not work with SSO authentication.
- A server installation using the Skip Database option requires a
manual reload of plug-ins
If you install the Serena Release Automation server using the Skip Database option, you must load all non-default plug-ins again manually. If you do not do this, these plug-ins will still appear on the plug-ins page, but these plug-ins will not really work because they are not in the database.
- (Windows only) The agent uninstall doesn't reset registry keys
In Windows, after uninstalling an agent, the registry keys are not reset properly.
The agent install wizard Browse button is disabled (DEF231840)
In the agent UI installer wizard, pressing Back to return to the Java Runtime Environment page disables the Browse button. To enable the Browse button, toggle between the Install JRE and Use Existing JRE buttons.
- The agent UI uninstall wizard displays an incorrect path
During an agent UI uninstall, the last page of the wizard displays the incorrect path to the log. The uninstall log can actually be found in the serena_ra_agent_install folder.
- The agent UI install requires an English username (DEF231832)
When using the agent UI installer, you can enter only an English username. Agent installation into a path containing non-ASCII characters is not supported.
- When installing an agent as a service, the displayed service
name format for an agent is not correct (DEF230599)
The service name format should be: serenaRA Agent <specified_name> not <specified_name>.
- The agent uninstall wizard displays errors for a successful
For any agent not installed as a Windows service, the agent uninstall wizard's final panel displays uninstallation errors despite a successful uninstallation.
For Unix and Linux uninstallers, uninstalls that include an
uninstall of Common Tools leave the Tomcat service running (DEF239676)
For Unix and Linux uninstallers, uninstalls that include an uninstall of Common Tools leave the Tomcat service running and don't remove the Common Tools folder. You must manually stop the server and then remove the Common Tools folder.
- In the section "(Linux/UNIX Platforms) Agent Silent
Installation", the executable name for the Linux/UNIX platforms silent
installation command is incorrect. It should be
In the section "(Linux/UNIX Platforms) Agent Silent Installation", step 3 says:
Issue the command: SerenaRA-Agent.exe -silent -options optionsFile.txt
It should say:
Issue the command: SerenaRA-Agent.bin -silent -options optionsFile.txt
- In the section "Automation Plug-ins", the first Serena Support
website link is incorrect. It should be
In the "Automation Plug-ins" section, the second line says:
You can download a zip file that contains all the plug-ins from http://www.serenasupport.com.
It should say:
You can download a zip file that contains all the plug-ins from http://support.serena.com.
In the section "Command Format", the example command has an
incomplete URL. It should be
In the section "Command Format", the example command is given as follows:
serenara-client -weburl http://localhost:8080 -username admin -password admin getResources
It should be:
serenara-client -weburl http://localhost:8080/serena_ra -username admin -password admin getResources
- In the section "Adding an Alias to an Agent", in step 4, the
last part of the command to check the result is incorrect. It should be
In the section "Adding an Alias to an Agent", step 4 says:
To check the result, run the command: keytool -list -keystore agent.keystore
It should say:
To check the result, run the command: keytool -list -keystore sra.keystore
- In the section "Property Settings for Mutual Authentication",
the first table entry for the property
agent.mutual_auth should not be included.
In the section "Property Settings for Mutual Authentication", in the "Property Settings Required Before Exchanging Keys" table, the third property listed, agent.mutual_auth, should not be included.
- The section "Integrating Release Automation with Serena
Solutions" includes a misleading statement that implies REST service
information can be imported directly from the web services WADL file.
The second list item in "Integrating Release Automation with Serena Solutions", Import of Serena Release Automation WADL into SBM REST Grids, should be removed.
The following procedure should be added to the documentation.
Configuring the REST Grid Widgets
In SBM Composer, in a Visual Design layout REST Grid widget, you can get data directly from Serena Release Automation REST services.
To configure the REST grid widget in SBM Composer:
In the REST grid widget, in the Configure URL dialog, provide the REST service method URL and add the composerMode=true request parameter.
If the given Serena Release Automation GET REST service method supports Composer Mode, a sample JSON with returned property names will appear in the p tab. These do not include real data, but are the JSON structure.
In the Result tab, pick the corresponding property names to construct your REST grid widget columns.
When you have finished picking the property names to construct your columns, change the REST service method URL composerMode parameter to false.
Turn on SSO authentication.
In the Result tab, select data to be returned in the output.
Deploy the process app.
Verify the information in the SBM process app's user workspace.
- Information on changing the database password after installation
is missing. (DOC240849)
The following section should be added to the documentation in the Database Installation section.
Changing the Database User Password
If needed after the installation, your database administrator can later change the password for the database schema user that Serena Release Automation uses.
To change the database user password:
Edit the file %serverInstallDir%/conf/server/installed.properties and change the value of the property hibernate.connection.password to the new password.
Restart the Serena Common Tools where the Serena Release Automation server is installed.
The value of the property hibernate.connection.password will be encrypted after the server starts if it is not already encrypted.
- In the section "Serena Dimensions CM" in "Source Configuration
Fields", the field descriptions for Includes and Excludes are missing.
In the section "Serena Dimensions CM" in "Source Configuration Fields", the Serena Dimensions Fields table field descriptions for Includes and Excludes are missing. The fields are as follows:
Field Description Includes
Specify the patterns to match files to include in the upload. You can match exact file paths and file names, or you can specify wildcards.
You can specify exact file path and file name combinations with one entry per line. For example,
You can specify wildcards to match directories and files where the wildcard ** indicates every directory and the wildcard * indicates every file.
For example, the pattern dist/**/* would retrieve the entire file tree beneath the dist directory.
Specify the patterns to match files to exclude from the upload. You can match exact file paths and file names, or you can specify wildcards. See the examples in the previous table entry.