Glossary

Key terms that are used in/by the UDEP

Sl.	Term	Definition
1.	Company / Domain	UDEP is a multi-tenant platform. Each tenant is identified by a Company ID (also called as Domain). For e.g. the domain for Unvired Inc. is UNVIRED
2.	SA	SuperAdmin user who is automatically created for every company, The SA user can perform all operations within a company and has unfettered access similar to a root account. Use with care.
3.	Users	Users registered on the UDEP who can be Administrators, Developers or Application users. Additionally users can have Frontend users (devices) attached to them. They can also have backend users which refers to their individual credentials on these systems. If the login to apps is via a different identity management system such as MS ADS they can also have Federation users attached.
4.	Groups	Groups of users who can be deployed applications to se, run schedules for etc.
5.	Backend System	The systems that applications deployed in the UDEP connect to. Some examples are SAP S4/HANA, SAP ECC, SFDC, databases like MySQL, MSSQL etc.
6.	Backend Port	The port that is configured on a system. This is synonymous to a network port but in addition also identifies the service the port is configured for. For e.g. RFC is a port on SAP systems and identifies both the port to connect to and that the protocol is SAP RFC. Similarly HTTP(S) service on port 80/443 etc.
7.	Backend Function	A function that can be executed by a UDEP application. Each function is provided by a Port and determines the type of function. For e.g. an RFC function is provided by an SAP PORT that is available from an SAP Backend System. Similarly a REST endpoint (function) is provided by a REST PORT on an HTTP(S) Web Server Backend System.
8.	ME System	ME is a special system in the UDEP landscape and refers to the system on which the UDEP platform is deployed and running. All Process Agent Java functions are attached to the Java Port of the ME system.
9.	Application	An Application is the set of Functions that a Frontend (device or client) connects to for executing the required functionality.
10.	Library	A Library extends the functionality provided by an Application by adding more functions.
11.	Application Properties	Application Properties are a standard set of properties that can be configured for an application. These are defined by UDEP and can be configured based on need. For e.g. the output of the application (JSON or XML) can be controlled via an App Property.
12.	Application Deployment	This refers to the process of making applications available to users on the platform. Administrators can deploy applications for users or teams.
13.	Application Activation	Once users login to the application via their credentials, the deployed application is marked as active on the specified device.
14.	Process Agent	Process Agent or PA is the binary Application that will be executed in the UDEP Java Runtime when a function is invoked, The binary Jar file is obtained by compiling the Process Agent project in the Eclipse Modeler. All Process Agent functions are attached to the JAVA Port of the ME system.
15.	Process Agent Settings	These are Key-Value pairs that can be saved and accessed programmatically on the UDEP. PA Settings can be App related or can be specific to the users accessing the application. Custom configuration of an app can be stored as PA App Settings and user specific configuration and customization information can be stored as PA App User settings.
16.	Frontend	Refers to the devices or clients that the UDEP is aware of to receive incoming requests and to push messages to. These include iPhone, iPad, Android Phones and Tablets, Windows Tablets, Browsers and other Servers.
17.	Sync Requests (Messages)	Synchronous or Sync refer to all the requests that are posted by the mobile and web applications to the UDEP platform synchronously for execution and receive the result of execution immediately.
18.	Async Requests (Messages)	Asynchronous or Async refer to all the requests that are posted by the mobile and web applications to the UDEP platform asynchronously for execution and receive an acknowledgement immediately upon queuing. The request is subsequently processed and result is queued for delivery to the mobile devices.
19.	REST Request	Web Apps and other server integrations are executed on the UDEP by using REST APIs provided by UDEP. These are then queued either Sync or Async based on the execution mode.