[cosmos-dev] RE: Solicitiing opinion (bug 229795)

[Hubert H Leung <hkyleung@xxxxxxxxxx>]

This is a discussion related to bug 229795. We discussed the solution in the DC call as well. Here is the latest proposal.

This bug is to provide the ability to register a data manager with the broker. (We had a command to register ALL data managers with the broker in i10.) One further requirement is that the data manager may be a non-COSMOS MDR or federating CMDB.

We will have two new commands - one for registering a COSMOS data manager, and one for registering a group of web serivces (e.g. a non-COSMOS MDR). For the first command, we assume it's an axis2 web service and a service finder service is also installed on the same server.

broker registerDataManager <data manager name> [service finder epr]


For the case of registering non-COSMOS services, we may not have service finder service. The command can look like this:

broker registerServiceGroup <group name> [URL to WSDL1] [URL to WSDL2] ...

<group name> is the a name given to the group of services, which is equivalent to the data manager name.
Then we accept a list of URLs to WSDL of web services. From each WSDL, get the target namespace and the service EPR.


Here is an alternative to the command above. The previous one was in favor during the DC call.
broker registerServiceGroup <group name> [EPR1[,namespace1]] [EPR2[,namespace2]] ...
Here we provide a list of service EPRs. For each EPR, there is an optional namespace value. If the namespace is not provided, the command will get the wsdl by appending ?wsdl to the EPR and retrieve the namespace from the WSDL.


Thanks,
_________________________
Hubert Leung
IBM Toronto Lab
hkyleung@xxxxxxxxxx
905-413-3382
"Todd, John A" <John.Todd@xxxxxx>

"Todd, John A" <John.Todd@xxxxxx>

05/13/2008 10:01 AM

To	"Muldoon, William H" <William.Muldoon@xxxxxx>, Hubert H Leung/Toronto/IBM@IBMCA
cc
Subject	RE: Solicitiing opinion

> “broker register <serviceEPR>”
We need to talk here about what exactly we are registering, 
I think the intent is to be able to register datamanagers, and datamanagers can have multiple services.
 
We don’t want to register the individual services of the datamanagers, but the datamanager as a service group.
 
My initial thought had been to have a command that looked like this
 
> broker register <datamanager name> [service finder epr]
Use the service finder to get a list of datamanagers, and only register the one with that name.
 
And do something different I guess for non-cosmos datamanagers
 
- John

---

From: Muldoon, William H 
Sent: Monday, May 12, 2008 12:30 PM
To: Todd, John A; 'Hubert H Leung'
Subject: RE: Solicitiing opinion
 
Hubert
 
    I think it would be more user-friendly and less error prone if we deduced the broker registration information from the WSDL of the service (instead of requiring the user to specify all the information on the command line).
    For example: “broker register <serviceEPR>” would internally query the wsdl and then register the service using the service name, description, and namespace from the wsdl. It would also output informational messages about the service (see below). 
 
    We could also include the ability to list all the available services on an axis (or axis2) server and deduce the COSMOS compatibility information.
    For example: “broker listAxisServices <axisEPR>” would display the list of services available on the axis server, including which ones are MDRs, CMDBfs or Data Managers (based on the namespace and supported operations of each service) and even highlight which ones are already registered. 
 
    The result would allow the user to quickly list all his or her Axis services, and then easily register the selected services.
 
    Note that all of the above should work the same with both COSMOS and non-COSMOS data managers.
 
Regards
Bill

---

From: Todd, John A 
Sent: Monday, May 12, 2008 10:46 AM
To: Hubert H Leung
Cc: Muldoon, William H
Subject: RE: Solicitiing opinion
 
Yes ok, 
So we’ll have on register command that will use the service finder the fill in the information
And other that will take all the information directly from the user.
 
- John

---

From: Hubert H Leung [mailto:hkyleung@xxxxxxxxxx] 
Sent: Monday, May 12, 2008 10:43 AM
To: Todd, John A
Cc: Muldoon, William H
Subject: Re: Solicitiing opinion

Hi John,

The command "‘broker register <servicename> [service finder epr]" looks good. I assume <servicename> means the name of the axis2 service group, which can have more than 1 services. This command can be used for registering a single data manager. The data manager (or axis2 service group) doesn't have to be COSMOS data manager, but the find data managers command only returns COSMOS data managers. So the non-COSMOS service groups are not listed from the command line client.

Since we also want to allow non-COSMOS data managers be registered, we also need another command that does not make use of service finder. You can gather values such as EPR, namespace, etc. from command line.

I have copied Bill in this email, who may have some input to the design.

Thanks,
_________________________
Hubert Leung
IBM Toronto Lab
hkyleung@xxxxxxxxxx
905-413-3382
"Todd, John A" <John.Todd@xxxxxx>

"Todd, John A" <John.Todd@xxxxxx>

05/12/2008 09:25 AM

To	Hubert H Leung/Toronto/IBM@IBMCA
cc
Subject	Solicitiing opinion

For registering individual services from the CLI,

Do you think we need the option where the user can specify all the information, 
Or do you think it will be sufficient to just say 

‘broker register <servicename> [service finder epr]’

So you can say like
>CLI broker register LoggingDataManager

And it’ll use the service finder to get the rest of the information and register that.

Thanks.

- John