SAP Asset Manager Installation Guide THE BEST RUN. PUBLIC SAP Asset Manager Document Version:

(1)

PUBLIC

SAP Asset Manager

Document Version: 2105 – 2021-06-16

SAP Asset Manager Installation Guide

(2)

Content

1 SAP Asset Manager Architecture. . . .4

1.1 SAP Business Technology Platform Overview. . . . 4

SAP Business Technology Platform Mobile Services Overview. . . .7

SAP Business Technology Platform SDK Overview. . . . 8

2 Deployment and Configuration of SAP Asset Manager. . . .9

2.1 High-Level Installation Process for SAP Asset Manager. . . . 9

2.2 Relevant SAP Notes. . . . 10

2.3 Installation Prerequisites. . . . 11

2.4 Setting up the SAP Business Technology Platform Cloud Connector System Mapping. . . .12

2.5 Creating an Application in SAP Business Technology Platform Mobile Services - Overview. . . .13

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

Creating an Application in SAP Business Technology Platform Mobile Services - Cloud Foundry . . . . 18

2.6 Enabling the Mobile Development Kit. . . . 22

Importing Metadata Definitions to the SAP Web IDE Mobile Development Kit. . . .22

Deploying Metadata Definitions to Mobile Services. . . .24

3 Building / Branding the SAP Asset Manager Application. . . .26

3.1 Building the SAP Asset Manager Application Overview. . . .26

3.2 Building the SAP Asset Manager Application Client. . . . 27

Allowing Custom URI Schemes. . . .34

Customizing Map Icons. . . . 37

4 Updating Offline Settings for the SAP Asset Manager Application. . . .39

4.1 Updating Offline Settings for SAP Asset Manager Overview. . . . 39

Using the OData Offline Configuration Builder to Update Offline OData Settings. . . .39

4.2 SAP Asset Manager Entity Sets. . . . 44

(3)

Document History

Before you begin reading this guide, be sure that you have the latest version. Find the latest version at https://

help.sap.com/viewer/p/SAP_ASSET_MANAGER.

The following table provides an overview of the most important document changes.

Document Version Date Description of Changes

1.0 JUN 2021 Original release of the SAP Asset Man

ager Installation guide, version 2105

(4)

1 SAP Asset Manager Architecture

1.1 SAP Business Technology Platform Overview

SAP Business Technology Platform enables customers and partners to rapidly build, deploy, and manage cloud-based enterprise applications that complement and extend your SAP or non-SAP solutions, either on- premise or on-demand.

 Note

For more information on prerequisites and procedures for setting up customer accounts on SAP Business Technology Platform, see the topic Getting Started with a Customer Account: Workflow in the Neo and Cloud Foundry environment.

SAP Business Technology Platform is an in-memory cloud platform based on open standards. It provides access to a feature-rich, easy-to-use development environment in the cloud. The platform includes a comprehensive set of services for integration, enterprise mobility, collaboration, and analytics.

As a Platform-as-a-Service operated by SAP, our product frees your administrators from any infrastructure and IT costs and offers state-of-the art quality of service.

Scenarios

(5)

● Develop new cloud applications

This scenario is suitable for companies that need to start developing new applications from scratch. You can create brand new cloud applications and reach your end customers easily, with a low learning curve and small capital investment in software and hardware.

● Develop on-premise extensions

This scenario is suitable for companies that have already invested a lot in on-premise IT infrastructure. You can create the new extensions to the system on the cloud, and integrate seamlessly with the on-premise components using Connectivity Service and Cloud Connector.

● Develop cloud extensions

At SAP Business Technology Platform, you can also develop extensions to other cloud products, such as SuccessFactors.

Application development

You can use the following programming models to build highly scalable applications:

● Java - SAP Business Technology Platform is Java EE 6 Web Profile certified. You can develop Java applications just like for any application server. You can also easily run your existing Java applications on the platform.

● SAP HANA - you can use the SAP HANA development tools to create comprehensive analytical models and build applications with SAP HANA programmatic interfaces and integrated development environment.

● HTML5 - you can easily develop and run lightweight HTML5 applications in a cloud environment.

● SAPUI5 - use the UI Development Toolkit for HTML5 (SAPUI5) for developing rich user interfaces for modern Web business applications.

Solutions

In the context of SAP Business Technology Platform, a solution is comprised of various application types and configurations created with different technologies, and is designed to implement a certain scenario or task flow. You can deploy solutions by using the Change and Transport System (CTS+) tool, the console client, or by using the cockpit, where you can also monitor your solutions. To describe and technically realize the solutions, SAP Introduces the multi-target application (MTA) model. It encompasses and describes application modules, dependencies, and interfaces in an approach that facilitates validation, orchestration, maintenance, and automation of the application throughout its lifecycle.

