Integration Framework - Smart Package
Installer (SPI)
Definition
Smart Package Installer (SPI) refers to the entry point for SAP mobile component installation using a third-party Device Management System. It triggers mobile component installation or uninstallation on the client device after successful deployment. SPI provides several features that are available to users. Those features can be accessed by passing various arguments to SPI at startup. The following tables provide a description for these features:
Deployment Options
Short Description |
Argument |
Description |
Uninstallation |
-U |
Specifies that a mobile component uninstallation is required. When this parameter is not passed the system assumes that mobile component installation is required. |
Installation |
|
The system assumes mobile component installation by default if the uninstallation argument is not passed. |
Trace Options
Short Description |
Argument |
Description |
Trace path |
-TP |
Provides a way for the user to specify a trace file name and location. Use this feature to identify the source of a problem when you are having difficulties installing or uninstalling an SAP mobile component. If the destination folder of the trace file specified does not exist on the client device, SPI creates it automatically. This parameter is optional. |
Trace size |
-TS |
Specifies the maximum trace file size in bytes. This parameter can be used only when a trace path is passed as an argument. Otherwise, the parameter ignored. Whenever the maximum trace file size is reached, the existing trace file extension is renamed to .BAK and a new trace file is created. Only one copy of the .BAK file is maintained. This means that only two cycles of tracing are maintained by the system. This parameter is optional. |
Communication Options
Short Description |
Argument |
Description |
Communications Port |
-P |
Provides a way for a DM administrator to change the default communications port used to communicate with the SAP NetWeaver Mobile Client. The communications port is used to notify the SAP NetWeaver Mobile Client that an SAP mobile component needs to be installed or uninstalled. This parameter is optional. |
The system creates a default log file in the device’s system directory whenever invalid parameters are passed to SPI. The default log file, SPILog.txt, provides a brief description of the error.
Use
SPI [-U] [-TP:”tracefile”] [-TS:SIZE] [-P:PORT]
Example
Mobile Component Installation:
SPI –TP:”c:\\Trace\\trace.log” –TS:5000 –P:45000
Where:
-TP:“c:\\Trace\\trace.log” – Refers to the trace file to be created.
-TS:5000 – Maximum of 5000 bytes for the trace file.
-P:45000 – Port 45000 is used to communicate with the SAP NetWeaver Mobile client.
Mobile Component Uninstallation:
SPI –U –TP:”c:\\Trace\\trace.log” –TS:5000 –P:45000
Where:
-TP:“c:\\Trace\\trace.log” – Refers to the trace file to be created.
-TS:5000 – Maximum of 5000 bytes for the trace file.
-P:45000 – Port 45000 is used to communicate with the SAP NetWeaver Mobile client.