devopsy.kinsta.cloud

Tag: mobile

Choosing a Mobile Test Automation Solution: What You Need to Know

Organizations today rely more and more heavily on mobile apps to drive their business. In fact, many companies are already seeing more than half of their web traffic coming in via mobile devices. In some cases, their mobile app is the only way customers interact with their products.

It’s no surprise, then, that developing, testing, and releasing quality mobile apps quickly and efficiently is a high priority for most organizations—as it should be! Fortunately, mobile development tools are evolving to meet these needs, with modern dev teams having access to better test automation than ever before.

Of course, the effectiveness of a mobile testing process is only as good as the technology behind it. This makes it even more crucial for organizations to know what factors are most important to take into account when choosing or building a robust mobile testing solution. Below, we outline some key things to consider:

Native, Hybrid, and Mobile Web Support
Modern mobile applications come in three different flavors: native, hybrid and web. Native apps are built using the vendor-provided SDKs. Hybrid apps run some or all of their functionality inside a webview embedded in a native app. Finally, mobile web apps are simply mobile-optimized website that users access through their mobile browsers. While there is a growing trend towards mobile web and hybrid applications (rather than native), to ensure maximum flexibility and impact of your QA solution, it’s important that you choose a tool that supports all three kinds of apps.

On-Demand Cloud Testing
With QA teams becoming more and more distributed, it makes sense to ensure that your mobile application testing solution includes a cloud component. Leveraging an automation cloud enables teams to use organize around a single implementation of test architecture, with devices and test result data accessible from anywhere in the world. You can spend your time worrying about your testsuite, not the cost and maintenance headaches associated with keeping up multiple home-grown device grids and architectural patterns.

Automation
When it comes to mobile testing, automation is essential. Choosing the right automation frameworks (Selenium, Appium, etc…) and test tools (languages, test runners, etc…) can be a challenge, and it’s important to think about all the factors involved in getting a solid mobile build process going, relative to the expertise your QA team possesses. What kinds of user flows will you need to automate, and can the automation tool support them? Do you want automation code mixed in with your app code or cleanly separate? Is automation support available for the languages and tools you know best? Think about building a testsuite with the same level of architectural foresight as you would building an app.

Integration with Key Support Systems
It’s also important to consider what level of integration is needed with support systems in your environment – whether it’s a test management system, a CI server, or defect tracking system. A strong solution will be able to easily integrate with all of these other systems, perhaps all the way down to the IDEs your developers are using.

Cross Platform Support
With the majority of applications being developed for iOS and Android, it’s a minimum requirement for your mobile application testing solution to support automation on both platforms. Of course, this will no doubt expand as you consider other devices and operating systems such as Windows, FirefoxOS, etc…, based on your customer base.

Scalability
As the number of device types and operating systems being tested increases, it becomes increasingly important that your test architecture is able to scale automatically based on the number of tests you want to run and the amount of time you want your build to take. Building your automation on a framework like the open source Appium project is a good architectural investment; Appium’s client/server architecture makes it easy to build a testsuite than can automatically utilize a cloud service as your need for more emulators, simulators, and real devices grows.

The proliferation of web and mobile applications across a myriad of devices and operating systems is fueling a demand for faster and faster delivery of software experiences, without any sacrifice of quality. Today’s leading software companies know that successful apps are built on the foundation of their mobile application testing processes and tools. By keeping in mind the key features mentioned above, organizations can work towards building and identifying the best testing solution for them. The QA process should be a breeze, rather than a hassle.

About the Author/Jonathan Lipps

Jonathan Lipps serves as the director of ecosystem and integrations at Sauce Labs, where he leads a team of developers to ensure that the open source ecosystem surrounding the company’s core products is always maintained. He is a frequent speaker on automated web and mobile app testing, and holds advanced degrees in Linguistics and Philosophy. Reach Jonathan on twitter.

June 23, 2015
I Like Your Backend

