1 2 3 34 Previous Next

SAP Cloud Computing

500 Posts

More than 65% of enterprise IT organizations will commit to hybrid cloud technologies before 2016

Source: IDC Cloud Predictions https://www.idc.com/getdoc.jsp?containerId=prUS25350114


This is one of many studies and predictions suggesting that most IT organizations will transform into a hybrid landscape in the next couple of years. Just a side note on this: IDC defines hybrid cloud as an integration of internal IT environment with private, hosted or public cloud services.


We see the same trend valid for SAP’s customer base, which has become more and more interested in adopting cloud solutions to their on-premise environments.


SAP’s customers are able to choose between on premise, cloud and hybrid deployments - a combination of both on premise and cloud. This freedom of choice allow firms to transform at their own pace following their individual business priorities and their markets, which, by the way may change at any time.


Picture1.pngA hybrid deployment has several benefits for our customers, since they can keep their highly client specific processes and the mission critical business functionalities on premise, while at the same time support other business areas, where they want to be innovative and fast, with a cloud solution. So, a hybrid deployment model allows our customers to combine the best of both worlds.


However, the transformation from an on-premise landscape to a hybrid landscape, where cloud and traditional on-premise systems are integrated seamlessly, is not always as simple as it may seem. There are certain key aspects which need to be considered on this journey, such as integration, operations and security.


Known and established principles, especially around operations and security, are still valid – but it is the expansion of the existing options, that comes with cloud, which initially increases the overall complexity. In a hybrid landscape the on-premise systems and the cloud solutions have to be orchestrated together to ensure continuous proper business support.


Questions often arise, such as “How do I get there?”, “what does the hybrid deployment model mean for my security and operations teams?” and “how can I ensure sufficient integration between the different environments?” There will not be just one “right” answer to all of these questions, since they are highly company specific.


SAP is offering an openSAP course, running over five weeks that will handle these topics and provide you with the key areas to be considered on transforming towards a hybrid landscape. The goal of this openSAP course is to give you an understanding for what running a hybrid landscape means for integration, security and operations and how you can start your own hybrid transformation journey.




What will be covered in the agenda?

The first week will give you an introduction to the topic of cloud and hybrid deployments and go through the business benefits and drivers, the different deployment options and service models, how SAP is supporting a hybrid deployment model finally go through some typical hybrid customer use cases.

In week two you will get a deep dive into the topic of integration, where we will first give you an overview of the different integration technologies and thereafter comparing them. You will see demos of several different integration scenarios and get information about the best practices of how to set it up.

Week three focuses on the very important topic of security. Many of you may wonder if your data is secure in the public cloud and in this week we will talk about what security aspects you should keep in mind to implement, in order to ensure that your data is secure in a hybrid landscape.

In week four, we will talk about operations. How do your operations change when you come from an on-premise environment and adopt cloud? What do you need to do to prepare your own organization for the transformation?

In week five, the course concludes with the transformation topic. Here we will talk about the new mindset that is necessary to adopt when consuming cloud solutions and the importance of developing a strategy for the transformation. We help you define your transformation drivers and to determine use cases for your hybrid landscape.


The openSAP courses are open to the public, so you as a customer, partner, and of course anyone working with SAP are encouraged to sign up for this course, that is free of charge. You have the chance to interact with the experts and exchange ideas and experiences with other participants in the discussion forum. I hope this openSAP course helps you to start your individual cloud transformation within your company.


Enjoy the weeks of learning, collaborating, exchanging ideas and sharing experiences! Have a great openSAP course!

                I’ve been working on SAP customer projects in cloud-like environments for the past several years. A large portion of these have been BW on HANA in the cloud. Customers will very often point the finger at HANA as the cause of performance issues after moving their BW to HANA and into the cloud, but HANA is rarely the culprit. The same questions always seem to come up, so I decided to jot down some lessons learned.


                We all know that BW by itself doesn’t do much. Referencing the famous picture below, we know that there are multiple interfaces required. We need data sources from which to get the data, whether this SAP or non-SAP sources. Some options to get the data into BW are native BW extractors, SLT or Data Services. Depending on the use case, the implementation could use one or more of these solutions. The open hub services allows the distribution of outbound data, but I don’t have much experience with this. Why would you want to send the data anywhere else if it is sitting on HANA? There must also be a way to consume the data. These can include BEX Analyzer, BEx Web or an integration with BOBJ BI using dashboards, BI Launchpad or Crystal Reports.



(graphic source: SAP documentation)



I would say 90% or more of the BW on HANA projects I have been involved in included a BOBJ BI implementation. The other common systems I see deployed are SLT and Data Services. From experience, it makes sense for some of these systems to sit in the same physical location as the BW on HANA. What can seem like HANA performance issues to the customer are more often latency issues between systems.


On to some of more interesting bits. I’ll assume HANA and the applications are sized and architected properly. We won’t discuss diagnosing HANA or application performance issues, but potential issues with network latency and bandwidth and how to manage these challenges.


I would say an SAP system could be considered a tightly coupled system. What I mean by this is that the database and application tier must sit in the same location and work in concert to ensure smooth operation. On the other hand, I would argue most SAP landscapes can be considered loosely coupled and it is ok to separate the systems by some distance. Although, there are some architecture decisions that need to be made to ensure satisfactory performance in a hybrid cloud environment. When systems are all sitting in the same location connected by a 10G network connection, latency and bandwidth is usually not a concern.


Lessons Learned w/ real world examples


