Tuesday Oct 28, 2008

NetBeans 6.5 RC1 out!

NetBeans 6.5 RC1 is now available for download. The information is available at http://www.netbeans.org/community/releases/65/

You can download the same at http://dlc.sun.com.edgesuite.net/netbeans/6.5/rc/.

What it means to me from Java /SOA perspective are the following:

  • Improved Camelcase code completion

  • Improved Encapsulate Fields Refactoring

  • XML and Schema Tools

  • Quick Search

Not limited to these there are several other!! I checked out the this one and it seems to be cool!
Try it out today!

Monday Jul 16, 2007

Performance in FCAPS

The 'P' in FCAPS is a very strong Quality Of Service(QOS) measure for any Networking environment and means a lot from the Service Level Agreement(SLA) perspective since it involves money. Lets see in this post what does comprise parameters for “P” and what would an NMS require from this perspective.

Network bandwidth or the performance depends upon the traffic or the payload that is being carried in the network. There are many factors those are responsible for the performance. Each of the device or Network Element has certain set of characteristics which effect the bandwidth and these characteristics depend upon some input criteria. The mechanism of optimizing the input parameters for the device so that the specified output criteria is met is called Throttling. This can mean different things for different devices for different parameters, either hardware or software. Lets look at different kinds of throttling:

Bandwidth throttling is a method of ensuring a bandwidth intensive device, such as a server, will limit ("throttle") the quantity of data it transmits and/or accepts within a specified period of time. Bandwidth throttling helps provide quality of service (QoS) by limiting network congestion and server crashes

A server, such as a web server, is a host computer connected to a network, such as the Internet, which provides data in response to requests by client computers. Understandably, there are periods where client requests may peak (certain hours of the day, for example). Such peaks may cause congestion of data ( bottlenecks) across the connection or cause the server to crash, resulting in downtime. In order to prevent such issues, a server administrator may implement bandwidth throttling to control the number of requests a server responds to within a specified period of time.

When a server using bandwidth throttling has reached the allowed bandwidth set by the administrator, it will block further read attempts, usually moving them into a queue to be processed once the bandwidth use reaches an acceptable level. Bandwidth throttling will usually continue to allow write requests (such as a user submitting a form) and transmission requests, unless the bandwidth continues to fail to return to an acceptable level.

Likewise, some software, such as peer-to-peer (P2P) network programs, have similar bandwidth throttling features, which allow a user to set desired maximum upload and download rates, so as not to consume the entire available bandwidth of his or her Internet connection.

CPU throttling refers to a series of methods for reducing power consumption in computers by lowering the clock frequency. Other methods include reducing the supply voltage and the capacitance

I/O throttling: input /output throttling, a technique used to more efficiently handle memory processing. During low-memory conditions, a system will slow down the processing of I/O memory requests, typically processing one sequence at a time in the order the request was received. I/O throttling slows down a system but typically will prevent the system from crashing.

When the NMS wants to tackle throttling issue it should serve the following purpose:

  • Determine the problems if any prior to their affecting the services

  • Maximize network utilization

  • Preempt the occurrence of the congestion

  • Demonstrate the compliance with the agreed SLAs (Service Level Agreement)

  • Indicate when extra network investment is needed.

Requirements for such system:

  • Receives asynchronously to the generated NE data

  • Pro actively retrieve the data from the NE the data such as Bandwidth consumption with respect to interfaces

  • Configuring intelligent NE to give out this data either as Alarm/Trap

  • Mediation being introduced for producing sanitizing details for the downstream use by third party applications

  • Aggregation of separate performance data records of Nodes / Interfaces / Links / LSPs / Multi service cross connections – Ethernet to MPLS, FR over ATM etc.

  • Policies can be built with predefined format and the device/network views can be polled

  • Correlation of the aggregated data with the associated managed objects like no of IP packets by an LSP End to End, No of Ethernet frames forwarded by LSP End to End, No of Cells carried or dropped by an ATM switch etc.

  • Reports can be generated from such data with respect to the utilization of managed objects like interfaces, nodes etc., difference between actual and planned loads, real time and historical SLA conformance etc.

  • Topology issues like detection of a congested link, traffic flow in the circuit which would have serious implications with respect to the performance of the network.

  • Maintaining Database tables for this effect at the NE level and at network level is essential for producing such kind of data and reports.

In my next post I would delve further on the strategies from NMS perspective.

Friday Jul 06, 2007


We shall continue this post from the previous one exploring the FCAPS of the Network Management.