Back in the early 80’s, dumb terminal networks ruled enterprise IT. Mammoth mainframe IT infrastructures worked as centralized corporate computing platforms feeding a vast nexus of thin clients performing mundane IT operations as intended. Perhaps that was all what end-users longed for.

(more…)

November 5, 2014
Electric Cloud’s ship.io tackles mobile continuous delivery

As increasingly more organizations run into unique challenges around extending the continuous delivery development model to mobile applications, vendors are coming out of the woodwork to start helping organizations revamp their mobile build and test infrastructures accordingly. This week, Electric Cloud tossed its hat into the ring with the beta release of ship.io, a new SaaS service that it’s launching to help users build, test and deploy native iOS and Android apps.

In spite of the fast-paced demands of the mobile marketplace, according to studies from Forrester, 64 percent of organizations release mobile apps four or fewer times per year per device. Many organizations struggle with the fragmented nature of the mobile device and operating system landscape, which can make testing a nightmare.

“Testing typically needs to cover hundreds of different devices operating across multiple mobile platforms, including mobile devices that are no longer being sold or even supported but that are stil used in the marketplace,” writes Mark Buenen, an expert in managed testing services for consulting firm Capgemini.

As a result, mobile testing lags significantly, with stats out from Capgemini stating that only approximately 55 percent of organizations test their mobile apps.
At the same time, commercial app store demands for testing prior to release raises the stakes even higher for testing, as a buggy release could take days to fix due to the time it takes for app store approval. In just those few short days, negative reviews about the bugs could scuttle the app’s future success. And within the enterprise, mobile apps are gaining importance as mobile applications gain a higher profile within core business processes.

“Mobile app development is increasingly important to a growing range of organizations, and it represents a challenge due to the range of operating systems and devices that each application must support,” said Steve Brodie, CEO for Electric Cloud.

Ship.io automatically detects and configures iOS and Android dev projects to simplify the process of creating code across multiple operating systems, versions and device screen densities. Made possible by the acquisition of intellectual property from AngelPad-backed Cisimple, an early start-up in the mobile continuous delivery space, the service is powered by integrations with GitHub, BitBucket and other Git repositories. Similarly, ship.io centralizes the automation of testing and distribution through integrations with AppThwack, HockeyApp and TestFlight. These capabilities are all condensed into a centralized management platform meant to offer a dashboard into build and test status levels across all apps and development platforms.

The ship.io release is a logical extension of services for Electric Cloud, which already focusing on automating processes for continuous delivery within the enterprise. Last week the company released a new version of its ElectricFlow Deploy product, which now, among other features, automatically detects the differences between what’s about to be deployed and what is already in an environment so that only the changed code is deployed in order to reduce risk and deployment time.

While products like ship.io could stand to make DevOps teams more effective in bringing continuous delivery to their development and deployment of mobile applications, process will still play a huge role. According to Capgemini, in its annual World Quality Report focusing on testing trends, its study showed there was a marked shift in worry about mobile testing challenges from previously lacking tools to do a good job to now lacking appropriate testing processes and methods, which 56 percent of organizations stated as a stumbling block. Similarly, lack of mobile testing expertise was named by 48 percent of organizations as one of the biggest challenges.

October 13, 2014
Technology’s effect on religion

Today being Good Friday, with Easter being Sunday and in the midst of Passover; it is a time for reflection. Instead of thinking about DevOps, today I ponder life and religion. What comes to mind is the future of religion in these technological times. The number of Americans with a religious affiliation continues to decline, less and less of us make an appearance at a Synagogue, Church or any house of worship for that matter. In my childhood we would at the very least make an appearance a few holidays a year, notably at the annual pancake breakfast.

