Saturday, March 07, 2009

jprof tool





jprof  is the  IBM Proprietary tool for analysing the performance of the JAVA Application.

it gives in-depth analysis of the method entry exit of a object , it gives the lucid picture memory leaks  , so easy to pin-point the problem which object is the cause for memory leaks 

after installing jprof tool , to generate run time logs and analysis of the logs using mx-view is explained below 


1) make sure linux source code is present in /usr/src directory of the Node machine

2) edit the file   /etc/grub.conf

 kernel /vmlinuz-2.6.18-92.el5 ro root=LABEL=/ rhgb quiet clock=tsc

After Installation 

change the generic JVM argument to 
" -agentlib:jprof=callflow,delay_start,logpath=/opt/jprof/xdms -Xgc:noAdaptiveTenure,tenureAge=8,stdGlobalCompactToSatisfyAllocate -Xgcpolicy:gencon -Xconcurrentlevel1"


copy all the *.so files from  cd /opt/jprof/xdms/  to "/opt/IBM/WebSphere6/AppServer/java/jre/bin"


cd /opt/Dpiperf/bin/

run the following command before starting the Node

 cd /opt/Dpiperf/bin/
 
  . setrunenv

 cd ../
  
 ./tinstall.appl

Now start the Cluster , after it starts check the jprof logs 

cd /opt/jprof/xdms directory 

log-msg_16699 where 16699 is the pid of Appserver


Execution of jprof:


CNSIP Service:

1) Ramp up the system by sending sipp requests (in ramp up manner ) up to 60 sec until cpu reaches 85-90% , pump the requests with 85-90% cpu  for 5 minutes with 120 tps , then bring the load back to  
15 tps, now the cpu also comes down to 10% wait for 1 minute 

now cd /opt/jprof/xdms

run the following command
 
rtdriver -l -c start 10 -c flush 30

10 represents duration of the rtdriver execution period

30 represents the flush time of buffer

Note:  some times it won't give all the thread details correctly , so vary the flush time(15 sec or 30 sec..).

output of the file is log-rt.1_18084 (cd /opt/jprof/xdms )where rt means runtime


there is some bug in the jprof tool it won't give user cpu% utilisation as 0.0%
(top or nmon)

so to know the correct cpu utilisation 

cd /opt/Dpiperf/bin

run the following command

swtrace ai 5


busy= usr+sys+wait



to analyse rt.log we need to use "mxview" graphical tool

so run xmanager before and export DISPLAY=ipaddress:0.0

run the following command 

java /opt/Dpiperf/bin/mxview.jar

once it opens , File->open

select the path of log-rt.1_18084 log for which you want to analyse




snapshot of mxview

7.78 and 7.72 ... represents the threads which are driving more cpu , so we need to track down the tree until bottom to find the thread which using more resources


it gives the thread details in the right hand side




ls -l /opt/jprof/xdms

. ./setrunenv

arcf -Ft /opt/jprof/xdms/log-rt.1_19443

arcf -t mtreeN BASE -F /opt/jprof/xdms/log-rt.1_19443

-bash-3.2# arcf -t mtreeN BASE -F /opt/jprof/xdms/log-rt.1_19443

 ARCFLOW 05.00.00

  (Built    : Tue Mar  3 22:09:55 IST 2009)

  (Source   : Thu Jan 15 10:00:00 Central Daylight Time 2009)

  (Platform : Linux-x86)


xtree is created in cd /opt/Dpiperf/bin/



now open the xtree with " mxview "



Saturday, February 07, 2009

Nokia 5800 XpressMusic

Nokia 5800 XpressMusic

   
Nokia 5800 XpressMusic 
Seller:TEKNIX
Price:Rs. 23995.00
Selling Price:Rs. 19490.00 / USD 400.62
You Save:Rs. 4505.00
 
View Large Image
   
 
   
>> Customer Rating : 
>> Shipping charges extra
>> Usually Delivered in 5 - 7 Working Days
Click here to see all payment options
 

About the Product : Nokia 5800 XpressMusic
 

