您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.

规划 Azure 中的 SAP 云采用Plan for SAP cloud adoption in Azure

如 SAP 策略 一文中所述,从 sap cloud 采纳返回可能会很高,但可能会造成缺少预期的风险。As discussed in the SAP strategy article, the returns from SAP cloud adoption can be very high, but so can the risk of missed expectations. 基于您的数字场地开发清楚的财务计划将确保您设置的期望更准确。Developing a clear financial plan that's based on your digital estate will ensure greater accuracy in the expectations that you set. 相同的财务规划练习将为云采用团队提供规划技术活动所需的数据。The same financial planning exercises will provide the cloud adoption team with the data needed to plan technical activities.

云采用框架中的 策略和计划模板 和其他资源可帮助你的组织捕获适用于 SAP Cloud 采纳的合适计划。The strategy and plan template and other resources in the Cloud Adoption Framework can help your organization to capture a suitable plan for SAP cloud adoption.

SAP 数字场地规划SAP digital estate planning

与大多数复杂平台一样,SAP 数字场地会包含三个资产类别,这些资产类别应在您的计划中识别:平台、基础和工作负荷资产。Like most complex platforms, your SAP digital estate will include three asset categories that should be recognized in your plan: platform, foundational, and workload assets.

  • 平台资产: SAP 平台运行在专用应用程序、数据、虚拟机或服务器以及可能的设备的集合上。Platform assets: Your SAP platform runs on a collection of dedicated applications, data, virtual machines or server, and potentially appliances. 无论你的组织在该平台上执行什么操作,这些资产都按 SAP 部署要求定义。Regardless of what your organization does on that platform, those assets are as defined by SAP deployment requirements.

  • 基础资产: 你的 SAP 平台和支持环境也由标识提供者、网络、操作管理工具等必要资产的集合生产。Foundational assets: Your SAP platform and the supporting environment are also upheld by a collection of necessary assets like identity providers, networking, operational management tools, and more. Azure 将这些资产称为基础实用程序,这篇文章系列稍后将介绍如何部署 Azure 登陆区域以提供它们。Azure refers to these assets as foundational utilities, and this articles series will later describe how to deploy of an Azure landing zone to provide them.

  • 工作负荷资产: 大多数组织将 SAP 扩展或集成到各种业务流程,这些业务流程是跨整个公文包的一系列工作负荷所支持的。Workload assets: Most organizations extend or integrate SAP into various business processes that are supported by a range of workloads across the portfolio. 这些工作负载受其应用程序、数据和不属于核心平台部署的虚拟机的集合支持。Those workloads are supported by their collections of applications, data, and virtual machines that aren't part of the core platform deployment. 对 SAP 平台具有依赖关系的每个工作负荷都应该分别进行命名、清点、合理化和跟踪,以实现精细的财务和技术规划决策。Each workload with a dependency on the SAP platform should be named, inventoried, rationalized, and tracked individually to allow for granular financial and technical planning decisions.

有关 SAP 数字领域规划的指导,请查看有关 数字领域规划一文中所述的过程。For guidance on SAP digital estate planning, look through the processes outlined in the article series on digital estate planning. 评估用于迁移到 Azure 的本地工作负荷的最佳实践一文建议 Azure Migrate 和其他评估工具,以使前面的文章可操作的理论指导。The best practice article on assessing on-premises workloads for migration to Azure proposes Azure Migrate and other assessment tools to make that theoretical guidance from the prior article actionable.