Disclaimer: This is only an example. These numbers were provided during testing by the customer.  

  • SLT is used for real time replication from varying data sources. A typical use case is replicating data from an on premisis ERP, CRM or a 3rd party DB to the BW on HANA in the cloud.
  • SAP’s recommended network connection for SLT is 1Gbps. It can be expensive for a VPN or MPLS line to have so much bandwidth and it is often overkill.
  • Real world scenario of Fortune 500 company with hybrid cloud implementation; HANA, BOBJ BI and SLT in the cloud replicating from on-premisis ERP
    • Initial data load was a concern, so several iterations of testing were performed over a 100Mbps VPN
      • Before optimization, it took 14 hours to replicate ~350,000,000 records
      • After SLT optimization, 7 hours to replicate ~500,000,000
        • No substitute for well optimized SLT system
    • Initial load peaked at 40Mbps of bandwidth
    • After initial load, VPN bandwidth was throttled down to 15Mbps to sufficiently handle real time replication of ~4 records per second.
    • Sizing depends on scenario, but real world numbers are shown just as an example.
  • SLT should be near the target system
    • RFC traffic is compressed by default
      • In above scenario, network team saw a total of 23.23GBs go through VPN tunnel, but total size of all replicated tables was ~100GBs
      • Since VPN is bottleneck, we want as much compression as possible over the connection
    • The DB connection is not compressed.
    • SLT.png
  • In the event of a network failure, the replication will be retried until it completes, but will lead to longer execution times and increased resource usage



  • Customer had BEx integration with Portal, but portal stayed on premises
    • Users experienced unacceptable response time trying to display reports
    • After much troubleshooting, portal was moved to the cloud next to BW
    • Performance improved dramatically
  • BEx provides a rich web-based reporting interface, but this can come at a cost
    • Common interface from BOBJ to BW is BICS, which is XML that goes through the Java layer for Webi, Crystal, Analysis reports
    • Simple operation such as requesting a list of documents can have 90 individual HTTP requests
    • The bandwidth typically isn’t the issue, but the latency for so much back and forth communication causes delays
    • This is not an issue with low latency connections
  • BEx performance will be best if both the BW and the BOE servers are in the same location
    • This will ensure the best report refresh times
    • Will make latency between BW and BI a non-issue
  • 1733726 - Performance optimization in WAN scenarios with BICS
  • If BEX is integrated with Portal, then portal should sit next to BOBJ BI in the cloud


BOBJ Data Services

  • Every implementation that I’ve come across that had BODS in the cloud required a local WTS for BODS Designer
  • There are known issues with Data Services Designer connecting over a WAN
  • BODS development has been aware of this for several versions, but the issue still occurs as of the 1.4 client
  • Only acceptable solution is to put a WTS server with the client tools in the DC where BW and the BODS job server are located
  • May be an option to put BODS on premise, but typically best to put near BW and BOBJ BI


Example architecture


I hope this is helpful. Again, this is my experience over many implementations, but would love to hear any experiences others have had with hybrid cloud scenarios.

SAP implementation projects are highly complex projects based on long lists of functional and non-functional requirements with high organizational and IT dependencies. Such projects normally comprise the complete Enterprise Architecture layers of


1. Business processes and organizations

2. Data and information flows

3. Application architecture

4. Technology and infrastructure


Enterprises need to have a deep transparency into these layers following a complex blueprint and project plan. The project scope normally covers core and context areas of the layers. The value of Cloud contributes in the instant provisioning and inclusion of services  in context areas.


Steer up with cloud services


With the evaluation of pre-defined services customers can try and test their scope and fit instead of trusting the blueprinting only which heavily reduces risks. It also moves the evaluation phase to the beginning of the project with the requirement engineering instead of having this after initial implementation.



1. gear: Gain speed on infrastructure and technology

On the technology and infrastructure with ready to use Infrastructure as a as a service (IaaS). Enterprises gain speed by using pre-configured IaaS offerings which already include the service in provisioning and maintaining infrastructure in the exact scalable size and with pre-defined qualities (SLAs). Enterprises can rent or subscribe to these IaaS offering and do not need to purchase and setup the infrastructure themselves which reduces technology and infrastructure use by several weeks or months.


  • SAP offers with its SAP HANA Cloud Platform offering Servicer capacity and performance in different packages for monthly subscription.
  • SAP offers with its SAP HANA Enterprise Cloud a fully managed hosting offering which provides productive and non-productive SAP environments with SLAs suitable for implementation projects



2. gear: Gain speed on application layer


On the application architecture layer SAP provides with its


  • Cloud Appliance Library (CAL) pre-packaged SAP products which can be directly deployed on the SAP HANA Cloud Platform or in Amazon Web Services. Therefore enterprises do not need to setup the required solution landscape with its latest patches and upgrades themselves but receive a ready-to use core-application platform which can be configured to the specific needs. This reduces the time spend on installation by several days to weeks.
  • With its Pre-Assembly Service for Rapid Deployment Solutions  (RDS) SAP provides the ability for customers to pre-build a template and ready to use solution environment based on customers specific scope by technically harmonizing the required SAP software products and activate the necessary content packages. The template is provided as a virtual image in the SAP HANA Enterprise Cloud or it can be deployed in any defined target data center. Customers can start configuring the solution to their needs instead of installing and testing the software themselves. This cuts the technical preparation phase of implementation projects down to 25%. More information can be found on the SAP Service Marketplace (user account required)
  • With the usage of a cloud-based platform as a service (PaaS) such as the SAP HANA Cloud Platform customers can build extensions and customizations outside the standard solution with using a rich platform providing pre-coded code-elements for database and process and analytics capabilities of the underlying core system, APIs and integration adapters. This decreases the implementation time as the reuse of patterns speed up the project without the need to code and test these elements themselves.


3. gear: shift data to the lowest complexity


Using a data platform as a service (DBaaS) enterprises can use the latest capabilities of designing and maintaining data and information flows.


  • With the DBaaS offering as part of the SAP HANA Cloud Platform from customers can use subscribe to the capacity they need with using the standard integration points and maintain the business and data flows through a hosted Solution Manager. This ensures direct execution from process and data modelling to SAP systems without the need to code it. Test scenarios can directly be defined and executed using Testing tools or the SAP Solution Manager capability. This reduces the implementation time up to 50%


4.gear: Full speed with standard process usage


With the use of software as a service (SaaS) offerings like


- SAP Cloud for customers (CRM processes)

- SuccessFactors (HR processes)

- Hybris (marketing, ecommerce processes)

