I am using BP 6.2.1 and am wanting to implement web services and have a few questions/seeking advice. Here is a simple description of my environment:
We currently have a single runtime license and it is currently only used less than an hour a day. Once I implement my new solution I've been working on, the time usage will increase a lot - it might be running 24x7 for a few weeks each month. So, the workload will vary but we do want to maximize the value of our license so we are not "over buying". In other words, I will have a hard time justifying an additional runtime license.
My current solution uses the BP scheduler and runs at the same time ever day. My BP process consumes a few RESTful API's to collect dates and other information. It grabs the API info, writes to a BP work queue, then another BP process runs after the polling is complete. This works fine for my original solutions.
My new solution I'm working on is much more dynamic and a scheduled task is not well-suited. The problem is that I'm waiting on another department to do certain things and basically give the OK for Blue Prism to run and do its thing (which can take an hour or more each time this happens). My company has a workflow manager - this will be our source of information. The workflow tool has an API - I will be using it.
What I'm proposing to do is have a SOAP service send information to Blue Prism (background object) and write the information to a BP work queue. I'm working on this right now and expect to have a test ready soon. Ideally, I can also have a web service tell a BP process to wake up - it has work to do.
My questions (sorry for the long back story!):
1. If my object is a background process, can a single runtime license accept SOAP info/update a work queue while a process might be running in the foreground (likely running for a long time).
2. Does my approach seem reasonable? The data I'm expecting will never be ready at the same time - it will trickle in. There is a lot of work, so I don't want to wait until all data is available and kick off a scheduled task (like my original solution I created - it's a small amount of data and only takes a half hour to complete - the new solution is lots of work that takes a long time to run).
3. I also want my original task to run at least once a day. Let's say I have it run from 12:00am until 1:00am. That gives me other process the ability to run 23 hours a day.
Thanks in advance for any thoughts/advice. I'm worried I'm going to run into license problems and it's not easy to obtain an additional license.
We currently have a single runtime license and it is currently only used less than an hour a day. Once I implement my new solution I've been working on, the time usage will increase a lot - it might be running 24x7 for a few weeks each month. So, the workload will vary but we do want to maximize the value of our license so we are not "over buying". In other words, I will have a hard time justifying an additional runtime license.
My current solution uses the BP scheduler and runs at the same time ever day. My BP process consumes a few RESTful API's to collect dates and other information. It grabs the API info, writes to a BP work queue, then another BP process runs after the polling is complete. This works fine for my original solutions.
My new solution I'm working on is much more dynamic and a scheduled task is not well-suited. The problem is that I'm waiting on another department to do certain things and basically give the OK for Blue Prism to run and do its thing (which can take an hour or more each time this happens). My company has a workflow manager - this will be our source of information. The workflow tool has an API - I will be using it.
What I'm proposing to do is have a SOAP service send information to Blue Prism (background object) and write the information to a BP work queue. I'm working on this right now and expect to have a test ready soon. Ideally, I can also have a web service tell a BP process to wake up - it has work to do.
My questions (sorry for the long back story!):
1. If my object is a background process, can a single runtime license accept SOAP info/update a work queue while a process might be running in the foreground (likely running for a long time).
2. Does my approach seem reasonable? The data I'm expecting will never be ready at the same time - it will trickle in. There is a lot of work, so I don't want to wait until all data is available and kick off a scheduled task (like my original solution I created - it's a small amount of data and only takes a half hour to complete - the new solution is lots of work that takes a long time to run).
3. I also want my original task to run at least once a day. Let's say I have it run from 12:00am until 1:00am. That gives me other process the ability to run 23 hours a day.
Thanks in advance for any thoughts/advice. I'm worried I'm going to run into license problems and it's not easy to obtain an additional license.