Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

New TIBCO Community Coming Soon
In early summer, TIBCO plans to launch a new community—with a new user experience, enhanced search, and expanded capabilities for member engagement with answers and discussions! In advance of that, the current myibi community will be retired on April 30. We will continue to provide updates here on both the retirement of myibi and the new community launch.

What You Need to Know about Our New Community
We value the wealth of knowledge and engagement shared by community members and hope the new community will continue cultivating networking, knowledge sharing, and discussion.

During the transition period, from April 20th until the new community is launched this summer, myibi users should access the TIBCO WebFOCUS page to engage.


Focal Point    Focal Point Forums  Hop To Forum Categories  iWay Software Product Forum on Focal Point    [CLOSED] iSM - How to get the agent type during a process flow runtime execution

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED] iSM - How to get the agent type during a process flow runtime execution
 Login/Join
 
Tsepe
Member
posted
Hi All,

Is there a ifl, agent or specialregister I can use to get the agent type for the last executed agent in a process flow? I need something similar to the iway.lastnode and iway.priornode special registers for the agent name

I want to use a catch agent( com.ibi.agents.XDCatchAgent) in all my process flows to trap any error edges encountered during a process execution in order to route the error payload to a generic error handling process flow. I want to make the process of trapping errors in my main process flows to be as lightweight and generic as possible.

The only thing I am missing is the agent type (It would also be nice if all agents generated the same error doc/payload but thats a conversation for another day)

iSM8.0.2

This message has been edited. Last edited by: FP Mod Chuck,


iWay Datamigrator 76,
iWay Service Manager 5.5, Windows server 2000,
 
Posts: 6 | Registered: April 15, 2009Report This Post
vinodh
Gold member
posted Hide Post
did you resolved it.

if not, then you can use a proper naming convention to the object would solve the problem.

i always suffix a agent/object name with that particular type. so that i can use the iway.lastnode and strip out the suffix whenever i need.

do you think it will help you.
post me if you got a better one.


WebFOCUS 8
Windows, All Outputs
 
Posts: 71 | Registered: January 23, 2018Report This Post
Tsepe
Member
posted Hide Post
Hi

I did not find a solution for this. I thought about the naming convention solution but it is difficult to implement in a team environment where you are not able to do in-depth code reviews


I appreciate the feedback though


iWay Datamigrator 76,
iWay Service Manager 5.5, Windows server 2000,
 
Posts: 6 | Registered: April 15, 2009Report This Post
vinodh
Gold member
posted Hide Post
if you want to achieve a certain step, then you have to advice the team with the benefits and go ahead with the solution. we have done in similar environments and it worked great.


quote:
Originally posted by vinodh:
did you resolved it.

if not, then you can use a proper naming convention to the object would solve the problem.

i always suffix a agent/object name with that particular type. so that i can use the iway.lastnode and strip out the suffix whenever i need.

do you think it will help you.
post me if you got a better one.


WebFOCUS 8
Windows, All Outputs
 
Posts: 71 | Registered: January 23, 2018Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  iWay Software Product Forum on Focal Point    [CLOSED] iSM - How to get the agent type during a process flow runtime execution

Copyright © 1996-2020 Information Builders