Translation Table Details

This window can be displayed in two different ways:

• In the translation tables list, click New, Display, Update, or Duplicate.
• In the Deployments list > New Deployment, in the Source section, right to the Translation Table field, click New.

It allows you to create either a saved translation table that can be reused, or a temporary translation table for a deployment. The creation mode depends on the selected action, respectively Save or Ok (described below).

Local objects are displayed in the value help lists but it is possible to manually enter a name. If this object does not exist, an error will occur during the deployment.

The list can be sorted using the Move Up and Move Down buttons. The list order determines the priority of assigning a translation. Please refer to section Translation rules.

Actions

• Import File

  Imports a translation table from a backup file. The user can import data from a .txt file created manually or generated by a translation table export. Depending on the Import File button used :

  • Window main tool bar: the user can import the file data to the translation table.
  • Section tool bar: the user can import the file data to the translation table section.

  Click Import File to display an Open dialog box. Browse through the folders and select the file to import. Then click Open to import the file data to the selected table.

  If the file does not contain data of the section type in which the import was requested, nothing will be imported and no error will be logged. Only the data corresponding to the target section are imported.

• Export File

  Exports a translation table to a backup file. A backup file may be used to import a translation table to another Univiewer Management Server. Depending on the Export File button used:

  • Window main tool bar: the user can export all the translation table to a file.
  • Section tool bar: the user can export the translation table section to a file.

  Click Export File to display a Save dialog box. Change the file default name (_export.txt) and select the destination folder. Then click Save to create the file in the selected folder.

• Save

  Saves the translation table in the translation tables list. It is not mandatory if the window has been opened from a New deployment. In this case, the user can create a temporary translation table by clicking OK at the bottom of the window.

• OK

  Only displayed if the window has been opened from a New deployment. It allows you to create a temporary translation table (not saved in the translation tables list). In this case, the temporary translation table that has been created will be used for this particular deployment but can not be reused nor viewed later.

Format of the Export File

The translation table export file is a text file that can be opened and edited with a text editor. It consists of lines whose format is as follows:

KEYWORD;source object;translated object

The keywords are:

• USER for a user
• MU for a management unit
• MUTYPE for a management unit type
• QUEUE for a batch queue
• NODE for a node

For a same keyword, the order in the file is important. For each object type, the first translation found determines the target object.

General

• Name

  Name of the translation table that will be displayed in the translation tables list and in the New Deployment window.

MU Translation

This list displays the translation rules that should be applied to the management units contained in the objects before the deployment.

The translation of a management unit allows you to change:

• A dependent management unit in a MU
• The management unit in a Uproc condition
• The execution management unit of a Uproc in a session
• The management unit of a task

Click Add to add a new translation rule:

• MU Name: Select the source management unit.
• Translation: Select the management unit that should replace the source MU in all the objects that will be targeted by the deployment.

Then click OK to confirm.

MU Type Translation

This list displays the translation rules that should be applied to the management unit types contained in the objects before the deployment.

The translation of a management unit type allows you to change:

• The MU type or the HDP of a condition in a Uproc
• The MU type or the HDP of a Uproc execution context in a session

Click Add to add a new translation rule:

• MU Type Name: Select the source management unit type.
• Translation: Select the management unit type that should replace the source MU type in all the objects that will be targeted by the deployment.

Then click OK to confirm.

User Translation

This list displays the translation rules that should be applied to the users contained in the objects before the deployment.

The translation of a user allows you to change:

• A MU default submission account
• A task submission account

Click Add to add a new translation rule:

• User Name: Select the source user.
• Translation: Select the user that should replace the source user in all objects that will be targeted by the deployment.

Then click OK to confirm.

Queue Translation

This list displays the translation rules that should be applied to the batch queues contained in the objects before the deployment.

The translation of a batch queue allows you to change the execution batch queue of a task.

Click Add to add a new translation rule:

• Queue Name: Select the source batch queue.
• Translation: Select the batch queue that should replace the source batch queue in all tasks that will be targeted by the deployment.

Then click OK to confirm.

Node Translation

This list displays the translation rules that should be applied to the nodes contained in the objects before the deployment.

The translation of a node allows you to change the residence node of a management unit.

Click Add to add a new translation rule:

• Node Name: Select the source node.
• Translation: Select the node that should replace the source node in all MU that will be targeted by the deployment. If the localhost keyword is entered in this field, the node of residence in the MU after deployment will be the target node used in the Destination section of the deployment.

Then click OK to confirm.