Page tree
Skip to end of metadata
Go to start of metadata

OSGi services provided by SAP ECTR

OSGi services provided by SAP ECTR are services that are supposed to be used by third party extensions.

The following OSGI Services are available:

OSGi serviceDescription

Available since SAP ECTR Version

RfcExecutor

RfcExecutor provides possibility to execute RFC modules on Backend ECTR connected to.

5.1.1.0
PlmLoggerPlmLogger can be used to log messages to the PLM log file.5.1.1.0

PlmDictionary

PlmDictionary provides access to the PLM dictionary.

5.1.5.0

PlmEnvironmentPlmEnvironment provides access to the PLM environment.5.1.5.0
PlmLogonDataPlmLogonData is an interface which provides information about the connected ECTR Backend, like destination, username and so on.5.1.5.0
PlmPreferencesPlmPreferences provides access to preferences5.1.8.1

ResourceAccessor

ResourceAccessor provides access to resources like icons and images

5.1.15.0
ObjectListServiceWith ObjectListService it is possible to manage object lists in ECTR.5.2.3.0
DisplayTableSelectionDialogServiceDisplayTableSelectionDialogService displays objects in an object selection dialog and lets the user select them.5.2.4.0
NotificationBroadcastingServiceNotificationBroadcastingService informs the user when there are new SAP inbox messages.5.2.5.0
ExpandObjectListExpandObjectList  expands an object list with the specified name.
5.2.6.0
GetObjectListNamesGetObjectListNames provides names of all available object lists.5.2.6.0

PlmCacheController

PlmCacheController clears the content of the cache. Since all data has to be read again afterwards, which may harm performance, use this service only when cache data is certainly invalid for some reason.5.2.6.0
OperationCreateService OperationCreateService makes it possible to enhance operations in attribute creation and transfer (attributes-from-sap.xml and attributes-to-sap.xml).5.2.6.0

Please note that names of add-ons mustn't contain spaces.

Allowed characters are: [A-Za-z0-9,\-\+\.]

In order to avoid conflicts, we recommend adhering to JAVA package naming conventions.
Quote: “Companies use their reversed Internet domain name to begin their package names—for example, com.example.mypackage for a package named mypackage created by a programmer at example.com.”

Source: https://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html    

Examples for partner solutions: "com.cideon.conversionEngineCockpit", "com.dot.riess.copyAssistent", "com.dscsag.keepassLogon", ...