| PrintNumber | ErrorLocation | Error | Correction | DateAdded |
|---|---|---|---|---|
| 1 | Back Cover | John Rasmussen is a Senior IT Specialist with IBM Software Services for WebSphere and has worked with DataPower devices for seven years. | John Rasmussen is a Senior IT Specialist with IBM Software Services for WebSphere and has worked on the engineering and integration of DataPower devices, since their earliest implementations. | 3/2/2009 |
| 1 | p227 | If the SetReplyTo option had been utilized on the backend dpmq URL, any ReplyQueue specified would have been entered automatically into the MQMQ ReplyToQ header. | If the SetReplyTo option had been utilized on the backend dpmq URL, any ReplyQueue specified would have been entered automatically into the MQMD ReplyToQ header. | 3/2/2009 |
| 1 | p229 | The result of synchronization (parameters or MQ properties) is dependant upon the completion each transaction. | The result of synchronization (parameters or MQ properties) is dependant upon the completion of each transaction. | 3/2/2009 |
| 1 | p320 | Combining these techniques can help you in building flexible, efficient, and powerful Web service proxies for all your Web applications. | Combining these techniques can help you in building flexible, efficient, and powerful proxies for all your Web applications. | 3/2/2009 |
| 1 | p399 | This investigation leads to a sample configuration architecture and a demonstration of the migration of configuration settings from development through production. | This investigation leads to a sample configuration architecture and a discussion of the migration of configuration from development through production. | 3/2/2009 |
| 1 | p403 | You may have more than one configuration file on the device at a time, although only one is the active configuration. | You may have more than one defualt domain configuration file on the device at a time, although only one is the active configuration. | 3/2/2009 |
| 1 | p404 | Figure 15-5 updated | fixed | 3/2/2009 |
| 1 | p412 | It will not release a private key or certificate from the certificate (cert:) directory; this is a valuable security attribute. | It will not release a private key or certificate from the private certificate directories (cert: and sharedcert:); this is a valuable security attribute. | 3/2/2009 |
| 1 | p417 | The black-list is not required, and only those objects within the while-list range that are not to be imported need be identified. | The black-list is not required, and only those objects within the black-list range that are not to be imported need be identified. | 3/3/2009 |
| 1 | p418 | You may have been intimidated by the URI string, but fear not, the Build button (seen in Figure 15-25) allows for easy creation, just as with the accepted and filtered configuration URI strings. All you have to do is identify the resource—there’s even a drop-down box for the resource type (objects), and you can use PCRE (PERL compatible regular expressions) to match multiple objects with a single string. | You may have been intimidated by the configuration match string, but fear not, the Build button (seen in Figure 15-25) allows for easy creation, just as with the accepted and filtered configuration URI strings. All you have to do is identify the resource—there’s even a drop-down box for the resource type (objects), and you can use PCRE expressions to match multiple objects with a single string. | 3/3/2009 |
| 1 | p419 | Figure 15-26 Deployment Policy URL builder | Figure 15-26 Deployment Policy configuration match builder | 3/3/2009 |
| 1 | p422 | Listing 15-7 and Listing 15-8: source-url “https://9.33.96.224:8080/BookServiceExport.zip” |
Should be: source-url “https://192.168.1.35:8080/BookServiceExport.zip” |
3/3/2009 |
| 1 | p423 | Listing 15-9: copy -f https://9.33.96.224:8080/IdentityDocument.xml |
Should be: copy -f https://192.168.1.35:8080/IdentityDocument.xml |
3/3/2009 |
| 1 | p433 | These are the individual exports that the developers created from the development environment. | These are the exports created from the development environment merged with the previous generation of the application domain configuration. | 3/3/2009 |
| 1 | p748 | Figure 25-25 typo .xcl |
fixed .xsl | 3/3/2009 |
| 1 | p748 | Further steps must be taken to refresh the cache with this new file, such as manually refreshing the stylesheet cache in the XML manager, creating a URL Refresh Policy, or not caching them at all while developing. |
Further steps must be taken to refresh the cache with this new file, such as manually refreshing the stylesheet cache in the XML Manager, creating a URL Refresh Policy, or not caching them at all while developing. | 3/3/2009 |
| 1 | p761 | Note that this contains a rather tricky construct for repeating data—the OCCURS DEPENDING ON clause. | Note that this contains a construct for repeating data—the OCCURS DEPENDING ON clause. | 3/4/2009 |
| 1 | p778 | The first step is to locate the generated artifacts in the Design Studio workspace directory for your project, and upload those to the DataPower appliance. There will be an XML file, which is the metadata to be used by the DataGlue engine to do the transformation, and two .mts files, which are the descriptions of the data, the type trees. | The first step is to locate the generated artifacts in the Design Studio workspace directory for your project, and upload those to the DataPower appliance. If you are using DPA mode, this will be one file with a .dpa extension. Otherwise, there will be an XML file, which is the metadata to be used by the DataGlue engine to do the transformation, and two .mts files, which are the descriptions of the data, the type trees. | 3/4/2009 |
| 1 | p778 | Next, the XML file that was just uploaded must be specified in the WTX Map file field. There is no need to specify the MTS files anywhere—they are referenced inside the XML file. | Next, the XML or DPA file that was just uploaded must be specified in the WTX Map file field. There is no need to specify the MTS files anywhere—they are referenced inside the XML file or contained in the DPA file. | 3/4/2009 |
| 1 | p779 | Figure 26-29 updated | fixed | 3/4/2009 |
| 1 | p884 | Add to Table: WSDM Web Services Distributed Management |
fixed | 3/4/2009 |