![]() |
Sun Java System Access Manager 2005Q1 Sample |
Application Server Samples Readme FileIntegrating with Access Manager on Application ServerThis document describes about the deployment issues when the applications (consists of Servlets and JSPs ) are integrating with Access Manager on Sun Java System Application Server. Access Manager deploys as a war file on Sun Java System Application Server. Sun Java System Application Server supports multi JVMs, load balancing and hence the performance. The goal of the load balancing is to evenly distribute the workload between multiple Sun Java System Application Server engines/processes. But if the requests within the same session are processed by more than one Sun Java System Application Server engine/process, session information that is not configured to be distributed is lost. Therefore applications which are based on Session information should use sticky load balancing when deploying onto Sun Java System Application Server. Access Manager is a session based application and will use sticky load balancing for it's deployment. Deployment on Sun Java System Application ServerSun Java System Application Server needs two XML files for
deploying any kind of applications such as Registering Application ComponentsDeploying Servlets:
A sample
<?xml version="1.0" ?> <!DOCTYPE web-app> <web-app> <display-name>Sample File</display-name> <servlet> <servlet-name>SimpleServlet</servlet-name> <servlet-class>com.iplanet.samples.SampleServlet</servlet-class> </servlet> <servlet-mapping> <servlet-name>SimpleServlet</servlet-name> <url-pattern>/simpleservlet</url-pattern> </servlet-mapping> </web-app>
<?xml version="1.0" ?> <ias-web-app> <servlet> <servlet-name>SimpleServlet</servlet-name> <guid>{aaaabbbb-A456-161A-8be4-0800203942f2}</guid> <sticky>true</sticky> </servlet> </ias-web-app>
Once the application is deployed, the servlet is accessible from from this URL
Deploying JSPsThere are two ways to deploy JSPs on Sun Java System Application Server, unregistered and registered. Unregistered JSPs are deployed by just copying into the corresponding directory structure like an HTML files. They need not mention inweb.xml and ias-web.xml files. Sun Java System Application Server
allows JSPs to be registered with GUIDs with XML file. This
will allow JSPs to use Sun Java System Application Server specific features like load balancing etc.
If the Applications JSPs are Session based and when they integrate with
Access Manager, they should be registered JSPs.
Sample <?xml version="1.0" ?> <!DOCTYPE web-app> <web-app> <display-name>An Example Registered JSP File </display-name> <servlet> <servlet-name>JSPExample</servlet-name> <jsp-file>JSPExample.jsp</jsp-file> </servlet> <servlet-mapping> <servlet-name>JSPExample</servlet-name> <url-pattern>/jspexample</url-pattern> </servlet-mapping> </web-app>
<?xml version="1.0" ?> <ias-web-app> <servlet> <servlet-name>JSPExample</servlet-name> <guid>{aaaabbbb-B456-161A-8be4-0800803942f2}</guid> <sticky>true</sticky> </servlet> </ias-web-app> This JSP can accessed by using a URL
Access Manager SamplesAccess Manager supplies a sample war file to deploy onto Sun Java System Application Server.
This war file consists of In order to run these samples, deploy this war file using Sun Java System Application Server deployment tool
These samples will describe how to create /display a user
and they use a sample servlet and JSP pages to describe the flow
To create a user, There's no need of adding Access Manager class files to the CLASSPATH variable in order to run these samples since we are deploying Access Manager as a war file and hence Sun Java System Application Server takes care of it. |