Integration objects play an important role in managing the state of an application or creating a new host connection. However, they typically are used for starting a new HATS connection from within an existing HATS customization. So when should you use an integration object? Web services and combining multiple hosts data onto a single screen are the two options of choice.
Integration objects are essentially a Java wrapper the encapsulates the macro state management. What I mean by that is, you can call setters and getters on the integration object and manage its state.
Macros on the other hand can only be run within the context of either a customization or the macros tab of the default connection. So in case you didn't already know, you can run macros automatically when the connection is established.
So, think of integration objects as an extension to a macro. They still use the .hma script during execution and they given greater flexibility for use in web services or they allow you to create a nice lightweight framework for use with JSF, Richfaces, Spring, Hibernate, and other exciting technologies.
Sirius Computer Solutions[Read More]
HATS HotSpot Blog
Matching: macro X
RationalGerald 0600005S6U Tags:  customization hats macro variables transformation global 1 Comment 7,393 Views
How to use Global Variables to populate Macro Variables in a HATS Transformation MacroIf you want to populate a macro variable with a global variable value, there is an easy way to do so.
The first step is to make sure that there is a global variable to prompt from.
Create a Global Variable
Now we need to make sure that your macro is set up to work with macro variables, and that the macro has a macro variable available to work with.
Create a Macro Variable
This macro variable will show in the source view as
<vars>Now that we have a valid macro variable, we can use it in the prompt action.
Create a Prompt Action
In the source view you can see that the following action was added to the screen.
<prompt assigntovar="$testMV1$" clearfield="false" col="0" default="" description="" encrypted="false" len="80" movecursor="false" name="'gv_to_mv'" required="false" row="0" title="" varupdateonly="true" xlatehostkeys="false"/>Note that the assigntovar parameter has the macro variable name with the $ symbol surrounding the macro variable name. Also notice that the varupdateonly parameter in the prompt action was set to true, so that we will not accidentally change the host screen.
We are finished, and now can get our global variable value to our macro variable!
Next time I will cover how to copy data in the other direction, from a macro variable to a global variable.[Read More]