BMC Remedy AR System server enhancements in version 9.0.00
This topic provides information about the following BMC Remedy AR System server enhancements.
The new improved archiving offers the following:
- All the forms are archived on a common global schedule.
- Related data in multiple forms can be archived in a single transaction.
- The archive definition includes an age qualification.
- An archive management console has been introduced.
For more information, see Archiving Concepts.
- In version 9.0, archives must be of type copy and delete or delete. Any archives that are of type copy at the time of upgrade will be converted to copy and delete. This ensures that records in the archive form are unique.
- Starting 9.0, vendor form and join form cannot be archived. Any existing archive defined for join form and vendor form is ignored for archiving.
Restrictions for users and groups
Starting with this release, new restrictions are added that prevents you to create other users with more administrative rights than yourself, and to modify your own rights.
The new restrictions prevent:
- Creation of an administrative user by a nonadministrative user.
- Creation of an administrative user with access to more overlay groups than the administrative user who created them.
The following restrictions apply before and after you create or modify any user in the User and Group form.
- Only an administrator can create, modify, or delete other users belonging to the Administrator, Sub-Administrator, Struct Admin, or Struct Sub-Admin groups.
- A user must have Group ID 1, AR System Administrator rights, and Fixed License in the group list to create, modify, or delete another user of any of the four administrative class groups in their group list.
- No administrator user can create or modify a user (themselves included) with lesser administrative restrictions than themselves.
For example, an administrator user with Overlay Group 1 rights cannot create or modify users who are not a part of overlay groups. Consider a situation where you have created an ABCGroup with an Overlay Group set to 1. User ABCAdmin is part of the Administrator group and the ABCGroup. However, ABCAdmin is restricted only to the ABCGroup. ABCAdmin can change (create/modify/delete) any user belonging only to the ABCGroup. For more information about creating a group as an overlay group, see Creating groups.
- A user cannot create another administrator with the ability to modify base objects if they themselves cannot do it.
- Only an unrestricted administrator can create, modify, or delete groups that restrict a user’s administrative capabilities.
- Only an administrator without an overlay-specific groups can create, modify, or remove overlay-specific groups.
For information about creating and modifying user information, see Adding and modifying user information.
Before this release, BMC Remedy AR System components stored their configuration data in separate files. Configuration data for the AR System server and the BMC Remedy Approval Server was stored in the ar.cfg (ar.conf) file; the data for Mid Tier was stored in the config.properties file; the data for the BMC Remedy Email Engine was stored in the emaildaemon.properties file; and the data for the Java plugin server was stored in the pluginsvr_config.xml file. Because the configuration data was dispersed across files, it was difficult to share the data across servers, or to backup or restore data. This decentralized structure also led to maintenance issues, data redundancy, and low data security.
Starting with this release, configuration data is stored in new centralized configuration forms and reflected in the ar.cfg configuration file (for backward compatibility). Centralized configuration not only makes configuration data easier to manage, but also makes it easy to share the configuration settings across servers. Also, because configuration data is stored directly in the database, it is more secure.
With this release, the configuration data for the following components is centralized:
- BMC Remdy AR System server
- BMC Remedy Mid Tier
- BMC Remedy Approval Server
- BMC Remedy Email Engine
- BMC Remedy Java plug-in server
For more information, see Centralized configuration.
Before this release, companion services were dependent on, and shared the state of the AR System servers. If the AR System server failed, all the dependent services also failed.
Starting with this release, the servers in the group cooperate together to manage service failover. The server group manages when the companion services become active to perform tasks and when they are suspended. Also, the companion services are tracked and can fail over independently of any AR System server.
For more information, see Service failover.
AR System server queue threads configuration changes
The AR System server scheduler has many work queues, such as queues for archiving, for escalation pool 1, for escalation pool 2, and so on. Before this release, each queue had its own dedicated thread. When jobs were triggered, they were automatically put in the appropriate queue to make sure that they were serialized with the other jobs in the same queue.
Starting with this release, AR System server uses threads from a thread pool. A scheduled request is received by the first available thread. After the request is processed, the thread returns to the pool and becomes available for another request.
The Fast, List, and Private queues do not use threads from the thread pool.
For more information, see in the BMC Remedy ITSM Deployment documentation.
Service operations monitoring
You can now monitor the number of emails sent and received from AR System server in an hour. For more information, see Monitoring service operations.
Limiting entries in a report
Starting with this release, you can add the new
maxEntriesInFileReport parameter to limit the number of entries in a BMC Remedy Action Request System (AR System) report using AR System Administration:Plugin Server Configuration form. For more information, see Limiting entries using a published report.
API call monitoring
You can now monitor the API calls between an AR System server and its clients and capture information such as the number of API calls based on the client type, the total amount of data sent to the client, the number of successful API calls, and so on.
For more information, see Monitoring API calls.
Enhanced logging features
BMC Remedy AR System now provides the following enhanced logging features:
Modify the logging parameters such as log file name, log file size, logging level and so on, without restarting the process. Modifications to the logging parameters are applied immediately, without an interruption to the service or to the business.
The logging configuration enhancements are available in:
Restrict logging to specific criteria.
Typically, you turn on logging to troubleshoot issues. Generally, log files capture all the information for an area being logged, which impacts the system performance. The log files capture more information than required and their large size consumes additional disk space. The logging restriction feature allows you to capture only the required information in a log file, so that it has less impact on system performance, and extra information is not recorded. You do not have to parse through large log files to find the source of an issue.
The logging restriction enhancement is available in:
Format log files consistently. Data is presented in a familiar format to help you parse log files and find root cause issues easily.
The formats of following log files are consistent with the AR System server log files:
Full-Text Search enhancements
The following enhancements for Full Text Search (FTS) are available:
|High Availability for FTS|
In a server group environment, Full Text Search (FTS) can be configured for High Availability so search requests are completed even when a server in the group becomes unavailable. Under the FTS HA model:
For more information, refer to Enabling FTS high availability.
|FTS indexing with schema-specific files improved|
AR System uses the Lucene 4.9 search engine for Full Text Search (FTS) and uses a schema-specific multi file index format to optimize read/write operations, resulting in searches that are about three times faster and indexes that are about 40 percent smaller than the Lucene 2.9 index used in earlier releases.
For more information, refer to FTS index migration.
|FTS components upgraded to latest releases|
|FTS index migration utility|
The Full Text Search (FTS) index migration utility arftsutil migrates the single-file Lucene 2.9 index into a multi file schema-specific index compatible with the Lucene 4.9 search engine. The arftsutil utility is embedded in the interactive GUI AR System installer, so existing Apache Lucene 2.9 single-file indexes are automatically migrated to the Lucene 4.9 schema-specific multi file format. Automatic migration can be skipped when you use the silent installer. The arftsutil utility can be run from the command line to migrate an existing Lucene 2.9 index to the 4.9 format.
For more information, refer to FTS index migration.
New AR System Server Object — Association
The BMC Remedy AR System now offers a way to explicitly define relationships using Association, a new AR System server object. In AR Applications, relationships between forms are implicit since they are defined by creating workflow that ties them together using various actions. This makes it harder for one to understand dependencies and thus the application as a whole.
Enforced associations eliminate the need to create workflows to enforce referential integrity and deleting related data. Reducing the number of workflows for applications makes them easier to understand. Association can also be used to get related data and archive them as well.
For more information, see Associations Overview.