Generating Specialized WARs with Generation X
By docteger on Jun 15, 2008
Here are the instructions in the README found in the
/deployable-wardirectory of the extracted
opensso.zip. It describes how to generate a specialized WAR for deployment. I've added some explanations to the procedure.
- Create a new directory as the staging area for the WAR you want to generate. For example:
% mkdir /noconsolewar
- Extract the contents of
% cd /noconsolewar % jar xvf /opensso/deployable-war/opensso.war
- Create the WAR using the appropriate
.listfile. For example:
% cd /noconsolewar % jar cvf /opensso/deployable-war/fam-nocon.war @/opensso/deployable-war/fam-noconsole.list
.listfiles included are:
fam-idpdiscovery.listlists the files needed to generate a WAR to deploy the Identity Provider Discovery Service.
fam-distauth.listlists the files needed to generate a WAR to deploy the Distributed Authentication User Interface.
fam-console.listlists the files needed to generate a WAR to deploy a Federated Access Manager console only.
fam-noconsole.listlists the files needed to generate a WAR to deploy a Federated Access Manager server without the console.
- Update the generated WAR with the additional files found in the appropriate directory. For example:
Directories included are:
% cd /opensso/deployable-war/noconsole % jar uvf /opensso/deployable-war/fam-nocon.war \*
idpdiscoverycontains additional files for the Identity Provider Discovery Service WAR.
distauthcontains additional files for the Distributed Authentication User Interface WAR.
consolecontains additional files for the console only WAR.
noconsolecontains additional files for the Federated Access Manager server without a console WAR.
- Deploy your specialized WAR.
- Access the WAR deployment URL from your browser to configure. For example: