Phased rollout

 

This version of the software is currently available only to early adopter SaaS customers as the first step in our phased rollout. Click here to view an earlier version.

Configuring forms to use DSO unique prefixes

Important

The Distributed Server Option (DSO) is available only for on-premises deployments.

When you are using a distributed environment that has more than one AR System server that can create records, the servers might create records with the same ID. It is important, therefore, to make sure that the servers create records with unique IDs. To do this, you create a record ID prefix that is unique to the AR System server that created it. For example, in a two-server environment where the servers are named Server 1 and Server 2, change the prefix for incident request records on Server 1 from the default INC to S1INC and on Server 2 to S2INC. These designations let your system distinguish between incident records that were created on Server 1 and Server 2.

You can use different prefixes to identify tickets for different companies. For example, an AHD prefix identifies incident tickets for ABC Corp, and an XHD prefix identifies incident tickets for XYZ Company.

To assign unique prefixes to records, you must first configure the AR System server to use custom prefixes. How to do this is described in the following procedure. After you configure the AR System server, you then create the custom ID prefix for the forms to use.

Warning

If you are configuring a hub and spoke environment, do not create unique prefixes with this method. Instead, use the Running the Prefix Manager to create the unique prefixes.

To configure forms to allow unique prefixes

  1. From your browser, log in to the AR System server through Mid Tier by using an ID with application administrator privileges.
  2. From the Application Administration Console, click the Custom Configuration tab.
  3. From the Application Settings list, select Foundation > Advanced Options > System Configuration Settings - System Settings, and then click Open.
  4. To enable the capability to define unique prefixes for records, select Enable User Defined Prefix.
  5. Click Save.
    All configurations and settings are now available for use.

To create a custom form ID prefix

  1. From your browser, log int o the AR System server through Mid Tier by using an ID with application administrator privileges.
  2. In the browser's address bar, type the following URL and then press Enter:
    http://<mid-tierServer>/arsys/forms/<ARserverName>/SHR:SchemaNames
    The SHR:SchemaNames form opens in the Object list.

  3. Search for the schema that requires a custom prefix by typing the form name in the Schema Name field on the search form.
  4. Select the Form Lookup tab.
  5. In the User Defined Prefix field enter up to five characters.
  6. Save the record and close the form.
  7. Repeat step 3 to step 6 for all forms that require a custom prefix.
  8. Log in to either AR System Administrator tool or Developer Studio, depending on the version of BMC Helix ITSM you are using.
  9. Open one of the forms that you modified in the previous procedure.
  10. Do one of the following actions, depending on whether you are using AR System Administrator Tool, or Developer Studio.

    AR System Administrator Tool

    Developer Studio

    1. Open the Field Properties dialog box by selecting field ID 1 from the ID Field list on the toolbar, and then clicking the Field Properties button.
    2. Select the Attributes tab, and change the default field values to specify the new custom prefix that you specified on the SHR:SchemaNames form.
    1. In the Outline tab, select field ID 1.
    2. In the Properties tab, select the Default Value property, click its ellipsis button, enter the custom prefix, and then click OK.

    Important

    If field ID 1 is not in the view, you must bring the field into the view. Be sure to remove it from the view when you finish. The field ID 1 names are listed in Forms that require a prefix.

  11. Close the Field Properties tab or the Properties window.
  12. Save the form and close it.
  13. Repeat steps step 9 to step 12 for all forms that are listed in Forms that require a prefix.

    Important

    You must add a custom prefix to the files listed in the Forms that require a prefix section. We recommend, however, that you apply a custom prefix to all forms used in your DSO implementation.

  14. After each form has custom prefix settings, you must recache the form data and then the distributed environment is ready to use.

Forms that require a prefix

Form

Field ID 1

Default Prefix

AST:CI Unavailability

CI Unavailability ID

AOT

AST:CMDB Associations

Associations ID

AAA

AST:PurchaseOrder

Order ID

PO

AST:PurchaseRequisition

Requisition ID

PR

AST:PurchaseRequisitionWorkLog

Work Log ID

PWL

AST:WorkLog

Work Log ID

AWL

CHG:Associations

Associations ID

CHA

CHG:CFG Ticket Num Generator

Request ID

CRQ

CHG:Infrastructure Change

Request ID

CRQ

CHG:Template

CHG Template ID

CTP

CHG:Template Associations

Associations ID

CTT

CHG:TemplateSPGAssoc

TemplateSPGAssoc ID

CTE

CHG:WorkLog

Work Log ID

CWL

RMS:Associations

Associations ID

RLM

RMS:CFG Ticket Num Generator

Request ID

RLM

RMS:Template

RMS Template ID

RTP

RMS:Template Associations

Associations ID

RTT

RMS:WorkLog

Work Log ID

RWL

HPD:Associations

Associations ID

HAS

HPD:CFG Ticket Num Generator

Incident Number

INC

HPD:Help Desk

Entry ID

INC

HPD:Help Desk Assignment Log

HPD Assignment Log ID

HDA

HPD:Template

HPD Template ID

HTP

HPD:Template Associations

Associations ID

HTT

HPD:WorkLog

Work Log ID

WLG

PBM:CFG PI TicketNumGenerator

Request ID

PBI

PBM:Problem Investigation

Sys-Problem Investigation ID

PBI

PBM:CFG KE TicketNumGenerator

Request ID

PKE

PBM:Known Error

Sys-Known Error ID

PKE

PBM:CFG KDBTagNumGenerator

Solution Database Tag Number

SDB

PBM:Solution Database

Request ID

SDB

PBM:Investigation Assgnmt Log

PBI Assignment Log ID

PAL

PBM:Investigation Associations

Associations ID

PAS

PBM:Investigation WorkLog

Work Log ID

PIW

PBM:Known Error Associations

Associations ID

KEA

PBM:Known Error WorkLog

Work Log ID

WKE

PBM:Solution DB Alias

Knowledge Database Alias ID

KDA

PBM:Solution DB Associations

Associations ID

KBA

PBM:Solution WorkLog

Work Log ID

KDW

PBM:Template

PBM Template ID

PMT

Foundation and Common forms

AAS:Activity

Request ID

AAS

AAS:ConfigurationTicketNumGenerator

WOI_Number

AAS

AAS:Template

AAS Template ID

ATP

AAS:WorkInfo

Work Log ID

AWI

COM:Company

Company Entry ID

CPY

COM:Company Alias

Company Alias ID

CPA

CTM:People

Person ID

PPL

CTM:Region

Region ID

RGN

CTR:Contract_Relationship

Relationship ID

CRE

CTR:Rights_Granted

Request ID

CRG

CTR:Terms_Conditions

Request ID

TAC

CTR:WorkLog

Work Log ID

CWL

SIT:Site

Site ID

STE

SIT:Site Alias

Site Alias ID

STA

TMS:Task

Task ID

TAS

Where to go from here

Configuring your DSO environment for data transfer and deletion

Was this page helpful? Yes No Submitting... Thank you

Comments