This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

9.1.00 enhancements

This topic provides information about the following enhancements in this release:

The following interactive graphic summarizes enhancements for the BMC Remedy Action Request System 9.1. (The graphic may take a few seconds to load).

Centralized configuration available for more parameters

In the 9.1 release, parameters for the following components have been migrated to the centralized configuration console:

  • BMC Remedy Distributed Server Option
  • BMC Remedy Flashboards server
  • BMC Remedy Assignment Engine
  • AR System Database Connectivity (ARDBC) LDAP plug-in
  • AR External Authentication (AREA) LDAP plug-in 

Previously, these parameters were stored and configured either in the ar.cfg file or in the server.conf file. Starting from this release, changes to the parameters of these components are made only through the centralized configuration console. You cannot configure the parameters using the ar.cfg file. For more information, see Centralized configuration.

Improved search relevancy for Multi-Form Search (MFS)

Starting with this release, a new aggregate field is added to the index file for Multi-Form Search. The aggregate field is a collection of all the fields in the index file and the AR System server searches on this field to produce better search results. For more information, see Performing searches on multiple forms.

Enhancements to armonitor

In BMC Remedy Action Request System 9.1, a new Java-based process armonitor is used to maintain a list of all BMC Remedy AR System processes. The armonitor file provides functionality to detect changes made to the armonitor.cfg (armonitor.conf) file. The armonitor feature includes a utility that allows you to start, stop, and restart the processes maintained in armonitor.cfg (armonitor.conf) file. For more information see, armonitor.

Field encryption

Starting from BMC Remedy Action Request System 9.1, you can configure the character field as confidential so that the data remains encrypted in the database. To encrypt the data in the character field you must set the property Encrypt Data At Rest to True. For more information, see Encrypt Data At Rest.

Improved functionality for BMC Remedy Deployment Manager

The following enhancements for BMC Remedy Deployment Manager are available:

EnhancementDescription
Rollback functionalityRestores the objects in a package to the pre-deployment state if any issues are found during validation of the package after the package is deployed successfully. For more information, see Rollback
Migration support for Service Request Management (SRM) objectsTransfers BMC Remedy AR System service request definitions (SRDs), process definition templates (PDTs), and supporting data easily and reliably across environments. For more information, see Adding SRM objects to a package
Support for migrating base and overlay objectsStarting from this release, you can now include base and overlay objects in a package and migrate them across environments. For more information, see Defining a package

Enhancements to BMC Remedy Single Sign-On

BMC Remedy Single Sign-On 9.1 release comprises the following enhancements:

EnhancementTopic

Enable LDAP for single sign-on user authentication.

After configuring LDAP authentication for a particular realm, the ID and password entered by the user are validated against the ID and password stored in the LDAP directory.

Configuring BMC Remedy SSO for LDAP authentication

Use silent installations to deploy BMC Remedy Single Sign-On to multiple systems.

Silent installations require installing BMC Remedy Single Sign-On, generating an options file, and then installing BMC Remedy Single Sign-On silently.

Installing the BMC Remedy Single Sign-On using silent mode

Add complex user id transformations.

When you integrate BMC Remedy Single Sign-On with BMC applications by using new authentication methods, the new authentication methods might not provide the same user ID format that was available with previous authentication methods. In such situations, in addition to the default options, you can add complex transformations to the Transformation list in BMC Remedy Single Sign-On by creating customized plug-ins.

Creating a new plug-in to transform user IDs

Export and import server configuration details.

After export, the server configuration details including the templates is exported. During import, after the file is imported, BMC Remedy Single Sign-On is refreshed to display the imported configuration.

Configuring server settings for BMC Remedy SSO
Edit the template used for SAML authentication request.Configuring BMC Remedy Single Sign-On for SAMLv2 authentication

Compatibility and Support enhancements

  • Compatible with BMC Remedy AR System versions 7.6.04, 8.1, 9.0, and 9.1
  • Supports additional platforms
Was this page helpful? Yes No Submitting... Thank you

Comments