So what is an enterprise drive?, it is not sadly a hard drive authorised by Starfleet to boldly go where no hard drive has gone before. It is a drive designed, manufactured and configured for use by the type of ‘enterprises’ that employ multi-user computer systems, server installations, networked systems and tiered storage arrays. Most if not all of the major drive manufacturers offer some form of enterprise class device, with Seagate’s Cheetah and ES as well as Western Digitals’ Velociraptor and RE2 and RE3 ranges being prime examples. So what does the term actually relate to? What an enterprise drive is, fundamentally stems from the demands such usage places upon it. Drives are commonly required to be in constant, round-the-clock operation. They must deliver the highest possible performance without sacrificing reliability, and they must be able to function in demanding environments. Because of the nature of their use, maximising capacity is not always the primary goal, and as a result the drives are often offered in Gb sizes that the average domestic computing enthusiast would consider very small in relation to their cost. So how are the various performance parameters achieved? Increased ‘Input/Outputs per Second’ (IOPS) result from higher rotational speeds and larger cache sizes, with the former commonly dictating the use of 2.5″ diameter platters, even for 3.5″ form factor drives. The smaller platters allow the spindle bearings to maintain stable head alignment at spin speeds regularly in the region of 15,000 rpm, and have the added benefit of reducing power consumption. 24/7 operation requires a higher standard of design, manufacturing tolerance and component quality. Because such drives are commonly housed in racks or enclosures with many other drives, fans and other motor driven devices, the ability to withstand vibration is a major consideration as is cooling, ventilation and airflow management. Increasing energy costs have meant that manufacturers have had to place a higher emphasis on the often conflicting demands of cooling and power consumption. The performance required also dictates the use of an interface that can support it. SCSI and Fibre Channel (FC) devices were often the first choice and may still be, though Serial Attached SCSI (SAS) and even high-end SATA are becoming increasingly evident. Drive firmware is likely to be more complex to handle demand management or ‘queuing’ as well as more robust error detection and correction (EDC) functions. All the aforementioned performance considerations mean that one of the easiest ways to identify an enterprise drive is, not surprisingly, by its higher cost. The increasing use of RAID systems combined with the increasing performance of conventional drives has meant that they are starting to be viewed as a viable alternative to the use of enterprise drives, but for applications that demand the ultimate in performance and reliability, the enterprise drive is likely to remain the weapon of choice. The quest for even higher specs has led to enterprise drives being used in RAID arrays and even the use of ‘short-stroking’ techniques. These involve the use of software that restrict the drive to using only part of the physical platter capacity, perhaps using only 10% of the overall sectors at the outer platter edges where access speeds are greatest. This also limits the time taken for the heads to reposition onto other tracks and also reduces the physical demands on the head actuator assembly. This obviously causes an associated reduction in capacity and increase in outlay for hardware so is likely to be reserved for ‘cost is not a factor’ applications. It was widely forecast that Solid State Device (SSD) drives, using flash memory technology and without any moving parts would become preeminent in the enterprise market. Here their performance characteristics gave them an advantage and their smaller capacities were not a barrier. However, though they are being chosen for many installations the traditional rotating platter hard drive is still very much in evidence in enterprise form, and no doubt the traditional hard drive manufacturers will be striving to keep it that way.
Posts Tagged ‘enterprise’
VNCScan Enterprise Console
VNCScan Enterprise Console allows you to remotely control and manage your workstations and servers. VNCScan is the legendary front end to VNC. With VNCScan, you cantake remote screen captures over the network, scan for and deploy VNC Remote Control on your network, search a network for a user… [ Remote Access Software ]
Hand in Hand – Database and Code Refractoring for Quality and Low cost Enterprise Software
Hand in Hand – Database and Code Refractoring for Quality and Low cost Enterprise Software K.Ravi Abstract Any software project development is supported by a programming language code (Front End) and a Database (Back end). Producing software is a very complex process that takes a considerable time to evolve. Poorly designed software systems are difficult to understand and maintain. Modifying code in one place could lead to unwanted repercussions elsewhere due to high coupling. Adding new features can cause further quality degradation to the code if proper design and architectural concerns were not implemented. Development in a large enterprise system with such attributes will, over time, lead to a myriad of concerns unless the system is periodically overhauled or refactored in some way. Software maintenance can take up to 50% of the overall development costs of producing software. One of the main attributes to these high costs is poorly designed code, which makes it difficult for developers to understand the system even before considering implementing new code. In the context of software engineering process, Software Refactoring has a direct influence on reducing the cost of software maintenance through changing the internal structure of the code to increase the design which helps the present and future developers evolve and understand the system. In this article we shall discuss mainly about database and code refractoring as these two are the major components of any software development Key words: Software Refractoring, Database refractoring, Software maintenance 1.Database Refractoring A database refactoring is a small change to a database schema which improves its design without changing, at a practical level, the semantics of the database. In other words, it is a simple database transformation which neither adds nor breaks anything. The process of database refactoring defines how to safely evolve a database schema in small steps. Database refactoring enables data professionals to work in an evolutionary manner, just as modern application developers do. It also provides a coherent strategy for organizations to dig their way out of the legacy database hole. A database refactoring is a simple change to a database schema that improves its design while retaining both its behavioral and informational semantics. For the sake of this discussion a database schema includes both structural aspects such as table and view definitions as well as functional aspects such as stored procedures and triggers. An interesting thing to note is that a database refactoring is conceptually more difficult than a code refactoring; code refactorings only need to maintain behavioral semantics while database refactorings also must maintain informational semantics. 2. Why Database Refactoring? There are two fundamental reasons why you want to adopt database refactoring: To repair existing legacy databases. Database refactoring enables you to safely evolve your database design in small steps, making it an important technique for improving the legacy assets within your organization. This is clearly much less risky than a “big bang” approach where you rewrite all of your applications and rework your database schema and release them all into production at once. Furthermore, it is much better than the “let’s try not to allow things to get any worse” strategy currently employed by the vast majority of data management groups which I’ve run into, a strategy which has no hope of success because all it takes is one development team to go around the data management group and do an imperfect database design. The bottom line is that legacy databases aren’t going to fix themselves, and that from a technical point of view database refactoring is a safe, simple way to improve data, and database, quality over time. July 2006 survey into the current state of data management shows that 33% of organizations either are, or intend to take, an refactoring-based approach to addressing existing production data quality problems. To support evolutionary software development. Modern software development processes, including the Rational Unified Process (RUP), Extreme Programming (XP), Agile Unified Process (AUP), Scrum, and Dynamic System Development Method (DSDM), are all evolutionary in nature. Craig Larman [4] summarizes the research evidence, as well as the overwhelming support among the thought leaders within the IT community, in support of evolutionary approaches. Unfortunately, most data-oriented techniques are serial in nature, relying on specialists performing relatively narrow tasks, such as logical data modeling or physical data modeling. Therein lies the rub – the two groups need to work together, but both want to do so in different manners. I believe that data professionals need to adopt evolutionary techniques, such as database refactoring, which enable them to be relevant to modern development teams. Luckily these techniques exist, and they work quite well, it is now up to data professionals to choose to adopt them. 3.The lifecycle of a database refactoring. 4.The process of database refactoring. Database refactoring as a three-step process: 1.Start in your development sandbox 2. Implement in your integration sandbox (es) 3.Install into production Step 1: Start In Your Development Sandbox Your development sandbox is the technical environment where your software, including both your application code and database schema, is developed and unit tested. The need to refactor your database schema is typically identified by an application developer who is trying to implement a new requirement or who is fixing a defect. For example, a developer may need to extend their application to accept Canadian mailing addresses in addition to American addresses. The main difference is that Canadian addresses have postal codes such as R2D 2C3 instead of zip codes such as 90210-1234. Unfortunately the ZipCode column of the Surface Address table is numeric and therefore will not currently support Canadian postal codes. The application developer describes the needed change to one of the Agile DBA(s) on their project and the database refactoring effort begins. As depicted in Figure, the Agile DBA and application developer will typically work through some or all of the following steps to implement the refactoring: •Verify that a database refactoring is required •Choose the most appropriate database refactoring •Deprecate the original schema •Write unit tests •Modify the database schema •Migrate the source data •Update external access programs •Update your data migration script(s) •Run your regression tests •Announce the refactoring •Version control your work Fig. Database refactoring process Step 2: Implement In Your Integration Sandbox After several days have passed you will be ready to implement your database refactoring within your project integration sandbox. The reason why you need to wait to do so is to give your teammates time to refactor their own code to use the new schema. Teams that have chosen to encapsulate access to their database via the use of a persistence framework will find it easier to react to database schema changes and therefore may discover they can tighten up the period between implementing a database refactoring within a development sandbox and in their project integration sandbox. This is due to the fact that the database schema is represented in meta data, therefore many database schema changes will only require updates to the meta data and not to the actual source code. To deploy into each sandbox you will need to both build your application and run your database management scripts (tools such as Autopatch can help). The next step is to rerun your regression tests to ensure that your system still works – if not you will need to fix it in your development environment, redeploy, and retest. The goal in your project integration sandbox is to validate that the work of everyone on your team works together, whereas your goal in the Test/QA sandbox is to validate that your system works well with the other systems within your organization. A critical part of deploying database refactorings into your Test/QA sandbox, I’m using the plural now because you typically introduce several database factors into this environment at once, is communication. Long before you change your database schema you need to communicate and negotiate the changes with the owners of all of the other applications that access your database. Your enterprise administrators will be involved in this negotiation, they may even facilitate the effort, to ensure that the overall needs of your organization are met. Luckily the process that you followed in your development sandbox has made this aspect of database refactoring easier: • The Agile DBA only allowed database refactorings that can realistically be implemented – if another application team isn’t going to be able to rework their code to access the new schema then you can’t make the change. • The documentation, even if it’s only a brief description of each change, that the Agile DBA wrote is important because it provides an overview of the changes that are about to be deployed. • The new version physical data model (PDM), which was updated as database refactorings were implemented, serves as a focal point for the negotiations with other teams. Agile Modeling (AM) would consider the PDM to be a “contract model” [...]
Worldwide Crosspoint Switch Market Shares Strategies, And Forecasts, 2009-2015-Aarkstore Enterprise
Less expensive crosspoint switches allow proliferation of devices into a wide range of equipment applications. According to Susan Eustis, lead author of the study, “Economies of scale leverage the technology advances needed to make crosspoint switches competitive. Integration technology provided by crosspoint switches solves the issues poised by high speed network conflicting standards. Crosspoint switch price reductions are poised to drive market adoption by making multimedia technology affordable.” The Internet and wireless communications dominate communications technology. Wireless web devices, Voice over Internet Protocol (VoIP), video-on-demand, third generation (3G) wireless services increase demand for higher speed, higher bandwidth communications systems. Remote network access has increased network bandwidth requirements and complexity. The continuing adoption of broadband technology is unrelenting. E-mail, instant messaging, blogging, wikis, and e-commerce originally PC based, are being combined with the increasing availability of next-generation wireless devices. Features include internet browsing, cameras and video recorders. These initiatives drive data traffic through the network infrastructure. The different types of data transmitted at various speeds over the Internet require service providers and enterprises to invest in multi-service equipment. Broadband equipment is emerging that can securely and efficiently process and transport the varied types of network traffic, regardless of whether it is voice traffic or data traffic. To achieve the performance and functionality required by such systems, original equipment manufacturers (OEMs) utilize complex crosspoint switch ICs to address both the cost and functionality of a system. As a result of the pace of new product introductions in response to the changing market conditions in the telecommunications environments, there is a proliferation of standards. Crosspoint switches are designed to accommodate cost reductions involved in implementing new systems. Difficulty of designing and producing required ICs has stimulated the market for crosspoint switches. A position has evolved for the semiconductor companies. Equipment suppliers have increasingly outsourced IC design and manufacture to semiconductor firms with specialized expertise. These trends have created a significant opportunity for IC suppliers that can design cost-effective solutions for the processing and transport of data. OEMs require IC suppliers that possess system-level expertise and can quickly bring to market highperformance, highly reliable, power-efficient ICs. Demand for high bandwidth, high speed video and multimedia applications create demand for cross point switches. The weakening global economy is a concern to vendors participating in the crosspoint switch market. Previous revenue targets are being revised downward. Some market segments like security and video are anticipated to remain strong even in the global downturn. Some of the market segments will shrink from 2008 levels before picking up again. The automotive market appears to be particularly vulnerable. Carrier spending is likely to be cut back during the economic downturn. Many semiconductor companies have cut back their expected revenue outlook. Texas Instruments is illustrative of the effect of the financial market thrashing. DALLAS (Dec. 8, 2008) – In a scheduled update to its business outlook for the fourth quarter of 2008, Texas Instruments Incorporated (TI) (NYSE: TXN) today lowered its expected ranges for revenue and earnings per share (EPS). The company currently expects its financial results to fall within the following ranges: * Revenue: $2.30 – 2.50 billion, compared with the prior range of $2.83 – 3.07 billion. December 18, 2008 – LSI Corporation (NYSE: LSI) business outlook for the fourth quarter ending projects revenues of $570 to $610 million. The previous business outlook, which was announced on October 22, 2008, projected revenues in the range of $670 million to $710 million. The revised LSI outlook reflects anticipated sales levels that are lower than previously expected due to the weakening global macroeconomic environment. LSI has already begun taking steps to reduce operating expenses as a result of continuing demand uncertainty and expects to maintain tight expense controls for the foreseeable future. Markets for crosspoint switches at $554 million in 2008 are anticipated to reach $2.98 billion by 2015, growing in response to decreases in unit costs and increases in integrated IC functionality. Some applications are relatively recession proof, including security and high speed video applications. Crosspoint switches are poised to make people more productive in security environments, help increase productivity with faster desktop access capabilities, and increase storage seek times. Report MethodologyThis is the 398th report in a series of market research reports that provide forecasts in communications, telecommunications, the internet, computer, software, and telephone equipment. The project leaders take direct responsibility for writing and preparing each report. They have significant experience preparing industry studies. Forecasts are based on primary research and proprietary data bases. Forecasts reflect analysis of the market trends in the segment and related segments. Unit and dollar shipments are analyzed through consideration of dollar volume of each market participation in the segment. Market share analysis includes conversations with key customers of products, industry segment leaders, marketing directors, distributors, leading market participants, and companies seeking to develop measurable market share. Over 200 in-depth interviews are conducted for each report with a broad range of key participants and opinion leaders in the market segment. Table of Contents : Crosspoint Switch Executive Summary ES-1 Demand For Integrated Communications Semiconductors ES-1 Crosspoint Switch Market Shares ES-6 National Semiconductor MuxBuffer ES-9 Crosspoint Switch Market Forecasts ES-10 <!–[if !supportEmptyParas]–> <!–[endif]–> 1. Crosspoint Switch Market Dynamics and Market Description 1-1 1.1 Internet And Wireless Dominate Communications Technology 1-1 1.1.1 Optical Networks 1-2 1.1.2 Data And Video Traffic Being Added In Abundance To Voice Traffic 1-2 1.1.3 Semiconductor Companies Design Crosspoint Switches 1-3 1.2 Storage Industry 1-4 1.3 Mixed Signal Analog Integrated Circuit Market 1-6 1.3.1 Crosspoint Switch Matrix With Input And Output 1-6 1.3.2 Enterprise Networks 1-9 1.3.3 Network Access Last Mile Of Telecommunications Network 1-10 1.3.4 Metropolitan Area Networks 1-10 1.3.5 Internet 1-11 1.4 Security Systems 1-12 1.5 Crosspoint Switch Architecture 1-14 1.5.1 Multistage Crosspoint Switching Designs 1-16 1.6 Signal Processing 1-17 1.7 Product Positioning 1-18 1.7.1 Crosspoint Switch Advantages 1-22 1.7.2 Crosspoint Limitations 1-25 1.8 Crosspoint Switch Functions 1-26 1.8.1 Crosspoint Switch Standards 1-26 1.8.2 Crosspoint Switch Equalization Technology 1-26 1.8.3 Channel-Isolation Capabilities 1-29 1.8.4 Input Equalization 1-29 1.8.5 Power Conservation Technology 1-30 1.8.6 Built-In System Test Features 1-30 <!–[if !supportEmptyParas]–> <!–[endif]–> 2. Crosspoint Switch Market Shares and Market Forecasts 2-1 2.1 Demand For Integrated Communications Semiconductors 2-1 2.1.1 Crosspoint Switch IC Market Participants 2-8 2.2 Crosspoint Switch Market Shares 2-9 2.2.1 Carrier Crosspoint Switch Market Shares 2-12 2.2.2 NTSC or PAL Composite Video Input Crosspoint Switch Market Shares 2-14 2.2.3 LVDS Crosspoint Switch Market Shares 2-16 2.2.4 MindSpeed Multi-Gigabit Switching Systems 2-19 2.2.5 Intersil Video Crosspoint Switch Clearer Pictures and Greater Flexibility 2-19 2.2.6 Intersil Black-Level Consistency with 32×16 Video Crosspoint 2-20 2.2.7 Maxim MAX4355 16×16 Nonblocking Video Crosspoint Switch with I/O Buffers 2-20 2.2.8 National’s LVDS Portfolio 2-21 2.2.9 National Semiconductor AEC-Q100 Compliant LVDS Crosspoint Switches, Drivers, and Receivers 2-22 2.2.10 National Semiconductor Digital LVDS/CML Crosspoints 2-23 2.2.11 National Semiconductor Analog Crosspoint Switch Video Solutions 2-24 2.2.12 Texas Instruments 2-24 2.3 Crosspoint Switch Market Forecasts 2-25 2.3.1 Automotive Crosspoint Switch Market Forecasts 2-29 2.3.2 DWDM/CWDM Carrier Ethernet Crosspoint Switch Market Forecasts 2-30 2.3.3 Video Crosspoint Switch Market Forecasts 2-31 2.3.4 Security Crosspoint Switch Market Forecasts 2-33 2.4 Analog IC Market 2-34 2.4.1 Communications Industry 2-35 2.4.2 Carrier Networking 2-36 2.4.3 Next-Generation SONET/SDH Networks Use Enhanced Ethernet-Over-SONET 2-37 2.4.4 Exponential Increases In Data Traffic 2-37 2.4.5 Enterprise Networking 2-38 2.4.6 Data Center Trend Towards Converged Ethernet 2-40 2.4.7 Storage Networking 2-40 2.4.8 Next-Generation Networking Integrated Circuits 2-42 2.4.9 Higher Integration Of Multiple Functions On The Same Chip: Switching, Routing, CPUs, Memory 2-42 2.4.10 Communications Industry 2-47 2.4.11 Disparity Between Bandwidth In The Fiber Optic Core And Bandwidth At Subscriber Premises 2-48 2.4.12 Demand For Faster Speed And More Reliable Communications Services 2-49 2.4.13 Access Networks 2-49 2.5 Crosspoint Switch Pricing and Availability 2-50 2.6 Crosspoint Switch Geographical Market Segments 2-51 2.6.1 National Semiconductor Geographic Sales 2-53 2.6.2 Analog Devices 2-54 <!–[if !supportEmptyParas]–> <!–[endif]–> 3. Crosspoint Switch Product Description 3-1 3.1 Crosspoint Switches 3-1 3.1.1 Enterprise Systems 3-1 3.1.2 Carrier Systems 3-2 3.2 National Semiconductor 3-2 3.2.1 National Semiconductor DS10CP154A 1.5 Gbps 4×4 LVDS Crosspoint Switch 3-3 3.2.2 National Semiconductor AEC-Q100 Compliant LVDS Crosspoint Switches, Drivers, and Receivers 3-4 3.2.3 National’s LVDS Portfolio 3-7 3.2.4 National’s LVDS Portfolio Pricing and Availability 3-7 3.2.5 National Semiconductor LVDS 3-7 3.2.6 National Semiconductor Video System Solution Support 3-10 3.2.7 National Semiconductor Automotive (Infotainment) 3-10 3.2.8 National Semiconductor Video Surveillance Market Analog Crosspoint Switches 3-11 3.3 Analog Devices 3-12 3.3.1 Analog Devices ADV320 3-12 3.3.2 Analog Devices ADV3200 Availability and Pricing 3-13 3.4 Mindspeed Crosspoint Switches 3-17 3.4.1 Mindspeed Products 3-17 3.4.2 Mindspeed Crosspoint 4×4 Switches 3-18 3.4.3 Mindspeed Crosspoint 17×17 Switches 3-20 3.4.4 Mindspeed Crosspoint 34×34 Switches 3-21 3.4.5 Mindspeed Crosspoint 72×72 Switches 3-22 3.4.6 Mindspeed Crosspoint 144×144 Switches 3-24 3.4.7 Mindspeed Large Crosspoint Switches For High-Definition Multimedia Interface Routing/ Switching Applications 3-26 3.4.8 Mindspeed Large Crosspoint Switches 3-28 3.4.9 Mindspeed Mid-Size Crosspoint Products (17×17) 3-29 3.4.10 Mindspeed Crosspoint Switches Non-Blocking Switch Core 3-31 3.4.11 Mindspeed® Crosspoint Switch Usde In Infinera DTN Optical System 3-32 3.4.12 Mindspeed 144×144 3.2 Gbps Crosspoint Switch with [...]
Nokia Mobile Phone E65 an Enterprise Solution
Introduction In order to tap the large business user and the professionals on the go Nokia has introduced the E series. Among that the E65 is one latest offering by the company aimed at the high end users. Unlike other business phones that are wide and bulky this one is more like the regular mobile phone. It is a device for energetic people, who make loads of calls and communicate with great many of workmates Nokia E65 This Nokia mobile phone has a slider handset, and alongside the capable S60 operating system. It is the company’s smallest slider-styled offerings, measuring up at 105x49x15.5 mm. It is a flashy piece due to the display edging and patterned surface. It comes in colors like silver and grey or black. The company seems to sway towards fashion segment as they have launched in red too. This Nokia mobile phone weighs in at 115 grams and measures 137 mm long when zipped open, which makes for comfort. An added feature is that you can accept and make calls without sliding the E65 open. One of the highlights of the phone is the leather-like surface of the battery cover at the back. The quality of the plastic is good it gives the feel of something between soft touch and standard plastic coating. Software It has the Nokia’s Team Suite software. This groups management software helps to set up groups and send e-mails, texts and MMS’s to the whole group at once, view Web pages that relate to them and initiate conference calls with them. One of the many buttons on the front of the casing is used for conference calling. There is also a button to mute the microphone. Features The handset utilizes QVGA display (240×320 pixels, 2.2 inches, 34×45 mm), capable of 16 mln. Colors (TFT). The 65 comes installed with a mirror layer for the display, making its usable when the sun is shining bright and keeping the picture perfectly clear, which is especially vital for navigation mode. Also the handset carries ambient light sensor, which adjusts backlighting level basing on current light conditions. It also has a 2 mega pixel camera but lacks self-portrait mirror, flash, auto-focus or a macro mode The built in Wi-Fi makes in the usage of Voice over IP calls and Web browsing much easier. The phone comes with PC connectivity software and a USB cable and has a battery life of 10 hours of non-stop MP3 music. The battery life is quoted at 3 hours talk time and 240 hours standby time. This Nokia mobile phone comes loaded with Quick Office, ZIP, Adobe PDF, and HP Printer. You can also upload Golf Pro Tour game. This phone a well-packed device, sporting typical functionality for current S60 solutions, an add-on in the form of WiFi, a few extra keys and Team Suite.
SAML 2.0 Token Bridging with Intel® SOA Expressway
One of the cool features of Intel(R) SOA Expressway is its ability to easily handle token bridging with just a few clicks. What is token bridging you ask? With the increased need for Enterprises to talk outside their perimeter to other Enterprises or cloud services, we need an easy way to morph message level credentials into the proper form as they move across the dynamic perimeter of the Enterprise. In practice this means that Enterprises deal with different authentication directories and identity management systems and employ different standards and even different variants of authentication standards. If we cross-multiply authentication schemes used in the “web” and “web service” worlds, the range of token types begins to multiply like out of control rabbits: Credentials can be anything from simple HTTP Basic Authorization tokens, Kerberos tickets, custom Microsoft schemes like NTLM, OAuth access tokens, SAML tokens of various types, X.509 tokens, SSL certificates, WS-Security Username/Password tokens and then to make matters more complex, you also have domain-specific cookies from legacy identity management systems such as CA Siteminder, IBM Tivoli Access Manager, and Oracle Access Manager. Fortunately, Intel(R) SOA Expressway gives you some nice tools to implement a cross-domain token broker and ease the pain of mapping a format used internally to something that might be accepted by a business partner, such as a SAML token. In this blog post, we’ll return to the familiar calculator web service and show how you can use Intel(R) Expressway to implement a simple policy that maps a HTTP Basic Authentication token to a SAML 2.0 authentication assertion for a SOAP web service. To follow along, you’ll need a copy of SOA Expressway, which can be downloaded from http://www.dynamicperimeter.com as well as a SOAP client such as SOAP UI . You will also need a sample web service. In this case we’ll use an example calculator service. You can grab the WSDL here . The Basic Architecture Expressway is a web services proxy, which means it’s usually placed in the line of fire between a client and the actual service. The architecture assumes a request leaves the Enterprise and calls a partner web service over the Internet. In the basic architecture the enterprise will make a SOAP call with a username and password which Expressway will map to a SAML assertion for the destination calculator web service. More astute readers will recognize that in this model, Expressway is acting as a SAML authority because it is actually the issuer of the assertion. In the actual example we will go through, we’ll omit the actual authentication of the user as that would make this post a bit long, but it can be easily done by Expressway and is usually accomplished by contacting an LDAP directory. The Application To begin, start up Intel(R) Services Designer and select File > New > Intel(R) SOA Expressway Project. Then, give your project a name such as ‘GenerateSAML’ and select ‘Empty Project’ for the Application type drop-down and hit finish. To keep things simple, we’ll just add a single proxy workflow. To do this, right-click on the project name and choose New > Intel(R) SOA Expressway Workflow. It’s one of the options lower down on the context menu. After choosing the project for the workflow, you should see the new workflow creation screen. Click the thumbnail to expand. Choose the proxy workflow and hit Finish. In the next screen you need to provide the location for the WSDL and be sure to select the specific operation to proxy. In this simple example we are only supporting the “add” operation though you can easily support them all with Expressway’s service proxy wizard. If you’ve done everything right so far you’ll get a basic proxy workflow consisting of just receive, invoke, reply. The Security Policy The starting point workflow is very simple. To start with it just channels the SOAP request and response through Expressway. How do we add our security policy? To add token bridging to this we need to drag the AAA step from the palette between the receive and invoke actions. Click the thumnail to expand. Next, in the properties tab for the AAA step we can select the option to create a new policy. Give it a simple name such as Policy.aaa and hit Finish. Then, double click on the new .aaa file in the project which brings up the policy editor in the main workspace. Then, if you click on the Identity Management tab on the bottom portion of the window you will be shown the token bridging options We’ll set a few important options here. First, we need to tell the policy to extract the identity from an HTTP Basic Authentication header. For now, we’ll skip authentication but if you want to also authenticate the user against a directory or identity management system it can be done by clicking the box to authenticate the identity. For the map options, we’ll choose a SAML assertion and fill out a value for the issuer. Click the thumnail to expand. To have Expressway sign the assertion, simply click on the Signature option. Expressway ships with a demonstration key-pair that can be used for testing purposes. It’s part of the default security package provided with the product. Click the thumnail below to expand. Finally, if you want to generate a version 2.0 assertion, you can set this option from the policy options tab as follows. Click the thumbnail to expand. If you’ve done everything correctly so far you should get summary of what the policy is doing written in English language in the Properties tab for the AAA step. You can see this if you double-click the .bpel file and then make sure the AAA step is selected. Click the thumbnail to expand. Deploying the Application To deploy the application, we can right-click on the project in Intel® Services Designer and then upload the application to an active configuration on the appliance. Before activation make sure that the invocation agent for the service (in our case the calculator service) is set with the proper IP address and that Expressway can reach this network location. You will also have to make sure the default security package is selected so we can use the demo signing key. Click the thumbnal to expand. For this application to work, the destination service has to be able to understand and verify the SAML 2.0 assertion that has been added to the message. In our simple case the calculator web service ignores the headers completely, so we can really send anything and we won’t have a way of knowing if Expressway actually inserted the SAML assertion. One way to check is to enable processing of the SAML assertion for the destination service. Another way, however, is a little trick that can be used to force Expressway to throw the message back directly to the client for debugging purposes. To do this, all you have to do is change the output of the ‘Reply’ step to be the output of the ‘AAA’ step. This is done by selecting the appropriate drop-down in the Reply step. Click the thumbnail to expand: To see this in action, we can fire-up our soap client (SOAPUI is shown here) and immediately see what Expressway has been up to. In this case we can see all of the details – the incoming message has an HTTP Basic Authentication header and the output SOAP message has a SAML 2.0 assertion. Click the thumbnail to expand.
Application Development And Lifecycle Management: The Impact Of Agile Practices On People, Processes, And Tools-Aarkstore Enterprise
The most recent trend of cloud computing is also opening new possibilities that are lowering the cost barrier, increasing access to high performance computing, and also lowering the skill barrier for non-programmer information workers, whether in SMEs or departments in large organisations, to build business applications. KEY FINDINGS- ALM systems have improved considerably from the first generation of products; the new generation is Web-based and strong on collaboration.- Agile methodology adoption has entered mainstream development and is making developers and managers rethink how they carry out application development.- Agile practices are having a major influence on the ALM solutions market; supporting Agile processes is a hot area.- ALM system architecture identifies core lifecycle functions, including process support with workflow, integrated data repository, and reporting.- Business Intelligence (BI) for application development has now become an ALM system fixture, offering advanced analytics applied to project statistics.- Software estimation remains a niche activity but should, be a core lifecycle activity in ALM.- Defect and Issue Management is another core activity that cross-cuts the application lifecycle and is supported well by leading ALM systems.- ALM system users should have read-and-write features for process guides, allowing users to modify content, supporting collaboration and knowledge exchange.- ALM systems that alter the functionality exposed depending on the process selected represent an advanced, state-of-the-art technology, not yet seen in the market.- The rise in Software Systems Engineering reflects the increasing use of software CATALYSTApplication development continues to evolve with processes and methodologies receiving significantattention through Agile practices, while on the tooling side a new generation of Application LifecycleManagement (ALM) products are appearing with process and workflow support figuring largely.June 2009 ANALYSISIntroductionSoftware application development is one of those subjects that never disappears but is always evolving. Since the last general survey Report on this subject – Application LifecycleManagement (ALM), published in September 2005 – there has been a lot of activity in the ALM field. With our colleagues in Datamonitor we published an ALM Decision Matrix in 2007 that looked at the vendor ALM suite market, and we now repeat that exercise in this Report with all the leading vendors participating. (The Datamonitor Decision Matrix also replaces what used to be the Market Lifecycle Ratings in Technology Evaluation and Comparison Reports).The areas that are currently receiving the greatest activity in application development are:- Agile development and Agile project management.- ALM.- Testing and test management.- Enterprise Web 2.0. The application development subjects that are on the horizon, are:- Development in the Cloud.- Parallel programming (especially General Purpose computing on Graphics Processing Units – orGPGPU).- Extension of ALM to overlap IT governance.- RESTful Service Oriented Architecture. (REST is Representational State Transfer). While what and how applications are being developed evolves, developers are still needed to programme the machines and create these applications. It had been considered that advanced modelling such as Model Driven Development (MDD) in the guise of software factories would at some point deliver on the next leap forward, a technological breakthrough such as a higher abstraction compiler that takes models rather than a high-level programming language to churn out the machine code. The Object Management Group’s Model Driven Architecture (MDA) appeared to be moving in that direction. This did not transpire, and is not likely to in the immediate future. These themes are expanded upon below.Business Issues Ultimately, software applications are built to satisfy the needs of the business, and the subject of the clash of two different cultures – the IT department and the rest of the business – has been discussed often, possibly to exhaustion. Some intractable problems become ‘solved’ through irrelevance because the ground has moved, and it can be said that whereas in the early days of computing the computer department in a business was a quite distinct function, a place where data was sent to be processed and returned with some useful statistics or reports, today there are businesses whose sole basis for existence relies on the IT function. Examples vary from obvious ones such as online banks and Web 2.0 companies, to less obvious virtual companies that operate solely due to the existence of the Internet and products with embedded software where the software component has grown exponentially. The net result of this shift towards greater reliance on IT is that the business has to take a greater interest in its IT function to succeed in the market, especially if the IT people are not delivering. A real-world example illustrates how businesses are tackling this problem (names are omitted for confidentiality reasons): an IT company arose from being a small operation to having a billion dollar turnover in a short period. This company used to release its key platform application on an annual basis, but as a result of this rapid growth its current releases were taking 18 months and longer. The CEO gave the Chief Technology Officer (CTO) the highest priority directive to solve the problem. The CTO decided that all the company’s developers would switch to Scrum, the most popular Agile methodology, in big-bang fashion. The switchover was a success and delivery was back to a 12-month cycle. BT is another example where in this instance the CEO directed the company to adopt Agile, and an incremental adoption plan is in progress. Alternately, the concept of reducing waste is a message that many businesses understand and this is central to Lean Development, which takes many ideas from the lean movement and Total Quality Management, and combines them into an Agile methodology. Lean Development is found to be more comprehensible to businesses than some of the more developer-oriented Agile practices. Businesses also want greater real-time insight into software project progress, and the new generation of BI solutions integrated into ALM suites provide this capability. Rather than reacting post-event, senior managers can act to avert problems escalating into software crisis dimensions. In particular, visibilityinto quality control and test performance of the work in progress is necessary. When schedules become pressured, testing is the area that is traditionally cut by Project Managers. Therefore senior business managers must keep track of testing and quality – getting this wrong incurs long-term damage to the organisation in the marketplace. Agile methodologies are liked by business executives because they maketesting an integral part of the development lifecycle, not the last activity beforeshipping. Enterprise Web 2.0 represents a puzzle to many company executives: they see staggeringly successful businesses emerge, based on the Internet and the set of concepts and technologies behind Web 2.0, but do not see how this is relevant for them, or how they can emulate that success. This is likely to change as Web 2.0 culture permeates the workforce, that were raised in the Internet age, and use of the Web grows. Cloud Computing will accelerate that process, as various entrants trial new business models for earning revenue by offering utility-like computing services. Addressing security concerns is paramount though and will act as the brake whenever any mission-critical applications are considered. Expendable, low-risk business activity will find its way to the Cloud today. It will probably take the Internet mark 2 (there are various initiatives for upgrading the Internet, increasing bandwidth and improving security at nodes being prime motivations), for Cloud Computing to become truly ubiquitous. Technology Issues The ALM suite represents the best investment to support developers and management. However, its takeuphas tended to be at the large enterprise level, with many smaller organisations relying on point solutions. This has changed in the last few years with the increasing adoption of Agile methodologies and the need to support the greater discipline and process required in these practices. The waterfall process is relatively straightforward, with simple stage-gates and linear workflow, whereas an Agile methodology like Scrum has iterations (daily Scrums) within iterations (Sprints, Spikes, and Retrospectives) within iterations (the release plan). In order to support complex projects and distributed team members there is a need for tooling that allows Agile work items, called ‘stories’ or ‘features’, to be easily moved around the workflow. Developer testing is a core activity in Agile, so rigging-up automated, continuous testing is necessary. Real-time reports with charts for velocity and burndown need to be easily accessed and displayed to all team members. The project managers need the electronic equivalent of a white board to easily manage an Agile project and perform the various activities in the process. For example, at the iteration end a retrospective is held that requires allstakeholders to attend and the product owner to re-prioritise stories. This needs to be easily performed and tracked. A new generation of ALM solutions have appeared on the market to support these activities –discussed in Section 2.3 of this Report. ALM architecture, our state-of-the-art view of ALM given in Section 3.1, makes a number of distinctions: it separates out core ALM activity, cross-cutting the lifecycle segments, from plug-in ALM tools via a Service Oriented Architecture (SOA) integration layer, and from external development tools like Integrated Development Environments, test tools, and third-party ALM tools via an interoperability layer. The core layer comprises: [...]
First, Responder, Homeland Security, And Law Enforcement Robots Market Shares, Strategies, And Forecasts, Worldwide, 2010 To 2016-Aarkstore Enterprise
HTML clipboard Worldwide markets are poised to achieve significant growth as the first responder and homeland security ground robots are used globally. Growth comes as the border patrols and law enforcement agencies use robots to achieve broader security in a less expensive manner, delivering the promise of automated process in yet another industry. First responder robots bring changes in every region while the globally integrated enterprise replaces nationalistic dominance, creating broader cooperative police actions that replace nationalistic wars. These police actions are aimed against the bad guys. This cost is creating resistance among the agencies to spend such a large amount for what is seen as a device that gives little return in comparison to what a person can do all year. Costs of robots are expected to decrease rapidly in the next year, creating a much larger market than exists now. The current market at $203 million does provide a significant base for solid growth. Vendors of homeland security and first responder robots have positioned to provide a common framework through which federal, state, local, and tribal governments can address emergencies. US federal first responder agencies are negotiating agreements with state and local government law enforcement groups to share equipment. First responder robots cost $50,000 and up, the cost of a person for one year. Whereas a person can patrol and investigate, a first responder robot able to sniff for explosives is not justified in high quantity. .a few shared units go a long way in detecting explosives. The challenge for vendors is to find applications where the robot is used 24×7 365 days per year. Then there is payback. An exception is an airport and a border patrol crossing point where there is continuous need to sniff for explosives. First responder and homeland security robots are useful as patrol units. Just as foot police and patrol cars look for dangerous situations, so also a first responder robot can patrol an area with cameras and chemical sensors. First responder and homeland security robot automation of the defense process is the next wave of first responder and homeland security evolution. As automated systems and networking complement the Internet , communication is facilitated on a global basis. The first responder and homeland security charter is shifting to providing protection against terrorists and people seek to maintain a safe, mobile, independent lifestyle. Much of the first responder and homeland security mission is moving to adopt a police force training mission, seeking to achieve protection of civilian populations on a worldwide basis. According to Susan Eustis, the lead author of the study, “the purchase of First responder and homeland security Robots s is dependent on budget constraints. The use of First responder and homeland security Robots s is based on providing a robot that is less expensive to put in the field than a trained soldier. That automation of process has appeal to those who run the first responder and homeland security. Robots are automating first responder and homeland security ground systems, permitting vital protection of police officers and people in the field, creating the possibility of reduced fatalities in this profession. Mobile robotics operate independently of the operator. The innovation coming from all the vendors is astounding. No one innovation is more significant than another. One vendor, BAE Systems has an ant size robot useful for reconnaissance and networking robots in development. As soldiers take up secure positions behind a wall, they deploy a small reconnaissance team. The initial deployment is poised to be a very, very small reconnaissance team. Some hopping, some flying, the stealthy autonomous reconnaissance squad vanishes into a suspicious building for several minutes, then relays the all-clear back to its partners outside when that is the case. Use of remote-control toys in Iraq started as improvised robots to check out possible roadside bombs. There has since been a flurry of activity on the robotic explosive ordnance disposal (EOD) front since that early beginning. Deliveries of smaller and cheaper Bots are anticipated. The emergence of a market for intelligent, mobile robots for use in the field and the confined areas of city fighting presents many opportunities. Units used in public spaces and on the border create a better, more flexible, more cost efficient first responder and homeland security. Technology is used to actuate the disparate robot types. Core robotics research and advances in robotic technology can be applied across a variety of robotic form factors and robotic functionality. Advances feed on and off of each other. With each new round of innovation, a type of technological cross pollination occurs that improves existing robotic platforms and opens up other avenues where intelligent mobile robots can be employed, effectively creating new markets. Roboticists are more advanced in their training and in the tools available to create units. First responder and homeland security robots have evolved from units used in the field to manage different situations that arise. Robots save lives.. Robotic security systems have an emphasis on causality reduction during law enforcement activities. This has resulted in investment in robotics technology that is useful. Robotic research is on the fast track for government spending. First responder and homeland security ground robot market forecast analysis indicates that vendor strategy is to pursue developing new applications that leverage leading edge technology. Robot solutions are achieved by leveraging the ability to innovate, to bring products to market quickly. First responder and homeland security purchasing authorities seek to reduce costs through design and outsourcing. Vendor capabilities depend on the ability to commercialize the results of research in order to fund further research. Government funded research is evolving some more ground robot capability. Markets at $203.1 million in 2009 are anticipated to reach $3.7 billion by 2016. Report Methodology This is the 435th report in a series of primary market research reports that provide forecasts in communications, telecommunications, the Internet, computer, software, telephone equipment, health equipment, and energy. Automated process and significant growth potential are a priorities in topic selection. The project leaders take direct responsibility for writing and preparing each report. They have significant experience preparing industry studies. Forecasts are based on primary research and proprietary data bases. The primary research is conducted by talking to customers, distributors and companies. The survey data is not enough to make accurate assessment of market size, so It looks at the value of shipments and the average price to achievem market assessments. Our track record in achieving accuracy is unsurpassed in the industry. We are known for being able to develop accurate market shares and projections. This is our specialty. The analyst process is concentrated on getting good market numbers. This process involves looking at the markets from several different perspectives, including vendor shipments. The interview process is an essential aspect as well. We do have a lot of granular analysis of the different shipments by vendor in the study and addenda prepared after the study was published if that is appropriate. Forecasts reflect analysis of the market trends in the segment and related segments. Unit and dollar shipments are analyzed through consideration of dollar volume of each market participant in the segment. Installed base analysis and unit analysis is based on interviews and an information search. Market share analysis includes conversations with key customers of products, industry segment leaders, marketing directors, distributors, leading market participants, opinion leaders, and companies seeking to develop measurable market share. Table of Contents : FIRST RESPONDER ROBOT EXECUTIVE SUMMARY ES-1 First Responder, Homeland Security, and Law Enforcement Robots Market Driving Forces ES-1 Homeland Security And Police Ground Robots ES-2 Robots Operate Independently ES-2 Homeland Security Law Enforcement And First Responder Ground Robots Market Shares ES-5 Homeland Security Law Enforcement And First Responder Ground Robots Market Forecasts ES-6 1. FIRST RESPONDER ROBOTS MARKET DESCRIPTION ANDMARKET DYNAMICS 1-1 1.1 First Responders 1-1 1.1.1 First Responder Need for Robots 1-2 1.2 First Responder Robot Border Patrol 1-3 1.2.1 Border Patrol and Homeland Security 1-5 1.3 Delivering Robotic Capabilities to Combat Teams 1-6 1.4 Military Robot Scope 1-7 1.4.1 Military Robot Applications 1-8 1.5 Army’s G8 Futures office 1-11 1.5.1 Delivering Capabilities to the Army’s Brigade Combat Teams 1-13 1.5.2 Transition Between The Current Market And Where The Market Is Going 1-14 1.5.3 Different Sizes of UGVs 1-15 1.6 Types of Military Robots 1-17 1.6.1 Telerob Explosive Observation Robot and Ordnance Disposal 1-17 1.6.2 QinetiQ North America Talon® Robots Universal Disrupter Mount 1-20 1.6.3 General Dynamics Next-Generation CROWS II Increases Soldiers Safety 1-22 1.6.4 Soldier Unmanned Ground Vehicle from iRobot 1-23 1.7 UGV Enabling Technologies 1-24 1.7.1 Sensor Processing 1-25 1.7.2 Machine Autonomy 1-26 1.8 Military Robot Bandwidth 1-27 1.8.1 UGV Follow-Me Capability 1-27 1.8.2 Communications Bandwidth 1-28 1.8.3 Battery Power 1-28 1.8.4 Combination Of Batteries Linked To Onboard Conventional Diesel 1-29 1.9 SUGVs 1-30 1.9.1 Mid-Size Category UGV 1-30 1.9.2 Large UGV 1-31 1.9.3 U.S. Army Ground Combat Vehicle 1-32 1.9.4 TARDEC 1-33 1.9.5 Tacom 1-34 2. FIRST RESPONDER ROBOT MARKET SHARES AND FORECASTS 2-1 2.1 First Responder, Homeland Security, and Law Enforcement Robots Market [...]
Review: 2009 Top Ten Technology enterprise storage industry analysis – Storage, Security – Security Industry
2009, would go away, Over the past year, the occurrence of too many things, multi-core, high-performance computing, cloud computing, even before the “Finish” Godson let our excitement once. Whole IT Industry gradually recovered in the financial crisis, servers, or more or less large number of innovative technologies amazed us. However, the server does not cover the field of technology Enterprise Other areas, referred to storage technology, emerged ten prominent enterprise technology, we believe these technologies in the enterprise will have a tremendous impact, and continue …. IT industry in different areas of development have a different meaning to address the impact of the financial crisis. Storage Product Field is no exception, with the development of cloud computing, cloud storage as a technology to be mentioned; 10Gb Ethernet and SAS2.0 will replace Fibre Channel (FC) technology; Disaster Recovery application to become the cornerstone of sustainable development of enterprises; storage virtualization features adhering to the development of virtual technology changing. A result, the storage industry is still hot in the financial crisis continued, just as any standing proudly Market The success of most front-end technology, not only the development of its unique application, you can make the entire storage industry, rapid growth of the market, let us remember to open the door to re-examine changes in the storage industry this year. Cloud Storage Proposed the concept of cloud storage, and won the support and concern of many manufacturers have been offering the appropriate products, resulting in a lot of people confuse the cloud storage, cloud storage is not stored, but the service. Like cloud, like wide area networks and the Internet, cloud storage to the user speaking, not referring to a specific device, but to a large number were composed of storage devices and servers, collection of. Cloud storage users is not using a particular storage device, but the cloud storage system using a data access service. So, strictly speaking, cloud storage is not stored, but a service. Cloud storage is the core of application integration software and storage devices, achieved through the application software storage device to the storage service changes. It is this change, all companies in the 2009 launch cloud storage products, whether hardware or software, IBM announced in October the latest cloud storage and archiving Solutions Symantec will release a cloud environment for the cluster file system. Before that, HP, EMC and NetApp also introduced their products in this regard, the data storage manufacturers have been involved in this new field. Deduplication Duplication storage industry is undoubtedly the most popular technology in recent years, and even that data deduplication is “10 years of the most important storage technology innovation.” The reason why duplication is more extensive in 2009 the development of the main reasons is its chief selling point is simple — the traditional backup technology to eliminate duplication of stored data derived from the problem, then the cost savings for the company, which happened to meet the financial demands crisis, the impact of the IT industry. 2009 date, six Company : Acronis, Barracuda, CA, CommVault, IBM, and Symantec in their backup software to increase or extend the duplication of functions. Storage virtualization Virtualization is a must to mention the concept of storage area in the same way, although there is no standard to speak of storage virtualization, various definitions are not the same, but the fundamental purpose of storage virtualization is very clear-cut: to management and application tools are easier and cheaper. In addition, compared with traditional storage systems, storage virtualization can achieve fault-tolerant pairs HSTD system performance; can be multi-port parallel technology, input and output to eliminate storage bottlenecks; using large-capacity cache, significantly improve data transmission speed. Using storage virtualization technology is more a “do heterogeneous platform data replication and migration.” In fact, both EMC’s Invista, HDS’s TagmaStore, HP’s SVSP, IBM’s SVC, or LSI’s SVM, of course, many other manufacturers similar products for data migration, heterogeneous platforms are the most basic functions.



Posted in
Tags: