How Connections Are Registered

Connection registration occurs after the user, device, and application are recognized and assigned to a connection. This multi-way grouping creates a unique connection in SAP Control Center, so the registered connection activity can be monitored.

The process by which a user becomes recognized depends on whether:

The real identity need to be established with by SAP Mobile Server or by the EIS data source. SAP recommends using an identity to recognize the user.
The degree of manual intervention required to complete registration.

Once the connection is registered, the platform administrator can view the application user that is associated with the activated application connection; however, the user name displayed is not necessarily same as an authenticated user identity. Consider:

Only automatic registrations use the extracted user identity.
For manual activation code-based registration, the administrator can freely name the user. The relationship between user name and application connection is established when you click the Package Users button for an in-bound connection.
No user names appear for anonymous role-based registration.

Note: SAP applications that have connections registered with SAP Mobile Server, can also have licenses counted by SAP License Audit service. For a list of SAP applications for which licenses are counted, see SAP Applications Tracked with SAP License Audit in System Administration.

Automatic Connection Registration with Identities
Automatic connection registration is the process by which a user and application ID is paired to an connection by using the authentication identity. It is considered automatic, because the administrator does not need to manually create this pairing by selecting the in-bound connection and registering it in SAP Control Center.
Manual Connection Registration with Activation Codes
Activation codes are an alternate way to complete the connection registration process. It is considered a manual registration method because users must enter the supplied activation code before administrators can manually register the inbound connection request.
Anonymous Connection Registration
(Recommended only for online applications) In large business-to-customer deployments, application design may support anonymous user connections to SAP Mobile Server.
When Reregistration is Required
Because the assignment of connections and resources occurs after applications, identities, and devices are paired, then reregistration is required when this association breaks or requires a different pairing.

Parent topic: The Activation Process