Comments on Impossible Siebel: ABS Framework - Logging & Tracing Module

Hi Anon, you'll need to get in Contact with yo...

2011-01-07T19:25:54.753+11:00

Hi Anon, you'll need to get in Contact with your ABS vendor for this functionality. This feature is not available in all versions of ABS - Jason

Hey this is is a nice poet..I feel very happy to f...

2010-12-23T18:05:44.166+11:00

Hey this is is a nice poet..I feel very happy to find such kind of informative posts

Jason - We've similar requirements as "fk...

2010-12-20T11:42:35.230+11:00

Jason - We've similar requirements as "fkirill" pointed out in this first comment
1) Queues of entities.....

and you said "For question #1, there is an extra in ABS framework called "ABS Business Previledge Service" which should meet your requirements."

can you elaborate on "ABS Business Previledge Service"? point me to the link where I can find documents

Thanks

Hi Biku, You need to be on a project that already ...

2010-06-23T08:53:24.841+10:00

Hi Biku, You need to be on a project that already has ABS =), it currently cannot be openly sourced.

Hi Jason, Very Nice and Interesting post. But wher...

2010-06-23T05:08:58.621+10:00

Hi Jason,
Very Nice and Interesting post. But where do I find this ABS logging module?

Thanks,
Biku

Hi fkirill You have very good questions. For que...

2009-11-30T19:09:17.412+11:00

Hi fkirill

You have very good questions.

For question #1, there is an extra in ABS framework called "ABS Business Previledge Service" which should meet your requirements.

Functionality in points 2,3,4,5 are not implemented in ABS.

ABS provides other value-added features to EIM and EAI, but i dont have information on the comming features, and there isn't any available commercial model at the moment (that i know of).

If you are really interested, I can direct you to a proper contact.

You can reach me at
jason@impossiblesiebel.com

Hello, very good article. Obviously you have lots ...

2009-11-22T09:32:10.181+11:00

Hello, very good article. Obviously you have lots of experience from real-life projects and a good architectural approach.

I would like to propose some other areas to be implemented as a some sort of a script library (and native code too, CLib.invoke is a good thing after all if used with care).

Well, it looks like quite a lot of things which have very wide and common application areas are completely missing from Siebel, which is sad (in spite of the fact that a lot of things Siebel supports out of the box).

I would thing of supporing the following pieces of functionality as they are reappearing over and over again from project to project:
1) Queues of entities. I mean queue of service requests, activities etc. which are handled by a pool of users. Well, some might say about Task UI and Universal Inbox, but those of you who had a pleasure to work with above-mentioned functionality might notice lack of architectural idea behind all this. Normally you have a pool of tasks to be perfomed by a pool of users with a complex logic of approval, parallel execution etc. All of these execution blocks should be accompanied by internal queues of tasks which accumulate incoming events based on FIFO or any other principle or sort order.
2) Exclusive access to some data (analog of semaphores or critical blocks in Windows). In Siebel there is no standard notion of shared global between all the sessions other then database record (S_SSA_ID would be a good example if this approach used within Siebel itself though with some pecularities) and gateway data (which has no public API). In a lot of cases we need to obtain some sort of a global counter or some other shared global data to be accessed by more then one session. Moreover we need to introduce some kind of access policy to avoid concurrent read or write access depending on the task. Well, there are workarounds of course, starting from database's sequence fields and triggers (which in turn employ SELECT FOR UPDATE for example). But this is quite complex for such a simple task and may be greatly improved.
3) Backgound UI processing. Well, imagine you have external billing or scoring system, accepting Web-Services as a means of communication, or you have your own Business Service that performs complicated computations to be presented to a user. You need to pass the parameters and show the result in an applet. The problem is that you have SLA to show the screen to a user within at most 3 secs, but billing can only provide response within 10 secs. There should be a mechanism to allow lazy population of data based on the availability of those data. In other words, there should be a mechanism of background calculation of data and a mechanism to push the data to the client.
4) Server-to-client event propagation. This is some generalization of a second part from my previous point. Now there is no theoretical possibility to push event from server to client until client asks server for something (refresh broadcast, leave a record etc.) The only way to push some event to a client is to use non-documented features of Communication Toolbar, but not all projects use it. The simpler analog can and should be introduced (and also without java).
5) Ability to invoke arbitrary SQL(Visual Basic and CreateObject/ADO don't work on UNIX). Well, I believe this need no further comments. This is not a good practice, this is potentially dangerous, but sometimes you just need to invoke very specific SELECT statement. On Windows this is normally done through VB/CreateObject/ADO and VBC on top, but on UNIX these is no such a possibility. The main problem is not invoking statement itself, but in returning results back to script/VBC/UI.

Do you have formal scope or at least a list of ideas to be implemented in ABS?
What's the commercial model you plan to use for ABS?

Thanks Neel, I tried to give it a broad appeal, b...

2009-11-17T23:29:28.362+11:00

Thanks Neel,

I tried to give it a broad appeal, because not everyone has ABS code for reference. I'm glad you got some value out of it.

Are you using ST or non ST engine, can you provide some examples. Send to my email, if you like.

This is really nice info and introduction to ABS F...

2009-11-17T04:38:11.488+11:00

This is really nice info and introduction to ABS Framework logging module.

overriding the exception object and throwing a custom object is really nice but what I had observed is that in case I throw a normal exception object then I don't need to do a RaiseErrorText to show the error message on UI but if I throw a custom object then it goes along the chain as expected but never reaches UI and error message is suppressed.

Any thoughts on this behavior???