Difference between revisions of "Post Installation"

From GreenVulcano Wiki
Jump to: navigation, search
(Created page with "After installation and configuration previously described, make sure that, in case of *nix systems, the user with which {{GVESB}} will be executed has permission for the followi...")
 
Line 1: Line 1:
After installation and configuration previously described, make sure that, in case of *nix systems, the user with which {{GVESB}} will be executed  has permission for the following script:
+
After installation and configuration previously described, make sure that, in case of *nix systems, the user with which {{GVESB}} will be executed  has permission for the following scripts:
  
 
: $GV_SERVER/bin/start_GreenV.sh<br/>
 
: $GV_SERVER/bin/start_GreenV.sh<br/>
Line 5: Line 5:
 
: $JBOSS_HOME/bin/run.sh<br/>
 
: $JBOSS_HOME/bin/run.sh<br/>
 
: $JBOSS_HOME/bin/shutdown.sh
 
: $JBOSS_HOME/bin/shutdown.sh
 
  
 
'''Finalizing the installation'''
 
'''Finalizing the installation'''
 
  
 
If you have chosen to perform the installation by downloading the {{GVESB}} Package that does not include JBoss, you need to change some files with steps described below:
 
If you have chosen to perform the installation by downloading the {{GVESB}} Package that does not include JBoss, you need to change some files with steps described below:
 
+
{| class="note"
 
 
{| class="wikitable" style="margin: 1em auto 1em auto;"
 
 
|-
 
|-
| [[File:helpIcon.jpeg]] || The jboss-service.xml is present in the following location:  
+
| [[File:helpIcon.jpeg]]
 +
| The ''jboss-service.xml'' is present in the following location:  
 
: $GV_SERVER/conf  
 
: $GV_SERVER/conf  
 
The variable gv.app.home defined in the script ''start'' indicates the home directory of the product.
 
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'':
 
Add the following lines to the file ''jboss-service.xml'':
 
+
<syntaxhighlight lang="XML">
: <classpath codebase="file://${gv.app.home}/application/gvlib" archives="*"/>
+
<classpath codebase="file://${gv.app.home}/application/gvlib" archives="*"/>
: <classpath codebase="file://${gv.app.home}/application/lib" archives="*"/>
+
<classpath codebase="file://${gv.app.home}/application/lib" archives="*"/>
 
+
</syntaxhighlight>
 
before
 
before
 
+
<syntaxhighlight lang="XML">
: <classpath codebase="${jboss.server.lib.url:lib}" archives="*"/>
+
<classpath codebase="${jboss.server.lib.url:lib}" archives="*"/>
 
+
</syntaxhighlight>
  
 
Change in the same file the URLs value for the ''mbean'':
 
Change in the same file the URLs value for the ''mbean'':
 
+
  name: jboss.deployment: type = DeploymentScanner, flavor = URL
: name: jboss.deployment: type = DeploymentScanner, flavor = URL
 
  
 
adding the following string separated by a comma:
 
adding the following string separated by a comma:
 
+
  file://${gv.app.home}/application/deploy/
: file://${gv.app.home}/application/deploy/
 
  
 
For example:
 
For example:
 
+
<syntaxhighlight lang="XML">
: <mbean code="org.jboss.deployment.scanner.URLDeploymentScanner" name="jboss.deployment:type=DeploymentScanner,flavor=URL">
+
<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>
+
  <attribute name="URLs">deploy/,file:${gv.app.home}/application/deploy/</attribute>
::. . . . .
+
....
:</mbean>
+
</mbean>
 
+
</syntaxhighlight>
  
 
Modify the file ''login-config.xml'' as follow:
 
Modify the file ''login-config.xml'' as follow:
 
+
{| class="note"
{| class="wikitable" style="margin: 1em auto 1em auto;"
 
 
|-
 
|-
| [[File:helpIcon.jpeg]] || The file ''login-config.xml'' is present in the following path  
+
| [[File:helpIcon.jpeg]]
: $GV_SERVER/conf
+
| The file ''login-config.xml'' is present in the following path:
 +
:$GV_SERVER/conf
 
|}
 
|}
  
 +
<syntaxhighlight lang="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>
 +
</syntaxhighlight>
  
:<application-policy name="gvesb">
+
{| class="note"
::<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>
 
 
 
 
 
{| class="wikitable" style="margin: 1em auto 1em auto;"
 
 
|-
 
|-
| [[File:helpIcon.jpeg]] || The third part configurable components, in order to be integrated with {{GVESB}}, <br/>can be copied in the following directory:  
+
| [[File:helpIcon.jpeg]]
 +
| 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
 
|}
 
|}
 
  
 
When the installation procedure described above is finished, the file system will be structured as follow:
 
When the installation procedure described above is finished, the file system will be structured as follow:
 
 
::$GV_HOME/
 
::$GV_HOME/
 
:::application/
 
:::application/

Revision as of 18:53, 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:

HelpIcon.jpeg 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:

HelpIcon.jpeg 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>
HelpIcon.jpeg 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/