TEC Workbook - IBM

More documents

Recommendations

Info

<strong>IBM</strong> Software 3.2.11 DataPower Contexts While configuring the various actions (sign, transform, etc.), you may have noticed that each action declares an input and an output context. In the case of a transform action, the input context will be the document that is fed to the transformer, and the results of the transformation will be written to the output context. Some actions may only have an input context. For example, the verify action has an input context, but no output context; the signature verification either passes or fails. In contrast, some actions may only have an output context. The fetch action can fetch an XML document from a local file or a remote server, and the fetched document becomes the output context. Contexts are referred to by the following names: ● INPUT – represents the original message as it arrived from the client. ● OUTPUT – represents the outbound message which will be forwarded to the destination. In the case of client-to-server processing, the OUTPUT context represents what will be sent to the backend server. In the case of server-to-client processing, the OUTPUT context represents what will be returned to the client. ● NULL – indicates that the output is not needed. In other words, the output from the action is sent to the bit bucket. ● PIPE – indicates that the output of the action should be piped into the input of the next action. In this case, the input context of the next action must also specify PIPE. ● Named context – in this case, you can assign a name to a context and use it at a later point in the processing rule. For example, a transform action can be configured with an input context of INPUT and an output context of newRequest. Later in the processing rule, another action can use newRequest as the input context. __1. Click on the magnifying glass in front of the transform action. The XML document shown in the window shows what will be fed into the transform action as the context document. In this case, the message with the digital signature will be the input context to the transformation. __2. Click on the magnifying glass after the transform action (in front of the sign action). The input to the schema validate action is the results of the prior transform action. In the content section, notice that the digital signature has been removed. Page 62 WebSphere Lab Jam
<strong>IBM</strong> Software __3. Click on the last magnifying glass. It contains the contents of the OUTPUT context, which will be forwarded to the backend service. __4. Close the transaction detail window. __5. In the transaction list window, click on the magnifying glass to the left of the response. The INPUT context shown in the transaction window shows the response that came back from the backend service. __6. Click on the magnifying glass after the transform action. In the content section, you should that the transformation decoded the encoded description and expanded the benefits list into an XML nodeset. __7. Click on the magnifying glass after the sign action. In the content section, you should see that the message now contains a digital signature. __8. Finally, click on the last magnifying glass. It represents the content that will be returned to soapUI. Lab 3 - Securing XML Message Content using WS-Security Page 63
Page 1 and 2:
WebSphere Lab Jam Connectivity WebS
Page 3 and 4:
Contents IBM Software CONNECTION PA
Page 5 and 6:
Connection Parameters Spreadsheet I
Page 7 and 8:
1.4 Introduction to WebSphere DataP
Page 9 and 10:
IBM Software You’re now ready to
Page 11 and 12: There are several areas in the WebG
Page 13 and 14: 1.10 WebSphere DataPower Services I
Page 15 and 16: IBM Software Gateway supports WebSp
Page 17 and 18: cert: Directory Usage IBM Software
Page 19 and 20: __7. Click on the small plus sign t
Page 21 and 22: 1.13 Logging IBM Software WebSphere
Page 23 and 24: ● Trigger a set of actions to occ
Page 25 and 26: 1.13.4 Appliance management IBM Sof
Page 27 and 28: 1.13.8 Configuration Comparison, Ch
Page 29 and 30: Lab 2 Working with XML Prerequisite
Page 31 and 32: 2.1.5 WebSphere DataPower Configura
Page 33 and 34: IBM Software It’s also possible t
Page 35 and 36: Match Rule - evaluate statements us
Page 37 and 38: IBM Software __18. In the Configure
Page 39 and 40: IBM Software __2. Expand the policy
Page 41 and 42: IBM Software __12. In soapUI, click
Page 43 and 44: IBM Software __3. Click the green s
Page 45 and 46: The SQL statement would become: SEL
Page 47 and 48: __2. Click and drag a transform act
Page 49 and 50: 2.7 Stylesheet Caching IBM Software
Page 51 and 52: 2.8.3 Virus Scanning IBM Software V
Page 53 and 54: Lab 3 Securing XML Message Content
Page 55 and 56: 3.2.2 Create the Crypto Key and Cer
Page 57 and 58: 3.2.7 Verifying the request signatu
Page 59 and 60: __8. Click the Close Window link to
Page 61: __12. Click on the small [+] to sho
Page 65 and 66: IBM Software __6. In the list of co
Page 67 and 68: __11. Click the Done button in the
Page 69 and 70: Lab 4 Access Control Framework Prer
Page 71 and 72: __3. Double click the yellow outlin
Page 73 and 74: Appendix A. Notices This informatio
Page 75 and 76: Appendix B. Trademarks and copyrigh
Page 77 and 78: NOTES
show all

TEC Workbook - IBM

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

Delete template?

Save as template?