030202010106 SERVICIOS AMBIENTALES DE LOS ECOSISTEMAS FORESTALES

PROGRAMÁTICA

030202010106 SERVICIOS AMBIENTALES DE LOS ECOSISTEMAS FORESTALES

You can install and deploy the Alfresco WAR on the JBoss application server.

Ensure that JBoss is installed. Review the Supported Platforms page on the Support Portal for more information. These steps also assume that you know the path of the JBoss directory, which is represented in these steps as <JBOSS_HOME>.

1. Browse to the Enterprise download area.

2. Download the following file to your local machine:

alfresco-enterprise-3.4.3.zip

3. Create a temporary directory and uncompress the file.

4. Copy the alfresco-global.properties file from the temporary directory to the

<JBOSS_HOME>/conf directory.

5. Edit the parameters in the alfresco-global.properties file to suit your environment. 6. Copy or move the alfresco.war and share.war file from the uncompressed Alfresco

WAR to the <JBOSS_HOME>/deploy directory.

7. Follow the instructions for configuring JBoss for Alfresco.

Configuring JBoss for Alfresco

This section describes how to configure an Alfresco installation on JBoss.

a. Copy the PostgreSQL driver JAR to <JBOSS_HOME>/server/default/lib.

b. Follow the instructions for configuring the PostgreSQL database. 2. Configure UTF-8 support.

a. Edit the following files:

• <JBOSS_HOME>/server/default/deploy/jbossweb.sar/server.xml

• <JBOSS_HOME>/server/all/deploy/jbossweb.sar/server.xml

b. Add URIEncoding="UTF-8" to the following section:

<Connector protocol="HTTP/1.1" port="8080" URIEncoding="UTF-8" address="${jboss.bind.address}"

connectionTimeout="20000" redirectPort="8443" />

3. Configure logging.

a. Edit the <JBOSS_HOME>/server/default/conf/jboss-log4j.xml file to reduce the

huge debug log output. For example: <root> <priority value="INFO" /> <appender-ref ref="CONSOLE"/> <appender-ref ref="FILE"/> </root>

b. (Optional) The logging configuration that is set reduces the debug output but there will still be a lot of output sent to the console. To reduce it further, adding the following to the <JBOSS_HOME>/server/default/conf/jboss-log4j.xml file:

<priority value="ERROR"/> </category> <category name="org.apache.myfaces"> <priority value="ERROR"/> </category> <category name="org.jbpm.jpdl.xml.JpdlXmlReader"> <priority value="ERROR"/> </category> 4. Configure Hibernate.

a. Edit the <JBOSS_HOME>/server/default/deployers/ejb3.deployer/ META-INF/jpa-deployers-jboss-beans.xml file, and then

change the hibernate.bytecode.provider=javassist line to hibernate.bytecode.provider=cglib. For example: <entry> <key>hibernate.bytecode.provider</key> <value>cglib</value> </entry>

5. Configure the JVM options.

a. Ensure that the <JBOSS_HOME>/bin/run.conf file specifies appropriate JVM memory settings in JAVA_OPTS.

For example, the following are minimums:

-Xms128m -Xmx1024m -XX:MaxPermSize=256m

b. Enable JMX monitoring and automatic discovery of Alfresco by the Hyperic plugin by ensuring that JAVA_OPTS contains the following arguments:

-Dcom.sun.management.jmxremote -Dalfresco.home=.

c. Open the <JBOSS_HOME>/server/default/deployers/jbossweb.deployer/META- INF/war-deployers-jboss-beans.xml file, and then edit the filteredPackages

property of the WarClassLoaderDeployer bean. Add the following filtered packages.

