This topic provides information about fixes and updates in version 9.1.04 and instructions for downloading and installing the version 9.1.04.
|Enhancements in version 9.1.04|
For information about enhancements in version 9.1.04, see Enhancements.
|Known issues||For information about issues corrected in this release, see Known and corrected issues.|
|Installing or upgrading version 9.1.04|
For information about installing version 9.1.04, see
Version 9.1.04 provides the following enhancements:
Custom binary payload deployment
The binary payload is a set of binary files, configuration files, batch or Shell scripts. Binary payload deployment provides a single method for easily promoting binary-related customization, consuming less time for applying the customization. The main advantages of having a binary payload are:
- You can deploy a patch or hotfix without using the installer.
- The update is applied to all the servers in a server group.
- No manual steps are required for deploying a payload.
For more information about binary payload, see Creating and deploying a binary payload.
Log management for multiple servers
Currently, enabling logs on multiple servers is a time-consuming process because you need to access each server directly. The new Server Group Logs Management form provides a single location so you can enable logs on multiple servers. These log files refer to the relative path because different servers in a server group might have different directory structures.
The AR System Server Group Name List form allows you to specify a Server Name List with characteristics such as user-facing servers, reporting servers, integration servers, and FTS indexing servers. You can refer this name list on AR System Server Group Log Management form and manage logs for specific servers in the list.
For more information about managing logs for multiple servers, see Managing logs for server group.
Maximum size setting for zip files
You can now set the maximum size for the zip file, using the Log Zipper utility. The Log Zipper utility also offers the following additional features:
- Log zipper can zip *.n log files.
- You can define the maximum size for a zip file (1024 MB) that eases the file transfer.
- Centralized configuration data is exported and collected by Log Zipper.
For more information about Log Zipper enhancement, see Collecting diagnostics in a zip file.
BMC Remedy Deployment Application enhancements
BMC Remedy Deployment Application is improved with the following enhancements:
View Activity Log UI
The View Activity Log tab opens a new browser window displaying a table of activity logs. When you select an entry, the Description and Status Reason fields are displayed.
Archive process for previously deployed packages
You can archive previously deployed packages from the AR System Deployment Management Console. You can also archive a package prior to the default age. For more information about archiving a package, see Archiving a package.
Application object for deploying tasks and task group templates
Use the Application object Content Type to deploy tasks or task group templates across environments. For more information, see Application Object.
Email notification about the status of the package
You can configure an email address on the AR System Deployment Management form to receive email notifications about the status of your package. You can configure single or multiple email IDs (separated by semicolon) or an email distribution list.
Define Pre-Check for a package
You can define a Pre-Check for a package. Pre-Check is a qualification that runs before you deploy or rollback a package. For more information on Pre-Check, see Defining a Pre-Check.
You can now select multiple objects when you add a definition or you add a delete definition to the package.
Notifications about mid tier user session timeout
The browser displays mid tier session timeout notification five minutes prior to the mid tier session timeout. This feature allows you to extend the mid tier session and helps avoid an abrupt session timeout.
When you click OK, the session continues for the specified time. If you click [X] on the notification dialog box, the session times out after the number of minutes shown on the notification dialog box (provided you keep the system idle). For more information about the mid tier session timeout alerts, see Enabling notifications for mid tier session timeout.
Audit report for SHARE:Application_Properties form
A new Audit tab on the SHARE: Application_Properties form shows the audit details. You can download the audit report, using the Report button on the Audit tab. For more information, see Share Application Properties
The AR System Report Console has a new category for auditing the SHARE: Application_Properties form. You can download audit report for all the records on the SHARE: Application_Properties form, using this category.
Reduced CPU resource usage for BMC Remedy Mid Tier
The CPU resource usage on systems running BMC Remedy Mid Tier is reduced by about 50%. The actual CPU usage reduction in your Remedy environment depends on the specific workload.
Enhanced web services
The web services now support the NTLMv2 authentication and use the XSI type for all elements. The web services validations are widely tested to cover the enhanced automation. Additionally, web services are improved with the following enhancements:
Refactored XML APIs
- Simplified the XML request/response parsing code to remove complexities in element validation.
- Refactored attachment data retrieval mechanism to improve the performance of GET calls.
Honoring the WSDL file
The web service always honors the WSDL file specified while parsing input request or sending a response. The elements are processed in the order defined in WSDL.
- The AR System Server honors the order of elements specified in WSDL.
- The AR System Server honors the
Nillableattribute defined for an element in WSDL and updates a value in a field associated with this element.
- When you do not specify
minOccursattribute for an element in WSDL, the AR System Server considers that the
minOccursattribute is one and throws the run time exception, if that element is missing from the XML input request.
- Exception for XML element:
(8961) A required element is missing from the XML input document.
- Exception for XML attribute:
(8969)- A required attribute is missing from the XML input document.
- Exception for XML element:
Refer to the following examples:
- In an input field, if you specify a
Nillableelement with a blank value, the AR System Server updates the field that is mapped to the
Nillableelement with a NULL value.
- When the AR system server returns a response to any
Nillableelement in output mapping, the AR System Server returns the element with an empty value and NIL attribute.
Improved validation logic
- The AR System Server throws the following exception when the required form mapping element is missing in the input request.
(8961) A required element is missing from the XML input document.
- Removed redundant code for entry validation.
- The AR System Server honors the default value when a required element has the default value specified in WSDL.
- The AR System Server throws an exception when you provide a different type of data to an element.For example, an exception occurs when you provide a String type of data to an element that holds integer type of data.
The AR System Server shows the following error when incorrect value is entered in the Selection field.
(306) Value does not fall within the limits specified for the field.
The following error is displayed when you specify a NULL value in the Currency field.
(8735) Bad decimal value.
The following error is displayed when currency code information is missing from the currency value.
(985) No active Currency Code found on the Currency Code form.
Handling Parent-child relationship
- The AR System Server now supports using parent-child relationship on a submit event.
- The AR System Server consolidates mapping and populates data in all fields including parent-child.
Refactored WSDL generation logic
Refactored WSDL generation logic helps to populate the required attributes and honors the following criteria:
- If you specify a default value for an XML element, the default value is reflected in WSDL.
- If you specify a minOccur attribute for an XML element, the minOccurs attribute is reflected in WSDL.
- If you specify a maxOccur attribute for an XML element, the maxOccur attribute is reflected in WSDL.
- If you specify a NIL attribute for an XML element, the NIL attribute is reflected in WSDL.
What's changed in this release
Version 9.1.04 has introduced the following significant changes in the product behaviour:
|Enhancement||Product behavior in versions earlier than 9.1.04||Product behavior in version 9.1.04|
Customizing the armonitor.conf file.
|The previous versions of BMC Remedy AR System do not allow you to customize the armonitor.conf file.||When you have additional processes for the armonitor.conf file, you can choose to create a copy of the armonitor.conf file and store the copy at the different location. The -c parameter instructs the armonitor to load information from the specified configuration file. For more information, see armonitor.conf or armonitor.cfg.|
|Using the ||The previous versions of BMC Remedy AR System do not allow you to replace the server name in the following forms:||The |
For more information, see Renaming the AR System server.
|Using the jetty-http.xml file for configuring the REST API.||The previous versions of BMC Remedy AR System use the jetty-selector.xml file to configure the REST API.||This version uses the jetty-http.xml file to configure REST API. For more information, see Configuring the REST API.|
|Restrictions for accessing the records.||In the previous versions of BMC Remedy AR System, a deployment manager has access to all the available records. The deployment manager can create, build and deploy a package with all the available records.|
A user who is not an administrator can view a record and create or build a package with only those records that are created by him. An administrator can view all the records and can create or build a package with all the available records.
For example, Allen, a deployment manager, creates five records on a form. He creates and saves a package with five records. When Allen builds and deploys the package, it has five records.
Ian, another deployment manager, creates another eight records on a form. He creates and saves a package with eight records. When Ian builds and deploys the same package saved by Allen, the package has eight records created by him.
Mary, who is AR System Administrator, can see all the records created by Allen and Ian. When Mary builds and deploys the package created by Allen, the package has all the available records (13 records).
|The Encryption tab from BMC Remedy AR System Maintenance tool is removed.||BMC Remedy AR System Maintenance tool Encryption tab allows you to generate an encrypted password to use when running a silent installation.|
The Encryption tab from BMC Remedy AR System Maintenance tool that allows you to generate an encrypted password to use when running a silent installation is removed.
You can encrypt password using the following commands from the command line:
|Increased memory for AR Plug-in server||The AR Plug-in server memory is 512 MB.||The AR Plug-in server memory is increased to 1024 MB.|
|Automatic management of server groups|
Server groups are not automatically managed.
The default value of the Server-Group-Member option is F.
Server groups are automatically managed.
The default value of the Server-Group-Member option is T.
|The support for ||BMC does not support the |
The Db-Connection-Retries property is deprecated.
|This property helps in re-establishing the lost connection with the database.|
The AR System server honors every request to connect with database. The following error is displayed if the database is not available during a client activity:
When the database is not available, the administrator can see the following error in the arerror.log file, located in the db folder.
However, the AR System server keeps running. If the database becomes available again, the AR System server makes a new request to connect to the database.