This section contains the following topics:
Edit Deployment Descriptors of JAX-RPC Applications
Configure Policies for the SiteMinder WSS Agent
After completing WebSphere-side configuration of the SiteMinder WSS Agent, you must restart WebSphere.
To restart IBM WebSphere
To stop the server, you will require the server user ID and Server user password you entered when configuring LDAP as a WebSphere user registry. The command is:
stopServer server1 -username serveruserID -password serveruserpassword
To start the server, you do not need a password:
startServer server1
WebSphere’s SystemOut.log and SystemErr.log file resides in:
WAS_HOME/profiles/profile_name/logs/server_name
The logs indicate should indicate that everything is working correctly. If the logs indicate problems, you should troubleshoot your configuration.
To protect a JAX-RPC web service you must edit its deployment descriptor to add the SiteMinder WSS Agent JAX-RPC Handler.
To edit a JAX-RPC web service deployment descriptor
<handler> <handler-name>SiteMinder WSS Agent Handler</handler-name> <handler-class> com.ca.soa.agent.appserver.jaxrpc.XMLgentJaxrpcHandler </handler-class> </handler>
Note: The SiteMinder WSS Agent JAX-RPC handler must always be invoked first; If other handler elements are already present or subsequently added to the webservices.xml file, the SiteMinder WSS Agent JAX-RPC Handler element must placed before them.
You create authentication and authorization policies to protect web service resources hosted on WebSphere from their associated WSDL files using the CA SiteMinder® Web Services Security Configuration User Interface. For more information, see the CA SiteMinder® Web Services Security Policy Configuration Guide.
Copyright © 2013 CA.
All rights reserved.
|
|