All, We already have a tool to create endpoints : Dev Studio.
All we need is a way to choose the endpoints from a list in the APIM UI . Recreating the endpoints UI in the publisher would duplicate dev and maintenance work. We should create a clean integration between DevStudio and API publisher, to create/publish sequences and endpoints into the API Manager registry and use them from the Publisher UI. Can we do this as part of Phase 1 ? Isabelle. ------ Isabelle Mauny Director, Product Management; WSO2, Inc.; http://wso2.com/ email: [email protected] <[email protected]> - mobile: +34 616050684 On Thu, Oct 3, 2013 at 4:40 AM, Sanjiva Weerawarana <[email protected]>wrote: > On Wed, Oct 2, 2013 at 2:50 PM, Joseph Fonseka <[email protected]> wrote: > >> In the current APIM we only support Address endpoint type. So we are >>> planing to include other endpoint types which are supported by the ESB. >>> >>> Following are the other endpoint types >>> >>> Address Endpoint >>> <https://10.100.5.20:9445/carbon/endpoints/addressEndpoint.jsp?> Defines >>> the direct URL of the serveice Default >>> Endpoint <http://docs.wso2.org/display/ESB403/Default+Endpoint> Defines >>> additional configuration for the default target Failover >>> Group <https://10.100.5.20:9445/carbon/endpoints/failoverEndpoint.jsp?> >>> Defines the endpoints that the service will try to connect to in case of a >>> failure. This will take place in a round robin manner HTTP Endpoint >>> <https://10.100.5.20:9445/carbon/endpoints/httpEndpoint.jsp?> Defines >>> a URI Template based REST Service endpoint Load Balance Endpoint >>> <https://10.100.5.20:9445/carbon/endpoints/loadBalanceEndpoint.jsp?> >>> Defines groups of endpoints for replicated services.The incoming requests >>> will be directed to these endpoints in a round robin manner. These >>> endpoints automatically handle the fail-over cases as well Recipient >>> List Group >>> <https://10.100.5.20:9445/carbon/endpoints/recipientlistEndpoint.jsp?> >>> Defines the list of endpoints a message will be routed to Template >>> Endpoint >>> <https://10.100.5.20:9445/carbon/endpoints/templateEndpoint.jsp?> Defines a >>> template endpoint that can parameterfy endpoints WSDL >>> Endpoint <https://10.100.5.20:9445/carbon/endpoints/wsdlEndpoint.jsp?> >>> Defines the WSDL, Service and Port >>> >> > Jo does this also address secured endpoints? E.g. basic auth secured or > WSSec-UT or other (as long as its supported by the ESB)? > > From the above list do we need to ? and how to include the following ? >>> >>> 1. Default Endpoint >>> >> > What does this mean? > > >> 2. HTTP Endpoint - This require to populate the uri template during >>> mediation. >>> 3. Template Endpoint - You need to specify a template when creating an >>> endpoint. >>> >> > So this is a way to create an endpoint based on some info in the incoming > request? > > Some of the above need additional configuration. As I understood configure >>> meditations and defining templates. Do we have to provide UI for them as >>> well. >>> >> > I think we need to provide a UI to define these endpoints. Is there > something other than that in your mind? By "templates" you didn't mean ESB > templates right? > > Sanjiva. > -- > Sanjiva Weerawarana, Ph.D. > Founder, Chairman & CEO; WSO2, Inc.; http://wso2.com/ > email: [email protected]; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 > 650 265 8311 > blog: http://sanjiva.weerawarana.org/ > > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
