1 / 8

Interesting Problem at Cisco

Interesting Problem at Cisco. DP&NM Members dpnm@tigris.postech.ac.kr Tel: 0562-279-5641 http://dpnm.postech.ac.kr Distributed Processing & Network Management Lab Dept. of Computer Science and Engineering POSTECH. Dear DPNM Members. Prof. Hong write:

wynter-sears
Download Presentation

Interesting Problem at Cisco

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interesting Problem at Cisco DP&NM Members dpnm@tigris.postech.ac.kr Tel: 0562-279-5641 http://dpnm.postech.ac.kr Distributed Processing & Network Management Lab Dept. of Computer Science and Engineering POSTECH

  2. Dear DPNM Members Prof. Hong write: • I have received a request to see if we can investigate the following. • I would like you all to think about this and we can discuss about this at the next Lab meeting, Tuesday 4:00pm.

  3. High-Level Description: The topic we are interested in is to investigate for a particular product what it would involve to convert it from a Java-based management application into applets (i.e. into a browser-based application) from a product standpoint: i.e. technical effort involved, distribution aspects, considerations with regard to startup time and reliability, benefits/tradeoffs, etc.

  4. Detailed Description: • We have ELS/NMS cisco WAN manager which used to have a Motif-based GUI interface. We want to make the GUI web based. We are building Java application using Orbixweb. Our Java client GUI uses idl interface to talk to a C++ backend process. • We also want to make the Java application as Java applets which then can be used from a standard browser. • We would like some one to come and evaluate multiple options to do these and recommend a scaleable solution. • Currently one CWM server supports up to 40 desktops and manages networks with around 2000 nodes and around 500K PVC. When we go to web based solution, we would like to support 100's of Web Clients. • Please let me know what you can do to contribute in this area.

  5. Problem • How to convert from Java application to Java applet? (Java application using OribixWeb & C++ backend process)

  6. Problem • What problems exist in Java applet distribution and what solutions to the problem? • security, upload time, disparate JRE …

  7. Problem • How to manage scalability, with the performance point of view? • supports up to 40 desktops • manages around 2000 nodes and around 500K PVC • supports 100's of Web Clients

  8. Problem • What advantages/disadvantages does Java applet has over Java application? • No user program, real ubiquity / startup time, reliability ...

More Related