|
58 | 58 | } |
59 | 59 | ], |
60 | 60 | "outcomesName": "Learning outcomes", |
61 | | - "_outcomesComment": "Use IBM Integration Bus to create and invoke a message flow which transforms data using a Map.", |
| 61 | + "_outcomesComment": "Use IBM Integration Bus to create and drive a message flow which transforms data using a Map.", |
62 | 62 | "outcomeList": |
63 | 63 | [ |
64 | 64 | { |
65 | | - "title": "Use IBM Integration Bus to create and invoke a message flow which transforms data using a Map." |
| 65 | + "title": "Use IBM Integration Bus to create and drive a message flow which transforms data using a Map." |
66 | 66 | } |
67 | 67 | ], |
68 | 68 | "summary": |
|
75 | 75 | "section": "This tutorial demonstrates a simple message flow which receives XML data over HTTP. The flow transforms the input XML structure into a different output XML structure using a Mapping node, and sends this back to the HTTP request." |
76 | 76 | }, |
77 | 77 | { |
78 | | - "section": "In IBM Integration Bus, message flows can be used to transform input data structures into output data structures. Several transformation options are provided including a including a Compute node (which uses ESQL), a Mapping node, a JavaCompute node (which can navigate data using an IBM Integration Bus Java API or JAXB), an XSL Transform node and a .NETCompute node." |
| 78 | + "section": "In IBM Integration Bus, message flows can be used to transform input data structures into output data structures. Several transformation options are provided including a Compute node (which uses ESQL), a Mapping node, a JavaCompute node (which can navigate data using an IBM Integration Bus Java API or JAXB), an XSL Transform node and a .NETCompute node." |
79 | 79 | } |
80 | 80 | ] |
81 | 81 | }, |
|
101 | 101 | "overview": |
102 | 102 | { |
103 | 103 | "name": "Create", |
104 | | - "heading": "Import projects", |
| 104 | + "heading": "Import project", |
105 | 105 | "_createComment": "A description of what will happen when the user clicks Import.", |
106 | 106 | "sections": |
107 | 107 | [ |
108 | 108 | { |
109 | | - "section": "The Transformation_Map application includes one project that is imported into your workspace." |
| 109 | + "section": "Click <span class='uicontrol'>Import</span> and the <span class='uicontrol'>Transformation_Map</span> application will be imported into your workspace." |
| 110 | + }, |
| 111 | + { |
| 112 | + "section": "The <span class='uicontrol'>Transformation_Map</span> message flow will be opened for you." |
110 | 113 | } |
111 | 114 | ] |
112 | 115 | }, |
|
117 | 120 | [ |
118 | 121 | { |
119 | 122 | "title": "Knowledge Center link to ", |
120 | | - "description": "Developing integration solutions by using applications", |
| 123 | + "description": "Developing integration solutions from scratch", |
121 | 124 | "link": "com.ibm.etools.mft.doc/bi12002_.htm" |
122 | 125 | } |
123 | 126 | ] |
|
144 | 147 | "sections": |
145 | 148 | [ |
146 | 149 | { |
147 | | - "section": "The Transformation_Map application is shown in the Application Development view of your workspace." |
| 150 | + "section": "The <span class='uicontrol'>Transformation_Map</span> application is now shown in the Application Development view of your workspace." |
148 | 151 | }, |
149 | 152 | { |
150 | | - "section": "" |
| 153 | + "section": "No other preparation steps are required for this tutorial." |
151 | 154 | }, |
152 | 155 | { |
153 | | - "section": "The application will be deployed to your default integration server. The message flow is then started and ready to be invoked." |
| 156 | + "section": "Next you will use the Flow exerciser to send HTTP requests to the message flow." |
154 | 157 | } |
155 | 158 | ] |
156 | 159 | }, |
|
161 | 164 | [ |
162 | 165 | { |
163 | 166 | "title": "Knowledge Center link to ", |
164 | | - "description": "Developing integration solutions by using integration services", |
165 | | - "link": "com.ibm.etools.mft.doc/bi12002_.htm" |
| 167 | + "description": "Using Message Maps", |
| 168 | + "link": "com.ibm.etools.mft.doc/br28800_.htm" |
166 | 169 | } |
167 | 170 | ] |
168 | 171 | }, |
|
188 | 191 | "sections": |
189 | 192 | [ |
190 | 193 | { |
191 | | - "section": "The Transformation_Java application is shown in the Application Development view of your workspace.", |
| 194 | + "section": "The <span class='uicontrol'>Transformation_Map</span> message flow should be open already:", |
192 | 195 | "steps": |
193 | 196 | { |
194 | 197 | "type": "ordered", |
195 | 198 | "details": |
196 | 199 | [ |
197 | 200 | { |
198 | | - "details": "Open the Transformation_Map message flow, and click the Flow Exerciser icon <img src='http://ot4i.github.io/ot4i.tutorials//dist/images/icons/iib/startFlowExerciser.png' alt='' /> to start recording the message path through the flow." |
| 201 | + "details": "Click the Flow Exerciser icon <img src='http://ot4i.github.io/ot4i.tutorials//dist/images/icons/iib/startFlowExerciser.png' alt='' /> to start recording the message path through the flow." |
199 | 202 | }, |
200 | 203 | { |
201 | 204 | "details": "Click the Send Message icon <img src='http://ot4i.github.io/ot4i.tutorials/dist/images/icons/iib/sendMessage.png' alt='' /> to select a message to send to the flow." |
202 | 205 | }, |
203 | 206 | { |
204 | | - "details": "Choose Message1, edit the message data if you like, and click Send. Your request message is sent to the HTTP input node." |
| 207 | + "details": "Choose Message1, edit the message data if you like, and click Send. Your request message is sent to the HTTP Input node." |
205 | 208 | } |
206 | 209 | ] |
207 | 210 | } |
|
210 | 213 | "section": "After the request message is processed, the message path is automatically highlighted on the message flow." |
211 | 214 | }, |
212 | 215 | { |
213 | | - "section": "Click on any connection to see the data that passed through that connection. You can see that the request (input) message data has been transformed into a different response XML message." |
214 | | - } |
| 216 | + "section": "Click on any connection to see the data that passed through that connection." |
| 217 | + }, |
| 218 | + { |
| 219 | + "section": "You can see that the request (input) message data has been transformed into a different response XML message." |
| 220 | + } |
215 | 221 | ] |
216 | 222 | }, |
217 | 223 | "helpLinks": |
218 | 224 | { |
219 | 225 | "title": "Find out more", |
220 | 226 | "details": |
221 | | - [ |
222 | | - { |
223 | | - "title": "Knowledge Center link to ", |
224 | | - "description": "Developing integration solutions by using applications", |
225 | | - "link": "com.ibm.etools.mft.doc/bi12002_.htm" |
226 | | - }, |
| 227 | + [ |
227 | 228 | { |
228 | 229 | "title": "Knowledge Center link to ", |
229 | 230 | "description": "Testing your message flow by using the Flow exerciser", |
230 | 231 | "link": "com.ibm.etools.mft.doc/rt26110_.htm" |
231 | 232 | } |
232 | 233 | ] |
233 | | - }, |
234 | | - "actions": |
235 | | - { |
236 | | - "title": "Run Actions", |
237 | | - "details": |
238 | | - [ |
239 | | - { |
240 | | - "name": "Deploy", |
241 | | - "method": "deployArtifacts()" |
242 | | - } |
243 | | - ] |
244 | 234 | }, |
245 | 235 | "exits": |
246 | 236 | { |
|
0 commit comments