Skip navigation
Twitter   Follow us  •   Share   Share    Become a member

Smart Architect

3 Posts tagged with the mobile tag
0

Consumers flock to app stores to load their devices up with the latest games, social media and other apps. Now, these same consumers are bringing their insatiable thirst for mobile apps into the workplace.

 

Companies are responding to the disruption with their own take on the Apple innovation that changed the mobile world as we know it: Giants such as Pepsi are erecting their own internal app stores to quench employees’ desire for mobile business apps in a sane, safe and secure fashion. They’re intent on stopping the trend of employees and business units adopting whatever apps they want from wherever they want them, without IT supervision. In a recent IDC white paper, sponsored by CA Technologies, the research firm found that adoption of of public cloud, social and mobile technologies in business operations “has already reached high levels, often driven by “stealth IT” (i.e., by business units or individuals without corporate IT’s knowledge or support).”

 

Managed Security, Provisioning, Usage

The enterprise app store is a centrally managed repository of software that’s either been custom-developed, bought from a third party, or acquired under a volume license agreement through a commercial app store such as Apple’s. From this central repository, the enterprise can not only adopt the apps it wants, but it can also blacklist those it doesn’t. And, the enterprise can define who gets access to what. Based on those rules, IT can implement app security policies and automatically provision and deprovision apps as employees join and leave the company, thus preventing a former worker from accessing proprietary corporate information.

 

Many of these new app security tools will let the enterprise track application usage and performance, too. Software version management is another important feature, ensuring that employees use the latest approved version on their mobile devices. And, from the store repository, IT also can manage software licenses, renewals and compliance with vendor agreements.

 

A growing number of vendors offer enterprise app stores as part of their mobile device management and application development platforms.

 

And here’s where the enterprise architect can get in front of the mobile app trend and play a key leadership role: The architect can help identify the solution that’s best for his or her company and that works well within the existing enterprise architecture. Mobile app stores can be implemented as software that resides inside the firewall, as a service within a cloud architecture, or as a subscription-based service offered by carriers such as Verizon and AT&T.

 

If you’re an enterprise architect at an organization that’s moving aggressively toward Software as a Service (SaaS), the cloud approach is best. (By the way, have a look at this article to learn more about the trend to “everything as a service,” or XaaS, changes the IT management landscape in a big way.) If you serve in an enterprise architect’s role at a bank, where there’s hyperconcern about security and data protection, an internal software implementation is the way to go.

 

The Enterprise Architect Behind the App Store Scene

 

Enterprise app stores address the following areas of app security, and as part of the job of recommending the appropriate framework, the EA should assess how well various offerings address each piece:

 

  • App quality — includes preventing the distribution of malware via mobile apps
  • Information access — includes determining who has access to data from mobile apps
  • App distribution — involves how to get apps on devices and control employee access rights
  • Information at rest — affects how to determine which data should reside on the mobile device
  • Data wipe — deals with removing data from mobile devices if it’s not needed or poses a security risk

 

In addition to identifying the best app store solution for his or her company, the enterprise architect should outline some best practices and standards that apply consistently across all the apps that will reside in the app store. For example, will the app store group applications around enterprise function, such as ERP or CRM? Or does it make more sense to organize apps by department, geography or job function? Either approach helps with the information-access issue, of course.

 

It’s important for the architect to be proactive and establish a common “world view” of mobile app security and management for the company, which includes getting key stakeholders on board early in the process. So, how’s your mobile app store coming along? Or are you exploring other innovative ways to secure mobile app and information access? Let us know below.

0

A few weeks back I wrote about the benefits — and challenges — of a federated architecture. In that blog I wrote that such an approach helps the enterprise architect organize the efforts of disparate groups to avoid duplicate software project silos, but also that the approach won’t get far without buy-in and cooperation from business users, data owners and various other stakeholders. (For a more detailed refresher, see the original post here).

 