- Ariba (procurement, SRM processes

- Field glass (workforce management processes)

- Concur (travel and expense processes)


customers can reuse pre-defined business functionality and integrate it into their business processes instead of rebuilding the functionality. With the adoption of the given process steps it is often quicker to adjust the internal process flow instead of customizing the solution to the internal process. This saves money and time of future functional updates and extensions as backward compatibility is ensured by the vendor and need to be elaborated by the enterprise.


Get your tailored roadmap for cloud adoption within a 2 weeks consulting engagement with the Cloud Strategy and Roadmap Service. SAP supports its customer in adopting cloud to their needs with providing the right solution selection, reference architecture, business case and cloud adoption methodology.


Decision trees, capability mappings and cloud integration checklists speed up the definition of hybrid landscape between on-premise and cloud-based SAP solution and components as well as third party products. More information on the Cloud Strategy and Roadmap Service can be found on the SAP Service Marketplace (user account required).

It’s difficult to escape the discussion of cloud, on-premise, and hybrid landscapes. But what exactly do these terms mean?

Previously, all systems were on-premise which means they were hosted on servers on the customer’s site and required end users to install software on their computers to run. Cloud systems or software as a service has become a popular choice in recent times. These offerings are hosted on a providers’ server without the need to install software locally, making transactions easier and reflected in real-time. This allows users to work remotely and on mobile devices, benefit from system updates quickly and efficiently, and provides real-time information across all applications and to all users.


In order to make the transition from on-premise to cloud a smoother process, companies are opting to use hybrid landscapes as an interim solution – that meanscoursePic.PNG cloud and on-premise systems working together to transition to the cloud without disruption. Businesses and end users have many concerns about changing their system landscapes and fear of the unknown. There are common questions which focus on architectural best practices, integration options, security aspects and how to operate the new environment.


With this openSAP course, Transformation to Hybrid Landscapes, you will learn about the benefits of each landscape option to help you make informed decisions about your company’s system landscape, along with best practices and recommendations. You will learn about cloud deployment and service models along with use cases of when customers use cloud, on-premise, or hybrid models. The course will also focus on data privacy and compliance, identity and access management, and interface and network security. Join the experts in the discussion forum to raise questions you may have.


The course begins from July 2 and, as with all openSAP courses, is offered free of charge and is open to an unrestricted audience. All you need to sign up is a valid e-mail address.


Interested in SAP Business ByDesign? Check out Application Development for SAP Business ByDesign, starting June 3

To reiterate from my first blog (part-1): http://scn.sap.com/community/career-center/blog/2015/04/27/understanding-digital-transformation-in-sis-way:


By 2016 80% of the IT decisions involve LoBs:  This will be most influencing factor for all support functions run at back office to support sales and presales teams and to some extend on the individuals at the level of roles they will be playing. This change in IT decision making forces SIs solutions should be focused around individual LoBs concerns and improvement of KPIs involved in their operations rather than traditional integrated solutions.


Here we might deviate slightly from people perception to technology but this will still elevate the people perception finally.


What will be the focus for LoBs when it comes to decision making?


Improved KPIs of their business functions

Leveraging up to date systems and latest technology available in the market

More end user involvement

• Enough visibility of the process in case of cross functions


Let us look at some example scenarios which can explain this well:


Let us take financial aid systems that governments use to fund education, infrastructure projects etc. needs (Ex: Student Financial aid): Most of these applications are implemented on CRM (With BRF Plus, Web forms as main components) and ECC platform (Fi, PSCD as main component). For different departments targets will be different and may be involving conflict of interest also. Like front office guys KPI might be maximum applications screened/Validated for that academic year at the same time for responsible ministry of the government this might be minimum funds spent for one academic year.


Let us take financial aid systems that governments use to fund education, infrastructure projects etc. needs (Ex: Student Financial aid): Most of these applications are implemented on CRM (With BRF Plus, Web forms as main components) and ECC platform (Fi, PSCD as main component). For different departments targets will be different and may be involving conflict of interest also. Like front office guys KPI might be maximum applications screened/Validated for that academic year at the same time for responsible ministry of the government this might be minimum funds spent for one academic year.


For front office operations one of the critical pieces here is application form provided to the students. Because of technology limitations these forms might be of BSP, WDA, Adobe forms. Target audience being young generation these applications can’t meet the purpose or expectations of the end users. And for front office guys who validates the applications are constrained by the technology which helps in managing the other departments KPIs better (SAP ECC, CRM combination works better for back office/Finance teams to manage their KPIs).


As part of Digital Transformation (basically moving from transactions or system based operations to applications way of managing operations), if the student application is implemented on cloud or on mobile friendly way and integrating the same with BRM for rules management will help front office to manage their operation better at the same time back office can continue with on premise systems helping to manage their KPIs also better. So this hybrid platform can create win-win situation for both departments. Use of BPM (better if cloud based) on top of application processing gives better visibility to both departments by providing insights like what is happening to the processed applications to the front office staff and by providing projections on how many applications will be following for back office actions.


Invoicing at manufacturing industry can be another example here, Take the present scenario at a plat where 200-500 trucks need to move out every day and invoices need to be prepared for all these trucks when they arrive at dispatching point.  Most of the times this activity is performed by the staff sitting at dispatch counter, who are not well versed with SAP systems and technology but trained to perform these activities. Sometimes these terminals will have limited network connectivity. As part of our initial SAP projects implementations we have experienced such scenarios in practical where terminals having very limited connectivity or SAP systems having some problem causing huge blockage at main gate with hundreds of trucks waiting to move out.


Instead of transaction based operation if a cloud based custom UI5/Fiori app, with use of GPS based tracking and with a proper scheduling calculation, showing trucks information arriving at dispatch bays can provide much effective platform to perform these operations.


Hence if SIs can help customers to move from integrated platforms to componentized application platforms, their solutions can be more attractive to LoBs and help them winning the situation. May be BPM, BRM and Mobile platforms (on premise or preferably Cloud based) will help in creating such solutions. May be here we observer the significance of  MBOs (Mini Business object) structures which helps in creating applications in more modularized way.  In the previous examples may be use of Gateway which is representing backend objects with an abstract services is almost playing the same role without data storage capability at staging level. But the application architecture principles will going forward force us to have such staging areas with data storage capabilities. So this will be one of the areas SIs can use their expertise and come up with such solutions. I can foresee HCP database will be playing this role and to some extend it is already in practice also.



This is something inline with what S/4Hana offering as  per the technical insight detailed in : http://diginomica.com/2015/02/15/sap-s4hana-deeper-analysis-technical-side/



This is where people on the ground(Directly) and SIs support structures alignment(indirectly) make a difference having knowledge of operational issues and should be able to read the situation and by applying digital transformation principles effectively. So to meet these needs of the customers SIs back office planning should be aligned and well-armed with architects pools with different streams  who can stand up to the situation  and provide ad-hoc solutions and at the same time help SIs to be equipped with all required solutions while approaching the customers.


In the next blog we will see more on back office support structure alignments like what kind of architect pools, SIs can build to meet these digital transformation needs of customers. This might touch upon required changes from conventional Solution Architects understanding (Functional SMEs as Solution architects) of SIs to modern Social Solution Architects (Technology oriented people as SSAs) , as this Digital transformation has to address the technology driven disruption and handle the issues that are social in nature.

In this latest article in our data privacy and security series, we discuss cloud data security.

Read the first installments of the series here.


Cloud applications and services offer flexibility,
innovation, and speed. Yet data security concerns – encompassing unauthorized
access, information privacy, and business continuity – remain stumbling blocks
when evaluating a move to the cloud. Companies must also comply with local laws
and industry regulations governing how data must be secured and held private.


One of the common misconceptions about cloud data
security is that more onsite control equals more security. But sophisticated
in-house security is complex and expensive, and midsize companies seldom have
the IT resources to devote to it. For most small and midsize businesses,
trusting their data to a respected cloud services provider with the transparency,
capacity, and skills to ensure privacy and security is the most secure choice.


Whether you store your data on premise or in a
private or public cloud, data security is critical – and to make the right
choices, you need a clear roadmap and security framework.


Asking the right questions

To begin assessing your situation, ask yourself
these three questions about data privacy and security:


Is the collection and use of this data legally allowed?

Some countries have laws prohibiting collection, use, or processing

of certain types of data – for example, the European Data Protection Directive

or US HIPAA privacy laws. Legal constraints apply regardless
of whether you choose an on-premise or cloud solution.


Is the data secure?

The answer here varies based on whether the data is
controlled on premise or in the cloud. If it’s in house, you’re ultimately responsible
for ensuring data security. With a cloud solution, do your homework on your
cloud provider’s security standards and practices. In many cases, data security
is a joint effort. The cloud provider manages the infrastructure (and should
rely on industry standards including the ISO27000 framework). The customer is generally
responsible for data access, authentication, and authority.


Is the solution reliable?
For in-house solutions, testing
and control is the customer’s responsibility. With a cloud provider – which can
serve thousands of customers on multitenant or public clouds – it isn’t practical
for each customer to perform independent audits. The provider must therefore validate
security in a different way – usually through regular independent compliance
audits. At SAP, for example, an independent third party provider audits
procedures, controls, and IT security using SSAE16-SOC2 standards.


A multidimensional approach to data privacy and compliance

To address cloud data security concerns, SAP has
built a multidimensional framework based on three primary aspects:


  • Scoping. Covers all technology and infrastructure components,
    relevant processes, and regular personnel training.
  • Information security and
    data privacy.
    Focuses on data
    confidentiality and integrity as well as system availability. This covers privacy
    and protection of personal data and intellectual property.
  • Enforcement and evidence.


Multi-Dimension Framework.png


How SAP supports data privacy

Evaluating your cloud security needs? SAP
Services can help you build a foundation of comprehensive security architecture,
then add supporting compliance functions including integrated information
security management, data protection, and service delivery systems. Our experts
can help you design organizational reports that provide independent evidence
for security, privacy, and availability, and ensure that your data processing
agreements meet local, national, and international data privacy regulations.


SAP Business Cloud customers also get a range of
security support. Our solutions are designed and sold to ensure that you control,
and have complete ownership of your data. All cloud subscriptions include data
protection agreements. The contract is based in the country of the customer’s choice
signed with the local SAP affiliate or partner. We use a leading compliance
framework with twice-yearly independent SSAE 16-SOC2 compliance audits. And you
can select the geography where your services will be hosted – for example, near
your headquarters or major clients.


Learn more now


To learn more about how SAP Services can help
you move confidently to the cloud while ensuring transparent and compliant data
security for all your applications and needs, visit us online.


To learn more please join us at the SAP Service and Support SAPPHIRE NOW area in Orlando.

Update to my earlier post:

In 2013, ASUG launched a cloud integration Influence Council which spanned several integration topics between SAP Business Suite (with a focus though on SAP ERP) and SAP's recently acquired cloud solutions.  While the initial focus targeted cross-cloud solutions, this year the councils narrowed their focus further and formed separate groups - one very important one focuses on integration with Ariba.

At this year's 2015 ASUG Annual Conference in Orlando, we had a chance to meet with SAP customers and partners in two scheduled influence activities and in one-on-one sessions on the show floor to get the 'customer voice' into SAP's development of more simplified and streamlined integration capabilities between SAP Business Suite integration with Ariba.

Thank you for all who were able to join us onsite!

Special thanks to our ASUG (America's SAP User Group) Influence Council Chair Person, Nick DeCenzo ,and our ASUG Influence program managers, SAP Product Managers for Ariba integration, and the SAP Customer Engagement Initiative team to provide a great venue to do that - at the conference and beyond.

Going forward we're looking forward to an ongoing collaboration that you can join too - either via the ASUG Influence Council for Ariba Integration, or if you're outside of North America, look for our upcoming SAP Customer Engagement Initiative project, "Simplify the Integration of Ariba, Fieldglass and SAP Business Suite with New RDS Preconfigured Scenarios".

What did we learn so far?

  1. Many SAP customers still need more information about the different cloud solutions from Ariba (Yes! There is more than one Ariba solution!) and how they compare or overlap with capabilities in their on-premise SAP solutions. These different Ariba cloud apps support different procurement use cases and capabilities which provide lots of flexibility to extend existing on-premise capabilities in different ways where it makes sense.
  2. Many existing SAP customers would like help comparing which Ariba capabilities can extend their already implemented SAP on-premise capabilities (e.g. SAP ERP, SAP SRM, and SAP Supply Chain or any combination thereof), and if they should consider migrating off of any of their on-premise solutions.  The good news is that their investments in their SAP solutions are secure, and SAP continues to invest in and support the SAP on-premise solutions, providing better integration between SAP ERP, SRM and Ariba in the use cases where it makes sense.  

    As a result, the ASUG group for SRM will discuss with several other ASUG groups (procurement, Accounts Payable and Supply Chain)  to offer webcasts which will help better define potential integration use cases
  3. Additional integration requirements were identified between the SAP on-premise solutions and the Ariba solutions, many of which are already on SAP's development roadmap where customer insight and prioritization is already well underway and the council will support.

Want to join the discussion?

If you're interested in participating in the ASUG Influence Council for Ariba Integration with SAP (ASUG members only),  or in the SAP Customer Engagement Initiative project, Simplify Ariba Integration with new packaged Best Practice scenarios, let us know.  Participants need to have a current "Feedback Agreement" (FBA) with SAP in place, and be able to participate in periodic one-on-one and group conference calls.

We'll keep you posted on our progress!

Note - From my original post, sessions scheduled at SAPPHIRE and ASUG Annual Conference in Orlando included the following:

1. Preconference Deep Dive: Ariba & SAP Integration 101:

Arriving on Sunday or Monday?  During the all-day "Ariba & SAP Business Suite Integration 101" ASUG Pre-conference session, attendees will participate in a full-day deep dive workshop covering Ariba & Business Suite integration. Hear options, best practices, and the roadmap for Ariba Integration with SAP Business Suite and gain a deep dive into the integration options to simplify the integration including options for SAP HANA Cloud Integration, Ariba Integration Tool Kit, Direct Connectivity, and SAP NetWeaver PI, and what packaged SAP Best Practices are available in SAP Rapid Deployment Solutions.  We'll have several "bring-your-own-PC" hands on exercises using offline simulations you can take home with you, and download project tools to help you get started.

During the lunch break, we'll host Influence Lunch Table discussions with workshop participants, hosted by our ASUG Influence Customer Chair, Nick DeCenzo, and SAP Product & Package Owners including , Lisa Sammer, Cathal O'Sullivan, and Kirsten Loegering.


2. ASUG SAP Ariba Influence session in the ASUG Hub  on Wednesday, May 6th at 4:15PM

Join Ariba Integration ASUG Influence Council Customer Chair,  Nick DeCenzo and several Ariba/SAP Product Managers regarding future development plans and ASUG member needs regarding Ariba integration with SAP Business Suite.

Last year the ASUG Cloud Integration Influence Council was run as one council with a bigger cross-cloud solution and technical focus, but has since been split into separate influence councils focused on specific cloud solutions.  In several cases in the past we collaborated with the existing SRM focus/influence group as well where possible, and will continue to do so.  During this session we'll have several SAP Product Management teams represented to hear your ideas and requirements, and to share their areas of development where SAP is actively seeking ASUG input via integration between ASUG Influence Councils and SAP CEI projects.  Join us to learn more!

Of course there is the regular and seasonal market floating, and some highs of economic instabilities. It happens with all industries, and all markets around the world.


The question is how to act in this time of uncertain. You must have heard "Behind every crisis, lies opportunities" and when it comes about market changes, invest and innovate this is 100% true. If you make the right call to keep up, change and adapt, by the time the market gets back to its stability and the "sea goes calm again" you will be one step ahead of those companies who did nothing, in a time you are supposed to do exactly the opposite.


Technology makes it lot easier to seek the correct information, and it helps you to change as you must, and as you can. This is why the implementation of new technologies such as cloud computing is so important today. Treading this path, and choosing the right tools can put you on a great position to take the right decisions and seek growth in a time everyone else seeks stability.

From last couple of months, I have been working with Cloud Platform. During this period, my journey was full of interesting questions and challenges. I thought I would sum up all challenges here which will help us to make our Journey smother towards Cloudification. Here are few points.


Compliance – When we think about Cloud, a few important questions to come to our mind -  Where will my data reside? Whether my data is safe in the cloud? What are the security features enforced by Cloud provider on their data centers? Will my company still comply with legal requirements?

Answer of all these question lies in careful evaluation  and discussion between the various stakeholders. So, during the feasibility study phase, it is very important to involve IT, Business, Legal and Finance etc. teams. One thing that we need to keep in mind that decision to move some/all of the systems to Cloud should not be an IT Team decision as it will impact everyone in the organization. Business will be impacted if Systems availability SLA in Cloud will not match with Business Continuity, Legal Team will be impacted if Data security is not in compliance with country’s legal requirements, Finance will be impacted if it will overshoot cost etc. So, everyone needs to be involved in this decision.


Infrastructure – Infrastructure plays an important role while implementing solutions on Cloud. A Simple question is How Cloud Providers network will be connected with Customers network? But answer of this question is quite complex as it depends upon lot of factors like Bandwidth, Network Latency, Cost and Connectivity etc.

Based on evaluation of these factors customer can decide to setup Corporate VPN connectivity between cloud providers data center and customer network.

Another option is to setup dedicated Local Area Network connection which will reduce network latency but at same time can have impact on cost.

So, these factors should be evaluated based on different factors and latency test can be carried out to test Network through put, round trip time and network stability etc.


DNS Resolution – Before implementing new solutions into Cloud, one of the important factors is DNS resolution. Systems installed in Cloud will be on different network than the customer’s network. In order to access systems installed in Cloud from Customer’s network, Customers need to establish DNS connectivity between Cloud Provider network and their own network. This will also be required if Cloud systems needs to be integrated with On Premise systems.

There are lots of DNS resolution mechanisms available in the market to achieve this like Static DNS Scenario, DNS Forwarding Scenario and DNS Zone Transfer Scenario etc.


High Availability & Disaster Recovery – While deciding on the Cloud then it is very important to discuss about Business Continuity as all Cloud vendors has SLA’s related to availability of the systems in cloud. So, it is very important to discuss about Maintenance Period.

Also, architecture for High availability of systems and disaster recovery plays a major role. So, it is important to know what will happen to systems in case of any disaster and how quickly systems in cloud can recover from any disaster to minimize impact on Business.


Integration Strategy – When moving to Cloud, it is very important to decide on Integration Strategy as lot of legacy systems, third party systems and On Premise systems need to interact with systems in Cloud. So, it is very important to design Integration architecture to show how different systems will integrate with each other, will there any requirement of any 3rd party integration solution etc.


Enterprise Single Sign-On – This is one of the important aspects when customer is using Enterprise wide Single Sign-On for their On Premise solutions. While migrating to Cloud, it is important to assess that whether existing Single Sign-On solution can be utilized for new systems in cloud or there is need to use different Single Sign-On solution as lot of Single Sign-On Solution depends upon operating system on which systems are installed.

This will be one of the deciding factors in case new solutions in cloud cannot use existing Single Sign-On solution and it can impact the cost & timeliness of the project.


Email Server Integration – If systems installed in Cloud needs to send email with in customer organization or outside organization then it is very important to decide how email server integration. There can be multiple options in this scenario like Customer can integrate their own Email server to the systems installed in cloud, this might require change in firewall rules to allow systems installed in cloud to use email server or Cloud provider provides their own Email server to integrate with systems installed in cloud etc.

So, it is important to decide how Email services will work in systems installed in cloud.


Responsibility Matrix – This is one of the areas where Customer and Vendor need a lot of attention in order to effectively define Roles and Responsibilities. Responsibility matrix includes who will support the systems, who will ensure proper backups of the systems, if it is Managed Cloud then what are the responsibilities of Vendor for managing the systems and who will do upgrade & when etc.


FQDN – This is very small but an important aspect while installing new solutions in Cloud. When few systems are installed in cloud and few in On Premise infrastructure then it is important to use Fully Qualified Domain Name while setting up communication between On Premise system and Cloud systems. This is required because Cloud systems and On Premise systems are in different domains. So, always use FQDN while setting up any connectivity.


Conclusion – While Future of Technology lies in harnessing the Power of Cloud, so, it is very important that we make our strategy in such a way that it will faster Innovation cycle, increase flexibility, reduce carbon emission, make Business more scalable and make Business real time.


For more information, please refer to below links.


SAP HANA Cloud Platform

Amazon Web Services


Disclaimer: This Blog is the personal Blog and only contains my personal views, thoughts and opinions. It is not endorsed by my employer nor does it constitute any official communication of my employer.

At the recent Hybris Global Partner Summit in Munich,  hybris-as-a-service (yaaS) was introduced as a modern commerce platform based on microservices (it is now in beta ).  I’ve blogged about YaaS in the past in conjunction with SAP’s PaaS – HANA Cloud Platform (HCP) – and its evolution towards a tighter association with Cloud Foundry.


YaaS contains a modern architecture and uses cutting-edge technology such Cloud Foundry, Apache Kafka (a high throughput distributed messaging system), apigee, RAML, etc.




Note: Other SAP competitors (such as Workday) are also moving towards such micro-service-based architectures.


The architecture also uses micro-services mash-ups to aggregate service calls or to compose more complex service flows that “stop cascading failure and enable resilience in complex distributed systems where failure is inevitable”. This model was demonstrated by NetFlix in its Hystrix solution) and has been used successfully in numerous environments.


Note: Before people start screaming and yelling that YaaS will replace HCP, it is important to understand that YaaS will be based on HCP as its underlying PaaS layer.



NoteCurrently HCP does not yet support Cloud Foundry so the YaaS Beta doesn’t run on HCP.


As others have discovered, this architecture has broader implications for SAP’s general cloud efforts.


Journalist Jason Bloomberg  states:

Not only does YaaS represent a next-generation strategy for hybris, it portends a momentous transformation of the SAP mother ship as well.

Christine Crandell compares YaaS to Force.com and describes YaaS’ differentiators as a threat to Salesforce:

  1. Independence from the business domain
  2. Independence from devices
  3. Pre-build business processes
  4. Non-proprietary that offers freedom of choice in programming languages, underlying database technology and portability of services and applications between cloud infrastructures.

Truthfully, a threat to Force.com from SAP would be a pretty big change in the “Cloud Platform wars” and would require a very widespread use of YaaS and similar architectures in SAP’s various cloud assets. How realistic is this transformation?


SAP’s developers and YaaS


Cutting edge architectures – such as YaaS- often move slowly into larger organizations / vendors that have other entrenched (I won’t say “legacy”) technologies.  How fast can SAP move towards implementing YaaS-like architectures and engaging internal developers to use such tools.


SAP’s main focus in the PaaS arena remains HCP, yet publicly-available session lists for the upcoming internal DKOMs in Waldorf and Palo Alto provide additional insight into SAP’s activities concerning YaaS, Cloud Foundry and other related development topics.


NotePlaying with the sessioncatalog.sapevents.com URL, I discovered other session lists for internal SAP events (recent FKOM in Mexico, etc).  Although only the abstracts are available, there is a wealth of information available for those patient enough to look at the specific details of individual sessions.  The associated presentations aren’t available but the abstracts provide enough additional information to see patterns and thus gain valuable information.




YaaS Overview

Loyalty Management on Hybris as a Service (YaaS) Platform

Hybris Loyalty Management is a brand new application based on the micro-services architecture and Cloud Foundry. It extends Hybris Commerce as a Service solution and helps retailers easily run their loyalty programs to engage customers, deliver personalized promotions, encourage advocacy, and increase sales. Learn how easy it was for us to build business functionality, rule engine, job scheduler, integration with Hybris and SAP systems and responsive UI using YaaS and microservices architecture.

Modern Customer Engagement Center Built on Hybris YaaS.IO-Cloud Platform

The Customer Engagement Center is YaaS.io Cloud Stack based to enable our customers to provide simple and direct next generation customer service via Peer-to-Peer VideoChat and Social Media capabilities. It was built in an greenfield approach using Hybris YaaS.IO commerce cloud platform to deliver a glimpse of what is possible in 8 weeks using Cloud Development paradigms like Yaas.IO factors, microservices, open sources libraries and modern Web based real time communication technologies.

Hands on YaaS - a new cloud platform for CEC

Get your hands on the brand new YaaS (hybris-as-a-service) platform, based on a microservices architecture. Define your RESTful API, use the SDK to bootstrap a service stub in Java within a few minutes, and make it do something cool by calling existing Core and Commerce APIs.

Development on YaaS: First-Hand Experience on Building Microservices

Field report from first projects within the LOB CEC building on hybris YaaS: - Lessons learned and best practices from running proof of concepts and CEC Cloud Bootcamps - Getting started with the help of a growing community

Cloud billing based on yaaS platform

This session will demonstrate how an end-to-end public cloud billing solution can be developed on the cloud foundry (open source) based yaaS platform. We will explain to you the architecture we drafted to be able to quickly deploy rich functionality and how we plan to evolve the solution over time. Based on a realistic user story, the session will give insight into what and how we exactly developed on the various layers of the platform.

Service Management in C4C with Drones

In this talk we will discuss inner workings of drones, software integration of drones with C4C and code that runs on yaaS running image analysis routines and algorithms.

Cloud for Customer - OData APIs and Extension Apps on yaaS/HCP

To complement SAP Cloud for Customer (C4C) application, our customers and partners, can leverage yaaS or HCP to build innovative cloud scale application integrated with C4C. We have built new capabilities in C4C enabling customers to quickly consume OData APIs exposed by SAP Cloud for Customer for not only standard business objects but also those extended/customized by customers in an open, standard based, easy to use cloud development and runtime environment and build application using HCP/yaaS


Interesting dimensions

  1. Session  speakers are from SAP SE and hybris which shows that the technology is expanding to include more than just hybris developers.
  2. Although the focus is primarily on LoB Customer Engagement & Commerce (CEC) applications, there are a variety of other YaaS-based applications (drones, cloud billing, etc) which are more generic in character.
  3. The fact that extensions might also run on YaaS technology is intriguing.
  4. There are still more general HCP sessions than YaaS sessions at the DKOMs - Palo Alto : 20 vs.6 – Waldorf: 17 vs. 9) but the amount of YaaS-related sessions is interesting especially as it was just released at the beginning of February .
  5. The development speed that this new architecture may bring is important to consider – building a cloud solution in 8 weeks is pretty impressive.


