SAP Hana development model-Multi-team product R & D based on SAP Hana Platform

"Basic" Development Mode

Windows:

Unix/Linux:

In basic mode, we can activate our object through Regi. Regi is a git-like command line tool that facilitates interaction with Hana repository.

The procedure is as follows:

1. Create a Hana user key:
   Hdbuserstore set <key> <Hana Server>: <port> <username> <password>
2. Create an Xs Workspace
   Regi create workspace <project folder> <key>
3. Track Xs project packages
   Regi track <package>
4. Submit
   Regi commit
5. Activate a project
   Regi activate

You can use Regi push to complete step 4 and Step 5.

The entire process is used as an example:

Hdbuserstore set hanadev 127.0.0.1: 30015 System Manager

Regi create workspace hanadevelop hanadev

CD hanadevelop

Regi track sap. Hana. Demo

Regi commit

Regi activate

 

"Official" Development Model

+ +Other plug-ins

In the old version of Hana studio, Regi and Hana repository are used for interaction. This is enhanced since rev 70, and Regi is not used. Specific information: http://scn.sap.com/community/developer-center/hana/blog/2013/12/03/sap-hana-sps07--various-new-developer-features

Everything is in Hana, more specifically, repository.

Procedure:

1. Create a new repository package in Hana Studio
2. Create a new project
3. Share a newly created Project through Xs team provider
4. Create an object in the project, commit and activate

Here we already have a good development environment, but how can we debug it? Don't worry. We need some special settings. (This is the debugger on the server side)

Xsengine. ini

• Debugger-enabled: True
• Debugger-listenport: 47112

What do you think? What do you think? Can these development modes be used for large-scale development by multiple teams? It does not seem to match the popular "best practice" on the market.

"Multi-team and large-scale" Development Model

• Use git to manage source code (or P4 or SVN doesn't matter)
• Use Maven to manage projects
• Multiple people work on the same Hana instance, and they are not in the ABAP mode.
• Integrated with a continuous integration system

Maven is used to interact with Hana repository. This plugin implements Regi operations to hide these complex names. You can also use other plugins to interact with Hana repository.

In this development mode, what we want most is:

• Many developers can develop on the same Hana instance.
• Many testers can perform tests on the same Hana instance in multiple versions.

Obviously, the default development mode does not support this idea. How can we do this? Here, we can change the package at the top to configurable.

For example, sap. Hana. Demo becomes $ {rootpackage}. Hana. demo.

Rootpackage can be set based on the employee number of each person. Through Maven configuration, we can easily implement what we want. If you are interested in the specific practice and listen to the next decomposition.

SAP Hana development model-Multi-team product R & D based on SAP Hana Platform