I mentioned there that I’d be following up the post with another to discuss a project I’ve been involved in to tie disparate financial systems into a federated portal, which included taking mobility into consideration early in the design process.  I know you’ve been waiting for it, so sit back and enjoy as I delve into the how of architecting that federated effort! I hope my experience will help prepare you for issues that may arise with federated systems in your own enterprise, regarding security, deployment coordination and user interfaces, which is where we’ll start.

 

Dressing for Success

 

The enterprise architect’s first challenge will be getting agreement on a unified presentation strategy. Without standardizing on a single presentation technology, you risk a user interface (UI) that looks disorganized and disjointed. Equally bad, you lose the ability to share design patterns and code across software projects, and developers remain in silos, jeopardizing the agility that can occur when they are free to share their talent with, or even move to, other development groups to create added value. Technical problems, such as OS resource competition and varying data refresh rates, are bound to arise as well.

 

The Web-based portal I’ve been focused on building is for a set of applications — involving multiple development groups — in the banking space. Being Web-based, HTML makes up most of the UI. But because the portal is to be a rich Internet application, we had to get agreement on which more complex UI elements we would leverage for displaying dynamic data (financial market data in this case). Ajax, Silverlight or Flash technologies were in the mix, but trying to combine them all adds up to a sloppy presentation. As the enterprise architect on the case, it was important to listen to the arguments on all counts, and in addition mobility features had to figure heavily into the final verdict. Flash is a good cross-platform, cross-browser choice for dynamic UI development, but even better, it’s turned out to be a real star in the world of mobile devices.


Just Log In

 

Another area of focus in federated architecture is user authentication. It’s absolutely necessary to build a single sign-on (SSO) solution—not necessarily one based on SAML (Security Assertion Markup Language), but one that’s web-proxy friendly—that unifies the login process for your internal applications. But it’s just as important to enable access from external domains, such as those of your customers and business partners, seamlessly and without sacrificing security.

 

Solutions such as those in CA’s Identity and Access Management suite, provide capabilities that can work in your enterprise, across the Web, and even extend to the cloud. A single sign-on product, such as CA SiteMinder®, is specifically built to solve this problem, as shown in Figure 1. 

 

ca.jpg

Figure 1 - How Single Sign-on Works (Illustration credit: CA SiteMinder Product Brief)

 

Here’s how it works:

  1. The user accesses a protected resource.
  2. The user is challenged for credentials, which are passed to a secure SSO agent, such CA SiteMinder.
  3. After passing through another layer of network security, the credentials are passed to a policy server.
  4. The policy server securely authenticates the user against the correct data store.
  5. Entitlements are passed back to the policy server where access is granted.
  6. The user’s profile data is passed to the appropriate application(s).
  7. Appropriate application content is provided to the authenticated user.

 

Remember, in a federated solution, all of your organization’s secure applications need to be unified within a single SSO solution, and all of your user authentication must be accessible within a single set of data stores. 


Deployment Demands

 

Another critical task facing the enterprise architect who drives a Web-based federated effort that runs well on mobile devices is the deployment and administration of services within the cloud. In my case, this involved a private cloud.

 

The main goals were to enable lifecycle and operational independence. The first mistake of some of the groups participating in the effort was that they placed their enterprise software components into the cloud as one large component. This quickly led to problems in the areas of scalability and ease of deployment.

 

As a result, I began an effort to break down all software components into sets of basic services with discrete tasks. We designed a way to easily deploy and dynamically execute these services across servers, both physical and virtual, according to a core set of capabilities and prerequisites. For example, information such as average transaction time, network bandwidth needs, dependencies on other services, and external resources and storage needs all are factors in deciding how many instances of each service are started, and where they’re located.

 

That’s why the system now can manage itself to a degree. However, administrators still can control individual services, migrate them across servers if problems arise, and roll out individual service updates without interrupting the entire federated system. In the end, the entire system and process is more agile, with limited dependency on specific developers’ expertise, or custom frameworks that duplicate deployment and administrative tasks. In summary, less human interaction equates to more efficiency, and reduced duplication equates to reduced costs and greater shared value.

 

Looking Ahead

 