From the calculator to the computer, from mobile devices and the Internet, advances in technology are creating monumental changes in our lives and in turn the way religion is practiced. The universal acceptance of mobile devices, like the iPhone and iPad, is provoking a profound social change. The dependence on these devices is eliminating the individuals need for traditional religion and going to traditional houses of worship. The problem is, without the traditional religious brick and mortar upbringing, the youth of today forgo a key element of the religious experience. Religion was never just about a supreme being, the social gathering and interaction of those with similar beliefs and values is also a critical part of the experience. Religion is losing the youth.

It seems there are now thousands of apps which allow parishioners to bring Bible quotes, Torah-chanting practice and Buddhist prayer wheels anywhere, anytime day or night. My concern is how many of our youth are downloading religious apps as opposed to angry birds. The challenge is how to mobilize religion while still achieving all the religious personal support and socialization benefits that are realized from real life interaction in attending a place of worship. Is the virtual congregation a realistic way to gather people and practice religion? I have a hard time thinking the young will embrace religion without the real life experience which creates the feeling of being at peace with oneself.

The virtual congregation will be effective fill in for those who have already experienced religion in the traditional sense. Worshippers who cannot find their way to their house of worship for services will pray online with their fellow believers via the latest technology, confident that the other worshipers are doing the same on their devices. How powerful that will be is the question, it has been relatively effective via Television. But those are already followers seeking religious celebrities, not new believers.

There is no denying religious leaders who conduct services via technology to a geographically wide spread audience will notice a significant difference in how worshippers experience the event. Religion is very much an emotional event and technology can be a non starter for the holy rollers. Gathering around technology in smaller groups may be an answer.

The religious apathy of the young produces a serious problem for religious leaders looking to grow shrinking congregations. The lack of formal religious upbringing has lost many of the young and younger worshippers that do exist expect any religious event to embrace technology use. Device multitasking has become such a pervasive part of their life that quiet, hard cover book based religious ceremonies seem awkward and therefore not compelling.

Technology may represent the end of traditional religious worship, and the beginning of a new age of worship, the form of which no one can reasonably predict or control. The bottom line is if you look at technology and say how does this change people going to house of worship? You miss the point, because religion is a much deeper set of beliefs. The question is without new young followers, what does the future hold for organized religions?

If you would like say something; email parker@devops.com and don’t forget to comment here.

April 18, 2014
DevOps Needs a Tsunami To Jump The Chasm

All start up business endeavors must go through the phase of crossing the chasm. Most of those business endeavors usually fall prey to the chasm. The chasm is this black hole that everyone claims to understand but no one truly does. We have all seen businesses cross the chasm or fail to cross the chasm and fall into the black hole. But no one seems to understand why and how that crossing happens. The bestselling book by Geoffrey A. Moore titled “Crossing the Chasm,” is all about the heart and soul required to get early stage technology across the chasm, from early adopters to mainstream customers.

There is a big difference between people who are enthusiastic to try leading edge technologies and the rest of the inhabitants, who tend to be much more conservative. The reasons that people spend time trying to figure out how to cross or jump, if you will, the chasm is because that black hole is what stands between them and making their fortune. The early adopters are just a small sample of the market and there is no money in building a business or technology around them. To make real money, you need to cross over into the mainstream.

In Geoff’s model, the innovators are all about technology. You know those people, when a new iphone is released, they spend days standing on line to get latest and greatest new technology. The early adopters are the visionaries that are always on the bleeding edge. The mainstream are the pragmatists, the people who practice risk avoidance. These pragmatists are the key to jumping the black hole, they move the needle.

DevOps first order of business was getting on the curve and to that end DevOps has evangelists. But, understand that what worked in converting these early adopters probably won’t work for the pragmatists. These DevOps evangelists and visionaries want DevOps power tools, as opposed to the pragmatists who simply want to push the button and say “that was easy”.

By all appearances DevOps has been accepted by the early adoption set. Just how does DevOps cross the chasm? Jumping the black hole after all can be quite a daunting task. To do so DevOps has to create what I refer to as the tsunami effect.