Nokia 5800 XpressMusic, a mobile device for music that brings innovative new features to the mass market. Delivering on Nokia's vision to provide the best total music experience possible, the Nokia 5800 XpressMusic will be among the first devices to support Comes With Music, Nokia's groundbreaking service which offers one year of unlimited access to the entire Nokia Music Store catalogue. The Nokia 5800 XpressMusic is a S60 5th Edition device with a resistive touch screen and tactile feedback. The device has variety of input methods: stylus, plectrum and finger touch support for text input and UI control (alphanumeric keypad, full and mini qwerty keyboard, handwriting recognition). Use the Nokia 5800 XpressMusic to connect to mobile broadband using WLAN or HSDPA (3.5G). Supported WCDMA frequencies depend on the region where the device is available. Find directions and locations with the integrated A-GPS and included maps.

When it comes to music phones, people all over the world want a device that is a great music experience - with more memory, loud and powerful speakers, easy synchronization - and must still work well as a mobile phone with direct access to important contacts and content. The Nokia 5800 XpressMusic delivers on all counts and allows consumers to access and share content.

Media Bar, Contacts Bar - putting people first Taking advantage of touch screen technology, the Nokia 5800 XpressMusic introduces the 'Media Bar', a handy drop down menu that provides direct access to music and entertainment, including favourite tracks, videos and photos. The Media Bar also offers a direct link to the web and to online sharing. Because the Nokia 5800 XpressMusic supports Flash content, individuals can surf the entire web, not just pieces of it. In addition, the Nokia 5800 XpressMusic offers all the music essentials, including a graphic equalizer, 8GB memory for up to 6000 tracks and support for all main digital music formats, and a 3.5mm jack. Built-in surround sound stereo speakers offer the industry's most powerful sound.

Ensuring a seamless music experience, Nokia 5800 XpressMusic also provides easy access to browse and purchase tracks from the Nokia Music Store, where applicable, while the newly updated Nokia Music PC software allows for easy drag-and-drop transfer of songs and management of any music collection.

The innovative 'Contacts Bar' lets consumers highlight four favorite contacts on their home-screen and, through a single touch, track a digital history of recent text messages, emails, phone logs, photos and blog updates.

For the best screen resolution available on a mobile phone, the 3.2" widescreen display brings photos, video clips and web content to life in vibrant color and true clarity. With a 16 by 9 aspect ratio and 30 frames-per-second playback and recording, the device is ideal for VGA quality video recording and playback.

The Nokia 5800 XpressMusic also features a 3.2 megapixel camera with Carl Zeiss lens and, with a single touch, images or videos can be shared via a favorite online community, such as Share on Ovi, Flickr, or Facebook. Music playlist song titles can also be shared through Bluetooth, MMS or online sharing.

Music for the masses The Nokia 5800 XpressMusic supports 60 languages worldwide, which covers nearly 90 percent of the world's population. As people around the world use their phones in different ways, the Nokia 5800 XpressMusic offers a variety of input methods including a virtual alphanumeric keypad, a virtual computer-style QWERTY keyboard, a pen stylus and for true music enthusiasts, a plectrum are all available.

Physical features, power and memory