规划 SAP 采用时,应注意以下几个问题:Several considerations should be included in those processes when planning for SAP adoption:

  • 评估依赖关系: SAP 等核心平台上的依赖关系经常未记录。Evaluate dependencies: Dependencies on a core platform like SAP are often undocumented. 确保为公文包中的所有资产包含依赖项分析。Be sure to include a dependency analysis for all assets in the portfolio. 有关可操作的参考指南,请参阅 best practices 文章的步骤 5See Step 5 of the best practices article for an actionable reference guide.

  • 标记、分组和元数据: 仔细标记或分组所有资产:Tagging, grouping, and metadata: Carefully tag or group all assets:

    • 在平台上全面标记和分组资产。Thoroughly tag and group assets on the platform. 不要遗漏任何资产,这一点很重要,因为它们是优化财务或技术计划的关键。It's important to not miss any assets, as they're key to refining the financial or technical plan.

    • 分隔 SAP 部署所依赖的所有基础资产并对其进行分组。Separate and group any foundational assets on which the SAP deployment depends. 稍后可将其替换为更有效的 Azure 登陆区域选项。These can later be replaced with more efficient Azure landing zone options.

    • 分别对每个相关工作负荷进行分组。Group each dependant workload individually. 在合理化和迁移工作中,每个工作负荷都可以独立考虑。Those workloads can each be considered independently during rationalization and migration efforts.

  • 资产合理化: 合理化是金融计划最重要的注意事项之一。Asset rationalization: Rationalization is one of the most important considerations for the financial plan. 请考虑每组资产的以下内容:Think about the following with each group of assets:

    • 是否可通过云本机 Azure 登陆区域选项来停用基本资产?Can foundational assets be retired in favor of cloud-native Azure landing zone options?

    • 对于每个工作负荷,是否会停用工作负载?For each workload, will you retire the workload? 是否有必要将工作负荷 rehost 为 "基础结构即服务"?Would it make sense to rehost the workload to infrastructure as a service? 是否应将此工作负荷现代化?Should you modernize this workload? 此工作负荷的有影响力是否足以考虑重新架构或重建工作负荷以利用云本机托管?Is this workload impactful enough to consider rearchitecting or rebuilding the workload to take advantage of cloud-native hosting?

  • 优先级和顺序: 确定平台和工作负荷的优先级和顺序,以建立时间线和计划。Prioritization and sequencing: Prioritize and sequence the platform and workloads to establish a timeline and plan.

  • 混合注意事项: 在执行该计划期间,是否会在迁移波中发布?Hybrid considerations: During the execution of the plan, will you release in migration waves? 在迁移时是否需要用于生产流量的混合连接?Will you need hybrid connectivity for production traffic during migration waves? 使用混合云,公司可以扩展计算资源。Using a hybrid cloud allows companies to scale computing resources. 混合实现还无需做出巨大的资本支出来处理短期的需求高峰。Hybrid implementations also eliminate the need to make massive capital expenditures to handle short-term spikes in demand. 当业务需要释放本地资源以获得更敏感的数据或应用程序时,混合实现可以加快资源的降低。When the business needs to free up local resources for more sensitive data or applications, a hybrid implementation accelerates resource reduction efforts.

  • 环境规划: 你是同时还是单独移动生产和非生产 SAP 平台?Environment planning: Are you moving production and nonproduction SAP platforms at the same time or separately? 客户有时会将其非生产 SAP 平台迁移到 Azure,从而创建用于学习和降低风险的环境。Customers sometimes move their nonproduction SAP platform to Azure, creating an environment for learning and reducing risk. 团队在熟悉 SAP 平台的操作和 Azure 工作负荷后,将会在以后的几周或几个月内迁移生产平台和工作负荷?Once the team is comfortable with the SAP platform's operations and Azure workloads, they will migrate the production platform and workloads weeks or months later?

  • 平台合理化: 最重要的注意事项是如何合理化 SAP 平台资产;考虑如何迁移平台。Platform rationalization: The most important consideration is how to rationalize an SAP platform's assets; consider how you'll migrate the platform. 迁移方法将对云中保留的资产的清单进行清点,并为其提供工作。The migration approach will shape the inventory of assets that will persist in the cloud and the work to get there. 可以考虑以下选项:The following options can be considered:

    • Rehost: 使用 Azure Migrate 或同类系统副本来提升和转换当前的 SAP/OS/DBMS 平台。Rehost: Use Azure Migrate or a homogeneous system copy to lift and shift the current SAP/OS/DBMS platform.

    • Replatform: 结合使用 SAP 的异类平台副本和迁移到 Azure,例如当 OS 需要此类或 DBMS 发生变化时。Replatform: Combine making heterogeneous platform copy of SAP with a move to Azure, such as when the OS requires this or the DBMS changes. 这包括 SAP NetWeaver 生产更改为 DBMS 时的情况。This include when an SAP NetWeaver production changes to HANA as a DBMS.

  • 重塑: 在 Azure 上实现新的 SAP 平台。Rearchitect: Implement a new SAP platform on Azure.

