-
Configure the database. This example assumes you are using a PostgreSQL database.
- Copy the PostgreSQL driver JAR to <JBOSS_HOME>/server/default/lib.
- Follow the instructions for configuring the PostgreSQL database.
-
Configure UTF-8 support.
-
Edit the following files:
- <JBOSS_HOME>/server/default/deploy/jbossweb.sar/server.xml
- <JBOSS_HOME>/server/all/deploy/jbossweb.sar/server.xml
-
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" /> <!-- A AJP 1.3 Connector on port 8009 --> <Connector protocol="AJP/1.3" port="8009" URIEncoding="UTF-8" address="${jboss.bind.address}" redirectPort="8443" />
-
Edit the following files:
-
Configure logging.
-
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>
-
(Optional) The logging configuration that is set reduces the debug output but there
will still be a large volume of output sent to the console. To reduce it further, add
the following to the
<JBOSS_HOME>/server/default/conf/jboss-log4j.xml file:
<category name="org.jboss.logging.Log4jService$URLWatchTimerTask"> <priority value="INFO"/> </category> <category name="org.jboss.system.server.Server"> <priority value="INFO"/> </category> <category name="org.jboss"> <priority value="WARN"/> </category> <category name="net"> <priority value="WARN"/> </category> <category name="org.alfresco"> <priority value="WARN"/> </category> <category name="org.alfresco.repo.policy"> <priority value="WARN"/> </category> <category name="org.springframework"> <priority value="WARN"/> </category> <category name="org.hibernate"> <priority value="WARN"/> </category> <category name="org.hibernate.cache.ReadWriteCache"> <priority value="ERROR"/> </category> <category name="org.hibernate.cache.EhCacheProvider"> <priority value="ERROR"/> </category> <category name="org.hibernate.engine.StatefulPersistenceContext.ProxyWarnLog"> <priority value="ERROR"/> </category> <category name="org.apache.myfaces"> <priority value="ERROR"/> </category> <category name="org.jbpm.jpdl.xml.JpdlXmlReader"> <priority value="ERROR"/> </category>
-
Edit the <JBOSS_HOME>/server/default/conf/jboss-log4j.xml
file to reduce the huge debug log output.
-
Configure Hibernate.
-
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>
-
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.
-
Open the <JBOSS_HOME>/bin/run.conf file.
-
Set the conf directory in the global classpath to ensure that
the SkyVault
extensions and web-extensions directories
are available:
Add the JBOSS_CLASSPATH= setting, specifying the full path of your conf directory, for example:
JBOSS_CLASSPATH="/opt/app_servers/jboss_ga/server/default/conf"
An example for this setting on Windows is:
set JBOSS_CLASSPATH=d:\app_servers\jboss_ga\server\default\conf
-
Ensure that the <JBOSS_HOME>/bin/run.conf file specifies
appropriate JVM memory parameters in JAVA_OPTS.
For example, the following are minimums:
-Xms128m -Xmx1024m -XX:MaxPermSize=256m
-
Enable JMX monitoring and automatic discovery of SkyVault by ensuring that
JAVA_OPTS contains the following parameters:
-Dcom.sun.management.jmxremote -Dalfresco.home=.
-
For running SkyVault on Windows 2003 Server with OpenOffice 3.2, ensure that the
JAVA_OPTS contains the following parameters:
-Djboss.server.temp.dir.overrideJavaTmpDir=true
- Save the run.conf file.
-
Set the conf directory in the global classpath to ensure that
the SkyVault
extensions and web-extensions directories
are available:
-
Edit the filtered packages list.
- Open the <JBOSS_HOME>/server/default/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml file, and then locate the filteredPackages property of the WarClassLoaderDeployer bean.
-
Open the
<extension>\war-deployers-jboss-beans.xml.fragment.sample
file.
This sample file contains a WarClassLoaderDeployer bean definition fragment for use when configuring JBoss.
- Copy the full WarClassLoaderDeployer bean from the sample file.
-
In the war-deployers-jboss-beans.xml file, paste the sample
bean fragment over the WarClassLoaderDeployer bean.
The bean definition contains the filteredPackages list that is required for SkyVault. This list is on one line and must not contain any breaks.
- Save the <JBOSS_HOME>/server/default/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml file.
This setting avoids collisions between the JVM bootstrap classes and those embedded in the war.
-
Execute the <JBOSS_HOME>/bin/run.sh file.
Note: 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
Note: The following warning message will appear in the log but can be ignored, since SkyVault 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. - Start the SkyVault server.
You are here
Configuring JBoss for SkyVault
This section describes how to configure an SkyVault installation on
JBoss.
These steps assume that you know the path of the JBoss directory, which is represented
as <JBOSS_HOME>.
© 2017 TBS-LLC. All Rights Reserved. Follow @twitter