Runtime container for applications

Applications developed on SAP Business Technology Platform run in a modular and lightweight runtime container. The platform provides a secure, scalable runtime environment with reusable platform services.

(6)

Virtual Machines

Virtual machines allow you to install and maintain your own applications in scenarios not covered by the platform. A virtual machine is the virtualized hardware resource (CPU, RAM, disk space, installed OS) that blends the line between Platform-as-a-Service and Infrastructure-as-a-Service.

Services

You can consume a set of services provided by SAP Business Technology Platform according to the technology you prefer and the use cases of your scenarios.

Integration with SAP and non-SAP software

SAP Business Technology Platform facilitates secure integration with on-premise systems running software from SAP and other vendors. Using the platform services, such as the connectivity service, applications can establish secure connections to on-premise solutions, enabling integration scenarios with your cloud based applications.

In-memory persistence

SAP Business Technology Platform includes persistence powered by SAP HANA, taking full advantage of its real-time, in-memory computing technology and built-in analytics.

Secure data

Comprehensive, multilevel security measures have been built into SAP Business Technology Platform. This security is engineered to protect your mission critical business data and assets and to provide the necessary industry standard compliance certifications.

Free trial

You can start by getting a free SAP Business Technology Platform developer license on SAP Business Technology Platform Developer Center that also gives you access to our community and all the free technical resources, tutorials, blogs, support you need.

(7)

1.1.1 SAP Business Technology Platform Mobile Services Overview

SAP Business Technology Platform Mobile Services, or SAP BTP services, provides services to mobile applications, such as application analytics, app resources, onboarding, and HTTP/HTTPS configuration.

Mobile application services consist of the following:

● Application analytics: Usage statistics that are displayed graphically in the SAP BTP cockpit

● App resources: Containers of dynamic configurations, styles, or content that are downloaded by native applications

● Onboarding: Authentication of users who are registering through SAP Mobile Place

● HTTP/HTTPS configuration: Open standards for client communications

● Life cycle management: Managing and deploying multiple versions of an application

● Offline oData service: Optimizes data transport between the back end and the client offline store

● Push notifications: Native notifications sent from back-end systems to the server, which forwards them on to the clients

● SAP BTP cockpit: Deploys, manages, and monitors applications

(8)

● Supportability: Logs for monitoring system health and troubleshooting

SAP BTP services can expose on-premise back end services through Cloud Connector, and on-demand back end services directly.

SAP BTP services security enables you to use an on-premise identity management system for on-demand applications. You can use basic authentication using LDAP, or form-based application authentication using SAML.

All configuration and runtime data is persisted in an SAP S/4HANA database.

1.1.2 SAP Business Technology Platform SDK Overview

The SAP Business Technology Platform SDK includes well defined layers (SDK frameworks, components, and platform services) that simplify development of enterprise-ready mobile native apps that take full advantage of the mobile platform features.

The SAP Business Technology Platform SDK is tightly integrated with the SAP Business Technology Platform Mobile Services Cockpit to provide the following:

● End-to-end integrated security

● Support for offline applications

● Enterprise grade logging and monitoring support

● Access to core SAP ERP or SAP S/4HANA data and business processes, as well as access to third-party data sources

● Access to SAP Business Technology Platform capabilities and services

For more information about the SAP Business Technology Platform SDK see the following topics, depending on your mobile client platform:

● SAP Cloud Platform SDK for iOS

● SAP Cloud Platform SDK for Android

(9)

2 Deployment and Configuration of SAP Asset Manager

2.1 High-Level Installation Process for SAP Asset Manager

To install the SAP Asset Manager application, you must follow a specific order for certain steps in the installation process. Some objects in the installation rely on previously installed objects for IDs or URLs, or other data.

Use the following high-level process table for information on the process steps to take when installing the SAP Asset Manager.

Step Product Role Prerequisite Steps

Prerequi

sites

Before you can install the SAP Asset Manager application, ensure that the following SAP components are installed:

● Plant Maintenance is installed and running

● HR: If you’re using distribution work orders by personnel number, then the HR personnel management module is required.

1 Creation or update of SAP Business Technology Platform ac

count

Use the default subaccount or create a subaccount within your SAP Business Technology Platform account.

See the following:

● Getting Started topic in the SAP Business Technology Platform guide

● Neo installations: SCPms - Neo topic in the SAP Asset Manager Getting Started guide

● Cloud Foundry installations: SCPms - Cloud Foundry topic in the SAP Asset Manager Getting Started guide

SAP Business Tech

nology Platform ad

ministrator

Must be first step