If you’re interested in moving your enterprise toward a federated architecture, you must understand that you’ll need to constantly engage in forward-thinking and proactive planning, since unification efforts take a great deal of time and need to be flexible. That’s especially true as new development groups come on board and various databases need to be consolidated.

 

But as most enterprise architects learn early on, a good architecture is never complete. It just continues to evolve over time. We’d love to hear about any of your own evolutionary experiences as an architect.

0

What’s the future of enterprise architecture management? Detecon Consulting, an information and communications management consultancy headquartered in Bonn, Germany, expects to soon publish new research that explores this topic from the perspective both of businesses and the vendors that supply them with enterprise architecture (EA) tools. With some exceptions, both parties are predicting the same outcome: While EA is currently viewed in many organizations in terms of technology-operational or technology-strategic issues, that isn’t a sustainable model. Enterprise architecture’s future is to manage the whole enterprise, not just IT.

 

“What I have seen, not only in our study but in discussions with other customers and industry partners,” is the need for a “strategy to expand and extend their function into the business,” says Marcel Berneaud, Managing Consultant, Team Head EA Transformation, at Detecon. This expanded concept of EA is playing out in the implementation of roles such as demand manager or business architect, for example, to create better alignment between the business and IT. “The demand from the business side is that EA management should help them in a more business-strategic way, not just in a technical way.”

 

Phasing-in the Changes

But many wonder whether senior executives will embrace a broadened view of EA possibilities that will make it possible for architects to deliver strategic business management, and where might they draw some lines. For instance, many organizations need to encourage more skills development so the staff can apply EA frameworks to managing the extended enterprise rather than just the information systems. And perhaps there’s a need for bigger budgets to develop these skills, too, leading to some fears that a holistic approach of EA management might be too grand a scheme. The good news, says Berneaud, is that it is possible to take a phased and sequential approach to moving EA beyond its IT borders.

 

Starting sooner rather than later makes sense when you consider trends and challenges such as globalized businesses that require the enterprise to act in totally new environments. When you think about the international environment, “with many suppliers and customers, you need to see the big picture,” explains Detecon consultant Aneta Nowobilska. “You need new methods that let you handle your processes, enable the integration and exchange of data. Enterprise architecture can support these scenarios.” 

 

The Trends for Enterprise Architecture Management and Tools study explores many other scenarios, too, although the study also cautions that disparate viewpoints need to mesh a little better when it comes to whether or how EA tools can support the extended view of the function. The Detecon team points to some vendors having more of a technical history and maintaining their focus on the IT part of EA management, while others are trying to push the envelope even when architects themselves aren’t sure of how deep to go. For example, they’ve seen that EA tool vendors are finding it important to consider business continuity because it plays into the bigger picture of corporate risk management. But the research shows that some companies don’t see EA methods as having a role in supporting business continuity. Conversely, EA stakeholders are thinking more about their role in the mobile device/universally available information world, whereas some tools vendors haven’t seen mobile support as part of their job. 

 

New Vision of EA

Detecon is hopeful that its study will accomplish a couple of things: On the one hand, it can give enterprise architects more proof for persuading management to embrace EA for business requirements without fear. That can be found in advice on choosing pilot projects and applying EA management methods to show how well they can support business strategy and contribute to IT and business alignment. For their part, tool vendors will get some insight into what their customers are thinking that could play a role in how they evolve their tools. “It’s [about] what companies want to do in the future with EA management. And, if they want to stay competitive, they’ll have to comply with that vision,” says Nowobilska.

 

When it comes to EA's role in managing the enterprise, you can see that we at Smart Architect couldn't agree more -- just have a look here, or here, or here, for starters, Feel free to weigh in with your own thoughts on EA's impact on strategic business management. 

 

 

 

 



We encourage your feedback. Reach out via the "Contact the Editor" and "Contact the Concierge" services for any needs, questions or comments. We look forward to serving you!

Paula Klein, Smart Enterprise Exchange Editor
e-mail

Ellen Lalier, Smart Enterprise Exchange Concierge
e-mail
phone 516-562-5727; fax 516-562-5466