The Tsunami effect is where DevOps gains acceptance in multiple industries or markets in what seems like a gold rush, it’s here that fortunes are made. More accurately, it’s where cult communities transform overnight into mainstream communities. Many technologies simply create a single tornado which remains in a silo forever never gaining enough momentum to really emerge. Another common path what I call an earthquake, there is a lot of hype but it tends to fizzle out quickly, if not tended to properly. Right now DevOps has all the appearances of an earthquake, Devops evangelists have created a lot of buzz, but acceptance beyond a set of power tools is still a huge question.

Considering DevOps is in the earthquake phase, as opposed to the tornado phase, DevOps cannot be successful converting one group at a time. The strategy in the tornado phase is convert industries and markets one at a time, via tornados forming within industries or markets. The tactical execution is to get smaller industries or markets committed and therefore the larger industries or markets will then embrace the movement. That is simply crossing the chasm. DevOps has too many cultural implications to convert believers over a long period of time; DevOps requires reorganization, not a subtle shift.

Since I consider DevOps to be in the earthquake phase, crossing the chasm is not an option. DevOps must jump the chasm in a surge of overwhelming momentum, hence creating a tsunami. DevOps has created a very closely knit culture, DevOps needs to push hard to create a tsunami and flood the pragmatic population. But, be advised, DevOps has to be all but universally accepted, there is no almost in bringing together Dev and Ops. But if DevOps wins, it wins big, DevOps will go from being a niche culture to a truly mainstream practice.

So what’s the strategy to create a tsunami? And more importantly, how do you move beyond the earthquake phase? Here’s how I see it according to Geoff, with my DevOps spin: First, DevOps must clearly establish that the mission-critical software development process is broken and is causing management enough pain that it would gamble on unproven methodology that is populated with a bunch of prima donnas. I am not convinced the DevOps cult has clearly established this as fact. Is the development and operations process broken or have just new power tools been created to improve speed and accuracy? Second, DevOps needs to present the total solution, not just tools. Overwhelm the community; each new DevOps tool should leverage the success and technology of the last hence creating a methodology. Even more importantly, because the DevOps tools are closely related, credibility can cross industries and markets and create the momentum required for a tsunami. Once Devops has reached critical mass by providing the total solution in a few industries or markets simultaneously the tsunami is created and DevOps has jumped the chasm.

The tsunami will emerge suddenly with everyone seeming to adopt DevOps all at once. This will result in explosive growth and will pull, willingly or unwillingly, everyone into its path. It’s driven and sustained by the pragmatists. Here, everybody has to get the latest thing all at once; the masses have been converted to DevOps. DevOps needs mass-market success, DevOps needs to become a tsunami and everyone will want to play DevOps.

Now that you know the formula, go forward and create the perfect storm.

If you would like to say something; email parker@devops.com and don’t forget to comment here.

April 10, 2014
A Winning DevOps Approach for Established Enterprises: Pace-layered
Does your bank offer the ability to deposit a check by taking its picture with your smartphone? When that feature debuted a few years back, I remember thinking it was interesting and convenient enough that if my bank didn’t offer it soon, I’d be willing to switch to one that did.

I bring this example up for two reasons: one, it’s a microcosm of the larger race to innovation that is happening in every company and industry as we speak; and two, it involves banks, which are good touch-points for a discussion about the unique challenges established enterprises face as they attempt to implement DevOps practices in their IT organizations.

We know that DevOps means incorporating best-practice application delivery methods that improve communication, integration and collaboration between development and operations, but what is its ultimate goal? Quite simply, getting high-quality services to market faster than competitors – at a cost that aligns with both IT budgets and business goals. And as my check-depositing story illustrates, if you’re not first in the market, you at least need to be nimble enough to catch up, or you risk losing customers.

For long-time enterprises, this can be easier said than done. In my previous blog about DevOps culture, I used Etsy as an example of an organization that has had great success with its DevOps transformation, but the e-commerce company has been around for less than a decade. Its young IT architecture is apples to the oranges of established enterprises, whose complex environments often comprise a mix of legacy and modern technologies that have been cobbled together over time.