Size
  • Form: Classic with full touch user interface
  • Dimensions: 111 x 51.7 x 15.5 mm
  • Weight: 109 g
  • Volume: 83 cc
  • Touch user interface optimised for one-hand use with tactile feedback


  • Display and 3D
    Main display - Size: 3.2" - Resolution: 640 x 360 pixels (nHD) - Up to 16 million colours - aspect ratio 16:9 - automatic orientation sensor (Accelerometer) for display rotation - 3D image engine 

    Keys and input method
  • Stylus, plectrum and finger touch support for text input and user interface control (alphanumeric keypad, full and mini qwerty keyboard, handwriting recognition, full screen handwriting for Chinese language)
  • Dedicated Media Bar touch key for access to music, gallery, share on-line, Video Centre and web browser
  • Voice commands
  • Physical keys for application launch key (menu key), send & end, power, camera, lock, volume up & down


  • Connectors
  •  Micro-USB connector, USB 2.0 High Speed
  • 3.5 mm Nokia AV connector
  • MicroSD card slot, small DC jack, Micro USB cable interface to PC (CA-101), TV out interface (CA-75U)


  • Power
  • BL-5J 1320 mAh Li-Ion battery
  • Talk time (maximum): - GSM 8.8 h - WCDMA 5 h
  • Standby time (maximum): - GSM 406.2 h - WCDMA 400 h
  • Browsing time with packet data (maximum): 3.4 h
  • Video playback time (maximum): 5.2 h, Video playback time (maximum, nHD/Mpeg4) 3.4 h, VGA video playback using TV-Out with Stereo BT Headset 3.8 h
  • Video recording time (maximum): 3.6 h
  • Video call time (maximum): 3 h
  • Music playback time (maximum): Up to 35 h
  • Gaming time (maximum): 5.6 h


  • Memory
  • MicroSD memory card slot, hot swappable, max. 16 GB
  • 81 MB internal memory
  • 8GB microSD memory card in-box, expandable up to 16GB
  • Operating frequency
  • WCDMA 900/2100
  • GSM/EDGE 850/900/1800/1900
  • WCDMA 850/1900 (Latin America and Brazil variant only)
  • Automatic switching between GSM bands
  • Flight mode


  • Data network
  • CSD
  • HSCSD
  • GPRS/EDGE class B, multislot class 32, maximum speed 296/177 kbps (DL/UL)
  • WCDMA 2100/900 with simultanous voice and packet data, maximum speed PS 384/384 kbps (UL/DL), CS maximum speed 64 kbps
  • HSDPA cat 6, maximum speed 3.6 Mbps (DL)
  • WLAN IEEE 802.11 b/g (3G version only)
  • TCP/IP support


  • Local connectivity and synchronization
  • Bluetooth version 2.0 - Bluetooth profiles: A2DP & AVRCP
  • MTP (Mobile Transfer Protocol) support
  • TV out with Nokia Video Connectivity Cable (CA-75U, in-box)
  • Support for PC synchronisation with Nokia OVI Suite


  • Call features
  • Integrated hands-free speakerphone
  • Number screening for messaging and calls
  • Automatic answer with headset or car kit
  • Any key answer
  • Call waiting, call hold, call divert
  • Call timer
  • Logging of dialled, received and missed calls
  • Automatic redial
  • Speed dialling
  • Voice dialling: speaker independent dialling and voice commands (SIND)
  • Fixed dialling number support
  • Vibrating alert (internal), also with tactile feedback
  • Side volume keys
  • Mute/unmute
  • Contacts bar for 4 contacts with images and communication history (SMS, IM, email, web feeds)
  • Talking ring tones
  • Conference calling with up to 6 participants
  •  Video calling: up to 3h, QCIF 176 x 144 pixels, low up to 5 fps, normal up to 10 fps, smooth up to 15 fps


  • Messaging
  • SMS
  • Multiple SMS deletion
  • MMS version 1.3, message size up to 600 kb
  • Automatic resizing of images for MMS
  • Nokia Xpress audio messaging
  • Common inbox for SMS and MMS messages
  • Number screening for messaging
  • Distribution lists for messaging
  • Instant messaging client
  • Cell broadcast

  • E-mail
  • Supported protocols: IMAP, POP, SMTP
  • Support for e-mail attachments
  • OMA e-mail notification support
  • Mail for Exchange 2008 in DL client, in 2009 embedded


  • Web browsing
  • Supported markup languages: HTML, XHTML, WML
  • Supported protocols: HTTP, WAP, JavaScript
  • TCP/IP support
  • OSS browser
  • Nokia Mobile Search


  • GPS and navigation
  • Integrated GPS for pedestrian and car navigation
  • Nokia Maps 2.0 Touch application
  • Photography
  • 3.2 megapixel camera (2048 x 1536 pixels)
  • Image formats: JPEG
  • Carl Zeiss optics
  • 3x digital zoom
  • Autofocus
  • Dual LED flash
  • Flash modes: On, off, automatic, red-eye reduction
  • White balance modes: automatic, sunny, cloudy, incandescent, fluorescent
  • Centre weighted auto exposure; exposure compensation: +2 ~ -2EV at 0.5 step
  • Normal, Sepia, Black&White, Vivid, Negative
  • Dedicated camera key
  • Landscape (horizontal) orientation
  • Photo editor on device
  • Direct printing to compatible picture printers


  • Video
  • Main camera Video recording at up to 640 x 480 pixels and up to 30 fps (TV high quality), up to 640 x 352 pixels and up to 30 fps (widescreen quality), up to 320 x 240 pixels and up to 30 fps/15 fps (email high/normal quality), up to 176 x 144 and up to 15 fps (sharing quality) - Up to 4x digital video zoom
  • Front camera for video calling
  • Video recording file formats: .mp4, .3gp
  • Audio recording formats: WAV (normal), AMR (MMS), AAC/MP4 (high quality)
  • Video white balance modes: automatic, sunny, cloudy, incandescent, fluorescent
  • Scene modes: automatic, night
  • Colour tone modes: normal, sepia, black & white, vivid, negative
  • Clip length (maximum): 1 h 30 min (high or normal quality). Dependable on available memory.
  • RealPlayer
  • Video playback file formats: MPEG4-SP playback 30fps VGA, MPEG4-AVC playback 30fps QVGA, WMV9 playback 30fps QVGA, MPEG4-SP playback 30 fps nHD
  • Video streaming: 3GPP and CIF
  • Landscape mode video playback
  • Video editor on device
  • Video Centre service supported: download and stream video content, WMV support, video feeds


  • Music and audio playback
  • Nokia Nseries digital music player - Playlists - 8-band graphical equalizer - selection by artist, composers, album and genre album graphics display and audio visualisations bass booster, stereo widening, loudness
  • Music playback file formats: .mp3, SpMidi, AAC, AAC+, eAAC+, WMA
  • Dedicated volume keys & immediate access to Music Player from Media Bar, dedicated music keys in the headset control unit AD-54
  • Stereo FM radio
  • 3.5 mm Nokia AV connector
  • Music Player
  • Nokia Music Manager
  • Nokia Music Store support
  • Nokia Podcasting support
  • Ring tones: 3D stereo ring tones, 64-tone polyphonic, mp3 & video ring tones (3 videos and 9 mp3 songs built-in)
  • Integrated stereo speakers with surround sound (crystal clear hi-fi sound quality with dedicated audio chip)


  • Voice and audio recording
  • Voice commands
  • Speaker-independent name dialling (SIND)
  • Voice recorder
  • AMR, NB-AMR, FR, EFR
  • Digital stereo microphone


  • Personalization: profiles, themes, ring tones
  • Customizable profiles
  • Ring tones: 3D stereo ring tones, 64-tone polyphonic, mp3 & video ring tones
  • Themes
  •  
  • Warranty : 1 Year Manufacturer's Warranty
  • Monday, January 19, 2009

    IP Multimedia Subsystem (IMS)



    What is IMS?


     

    UDN, an Avaya DevConnect program

    Everyone agrees on the need for new and innovative communication services. People use an increasing variety of communication methods, from traditional voice calls to text messages, instant messages, pictures, video and online gaming. Many of these new services were born on the Internet while others emerged from cellular phone networks. As communication networks migrate universally to IP technology, these services are converging and becoming available on an increasing variety of devices, from laptops to cell phones, Blackberrys, PDAs and smart phones.

    Naturally, network operators are keen to offer customers as many of these services as possible and develop yet more features that people will pay for. New products not only generate revenue, but also help a service provider stand out in an increasingly congested and commoditized market.

    The IP Multimedia Subsystem (IMS) is a specification of an environment where these kinds of new services can flourish. It is an area dedicated to innovation in a service provider network. IMS is designed to make the development, deployment and delivery of new applications as quick and simple as possible in a standardized fashion. In particular, IMS is concerned with a network within which communication is in real time between peers. IMS is much less concerned with applications for the consumption of multimedia content, delivered in a synchronous, browser-based fashion.

    SIP is the Key

    The key technology behind IMS is the SIP protocol; the 3GPP have chosen SIP as the protocol underlying many of the important interfaces between elements in an IMS-based network. Carriers and service providers have been using SIP to build new products for sometime. Why? There are several big advantages to building a new feature or service using SIP:

    • Simple. SIP is based on a straightforward request-response interaction model, making life simple and comprehensible for developers. The messages are also text-based which makes them easy to parse, create, read, understand and debug.

    • Extensible. SIP can set up sessions for any media type, be it voice, video, application sharing or teleportation (once we invent it!)

    • Flexible. SIP allows developers to interact with the individual protocol messages (within limits) without breaking anything. This means that developers can perform a lot of neat tricks that make development much easier.

    • Familiar: In large part because SIP borrows heavily from HTTP and other internet standards from the IETF, lots of web-like technologies can be used to build SIP applications. SIP development looks and feels a lot like web development, and there are a lot of web developers out there.

    So clearly, there are many reasons you would want to build your applications in the land of SIP. The only problem with this approach is that few networks, and even fewer phones, speak SIP today (although they will in the future). Most cell phones, office phones and home phones don’t understand it. So if we build applications in SIP, how do can we use the new services using our old, non-SIP phones?

    The answer is to surround our SIP development ‘oasis’ with gateways which convert SIP signaling to protocols that the rest of the network can understand, including your cell phone and my home phone. If we put these gateways in the right place, then everyone is happy: developers get a great environment in which to build new applications and we get to use their new features using our existing phones. The diagram below shows this gateway architecture in action. Bob has a new feature, find-me-follow-me, which his service provider decided to build in SIP space and deploy using IMS. Bob isn’t aware of SIP or IMS of course: he just gets a great new feature which ensures Alice can always find and speak to him.


    SIP gateway architecture in action

    Today, this is really the essence of IMS: a standardized way of embedding a SIP oasis into a non-SIP network in order to create a happy place for applications developers. It’s important to do this in a standard way so that network equipment vendors, software companies and service providers can mix-and-match components. IMS is the specification to which all these companies are working.

    IP on Everything

    This oasis architecture is not the endgame for IMS. Eventually, everything in the network will be IP-based, or as Vint Cerf said, there will be “IP on everything”. Fourth generation (4G) cell phone networks will be pure IP and SIP, all the way to the handset. All calls and other interactions from your cell phone will be entirely IP based. Eventually even the old phone in the kitchen will be an IP phone. Once this happens, we won’t need gateways to perform protocol conversion to and from IMS anymore. In this case IMS become the specification for the entire network architecture and endpoints will connect directly to it using pure IP and SIP. We’re not there yet of course, so IMS will remain as an oasis in a non-IP network for a while. But someday we may be able to say “Everything on IMS” (and Vint Cerf will doubtless say “I MS with Everything”).

    Wireless or Wireline? Both.

    IMS was originally conceived as part of the 3rd Generation Partnership Project (3GPP) specification for third generation (3G) cell phone networks. The forebears of the 3GPP organization were responsible for specifying the GSM second generation (2G) system and their work helped it become the most widely deployed cellular technology in the world. Standardization made possible some remarkable features for GSM customers, such as international roaming and interchangeable handsets. Clearly IMS is an important specification with a distinguished heritage and pedigree.

    3GPP is specifying IMS to deliver new services and applications to 3G cell phone users. Part of the specification ensures that IMS is independent of the access network, so that network operators can offer new services over different types of radio interface and different types of cell phones. This is the essence of the gateway architecture we’ve already discussed – delivering new SIP-based services to any kind of device, and by extension, to any kind of network. Because this design cleanly separates applications from user access, IMS has become attractive to other service providers outside the wireless industry, who can simply swap the radio access interface for their own access network.

    As IP technology is adopted across all kinds of networks and industries, network architectures are converging so that wireless, wireline, voice, video and data network designs look essentially the same. As network architectures converge, IMS has become attractive to anyone who wants to offer advanced services, from mobile phone operators to traditional phone companies to internet service providers and cable companies. Indeed, it is likely that wireline operators will be in the vanguard of IMS adoption and deployment because they often face more competition than mobile operators, and thus have a greater need for the kind of high-value, differentiating services IMS can deliver.

    There is an IMS variation tailored for the requirements of wireline operators. The Telecoms & Internet converged Services & Protocols for Advanced Networks (TISPAN) specification is controlled by the European Telecommunications Standards Institute (ETSI).

    The Specification

    So what does the IMS standard describe? How does IMS recommend we build our oasis for new applications? The specification essentially describes two things:

    • A selection of logical network functions. IMS defines a set of logical elements that are required to deliver new services: It’s rather like a tool box for developers of new services. One of the key aims of IMS is to offer a reusable ‘kit of parts’ that are shared among applications to ensure new applications don’t require separate disconnected silos of data and functions. The kit inventory includes everything an application developer needs, including application servers, media servers, gateways and data stores. A key IMS concept is shared customer data, to which all applications have access.

    • The interfaces between these functions. By making the interaction between the logical elements standard, we can mix and match different components from different manufacturers, or even build our own (at least, that’s the idea).

    It’s the Software, Stupid!

    By standardizing components and interfaces, IMS describes a network that is very different from those in use today. Before IP networks and IMS, telecom networks were typically composed of closed, vertical silos of components that didn’t interact with each other, with no reuse of components and no possibility of mixing and matching elements from different sources. As a result, IMS is set to create a very different commercial, as well as technical environment. Network equipment vendors (NEVs) will find it much harder to lock-in operators with closed, proprietary technology. IMS solutions will typically be a collaboration of many companies, each bringing their individual expertise to the environment. This is particularly important as the role of software becomes fundamental in the network. IP networks in general - and IMS in particular - will swing the focus of development towards software folks and away from traditional hardware manufacturers who have previously dominated the industry. Hardware and software expertise and culture are rarely easily combined.

    In addition, IMS also offers the opportunity to expose standard software interfaces to third-party software developers so that they can take part in the creation of new applications. Again, this is in direct contrast to today’s closed systems which are accessible to only a handful of developers, using arcane, complex interfaces - proprietary to each manufacturer. As we have already seen, SIP technology looks very familiar to the multitude of software developers working with Internet technologies. IMS aims to embrace this community of developers by offering them standard interfaces, like web services, that are both familiar and simple to use.

    What the User Gets

    Of course customers don’t care about reusable components, standard interfaces and shared data. They only care about much higher-level behaviors they can interact with directly, such as the quality of their voice call, or easy access to their email and instant messaging contacts. As well as standardizing lower-level functions, IMS specifies higher level behaviors too. These behaviors benefit the customer and make the difference between using a paid IMS service over a similar, freely available service on the Internet. For example:

    • Security. IMS ensures proper user authentication and authorization, and privacy. Users are authenticated once, and this single-sign-on is used to access the entire range of services to which they subscribe.

    • Roaming. Services can be offered across separate networks via roaming mechanisms specified by IMS. Users of GSM phones can already roam between different networks run by different operators. IMS enhances the roaming experience by allowing users seamless access to their services, data and applications from another network.

    • Quality of Service. IMS makes sure that communication sessions are of guaranteed quality. One of the problems with public Internet-based communications is that it is typically ‘best effort’. The Internet offers no guarantees of bandwidth or latency and the communication experience varies widely as a result. The IMS specification makes sure there are always enough resources available for your communication session by dynamically reallocating as required, prioritizing your important video conference over my frivolous ringtone download.

    Network-centric in a Peer-to-Peer World

    An interesting feature of IMS is that it represents a very network-centric view of the world, while SIP is fundamentally a peer-to-peer protocol. One of the design goals of SIP was to produce a highly scalable communication model by pushing intelligence to the edge of the network. The dumber the center of the network, the faster it can operate and the more scalable it becomes. Traditional telephone networks operate in the opposite way: An intelligent center with dumb telephones at the edge. The traditional network model gives service providers ultimate control, and IMS is clearly rooted in this approach and it defines only the network core and has little to say about edge devices.

    Service providers must find a role to play in the center of the network to avoid disintermediation by pure peer-to-peer technologies (of which Skype is a prime example). Although SIP can operate in a pure peer-to-peer mode, it is enhanced by the addition of central network elements. Proxies, registrars and other SIP network elements offer basic functionality to make the routing of calls much simpler and the user experience can be enhanced yet further by the addition of more sophisticated SIP applications. This is where service providers aim to add value, and to make money. SIP can be forced out of a pure peer-to-peer model by the insertion of back-to-back user agents (B2BUAs) and other constructs which return control to the network center. The IMS specification makes extensive use of these kinds of techniques for network-centric control.

    Part Two

    In Part 2, we will take a deeper technical dive into each of the major functional elements standardized by IMS. We will look at the purpose of each element, their interactions and standard interfaces between them.

    By Matt Darby, Avaya.

    The Avaya SIP Application Server works seamlessly with the J2EE and service oriented architectures of today's 2.5G networks, while also integrating with 3G IP Multimedia Subsystem (IMS) architectures - future proofing today's deployments.

    Mobile service providers can deliver high margin, end-to-end next generation applications quickly and cost effectively by utilizing Avaya Professional Services as well as our strategic IMS, J2EE, and handset partners, including HP, IBM, Nokia, Nortel, Qualphone, and Siemens.

    Further information >>>

    Popular Posts