This documentation supports the 9.1 version of Service Request Management.

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

Adding customized fields to the People vendor form on ESS

Identity Request Management no longer supported

The Identity Request Management (IRM) module is no longer supported in versions 9.0 and later of BMC Service Request Management. However, IRM continues to be shipped for reference in version 9.1.00 of BMC Service Request Management.

For more information about the end of life of IRM, see Product announcements.

If you add ESS customized fields of data type character, integer, or selection list to People vendor form in Identity Request Management, you must configure the Identity Request Management plug-in and map the fields to the ESS keywords.

Note

Get and Set actions are supported. Create is not supported.

To add ESS customized fields to the People vendor form in Identity Request Management

  1. Restart the BMC Remedy AR System server.
  2. Rename the existing Identity Request Management plug-in jar files:
    • Rename iamplugin.jar to iamplugin.jar.org. This file is located in %BMC_AR_SYSTEM_HOME%/pluginsvr/iam.
    • Rename iamcommon.jar to iamcommon.jar.org. This file is located in %BMC_AR_SYSTEM_HOME%/pluginsvr/iam.
  3. In the ARSystemHomeFolder/pluginsvr/pluginsvr_config.xml file, add <userDefined> tag entries with the correct path to the Identity Request Management home folder.

    <userDefined>
    <irm_home>%BMC_AR_SYSTEM_HOME%</irm <irm_home>
    </userDefined>
  4. Find plug-in entries for RMDY.FILTER.IDM.PLUGIN.AGNOSTIC and RMDY.ARDBC.IDM.PLUGIN.AGNOSTIC plug-ins, and add the <userDefined> tag entries before the </plugin> tag for each.
    Following is an example file:

    <plugin>
    <type>FilterAPI</type>
    <name>RMDY.FILTER.IDM.PLUGIN.AGNOSTIC</name>
    <code>JAVA</code>
    <filename>C:\Program Files\BMC Software\ARSystem\machine1\pluginsvr\iam\iamplugin.jar</filename>
    <classname>com.bmc.remedy.idm.brim.core.plugin.filterapi.IdmFilterAPI</classname>
    <pathelement type="path">C:\Program Files\BMC Software\ARSystem\machine1\pluginsvr\iam</pathelement>
    <userDefined>
    <irm_home>C:\Program Files\BMC Software\ARSystem\machine1\irm</irm_home>
    </userDefined>
    </plugin>
    <plugin>
    <type>ARDBC</type>
    <name>RMDY.ARDBC.IDM.PLUGIN.AGNOSTIC</name>
    <code>JAVA</code>
    <filename>C:\Program Files\BMC Software\IdentityRequestManagement\vw-pun-rem-qa65\plugin\iamplugin.jar</filename>
    <classname>com.bmc.remedy.idm.brim.core.plugin.ardbc.IdmARDBCPlugin</classname>
    <pathelement type="path">C:\Program Files\BMC Software\ARSystem\machine1\pluginsvr\iam</pathelement>
    <userDefined>
    <irm_home>C:\Program Files\BMC Software\ARSystem\machine1\irm </irm_home>
    </userDefined>
    </plugin>
  5. Restart the server.
  6. For each customized field you add to the Person vendor form, create a mapping with the backend ESS keywords.
    For character and numeric data types:
    1. Add a character type field to the Person form.
    2. Select the field.
    3. In the Properties tab, select the Column property, and enter the ESS field name's value (not the field label).
      For field selection data types:
    4. Add Selection field with values to the Person form.
    5. Select the field.
    6. In the Properties tab, select Column, and enter the ESS field name's value (not the field label).
  7. Double-click Selections, and note the selection values and IDs.
  8. Create a csv file in the ARSystemHomeFolder/irm/adapter/adapterName/version/ folder. In the file, add the following information for each value:
    • The ESS field name (as specified in the Column property)
    • The selection ID
    • The selection value on the ESS server.
    • The format for each line is:

      ESSFieldName,selectionID,selectionValue

      For example, you might create a file called PersonAttributes.csv where you add the following lines for the Employee Type field (which is mapped to the emp_type field on the ESS server):
      emp_type,0,Employee
      emp_type,1,Contractor
      emp_type,2,Vendor
      The PersonAttributes.csv file is case-sensitive when used with the plug-in. Use the same csv file to configure all new selection fields on the Person form.

  9. After creating the new keyword in ESS and new field in Vendor form, restart ESS and the Identity Management Suite. Then, flush the mid tier cache and browser cache.
    • Any time that you make any changes to selection data in the adapter configuration or in the csv file, stop the plug-in server, flush the midtier cache, clear browser cache, and re-start plugin server.
    • While searching through the vendor form for a person, specify the value for the Locale field.
    • After you set and save any values for a customized field in the vendor form, the changes are not reflected immediately. To view the updated value in the vendor form, perform a new search.
Was this page helpful? Yes No Submitting... Thank you

Comments