As a result, the DevOps journey is typically longer and more difficult for such organizations – but that doesn’t mean they can afford not to pursue it.

Improving Deployment Practices at Every Infrastructure Layer

When you look at the IT infrastructure of an established enterprise, you normally find three layers of technology. Let’s call the first “systems of record.” These are the legacy transactional systems (often mainframes) that have been with a company since the beginning. They do their jobs well, but their size and inflexibility make them resistant to the type of Agile development that DevOps typically embraces.

The next layer is “systems of differentiation,” or the various hardware, software and middleware components an organization accumulates as it grows, merges with/acquires companies and enters new markets. While these systems are often more Agile-ready than the systems of record, their decoupled/distributed nature can complicate and slow down development and deployment processes.

Finally, there is the “systems of innovation” layer, which is made up of mobile and Web applications and leverages the latest technologies. Because of its light footprint and flexibility, this layer is the most adaptable to DevOps practices. In fact, as you move up the layers from systems of record to systems of innovation, the holy grail of high-quality, fast and low-cost deployment becomes more and more attainable.

What does this mean from a macro perspective? Basically that established enterprises need to take a pace-layered approach, where application delivery occurs at different paces within the different areas of their architectures. The point, though, is to improve in each layer.

So if an organization pushes out a mainframe update once per year, perhaps it can move to a bi-annual schedule (with support from the right people, processes and technology, of course). On the other hand, a Web team that publishes updates once or twice a week could leverage DevOps tactics and technologies to adopt a daily update cadence. Bottom line: Different deployment paces are fine across layers, as long as improvements are occurring across the board.

Kick-starting the Journey with Service Virtualization

Now that we know why the DevOps journey can be difficult for established enterprises, let’s look at how one such organization, namely Union Bank, overcame these challenges and achieved success.

According to an article on Bank Systems & Technology, Union Bank was looking for ways to compete with top-tier banks, so it began “acquiring other institutions, updating legacy systems and launching new front-end applications.” In order to support these efforts, the bank implemented a service virtualization solution, which simulates constrained or unavailable systems across the software development lifecycle (SDLC). This allowed its developers, testers and performance teams to work in parallel for faster delivery and higher application quality and reliability.

Here are some of the results Union Bank has achieved since:
- Cut testing environment setup time from 42 days to 3 days
- Slashed three and a half months from mobile and Web application development time
- Reduced the cost of testing cycles by 65 to 85 percent
Obviously, a service virtualization solution is only one piece of the DevOps puzzle, but Union Bank stands as a powerful example of how a long-standing enterprise can leverage such a tool to be more innovative and nimble in the marketplace.
April 9, 2014
VictorOps Joins Rackspace Marketplace; Offers Collaborative Alert Management Platform for DevOps

Significantly Decreases Time To Resolution for Incidents to Reduce Costs For Customers

BOULDER, Colo., March 19, 2014 /PRNewswire/ — VictorOps, a collaboration and incident management platform designed for DevOps teams, today announced that it has joined the Marketplace for Rackspace® Hosting, RAX +0.03% , the open cloud company. As part of the Marketplace, VictorOps will offer a solution for Rackspace customers that gives them constant situational awareness of their application performance allowing for smarter, real-time collaboration around problems.

The VictorOps platform allows DevOps to define on-call schedules that notify team members of infrastructure and service delivery platform problems as they occur according to company, team and personal escalation policies. Team members are alerted via VictorOps’ native Android and iOS applications or by SMS, email or phone call.

“As long-term Rackspace customers, and as a DevOps driven organization, we’re excited to see tools like VictorOps in the Rackspace Marketplace,” said Nick Stielau, Director of Operations for Pantheon. Stielau is focused on architecting and selecting solutions that support his DevOps team members. “Without innovative, team-centric tools like VictorOps, creating an aligned development organization is an uphill battle,” he continued.