<bean name="WarClassLoaderDeployer" class="org.jboss.web.tomcat.service.deployers.WarClassLoaderDeployer"> <property name="relativeOrder">-1</property> <property name="filteredPackages">javax.activation,javax.servlet,javax.servlet.jsp, javax.servlet.jsp.jstl,javax.servlet.jsp.jstl.core,javax.servlet.jsp.jstl.fmt, javax.servlet.jsp.jstl.sql,javax.servlet.jsp.jstl.tlv,javax.xml, javax.xml.bind,javax.xml.bind.annotation,javax.xml.bind.annotation.adapters, javax.xml.bind.attachment,javax.xml.bind.helpers,javax.xml.bind.util,javax.xml.crypto, javax.xml.crypto.dom,javax.xml.crypto.dsig,javax.xml.crypto.dsig.dom,javax.xml.crypto.dsig.keyinfo, javax.xml.crypto.dsig.spec,javax.xml.datatype,javax.xml.messaging, javax.xml.namespace,javax.xml.parsers,javax.xml.rpc,javax.xml.rpc.encoding, javax.xml.rpc.handler,javax.xml.rpc.handler.soap,javax.xml.rpc.holders, javax.xml.rpc.server,javax.xml.rpc.soap,javax.xml.soap,javax.xml.stream, javax.xml.stream.events,javax.xml.stream.util,javax.xml.transform, javax.xml.transform.dom,javax.xml.transform.sax,javax.xml.transform.stream, javax.xml.validation,javax.xml.ws,javax.xml.ws.handler,javax.xml.ws.handler.soap, javax.xml.ws.http,javax.xml.ws.soap,javax.xml.ws.spi,javax.xml.ws.wsaddressing, javax.xml.xpath,org.apache.commons.logging,org.apache.commons.logging.impl, org.apache.xerces,org.apache.xerces.dom,org.apache.xerces.dom.events, org.apache.xerces.dom3,org.apache.xerces.dom3.as,org.apache.xerces.impl, org.apache.xerces.impl.dtd,org.apache.xerces.impl.dtd.models,org.apache.xerces.impl.dv, org.apache.xerces.impl.dv.dtd,org.apache.xerces.impl.dv.util, org.apache.xerces.impl.dv.xs,org.apache.xerces.impl.io,org.apache.xerces.impl.msg, org.apache.xerces.impl.validation,org.apache.xerces.impl.xpath, org.apache.xerces.impl.xpath.regex,org.apache.xerces.impl.xs, org.apache.xerces.impl.xs.identity,org.apache.xerces.impl.xs.models, org.apache.xerces.impl.xs.opti,org.apache.xerces.impl.xs.traversers, org.apache.xerces.impl.xs.util,org.apache.xerces.jaxp, org.apache.xerces.jaxp.datatype,org.apache.xerces.jaxp.validation,

org.apache.xerces.parsers,org.apache.xerces.util,org.apache.xerces.xinclude, org.apache.xerces.xni,org.apache.xerces.xni.grammars, org.apache.xerces.xni.parser,org.apache.xerces.xpointer, org.apache.xerces.xs,org.apache.xerces.xs.datatypes,org.apache.xml, org.apache.xml.resolver,org.apache.xml.resolver.apps,org.apache.xml.resolver.etc, org.apache.xml.resolver.etc.catalog.dtd,org.apache.xml.resolver.etc.catalog.rng, org.apache.xml.resolver.etc.catalog.xsd,org.apache.xml.resolver.etc.xcatalog.dtd, org.apache.xml.resolver.helpers,org.apache.xml.resolver.readers, org.apache.xml.resolver.tools,org.apache.xml.security, org.apache.xml.security.algorithms,org.apache.xml.security.algorithms.implementations, org.apache.xml.security.c14n,org.apache.xml.security.c14n.helper, org.apache.xml.security.c14n.implementations,org.apache.xml.security.encryption, org.apache.xml.security.exceptions,org.apache.xml.security.keys, org.apache.xml.security.keys.content,org.apache.xml.security.keys.content.keyvalues, org.apache.xml.security.keys.content.x509,org.apache.xml.security.keys.keyresolver, org.apache.xml.security.keys.keyresolver.implementations, org.apache.xml.security.keys.storage,org.apache.xml.security.keys.storage.implementations, org.apache.xml.security.resource,org.apache.xml.security.resource.schema, org.apache.xml.security.signature,org.apache.xml.security.transforms, org.apache.xml.security.transforms.implementations, org.apache.xml.security.transforms.params,org.apache.xml.security.utils, org.apache.xml.security.utils.resolver,org.apache.xml.security.utils.resolver.implementations, org.apache.xml.serialize,org.apache.xmlcommons,org.xml,org.xml.sax,org.xml.sax.ext, org.xml.sax.helpers,org.w3c.css,org.w3c.css.sac,org.w3c.css.sac.helpers, org.w3c.dom,org.w3c.dom.bootstrap,org.w3c.dom.css,org.w3c.dom.events, org.w3c.dom.html,org.w3c.dom.ls,org.w3c.dom.ranges,org.w3c.dom.smil, org.w3c.dom.stylesheets,org.w3c.dom.svg,org.w3c.dom.traversal, org.w3c.dom.views,org.w3c.dom.xpath</property> </bean>

