On Mon, Oct 12, 2015 at 1:42 PM, Gayan Dhanushka <[email protected]> wrote:
> Hi all, > > The current plan is to deploy the ESB applications in App Factory as car > files. As we have previously highlighted the fact that we need a mechanism > to launch an ESB application once the deployment is completed, I think it > would be better to view the content of the car file as of in the management > console of the ESB [1]. Is this the correct behavior to be implemented when > ESB applications are launched? > ESB admin console allows us to get more details related to ESB artifact like Proxy service endpoints, local entry values and API related data in the Carbon Application. How about listing this information on a summary page like in the service console. > Currently in the ESB management console the URL of this content page would > look like the following. > > https:// > <ESB_IP>:<ESB_PORT>/carbon/carbonapps/application_info.jsp?appName=<CAR_name> > > Currently this view comes up with the ESB management console. But IMO we > need to decouple this view from our ESB management console. How about > calling the endpoints used in this page and render it on a custom jaggery > page in App Factory ? > > [1] > > car_content_view.png > <https://drive.google.com/a/wso2.com/file/d/0B5OmHe7M-ZSHX3RwN0JTUEU4QlU/view?usp=drive_web> > > Regards > > -- > Gayan Dhanuska > Software Engineer > http://wso2.com/ > Lean Enterprise Middleware > > Mobile > 071 666 2327 > > Office > Tel : 94 11 214 5345 > Fax : 94 11 214 5300 > > Twitter : https://twitter.com/gayanlggd > -- Deependra Ariyadewa WSO2, Inc. http://wso2.com/ http://wso2.org email [email protected]; cell +94 71 403 5996 ; Blog http://risenfall.wordpress.com/ PGP info: KeyID: 'DC627E6F' *WSO2 - Lean . Enterprise . Middleware*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
