NOTE: 2012-03-04: This has been reposted under the BMC Remedy forum where I will maintain my future DM blog entries.
The latest Remedy 8.0 release includes significant improvements to the Data Management features allowing imports of data from spreadsheets, LDAP-enabled directories and databases. These features can reduce the manual input of numerous records throughout the system and ease the process of creating/updating many types of records and on-boarding new system users, support groups, etc.
A system administrator must configure a location to which data management servers may write temporary files for their operation. Because data management jobs may be processed by multiple servers in a single environment, the location must be shared by all DM servers in the environment. This setting is made in the Administrator Console > Application Administration Console > Custom Configuration
> Foundation > Advanced Options > System Configuration Settings - System Settings.
For Windows-based servers, the share is defined as a universal naming convention (UNC) compliant shared folder (e.g., \\server\sharedfolder\). Note that the trailing slash is required, and you must create this share before testing the shared path.
For Linux/Unix-based servers, the location is a file system location (e.g., /opt/sharedfolder/). Note that the trailing slash is required. Linux/Unix servers may share a common SAN (storage area network) LUN (technically, this is a logical unit number however, it is frequently used interchangeably with ‘virtual hard drive’ that a SAN provides to a client) which may be shared across multiple Linux/Unix servers as a mounted volume.
A user must be a member of the appropriate permissions group in order to access the Data Management (DM) features.
The two permission groups and a brief description of their capabilities are:
- DMT Admin – Membership in this group grants full control over all DM features and access to all jobs regardless of tenant or company from which the job was initiated or impacted.
- DMT User - Membership in this group grants full control over all DM features and access to all jobs for a particular tenant or company to which the user in a member.
Lastly, if you rename your midtier (e.g. from oldserver to myserver), you likely need to create a new entry (or update the existing one) in the UDM:RAppPassword form (e.g. http://myserver:8080/arsys/forms/myserver/UDM:RAppPassword ).
- Click New Request.
- Set Server Name to myserver. (I had to add an entry for TEN after installing as LOCALHOST.)
- Set RApp Password to <whateveryourpasswordis>.
- Click Save.