[Users] Connect easierBSM to Petals ESB

[jlesbegueries]

You could use the EasierBSM as an ESB node but this is not a good practice.

The idea is to have on one side a topology of ESB nodes (EasyESB, Petals...)
to achieve an SOA with business exchanges, and on the other side, a topology
of EasierBSM nodes able to monitor this SOA. 

There is a CLI for EasyESB in experimental 
https://svn.petalslink.org/svnroot/trunk/research/dev/experimental/easyesb/tools/easyesb-cli/
<https://svn.petalslink.org/svnroot/trunk/research/dev/experimental/easyesb/tools/easyesb-cli/>  

that can be used for common operations between EasyESB and EasierBSM. 

A BSM CLI is in development in the context of the CHOREOS project but this
is still a work in progress.
For now I advise you to use SOAP UI for instance, on the WS administration.
If you want some examples of BSM specific queries such as Subscribe on QoS:

<ns13:Subscribe xmlns:ns10="http://com.petalslink.easyesb/data/admin/1.0"
xmlns:ns11="http://com.petalslink.easyesb/admin/model/datatype/1.0"
xmlns:ns12="http://com.petalslink.esstar/admin/model/datatype/1.0"
xmlns:ns13="http://docs.oasis-open.org/wsn/b-2"
xmlns:ns14="http://www.w3.org/2005/08/addressing"
xmlns:ns15="http://docs.oasis-open.org/wsrf/bf-2"
xmlns:ns16="http://docs.oasis-open.org/wsn/t-1"
xmlns:ns17="http://docs.oasis-open.org/wsrf/rp-2"
xmlns:ns18="http://com.petalslink.esstar/data/management/user/1.0"
xmlns:ns19="http://com.petalslink.esstar/data/management/admin/1.0"
xmlns:ns2="http://com.petalslink.easyesb/soa/model/datatype/1.0"
xmlns:ns20="http://www.ebmwebsourcing.com/wsn/t-1-extension"
xmlns:ns21="http://com.petalslink.easyesb/component/bpel/data/1.0"
xmlns:ns22="http://com.petalslink.easierbsm/data/wsdmmanager/1.0"
xmlns:ns23="http://www.petalslink.com/esstar/execution.environment.synchronizer.impl/1.0"
xmlns:ns24="http://docs.oasis-open.org/wsdm/mows-2.xsd"
xmlns:ns25="http://docs.oasis-open.org/wsdm/muws2-2.xsd"
xmlns:ns26="http://docs.oasis-open.org/wsdm/muws1-2.xsd"
xmlns:ns27="http://com.petalslink.easierbsm/data/wsdm/1.0"
xmlns:ns3="http://com.ebmwebsourcing.easyesb/soa/model/endpoint"
xmlns:ns4="http://com.ebmwebsourcing.easyesb/soa/model/service"
xmlns:ns5="http://com.ebmwebsourcing.easyesb/soa/model/component"
xmlns:ns6="http://com.ebmwebsourcing.easyesb/soa/model/node"
xmlns:ns7="http://com.ebmwebsourcing.easyesb/soa/model/registry"
xmlns:ns8="http://com.petalslink.easyesb/transporter/1.0"
xmlns:ns9="http://com.petalslink.easyesb/exchange/1.0">
  <ns13:ConsumerReference>
    <ns14:Address>http://localhost:9002/NotificationEndpoint</ns14:Address>
    <ns14:ReferenceParameters/>
  </ns13:ConsumerReference>
  <ns13:Filter>
    <ns13:TopicExpression
Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116">
      <ns20:simpleTopicExpression
xmlns:mows-ev="http://docs.oasis-open.org/wsdm/2004/12/mows/wsdm-mows-events.xml">mows-ev:MetricsCapability</ns20:simpleTopicExpression>
    </ns13:TopicExpression>
  </ns13:Filter>
</ns13:Subscribe>


This request must be invoked on a non functional endpoint of the BSM (some
WS exposed by the BSM 
that finishes by "_WSDMMonitoringClientProxyEndpoint"). These endpoints are
generated once the BSM is
connected to an ESB. There is one non functional endpoint per functional
endpoint found in the ESB.
The topic here is "MetricsCapability". Then the notification consumer (here
"http://localhost:9002/NotificationEndpoint") will receive WS-DM
OperationMetrics (containing information about service time, avg/min/max
requests size, number of failed requests, etc.).



Here is an example of SLA you can load in the BSM (related to a Weather
Service):
http://jul64.free.fr/CHOREOS/agreement/agreement4.xml
<http://jul64.free.fr/CHOREOS/agreement/agreement4.xml>  

If you want more information about either QoS or SLAs, feel free to ask.


For now you can't connect a Petals ESB with EasierBSM. 
Moreover, the connection works with a  SOAP endpoint (the administration of
the ESB node).
With EasyESB, what you have to put in connectToESB tags is the
administration address (something like
http://localhost:9876/services/adminExternalEndpoint), provided when you
type "i" in its console  for instance.


Best regards.





--
View this message in context: http://forum.petalslink.com/Connect-easierBSM-to-Petals-ESB-tp4025568p4025573.html
Sent from the Users (get help, provide help) mailing list archive at Nabble.com.