500 Patterns: Extended Enterprise SOA and Web Services
Figure B-11 An example of a special needs object type, customerRef.
8. After inputting all of the values, click Go at the bottom of the Actions frame.
9. If everything runs properly, the message that is shown in the Status frame of
the Web Services Explorer should be identical to the message coded into the
.NET Web service. This response is shown in Figure B-12.
Figure B-12 Successful response from the .NET Web service
10.Click the Source link to see the SOAP request and response messages used
during the Web services interaction.
Congratulations! You have implemented J2EE client consumer that has
successfully sent to and received messages from a .NET Web service. We now
explain how to enable Microsoft Internet Information Server to require
transport-level security using SSL for all incoming requests.
B.3 Enabling transport-level security with SSL
In remaining consistent with the Extended Enterprise context, it is common
security practice to introduce a layer of transport-level security between a Web
service provider and client. This security takes the form of SSL/HTTP in order to
Get Patterns: Extended Enterprise SOA and Web Services now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
