Installation Guide › Configuring the Server Post Installation › Optional Configuration Procedures › How to Use Image Files in Entity Records

How to Use Image Files in Entity Records

You can associate an image file with each user, role, or resource entity in the CA RCM database. This file is displayed in information and certification screens of the CA RCM portal. Each image file is matched to an entity based on the value of an attribute field.

To use image files in entity records

1. Plan implementation of image directories. Consider the following:
   • You can reference existing image directories, or create new directories locally on the CA RCM server. Image directories on other hosts in your network environment must be accessible to CA RCM server.
   • Use one or more user, role, or resource attributes to select the image that corresponds to a specific user, role, or resource. You can use existing attributes, or create attributes for image mapping.
2. (Optional) If you use new user, role, or resource entity attributes for image mapping, define them in the CA RCM portal or CA RCM client tools.
3. In the CA RCM portal, click Administration, Settings, Properties Settings and edit the following properties:

   user.image.url

   Defines a URL template that lets CA RCM retrieve an image for a specific user record. Typically this template combines the pathname of the image directory with wildcards for user attributes. In the following example, the /users directory on the CA RCM server stores user images, and the userID attribute identifies individual images.

   http://RCM_host:port/users/$(userID).jpg
   

   Note: RCM_host and port are the network address and communications port of the CA RCM server, and $(userID) is a placeholder for the actual value of the userID attribute.

   When CA RCM displays the user record with userID value of 2384 it retrieves the file 2384.jpg from the target pathname.

   role.image.url

   Defines a URL template that lets CA RCM retrieve an image for a specific role. Typically this template combines the pathname of the image directory with wildcards for role attributes. In the following example, the /roles directory on the CA RCM server stores role images, and the userID attribute identifies individual images.

   http://RCM_host:port/users/$(Owner).jpg
   

   Note: RCM_host and port are the network address and communications port of the CA RCM server, and $(Owner) is a placeholder for the actual value of the Owner attribute.

   When CA RCM displays the role with Owner value of 2384 it retrieves the file 2384.jpg from the target pathname.

   resource.image.url

   Defines a URL template that lets CA RCM retrieve an image for a specific resource record. Typically this template combines the pathname of the image directory with wildcards for resource attributes. In the following example, the /resources directory on the CA RCM server stores resource images, and the ResName3 attribute identifies individual images.

   http://RCM_host:port/users/$(ResName3).jpg
   

   Note: RCM_host and port are the network address and communications port of the CA RCM server, and $(ResName3) is a placeholder for the actual value of the ResName3 attribute.

   When CA RCM displays the resource record with ResName3 value of Unix_admins it retrieves the file Unix_admins.jpg from the target pathname.

4. (Optional) Create image directories corresponding to the pathnames you specified in the system parameters. Copy and rename image files to populate the directories.
5. (Optional) Replace the default images that CA RCM displays when a user, role, or resource entity does not have a unique image file.

   For CA RCM server on Windows/JBoss, replace images located under the following directory:

   RCM_install\Server\eurekify-jboss\server\eurekify\deploy\eurekify.war\img
   

   Note: RCM_install is the CA RCM installation directory.

   Name the new image files as follows. Overwrite or rename existing files.

   • Default user image: User_Silhouette.gif
   • Default role image: UserGroup_48.png
   • Default resource image: Resource_48.png