将这些注意事项集成到您的数字房地产评估版后,您可以优化您的业务理由。Once these considerations are integrated into your digital estate evaluation, you can refine your business justification. 你还可以准备构建 SAP cloud 采纳计划。You'll also be ready to build out your SAP cloud adoption plan.

SAP cloud 采纳计划SAP cloud adoption plan

云采用框架包含一个工具和多个模板,用于根据每个方法中所述的任务创建云采用计划或 Azure DevOps 积压工作(backlog)。The Cloud Adoption Framework includes a tool and several templates for creating a cloud adoption plan or Azure DevOps backlog, which are based on the tasks outlined in each methodology. 详细了解 云采用计划和 Azure DevOps 一文中的模板。Learn more about templates in the cloud adoption plan and Azure DevOps article.

无论你是使用模板还是你自己的项目规划工具,都需要考虑以下特定于 SAP 的操作:Whether you use templates or your own project planning tools, factor in the following SAP-specific actions:

  • 评估你的基础资产,并部署相应的 Azure 登陆区域。Evaluate your foundational assets, and deploy an appropriate Azure landing zone.
  • 使用平台合理化努力完成 SAP 平台迁移。Use your platform rationalization efforts to finish migrating the SAP platform.
  • 每个工作负荷 (或要迁移的工作负荷) 的浪潮的帐户。Account for each workload (or wave of workloads) to be migrated.

可以使用 Azure DevOps web 界面 将这些行项目添加到计划中。You can use the Azure DevOps web interface to add those line items to the plan. 如果你正在使用当前资产清单,则可以使用云采用框架一文中概述的 Microsoft Excel 集成来更快地生成计划。If you're working from a current asset inventory, you could build your plan faster with the Microsoft Excel integration outlined in the Cloud Adoption Framework article about tracking workloads.

SAP 就绪计划SAP readiness plan

完成常规工作计划后,即可开始协调团队成员并估计工作。Once you have a general work plan, you can begin aligning team members and estimating the work.

此项目的团队成员可以是 SAP 或 Azure 专家,但团队不太可能在这两个领域具有相同的专业知识。This project's team members could be SAP or Azure experts, but it's unlikely for the team to have equal expertise in both areas. 使用云采用计划确定团队需要获取的技能。Use the cloud adoption plan to determine the skills that the team will need to acquire. 然后,将这些技能映射到团队成员,以更清晰地了解准备情况、skilling 和培训需求。Then, map those skills to team members to gain a clearer picture of readiness, skilling, and training needs. 构建技能准备计划一文和战略与计划模板的云采用框架可帮助你的团队跟踪和解决 skilling 间隔,从而在每个冲刺(sprint)中创建更强大的跨功能协作。The Cloud Adoption Framework building a skills readiness plan article and strategy and plan template can help your team to track and address skilling gaps to create stronger cross-functional collaboration in each sprint.

下一步:查看环境或 Azure 登陆区域以进行 SAP 企业级迁移Next step: Review your environment or Azure landing zone for an SAP enterprise-scale migration

下列文章提供了整个云采用旅程中特定要点的指导,旨在帮助你在 Azure 中采用 SAP。The following articles provide guidance for specific points throughout the cloud adoption journey to help you succeed in adopting SAP in Azure.