Post Installation

After Installation and configuration previously described, make sure that, in case of *nix systems, the user with which GreenVulcano^® ESB will be executed has permission for the following scripts:

$GV_HOME/bin/env_GreenV.sh

$GV_HOME/bin/start_GreenV.sh

$GV_HOME/bin/stop_GreenV.sh

$GV_HOME/hsqldb/bin/start_DB.sh

$GV_HOME/hsqldb/stop_DB.sh

$JBOSS_HOME/bin/run.sh

$JBOSS_HOME/bin/shutdown.sh

Finalizing the installation

If you have chosen to perform the installation by downloading the GreenVulcano^® ESB Package that does not include JBoss, you need to change some files with steps described below:

The jboss-service.xml is present in the following location: $GV_SERVER/conf The variable gv.app.home defined in the script start indicates the home directory of the product.

Add the following lines to the file jboss-service.xml:

<!-- GreenVulcano ESB library directory -->
<classpath codebase="${gv.app.home}/application/lib" archives="*"/>

before

<classpath codebase="${jboss.server.lib.url}" archives="*"/>
<classpath codebase="${jboss.common.lib.url}" archives="*"/>

Change in the file the bootstrap/profile.xml the configuration of the mbean BootstrapProfileFactory as follows:

The file profile.xml is present in the following path: $GV_SERVER/conf/bootstrap

<bean name="BootstrapProfileFactory" class="org.jboss.system.server.profileservice.repository.StaticProfileFactory">
      <property name="bindingsURI">${jboss.server.home.url}conf/bindingservice.beans</property>
      <property name="bootstrapURI">${jboss.server.home.url}conf/jboss-service.xml</property>
      <property name="deployersURI">${jboss.server.home.url}deployers</property>
      <property name="applicationURIs">
         <list elementClass="java.net.URI">
            <value>${jboss.server.home.url}deploy</value>
            <!-- GreenVulcano ESB deployment directory -->
            <value>file://${gv.app.home}/application/deploy</value>
         </list>
      </property>
      <property name="attachmentStoreRoot">${jboss.server.data.dir}/attachments</property>
      <property name="profileFactory"><inject bean="ProfileFactory" /></property>
</bean>

Modify the file login-config.xml as follows:

The file login-config.xml is present in the following path: $GV_SERVER/conf The files *.properties are present in the following path: $GV_HOME/xmlconfig The OdeHsqlDbRealm needs a DataSource registered with name ds.ode usually configured in: $GV_HOME/application/deploy/gvesb-db-ds.xml

<application-policy name="gvesb">
    <authentication>
        <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule"
                      flag="required">
            <module-option name="usersProperties">gvesb-users.properties</module-option>
            <module-option name="rolesProperties">gvesb-roles.properties</module-option>
        </login-module>
    </authentication>
</application-policy>
<application-policy name = "OdeHsqlDbRealm">
    <authentication>
        <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule"
                      flag = "required">
            <module-option name = "principal">ode</module-option>
            <module-option name = "userName">ode</module-option>
            <module-option name = "password">ode</module-option>
            <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=ds.ode</module-option>
        </login-module>
    </authentication>
</application-policy>

The third part configurable components, in order to be integrated with GreenVulcano® ESB, can be copied in the following directory: $GV_HOME/application/deploy

When the installation procedure described above is finished, the file system will be structured as follows:

$GV_HOME/

application/

deploy/: contains the application components (ejb, war, ear) and the configuration files of the application server (JBoss) resources.

lib/  : contains the GreenVulcano^® ESB support libraries.

BIRTReportEngine/ :contains BIRT report definitions

BpelProcess/ :contains ODE BPEL prosess definitions

doc/

extra/  : contains the configuration files fragments and DDL scripts to enable logging, statistics and savepoints on various DataBases

licenses/ : contains the license of the libraries used by GreenVulcano^® ESB

reference/: contains the PDF files that are the GreenVulcano^® ESB configuration reference guides and XSD files that describe the internal structure of some GreenVulcano^® ESB XML

dtds/  : contains the dtds used by GV Console^®/VulCon^® to validate the GreenVulcano^® ESB configuration

gvconsole/: contains the GV Console^® work files and the configurations back-up

etc/

lock/

gvdte/  : contains the transformations maps used by the GreenVulcano^® ESB DTE (Data Transformation Engine).

datasource/

bin/  : contains the maps for binary transformation (binary buffers <-> XML)

xsl/  : contains the maps for XSL transformations

xsd/  : contains the XSD file used to validate the transformations input/output

log/  : contains the log files of the various GreenVulcano^® ESB subsystems, differentiated by the subsystem name and day. In this directory are generated the dumps of input/output buffers of services invoked by GV Console^®

Rules/ : Drools rules definition files

webservices/

modules/  : contains the MAR files that defines the extra modules for AXIS services

services/ : contains the AAR files that defines the WebService published by GreenVulcano^® ESB

xmlconfig/: contains the GreenVulcano^® ESB configuration XML files and the license enabling the adapters for the Enterprise version.

js/  : contains the JavaScript files used to create pre-configured execution contexts

wsdl/  : contains the WSDL files of the WebService published and invoked by GreenVulcano^® ESB

xsds/  : contains the XSD files used in the WSDL service published by GreenVulcano^® ESB and the validation of XML documents.

$JBOSS_HOME/

bin/

client/

common/

docs/

lib/

server/

GreenV/ --> alias $GV_SERVER

conf/

deploy/

lib/

lib/ : JBoss server log directory