Question

You are ready to deploy a SAP database environment, which will include a cluster SQL server, four front-end servers, and four back-end servers. You need to deploy this environ- ment into a test environment, a development environment, and a production environment. What would you use to deploy this environment and to ensure that the environments are standardized?

Answer 1

Answer:-

in the world of developer and operations tools, the situation is more in flux. SAP is moving toward embracing standard developer and operations technologies, but adoption has progressed at different rates on different platforms. Further, SAP's adoption of standard technologies often has a distinctively SAP-flavored spin, which can hinder the use of a standard kit of tools in conjunction with SAP's software.

Nevertheless, the same advantages of being able to leverage standard development technologies instead of proprietary ones are in play. They are:

• Pace of development. SAP can't keep up with the rest of the world in all areas all the time, and sometimes allows developer and operations tools to stagnate. This is less likely with standard technologies.
• Right tool for the job. Sometimes, a particular tool, such as Eclipse, just doesn't cut it as an integrated development environment.
• Enables scenarios SAP may not have anticipated. Development innovations, such as distributed version control, fully automated testing and Agile development, have been slow to spread in the SAP ecosystem, in large part because they are not enabled by SAP's developer and operations tools.

SAP often builds bridges to standard tools rather than adopting standard interfaces to allow standard tools to interact directly with SAP applications. This allows SAP to reap some of the benefits of pace of development, and enables some flexibility for tool choice.

However, this approach also results in a two-tier tooling situation in SAP environments, where SAP development tools are tier 1 and third-party tools are tier 2. The situation is workable in a fully SAP-centric environment, but in most environments, SAP is only one of many players, and development teams would prefer to standardize on a single version control system, continuous integration server and container technology. But as long as SAP is in play, such standardization is difficult, if not impossible.

For example, version control systems (VCSes) are often linchpins of DevOps infrastructure. Checking in code to a VCS will kick off builds, tests and deployment of code to various system landscapes. These systems tend to rely on the VCS being the canonical repository for the application code, with the VCS at the center of application development processes. However, in most SAP environments, including HANA and ABAP, SAP has decided to make the VCS a secondary tool, with SAP's own Web IDE and Eclipse tools as mediators.