trm-client 9.2.0 → 9.4.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -121
- package/changelog.txt +9 -0
- package/dist/command/AbstractCommand.js +0 -12
- package/dist/utils/logError.js +6 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -62,143 +62,33 @@ Full documentation can be seen at [https://docs.trmregistry.com/](https://docs.t
|
|
|
62
62
|
---
|
|
63
63
|
|
|
64
64
|
<!-- START OF SETUP.MD -->
|
|
65
|
+
# Install via Npm
|
|
65
66
|
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
If you are using [Docker](https://www.docker.com/), the recommended approach is to use [trm-docker](https://github.com/RegestaItalia/trm-docker).
|
|
69
|
-
|
|
70
|
-
## Download Docker Run Script
|
|
71
|
-
|
|
72
|
-
This script is a small utility used to run TRM inside Docker. After installing the required SAP proprietary tools, the script can be moved into a directory included in your `PATH` so that it can be executed from anywhere.
|
|
73
|
-
|
|
74
|
-
1. Go to the [trm-docker repository](https://github.com/RegestaItalia/trm-docker)
|
|
75
|
-
2. Download the script corresponding to your operating system:
|
|
76
|
-
- **Windows**: download [win.cmd](https://raw.githubusercontent.com/RegestaItalia/trm-docker/refs/heads/main/win.cmd) and rename it to `trm.cmd`
|
|
77
|
-
- **macOS / Linux**: download [macos](https://raw.githubusercontent.com/RegestaItalia/trm-docker/refs/heads/main/macos), rename it to `trm`, and make it executable:
|
|
78
|
-
```bash
|
|
79
|
-
chmod +x trm
|
|
80
|
-
```
|
|
81
|
-
3. In the same directory where you placed the script, create a folder named `init`.
|
|
82
|
-
|
|
83
|
-
This `init` folder will later contain the SAP proprietary files required by TRM.
|
|
84
|
-
|
|
85
|
-
## Download SAPCAR and SAPEXE and Extract Required Files
|
|
86
|
-
|
|
87
|
-
SAPCAR is used to extract `.SAR` archives downloaded from SAP Software Center.
|
|
88
|
-
|
|
89
|
-
### Download SAPCAR
|
|
90
|
-
|
|
91
|
-
1. Log in to the [SAP Software Center](https://me.sap.com/softwarecenter)
|
|
92
|
-
2. Click **SUPPORT PACKAGES & PATCHES**
|
|
93
|
-
3. Expand **By Alphabetical Index (A–Z)** and select **S**
|
|
94
|
-
4. Click **SAPCAR**
|
|
95
|
-
5. Choose the **latest version**
|
|
96
|
-
6. On the download page select your operating system:
|
|
97
|
-
- **WINDOWS ON X64 64BIT**
|
|
98
|
-
- **MACOS ON ARM64BIT**
|
|
99
|
-
- **MACOS X 64-BIT**
|
|
100
|
-
7. Download:
|
|
101
|
-
- **Windows** → latest `.EXE`
|
|
102
|
-
- **macOS** → latest `.ZIP`
|
|
103
|
-
8. If using macOS, extract the archive and make the binary executable:
|
|
104
|
-
```bash
|
|
105
|
-
chmod +x SAPCAR
|
|
106
|
-
```
|
|
107
|
-
|
|
108
|
-
### Download SAP Kernel Files
|
|
109
|
-
|
|
110
|
-
1. Go back to **SUPPORT PACKAGES & PATCHES**
|
|
111
|
-
2. Expand **By Alphabetical Index (A–Z)** and select **K**
|
|
112
|
-
3. Click **SAP KERNEL 64-BIT**
|
|
113
|
-
4. Choose the **latest version**
|
|
114
|
-
5. On the download page select **LINUX ON X86_64 64BIT**
|
|
115
|
-
6. Download the latest **SAPEXE** archive
|
|
116
|
-
(file name similar to `SAPEXE_###-########.SAR`)
|
|
117
|
-
|
|
118
|
-
### Extract the Required Files
|
|
119
|
-
|
|
120
|
-
1. Place the downloaded `SAPEXE_*.SAR` file in the same directory as `SAPCAR`.
|
|
121
|
-
2. Extract it:
|
|
122
|
-
|
|
123
|
-
**Windows**
|
|
124
|
-
```bash
|
|
125
|
-
SAPCAR -xvf SAPEXE_###-########.SAR
|
|
126
|
-
```
|
|
127
|
-
|
|
128
|
-
**macOS / Linux**
|
|
129
|
-
```bash
|
|
130
|
-
./SAPCAR -xvf SAPEXE_###-########.SAR
|
|
131
|
-
```
|
|
132
|
-
|
|
133
|
-
3. After extraction, move the following files into the previously created `init` folder:
|
|
134
|
-
|
|
135
|
-
```
|
|
136
|
-
R3trans
|
|
137
|
-
libicudata##.so
|
|
138
|
-
libicui18n##.so
|
|
139
|
-
libicuuc##.so
|
|
140
|
-
```
|
|
141
|
-
|
|
142
|
-
4. *(Optional)* If you want RFC functionality available in TRM, also move the following files into the `init` folder:
|
|
143
|
-
|
|
144
|
-
```
|
|
145
|
-
startrfc
|
|
146
|
-
rfcexec
|
|
147
|
-
libsapnwrfc.so
|
|
148
|
-
libsapucum.so
|
|
149
|
-
```
|
|
150
|
-
|
|
151
|
-
## Pull docker image
|
|
152
|
-
|
|
153
|
-
Execute this command to pull the latest docker image
|
|
67
|
+
With [Node.js and npm](https://nodejs.org/en/download) installed, you can install [trm-client](https://www.npmjs.com/package/trm-client) via npm, as it is distributed as a Node.js package.
|
|
154
68
|
|
|
155
69
|
```bash
|
|
156
|
-
|
|
70
|
+
npm install -g trm-client
|
|
157
71
|
```
|
|
158
72
|
|
|
159
|
-
##
|
|
73
|
+
## Connect to SAP via RFC
|
|
160
74
|
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
**Windows**
|
|
164
|
-
```bash
|
|
165
|
-
trm
|
|
166
|
-
```
|
|
75
|
+
If you wish to connect to an SAP system via RFC, install the requirements for [node-rfc](https://github.com/SAP-archive/node-rfc) and execute
|
|
167
76
|
|
|
168
|
-
**macOS / Linux**
|
|
169
77
|
```bash
|
|
170
|
-
|
|
78
|
+
npm install -g node-rfc
|
|
171
79
|
```
|
|
172
80
|
|
|
173
|
-
|
|
174
|
-
After the installation completes, you may move the script to a directory included in your system `PATH` so it can be executed from anywhere.
|
|
81
|
+
RFC should now be available as an option when trying to connect to a system.
|
|
175
82
|
|
|
176
|
-
|
|
177
|
-
```
|
|
178
|
-
C:\Windows\System32
|
|
179
|
-
```
|
|
83
|
+
## Connect to SAP via BTP
|
|
180
84
|
|
|
181
|
-
|
|
182
|
-
```
|
|
183
|
-
/usr/local/bin
|
|
184
|
-
```
|
|
185
|
-
|
|
186
|
-
After this step, you can simply run:
|
|
85
|
+
If you wish to connect to an SAP system via BTP exposed destination, install the requirements for [trm-plugin-btp-dest](https://github.com/RegestaItalia/trm-plugin-btp-dest) and execute
|
|
187
86
|
|
|
188
87
|
```bash
|
|
189
|
-
trm
|
|
88
|
+
npm install -g trm-plugin-btp-dest
|
|
190
89
|
```
|
|
191
90
|
|
|
192
|
-
|
|
193
|
-
|
|
194
|
-
---
|
|
195
|
-
|
|
196
|
-
# Install via Npm
|
|
197
|
-
|
|
198
|
-
With [Node.js and npm](https://nodejs.org/en/download) installed, you can install [trm-client](https://www.npmjs.com/package/trm-client) via npm, as it is distributed as a Node.js package.
|
|
199
|
-
|
|
200
|
-
## TODO
|
|
201
|
-
|
|
91
|
+
BTP should now be available as an option when trying to connect to a system.
|
|
202
92
|
<!-- END OF SETUP.MD -->
|
|
203
93
|
|
|
204
94
|
---
|
package/changelog.txt
CHANGED
|
@@ -8,6 +8,15 @@ Legend
|
|
|
8
8
|
+ : added
|
|
9
9
|
- : removed
|
|
10
10
|
|
|
11
|
+
2026-06-15 v9.4.0
|
|
12
|
+
-------------------
|
|
13
|
+
! trm-core ^9.8.0
|
|
14
|
+
- tmp remove of useR3trans
|
|
15
|
+
|
|
16
|
+
2026-05-26 v9.3.0
|
|
17
|
+
-------------------
|
|
18
|
+
! trm-core ^9.7.0
|
|
19
|
+
|
|
11
20
|
2026-05-11 v9.2.0
|
|
12
21
|
-------------------
|
|
13
22
|
! trm-core ^9.6.0
|
|
@@ -377,18 +377,6 @@ class AbstractCommand {
|
|
|
377
377
|
yield Commons.Plugin.call("client", "loadCommons", { commons: Commons });
|
|
378
378
|
Commons.Inquirer.inquirer = this.getInquirer(InquirerType_1.InquirerType.CLI);
|
|
379
379
|
Commons.Logger.logger = this.getLogger(this.args.logger, this.args.debug, this.args.loggerOutDir);
|
|
380
|
-
const useDocker = utils_1.GlobalContext.getInstance().getSettings().r3transDocker;
|
|
381
|
-
if (this.registerOpts.requiresR3trans && useDocker) {
|
|
382
|
-
Commons.Logger.info(`This command needs R3trans program dockerized.`);
|
|
383
|
-
Commons.Logger.loading(`Checking if docker is running...`);
|
|
384
|
-
if (yield (0, utils_1.isDockerRunning)()) {
|
|
385
|
-
const dockerName = utils_1.GlobalContext.getInstance().getSettings().r3transDockerName;
|
|
386
|
-
Commons.Logger.info(`Docker "${dockerName || 'local/r3trans'}" will be used.`);
|
|
387
|
-
}
|
|
388
|
-
else {
|
|
389
|
-
throw new Error(`Command needs R3trans dockerized, docker engine is not currently running.`);
|
|
390
|
-
}
|
|
391
|
-
}
|
|
392
380
|
if (process.platform !== 'win32' && process.platform !== 'darwin' && process.platform !== 'linux') {
|
|
393
381
|
Commons.Logger.warning(`Running on untested OS "${process.platform}"! Some features aren't tested yet.`);
|
|
394
382
|
}
|
package/dist/utils/logError.js
CHANGED
|
@@ -68,7 +68,12 @@ function logError(err) {
|
|
|
68
68
|
if (restClientError.restError.status === 404) {
|
|
69
69
|
aError.push(`${chalk_1.default.black.bgRed(restClientError.restError.status)} Service cannot be reached (Check if trm-rest is installed and activated correctly).`);
|
|
70
70
|
}
|
|
71
|
-
|
|
71
|
+
if (restClientError.restError.status) {
|
|
72
|
+
sError = `${chalk_1.default.black.bgRed(restClientError.restError.status)} ${sError}`;
|
|
73
|
+
}
|
|
74
|
+
else {
|
|
75
|
+
sError = `${sError}`;
|
|
76
|
+
}
|
|
72
77
|
}
|
|
73
78
|
}
|
|
74
79
|
if (sError) {
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "trm-client",
|
|
3
|
-
"version": "9.
|
|
3
|
+
"version": "9.4.0",
|
|
4
4
|
"description": "TRM (Transport Request Manager) Client",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"types": "dist/index.d.ts",
|
|
@@ -48,7 +48,7 @@
|
|
|
48
48
|
"sanitize-filename": "^1.6.3",
|
|
49
49
|
"semver": "^7.7.4",
|
|
50
50
|
"trm-commons": "^5.0.0",
|
|
51
|
-
"trm-core": "^9.
|
|
51
|
+
"trm-core": "^9.8.0",
|
|
52
52
|
"trm-registry-types": "^2.1.0",
|
|
53
53
|
"xml2js": "^0.6.2"
|
|
54
54
|
},
|