Team members can post ideas and trouble shoot problems in real-time while having unprecedented access to the data they need to solve the problem regardless of physical location or time-of-day. Teams that can share situational data easily, inject thoughts and comments, and leverage team members who are not physically present is key to reducing the time-to-resolution for the company and a better lifestyle for the team as a whole.

“The power of a collaborative solution for real-time problem solving is in its ability to leverage the entire team’s knowledge in a scalable way through all phases of the incident lifecycle,” said Todd Vernon, CEO and co-founder, VictorOps. “Bringing our collaboration platform to the Marketplace enables Rackspace customers to purchase a solution with new ways to solve problems in a smarter way, which can help solve the same or similar problems faster the next time they occur. This reduces overall costs for a business.”

“As early adopters of DevOps, we see VictorOps as a natural fit for the Marketplace,” said John Engates, chief technology officer, Rackspace. “We share their desire to enable DevOps teams to do their jobs more effectively and believe that the addition of VictorOps will add great value to the Marketplace.”

For additional information about VictorOps and Rackspace Marketplace, visit: try.victorops.com/rackspace.

About VictorOps VictorOps is the world’s first collaborative alert management platform designed for DevOps teams that combines the power of people and data to solve IT problems in real-time. The VictorOps platform seamlessly orchestrates team situational awareness, incident creation, escalation, notification, and remediation with team members regardless of physical location or time of day. Privately held, VictorOps is backed by Costanoa Venture Capital and Foundry Group. For more information, visithttp://www.victorops.com and follow the company on Twitter @GoVictorOps.

SOURCE VictorOps

Copyright (C) 2014 PR Newswire. All rights reserved

March 19, 2014
Always-on: The New Normal

One of the many challenges of DevOps is finding great team members that can handle the always-on nature of the job. Nearly everyone at VictorOps has been “that person” and has done the weeklong stint of carrying the virtual pager.

What we noticed in our years of doing that job is that team member behavior tends to be polarized. If it’s your week to be on-call, then you are “all in”. You don’t venture far from home, you can’t attend special events and you have to apologize to your significant other a lot. When you are not on-call, you tend to unplug from the company. These are normal behaviors and completely understandable given the difficulty of the job.

The problem is that this on-call way of life is not conducive to actually fixing problems faster. In a perfect, company-centric world, everyone would get paged for every problem with the logic being that one of the team members actually has the information needed to solve the problem. But that’s not going to happen. And unfortunately, the truth of the situation is that you’re not sure who that one person with the correct knowledge to solve the problem will be.

The question then arises…how can team members have more knowledge about what is going on with the complex systems in their architectures while also maintaining their quality of life?

Consider Twitter and Facebook user behavior. I have a cousin that lives in Chicago. I have seen her in-person once in the last 30 years, yet I know she remodeled her living room, I know about her work and I know where she took her last vacation. I know these things because the Twitter and Facebook experiences leverage something called Continuous Partial Attention, a term coined by Linda Stone in 1998. Basically, I pull my phone out of my pocket, swipe once, and gain a disproportionate amount of information for the effort (or conscience thought) I put into it.

If you’re in DevOps, then the idea of Continuous Partial Attention is something you’re already living daily. Now imagine putting CPA to work for your team. Everyone can have an eye on the infrastructure, but not “feel like it”. The on-call team member is still responsible but if everyone has an idea of what is happening, the likelihood of someone knowing the answer is revealed sooner. Now everyone wins because the problem is solved faster, getting the team back to their lives and the company back to revenue generation.

March 13, 2014
VictorOps Announces Integrations at All Levels of the Technology Stack
New Integrations Open Up Previously Hidden Information to DevOps and Reduce Time to Incident Resolution

PR Newswire

