Hi Subash, Currently we have endpoint with the following format (ESB endpoint format) with the mediatype application/vnd.wso2.endpoint.
<ns:endpoint xmlns:ns="http://ws.apache.org/ns/synapse"; name="gov/_250/_0/_100/_10/services/samples/ep-DTPSampleService-SOAP11Endpoint"><ns:address uri=" http://10.100.0.250:9767/services/samples/DTPSampleService.SOAP11Endpoint/ "/></ns:endpoint> If we using a endpoint(rxt) with new mediatype application/vnd.wso2.endpoint+xml, 1. There will be confusion with the endpoints. So we may have to unify them to a single mediatype with a unified content. 2. We have fix the WSDLProcessor to save the endpoints of a WSDL with the current format. 3. We have to fix the saving endpoint of ESB to registry to use the same format. Please correct me if I have misunderstood your model. thanks Eranda On Mon, Jun 3, 2013 at 11:03 AM, Subash Chaturanga <[email protected]> wrote: > Hi Senaka, > I have completed the first milestone of this. > > - This runs as a task in G-Reg. And task can be configured via > registry.xml where you provide ESB server details as task parameters. > - This task will sync ESB proxy services,sequences and endpoints in G-Reg. > i.e > - When proxy services/sequence/endpoints get created corresponding > asset types get created in GReg. > - When proxy services/sequence/endpoints get deleted corresponding > asset types get deleted in GReg. > - When proxy services/sequence/endpoints get created corresponding > dependencies get created for the esb artifact in GReg. > i.e when a proxy created, its sequences and endpoints becomes its > dependencies. And those sequences/endpoints have "usedBy" relationship to > the Proxy. > - When a proxy services/sequence removes its endpoints/sequences, the > corresponding dependencies/associations of the artifact also get updated. > > By default the task configuration is commented out. Users can uncomment it > and run it with ESB. How frequently we should run this task by default ? > > On Tue, May 28, 2013 at 11:54 PM, Eranda Sooriyabandara > <[email protected]>wrote: > >> Hi Subash, >> >> How you are going to publish the data to the G-Reg from ESB? >> We may use an admin service for pulling out the details to G-Reg. To do >> that we may need to have a place (may be UI) to configure ESB URL, username >> and password. WDYT? >> >> thanks >> Eranda >> >> On Tue, May 28, 2013 at 3:57 PM, Subash Chaturanga <[email protected]>wrote: >> >>> Hi >>> I have started working on $subject. This feature will provide ability to >>> govern ESB artifacts on G-Reg at runtime. To start with, we are focusing on >>> following ESB artifacts. >>> - Proxy Services >>> - Sequences >>> - Endpoints >>> >>> Following will be the expected meta data model for each aforementioned >>> artifacts. And G-Reg will create associations between the artifacts. i.e >>> sequence "foo" usedBy proxy "bar". >>> So from G-Reg side, a task will be run in background which will call esb >>> admin services to fetch/store and sync these artifacts. Please add any >>> missing meta data that you feel which would be useful to have. >>> >>> *- Proxy Services* >>> Basic Info: >>> - Name >>> - Transports >>> - StartOnLoad >>> - Trace >>> - PinnedServers >>> - ServiceGroup >>> >>> Other >>> - InSequence(Name) >>> - OutSequence(Name) >>> - FaultSequence(Name) >>> - Endpoint(Key/URL) >>> - PublishWSDL (key, uri) >>> - Policies (List) >>> - Parameters (List) >>> - EnableAddressing(True/False) >>> - EnableSec(True/False) >>> - EnableRM(True/False) >>> >>> >>> *- Sequence* >>> * - *Basic Info: >>> - Name/Key >>> - OnErrorSequence >>> * - *Trace* * >>> * - *Mediators >>> * - *List of mediator names* * >>> >>> *- Endpoint* >>> * *- Basic Info: >>> - Name/Key >>> * - *Address Info >>> >>> >>> >>> >>> >>> >>> -- >>> Thanks >>> /subash >>> >>> *Subash Chaturanga* >>> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com >>> >>> email: [email protected] >>> blog: http://subashsdm.blogspot.com/ >>> twitter: @subash89 >>> phone: +9477 2225922 >>> Lean . Enterprise . Middleware >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Eranda Sooriyabandara >> *Software Engineer; >> Integration Technologies Team; >> WSO2 Inc.; http://wso2.com >> Lean . Enterprise . Middleware >> >> E-mail: eranda AT wso2.com >> Mobile: +94 716 472 816 >> Linked-In: http://www.linkedin.com/in/erandasooriyabandara >> Blog: http://emsooriyabandara.blogspot.com/ >> >> >> >> * >> * >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Thanks > /subash > > *Subash Chaturanga* > Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com > > email: [email protected] > blog: http://subashsdm.blogspot.com/ > twitter: @subash89 > phone: +9477 2225922 > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Eranda Sooriyabandara *Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/ * *
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
