Skip to content

Commit f1188f2

Browse files
committed
Update _data.json
Editted instructions to be Compute node ESQL specific
1 parent 2f481a6 commit f1188f2

1 file changed

Lines changed: 20 additions & 20 deletions

File tree

doc/_data.json

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -28,22 +28,22 @@
2828
{
2929
"_comments":"formal phrase == 'View Details', casual phrase == '?'",
3030
"text":"View Details",
31-
"link":"tutorials/TransformationXSL/overview.html"
31+
"link":"tutorials/TransformationESQL/overview.html"
3232
},
3333
"buttonStartTutorial":
3434
{
3535
"_comments":"formal phrase == 'Start Tutorial', casual phrase == '?'",
3636
"text":"Start Tutorial",
37-
"link":"tutorials/TransformationXSL/steps/steps.html"
37+
"link":"tutorials/TransformationESQL/steps/steps.html"
3838
},
3939
"_commentskillLevel":"1=novice, 2=beginner, 3=intermediate, 4=Advanced or experienced and 5=Expert or Guru",
4040
"skillLevel":"2",
4141
"_commentConceptsUsed":"Give a list",
4242
"conceptsUsed":
4343
[
4444
{
45-
"concept":"XML Transformation node",
46-
"description":"XML Transformation node"
45+
"concept":"Compute node",
46+
"description":"Compute node"
4747
}
4848
]
4949
},
@@ -88,8 +88,8 @@
8888
"tutorial":
8989
{ "_common":
9090
{
91-
"name":"Transformation using XSL in a message flow",
92-
"shortDescription":"Learn how to use an XML Transformation node to transform data using an XML Stylesheet in an IBM Integration Bus message flow by exploring this simple example.",
91+
"name":"Transformation using ESQL in a message flow",
92+
"shortDescription":"Learn how to use a Compute node to transform data using ESQL in an IBM Integration Bus message flow by exploring this simple example.",
9393
"_comment_category":"Categories are either 'tool' or 'scenario'",
9494
"category":"tool",
9595
"isPattern" : "false",
@@ -104,8 +104,8 @@
104104
"topicList":
105105
[
106106
{
107-
"title":"XML Transformation node",
108-
"description":"XML Transformation node"
107+
"title":"Compute node",
108+
"description":"Compute node"
109109
},
110110
{
111111
"title":"XML parsing and writing",
@@ -116,8 +116,8 @@
116116
"outcomeList":
117117
[
118118
{
119-
"title":"Use IBM Integration Bus to create and invoke a message flow which transforms data using an XML stylesheet.",
120-
"description":"Use IBM Integration Bus to create and invoke a message flow which transforms data using an XML stylesheet."
119+
"title":"Use IBM Integration Bus to create and invoke a message flow which transforms data using ESQL.",
120+
"description":"Use IBM Integration Bus to create and invoke a message flow which transforms data using ESQL."
121121
}
122122
],
123123
"summary":
@@ -127,10 +127,10 @@
127127
"sections":
128128
[
129129
{
130-
"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 an XML Transformation node (whose behavior is based on a stylesheet, and sends this back to the HTTP request."
130+
"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 Compute node (whose behavior is based on ESQL), and sends this back to the HTTP request."
131131
},
132132
{
133-
"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 an XML Transformation node, a graphical data mapping node, a Compute node (which uses ESQL), a JavaCompute node (which can navigate data using an IBM Integration Bus Java API or JAXB) and a .NET Compute node."
133+
"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 graphical data mapping node, a JavaCompute node (which can navigate data using an IBM Integration Bus Java API or JAXB), an XML Transformation node and a .NET Compute node."
134134
}
135135
]
136136
}
@@ -147,7 +147,7 @@
147147
"sections":
148148
[
149149
{
150-
"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 an XML Transformation node (whose behavior is based on a stylesheet, and sends this back to the HTTP request."
150+
"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 Compute node (whose behavior is based on ESQL), and sends this back to the HTTP request."
151151
},
152152
{
153153
"section":"You will import the message flow to your Integration Toolkit workspace, deploy it to your default integration server, and invoke the message flow by using the Flow exerciser."
@@ -197,7 +197,7 @@
197197
"sections":
198198
[
199199
{
200-
"section":"The Transformation_XSL application includes one project that is imported into your workspace."
200+
"section":"The Transformation_ESQL application includes one project that is imported into your workspace."
201201
}
202202
]
203203
},
@@ -210,7 +210,7 @@
210210
"section":"Developing integration solutions by using applications."
211211
},
212212
{
213-
"section":"The Transformation_XSL application is shown in the Application Development view of your workspace. You can explore the message flow Transformation_XSL.msgflow inside the application before deploying the application to an integration node."
213+
"section":"The Transformation_ESQL application is shown in the Application Development view of your workspace. You can explore the message flow Transformation_ESQL.msgflow inside the application before deploying the application to an integration node."
214214
}
215215
]
216216
},
@@ -238,7 +238,7 @@
238238
"sections":
239239
[
240240
{
241-
"section":"The Transformation_XSL application is shown in the Application Development view of your workspace."
241+
"section":"The Transformation_ESQL application is shown in the Application Development view of your workspace."
242242
},
243243
{
244244
"section":""
@@ -256,7 +256,7 @@
256256
"sections":
257257
[
258258
{
259-
"section":"The Transformation_XSL application will be deployed to your default integration server."
259+
"section":"The Transformation_ESQL application will be deployed to your default integration server."
260260
},
261261
{
262262
"section":"The message flow is then started and ready to be invoked."
@@ -289,15 +289,15 @@
289289
"sections":
290290
[
291291
{
292-
"section":"The Transformation_XSL application is shown in the Application Development view of your workspace.",
292+
"section":"The Transformation_ESQL application is shown in the Application Development view of your workspace.",
293293
"steps":
294294
{
295295
"type":"ordered",
296296
"details":
297297
[
298298
{
299299
"name":"",
300-
"details":"Open the Transformation_XSL message flow, and click the Flow Exerciser icon to start recording the message path through the flow."
300+
"details":"Open the Transformation_ESQL message flow, and click the Flow Exerciser icon to start recording the message path through the flow."
301301
},
302302
{
303303
"name":"",
@@ -350,4 +350,4 @@
350350
}
351351
}
352352
}
353-
}
353+
}

0 commit comments

Comments
 (0)