Note: When viewing this file in Internet Explorer 8, numbered or alphabetical lists may appear corrupted.
You can find information about the following in this document:
This Readme describes the changes made to HP Release Control for 9.21 Patch 2. It contains important information not included in the manuals or in the online help.
For detailed information about HP Release Control, please refer to the documentation set, available on the HP Release Control installation disk, or accessible from the HP Release Control application by selecting Help > HP Release Control Documentation Library.
HP Release Control Version 9.21 Patch 2 introduces the new strings of Logout Successfully
and Login again
. If required, you can translate this string to other supported languages using the Language Builder. For details, see the HP Release Control Open Localization Toolkit User Guide. (To access the documentation, select Start > Programs > HP Release Control 9.21 > Documentation and open the pdfs directory.)
HP Release Control Version 9.21 Patch 2 includes several customer requested software fixes. The following list of Change Request (CR) fixes is included in this software release.
Global ID
|
Problem
|
Solution
|
---|---|---|
QCCR1E107787
|
Users receive "session expiry" error messages during their activities in Release Control and then are logged out. |
Updated a variable to fix this disconnection issue. User will not be logged out when using Release Control. |
QCCR1E112834
|
Change records are not refreshed in the Similarity section in Release Control. Similarity record are deleted incorrectly when changes are updated. You cannot find similar records. |
Change records are refreshed in the Similarity section in Release Control. When new changes arrive in RC or old changes get updated, they can be found in similar change records section. |
Instructions for installing HP Release Control Version 9.21 Patch 2 on Windows are documented in PatchNotes.txt, which is provided in the product's installation package.
Instructions for installing HP Release Control Version 9.21 Patch 2 on Linux are documented in Release Control Deployment Guide > Upgrading HP Release Control.
The Compatibility Matrix lists supported versions of operating systems, browsers, HP Software products, and other compatibility and support information.
This Readme describes the changes made to HP Release Control for 9.21 Patch 1. It contains important information not included in the manuals or in online help.
For detailed information about HP Release Control, please refer to the documentation set, available on the HP Release Control installation disk, or accessible from the HP Release Control application by selecting Help > HP Release Control Documentation Library.
HP Release Control Version 9.21 Patch 1 includes several customer requested software fixes. The following list of Change Request (CR) fixes is included in this software release.
Global ID
|
Problem
|
Solution
|
---|---|---|
QCCR1E107382
|
Request to support multi-tenants point to one uCMDB customer ID. |
More tenants can point to one customer ID. |
QCCR1H71287
|
Release Control displays 01/01/1970 for the changes without Planned start or Planned end. |
Set the date to the start of selected week or month. |
QCCR1E98061
|
Release Control does not get all Service Manager tickets due to a bug in the tickets polling process. |
Tickets will not miss if the Release Control server and the Service Manager server has the same clock running. |
QCCR1E96766
|
Maintenance Window occurrence does not work correctly. Suppose there are: G7L Impacting Maintenance Window - Every 4th Saturday between 8:00PM (Sat.) and 2:00AM the following morning (Sun.). G7L Non-Impacting Maintenance Window - Daily between 2:00AM and 6:00AM the same day. On the 4th Saturday of June - There is only one Maintenance Window from 2:00AM until 6:00AM. But the Impacting Maintenance Window is not seen. If you scroll to 30th June, there is the Impacting Maintenance Window from 8:00PM on Saturday until 2:00AM Sunday Morning. But this is the 5th Saturday of June, not the 4th. |
Maintenance Window occurrence now works correctly. |
QCCR1E99131
|
Tickets are stuck in the queue after Release Control upgrade to 9.20 due to change flow script failure. |
Expose interface: setField for change object in functions: postChangeProcess/preChangeProcess/preCalcRisk. You can use this interface in change flow script and update changes in certain functions. |
QCCR1E92877
|
Many change tickets jam in Release Control queue, in which some CIs have empty display labels. |
Change tickets will not jam in Release Control queue. If a CI has empty display label and has "Null value of attribute: display_label, a message will be generated for your reference in the cmdb-<##>_general.log file. |
QCCR1E100252
|
Unable to successfully integrate Release Control 9.13 with UCMDB 10. |
User can successfully integrate Release Control 9.13 with UCMDB 10 if root context is enabled. Note: This patch introduces the new string of |
QCCR1E100727
|
When integrating Release Control 9.20 with UCMDB 10.01 CUP4, instances without the MODELING_ENABLED qualifier are synchronized to Release Control. |
Any instances without the MODELING_ENABLED qualifier cannot be synchronized to Release Control. |
QCCR1E102910
|
E-mail notifications are getting backlogged with the following error message.
|
Email notifications performance are improved by using multiple threading when sending e-mails. |
QCCR1E92930
|
Unable to start implementation of Changes in the Logging phase. In addition, need an additional Status filter so that the user knows which Changes he can start implementing without having to check each Change individually. |
Added an additional status filter so that the user knows which Changes can be implemented without having to check each Change individually. Note: This patch introduces the new string of |
HP Release Control Version 9.21 Patch 1 includes several customer requested software enhancements. The following items (identified by reference number) are enhanced in the current software release.
Global ID
|
Problem
|
Solution
|
---|---|---|
QCCR1E104788
|
Request HP Release Control to support 64-bit Java to improve performance. |
Included x64 JRE and x64 Tomcat in the package. |
QCCR1E99396
|
Request to change the encryption algorithm for storing password to SHA512. |
HP Release Control now supports the SHA512 encryption algorithms for storing password. |
Instructions for installing HP Release Control Version 9.21 Patch 1 are documented in PatchNotes.txt, which is provided in the product's installation package.
The Compatibility Matrix lists supported versions of operating systems, browsers, HP Software products, and other compatibility and support information.
This Readme describes the changes made to HP Release Control 9.21. It contains important information that is not included in books or the HP Release Control Help.
For detailed information about HP Release Control, please refer to the documentation set, available on the HP Release Control installation disk, or accessible from the HP Release Control application by selecting Help > HP Release Control Documentation Library.
HP Release Control Version 9.21 includes several customer requested software fixes. The following list of Change Request(CR) fixes is included in this software release.
Global ID
|
Problem
|
Solution
|
---|---|---|
QCCR1H76080
|
Labels (or other properties, such as toolTip, colHeader) of custom fields created in RC cannot be translated. |
The related instructions were missing in the document. Added a topic "How to Translate the Label for a Custom Field" to FAQ section in RC 9.21 Deployment Guide. |
QCCR1H67697
|
When Changes are pulled to RC through the service desk adapter, if the coordinator or the implementer of the Change record is not an existing user in RC, a new user account will be automatically created in RC. However, this new user cannot be seen in RC GUI. An error will be displayed if you try to add a user account with the same name in RC GUI since it is already existing in the database. |
Now you can add user accounts in RC GUI even if the user names have already been created as Implementers. |
QCCR1E95788
|
When following the instruction in RC Deployment Guide to perform system upgrade, the new version was wrongly removed by running uninstallation instead of the old version. |
Corrected the instruction for Post Upgrade Recommendations in RC Deployment Guide to remove the old version correctly. |
QCCR1E91509
|
When creating several maintenance windows and lockdowns with many business CIs in Release Control, these items are displayed in Time Period Conflicts tab with maintenance windows. After some changes these business CIs listed inside the filters for maintenance windows and lockdowns are displayed with (obsolete) after them. |
Business CIs do not become obsolete. The existing obsolete business CIs are recovered to normal instead of being reloaded. |
QCCR1E91481
|
The Service Desk adapter pulls the tickets from BMC Remedy and then suddenly stops pulling them without any errors in the log. |
Now the Service Desk adapter is able to pull tickets from Remedy without intermittency. |
QCCR1E90526
|
When customizing the OOB rcDetectedChanges by replacing CI type "Node element" with "running software", there is no latent changes found in RC. |
Updated uCMDB API to a new version. Now RC is able to find the latent Changes with customized TQL successfully. |
QCCR1E89076
|
When importing changes from Service Manager to Release Control, errors about the SuggestedStartDate field and the SuggestedEndDate field are displayed in the ccm_sdi log file. |
Removed the reference to suggested time field in the out-of-box convertTask.js file. Now changes are imported successfully without any errors. To use suggested time, you need to expose these fields in the WSDL of Service Manager first. |
QCCR1E88854
|
Unable to implement LW-SSO between RC and SM with SSL encryption enabled in a mixed physical/logical domain. |
Removed the forceful domain overwrite code. The LW-SSO integration can be implemented with SSL encryption in a mixed physical/logical domain. |
QCCR1H77515
|
When setting value for boolean field in convertChange.js, an exception is displayed in the log file. The XML service desk adapter did not update the records in the database properly. Consequently, the records were not displayed correctly in the RC GUI. |
Now RC supports setting boolean type of fields in convertChange.js. RC is able to read XML files properly and create/update records correctly. |
QCCR1H77514
|
The RC documentation does not include manual configuration steps to support Oracle RAC. |
RC Deployment Guide is updated to include manual configuration steps in RC to support Oracle RAC. |
QCCR1H77376
|
RC does not work with IIS 7. |
RC can be manually configured to work with IIS 7 with the following instructions:
|
QCCR1H76338
|
CIs are missing in "Changed Configuration Items Affecting my Business CIs" section in the automated subscription notifications sent from RC. |
The CIs which triggerred the subscribed Business CIs are added in the notification mail. |
QCCR1H76023
|
When login to RC through LDAP authentication with a wildcard in the login ID (for example, u123456*), the system displays an HTTP 500 error. |
Now you can login RC with a wildcard in the login name through LDAP authentication. HTTP 500 error is not displayed any longer. |
This software release has the following limitations.
Global ID
|
Summary
|
---|---|
QCCR1E94402
|
There is no accessibility in the change request’s Calendar view when user activates the Monthly mode tab because RC's Flex technology does not support animation accessibility. |
QCCR1E98140
|
Impact Graph is not accessible inside Impact tab because RC's Flex technology does not support animation accessibility. |
QCCR1E98125
|
In the SM-RC integration, the focus cannot move to RC from SM or move out of RC to SM in Firefox 22.0 because Firefox does not fully support HTML embedded SWF file accessibility. |
QCCR1E96934
|
The screen reader cannot read the Time Period bar in the Change request grid and Timeline grid because RC's Flex technology does not fully support gantt grid accessibility. |
Instructions for installing HP Release Control Version 9.21 on Windows are documented in PatchNotes.txt, which is provided in the product's installation package.
Instructions for installing HP Release Control Version 9.21 on Linux are documented in HP Release Control 9.21 Deployment Guide.
The Compatibility Matrix lists supported versions of operating systems, browsers, HP Software products, and other compatibility and support information.
This Readme describes the changes made to HP Release Control 9.20. It contains important information that is not included in books or the HP Release Control Help.
For detailed information about HP Release Control, please refer to the documentation set, available on the HP Release Control installation disk, or accessible from the HP Release Control application by selecting Help > HP Release Control Documentation Library.
Impact CIs (Too many CIs to display. Please refine the search criteria.)
.
You can configure the default value of Maximum impact search result size in Configuration > Modules > Analysis,
and narrow the search scope by either clicking the My Business CIs button or
using the CIs search box.Note: For the existing legacy Changes with more than 2000 Impact CIs, you can launch Manual Change Process to retrieve the full CIs without truncation anymore after upgrade to version 9.20.
Global ID
|
Problem
|
Solution
|
---|---|---|
QCCR1H68331
|
The RC-SM Integration using SSO section does not include all the necessary steps for RC to correctly communicate with SM. |
Updated the RC 920 Deployment Guide. |
QCCR1H65951
|
The Change Cleaner utility cannot remove only one change from all the filtered changes and the related data. |
The behavior of the Change Cleaner utility is improved. |
QCCR1H75809
|
In SM 9.21/RC 9.13 integration,RC cannot get the value of "Approvalstatus" Field in SM, and SM cannot get the value of "RiskLevel" from RC. |
SM and RC can get values correctly. |
QCCR1H75516
|
The customer has integrated PPM 9.12 with RC 9.13. Under the Calendar View, tickets are not giving the proper count on each day when trying to use the Month View. |
Month view displays correct number of changes for each day. |
QCCR1H73938
|
Cannot configure time periods because of time zones settings. |
The time periods can be configured correctly. |
QCCR1H73937
|
In RC 9.13 patch1/SM 9.30 integration, when logging into SM and opening the Change calendar, LWSSO does not work when LDAP is used. |
Change calendar can work even if the user account does not exist in RC database. |
QCCR1H71033
|
The SM-RC integration is implemented using SOAP. Each soap message creates a new session and logs in/out SM independently. |
The SM-RC integration is using persistent connection now. |
QCCR1H70018
|
When importing changes from Service Desk, Release Control extracts the name from the implementor field and creates a user in its database. Release Control uses the same name for both First and Last name; therefore, in the GUI, the name will show up twice. |
Implementers' names are not duplicate. |
QCCR1H70525
|
When a change is brought from Service Manager to Release Control, paragraphs in the Description field are mixed up. |
In Release Control, the Description field of a change is displayed correctly as it is in Service Manager. |
QCCR1H68485
|
The Impact icon is always "unknown". |
The Impact icon is "unknown" because there is no affected business CI for this change. Try to add some affected business CI and check whether the icon is properly displayed. The User Guide is updated to remind customers about this. |
QCCR1H65952
|
In Analysis Calendar page, the Month view is not consistent with the Day view. |
In Analysis Calendar page, the Month view is consistent with the Day view. |
QCCR1H65962
|
Changes and tasks disappear from the UI until refreshing the changes or resizing the windows. |
The change tickets and tasks are properly displayed. |
QCCR1H65954
|
Customers cannot receive emails from RC. RC is sending all alerts at one time and committing them at last. |
RC sends 30 alerts at one time and commits them one by one. |
QCCR1H63201
|
In Module > Administrator > Configuration tab > Change Process > Risk Factors > Damage Factors, the Source field on the Risk Factors pane cannot be updated. |
The Source field on the Risk Factors pane can be updated. |
Instructions for installing HP Release Control Version 9.20 are documented in PatchNotes.txt, which is provided in the product's installation package.
The Compatibility Matrix lists supported versions of operating systems, browsers, HP Software products, and other compatibility and support information.
This Readme describes the changes made to HP Release Control for 9.13 Patch 3. It contains important information not included in the manuals or in online help.
For detailed information about HP Release Control, please refer to the documentation set, available on the HP Release Control installation disk, or accessible from the HP Release Control application by selecting Help > HP Release Control Documentation Library.
HP Release Control Version 9.13 Patch 3 includes several customer requested software fixes. The following list of Change Request (CR) fixes is included in this software release.
Global ID
|
Problem
|
Solution
|
---|---|---|
QCCR1E100252
|
Unable to successfully integrate Release Control 9.13 with UCMDB 10. |
User can successfully integrate Release Control 9.13 with UCMDB 10 if root context is enabled. Note: This patch introduces the new string of |
QCCR1E92877
|
Many change tickets jam in Release Control queue, in which some CIs have empty display labels. |
Change tickets will not jam in Release Control queue. If a CI has empty display label and has "Null value of attribute: display_label, a message will be generated for your reference in the cmdb-<##>_general.log file. |
QCCR1H69390
|
When there are more than ten changes in Calendar view, click the Refresh button will get an error. |
No error found when refreshing the Calendar view. |
QCCR1H77041
|
When integrating Release Control 9.13 with Service Manager, sdiConfigurere.bat failed with the following error.
|
sdiConfigurere.bat runs successfully. |
QCCR1H68500
|
In some cases, time periods are not assigned to changes correctly. There is one day offset when calculating the time period. |
Time periods are assigned to changes correctly. |
QCCR1H71966
|
Release Control does not print help message for the ChangeContextPath utility. |
Added help message when running the changecontextpath.bat utility. |
QCCR1H71277
|
The Documentation Library home page cannot be opened after the context path is changed to "x/y/z". |
The documentation Library home page is displayed as normal. |
QCCR1H77320
|
Changes from Service Manager are not visible to the customer in the Release Control UI. |
Catch the nullpointerException and drop the event. Changes from Service Manager are displayed in the Release Control UI. |
No enhancements and updates are implemented in HP Release Control Version 9.13 Patch 3.
Instructions for installing HP Release Control Version 9.13 Patch 3 (RC 9.13p3) are documented in PatchNotes.txt, which is provided in the product's installation package.
The Compatibility Matrix lists supported versions of operating systems, browsers, HP Software products, and other compatibility and support information.
This Readme describes the changes made to HP Release Control for 9.13.0001 Patch 2. It contains important information not included in the manuals or in online help.
For detailed information about HP Release Control, please refer to the documentation set, available on the HP Release Control installation disk, or accessible from the HP Release Control application by selecting Help > HP Release Control Documentation Library.
HP Release Control Version 9.13, build 0001 Patch 2 (RC 9.13p2) includes several customer requested software fixes. The following list of Change Request (CR) fixes is included in this software release.
Global ID
|
Problem
|
Solution
|
---|---|---|
QCCR1H72751
|
When Release Control version 9.13 is reinstalled, all latent changes disappeared. |
Release Control uses a multiple-thread connection manager when connecting to UDMDB. |
QCCR1H72437
|
Changes are stuck in the queue if the "Requests affecting any business CI" filter is used in time period. |
Changes are processed normally when a filter on business CI is used in time period. |
QCCR1H71128
|
After Release Control version 9.13 patch 1 is applyied in LDAP+LWSSO environment, the user cannot approve a change. The authorization problem occurs. |
User can approve a change in Service Manager when integrating with Release Control in LDAP+LWSSO environment. |
QCCR1H71144
|
In Collision settings, "Max change duration(days)" cannot be set to more than 24 days. Otherwise, collision will not be calculated for some changes. |
The limitation of "Max change duration(days)" is removed. |
QCCR1H70994
|
When a change is planned and a new date-time is set, there is an issue with the time display format. |
When the selected time (00:xx) is saved in the planned start/end field, the display does not change. |
QCCR1H70858
|
Report generated in Excel format cannot be opened. |
Update jasper report from version 3.1.0 to 4.5.0. Report generated in Excel format can be opened. |
QCCR1H70390
|
When using RC 9.13 in French, the date format displayed is MM/DD/YYYY instead of DD/MM/YYYY in Day view. |
Added date.format.fullMonth.day.year=DD/MM/YYYY to the date format properties file. To change to date to other format:
|
QCCR1H68808
|
Unable to pull information by using the "Post Implementation" function in the Dashboard module when the language selected is other than English. |
When the language selected is other than English, information is pulled successfully by using the "Post Implementation" function. |
QCCR1H68580
|
With version 9.1x, RC writes analysis data back to SM without any reason. The SM user has to re-open the change and all updated information are lost. |
Added a new function shouldUpdateAnalysis in change-flow.js to control whether to update SM with analysis data. |
QCCR1H68500
|
In some cases, time periods are not assigned to changes correctly. There is one day offset when calculating the time period. |
Time periods are assigned to changes correctly. |
QCCR1H65542
|
In Module > Analysis > Change Requests > Assess > Impact tab, the description for DIRECTLY AFFECTED BUSINESS (DAB) and INDIRECTLY AFFECTED BUSINESS (IAB) is not accurate. |
The description for DIRECTLY AFFECTED BUSINESS (DAB) and INDIRECTLY AFFECTED BUSINESS (IAB) is accurate now. |
HP Release Control Version 9.13 Patch 2 includes several customer requested software enhancements. The following items (identified by reference number) are enhanced in the current software release.
Global ID
|
Problem
|
Solution
|
---|---|---|
QCCR1H72757
|
HP Release Control version 9.13 (including patch 1) does not support HP Service Manager Process Designer (PD) changes. |
HP Release Control added support for HP Service Manager 9.30 Process Designer (PD) Content Pack 2:
Refer to HP Service Manager Process Designer integration documentation for more information. |
QCCR1H68280
|
Unable to configure context paths for different Release Control servers behind a Server Reverse Proxy (SRP) because /ccm in the URL is hardcoded. |
The context path is configurable now. For detailed configuration steps, refer to the change_context_path.pdf in the <HP Release Control installation directory>\apps\rcdocs directory. |
Instructions for installing HP Release Control Version 9.13 Patch 2 (RC 9.13p2) are documented in PatchNotes.txt, which is provided in the product's installation package.
The Compatibility Matrix lists supported versions of operating systems, browsers, HP Software products, and other compatibility and support information.
This Readme describes the changes made to HP Release Control for 9.13.0001 Patch 1. It contains important information not included in the manuals or in online help.
For detailed information about HP Release Control, please refer to the documentation set, available on the HP Release Control installation disk, or accessible from the HP Release Control application by selecting Help > HP Release Control Documentation Library.
HP Release Control Version 9.13, build 0001 Patch 1 (RC 9.13p1) includes several customer requested software fixes. The following list of Change Request (CR) fixes is included in this software release.
Global ID
|
Problem
|
Solution
|
---|---|---|
QCCR1H63695
|
When browsing to the dashboard and displaying the default Analysis Portal, a big red undefined error is displayed instead of the actual data. When examining the stdout.log, the error is generated by attempting to get the client's time zone. |
Release Control caches httprequest in the web filter. |
QCCR1H62990
|
Change process of some tickets takes a long time of more than one hour. |
When processing each task, Release Control loads the existing ticket itself instead of loading the whole hierarchy. |
QCCR1H67133
|
When importing a configuration set to the current updated draft, error is reported. |
The import process is completed without errors, and the existing configuration set is overridden. |
QCCR1H64823
|
Customers cannot receive notification emails from Release Control. |
Release Control now processes 30 alerts each time and sends notification emails properly. |
QCCR1H64178
|
Tickets are processed slowly in Release Control due to long duration of time periods calculation. |
Release Control optimizes time periods calculation and speeds up change process. |
QCCR1H63379
|
A notification email will not be sent if its subject exceeds 255 characters. |
Release Control now sends the emails properly. |
QCCR1H66278
|
Changes and tasks disappear from the UI until refreshing the changes or resizing the windows. |
Release Control checks the null value before calling its method. The change tickets are properly displayed. |
QCCR1H65890
|
On analysis calendar page, the Month view is not consistent with the Day view. |
Release Control does not count the change if the change's planed end time is the actual start time of the day. |
QCCR1H64704
|
When logging into Release Control with a user profile which is restricted to Administrator module and has user management permission only, an error is displayed in the UI. |
Now any user profile with the viewAdministrationModule permission also has the editConfiguration permission. |
QCCR1H33929
|
Upgrade from 4.12 to 913 failed with the following error: java.sql.SQLException: ORA-06502: PL/SQL: numeric or value error: number precision too large ORA-06512: at line 7 |
Updated the upgrade.sql file. |
QCCR1H62594
|
Release Control logs are filled with errors. |
Release Control now skips sending an email when the email address is empty. |
QCCR1H66439
|
In Calendar > Monthly View, an exception is displayed when the customer adds a field with delimiter value in a chart. |
Release Control now removes the fields with delimiter value in charts configuration. |
QCCR1H38090
|
In Directory Module > Control, when trying to display info by holding the mouse pointer over the record line, no information is displayed in French. Whereas in English, information is displayed. |
Added variable tag in the French language configuration file. |
QCCR1H67396
|
When logging into Release Control with Chinese language, the month tag is duplicated in the date format. |
Removed the duplicate tag and corrected the date format. |
QCCR1H65401
|
The RC9.13-SC6.2 integration failed due to the SOAP API license requirement. |
Use "changecalendar" instead of "Change Calendar" pragma in header. Release Control now has no license requirement for SOAP API. |
QCCR1H63749
|
The SDI adapter failed to start with ServiceCenter 6.2. |
Added deny and canDeny operation for ServiceCenter. |
QCCR1H67130
|
Every time "populate.bat i" is run on brand new schemas, it fails with the following error: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1 ORA-02264: name already used by an existing constraint |
Updated SQL for future versions of Oracle 9. Changed "drop table TABLE_NAME; " to "drop table TABLE_NAME cascade constraint purge; ". Deleted table and constraints directly and removed all drop table actions in SQL files. Now populate.bat i can finish successfully without the "ORA-02264: name already used by an existing constraint" errors. |
QCCR1H67891
|
The RC LDAP loginName is case-sensitive. When login failed due to this issue, the http 500 error is displayed. |
Saved the loginName as lower case string in RC database and queried the user with lower- case string. The RC LDAP loginName is not case-sensitive now. |
QCCR1H67000
|
Cannot display all Time Periods in the Analysis module and there is no scroll bars. |
Added a scroll bar and the complete time period list can be displayed. |
QCCR1H66792
|
When clicking to display time periods, only the first 7 are displayed. The rest become visible only after the Refresh button is clicked. |
When clicking to display time period, the complete time period list can be displayed. |
HP Release Control Version 9.13 Patch 1 includes several customer requested software enhancements. The following items (identified by reference number) are enhanced in the current software release.
Global ID
|
Problem
|
Solution
|
---|---|---|
QCCR1H62244
|
Cannot get information from Release Control logs about the change process duration time of a ticket. |
Added info level message for the duration of processing each queue ticket, change and operation into ccm_services.log. Added debug level message for each step in impact analysis into ccm_cmdb.log. |
QCCR1H64681
|
Cannot remove all the filtered changes and the related data by using the Change Cleaner utility. After using the command to delete all changes, size of the database is still 2 GB. It seems that the information is not deleted properly. |
Enhanced the Change Cleaner utility to delete change by change/task numbers. |
This software release has the following known issues.
Global ID
|
Known Issue
|
Workaround
|
---|---|---|
QCCR1H68530
|
Alphabetical lists in the User Portal page are not correctly displayed. When viewing the RC web help User Portal page in Internet Explorer 9, numbered or alphabetical lists appear corrupted. |
No workaround available at this time. |
Instructions for installing HP Release Control Version 9.13 Patch 1 (RC 9.13p1) are documented in PatchNotes.txt, which is provided in the product's installation package.
The Compatibility Matrix lists supported versions of operating systems, browsers, HP Software products, and other compatibility and support information.
This Readme describes the changes made to HP Release Control 9.13. It contains important information that is not included in books or the HP Release Control Help.
For detailed information about HP Release Control, refer to the documentation set, available on the HP Release Control installation disk, or accessible from the HP Release Control application by selecting Help > HP Release Control Documentation Library.
The Service Desk Integration module supports the following service desk applications:
To enable access to HP Release Control through SRP, perform the following:
For example, if the reverse proxy is Apache server, add the following lines to the https.conf file:
The HP Release Control access URL should refer to the reverse proxy host. For example:
http://<proxy_host>/ccm and http://<proxy host>/rcdocs respectively.
Note: Different types of reverse proxy may require different configuration steps. Refer to your proxy server documentation for more information.
To use HTTPS with SRP, perform the following steps:
Note: In Apache server, the truststore (cacerts file) file is not a part of the installation. You may need to create a new PEM encoded cacerts file. Refer to the Apache documentation for details.
To invoke the REST API:
Content-Type : application/json |
http://<RC_Server_Name>:<Port>/ccm/rest/rfc/rfcId/<Change rfc number>/adapterName/<Adapter Name>/changeImpactCis.json |
For example:
http://localhost:8080/ccm/rest/rfc/rfcId/C0008983/adapterName/test/ changeImpactCis.json |
where:
RC_Server_Name is localhost
Change rfc number is C0008983
Adapter_Name is test
The responses are returned in JSON format, which is supported using Java APIs.
The following information supplements the current HP Release Control documentation and should be used along with the Help when reading about the following:
The Dashboard portlets display change request information based on:
To create a customized portlet:
This Readme describes the changes made to HP Release Control 9.12. It contains important information that is not included in books or the HP Release Control Help.
For detailed information about HP Release Control, refer to the documentation set, available on the HP Release Control installation disk, or accessible from the HP Release Control application by selecting Help > HP Release Control Documentation Library.
The following table describes the system requirements for the HP Release Control server:
or
For HP Universal CMDB 9.0x, open the <HP Release Control root directory>\apps\cmdb-adapter-90\WEB-INF\lib\ccm-mam-mam90-9.12.0000.jar file.
<bean id="conditionOperator" class="java.lang.String"> <!-- possible values: equals, equals_ignore_case, like, like_ignore_case --> <constructor-arg value="equals_ignore_case" /> </bean> |
To receive an email notification in case the number of impacted CIs is greater than 2000, perform the following steps:
Note: To check whether a specific request's impact list has been truncated, use the newChange.getImpact.isTruncated function.
The following information supplements the current HP Release Control documentation and should be used along with the Help when reading about the following:
Changes to the URL used to generate a link. To create a link to the HP Release Control calendar, enter the following URL, customized according to the example below:
where:
refid is the ID of the change request that enables the embedded change request to be highlighted in the originating service desk.
serviceDesk identifies the service desk from where the change request originated.
This Readme describes the changes made to HP Release Control 9.11. It contains important information that is not included in books or the HP Release Control Help.
For detailed information about HP Release Control, please refer to the documentation set, available on the HP Release Control installation disk, or accessible from the HP Release Control application by selecting Help > HP Release Control Documentation Library.
The Service Desk Integration module supports the following service desk applications:
HP Release Control server requirements. Database connectivity requires high bandwidth and low latency network paths.
The following information supplements the current HP Release Control documentation and should be used along with the Help when reading about the following areas.
Note:
To export part of a configuration set to your local directory:
The section Configuring a Database as a Service Desk on page 57 in the HP Release Control Deployment Guide, is being replaced by the deployment_guide_update.pdf file provided with HP Release Control 9.11.
This section provides the following information about HP Release Control 9.10L:
For detailed information about HP Release Control, please refer to the documentation set, available on the HP Release Control installation disk, or accessible from the HP Release Control application by selecting Help > HP Release Control Documentation Library.
HP Release Control contains the following new features and enhancements to existing features:
The following table describes the system requirements for the HP Release Control server:
The following table describes the client requirements for viewing HP Release Control:
The Service Desk Integration module supports the following service desk applications:
The first page of this document contains the following identifying information:
To check for recent updates or to verify that you are using the most recent edition, visit this URL: HP Software Product Manuals
To retrieve a document, select the:
You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site.
You can visit the HP Software support web site at:
www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.
HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:
To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.
Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.
To register for an HP Passport ID, go to: HP Passport Registration.
®Copyright 2012 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
For information about third-party and/or open source license agreements, see Docs\Open Source and Third-Party Software Acknowledgements.htm on the product installation media.
Oracle® is a registered US trademark of Oracle Corporation, Redwood City, California.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
Java™ is a registered trademark of Oracle and/or its affiliates.
Adobe® is a trademark of Adobe Systems Incorporated.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
This product includes software developed by the Indiana University Extreme! Lab (http://www.extreme.indiana.edu/).
If you have any comments or suggestions regarding this document, please send them by e-mail to SW-Doc@hp.com.