Use this information to configure a SkyVault installation on JBoss.
These steps assume that you know the path of the JBoss directory, which is represented
as <JBOSS_EAP_HOME>.
-
Install the JDBC driver for MySQL database.
- To install the required JDBC driver as a core module, create the <JBOSS_EAP_HOME>\modules\com\mysql\main directory.
- Copy the JDBC driver, mysql-connector-java-5.1.20-bin.jar to <JBOSS_EAP_HOME>\modules\com\mysql\main.
-
Create the
<JBOSS_EAP_HOME>\modules\com\mysql\main\module.xml file with
the following contents:
<?xml version="1.0" encoding="UTF-8"?> <module xmlns="urn:jboss:module:1.0" name="com.mysql"> <resources> <resource-root path="mysql-connector-java-5.1.20-bin.jar"/> </resources> <dependencies> <module name="javax.api"/> </dependencies> </module>
-
Configure the MySQL datasource resource in the server subsystem.
Modify the subsystem datasources in the <JBOSS_EAP_HOME>\standalone\configuration\standalone.xml file to have the following content:
<subsystem xmlns="urn:jboss:domain:datasources:1.1"> <datasources> <datasource jndi-name="java:jboss/datasources/MySqlDS" pool-name="MySqlDS" enabled="true"> <connection-url>jdbc:mysql://localhost:3306/alfresco</connection-url> <driver>com.mysql</driver> <pool> <min-pool-size>10</min-pool-size> <max-pool-size>100</max-pool-size> <prefill>true</prefill> </pool> <security> <user-name>alfresco</user-name> <password>alfresco</password> </security> <statement> <prepared-statement-cache-size>32</prepared-statement-cache-size> <share-prepared-statements>true</share-prepared-statements> </statement> </datasource> <drivers> <driver name="com.mysql" module="com.mysql"> <driver-class>com.mysql.jdbc.Driver</driver-class> <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class> </driver> </drivers> </datasources> </subsystem>
Note: If SkyVault is deployed with MS SQL Server, set SNAPSHOT transaction isolation level by adding the following to the subsystem datasources:<new-connection-sql>SET TRANSACTION ISOLATION LEVEL SNAPSHOT;</new-connection-sql>
Ensure that ALLOW_SNAPSHOT_ISOLATION database option is set to ON.
Also ensure that enable-welcome-root is set to false. For example:
<subsystem xmlns="urn:jboss:domain:web:1.5" default-virtual-server="default-host" native="false"> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/> <virtual-server name="default-host" enable-welcome-root="false"> <alias name="localhost"/> <alias name="example.com"/> </virtual-server> </subsystem>
-
Apply a workaround to upgrade the JBoss library to avoid EclipseJavaCompiler
problems.
CAUTION:From JBoss EAP 6.4.0 onwards, this step is not needed.Note: There is an outstanding issue with Java 8 and the Eclipse Compiler for Java. Follow these steps to avoid the problem, and see ClassFormatException problem if you require more information about of the JBoss issue.
- Download the Eclipse Compiler for Java 4.4 JAR file: ECJ 4.4
-
Navigate to
jboss-eap-6.2\modules\system\layers\base\org\jboss\as\web\main\module.xml
and change the following line:
<resource-root path="ecj-3.7.2-redhat-1.jar"/>
to<resource-root path="ecj-4.4.jar"/>
- Add the new ECJ version JAR file to the jboss-eap-6.2\modules\system\layers\base\org\jboss\as\web\main\ directory.
- (Optional): Configure another datasource for the Activiti ID generator that is used in activiti-context.xml (recommended for production). For simplicity, you can reuse MySqlDS as defined in step 2.
-
Unzip <TEMP>/alfresco.war and check or modify the
WEB-INF\jboss-web.xml file to have correct references to the main
data source (in this example, it is MySqlDS, which is defined in
standalone.xml) and to
activitiIdGeneratorDataSource (used in
activiti-context.xml):
<?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE jboss-web PUBLIC"-//JBoss //DTD Web Application 4.2//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_2.dtd"> <jboss-web> <resource-ref> <res-ref-name>jdbc/dataSource</res-ref-name> <jndi-name>java:jboss/datasources/MySqlDS</jndi-name> </resource-ref> <resource-ref> <res-ref-name>jdbc/activitiIdGeneratorDataSource</res-ref-name> <jndi-name>java:jboss/datasources/MySqlDS</jndi-name> </resource-ref> </jboss-web>
-
Copy vaadin-application-server-class-loader-workaround-1.0.1.jar
from <TEMP>\web-server\lib to
<ALFRESCO_HOME>\WEB-INF\lib of the unzipped SkyVault-enterprise-5.1.3.ear.
Note: <TEMP> refers to the path of the temporary directory.
-
Configure logging.
-
(For Windows): In
<JBOSS_EAP_HOME>\bin\standalone.conf.bat, add the following
to JAVA_OPTS:
set "JAVA_OPTS=%JAVA_OPTS% -Dorg.jboss.as.logging.per-deployment=false"
(For Unix/Linux): In <JBOSS_EAP_HOME>/bin/standalone.conf, add the following to JAVA_OPTS:
JAVA_OPTS="$JAVA_OPTS -Dorg.jboss.as.logging.per-deployment=false"
-
Modify logging subsystem in
<JBOSS_EAP_HOME>\standalone\configuration\standalone.xml.
- Change the default level for <root-logger> from INFO to ERROR in <subsystem xmlns="urn:jboss:domain:logging:1.3">.
- Add the logger elements as children to <subsystem xmlns="urn:jboss:domain:logging:1.3”> with logging configuration taken from SkyVault-enterprise-5.1.3.ear\alfresco.war\WEB-INF\classes\log4j.properties.
Note: For more information on logging mapping elements, see JBoss logging.
-
(For Windows): In
<JBOSS_EAP_HOME>\bin\standalone.conf.bat, add the following
to JAVA_OPTS:
-
Set appropriate memory values for –Xms, -Xmx,
-XX:MaxPermSize and other JVM options in:
- <JBOSS_EAP_HOME>\bin\standalone.conf.bat (For Windows) or
- <JBOSS_EAP_HOME>/bin/standalone.conf (For Unix/Linux).
-
Configure URI_ENCODING with UTF-8. Set the following system properties
in standalone.xml after extensions tag:
<system-properties> <property name="org.apache.catalina.connector.URI_ENCODING" value="UTF-8"/> <property name="org.apache.catalina.connector.USE_BODY_ENCODING_FOR_QUERY_STRING" value="true"/> </system-properties>
-
Disable the JBoss webservices subsystem as it conflicts with SkyVault CMIS. The
following lines should be removed from
<JBOSS_EAP_HOME>\standalone\configuration\standalone.xml:
<extension module="org.jboss.as.webservices"/>
<subsystem xmlns="urn:jboss:domain:webservices:1.2"> <modify-wsdl-address>true</modify-wsdl-address> <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host> <endpoint-config name="Standard-Endpoint-Config"/> <endpoint-config name="Recording-Endpoint-Config"> <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM"> <handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/> </pre-handler-chain> </endpoint-config> </subsystem>
- Compress SkyVault.war and SkyVault-enterprise-5.1.3.ear to include the changes made.
- Start the standalone JBoss server.
-
Set the server's IP address in the JBoss Management Console.
- Open the JBoss Management Console.
- Set the server IP address in Profiles > General Configurations > Interfaces > Network Interfaces > Available Interfaces.
- Set the server IP address in all the corresponding SkyVault configuration files, including SkyVault-global.properties.
-
Deploy SkyVault.
- Open the JBoss Management Console.
- Navigate to Runtime > Manage Deployments.
- Click the Add button.
- Browse and select the modified SkyVault-one-ear-distribution-5.1.3.zip file.
- After the EAR file is added, click the Enable button.
SkyVault is successfully deployed.
Note: Oracle JMX is not supported when using JBoss EAP. This is a known issue; see JBoss issue
AS7-1859. SkyVault recommends that you use JBoss JMX instead. For information on
how to connect to the JBoss AS7 JMX MBeanServer from JConsole, see the JBoss Developer documentation.