2 Mobile Add-On for SAP S/4HANA system installation pro

cedure: See Installing the Mobile Add-On for SAP S/4HANA

SAP S/4HANA admin

istrator or SAP ERP (ECC) administrator

None

Mobile Add-On for SAP ERP system installation procedure (ECC): See Installing the Mobile Add-On for ERP

3 On-premise Cloud Connector setup. See the Cloud Connec

tor Installation topic.

IT administrator Relies on Step 1

(10)

Step Product Role Prerequisite Steps

4 Create your application in SAP BTP services (SAP Cloud Platform Mobile Services):

Set application security settings. For more information, see the Security Administration topic in the SAP BTP services guide.

Set application connection settings. For more information, see the topic Set Up Customer Accounts and the associated subtopics in the SAP BTP services guide.

SAP Business Tech

nology Platform ad

ministrator or Busi

ness expert

Application connec

tion settings rely on Step 2

5 Choose to set up or build the mobile application in one of the following ways:

1. Set up the mobile application:

○ Obtain onboarding URL and QR code. See the On

boarding to the MDK Client App topic for more in

formation.

2. Build the mobile application (optional):

○ Building the SAP Asset Manager Application Over

view [page 26]

○ Building the SAP Asset Manager Application Client [page 27]

No matter which option you select, see also Step 6 in the topic Building the SAP Asset Manager Client to link the on

boarding URL with the SAP Asset Manager client application.

Administrator Relies on Application security settings in Step 4

6 Import the metadata definitions into the SAP Web IDE For more information, see Enabling the Mobile Development Kit [page 22]

Business expert Relies on Steps 4–5

7 Launch the SAP Asset Manager application using the on

boarding URL. Navigate through the launch screens and per

form the initial sync.

Administrator Relies on Steps 1–6

2.2 Relevant SAP Notes

Read the following SAP Notes before you begin installation. The SAP Notes contain the most recent information about the installation, as well as any corrections to the installation process.

Make sure you have the most recent version of each SAP Note. Find SAP Notes on the SAP Service Marketplace at https://sap.com/notes .

(11)

SAP Note Number Title Description

2495578 Release Information Note - Mobile Add-On for SAP S/4HANA 1.0 and Support Pack

ages

Information and references to additional SAP Notes in the context of applying the Mobile Add-On for S/

4HANA 1.0 and support packages to an SAP S/4HANA on premise system

2493602 SAP Asset Manager Mobile Add-On for SAP S/4HANA Installation Master SAP Note

Release and Information (RIN) note about planning the installation and upgrades of the ABAP Add-On for the SAP Asset Manager application

2566071 SAP Cloud Platform (SCPms) Setup Info for SAP Asset Manager with an SAP S/4HANA On-Premise System

Information on how to set up SAP Business Technol

ogy Platform Mobile Services (SCPms) to run the SAP Asset Manager application

2660862 SAP Cloud Platform (SCPms) Setup Info for SAP Asset Manager with an SAP ERP On- Premise System

Information on how to set up SAP Business Technol

ogy Platform Mobile Services (SCPms) to run the SAP Asset Manager application

2933065 SAP Asset Manager - MDK Support Matrix Detailed information on SAP Asset Manager and Mo

bile Development Kit version compatibility

2970982 MDK App Crash on Launch on Certain iOS 14 Devices

Corrects issues with iOS 14 when building an iOS client

You can find additional information for the Mobile Development Kit in the following continually updated blog post: Latest Mobile Development Kit Blogs and Videos .

2.3 Installation Prerequisites

SAP Asset Manager uses the oData service that is provided with the SAP Business Technology Platform Mobile Services.

The oData service provides a universally available service for the SAP Asset Manager application.

 Note

To fully install and run the SAP Asset Manager application, perform the Building the SAP Asset Manager Application Client [page 27] procedure after performing the tasks in this Deployment and Configuration section.

Back End Landscape Prerequisites

● Ensure that an SAP Business Technology Platform Mobile Services account with an active mobile services account is available

(12)

● A Cloud Connector is required. For more information, see the Setting up the SAP Business Technology Platform Cloud Connector System Mapping [page 12] procedure.

● The correct SAP Mobile Add-On for your system is already installed. For more information, see the High- Level Installation Process for SAP Asset Manager [page 9] topic, Step 2.

Prerequisites for SAP Asset Manager Application Installation

● Access to your SAP Business Technology Platform Mobile Services environment

● Administrative access to the Mobile Development Kit

● Access to a computer to build and run the Mobile Development Kit client either in a simulator or on a device

● If using certificate-based authentication, acquire the certificates the IdP expects from mobile devices running the SAP Asset Manager application. See the SAP Cloud Platform Identity Provider portal page for complete information on working with certificates and Identity Providers.

