Instrucciones cluster jboss

Solo disponible en BuenasTareas
  • Páginas : 8 (1918 palabras )
  • Descarga(s) : 0
  • Publicado : 8 de febrero de 2012
Leer documento completo
Vista previa del texto
OBJETIVO
El objetivo del presente documento es documentar los cambios requeridos para configurar jboss en formato Cluster para que se puedan administrar varios VLS’s a través de una sola publicación.


CONFIGURACIÓN

Para iniciar esta configuración es necesario tener instalado Versata.

1. Realizar deploy al VLS del repositorio.


2. Setting Versata configuration properties for asingle cluster on a network
C:\Versata\VLS-5.6-JBoss\Client\lib
To set up JBoss clustering, you need to set the following properties in the VERSATA_HOME\Client\lib\VFCResource.properties file:
�� providerURL=: (for example, host-1:1100,host-2:1100,host-3:1100


The providerURL also could be left empty to use the auto-discovery feature provided by JBoss throughmulticast.


Host=localhost
#---- Servlet Session Tracking -----
# Controls how the servlet tracks sessions. One of:
# versata.vfc.html.servlet.SessionTrackingHTTP
# versata.vfc.html.servlet.SessionTrackingInternal
ServletSessionTrackingClassName=versata.vfc.html.servlet.SessionTrackingHTTP


# Used to control how often (in seconds) the servletcleans out timed out sessions
# when SessionInternalTracking is used
ServletSessionSweepRate=600


xdaAppServerConnectorClassName=versata.vfc.XDAEJBConnector
xdaConnectorClassName=versata.vfc.html.common.XDAPLSEJBConnector
SessionHomeName=VLSContextHome
plsContextHomeName=PLSContextHome
AdminHomeName=VLSContextHome#UserTransactionHomeName=jta/usertransaction
UserTransactionHomeName=java:comp/UserTransaction
Port=1099
lookAndFeel=com.sun.java.swing.plaf.windows.WindowsLookAndFeel
nameService=org.jnp.interfaces.NamingContextFactory


#Clients which use AutoDiscover feature for accessing clustered applications, shall keep providerURL=.
providerURL=:1099, :1099#jnp.discoveryGroup and jnp.discoveryPort should be be set appropriately, for accessing clustered applications using AutoDiscover feature.
#jnp.discoveryGroup=230.0.0.4
#jnp.discoveryPort=1102




java.naming.authoritative=true
#com.ibm.websphere.naming.jndicache.cacheobject=none


# The default JNDI name of the VLS bean is /VLSContextHome.
# If you change thedefault name then set the JNDI name using below variable to override the default name.
# VLSJNDIName=


3. Realizar la publicación del repositorio, colocar en Server Location: 230.0.0.4:1102


[pic]




al término, bajar los servicios


4. Required container configuration changes for enterprise bean clustering

In order to cluster enterprise beans, you need tomodify settings in their EJB descriptor (jboss.xml) files.

C:\Versata\VLS-5.6-JBoss\Config\server\default\deploy\.ear\.jar\META-INF\jboss.xml

Container configuration changes for stateless session beans
When stateless session beans are clustered, no state is involved, so calls can be load balanced on any participating node, meaning any cluster node that has this specific bean deployed. Tocluster a stateless session bean, you need to modify its jboss.xml descriptor to contain a tag. The file is located in \META-INF
[pic]
Figure 4 Settings for entity bean clustering





false


VLSUtil
repositorio/VLSUtil
true

DefaultPartition
org.jboss.ha.framework.interfaces.RoundRobinorg.jboss.ha.framework.interfaces.RoundRobin




objeto1
repositorio/objeto1


objeto2
repositorio/objeto2


objeto3
repositorio/objeto3





In the stateless session bean configuration, only the tag is mandatory. All other elements are the same as in the entity bean configuration....
tracking img