Implementation Guide › Implementation › Data Gathering (Data Source Expert) › Automatic Translations with Translation Scripts

Automatic Translations with Translation Scripts

Automatic Translation is the automation of the creation and translation processes and infrastructure, based on an external data source using scripts that run and perform the Translation actions.

Automatic Translation is done through translation scripts. Translation scripts speed up the process of mapping new IT and business resources into CA Business Service Insight. The translation script automatically identifies when a new translation entry is received and translates resources, allowing for quick and efficient resource mapping. The automation supports the interface to CMDBs, enabling the system to identify resources based on their configured definition. Automatic translation has a number of benefits, including easing the maintenance of translations and preventing errors. Translation scripts can be used to create new resources and allocate changes.

Additionally, translation scripts can be used to:

• Translate entries to existing CA Business Service Insight objects.
• Add new CA Business Service Insight objects and translate to them based on existing translation entries.
• Create objects and translate entries on the basis of tables outside CA Business Service Insight, for example, resource tables from another external CMS.
• Check whether an object exists.
• Create resources and perform resource allocations, such as, resource types, resource groups, contract parties, and service components.
• Allocated/Deallocate resources to Change Sets.

Since the translation process is also supported as a manual procedure in the user interface, a decision on which translation process to choose is required. When doing so, consider the following pros and cons concerning automatic translation:

• Increased project complexity-translation scripts require appropriate skills and script development efforts.
• Added development time as well as Quality Assurance time for testing.
• Need not be implemented in cases when the translation process is merely a one-time initial effort.
• Can be scheduled for implementation as part of a second phase approach.
• Reduced ongoing maintenance.
• Reduced human translation errors.
• For further information on creating and executing Translation Scripts please refer to the SDK guide in the CMDB Integration chapter.