Management J2EE & JOnAS Domain Management JOnAS Juin 2005

Page 2 © Bull 2005 Management J2EE & JOnAS Overview J1 (master) JMX Service JMX Server Discovery Service Mejb jonasAd min r jmx JMX Service JMX Server Discovery Service J3 (slave) JMX Service JMX Server Discovery Service J2 (slave) D1 Group of JOnAS instances Management from a single admin console JOnAS 4.4 / 4.5 Use  add discovery svc  jonas start –nJ1-Ddomain.name=D1

Page 3 © Bull 2005 Management J2EE & JOnAS Group communication with ip-multicast Easy/Quick to develop J1 (master) Discovery Service URL connector jmx Discovery Service J3 (slave) Discovery Service J2 (slave) Broadcast Remote JMX URL IP multicast - First version– Spec recommends use of a JNDI solution - Don’t cross network devices - specific impl. for FIFO order

Page 4 © Bull 2005 Management J2EE & JOnAS Add discovery & remote connection for domain  JOnAS 4.4 Add MBean J2EEDomain + domain management information in JMX service  JOnAS 4.4 Take into account domain within jonasAdmin  To be able to manage multiple JOnAS instance from a single console  JOnAS 4.4 Take into account domain within MEJB  JOnAS 4.4 Workplan 1/2 Page 4 © Bull 2005

Page 5 © Bull 2005 Management J2EE & JOnAS Add domain management operations at the MBean level & jonasAdmin enhancements  Deployment  Configuration  and so forth Add MBean for cluster management & jonasAdmin enhancements  Cluster = subgroup of JOnAS instances within a domain Workplan 2/2 Page 5 © Bull 2005  JOnAS 4.5

Page 6 © Bull 2005 Management J2EE & JOnAS Domain level deployment Add deployment operations to J2EEDomain MBean:  deployJar(String fileName), deployWar(String fileName),...=> deploy on every server in the domain  deployJar(String[] target, String fileNma),...=> deploy on a subset given by the target -> list of server identifiers (serverName list or J2EEServer ObjectName list) call deployJar(fileName) on the J2EEServer MBeans Add 'progress' attribute to J2EEDomainMBean  initialized to RUNNING when the deploy operation starts  set to COMPLETED when all operations completed  set to FAILED if an operation fails

Page 7 © Bull 2005 Management J2EE & JOnAS JonasAdmin evolution Add 'Deployment' sub-tree to 'Domain' root.  Domain level 'Deployment' will have 4 sub-trees correspondong to the 4 module types (jar, war, ear, rar)  Actions corresponding to the 4 sub-trees are based on the J2EEDomain MBean.  Each sub-tree has to present: a layout allowing to choose the deployment target a layout allowing to choose the file to deploy between the modules installed on the current master. a status based on the progress attribute

Page 8 © Bull 2005 Management J2EE & JOnAS Domain Management – Naming Rules Goal: define rules for the identification of  domains  servers in domains Status Requirements Architecture

Page 9 © Bull 2005 Management J2EE & JOnAS Status The 'administrator' choose a domain name and names for the server instances belonging to the domain:  jonas start -n serverName -Ddomain.name=domainName The 'administrator' is asked to provide unique server names in the domain scope The is no mechanism to enforce unicity is the 'administrator' makes a mistake A Discovery Greeting mechanism have been add to the discovery service in order to detect naming errors and correct them

Page 10 © Bull 2005 Management J2EE & JOnAS Requirements Allow different management policies to be used. Policy examples:  Use or not use enforced naming (probably yes in a large distributed context, but no if a unique 'administrator' has contol)  If no enforcement mechanism is used, allow to plug error detection policy error correction policy

Page 11 © Bull 2005 Management J2EE & JOnAS Architecture requirements: separate mechanisms from policies A three layers architecture: - Discovery layer with Descovery MBean (publisher role) and Eroller and DiscovertClient MBeans (receiver role) – use IP messaging, emit JMX notifs - Management layer with JMXService ans J2EEDomain MBeans containing the domain management information to be used by the admin tools – listen for discovery notifs emitted by the DL - Connection layer – une JMX connectors Policies are to be added into the Management Layer !

Page 12 © Bull 2005 Management J2EE & JOnAS Policy implementation proposition Define and implement new MBeans which implement a given policy (naming enforcement, error detection, error correction, etc) Define how the policy MBeans are integrated in the current architecture Configure discovery service to deploy the desired policy MBeans

Page 13 © Bull 2005 Management J2EE & JOnAS Architecture proposition Make Policy MBeans intercept Discovery notifications, make specified treatement, and possibly emit notifications to the final receptors: the J2EEDomain Mbean and the JMXService.

Page 14 © Bull 2005 Management J2EE & JOnAS