As mentioned above, YaaS also focuses on micro-service-based architectures; I also found a variety of related sessions.




Developing apps with SAP HANA Cloud Platform and Cloud Foundry

At this booth we will present our plans to integrate the open elastic runtime platform Cloud Foundry as substantial part of SAP HANA Cloud Platform. We will explain how this allows developers to build applications in Java, node.js or XSJS. And you will learn how developers can use well-known community as well as enterprise-grade SAP services to build micro service oriented cloud applications.

SMP/HCPms and Microservices in the Cloud

This talk will describe the factors and techniques that were involved in taking an existing monolithic on-premise application, SMP - SAP Mobile Platform, and turning it, without major redevelopment, into deployable cloud services; HCPms - HCP mobile services. This includes the steps taken to ensure we can adapt to the evolving cloud microservice architecture and container strategy of SAP. Targeted at server-side developers and architects, you will gain insight into the HCPms cloud architecture.

LoB CEC Strategy and Architecture

Our mission is to enable companies to provide real-time, contextual, consistent, and relevant experiences to their customers, regardless of channel or device, across Sales, Service, Marketing, and Commerce. This talk discusses the architecture implications, API and integration technology strategy, and evolution of product portfolio towards a more harmonized micro-services based cloud architecture to enable these customer experiences and different deployment options.