If you optionally enable certificate based authentication, the Mobile Development Kit client passes the certificate to the IdP for use in authentication as long as the IdP supports and asks for certificates, and certificates are present on the mobile device.

Software Prerequisites

For all prerequisite and installation information for the Mobile Development Kit, see the https://help.sap.com/

viewer/977416d43cd74bdc958289038749100e/Latest/en-US manual.

2.4 Setting up the SAP Business Technology Platform Cloud Connector System Mapping

The SAP Business Technology Platform Cloud Connector serves as the link between on-demand applications in the SAP Business Technology Platform and existing on-premise systems.

For general Cloud Connector set up and configuration, see the SAP Business Technology Platform Cloud Connector documentation, specifically Configure Access Control (HTTP). The following topic addresses specific SAP Asset Manager Cloud Connector configurations to make in the Cloud Connector cockpit. Perform these additional configuration modifications after the initial Cloud Connector installation and configuration.

1. Click the Cloud to On-Premise link, and in the Access Control tab, add your on-premise system in your Cloud to On-Premise mapping as follows:

○ Protocol: HTTPS

○ Back-End Type: ABAP

○ Virtual Host: Your choice

○ Virtual Port Your choice

○ Internal Host: SAP back-end system

(13)

○ Internal Port: SAP back-end system

○ Principle Type: X.509 Certificate

2. Add a resource to your Cloud to On-Premise account:

○ URL Path: /sap/opu/odata

○ Click the Path and all sub-paths radio button

3. Click the Principle Propagation tab and set each of the Trust Configurations to Trusted (checked).

2.5 Creating an Application in SAP Business Technology Platform Mobile Services - Overview

To successfully deploy the SAP Asset ManagerSAP Shop Floor Manager application, you must create a corresponding application in SAP Business Technology Platform Mobile Services.

The corresponding application created in SAP Business Technology Platform Mobile Services connects a mobile device application to its corresponding data service on the on-premise back-end servers. There are two corresponding versions of SAP Business Technology Platform Mobile Services: an SAP Business Technology Platform Neo environment and an SAP Business Technology Platform Cloud Foundry environment.

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

Procedure

1. Using theSAP Business Technology Platform Cockpit, navigate to the Services Development &

Operations 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.

(14)

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 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 Asset Manager Version Destination

SAP Asset Manager 1.1 DEST_SAM10_PPROP

SAP Asset Manager 1911 DEST_SAM1911_PPROP

SAP Asset Manager 2.0 with Meter Management DEST_SMM10_PPROP

SAP Asset Manager 4.0 online service DEST_SAM40_ONLINE_PPROP

(15)

SAP Asset Manager 1911 online service DEST_SAM1911_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>.

○ 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-On for SAP S/4HANA on-premise connections to SAP Asset 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 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-On 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-On 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

(16)

○ 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 Asset Manager and the SAP Mobile Add-On. 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.

(17)

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 Updating Offline Settings for SAP Asset Manager Overview [page 39]

○ 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.

(18)

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 samclient URL scheme that is contained in the Onboarding URL scheme. The redirect URL must also match the redirect URL defined for the SAP Asset Manager application.

See the following screenshot for an example.

○

Make a note of the following settings, as you need them during the Building the SAP Asset Manager Application Client [page 27] 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 during the Building the SAP Asset Manager Application Client [page 27]

procedure.

2.5.2 Creating an Application in SAP Business Technology Platform Mobile Services - Cloud Foundry

Procedure

1. Using the SAP Business Technology Platform Cockpit, navigate to the space you want to work in. If mobile services are already enabled, navigate to a Service Instance and open it.

 Note

If mobile services are not enabled, enable it in the Service Marketplace.

2. Click the Service link. Follow the navigation, and click Support to open mobile services on Cloud Foundry.

(19)

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

3. Click the Mobile Application link on the left, then click Native/Hybrid to create a new application.

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

○ 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

○ Back-End Connection Timeout: The timeout for each network transition between the device and the back-end system. Settings are based on the following:

○ The expected timeout requirements for the SAP Mobile Add-On for SAP S/4HANA on-premise connections to SAP Asset Manager is 600,000 ms.

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:

○ Mobile App Update: You can upload application metadata bundles to update mobile apps on devices here. This setting controls how new metadata definitions are pushed to the Mobile Development Kit clients.

○ Mobile Settings Exchange: 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 Password Policy. Then define the password requirements.

○ Mobile Connectivity: How the SAP Business Technology Platform communicates with the back end.

Additional configuration needed (performed in Step 7).

○ Mobile Offline Access: See Updating Offline Settings for SAP Asset Manager Overview [page 39].

