278N/A<?
xml version="1.0" encoding="UTF-8"?>
278N/A ! This work is licensed under the Creative Commons 278N/A ! Attribution-NonCommercial-NoDerivs 3.0 Unported License. 278N/A ! To view a copy of this license, visit 278N/A ! or send a letter to Creative Commons, 444 Castro Street, 278N/A ! Suite 900, Mountain View, California, 94041, USA. 278N/A ! You can also obtain a copy of the license at 278N/A ! See the License for the specific language governing permissions 278N/A ! and limitations under the License. 278N/A ! If applicable, add the following below this CCPL HEADER, with the fields 278N/A ! enclosed by brackets "[]" replaced with your own identifying information: 278N/A ! Portions Copyright [yyyy] [name of copyright owner] 278N/A ! Copyright 2012-2013 ForgeRock AS 735N/A<
chapter xml:
id='chap-javaee-agents' 278N/A <
title>Java EE Policy Agents <?
eval ${
agentsDocTargetVersion}?></
title>
278N/A <
para>This chapter concerns OpenAM Java EE policy agents. Java EE policy
278N/A agents run in web application containers and protect Java EE
278N/A <
para>OpenAM Java EE Policy Agents <?
eval ${
agentsDocTargetVersion}?> Xpress
278N/A is a milestone release from the main development branch of the product. The
278N/A Xpress release contains selected key features and all current fixed issues.
278N/A An Xpress release undergoes important functional testing but not the complete
278N/A testing cycle that is done for a full Enterprise release.</
para>
278N/A <
para>Xpress releases are supported through ForgeRock subscriptions and are
278N/A upgradeable to the Enterprise version, which has long term support.</
para>
278N/A <
para>The goal of an Xpress release is to enable you to start build phases
278N/A earlier, with the most recent features, instead of having to wait for the
278N/A Enterprise release date. Fixes to issues that are discovered in an Xpress
278N/A release are delivered as patches to ForgeRock customers, and are guaranteed
278N/A to be delivered in the Enterprise release that follows. Xpress releases are
278N/A supported for a grace period after the Enterprise version has been
278N/A <
para>With the exception of these Release Notes, the official documentation
278N/A for this release is still in progress, and is accessible at
278N/A documentation set will be available with the Enterprise release.</
para>
278N/A <
section xml:
id="what-new-javaee-agents">
278N/A <
title>New in JavaEE Policy Agents <?
eval ${
javaEEAgentsDocTargetVersion}?></
title>
278N/A <
para>The Java EE agent goto URL can now be modified (<
link 278N/A xlink:
show="new">OPENAM-1299</
link>).</
para>
278N/A <
para>The Apache Tomcat policy agent now supports Tomcat 7 as well (<
link 278N/A xlink:
show="new">OPENAM-1273</
link>).</
para>
278N/A <
para>Java EE policy agents can now conditionally redirect users based on
278N/A the incoming request URL (<
link 278N/A xlink:
show="new">OPENAM-1265</
link>).</
para>
278N/A now parses as valid XML (<
link 278N/A xlink:
show="new">OPENAM-674</
link>).</
para>
278N/A <
section xml:
id="before-you-start-javaee-agents">
278N/A <
title>Before You Install OpenAM Java EE Policy Agents</
title>
278N/A <
para>This section covers software and hardware prerequisites for installing
278N/A and running OpenAM Java EE Policy Agents.</
para>
278N/A <
para>If you have a special request to support a combination not listed here,
278N/A contact ForgeRock at <
link xlink:
href="mailto:info@forgerock.com" 278N/A >info@forgerock.com</
link>.</
para>
278N/A <
section xml:
id="java-requirements-javaee-agents">
278N/A <
title>Java EE Agents Java Requirements</
title>
278N/A <
para>Java EE policy agents run in a Java EE Web container.
278N/A Please review the <
link xlink:
show="new" 278N/A <
citetitle>OpenAM Release Notes</
citetitle></
link> for the currently supported version
278N/A of Java. ForgeRock recommends the most recent update of the installed version of Java
278N/A to ensure you have the latest security fixes.</
para>
278N/A <
para>ForgeRock has tested this release with Oracle Java SE JDK.</
para>
278N/A <
section xml:
id="browser-requirements-javaee-agents">
278N/A <
title>Java EE Agents Browsers Tested</
title>
278N/A <
para>ForgeRock has tested this policy agent release with the following web
<
listitem><
para>Chrome release 16 and later</
para></
listitem>
<
listitem><
para>Firefox 3.6 and later</
para></
listitem>
<
listitem><
para>Internet Explorer 7 and later</
para></
listitem>
<
section xml:
id="web-container-requirements-javaee-agents">
<
title>Web Application Container Requirements</
title>
<
para>Java EE policy agents support the following Java EE application
<
para><?
eval ${
agentTomcatSupport}?></
para>
<
para><?
eval ${
agentGlassFishSupport}?></
para>
<
para><?
eval ${
agentWebSphereSupport}?></
para>
<
para><?
eval ${
agentJBossSupport}?></
para>
<
para><?
eval ${
agentJettySupport}?></
para>
<
para><?
eval ${
agentWebLogicSupport}?></
para>
<
section xml:
id="platform-requirements-javaee-agents">
<
title>Java EE Agents Platform Requirements</
title>
<
para>Apache Tomcat Java EE policy agents have been tested on Linux 2.6 or
later, and on Microsoft Windows Server 2008 R2.</
para>
<
para>GlassFish Java EE policy agents have been tested on Oracle Solaris 10
<
para>Other Java EE policy agents have been tested on Linux 2.6 or
<
para>Testing has focused on 64-bit operating systems.</
para>
<
section xml:
id="hardware-requirements-javaee-agents">
<
title>Java EE Agents Hardware Requirements</
title>
<
para>You can deploy OpenAM Java EE policy agents on any hardware supported
for the combination of software required.</
para>
<
para>ForgeRock has tested this release on x86 and x64 based systems.</
para>
<
section xml:
id="javaee-agent-compatibility">
<
title>Java EE Policy Agent Compatibility</
title>
<
para>This section concerns OpenAM Java EE Policy Agents
<?
eval ${
javaEEAgentsDocTargetVersion}?>.</
para>
<
section xml:
id="javaee-agent-major-changes">
<
title>Major Changes to Java EE Policy Agent Functionality</
title>
<
para>No major changes affecting compatibility have been made to the OpenAM
Java EE Policy Agents in this release.</
para>
<
section xml:
id="javaee-agent-deprecated">
<
title>Deprecated Functionality</
title>
<
para>No functionality has been deprecated in this release.</
para>
<!-- Keep the wording here for use in a future release: <para>The following functionality is deprecated in OpenAM Java EE Policy Agents <?eval ${javaEEAgentsDocTargetVersion}?>, and is likely to be removed in a future release.</para> <para>Functionality, description...</para> <
section xml:
id="javaee-agent-removed">
<
title>Removed Functionality</
title>
<
para>No functionality has been removed in OpenAM Java EE Policy Agents
<?
eval ${
javaEEAgentsDocTargetVersion}?>.</
para>
<
section xml:
id="javaee-agent-issues">
<
title>Java EE Policy Agents Fixes, Limitations, & Known Issues</
title>
<
para>OpenAM Java EE policy agent issues are tracked at <
link xlink:
show="new" <
section xml:
id="javaee-agent-fixes">
<
para>The following bugs were fixed in release
<?
eval ${
javaEEAgentsDocTargetVersion}?>. For details, see the <
link >OpenAM issue tracker</
link>.</
para>
<
section xml:
id="javaee-agent-limitations">
<
title>Limitations</
title>
<
para>Not all features of OpenAM Java EE policy agents work with IPv6.</
para>
<!-- For OPENAM-1991 TODO: Remove when this is fixed after 3.1.0-Xpress --> <
para>Apache Tomcat can fail to shut down properly when the Java EE policy
agent for Tomcat is deployed. To work around this limitation, add the
following to your Tomcat configuration in the <
literal><Server port="8005"
shutdown="SHUTDOWN"></
literal> section.</
para>
<
literallayout class="monospaced" <
section xml:
id="javaee-agent-known-issues">
<
title>Known Issues</
title>
<
para>The following important known issues remained open at the time
release <?
eval ${
javaEEAgentsDocTargetVersion}?> became available. For
details and information on other issues, see the <
link xlink:
show="new"