Optimizing ABAP development as a service
A development account is provisioned, the provisioning including a request for a backing service. The backing service includes: generating a developer schema in a database, generating a table link in the developer schema to shared tables required for the new development environment, generating a delta table, and generating a union view with a defined instead-of-trigger used to write, update, or delete from the delta table upon a write, update, or delete operation on the union view. A runtime application server is obtained and a repository is configured in a version control system. The runtime application server is configured to connect to the generated developer schema of the provisioned development account, and an identifier is provided to the provisioned development account.
1. A computer-implemented method, comprising:
provisioning an isolated ABAP development account, the provisioning including a request for a backing service, comprising:
generating a developer schema in a database;
generating a table link in the developer schema to read only shared tables required for the new development environment;
generating a delta table; and
generating a union view reading data from the delta table and a shared table corresponding to the delta table;
obtaining a runtime application server, the runtime application server writing to the delta table and reading from the delta table and the shared table corresponding to the delta table;
configuring a repository in a version control system by:
determining if content associated with the provisioned development account already exists in the version control system;
if content exists:
receiving a selection of a repository in the version control system to use;
syncing content associated with the selected repository to a file system directory structure;
calling a tool to create a deployment file out of the content associated with the selected repository;
calling a deploy tool to deploy the deployment file to the provisioned development account;
configuring the runtime application server to connect to the generated developer schema of the provisioned development account;
providing an identifier to the provisioned development account, the identifier identifying the repository; and
using the identifier, importing changes to content in the provisioned development account into the repository.
2. The computer-implemented method of claim 1 , wherein the table link links to a master database schema.
3. The computer-implemented method of claim 1 , wherein the delta table has the same structure as the shared table corresponding to the delta table.
4. The computer-implemented method of claim 1 , wherein the union view selects from the delta table if content exists, otherwise from the shared table.
5. The computer-implemented method of claim 1 , comprising:
changing code or content in the development account;
writing changes to the code or content to a transport order; and
once the transport is released, the transport is exported to a file system and imported to the version control system repository.
6. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
provisioning an isolated ABAP development account, the provisioning including a request for a backing service, comprising:
generating a developer schema in a database;
generating a table link in the developer schema to read only shared tables required for the new development environment;
generating a delta table; and
generating a union view reading data from the delta table and a shared table corresponding to the delta table;
obtaining a runtime application server, the runtime application server writing to the delta table and reading from the delta table and the shared table corresponding to the delta table;
configuring a repository in a version control system by:
determining if content associated with the provisioned development account already exists in the version control system;
if content exists:
receiving a selection of a repository in the version control system to use;
syncing content associated with the selected repository to a file system directory structure;
calling a tool to create a deployment file out of the content associated with the selected repository;
calling a deploy tool to deploy the development file to the provisioned development account;
configuring the runtime application server to connect to the generated developer schema of the provisioned development account;
providing an identifier to the provisioned development account, the identifier identifying the repository; and
using the identifier, importing changes to content in the provisioned development account into the repository.
7. The non-transitory, computer-readable medium of claim 6 , wherein the table link links to a master database schema.
8. The non-transitory, computer-readable medium of claim 6 wherein the delta table has the same structure as the shared table corresponding to the delta table.
9. The non-transitory, computer-readable medium of claim 6 , wherein the union view selects from the delta table if content exists, otherwise from the shared table.
10. The non-transitory, computer-readable medium of claim 6 , comprising:
changing code or content in the development account;
writing changes to the code or content to a transport order; and
once the transport is released, the transport is exported to a file system and imported to the version control system repository.
11. A computer system, comprising:
a computer memory; and
a hardware processor interoperably coupled with the computer memory and configured to perform operations comprising:
provisioning an isolated ABAP development account, the provisioning including a request for a backing service, comprising:
generating a developer schema in a database;
generating a table link in the developer schema to read only shared tables required for the new development environment;
generating a delta table; and
generating a union view reading data from the delta table and a shared table corresponding to the delta table;
obtaining a runtime application server, the runtime application server writing to the delta table and reading from the delta table and the shared table corresponding to the delta table;
configuring a repository in a version control system by:
determining if content associated with the provisioned development account already exists in the version control system;
if content exists:
receiving a selection of a repository in the version control system to use;
syncing content associated with the selected repository to a file system directory structure;
calling a tool to create a deployment file out of the content associated with the selected repository;
calling a deploy tool to deploy the deployment file to the provisioned development account;
configuring the runtime application server to connect to the generated developer schema of the provisioned development account;
providing an identifier to the provisioned development account, the identifier identifying the repository; and
using the identifier, importing changes to content in the provisioned development account into the repository.
12. The computer system of claim 11 , wherein the table link links to a master database schema.
13. The computer system of claim 11 , wherein the delta table has the same structure as the shared table corresponding to the delta table.
14. The computer system of claim 11 , wherein the union view selects from the delta table if content exists, otherwise from the shared table.
15. The computer system of claim 11 , comprising:
changing code or content in the development account;
writing changes to the code or content to a transport order; and
once the transport is released, the transport is exported to a file system and imported to the version control system repository.