○ Mobile Push Notification: See the procedure.

○ Mobile Network Trace: Sets up network tracing for the offline and connectivity components.

7. Click the Mobile Connectivity feature. Then click New under Mobile Destinations 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 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:

(20)

SAP Asset Manager 2.0 with Meter Management DEST_SMM10_PPROP

SAP Asset Manager 4.0 online service DEST_SAM40_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 don’t 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 HTTPS scheme, with the HTTPS 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>.

○ Use Cloud Connector: Selected

○ Cloud Connector Location ID: Set to the location ID designated by the Cloud Connector

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

(21)

○ 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-On for SAP S/4HANA on-premise connections to SAP Asset Manager is 600,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-On OData service, you can set the Rewrite Mode to Rewrite URL.

○ If the virtual host and the port in the Cloud Connector don’t match the internal host and the port of the SAP Mobile Add-On 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.

○ Keep X-Forwarded-* Header: Not applicable for the default shipment of this version of SAP Asset Manager

○ Custom Headers: Additional headers needed for OData service

○ If a default client isn’t 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: Cloud Connector SSO

○ Principal propagation is the officially supported authentication method between the SAP Asset Manager and the SAP Mobile Add-On. For more information, see the topic Configure Principal Propagation to an ABAP System for HTTPS.

8. Optional: To debug an existing application, click the Enable Detailed Event Log link in the top-right corner of each feature. Ensure that the logs for the feature are enabled.

9. Save your changes. Click back to your new application and click the Security tab.

The Security information displays.

10. In OAuth Settings section, set the following parameters:

○ Token Lifetime: Default is set to 12 hours

○ Refresh Token Lifetime: Default is set to 30 days

○ Redirect URL: If enabling certificate-based authentication, ensure that the field contains the same samclient URL scheme that is contained in the Onboarding URL scheme. The redirect URL must also match the redirect URL defined for the SAP Asset Manager application.

○ Client ID: ID of the client used to identify the application to the OAuth client

11. Make a note of the following settings, as you need them during the Building the SAP Asset Manager Application Client [page 27] procedure:

○ Client ID

○ Redirect URL

○ Authorization Endpoint

○ Token Endpoint

12. Click back to the main application page and click the APIs tab. Make a note of the Server setting, as you need it during the Building the SAP Asset Manager Application Client [page 27] procedure.

(22)

2.6 Enabling the Mobile Development Kit

Procedure

1. Log in to the SAP Business Technology Platform Cockpit and from Home Region , click the Region in which your account is based.

2. Select your Global Account. From the Global Account page, select the Subaccounts tab on the left side.

Then select the subaccount where you wish to deploy your applications.

3. Find the SAP Web IDE Full-Stack tile. If it is not Enabled, enable it. Then click Go to Service.

The SAP Web IDE Full-Stack browser opens.

4. Click the Preferences icon ( ) on the left.

5. Click Extensions. Ensure the Mobile Services App Development Tools editor tile is enabled. If not, enable it by clicking the radio button at the top right of the tile. After enabling the tool, click Save.

The SAP Web IDE prompts to refresh. Refresh the SAP Web IDE to view the new tile.

6. Click the MDK Development icon. If the Mobile Development Kit icon does not appear, ensure it is enabled.

After enabling, refresh the SAP Web IDE.

Next Steps

Proceed to the Importing Metadata Definitions to the SAP Web IDE Mobile Development Kit [page 22]

procedure.

2.6.1 Importing Metadata Definitions to the SAP Web IDE Mobile Development Kit

You can import a project and its resources from your local file system to the SAP Web IDE Mobile Development Kit workspace.

Prerequisites

Ensure that the SAP Asset Manager 2105 and Mobile Development Kit 4.3.2 installation files are downloaded from the SAP Download Center .

If an earlier version of the Mobile Development Kit is already installed on your back-end system when compared to your version of the SAP Asset Manager application that you are attempting to install, you must also import and deploy the current version of the Mobile Development Kit to the SAP Web IDE.

(23)

Procedure

1. Click the MDK Development icon ( ).

2. Select the folder to which you want to import your project from your Mobile Development Kit workspace.

3. Import your project. Select File Import From File System from the main menu. Alternatively, you can right-click on your Workspace folder and choose Import from the menu choices.

An Import window displays.

4. Click the Browse button and browse to the folder where your ZIP file is located. If the folder listed in the Import to field is incorrect, click the Select Folder button to choose the correct folder. If you’re importing an entire project, the top-level folder is the correct folder.

5. You can optionally change the <Import To> folder name to SAPAssetManager, but it's not required.