This avoids collisions between the JVM bootstrap classes and those embedded in the war.

6. Execute the <JBOSS_HOME>/bin/run.sh file.

By default JBoss will only listen on the localhost network adapter, rather than the adapter with a real IP address connected to the outside world. To override this, start JBoss with the -b addr option, specifying the IP address of the network adapter you

want to listen on or 0.0.0.0 to listen on all adapters. For example: run.sh -b 0.0.0.0

The following warning message will appear in the log but can be ignored, since Alfresco disables the faces RI with a special parameter in web.xml:

[STDOUT] 16:59:43,814 ERROR [shared_impl.config.MyfacesConfig] Both MyFaces and the RI are on your classpath. Please make sure to use only one of the two JSF- implementations.

7. Start the Alfresco server.

Installing Alfresco on WebLogic

This section describes how to install Alfresco as an Enterprise ARchive format (EAR) into Oracle WebLogic 10.3.

Certain components of Alfresco require access to the EAR file contents as files. These instructions require expanding the .ear into exploded format, as described in the

WebLogic documentation. The Alfresco WebLogic deployment solution makes use of a Filter Classloader, configured in the weblogic-application.xml file, to ensure that the unmodified contents of the Alfresco web module will run in WebLogic.

Before you start:

• Install OpenOffice and ensure that the ooo.exe property is set in the the alfresco- global.properties file

• Create an alfresco database and user with appropriate permissions

• Install WebLogic 10.3 without creating any domains or servers 1. Browse to the Enterprise download area.

2. Download the alfresco-enterprise-3.4.3.ear file. 3. Obtain the license (.lic file).

4. Create a directory in the WebLogic user's home directory to host the exploded EAR file and copy the alfresco-enterprise-3.4.3.ear file to that directory.

5. Run the following commands in the new directory to explode the EAR file: a. mkdir alfresco b. cd alfresco c. jar xvf ../alfresco-enterprise-3.4.3.ear d. mv alfresco.war alfresco.war.tmp e. mv share.war share.war.tmp f. mkdir alfresco.war g. mkdir share.war h. cd alfresco.war i. jar xvf ../alfresco.war.tmp j. cd ../share.war k. jar xvf ../share.war.tmp

6. Open the WebLogic Configuration Wizard.

For example, on Unix, use the following command to create a new domain, alf_domain:

<Weblogic_HOME>/common/bin/config.sh

7. Create a directory for the license file.

For example, in Linux, use the following command:

mkdir -p <Weblogic_HOME>/user_projects/domains/alf_domain/alfresco/ extension/license

8. Move the license .lic file into the license directory.

9. In the <Weblogic_HOME>/user_projects/domains/alf_domain directory, create the

alfresco-global.properties file.

Modify the file in the same way you would for global properties configuration. 10. In the alfresco-global.properties file, add the following line:

