Skip to content

RegestaItalia/trm-docs

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

118 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

🚚 TRM (Transport Request Manager)

Contributor Covenant View Code Wiki

trm-client version trm-server version trm-core version trm-registry-types version

trm-registry roadmap stage

πŸš€ This project is funded and maintained by 🏦 πŸ”—
Regesta S.p.A. https://www.regestaitalia.eu/
Clarex S.r.l. https://www.clarex.it/

TRM (Transport Request Manager) is a package manager inspired solution built leveraging CTS that simplifies SAP ABAP transports.

TRM Logo

TRM introduces package-based software delivery to the SAP ecosystem, bringing with it semantic versioning, dependency management, and automated deployment activities.


What is TRM?

TRM is a software that transforms how custom ABAP developments are published, installed, and maintained across SAP landscapes. Inspired by modern package managers, TRM introduces a declarative, version-controlled, and automated way to manage your SAP transports.

With TRM, you can:

  • Define a manifest for each ABAP package (similar to package.json with Node.js or pom.xml with Maven)
  • Version your products (SemVer compliance)
  • Declare dependencies (to other TRM packages, SAP standard objects, or customizing data)
  • Automate post-install activities, such as client dependant customizing, cache invalidation etc.
  • Validate system requirements prior to installation
  • Compare versions of the same product across multiple SAP systems (in or outside the same landscape)
  • Distribute your product release to the public or to a restricted number of users:
    • Registry (e.g., trmregistry.com or private registry)
    • Local .trm files for offline installations

Modern approach for ABAP

  • Publish ABAP packages from a central development system
  • Deliver packages to target systems (outside of the original landscape e.g. customers development system) using a single CLI command (or in a pipeline)
  • Full support for workbench objects, customizing, and translations

Structured Manifest

Each package includes a manifest.json that declares:

  • Version and metadata
  • System requirements
  • Dependencies
  • Post-install scripts

Architecture Overview

  • Server: Collection of APIs installed on source and destination systems
  • Client: Command-line interface that talks with SAP instances
  • Registry: Cloud registry where package releases are safely stored for end users to install

Contributors

Like every other TRM open-source projects, contributions are always welcomed ❀️.

Make sure to open an issue first.

Contributions will be merged upon approval.

Click here for the full list of TRM contribution guidelines.

About

🚚 TRM (Transport Request Manager) Documentation

Topics

Resources

License

Code of conduct

Contributing

Stars

Watchers

Forks

Contributors