| Author |
Message
|
| ReneBaggio |
 Posted: Thu Jun 09, 2016 12:34 pm Post subject: IB 10.0.0.5 REST API (Broker Schema) |
 |
|
Newbie
Joined: 11 Nov 2015
Posts: 4
|
| I have a problem, in the next post i will describe it (the forum does not let me post the text). |
|
| Back to top |
|
 |
| ReneBaggio |
| Posted: Thu Jun 09, 2016 12:36 pm Post subject: |
|
|
Newbie
Joined: 11 Nov 2015
Posts: 4
|
I have downloaded the new integration bus v 10, i have created a rest api using the swagger editor but i have one question.
Is it possible change the broker schema name (the rest api autogenerates the "gen" broker schema) ?
I have changed the name using the restapi.descriptor (I move the main flow to the new broker schema) but when i build the proyect, it automaticaly creates the autogenerated flow (gen.FlowName).
Thanks and Greetings! |
|
| Back to top |
|
|
| stoney |
| Posted: Thu Jun 09, 2016 11:14 pm Post subject: |
|
|
Centurion
Joined: 03 Apr 2013
Posts: 140
|
Why do you want to do this?
The message flow in that schema is automatically generated and managed by the toolkit.
It is not intended for users to modify it, hence the yellow warning note when you open it in the message flow editor. |
|
| Back to top |
|
|
| ReneBaggio |
| Posted: Fri Jun 10, 2016 1:55 pm Post subject: |
|
|
Newbie
Joined: 11 Nov 2015
Posts: 4
|
Only for accomplish the development guidelines from mi org.
But if is not recommended.. Would you know if in the ibm info center can i find something about that?
Greetings |
|
| Back to top |
|
|
| stoney |
| Posted: Sun Jun 12, 2016 7:15 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2013
Posts: 140
|
We don't describe that message flow in the documentation unfortunately.
I think we were trying to pretend that it doesn't exist!
However, now I understand why you are looking to move it, I'll get the documentation updated.
Until then:
1) Do try to ignore the top level generated message flow; it belongs to the container, and is automatically managed by the container.
2) Do not attempt to move the generated message flow. Neither the toolkit or runtime have been developed or tested with this in mind.
3) Do not attempt to modify or add extra functionality to the generated message flow; it will get regenerated at some point, and you will lose your modifications.
The runtime is also intentionally picky about the contents of this message flow and it will reject additional nodes upon deployment.
4) You may need to modify the message flow in certain cases - for example to enable monitoring events or security profiles - use monitoring profiles or BAR file overrides for this.
In an ideal world, the generated message flow would not exist, and the container would magically take of everything.
Unfortunately, due to valid requirements like 4), having an actual message flow is a "necessary evil". |
|
| Back to top |
|
|
| ReneBaggio |
| Posted: Wed Jul 13, 2016 2:22 pm Post subject: |
|
|
Newbie
Joined: 11 Nov 2015
Posts: 4
|
|
| Back to top |
|
|
| timber |
| Posted: Thu Jul 14, 2016 1:07 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
I have a related question...
The IIB toolkit generates the top-level flow for the REST API in the 'gen' schema. If I open the REST API Description and click on 'Open the subflow for the operation', the IIB toolkit generates an implementation subflow. That subflow is also in the 'gen' schema. In an ideal world, I would be able to specify a broker schema for the implementation subflows because they are not really 'generated' flows; only the input and output nodes are generated.
Is there any way to achieve this? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jul 14, 2016 3:49 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Presumably easy enough to move afterwards.
Maybe stoney has a magic button.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| timber |
| Posted: Thu Jul 14, 2016 4:15 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| If I move it into a different broker schema then I will need to edit the (generated) top-level message flow - otherwise the link will be broken. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jul 14, 2016 4:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| timber wrote: |
| If I move it into a different broker schema then I will need to edit the (generated) top-level message flow - otherwise the link will be broken. |
Maybe? It might notice that for you...
Obviously I've not tried it.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| timber |
| Posted: Thu Jul 14, 2016 4:44 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| I think it probably *would* fix the link in the top-level automatically. But I would be surprised if that change was preserved when the top-level flow was re-generated ( as the comment in the flow says it will be ). |
|
| Back to top |
|
|
| stoney |
| Posted: Thu Jul 14, 2016 4:45 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2013
Posts: 140
|
There is also a link between the operation definition in the Swagger document and the subflow implementing that operation.
That link is stored in the hidden and undocumented restapi.descriptor file. I do not recommend that you modify that file 
You can edit the main flow to point at the new location of the subflow once you've moved it, however if you don't fix the link in that file then your modifications to the main flow will be undone the next time you do something that causes the main flow gets regenerated.
As usual, the best thing to do would be to raise an RFE, maybe asking for tooling options to move subflows around or select an existing subflow? |
|
| Back to top |
|
|
| timber |
| Posted: Fri Jul 15, 2016 11:23 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
|
| Back to top |
|
|
|
|
