Community
Participate
Working Groups
We need to consider adding some NON-instance data to the COSMOS Broker. Some items that I can think of that the COSMOS Broker could support: 1. Dialect for each Data Manager / MDR 2. SOAP version for each Data Manager / MDR There may be more requirements from CA in this regard, I will update this ER.
This supplements (this should be a keyword) 231343.
mdrID is also another field we need...
could the security provisions also be part of this requirement?
We will NOT do any syncronization between Broker and Data Managers / MDRs...
The Data Manager / MDRId should be determined based on considerations stated in 233690.
Created design page
Changes have been submitted
How is this fixed if it was blocked by bug 233690, which is not fixed?
(In reply to comment #8) > How is this fixed if it was blocked by bug 233690, which is not fixed? This issue adds static info to the Broker while 233690 is about the making the DMs configurable from a file. I think these issues are more related than dependent.
So bug 233690 doesn't depend on this one either? I.e. it could have been completed without this one being fixed?
This enhancement is about storing the record type namespace for data manager, SOAP version of each service, etc. These values come from the data managers and is made availabe by enhancement 233690. That was why I said 233690 is a dependency. Have you changed the broker registration web service operation to accept more values and assume the values are available? And you will do the integration test when 233690 is ready? Can you document in this bug exactly what are the new static values stored in the broker? e.g. I see "Security level required by the Data Manager" is one value to be store, but I don't know where the value will come from. Also, can you explain how bug 231343 is related to this bug (235898)?
Yes, I've changed the broker registration web service to accept the 4 new attributes. They are id, soapNamespace, recordTypeNamespace, and securityNamespace. I've also changed the CLI to accept these values during a manual registration and the demo install application. As part of 233690, JT is changing the service finder service to pull these values from the DM configuration file thru the GetDataManagerInfo operation and include them in the registration request. This is the link between these ERs. The actual values are arbitrary, except for the soap version. For Soap 1.1, axis2 uses org.apache.axiom.soap.SOAP11Constants.SOAP_ENVELOPE_NAMESPACE_URI , which contains the value: http://schemas.xmlsoap.org/soap/envelope/ For Soap 1.2, axis2 uses org.apache.axiom.soap.SOAP12Constants.SOAP_ENVELOPE_NAMESPACE_URI , which contains the value: http://www.w3.org/2003/05/soap-envelope We need to define a convention for the COSMOS basic security namespace value. I suggest "http://www.eclipse.org/cosmos/security/basic" as the security namespace. This can be used by the UI to determine whether to prompt for credentials (see issue 238298)
QA Review for Manual Tests/Junits: - No explicit test cases defined here, however this has been tested as part of End2End testing using COSMOS Command line operations - GetSoapVersion,GetDataManagerById,GetDataManagersByRecordTypeNamespace and by manual inspection and modification of cosmos.properties file
Closing per note from Srinivas Doma Reddy on 8/1/08.
