Security Context : Programmer’s Checklist for Security Context

Programmer’s Checklist for Security Context
Developers of web service programs can use this checklist during the four phases of the development cycle: installing Management Agent for WebSphere software, coding your Java program, compiling your Java program, and deploying your program as a WebSphere service.
Install
Install the Management Agent for WebSphere software release, which automatically includes the Java archive file com.tibco.policyagent.was.api_version.jar, which contains the class com.tibco.amma.was.security.SecurityContext.
Code
Import com.tibco.amma.was.security.
Implement the ServiceLifecycle interface.
Its init method must initialize the instance variable (of type ServletEndpointContext).
For JAX-WS services, your endpoint implementation class must define a variable of type WebServ iceContext, using the @Resource annotation.
Compile
The CLASSPATH variable must include the archive file directory TIBCO_HOME/components/eclipse/plugins, to access the archive file com.tibco.policyagent.was.api_version.jar.
The CLASSPATH variable must include the directory TIBCO_HOME/components/eclipse/plugins/com.tibco.policy.agent.lib_version, to access the archive file ap-xmlaccess.jar. <>
For JAX-RPC services, the CLASSPATH variable must include the directory was_home/runtimes, to access the archive file com.ibm.ws.webservices.thinclient_6.1.0.jar.
For JAX-WS services, the CLASSPATH variable must include the directory was_home/plugins, to access the archive file org.apache.axis2_6.1.0.jar.
Deploy
When you deploy your Java services in a WebSphere application server, you must not disable the WebSphere installation option Create MBeans for resources (this option is enabled by default).