Re: Replacement for Event Handler?

This is true, Danny. EHs have been deprecated for a couple of
versions and are going the way of the dodo in the next release.
The recommended approach for making TDI Adapters is to use the
RMI-method, creating one AL per service operation (add, search,
etc.) and then loading these into the TIM LDAP.

You will  also want to look at the ADT (Adapter Development Toolkit)
available on Tivoli OPAL:

http://catalog.lotus.com/wps/portal/topal/details?catalog.label=1TW10IM0H

ADT gives you a visual environment that speaks "TIM terminology"
while building the underlying TDI Config assets you need, plus
a number of other TIM support files. It even gives you test ALs
for verifying your Adapter logic.

Perhaps someone with TIM experience could chime in here as well :)

-Eddie
http://www.tdi-users.org


Danny Lee wrote:
> Hello ITDI gurus,
> 
>     I've been hearing a bit of news that one shouldn't be using the 
> event handler in ITDI as it won't be available in future ITDI releases.
> 
>     I've primarily be using it in our custom ITIM adapters, (ie. 
> listening to ITIM DSMLv2 provisioning requests and then using it to kick 
> off Add account, Delete Account, Modify Account or Search assembly lines).
> 
>     Can anyone advise if it is indeed true that event handler won't be 
> supported in the near future?  And if so, what should one use in a 
> custom ITIM adapter instead of the good old DSMLv2 event handler?
> 
> Thanks in advance,

Hello ITDI gurus,

	I've been hearing a bit of news that one shouldn't be using the event 
handler in ITDI as it won't be available in future ITDI releases.

	I've primarily be using it in our custom ITIM adapters, (ie. listening 
to ITIM DSMLv2 provisioning requests and then using it to kick off Add 
account, Delete Account, Modify Account or Search assembly lines).

	Can anyone advise if it is indeed true that event handler won't be 
supported in the near future?  And if so, what should one use in a 
custom ITIM adapter instead of the good old DSMLv2 event handler?

Thanks in advance,

Thanks for the advice, Eddie.

Danny

Eddie Hartman wrote:
> This is true, Danny. EHs have been deprecated for a couple of
> versions and are going the way of the dodo in the next release.
> The recommended approach for making TDI Adapters is to use the
> RMI-method, creating one AL per service operation (add, search,
> etc.) and then loading these into the TIM LDAP.
> 
> You will  also want to look at the ADT (Adapter Development Toolkit)
> available on Tivoli OPAL:
> 
> http://catalog.lotus.com/wps/portal/topal/details?catalog.label=1TW10IM0H
> 
> ADT gives you a visual environment that speaks "TIM terminology"
> while building the underlying TDI Config assets you need, plus
> a number of other TIM support files. It even gives you test ALs
> for verifying your Adapter logic.
> 
> Perhaps someone with TIM experience could chime in here as well :)
> 
> -Eddie
> http://www.tdi-users.org
> 
> 
> Danny Lee wrote:
>> Hello ITDI gurus,
>>
>>     I've been hearing a bit of news that one shouldn't be using the 
>> event handler in ITDI as it won't be available in future ITDI
releases.
>>
>>     I've primarily be using it in our custom ITIM adapters, (ie. 
>> listening to ITIM DSMLv2 provisioning requests and then using it to 
>> kick off Add account, Delete Account, Modify Account or Search 
>> assembly lines).
>>
>>     Can anyone advise if it is indeed true that event handler won't be

>> supported in the near future?  And if so, what should one use in a 
>> custom ITIM adapter instead of the good old DSMLv2 event handler?
>>
>> Thanks in advance,