Skip to main content

How to performed testing on Map Network and Application Architecture

 What is Map Network?
Network map is a visualization of device on networks, their inter relationships, & the transport layers providing a network services. Practically, a Network Map is a single tool to provide network users, managers or administrators, & IT personnel with a better understanding of the network performance, specifically concerning data bottle-necks & associated root cause analysis.

What is the Application Architecture?
In this information system, Applications Architecture is one of several architectures domain’s that forms of the pillars of enterprise architecture and solutions of architecture.
The different type’s elements that make up the infra-structure required to be determined to understand how they meet with a web application & how they affect security. In fact it takes only an ace vulnerability to undermine the security of the whole infra-structure, & even small & seemingly un-important problems may be evolve into harsh risks for another application on the same server.

How to test the network map or application architecture
The application architecture required to be mapped by some test to determine, what different components are used to create the web application. On more complicated setups, such as an online bank system and multiple servers might be included. These may be including a reverse proxy, a front end web server, an application’s server or a database servers and Light-weight Directory Access Protocol (LDAP) server. Then they will be retrieve the information from other tests or derives the different elements, question these assumptions & extend the architecture’s map.

This builds the different demilitarized zones (DMZs) so that access to the web server will not to give a remote user’s access to the authentication of mechanism itself, or so that compromises of the different components of the architecture can be isolated so that they will not agreement the entire architecture. Getting the knowledge of application architecture can be easy, if this data is provided to the testing team through the application’s developer in document form and through interviews, but can also prove to be very difficult.

Components of the application and map network

What is Component?
A component is the object that contains the code to manipulate the data from one to another, & which provides the access that code through a well specified set of publicly presents the services. The key characteristics of a component are that when it is built for use, the codes for the elements, as well as the data associated with the elements are packaged together.
  
CLB:
CLB means Component Load Balancing; it allows to multiple application’s server to provide the same COM+ objects for use in application. When that object’s required, the creation of request’s sent first to CLB Servers which then re-directs to the request an appropriate application’s server, based on specific criteria.

IMDB:
The means of IMDB is "In-Memory Database Support", it is a momentary transnational database style cache that re-sides in RAM memory or provides enormously fast access to information on the machine on which it is re-sides.

Queued Component’s:
It combines the features of COM to provide a path to invoke & execute the components asynchronously. Activities can occur without respect to the availability and accessibility either of the sender &receiver. When the client calls queue component, the calls made to the Queued Components Recorder (QCR), which packages it as a part of message to the server or puts it in a queue?

Object Pooling’s:
Object pooling’s is an automatic service provided through COM+ that enables you to have examples of a components kept process in a pool, ready to be used through any customer that requests to the components. At the time, application is executing, COM+ manages the pool, controlling the details of object’s activation or re-use according to the criteria of you have fixed.

Comments

Popular posts from this blog

Steps To Hunt the Bugs Successfully

The testers should catch the bugs in software that they’re testing. Testers should try to catch as several vital bugs as soon as possible. Catching the crucial bug earlier on Product-Life-Cycle can save the Projects from financial losses & mitigate the risks as compared for catching the same at a later stage in SDLC. Steps to hunt the bugs: Sometimes it’s useful to break the rules: The following test cases, which were predefined a tester can miss the bugs so it makes it impossible’s to provide the product i.e. 100 percent bug free. If you-follow pre-determined test cases you risks becoming blind to outside the bugs. A first secret is to check the functionality under the test. It’ll be an effective channel to discover the more bugs, because functionality is not generally covered by the test cases. Examine the patterns: You might have noticed that the bugs can be often met in the groups, one can call them-gregarious. The testing a new but the similar functionality...

Cross browser testing Tools

Cross Browser testing It is a process to test the web apps across multiple browsers. It involves the checking compatibility of the app across multiple web browsers & ensures that your web app’s works correctly across different web browsers. Tools for Cross Browser Testing Browser shots: The browser shots might be most exhaustive cross browser-testing tool that exists. Browser Shots includes all of most popular-browsers, like Firefox, Chrome, & Safari, along with the tons of another browser’s that might sound unfamiliar, like Sea Monkey, Flock, & Iceape. You can adjust the resolution, color-settings, & even Flash and JavaScript settings. Cross Browser Testing: It allows users to test their websites with over the hundred resolution or browser and Operating System combinations. This also has support to mobile web-browsers, which is crucial because the web traffic is making shift from the primarily desktop computer users to primarily mobile ...

Mobile Application Testing: Strategy for Development

There are a huge number of demands and lots of competitions in the mobile application industries. In that demands and competitions, the mobile application testing has become more important. The testing phase of the mobile application testing looks like evil between the creative process and excitement of new products in the market. According to the survey, “In US, on an average 2-3 hours per day people spends their time on smartphones and tablets. On that time, they spent 80% on mobile application and remaining 20% on web applications.” Few list of key factors for successful mobile application testing strategies are: Selection of Device for Testing : Before introducing the mobile application test activities, first select the devices for testing the application. Selection decision is very important because only devices can help to targets maximum numbers of the customers for accessing the application. There are two parts for device selection: §   Device Model ...