If you decide to leave the folder name as-is, once the import is complete, hit refresh on your browser to reload the SAP Web IDE. After refreshing, the folder name shows up and correctly matches the Application Name in your Application.app file.

6. Delete the SIGNATURE.SMF file.

(24)

7. Check the Extract Archive checkbox and click OK.

The project is imported into the selected folder with the same name as the <Import To> field.

 Note

If the target folder already exists in your workspace, you’re prompted to approve the overwriting of the existing files.

2.6.2 Deploying Metadata Definitions to Mobile Services

Prerequisites

In the SAP Business Technology Platform Cockpit, ensure that the mobileservices destination has the additional property of WebIDEUseage set with the property of mobile.

(25)

Context

Once your desired changes to the metadata definitions for the Mobile Development Kit are complete, use the Mobile Services app development tools deployment feature to deploy the metadata definitions to your application in Mobile Services. Then, when you change the SAP Asset Manager application, and redeploy the metadata files in the Mobile Development Kit editor, a timer looks for new definitions within the bundle.

Procedure

1. Click the Development icon (_).

2. From your Mobile Development Kit workspace, select the folder from which you want to deploy your project.

3. Right-click and select File MDK Deploy and Activate . A ZIP file is created of your application definitions.

4. Select the options you would like to deploy with and click Next.

5. In the <Destination Name> field, select mobileservices. In the <Application ID> field, select the desired application ID you want to deploy to. Click Next.

Results

The bundle.js is uploaded from the SAP Web IDE to Mobile Services.

(26)

3 Building / Branding the SAP Asset Manager Application

3.1 Building the SAP Asset Manager Application Overview

Use the following information as a reference when building your application using the procedure Building the SAP Asset Manager Application Client [page 27].

Structure of .mdkproject

● BrandedSettings.json: Runtime configurations such as security settings, URLs for connecting to the SAP Business Technology Platform Mobile Services, and more

● MDKProject.json: Build time configurations such as the application name, version, and bundle ID

● App_Resources: Any custom resources used by the application, such as all of your action bar images that are customized for your application.

● demo: To make an OData service available in demo mode, include the .udb and .rq.udb files for that service in this directory

Currently the SAP Asset Manager application can’t take the demo UDBs created by the most recent SAP Business Technology Platform SDK and use them with an older SAP Business Technology Platform SDK version.

Therefore, use the Android UDBs for demo mode, for both the iOS and Android applications. Failure to do so results in the inability to perform Update or Create OData actions, such as:

○ Changing the mobile status of any work orders

○ Creating reminders

● extensions: Include any extensions used by the application in this directory

● metadata: Built in metadata for the application

Configuring the MDKProject.json File

The MDKProject.json file contains settings that you can only configure before running the create- client.command:

● AppName: Determines the name of the application project and the app as it appears on a mobile device

● AppVersion: The client project application version

● BaseProject: The metadata subdirectory under the .mdkproject structure that contains the main application metadata. The main application metadata is the MDK application, which includes one or more component MDK applications. The component applications are only required if you are adding

components to your base application, such as Meter Management or Field Operations Worker.

(27)

● BundleID: Uniquely identifies the resulting MDK client application on the device. Only one instance of a bundle ID can be installed on a device at a time. If you attempt to install a second application using the same bundle ID, it will overwrite the existing application.

● Externals: A list of NPM nodules that should not be included in the application bundle. Use this option for dependencies you expect to be in the environment when the application is built.

Note that the modules file-system and ui/dialogs are automatically used as externals as they are already included in the client application.

● URLScheme: Allows you to specify a custom URL scheme that opens the client. If the URL includes connection settings such as URL parameters, these settings override the settings used by the client.

Defaults to mdkclient.

Application Version and Notes on the Settings App

The Mobile Development Kit client tracks several versions, which you can view in the iOS Settings menu. These versions are identified as the application version, the definitions version, and the frameworks versions for the frameworks used in the client build.

When generating a client project, you can specify the application version. Specifying the application version allows you to version the client itself, which can be useful if you change extension controls or other branded settings. To specify the application version, specify the AppVersion property in the MDKProject.json file before running create.client.command.

To further customize the entry of your application in the iOS Settings menu, you can manually edit

<ProjectDirectory>/app/App_Resources/iOS/Settings.bundle/Root.plist after the script has completed. You can add new entries, but do not remove existing entries or the application may not function correctly.

For more information, see Implementing an iOS Settings Bundle .

3.2 Building the SAP Asset Manager Application Client

Deploy SAP Asset Manager from the out of the box configuration to set the cloud endpoint authentication URL and the OData service URL. You can also set other configuration values.

Prerequisites

● Verify that your system is set up to build the SAP Asset Manager application by running the MDK

