RE: [Axis2] Management Interface

[Soumadeep]

Chathura,   I am still waiting for an answer, could you please reply.   Thanks Soumadeep   -----Original Message----- From: Soumadeep [mailto:[EMAIL PROTECTED] Sent: Sunday, March 19, 2006 1:05 PM To: axis-dev@ws.apache.org Subject: [Axis2] Management Interface   Chathura,   External monitoring applications would require event details from AXIS2/Synapse for instrumenting management information and other stats let me know how are we going to expose it. Ref http://marc2.theaimsgroup.com/?l=synapse-dev&m=114070435931685&w=3   Out of the following, which one are we planning to use: 1) Using an MBean to broadcast notifications from AXIS2 2) Using a Synapse mediator to send notification to a remote listener   The other thing that we might need to deal with is ObjectNames from a JMX perspective.   Thoughts please!   Best regards Soumadeep   FYI: the information that could be required is, would have a schema once the information is finalized. <ManagementInformationExchange>   <EndPointReference>String</EndPointReference>   <TransactionID>String</TransactionID>   <TimeStamp>2001-12-17T09:30:47.0Z</TimeStamp>   <Operation>String</Operation>   <ClientIP>String</ClientIP>   <UserAgent>String</UserAgent>   <ProviderEPR>String</ProviderEPR>   <SOAPRequest>String</SOAPRequest>   <SOAPResponse>String</SOAPResponse>   <ExecutionStatus>    <Synapse>true</Synapse>    <Provider>true</Provider>   </ExecutionStatus>   <ExecutionTime>    <TotalRoundTrip>2147483647</TotalRoundTrip>    <ProviderExecutionTime>2147483647</ProviderExecutionTime>    <MediatorExecutionTime>     <Mediator name="M1">2147483647</Mediator>     <Mediator name="M2">2147483647</Mediator>     <Mediator name="M3">2147483647</Mediator>    </MediatorExecutionTime>   </ExecutionTime>  </ManagementInformationExchange> -----Original Message----- From: Chathura Ekanayake [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 08, 2006 11:16 PM To: axis-dev@ws.apache.org Subject: Re: [Axis2] Management Interface   Hi Soumadeep,   The features provided by the management system is seperated into different components as much as possible. For example administrating services are done by a seperate class (ServiceManager) and adminstrating modules are done by another class (ModuleManager). Interfaces for these different manageable parts are also provided by seperate classes. As an example web services interface for adminstrating services is provided by the "AxisServices" web service and module adminstrating can be accessed by the "AxisModules" web service.   This seperation holds for management features as well. All statistics monitoring are done by a seperate set of classes (DynamicStatsManager, ServiceStats and OperationStats) and the interface is provided by the "AxisDynamicStats" web service. We can add more management functionality as new features to existing classes or as completely new classes. Is this kind of seperation ok?   Beacause of this seperation, we can even pack administration and management as seperate libraries. I will implement security for all web services interfaces based on WS-Security. I think this will satisfy the security concerns over allowing administrating functionality via web services.   I am planing to add following features to the management system:   - JMX based interface. - Improving the web based management console to act as a JMX client. - Security for WS interfaces based on WS-Security. - More statistics monitoring to capture statistics pointed out by you and Steve Loughran.   Please give your ideas about this and any other things which should go into management system.   Regards,   Chathura.           On 3/8/06, Soumadeep <[EMAIL PROTECTED] > wrote: Chathura,   Please see my comments inline. I think we need to be specific about management related features and administration related features. I would suggest you please look at (Mukund's) code for management interfaces in the scratch area. link  http://svn.apache.org/viewcvs?rev=383852&view=rev   Thanks Soumadeep -----Original Message----- From: Chathura Ekanayake [mailto: [EMAIL PROTECTED]] Sent: Wednesday, March 08, 2006 2:26 PM To: axis-dev@ws.apache.org Subject: [Axis2] Management Interface   Hi,   I am sending the initial work I have done on Axis2 management interface as the attached patch.   Currently it provides following feathers via web services interface: [Soumadeep] These are Administration related features    - Get all available services, operations and modules - Configuring parameters at all levels (i.e. Global, Service, Operation) - Get modules engaged at all levels - Engaging modules at all levels - Get available service groups and services grouped under those service groups - Get available transports and configure transport parameters [Soumadeep] And this is Management related  - Get statistics about entire Axis2 engine, individual services and operations (number of in messages, out messages, fault in messages, fault out messages)   A documentation about building and installing the management interface is included in the "management\xdocs\management.html".   Please commit the patch to the scratch area - https://svn.apache.org/repos/asf/webservices/axis2/trunk/archive/java/scratch   Regards,   Chathura.