trm-server

Minimum tested release: SAP_BASIS 702 SP12 (SAP ECC 6.0 EHP2)

trm-server is the server-side component of TRM.

🚚 TRM (Transport Request Manager) is an open-source package manager for SAP ABAP that publishes, installs, updates, and uninstalls versioned software through CTS transports.

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

Note

If you're looking for the REST implementation of trm-server, head over to trm-rest

It acts as the secure bridge between the SAP application server and the TRM client.

It exposes the APIs that allow TRM to import/export transports, and, as a consequence, it must be installed only on source and target systems, as its not required on any other system in the landscape.

              ┌──────────────────────────┐
              │        TRM Client        │
              └─────────────┬────────────┘
                            │
                            │  System Connector
                            │  (RFC SDK / REST / BTP / ...)
                            ▼
              ┌──────────────────────────┐
              │        trm-server        │
              │  (Installed on SAP)      │
              └─────────────┬────────────┘
                            │
                            │  Native SAP APIs
                            ▼
              ┌──────────────────────────┐
              │        SAP System        │
              └──────────────────────────┘

Documentation

Full documentation can be seen at https://docs.trmregistry.com.

Basic Usage

In a typical scenario, TRM Client connects to a SAP system through a System Connector (RFC SDK, REST, BTP, etc.).
After checking that trm-server is installed on the system, the client uses its APIs to perform secure and controlled transport export and import operations.
If not installed, the client can still communicate directly with the SAP system, but with limited capabilities and without extended TRM features.

Server setup

trm-server is the server-side component of TRM.

It acts as the secure bridge between the SAP application server and the TRM client.

It exposes the APIs that allow TRM to import/export transports, and, as a consequence, it must be installed only on source and target systems, as its not required on any other system in the landscape.

First Installation

The first installation must be performed using the standalone installer.

The standalone installer is a self-contained ABAP report that allows the installation of trm-server and trm-rest.
The installer imports trm-server transports (and trm-rest transports, if necessary) into your system and automatically moves their objects into the temporary package(s) $TRM/$TRM_*, which it also creates.
The installer does not import the /ATRM/ namespace because trm-server and trm-rest are intended to be used as-is. If you need to modify their objects, consider installing them via abapGit instead.

After the initial installation, we recommend installing subsequent updates through TRM.

1. Download the report source code from here
2. Open transaction SE38 and create a new report called ZTRM_INSTALLER

3. Give it a title and set the type to "Executable program"

4. Save as a local object (or in temporary package $TMP)

5. Paste or upload the report's source code, then activate it

Release file install (From file)

Download the releases

1. Go to https://trmregistry.com and search for trm-server
2. On the release page, select Download
3. Download trm-rest too, if needed
4. Open SE38 and run ZTRM_INSTALLER
5. Select the file(s) downloaded
6. Execute the report and wait for the installation to complete (approximately 10 minutes)

Installation of either package can be performed at any time through this report. However, you should consider using a TRM client when upgrading trm-server or trm-rest.

Authorize Users

Grant each SAP user who needs to use TRM authorization object ZTRM_AUTH with activity ACTVT = 16 (Execute), typically through an assigned role.

For security reasons, TRM does not allow a user to execute its functions unless the user has this authorization.

Verify RFC Authorization

To verify that a user has access to RFC functions:

1. Log into the system as the user you want to test
2. Execute function module /ATRM/PING

If the user is authorized, no errors should occur. If not authorized, access will be denied.

Install with abapGit

Because this package uses the /ATRM/ namespace, installation through abapGit requires a system with this namespace installed.

Installing via abapGit is not recommended unless you are planning to contribute new features or bug fixes.

Demo systems

If you are running a demo system, you can use the following keys:

Development key: 18531191373370851361
Repair key: 00211665563784583720

Other systems

For abapGit to work, you need to generate a valid developer key using the Development Namespace Application.

Contributing

Like every other TRM open-soruce 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.