BOULDER, Colo., March 5, 2014
BOULDER, Colo., March 5, 2014 /PRNewswire/ — VictorOps, a collaboration and incident management platform designed for DevOps teams, today announced new integrations that span all levels of the technology stack. With the addition of New Relic, SalesForce, Sensu and Zabbix to the list of integration partners, VictorOps is expanding the amount of relevant information available to DevOps as a way to help them make better-informed decisions which leads to reduced time-to-resolution.

VictorOps has selected these integration partners as a result of user requests. New Relic, in particular, was an important addition because such a large percentage of VictorOps user base utilizes the offering.

With these additions, the current VictorOps integration list includes:
- Technical Support: SalesForce, UserVoice
- Application Layer: Pingdom, New Relic
- Core Infrastructure: Nagios/Icinga, Zabbix, Sensu, Amazon CloudWatch
“The modern DevOps culture revolves around technical teams being more integrated into the business as a whole,” said Todd Vernon, CEO and co-founder, VictorOps. “That is why we are looking to add integrations higher up in the stack – to surface and share typically unavailable information with DevOps as a way to decrease time to incident resolution and ultimately reduce costs for businesses. Integrating with New Relic and Salesforce are great examples of this effort.”

VictorOps will continue to add first-class integrations based on user feedback and an ongoing review of industry leaders at all levels of the technology stack.

About VictorOps
VictorOps is the world’s first collaborative platform designed for DevOps teams that combines the power of people and data to solve IT problems in real-time. The VictorOps platform seamlessly orchestrates team situational awareness, incident creation, escalation, notification, and remediation with team members regardless of physical location or time of day. Privately held, VictorOps is backed by Costanoa Venture Capital and Foundry Group. For more information, visit http://www.victorops.com and follow the company on Twitter @GoVictorOps.

SOURCE VictorOps
March 5, 2014
CA Technologies Launches Industry’s First Management Cloud for Mobility
Solutions to Secure the Mobile Enterprise and Accelerate Innovation to Capture Growth in the Global Mobile Economy
February 24, 2014 09:00 AM Eastern Standard Time

Mobile World Congress 2014
BARCELONA, Spain–(BUSINESS WIRE)–MOBILE WORLD CONGRESS– Today at Mobile World Congress, CA Technologies (NASDAQ:CA) launched the industry’s first, comprehensive Management Cloud for Mobility. Delivered as a cloud service, this portfolio enables enterprises to manage, secure and grow their business, increase productivity and deliver an enhanced mobile experience.

“The growth of mobile devices and apps in the enterprise is blurring the lines between personal and corporate data and leading to new challenges for enterprises”

“The explosion of new devices, applications, content and transactions in the mobile environment has opened new challenges for enterprises of all sizes, worldwide. The CA Management Cloud for Mobility will help enterprises transform the challenges of the new mobile economy into significant opportunity,” said Ram Varadarajan, general manager, New Business Innovation, CA Technologies. “With solutions that power innovation, drive productivity and accelerate the development of new mobile applications and offerings, CA is extending its leadership in IT management to help businesses capitalize on the next technological and business shift – mobility.”

The portfolio includes three complementary solution suites: Enterprise Mobility Management (EMM) to manage and secure mobile devices, applications and content; Mobile DevOps to accelerate application development and deployment; andEnterprise Internet of Things (IoT) to enable the adoption of internet-connected devices. The complete EMM suite and key products of the Mobile DevOps suite are available for purchase. Customers have the choice and flexibility to deploy the complete portfolio of solutions or individual components, with the ability to customize and scale cost effectively.

This CA Management Cloud for Mobility is powered by Smart Containerization™ technology. Unlike traditional device-focused mobility management techniques, Smart Containerization™ allows enterprises to manage the security, performance, compliance and support characteristics of the device, application, content or email while preserving the quality of the mobile user experience.

“The growth of mobile devices and apps in the enterprise is blurring the lines between personal and corporate data and leading to new challenges for enterprises,” said Chris Hazelton, Research Director, Mobile & Wireless, 451 Research. “The EMM space is evolving as companies are looking for more complete offerings that support customers and productive mobile employees. Secure container technologies must provide enterprise scalability and comprehensive security across app development, delivery and support, all while preserving the familiar native look and feel of nearly any mobile device an employee chooses to carry.”

