Domino Connector

Alon Raskin araskin at 3i-consulting.com
Sat Aug 10 04:13:15 EDT 2002


Hi Guys,
 
Just a quick question. Is the Lotus Notes Connector free (like SAP Exchange
Connector) or does it have to be purchased. If so does anyone know how much
it is?
 
Regards,
 
Alon Raskin
3i Consulting Group
e: araskin at 3i-consulting.com
w: http://www.3i-consulting.com
 
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Pokraka, Michael
Sent: Thursday, August 08, 2002 12:28 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow Performance
 
Hi Alon,
You are quite correct, wf's don't really 'wait' for events. They just put
themselves into a table and the event handler looks in there for any
workflows to be executed.
 
For performance, you can go two routes: one is to use a dedicated app server
and the other is to use the event queue. Both have advantages and drawbacks,
depending on your scenario.
You need to evaluate which process(es) is/are most likely  to cause
performance bottlenecks and take that into account.
E.g. in our scenario, batch processing was a major factor. Lots of documents
created in a batch process will trigger 2 workflows each all at once - all
on the same app server as the original doc being created. Result: all dialog
processes are used up and anyone else connected to that particular server
comes to a grinding halt until everything has run.
Since this was a 'peak time load', it was not really worthwhile to dedicate
an app server which will only be busy for short times during the day.
The event queue has two advantages: it lets you throttle the amounts of
events being raised to n/minute, and you can use load balancing to
distribute them across servers (4.6c here). In our case we've shifted the
bottleneck from Workflow back to the process that creates the 'triggering'
document (e.g. batch delivery creation). Drawback - the wf's defined to use
the queue can take a little time to start (depending on your queue config).
 
HTH
Cheers
Mike
 
 
 
 
-----Original Message-----
From: Alon Raskin [mailto:araskin at 3i-consulting.com]
Sent: 07 August 2002 22:55
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Workflow Performance
 
 
My current client is quite concerned about Workflow and its impact on system
Performance. I would like to hear others who have had 'large' clients weigh
in on this.
 
I have tried to explain to my client that if we are kicking off many events
per hour then that can have an impact on the system performance. I explained
that this can be offset by using the Event Queue (I am not sure that that is
its proper name).
 
They are also concerned about having many workflows 'sitting around' and
listening for events to be raised. I told them that this is not really a
problem as the Workflow is not actually polling. In fact when the even
occurs it triggers the workflow.
 
I would love to hear from other people who have had experience with large
workflow implementations.
 
Just for your information, our site has just gone through a sizing exercise
and it seems that they will be needing 49 app servers. So we are talking
about some serious sized implementation.
 
I look forward to your thoughts about any workflow-performance experience
that you would like to share.
 
Regards,
 
Alon Raskin
3i Consulting Group
e: araskin at 3i-consulting.com
w: http://www.3i-consulting.com
 
----------------------------------------------------------------------------
--
This e-mail is intended for the use of the addressee(s) only and may contain
privileged, confidential, or proprietary information that is exempt from
disclosure under law.  If you have received this message in error, please
inform us promptly by reply e-mail, then delete the e-mail and destroy any
printed copy.   Thank you.
 
 ===========================================================================
==
 


More information about the SAP-WUG mailing list