Getting Started with IBM Data Studio for DB2

More documents

Recommendations

Info

372 Getting Started with IBM Data Studio for DB2 treat multibyte UTF-8 characters in URLs correctly. Tomcat With Tomcat, you need to add the attribute URIEncoding="UTF-8" to your configurations in theserver.xml file. More details can be found here: http://wiki.apache.org/tomcat/FAQ/Connectors WebSphere Application Server Community Edition (WAS CE): WAS CE ships Tomcat as its web container - but there is noserver.xml file. Instead, there is a Tomcat configuration section in the$WASCE_HOME/var/config/config.xml file. You need to add UTF-8 to the section. More details can be found here: http://publib.boulder.ibm.com/wasce/V2.1.1/en/tomcat-configuration.html SQL NULL values are treated as absent. This means parameter values that are not present in the key/value string are set to SQL NULL. A parameter with an empty value is treated as an empty string. You can also easily test the HTTP GET binding with your web Browser. Simply enter the URL into your browser to start the web service operation. Figure E.6 shows what the RankEmployee operation looks like when you open it with Firefox. Figure E.6 – The service response in a web browser window E.1.6 HTTP POST (JSON) Binding Finally, data web services provides you with a simple JSON binding that can be leveraged from JavaScript applications –for example, when using AJAX with theXMLHttpRequest
Appendix E – Advanced topics for developing data web services 373 object. In order to test the JSON binding with cURL you need to create the JSON request message first. The building rules for a data web services JSON request message are as follows: {"":{"":,"":,...}} Note: JSON data type formatting: The data type formats follow the JSON specification. Date, time and timestamp types are expected to be provided in XSD format: xs:date, xs:time and xs:dateTime. Binary data types are expected as base64 encoded strings. SQL NULL values are represented as JSON null. Create a new file calledRankEmployeeJSON.txt. The content of the file should look like this: {"RankEmployee": {"EMPLOYEE_CODE":10004,"RANKING":"Excellent"} } The cURL command to send the request to the web service should look this: curl.exe -d @"GetBestSellingProductsByMonthJSON.txt" -H "Content-Type:application/json;charset=utf-8" -v http://localhost:8080/WebServicesSimpleService/rest/SimpleService/RankEmpl oyee The output of the command should look similar to what is shown in Listing E.3. ... < HTTP/1.1 200 OK < Server: Apache-Coyote/1.1 < Cache-Control: no-cache, no-store, max-age=0 < Expires: Thu, 01 Jan 1970 00:00:01 GMT < Content-Type: application/json;charset=UTF-8 < Content-Length: 129 < Date: Sun, 28 Jun 2009 04:48:26 GMT < {"RankEmployeeResponse":[{"RANKING_DATE":"2009-06-27T21:48:26.203Z","RANKING_YEA R":2009,"EMPLOYEE_CODE":10004,"RANKING_CODE":5}]} Listing E.3 – The service response The response is also formatted as JSON. Note: Switching output format from XML to JSON: For all HTTP RPC bindings, if the response should be returned as XML or JSON, you can specify the_outputFormat control parameter (the initial underscore character marks it as a control parameter) in the URL to define. For all bindings except HTTP POST (JSON), the
Page 1 and 2:
]
Page 3 and 4:
3 Notices This information was deve
Page 5 and 6:
Table of contents 5 Table of conten
Page 7 and 8:
3.3.1 Exporting data...............
Page 9 and 10:
Chapter 7 - Tuning queries ........
Page 11 and 12:
11.4 Community and resources ......
Page 13 and 14:
Preface 13 Keeping your skills curr
Page 15 and 16:
around the world have participated
Page 17 and 18:
17 About the authors Dimple Bhatia
Page 19 and 20:
Contributors 19 The following peopl
Page 21:
21 Acknowledgements The authors owe
Page 24 and 25:
24 Getting Started with IBM Data St
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
100 Getting Started with IBM Data S
Page 103 and 104:
103 Chapter 3 - Maintaining the dat
Page 105 and 106:
Chapter 3 - Maintaining the databas
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Figure 3.35 - Selecting additional
Page 135 and 136:
Page 137:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 159 and 160:
159 Chapter 5 - Creating SQL and XQ
Page 161 and 162:
Chapter 5 - Creating SQL and XQuery
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
On Success On Error Result Chapter
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
193 Chapter 6 - Managing jobs Job m
Page 195 and 196:
Chapter 6 - Managing jobs 195 6.3 J
Page 197 and 198:
Chapter 6 - Managing jobs 197 6.4 C
Page 199 and 200:
Chapter 6 - Managing jobs 199 Figur
Page 201 and 202:
Chapter 6 - Managing jobs 201 Comp
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Chapter 6 - Managing jobs 207 6.5 R
Page 209 and 210:
Chapter 6 - Managing jobs 209 6.6.2
Page 211 and 212:
Page 213 and 214:
213 Chapter 7 - Tuning queries In t
Page 215 and 216:
Chapter 7 - Tuning queries 215 Figu
Page 217 and 218:
Chapter 7 - Tuning queries 217 You
Page 219 and 220:
Chapter 7 - Tuning queries 219 •
Page 221 and 222:
Page 223 and 224:
7.4.2 Run the Statistics Advisor an
Page 225 and 226:
Chapter 7 - Tuning queries 225 7.4.
Page 227 and 228:
Chapter 7 - Tuning queries 227 For
Page 229 and 230:
Page 231 and 232:
Chapter 7 - Tuning queries 231 To s
Page 233 and 234:
Chapter 7 - Tuning queries 233 3. O
Page 235 and 236:
Chapter 7 - Tuning queries 235 7.6
Page 237 and 238:
237 Chapter 8 - Developing SQL stor
Page 239 and 240:
Chapter 8 - Developing SQL stored p
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323: 322 Getting Started with IBM Data S
Page 355 and 356: 355 Appendix D - The Sample Outdoor
Page 357 and 358: Appendix D - The Sample Outdoor Com
Page 363 and 364: Appendix E - Advanced topics for de
Page 371: Appendix E - Advanced topics for de
Page 389 and 390: E.5.4 Data web services artifacts A
Page 391 and 392: References 391 References [1] HAYES
Page 393 and 394: References 393 Books and articles 1
Page 396: 396 Getting started with IBM Data S
show all

Getting Started with IBM Data Studio for DB2

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?