Lookups are executed by the SRT during the processing of an upstream XML service request. Lookups can be used to look up additional parameters that are required for activation of services, to format parameters so that they are compatible with service action parameters, and so forth. The Lookup library contains custom lookups that are used by the SRT only.
To create new lookups:
Select Studio, then select Show Design Perspective.
In the Studio Projects view, right-click and select New, select Activation, then select Lookup.
Alternatively, select Studio, select New, select Activation, then select Lookup. The Studio Model Entity wizard appears.
Select the applicable project from the list and enter a name for the lookup.
Click Browse to open a Select Location dialog box and select a location from a list.
This populates the Location field and specifies the folder under the cartridge project where the new lookup will be located. If no folder exists, type in the location name, which creates a new folder with that name.
Note:
Specifying a location is optional, but is recommended to organize your elements and to avoid locating elements directly below the root folder.Click Finish.
The new lookup appears under your project folder in Studio view.
Use the Lookup editor to configure the lookup.
Double-click the lookup entity.
The Lookup editor opens.
From the Type list, select a lookup type.
If you select type as JAR, see "Selecting Lookup Class for JAR format" for more information.
In the Lookup Properties area, define the properties for the lookup.
In the Input Parameters tab, click Add.
An input parameter is added.
Click the specific row and configure in the Input Parameter Details area.
In the Output Parameters tab, click Add.
An output parameter is added.
Click the specific row and configure in the Output Parameter Details area.
Select File, then select Save.
Modeling ASAP SRT Implementations
If you have selected ASAP version 5.2 and have defined lookups with input parameters that map to other lookups, an additional source attribute is generated in the lookup model xml.
Precondition: SRT project is created for Activation 5.2.
Precondition: Two lookups are created in the same cartridge (for example LK1, LK2)
Create a lookup.
For example, LK3.
Add an input parameter (lookup type).
Map to another lookup.
For example, map to LK1.
Save the lookup.
From the Package Explorer view, cartridgeBuild/model, examine the lookup.xml.
For example, LK3.xml: A new attribute has been added called sourceDocument=
Consider the following code example, which illustrates the previous stepped procedure:
<inputParameter> <parameterName>inParm4</parameterName> <lookupParameterName> outParm1</lookupParameterName> </inputParameter>
would become
<inputParameter> <parameterName>inParm1-lk3</parameterName> <lookupParameterName sourceDocument="LK1">outParm1-lk1</lookupParameterName> </inputParameter>
To select lookup class in the jar file that performs the lookup:
On the Lookup editor, click Select to open Select Lookup Class dialog box.
Do any one of the following:
In the Select entries field, enter the name of a class which exists in a .jar file referenced in the classpath.
Enter any character or string of characters contained in the class name. Matching class names appear in the Matching items area of the dialog box.
Select a class name in the dialog box and click OK to populate the class name in the Class field.