Note: I just have access to the DKOM session abstracts and have no way to judge how many developers will really attend them but the presence of such sessions is an indicator of their relative importance.

My take

SAP DKOMs contain many sessions (in Waldorf there are over 300) that compete for developers’ interest and the emergence of S/4HANA, Fiori /UX or HANA will probably pull larger crowds but I’m hoping that the YaaS sessions will also draw crowds.


As SAP moves towards the cloud, YaaS and its architecture will play an important part in this evolution.  DKOM is an internal event for developers – I’m waiting for similar efforts to educate the partner ecosystem. One of the most important features of YaaS is an app / services marketplace that will finally provide SAP partners with the opportunity to easily sell their cloud assets – a change that will be welcomed by such companies considering the present lack-luster SAP Store in terms of its support of cloud solutions.


For SIs / ISVs struggling to understand / cope with the impact of this transition to the cloud, the necessity of learning yet another new technology may not be welcomed.  Thus, existing partners must be motivated to take advantage of such offers. In the future, they will be faced with a new type of competitor who is micro-service-savvy and already accustomed to the new development paradigms promoted by AWS, Netflix , etc.  Such competitors may not have experience in enterprise software space but their technical maturity in the necessary technology makes them excellent choices for larger more traditional SIs to acquire to quickly gain market share.

