Difference between revisions of "Post Installation"

From GreenVulcano Wiki
Jump to: navigation, search
Line 11: Line 11:
 
{| class="note"
 
{| class="note"
 
|-
 
|-
| [[File:helpIcon.jpeg]]
+
| [[File:info.png]]
 
| The ''jboss-service.xml'' is present in the following location:  
 
| The ''jboss-service.xml'' is present in the following location:  
 
: $GV_SERVER/conf  
 
: $GV_SERVER/conf  
Line 45: Line 45:
 
{| class="note"
 
{| class="note"
 
|-
 
|-
| [[File:helpIcon.jpeg]]
+
| [[File:info.png]]
 
| The file ''login-config.xml'' is present in the following path:
 
| The file ''login-config.xml'' is present in the following path:
 
:$GV_SERVER/conf
 
:$GV_SERVER/conf
Line 63: Line 63:
 
{| class="note"
 
{| class="note"
 
|-
 
|-
| [[File:helpIcon.jpeg]]
+
| [[File:info.png]]
 
| The third part configurable components, in order to be integrated with {{GVESB}}, <br/>can be copied in the following directory:  
 
| The third part configurable components, in order to be integrated with {{GVESB}}, <br/>can be copied in the following directory:  
 
: $GV_HOME/application/deploy
 
: $GV_HOME/application/deploy

Revision as of 18:59, 24 January 2012

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_SERVER/bin/start_GreenV.sh
$GV_SERVER/bin/stop_GreenV.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:

Info.png 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:

<classpath codebase="file://${gv.app.home}/application/gvlib" archives="*"/>
<classpath codebase="file://${gv.app.home}/application/lib" archives="*"/>

before

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

Change in the same file the URLs value for the mbean:

 name: jboss.deployment: type = DeploymentScanner, flavor = URL

adding the following string separated by a comma:

 file://${gv.app.home}/application/deploy/

For example:

<mbean code="org.jboss.deployment.scanner.URLDeploymentScanner" name="jboss.deployment:type=DeploymentScanner,flavor=URL">
....
  <attribute name="URLs">deploy/,file:${gv.app.home}/application/deploy/</attribute>
....
</mbean>

Modify the file login-config.xml as follow:

Info.png The file login-config.xml is present in the following path:
$GV_SERVER/conf
<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>
Info.png 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 follow:

$GV_HOME/
application/
deploy/
gvlib/
lib/
BIRTReportEngine/
doc/
dtds/
gvconsole/
etc/
lock/
gvdte/
log/
webservices/
xmlconfig/
$JBOSS_HOME/
bin/
client/
docs/
lib/
server/
GreenV/ --> alias $GV_SERVER
bin/
conf/
deploy
lib/