Dependencies Installer. This tool detects all the components to install or update, allowing you to update or install them instantly.

For more information and instructions on how to obtain the MDK Dependencies Installer, see the Building Your MDK Client SDK procedure.

● Complete the Creating an Application in SAP Cloud Platform mobile services procedure.

(28)

Context

 Restriction

Develop any customization on the app as a separate component in a Mobile Development Kit project.

Developing customizations as a component makes it easier to maintain customizations during upgrades, as it isolates custom code. Isolating your custom code eliminates the chance of overwriting when you implement a new release.

Use the following procedure to build and brand the SAP Asset Manager application.

Procedure

1. Locate the required installation files from the SAP Download Center and navigating to:

Software Downloads By Category SAP Mobile Solutions SAP Asset Manager

 Note

For detailed information on SAP Asset Manager and Mobile Development Kit version compatibility, see 2933065 .

See 2970982 for detailed information when building an iOS client using iOS 14.

2. Download the files found in the MDK PLUG-IN SDK folder. Select the correct version for your installation.

Select either iOS or Android, depending on your installation platform.

3. Download the files from either SAP ASSET MANAGER for iOS devices or MOB ASSET MANAGER AND for Android devices. Select the correct application version folder. In the version folder, download the SDK file and the metadata files found in the following subfolders:

○ ASSET MANAGER METADATA: SAP Asset Manager

○ ASSET MGR BRANDING SDK: Branding SDK for SAP Asset Manager, Meter Management, Field Operations Worker, Crew Management, Customer Service, Quality Management, and Asset Central

○ ASSET MGR CREW METADATA: Crew Management

○ ASSET MGR METER METADATA: Meter Management

○ ASSETMGR ASSETCENTRL META: Asset Central

○ ASSETMGR CUSTOMERSVC META: Customer Service

○ FIELD OPS WORKER METADATA: Field Operations Worker

○ ASSETMGR QUALITYMGMT META: Quality Management 4. Create a folder to contain the installation files (SAPAssetManager).

5. Extract the SAP Asset Manager branding SDK:

a. Unzip the ASSET MGR BRANDING SDK folder.

b. Copy the SAPAssetManager/SAM.mdkproject folder to the SAPAssetManager folder.

c. Set up the SAP Asset Manager Mobile Development Kit project folders:

1. In the SAPAssetManager/SAM.mdkproject folder, create a folder named metadata.

2. In the SAPAssetManager/SAM.mdkproject folder, create a folder named extensions.

(29)

6. Extract the SAP Asset Manager metadata:

a. Unzip the ASSET MANAGER METADATA file.

b. Copy all contents of the ZIP file to SAPAssetManager/SAM.mdkproject/metadata.

c. If present, delete the SIGNATURE.SMF file from the SAPAssetManager/SAM.mdkproject/

metadata folder.

7. Extract the MDK plug-in SDK in one of the following ways, based on whether you’re building either an iOS or an Android client:

iOS Client Android Client

1. Unzip the iOS subfolder found in the MDK PLUG- IN SDK^{zip file.}

2. Choose your architecture from one of the following folders:

○ Release-iphoneos

○ Release-iphonesimulator

○ Release-fat (contains both the iphoneos and the iphonesimulator architectures)

3. Copy the following folders from your selected ar

chitecture folder to the SAPAssetManager/

SAM.mdkproject/extensions folder:

○ extension-Analytics

○ extension-BarcodeScanner

○ extension-FieldDataCapture

○ extension-MapFramework

○ extension-HierarchyFramework

1. Unzip the Android subfolder found in the MDK PLUG-IN SDK^{zip file.}

2. Copy the following folders from your Universal folder to the SAPAssetManager/

SAM.mdkproject/extensions folder:

○ extension-Analytics

○ extension-BarcodeScanner

○ extension-FieldDataCapture

○ extension-MapFramework

○ extension-HierarchyFramework

8. Configure the connection to SAP Business Technology Platform Mobile Services:

a. Retrieve the following information to establish a connection between the SAP Asset Manager application and the SAP Business Technology Platform Mobile Services:

○ AppId: Set to the ID under the Mobile Development Kit that you created in Step 6 of the Creating an Application in SAP Cloud Platform mobile services procedure.

○ ClientID:

○ Neo: Set to the oAuth client ID that you created in Step 12 of the Creating an Application in SAP Cloud Platform mobile services Creating an Application in SAP Business Technology Platform Mobile Services - Neo [page 13] procedure.

○ Cloud Foundry: Set to the oAuth client ID that you created in Step 11 of the Creating an Application in SAP Cloud Platform mobile services Creating an Application in SAP Business Technology Platform Mobile Services - Cloud Foundry [page 18] procedure.

