Interoperability of Web services between Microsoft.NET and WebSphere application Server V7.0

1. Introduction

Through a series of standard technologies, WEB Services has become the first choice for enterprise to implement service-oriented architecture (oriented Architecture,soa). It realizes platform-independent and language independence in the real sense. As Web Services become more widely used, security and interoperability are becoming increasingly important. The specification for WEB Services Security and interoperability is then developed and constantly updated.

Currently, there are many security specifications for Web Services, including ws-addressing,ws-security,ws-reliable messaging (WS-RM), ws-secure Conversation (WS-SC), etc. They guarantee the security of Web Services from different angles and ranges.

Because the Web Services security specification involves various aspects of the authentication mechanism, confidentiality, and integrity of the message, and there is considerable scope to choose from, the support for Web services security provided by different application servers varies. This makes it a problem to secure interoperability between Web services and client running in different application server environments. As Java EE and Microsoft's. Net increasingly become the two mainstream platforms today, the solution of interoperability between them has become an important subject of many Web services interoperability standards. Microsoft's Windows Communication Foundation V3.0 (hereinafter referred to as WCF) is a collection of technologies for creating and running distributed systems, a complete technical framework designed by Microsoft for SOA that integrates. Net All previous distributed development technology under the platform. So the interoperation between Java EE and the. NET platform is primarily interoperability with WCF applications on. Net.

To this end, the organization Web Services Interoperability (WS-I), dedicated to improving interoperability, presented a series of overviews, including the WS-I basic profile,ws-i basic Secure profile, which showed that interoperability , how developers and Deployer should use various WEB Services standards. was V7.0 implemented full support for the WS-I Basic Security Profile 1.0 and most of the support for WS-I basic Security Profile 1.1. In the application server that supports Web Services, was the support of various standards is relatively comprehensive, relatively early.

Was V7.0 contained a set of Java API for xml-based Web Services (hereinafter referred to as JAX-WS) sample program, this article through the sample program configuration Web Service secure conversation security policy set, demonstrated How to implement interoperability between was V7.0 and Microsoft's WCF.

3. In the above figure, select the certificate (current user)-> personal-> certificate, right click on all Tasks-> import, will alice-key.p12 import, prompt password, input sampleapp.

4. Next, import Bob-cert.der to the certificate (current user)-> the trusted person-> certificate.

5. Then import the myca.cer into the trusted root certification authority.

If you are testing examples of Jax-ws Client access to WCF Service, you also need to do the following: Select a file-> add a snap-in, click Add on the Standalone tab, choose Certificate-> computer account, and then click Finish. Follow the steps above to import BOB-KEY.P12 into the personal certificate of the certificate (local computer). Import Alice-cert.der into the certificate of the trusted person for the certificate (local computer). Import Myca.cer into the Trusted root certification authority of the certificate (local computer).

Import certificates for JAX-WS applications

For the Jax-ws Service, it is necessary to import the WCF client side of Alice's certificate into the KeyStore in the was side. This article provides the JKS type of keystore:receiver.jks that is already in place, so just copy the mysyskeys.zip to the WebSphere server side and unlock mysyskeys.zip to a directory. For Jax-ws Client access to the WCF Service, you need to import Bob's certificate into the KeyStore in the was side, which provides the keystore:sender.jks that has been guided, as well as just a directory on the was side.