Map Published Data
The Map Published Data object
transforms the existing content of Published Data or Variable items
into new content according to rules that you specify.
When you place this object in a
Policy workflow, you must place it after all Published Data items
that you want to transform have been created by other objects, and
you must place it before objects that will use the new, transformed
items. If you use this object to transform Variable items, you can
place it at the beginning of the workflow.
Configuration
To configure the Map Published Data
object, you will need to know the names of the Published Data or
Variable items that you want to transform, and the information that
you want to replace them with.
Mapping rules tab
The Mapping rules tab displays a list of
all transformations that you have created.
To add a mapping
rule:
1.
|
Click the Add button. The Add Mapping dialog appears.
|
2.
|
In the Output Published Data field, type the
name that you want to assign to the new Published Data item that
you are creating.
|
3.
|
In the Source data field, do one of the
following:
|
•
|
Insert or type the code for the
existing Published Data or Variable items that will be mapped to
the new Published Data item. You can insert as many as you
require.
|
•
|
Type the text that will be
replaced by the new Published Data item.
|
4.
|
In the Pattern field, type the existing
pattern that you want to change from.
|
5.
|
In the Map to field, type the new pattern that
you want to replace the content of the Pattern field with.
|
7.
|
Repeat these steps for each rule
that you want to assign to this mapping.
|
8.
|
Click OK. The Map Published Properties dialog
appears.
|
9.
|
To remove items from the list,
click Remove. To edit an
item in the list, click Edit.
|
Examples
The following is a list of
situations that describe how to use the Map Published Data
object.
Single Published Data or
Variable item
The Read Line object creates a
Published Data item called File
and path name. If the path in this item is expressed as a
drive letter, you can create a mapping to convert it to a UNC
path:
1.
|
In the Source data field, insert the
File and path name
Published Data item from the Read Line object.
|
2.
|
In the Pattern field, type the drive letter
and a colon, such as Y:.
|
3.
|
In the Map to field, type the UNC path that
will replace Y:, such as \\servername\folder.
|
You use products that express
severity levels in two different ways—one in numbers, the other in
words such as High, Medium, Low. You want to convert the numbers
expressed by one product to the words used by the other.
1.
|
In the Source data field, insert the Published
Data item for the severity level from the product that expresses
severity levels in numbers.
|
2.
|
In the Pattern field, type 1.
|
3.
|
In the Map to field, type High.
|
5.
|
Repeat for each severity level,
such as 2, 3, 4, etc.
|
7.
|
When you need to transfer
severity levels to the product that expresses them in words, insert
the Published Data item that you just created in the field. Items
from the originating product with a severity level of 1 will be
placed into the receiving product with a severity level of
High.
|
Wildcards
You can replace strings of words
with wildcards combined with words. For example, a Published Data
item may describe Microsoft Windows 2000 inconsistently, as either
“Win2K”, or “W2K”. Similarly, Microsoft Windows 98 may be described
as “Win98”, while Microsoft Windows 95 may be described as “Win95”.
Using wildcards, you can convert the terms “Win2K” and “W2K” to
“Microsoft Windows 2000”, and “Win98” and “Win95” to “Microsoft
Windows 9x”.
There are two wildcards
available:
•
|
* – use the asterisk to search for any
number of characters after your alpha-numeric search character. For
example, a* will produce aa, aaa, aaaa, aaabbb, and so on.
|
•
|
? – use the question mark to find a
specified number of characters after your alpha-numeric search
character. For example, a?? will produce aaa, abb, abc, aac, but
not aaaa or aaabbb, and so on.
|
1.
|
In the Source data field, insert the Published
Data item that represents the inconsistent names.
|
2.
|
In the Pattern field, type W*2K.
|
3.
|
In the Map to field, type Microsoft Windows 2000.
|
5.
|
In the Pattern field, type win9?.
|
6.
|
In the Map to field, type Microsoft Windows 9x.
|
Multiple Published Data or
Variable items
Operating system names are usually
composed of multiple parts, such as manufacturer, platform, and
variant. For example, Microsoft Windows XP Professional. In Opalis
Integration Server, each of these parts may be represented by an
individual Published Data item. You can combine multiple Published
Data items into one new item, such as Microsoft Windows.
1.
|
In the Source data field, insert each
Published Data item that you want to combine into the new item,
separated by spaces.
|
2.
|
In the Pattern field, type win*.
|
3.
|
In the Map to field, type Microsoft Windows.
|
4.
|
Click Add, then OK. All references will be changed to
Microsoft Windows.
|
Available Published Data
This object only generates Published
Data that you create.