(30)

○ SapCloudPlatformEndpoint: Find the Endpoint setting inside the application list of APIs on the Mobile Services under the Server API:

(31)

 Note

By default, the Server API has a / at the end of the endpoint URL. Do not add this / into your connection settings.

○ Neo:

○ AuthorizationEndpointURL: Set to the oAuth authorization endpoint URL that you created in Step 12 of the Creating an Application in SAP Business Technology Platform Mobile Services - Neo [page 13] procedure.

○ RedirectURL: Set to the callback URL that is automatically generated with the creation of the oAuth client in Step 12 of the Creating an Application in SAP Business Technology Platform Mobile Services - Neo [page 13] procedure.

○ TokenURL: Set to the token URL that is automatically generated with the creation of the oAuth client in Step 12 of the Creating an Application in SAP Business Technology Platform Mobile Services - Neo [page 13] procedure.

○ Cloud Foundry:

○ AuthorizationEndpointURL: Set to the oAuth authorization endpoint URL that you created in Step 11 of the Creating an Application in SAP Business Technology Platform Mobile Services - Cloud Foundry [page 18] procedure.

○ RedirectURL: Set to the callback URL that is automatically generated with the creation of the oAuth client in Step 11 of the Creating an Application in SAP Business Technology Platform Mobile Services - Cloud Foundry [page 18] procedure.

○ TokenURL: Set to the token URL that is automatically generated with the creation of the oAuth client in Step 11 of the Creating an Application in SAP Business Technology Platform Mobile Services - Cloud Foundry [page 18] procedure.

b. Choose your client configuration:

To preconfigure your client to connect to your mobile application, add the information retrieved in the above step to the ConnectionSettings block. When adding additional entries, include a comma after the existing EnableOverrides entry. An example is included in the table for reference when you’re adding entries to your file.

If you want to use SAP Asset Manager against different back-end mobile applications (ex: DEV and QA), leave the ConnectionSettings as is, and build an onboarding URL for users using the values found in Step 6a. See the example in the table for further information on how to connect a client using either of the methods.

 Note

If you are using the onboarding URL approach, note that all users must recieve an email with the onboarding URL to connect applications toSAP Business Technology Platform Mobile Services.

c. OPTIONAL: Enable certificate authentication in the Mobile Development Kit:

In the BrandedSettings.json file, ConnectionSettings section, set AllowCerts to true.

(32)

Preconfigured Client Onboarding URL To configure the client to connect to a specific applica

tion, update the following values in the BrandedSettings.json file:

 Sample Code

…

“ApplicationDisplayName": "<Name of application>",

"ConnectionSettings": { "EnableOverrides": true, "AppId": "<Insert AppID value here>",

"ClientId": "<Insert ClientID value here>",

"SapCloudPlatformEndpoint":

"https://<Insert cloud platform endpoint URL here>",

"AuthorizationEndpointUrl":

"https://<insert authorization endpoint URL here>",

"RedirectUrl": "https://

<insert redirect URL here>", "TokenUrl": "https://<insert token URL here>",

"AllowCerts": <true/false>

},

Using the example as a guide, insert your own connec

tion-specific values where they belong.

Save any changes you make.

You can generate an onboarding link to overwrite the val

ues discussed in this substep on a device. Use the follow

ing format in a URI:

 Sample Code

samclient://?AppId=<Insert AppID value here>

&ClientId=<Insert ClientID value here>

&SapCloudPlatformEndpoint=<Insert cloud platform endpoint URL here>

&AuthorizationEndpointUrl=<insert authorization endpoint URL here>

&RedirectUrl=<insert redirect URL here>

&TokenUrl=<insert token URL here>

&ServiceTimeZoneAbbreviation=<inse rt timezone abbreviation here>

Save any changes you make.

9. Edit the project settings:

a. Open the SAPAssetManager/SAM.mdkproject/MDKProject.json file in a text editor. Edit app information such as:

○ Application name on the home screen

○ App version

○ Bundle ID to uniquely identify the application on the device

○ URL scheme for onboarding URLs b. Save any changes you make.

10. Set up the Mobile Development Kit Client SDK:

a. Unzip Mobile Development Kit MDK PLUG-IN SDK.

1. Run the Mobile Development Kit dependencies installer and confirm that your system is ready.

2. Unzip MDKClient_SDK.zip to the new SAPAssetManager folder.

b. To install the necessary dependencies, open a Terminal prompt in the SAPAssetManager/

MDKClient_SDK directory. Run either ./install.command on a Mac or ./install.cmd on a Windows PC. Note that you can build both iOS and an Android on a Mac. You can only build Android if you’re using a Windows PC.