Creating an Application in SAP Business Technology Platform Mobile Services - Neo

Procedure

  1. Using theSAP BTP cockpit, navigate to the Start of the navigation pathServices Next navigation step Development & OperationsEnd of the navigation path tile. If it is not enabled, enable it. Then click the Go to Service link after clicking on the tile.

    The Mobile Service for Development and Operations, or Admin UI view, opens in a new window.

  2. Click the Destinations link on the left, then click New to create a new destination. Fill in the following fields:

    • Type: Mobile destination

    • Destination names: Must match the names of the destinations defined in the Application Metadata.

      • For the SAP Service and Asset Manager application, the default destination name defined in the product release varies based on which version of the application is running. See the following chart for more information:

        SAP Service and Asset Manager Version

        Destination

        SAP Service and Asset Manager 1.1

        DEST_SAM10_PPROP

        SAP Service and Asset Manager 2.0

        DEST_SAM20_PPROP

        SAP Service and Asset Manager 3.0

        DEST_SAM30_PPROP

        SAP Service and Asset Manager 4.0

        DEST_SAM40_PPROP

        SAP Service and Asset Manager 1911

        DEST_SAM1911_PPROP

        SAP Service and Asset Manager 2005

        DEST_SAM2005_PPROP

        SAP Service and Asset Manager 2010

        DEST_SAM2010_PPROP

        SAP Service and Asset Manager 2105

        DEST_SAM2105_PPROP

        SAP Service and Asset Manager 2110

        DEST_SAM2110_PPROP

        SAP Service and Asset Manager 2205

        DEST_SAM2205_PPROP

        SAP Service and Asset Manager 2.0 with Meter Management

        DEST_SMM10_PPROP

        SAP Service and Asset Manager 4.0 online service

        DEST_SAM40_ONLINE_PPROP

        SAP Service and Asset Manager 1911 online service

        DEST_SAM1911_ONLINE_PPROP

        SAP Service and Asset Manager 2005 online service

        DEST_SAM2005_ONLINE_PPROP

        SAP Service and Asset Manager 2010 online service

        DEST_SAM2010_ONLINE_PPROP

        SAP Service and Asset Manager 2105 online service

        DEST_SAM2105_ONLINE_PPROP

        SAP Service and Asset Manager 2110 online service

        DEST_SAM2110_ONLINE_PPROP

        SAP Service and Asset Manager 2205 online service

        DEST_SAM2205_ONLINE_PPROP

      • If the application metadata is edited to use a different destination name than what is defined in the assetmanager.service file, the created destination on the SAP Business Technology Platform Mobile Services must also reflect the service name. For more information on where to find application metadata, see Step 1 of the Building the SAP Asset Manager Application Client procedure.

    • URL: URL to reach the mobile add-on service through the Cloud Connector

      • The URL specified must use the given host name from the virtual host of the Cloud Connector regardless of port specification.

      • Include the full URL path of the OData service in the URL. All of the resources are specified in the ICF nodes that the OData service resides under.

      • If the Cloud Connector connecting to the Mobile Development Kit client is configured to use HTTPS, you do not have to make the HTTPS specification in the URL. Your on-premise connections through a properly configured Cloud Connector should specify a URL using an HTTP scheme, with the HTTP port specified.

      • A sample URL is as follows: http://<cloud connector virtual host>:<cloud connector virtual port> /sap/opu/odata/<mobile add-on component>/<mobile add-on service>, with MERP an example of <mobile add-on component> and SAP_ASSET_MANAGER_<version> an example of <mobile add-on service>.

    • A sample URL is as follows: http://<cloud connector virtual host>:<cloud connector virtual port> /sap/opu/odata/<Mobile Add-On Integration Framework component>/<<Mobile Add-On Integration Framework service>, with MERP an example of < Mobile Add-On Integration Framework component > and SAP_PROD_SUPERVISOR_<version> an example of <Mobile Add-On Integration Framework service>.

    • Proxy Type: On-premise (Cloud Connector)

    • Maximum Connections: However many concurrent users are expected for your application connection

    • Timeout: The timeout for each network transmission between the device and back end system. Settings are based on the following:

      • The expected timeout requirements for the SAP Mobile Add-OnMobile Add-On Integration Framework for SAP S/4HANA on-premise connections to SAP Service and Asset ManagerSAP Shop Floor Manager is 600,000ms.

      • The expected timeout requirements for the SAP Mobile Add-On for SAP ERP ECC6.0 EHP 7 SP14 connections to SAP Service and Asset Manager is 1,200,000ms.

    • Rewrite Mode: Rewrite URL. Setting must match the mapping in the Cloud Connector

      • If the virtual host and the port in the Cloud Connector are set the same as the internal host and the port of the SAP Mobile Add-OnMobile Add-On Integration Framework OData service, you can set the Rewrite Mode to Rewrite URL.

      • If the virtual host and the port in the Cloud Connector do not match the internal host and the port of the SAP Mobile Add-OnMobile Add-On Integration Framework OData service, set the Rewrite Mode to Custom Rewrite URL. Setting the Rewrite Mode to Custom Rewrite URL properly maps the outgoing URLs from the Cloud Connector.

      • OPTIONAL If the Custom Rewrite URL is set, add an outbound rewrite URL when you create system mapping. For more information, see the Rewrite Modes topic.

    • Custom Headers: Not applicable

      • If a default client is not properly set for your oData service, you can override the connected client by adding a custom header with a <Header Key> of sap-client and a <Header Value> of your client number.

    • SSO Mechanism / Authentication: Principal Propagation

      • Principal propagation is the officially supported authentication method between the SAP Service and Asset ManagerSAP Shop Floor Manager and the SAP Mobile Add-OnMobile Add-On Integration Framework. For more information, see the topic Configure Principal Propagation to an ABAP System for HTTPS.

  3. Click the Mobile Applications link on the left, then click Native / Hybrid.

  4. Click the New button. When the New Application window displays, fill the fields as follows:

    • Config Templates: Select Mobile Development Kit from the dropdown

    • ID: Whatever your administrator wishes to use that is meaningful to them. The ID is used to control features on the application and is displayed in branded settings on the client.

    • Name: Name of your application

    • Description: Optional description of your application

    • Vendor: Optional name of your vendor

  5. Click Save to create the preliminary cloud application, then click the newly created cloud application.

    You access the detail screen of your newly created application.

  6. Some Assigned Features need additional configuration, or you can optionally configure them at a later date:

    • App Update: You can configure this later. This setting controls how new metadata definitions are pushed to the Mobile Development Kit clients.

    • Client Policies: Enabled by default. Can control uploading of client error logs to the SAP Business Technology Platform Mobile Services, whether or not passwords are allowed to secure applications, and locking and wiping policies.

      If users need to lock their devices with passwords,select Enable Passcode Policy. You can define the password requirements after selection.

    • Connectivity: Additional configuration needed (performed in the Step 8). How the SAP Business Technology Platform communicates with the back end.

    • Offline: See

    • Push Notification: See the procedure

    • Security: Additional configuration needed (performed in the current procedure). How authentication is performed.

  7. Optional: To debug an existing application, click the Client Policies link and ensure the following logs are enabled:

    Set the log levels for the lowest level you wish to see logs. For example:

    • ERROR: Displays only errors

    • PATH: Displays everything that can show up in the logger

  8. Click the Connectivity link.

    The Connectivity window displays.

  9. Select the Add Destination button (). Then select the appropriate destination that you defined in Step 2 of this procedure.
  10. Save your changes. Click back to your new application and click the Security link.

    The Security window displays.

  11. In the Security Configuration dropdown field, select OAuth. Save your changes, click back into the main application window to refresh the configuration. Then click the Security link again to enter the Security window.

    The Security window displays with new OAuth Client section visible.

  12. Click an OAuth client to view or change the following settings:

    • Token Lifetime: Default is set to 0, which is infinite (never expires)

    • Refresh Token Lifetime: Default is set to 0, which is infinite (never expires)

    • Redirect URL: If enabling certificate-based authentication, ensure the field contains the same samclientsfmclient URL scheme that is contained in the Onboarding URL scheme. The redirect URL must also match the redirect URL defined for the SAP Service and Asset ManagerSAP Shop Floor Manager application.

      See the following screenshot for an example.

    Make a note of the following settings, as you need them later:during the procedure:

    • Client ID

    • Authorization Endpoint

    • Token Endpoint

  13. Click back to the main application page and click the APIs tab. Make a note of the Server setting, minus the trailing /, as you need it laterduring the procedure.