After facing Concur in FKOM2015 in Barcelona, I really want to test concur by myself, so today I have registered a 30 days free trial account here: Test Drive Concur® Expense - Concur  and immediately start to use.


Once I have logged in, I have found everything that I might need while punching ( for mobille version I think we'll no more enter many things). Looks so simple, I did not refer to any help or manual, Concur guided me to start.


Then I have started to enter my FKOM expenses, wow it is really easy, just select the expense item from right-end side and concur will propose you the vendor from it's database, if not recognized one just enter the name.


Concur lets the organizations to define expenses and the limitations, this gives confidence to managers that expenses are under control. I have hit the limits while entering the taxi.



No problem I have proceeded by entering an explanation to my manager I finished my entry and submitted for approval. Without any training or preparation I have completed all in 5 minutes!



Concur really fun and easy,




Sarhan, follow me on twitter http://www.twitter.com/sarhanpolatates

Here is something we all have witnessed at some point of time. Everybody keeps talking of some term, it becomes a buzz-word in no time & then it becomes so hugely popular that you won’t dare to ask what-the-heck-it-actually-means? Right :-?


Ok,  so here is one sincere attempt to unravel the hazy world of Cloud..!  


We’ve come a long way from that famous quote “ 640K ought to be enough for anybody”! With the ICT convergence, 3G (& now 4G) network & the humongous BIG social media apps, DATA is growing faster and faster.   No wonder, if given the choice to move one workload to the cloud, most choose storage & which has given rise to Cloud computing model of IaaS – Infrastructure as a Service, which basically offers  bundled services of Compute, Storage, Network & Security requirements. Many organizations are moving their ERP applications to Cloud either at the time of hardware refresh/upgrade or are directly hosting the applications on Cloud right from the inception of business. By doing this, not only they move away from Capex to Opex (Capital expenses to Operating expenses), but also enjoy the scalability of Cloud (can add/reduce storage/compute/network bandwidth as per the need) within an agreed SLA-framework! While Amazon is a global leader as IaaS provider, ICT players like Sify Technologies (India’s first SSAE-16 Cloud certified provider) in India have helped many organizations in moving their ERP applications (& especially SAP) to Cloud seamlessly.

PaaS (Platform as a Service) – Here cloud providers deliver a computing platform, typically including operating system, programming language execution environment, database, and web server. Application developers can develop and run their software solutions on a cloud platform without the cost and complexity of buying and managing the underlying hardware and software layers. With some PaaS providers like Microsoft Azure and Google App Engine, the underlying computer and storage resources scale automatically to match application demand so that the cloud user does not have to allocate resources manually.


SaaS  - In Software as a Service (which is also called as ‘On-demand’ software) model, cloud providers install and operate application software in the cloud and cloud users access the software from cloud clients. This eliminates the need to install and run the application on the cloud user's own computers, which simplifies maintenance and support. The pricing model for SaaS applications is typically a monthly or yearly flat fee per user so price is scalable and adjustable if users are added or removed at any point.

  1. Saleforce.com, Ariba, & Success-factors (latter two are from SAP stable) are some of the hugely popular applications used by enterprises all over the world to manage their sales/purchase/HR processes dynamically.

SaaS allows a business the potential to reduce IT operational costs by outsourcing hardware and software maintenance and support to the cloud provider. This enables the business to reallocate IT operations costs away from hardware/software spending and personnel expenses, towards meeting other business goals. In addition, with applications hosted centrally, updates can be released without the need for users to install new software.


Depending on the deployment options, Cloud is classified under Public, Private & Hybrid Cloud, which vary due to security considerations.  As the world embraces Cloud, Cloud players are adding more and more stringent layers of security through software/hardware firewall & Managed Security services (including data encryption technology) .


Last word .. Cloud is not vaporware, it is there to stay and …only to grow bigger and BIGGER by the day!


So, when is your organization moving onto Cloud nine :-?

SAP announced its next big thing in FKOM and I am excited to be part of it: Business Suite 4 HANA or S4HANA.

The S is for Simple and the 4 is for the 4th generation of SAP ERP: R/2, R/3, ERP, and S4HANA.





S4HANA is the successor of SAP Business Suite, built on SAP’s HANA platform. It comes with re-written code (no materialized aggregates) to leverage SAP HANA transactional and real-time analytical capabilities, delivered through a simplified and enhanced end-user interface based on SAP Fiori, available in the cloud and on premise.






Some takeaways from FKOM



Simplicity delivered with S4HANA:


- Based on cloud-first approach


- HTAP (hybrid transaction analytical processing) – a database that can support OLTP and OLAP without data replication


- HANA multi-tenancy – in the cloud or on premise


- No unnecessary indices, no aggregates – replaced by on-the-fly calculations, thanks to an in-memory database


- User interface is Fiori based


- Maintains ERP core data models



Real benefits:


- Reduced data footprint – highly compressed data, less tables


- Higher table throughput – fewer table updates, less locking, faster processing


- More Flexible – complexity is reduced as indices and aggregates are removed



SAP’s new cloud-based business models are disrupting the enterprise-software industry – watch this space.

I see that far from the main capitals in third world countries, the Cloud Business is approached very cautious by entrepreneurs.



This is rightly? We here know the poor quality of internet services in comparison to other countries when you are away from the capital, and this serves as ammunition to favor other negative factors.




Of course not everything is negativity, and this has been changing gradually, the internet services are improving and some entrepreneurs are taking Their chances in cloud business.



Such infrastructure problems in these countries directly affect the results of technology-related business, the advancement of information and technological should be pillars of these countries economies.

In my last blog,  I talked about creating a "decision framework" to help organization move towards Cloud adoption. However, I had little idea of what it may take to create a “decision framework” until attended this Gartner webinar by Drue Reeves, Distinguished Gartner Analyst. This webinar, titled "A methodology for determining which application can go on the Cloud", taught me something that I believe can also be used an inputs for developing “Cloud Strategy”. I would like to share with you the notes I took from this webinar.


Step 1: Risk Assessment

When you put the application in the Cloud, you need to understand that you are losing control over it to some extent, especially when you are putting your application in the public Cloud.

With IaaS you have much more control and with SaaS you have some control.


Think of what is your risk tolerance for the application if you lose some transactions/data, or you lose service connection. Will that cause any loss of life, or loss of your brand or productivity?

Are you risking customer privacy? Are you staying complaint? If you think that you can't tolerate your Cloud application going down for few minutes or your risk tolerance for the Cloud application is extremely low then stop here!


Step 2: Risk Mitigation

Once you have evaluated your risks and risk tolerance and decided to move forward, you need to think how you can mitigate these risks. You may mitigate some of the risks by :

- making sure the Cloud service is in compliance to security requirements

- by adopting a hybrid Cloud approach where you can run your application on the public Cloud but store your data and access control inside your own company network. This way even if you lose access to the Cloud, your data stays secure.

- having an insurance that will pay you in case you loss of control and resulting financial loss to your business.


Step 3: Select Cloud Layer

Once you understand the risks and have a plan for risk mitigation, next step is to select Cloud layer: "IaaS, PaaS or SaaS. You should involve application owner in this process.

You should ask them if they want to manage the application at the user level or at the storage level,

Do they want to just replace the application or want to re-factor the application?

If application owners want to manage applications at the storage level, then you will select IaaS layer.

If the application owners say that they are not looking to manage the application at storage level, don't want to deal with backups, don't want to build extensions or refractor the application  then you know that they are just looking for the replacing the application with a SaaS application.

However, if the requirement is to re-factor the application and run it using Hybrid model then the right option is to go with PaaS.


Step 4: Technical Assessment

Next, you need to perform technical and cost assessment of the Cloud layer that you are thinking of using.  For example, if you are going for IaaS, you need to find out what kind of computing resources (CPUs, memory) and storage are required by the application. If you are going for SaaS, you need to find out how many users will be using the application, what functionality business owners plan to use and what data will flow in or out of the application. Based on your technical assessment, you need to come up with a total cost.


Step 5: Cloud Application Design

Once you have selected your Cloud layer, you need to decide what design changes are required to make it usable for the business.

If you are going for IaaS or PaaS, you may want to:

- design it for resiliency

- add services for backup and snapshot

- add additional servers for load balancing


If you decide to use SaaS:

- You need to customize the user interface to make it usable for the business.

- You may add a mobility layer so that application can be used from mobile devices.


Whatever service you select, you want to add it to a check list of things to monitor.

You want to monitor your Cloud application and services to make sure it is keeping up with the growth.


Step 6: Cloud Bill Estimation and Governance

You can't deploy to the Cloud without knowing how much it would cost. You don’t want to find out later that your Cloud requirement has grown and your IT budget is blown out.

You should also want to ask your business how the application will grow over time, so that you can estimate the cost for adding resources and features to the application in the Cloud.

For example, how many users you will need to added with time, how many instances you may have to add to keep up the optimum performance. You need to have a governance process in place to make sure you have only the required number of active accounts in the Cloud and you are not over-consuming.



Note: Once you have reached this point, you have everything you need to make go/no-go call for moving to Cloud.


Step 7: Flow of approval

Once you have decided to go ahead with Cloud deployment, you need to get buy in from all key players: application owners and their business unit leaders. On the strength of this process, you can show that due diligence is done, and you can get approval based on that.


Step 8: Cloud Supply Chain

Now you have the approval to migrate app to the Cloud. You must have process defined for opening and shutting down could account. Migration strategy: you have to order the app, you have to think hybrid when putting application the public Cloud but may want keep access control inside your network. Storage migration strategy: if you decide to keep data in house, you may need fast connection between Cloud and on-premise systems.


Step 9: Manage and evaluate

Information you have gathered from previous steps need to be used to manage expectations.

You need to monitor and control your Cloud application to make sure it meets the expectations that has been set with the business owners.


Webinar Registration: A Methodology for Determining Which Applications Are for the Cloud | Gartner


Filter Blog

By author:
By date:
By tag: