x

1. To install JBoss from a zip file, unzip the file, as follows:

   unzip jboss-eap-6.0.x.zip

   This will create a subdirectory in the form jboss-eap-6.0.

2. Create an administration user, as follows:

   cd install_dir/bin
   ./add-user.sh admin password

   where install_dir refers to /dir/jboss-eap-6.x/jboss-as. This procedure assumes use of the standalone configuration.

3. If installing on a system that is running other JBoss instances or if the following ports are in use, edit the install_dir/standalone/configuration/standalone.xml file and change the following port assignments:

   Note: There are additional ports listed in the standalone.xml file. If you are deploying WebFOCUS, only the services they support do not run and they are not used.

   • 8080 - HTTP port
   • 8443 - HTTPS port
   • 8009 - AJP port
   • 4447 - Remote port
   • 9990 - Management HTTP port
   • 9999 - Management native port
4. If you are using Derby, the JBoss installation already contains the Derby JDBC driver. The default standalone configuration sets java.awt.headless=true. If you need to add another JDBC driver, change the headless setting, or change other JVM settings, edit the install_dir/bin/standalone.conf file. Search for JAVA_OPTS to headless setting or other JVM properties.
5. Start JBoss so that all ports listen on all interfaces. Otherwise, by default, they will only listen on 127.0.0.1. As an alternative to all interfaces, you can specify a specific IP address to listen on, as follows.

   cd install_dir/bin
   ./standalone.sh -b 0.0.0.0 -bmanagement=0.0.0.0

   Note: To stop JBoss, press Ctrl-C.

x

JBoss is delivered with log4j that is not compatible with WebFOCUS and conflicts with ibi_help. As a result, the WebFOCUS web applications need to be modified to use isolated class loaders and parent last class loading. The following modifications are required and assumes that you are in the ibi/WebFOCUS80/webapps directory. Note that the xml files created in each step are not identical.

APPROOT

mv approot.war approot-orig.war mkdir approot
cd approot
jar xf ../approot-orig.war cd WEB-INF

Create the jboss-classloading.xml file with the following:

<?xml version="1.0" encoding="UTF-8"?>
<classloading xmlns="urn:jboss:classloading:1.0" name="approot.war"
domain="approot.war" export-all="NON_EMPTY" import-all="true"
parent-first="false"
/>

cd ..
jar cf ../approot.war . 
cd ..

IBI_HTML

mv ibi_html.war ibi_html-orig.war mkdir ibi_html
cd ibi_html
jar xf ../ibi_html-orig.war cd WEB-INF

Create the jboss-classloading.xml file with the following:

<?xml version="1.0" encoding="UTF-8"?>
<classloading xmlns="urn:jboss:classloading:1.0" name="ibi_html.war"
domain="ibi_html.war" export-all="NON_EMPTY" import-all="true"
parent-first="false"
/>

cd ..
jar cf ../ibi_html.war .
cd ..

IBI_HELP

mv ibi_help.war ibi_help-orig.war
cd ibi_help/WEB-INF (exploded directory already exists)

Create the jboss-classloading.xml file with the following:

<?xml version="1.0" encoding="UTF-8"?>
<classloading xmlns="urn:jboss:classloading:1.0" name="ibi_help.war"
domain="ibi_help.war" export-all="NON_EMPTY" import-all="true"
parent-first="false"
/>

cd ..
jar cf ../ibi_help.war .
cd ..

WebFOCUS will create the new war file as ibi_apps.war to pick up the correct context root, rather than add additional JBoss syntax to the xml files:

cd webfocus/WEB-INF (exploded directory already exists)

Create the jboss-classloading.xml file with the following:

<?xml version="1.0" encoding="UTF-8"?>
<classloading xmlns="urn:jboss:classloading:1.0" name="ibi_apps.war"
domain="ibi_apps.war" export-all="NON_EMPTY" import-all="true"
parent-first="false"
/>

Create the WEB-INF/jboss-deployment-structure.xml file with the following:

<jboss-deployment-structure>
 <deployment>
 <!-- Exclusions allow you to prevent the server from automatically adding some dependencies -->
  <exclusions>
   <module name="org.apache.log4j" />
   <module name="org.apache.commons.logging" />
  </exclusions>
 </deployment>
</jboss-deployment-structure>

cd lib
mv serializer-2.11.0.jar ../../../serializer-2.11.0.save
cd ../..
jar cf ../ibi_apps.war .
cd ..

x

In JBoss EAP 6.0.x or 6.2.x, you can either use the Adminstration Console or the command line to deploy the WebFOCUS web application files. Using the Console requires transferring the war files to the system running the browser. The following demonstrates using the command line interface.

Deploy (the applications start as soon as they are deployed):

cd install_dir/bin
./jboss-cli.sh -connect -controller=localhost:9999 (or the new Management native port if it was modified)
[standalone@localhost:9999 /] deploy WF_install_dir/ibi/WebFOCUS80/webapps/approot.war
[standalone@localhost:9999 /] deploy WF_install_dir/ibi/WebFOCUS80/webapps/ibi_html.war
[standalone@localhost:9999 /] deploy WF_install_dir/ibi/WebFOCUS80/webapps/ibi_help.war
[standalone@localhost:9999 /] deploy WF_install_dir/ibi/WebFOCUS80/webapps/ibi_apps.war
[standalone@localhost:9999 /] exit

Undeploy (the applications are stopped when they are undeployed):

cd install_dir/bin
[standalone@localhost:9999 /] undeploy approot.war
[standalone@localhost:9999 /] undeploy ibi_html.war
[standalone@localhost:9999 /] undeploy ibi_help.war
[standalone@localhost:9999 /] undeploy ibi_apps.war
[standalone@localhost:9999 /]
exit