Skip to main content

This is fairly basic question about K2 architecture.

 

In production we have a K2 server which runs the Blackpearl window service and also the K2 web sites.  We have a seperate server that runs our main application web site.  The main web server uses the K2 API calling methods on local DLLs on the server.  What I don't understand is how the K2 DLL communicate with the K2 Server.  Is there a custom RPC mechanism between the K2 Host Server process and the DLLs ??

 

We are having performance problems with K2 where it can take 10 seconds to create a process instance and on other occcasions the main web server gets no response from K2 at all.  Trying to understand what talks to what and how is our current plan to trying and fix this.

it depends on how your custom website is talking to k2. There are many ways. old style web services, REST, API connectionstring etc. You can enable full loggin on the K2 server and monitor the calls being made by your custom website.

 

Regarding your performance issues, does it always take 10sec to create the instance in successive attempts? If it is a large workflow and you rarely start instances, it is normal to take 10sec.


Reply