Configuring X.509 Certificates for SAP Single Sign-on
Import, export, and generate the X.509 certificates that secure communication paths between SAP Mobile Server and the SAP enterprise information system (EIS), and for client authentication, including single sign-on (SSO) with X.509 or SSO2 tokens.
Deploying and Configuring DOE-C Packages
Unlike Hybrid App or MBO packages that use SAP Control Center to deploy packages to SAP Mobile Server, you must deploy the DOE-C package to specific domain using the DOE-C command line utility (CLU). Once deployed, the DOE-C package is visible and manageable from SAP Control Center.
Enabling the DOE-C Connection
Configure the SAP® Data Orchestration Engine Connector (DOE-C) connection pool between SAP Mobile Server and the SAP EIS. This is the port on which SAP Mobile Server communicates with the DOE, including forwarding subscriptions and allowing client operations to flow through to the DOE.
Provisioning the Public RSA key from the Messaging Server for MBS Encryption
If you are not using Afaria, you can install the client application, then connect to the corporate LAN using Wi-Fi or other method of your choosing in order to provision devices with required files. This allows you to seed public RSA keys to the device so that over-the-air connections to SAP Mobile Server can be mutually-authenticated and you can minimize the possibility of a rogue server intercepting your initial synchronization and providing its own RSA public key.