A Family of fam Directories

In the midst of deploying, configuring and launching Federated Access Manager to learn about the Fedlet, I got a bit confused about the different directories that are created during the process. The first time I come into contact with a fam directory is when I download fam.zip. When the file is unzipped, everything is put into the /fam directory on the same level on which the ZIP was downloaded. This directory contains fam.war which will be used to deploy Federated Access Manager as well as other adjunct pieces of Federated Access Manager. This directory is not used by Glassfish (my web container of choice) or Federated Access Manager, and should be exploded in a download directory of your choice.

The second fam directory rears it's head when I log into the Glassfish console to deploy fam.war. By default, Glassfish uses the name of the about-to-be-deployed WAR file (without the file extension .war) as the value for its Application Name and Context Root attributes. The context root, which must start with a forward slash (/) and end with a string, identifies a unique, base directory for a web application deployed in a J2EE web container. Glassfish creates this directory in /glassfish/domains/domain_name/applications/j2ee-modules/, and the URL for the deployed web application will include this context root; in this example, http://host_machine:port/fam. The J2EE web container then uses this URL to determine which web application services an incoming request. The context root is stored in sun-web.xml, and the value can be manually modified while deploying the WAR if you want to use another name besides that ubiquitous fam.

The final fam directory is the default value for the configuration directory created after the WAR is deployed and the Federated Access Manager Configurator is launched. This value can be changed to any directory to which the web container can write - and I would do that to remain sane. In the course of configuration, a tree is created under the configuration directory that contains the bootstrap file, a sub config directory, an opends directory, and other files.

So there you have it: three directories with different purposes that make Federated Access Manager family friendly. Now join hands with a different Family, the cast of Dreamgirls.

Comments:

Nice writeup, Michael, as always! You know, we're running the risk of just ANYBODY being able to deploy and configure FAM ;-)

Posted by Pat Patterson on May 30, 2008 at 12:49 PM PDT #

Thanks, Pat. And I should've let everyone know that it was SuperPat who answered my questions regarding these different directories.

Posted by DocTeger on June 02, 2008 at 12:27 AM PDT #

don't forget the LDAP directories :)

Posted by horto on July 15, 2008 at 12:46 AM PDT #

Oyyy, don't get me started on that! OK, I'll get something written ASAIC.

Posted by DocTeger on July 15, 2008 at 01:08 AM PDT #

Post a Comment:
Comments are closed for this entry.
About

docteger

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today