JBoss Portal SVN: r12337 - docs/enterprise/trunk/Installation_Guide/en-US.
by portal-commits＠lists.jboss.org
Author: prabhat.jha(a)jboss.com
Date: 2008-12-03 12:01:22 -0500 (Wed, 03 Dec 2008)
New Revision: 12337
Modified:
docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml
docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml
docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml
docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide_CP03.ent
docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml
docs/enterprise/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml
Log:
Changing EAP ref to EPP and some DB stuff.
Modified: docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml 2008-12-03 15:40:41 UTC (rev 12336)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml 2008-12-03 17:01:22 UTC (rev 12337)
@@ -2,17 +2,17 @@
<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
]>
-<bookinfo id="Installation_Guide_JBoss_Enterprise_Application_Platform">
- <title>Installation Guide CP03</title>
- <subtitle>For use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 3</subtitle>
+<bookinfo id="Installation_Guide_JBoss_Enterprise_Portal_Platform">
+ <title>Installation Guide</title>
+ <subtitle>For use with JBoss Enterprise Portal Platform 4.3 </subtitle>
<edition>2.0</edition>
<pubsnumber>4</pubsnumber>
- <productname>JBoss Enterprise Application Platform</productname>
+ <productname>JBoss Enterprise Portal Platform</productname>
<productnumber>4.3</productnumber>
<pubdate>Dec, 2008</pubdate>
<isbn>N/A</isbn>
<abstract><para>This Installation Guide documents relevant information regarding
-the installation of JBoss Enterprise Application Platform</para>
+the installation of JBoss Enterprise Portal Platform</para>
</abstract>
<corpauthor>
<inlinemediaobject>
Modified: docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml 2008-12-03 15:40:41 UTC (rev 12336)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml 2008-12-03 17:01:22 UTC (rev 12337)
@@ -5,39 +5,18 @@
<chapter id="chap-Portal_EAP-Databases">
<title>Databases</title>
<para>
- The following chapter contains examples for how to use the Hypersonic SQL and MySQL databases to store JBoss Portal user information.
+ &EPP; comes bundled with Hypersonic SQL (HSQL) database so that users can get started up and running quickly without having to setup
+ database initially. However, HSQL should not be used in production environment. Removing HSQL is simply a matter of removing
+ <filename>JBOSS_DIST/jboss-as/server/production/deploy/portal-hsql-ds.xml</filename>. The following chapter contains examples for how to use
+ MySQL databases to store JBoss Enterprise Portal user information.
</para>
- <section id="sect-Portal_EAP-Databases-Using_a_Hypersonic_SQL_Database">
- <title>Using a Hypersonic SQL Database</title>
- <para>
- JBoss EAP contains an embedded <ulink url="http://hsqldb.org/">Hypersonic SQL</ulink> database instance. After starting JBoss EAP and deploying JBoss portal for the first time, the Hypersonic SQL database is created in the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/data/</filename> directory. This directory will not exist until after starting JBoss EAP and deploying JBoss Portal. The Hypersonic SQL database is used by default, but is only recommended for developer use.
- </para>
- <para>
- To use the Hypersonic SQL database, change into the <filename>setup/</filename> subdirectory where JBoss Portal was extracted to. Copy the <filename>portal-hsqldb-ds.xml</filename> file into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory. Alternatively, copy and save the following example as <filename>portal-hsqldb-ds.xml</filename> into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory:
- </para>
- <para>
-<screen>
-<?xml version="1.0" encoding="UTF-8"?>
-<datasources>
- <local-tx-datasource>
- <jndi-name>PortalDS</jndi-name>
- <connection-url>jdbc:hsqldb:${jboss.server.data.dir}$
- {/}portal${/}hypersonic${/}database</connection-url>
- <driver-class>org.hsqldb.jdbcDriver</driver-class>
- <user-name>sa</user-name>
- <password><![CDATA[]]></password>
- </local-tx-datasource>
-</datasources>
-</screen>
- </para>
- </section>
-
+
<section id="sect-Portal_EAP-Databases-Using_a_MySQL_Database">
<title>Using a MySQL Database</title>
<formalpara id="form-Portal_EAP-Using_a_MySQL_Database-Installing_the_MySQL_RDBMS_JDBC_connector">
<title>Installing the MySQL RDBMS JDBC connector</title>
<para>
- The RDBMS JDBC MySQL connector is required for JBoss Portal to use a MySQL database:
+ The RDBMS JDBC MySQL connector is required for JBoss Portal to use a MySQL database:
</para>
</formalpara>
<orderedlist>
Modified: docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml 2008-12-03 15:40:41 UTC (rev 12336)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml 2008-12-03 17:01:22 UTC (rev 12337)
@@ -7,7 +7,7 @@
<section id="Getting_Started-Pre_Requisites">
<title>Pre-Requisites</title>
<para>
- You must have adequate disk space<!--TODO how much --> to install JDK and &JBEAP; while also allowing enough space for your applications. Before installing &JBEAP; you must have a working installation of Java. Since JBoss is 100% pure Java you can have it working on any Operating System / Platform that supports Java. However, there are a few Operating System-specific issues that you should be aware of. Refer to <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossOperatingSystemSpecificIssues"></ulink> for more information.
+ You must have adequate disk space<!--TODO how much --> to install JDK and &JBEPP; while also allowing enough space for your applications. Before installing &JBEPP; you must have a working installation of Java. Since JBoss is 100% pure Java you can have it working on any Operating System / Platform that supports Java. However, there are a few Operating System-specific issues that you should be aware of. Refer to <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossOperatingSystemSpecificIssues"></ulink> for more information.
</para>
<section id="Pre_Requisites-Hardware_and_Operating_System_Requirements">
<title>Hardware and Operating System Requirements</title>
Modified: docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide_CP03.ent
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide_CP03.ent 2008-12-03 15:40:41 UTC (rev 12336)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide_CP03.ent 2008-12-03 17:01:22 UTC (rev 12337)
@@ -1,4 +1,6 @@
<!ENTITY JBEAP "JBoss Enterprise Application Platform">
+<!ENTITY JBEPP "JBoss Enterprise Portal Platform">
+<!ENTITY JBEPPVERS "4.3">
<!ENTITY JBEAPVERS "4.3">
<!ENTITY HOLDER "Red Hat, Inc">
<!ENTITY YEAR "2008">
Modified: docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml 2008-12-03 15:40:41 UTC (rev 12336)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml 2008-12-03 17:01:22 UTC (rev 12337)
@@ -4,17 +4,19 @@
<chapter id="Introduction">
<title>Introduction</title>
- <para>
- &JBEAP; is the open source implementation of the Java EE suite of services. It comprises a set of offerings for enterprise customers who are looking for preconfigured profiles of JBoss Enterprise Middleware components that have been tested and certified together to provide an integrated experience. Its easy-to-use server architecture and high flexibility makes JBoss the ideal choice for users just starting out with J2EE, as well as senior architects looking for a customizable middleware platform.
+ <para>
+ &JBEPP; is the open source implementation of the Java EE suite of services and Portal services running atop &JBEAP;. It comprises a set of offerings
+ for enterprise customers who are looking for preconfigured profiles of JBoss Enterprise Middleware components that have been tested and certified together
+ to provide an integrated experience. Its easy-to-use server architecture and high flexibility makes JBoss the ideal choice for users just starting out with J2EE, as well as senior architects looking for a customizable middleware platform.
</para>
<para>
- Because it is Java-based, &JBEAP; is cross-platform and easy to install and use on any operating system that supports Java. The readily available source code is a powerful learning tool to debug the server and understand it. It also gives you the flexibility to create customized versions for your personal or business use.
+ Because it is Java-based, &JBEPP; is cross-platform and easy to install and use on any operating system that supports Java. The readily available source code is a powerful learning tool to debug the server and understand it. It also gives you the flexibility to create customized versions for your personal or business use.
</para>
<para>
- Installing &JBEAP; is simple and easy. You can have it installed and running in no time. This guide will teach you to install and uninstall JBoss.<!--: <itemizedlist>
+ Installing &JBEPP; is simple and easy. You can have it installed and running in no time. This guide will teach you to install and uninstall JBoss.<!--: <itemizedlist>
<listitem>
<para>
- How to install &JBEAP;
+ How to install &JBEPP;
</para>
</listitem>
<listitem>
Modified: docs/enterprise/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml 2008-12-03 15:40:41 UTC (rev 12336)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml 2008-12-03 17:01:22 UTC (rev 12337)
@@ -5,7 +5,7 @@
<chapter id="Uninstall_JBoss">
<title>Uninstall JBoss</title>
<para>
- As JBoss Enterprise Application Platform was installed from a zipfile, you may uninstall it by simply deleting the &JBEAP; installed directory.
+ As JBoss Enterprise Application Platform was installed from a zipfile, you may uninstall it by simply deleting the &JBEPP; installed directory.
</para>
</chapter>
17 years, 5 months
- 1
- 0
JBoss Portal SVN: r12336 - docs/enterprise/trunk/Installation_Guide/en-US.
by portal-commits＠lists.jboss.org
Author: prabhat.jha(a)jboss.com
Date: 2008-12-03 10:40:41 -0500 (Wed, 03 Dec 2008)
New Revision: 12336
Modified:
docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml
Log:
testing my commit right
Modified: docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml 2008-12-03 15:37:38 UTC (rev 12335)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml 2008-12-03 15:40:41 UTC (rev 12336)
@@ -5,7 +5,7 @@
<chapter id="Test_your_Installation">
<title>Test your Installation</title>
<para>
- After you have installed the JBoss Enterprise Application Platform, it is wise to perform a simple startup test to validate that there are no major problems with your Java VM/operating system combination. Make sure you have set the <literal>JBOSS_HOME</literal> envirnoment variables as explained in <ulink url="Post_Installation_Configuration"/>. To test your installation, move to <filename>JBOSS_DIST/jboss-as/bin</filename> directory and execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system. Your output should look like the following (accounting for installation directory differences) and contain no error or exception messages:
+ After you have installed the JBoss Enterprise Portal Platform, it is wise to perform a simple startup test to validate that there are no major problems with your Java VM/operating system combination. Make sure you have set the <literal>JBOSS_HOME</literal> envirnoment variables as explained in <ulink url="Post_Installation_Configuration"/>. To test your installation, move to <filename>JBOSS_DIST/jboss-as/bin</filename> directory and execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system. Your output should look like the following (accounting for installation directory differences) and contain no error or exception messages:
</para>
<programlisting>
[vrenish@vinux bin]$ ./run.sh
17 years, 5 months
- 1
- 0
JBoss Portal SVN: r12334 - in modules/authorization/trunk: PAP and 10 other directories.
by portal-commits＠lists.jboss.org
Author: sohil.shah(a)jboss.com
Date: 2008-12-03 02:10:07 -0500 (Wed, 03 Dec 2008)
New Revision: 12334
Added:
modules/authorization/trunk/PAP/src/main/java/org/jboss/security/authz/pap/service/DroolsRuleManager.java
modules/authorization/trunk/PAP/src/main/resources/rules/
modules/authorization/trunk/PAP/src/main/resources/rules/security.drl
modules/authorization/trunk/PAP/src/test/java/org/jboss/security/authz/pap/plugin/TestDroolsRules.java
modules/authorization/trunk/PAP/src/test/java/org/jboss/security/authz/pap/service/TestDroolsRuleManager.java
modules/authorization/trunk/PAP/src/test/resources/rules/
modules/authorization/trunk/PAP/src/test/resources/rules/add-security.drl
modules/authorization/trunk/PAP/src/test/resources/rules/test-security.drl
Removed:
modules/authorization/trunk/PEP/multitier-policy.xml
modules/authorization/trunk/PEP/simple-policy.xml
Modified:
modules/authorization/trunk/.classpath
modules/authorization/trunk/PAP/pom.xml
modules/authorization/trunk/PAP/src/main/java/org/jboss/security/authz/pap/plugin/DroolsFunction.java
modules/authorization/trunk/PAP/src/main/java/org/jboss/security/authz/pap/plugin/EnterprisePolicyFinder.java
modules/authorization/trunk/PEP/pom.xml
modules/authorization/trunk/common/src/main/java/org/jboss/security/authz/model/DroolsRuleExpression.java
modules/authorization/trunk/common/src/main/java/org/jboss/security/authz/model/Subject.java
modules/authorization/trunk/pom.xml
Log:
code backup
Modified: modules/authorization/trunk/.classpath
===================================================================
--- modules/authorization/trunk/.classpath 2008-12-03 06:35:00 UTC (rev 12333)
+++ modules/authorization/trunk/.classpath 2008-12-03 07:10:07 UTC (rev 12334)
@@ -42,4 +42,6 @@
<classpathentry kind="var" path="M2_REPO/org/jboss/security/jboss-sunxacml/2.0.3-SNAPSHOT/jboss-sunxacml-2.0.3-SNAPSHOT.jar" sourcepath="M2_REPO/org/jboss/security/jboss-sunxacml/2.0.3-SNAPSHOT/jboss-sunxacml-2.0.3-SNAPSHOT-sources.jar"/>
<classpathentry kind="var" path="M2_REPO/org/jboss/security/jboss-xacml/2.0.3-SNAPSHOT/jboss-xacml-2.0.3-SNAPSHOT.jar" sourcepath="M2_REPO/org/jboss/security/jboss-xacml/2.0.3-SNAPSHOT/jboss-xacml-2.0.3-SNAPSHOT-sources.jar"/>
<classpathentry kind="var" path="M2_REPO/apache-log4j/log4j/1.2.14/log4j-1.2.14.jar"/>
+ <classpathentry kind="var" path="M2_REPO/org/drools/drools-core/4.0.7/drools-core-4.0.7.jar"/>
+ <classpathentry kind="var" path="M2_REPO/org/drools/drools-compiler/4.0.7/drools-compiler-4.0.7.jar"/>
</classpath>
Modified: modules/authorization/trunk/PAP/pom.xml
===================================================================
--- modules/authorization/trunk/PAP/pom.xml 2008-12-03 06:35:00 UTC (rev 12333)
+++ modules/authorization/trunk/PAP/pom.xml 2008-12-03 07:10:07 UTC (rev 12334)
@@ -44,6 +44,17 @@
<artifactId>jaxb-xjc</artifactId>
</dependency>
+ <!-- Drools -->
+ <dependency>
+ <groupId>org.drools</groupId>
+ <artifactId>drools-core</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>org.drools</groupId>
+ <artifactId>drools-compiler</artifactId>
+ </dependency>
+
+
<!-- junit -->
<dependency>
<groupId>junit</groupId>
@@ -58,8 +69,8 @@
<artifactId>maven-surefire-plugin</artifactId>
<version>2.3.1</version>
<configuration>
- <includes>
- <include>**/TestDroolsFunction.java</include>
+ <includes>
+ <include>**/TestDroolsRuleManager.java</include>
</includes>
</configuration>
</plugin>
Modified: modules/authorization/trunk/PAP/src/main/java/org/jboss/security/authz/pap/plugin/DroolsFunction.java
===================================================================
--- modules/authorization/trunk/PAP/src/main/java/org/jboss/security/authz/pap/plugin/DroolsFunction.java 2008-12-03 06:35:00 UTC (rev 12333)
+++ modules/authorization/trunk/PAP/src/main/java/org/jboss/security/authz/pap/plugin/DroolsFunction.java 2008-12-03 07:10:07 UTC (rev 12334)
@@ -22,14 +22,27 @@
******************************************************************************/
package org.jboss.security.authz.pap.plugin;
+import java.io.InputStreamReader;
+import java.io.Reader;
import java.util.List;
+import java.util.ArrayList;
+import org.drools.RuleBase;
+import org.drools.RuleBaseFactory;
+import org.drools.WorkingMemory;
+import org.drools.rule.Package;
+import org.drools.compiler.PackageBuilder;
+
import org.jboss.security.xacml.sunxacml.EvaluationCtx;
import org.jboss.security.xacml.sunxacml.cond.EvaluationResult;
import org.jboss.security.xacml.sunxacml.cond.FunctionBase;
+import org.jboss.security.xacml.sunxacml.ctx.Status;
import org.jboss.security.xacml.sunxacml.attr.BooleanAttribute;
/**
+ * A custom XACML Function which is used to evaluate an XACML Condition based on the Evaluation Results of a specified Business Rule based on the
+ * Drools/JBoss Rules product
+ *
* @author <a href="mailto:sshah@redhat.com">Sohil Shah</a>
*
*/
@@ -37,6 +50,8 @@
{
public static final String NAME = FUNCTION_NS + "drools:rule";
+ private RuleBase rules = null;
+
/**
*
* @param functionName
@@ -51,10 +66,19 @@
public DroolsFunction()
{
super(NAME,
- 0, //FunctionId
- BooleanAttribute.identifier, //returnType
- false //returns a Bag of values
- );
+ 0, //FunctionId
+ BooleanAttribute.identifier, //returnType
+ false //returns a Bag of values
+ );
+
+ try
+ {
+ this.rules = this.readStaticRules();
+ }
+ catch(Exception e)
+ {
+ throw new RuntimeException(e);
+ }
}
@@ -83,10 +107,64 @@
*
*/
public EvaluationResult evaluate(List inputs, EvaluationCtx context)
- {
- /**
- * TODO: start a Drools context and evaluate the specified Rule against the data presented in the EvaluationContext
- */
- return EvaluationResult.getTrueInstance();
+ {
+ EvaluationResult result = null;
+ try
+ {
+ //Mock Code
+ WorkingMemory workingMemory = this.rules.newStatefulSession();
+
+ //Insert Security related Facts into the Rule Engine
+
+ workingMemory.fireAllRules();
+
+
+ /**
+ * TODO: start a Drools context and evaluate the specified Rule against the data presented in the EvaluationContext
+ */
+ result = EvaluationResult.getTrueInstance();
+ }
+ catch(Exception e)
+ {
+ List code = new ArrayList();
+ code.add(Status.STATUS_PROCESSING_ERROR);
+ Status status = new Status(code, e.toString()+": "+e.getMessage());
+ result = new EvaluationResult(status);
+ }
+ return result;
+ }
+ //--------------------------------------------------------------------------------------------------------------------------------------------------------------
+ /**
+ * Used when using Rule Deployment in a static manner from the classpath
+ *
+ * With this approach, the Policy Condition Rules are supplied during server startup. Rule Modifications require a server re-start
+ */
+ private RuleBase readStaticRules() throws Exception
+ {
+ //read in the source
+ Reader source = new InputStreamReader(this.getClass().getResourceAsStream("/rules/security.drl"));
+
+ //optionally read in the DSL (if you are using it).
+ //Reader dsl = new InputStreamReader( DroolsTest.class.getResourceAsStream( "/mylang.dsl" ) );
+
+ //Use package builder to build up a rule package.
+ //An alternative lower level class called "DrlParser" can also be used...
+
+ PackageBuilder builder = new PackageBuilder();
+
+ //this wil parse and compile in one step
+ //NOTE: There are 2 methods here, the one argument one is for normal DRL.
+ builder.addPackageFromDrl(source);
+
+ //Use the following instead of above if you are using a DSL:
+ //builder.addPackageFromDrl( source, dsl );
+
+ //get the compiled package (which is serializable)
+ Package pkg = builder.getPackage();
+
+ //add the package to a rulebase (deploy the rule package).
+ RuleBase ruleBase = RuleBaseFactory.newRuleBase();
+ ruleBase.addPackage(pkg);
+ return ruleBase;
}
}
Modified: modules/authorization/trunk/PAP/src/main/java/org/jboss/security/authz/pap/plugin/EnterprisePolicyFinder.java
===================================================================
--- modules/authorization/trunk/PAP/src/main/java/org/jboss/security/authz/pap/plugin/EnterprisePolicyFinder.java 2008-12-03 06:35:00 UTC (rev 12333)
+++ modules/authorization/trunk/PAP/src/main/java/org/jboss/security/authz/pap/plugin/EnterprisePolicyFinder.java 2008-12-03 07:10:07 UTC (rev 12334)
@@ -25,11 +25,19 @@
import org.jboss.security.xacml.sunxacml.finder.PolicyFinderModule;
/**
+ * A production ready Enterprise Policy Finder that would be used by the Policy Server/PDP component.
*
+ * It is designed for being production ready from a performance/scalability/clustering standpoint
+ *
+ * This particular version will provide performance enhancement by the use of a clustered cache based on JBoss Cache
+ * The actual storage of the policies will be done within a relational database
+ *
+ * This also allows for runtime modification of Security Policies without requiring any restart/refresh of the Applications
+ *
* @author <a href="mailto:sshah@redhat.com">Sohil Shah</a>
*
*/
public abstract class EnterprisePolicyFinder extends PolicyFinderModule
{
-}
+}
\ No newline at end of file
Added: modules/authorization/trunk/PAP/src/main/java/org/jboss/security/authz/pap/service/DroolsRuleManager.java
===================================================================
--- modules/authorization/trunk/PAP/src/main/java/org/jboss/security/authz/pap/service/DroolsRuleManager.java (rev 0)
+++ modules/authorization/trunk/PAP/src/main/java/org/jboss/security/authz/pap/service/DroolsRuleManager.java 2008-12-03 07:10:07 UTC (rev 12334)
@@ -0,0 +1,178 @@
+/******************************************************************************
+ * JBoss, a division of Red Hat *
+ * Copyright 2006, Red Hat Middleware, LLC, and individual *
+ * contributors as indicated by the @authors tag. See the *
+ * copyright.txt in the distribution for a full listing of *
+ * individual contributors. *
+ * *
+ * This is free software; you can redistribute it and/or modify it *
+ * under the terms of the GNU Lesser General Public License as *
+ * published by the Free Software Foundation; either version 2.1 of *
+ * the License, or (at your option) any later version. *
+ * *
+ * This software is distributed in the hope that it will be useful, *
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of *
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU *
+ * Lesser General Public License for more details. *
+ * *
+ * You should have received a copy of the GNU Lesser General Public *
+ * License along with this software; if not, write to the Free *
+ * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA *
+ * 02110-1301 USA, or see the FSF site: http://www.fsf.org. *
+ ******************************************************************************/
+package org.jboss.security.authz.pap.service;
+
+import java.io.InputStreamReader;
+import java.io.Reader;
+import java.io.ByteArrayInputStream;
+import java.util.Map;
+import java.util.HashMap;
+
+import org.drools.RuleBase;
+import org.drools.RuleBaseFactory;
+import org.drools.compiler.PackageBuilder;
+
+import org.jboss.security.authz.model.DroolsRuleExpression;
+
+/**
+ * This service provides management for Drools based authorization Rules/Logic used by the Drools Function extension of the XACML Engine
+ *
+ * TODO: Add Database Persistence to the State of this Manager
+ *
+ * @author <a href="mailto:sshah@redhat.com">Sohil Shah</a>
+ *
+ */
+public class DroolsRuleManager
+{
+ private static String rulePkg =
+ "package security\n"+
+ "import org.jboss.security.authz.model.*;\n"+
+ "import org.jboss.security.xacml.interfaces.XACMLConstants;\n";
+
+ private RuleBase activeRuleBase = null;
+ private Map<String, String> drls = null;
+
+ public DroolsRuleManager()
+ {
+ }
+
+ public void start()
+ {
+ try
+ {
+ this.drls = new HashMap<String, String>();
+ this.reloadActiveRuleBase();
+ }
+ catch(Exception e)
+ {
+ throw new RuntimeException(e);
+ }
+ }
+
+ public void stop()
+ {
+ this.activeRuleBase = null;
+ this.drls = null;
+ }
+ //---------------------------------------------------------------------------------------------------------------------------------------------------------
+ public RuleBase getActiveRuleBase()
+ {
+ return this.activeRuleBase;
+ }
+
+ public void addRule(DroolsRuleExpression rule) throws Exception
+ {
+ if(rule.getRuleReference() == null || rule.getRuleReference().trim().length() == 0)
+ {
+ throw new IllegalArgumentException("Rule Reference is missing");
+ }
+ if(rule.getWhen() == null || rule.getWhen().trim().length() == 0)
+ {
+ throw new IllegalArgumentException("LHS value is missing");
+ }
+
+
+ this.drls.put(rule.getRuleReference(), rule.getWhen());
+ this.reloadActiveRuleBase();
+ }
+
+ public DroolsRuleExpression readRule(String ruleReference) throws Exception
+ {
+ if(ruleReference == null || ruleReference.trim().length() == 0)
+ {
+ throw new IllegalArgumentException("Rule Reference is missing");
+ }
+
+ DroolsRuleExpression rule = null;
+
+ String when = this.drls.get(ruleReference);
+
+ rule = new DroolsRuleExpression();
+ rule.setRuleReference(ruleReference);
+ rule.setWhen(when);
+
+ return rule;
+ }
+
+ public void updateRule(DroolsRuleExpression rule) throws Exception
+ {
+ if(rule.getRuleReference() == null || rule.getRuleReference().trim().length() == 0)
+ {
+ throw new IllegalArgumentException("Rule Reference is missing");
+ }
+ if(rule.getWhen() == null || rule.getWhen().trim().length() == 0)
+ {
+ throw new IllegalArgumentException("LHS value is missing");
+ }
+
+ this.drls.put(rule.getRuleReference(), rule.getWhen());
+ this.reloadActiveRuleBase();
+ }
+
+ public void removeRule(String ruleReference) throws Exception
+ {
+ if(ruleReference == null || ruleReference.trim().length() == 0)
+ {
+ throw new IllegalArgumentException("Rule Reference is missing");
+ }
+
+ this.drls.remove(ruleReference);
+ this.reloadActiveRuleBase();
+ }
+ //-----------------------------------------------------------------------------------------------------------------------------------------------------------
+ private synchronized void reloadActiveRuleBase() throws Exception
+ {
+ StringBuilder buffer = new StringBuilder();
+
+ buffer.append(DroolsRuleManager.rulePkg+"\n");
+
+ for(String drl: this.drls.values())
+ {
+ buffer.append(drl+"\n");
+ }
+
+
+ ByteArrayInputStream bis = new ByteArrayInputStream(buffer.toString().getBytes());
+ try
+ {
+ Reader source = new InputStreamReader(bis);
+
+ PackageBuilder packageBuilder = new PackageBuilder();
+ packageBuilder.addPackageFromDrl(source);
+
+ if(this.activeRuleBase == null)
+ {
+ this.activeRuleBase = RuleBaseFactory.newRuleBase();
+ }
+
+ //Perform the reloading of the RuleBase with the updated Rules
+ this.activeRuleBase.lock();
+ this.activeRuleBase.addPackage(packageBuilder.getPackage());
+ this.activeRuleBase.unlock();
+ }
+ finally
+ {
+ bis.close();
+ }
+ }
+}
Added: modules/authorization/trunk/PAP/src/main/resources/rules/security.drl
===================================================================
--- modules/authorization/trunk/PAP/src/main/resources/rules/security.drl (rev 0)
+++ modules/authorization/trunk/PAP/src/main/resources/rules/security.drl 2008-12-03 07:10:07 UTC (rev 12334)
@@ -0,0 +1,8 @@
+package org.jboss.security.authz.pap.plugin
+
+
+rule "WriteRule"
+ when
+ then
+ System.out.println("WriteRule successfully invoked........");
+end
\ No newline at end of file
Added: modules/authorization/trunk/PAP/src/test/java/org/jboss/security/authz/pap/plugin/TestDroolsRules.java
===================================================================
--- modules/authorization/trunk/PAP/src/test/java/org/jboss/security/authz/pap/plugin/TestDroolsRules.java (rev 0)
+++ modules/authorization/trunk/PAP/src/test/java/org/jboss/security/authz/pap/plugin/TestDroolsRules.java 2008-12-03 07:10:07 UTC (rev 12334)
@@ -0,0 +1,134 @@
+/******************************************************************************
+ * JBoss, a division of Red Hat *
+ * Copyright 2006, Red Hat Middleware, LLC, and individual *
+ * contributors as indicated by the @authors tag. See the *
+ * copyright.txt in the distribution for a full listing of *
+ * individual contributors. *
+ * *
+ * This is free software; you can redistribute it and/or modify it *
+ * under the terms of the GNU Lesser General Public License as *
+ * published by the Free Software Foundation; either version 2.1 of *
+ * the License, or (at your option) any later version. *
+ * *
+ * This software is distributed in the hope that it will be useful, *
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of *
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU *
+ * Lesser General Public License for more details. *
+ * *
+ * You should have received a copy of the GNU Lesser General Public *
+ * License along with this software; if not, write to the Free *
+ * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA *
+ * 02110-1301 USA, or see the FSF site: http://www.fsf.org. *
+ ******************************************************************************/
+package org.jboss.security.authz.pap.plugin;
+
+
+import junit.framework.TestCase;
+
+import org.drools.WorkingMemory;
+import org.drools.StatefulSession;
+
+import org.jboss.security.xacml.interfaces.XACMLConstants;
+import org.jboss.security.xacml.interfaces.XMLSchemaConstants;
+import org.jboss.security.authz.model.*;
+import org.jboss.security.authz.pap.service.DroolsRuleManager;
+
+/**
+ * @author <a href="mailto:sshah@redhat.com">Sohil Shah</a>
+ *
+ */
+public class TestDroolsRules extends TestCase
+{
+ private static final String rule2 =
+ "rule \"Rule2\"\n"+
+ "when\n"+
+ "$subject: Subject()\n"+
+ "String(toString == \"Rule2\")\n"+
+ "Subject(category == XACMLConstants.ATTRIBUTEID_ACCESS_SUBJECT)\n"+
+ "Attribute(uri == XACMLConstants.ATTRIBUTEID_ROLE && value == \"developer\") from $subject.attributes\n"+
+ "then\n"+
+ "System.out.println(\"Rule2 successfully fired\");\n"+
+ "end\n";
+
+ private static final String rule1 =
+ "rule \"Rule1\"\n"+
+ "when\n"+
+ "$subject: Subject()\n"+
+ "String(toString == \"Rule1\")\n"+
+ "Subject(category == XACMLConstants.ATTRIBUTEID_ACCESS_SUBJECT)\n"+
+ "Attribute(uri == XACMLConstants.ATTRIBUTEID_ROLE && value == \"developer\") from $subject.attributes\n"+
+ "then\n"+
+ "System.out.println(\"Rule1 successfully fired\");\n"+
+ "end\n";
+
+ private DroolsRuleManager ruleManager = null;
+
+
+ @Override
+ protected void setUp() throws Exception
+ {
+ this.ruleManager = new DroolsRuleManager();
+ this.ruleManager.start();
+ }
+
+ @Override
+ protected void tearDown() throws Exception
+ {
+ this.ruleManager = null;
+ }
+ //------------------------------------------------------------------------------------------------------------------------------------------------------------
+ public void testAddRule() throws Exception
+ {
+ DroolsRuleExpression expression = new DroolsRuleExpression();
+ expression.setRuleReference("Rule2");
+ expression.setWhen(TestDroolsRules.rule2);
+ this.ruleManager.addRule(expression);
+
+ WorkingMemory workingMemory = ruleManager.getActiveRuleBase().newStatefulSession();
+ workingMemory.insert("Rule2");
+ workingMemory.insert(this.getSubject());
+
+ //Fire
+ System.out.println("Firing Rule2........");
+ workingMemory.fireAllRules();
+ ((StatefulSession)workingMemory).dispose();
+
+ expression.setRuleReference("Rule1");
+ expression.setWhen(TestDroolsRules.rule1);
+ this.ruleManager.addRule(expression);
+
+ workingMemory = ruleManager.getActiveRuleBase().newStatefulSession();
+ workingMemory.insert("Rule1");
+ workingMemory.insert(this.getSubject());
+
+ //Fire
+ System.out.println("Firing Rule1........");
+ workingMemory.fireAllRules();
+ ((StatefulSession)workingMemory).dispose();
+
+ workingMemory = ruleManager.getActiveRuleBase().newStatefulSession();
+ workingMemory.insert("Rule2");
+ workingMemory.insert(this.getSubject());
+
+ //Fire
+ System.out.println("Firing Rule2........");
+ workingMemory.fireAllRules();
+ ((StatefulSession)workingMemory).dispose();
+ }
+ //-----------------------------------------------------------------------------------------------------------------------------------------------------------
+ private Subject getSubject()
+ {
+ Subject subject = new Subject();
+
+ subject.setCategory(XACMLConstants.ATTRIBUTEID_ACCESS_SUBJECT);
+
+ //Create a Role Attribute
+ Attribute attribute = new Attribute();
+ attribute.setUri(XACMLConstants.ATTRIBUTEID_ROLE);
+ attribute.setDatatType(XMLSchemaConstants.DATATYPE_STRING);
+ attribute.setValue("developer");
+ subject.addAttribute(attribute);
+
+ return subject;
+ }
+}
Added: modules/authorization/trunk/PAP/src/test/java/org/jboss/security/authz/pap/service/TestDroolsRuleManager.java
===================================================================
--- modules/authorization/trunk/PAP/src/test/java/org/jboss/security/authz/pap/service/TestDroolsRuleManager.java (rev 0)
+++ modules/authorization/trunk/PAP/src/test/java/org/jboss/security/authz/pap/service/TestDroolsRuleManager.java 2008-12-03 07:10:07 UTC (rev 12334)
@@ -0,0 +1,134 @@
+/******************************************************************************
+ * JBoss, a division of Red Hat *
+ * Copyright 2006, Red Hat Middleware, LLC, and individual *
+ * contributors as indicated by the @authors tag. See the *
+ * copyright.txt in the distribution for a full listing of *
+ * individual contributors. *
+ * *
+ * This is free software; you can redistribute it and/or modify it *
+ * under the terms of the GNU Lesser General Public License as *
+ * published by the Free Software Foundation; either version 2.1 of *
+ * the License, or (at your option) any later version. *
+ * *
+ * This software is distributed in the hope that it will be useful, *
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of *
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU *
+ * Lesser General Public License for more details. *
+ * *
+ * You should have received a copy of the GNU Lesser General Public *
+ * License along with this software; if not, write to the Free *
+ * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA *
+ * 02110-1301 USA, or see the FSF site: http://www.fsf.org. *
+ ******************************************************************************/
+package org.jboss.security.authz.pap.service;
+
+
+import junit.framework.TestCase;
+
+import org.drools.WorkingMemory;
+import org.drools.StatefulSession;
+
+import org.jboss.security.xacml.interfaces.XACMLConstants;
+import org.jboss.security.xacml.interfaces.XMLSchemaConstants;
+import org.jboss.security.authz.model.*;
+import org.jboss.security.authz.pap.service.DroolsRuleManager;
+
+/**
+ * @author <a href="mailto:sshah@redhat.com">Sohil Shah</a>
+ *
+ */
+public class TestDroolsRuleManager extends TestCase
+{
+ private static final String rule2 =
+ "rule \"Rule2\"\n"+
+ "when\n"+
+ "$subject: Subject()\n"+
+ "String(toString == \"Rule2\")\n"+
+ "Subject(category == XACMLConstants.ATTRIBUTEID_ACCESS_SUBJECT)\n"+
+ "Attribute(uri == XACMLConstants.ATTRIBUTEID_ROLE && value == \"developer\") from $subject.attributes\n"+
+ "then\n"+
+ "System.out.println(\"Rule2 successfully fired\");\n"+
+ "end\n";
+
+ private static final String rule1 =
+ "rule \"Rule1\"\n"+
+ "when\n"+
+ "$subject: Subject()\n"+
+ "String(toString == \"Rule1\")\n"+
+ "Subject(category == XACMLConstants.ATTRIBUTEID_ACCESS_SUBJECT)\n"+
+ "Attribute(uri == XACMLConstants.ATTRIBUTEID_ROLE && value == \"developer\") from $subject.attributes\n"+
+ "then\n"+
+ "System.out.println(\"Rule1 successfully fired\");\n"+
+ "end\n";
+
+ private DroolsRuleManager ruleManager = null;
+
+
+ @Override
+ protected void setUp() throws Exception
+ {
+ this.ruleManager = new DroolsRuleManager();
+ this.ruleManager.start();
+ }
+
+ @Override
+ protected void tearDown() throws Exception
+ {
+ this.ruleManager = null;
+ }
+ //------------------------------------------------------------------------------------------------------------------------------------------------------------
+ public void testAddRule() throws Exception
+ {
+ DroolsRuleExpression expression = new DroolsRuleExpression();
+ expression.setRuleReference("Rule2");
+ expression.setWhen(TestDroolsRuleManager.rule2);
+ this.ruleManager.addRule(expression);
+
+ WorkingMemory workingMemory = ruleManager.getActiveRuleBase().newStatefulSession();
+ workingMemory.insert("Rule2");
+ workingMemory.insert(this.getSubject());
+
+ //Fire
+ System.out.println("Firing Rule2........");
+ workingMemory.fireAllRules();
+ ((StatefulSession)workingMemory).dispose();
+
+ expression.setRuleReference("Rule1");
+ expression.setWhen(TestDroolsRuleManager.rule1);
+ this.ruleManager.addRule(expression);
+
+ workingMemory = ruleManager.getActiveRuleBase().newStatefulSession();
+ workingMemory.insert("Rule1");
+ workingMemory.insert(this.getSubject());
+
+ //Fire
+ System.out.println("Firing Rule1........");
+ workingMemory.fireAllRules();
+ ((StatefulSession)workingMemory).dispose();
+
+ workingMemory = ruleManager.getActiveRuleBase().newStatefulSession();
+ workingMemory.insert("Rule2");
+ workingMemory.insert(this.getSubject());
+
+ //Fire
+ System.out.println("Firing Rule2........");
+ workingMemory.fireAllRules();
+ ((StatefulSession)workingMemory).dispose();
+ }
+ //-----------------------------------------------------------------------------------------------------------------------------------------------------------
+ private Subject getSubject()
+ {
+ Subject subject = new Subject();
+
+ subject.setCategory(XACMLConstants.ATTRIBUTEID_ACCESS_SUBJECT);
+
+ //Create a Role Attribute
+ Attribute attribute = new Attribute();
+ attribute.setUri(XACMLConstants.ATTRIBUTEID_ROLE);
+ attribute.setDatatType(XMLSchemaConstants.DATATYPE_STRING);
+ attribute.setValue("developer");
+ subject.addAttribute(attribute);
+
+ return subject;
+ }
+}
Added: modules/authorization/trunk/PAP/src/test/resources/rules/add-security.drl
===================================================================
--- modules/authorization/trunk/PAP/src/test/resources/rules/add-security.drl (rev 0)
+++ modules/authorization/trunk/PAP/src/test/resources/rules/add-security.drl 2008-12-03 07:10:07 UTC (rev 12334)
@@ -0,0 +1,26 @@
+package test.security
+
+import java.lang.*;
+import org.jboss.security.authz.model.*;
+import org.jboss.security.xacml.interfaces.XACMLConstants;
+
+
+rule "Rule1"
+ when
+ $subject: Subject()
+ String(toString == "Rule1")
+ Subject(category == XACMLConstants.ATTRIBUTEID_ACCESS_SUBJECT)
+ Attribute(uri == XACMLConstants.ATTRIBUTEID_ROLE && value == "developer") from $subject.attributes
+ then
+ System.out.println("Rule1 (Updated)....");
+end
+
+rule "Rule2"
+ when
+ $subject: Subject()
+ String(toString == "Rule2")
+ Subject(category == XACMLConstants.ATTRIBUTEID_ACCESS_SUBJECT)
+ Attribute(uri == XACMLConstants.ATTRIBUTEID_ROLE && value == "developer") from $subject.attributes
+ then
+ System.out.println("Rule2....");
+end
\ No newline at end of file
Added: modules/authorization/trunk/PAP/src/test/resources/rules/test-security.drl
===================================================================
--- modules/authorization/trunk/PAP/src/test/resources/rules/test-security.drl (rev 0)
+++ modules/authorization/trunk/PAP/src/test/resources/rules/test-security.drl 2008-12-03 07:10:07 UTC (rev 12334)
@@ -0,0 +1,16 @@
+package test.security
+
+import java.lang.*;
+import org.jboss.security.authz.model.*;
+import org.jboss.security.xacml.interfaces.XACMLConstants;
+
+
+rule "Rule1"
+ when
+ $subject: Subject()
+ String(toString == "Rule1")
+ Subject(category == XACMLConstants.ATTRIBUTEID_ACCESS_SUBJECT)
+ Attribute(uri == XACMLConstants.ATTRIBUTEID_ROLE && value == "developer") from $subject.attributes
+ then
+ System.out.println("Rule1....");
+end
\ No newline at end of file
Deleted: modules/authorization/trunk/PEP/multitier-policy.xml
===================================================================
--- modules/authorization/trunk/PEP/multitier-policy.xml 2008-12-03 06:35:00 UTC (rev 12333)
+++ modules/authorization/trunk/PEP/multitier-policy.xml 2008-12-03 07:10:07 UTC (rev 12334)
@@ -1,41 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
-<Policy xmlns="urn:oasis:names:tc:xacml:2.0:policy:schema:os" RuleCombiningAlgId="rule-combining-alg:nopermit-means-denied" Version="2.0" PolicyId="MultiTierPolicy">
- <Target>
- <Resources>
- <Resource>
- <ResourceMatch MatchId="urn:oasis:names:tc:xacml:1.0:function:anyURI-equal">
- <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#anyURI">http://www.redhat.com/protected/index.html</AttributeValue>
- <ResourceAttributeDesignator MustBePresent="false" DataType="http://www.w3.org/2001/XMLSchema#anyURI" AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id"/>
- </ResourceMatch>
- </Resource>
- <Resource>
- <ResourceMatch MatchId="urn:oasis:names:tc:xacml:1.0:function:anyURI-equal">
- <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#anyURI">org.jboss.cms.CMSService</AttributeValue>
- <ResourceAttributeDesignator MustBePresent="false" DataType="http://www.w3.org/2001/XMLSchema#anyURI" AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id"/>
- </ResourceMatch>
- <ResourceMatch MatchId="urn:oasis:names:tc:xacml:1.0:function:anyURI-equal">
- <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#anyURI">http://www.redhat.com/protected/index.html</AttributeValue>
- <ResourceAttributeDesignator MustBePresent="false" DataType="http://www.w3.org/2001/XMLSchema#anyURI" AttributeId="urn:oasis:names:tc:xacml:2.0:custom:attribute:param0"/>
- </ResourceMatch>
- </Resource>
- </Resources>
- </Target>
- <Rule Effect="Permit" RuleId="WriteRule">
- <Target>
- <Actions>
- <Action>
- <ActionMatch MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal">
- <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">write</AttributeValue>
- <ActionAttributeDesignator MustBePresent="false" DataType="http://www.w3.org/2001/XMLSchema#string" AttributeId="urn:oasis:names:tc:xacml:1.0:action:action-id"/>
- </ActionMatch>
- </Action>
- </Actions>
- </Target>
- <Condition>
- <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-is-in">
- <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">developer</AttributeValue>
- <SubjectAttributeDesignator MustBePresent="false" DataType="http://www.w3.org/2001/XMLSchema#string" AttributeId="urn:oasis:names:tc:xacml:2.0:subject:role"/>
- </Apply>
- </Condition>
- </Rule>
-</Policy>
Modified: modules/authorization/trunk/PEP/pom.xml
===================================================================
--- modules/authorization/trunk/PEP/pom.xml 2008-12-03 06:35:00 UTC (rev 12333)
+++ modules/authorization/trunk/PEP/pom.xml 2008-12-03 07:10:07 UTC (rev 12334)
@@ -58,11 +58,7 @@
<artifactId>maven-surefire-plugin</artifactId>
<version>2.3.1</version>
<configuration>
- <includes>
- <include>**/TestPDP.java</include>
- <!--
- <include>**/TestPolicyBuilder.java</include>
- -->
+ <includes>
</includes>
</configuration>
</plugin>
Deleted: modules/authorization/trunk/PEP/simple-policy.xml
===================================================================
--- modules/authorization/trunk/PEP/simple-policy.xml 2008-12-03 06:35:00 UTC (rev 12333)
+++ modules/authorization/trunk/PEP/simple-policy.xml 2008-12-03 07:10:07 UTC (rev 12334)
@@ -1,31 +0,0 @@
-<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
-<Policy xmlns="urn:oasis:names:tc:xacml:2.0:policy:schema:os" RuleCombiningAlgId="rule-combining-alg:nopermit-means-denied" Version="2.0" PolicyId="SimplePolicy">
- <Target>
- <Resources>
- <Resource>
- <ResourceMatch MatchId="urn:oasis:names:tc:xacml:1.0:function:anyURI-equal">
- <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#anyURI">http://www.redhat.com/protected/index.html</AttributeValue>
- <ResourceAttributeDesignator MustBePresent="false" DataType="http://www.w3.org/2001/XMLSchema#anyURI" AttributeId="urn:oasis:names:tc:xacml:1.0:resource:resource-id"/>
- </ResourceMatch>
- </Resource>
- </Resources>
- </Target>
- <Rule Effect="Permit" RuleId="WriteRule">
- <Target>
- <Actions>
- <Action>
- <ActionMatch MatchId="urn:oasis:names:tc:xacml:1.0:function:string-equal">
- <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">write</AttributeValue>
- <ActionAttributeDesignator MustBePresent="false" DataType="http://www.w3.org/2001/XMLSchema#string" AttributeId="urn:oasis:names:tc:xacml:1.0:action:action-id"/>
- </ActionMatch>
- </Action>
- </Actions>
- </Target>
- <Condition>
- <Apply FunctionId="urn:oasis:names:tc:xacml:1.0:function:string-is-in">
- <AttributeValue DataType="http://www.w3.org/2001/XMLSchema#string">developer</AttributeValue>
- <SubjectAttributeDesignator MustBePresent="false" DataType="http://www.w3.org/2001/XMLSchema#string" AttributeId="urn:oasis:names:tc:xacml:2.0:subject:role"/>
- </Apply>
- </Condition>
- </Rule>
-</Policy>
Modified: modules/authorization/trunk/common/src/main/java/org/jboss/security/authz/model/DroolsRuleExpression.java
===================================================================
--- modules/authorization/trunk/common/src/main/java/org/jboss/security/authz/model/DroolsRuleExpression.java 2008-12-03 06:35:00 UTC (rev 12333)
+++ modules/authorization/trunk/common/src/main/java/org/jboss/security/authz/model/DroolsRuleExpression.java 2008-12-03 07:10:07 UTC (rev 12334)
@@ -32,6 +32,7 @@
{
private String functionId = null;
private String ruleReference = null;
+ private String when = null;
public DroolsRuleExpression()
{
@@ -57,4 +58,14 @@
{
this.ruleReference = ruleReference;
}
+
+ public String getWhen()
+ {
+ return this.when;
+ }
+
+ public void setWhen(String when)
+ {
+ this.when = when;
+ }
}
Modified: modules/authorization/trunk/common/src/main/java/org/jboss/security/authz/model/Subject.java
===================================================================
--- modules/authorization/trunk/common/src/main/java/org/jboss/security/authz/model/Subject.java 2008-12-03 06:35:00 UTC (rev 12333)
+++ modules/authorization/trunk/common/src/main/java/org/jboss/security/authz/model/Subject.java 2008-12-03 07:10:07 UTC (rev 12334)
@@ -23,6 +23,7 @@
package org.jboss.security.authz.model;
import java.util.Set;
+import java.util.HashSet;
/**
* Represents the Identity of the user, machine, etc trying to execute a protected Action on a protected Resource
@@ -38,6 +39,11 @@
private Set<Attribute> attributes = null;
/**
+ * Category of Subject such as a user Identity, a Machine Identity, etc
+ */
+ private String category = null;
+
+ /**
*
*
*/
@@ -62,5 +68,39 @@
public void setAttributes(Set<Attribute> attributes)
{
this.attributes = attributes;
- }
+ }
+
+ /**
+ *
+ * @return
+ */
+ public String getCategory()
+ {
+ return category;
+ }
+
+ /**
+ *
+ * @param category
+ */
+ public void setCategory(String category)
+ {
+ this.category = category;
+ }
+
+ /**
+ *
+ * @param attribute
+ */
+ public void addAttribute(Attribute attribute)
+ {
+ if(this.attributes == null)
+ {
+ this.attributes = new HashSet<Attribute>();
+ }
+
+ this.attributes.add(attribute);
+ }
+
+
}
Modified: modules/authorization/trunk/pom.xml
===================================================================
--- modules/authorization/trunk/pom.xml 2008-12-03 06:35:00 UTC (rev 12333)
+++ modules/authorization/trunk/pom.xml 2008-12-03 07:10:07 UTC (rev 12334)
@@ -11,7 +11,9 @@
<modules>
<module>common</module>
+ <!--
<module>security-console</module>
+ -->
<module>PEP</module>
<module>PAP</module>
</modules>
@@ -29,8 +31,10 @@
<version.commons-digester>1.6</version.commons-digester>
<version.junit>3.8.2</version.junit>
<version.sun.jaxb>2.1.4</version.sun.jaxb>
+ <version.sun.jaf>1.1</version.sun.jaf>
<version.jboss.xacml>2.0.3-SNAPSHOT</version.jboss.xacml>
<version.apache.log4j>1.2.14</version.apache.log4j>
+ <version.org.drools>4.0.7</version.org.drools>
<!-- local environment properties -->
<jboss.home>/home/soshah/appServers/jboss-4.2.2.GA</jboss.home>
@@ -132,6 +136,13 @@
<scope>provided</scope>
</dependency>
+ <!-- sun jaf -->
+ <dependency>
+ <groupId>sun-jaf</groupId>
+ <artifactId>activation</artifactId>
+ <version>${version.sun.jaf}</version>
+ </dependency>
+
<!-- jboss xacml -->
<dependency>
<groupId>org.jboss.security</groupId>
@@ -160,6 +171,20 @@
<artifactId>log4j</artifactId>
<version>${version.apache.log4j}</version>
<scope>provided</scope>
+ </dependency>
+
+ <!-- Drools -->
+ <dependency>
+ <groupId>org.drools</groupId>
+ <artifactId>drools-core</artifactId>
+ <version>${version.org.drools}</version>
+ <scope>provided</scope>
+ </dependency>
+ <dependency>
+ <groupId>org.drools</groupId>
+ <artifactId>drools-compiler</artifactId>
+ <version>${version.org.drools}</version>
+ <scope>provided</scope>
</dependency>
</dependencies>
</dependencyManagement>
@@ -171,6 +196,12 @@
<groupId>apache-log4j</groupId>
<artifactId>log4j</artifactId>
</dependency>
+
+ <dependency>
+ <groupId>sun-jaf</groupId>
+ <artifactId>activation</artifactId>
+ <scope>test</scope>
+ </dependency>
</dependencies>
<build>
17 years, 5 months
- 1
- 0
JBoss Portal SVN: r12333 - docs/enterprise/trunk/UserGuide/en-US.
by portal-commits＠lists.jboss.org
Author: smeehan
Date: 2008-12-03 01:35:00 -0500 (Wed, 03 Dec 2008)
New Revision: 12333
Modified:
docs/enterprise/trunk/UserGuide/en-US/Book_Info.xml
docs/enterprise/trunk/UserGuide/en-US/JBoss_Portal_Basics.xml
docs/enterprise/trunk/UserGuide/en-US/User_Role.xml
Log:
Revisions JBPORTAL-2198
Modified: docs/enterprise/trunk/UserGuide/en-US/Book_Info.xml
===================================================================
--- docs/enterprise/trunk/UserGuide/en-US/Book_Info.xml 2008-12-03 05:07:04 UTC (rev 12332)
+++ docs/enterprise/trunk/UserGuide/en-US/Book_Info.xml 2008-12-03 06:35:00 UTC (rev 12333)
@@ -12,7 +12,7 @@
<abstract>
<para>This document is intended for those using JBoss Portal as End-Users. This is a "Where do I Click?" Guide.</para>
<para>
- For Portlet developers, Portal administrators, and those wishing to implement/extend the JBoss
+ For Portlet developers, Portal administrators, and those wishing to extend and/or implement the JBoss
Portal framework, there is a Reference Guide available from our
<ulink url="http://labs.jboss.com/portal/jbossportal/docs/index.html">documentation page</ulink>
.
Modified: docs/enterprise/trunk/UserGuide/en-US/JBoss_Portal_Basics.xml
===================================================================
--- docs/enterprise/trunk/UserGuide/en-US/JBoss_Portal_Basics.xml 2008-12-03 05:07:04 UTC (rev 12332)
+++ docs/enterprise/trunk/UserGuide/en-US/JBoss_Portal_Basics.xml 2008-12-03 06:35:00 UTC (rev 12333)
@@ -10,7 +10,7 @@
<title>Portal Concepts - Illustrated</title>
<para>
- This section will introduce the reader to some basic portal terms and concepts used within JBoss Portal and thoughout this document.
+ This section will introduce the reader to some basic portal terms and concepts used within JBoss Portal and throughout this document.
</para>
@@ -109,34 +109,34 @@
</para>
</listitem>
</itemizedlist>
- <table id="Table_1">
- <title>Window state icons and their meaning</title>
- <tgroup cols="3">
- <colspec colname="c1" colnum="1" colwidth="1*"/>
- <colspec colname="c2" colnum="2" colwidth="4*"/>
- <colspec colname="c3" colnum="3" colwidth="4*"/>
- <thead>
- <row>
- <entry>
- Window State
- </entry>
- <entry>
- Icon
- </entry>
- <entry>
- Meaning
- </entry>
+ <table id="Table_1">
+ <title>Window state icons and their meaning</title>
+ <tgroup cols="3">
+ <colspec colname="c1" colnum="1" colwidth="1*"/>
+ <colspec colname="c2" colnum="2" colwidth="4*"/>
+ <colspec colname="c3" colnum="3" colwidth="4*"/>
+ <thead>
+ <row>
+ <entry>
+ Window State
+ </entry>
+ <entry>
+ Icon
+ </entry>
+ <entry>
+ Meaning
+ </entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- Normal
- </entry>
- <entry>
- <mediaobject>
- <imageobject>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ Normal
+ </entry>
+ <entry>
+ <mediaobject>
+ <imageobject>
<imagedata fileref="images/intro/ico_16_normal.gif" format="GIF"/>
</imageobject>
</mediaobject>
@@ -144,9 +144,7 @@
<entry>
- Normal window state, is the most common state for portlets (portlets in the
- above image are in the normal window state). The portlet window will occupy only
- enough space to show the portlet content on the page.
+ Normal window state, is the most common state for portlets (portlets in the above image are in the normal window state). The portlet window will occupy only enough space to show the portlet content on the page.
</entry>
@@ -183,28 +181,19 @@
<entry>
The portlet window can occupy as much space of real estate on the page.
</entry>
- </row>
-
-
+ </row>
</tbody>
</tgroup>
</table>
-
-
-
-
-
-
-
-
+
- <para>
- <emphasis role="bold">Portlet Modes and their meaning:</emphasis>
- Portlet modes are not always available (it depends on the portlet support for a given mode).
- Moreover, the Edit mode is only available to logged-in users, as in this mode, the portlet
- preferences can be modified to be individually suited to a particular user's needs.
- </para>
+ <para>
+ <emphasis role="bold">Portlet Modes and their meaning:</emphasis>
+ Portlet modes are not always available (it depends on the portlet support for a given mode).
+ Moreover, the Edit mode is only available to logged-in users, as in this mode, the portlet
+ preferences can be modified to be individually suited to a particular user's needs.
+ </para>
<itemizedlist>
<listitem>
<para>
@@ -213,8 +202,8 @@
<imagedata fileref="images/intro/ico_edit.gif" format="GIF"/>
</imageobject>
</mediaobject>
- <emphasis role="bold">(Edit)</emphasis>
- - Only visible to logged-in users. Allows a logged-in user to customize the
+ <emphasis role="bold">Edit</emphasis>
+ : Only visible to logged-in users. Allows a logged-in user to customize the
portlet's preferences.
</para>
</listitem>
@@ -225,8 +214,8 @@
<imagedata fileref="images/intro/ico_cancel.gif" format="GIF"/>
</imageobject>
</mediaobject>
- <emphasis role="bold">(Return to View mode)</emphasis>
- - The button labeled 'Cancel' is only visible when a user is logged in and the
+ <emphasis role="bold">Return to View mode</emphasis>
+ : The button labeled 'Cancel' is only visible when a user is logged in and the
portlet associated to the current window is in the Edit mode. This replaces the
Edit button so the user understands that by clicking it the user will leave the
"Edit mode" and revert back to "View mode". Portlets are by default in View
@@ -241,7 +230,7 @@
</imageobject>
</mediaobject>
<emphasis role="bold">Help</emphasis>
- - Allows a user to access useful information about the portlet.
+ : Allows a user to access useful information about the portlet.
</para>
</listitem>
</itemizedlist>
@@ -326,7 +315,7 @@
</para>
<note>
<para>
- If you login as an administrator, you will also be presented with a link to the <emphasis>Admin</emphasis> portal.
+ If you login as an administrator, you will also be presented with a link to the <emphasis role="bold">Admin</emphasis> portal.
</para>
</note>
@@ -358,7 +347,7 @@
<note>
<para>
Administrators should view <xref linkend="Portal_User_Guide-User_Role-Managing_Users"/> for managing the portal user base. Only user
- operations are covered in this section...</para>
+ operations are covered in this section.</para>
</note>
<para>
<mediaobject>
@@ -386,7 +375,7 @@
<emphasis role="bold">Create a new account</emphasis>
</para>
<para>
- Create a new account by clicking on the <emphasis>Register</emphasis>
+ Create a new account by clicking on the <emphasis role="bold">Register</emphasis>
link in the navigation of the portlet. A user can then fill in the necessary
information to create an account on the system:
<mediaobject>
@@ -402,7 +391,7 @@
<emphasis role="bold">Lost password</emphasis>
</para>
<para>
- Already registered users can request a new password by clicking on the <emphasis>Lost password</emphasis> link
+ Already registered users can request a new password by clicking on the <emphasis role="bold">Lost password</emphasis> link
in the navigation of the portlet. After entering your user name you will receive an e-mail with your new
login credentials.
</para>
@@ -428,7 +417,7 @@
<emphasis role="bold">Edit personal information</emphasis>
</para>
<para>A user has the ability to edit their personal information, change their password and e-mail address at any time by clicking on the
- <emphasis>Edit profile</emphasis> link, when logged in.
+ <emphasis role="bold">Edit profile</emphasis> link, when logged in.
</para>
</listitem>
</itemizedlist>
@@ -626,7 +615,7 @@
</imageobject>
</mediaobject>
- Click on <emphasis>submit</emphasis>
+ Click on <emphasis role="bold">submit</emphasis>
<mediaobject>
<imageobject>
@@ -692,11 +681,11 @@
<para>
You can select a theme and layout for your dashboard by selecting from the available ones and then
- clicking on select in the <emphasis>Theme and Layout</emphasis> form.
+ clicking on select in the <emphasis role="bold">Theme and Layout</emphasis> form.
</para>
<para>
You can also create new pages that will be added to your dashboard by simply entering the name of the new
- page in the <emphasis>Create New Page</emphasis> form at the top left of the screen.
+ page in the <emphasis role="bold">Create New Page</emphasis> form at the top left of the screen.
<note>
<itemizedlist>
<listitem>
@@ -757,7 +746,7 @@
<para>
The Admin Portal's purpose is to allow an administrator to manage all aspects of the portal. You <emphasis role="bold">must be</emphasis> logged in as an administrator, or have proper privileges
- to see this portal.Follow the links for in-depth reviews of these functions:
+ to see this portal. Follow the links for in-depth reviews of these functions:
<itemizedlist>
<listitem>
Modified: docs/enterprise/trunk/UserGuide/en-US/User_Role.xml
===================================================================
--- docs/enterprise/trunk/UserGuide/en-US/User_Role.xml 2008-12-03 05:07:04 UTC (rev 12332)
+++ docs/enterprise/trunk/UserGuide/en-US/User_Role.xml 2008-12-03 06:35:00 UTC (rev 12333)
@@ -18,7 +18,7 @@
<title>Managing Users</title>
<para>
- This section covers the user management of the IdentityUserManagementPortlet which is displayed by default.
+ This section covers the user management of the <classname>IdentityUserManagementPortlet</classname> which is displayed by default.
For role management please see <xref linkend="Portal_User_Guide-User_Role-Managing_Roles"/>.
<mediaobject>
@@ -77,7 +77,7 @@
<title>Updating User Profiles</title>
<para>
Clicking on the
- <emphasis>Edit user</emphasis>
+ <emphasis role="bold">Edit user</emphasis>
link on the search page will allow you to edit a user's profile data, and even reset his password.
<mediaobject>
@@ -100,7 +100,7 @@
<para>
Clicking on the
- <emphasis>Roles</emphasis>
+ <emphasis role="bold">Roles</emphasis>
link in the search page allows you to modify the roles a specific user belongs to.
<mediaobject>
@@ -121,7 +121,7 @@
<title>Creating Users</title>
<para>
Clicking on the
- <emphasis>Create User Account</emphasis>
+ <emphasis role="bold">Create User Account</emphasis>
link on the main UserPortlet view, allows administrators to instantly create new users.
<mediaobject>
@@ -144,7 +144,7 @@
<para>
- Click on the <emphasis>Show pending registrations</emphasis> link to show all registrations with validated e-mail addresses.
+ Click on the <emphasis role="bold">Show pending registrations</emphasis> link to show all registrations with validated e-mail addresses.
You can approve or reject each user by clicking on the corresponding action or click on <emphasis>select all</emphasis>
to approve or reject all selected users.
</para>
@@ -166,7 +166,7 @@
<note>
<para>
By default the subscription modes are set to <emphasis>automatic</emphasis> and users will be created automatically. Furthermore the
- link to <emphasis>Show pending registrations</emphasis> will only be displayed if a user needs to be approved by the administrator.
+ link to <emphasis role="bold">Show pending registrations</emphasis> will only be displayed if a user needs to be approved by the administrator.
</para>
</note>
</section>
@@ -179,7 +179,7 @@
<title>Managing Roles</title>
<para>
- The User management portlet is also responsible to create and edit roles and it is accessible once logged in - as described in previously - when clicking on the <emphasis>role management</emphasis>
+ The User management portlet is also responsible to create and edit roles and it is accessible once logged in - as described in previously - when clicking on the <emphasis role="bold">role management</emphasis>
link in the User management portlet.
</para>
@@ -217,7 +217,7 @@
<para>
Creating new roles, is accomplished by first clicking on the
- <emphasis>Create new role</emphasis>
+ <emphasis role="bold">Create new role</emphasis>
link in the portlet.
<mediaobject>
<imageobject>
@@ -245,7 +245,7 @@
<title>Edit a role</title>
<para>
- Editing roles is accomplished by clicking on <emphasis>Edit role</emphasis> in the row of the role you want to edit.
+ Editing roles is accomplished by clicking on <emphasis role="bold">Edit role</emphasis> in the row of the role you want to edit.
<mediaobject>
<imageobject>
<imagedata fileref="images/role/edit_role.png" format="PNG" scalefit="1"/>
@@ -266,7 +266,7 @@
<para>
Editing role members is accomplished by first clicking the
- <emphasis>Members</emphasis>
+ <emphasis role="bold">Members</emphasis>
link at the role management page for the role you would like to modify.
<mediaobject>
@@ -290,7 +290,7 @@
<para>
Deleting roles is accomplished by clicking the
- <emphasis>Delete</emphasis>
+ <emphasis role="bold">Delete</emphasis>
link for the role you would like to remove.
</para>
17 years, 5 months
- 1
- 0
JBoss Portal SVN: r12332 - docs/enterprise/trunk/UserGuide/en-US.
by portal-commits＠lists.jboss.org
Author: smeehan
Date: 2008-12-03 00:07:04 -0500 (Wed, 03 Dec 2008)
New Revision: 12332
Modified:
docs/enterprise/trunk/UserGuide/en-US/Administration_CMS_Portlet.xml
docs/enterprise/trunk/UserGuide/en-US/Author_Group.xml
docs/enterprise/trunk/UserGuide/en-US/Book_Info.xml
docs/enterprise/trunk/UserGuide/en-US/Dynamicity.xml
docs/enterprise/trunk/UserGuide/en-US/JBoss_Portal_Basics.xml
docs/enterprise/trunk/UserGuide/en-US/Portal_User_Guide.ent
docs/enterprise/trunk/UserGuide/en-US/Portal_User_Guide.xml
docs/enterprise/trunk/UserGuide/en-US/Revision_History.xml
docs/enterprise/trunk/UserGuide/en-US/User_Role.xml
Log:
revisions JBPORTAL-2198
Modified: docs/enterprise/trunk/UserGuide/en-US/Administration_CMS_Portlet.xml
===================================================================
--- docs/enterprise/trunk/UserGuide/en-US/Administration_CMS_Portlet.xml 2008-12-03 05:04:12 UTC (rev 12331)
+++ docs/enterprise/trunk/UserGuide/en-US/Administration_CMS_Portlet.xml 2008-12-03 05:07:04 UTC (rev 12332)
@@ -3,14 +3,9 @@
]>
<chapter id="Portal_User_Guide-Test-Administration_CMS_Portlet">
- <title>Administration CMS Portlet</title>
+ <title>Administration Content Management System (CMS) Portlet</title>
-<section id="Portal_User_Guide-Administration_CMS_Portlet-Administration_-_Content_Management_System">
- <title>Administration - Content Management System</title>
- <para>
- Test of a section
- </para>
-</section>
+
<section id="Portal_User_Guide-Administration_-_Content_Management_System-Introduction">
<title>Introduction</title>
@@ -21,11 +16,11 @@
</para>
<para>
- Viewing the CMSAdmin Portlet is accomplished by logging in as an admin (admin/admin) and navigating to the admin portal and then the CMS Page tab.
+ Viewing the CMSAdmin Portlet is accomplished by logging in as admin (admin/admin) and navigating to the admin portal and then the CMS Page tab.
</para>
<para>
- You should then be presented with a page that is similar to this:
+ You will then be presented with a page that is similar to this:
</para>
<mediaobject>
@@ -90,7 +85,7 @@
</para>
<para>
- Version and Locale Information are also contained on this screen. Note that any version labeled with the
+ Version and Locale Information are also contained on this screen. Note that any version labeled with a
<mediaobject>
<imageobject>
@@ -118,7 +113,7 @@
<para>
The copy resource window allows a user to copy files to any folder on the system, as well as copy whole directory trees to any directory on the system. A user can select which
- destination directory to copy the resource to, by using the directory browser. Clicking the
+ destination directory to copy the resource to by using the directory browser. Clicking the
<mediaobject>
<imageobject>
@@ -126,7 +121,7 @@
</imageobject>
</mediaobject>
- icon expands the directory tree. Clicking on the name of the directory within the tree, sets it as the destination directory for the copied resource.
+ icon expands the directory tree. Clicking on the name of the directory within the tree sets it as the destination directory for the copied resource.
</para>
</section>
@@ -155,7 +150,7 @@
</imageobject>
</mediaobject>
- icon expands the directory tree. Clicking on the name of the directory within the tree, sets it as the destination directory for the moved resource.
+ icon expands the directory tree. Clicking on the name of the directory within the tree sets it as the destination directory for the moved resource.
</para>
@@ -176,7 +171,7 @@
</mediaobject>
<para>
- The delete resource confirmation window allows a user to delete a file, or a directory on the system. Note that deleting a directory, will delete the entire tree, so all directories under the deleted one, will also be deleted.
+ The delete resource confirmation window allows a user to delete a file or a directory on the system. Note that deleting a directory will delete the entire tree, so all directories under the deleted one will also be deleted.
</para>
@@ -250,10 +245,10 @@
icon.
</para>
- <note>
+ <important>
<para>
- It is important to note here that when creating links to images or other resources within the system, as user must use the relative file path to that resource. ie: images/hello.gif. Keep in mind at all times that the document base is http://localhost/portal/ by default!</para>
- </note>
+ It is important to note here that when creating links to images or other resources within the system, a user must use the relative file path to that resource. ie: images/hello.gif. Keep in mind at all times that the document base is http://localhost/portal/ by default!</para>
+ </important>
<para>
Additionally, a user can set a title for the file that will be used in the portlet title bar, and a language for the file, used in serving localized content.
@@ -316,8 +311,8 @@
</section>
- <section id="Portal_User_Guide-Actions-Exportig_Folders">
- <title>Exporting folders</title>
+ <section id="Portal_User_Guide-Actions-Exporting_Folders">
+ <title>Exporting Folders</title>
<para>
@@ -343,11 +338,11 @@
icon expands the directory tree. Clicking on the name of the directory within the tree, sets it as the source directory for the export resource. Additionally, a user can set a language for the files to be exported.
</para>
- <note>
+ <important>
<para>
Version information is not exported. Only versions labeled "Live" are exported!
</para>
- </note>
+ </important>
</section>
@@ -415,7 +410,7 @@
</mediaobject>
</para>
<para>
- You should then be presented with a screen that allows you to assign read, write, and manage priviledges on the selected node for selected Roles or specific Users.
+ You should then be presented with a screen that allows you to assign read, write, and manage privileges on the selected node for selected Roles or specific Users.
<mediaobject>
<imageobject>
@@ -440,7 +435,7 @@
</listitem>
</itemizedlist>
- Adminsitrating and assigning permissions on a selected node is as simple as selecting which Roles and/or Users you want to allow to have a specific permission.
+ Administrating and assigning permissions on a selected node is as simple as selecting which Roles and/or Users you want to allow to have a specific permission.
</para>
</section>
Modified: docs/enterprise/trunk/UserGuide/en-US/Author_Group.xml
===================================================================
--- docs/enterprise/trunk/UserGuide/en-US/Author_Group.xml 2008-12-03 05:04:12 UTC (rev 12331)
+++ docs/enterprise/trunk/UserGuide/en-US/Author_Group.xml 2008-12-03 05:07:04 UTC (rev 12332)
@@ -4,33 +4,25 @@
<authorgroup>
<author>
- <firstname>Roy</firstname>
- <surname>Russo</surname>
- <affiliation>
- <orgname>JBoss</orgname>
- <orgdiv>Best Div in the place</orgdiv>
- </affiliation>
- <email>roy(a)jboss.org</email>
- </author>
-
- <author>
<firstname>Chris</firstname>
<surname>Laprun</surname>
- <affiliation>
- <orgname>JBoss</orgname>
- <orgdiv>Best Div in the place</orgdiv>
- </affiliation>
<email>chris.laprun(a)jboss.com</email>
</author>
+
<author>
<firstname>Emanuel</firstname>
- <surname>Muckenhuber</surname>
- <affiliation>
- <orgname>JBoss</orgname>
- <orgdiv>Best Div in the place</orgdiv>
- </affiliation>
+ <surname>Muckenhuber</surname>
<email>emuckenh(a)redhat.com</email>
</author>
+
+ <author>
+ <firstname>Roy</firstname>
+ <surname>Russo</surname>
+ <email>roy(a)jboss.org</email>
+ </author>
+
+
+
Modified: docs/enterprise/trunk/UserGuide/en-US/Book_Info.xml
===================================================================
--- docs/enterprise/trunk/UserGuide/en-US/Book_Info.xml 2008-12-03 05:04:12 UTC (rev 12331)
+++ docs/enterprise/trunk/UserGuide/en-US/Book_Info.xml 2008-12-03 05:07:04 UTC (rev 12332)
@@ -4,10 +4,10 @@
<bookinfo id="Portal_User_Guide-Documentation">
<title>Portal User Guide</title>
- <subtitle>short descriptor</subtitle>
+
<productname>JBoss</productname>
<productnumber>0.1</productnumber>
- <edition>0</edition>
+ <edition>1</edition>
<pubsnumber>0</pubsnumber>
<abstract>
<para>This document is intended for those using JBoss Portal as End-Users. This is a "Where do I Click?" Guide.</para>
Modified: docs/enterprise/trunk/UserGuide/en-US/Dynamicity.xml
===================================================================
--- docs/enterprise/trunk/UserGuide/en-US/Dynamicity.xml 2008-12-03 05:04:12 UTC (rev 12331)
+++ docs/enterprise/trunk/UserGuide/en-US/Dynamicity.xml 2008-12-03 05:07:04 UTC (rev 12332)
@@ -3,38 +3,41 @@
]>
<chapter id="Portal_User_Guide-Dynamicity">
- <title>Administration - Portal Object Management (Dynamcity)</title>
+ <title>Administration - Portal Object Management (Dynamicity)</title>
<section id="Portal_User_Guide-Dynamacity-Introduction">
<title>Introduction</title>
- <note>
- <para>
- Viewing the Management Portlet is accomplished by logging in as an admin (admin/admin) and navigating to the Admin portal (see linkcommentedout <!-- <xref linkend="adminportal"/> -->).</para>
- </note>
+
- <para>
+ <para>
- The concept of dynamicity refers to the fact all portal objects can be dynamically modified at runtime,
- eliminating the need to struggle with large xml files, or restarting the application server for changes to take
- effect. In the scope of dynamicity, Portal objects are defined and can be altered as follows:
+ The concept of dynamicity refers to the fact all portal objects can be dynamically modified at runtime,
+ eliminating the need to struggle with large xml files, or restarting the application server for changes to take
+ effect. In the scope of dynamicity, portal objects are defined and can be altered as follows:
- <itemizedlist>
- <listitem>
- <para>Portal Instances: Multiple Portal instances can be launched at any time, secured, and skinned.</para></listitem>
- <listitem><para>Pages: Multiple pages, composed of windows, can coexist inside a portal instance, secured and each
- could have its own theme applied, if desired.</para></listitem>
- <listitem><para>Portlets: Can be hot-deployed and will instantly register with the portal, appearing in the
- management portlet.</para></listitem>
- <listitem><para>Portlet Instances: Instances can be created/destroyed. Their preference variables can be modified
- at runtime, instances assigned to windows and secured.</para></listitem>
+ <itemizedlist>
+ <listitem>
+ <para>Portal Instances: Multiple Portal instances can be launched at any time, secured, and skinned.</para></listitem>
+ <listitem><para>Pages: Multiple pages, composed of windows, can securely coexist inside a portal instance. Each
+ could have its own theme applied, if desired.</para></listitem>
+ <listitem><para>Portlets: Can be hot-deployed and will instantly register with the portal, appearing in the
+ management portlet.</para></listitem>
+ <listitem><para>Portlet Instances: Instances can be created/destroyed. Instance preference variables can be modified
+ at runtime, assigned to windows and secured.</para></listitem>
<listitem><para>Windows: Windows can be secured, created/destroyed, and assigned to specific pages.</para></listitem>
- <listitem><para>Themes/Layouts: Can be hot-deployed and will register with the portal, appearing the management
+ <listitem><para>Themes/Layouts: Can be hot-deployed and will register with the portal. They appear in the management
portlet, allowing for dynamic customization of any of the above components.</para>
</listitem>
</itemizedlist>
</para>
- <!--
+ <note>
+ <para>
+ Viewing the Management Portlet is accomplished by logging in as an admin (admin/admin) and navigating to the Admin portal (see <xref linkend="Portal_User_Guide-JBoss_Portal_Basics-Admin_Portal"/>).
+ </para>
+ </note>
+
+ <!--
<note>
Many of the operations that can be done via the Management portlet are done in the context of the current
user session. In order to see the changes on the affected pages, please log out and log back in.
@@ -47,16 +50,18 @@
<title>Management Portlet</title>
- <note>
+
<para>
+ The management portlet provides a two-part interface: tabs at the top which correspond to the different sections
+ that can be managed; and the main area under it, which displays the current information for the selected tab.
+ </para>
+ <note>
+ <para>
For the remainder of this chapter, the term <emphasis role="bold">object</emphasis> will be used to mean
Portal, Page, Portlet, or Window indifferently.
</para>
- </note>
- <para>
- The management portlet provides a two-part interface: tabs, at the top, corresponding to the different sections
- that can be managed; and the main area under it, displaying the current information for the selected tab.
-
+ </note>
+ <para>
<mediaobject>
<imageobject>
<imagedata fileref="images/intro/adminportal.png" format="PNG" scalefit="1"/>
@@ -68,18 +73,18 @@
<itemizedlist>
<listitem>
- <para><emphasis>Portal Objects</emphasis> gathering operations pertaining to managing portal objects
+ <para><emphasis role="bold">Portal Objects</emphasis> gather operations pertaining to managing portal objects
(portal instances, pages, windows and their respective configuration information). This is the most
complex part of the interface.</para>
</listitem>
- <listitem><para><emphasis>Portlet Instances</emphasis> giving access to all the Portlet instances that have been
+ <listitem><para><emphasis role="bold">Portlet Instances</emphasis> give access to all the Portlet instances that have been
configured.</para>
</listitem>
- <listitem><para><emphasis>Portlet Definitions</emphasis> giving access to the currently available portlet
+ <listitem><para><emphasis role="bold">Portlet Definitions</emphasis> give access to the currently available portlet
providers as well as the Portlets that each provider publishes.</para>
</listitem>
<listitem>
- <para><emphasis>Dashboards</emphasis> allowing administrators to configure how Dashboards should behave.</para>
+ <para><emphasis role="bold">Dashboards</emphasis> allow administrators to configure how Dashboards should behave.</para>
</listitem>
</itemizedlist>
@@ -90,7 +95,7 @@
<section id="Portal_User_Guide-Management_Portlet-Managing_Portal_Objects">
- <title>Magaging Portal Objects</title>
+ <title>Managing Portal Objects</title>
@@ -106,12 +111,12 @@
</mediaobject>
<para>
- The <literal>Portal Objects</literal> brings the administrator to a page showing the list of the
+ <emphasis role="bold">Portal Objects</emphasis> brings the administrator to a page displaying a list of the
available portal instances defined for this Portal server. Several points are of particular interest. First, a
navigation indicator or "breadcrumbs" is located right beneath the tabs. This provides context as to
- where in the hierarchy of portal objects the current screen is located as some of the screens can be
- found at several levels of the hierarchy. If you are lost, take a look at the breadcrumbs for context!
- When you first click on the <literal>Portal Objects</literal> tab, the context is the list of portals
+ where in the hierarchy of portal objects the current screen is located. Some of the screens can be
+ found at several levels of the hierarchy. If you are lost, refer to the breadcrumbs for context.
+ When you first click on the <emphasis role="bold">Portal Objects</emphasis> tab, the context is the list of portals
as shown in the picture above.
</para>
@@ -146,9 +151,9 @@
hierarchy of available portal objects. Clicking on an action name will execute the specified action
on the associated portal instance. These actions are available on each individual portal screen as we
shall see. The notable exception is the <literal>Make Default/Default</literal> action which is only
- available in this listing as it is more of an action across portals than specific to a portal thus
+ available in this listing as it is more of an action across portals than to a specific portal thus
benefiting from being seen at this level. This action allows users to specify which portal instance
- is displayed when Portal is first being accessed. Clicking on <literal>Make Default</literal> will
+ is displayed when the Portal is first being accessed. Clicking on <literal>Make Default</literal> will
specify that the associated portal will be displayed to users by default. The portal list will be
refreshed and the selected portal status will be refreshed, its action now showing its
<literal>Default</literal> status.
@@ -157,7 +162,7 @@
<para>
In the next sections we will demonstrate the functionality of the management portlet by drilling
progressively further down this hierarchy to look at the default portal, one of its pages, show
- how to configure content on a page and, finally, look at a specific window information.
+ how to configure content on a page and, finally, look at specific window information.
</para>
</section>
@@ -166,7 +171,7 @@
<para>
If you click on the <literal>default</literal> portal in the list of available portal instances on the
- top-level <literal>Portal Objects</literal> page, you'll be taken to a page showing the information
+ top-level <literal>Portal Objects</literal> page, you will be taken to a page showing the information
for the portal instance named "default", as shown below:
<mediaobject>
@@ -175,7 +180,7 @@
</imageobject>
</mediaobject>
- Note the breadcrumbs at the top of the screen indicating where in the hierachy you currently are.
+ Note the breadcrumbs at the top of the screen indicating where in the hierarchy you currently are.
In this case, we are looking at the <literal>default</literal> portal.
</para>
@@ -197,7 +202,7 @@
<para>
Finally, a table displaying the list of available pages for this portal instance is located at the
bottom of this screen. The first column shows the page name, which you can click to drill down the
- hierachy and display the information specific to that particular page. The second column, on the other
+ hierarchy and display the information specific to that particular page. The second column, on the other
hand, provides a list of action links on the associated page. These links
will be also appearing on individual page screens, as we shall see, just like portal action links
appearing in the portal instances list also appeared on individual portal pages. Once again, the
@@ -270,7 +275,7 @@
</para>
<para>
- Now that we have looked at portal level information, let's drill down the hierachy again and look at
+ Now that we have looked at portal level information, let's drill down the hierarchy again and look at
a page, more precisely the <literal>default</literal> page, by clicking its name in the pages list.
</para>
</section>
@@ -300,7 +305,7 @@
Similarly to other screens in the portal objects hierarchy, a page configuration screen also provides
a list of all windows for that page. This list contains two columns: the first one contains the
name of the window, while the second one provides a list of action links for that specific window.
- As usual, clicking on a window name will display information about that window.
+ Clicking on a window name will display information about that window.
</para>
<para>
@@ -360,7 +365,7 @@
</mediaobject>
Note that this displays some information about the portlet instance.
- Finally, we can add our window to the center region of the page by clicking on <literal>Add</literal>
+ Finally, we can add our window to the center region of the page by clicking on the <literal>Add</literal>
button located left to the windows list for the region:
<mediaobject>
@@ -459,7 +464,7 @@
Integration
</ulink>
- in the Reference Guide. More details on how to setup content roots in CMS are available in linkcommentedout <!-- <xref linkend="cmsadmin"/> -->.
+ in the Reference Guide. More details on how to setup content roots in CMS are available in <xref linkend="Portal_User_Guide-Administration_-_Content_Management_System-Introduction"/>.
</para>
</section>
@@ -469,7 +474,7 @@
<title>Looking at windows of a given page</title>
<para>
- Window operations are similar to the same operations at other level of the hierachy of portal objects.
+ Window operations are similar to the same operations at other level of the hierarchy of portal objects.
The only information displayed when a window name is clicked in the windows list of a portal page
information screen is information about the content, similar to the one that is displayed in the
page layout screen. Thus, for the <literal>google</literal> window that we created in the previous
@@ -481,7 +486,7 @@
</imageobject>
</mediaobject>
- Note, once again, the breadcrumbs... :)
+
</para>
</section>
</section>
@@ -509,8 +514,8 @@
<para>
The <literal>Portlet Definitions</literal> tab brings the administrator to the list of portlet
- definitions, formatted as a table displaying name, description, whether the portlet is remote (i.e. accessed
- via WSRP from a remote producer) or if it is remotable (i.e. if it is exposed to WSRP consumers by Portal's
+ definitions, formatted as a table displaying name, description, whether the portlet is remote (i.e., accessed
+ via WSRP from a remote producer) or if it is remotable (i.e., if it is exposed to WSRP consumers by Portal's
producer).
</para>
@@ -521,11 +526,11 @@
<itemizedlist>
<listitem>
- <para><emphasis>local</emphasis>: this is Portal's portlet container. Any successfully deployed portlet will
+ <para><emphasis role="bold">local</emphasis>: this is Portal's portlet container. Any successfully deployed portlet will
appear in the list of available portlet definitions for this provider.</para>
</listitem>
<listitem>
- <para><emphasis>self</emphasis>: this is Portal's default WSRP consumer configured to consume portlets
+ <para><emphasis role="bold">self</emphasis>: this is Portal's default WSRP consumer configured to consume portlets
published by Portal's own WSRP producer. This doesn't have much practical interest apart from allowing
a quick test of the WSRP functionality of Portal.</para>
</listitem>
@@ -567,7 +572,7 @@
<para>
The <literal>Dashboards</literal> tab allows the administrator to configure parameters for all user dashboards.
- It also allows her to configure the error pages and theme properties as for the other portal objects.
+ It also allows the user to configure the error pages and theme properties as for the other portal objects.
</para>
</section>
@@ -577,8 +582,8 @@
<para>
The wizard mode is a fast and easy way to create a new window on a page backed by a portlet instance.
- The user just needs to define which portlet definition to use, where should the instance be located
- (portal / page / location on the page) and the wizard will automatically create a new instance of
+ The user just needs to define which portlet definition to use and where the instance should be located
+ (portal / page / location on the page. The wizard will automatically create a new instance of
the portlet, create a window for it and add that window to the specified region on the page
defined by the user.
Modified: docs/enterprise/trunk/UserGuide/en-US/JBoss_Portal_Basics.xml
===================================================================
--- docs/enterprise/trunk/UserGuide/en-US/JBoss_Portal_Basics.xml 2008-12-03 05:04:12 UTC (rev 12331)
+++ docs/enterprise/trunk/UserGuide/en-US/JBoss_Portal_Basics.xml 2008-12-03 05:07:04 UTC (rev 12332)
@@ -4,15 +4,13 @@
<chapter id="Portal_User_Guide-JBoss_Portal_Basics">
<title>JBoss Portal Basics</title>
- <para>
- This is a test paragraph
- </para>
+
<section id="Portal_User_Guide-JBoss_Portal_Basics-Portal_Concepts">
<title>Portal Concepts - Illustrated</title>
<para>
- This section will introduce the reader to some basic portal concepts and terms, used within JBoss Portal and this document.
+ This section will introduce the reader to some basic portal terms and concepts used within JBoss Portal and thoughout this document.
</para>
@@ -21,7 +19,7 @@
<title>Portal Instances</title>
<para>
- JBoss Portal supports multiple portal instances running within one container. A portal instance can be viewed as a 'bucket', containing portal objects such as, Portal Pages, Themes, Layouts, and Portlet Windows. It also manages the relationship between the user and the portal itself. The hierarchy of portal objects is depicted as follows:
+ JBoss Portal supports multiple portal instances running within one container. A portal instance can be viewed as a 'bucket', containing portal objects such as Portal Pages, Themes, Layouts, and Portlet Windows. It also manages the relationship between the user and the portal itself. The hierarchy of portal objects is depicted in the following diagram:
<mediaobject>
<imageobject>
@@ -34,43 +32,38 @@
<para>
A portal instance is
reachable by the url format
- <emphasis>http://[domain]/[context]/portal/[portal_name]</emphasis>. In a default/local install, the
+ <emphasis>http://<replaceable>[domain]</replaceable>/<replaceable>[context]</replaceable>/portal/<replaceable>[portal_name]</replaceable></emphasis>. In a default/local install, the
<emphasis>default</emphasis>
portal instance can be reached at
- <ulink url="http://localhost:8080/portal/portal/default">http://localhost:8080/portal/portal/default</ulink>
+ http://localhost:8080/portal/portal/default.Consult your portal administrator for information on the available portal instances - some of which may have restricted logins.
.
</para>
- <note>
- <para> Consult your portal administrator for information on the available portal instances - some of which may have restricted logins, not found in others.
- </para>
- </note>
-
</section>
- <section id="Portal_User_Guide-Portal_Concepts-Portal_Images">
+ <section id="Portal_User_Guide-Portal_Concepts-Portal_Pages">
<title>Pages</title>
<para>
- A Portal Page is an aggregator of Portlet Windows. It is generated by the portal, during the reponse phase. During this phase, the portal aggregates all of the HTML markup created the individual portlets, decorates them with window controls, and presents them to the user as a consolidated page.
+ A Portal Page is an aggregator of Portlet Windows. It is generated by the portal, during the response phase. During this phase, the portal aggregates all of the HTML markup created by the individual portlets, decorates them with window controls, and presents them to the user as a consolidated page.
</para>
<para>
A portal page is reachable by the url format
- <emphasis>http://[domain]/[context]/portal/[portal_name]/[page_name]</emphasis>. In a default/local install, the
+ <emphasis>http://<replaceable>[domain]</replaceable>/<replaceable>[context]</replaceable>/portal/<replaceable>[portal_name]</replaceable>/<replaceable>[page_name]</replaceable></emphasis>. In a default/local install, the
<emphasis>default</emphasis>
page can be reached at
- <ulink url="http://localhost:8080/portal/portal/default">
+
http://localhost:8080/portal/portal/default/default
- </ulink>
+
. Likewise, the News Page in a default install can be reached at
- <ulink url="http://localhost:8080/portal/portal/default/News">
+
http://localhost:8080/portal/portal/default/News
- </ulink>
+
</para>
<para>
More, on navigating the portal pages and what they contain can be found in,
- linkcommentedout <!-- <xref linkend="contents_pages"/> -->
+ <xref linkend="Portal_User_Guide-JBoss_Portal_Basics-Contents_Pages"/>
</para>
</section>
@@ -86,10 +79,10 @@
</imageobject>
</mediaobject>
- The diagram above, shows the default JBoss Portal page with certain window-related items highlighted (in red).
+ The diagram above shows the default JBoss Portal page with certain window-related items highlighted (in red).
Lets look at these items:
-
+ </para>
<itemizedlist>
<listitem>
<para>
@@ -112,56 +105,106 @@
will take on the page and how much markup will be shown.
<emphasis role="bold">Portlet Mode</emphasis> icons, on the other hand, control the mode in which
the portlet operates, thus impacting the type of generated markup. Note that not all portlets
- support all defined window states and/or portlet modes.
- <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Window State icons and their meaning:</emphasis>
- <itemizedlist>
- <listitem>
- <para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/intro/ico_16_normal.gif" format="GIF"/>
- </imageobject>
- </mediaobject>
- <emphasis role="bold">(Normal)</emphasis>
- - Normal window state, is the most common state for portlets (portlets in the
- above image are in the normal window state). The portlet window will occupy only
- enough space to show the portlet content on the page.
- </para>
- </listitem>
- <listitem>
- <para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/intro/ico_16_minimize.gif" format="GIF"/>
- </imageobject>
- </mediaobject>
- <emphasis role="bold">(Minimized)</emphasis>
- - The portlet is instructed to render minimal-to-no markup.
- </para>
- </listitem>
- <listitem>
- <para>
+ support all defined window states and/or portlet modes. The table below explains the different Window State icons and their meaning.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <table id="Table_1">
+ <title>Window state icons and their meaning</title>
+ <tgroup cols="3">
+ <colspec colname="c1" colnum="1" colwidth="1*"/>
+ <colspec colname="c2" colnum="2" colwidth="4*"/>
+ <colspec colname="c3" colnum="3" colwidth="4*"/>
+ <thead>
+ <row>
+ <entry>
+ Window State
+ </entry>
+ <entry>
+ Icon
+ </entry>
+ <entry>
+ Meaning
+ </entry>
+
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ Normal
+ </entry>
+ <entry>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/intro/ico_16_normal.gif" format="GIF"/>
+ </imageobject>
+ </mediaobject>
+ </entry>
+
+
+ <entry>
+ Normal window state, is the most common state for portlets (portlets in the
+ above image are in the normal window state). The portlet window will occupy only
+ enough space to show the portlet content on the page.
+ </entry>
+
+
+
+ </row>
+ <row>
+ <entry>
+ Minimized
+ </entry>
+ <entry>
<mediaobject>
<imageobject>
+ <imagedata fileref="images/intro/ico_16_minimize.gif" format="GIF"/>
+ </imageobject>
+ </mediaobject>
+ </entry>
+
+ <entry>
+ The portlet is instructed to render minimal-to-no markup.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Maximized
+ </entry>
+ <entry>
+ <mediaobject>
+ <imageobject>
<imagedata fileref="images/intro/ico_16_maximize.gif" format="GIF"/>
</imageobject>
</mediaobject>
- <emphasis role="bold">(Maximized)</emphasis>
- - The portlet window can occupy as much space of real estate on the page.
- </para>
- </listitem>
- </itemizedlist>
- </para>
- </listitem>
- <listitem>
+ </entry>
+
+ <entry>
+ The portlet window can occupy as much space of real estate on the page.
+ </entry>
+ </row>
+
+
+ </tbody>
+ </tgroup>
+ </table>
+
+
+
+
+
+
+
+
+
+
<para>
<emphasis role="bold">Portlet Modes and their meaning:</emphasis>
Portlet modes are not always available (it depends on the portlet support for a given mode).
Moreover, the Edit mode is only available to logged-in users, as in this mode, the portlet
preferences can be modified to be individually suited to a particular user's needs.
+ </para>
<itemizedlist>
<listitem>
<para>
@@ -185,8 +228,8 @@
<emphasis role="bold">(Return to View mode)</emphasis>
- The button labeled 'Cancel' is only visible when a user is logged in and the
portlet associated to the current window is in the Edit mode. This replaces the
- Edit button so the user understands that by clicking yhe user will leave the
- "Edit Mode" and reverting back to "View Mode". Portlets are by default in View
+ Edit button so the user understands that by clicking it the user will leave the
+ "Edit mode" and revert back to "View mode". Portlets are by default in View
mode.
</para>
</listitem>
@@ -197,19 +240,12 @@
<imagedata fileref="images/intro/ico_16_help.gif" format="GIF"/>
</imageobject>
</mediaobject>
- <emphasis role="bold">(Help)</emphasis>
- - Allows a user to access helpful information about the portlet, if it provides
- it (which is recommended).
+ <emphasis role="bold">Help</emphasis>
+ - Allows a user to access useful information about the portlet.
</para>
</listitem>
</itemizedlist>
- </para>
- </listitem>
- </itemizedlist>
- </para>
-</listitem>
-</itemizedlist>
-</para>
+
</section>
</section>
@@ -218,7 +254,7 @@
<title>Default Portal installation</title>
<para>
- This section will take a quick look at the default Portal installation and the pages and portlets that come
+ This section covers the default Portal installation and the pages and portlets that come
with it.
</para>
@@ -227,7 +263,7 @@
<para>
Three pages are available in the default Portal: Home, News and Weather. You can access pages either by
- entering the page URL in your browser location bar, as shown in linkcommentedout <!-- <xref linkend="intro_portal_pages"/> -->, or
+ entering the page URL in your browser location bar, as shown in <xref linkend="Portal_User_Guide-Portal_Concepts-Portal_Pages"/>, or
by clicking the tab associated to the page in the Navigation Tabs at the top of the page.
<mediaobject>
@@ -238,9 +274,9 @@
</para>
- <note>
+
<para>
- Navigation tabs support sub-page navigation as well. By hovering over a tab with child Pages, it will display a flyout menu for those subpages:
+ Although there are no pages with subpages in the default Portal installation, you can configure the navigation tabs to support sub-page navigation. By hovering over a tab with child Pages, it will display a menu for those subpages:
<mediaobject>
<imageobject>
@@ -248,12 +284,12 @@
</imageobject>
</mediaobject>
- There are no pages with subpages in the default Portal installation.</para>
- </note>
+ , .</para>
+
<para>
While you can use a Portal anonymously, it is much more interesting to do so while logged in, as you get the
opportunity to customize the content you want to see or even create your own personal Dashboard, as
- explained in linkcommentedout <!-- <xref linkend="dashboard"/> -->.
+ explained in <xref linkend="Portal_User_Guide-JBoss_Portal_Basics-Dashboard"/> .
</para>
</section>
@@ -262,7 +298,7 @@
<para>
Logging in to the portal is accomplished by clicking the
- <emphasis>Login</emphasis> link at the top-right of the portal page. Portal will present you with a logging
+ <emphasis>Login</emphasis> link at the top-right of the portal page. The portal will present you with a login
screen where you can enter your credentials:
<mediaobject>
@@ -312,7 +348,7 @@
</imageobject>
</mediaobject>
- Displays hard-coded links to downloading JBoss Portal, downloading portlets from <ulink url="http://www.portletswap.com">PortletSwap</ulink>, and the live online JBoss Portal demo. It also contains default authentication information on loging in, as well as a link to the official Portal documentation.
+ The Greetings Portlet displays hard-coded links to downloading JBoss Portal, downloading portlets from <ulink url="http://www.portletswap.com">PortletSwap</ulink>, and the live online JBoss Portal demo. It also contains default authentication information on logging in, as well as a link to the official Portal documentation.
</para>
</section>
@@ -321,7 +357,7 @@
<note>
<para>
- Administrators should view linkcommentedout <!-- <xref linkend="useradmin"/> --> for managing the portal user base. Only user
+ Administrators should view <xref linkend="Portal_User_Guide-User_Role-Managing_Users"/> for managing the portal user base. Only user
operations are covered in this section...</para>
</note>
<para>
@@ -333,7 +369,7 @@
</mediaobject>
</para>
<para>
- Once successfully logged in, the user will have additional functionality at his disposal, that
+ Once successfully logged in to the Identity User Portlet, the user will have additional functionality at their disposal, that
is covered in the following sections.
<mediaobject>
@@ -350,8 +386,8 @@
<emphasis role="bold">Create a new account</emphasis>
</para>
<para>
- Create a new account by clicking on the <emphasis>"Register"</emphasis>
- link in the navigation of the portlet, when not logged. A User can then fill in the necessary
+ Create a new account by clicking on the <emphasis>Register</emphasis>
+ link in the navigation of the portlet. A user can then fill in the necessary
information to create an account on the system:
<mediaobject>
<imageobject>
@@ -366,8 +402,8 @@
<emphasis role="bold">Lost password</emphasis>
</para>
<para>
- Already registered users can request a new password by clicking on the <emphasis>"Lost password"</emphasis> link
- in the navigation of the portlet. Therfore the user needs to fill in his user name to receive an e-mail with his new
+ Already registered users can request a new password by clicking on the <emphasis>Lost password</emphasis> link
+ in the navigation of the portlet. After entering your user name you will receive an e-mail with your new
login credentials.
</para>
<para>
@@ -384,15 +420,15 @@
<emphasis role="bold">View profile</emphasis>
</para>
<para>
- The default page after login is the view profile, which shows a summary of the most important properties of a user.
+ The default page after login is the view profile page. This page displays a summary of the most important properties of a user.
</para>
</listitem>
<listitem>
<para>
<emphasis role="bold">Edit personal information</emphasis>
</para>
- <para>A user has the ability to edit his personal information, change his password and e-mail address at any time by clicking on the
- <emphasis>"Edit profile"</emphasis> link, when logged in.
+ <para>A user has the ability to edit their personal information, change their password and e-mail address at any time by clicking on the
+ <emphasis>Edit profile</emphasis> link, when logged in.
</para>
</listitem>
</itemizedlist>
@@ -411,29 +447,29 @@
</imageobject>
</mediaobject>
- Portal includes a basic Content Management System (CMS). Portal provides a CMS portlet which allows users
+ Portal includes a basic Content Management System (CMS) portlet which allows users
to navigate the CMS content (static html, images, binary files, etc.).
</para>
<para>
- Displaying content is done by the portal using a path mapper. For example, if we wanted to display a zip
- file, located in <emphasis>/default/foo/bar.zip</emphasis>, we would type in the URL
+ Content is displayed through the portal using a path mapper. For example, if you wanted to display a zip
+ file, located in <emphasis>/default/foo/bar.zip</emphasis>, you would type in the URL
<emphasis>http://localhost:8080/content/default/foo/bar.zip</emphasis>.
- <emphasis
- role="bold">Notice how the path to the content, is prefixed with the '/content' term.</emphasis>
- Although in this example we are describing binary content retrieval, the same is to be said for text/html
+ Notice how the path to the content, is prefixed with the <emphasis
+ role="bold">/content</emphasis> term.
+ Although in this example we are describing binary content retrieval, the same can be said for text/html
files. Keep in mind, however, that binary files are displayed outside of the portal pages, but text/html
are displayed inside the CMSPortlet Window.
</para>
<para>
<emphasis role="bold">Serving Logic:</emphasis>
- The CMS Portlet now serves content based on the user's locale setting. For example: if a user's locale is
- set to Spanish in his browser, and he requests URL: default/index.html , the CMSPortlet will first try
+ The CMS Portlet now serves content based on the user's locale setting. For example, if a user's locale is
+ set to Spanish in their browser, and they request URL: default/index.html, the CMSPortlet will first try
and retrieve the Spanish version of that file. If a Spanish version is not found, it will then try and
retrieve the default language version set for the CMSPortlet (set to English, by default).
</para>
<note>
<para>
- Administrators should read linkcommentedout <!-- <xref linkend="admincmsPortlet"/> --> for managing the data in the CMS.
+ Administrators should read <xref linkend="Portal_User_Guide-Test-Administration_CMS_Portlet"/> for managing the data in the CMS.
</para>
</note>
</section>
@@ -443,37 +479,40 @@
<title>News Page</title>
<para>
- <mediaobject>
+ The News Page contains 2 portlets displaying news from common internet feeds. An open internet
+ connection on the server-side is therefore required for them to operate. <mediaobject>
+
<imageobject>
<imagedata fileref="images/intro/newspage.png" format="PNG" scalefit="1"/>
</imageobject>
</mediaobject>
- The News Page contains 2 portlets displaying news from common internet feeds. An open internet
- connection on the server-side is therefore required for them to operate. ;-)
+
</para>
<section id="Portal_User_Guide-News_Page-News_Portlet">
<title>News Portlet</title>
<para>
+ The News Portlet retrieves an RSS news feed from a URL and displays it as HTML to the user.
+
<mediaobject>
<imageobject>
<imagedata fileref="images/intro/newsportlet.png" format="PNG" scalefit="1"/>
</imageobject>
</mediaobject>
- The News Portlet retrieves an RSS news feed from a URL and displays it as HTML to the user.
+
</para>
<para>
- Additionally, a logged-in user is able to modify her preference in RSS feed source by using the
- Portlet's Edit Mode (click
+ Additionally, a logged-in user is able to modify their preference in RSS feed source by using the
+ Portlet's Edit Mode by clicking
<mediaobject>
<imageobject>
<imagedata fileref="images/intro/ico_edit.gif" format="GIF"/>
</imageobject>
</mediaobject>
- ). Once the form is submitted, this property will be saved
- in the user's preference, so she will always see the same news source, when logged in.
+ Once the form is submitted, this property will be saved
+ in the user's preference, so the user will always see the same news source when logged in.
<mediaobject>
<imageobject>
<imagedata fileref="images/intro/newsportlet_edit.png" format="PNG"/>
@@ -493,24 +532,26 @@
<title>Weather Page</title>
<para>
- This page contains a portlet displaying the weather forecast for a specific location.
+ This page contains a portlet that displays the weather forecast for a specific location.
</para>
<section id="Portal_User_Guide-Weather_Page-Weather_Portlet">
<title>Weather Portlet</title>
<para>
+ The Weather Portlet retrieves an RSS weather feed, based on a key (commonly a US Postal Code), and
+ displays it as HTML to the user.
+
<mediaobject>
<imageobject>
<imagedata fileref="images/intro/weatherportlet.gif" format="GIF"/>
</imageobject>
</mediaobject>
- The Weather Portlet retrieves an RSS weather feed, based on a key (commonly a US Postal Code), and
- displays it as HTML to the user.
+
</para>
<para>
- Additionally, a logged-in user is able to modify her preference in location by using the Portlet's Edit Mode (click
+ Additionally, a logged-in user is able to modify their location preference by using the Portlet's <emphasis role="bold">Edit Mode</emphasis> by clicking
<mediaobject>
<imageobject>
@@ -518,8 +559,8 @@
</imageobject>
</mediaobject>
- ). Any valid US Postal Code can be input here. Once the form is submitted, this property will be saved
- in the user's preference, so she will always see the same weather data for her location, when logged in.
+ Any valid US Postal Code can be input here. Once the form is submitted, this property will be saved
+ in the user's preference, so the user will always see the same weather data for their location when logged in.
<mediaobject>
<imageobject>
@@ -530,8 +571,7 @@
</para>
<para>
- <emphasis role="bold">Not in the United States?</emphasis>
- Follow these steps to configure the Weather portlet to display information for your area.
+ If you are not located in the United States you will need to configure the Weather portlet to display the information for your area.
<orderedlist>
<listitem>
<para>Go to
@@ -540,7 +580,7 @@
</listitem>
<listitem>
<para>
- Enter your city name in the location field, found on the page:
+ Enter your city name in the location field:
<mediaobject>
<imageobject>
<imagedata fileref="images/intro/weather_config1.png" format="PNG" align="center"
@@ -551,7 +591,7 @@
</listitem>
<listitem>
<para>
- Find your location on the list under the form and click on it (<emphasis>Marseille, France</emphasis>, in this case):
+ Find your location on the list under the <emphasis role="bold">Search Results</emphasis> and click on it (<emphasis>Marseille, France</emphasis>, in this case):
<mediaobject>
<imageobject>
@@ -577,7 +617,7 @@
</listitem>
<listitem>
<para>
- Paste these numbers in to the weather portlet edit form (<emphasis>FRXX0059</emphasis> in this case):
+ Paste these numbers into the weather portlet edit form (<emphasis>FRXX0059</emphasis> in this case):
<mediaobject>
<imageobject>
@@ -586,7 +626,7 @@
</imageobject>
</mediaobject>
- Hit <emphasis>submit</emphasis>...
+ Click on <emphasis>submit</emphasis>
<mediaobject>
<imageobject>
@@ -606,8 +646,8 @@
<title>Personal Dashboard</title>
<para>
- Once logged in, all users/administrations of the portal can access a personal dashboard by clicking the
- <emphasis>Dashboard</emphasis> link at the top-right of the portal page. Note how the links changed.
+ Once logged in, all users/administrators of the portal can access a personal dashboard by clicking the
+ <emphasis role="bold">Dashboard</emphasis> link at the top-right of the portal page. Note how the links changed.
<mediaobject>
<imageobject>
@@ -615,15 +655,14 @@
</imageobject>
</mediaobject>
- The personal dashboard allows users to customize their portal pages however they like, and all changes will be
- persisted... so the next time the user logs in to his dashboard, he will see the previous changes he made.
+ The personal dashboard allows users to customize their portal pages however they like. All changes will be
+ persisted so the next time the user logs in to their dashboard, the user will see the previous changes they made.
While navigating any of the dashboard pages, a user will be able to drag and drop portlet windows to any
location, if the administrator allows this functionality. Changes made in this fashion will also be persisted.
</para>
<para>
- It is also possible to copy the content of a shared page to your dashboard so you can customize it to your
- liking. Just click the <emphasis>'Copy to my dashboard'</emphasis> link at the top right of the page.
+ It is also possible to copy the content of a shared page to your dashboard so you can customize it to your liking. Just click the <emphasis role="bold">Copy to my dashboard</emphasis> link at the top right of the page.
This will clone the page and add it to your personal dashboard as a page with the same name.
<mediaobject>
@@ -638,7 +677,7 @@
<title>Configuring your personal dashboard</title>
<para>
- You can configure your dashboard by using the top-right menu item labeled <emphasis>'Configure dashboard'</emphasis>:
+ You can configure your dashboard by using the top-right menu item labeled <emphasis role="bold">'Configure dashboard'</emphasis>:
<mediaobject>
<imageobject>
@@ -677,8 +716,8 @@
</para>
<para>
You may delete dashboard pages at any time, by first selecting the page you want to delete using the
- popup menu at the top of the screen and then clicking the <emphasis>Delete this page</emphasis> button
- at the bottom of the screen. We will note that users are not able to delete the default dashboard page.
+ popup menu at the top of the screen and then clicking the <emphasis role="bold">Delete this page</emphasis> button
+ at the bottom of the screen. Users are not able to delete the default dashboard page.
<mediaobject>
<imageobject>
<imagedata fileref="images/intro/dashboard_deletepage.png" format="PNG" scalefit="1"/>
@@ -697,10 +736,10 @@
<title>Managing Portlets on a page</title>
<para>
- You can add, remove and reorder portlets on a dashboard page to adapt your environment to your liking.
- To do so, just select the page you want to modify using the page popup selector and use the portlet
+ You can add, remove and reorder portlets on a dashboard page to suit your specific requirements.
+ Select the page you want to modify by using the page popup selector and then the portlet
management form. We will not explain how to use it here as it is similar to the page layout functionality
- of the Admin portal, which we will look at in linkcommentedout <!-- <xref linkend="page_configuration"/> -->
+ of the Admin portal, which we will look at in <xref linkend="Portal_User_Guide-Managing_Portal_Objects-Page_configuration"/>
<mediaobject>
<imageobject>
@@ -716,28 +755,31 @@
<para>
- <note> <para>
- You <emphasis role="bold">must be</emphasis> logged in as an administrator, or have proper privileges
- to see this portal.</para>
- </note>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/intro/adminportal.png" format="PNG" scalefit="1"/>
- </imageobject>
- </mediaobject>
- The Admin Portal's purpose is to allow an administrator to manage all aspects of the portal. Follow the links for in-depth reviews of these functions:
- <itemizedlist>
+
+ The Admin Portal's purpose is to allow an administrator to manage all aspects of the portal. You <emphasis role="bold">must be</emphasis> logged in as an administrator, or have proper privileges
+ to see this portal.Follow the links for in-depth reviews of these functions:
+
+ <itemizedlist>
<listitem>
<para>
- Users/Roles (See: linkcommentedout <!-- <xref linkend="useradmin"/> -->, linkcommentedout <!-- <xref linkend="roleadmin"/> -->)</para></listitem>
- <listitem><para>Content Management System (See: linkcommentedout <!-- <xref linkend="admincmsPortlet"/> -->)</para></listitem>
+ Users/Roles (See: <xref linkend="Portal_User_Guide-User_Role-Managing_Users"/>
+
+ <xref linkend="Portal_User_Guide-User_Role-Managing_Roles"/></para></listitem>
+ <listitem><para>Content Management System (See: <xref linkend="Portal_User_Guide-Test-Administration_CMS_Portlet"/> </para></listitem>
<listitem><para>Portal Objects (themes, layouts, portal instances, pages, windows, security, and deployed
- portlets) (See: linkcommentedout <!-- <xref linkend="dynamicity"/> -->)</para></listitem>
+ portlets) (See: <xref linkend="Portal_User_Guide-Dynamicity"/> </para></listitem>
<listitem><para>WSRP (See the
<ulink url="http://docs.jboss.com/jbportal/v2.6/reference-guide/en/html/wsrp.html">WSRP chapter</ulink>
in the Reference Guide for more information)</para>
</listitem>
</itemizedlist>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/intro/adminportal.png" format="PNG" scalefit="1"/>
+ </imageobject>
+ </mediaobject>
+
+
</para>
Modified: docs/enterprise/trunk/UserGuide/en-US/Portal_User_Guide.ent
===================================================================
--- docs/enterprise/trunk/UserGuide/en-US/Portal_User_Guide.ent 2008-12-03 05:04:12 UTC (rev 12331)
+++ docs/enterprise/trunk/UserGuide/en-US/Portal_User_Guide.ent 2008-12-03 05:07:04 UTC (rev 12332)
@@ -1,5 +1,5 @@
<!ENTITY PRODUCT "Documentation">
<!ENTITY BOOKID "Portal_User_Guide">
<!ENTITY YEAR "2008">
-<!ENTITY HOLDER "YOUR NAME GOES HERE 'Portal_User_Guide.ent'">
+<!ENTITY HOLDER "Red Hat">
Modified: docs/enterprise/trunk/UserGuide/en-US/Portal_User_Guide.xml
===================================================================
--- docs/enterprise/trunk/UserGuide/en-US/Portal_User_Guide.xml 2008-12-03 05:04:12 UTC (rev 12331)
+++ docs/enterprise/trunk/UserGuide/en-US/Portal_User_Guide.xml 2008-12-03 05:07:04 UTC (rev 12332)
@@ -10,6 +10,6 @@
<xi:include href="Administration_CMS_Portlet.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="User_Role.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
- <index />
+
</book>
Modified: docs/enterprise/trunk/UserGuide/en-US/Revision_History.xml
===================================================================
--- docs/enterprise/trunk/UserGuide/en-US/Revision_History.xml 2008-12-03 05:04:12 UTC (rev 12331)
+++ docs/enterprise/trunk/UserGuide/en-US/Revision_History.xml 2008-12-03 05:07:04 UTC (rev 12332)
@@ -10,9 +10,9 @@
<revnumber>1.0</revnumber>
<date></date>
<author>
- <firstname></firstname>
- <surname></surname>
- <email></email>
+ <firstname>Sarah</firstname>
+ <surname>Meehan</surname>
+ <email>smeehan(a)redhat.com</email>
</author>
<revdescription>
<simplelist>
Modified: docs/enterprise/trunk/UserGuide/en-US/User_Role.xml
===================================================================
--- docs/enterprise/trunk/UserGuide/en-US/User_Role.xml 2008-12-03 05:04:12 UTC (rev 12331)
+++ docs/enterprise/trunk/UserGuide/en-US/User_Role.xml 2008-12-03 05:07:04 UTC (rev 12332)
@@ -7,8 +7,8 @@
<para>
This chapter covers the administrator functions made available by the User management portlet. For end-user operation, see:
- linkcommentedout <!-- <xref linkend="intro_user_portlet"/> -->. Administrative functions are available once you are logged in with the proper
- credentials (admin/admin), then going to the linkcommentedout <!-- <xref linkend="adminportal"/> --> and then the Members Page tab. You can change between
+ <xref linkend="Portal_User_Guide-Home_Page-Intro_user_portlet"/>. Administrative functions are available once you are logged in with the proper
+ credentials (admin/admin), then going to the <xref linkend="Portal_User_Guide-JBoss_Portal_Basics-Admin_Portal"/> and then the Members Page tab. You can change between
user and role management by clicking on the corresponding links in the top of the portlet.
</para>
@@ -19,7 +19,7 @@
<para>
This section covers the user management of the IdentityUserManagementPortlet which is displayed by default.
- For role management please see linkcommentedout <!-- <xref linkend="roleadmin"/> -->.
+ For role management please see <xref linkend="Portal_User_Guide-User_Role-Managing_Roles"/>.
<mediaobject>
<imageobject>
@@ -27,7 +27,7 @@
</imageobject>
<caption>
<para>
- The Members page in the linkcommentedout <!-- <xref linkend="adminportal"/> -->.
+ The Members page in the <xref linkend="Portal_User_Guide-JBoss_Portal_Basics-Admin_Portal"/>.
</para>
</caption>
</mediaobject>
@@ -56,7 +56,7 @@
<section id="Portal_User_Guide-Actions-Searching_for_Users">
<title>Searching for Users</title>
<para>
- For searching users click on the link <emphasis>Search users</emphasis> and then type a partial username in the form text field, to search for usernames matching that
+ To search for a user click on the link <emphasis role="bold">Search users</emphasis> and then type a partial username in the form text field. This will search for usernames that match that
criteria.
<mediaobject>
@@ -204,7 +204,7 @@
</section>
<section id="Portal_User_Guide-Managing_Roles-Actions">
- <title>Introduction</title>
+ <title>Actions</title>
<para>
The User management portlet also provides several actions related to role management, which are described in the following sections.
@@ -239,12 +239,33 @@
security rules.
</para>
</section>
+
+
+<section id="Portal_User_Guide-Actions-Edit_Role">
+ <title>Edit a role</title>
+ <para>
+ Editing roles is accomplished by clicking on <emphasis>Edit role</emphasis> in the row of the role you want to edit.
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/role/edit_role.png" format="PNG" scalefit="1"/>
+ </imageobject>
+ <caption>
+ <para>
+ Edit an existing role.
+ </para>
+ </caption>
+ </mediaobject>
+ While editing a role, you just need to pick an existing role then change the display name.
+ </para>
+</section>
+
+
<section id="Portal_User_Guide-Actions-Editing_Role_Members">
<title>Editing Role Members</title>
<para>
- Editing role members, is accomplished by first clicking the
+ Editing role members is accomplished by first clicking the
<emphasis>Members</emphasis>
link at the role management page for the role you would like to modify.
17 years, 5 months
- 1
- 0
JBoss Portal SVN: r12331 - in docs/enterprise/trunk/Installation_Guide/en-US: images and 1 other directory.
by portal-commits＠lists.jboss.org
Author: sradvan
Date: 2008-12-03 00:04:12 -0500 (Wed, 03 Dec 2008)
New Revision: 12331
Added:
docs/enterprise/trunk/Installation_Guide/en-US/Author_Group.xml
docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml
docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml
docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml
docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml
docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml
docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide_CP03.ent
docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide_CP03.xml
docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml
docs/enterprise/trunk/Installation_Guide/en-US/Post_Installation.xml
docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml
docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml
docs/enterprise/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml
docs/enterprise/trunk/Installation_Guide/en-US/images/
docs/enterprise/trunk/Installation_Guide/en-US/images/step3.png
docs/enterprise/trunk/Installation_Guide/en-US/images/step4.png
docs/enterprise/trunk/Installation_Guide/en-US/images/step8.png
docs/enterprise/trunk/Installation_Guide/en-US/images/test_install.png
docs/enterprise/trunk/Installation_Guide/en-US/images/title.jpg
docs/enterprise/trunk/Installation_Guide/en-US/images/uninstall.png
Log:
merging EPP guide info to EAP install guide
Added: docs/enterprise/trunk/Installation_Guide/en-US/Author_Group.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Author_Group.xml (rev 0)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Author_Group.xml 2008-12-03 05:04:12 UTC (rev 12331)
@@ -0,0 +1,10 @@
+<?xml version='1.0'?>
+<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<authorgroup>
+<author>
+ <firstname>Red Hat Documentation Group</firstname>
+ <surname></surname>
+ </author>
+</authorgroup>
Added: docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml (rev 0)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml 2008-12-03 05:04:12 UTC (rev 12331)
@@ -0,0 +1,31 @@
+<?xml version='1.0'?>
+<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+]>
+
+<bookinfo id="Installation_Guide_JBoss_Enterprise_Application_Platform">
+ <title>Installation Guide CP03</title>
+ <subtitle>For use with JBoss Enterprise Application Platform 4.3 Cumulative Patch 3</subtitle>
+ <edition>2.0</edition>
+ <pubsnumber>4</pubsnumber>
+ <productname>JBoss Enterprise Application Platform</productname>
+ <productnumber>4.3</productnumber>
+ <pubdate>Dec, 2008</pubdate>
+ <isbn>N/A</isbn>
+ <abstract><para>This Installation Guide documents relevant information regarding
+the installation of JBoss Enterprise Application Platform</para>
+ </abstract>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="Common_Content/images/redhat-logo.svg" />
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <copyright>
+ <year>&YEAR;</year>
+ <holder>&HOLDER;</holder>
+ </copyright>
+ <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</bookinfo>
+
Added: docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml (rev 0)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml 2008-12-03 05:04:12 UTC (rev 12331)
@@ -0,0 +1,55 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<chapter>
+ <title>Database Configuration</title>
+
+ <section id="sect-Portal_EAP-Configuration-Installing_an_RDBMS_JDBC_connector">
+ <title>Installing an RDBMS JDBC connector</title>
+ <para>
+ A relational database management system (RDBMS) Java Database Connectivity (JDBC) connector is required for JBoss Portal to communicate with a database. Test suites have been run against the <trademark class="registered">Oracle</trademark> 9, <trademark class="registered">Oracle</trademark> 10, <trademark class="registered">Microsoft SQL Server</trademark>, MySQL 4, MySQL 5, and PostgreSQL 8 databases - these databases are recommended for production use. Please refer to your database documentation for the correct RDBMS JDBC connector. The MySQL RDBMS JDBC connector can be downloaded from <ulink url="http://www.mysql.com/products/connector/j/"></ulink>, and the PostgreSQL RDBMS JDBC connector can be downloaded from <ulink url="http://jdbc.postgresql.org/download.html"></ulink>.
+ </para>
+ <para>
+ Refer to the help files in each download for installation instructions. In most cases, the RDBMS JDBC connector comes as a <computeroutput>.jar</computeroutput> file. Copy this file into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/lib/</filename> directory.
+ </para>
+ </section>
+
+ <section id="sect-Portal_EAP-Configuration-Datasource_Descriptors">
+ <title>Datasource Descriptors</title>
+ <para>
+ A Datasource descriptor is required for JBoss Portal to communicate with a database. Sample Datasource descriptor files are provided for the Hypersonic SQL, <trademark class="registered">Microsoft SQL Server</trademark>, MySQL, <trademark class="registered">Oracle</trademark>, and PostgreSQL databases. These can be found in the <filename>setup/</filename> subdirectory where the <computeroutput>JBoss Portal <replaceable>x.x.x</replaceable> binary distribution</computeroutput> file was extracted to. For example, if JBoss Portal was extracted into the <filename>/jboss/</filename> directory, the sample Datasource descriptors would be in the <filename>/jboss/jboss-portal-<replaceable>x.x.x</replaceable>/setup/</filename> directory.
+ </para>
+ <para>
+ The sample Datasource descriptors will work with default installations of external databases; however, you may need to configure the correct username and password. As well, the sample MySQL and PostgreSQL Datasource descriptors assume the name of the database to be <computeroutput>jbossportal</computeroutput>.
+ </para>
+ <para>
+ When copying a Datasource descriptor for MySQL, <trademark class="registered">Microsoft SQL Server</trademark>, PostgreSQL, or <trademark class="registered">Oracle</trademark> databases, change the <computeroutput><user-name><replaceable>portal</replaceable></user-name></computeroutput> and <computeroutput><password><replaceable>portalpassword</replaceable></password></computeroutput> sections to reflect the correct username and password for the user who has access to the jbossportal database.
+ </para>
+ <important>
+ <title>Different Datasource Descriptors</title>
+ <para>
+ Only have one Datasource descriptor in the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory. For example, if you want to use a MySQL database, remove the <filename>portal-hsqldb-ds.xml</filename> file, and other descriptors, if they exists.
+ </para>
+ </important>
+ <para>
+ The following is an example Datasource descriptor file for MySQL 5:
+ </para>
+ <para>
+<screen>
+<?xml version="1.0" encoding="UTF-8"?>
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>PortalDS</jndi-name>
+ <connection-url>jdbc:mysql://localhost:3306/jbossportal?
+ useServerPrepStmts=false&amp;jdbcCompliantTruncation=false</connection-url>
+ <driver-class>com.mysql.jdbc.Driver</driver-class>
+ <user-name><replaceable>portal</replaceable></user-name>
+ <password><replaceable>portalpassword</replaceable></password>
+ </local-tx-datasource>
+</datasources>
+</screen>
+ </para>
+ </section>
+
+</chapter>
+
Added: docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml (rev 0)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml 2008-12-03 05:04:12 UTC (rev 12331)
@@ -0,0 +1,196 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<chapter id="chap-Portal_EAP-Databases">
+ <title>Databases</title>
+ <para>
+ The following chapter contains examples for how to use the Hypersonic SQL and MySQL databases to store JBoss Portal user information.
+ </para>
+ <section id="sect-Portal_EAP-Databases-Using_a_Hypersonic_SQL_Database">
+ <title>Using a Hypersonic SQL Database</title>
+ <para>
+ JBoss EAP contains an embedded <ulink url="http://hsqldb.org/">Hypersonic SQL</ulink> database instance. After starting JBoss EAP and deploying JBoss portal for the first time, the Hypersonic SQL database is created in the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/data/</filename> directory. This directory will not exist until after starting JBoss EAP and deploying JBoss Portal. The Hypersonic SQL database is used by default, but is only recommended for developer use.
+ </para>
+ <para>
+ To use the Hypersonic SQL database, change into the <filename>setup/</filename> subdirectory where JBoss Portal was extracted to. Copy the <filename>portal-hsqldb-ds.xml</filename> file into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory. Alternatively, copy and save the following example as <filename>portal-hsqldb-ds.xml</filename> into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory:
+ </para>
+ <para>
+<screen>
+<?xml version="1.0" encoding="UTF-8"?>
+<datasources>
+ <local-tx-datasource>
+ <jndi-name>PortalDS</jndi-name>
+ <connection-url>jdbc:hsqldb:${jboss.server.data.dir}$
+ {/}portal${/}hypersonic${/}database</connection-url>
+ <driver-class>org.hsqldb.jdbcDriver</driver-class>
+ <user-name>sa</user-name>
+ <password><![CDATA[]]></password>
+ </local-tx-datasource>
+</datasources>
+</screen>
+ </para>
+ </section>
+
+ <section id="sect-Portal_EAP-Databases-Using_a_MySQL_Database">
+ <title>Using a MySQL Database</title>
+ <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-Installing_the_MySQL_RDBMS_JDBC_connector">
+ <title>Installing the MySQL RDBMS JDBC connector</title>
+ <para>
+ The RDBMS JDBC MySQL connector is required for JBoss Portal to use a MySQL database:
+ </para>
+ </formalpara>
+ <orderedlist>
+ <listitem>
+ <para>
+ Navigate to the <ulink url="http://dev.mysql.com/downloads/connector/j/3.1.html">JDBC MySQL connector</ulink> section of dev.mysql.com. Download the <computeroutput>Source and Binaries (zip)</computeroutput> file.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Unzip the <filename>mysql-java-connector</filename> into the desired directory. It does not matter which directory is used.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Change into the directory where the <filename>mysql-java-connector</filename> was extracted to. Copy the <filename>mysql-connector-java-<replaceable>version-number</replaceable>-bin.jar</filename> file into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/lib/</filename> directory.
+ </para>
+ </listitem>
+ </orderedlist>
+ <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-Data_Truncation_Errors">
+ <title>Data Truncation Errors</title>
+ <para>
+ If you are running MySQL 5, data truncation errors such as the following may occur:
+ </para>
+ </formalpara>
+ <para>
+<screen>
+ERROR JDBCExceptionReporter Data truncation: Data too long for column 'jbp_viewrealemail' at row 1
+</screen>
+ </para>
+ <para>
+ If you are running MySQL in strict mode, remove <computeroutput>STRICT_TRANS_TABLES</computeroutput> from the <computeroutput>sql-mode=</computeroutput> line, in the <filename>my.cnf</filename> file if you are running Linux, and from the <filename>my.cfg</filename> file if you are running <trademark class="registered">Windows</trademark>. For further information, please see <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=AvoidMySQL5DataTruncationErrors"></ulink>.
+ </para>
+ <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-Creating_a_MySQL_Database">
+ <title>Creating a MySQL Database</title>
+ <para>
+ If you have just installed MySQL, make sure the MySQL server is running, and then run the following command to set the root user password:
+ </para>
+ </formalpara>
+ <para>
+<screen>
+mysqladmin -u root password '<replaceable>new-root-user-password</replaceable>'
+</screen>
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ Run the following command to log in to MySQL. Enter the root user password when prompted:
+ </para>
+ <para>
+<screen>
+mysql -u root -p
+</screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use the <command>CREATE DATABASE</command> command to create a new jbossportal database. Note: the rest of this guide, and configuration examples following here after, assume the database name to be jbossportal. If you change the database name, please change the name in all necessary configuration files:
+ </para>
+ <para>
+<screen>
+mysql> CREATE DATABASE jbossportal;
+</screen>
+ </para>
+ <para>
+ The output should be similar to the following:
+ </para>
+ <para>
+<screen>
+Query OK, 1 row affected (0.00 sec)
+</screen>
+ </para>
+ <para>
+ At this point, the <command>SHOW DATABASES;</command> command should display the <command>jbossportal</command> database:
+ </para>
+ <para>
+<screen>
+mysql> SHOW DATABASES;
++--------------------+
+| Database |
++--------------------+
+| information_schema |
+| jbossportal |
+| mysql |
++--------------------+
+3 rows in set (0.00 sec)
+</screen>
+ </para>
+ <para>
+ It is safe to ignore the other databases.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Add a new user and give that user access to the jbossportal database. The following example adds a new user named <computeroutput>portal</computeroutput>, with the password <computeroutput>portalpassword</computeroutput>, and gives the portal user access to the jbossportal database. It is recommended that you change the password. Change <replaceable>portalpassword</replaceable> to change the password:
+ </para>
+ <para>
+<screen>
+mysql> GRANT ALL PRIVILEGES ON jbossportal.* TO '<replaceable>portal</replaceable>'@'localhost'
+IDENTIFIED BY '<replaceable>portalpassword</replaceable>' WITH GRANT OPTION;
+</screen>
+ </para>
+ <para>
+ The output should be similar to the following:
+ </para>
+ <para>
+<screen>
+Query OK, 0 rows affected (0.00 sec)
+</screen>
+ </para>
+ <para>
+ If you changed the portal user's password, also change the password in the MySQL Datasource descriptor.
+ </para>
+ </listitem>
+ </orderedlist>
+ <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-MySQL_Datasource_Descriptor">
+ <title>MySQL Datasource Descriptor</title>
+ <para>
+ To install the MySQL Datasource descriptor:
+ </para>
+ </formalpara>
+ <orderedlist>
+ <listitem>
+ <para>
+ Change into the <filename>setup</filename> subdirectory where JBoss Portal was extracted to. Copy the MySQL Datasource descriptor into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory. If you are running MySQL 5, use <filename>portal-mysql5-ds.xml</filename>, otherwise use <filename>portal-mysql-ds.xml</filename>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Update the <computeroutput><user-name><replaceable>portal</replaceable></user-name></computeroutput> and <computeroutput><password><replaceable>portalpassword</replaceable></password></computeroutput> sections in the Datasource descriptor to reflect the correct username and password for the user who has access to the jbossportal database.
+ </para>
+ </listitem>
+ </orderedlist>
+ <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-MySQL_Table_Errors">
+ <title>MySQL Table Errors</title>
+ <para>
+ Tables are set up automatically when JBoss Portal first starts. Initially, two users will be stored in the jbossportal MySQL database: a standard user with the username user, and the password user, and an administrative user with the username admin, and the password admin. Since the database tables are created during initial startup, errors such as the following may occur, but are safe to ignore:
+ </para>
+ </formalpara>
+ <para>
+<screen>
+WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
+ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_repositoryentry' doesn't exist
+WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
+ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_version_refs' doesn't exist
+WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
+ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_wsp_node' doesn't exist
+WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
+ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_cmsentry' doesn't exist
+WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
+</screen>
+ </para>
+ </section>
+
+</chapter>
+
Added: docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml (rev 0)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Getting_Started.xml 2008-12-03 05:04:12 UTC (rev 12331)
@@ -0,0 +1,593 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+]>
+
+<chapter id="Getting_Started">
+ <title>Getting Started</title>
+ <section id="Getting_Started-Pre_Requisites">
+ <title>Pre-Requisites</title>
+ <para>
+ You must have adequate disk space<!--TODO how much --> to install JDK and &JBEAP; while also allowing enough space for your applications. Before installing &JBEAP; you must have a working installation of Java. Since JBoss is 100% pure Java you can have it working on any Operating System / Platform that supports Java. However, there are a few Operating System-specific issues that you should be aware of. Refer to <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossOperatingSystemSpecificIssues"></ulink> for more information.
+ </para>
+ <section id="Pre_Requisites-Hardware_and_Operating_System_Requirements">
+ <title>Hardware and Operating System Requirements</title>
+
+ <para>For the latest information on supported Operating System / JVM combinations and supported Database platforms, please refer to <ulink url="http://www.jboss.com/products/platforms/application/testedconfigurations">http://www.jboss.com/products/platforms/application/testedconfigurations</ulink>.
+ </para>
+ <!-- <para>
+ The following is a list of supported operating systems and JVM version combination:
+ </para>
+
+ <table>
+ <title>
+ Supported Operating System / JVM Combinations.
+ </title>
+ <tgroup cols="2">
+ <colspec colnum="1" colname="OS" colwidth="1*"></colspec>
+ <colspec colnum="2" colname="JVM" colwidth="1*"></colspec>
+ <tbody>
+ <row>
+ <entry>
+ <emphasis>Operating System</emphasis>
+ </entry>
+ <entry>
+ <emphasis>JVM Version</emphasis>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ RHEL 4.5 x86
+ </entry>
+ <entry>
+ Sun JVM 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ RHEL 4.5 x86_64
+ </entry>
+ <entry>
+ Sun JVM 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ RHEL 5 x86
+ </entry>
+ <entry>
+ Sun JVM 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ RHEL 5 x86_64
+ </entry>
+ <entry>
+ Sun JVM 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ RHEL 4.5 x86
+ </entry>
+ <entry>
+ BEA JRockit 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ RHEL 4.5 x86_64
+ </entry>
+ <entry>
+ BEA JRockit 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ RHEL 5 x86
+ </entry>
+ <entry>
+ BEA JRockit 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ RHEL 5 x86_64
+ </entry>
+ <entry>
+ BEA JRockit 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Solaris SPARC 9
+ </entry>
+ <entry>
+ Sun JVM 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ MS-Windows 2003 x86
+ </entry>
+ <entry>
+ Sun JVM 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ MS-Windows 2003 x86_64
+ </entry>
+ <entry>
+ Sun JVM 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ MS-Windows 2003 x86
+ </entry>
+ <entry>
+ BEA JRockit 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ MS-Windows 2003 x86_64
+ </entry>
+ <entry>
+ BEA JRockit 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Solaris SPARC 10
+ </entry>
+ <entry>
+ Sun JVM 1.5 latest
+ </entry>
+ </row>
+ <row>
+ <entry>
+ HP 11i 1,2 RISC
+ </entry>
+ <entry>
+ HP JVM
+ </entry>
+ </row>
+ <row>
+ <entry>
+ HP 11i, 1,2 ia64
+ </entry>
+ <entry>
+ HP JVM
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <para>
+ The following is a list of supported databases and database drivers:
+ </para>
+
+ <table>
+ <title>
+ Supported Database / Database driver Combinations.
+ </title>
+
+ <tgroup cols="2">
+ <colspec colnum="1" colname="DB" colwidth="1*"></colspec>
+ <colspec colnum="2" colname="DB_driver" colwidth="1*"></colspec>
+ <tbody>
+ <row>
+ <entry>
+ <emphasis>Database</emphasis>
+ </entry>
+ <entry>
+ <emphasis>Database driver</emphasis>
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Oracle 9i
+ </entry>
+ <entry>
+ Oracle thin driver
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Oracle 10g R2
+ </entry>
+ <entry>
+ Oracle thin driver
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Microsoft SQL Server 2005
+ </entry>
+ <entry>
+ Microsoft JDBC Driver
+ </entry>
+ </row>
+ <row>
+ <entry>
+ MySQL 5.0
+ </entry>
+ <entry>
+ MySQL Driver
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Postgres SQL 8.1
+ </entry>
+ <entry>
+ Postgres Driver
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <note>
+ <para>
+ JBoss uses an embedded Tomcat and does not require a stand-alone Tomcat.
+ </para>
+ </note> -->
+ </section>
+
+ <section id="Pre_Requisites-Configuring_Your_Java_Environment">
+ <title>Configuring Your Java Environment</title>
+ <para>
+ You must have a working installation of <emphasis role="bold">JDK 1.5</emphasis> before you install &JBEAP;. You can install the 32-bit or 64-bit JVM as per your requirements. In this guide we will show you how to install a 32-bit Sun JDK 5.0 using RHN, on a generic Linux Platform and Microsoft Windows Platform. But before we do that let's take a look at some of the benefits of using a 64-bit JVM.
+ <itemizedlist id="Configuring_Your_Java_Environment-Benefits_of_64_bit_JVM_on_64_bit_OS_and_Hardware">
+ <title>Benefits of 64-bit JVM on 64-bit OS and Hardware:</title>
+ <listitem>
+ <para>
+ Wider datapath: The pipe between RAM and CPU is doubled, which improves the performance of memory-bound applications.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 64-bit memory addressing gives virtually unlimited (1 exabyte) heap allocation. However large heaps affect garbage collection.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Applications that run with more than 1.5GB of RAM (including free space for garbage collection optimization) should utilize the 64-bit JVM.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Applications that run on a 32-bit JVM and do not require more than minimal heap sizes will gain nothing from a 64-bit JVM. Barring memory issues, 64-bit hardware with the same relative clock speed and architecture is not likely to run Java applications faster than their 32-bit cousin.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_using_RHN">
+ <title>Installing and Configuring 32-bit Sun JDK 5.0 using RHN</title>
+ <listitem>
+ <para>
+ Java SDKs are provided by the Red Hat Enterprise Linux 5 Supplementary channel for your Linux variant and architecture. Depending on the architecture, the channel names are:
+ </para>
+ <para>
+ rhel-i386-server-supplementary-5 and rhel-x86_64-server-supplementary-5
+ </para>
+ <para>
+ The <command moreinfo="none">java-1.5.0-bea</command>,
+ <command moreinfo="none">java-1.5.0-ibm</command> and
+ <command moreinfo="none">java-1.5.0-sun</command> SDKs are available from
+ these channels. Make sure you also install the
+ <command moreinfo="none">-devel</command> subpackages.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Selecting <command moreinfo="none">alternatives</command> for <command moreinfo="none">java</command>, <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.5.0</command> (setting <command moreinfo="none">java_sdk_1.5.0</command> is optional).
+ </para>
+
+ <para>
+ This is only needed if you want to use the SysV service script
+ and/or want this installed SDK to be the default java and javac
+ in the system. This choice can often be overridden by setting
+ the <command moreinfo="none">JAVA_HOME</command> environment variable.
+ </para>
+
+ <para>
+ The <command moreinfo="none">alternatives</command> system allows different versions of Java, from different sources, to co-exist on your system. You should make sure the desired one is selected so that the service script uses the one you want.
+ </para>
+
+ <para>
+ As root, issue the following command:
+ </para>
+ <screen>
+ <command moreinfo="none">/usr/sbin/alternatives --config java</command>
+ </screen>
+ <para>
+ and make sure the desired one is selected (marked with a '+'), or select it by entering its number as prompted.
+ </para>
+
+ <para>
+ Make sure you do the same for <command moreinfo="none">javac</command> and <command moreinfo="none">java_sdk_1.5.0.</command> We recommend that all point to the same manufacturer and version.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_on_a_generic_Linux_platform">
+ <title>Installing and Configuring 32-bit Sun JDK 5.0 on a generic Linux platform</title>
+ <listitem>
+ <para>
+ Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp"></ulink>. Choose "JDK 5.0 Update <x>" (where x is the latest update number) for download and then select "RPM in self-extracting" file for Linux<footnote><para>Make sure you choose the appropriate file for your platform.</para></footnote>. Read the instructions on Sun's website for installing the JDK.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If you don't want to use SysV service scripts you can install the "self-extracting file" for Linux instead of choosing the "RPM in self-extracting" file. In that case you can skip the next step mentioned here. But it is recommended to use the SysV service scripts for production servers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Download and install the appropriate <literal>-compat RPM</literal> from <literal>JPackage</literal> <ulink url="ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-free/"> here</ulink>.
+
+Please ensure you choose a matching version of the <literal>-compat</literal> package to the JDK you installed.
+
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Create an environment variable that points to the JDK installation directory and call it <literal>JAVA_HOME</literal>. Add <literal>$JAVA_HOME/bin</literal> to the system path to be able to run <literal>java</literal> from the command line. You can do this by adding the following lines to the <filename>.bashrc</filename> file in your home directory. <programlisting>
+#In this example /usr/java/jdk1.5.0_11 is the JDK installation directory.
+export JAVA_HOME=/usr/java/jdk1.5.0_11
+export PATH=$PATH:$JAVA_HOME/bin
+</programlisting>
+ Set this variable for the user account doing the installation and also for the user account that will run the server.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If you have more than one version of JVM installed in your machine, make sure you are using the JDK1.5 installation as the default <literal>java</literal> and <literal>javac</literal>. You can do this using the alternatives system. The alternatives system allows different versions of Java, from different sources to co-exist on your system.
+ <itemizedlist>
+ <title>Select alternatives for java, javac and java_sdk_1.5.0</title>
+ <listitem>
+ <para>
+ As root, type the following command at the shell prompt and you should see something like this: <programlisting>
+[root@vsr ~]$ /usr/sbin/alternatives --config java
+There are 2 programs which provide 'java'.
+Selection Command
+-----------------------------------------------
+ 1 /usr/lib/jvm/jre-1.4.2-gcj/bin/java
+*+ 2 /usr/lib/jvm/jre-1.5.0-sun/bin/java
+Enter to keep the current selection[+], or type selection number:
+</programlisting>
+ Make sure the Sun version [<literal>jre-1.5.0-sun</literal> in this case] is selected (marked with a '+' in the output), or select it by entering its number as prompted.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Repeat the same for javac and java_sdk_1.5.0. <programlisting>
+[root@vsr ~]$ /usr/sbin/alternatives --config javac
+There are 1 programs which provide 'javac'.
+ Selection Command
+-----------------------------------------------
+*+ 1 /usr/lib/jvm/java-1.5.0-sun/bin/javac
+Enter to keep the current selection[+], or type selection number:
+</programlisting>
+<programlisting>
+[root@vsr ~]$ /usr/sbin/alternatives --config java_sdk_1.5.0
+There are 1 programs which provide 'java_sdk_1.5.0'.
+ Selection Command
+-----------------------------------------------
+*+ 1 /usr/lib/jvm/java-1.5.0-sun
+Enter to keep the current selection[+], or type selection number:
+</programlisting>
+ You should verify that java, javac and java_sdk_1.5.0 all point to the same manufacturer and version.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <note>
+ <para>
+ You can always override this step by setting the <literal>JAVA_HOME</literal> environment variable as explained in the previous step.
+ </para>
+ </note>
+ </listitem>
+ <listitem>
+ <para>
+ Make sure that the <literal>java</literal> executable is in your path and that you are using an appropriate version. To verify your Java environment, type <literal>java -version</literal> at the shell prompt and you should see something like this: <programlisting>
+[root@vsr ~]$ java -version
+java version "1.5.0_11"
+Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
+Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)
+</programlisting>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist id="Configuring_Your_Java_Environment-Installing_and_Configuring_32_bit_Sun_JDK_5.0_on_Microsoft_Windows">
+ <title>Installing and Configuring 32-bit Sun JDK 5.0 on Microsoft Windows</title>
+ <listitem>
+ <para>
+ Download the Sun JDK 5.0 (Java 2 Development Kit) from Sun's website: <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp"></ulink>. Choose "JDK 5.0 Update <x>" (where x is the latest update number) for download and then select your Windows Platform options to perform the installation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Create an environment variable called <literal>JAVA_HOME</literal> that points to the JDK installation directory, for example: <literal>C:\Program Files\Java\jdk1.5.0_11\</literal>. In order to run java from the command line add the <literal>jre\bin</literal> directory to your path, for example: <literal>C:\Program Files\Java\jdk1.5.0_11\jre\bin</literal>. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </section>
+
+ </section>
+
+ <section id="Getting_Started-Components_of_JBoss_Enterprise_Application_Platform">
+ <title>Components of &JBEAP;</title>
+
+ <para>For current information on the revision level of included components please refer to <ulink url="http://www.jboss.com/products/platforms/application/components">http://www.jboss.com/products/platforms/application/components</ulink>.
+ </para>
+
+ <!--<para>
+ Below is a listing of the components of &JBEAP; and their revision level at the time of writing. For an updated list of component revision levels please refer to <ulink url="http://www.redhat.com/docs/manuals/jboss">http://www.redhat.com/docs/manuals/jboss</ulink>.
+ </para>
+
+ <para>
+ <table id="Components_of_JBoss_Enterprise_Application_Platform_version_4.2-Application_Platform_4.2">
+ <title>Application Platform 4.2</title>
+ <tgroup cols="2">
+ <colspec colname="Project" colnum="1" colwidth="4*"></colspec>
+ <colspec colname="Version" colnum="2" colwidth="4*"></colspec>
+ <thead>
+ <row>
+ <entry>
+ Project
+ </entry>
+ <entry>
+ Version
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ Hibernate
+ </entry>
+ <entry>
+ 3.2.4.SP1_CP01
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Hibernate Entity Manager
+ </entry>
+ <entry>
+ 3.2.1
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Hibernate Annotations
+ </entry>
+ <entry>
+ 3.2.1
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JBoss AS
+ </entry>
+ <entry>
+ 4.2.0
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JBoss MQ
+ </entry>
+ <entry>
+ 4.2.0
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JBoss Web
+ </entry>
+ <entry>
+ 2.0.0
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JBoss Transactions
+ </entry>
+ <entry>
+ 4.2.3.SP4
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JTA
+ </entry>
+ <entry>
+ 1.0.1B
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JBoss EJB3
+ </entry>
+ <entry>
+ RC10
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JBoss WS
+ </entry>
+ <entry>
+ 1.2.1
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JBoss AOP
+ </entry>
+ <entry>
+ 1.5.5
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JBoss Remoting
+ </entry>
+ <entry>
+ 2.0.0.SP4
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JBoss Serialization
+ </entry>
+ <entry>
+ 1.0.3
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JBoss Cache
+ </entry>
+ <entry>
+ 1.4.1.SP3
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JGroups
+ </entry>
+ <entry>
+ 2.4.1.SP3
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JBoss Seam
+ </entry>
+ <entry>
+ 1.2.0.AP
+ </entry>
+ </row>
+ <row>
+ <entry>
+ jBPM (JPDL)
+ </entry>
+ <entry>
+ 3.1.4 (Seam dependency)
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para> -->
+ </section>
+
+</chapter>
+
Added: docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml (rev 0)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml 2008-12-03 05:04:12 UTC (rev 12331)
@@ -0,0 +1,39 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+]>
+
+<chapter id="Installation">
+ <title>Installation</title>
+
+ <section id="Download">
+ <title>Download</title>
+
+ <para>
+ You can download the zip file from the JBoss Customer Service Portal (CSP), located at <ulink url="https://network.jboss.com">https://network.jboss.com</ulink>.
+ </para>
+ </section>
+
+ <section id="Installing">
+ <title>Installing</title>
+
+ <para>
+ To install from a zip file, simply unzip the downloaded file to a directory of your choice. You can unzip the platform on any operating system that supports the zip format. Four types of server configurations will be included in your installation - minimal, default, production and all. The Getting Started Guide explains in detail the different server configuration file sets.
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Unzip <literal>jboss-eap-<replaceable><release></replaceable>.zip</literal> to extract the archive contents into the location of your choice. You can do this using the JDK <literal>jar</literal> tool (or any other ZIP extraction tool). <programlisting>
+ [vsr]$ <literal>cd jbeapinstallationdir</literal>
+ [vsr]$ <literal>jar -xvf jboss-eap-<replaceable><release></replaceable>.zip</literal></programlisting>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ You are done with the installation! You should now have a directory called <filename>jboss-eap-<replaceable><release></replaceable></filename>. Refer to the Getting Started Guide to understand and explore the Platform Directory Structure.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </section>
+</chapter>
+
Added: docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide_CP03.ent
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide_CP03.ent (rev 0)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide_CP03.ent 2008-12-03 05:04:12 UTC (rev 12331)
@@ -0,0 +1,4 @@
+<!ENTITY JBEAP "JBoss Enterprise Application Platform">
+<!ENTITY JBEAPVERS "4.3">
+<!ENTITY HOLDER "Red Hat, Inc">
+<!ENTITY YEAR "2008">
Added: docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide_CP03.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide_CP03.xml (rev 0)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Installation_Guide_CP03.xml 2008-12-03 05:04:12 UTC (rev 12331)
@@ -0,0 +1,16 @@
+<?xml version='1.0'?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+]>
+
+<book>
+ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Getting_Started.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Post_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Uninstall_JBoss.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="Test_Your_Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/>
+</book>
Added: docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml (rev 0)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Introduction.xml 2008-12-03 05:04:12 UTC (rev 12331)
@@ -0,0 +1,53 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+]>
+
+<chapter id="Introduction">
+ <title>Introduction</title>
+ <para>
+ &JBEAP; is the open source implementation of the Java EE suite of services. It comprises a set of offerings for enterprise customers who are looking for preconfigured profiles of JBoss Enterprise Middleware components that have been tested and certified together to provide an integrated experience. Its easy-to-use server architecture and high flexibility makes JBoss the ideal choice for users just starting out with J2EE, as well as senior architects looking for a customizable middleware platform.
+ </para>
+ <para>
+ Because it is Java-based, &JBEAP; is cross-platform and easy to install and use on any operating system that supports Java. The readily available source code is a powerful learning tool to debug the server and understand it. It also gives you the flexibility to create customized versions for your personal or business use.
+ </para>
+ <para>
+ Installing &JBEAP; is simple and easy. You can have it installed and running in no time. This guide will teach you to install and uninstall JBoss.<!--: <itemizedlist>
+ <listitem>
+ <para>
+ How to install &JBEAP;
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ How to Start and Stop your JBoss AS instance
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The Directory structure
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The key services and configuration files
+ </para>
+ </listitem>
+ </itemizedlist>-->
+ </para>
+ <section id="introduction-Feedback">
+ <title>Feedback</title>
+ <para>
+ If you spot a typo in this guide, or if you have thought of a way to make this manual better, we would love to hear from you! Submit a report in <ulink url="http://jira.jboss.com/jira/browse/JBPAPP">JIRA</ulink> against the Product: JBoss Enterprise Application Platform, Version: <replaceable><version></replaceable>, Component: <emphasis>Doc</emphasis>. If you have a suggestion for improving the documentation, try to be as specific as possible. If you have found an error, include the section number and some of the surrounding text so we can find it easily.
+ </para>
+ </section>
+
+ <section id="Introduction-Other_Manuals">
+ <title>Other Manuals</title>
+ <para>
+ If you are looking for detailed product information refer to the manuals available online at <ulink url="http://www.redhat.com/docs/manuals/jboss"></ulink>.
+ <!--TODO mention about the other guides attached-->
+ </para>
+ </section>
+
+</chapter>
+
Added: docs/enterprise/trunk/Installation_Guide/en-US/Post_Installation.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Post_Installation.xml (rev 0)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Post_Installation.xml 2008-12-03 05:04:12 UTC (rev 12331)
@@ -0,0 +1,207 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+]>
+<chapter id="Post_Installation_Configuration">
+ <title>Post Installation Configuration</title>
+ <section id="Set_JBOSS_HOME">
+ <title>
+ Set JBOSS_HOME Environment Variable
+ </title>
+ <formalpara>
+ <title>
+ On a Linux Platform
+ </title>
+ <para>
+ Create an environment variable that points to the installation directory (<filename>JBOSS_DIST/jboss-as</filename>) and call it <literal>JBOSS_HOME</literal>. Add <literal>$JBOSS_HOME/bin</literal> to the system path to be able to run the server from the command line. You can do this by adding the following lines to the <filename>.bashrc</filename> file in your home directory.
+ <programlisting>
+#In this example /home/vrenish/EnterprisePlatform-4.3.0/jboss-as is the installation directory.
+ export JBOSS_HOME=/home/vrenish/EnterprisePlatform-4.3.0/jboss-as
+ export PATH=$PATH:$JBOSS_HOME/bin
+ </programlisting>
+ Set this variable for the user account(s) that will run the server.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>
+ On Microsoft Windows
+ </title>
+ <para>
+ Create an environment variable called <literal>JBOSS_HOME</literal> that points to the installation directory, for example: C:\Program Files\EnterprisePlatform-4.3.0\jboss-as\. In order to run the server from the command line add the <filename>bin</filename> directory to your path, for example: C:\Program Files\EnterprisePlatform-4.3.0\jboss-as\bin. To do this, open the Control Panel from the Start Menu, switch to Classic View if necessary, open the System Control Panel applet, select the Advanced Tab, and click on the Environment Variables button.
+ </para>
+ </formalpara>
+ </section>
+ <section id="Adjust_Memory_Settings">
+ <title>Adjust memory settings</title>
+ <para>
+ The default configuration for the server to start with, if no other configuration is specified, is the production configuration. It is recommended to run the example Seam applications that are included with the documentation using the production configuration.
+ </para>
+ <para>
+ To avoid memory issues, adjust the memory settings before deploying the applications. You can do this by updating <literal>JAVA_OPTS</literal> settings in the file <filename>JBOSS_DIST/jboss-as/server/production/run.conf</filename> with these recommended values:
+<programlisting>
+ -Xms1303m -Xmx1303m -XX:PermSize=256m -XX:MaxPermSize=256m
+</programlisting>
+ </para>
+ </section>
+ <section id="Post-Installation">
+ <title>
+ Post Installation Security Configuration
+ </title>
+ <para>
+ When installed from the zip archive, all JBoss services require authentication to access most JBoss services, including administrative services. Additionally no user accounts are set up. This is to stop default user/password-based attacks.
+ </para>
+
+ <formalpara>
+ <title>Set up Accounts for <literal>jmx-console</literal> and the invokers by modifying:</title>
+ <para>
+ <programlisting>
+ $JBOSS_HOME/server/$CONFIG/conf/props/jmx-console-users.properties
+ </programlisting>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Set up Accounts for <literal>web-console</literal> users by modifying:</title>
+ <para>
+ <programlisting>
+ $JBOSS_HOME/server/$CONFIG/deploy/management/console-mgr.sar/
+ web-console.war/WEB-INF/classes/web-console-users.properties
+ </programlisting>
+ Where <literal>$JBOSS_HOME</literal> is the install directory and <literal>$CONFIG</literal> is the server configuration being used.
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Set SuckerPassword for JBoss Messaging:</title>
+ <para>
+ JBoss Messaging makes internal connections between nodes in order to redistribute messages between clustered destinations. These connections are made with the user name of a special reserved user whose password is specified by this parameter <literal>SuckerPassword</literal> in the Server Peer configuration file:
+ <programlisting>
+ $JBOSS_HOME/server/$CONFIG/deploy/jboss-messaging.sar/messaging-service.xml
+ </programlisting>
+ Where <literal>$JBOSS_HOME</literal> is the install directory and <literal>$CONFIG</literal> is the server configuration being used.
+ To avoid a security risk, you MUST specify the value of the attribute <literal>SuckerPassword</literal>, failing which the default value will be used. Any one who knows the default password will be able to gain access to any destinations on the server. The following fragment should be uncommented and modified:
+ <programlisting>
+ <mbean code="org.jboss.jms.server.ServerPeer"
+ name="jboss.messaging:service=ServerPeer"
+ xmbean-dd="xmdesc/ServerPeer-xmbean.xml">
+ ...
+ ...
+ ...
+ ...
+ <!-- The password used by the message sucker connections to create connections.
+ THIS SHOULD ALWAYS BE CHANGED AT INSTALL TIME TO SECURE SYSTEM -->
+ <attribute name="SuckerPassword"></attribute>
+
+ ...
+ ...
+ ...
+ </mbean>
+ </programlisting>
+ </para>
+ </formalpara>
+ </section>
+ <section id="Disabling_Authentication">
+ <title>Disabling Authentication</title>
+ <para>
+ It is also possible to disable authentication on specific services. All specified paths in the sections below are relative to <literal>$JBOSS_HOME</literal>.
+ </para>
+ <formalpara>
+ <title>Disabling Authentication for JXM Console:</title>
+ <para>
+ To disable authentication for the JMX console, edit the following file and comment out the security-constraint section:
+ <programlisting>
+server/$CONFIG/deploy/jmx-console.war/WEB-INF/web.xml
+ </programlisting>
+ The following fragment should be commented out:
+ <programlisting>
+<security-constraint>
+ <web-resource-collection>
+ <web-resource-name>HtmlAdaptor</web-resource-name>
+ <description>An example security config that only allows
+users with the
+role JBossAdmin to access the HTML JMX console web application
+ </description>
+ <url-pattern>/*</url-pattern>
+ <http-method>GET</http-method>
+ <http-method>POST</http-method>
+ </web-resource-collection>
+ <auth-constraint>
+ <role-name>JBossAdmin</role-name>
+ </auth-constraint>
+</security-constraint>
+ </programlisting>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Disabling Authentication for Web Console:</title>
+ <para>
+ To disable authentication for the Web console, edit the following file to comment out the security-constraint section:
+ <programlisting>
+server/$CONFIG/deploy/management/console-mgr.sar/web-console.war/WEB-INF/web.xml
+ </programlisting>
+ The following fragment should be commented out:
+ <programlisting>
+<security-constraint>
+ <web-resource-collection>
+ <web-resource-name>HtmlAdaptor</web-resource-name>
+ <description>An example security config that only allows
+users with the role JBossAdmin to access the HTML JMX console web application
+ </description>
+ <url-pattern>/*</url-pattern>
+ <http-method>GET</http-method>
+ <http-method>POST</http-method>
+ </web-resource-collection>
+ <auth-constraint>
+ <role-name>JBossAdmin</role-name>
+ </auth-constraint>
+</security-constraint>
+ </programlisting>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Disabling Authentication for HTTP Invoker:</title>
+ <para>
+ To disable authentication for the http invoker, <literal>JNDIFactory</literal>, <literal>EJBInvokerServlet</literal>, and <literal>JMXInvokerServlet</literal> need to be removed from the security realm in the file:
+ <programlisting>
+server/$CONFIG/deploy/httpha-invoker.sar/invoker.war/WEB-INF/web.xml
+ </programlisting>
+ For example, the security-constraint element should look as follows:
+ <programlisting>
+<security-constraint>
+ <web-resource-collection>
+ <web-resource-name>HttpInvokers</web-resource-name>
+ <description>An example security config that only allows
+users with the role HttpInvoker to access the HTTP invoker servlets
+ </description>
+ <url-pattern>/restricted/*</url-pattern>
+ <http-method>GET</http-method>
+ <http-method>POST</http-method>
+ </web-resource-collection>
+ <auth-constraint>
+ <role-name>HttpInvoker</role-name>
+ </auth-constraint>
+ </security-constraint>
+ </programlisting>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Disabling Authentication for JMX Invoker:</title>
+ <para>
+ To disable authentication for the JMX invoker, edit the following file to comment out the security interceptor passthrough:
+ <programlisting>
+server/$CONFIG/deploy/jmx-invoker-service.xml
+ </programlisting>
+ Locate the mbean section with the class <literal>org.jboss.jmx.connector.invoker.InvokerAdaptorService</literal>. In that section comment out the line that relates to authenticated users:
+ <programlisting>
+<descriptors>
+ <interceptors>
+ <!-- Uncomment to require authenticated users -->
+ <interceptor code="org.jboss.jmx.connector.invoker.AuthenticationInterceptor"
+ securityDomain="java:/jaas/jmx-console"/>
+ <!-- Interceptor that deals with non-serializable results -->
+ <interceptor code="org.jboss.jmx.connector.invoker.SerializableInterceptor"
+ policyClass="StripModelMBeanInfoPolicy"/>
+ </interceptors>
+</descriptors>
+ </programlisting>
+ </para>
+ </formalpara>
+ </section>
+</chapter>
Added: docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml (rev 0)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml 2008-12-03 05:04:12 UTC (rev 12331)
@@ -0,0 +1,26 @@
+<?xml version='1.0'?>
+<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<appendix id="appe-Publican-Revision_History">
+ <title>Revision History</title>
+ <simpara>
+ <revhistory>
+ <revision>
+ <revnumber>1.0</revnumber>
+ <date></date>
+ <author>
+ <firstname></firstname>
+ <surname></surname>
+ <email></email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member></member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ </revhistory>
+ </simpara>
+</appendix>
+
Added: docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml (rev 0)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Test_Your_Installation.xml 2008-12-03 05:04:12 UTC (rev 12331)
@@ -0,0 +1,62 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+]>
+
+<chapter id="Test_your_Installation">
+ <title>Test your Installation</title>
+ <para>
+ After you have installed the JBoss Enterprise Application Platform, it is wise to perform a simple startup test to validate that there are no major problems with your Java VM/operating system combination. Make sure you have set the <literal>JBOSS_HOME</literal> envirnoment variables as explained in <ulink url="Post_Installation_Configuration"/>. To test your installation, move to <filename>JBOSS_DIST/jboss-as/bin</filename> directory and execute the <filename>run.bat</filename> (for Windows) or <filename>run.sh</filename> (for Linux) script, as appropriate for your operating system. Your output should look like the following (accounting for installation directory differences) and contain no error or exception messages:
+ </para>
+<programlisting>
+[vrenish@vinux bin]$ ./run.sh
+=====================================================
+
+ JBoss Bootstrap Environment
+
+ JBOSS_HOME: /home/vrenish/jboss-eap-4.3/jboss-as
+
+ JAVA: /usr/java/jdk1.5.0_11/bin/java
+
+ JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1503m -Xmx1503m -Dsun.rmi.dgc.cli ent.gcInterval=3600000
+ -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.prefer IPv4Stack=true
+
+ CLASSPATH: /home/vrenish/jboss-eap-4.3/jboss-as/bin/run.jar:/u sr/java/jdk1.5.0_11/lib/tools.jar
+
+=====================================================
+
+18:45:49,550 INFO [Server] Starting JBoss (MX MicroKernel)...
+.
+.
+.
+.
+18:45:50,449 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems Inc.
+18:45:50,449 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_11-b03 ,Sun Microsystems Inc.
+18:45:50,449 INFO [ServerInfo] OS-System: Linux 2.6.9-42.0.3.EL,i386
+18:45:51,824 INFO [Server] Core system initialized
+18:45:59,622 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083 /
+18:45:59,659 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour ce:jboss-log4j.xml
+</programlisting>
+ <note>
+ <para>
+ Note that there is no "Server Started" message shown at the console when the server is started using the <literal>production</literal> profile, which is the default profile used when no other is specified. This message may be observed in the <filename>server.log</filename> file located in the <filename>server/production/log</filename> subdirectory.
+ </para>
+ </note>
+ <para>
+ Now open <literal>http://localhost:8080</literal> in your web browser. (Make sure you dont have anything else already on your machine using that port).<footnote><para>
+ Note that on some machines, the name localhost won’t resolve properly and you should use the local loopback address 127.0.0.1 instead.</para></footnote> The contents of your page should look similar to this: <xref linkend="Test_your_Installation-Test_your_Installation" />.
+ </para>
+ <para>
+ <figure id="Test_your_Installation-Test_your_Installation">
+ <title>Test your Installation</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata align="center" fileref="images/test_install.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </para>
+ <para>
+ You are now ready to use the JBoss Enterprise Application Platform. Refer to the Getting Started Guide for more information about the platform layout and example applications showcasing JBoss in action.
+ </para>
+</chapter>
+
Added: docs/enterprise/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml (rev 0)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Uninstall_JBoss.xml 2008-12-03 05:04:12 UTC (rev 12331)
@@ -0,0 +1,11 @@
+<?xml version='1.0'?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+]>
+
+<chapter id="Uninstall_JBoss">
+ <title>Uninstall JBoss</title>
+ <para>
+ As JBoss Enterprise Application Platform was installed from a zipfile, you may uninstall it by simply deleting the &JBEAP; installed directory.
+ </para>
+</chapter>
+
Added: docs/enterprise/trunk/Installation_Guide/en-US/images/step3.png
===================================================================
(Binary files differ)
Property changes on: docs/enterprise/trunk/Installation_Guide/en-US/images/step3.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/enterprise/trunk/Installation_Guide/en-US/images/step4.png
===================================================================
(Binary files differ)
Property changes on: docs/enterprise/trunk/Installation_Guide/en-US/images/step4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/enterprise/trunk/Installation_Guide/en-US/images/step8.png
===================================================================
(Binary files differ)
Property changes on: docs/enterprise/trunk/Installation_Guide/en-US/images/step8.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/enterprise/trunk/Installation_Guide/en-US/images/test_install.png
===================================================================
(Binary files differ)
Property changes on: docs/enterprise/trunk/Installation_Guide/en-US/images/test_install.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/enterprise/trunk/Installation_Guide/en-US/images/title.jpg
===================================================================
(Binary files differ)
Property changes on: docs/enterprise/trunk/Installation_Guide/en-US/images/title.jpg
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: docs/enterprise/trunk/Installation_Guide/en-US/images/uninstall.png
===================================================================
(Binary files differ)
Property changes on: docs/enterprise/trunk/Installation_Guide/en-US/images/uninstall.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
17 years, 5 months
- 1
- 0
JBoss Portal SVN: r12330 - docs/enterprise/trunk/Installation_Guide/en-US.
by portal-commits＠lists.jboss.org
Author: sradvan
Date: 2008-12-03 00:02:44 -0500 (Wed, 03 Dec 2008)
New Revision: 12330
Removed:
docs/enterprise/trunk/Installation_Guide/en-US/Appendix.xml
docs/enterprise/trunk/Installation_Guide/en-US/Author_Group.xml
docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml
docs/enterprise/trunk/Installation_Guide/en-US/Chapter.xml
docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml
docs/enterprise/trunk/Installation_Guide/en-US/Conventions.xml
docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml
docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml
docs/enterprise/trunk/Installation_Guide/en-US/Portal_EAP.ent
docs/enterprise/trunk/Installation_Guide/en-US/Portal_EAP.xml
docs/enterprise/trunk/Installation_Guide/en-US/Preface.xml
docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml
docs/enterprise/trunk/Installation_Guide/en-US/Running_Eap.xml
docs/enterprise/trunk/Installation_Guide/en-US/images/
Log:
merging guide
Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Appendix.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Appendix.xml 2008-12-02 10:30:12 UTC (rev 12329)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Appendix.xml 2008-12-03 05:02:44 UTC (rev 12330)
@@ -1,13 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<appendix id="appe-Portal_EAP-Revision_History">
- <appendixinfo>
- <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
- </appendixinfo>
- <title>Revision History</title>
- <para>
- </para>
-</appendix>
-
Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Author_Group.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Author_Group.xml 2008-12-02 10:30:12 UTC (rev 12329)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Author_Group.xml 2008-12-03 05:02:44 UTC (rev 12330)
@@ -1,10 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<authorgroup>
- <corpauthor>
- Red Hat Documentation Group
- </corpauthor>
-</authorgroup>
-
Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml 2008-12-02 10:30:12 UTC (rev 12329)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml 2008-12-03 05:02:44 UTC (rev 12330)
@@ -1,29 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<bookinfo id="book-Portal_EAP-JBoss_Portal">
- <title>JBoss Portal</title>
- <subtitle>Deploying JBoss Portal on JBoss Enterprise Application Platform 4.3</subtitle>
- <issuenum>1.0</issuenum>
- <productnumber>0</productnumber>
- <abstract>
- <para>This guide helps you deploy and configure JBoss Portal on JBoss
-Enterprise Application Platform 4.3.</para></abstract>
- <corpauthor>
- <inlinemediaobject>
- <imageobject>
- <imagedata fileref="Common_Content/images/redhat-logo.svg" />
- </imageobject>
- </inlinemediaobject>
- </corpauthor>
-<isbn>N/A</isbn>
-<pubdate>February 2008</pubdate>
- <copyright>
- <year>&YEAR;</year>
- <holder>Red Hat, Inc.</holder>
- </copyright>
- <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
- <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-</bookinfo>
-
Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Chapter.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Chapter.xml 2008-12-02 10:30:12 UTC (rev 12329)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Chapter.xml 2008-12-03 05:02:44 UTC (rev 12330)
@@ -1,25 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<chapter id="chap-Portal_EAP-Test">
- <title>Test</title>
- <para>
- This is a test paragraph
- </para>
- <section id="sect-Portal_EAP-Test-Section_1_Test">
- <title>Section 1 Test</title>
- <para>
- Test of a section
- </para>
- </section>
-
- <section id="sect-Portal_EAP-Test-Section_2_Test">
- <title>Section 2 Test</title>
- <para>
- Test of a section
- </para>
- </section>
-
-</chapter>
-
Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml 2008-12-02 10:30:12 UTC (rev 12329)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Configuration.xml 2008-12-03 05:02:44 UTC (rev 12330)
@@ -1,97 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<chapter id="chap-Portal_EAP-Configuration">
- <title>Configuration</title>
- <para>
- This is chapter describes how to configure your local environment, RDBMS JDBC connectors, and Datasource descriptors.
- </para>
- <section id="sect-Portal_EAP-Configuration-Configuring_Your_Local_Environment">
- <title>Configuring Your Local Environment</title>
- <orderedlist>
- <listitem>
- <para>
- Create a <filename>JBOSS_HOME</filename> environment variable that points to the JBoss EAP installation directory. Configure this environment variable while logged in under the user account that will be used to run the JBoss EAP server. For example, on Linux, if you installed JBoss EAP into the <filename>/jboss/</filename> directory, add the following line to your <filename>~/.bashrc</filename> file:
- </para>
- <para>
-<screen>
-export JBOSS_HOME=/jboss/jboss-eap-4.3/jboss-as/
-</screen>
- </para>
- </listitem>
- <listitem>
- <para>
- Configure a <filename>JAVA_HOME</filename> environment variable that points to the Sun JDK installation directory. Configure this environment variable while logged in under the user account that will be used to run the JBoss EAP server. For example, on Linux, if the Sun JDK was installed into the <filename>/usr/local/jdk<replaceable>version_number</replaceable>/</filename> directory, add the following line to your <filename>~/.bashrc</filename> file:
- </para>
- <para>
-<screen>
-export JAVA_HOME=/usr/local/jdk<replaceable>version_number</replaceable>/
-</screen>
- </para>
- </listitem>
- <listitem>
- <para>
- Run the following command to enable the <filename>JBOSS_HOME</filename> and <filename>JAVA_HOME</filename> environment variables:
- </para>
- <para>
-<screen>
-source ~/.bashrc
-</screen>
- </para>
- </listitem>
- </orderedlist>
- <para>
- This guide assumes you copied the Sun JDK into the <filename>/usr/local/jdk<replaceable>version_number</replaceable>/</filename> directory, as per <xref linkend="sect-Portal_EAP-Installation-Installing_the_Java_Environment" />. If this is not the case, set the <computeroutput>JAVA_HOME</computeroutput> environment variable to the correct directory.
- </para>
- </section>
-
- <section id="sect-Portal_EAP-Configuration-Installing_an_RDBMS_JDBC_connector">
- <title>Installing an RDBMS JDBC connector</title>
- <para>
- A relational database management system (RDBMS) Java Database Connectivity (JDBC) connector is required for JBoss Portal to communicate with a database. Test suites have been run against the <trademark class="registered">Oracle</trademark> 9, <trademark class="registered">Oracle</trademark> 10, <trademark class="registered">Microsoft SQL Server</trademark>, MySQL 4, MySQL 5, and PostgreSQL 8 databases - these databases are recommended for production use. Please refer to your database documentation for the correct RDBMS JDBC connector. The MySQL RDBMS JDBC connector can be downloaded from <ulink url="http://www.mysql.com/products/connector/j/"></ulink>, and the PostgreSQL RDBMS JDBC connector can be downloaded from <ulink url="http://jdbc.postgresql.org/download.html"></ulink>.
- </para>
- <para>
- Refer to the help files in each download for installation instructions. In most cases, the RDBMS JDBC connector comes as a <computeroutput>.jar</computeroutput> file. Copy this file into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/lib/</filename> directory.
- </para>
- </section>
-
- <section id="sect-Portal_EAP-Configuration-Datasource_Descriptors">
- <title>Datasource Descriptors</title>
- <para>
- A Datasource descriptor is required for JBoss Portal to communicate with a database. Sample Datasource descriptor files are provided for the Hypersonic SQL, <trademark class="registered">Microsoft SQL Server</trademark>, MySQL, <trademark class="registered">Oracle</trademark>, and PostgreSQL databases. These can be found in the <filename>setup/</filename> subdirectory where the <computeroutput>JBoss Portal <replaceable>x.x.x</replaceable> binary distribution</computeroutput> file was extracted to. For example, if JBoss Portal was extracted into the <filename>/jboss/</filename> directory, the sample Datasource descriptors would be in the <filename>/jboss/jboss-portal-<replaceable>x.x.x</replaceable>/setup/</filename> directory.
- </para>
- <para>
- The sample Datasource descriptors will work with default installations of external databases; however, you may need to configure the correct username and password. As well, the sample MySQL and PostgreSQL Datasource descriptors assume the name of the database to be <computeroutput>jbossportal</computeroutput>.
- </para>
- <para>
- When copying a Datasource descriptor for MySQL, <trademark class="registered">Microsoft SQL Server</trademark>, PostgreSQL, or <trademark class="registered">Oracle</trademark> databases, change the <computeroutput><user-name><replaceable>portal</replaceable></user-name></computeroutput> and <computeroutput><password><replaceable>portalpassword</replaceable></password></computeroutput> sections to reflect the correct username and password for the user who has access to the jbossportal database.
- </para>
- <important>
- <title>Different Datasource Descriptors</title>
- <para>
- Only have one Datasource descriptor in the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory. For example, if you want to use a MySQL database, remove the <filename>portal-hsqldb-ds.xml</filename> file, and other descriptors, if they exists.
- </para>
- </important>
- <para>
- The following is an example Datasource descriptor file for MySQL 5:
- </para>
- <para>
-<screen>
-<?xml version="1.0" encoding="UTF-8"?>
-<datasources>
- <local-tx-datasource>
- <jndi-name>PortalDS</jndi-name>
- <connection-url>jdbc:mysql://localhost:3306/jbossportal?
- useServerPrepStmts=false&amp;jdbcCompliantTruncation=false</connection-url>
- <driver-class>com.mysql.jdbc.Driver</driver-class>
- <user-name><replaceable>portal</replaceable></user-name>
- <password><replaceable>portalpassword</replaceable></password>
- </local-tx-datasource>
-</datasources>
-</screen>
- </para>
- </section>
-
-</chapter>
-
Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Conventions.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Conventions.xml 2008-12-02 10:30:12 UTC (rev 12329)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Conventions.xml 2008-12-03 05:02:44 UTC (rev 12330)
@@ -1,94 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<chapter id="chap-Portal_EAP-Document_Conventions">
- <title>Document Conventions</title>
- <para>
- Certain words in this manual are represented in different fonts, styles, and weights. This highlighting indicates that the word is part of a specific category. The categories include the following:
- </para>
- <variablelist>
- <varlistentry>
- <term><literal>Courier font</literal></term>
- <listitem>
- <para>
- Courier font represents <command>commands</command>, <filename>file names and paths</filename>, and <prompt>prompts</prompt> .
- </para>
- <para>
- When shown as below, it indicates computer output:
-<screen>
-Desktop about.html logs paulwesterberg.png
-Mail backupfiles mail reports
-</screen>
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><userinput>bold Courier font</userinput></term>
- <listitem>
- <para>
- Bold Courier font represents text that you are to type, such as: <userinput>service jonas start</userinput>
- </para>
- <para>
- If you have to run a command as root, the root prompt (<literal>#</literal>) precedes the command:
- </para>
-<screen>
-# <userinput>gconftool-2 </userinput>
-</screen>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><replaceable>italic Courier font</replaceable></term>
- <listitem>
- <para>
- Italic Courier font represents a variable, such as an installation directory: <filename><replaceable>install_dir</replaceable>/bin/</filename>
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><application>bold font</application></term>
- <listitem>
- <para>
- Bold font represents <application>application programs</application> and <guilabel>text found on a graphical interface</guilabel>.
- </para>
- <para>
- When shown like this: <guibutton> OK </guibutton>, it indicates a button on a graphical application interface.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- <para>
- Additionally, the manual uses different strategies to draw your attention to pieces of information. In order of how critical the information is to you, these items are marked as follows:
- </para>
- <note>
- <title>Note</title>
- <para>
- A note is typically information that you need to understand the behavior of the system.
- </para>
- </note>
- <tip>
- <title>Tip</title>
- <para>
- A tip is typically an alternative way of performing a task.
- </para>
- </tip>
- <important>
- <title>Important</title>
- <para>
- Important information is necessary, but possibly unexpected, such as a configuration change that will not persist after a reboot.
- </para>
- </important>
- <caution>
- <title>Caution</title>
- <para>
- A caution indicates an act that would violate your support agreement, such as recompiling the kernel.
- </para>
- </caution>
- <warning>
- <title>Warning</title>
- <para>
- A warning indicates potential data loss, as may happen when tuning hardware for maximum performance.
- </para>
- </warning>
-</chapter>
-
Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml 2008-12-02 10:30:12 UTC (rev 12329)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Databases.xml 2008-12-03 05:02:44 UTC (rev 12330)
@@ -1,202 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<chapter id="chap-Portal_EAP-Databases">
- <title>Databases</title>
- <para>
- The following chapter contains examples for how to use the Hypersonic SQL and MySQL databases to store JBoss Portal user information.
- </para>
- <section id="sect-Portal_EAP-Databases-Using_a_Hypersonic_SQL_Database">
- <title>Using a Hypersonic SQL Database</title>
- <para>
- JBoss EAP contains an embedded <ulink url="http://hsqldb.org/">Hypersonic SQL</ulink> database instance. After starting JBoss EAP and deploying JBoss portal for the first time, the Hypersonic SQL database is created in the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/data/</filename> directory. This directory will not exist until after starting JBoss EAP and deploying JBoss Portal. The Hypersonic SQL database is used by default, but is only recommended for developer use.
- </para>
- <para>
- To use the Hypersonic SQL database, change into the <filename>setup/</filename> subdirectory where JBoss Portal was extracted to. Copy the <filename>portal-hsqldb-ds.xml</filename> file into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory. Alternatively, copy and save the following example as <filename>portal-hsqldb-ds.xml</filename> into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory:
- </para>
- <para>
-<screen>
-<?xml version="1.0" encoding="UTF-8"?>
-<datasources>
- <local-tx-datasource>
- <jndi-name>PortalDS</jndi-name>
- <connection-url>jdbc:hsqldb:${jboss.server.data.dir}$
- {/}portal${/}hypersonic${/}database</connection-url>
- <driver-class>org.hsqldb.jdbcDriver</driver-class>
- <user-name>sa</user-name>
- <password><![CDATA[]]></password>
- </local-tx-datasource>
-</datasources>
-</screen>
- </para>
- <para>
- JBoss Portal is now ready to use the Hypersonic SQL database. See <xref linkend="chap-Portal_EAP-Running_JBoss_EAP" /> for instructions on starting JBoss EAP.
- </para>
- </section>
-
- <section id="sect-Portal_EAP-Databases-Using_a_MySQL_Database">
- <title>Using a MySQL Database</title>
- <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-Installing_the_MySQL_RDBMS_JDBC_connector">
- <title>Installing the MySQL RDBMS JDBC connector</title>
- <para>
- The RDBMS JDBC MySQL connector is required for JBoss Portal to use a MySQL database:
- </para>
- </formalpara>
- <orderedlist>
- <listitem>
- <para>
- Navigate to the <ulink url="http://dev.mysql.com/downloads/connector/j/3.1.html">JDBC MySQL connector</ulink> section of dev.mysql.com. Download the <computeroutput>Source and Binaries (zip)</computeroutput> file.
- </para>
- </listitem>
- <listitem>
- <para>
- Unzip the <filename>mysql-java-connector</filename> into the desired directory. It does not matter which directory is used.
- </para>
- </listitem>
- <listitem>
- <para>
- Change into the directory where the <filename>mysql-java-connector</filename> was extracted to. Copy the <filename>mysql-connector-java-<replaceable>version-number</replaceable>-bin.jar</filename> file into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/lib/</filename> directory.
- </para>
- </listitem>
- </orderedlist>
- <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-Data_Truncation_Errors">
- <title>Data Truncation Errors</title>
- <para>
- If you are running MySQL 5, data truncation errors such as the following may occur:
- </para>
- </formalpara>
- <para>
-<screen>
-ERROR JDBCExceptionReporter Data truncation: Data too long for column 'jbp_viewrealemail' at row 1
-</screen>
- </para>
- <para>
- If you are running MySQL in strict mode, remove <computeroutput>STRICT_TRANS_TABLES</computeroutput> from the <computeroutput>sql-mode=</computeroutput> line, in the <filename>my.cnf</filename> file if you are running Linux, and from the <filename>my.cfg</filename> file if you are running <trademark class="registered">Windows</trademark>. For further information, please see <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=AvoidMySQL5DataTruncationErrors"></ulink>.
- </para>
- <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-Creating_a_MySQL_Database">
- <title>Creating a MySQL Database</title>
- <para>
- If you have just installed MySQL, make sure the MySQL server is running, and then run the following command to set the root user password:
- </para>
- </formalpara>
- <para>
-<screen>
-mysqladmin -u root password '<replaceable>new-root-user-password</replaceable>'
-</screen>
- </para>
- <orderedlist>
- <listitem>
- <para>
- Run the following command to log in to MySQL. Enter the root user password when prompted:
- </para>
- <para>
-<screen>
-mysql -u root -p
-</screen>
- </para>
- </listitem>
- <listitem>
- <para>
- Use the <command>CREATE DATABASE</command> command to create a new jbossportal database. Note: the rest of this guide, and configuration examples following here after, assume the database name to be jbossportal. If you change the database name, please change the name in all necessary configuration files:
- </para>
- <para>
-<screen>
-mysql> CREATE DATABASE jbossportal;
-</screen>
- </para>
- <para>
- The output should be similar to the following:
- </para>
- <para>
-<screen>
-Query OK, 1 row affected (0.00 sec)
-</screen>
- </para>
- <para>
- At this point, the <command>SHOW DATABASES;</command> command should display the <command>jbossportal</command> database:
- </para>
- <para>
-<screen>
-mysql> SHOW DATABASES;
-+--------------------+
-| Database |
-+--------------------+
-| information_schema |
-| jbossportal |
-| mysql |
-+--------------------+
-3 rows in set (0.00 sec)
-</screen>
- </para>
- <para>
- It is safe to ignore the other databases.
- </para>
- </listitem>
- <listitem>
- <para>
- Add a new user and give that user access to the jbossportal database. The following example adds a new user named <computeroutput>portal</computeroutput>, with the password <computeroutput>portalpassword</computeroutput>, and gives the portal user access to the jbossportal database. It is recommended that you change the password. Change <replaceable>portalpassword</replaceable> to change the password:
- </para>
- <para>
-<screen>
-mysql> GRANT ALL PRIVILEGES ON jbossportal.* TO '<replaceable>portal</replaceable>'@'localhost'
-IDENTIFIED BY '<replaceable>portalpassword</replaceable>' WITH GRANT OPTION;
-</screen>
- </para>
- <para>
- The output should be similar to the following:
- </para>
- <para>
-<screen>
-Query OK, 0 rows affected (0.00 sec)
-</screen>
- </para>
- <para>
- If you changed the portal user's password, also change the password in the MySQL Datasource descriptor.
- </para>
- </listitem>
- </orderedlist>
- <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-MySQL_Datasource_Descriptor">
- <title>MySQL Datasource Descriptor</title>
- <para>
- To install the MySQL Datasource descriptor:
- </para>
- </formalpara>
- <orderedlist>
- <listitem>
- <para>
- Change into the <filename>setup</filename> subdirectory where JBoss Portal was extracted to. Copy the MySQL Datasource descriptor into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory. If you are running MySQL 5, use <filename>portal-mysql5-ds.xml</filename>, otherwise use <filename>portal-mysql-ds.xml</filename>.
- </para>
- </listitem>
- <listitem>
- <para>
- Update the <computeroutput><user-name><replaceable>portal</replaceable></user-name></computeroutput> and <computeroutput><password><replaceable>portalpassword</replaceable></password></computeroutput> sections in the Datasource descriptor to reflect the correct username and password for the user who has access to the jbossportal database.
- </para>
- </listitem>
- </orderedlist>
- <formalpara id="form-Portal_EAP-Using_a_MySQL_Database-MySQL_Table_Errors">
- <title>MySQL Table Errors</title>
- <para>
- Tables are set up automatically when JBoss Portal first starts. Initially, two users will be stored in the jbossportal MySQL database: a standard user with the username user, and the password user, and an administrative user with the username admin, and the password admin. Since the database tables are created during initial startup, errors such as the following may occur, but are safe to ignore:
- </para>
- </formalpara>
- <para>
-<screen>
-WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
-ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_repositoryentry' doesn't exist
-WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
-ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_version_refs' doesn't exist
-WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
-ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_wsp_node' doesn't exist
-WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
-ERROR [JDBCExceptionReporter] Table 'jbossportal.jbp_cms_cmsentry' doesn't exist
-WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: 42S02
-</screen>
- </para>
- <para>
- See <xref linkend="chap-Portal_EAP-Running_JBoss_EAP" /> for instructions on starting JBoss EAP.
- </para>
- </section>
-
-</chapter>
-
Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml 2008-12-02 10:30:12 UTC (rev 12329)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Installation.xml 2008-12-03 05:02:44 UTC (rev 12330)
@@ -1,385 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<chapter id="chap-Portal_EAP-Installation">
- <title>Installation</title>
- <para>
- This chapter describes how to download and install Java, the Sun Java 2 Development Kit (Sun JDK), JBoss Enterprise Application Platform (EAP), and JBoss Portal.
- </para>
- <section id="sect-Portal_EAP-Installation-Installing_the_Java_Environment">
- <title>Installing the Java Environment</title>
- <para>
- JBoss EAP requires a working installation of Java. For operating system specific downloads, please refer to <ulink url="http://www.java.com/en/download/index.jsp"></ulink>. If you encounter problems installing the Java environment, please refer to <ulink url="http://www.java.com/en/download/help/"></ulink>, or the operating system specific hints <ulink url="http://wiki.jboss.org/wiki/Wiki.jsp?page=OperatingSystemHints">on the JBoss wiki</ulink>.
- </para>
- <para>
- For example, if you are running Red Hat Enterprise Linux and have a subscription to the Red Hat Network, run the following command as root to install the Java environment:
- </para>
- <para>
-<screen>
-# yum install java-1.5.0-sun java-1.5.0-sun-devel java-1.5.0-sun-plugin
-</screen>
- </para>
- <para>
- Any Java 1.5 JVM should work; however, you should use the Sun JVM. On Red Hat Enterprise Linux, run the following command as root to confirm the Sun JVM is being used:
- </para>
- <para>
-<screen>
-# /usr/sbin/alternatives --config java
-</screen>
- </para>
- <para>
- Note: there should be a <computeroutput>*+</computeroutput> next to <computeroutput>/usr/lib/jvm/jre-1.5.0-sun/bin/java</computeroutput>. In the following example, the Sun JVM is selected:
- </para>
- <para>
-<screen>
-There are 2 programs which provide 'java'.
-
-Selection Command
------------------------------------------------
- 1 /usr/lib/jvm/jre-1.4.2-gcj/bin/java
-*+ 2 /usr/lib/jvm/jre-1.5.0-sun/bin/java
-</screen>
- </para>
- <para>
- Repeat the previous step for <computeroutput>javac</computeroutput> and <computeroutput>java_sdk_1.5.0</computeroutput>:
- </para>
- <para>
-<screen>
-# /usr/sbin/alternatives --config javac
-</screen>
- </para>
- <para>
- The output should be similar to the following:
- </para>
- <para>
-<screen>
-There is 1 program that provides 'javac'.
-
-Selection Command
------------------------------------------------
-*+ 1 /usr/lib/jvm/java-1.5.0-sun/bin/javac
-</screen>
- </para>
- <para>
-<screen>
-# /usr/sbin/alternatives --config java_sdk_1.5.0
-</screen>
- </para>
- <para>
- The output should be similar to the following:
- </para>
- <para>
-<screen>
-There is 1 program that provides 'java_sdk_1.5.0'.
-
-Selection Command
------------------------------------------------
-*+ 1 /usr/lib/jvm/java-1.5.0-sun
-</screen>
- </para>
- <formalpara id="form-Portal_EAP-Installing_the_Java_Environment-Sun_Java_2_Development_Kit">
- <title>Sun Java 2 Development Kit</title>
- <para>
- The Sun Java 2 Development Kit (Sun JDK 5.0) must be installed before installing JBoss EAP. To install the Sun JDK:
- </para>
- </formalpara>
- <orderedlist>
- <listitem>
- <para>
- Navigate to <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp"></ulink>.
- </para>
- </listitem>
- <listitem>
- <para>
- Download the Sun Java 2 Development Kit (Sun JDK 5.0). Click the <computeroutput>Download</computeroutput> button next to <computeroutput>JDK 5.0 Update <replaceable>x</replaceable></computeroutput>, where <replaceable>x</replaceable> is the latest version number. Note: the latest version may differ from the following image:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/select_jdk.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- Accept the License Agreement:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/accept_license.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- Download the appropriate Sun JDK version for your operating system. For example, on Linux, click the <computeroutput>Linux self-extracting file</computeroutput> link to download the Sun JDK. Note: the latest version may differ from the following image:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/jdk_download.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- </orderedlist>
- <para>
- To install the Sun JDK on Linux:
- </para>
- <orderedlist>
- <listitem>
- <para>
- Change into the directory where the <filename>jdk-<replaceable>version_number</replaceable>-linux-i586.bin</filename> file was downloaded to. Run the following command to allow execute permission on the <filename>jdk-<replaceable>version_number</replaceable>-linux-i586.bin</filename> file:
- </para>
- <para>
-<screen>
-chmod u+x jdk-<replaceable>version_number</replaceable>-linux-i586.bin
-</screen>
- </para>
- </listitem>
- <listitem>
- <para>
- Change into the directory where the <filename>jdk-<replaceable>version_number</replaceable>-linux-i586.bin</filename> file was downloaded to. Run the following command as root to unpack the Sun JDK:
- </para>
- <para>
-<screen>
-# ./jdk-<replaceable>version_number</replaceable>-linux-i586.bin
-</screen>
- </para>
- </listitem>
- <listitem>
- <para>
- Use the <keycap>Enter</keycap> key to scroll through the license agreement. At the end, type <userinput>yes</userinput> to accept the license agreement.
- </para>
- </listitem>
- <listitem>
- <para>
- Change into the directory where the <filename>jdk-<replaceable>version_number</replaceable>-linux-i586.bin</filename> file was downloaded to. Run the following command as root to move the Sun JDK into the <filename>/usr/local/</filename> directory:
- </para>
- <para>
-<screen>
-# cp -r jdk<replaceable>version_number</replaceable>/ /usr/local/
-</screen>
- </para>
- </listitem>
- </orderedlist>
- </section>
-
- <section id="sect-Portal_EAP-Installation-Installing_JBoss_EAP">
- <title>Installing JBoss EAP</title>
- <para>
- To install JBoss EAP:
- </para>
- <orderedlist>
- <listitem>
- <para>
- Navigate to the <ulink url="https://support.redhat.com/portal/login.html">JBoss Customer Support Portal (CSP)</ulink>. Log in using your CSP username and password:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/login.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- Click on the <computeroutput>Browse Software, Patches and Config Advisories</computeroutput> link underneath the <computeroutput>SOFTWARE</computeroutput> section:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/browse_software.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- On the <computeroutput>SOFTWARE DOWNLOADS</computeroutput> page, click on the <computeroutput>JBoss Application Server</computeroutput> link located on the left hand side of the page:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/csp_eap.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- Click on the <computeroutput>Application Platform 4.3.0.GA zip</computeroutput> link:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/select_eap.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- On the <computeroutput>SOFTWARE DETAILS</computeroutput> page, click on the <computeroutput>Download</computeroutput> link to download JBoss EAP:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/eap_details.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- Unzip the JBoss EAP ZIP file. It does not matter which directory the files are extracted to. The rest of the guide refers to the JBoss EAP installation directory - this directory, where you unzip JBoss EAP to, becomes the installation directory.The <computeroutput>$JBOSS_HOME</computeroutput> variable is used to define the JBoss installation directory, and is configured in <xref linkend="sect-Portal_EAP-Configuration-Configuring_Your_Local_Environment" />. When you see <computeroutput>$JBOSS_HOME</computeroutput> being used, it is referring to the JBoss EAP installation directory.
- </para>
- </listitem>
- </orderedlist>
- <para>
- Note: these instructions are not exhaustive. For full details of the JBoss EAP installation, please refer to the <ulink url="http://www.redhat.com/docs/manuals/jboss/jboss-eap-4.3/doc/Installation_G...">JBoss EAP Installation Guide</ulink>.
- </para>
- </section>
-
- <section id="sect-Portal_EAP-Installation-Installing_JBoss_Portal">
- <title>Installing JBoss Portal</title>
- <para>
- There are two versions of JBoss Portal: High Availability (HA), which includes clustering support, and non-High Availability (non-HA), which is the standard version. To install the non-HA version of JBoss Portal:
- </para>
- <orderedlist>
- <listitem>
- <para>
- Navigate to the <ulink url="https://support.redhat.com/portal/login.html">JBoss Customer Support Portal (CSP)</ulink>. Log in using your CSP username and password:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/login.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- Click on the <computeroutput>Browse Software, Patches and Config Advisories</computeroutput> link underneath the <computeroutput>SOFTWARE</computeroutput> section:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/browse_software.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- On the <computeroutput>SOFTWARE DOWNLOADS</computeroutput> section, click on the <computeroutput>JBoss Portal</computeroutput> link, located on the left hand side of the page:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/select_portal.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- Click on the <computeroutput>JBoss Portal <replaceable>x.x.x</replaceable> binary distribution </computeroutput> link, where <replaceable>x.x.x</replaceable> is the latest version Note: the latest version may differ from the following image:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/csp_portal.png" />
- </imageobject>
- </mediaobject>
- <para>
- At the time of writing, the latest version of JBoss Portal was 2.6.4.
- </para>
- </listitem>
- <listitem>
- <para>
- On the <computeroutput>SOFTWARE DETAILS</computeroutput> page, click on the <computeroutput>Download</computeroutput> link to download JBoss Portal. Note: the latest version may differ from the following image:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/portal_details.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- Unzip the JBoss Portal ZIP file. It does not matter which directory the files are extracted to.
- </para>
- </listitem>
- <listitem>
- <para>
- Change into the directory where JBoss Portal was extracted to. Copy the <filename>jboss-portal.sar</filename> directory into the <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename> directory.
- </para>
- <para>
- <note>
- <title>JBoss EAP Configurations</title>
- <para>
- When referring to a subdirectory within the JBoss EAP installation directory, for example, <filename>$JBOSS_HOME/server/<replaceable>configuration</replaceable>/deploy/</filename>, replace <replaceable>configuration</replaceable> with <computeroutput>all</computeroutput>, <computeroutput>minimal</computeroutput>, <computeroutput>default</computeroutput>, or <computeroutput>production</computeroutput>. This guides assumes the use of the <computeroutput>default</computeroutput> configuration.
- </para>
- </note>
- </para>
- </listitem>
- </orderedlist>
- <para>
- To install the HA version of JBoss Portal:
- </para>
- <orderedlist>
- <listitem>
- <para>
- Navigate to the <ulink url="https://support.redhat.com/portal/login.html">JBoss Customer Support Portal (CSP)</ulink>. Log in using your CSP username and password:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/login.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- Click on the <computeroutput>Browse Software, Patches and Config Advisories</computeroutput> link underneath the <computeroutput>SOFTWARE</computeroutput> section:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/browse_software.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- On the <computeroutput>SOFTWARE DOWNLOADS</computeroutput> section, click on the <computeroutput>JBoss Portal</computeroutput> link, located on the left hand side of the page:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/select_portal.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- Click on the <computeroutput>JBoss Portal <replaceable>x.x.x</replaceable> (clustered) distribution </computeroutput> link, where <replaceable>x.x.x</replaceable> is the latest version. Note: the latest version may differ from the following image:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/csp_portal_ha.png" />
- </imageobject>
- </mediaobject>
- <para>
- At the time of writing, the latest version of JBoss Portal HA was 2.6.4.
- </para>
- </listitem>
- <listitem>
- <para>
- On the <computeroutput>SOFTWARE DETAILS</computeroutput> page, click on the <computeroutput>Download</computeroutput> link to download JBoss Portal HA. Note: the latest version may differ from the following image:
- </para>
- <mediaobject>
- <imageobject>
- <imagedata fileref="./images/portal_ha_details.png" />
- </imageobject>
- </mediaobject>
- </listitem>
- <listitem>
- <para>
- Unzip the JBoss Portal HA ZIP file. It does not matter which directory the files are extracted to.
- </para>
- </listitem>
- <listitem>
- <para>
- Change into the directory where JBoss Portal HA was extracted to. Copy the <filename>jboss-portal-ha.sar</filename> directory into the <filename>$JBOSS_HOME/server/all/deploy/</filename> directory.
- </para>
- </listitem>
- </orderedlist>
- <para>
- This guide does not cover how to configure JBoss Portal for clustering. To configure JBoss Portal for a clustered environment, please refer to the <ulink url="http://docs.jboss.com/jbportal/v2.6.3/referenceGuide/html/clustering.html">Cluster Configuration</ulink> section of the <ulink url="http://docs.jboss.com/jbportal/v2.6.3/referenceGuide/html/">JBoss Portal Reference Guide</ulink>. The JBoss Portal Reference Guide is also available in the <filename>docs/referenceGuide</filename> subdirectory, underneath the directory where the JBoss Portal HA ZIP file was extracted to.
- </para>
- </section>
-
-</chapter>
-
Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Portal_EAP.ent
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Portal_EAP.ent 2008-12-02 10:30:12 UTC (rev 12329)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Portal_EAP.ent 2008-12-03 05:02:44 UTC (rev 12330)
@@ -1,4 +0,0 @@
-<!ENTITY PRODUCT "Documentation">
-<!ENTITY BOOKID "Portal_EAP">
-<!ENTITY YEAR "2008">
-<!ENTITY HOLDER "Red Hat, Inc">
Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Portal_EAP.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Portal_EAP.xml 2008-12-02 10:30:12 UTC (rev 12329)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Portal_EAP.xml 2008-12-03 05:02:44 UTC (rev 12330)
@@ -1,14 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<book>
- <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
- <xi:include href="Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
- <xi:include href="Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
- <xi:include href="Configuration.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
- <xi:include href="Databases.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
- <xi:include href="Running_Eap.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
- <xi:include href="Appendix.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-</book>
-
Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Preface.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Preface.xml 2008-12-02 10:30:12 UTC (rev 12329)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Preface.xml 2008-12-03 05:02:44 UTC (rev 12330)
@@ -1,8 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<preface>
- <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
-</preface>
-
Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml 2008-12-02 10:30:12 UTC (rev 12329)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml 2008-12-03 05:02:44 UTC (rev 12330)
@@ -1,21 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE revhistory PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<revhistory>
- <revision>
- <revnumber>1.0</revnumber>
- <date>Mon Feb 11 2008</date>
- <author>
- <firstname>Murray</firstname>
- <surname>McAllister</surname>
- <email>mmcallis(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Initial Content Release</member>
- </simplelist>
- </revdescription>
- </revision>
-</revhistory>
-
Deleted: docs/enterprise/trunk/Installation_Guide/en-US/Running_Eap.xml
===================================================================
--- docs/enterprise/trunk/Installation_Guide/en-US/Running_Eap.xml 2008-12-02 10:30:12 UTC (rev 12329)
+++ docs/enterprise/trunk/Installation_Guide/en-US/Running_Eap.xml 2008-12-03 05:02:44 UTC (rev 12330)
@@ -1,44 +0,0 @@
-<?xml version='1.0'?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<chapter id="chap-Portal_EAP-Running_JBoss_EAP">
- <title>Running JBoss EAP</title>
- <para>
- To run JBoss EAP:
- </para>
- <orderedlist>
- <listitem>
- <para>
- If you are using an external database, such as MySQL, make sure that the database is running.
- </para>
- </listitem>
- <listitem>
- <para>
- Change into the <filename>$JBOSS_HOME/bin/</filename> directory. If you are running Linux, run the following command to start JBoss EAP:
- </para>
- <para>
-<screen>
-sh run.sh -c default
-</screen>
- </para>
- <para>
- If you are running <trademark class="registered">Windows</trademark>, run the following command:
- </para>
- <para>
-<screen>
-run.bat -c default
-</screen>
- </para>
- <para>
- Note: these examples assume you are using the default configuration. If you are not, replace <computeroutput>default</computeroutput> with either all, minimal, or production.
- </para>
- </listitem>
- <listitem>
- <para>
- Use a Web browser to navigate to <computeroutput>http://localhost:8080/portal</computeroutput>
- </para>
- </listitem>
- </orderedlist>
-</chapter>
-
17 years, 5 months
- 1
- 0
JBoss Portal SVN: r12329 - in branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium: cms and 1 other directories.
by portal-commits＠lists.jboss.org
Author: vrockai
Date: 2008-12-02 05:30:12 -0500 (Tue, 02 Dec 2008)
New Revision: 12329
Modified:
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/DashboardTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossPortalSeleniumTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossSelenium.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossSeleniumTestListener.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSArchiveUploadTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileUploadTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/AdminPortalTestCase.java
Log:
removed redundant screenshots and text output
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/DashboardTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/DashboardTestCase.java 2008-12-02 03:33:35 UTC (rev 12328)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/DashboardTestCase.java 2008-12-02 10:30:12 UTC (rev 12329)
@@ -70,12 +70,8 @@
selenium.select(SEL_THEME, "label=renaissance");
- System.out.println("HOLA2"+selenium.getSelectedLabel(SEL_THEME));
selenium.click(SUB_THEMESEL);
selenium.waitForPageToLoad(PAGE_LOAD);
- System.out.println("HOLA2"+selenium.getSelectedLabel(SEL_THEME));
- selenium.windowMaximize();
- selenium.captureScreenshot("2x.jpg");
selenium.click(LNK_DASHBOARD);
selenium.waitForPageToLoad(PAGE_LOAD);
@@ -84,10 +80,6 @@
selectIfNotSelected(SEL_PAGE,"DashTestPage");
- selenium.windowMaximize();
- selenium.captureScreenshot("2.jpg");
- for (String s: selenium.getSelectOptions(SEL_THEME))
- System.out.println("LABEL!:"+s);
Assert.assertEquals(selenium.getSelectedLabel(SEL_THEME), "renaissance", "Previously selected theme other then expected.");
}
@@ -101,17 +93,10 @@
selenium.windowMaximize();
selectIfNotSelected(SEL_PAGE,"DashTestPage");
- selenium.captureScreenshot("3x1.jpg");
selenium.select(SEL_LAYOUT, "label=generic");
- System.out.println("HOLA3"+selenium.getSelectedLabel(SEL_LAYOUT));
- selenium.captureScreenshot("3x2.jpg");
selenium.click("//input[@name='jbpnsabcsnpbj:_viewRoot:dashboardLayoutForm:j_id12']");
- selenium.captureScreenshot("3x3.jpg");
selenium.waitForPageToLoad(PAGE_LOAD);
- selenium.captureScreenshot("3x4.jpg");
- System.out.println("HOLA3"+selenium.getSelectedLabel(SEL_LAYOUT));
- selenium.captureScreenshot("3x.jpg");
selenium.click(LNK_DASHBOARD);
selenium.waitForPageToLoad(PAGE_LOAD);
@@ -120,10 +105,6 @@
selectIfNotSelected(SEL_PAGE,"DashTestPage");
- selenium.windowMaximize();
- selenium.captureScreenshot("3.jpg");
- for (String s: selenium.getSelectOptions(SEL_LAYOUT))
- System.out.println("LABEL!:"+s);
Assert.assertEquals(selenium.getSelectedLabel(SEL_LAYOUT), "generic", "Previously selected layout other then expected.");
}
@@ -133,34 +114,21 @@
selenium.click(LNK_DASHBOARD);
selenium.waitForPageToLoad(PAGE_LOAD);
- selenium.windowMaximize();
- selenium.captureScreenshot("1x1.jpg");
selenium.click(LNK_CONFIGURE_DASHBOARD);
selenium.waitForPageToLoad(PAGE_LOAD);
- selenium.windowMaximize();
- selenium.captureScreenshot("1x21.jpg");
selectIfNotSelected(SEL_PAGE,"DashTestPage");
selenium.click("link=Who's online portlet");
- selenium.captureScreenshot("1x221.jpg");
selenium.waitForPageToLoad(PAGE_LOAD);
- selenium.captureScreenshot("1x222.jpg");
waitForElement("portlet-editor-title");
- //selenium.waitForPageToLoad(PAGE_LOAD);
- selenium.windowMaximize();
- selenium.captureScreenshot("1x3.jpg");
selenium.click(SUB_ADDCENTER);
selenium.waitForPageToLoad(PAGE_LOAD);
- selenium.windowMaximize();
- selenium.captureScreenshot("1x4.jpg");
selenium.click(LNK_DASHBOARD);
selenium.waitForPageToLoad(PAGE_LOAD);
selenium.click("link=DashTestPage");
selenium.waitForPageToLoad(PAGE_LOAD);
- selenium.windowMaximize();
- selenium.captureScreenshot("1.jpg");
Assert.assertTrue(selenium.isTextPresent("Current users"));
Assert.assertTrue(selenium.isTextPresent("Among them: * logged-in"));
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossPortalSeleniumTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossPortalSeleniumTestCase.java 2008-12-02 03:33:35 UTC (rev 12328)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossPortalSeleniumTestCase.java 2008-12-02 10:30:12 UTC (rev 12329)
@@ -150,7 +150,6 @@
protected void waitForElement(String locator) {
for (int second = 0;; second++) {
if (second >= ELEM_TIMEOUT) {
- selenium.captureScreenshot("err.jpg");
Assert.fail("Element " + locator + " not found.");
}
try {
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossSelenium.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossSelenium.java 2008-12-02 03:33:35 UTC (rev 12328)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossSelenium.java 2008-12-02 10:30:12 UTC (rev 12329)
@@ -42,7 +42,7 @@
} catch (IOException e1) {
e1.printStackTrace();
}
-
+ windowMaximize();
captureScreenshot(name +".jpg");
count++;
@@ -63,6 +63,7 @@
} catch (IOException e1) {
e1.printStackTrace();
}
+ windowMaximize();
captureScreenshot("shot"+ count +".jpg");
count++;
throw new SeleniumException(e);
@@ -82,6 +83,7 @@
} catch (IOException e1) {
e1.printStackTrace();
}
+ windowMaximize();
captureScreenshot("shot"+ count +".jpg");
count++;
throw new SeleniumException(e);
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossSeleniumTestListener.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossSeleniumTestListener.java 2008-12-02 03:33:35 UTC (rev 12328)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossSeleniumTestListener.java 2008-12-02 10:30:12 UTC (rev 12329)
@@ -23,7 +23,6 @@
@Override
public void onTestFailure(ITestResult tr) {
- System.out.println("F");
String name = "F_"+tr.getName()+"-" + count ;
try {
PrintWriter out = new PrintWriter(new BufferedWriter(new FileWriter(name + ".html")));
@@ -32,6 +31,7 @@
} catch (IOException e1) {
e1.printStackTrace();
}
+ selenium.windowMaximize();
selenium.captureScreenshot(name + ".jpg");
count++;
}
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSArchiveUploadTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSArchiveUploadTestCase.java 2008-12-02 03:33:35 UTC (rev 12328)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSArchiveUploadTestCase.java 2008-12-02 10:30:12 UTC (rev 12329)
@@ -43,7 +43,6 @@
@Test(enabled = true, description = "Test archive consisting of two files upload.")
public void testArchiveUpload() {
- //System.out.println("archive adress:" + WORKSPACE);
// canceling at the first stage
selenium.click(LNK_ADMIN);
@@ -102,7 +101,6 @@
@Test(enabled = true, description = "Test archive consisting of > 100 files upload.")
public void testManyFilesArchiveUpload() {
- //System.out.println("archive adress:" + WORKSPACE);
selenium.click(LNK_ADMIN);
selenium.waitForPageToLoad(PAGE_LOAD);
@@ -137,7 +135,6 @@
@Test(enabled = true, description = "Test archive consisting of 21MB file upload.")
public void testBigArchiveUpload() {
- //System.out.println("archive adress:" + WORKSPACE);
selenium.click(LNK_ADMIN);
selenium.waitForPageToLoad(PAGE_LOAD);
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileUploadTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileUploadTestCase.java 2008-12-02 03:33:35 UTC (rev 12328)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileUploadTestCase.java 2008-12-02 10:30:12 UTC (rev 12329)
@@ -89,8 +89,6 @@
selenium.type("title", "file to upload");
selenium.select("language", "label=Afar");
- //System.out.println(WORKSPACE);
-
selenium.type("response", WORKSPACE + "/test_files/testFile.txt");
selenium.click("submit");
selenium.waitForPageToLoad(PAGE_LOAD);
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/AdminPortalTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/AdminPortalTestCase.java 2008-12-02 03:33:35 UTC (rev 12328)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/AdminPortalTestCase.java 2008-12-02 10:30:12 UTC (rev 12329)
@@ -68,7 +68,7 @@
clickIfVisible(TAB_PORTALOBJ_ID);
clickIfVisible(LINK_PORTALS_ID);
- savePage("4.html");
+
Assert.assertFalse(selenium.isTextPresent("TestPortal"), "Not created page already exist.");
selenium.type(INPUT_PORTALNAME, "TestPortal");
17 years, 5 months
- 1
- 0
JBoss Portal SVN: r12328 - branches/JBoss_Portal_Branch_2_7/core/src/bin/portal-core-war/themes/renewal.
by portal-commits＠lists.jboss.org
Author: wesleyhales
Date: 2008-12-01 22:33:35 -0500 (Mon, 01 Dec 2008)
New Revision: 12328
Modified:
branches/JBoss_Portal_Branch_2_7/core/src/bin/portal-core-war/themes/renewal/portal_style.css
Log:
JBPORTAL-2249
Modified: branches/JBoss_Portal_Branch_2_7/core/src/bin/portal-core-war/themes/renewal/portal_style.css
===================================================================
--- branches/JBoss_Portal_Branch_2_7/core/src/bin/portal-core-war/themes/renewal/portal_style.css 2008-12-01 11:23:27 UTC (rev 12327)
+++ branches/JBoss_Portal_Branch_2_7/core/src/bin/portal-core-war/themes/renewal/portal_style.css 2008-12-02 03:33:35 UTC (rev 12328)
@@ -60,7 +60,7 @@
width: 250px;
height: 27px;
position: absolute;
- left: 29px;
+ left: 7px;
top: 3px;
}
@@ -82,7 +82,7 @@
/* min width for IE */
#expander {
- /*position: relative;*/
+ position: relative;
padding: 0 0 0 0;
margin: 0 -327px 0 -327px;
@@ -172,12 +172,11 @@
#regionA {
/* test to swap columns...
float: right; */
-
width: 30%;
float: left;
margin: 0px;
padding: 0px;
- min-width: 250px; /*height: 300px;*/
+/*height: 300px;*/
}
#regionB {
@@ -215,8 +214,6 @@
/* used to clear float in regionA,B,C divs so that
footer spans bottom of page */
-/* used to clear float in regionA,B,C divs so that
-footer spans bottom of page */
hr.cleaner {
clear: both;
height: 1px;
@@ -237,23 +234,36 @@
}
ul#tabsHeader {
- width: 100%;
list-style: none;
- margin: 0;
+ margin: 0 0 -5px 0;
padding: 0;
position:absolute;
+ bottom: 0px;
+ left: 0;
+ min-width: 550px;
+ z-index: 1;
+}
+
+* html ul#tabsHeader {
+ list-style: none;
+ margin: 0 0 -5px 0;
+ padding: 0;
+ position:absolute;
bottom: -5px;
left: 0;
+ min-width: 550px;
z-index: 1;
}
ul#tabsHeader li {
+ display: inline;
float: left;
height: 29px;
font-family: Lucida, Tahoma, Verdana, sans-serif;
font-size: 12px;
margin: 0 1px 0 1px;
position: relative;
+ white-space: nowrap;
}
ul#tabsHeader li,
@@ -262,7 +272,18 @@
background-repeat: no-repeat;
}
-ul#tabsHeader li a,
+ul#tabsHeader li a{
+ background-position: top left;
+ background-repeat: no-repeat;
+ padding: 5px 15px 0 15px;
+ display: block;
+ height: 29px;
+ font-weight: bold;
+ width: 55px;
+ white-space: nowrap;
+}
+
+
ul#tabsHeader li#current a{
background-position: top left;
background-repeat: no-repeat;
@@ -270,8 +291,11 @@
display: block;
height: 29px;
font-weight: bold;
+ white-space: nowrap;
}
+
+
ul#tabsHeader li#current {
background-image: url( 'images/nav-active-right2.gif' );
}
17 years, 5 months
- 1
- 0
JBoss Portal SVN: r12327 - in branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium: cms and 1 other directories.
by portal-commits＠lists.jboss.org
Author: vrockai
Date: 2008-12-01 06:23:27 -0500 (Mon, 01 Dec 2008)
New Revision: 12327
Modified:
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/DashboardTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/IdentityAdminTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossSeleniumTestListener.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/WSRPTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSArchiveUploadTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSDirectoryTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileUploadTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileWorkflowTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/AdminPortalTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/DashboardsTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/PortletDefinitionsTestCase.java
branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/PortletInstancesTestCase.java
Log:
screenshots fix
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/DashboardTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/DashboardTestCase.java 2008-12-01 10:29:25 UTC (rev 12326)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/DashboardTestCase.java 2008-12-01 11:23:27 UTC (rev 12327)
@@ -30,12 +30,13 @@
@BeforeMethod(groups = { "log" })
public void loginBeforeTest() {
+ logoutIfPossible();
login("admin", "admin");
}
@AfterMethod(groups = { "log" })
public void logoutAfterTest() {
- logout();
+
}
@Test(enabled = true)
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/IdentityAdminTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/IdentityAdminTestCase.java 2008-12-01 10:29:25 UTC (rev 12326)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/IdentityAdminTestCase.java 2008-12-01 11:23:27 UTC (rev 12327)
@@ -3,9 +3,7 @@
import java.text.MessageFormat;
import org.testng.Assert;
-import org.testng.annotations.AfterClass;
import org.testng.annotations.AfterMethod;
-import org.testng.annotations.BeforeClass;
import org.testng.annotations.BeforeMethod;
import org.testng.annotations.Test;
@@ -88,12 +86,13 @@
@BeforeMethod(groups = { "log" })
public void loginBeforeTest() {
+ logoutIfPossible();
login("admin", "admin");
}
@AfterMethod(groups = { "log" })
public void logoutAfterTest() {
- logoutIfPossible();
+
}
/*
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossSeleniumTestListener.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossSeleniumTestListener.java 2008-12-01 10:29:25 UTC (rev 12326)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/JBossSeleniumTestListener.java 2008-12-01 11:23:27 UTC (rev 12327)
@@ -1,23 +1,29 @@
package org.jboss.portal.test.selenium;
+import java.awt.event.InputMethodEvent;
+import java.awt.event.InputMethodListener;
import java.io.BufferedWriter;
import java.io.FileWriter;
import java.io.IOException;
import java.io.PrintWriter;
+import java.util.List;
+import org.testng.IMethodInstance;
+import org.testng.IMethodInterceptor;
+import org.testng.ITestContext;
import org.testng.ITestResult;
import org.testng.TestListenerAdapter;
import com.thoughtworks.selenium.Selenium;
-public class JBossSeleniumTestListener extends TestListenerAdapter {
+public class JBossSeleniumTestListener extends TestListenerAdapter {//extends ITestListener {
protected static Selenium selenium;
protected static int count;
-
+
@Override
public void onTestFailure(ITestResult tr) {
-
+ System.out.println("F");
String name = "F_"+tr.getName()+"-" + count ;
try {
PrintWriter out = new PrintWriter(new BufferedWriter(new FileWriter(name + ".html")));
@@ -29,5 +35,5 @@
selenium.captureScreenshot(name + ".jpg");
count++;
}
-
+
}
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/WSRPTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/WSRPTestCase.java 2008-12-01 10:29:25 UTC (rev 12326)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/WSRPTestCase.java 2008-12-01 11:23:27 UTC (rev 12327)
@@ -48,13 +48,13 @@
public static String WSRP_CONSUMER_TABLE = "//table[contains(@id,':consumer-list-form:consumersList')]";
@BeforeMethod(groups = { "log" })
public void loginBeforeTest() {
-
+ logoutIfPossible();
login("admin", "admin");
}
@AfterMethod(groups = { "log" })
public void logoutAfterTest() {
- logout();
+ //logout();
}
@Test(enabled = true, description = "Creating a standard BEA consumer.")
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSArchiveUploadTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSArchiveUploadTestCase.java 2008-12-01 10:29:25 UTC (rev 12326)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSArchiveUploadTestCase.java 2008-12-01 11:23:27 UTC (rev 12327)
@@ -32,12 +32,13 @@
@BeforeMethod( groups = { "log" })
public void loginBeforeTest() {
+ logoutIfPossible();
login("admin", "admin");
}
@AfterMethod( groups = { "log" })
public void logoutAfterTest() {
- logout();
+
}
@Test(enabled = true, description = "Test archive consisting of two files upload.")
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSDirectoryTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSDirectoryTestCase.java 2008-12-01 10:29:25 UTC (rev 12326)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSDirectoryTestCase.java 2008-12-01 11:23:27 UTC (rev 12327)
@@ -24,12 +24,13 @@
@BeforeMethod( groups = { "log" })
public void loginBeforeTest() {
+ logoutIfPossible();
login("admin", "admin");
}
@AfterMethod(groups = { "log" })
public void logoutAfterTest() {
- logout();
+
}
@Test(enabled = true, description="Directory creation.")
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileTestCase.java 2008-12-01 10:29:25 UTC (rev 12326)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileTestCase.java 2008-12-01 11:23:27 UTC (rev 12327)
@@ -19,12 +19,13 @@
@BeforeMethod(groups = { "log" })
public void loginBeforeTest() {
+ logoutIfPossible();
login("admin", "admin");
}
@AfterMethod( groups = { "log" })
public void logoutAfterTest() {
- logout();
+
}
@Test(enabled = true, description = "Common file structure browsing test.")
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileUploadTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileUploadTestCase.java 2008-12-01 10:29:25 UTC (rev 12326)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileUploadTestCase.java 2008-12-01 11:23:27 UTC (rev 12327)
@@ -24,12 +24,13 @@
@BeforeMethod(groups = { "log" })
public void loginBeforeTest() {
+ logoutIfPossible();
login("admin", "admin");
}
@AfterMethod(groups = { "log" })
public void logoutAfterTest() {
- logout();
+
}
@Test(enabled = true, description = "canceling of file upload")
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileWorkflowTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileWorkflowTestCase.java 2008-12-01 10:29:25 UTC (rev 12326)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/cms/CMSFileWorkflowTestCase.java 2008-12-01 11:23:27 UTC (rev 12327)
@@ -26,12 +26,13 @@
@BeforeMethod(groups = { "log" })
public void loginBeforeTest() {
+ logoutIfPossible();
login("admin", "admin");
}
@AfterMethod( groups = { "log" })
public void logoutAfterTest() {
- logout();
+
}
@Test(enabled = true, description = "Simple file creation.")
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/AdminPortalTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/AdminPortalTestCase.java 2008-12-01 10:29:25 UTC (rev 12326)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/AdminPortalTestCase.java 2008-12-01 11:23:27 UTC (rev 12327)
@@ -51,12 +51,13 @@
@BeforeMethod(groups = { "log" })
public void loginBeforeTest() {
+ logoutIfPossible();
login("admin", "admin");
}
@AfterMethod(groups = { "log" })
public void logoutAfterTest() {
- logout();
+
}
@Test(enabled = true)
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/DashboardsTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/DashboardsTestCase.java 2008-12-01 10:29:25 UTC (rev 12326)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/DashboardsTestCase.java 2008-12-01 11:23:27 UTC (rev 12327)
@@ -41,13 +41,14 @@
@BeforeMethod(groups = { "log" })
public void loginBeforeTest() {
+ logoutIfPossible();
login("admin", "admin");
goToDash();
}
@AfterMethod(groups = { "log" })
public void logoutAfterTest() {
- logout();
+
}
@Test(enabled = true)
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/PortletDefinitionsTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/PortletDefinitionsTestCase.java 2008-12-01 10:29:25 UTC (rev 12326)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/PortletDefinitionsTestCase.java 2008-12-01 11:23:27 UTC (rev 12327)
@@ -25,6 +25,7 @@
@BeforeMethod(groups = { "log" })
public void loginBeforeTest() {
+ logoutIfPossible();
login("admin", "admin");
goToPD();
}
Modified: branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/PortletInstancesTestCase.java
===================================================================
--- branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/PortletInstancesTestCase.java 2008-12-01 10:29:25 UTC (rev 12326)
+++ branches/JBoss_Portal_Branch_2_7/testsuite/ui-tests/src/org/jboss/portal/test/selenium/portal/PortletInstancesTestCase.java 2008-12-01 11:23:27 UTC (rev 12327)
@@ -42,13 +42,14 @@
@BeforeMethod(groups = { "log" })
public void loginBeforeTest() {
+ logoutIfPossible();
login("admin", "admin");
goToPI();
}
@AfterMethod(groups = { "log" })
public void logoutAfterTest() {
- logout();
+
}
@Test(enabled = true)
17 years, 5 months
- 1
- 0