Java Industry News
Modernizing Axis1 Services Painlessly
Migrating with WSAS
By: Michael Galpin
May. 28, 2008 03:30 PM
Managing the Service on WSAS
The various modules in the Module combo box represent Axis2 modules that implement various WS-*. Let’s say we’re interested in WS-Security. To enable this, we simply pick rampart from the list, as shown in Figure 9. Click the Engage button, and just like that WSAS will activate its WS-Security module for your service, as shown in Figure 10. Similarly, you can pick sandesha from the Module list and WSAS will enable WS-Reliable Messaging for your service. Let’s take a look at some of the security options we have available to us.
Notice that WSAS already has both a trusted certificate store and a keystore location provided to support encryption. The Management Console has a Keystore tab (on the left) that you can use to manage certificates and providers. Once you apply the security configuration, you can go back to the list of services and click on the Policy, as shown in Figure 13.
This will bring up the Policy, shown in Listing 3. The Policy is an extensible way to configure any/all of the WS-* technologies you have enabled for your service. Where did this Policy come from? It was generated by WSAS for you when you selected the Security Configuration. You can still manually edit this file either to tweak security or to configure your WS-Reliable Messaging policy.
Reader Feedback: Page 1 of 1
SOA World Latest Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week