You are viewing limited content. For full access, please sign in.

Question

Question

Two workflows for one repository in RIO

Workflow
Updated December 22, 2016
asked on July 8, 2015

 

Maybe this is a dumb question but I actually never try it.

In Avante you can have one WF to work with 1 repository

In RIO you can have multiple Server with his WF each one.

But can you have in RIO 1 repository and two Workflows for the same repository?

This is because I got a client with too many workflow that process 1 million transactions and it’s not enough. And now they need to add new tasks and they are never going to run because they enter in query and I can’t wait a year until the first process end.

0 0

Replies

replied on July 8, 2015

Yes, you can have multiple Workflow servers on the same repository in both Avante and Rio.

0 0
View 2 previous replies
replied on December 19, 2016

Miruna,

I was exploring this option as well, where we are planning to run 3 WF servers against same repository. Each WF Server will be woking in its own individual folder (each folder has hundreds of thousands of documents).

My concern is, is this going to hammer the LF/DB servers (for repository)? As this is a Live repository, so I am not sure that how much would it effect the daily user of the repository by the users.

Can you please advise the best practices for the above scenario?

0 0
replied on December 19, 2016

That's sort of too vague to answer. It depends on the load you expect on the 3 Workflow Server. But yes, there will be more activity in the repository as well as SQL.

0 0
replied on December 22, 2016

Miruna, 

Let me explain please.

So we have a Live repository which has around 5 million documents. We need to run two workflow servers, which will be:

1. Get InvoiceNumber and InvoiceDate from a sql table (this table has around 13k Invoice Numbers)

2. In a loop - Get list of tocIds of all the documents with the current Invoice Number (from LF DB)

3. Use get Entry by using the tocid and get the document

4. On the basis of the InvoiceDate, Tag that document (pre April 2015 or Post April 2015)

 

As the repository is in use 24/7, so we can't compromise on the repository performance.

Do you think two WF server hitting this repository would make any issue for us?

0 0
replied on December 22, 2016

So the 5 million documents all belong to the 13,000 invoices? It's still not clear to me why you need 2 Workflow servers. Is it because you're worrying about how long a single one would take process this many documents?

Loops over with that many iterations tend to be inefficient. I have a couple of questions before I can suggest a better design:

  • Do you know how your data breaks down in the repository and the external table?
    • For example, are the 5 million invoices pretty evenly distributed across the 13,000 invoices?
    • How do the invoice dates break down by month and year? Are most of them pre or post April 2015?

 

 

 

0 0
replied on December 22, 2016

Hi Miruna,

No, all 5 million documents don't belong to 13k invoices. That's why I am getting the list of tocids as per the Invoice Number value.

Yes we have only 1 month to run the workflow, that's why we are planning to have multiple WF servers. We will divide the list of Invoice Numbers in two different tables and these will be the source for two WFs at both servers.

I ran the current workflow and have processed 2500 documents in 15 minutes, which is a good news.

 

To answer you questions:

1. We could have any number of documents for an invoice. E.g., this could be 1 to 50 documents for each invoice number.

2. Most of the invoices will be pre April 2015.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...