db.pool.statements.enable=false

This property setting is required to make the DBCP connection pool work on WebLogic. 11. Move the database JDBC driver .jar to the <Weblogic_HOME>/user_projects/

domains/alf_domain/lib directory.

12. Edit the <Weblogic Home>/user_projects/domains/alf_domain/config/config.xml

file and add the following before the end of the </security-configuration> section: <enforce-valid-basic-auth-credentials>false</enforce-valid-basic-auth- credentials>

13. Open the <Weblogic Home>/user_projects/domains/alf_domain/bin/

setDomainEnv.sh file, and then edit all of the lines prefixed with MEM_MAX_PERM_SIZE to increase the PermGen space.

MEM_MAX_PERM_SIZE="-XX:MaxPermSize=256m"

MEM_MAX_PERM_SIZE_32BIT="-XX:MaxPermSize=256m"

You may see different combinations of these lines, depending on whether you have installed on a 64 or 32-bit platform.

This setting may need to be increased further, depending on the number of deployed applications.

14. Set the heap size parameter appropriately. The following setting is a recommendation:

WLS_MEM_ARGS="-Xmx2048m"

15. For Weblogic 10.3.2.0, the following extra edit is required to ensure that alf_domain is in

the global classpath.

PRE_CLASSPATH=$WL_HOME/user_projects/domains/alf_domain

16. Open the <Weblogic Home>/wlserver_10.3/common/nodemanager/

nodemanager.properties file, and then edit the settings so that the PermGen settings are passed on to the Alfresco server by the node manager.

StartScriptEnabled=true

17. Start the domain admin server. For example:

<Weblogic_HOME>/user_projects/domains/alf_domain/startWebLogic.sh

18. Open a web browser and log in to the admin server (for example, at http:// localhost:7001/console). The default user name and password is weblogic. 19. To enable automatic control of your Alfresco server:

a. Create a machine with the details of the machine running the domain. This will allow the node manager to control servers on that machine.

b. Create a server called AlfrescoServer, within the new machine.

Note that you have to choose a unique port number. A good port number to choose is 8080 because it is preconfigured in Share. You can leave the host name blank if you want it to listen on all network adapters.

c. Ensure that the node manager is running (for example, <Weblogic_HOME>/ wlserver_10.3/server/bin/startNodeManager.sh).

You will be able to use the admin server Change Center panel to start and stop the Alfresco server.

Refer to the WebLogic documentation to find out how to create a machine and new server within the machine.

20. In the left pane of the Administration Console, click Deployments. 21. In the right pane, click Install.

22. Using the Install Application Assistant, locate the directory of your exploded EAR file (containing the alfresco.war and share.war directories).

23. Locate the file or directory to install, and then click Next.

24. Check Install this deployment as an application radio button, and then click Next. 25. Click Finish.

26. Click Activate Changes.

27. Using the Change Center panel, restart AlfrescoServer. 28. Log in to Alfresco:

• Alfresco Share at http://localhost:8080/share

If the Alfresco finds a JDBC data source with JNDI path (java:comp/env/jdbc/ dataSource), it will use that rather than the embedded data source. To set

that up in WebLogic you need to define a new global data source, for example,

AlfrescoDataSource. See the WebLogic documentation for more information. Then, map AlfrescoDataSource in to Alfresco by adding the WEB-INF/weblogic.xml file into

alfresco.war containing the following:

<! DOCTYPE weblogic-web-app PUBLIC "-//BEA Systems, Inc.//DTD Web Application 8.1//EN"

"http://www.bea.com/servers/wls810/dtd/weblogic810-web-jar.dtd" > < weblogic-web-app >

< reference-descriptor > < resource-description >

< res-ref-name > jdbc /dataSource </ res-ref-name > < jndi-name > AlfrescoDataSource </ jndi-name > </ resource-description >

</ reference-descriptor > </ weblogic-web-app >

In document PROTECTORA DE BOSQUES (página 59-63)