Question
Avanade
US
Last activity: 23 Aug 2018 19:06 EDT
Deploying Multiple Projects To One Runtime Instance
How do you deploy multiple projects to the Runtime? Can you put them all under one solution and somehow deploy that solution? We have multiple projects, each of which handle a different use case, and want to combine them into one deployment so that a machine can run any of those projects.
Pegasystems Inc.
US
To combine them;
- Create your "main" solution and project.
- Right-click on the solution in the Solution Explorer window and select "Add existing project".
- Add your other projects into one solution.
- Add references to each of these projects to the "main" one.
- Right-click on the "main" project and select "Manage imported projects".
- Pull over all of the projects you are including.
- You can now call automations from the "child" projects in the "main" project.
Of course you'd still need to rectify any coordination logic between the projects.
Avanade
US
"Of course you'd still need to rectify any coordination logic between the projects."
I currently have my other projects (child projects) being kicked off via a case creation. If one of the child projects is loaded in runtime, and a case for that project is created, it automatically kicks off. Now that i have multiple project children under the parent, will it automatically start one of the child automations if a case is created, or do i need to have automation logic in the main project that says "if Case A is created, start project A; if Case B is created, start project B" etc.?
Pegasystems Inc.
US
I assume that you are using Robot Manager. In that case I would always place the logic for responding to the robot activity in the controller project and have it call automations in your specific child projects. In order for one bot to handle work from multiple workbaskets, those workbaskets must all be in the same workgroup. Robot Manager will assign any workbasket work in the workgroup to any bot in the workgroup, so it must be able to handle all of the workbaskets. Therefore, it doesn't make any sense to separate the handling of the work into separate projects.
Have your child projects limited to automations against specific applications that you can test independent of robot manager (i.e. you can supply all of the required inputs and receive all of the required outputs).