Enable Enterprise Mobility Management

The EMM suite enables enterprises to drive employee productivity and satisfaction by simplifying the management and security of devices, applications, content and email.

The four products within the EMM suite available for purchase are:

New CA Mobile Application Management (CA MAM): Provides security, management and control of mobile applications with fine-grained access control polices for mobile applications.

New CA Mobile Content Management (CA MCM): Enables secure content access and collaboration through file synchronization, access to enterprise content repositories and cloud store integration made available to the end user through policy-based mobile access.

New CA Mobile Email Management (CA MEM): Provides users with secure access to their corporate email and ensures group and policy-based controls to protect sensitive email content.

CA Mobile Device Management (CA MDM): Delivers comprehensive capabilities to provision, secure and manage mobile devices, and deploy mobile applications automatically or through an enterprise app store.

Accelerate Mobile Application Delivery

The Mobile DevOps suite helps enterprises accelerate the delivery of user-experience-focused mobile applications. It enables enterprises to achieve faster time to market by accelerating continuous application delivery while enhancing security. Working across multiple development tools, languages and methodologies, Mobile DevOps makes it easy to build and test rich API-based mobile applications, gain deep insights into performance, user experience, crash and log analytics, and automate and support these mobile applications when deployed onto millions of devices.

The four products within the Mobile DevOps suite available for purchase are:

New CA Layer 7 API Portal: Simplifies publishing APIs, onboarding developers, and streamlines enterprises’ ability to rapidly develop applications based on these APIs.

New CA Layer 7 Mobile Access Gateway: Delivers unified access across web and mobile, authenticates users based on risk levels and protects the datacenter against rogue applications.

CA LISA Test for Mobile: Offers mobile and web developers global access to a comprehensive platform that simulates an exhaustive list of user scenarios for testing.

CA LISA Service Virtualization: Allows customers to test new mobile applications in simulated environments.

Additional Mobile DevOps capabilities will be available in the next few months, including mobile APM, crash and log analytics, user experience analytics and remote application support.

According to a Forrester Research report, “Development shops are just starting to grapple with the biggest change to system architecture since the rise of client/server in the early 1990s: omnichannel clients deployed on smartphones, tablets, and other connected devices. The mobilefirst focus these organizations adopt, forces application architects to think differently about the APIs clients use to access data and functionality.”*

Manage and Grow in the Ubiquitously-Connected Tomorrow

Enterprise IoT will enable businesses to deploy internet-connected devices, and manage and secure billions of Machine-to-Machine (M2M) interactions. Ubiquitous connectivity, advancements in big data analytics and the ability to embed computing into everything have led to the rise of the IoT phenomenon. The Enterprise IoT suite will provide enterprises a secure foundation to extend mobility with IoT infrastructure to achieve business efficiencies.

These Mobility offerings from CA are further supported by significant advances in the CA Security portfolio. These include new and updated identity-based solutions that help customers secure their growing portfolio of cloud services and mobile applications.

For more information on the various solutions supporting mobility from CA Technologies, please visit: http://www.ca.com/us/mobility.aspx.

*The Forrester Wave™: API Management Platforms, Q1 2013, Forrester Research, Inc., February 5, 2013.

About CA Technologies

CA Technologies (NASDAQ: CA) provides IT management solutions that help customers manage and secure complex IT environments to support agile business services. Organizations leverage CA Technologies software and SaaS solutions to accelerate innovation, transform infrastructure and secure data and identities, from the data center to the cloud. Learn more about CA Technologies at www.ca.com.

Follow CA Technologies

Twitter

Social Media Page

Press Releases

Legal Notices

Copyright © 2014 CA. All Rights Reserved. One CA Plaza, Islandia, N.Y. 11749. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
February 24, 2014