| Author |
Message
|
| Ramphart |
 Posted: Wed Jun 20, 2018 3:26 am Post subject: Deploy particular flows within an Application Only - iiB v10 |
 |
|
Disciple
Joined: 21 Jul 2004
Posts: 150
Location: South Africa, JHB
|
Running on: iiB Version 10.0.0.11, Windows Server 2012 R2
Please advise if there is a way to select specific message flows within an Application when building a bar file for deployment (whether the message flows is under the same broker schema or a different broker schema).
My Scenario:
| Code: |
Application_A
--schema_1
----MessageFlow_1.msgflow
--schema_2
----MessageFlow_2.msgflow
|
From the example above I'd like to be able to select and deploy say MessageFlow_2.msgflow only. When building the bar file the only option available is to select the whole Application_A which includes all the flows under Application_A.
Your assistance is appreciated.
_________________
Applications Architect |
|
| Back to top |
|
 |
| martinb |
| Posted: Wed Jun 20, 2018 3:35 am Post subject: |
|
|
Master
Joined: 09 Nov 2006
Posts: 210
Location: UK
|
| That's by design, Applications are a container for all the resources that are required to create a solution. |
|
| Back to top |
|
|
| Ramphart |
| Posted: Wed Jun 20, 2018 3:41 am Post subject: |
|
|
Disciple
Joined: 21 Jul 2004
Posts: 150
Location: South Africa, JHB
|
| martinb wrote: |
| That's by design, Applications are a container for all the resources that are required to create a solution. |
Pity they've changed it to work this way. Use to be better in the older version like Message Broker 7 where you had the flexibility to choose exactly what you want to deploy.
Thx for the feedback though.
_________________
Applications Architect |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 20, 2018 5:38 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Flows are still supported as independent resources and can be deployed that way.
I think you'll find the benefits of using an application outweighs the problems.
Look at it this way - why would you not want to deploy an entire application? If you have flows that that shouldn't be deployed at the same time as other flows, why are they in the same application?
Or more extreme, what advantages are you getting from applications? If you're not, use independent resources.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| timber |
| Posted: Wed Jun 20, 2018 8:10 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
The usual reason for wanting to reduce the scope of deployment is a lack of trust in the build and release process.
But if you have a scripted build and deploy pipeline then you don't need to worry about accidentally deploying changed code. The pipeline deploys exactly what's in the release branch. The version control system can tell you exactly how it differs from what you deployed last time. |
|
| Back to top |
|
|
| Ramphart |
| Posted: Wed Jun 20, 2018 10:50 am Post subject: |
|
|
Disciple
Joined: 21 Jul 2004
Posts: 150
Location: South Africa, JHB
|
| Vitor wrote: |
Flows are still supported as independent resources and can be deployed that way.
I think you'll find the benefits of using an application outweighs the problems.
Look at it this way - why would you not want to deploy an entire application? If you have flows that that shouldn't be deployed at the same time as other flows, why are they in the same application?
Or more extreme, what advantages are you getting from applications? If you're not, use independent resources. |
Independent projects would be the way to go to achieve this yes.
In my opinion a better design would have been to allow one to select on schema level within an Application when adding to the bar files. All flows within the schema could then relate to one process and all the schemas combined could relate to an overall project. For instance in a B2B project you could have an Application called B2B with schemas for say Invoicing, Orders, Remittances, CreditNotes, etc. With the current design "restrictions" you'll need an Application for Invoicing, Application for Orders, Application for Remitances, etc.
In this way you'll get the benefits associated with an Application combined with a better logical way to group related processes within a business and the flexibility to select only the processes (schema with all its flows) from the Application which is ready to be deployed.
_________________
Applications Architect |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jun 20, 2018 7:12 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And this would be potentially a very bad thing.
Think about all the functions that your B2B application does, and know that you will most probably encounter the need to scale those function independently.
Having each of these function in its own application will allow you to scale differently depending on the function performed. I am not here talking about vertical scaling (number of instances for a flow) but more about horizontal scaling (number of integration nodes it is deployed to).
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Ramphart |
| Posted: Wed Jun 20, 2018 10:40 pm Post subject: |
|
|
Disciple
Joined: 21 Jul 2004
Posts: 150
Location: South Africa, JHB
|
| fjb_saper wrote: |
And this would be potentially a very bad thing.
Think about all the functions that your B2B application does, and know that you will most probably encounter the need to scale those function independently.
Having each of these function in its own application will allow you to scale differently depending on the function performed. I am not here talking about vertical scaling (number of instances for a flow) but more about horizontal scaling (number of integration nodes it is deployed to).
Have fun |
The scaling issue would come down to the same thing if you have one B2B Application and put all the different depending functions under that application. An independent project allows this design (potential danger) anyway. It's still a pity that one cannot select the functions that is ready to be deployed from within an Application.
Thank you all for the feedback. It's been helpful. Appreciated
_________________
Applications Architect |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jun 20, 2018 11:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I stand with my worthy associates on this. You clearly have to do what's best in your circumstances by your own lights but i do fear you're making a rod for your own back.
Good fortune to you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