The International Organization for Standardization (ISO) network management model defines five functional areas of network management.

  • Fault Management:

    • Detect, isolate, notify, and correct faults encountered in the network, like whether some device is down etc.

    • Increases Network reliability and effectiveness

    • Increases productivity of the users

  • Configuration Management:

    • Configuration aspects of network devices such as configuration file management, inventory management, and software management.

    • Allows rapid access to configuration information

    • Facilitates remote configuration and provisioning

    • Up-to-date inventory of the Network elements

    • It talks about issues like speed, trunking, STP state etc.

  • Performance Management:

    • Monitor and measure various aspects of performance so that overall performance can be maintained at an acceptable level.

    • Reduces network overcrowding and inaccessibility

    • Very good measure of QOS

    • With proactive utilization of data generated here NMS can prevent performance issues

    • it gives an account of issues like CPU utilization, Free Memory, utilization, Broadcast rates, interference in case of WLANS etc.

  • Security Management:

    • Provide access to network devices and corporate resources to authorized individuals.

    • Builds user confidence

    • protects Network from malicious attacks

    • This takes into consideration different ways of Security like RADIUS, ACL, Signature, Encryption etc.

  • Accounting Management:

    • Usage information of network resources for establishing metrics, check quotas, determine costs and bill users etc.

    • Measures and reports accounting information based on individual groups and users

    • Internal verification of third party billing for usage.

Further exploration of NMS in next post.

Monday Jul 02, 2007

Network Virtualization in open-esb (1)

When we talk about Network Management we tend to talk about fundamentally at 3 levels

  • Device / Element level
  • Group / View Level
  • Network as a whole
and NetConf are the 2 Protocols we discuss normally for Network
Management. In this note I compare both the protocols with their pros
and cons and suggest ways for looking at the same differently. In my
future writings I will delve how can we achieve virtualization of
Network and the integration of the same in open-esb

 In this article I tried to explore Netconf as an alternative to SNMP and how can we achieve the same with a paradigm shift with respect to the current network management solutions.

[Read More]

Monday Jun 04, 2007

Where should the Heathcare systems go?

In this post I talk about the issues that should be solved in the health care domain in the near future where interoperability amongst different health care systems is going to be a main concern.[Read More]

Where should the Heathcare systems go?

Recently while having a look at the HL7 BC at the open-esb I felt that there are several issues and challenges that are not yet solved in this domain.

From a philosophical perspective too if we look at, the globalization is happening at great speed and we need interoperability amongst the standards for accessing a patient's record who is diagonalized for a particular disease to be treated at a different geo-political location. Why I m talking about political here is to emphasize the disparate systems via which the patient records pass and heterogeneous health care and insurance systems we have in different geo-political regions.

The following list is not complete. This is only a start for looking at the things. :-) . I might be writing you more if we continue to do work.
Have a look and give your feed back.

  1. Arden Syntax, which is a language for encoding medical knowledge. HL7 adopted and oversees the standard beginning with Arden syntax 2.0. These Medical Logic Modules (MLMs) are used in the clinical setting as they can contain sufficient knowledge to make single medical decisions. They can produce alerts, diagnoses, interpretations, and contain a quality assurance function and administrative support. An MLM must be run on a computer that meets the minimum system requirements and has the correct program installed. Once this is provided, the MLM can give advice when and where it is needed.

  2. The HL7 Clinical Document Architecture (CDA) is an XML based markup standard intended to specify the encoding, structure and semantics clinical documents for exchange. It is based on the HL7 Reference Information Model (RIM) and the HL7 Version 3 Data Types,

  3. Interoperability with Clinical Data Interchange Standards Consortium (CDISC)

2 and 3 seem to be pervasive in the Health care domain. Supporting these things would certainly enhance the marketability etc.. Apart from above if we were to be leaders we need to do have the following to with interoperability amongst these protocols in mind (Why interoperability ??? --- for flexibility and transforming one kind of data to the other kind offering seamless transfer of data from one system to another system. This has potential of One kind of record to be looked from another kind of system without the user being switching from one kind of domain to the other kind). Have a look at Open Healthcare, Good European Healthcare Record (GEHR) and Electronic Health Record (EHR) and Electronic Medical Record (EMR).

Without inter-operable EMRs, practicing physicians, pharmacies and hospitals cannot share patient information, which is necessary for timely, patient-centered and portable care. There are currently multiple competing vendors of EHR systems, each selling a software suite that in many cases is not compatible with those of their competitors.Office of the National Coordinator for Health Information Technology (ONC), works to address interoperability issues and to establish a National Health Information Network (NHIN) in US. Under the ONC, Regional Health Information Organizations (RHIOs) have been estabilshed in many states in order to promote the sharing of health information. US Congress is currently working on legislation to increase funding to these and similar programs.

Wednesday Apr 04, 2007

Using Scripting Service in open-esb

1st part of the writeup on Scripting Service Engine. This note delves on how is scripting important for Java platform, what is JSR223 and a bit of internals on the same as a precursor to the usage of Scripting Service Engine in open-esb.[Read More]

I was part of Sun R&D in Java CAPS and later Glassfish ESB. I moved from R&D to Consulting. I am currently working as a Solution Architect in Oracle Consulting Services (India). I was sharing my experience w.r.t. Java CAPS and other technologies during Sun period. Now in Oracle world I share my experiences with Oracle FMW product line as well as other Oracle Technologies and products.


« March 2015