8. Support Engineering Group : Setup and Installation This page last changed on Mar 27, 2012 by kgomes. The MBARI Services server (named services.mbari.org) was setup to host core services for internal and external users. This page documents the setup that was done to get services.mbari.org up and running. Kevin Gomes met with Todd Ruston to talk about what this servers goals are and followed on with a help ticket (ticket number 13231) to I.S. to request that a RHEL 6 virtual machine be configured in the DMZ for this purpose. Pat installed RHEL 6 and named it 'services.mbari.org'. He installed Java 7 from Sun/Oracle and configured it as an alternative Java installation. He then configured it as the default. He then downloaded JBoss 7.1 and unpacked it to the /opt directory. We edited the /opt/jboss-as-7.1.0.Final/bin/init.d/jboss-as.conf file and changed it so the JBoss would run under the 'coredata' account and that the log file for the console output would be sent to /var/log/jboss.log We then copied that file from the JBoss directory to /etc/sysconfig/jboss-as/jboss-as.conf We edited the /opt/jboss-as-7.1.0.Final/bin/init.d/jboss-as-standalone.sh file and changed the location of the jboss-as.conf file to the one in the previous step. We then copied that file to /etc/init.d/jboss.sh
   | Defaults did not work The default scripts did not, strangely enough, work right from the start. See Pat's trouble ticket for the details on what happened and the fix for it.
11. Before starting it, I wanted to get some default configurations and security set up. I logged in as 'coredata' and cd'd to the /opt/jboss-as-7.1.0.Final/bin directory and ran the 'add-user.sh' script and added both 'kgomes' and 'coredata' as ManagementRealm users. This added encrypted passwords and usernames to the /opt/jboss-7.1.0.Final/standalone/configuration/mgmt-users.properties files so those users can interact with the admin application in JBoss. I then started up JBoss to verify it runs OK using:

        sudo /sbin/service jboss start
Initially, the server is configured to run on the 127.0.0.1 interface. That is fine for now. In order to configure data sources that connect to Postgresql databases, I copied the postgresql-9.1-901.jdbc4.jar to the /opt/jboss/standalone/deployments directory which makes the driver available for configuring data sources. I deployed the observations.war file to the services JBoss instance which then made the application available on http://services.mbari.org:8080/observations Cathy configured the mod_proxy on the Apache server to redirect all requests to http://services.mbari.org/observations to the 8080 url. Pete had to open the ports 80 and 8080 to the world to enable this to work. While I was hoping the default setup of the JBoss server to allow only requests from 127.0.0.1 would work with mod_proxy, that does not appear to be the case. Using the management interface, I set the network interface to accept requests from any address. This should probably be looked at again so nobody from the outside can hit the 8080 interface. The next step is to get the RHEL instance and the JBoss server configured to use the Centrify security system to enable SSO authentication.

Document generated by Confluence on Feb 03, 2026 16:22