Installation Guide SAP® CRM Mobile 7.01 (7.0 Ehp1) SP06

Installation Guide SAP® CRM Mobile 7.01 (7.0 EhP1) SP06

Target Audience ■ Consultants ■ Administrators ■ Others

Public Document version 1.02 – January 2017

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

No part of this publication may be reproduced or transmitted in any JavaScript is a registered trademark of Sun Microsystems, Inc., used form or for any purpose without the express permission of SAP AG. under license for technology invented and implemented by Netscape. The information contained herein may be changed without prior notice. MaxDB is a trademark of MySQL AB, Sweden.

Some software products marketed by SAP AG and its distributors SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, contain proprietary software components of other software vendors. ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are Microsoft, Windows, Outlook, and PowerPoint are registered trademarks or registered trademarks of SAP AG in Germany and in trademarks of Microsoft Corporation. several other countries all over the world. All other product and IBM, DB2, DB2 Universal Database, System I, System i5, System p, service names mentioned are the trademarks of their respective System p5, System x, System z, System z10, System z9, z10, z9, companies. Data contained in this document serves informational iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, purposes only. National product specifications may vary. OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, These materials are subject to change without notice. These materials POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System are provided by SAP AG and its affiliated companies (“SAP Group”) Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, for informational purposes only, without representation or warranty of OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, any kind, and SAP Group shall not be liable for errors or omissions WebSphere, Netfinity, Tivoli and Informix are trademarks or with respect to the materials. The only warranties for SAP Group registered trademarks of IBM Corporation. products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Linux is the registered trademark of Linus Torvalds in the U.S. and Nothing herein should be construed as constituting an additional other countries. warranty.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in Disclaimer the United States and/or other countries. Some components of this product are based on Java™. Any code change in these components may cause unpredictable Oracle is a registered trademark of Oracle Corporation. and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Any Java™ Source Code delivered with this product is Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, only to be used by SAP’s Support Services and may not be VideoFrame, and MultiWin are trademarks or registered trademarks of modified or altered in any way. Citrix Systems, Inc. Documentation in the SAP Service Marketplace HTML, XML, XHTML and W3C are trademarks or registered You can find this documentation at the following address: trademarks of W3C®, World Wide Web Consortium, Massachusetts http://service.sap.com/instguides Institute of Technology.

Typographic Conventions Icons

Type Style Description Icon Meaning

Example Text Words or characters quoted from Caution the screen. These include field names, screen titles, Example pushbuttons labels, menu Note names, menu paths, and menu options. Recommendation Cross-references to other Syntax documentation Example text Emphasized words or phrases in Additional icons are used in SAP Library body text, graphic titles, and documentation to help you identify different table titles types of information at a glance. For more EXAMPLE TEXT Technical names of system information, see Help on Help  General objects. These include report Information Classes and Information Classes names, program names, for Business Information Warehouse on the transaction codes, table names, first page of any version of SAP Library. and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

01 2017 3 1 Introduction

Contents 1 Introduction ...... 6 1.1 Document History ...... 6 1.2 About this Document ...... 6 1.3 Before You Start ...... 7 1.3.1 Naming Conventions...... 7 1.3.2 SAP Notes for the Installation ...... 7 2 Planning ...... 8 2.1 Typical Landscape ...... 8 2.1.1 Set Up of a System Landscape ...... 9 2.1.2 Core Machines ...... 11 2.2 Installation Sequence...... 21 2.2.1 Overview of Upgrade Process [flowchart]...... 21 2.3 Prerequisites ...... 23 2.3.1 Hardware Requirements ...... 23 2.3.2 Software Requirements ...... 24 3 Cross CRM support for CRM Mobile ...... 31 3.1 Supported CRM Server Releases with 7.0 EHP1 SP06 ...... 31 3.2 Prerequisites steps for CRM Mobile 7.01 with CRM Server 7.0 EHP2 ...... 31 3.3 Components ...... 32 3.3.1 Mobile Repository Server ...... 32 3.3.2 Mobile Development Workstation ...... 32 3.3.3 CRM Mobile – Middleware components ...... 32 3.3.4 CRM Mobile – Application ...... 34 4 Preparation ...... 35 4.1 Content of Installation DVD ...... 35 5 Installation ...... 36 5.1 Installing Mobile Repository Server ...... 38 5.1.1 Prerequisites ...... 38 5.1.2 Procedure ...... 38 5.1.3 Mobile Application Repository Language Installation ...... 43 5.2 Installing Mobile Development Workstation ...... 46 5.3 Installing Communication Station ...... 53 5.3.1 Introduction ...... 53 5.3.2 Installation Planning ...... 55 5.3.3 Installation Process ...... 56 5.3.4 Post Installation ...... 57 5.4 Installing Mobile Client Application ...... 63 5.4.1 Prerequisites ...... 63 5.4.2 Procedure ...... 64 5.5 Installing Workgroup Server ...... 71 5.5.1 Prerequisites ...... 71 5.5.2 Procedure ...... 71 5.6 Installing Workgroup Client ...... 78 5.6.1 Procedure ...... 78 5.7 Restarting the Installation (Maintenance Mode) ...... 85 5.7.1 Modifying Installed Applications ...... 87 5.7.2 Repairing Installed Applications ...... 88 5.7.3 Removing All Installed Applications ...... 90 6 Post-Installation ...... 94

01 2017 4

1 Introduction

6.1 Client Console Settings ...... 94 6.2 Patching IPC ...... 94 6.3 Security Settings for Ides ...... 95 7 Additional Information ...... 96 7.1 Appendix A: Central Service Reference Guide ...... 96 7.1.1 Command Line Options ...... 96 7.1.2 Guidelines for Using Command Line Options ...... 96 7.1.3 Updating Central Service Port Number in the Application Repository ...... 97 7.2 Appendix B: Installing Databases Using SwitchDB ...... 99 7.2.1 General User Interface Information ...... 99 7.2.2 SwitchDB Application – UI Mode ...... 107 7.2.3 Checking connection to the SQL Server...... 108 7.2.4 Installing a Database ...... 108 7.2.5 Uninstalling a Database ...... 110 7.2.6 Archiving and uninstalling a Database...... 111 7.2.7 SwitchDB Application-CommandLine Mode ...... 112 7.2.8 SwitchDB File Structure ...... 113 7.2.9 Example Scenarios ...... 113 7.2.10 Log Files ...... 115 7.3 Appendix C: Code Page Settings for Language Versions ...... 116 7.4 Appendix D: Mobile Repository Server Configuration ...... 119 7.4.1 Configure the Mobile Repository Server ...... 119 7.4.2 Installing the CRM Transport Component ...... 119 7.4.3 Creating a CRM Server User Account ...... 125 7.4.4 Assigning the MAR ID ...... 126 7.4.5 Creating User Accounts in User Manager ...... 127 7.4.6 Troubleshooting ...... 127 7.4.7 Technical Details ...... 129 7.5 Appendix E: Mobile Application Repository Transport Concepts ...... 131 7.5.1 Overview ...... 131 7.5.2 Transport Component ...... 131 7.5.3 Transport ...... 132 7.5.5 Client Upgrade ...... 134 7.6 Appendix F: Mobile Client Applications Installation with Initialization File ...... 136 7.6.1 Creating the Initialization File ...... 136 7.6.2 Installing Multiple Mobile Clients ...... 137 7.7 Appendix G: Generation of Table Scripts ...... 138 7.8 Appendix H: Mobile Client Rollout Manager...... 139 7.8.1 Installing the Mobile Client Rollout Manager ...... 140 7.8.2 Setting up the Environment for the Stationary Site ...... 140 7.8.3 Setting up the Environment for the Rollout/Recovery Site ...... 141 7.8.4 Intermediate Step Execution of the Mobile Client Rollout Manager ...... 141 7.8.5 Parallel Processing of the Rollout Manager Activities ...... 143 7.8.6 Replacing Defective Laptops ...... 143 7.8.7 Rollout Laptops ...... 147 7.8.8 Troubleshooting Options ...... 149 7.8.9 Logging Options ...... 149 7.8.10 Filter Criteria ...... 151 7.8.11 Searching for Sites based on User Information ...... 152 7.8.12 Searching for Sites based on Organization ...... 152 7.8.13 Executing Mobile Client Rollout Manager from the Command Line ...... 153 7.9 Appendix I: Customer Namespace Tool ...... 156 7.10 Appendix J: Steps to subscribe to a SAP Note ...... 157 8 Reference ...... 159

01 2017 5 1 Introduction

1 Introduction This document describes the procedure for installing SAP CRM Mobile Client Component 7.01 SP06. The activities required for installing are described separately for each machine type: Mobile Repository Server, Mobile Development Workstations, CommStation, Mobile Clients, Workstation Clients and Workstation Server. 1.1 Document History This section gives you an overview about the history of this guide. It gives the version number, the date on which the new version was published and what has changed.

Before you start the installing, make sure that you have the latest version of this document. You can find the latest version on SAP Service Marketplace at: http://service.sap.com/instguides.

The following table provides an overview about the most important document changes. Version Date Description 1.00 11/30/2012 First version 1.01 01/28/2014 Patch 01 Release. Note 1970719 1.02 01/16/2017 Patch 06 Release. Note 2408320 1.2 About this Document The Component Installation Guide for the SAP CRM Mobile guides you through the installation of SAP CRM Mobile 7.01 SP06.

Use the SAP CRM Installation Master Guide to get an overview of the installation of the involved software units and scenarios from a technical perspective. The Installation Master Guide is a document that helps you decide which software units you have to install by taking into account the dependencies between the software units.

You can find it under: http://service.sap.com/instguides → SAP Business Suite Applications → SAP CRM → SAP CRM 7.0 → Plan → Master Guide SAP CRM 7.0 SR1 The Mobile Installation Guide consists of the following main sections:

Planning This section provides information about the typical landscape in the Mobile Scenario, the installation sequence and prerequisites.

Preparation Here you can find an overview of the content of the Installation DVD.

Installation Process The section on Installation Process describes the Installation Procedure in detail for each machine. For better understanding, flowcharts are provided at the beginning of each section to provide a compact overview of each subprocess.

01 2017 6

1 Introduction

1.3 Before You Start 1.3.1 Naming Conventions Used Abbreviations within this document: BOL Business Object Layer CDB Consolidated Database CMT Code Migration Tool CommStation Communication Station MAR Mobile Application Repository MAS Mobile Application Studio MCIM Mobile Client Index Manager MDW Mobile Development Workstation MRS Mobile Repository Server MUP Mobile Upgrade Package RTO Run Time Objects UI User Interface

1.3.2 SAP Notes for the Installation The following note numbers are relevant for the Installation Process. They will get referenced again at the place, where they are needed. Before starting with the installation, it makes sense to take a printout of the notes, so you have them in front of yourself, when you need them. Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at http://service.sap.com/notes. While the mandatory notes have to be implemented into the system, the non-mandatory notes contain additional information for special scenarios, recommendations and so on The following table contains the Collective and Installation\Upgrade Note for 7.01 SP06. SAP Notes Note Title \ Document Description 1442966 SAP CRM 7.01 Mobile Client Component: Collective Note 1799687 CRM Mobile Client Component: Installation/Upgrade 7.01 SP06

Please refer to the Installation/Upgrade Note for 7.01 SP06 before you start the installation/upgrade to CRM Mobile 7.01 SP06.

01 2017 7 2 Planning

2 Planning 2.1 Typical Landscape The following diagram depicts the system landscape for a typical CRM Mobile environment that contains the required machines for running the Mobile Client Solution software Two scenarios are possible, a typical solution and a workgroup solution. For running the typical solution you will need the ‘Mobile Client’, for a workgroup scenario, the ‘Workgroup Server’ and the ‘Workgroup Client’ are necessary.

While all machines are required in the Production environment only, we recommend that you set up an identical landscape in all three environments. This installation routine does not include the installation routines for the back-end system and the CRM Server. The back-end server and the CRM Server are included in the diagrams to provide a complete system landscape; the numbers representing each machine indicate the order in which these machines must be installed. The Mobile Client Component Application installation assumes that the back-end system and the CRM Server are already in place.

01 2017 8

2 Planning

The following internationalization settings are supported in the SAP CRM Mobile System Landscape: 1. CRM Server on Unicode  Mobile client databases on Unicode  Mobile client databases on the same or different codepages In the latter case, the replication model has to assure that only characters that can be interpreted on the chosen codepage of a mobile client are replicated to the respective mobile client. 2. CRM Server non-Unicode  All mobile client databases on the same codepage (the same like the CRM Server codepage)

For more information on Unicode enabled mobile clients, refer to following note: Note 985294: FAQs on Unicode enabled Mobile Client

For information on the various scenarios of the CRM server and the mobile client in a 5.0SP15-environment, refer to following note: Note 1018164: Possible data transfer scenarios between MSA and CRM Server 2.1.1 Set Up of a System Landscape

Purpose This process describes how a system landscape is set up for implementing CRM Mobile Client Component Applications. This process helps you identify the need for setting up core machines that are required to install, configure and upgrade mobile client components. These core machines are set up to meet the following purposes:  To ensure an error-free installation or upgrade of mobile client components.  To eliminate the risks that may occur due to dependencies involving mobile client components.  To clearly distinguish implementation activities that are carried out in development, test and production environments.

For more information about the purpose of machines in the landscape, see Core Machines Process Flow 1. It is recommended to set up a three-system landscape as described below: a. Development environment - where mobile client applications are customized to meet business needs. Applications are customized without affecting the productive version. b. Test environment - where design and runtime behavior of the customized applications is tested. The test environment is isolated from the development environment.

01 2017 9 2 Planning

c. Production environment - where the customized applications are deployed to Mobile Clients (offline) or Workgroup Clients (online) or a combination of both. 2. The CRM Technology Consultant identifies the machines that need to be installed in the landscape, based on the purpose and requirements of each machine. 3. The CRM Technology Consultant installs the machines with the required hardware and third-party software.

Result A system landscape is set up with required machines. Necessary mobile client components specific to each machine can now be installed. Typical Landscape for a Standard Solution and/or Workgroup Solution The figure below illustrates the system landscape that must be set up to enhance or use mobile client applications as a standard solution. The connectors in the figure indicate the communication paths of core machines. For example, Mobile Repository Server communicates with the CRM Server and Mobile Development Workstation. Here, the CRM Server and Mobile Development Workstation are considered as related machines of the Mobile Repository Server.

The landscape of a workgroup solution is similar to the landscape of a standard solution. However, in the workgroup landscape, Workgroup Clients (online clients) exist in place of Mobile Clients (offline clients). It is also possible to use both, the standard and the workgroup scenario. The installation, configuration and upgrade instructions of the required software, repository, databases and the third-party software on the corresponding machines are grouped according to the machines recommended in the above figure. For better testing, it is recommended to connect Mobile Clients also to your Development and Test-Environment.

01 2017 10

2 Planning

2.1.2 Core Machines This section explains the need and details of each machine that is required in the typical landscape of a standard as well as workgroup solution. To eliminate any risks that may arise during installation and upgrade of various components, we recommend you to set up the machines as suggested. The need of maintaining these core machines in each environment has been indicated as optional or mandatory. For example, setting up a Communication Station in a development environment is optional where as it is mandatory in the test and production environments. For more information about the hardware and software requirements of each machine, see the section on Prerequisites. 2.1.2.1 Back-end System

Definition It is an existing SAP R/3 Enterprise or a legacy system (non-R/3 Enterprise) that contains the company's operational and financial data. It is an optional machine in the typical landscape.

Use An R/3 Enterprise contains master and transactional data that is transferred to the CRM Server and used by mobile client applications. A non-R/3 Enterprise contains master data that is migrated to the CRM Server and used by mobile client applications.

Integration The interaction of a Back-end System with other machines in the landscape is described below. Related machine Purpose of interaction Software used CRM Server The CRM Server interacts The R/3 Adapter handles the with the SAP R/3 Enterprise download. to download master and transactional data from the SAP R/3 Enterprise into CRM and further to the consolidated database (CDB). The CRM Server interacts The ASCII Adapter handles with the non-R/3 Enterprise the migration. to migrate master data from the legacy system into CRM and further to the CDB.

We recommend that you maintain the migrated master data on the CRM Server. This is in the case of migrating master data from a non-R/3 Enterprise. This is because only a one-way migration (from the non-R/3 Enterprise to the CRM Server) is available and synchronization of databases between the non-R/3 Enterprise (previous database) and the CDB of the CRM Server (current database) is not possible. However, in the case of an R/3 Enterprise the source for the master and transactional data can be retained in the Back-end System itself. In this way

01 2017 11 2 Planning

you can use the source data for validation and execution of any mobile client application related task. 2.1.2.2 CRM Server

Definition It is a central hub in the system landscape, on which most of the CRM Mobile Client Components’ business functionality and databases such as the CRM database and consolidated database (CDB) exist. It is a mandatory machine in the typical landscape. Integrating this system with other systems, such as Advanced Planner and Organizer (APO) and Business Information Warehouse (BW), provides additional functionality.

Integration The interaction of a CRM Server with other machines in the landscape is described below. Related machine Purpose of interaction Software used Back-end System The Back-end System interacts with The R/3 Adapter or ASCII the CRM Server to transfer or migrate Adapter handles the the required master or transactional transfer or migration of the data into CRM and further to the CDB. data respectively. Mobile Repository The MRS interacts with the CRM The MAR Transport Agent Server (MRS) Server to: facilitates moving the client upgrade packages or  Move client upgrade packages design time objects to the (runtime files) of the customized CRM Server. mobile client application to Mobile Clients. You can test the upgrade by connecting a test Mobile Client to the CRM Server via a Communication Station.  Move design time objects (transport) of the customized mobile client application to MRS in the typical landscape. Mobile Development The MDW interacts with the CRM  The SAP Mobile Workstation (MDW) Server to: Application Studio allows you to connect to the  Access the BDoc repository while BDoc repository from customizing a mobile client MDW. application.  The Client Console  Retrieve BDoc repository changes retrieves BDoc (if any). repository changes on to  Create or attach transport orders the MDW. for/to change lists.  The SAP Mobile Application Studio allows you to create or attach transport orders for change lists. Mobile Client The Mobile Client interacts with the  The Client Console is CRM Server through the used to set up the Communication Station: connection of the Mobile Client with the CRM  Initially to set up the connection of Server, and ConnTrans the Mobile Client with the CRM

01 2017 12

2 Planning

Server, and download the required is used to download the data from the CDB. required data.  Later to exchange data with CRM  ConnTrans is used to Server and receive specific client exchange data and upgrades. receive client upgrades. Workgroup Server The Workgroup Server interacts with  ConnTrans is used to the CRM Server: carry out these activities.  To perform the initial download of  The ConnTrans service data. schedules regular exchange of data  Later to exchange the data with the between the Workgroup CRM Server for its Workgroup Server and the CDB. Clients.

Structure The CRM Server contains the following technology, software, and databases required by mobile client applications.  CRM Server Applications Mobile client applications share master and transactional data with server applications such as CRM Enterprise, Internet Sales, and Contact Center.  CRM Middleware This component facilitates data distribution, and ensures data consistency across a network of distributed systems and databases. Mobile Clients, Back-end System and other SAP R/3 Systems (APO and BW) are connected to the CRM Server via CRM Middleware.  CRM Database It is a common database for all CRM Server applications. It contains a separate consolidated database (CDB) for mobile client applications. 2.1.2.3 Mobile Repository Server

Usage The Mobile Application Repository resides on this server. We recommend that you install the development, test, and production environment Mobile Application Repositories on separate machines

Definition It is a central hub containing a database that Mobile Development Workstations access when customizing mobile client applications. It is a mandatory machine in the typical landscape.

Integration The interaction of a Mobile Repository Server (MRS) with other machines in the landscape is described in the table below. Related machine Purpose of interaction Software used CRM Server MRS interacts with the CRM Server to: The MAR Transport Agent facilitates moving the client  Move client upgrade packages of the upgrade packages or customized mobile client application design time objects to the to the Mobile Clients. You can test CRM Server. the upgrade by having a test Mobile

01 2017 13 2 Planning

Client connected to the CRM Server through the Communication Station.  Move design time objects (transport) of the customized mobile client application to another MRS. Mobile Development The MDW interacts with the MRS to The SAP Mobile Workstation (MDW) access the Mobile Application Application Studio on Repository, when a mobile client MDW allows you to application is customized. connect to the MRS to access the Mobile Application Repository.

Structure The Mobile Repository Server contains the following: 1. Database a. Mobile Application Repository (MAR): It is a database that contains metadata of mobile client applications. 2. Tools a. Baseline Comparison tool: BLComparison.exe is used to compare baseline versions across Mobile Application Repositories. b. MAR Login Tool: This tool is used to change the password for the internal ARS user 'arssys'. c. MAR Transport Configurator: This tool is used to install and configure MAR Transport Service for a repository.

CustNsp.exe and BLComparison.exe are located in %mobilerootdir%\bin.net d. Mobile Upgrade Console: It is used to create upgrade packages of a customized mobile client application to be deployed on Mobile Clients. e. Mobile Client Upgrade Target: It is used to deploy upgrades on the Mobile Development Workstation. 3. Services a. SAP MAR Central Service: Provides Multi-User support for Mobile Application Repository. b. MAR Login Service: It is an internal ARS service performing User Management tasks. c. MAR Transport Agent: It is a component that handles transport of customized metadata between MRS and CRM Server.

01 2017 14

2 Planning

2.1.2.4 Mobile Development Workstation

Usage This machine contains software for system administration, development, and maintenance tasks. The software includes the following components.  Mobile Application Studio (MAS)  System Maintenance application for Mobile Sales, Mobile Sales Consumer Packaged Goods, Mobile Service and Mobile Sales Pharmaceuticals The MAS is an integrated development environment with which you can customize your Mobile Client Application. The MAS requires a connection to the Mobile Application Repository on the Mobile Repository Server. We recommend that you install the MAS on its own machine (or laptop). Doing so allows you to have several developers working on customization changes simultaneously. MAS Workstations can access the same repository concurrently. In the test and production environments, we recommend that one MAS Workstation be dedicated to the Mobile Application Repository on each Mobile Repository Server for emergency fixes.

Definition It is a workstation that contains various tools to customize, translate and create upgrade packages for mobile client applications. It is a mandatory machine in the typical landscape.

Integration The interaction of a Mobile Development Workstation (MDW) with other machines in the landscape is described in the table below. Related machine Purpose of interaction Software used CRM Server MDW interacts with the CRM Server  The SAP Mobile to: Application Studio allows you to connect to  Access the BDoc repository, while the BDoc repository. customizing the mobile client application.  The Client Console is used to retrieve BDoc  Retrieve BDoc repository changes (if repository changes. any).  The Mobile Client  Restore Mobile Clients, if required. Recovery Manager is  Create or attach transport orders used to restore the for/to the change lists. Mobile Clients that have lost data due to unavoidable reasons.  The SAP Mobile Application Studio allows you to create or attach transport orders for change lists. Mobile Repository MDW interacts with MRS to access The SAP Mobile Server (MRS) Mobile Application Repository (MAR), Application Studio on the while customizing a mobile client MDW allows you to application. It also uses MAR to connect to the MRS for temporarily store the client upgrade accessing MAR. data (runtime files), before sending it to the CRM Server.

01 2017 15 2 Planning

Structure The Mobile Development Workstation contains the following: 1. Database a. User Database: It is a database that contains application data of a mobile client application. 2. Mobile Development Package a. SAP Mobile Application Studio: It is a visual modeling tool that can be used to customize mobile client applications. b. Client Console: It is used to retrieve the BDoc changes made in the BDoc repository. c. Mobile Upgrade Console: It is used to create upgrade packages of a customized mobile client application to be deployed on Mobile Clients. d. Mobile Client Upgrade Target: It is used to deploy upgrades on the Mobile Development Workstation. e. Translation Tool: It is used to translate mobile client applications to different languages other than English and German. 3. Mobile Administration Tools a. Authorization Management Tool: Used to model authorizations for all mobile applications b. Mobile System Maintenance: Used to maintain Mobile-specific customizing for Mobile Applications c. Mobile Client Rollout Manager: It is used restore and rollout Mobile Clients. d. Namespace Reservation Tool: It is used to register the customer namespaces Y or Z that are provided by SAP by default. e. Mobile Client Package f. Contains the Mobile Client Framework, the Mobile Client Applications, IPC and Client Tools and Services. For more information refer to Mobile Client section. 2.1.2.5 Communication Station

Definition It is a machine used for:  Exchanging data between the Mobile Clients or the Workgroup Server with the consolidated database in the CRM Server. It is an optional machine in the development environment, but a required machine in the test and production environments of a typical landscape. However we recommend having a CommStation also in development environment.

Integration The interaction of a Communication Station with other machines in the landscape is described in the table below. Related machine Purpose of interaction Software used CRM Server The Communication Station interacts The ASCII Adapter with CRM Server to facilitate migration software is used for this.

01 2017 16

2 Planning

of master data from the Back-end System into the CDB of the CRM Server. Mobile Client The Mobile Client interacts with The ConnTrans software Communication Station to establish a installed on the Mobile connection with the CRM Server. Client is used for this. Workgroup Server The Workgroup Server interacts with The ConnTrans software Communication Station to establish a installed on the Workgroup connection with the CRM Server. Server is used for this.

Structure The Communication Station contains the following: 1. SAP .NET Connector: It is used to make RFC calls to the server from a windows application. It is the next generation for DCOM connector 2. CRM Message Transfer Service: It is the transfer service that is used by Conntrans to communicate to the server 3. NET4ABAP: It is a service running at the Commstation which is used by the CRM server for encryption of passwords for Mobile users. 4. SAP Gateway: These services enable SAP Systems and external programs to communicate with one another. CPI-C services can be used either in the ABAP program or for the external programs via the interfaces. 2.1.2.6 Mobile Client

Usage Sales and service representatives use the CRM Mobile Client Applications in or out of the office. You can choose among three types of Mobile Sales Applications.  Mobile Sales  Mobile Sales Consumer Packaged Goods  Mobile Sales Pharmaceuticals You can choose one Mobile Service Application.  Mobile Service Client Sales and Service Representatives use the CRM Mobile Client Applications in or out of the office.

Definition It is a laptop that always contains the latest (customized) version of mobile client applications. It also contains tools that are used for data exchange with CRM Server (ConnTrans). It allows you to use mobile client applications in the disconnected (offline) mode with the CRM Server when you are in the field and in the connected (online) mode when you want to exchange data with the CRM Server. It is an optional machine in the development environment, but a required machine in the test and production environments of a typical landscape. However we recommend having Mobile Clients available in development environment.

01 2017 17 2 Planning

Integration The interaction of a Mobile Client with other machines in the landscape is described in the table below. Related machine Purpose of interaction Software used CRM Server The Mobile Client interacts with the  The Client Console is CRM Server via Communication used to download data Station: from CDB.  Initially to download the required  The ConnTrans is data from CDB. used to exchange data and receive client  Later to exchange data with the upgrades. CDB and to receive specific client upgrades.

Structure A Mobile Client contains the following: 1. Database: a. User database: It is a database that contains application data of a mobile client application. 2. Mobile Client Package: a. Mobile Client Framework: Provides the Mobile Framework that is common across all installations b. Mobile Client Application(s): These are the applications such as Mobile Sales and Mobile Service that can be used in a disconnected mode with the CRM Server. c. Internet Pricing and Configurator: Tool that is used for pricing, taxation and configuration 3. Client Tools and Services: a. Mobile Client Upgrade Target: It is used to deploy upgrades on the Mobile Clients' b. Client Upgrade Deployer: This tool is used to re-run the failed MUPs which were received on the client machine. c. SAP Client Upgrade Helper Service: This service helps in deploying the Mobile Upgrade Package for a user without administrative privileges d. Client Console: It is a tool that is used to assign the site ID and to generate BDocs and tables. e. ConnTrans: It is a service that synchronizes application data between CDB and Mobile Clients. f. ConnTrans Service: It is used to run Conntrans as a service (without any UI). It can be used via scheduler to run conntrans at specific intervals via windows scheduler g. PDA Companion Service: This service pools the companion inbound queue (with an interval of 1 min) for entries from the device and triggers an import of data into the mobile laptop database.

01 2017 18

2 Planning

2.1.2.7 Workgroup Server

Usage

The Workgroup scenario allows a group of employees to share a User database on a common server. The server also contains the files required to enable the Workgroup Client applications to send data to the CRM server. In this case the Workgroup Server replicates data from the CRM server.

Definition It is a machine that contains a common user database, and facilitates the connected (online) mode of access with the CRM Server for all Workgroup Clients. It is an optional machine in the development and test environments and a mandatory machine in the production environment of a workgroup solution.

Integration The interaction of a Workgroup Server with other machines in the landscape is described in the table below. Related machine Purpose of interaction Software used CRM Server The Workgroup Server interacts with ConnTrans is used to carry the CRM Server through the out these activities. Communication Station to:  Initially download the required data from the CDB.  Exchange data with the CDB. Workgroup Client The Workgroup Client interacts with the Workgroup Server to store and retrieve data in/from the centrally located user database.

Structure A Workgroup Server contains the following: 1. Database: a. User database: It is a database that contains application data of a mobile client application. 2. Mobile Client Package: a. Contains the Mobile Client Framework, the Mobile Client Applications, IPC and Client Tools and Services. For more information refer to Mobile Client section. 2.1.2.8 Workgroup Client

Definition It is a desktop or a laptop that always contains the latest (customized) version of mobile client applications. It has a connected (online) mode of access to CRM Server through a Workgroup Server. It is an optional machine in the development and test environments, and a mandatory machine in the production environment of a workgroup solution.

01 2017 19 2 Planning

Integration The interaction of a Workgroup Client with other machines in the landscape is described in the table below. Related machine Purpose of interaction Software used Workgroup Client The Workgroup Client interacts with The ConnTrans is used to the Workgroup Server to store and carry out these activities. retrieve data in/from the centrally located user database.

Structure A Workgroup Client contains the following: 1. Mobile Client Package: a. Contains the Mobile Client Framework, the Mobile Client Applications, Client Tools and Services. For more information refer to Mobile Client section. 2.1.2.9 Non-CRM Machines The machines described below are used to add more business functionality to the mobile client applications. These are optional machines in the typical landscape.

SAP Business Information Warehouse The Business Information Warehouse is an end-to-end data warehouse solution that gives rapid access to data from SAP systems, from other enterprise applications, and from external sources. It can be used as an optional system for all SAP CRM scenarios in order to create reports and replicate them to the different offline Mobile Clients using CRM Middleware.

You need accurate, complete, and up-to-date information about your business. However, that information is spread on a wide variety of platforms and applications. In other words, getting hold of vital facts and figures can be a complex and time-consuming task. SAP offers you a quick and easy way to gain access to the information you need via the SAP Business Information Warehouse. For example, all the predefined reports, this can be used to:  Evaluate the sales and distribution data from CRM Marketing (Internet Sales Scenario)  Perform effective telemarketing campaign analysis (Contact Center Scenario) For more information, see SAP Business Information Warehouse (SAP BW) online help in the SAP Library. SAP Advanced Planner and Optimizer The SAP Advanced Planner & Optimizer (SAP APO) is SAP's supply chain planning solution, which offers best planning features and seamless integration with the CRM Server. It can be used as an optional system for the Field Sales scenario. It is used to check the product availability for real-time planning and decision support.

Supply chain planning is a major component to improve the performance of a company's supply chain and leads to shareholder value creation. The major benefits are increased customer service, reduced inventories, cycle-time compression, and lower supply chain variability. For more information, see SAP Advanced Planner and Optimizer (SAP APO) online help in the SAP Library.

01 2017 20

2 Planning

2.2 Installation Sequence 2.2.1 Overview of Upgrade Process [flowchart] Some machines can be set up in parallel, while others are dependent. Refer to the tree structure to determine the dependencies and hierarchical structure of the development environment. You must install software on the machines in the left-most positions before you install software on machines positioned further to the right. You can install software in parallel on machines which are located at the same indention level.

01 2017 21 2 Planning

2.2.1.1 Development Environment Installation Process After you install the CRM server, make sure that you have all components in place for the Mobile Client Component Applications scenario. In the development environment, you must install software on the CRM Server, the Mobile Repository Server, and the Mobile Development Workstation. These machines and the back-end system are mandatory for the Mobile Sales Development environment. The other machines are optional, unless you want to perform the initial download and do some preliminary testing in the development environment before moving into the test environment.

We recommend that you use the same setup in your development, test, and production environments. This ensures that you develop and test in an environment similar to the environment you use productively. 2.2.1.2 Test and Production Environment Installation Process After you install the CRM server, make sure that you have all components in place for the Mobile Client Component: Applications scenario. In the test environment, you must install software on the CRM Server, the Mobile Repository Server, the Mobile Development Workstation, the Mobile Admin Workstation and the Mobile Client for a typical solution. If you are using the Workgroup solution, then you must have software installed on a Workgroup Server as well.

01 2017 22

2 Planning

2.3 Prerequisites 2.3.1 Hardware Requirements A DVD ROM drive is required to Install the Mobile Client Release 7.01 SP06 using the Install DVD.

The following hardware requirements are based on average system load and use. Requirements can vary depending on your system's load and usage levels.

Requirements Machine Processor Memory Free Disk Space Mobile Repository Intel Pentium IV - or 3 GB Minimum 4 GB, plus Server compatible – 1,5 GHz required space for the ars_db database Mobile Development Intel Pentium IV - or 3 GB 4 GB, plus required Workstation compatible – 2 GHz space for the ides database Communication Pentium IV – or 2 GB 4 GB station compatible - with 2 GHz 4 GB recommended, when more than 10 clients are connected Mobile client Intel Pentium IV - or 1 GB 4 GB, plus required compatible – 1 GHz space for the ides 2 GB recommended database for high data volume and optimal performance Personal Digital Intel(R) PXA270 32 MB 1 MB (for standard SAP Assistant application files).If the customer adds additional tiles, this size will change. In addition, space for the user database is required. Workgroup Solution Workgroup Server Intel Pentium IV – or 2 GB 4 GB, plus required compatible – 2 GHz space for the ides 4 GB recommended, database when more than 10 clients are connected Workgroup Client Intel Pentium IV – or 1 GB 4 GB compatible- 1 GHz

The Workgroup Server must have a default printer set up.

01 2017 23 2 Planning

Please be aware, that any combination that is not included in the hardware section but could be supported by other SAP applications is not supported by Mobile Client.

If the total number of records in a fresh Mobile Client Companion database is around 40,000 records, then the approximate size of the mdf file will be 15 MB. The size of the user database on a Mobile Client is directly proportional to the amount of data downloaded to the Mobile Client from the CRM Server. The size of the user database on a Mobile Client Companion is directly proportional to the amount of data downloaded to it from the Mobile Client. 2.3.2 Software Requirements The following prerequisites must be fulfilled for installing the SAP CRM Mobile Client Component to Release 7.01 SP06.

You can install the Mobile Client Component Release 7.01 SP06 only after fulfilling the prerequisites defined in this section. The machine names tell where the software is necessary.

01 2017 24

2 Planning

2.3.2.1 General Software Requirements

x64 bit applications which are not mentioned below, their x32 bit version is valid as prerequisites.

Mobile Mobile Software Communica Workgroup Workgroup Repository Development Mobile Client Prerequisites tion Station Server Client Server Workstation

 Windows 7  Windows  Windows 8  Windows 7 Server 2003  Windows 8  Windows  Windows  Windows 7 SP02 or 2008 8.1  Windows Server: 2003  Windows 8  Windows 10 (CRM SP02 or  Windows 7  Windows 10 (CRM Mobile 7.01 2008 10 (CRM  Windows Mobile 7.01 SP 06  Windows 8 Mobile  Windows 7 2003 SP 06 Patch 6 7.01 SP 06  Windows 10 Server Patch 6 onwards) Microsoft  Windows 8 Patch 6 (CRM Mobile SP02 or onwards)  Vista Windows onwards) 7.01 SP 06 2008  Vista Enterprise Operating System  Windows 10  Vista Patch 6  XP SP02 Enterprise Edition (CRM Mobile Enterprise x32 bit or x64 bit onwards) or SP03 Edition SP01 7.01 SP 06 Edition Prof. SP01  XP SP02 Patch 6  XP SP02 SP01 onwards) Edition  XP SP02 or SP03 SP03 Prof.  XP SP02 or SP03 Prof. Edition or SP03  XP SP02 or Prof. Edition or Prof. SP03 Prof.  Vista Edition or XP Tablet Edition Edition Enterprise XP Tablet Edition Edition SP01 Edition SP2 SP2  7.0 SP00  7.0 SP00  7.0 SP00  7.0 SP00 Microsoft Internet  8.0  8.0  8.0  8.0 Explorer  9.0  9.0  9.0  9.0 x32 bit or x64 bit  10.0  10.0  10.0  10.0  11.0  11.0  11.0  11.0 Express, Express, or Standard or Standard Edition Standard or Standard or Edition  2005 SP01 Enterprise Enterprise  2005 SP01 to SP03 Edition Edition to SP03  2008  2005 SP01  2005 SP01  2008 to SP03 to SP03  2008 R2  2008 R2  2008  2008  2014 Microsoft SQL  2014 (CRM (CRM  2014 (CRM  2014 (CRM Server Mobile 7.01 Mobile Mobile 7.01 Mobile 7.01 SP 06 7.01 SP 06 x32 bit or x64 bit SP 06 Patch SP 06 Patch Patch 6 Patch 6 6 onwards) 6 onwards) onwards) onwards)  2016 (CRM  2016 (CRM  2016 (CRM  2016 Mobile 7.01 Mobile 7.01 Mobile 7.01 (CRM SP 06 Patch SP 06 Patch SP 06 Mobile 6 onwards) 6 onwards) Patch 6 7.01 SP 06 onwards) Patch 6 onwards) Microsoft .NET Runtime Framework Runtime 3.5 Runtime 3.5 Runtime 3.5 Runtime 3.5 Runtime 3.5 3.5 x32 bit

01 2017 25 2 Planning

Microsoft Visual Studio.NET Microsoft Visual 2008

Studio Professional or Enterprise Edition

Microsoft Office Setup (Select  XP  XP  XP  XP Custom Install  2003  2003  2003  2003 and choose Word,  2007  2007  2007  2007 Excel and  2010  2010  2010  2010 Outlook)  2013  2013  2013  2013 x32 bit SUN Java 2 Software Development Kit 1.5.0 1.5.0 1.5.0 x32 bit Sun Microsystems Java Runtime 1.5.0 1.5.0 1.5.0 1.5.0 Environment x32 bit Adobe Acrobat 9.0 9.0 9.0 9.0 9.0 9.0 Reader (Optional)

Lotus Notes 6.0 or 6.5 or 7.0 6.0 or 6.5 or 6.0 or 6.5 or

(Optional) or 8.0 7.0 or 8.0 7.0 or 8.0

SAP Business Objects Crystal 9.0 or 10.0 or 9.0 or 10.0 or 9.0 or 10.0 or Reports 11.0 or 2008 11.0 or 2008 11.0 or 2008 (Designer) – (Optional)

BEX 7.0

01 2017 26

2 Planning

Additional Information: Software Additional Information Microsoft Windows  Only English international version is supported on the CommStation.

Refer to Note 2415389 for the list of limitations on Windows 10

Communication Station can be installed on 32 bit and 64 bit processors for all the above operating system versions. Also refer to Note 1241004 for NET4ABAP service on 64 bit systems. However, for 64 bit systems, the Communication Station  can be installed on 64 bit AMD64 platform  cannot be installed on a 64 bit IA64 platform

Microsoft SQL Server Refer to Appendix C for the codepage settings for the different languages.

For SQL Server 2016, SQL management studio has to be installed separately. Only the following versions are supported: Microsoft SQL Server 2016 Standard Edition (64-bit) RTM Microsoft SQL Server 2016 Enterprise Edition: Core-based Licensing (64-bit) RTM Microsoft SQL Server 2016 Enterprise Edition (64-bit) RTM Microsoft SQL Server 2016 Developer Edition (64-bit) RTM Microsoft SQL Server 2016 Express Edition with Advanced Services (64-bit) RTM Microsoft SQL Server 2016 Express Edition (64-bit) RTM Microsoft SQL Server 2016 Express Edition (64-bit) SP1

For information about compatibility between different versions of Microsoft Windows and Microsoft SQL Server, see the documentation provided by Microsoft at http://msdn.microsoft.com/en-us/library/ms143506(SQL.90).aspx

For MSSQL Server 2005 SP02 Express edition, the backward compatibility setup needs to be installed from the following location from Microsoft. 1. Go to the following Link: http://www.microsoft.com/downloads/details.aspx?FamilyID=d 09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en.

01 2017 27 2 Planning

2. Go to the section "Microsoft SQL Server 2005 Backward Compatibility Components" 3. Install 'X86 Package (SQLServer2005_BC.msi)'.

The following link to MSDN describes how to connect remotely to Microsoft SQL 2005: http://support.microsoft.com/kb/914277

MSSQL Server installation should be checked for ‘Mixed mode’ and ‘Default instance’ during installation.

Some of the Microsoft SQL Server Editions (Express) have size limitations on the maximum size of the database file that can be handled by the server. For more information on threshold values and other configuration details, please refer Microsoft website to get updated results.

Please refer to the Microsoft website for information on the terms of use and restrictions for the individual product versions.

Microsoft SQL Server allows you to install several (named) instances. The SAP CRM Mobile Client Component databases must be installed in the default instance of Microsoft SQL Server. For more information about SQL Server instances, see the documentation provided by Microsoft at www.microsoft.com

Microsoft Visual Studio Visual Basic .Net must be installed along with Visual Studio IDE.

Microsoft Visual Studio Documentation should be installed with Microsoft Visual Studio installation

Microsoft Office If you want to use Microsoft Office 2007, consider the following note: Note 1224853: Microsoft Office 2007 support in Mobile Applications JDK, JRE If IPC, Survey or sign-control is used on the given machine, SDK is required – else, JRE is sufficient.

Use the following Link to download the required JDK/JRE: http://java.sun.com/products/archive/ → JDK/JRE - 5.0 Adobe Acrobat Necessary to view documentation Reader

01 2017 28

2 Planning

Optional: For Integration with Mobile Client Daily Activities / Calendar Microsoft Outlook Or Lotus Notes If you have Microsoft Outlook or Lotus, please make sure you have the ‘default mail client’ set. Optional: For designing your own reports SAP Business Objects Crystal Reports Installation of the Microsoft .Net Framework 1. To install the latest version of the Microsoft .Net Framework Package, Go to http://www.microsoft.com/downloads, type ‘.NET Framework Version 3.5 Redistributable Package’ In the search all download center text box and press enter. 2. Download the .NET Framework Version 3.5 Redistributable Package.

If an older version of the .NET Framework exists on the system, uninstall the same before you install the 3.5 3. Ensure that the system requirements provided in the instructions are met. To check if the package is successfully installed: Choose Start  Settings  Control Panel  Add/Remove Programs. The Microsoft .Net Framework 3.5 must be part of the currently installed programs. 3.3.2.2 Additional Software Requirements for Mobile Sales PDA Companion Additional Requirements for Mobile Sales PDA Companion Machine Application Software needed Additional Information Windows Mobile This software is present with Companion  2003 Second Edition or installation of the Microsoft .NET  Windows Mobile 2005 only Visual Studio, however do check for the latest SP releases. Microsoft .NET Compact Companion Framework Runtime 2.0 Redistributable (SP2 or above) Microsoft SQL Mobile 2005 Companion (Including SQL Mobile 2005 Replication) SQL Client 2.0 Companion Microsoft ActiveSync 4.0 or higher Based on device requirements Mobile Client, MRS, MDW Windows Mobile 5.0 SDK MRS, MDW

01 2017 29 2 Planning

Embedded Visual Tools 3.0 This is required only for migration MRS, MDW (Install embedded Visual Tools 3.0 and Microsoft Windows SDK for Pocket PC 2002).

As Microsoft ActiveSync is not supported on Microsoft Vista Operating Systems, the software package "Microsoft Windows Mobile Device Center 6 for Windows Vista (32-bit)" need be installed on Microsoft Vista Operating Systems.

Also see Note 1152312: Window Vista OS support for SAP CRM Mobile runtime

01 2017 30

3 Cross CRM support for CRM Mobile

3 Cross CRM support for CRM Mobile In a CRM Mobile landscape, there exists a CRM server and few hundreds of Mobile sales laptops. In a typical upgrade scenario the CRM server is upgraded to a higher version followed by the upgrade of all Mobile clients. The period after CRM server is upgraded and before the Mobile clients are upgraded can be a production down scenario. The Mobile clients may not be able to communicate to the CRM server which is of a higher release. In order to minimize this down time, the steps mentioned in the document under the specific areas/components will help.

Purpose The purpose of this section is to give the end user, the necessary steps to make a lower version of CRM Mobile client to be able to communicate/work with a higher version of CRM server. The lower version of CRM Mobile here is CRM 7.01 SP06 and the higher version of CRM server is CRM 7.0 EHP2.

Constraints This section does not explain how to install the back-end system and the SAP CRM server. It assumes that these are already in place.

3.1 Supported CRM Server Releases with 7.0 EHP1 SP06 All higher CRM releases like EHP3 can also be included.

CRM Release Service Packs

5.0 >= SP09

6.0 >= SP02

7.0 >= SP01

7.01 >= SP01

7.02 >= SP01

3.2 Prerequisites steps for CRM Mobile 7.01 with CRM Server 7.0 EHP2

Supported CRM Server Releases with CRM Mobile 7.01SP06 are listed in the previous section. Section 3.2 is an example scenario and it is valid for all the CRM Server releases listed above.

Scenario: CRM server is in the version 7.01 and is due for an upgrade. The Mobile clients, Mobile development work bench and the Application repository system are in version CRM 7.01 SP06 and the landscape is integrated.

CRM server will be upgraded to CRM 7.0 EHP2.

01 2017 31 3 Cross CRM support for CRM Mobile

3.3 Components 3.3.1 Mobile Repository Server Mobile Repository Server is the machine where the Application repository is installed .The application repository is a database which hosts all the development objects. ARS repository corresponding to Release CRM Mobile 7.01 SP06 can be used with CRM Server 7.0 EHP2.

Apply the following note, if you are using MS Windows XP SP02: SAP Note 960057: Unable to access ARS on WinXPSP2 due to firewall SAP Note 925881: Resolve: Port Conflict of Central Service and Upgrade Service

Transport Service is used to export the changelist created in one ARS Repository to another ARS Repository using the CRM Server. We can continue to use the same Transport Service with CRM Server 7.0 EHP2. 3.3.2 Mobile Development Workstation Mobile development workstation machine hosts the Mobile Application Studio and other development tools using which we model the application by creating new objects and modify the existing objects, generate and build the application. Mobile development workstation can be used with CRM Server 7.0 EHP2 for activities like Bdoc sync from Mobile application studio, Changelist release (Transport Order). Once the CRM Server is upgraded to 7.0 EHP2 version start a complete Bdoc Sync from MAS before starting with any changes in Mobile Application Studio.

SAP Note 1376656: Design Time Framework Mandatory Fixes

Mobile Upgrade packages (.mup files) are used to deploy files on a Mobile development machine or the Mobile client machine .You can use the same MUP files created on Development workstation of CRM Mobile 7.01 SP06 with CRM Server 7.0 EHP2.

SAP Note 1156416: Latest Client Upgrade Fixes 3.3.3 CRM Mobile – Middleware components 3.3.3.1 Communication Station The Mobile Client, which is part of the SAP CRM solution, is primarily offline. However, to synchronize data, the Mobile Client needs to connect to the CRM server. The communication station allows mobile clients to establish the connection to the CRM server.

SAP does not recommend the installation of the communication station and the Mobile Client on the same machine, as this affects the MTS registry settings and the components may not function as expected.

01 2017 32

3 Cross CRM support for CRM Mobile

A Communication Station belonging to a lower SP (like 7.01 SP06) is compatible with higher CRM server releases (like 7.0 EhP2).

SAP Note 1255658: CommStation Performance Improvement with Application Pooling SAP Note 1022089: Troubleshooting CommStation 3.3.3.2 Client Console A ClientConsole belonging to a lower SP (like 7.01 SP06) is compatible with higher CRM Server releases (like 7.0 EhP2). Indexes for the Mobile Client database (IDES) are consolidated to retain the indexes delivered by SAP for CRM Mobile Client as well as any indexes that the customer may have created or modified for CRM Mobile Client from lower versions. You must generate the appropriate BDoc/table index scripts using the Client Console when connected to the 70 EHP2 CRM server. All BDoc metadata would be available in file TPS.NET and Table/Index Scripts would be present in TableIndexScripts.sql. This generation can be done on the Mobile Development Workstation (MDW) and the using the below 2 units, these changes can be distributed to mobile clients using an MUP.  Deploy Index Changes - This unit updates the index changes made to the application tables. It contains the index script generated by the Client Console.  Deploy BDOC Changes - This unit updates the client with BDoc changes. Generation of Table Scripts To generate the table scripts and corresponding TPS.Net files using Client Console follow the below mentioned steps:

1. Select the type of script to be generated. a. Client Console can generate scripts for Unicode and Non Unicode Solution. b. Ensure that the option selected is compatible with the installed solution in terms of being Unicode or Non Unicode. 2. Select the generation type. a. The following options are available: i. Tables and Indexes: Generates both tables and Indexes. ii. Tables Only: Generates the tables only without indexes iii. Indexes Only: Generates only the indexes for the selected tables. 3. Select tables a. The following options are available: i. Selected Tables: Generates script for only the selected table. ii. All tables: Generates for all the tables fetched from the server. iii. Generates all tables fetched from a specified text file. iv. Advanced Selection Criteria: Lists additional parameters based on which tables can be further filtered. 4. Index Selection - This step is valid only if generation of the index has been selected in Step 3. a. The following options are available for this step: i. All Indexes: Generates index for all tables listed ii. Delta Indexes: Generates all delta indexes by comparing the timestamp of the indexes created at the server. iii. Modified between: All indexes modified within the data range specified. 5. Select the type of script to be generated. a. The following options are available for this step:

01 2017 33 3 Cross CRM support for CRM Mobile

i. Generate Delta Table Script: Generated only the delta changes in the tables. If this check box is not selected it carries out a full generation of the selected tables. ii. It generates additional scripts for Upgrade.sql in the bin.net directory. Normally this is not required. iii. This is used for the generation of middleware specific and populating them with some specific values. This is not related to any application and is only used by middleware. 6. Log scripts a. Log scripts to file: This is be used to log the generated script to a .sql file at a specific location. b. Execute on user database: Executes the scripts directly on the IDES.

SAP Note 1111613: Client Console HOTFIX for CRM Mobile 2007 and above SAP Note 1071267: Middleware HOTFIX for Mobile Clients 3.3.3.3 Conntrans While Client Console is used to set up the connection of the Mobile Client with the CRM server, ConnTrans is used to download the actual data. ConnTrans is used to exchange data and receive client upgrades (in the form of MUP files). Thus it acts as a synchronizing application for data exchanged between the CDB and Mobile Clients.

Conntrans.exe belonging to a lower SP (like 7.01 SP06) is compatible with higher CRM server releases (like 7.0 EhP2). 3.3.4 CRM Mobile – Application The Mobile Client hosts field applications which are the key capability within SAP CRM providing marketing, sales and service functionality in an offline environment. These applications with their rich set of functionalities provide a comprehensive support to users in their day to day work. The Mobile Client corresponding to the release 7.01 SP06 can be used with CRM Server 7.0 EHP2.

SAP Note 1385052: Mobile Client Runtime Framework Fixes from 5.0 SP11 SAP Note 1510637: Survey in Mobile Client Application-consolidated SAP Note 1153209: CRM Mobile client: Reporting framework files

In addition to bug-fixes the below feature which is added as a part of CRM Mobile Release 7.0 EHP1, would not be available.

Cancel button in the Custom Pop-up for Selection of Sales The cancel button in the custom pop-up for selection of Sales area for a Business Partner would not be available in the Mobile Client of Release 7.0 SP04 (below).

01 2017 34

4 Preparation

4 Preparation The installation tools first check the machine to ensure that the prerequisite hardware and software components exist. If the installation program cannot find the prerequisite software and hardware, it sends error messages and aborts the installation process. The installation also checks for the user's authorization. You must have administrator rights in Microsoft Windows operating system in order to install the Mobile Client Component and Applications. 4.1 Content of Installation DVD CRM Mobile Client Installation (SAPDVD: Mobile Client Installation) contains the following directories and software. This directory... Contains... Communication Station The SAP Communications setup program. Consolidated_Prefill Consolidated Prefill file which contains the customizing data MARLanguageInstallation Additional Mobile Application Repository Languages. Mobile_Client_Installation Files and folders required for the installation of Mobile Client. SwitchDB The Files for the Tool SwitchDB

The following table lists the different languages, their corresponding code pages, and the directories in which the databases for the different code pages can be found. Make sure to install the Microsoft SQL Server / Microsoft Data Engine (MSDE) with the language (code page configuration) that matches the operating system language. Language Code Page Corresponding DVD and Database Directory Greek EL SAPDVD: Mobile Client Installation\databases\EL Hebrew HE SAPDVD: Mobile Client Installation\databases\HE Japanese JA SAPDVD: Mobile Client Installation\databases\JA Korean KO SAPDVD: Mobile Client Installation\databases\KO Latin1 Latin1 SAPDVD: Mobile Client Installation\databases\Latin1 Latin2 Latin2 SAPDVD: Mobile Client Installation\databases\Latin2 Russian (Cyrillic) RU SAPDVD: Mobile Client Installation\databases\RU Turkish TR SAPDVD: Mobile Client Installation\databases\TR Unicode Unicode SAPDVD: Mobile Client Installation\databases\Unicode Chinese (Taiwan) ZF SAPDVD: Mobile Client Installation\databases\ZF Chinese ZH SAPDVD: Mobile Client Installation\databases\ZH

You must set up the code page information during the installation of Microsoft SQL Server or Microsoft Data Engine. This installation must be completed prior to installing the Mobile Client software.

Also refer to Appendix C for the codepage settings for the different languages.

01 2017 35 5 Installation

5 Installation

Starting Installation 1. Insert the DVD labeled Mobile Client Installation in the DVD drive. 2. In the directory, choose start.exe.

3. Choose Start Installation.

01 2017 36

5 Installation

In case of pending reboots you will receive a warning message on this screen. To avoid issues, we recommend you to do a reboot before continuing with the Mobile Installation.

Choosing the Question Mark on the top right hand side will open the Installation Guide In case you have a running MSA-installation on your machine, the following error will be shown.

Make sure you have no mobile client installed when running a fresh installation. 4. Choose Next to continue the installation process.

Depending on which machine you want to install, choose ‘Mobile Repository Server’, ‘Mobile Development Workstation’ or ‘Mobile Client Setup’. While the ‘Mobile Repository Server’ only allows you to install the MRS, the option ‘Mobile Development Workstation’ also provides the possibility to install a local Mobile Application Repository.

01 2017 37 5 Installation

5.1 Installing Mobile Repository Server 5.1.1 Prerequisites

Make sure, that the software and hardware requirements have been met.

Apply the following note, if you are using MS Windows XP SP02: Note 960057: Unable to access ARS on WinXPSP2 due to firewall

Make sure to install the Mobile Repository Server on separate machines for each environment you want to use; development, test, and production. For further information also see section system landscape.

If you want to install the Mobile Application Repository on the same machine as the Mobile Development Workstation, continue with the section Installing Mobile Development Workstation. However we recommend to install MRS and MDW on separate machines due to performance reasons. 5.1.2 Procedure 1. Select the solution ‘Mobile Repository Server’ by selecting the appropriate radio button.

01 2017 38

5 Installation

The following options are available

Select… Then...

Mobile Repository Server The Mobile Repository Server is selected by default and cannot be deselected. This installation includes the Mobile Repository and the associated tools. Mobile Client Framework The Mobile Client Framework is selected by default and cannot be deselected. It provides the mobile framework which is common across all installations. 2. Choose Next.

The prerequisite check tells you, if all necessary software requirements are met. If this is not the case, the installer will not allow you to continue.

Choosing the Button System Information will give you an overview of the hardware and software of the given machine. 3. Choose Next.

01 2017 39 5 Installation

 The standard installation path for the installation's destination folder on your PC will be defaulted. If you want to change it, choose Browse to use a customized path as the installation's destination folder.

If you choose a different destination folder, the installation program insures that the path string contains...\SAP\Mobile\ at the end.  If you want to review the items you selected to install, choose Selection Summary. This screen provides you the possibility to save the summary as textfile.

01 2017 40

5 Installation

 If you want to change the items you selected to install, choose Back.  If you want to save the configuration for this installation, choose Save Configuration, and then choose the file to install. Saving the configuration allows you to install the same configuration repeatedly, by storing the settings in an IUP file. 4. Choose Install to start the installation process for the Mobile Repository Server.

01 2017 41 5 Installation

5. When the installation process finishes, the following screen appears.

 The Button View Log provides a log-file on the installation process. In case installation did not finish successfully, the logfile should help further in finding the reason.

6. Choose Done. Reboot the system to start the various required services. You have installed the SAP CRM Mobile Client Component: Application Repository for the Mobile Repository Server.

 If you receive a message Locked file detected, choose OK, and continue rebooting the machine. This message does not affect the installation.  The default login information for the Mobile Application Repository is DSN: ars_db User: arsadmin Password:

01 2017 42

5 Installation

5.1.3 Mobile Application Repository Language Installation By default, text objects in a CRM MAR are available in English and German. To import additional languages for the first time, a special Application Repository Package called Language Installation Package is provided. This section provides an overview of the Language Installation Package and describes the procedure to install the package. In SAP CRM Mobile 7.01 SP06, you can install the following non default languages: Arabic, Italian, Spanish, French, Portuguese, Dutch, Japanese, Chinese (simplified), Chinese (traditional), Korean, Czech, Danish, Finnish, Greek, Hebrew, Swedish, Polish, Hungarian, Slovak, Russian, Turkish, Norwegian, Slovenian and Croatian.

Freshly installed languages correspond to Release 7.01 SP06.

Note 1799687: CRM Mobile Client Component: Installation/Upgrade 7.01 SP06 5.1.3.1 Installing the Language Installation Package

Installation of the Language Installation Package requires approximately 1.6 GB of disk space. Without this amount of disk space, setup.exe fails.

In addition, the import of change lists into the repository database requires disk space as well. The amount of disk space required depends on the number of languages installed. If sufficient disk space is not available during runtime, the language installation fails.  On your Installation DVD open the folder MARLanguageInstallation  Double-click Setup.exe to trigger installation of the Language Installation Package.

You must install the Language Installation Package on the machine where the MAR database is located. The installation takes approximately two minutes and creates a shortcut named SAP CRM 7.01 SP06 (7.0EhP1 SP06) Mobile Application Repository Language Installation Tool on the desktop. 5.1.3.2 Running the Language Installation Package

Prerequisites  You have created a backup of the repository that you want to upgrade.  No user is working on the repository during the language installation.  No transport service is running on the repository that you want to update.

Procedure

The user interface for the language installation is the same as for a standard repository upgrade. To access documentation about the tool, choose Manual on the menu. If this is the first time that you are working with the language installation package before, read the complete documentation before you run the package.

01 2017 43 5 Installation

1. Double-click the SAP CRM 7.01 SP06 (7.0EhP1 SP06) Mobile Application Repository Language Installation tool shortcut on your desktop. The following screen appears.

2. Choose Start Update. The CRM Mobile Application Repository Update screen appears. If the login to the specified database is successful, the tool determines the release version of the repository database. This information appears in a dialog box as shown below.

The release version of the database has to match the supported start releases 3. Select the language(s) that you want to install.

The time required for the language installation depends on the hardware used and the amount of data (text objects) that is imported. Tests have shown that

01 2017 44

5 Installation

it takes approximately an hour and a half, on average, to install a non-default language. 5.1.3.3 Uninstalling the Language Installation Package 1. Choose Start  Settings  Control Panel  Add/Remove Programs. 2. Choose SAP CRM 7.01 SP06 (7.0EhP1 SP06) Mobile Application Repository Language Installation Tool and choose Remove. The files that were copied to the target machine during installation are deleted. The other files are not affected.

01 2017 45 5 Installation

5.2 Installing Mobile Development Workstation

1. Select the solution ‘Mobile Development Workstation’ by selecting the appropriate radio button.

The following options are available

Select… Then...

01 2017 46

5 Installation

Mobile Application Studio The Mobile Application Studio is selected by default and cannot be deselected. It installs the design time tool to develop and change Mobile Applications. Local Design Repository If you would like to install the repository on the same machine as the Mobile Development Workstation, check the Local Design Repository checkbox.

Make sure, that the required software has been installed. Admin Applications Provides Administrative Tools for the Mobile Application.  Authorization Management Tool (AMT)  AMT is used to model authorizations for the mobile  Mobile System applications Maintenance (MSY)  MSY is used to maintain mobile specific customizing

Development and Deployment This tool is selected by default and cannot be Tools deselected. It is required for design and deployment activities

Mobile Applications Contains the setup for the Mobile Sales and Service Applications:  Mobile Sales Application (MSA)  MSA: Standard Mobile Sales Application  Mobile Service Application  MSV: Standard Mobile Service Application (MSV)  Mobile Sales  MSP: Sales Application containing special features Pharmaceuticals (MSP) for the Pharmaceutical Industry  Mobile Sales Consumer  MSC: Sales Application containing special features Goods (MSC) for the Consumer Goods Industry

You can install several mobile client applications simultaneously. Choose all applications you would like to install. Mobile Addons Provides additional features for the Mobile Applications:

 Internet Pricing and  IPC: Used to enable Pricing, Taxation and Configurator (IPC) Configuration.

User Database You can choose the following options:

 Demo User Database  The demo version uses a prefilled demo User  Unicode Database database; this database is not replicated with the CRM Server. If you do not choose this option, an empty User

01 2017 47 5 Installation

database will get installed.

 Installs the User Database in Unicode Collation

Mobile Client Framework The Mobile Client Framework is selected by default and cannot be deselected. Provides the mobile framework which is common across all installations.

The Mobile Application Studio requires that you install at least one type of Mobile Client Application on the machine. But you can also choose to install only the framework by checking Install Mobile Client Framework Only option. 2. Choose Next.

Depending on the default collation (code page) setting of your database server, you can receive the following screen with the appropriate Codepage enabled. For support purposes, the English version of the software is always installed.

 Select the appropriate language or languages that you want to install.

You must ensure that the language(s) match the Microsoft SQL Server / Microsoft Data Engine code page. For more information, see Content of the Installation DVD and Appendix C.

You have to set at least one language, else you won’t be allowed to continue.  Provide the Configuration settings:

Some options in the configuration section of the screen might appear disabled based on the Addons that got selected.

01 2017 48

5 Installation

When you have chosen to install the Demo User Database, the setting for the Communication Station will get disabled. In case you have chosen to install a Local Design Repository, the Mobile Repository Server will get defaulted with the local machine name.

Field Description

Communication Station  Enter the IP Address or the Server name of the Communication Station.

Mobile Repository Server  Enter the IP Address or the Server name of the Mobile Application Repository. This field will get defaulted to the local machine, if you chose to install the Local Design Repository

Workgroup Server  For MDW this field is not enabled

The installation does not check the connection to the Communication Station or Mobile Repository Server. Make sure that you have typed the IP address or the name properly. It is possible to keep the Connection to the Communication Station and the Application Repository empty and update them later.

3. Choose Next.

The prerequisite check tells you, if all necessary software requirements are met. If this is not the case, the installer will not allow you to continue.

01 2017 49 5 Installation

Choosing the Button System Information will give you an overview of the hardware and software of the given machine. 4. Choose Next.

01 2017 50

5 Installation

If you want to change the items you selected to install, choose Back.  If you want to save the configuration for this installation, choose Save Configuration, and then choose the file to install. Saving the configuration allows you to install the same configuration repeatedly, by storing the settings in an IUP file. 5. Choose Install to start the installation process for the Mobile Development Workstation.

01 2017 51 5 Installation

7. When the installation process finishes, the following screen appears.

 The Button View Log provides a log-file on the installation process. In case installation did not finish successfully, the logfile should help further in finding the reason.

6. Choose Done. Reboot the system to start the various required services. You have installed the SAP CRM Mobile Client Component: Applications for the Mobile Development Workstation.

 Apply SAP Note 433855 for installing the Internet Pricing and Configurator to work with the Mobile Client Applications.  The default login information for the Mobile Application Studio is DSN: ars_db User: arsadmin Password:

01 2017 52

5 Installation

5.3 Installing Communication Station 5.3.1 Introduction The mobile client, which is part of the SAP CRM solution, is primarily offline. However, to synchronize data, the mobile client needs to connect to the CRM server. The Communication Station allows mobile clients to establish the connection to the CRM server. The following section provides information on how to install the Communication Station for CRM 7.0.

Purpose

The CRM Landscape To understand how the communication station interacts with the different systems, you need to understand the CRM landscape. The following figures, Figure 1 and Figure 2 display the main components in a development/production environment. Figure 3 displays the services that refer to the Communication Station. All mobile clients from within and outside the firewall connect to the Communication Station for data exchange as it maintains a connection to the CRM Server.

Figure 1: The CRM Development Landscape

Figure 2: The CRM Production Landscape

01 2017 53 5 Installation

The scenarios displayed in the above mentioned figures are recommended by SAP. However, based on the number of Mobile clients, you can use more CommStations. As a result, you can install each component on a dedicated server or install all the components on the same machine. However, SAP does not recommend the installation of the Communication Station and the Mobile Client on the same machine, as this affects the MTS registry settings and the components may not function as expected.

Communication Station

Messaging: Password encryption: Monitoring: SAP .NET Connector NET4ABAP / SAP Gateway SAP OS Collector Message Transfer Service MTS

CRM Server (Middleware Broker)

Mobile Client Figure 3: Services on the Communication Station

01 2017 54

5 Installation

5.3.2 Installation Planning 5.3.2.1 Installation Process [flowchart]

01 2017 55 5 Installation

5.3.2.2 Hardware and Software Requirements The following table lists the requirements. The host machine must meet the following requirements: Requirement Type Requirement Hardware For Hardware and Software Requirements see the Prerequisites Requirements section Software Requirements Installation DVDs  CRM Mobile Server Components ..\Communication Station – Contains the installation files for the communication station and monitoring  CRM Mobile Client Installation ..\Mobile_Client_Installation\vsrtl – Contains the runtime libraries for the Microsoft Visual Studio

The CRM Mobile DVDs are part of the CRM 7.01 SP01 Mobile Client Installation and Upgrade DVD. Therefore, you can either use the DVD or create individual CDs from this DVD. This is applicable for all the references to the CRM Mobile DVDs in this guide. 5.3.3 Installation Process 5.3.3.1 Installation of the Visual Studio Runtime Environment 1. Insert the CRM Mobile Client Installation DVD into the CD ROM drive. 2. Go to :\Mobile_Client_Installation\vsrtl\SAP_Customised_MS_VSRTL_7.0_. 3. Double-click SAP_Customised_MS_VSRTL_7.0_.exe 4. If the warning message UnInstaller setup failed to initialize. You may not be able to uninstall this product. is displayed, choose OK and continue. The entire Runtime Environment will be installed. 5. After the installation is complete, you must restart your machine even if the setup does not prompt you for the same. 5.3.3.2 Installation of the Microsoft .Net Framework You will find more info’s on how to install Microsoft .Net Framework in the software requirements section. The Microsoft .Net Framework 3.5 must be part of the currently installed programs.

Ensure that at least the Microsoft .Net Framework 3.5 is installed. If this step is not executed successfully, the Communication Station Setup will fail.

01 2017 56

5 Installation

5.3.3.3 Installation of the Communication Station 1. Log on as the local system administrator 2. Insert the CRM Mobile Installation DVD into the CD ROM drive. 3. Go to the :\Communication Station folder. 4. Double-click Setup.exe. 5.3.4 Post Installation After the installation, use the printed out checklist to verify that the components are successfully installed and activate the message transfer and net4abap services. 5.3.4.1 Security Configuration of the Message Transfer Package For the regular message transfer, the mobile clients connect to the Communication Station and send or receive data through the message transfer component. This component uses a connection named _MT for data exchange with the CRM Middleware Server. Refer to the Communication Station Security section for more details about the security configuration of your CRM Landscape. Based on your security requirements, you have to define the appropriate configuration for the Message Transfer Package. As described in detail below, you can deactivate the authorization checks for the package and allow users from other domains to use the Communication Station.

Authorization to connect from different domains

Note 1022089 contains generic recommendations that can be followed on any system that runs the CommStation. Some points in the recommendation that changes the security will also enable the CommStation to be accessible from other domains. This means that the security settings for the CommStation application are made available for Anonymous users too so that the users who are not a part of the domain in which the CommStation is stationed are also able to connect to the CRM Server. If the Communication Station and all the client hosts are NOT in the same Windows domain or if local Windows users are used on the clients, the following setting must be performed additionally on the Mobile Clients: 1. Log on to the Mobile Client machine. 2. Start the Windows service program Dcomcnfg.exe (from the directory \winnt\system32). 3. In Windows 7, to set the Default Authentication Level, on the Component Services screen, choose Component Services  Computers  My Computer  Right-click  Properties  Default Properties and select the entry (None) for the Default Authentication Level. 4. Choose Apply and Ok. 5. Restart the mobile client machine to activate the new setting. To allow mobile client users to use the CRM Message Transfer service, some settings must be performed on the communication station as explained below: 1. Log on to the Communication Station. 2. Select Start  Settings  Control Panel. 3. Select Administrative Tools  Component Services.

01 2017 57 5 Installation

4. Select Console Root  Component Services  Computers  My Computer  Com+ Applications. 5. Go to SAP CRM Mobile Transfer  Roles  User  Users. 6. Right-click and choose New  User. 7. Add all the Windows users or Windows users groups specified in the domain that must have access to the component. For all the other local users that cannot be added, the only option is to create local users with the same name and password on the Communication Station with the NT user manager and to include them in the User role of the SAP CRM Mobile Transfer component. At least for such a heterogeneous NT network, deactivating the DCOM / MTS security is recommended. 5.3.4.2 Setup for Data Synchronization To setup communication between the Communication Station and the CRM Server for data synchronization, you need to use the Queued Message Transfer Configuration Tool (QmtCnfg). 1. Choose Start  Programs  Middleware  Qmt Configuration. The Qmt Configuration Properties screen appears.

2. Choose Select  Unicode SAP Destinations.

01 2017 58

5 Installation

3. Choose New Destination. The Create New Destination dialog box appears. 4. Enter a name for the new destination. 5. Under Connection Type:  Specify the type of connection as R/3 Connection.  Select Load Balancing or Dedicated Server.

If you select the Load Balancing option, the communication station connects to the R/3 system by using a message server. However, if you select the Dedicated Server option, the communication station connects to the R/3 system by using the host name of the R/3 system.

We recommend you to use the Load Balancing option.

Communication station performance: Note 1255658 suggest increasing the Pool Size of the Communication station: This will enable Microsoft Windows COM+ Architecture to instantiate as many processes (dllhost.exe) to host the COM+ Communication station application. For example, if you

01 2017 59 5 Installation

specify the pool size say 10, Windows COM+ will create a new DLLHOST.EXE hosting the Communication station until the number of alive DLLHOST.EXE reaches 10. From then on, these processes will be multiplexed for the incoming requests. 6. Under Connection Parameters: If you select Load Balancing under Connection Type, then:  In the Message Server: enter the name of the message server.  In the R/3 System Name: enter the name of the R/3 system.  In the Group: enter the name of the group. If you select Dedicated Server under Connection Type, then:  In the R/3 Hostname: enter the name of the message server.  In the System Number: enter the system number.

You can get the server details in the SAP Logon screen. 7. Under Logon, specify the client and language.

If you do not specify any values, the default values are used. 8. Under Security, specify a user ID and password to connect to the server.

 Do not specify an MTS Role.  Under Operation Mode, do not select the Pooling of R/3 Context and Trace options. 9. Choose Save. 10. To set the destination you created as the default destination, under Operation Mode, select Default Destination and choose Save. 11. To check the accuracy of the logon information, choose Test Connection.

After you have defined the Unicode SAP Destination, to review the Unicode Communication Settings, choose Select  Unicode Communication Station. The default settings of the Unicode Communication Station are displayed. 5.3.4.3 Configuration of NET4ABAP The program NET4ABAP is installed and running on your Communication Station as the Windows Service SAP Net for ABAP. NET4ABAP is used by the Administration Console only and does not affect the Communication Station. You can choose between using the Gateway of the CRM Server or Communication Station. However, in such a case, both settings, on the Communication Station and CRM Server must be the same. You must use the same gateway on both systems. Communication Station 1. Call up NET4ABAPServiceController by clicking Start  Programs  Middleware  Net for ABAP Configuration. The Net4abapServiceController window appears.

01 2017 60

5 Installation

2. Under the SAP Gateway Registry section:  In ProgramID: enter net4abap.  In the Host: enter the machine name of the gateway of the CRM Server or Communication Station.  In the Service: enter the service of the gateway of your CRM Server. This is sapgw<##> where ## is the instance number of the gateway of the CRM Server or Communication Station.

Use transaction code SMGW in CRM server to monitor the Gateway. From the Menu, Select Goto  Parameters  Display to display the Gateway parameters at the CRM server. In the list of parameters displayed, “gateway service” is the parameter which will give the value of the Gateway service.  Choose Start. This will start the SAP Net4ABAP service.

This service starts automatically when you start the system. 3. If any of the above parameters need to be changed, perform step 1, choose Stop and then perform step 2. CRM Server 1. Start transaction (SM59) and define a new RFC destination AC-NET4ABAP of type T (TCP/IP Connection). 2. Choose Save. 3. In the Technical settings tab, select Registered Server Program and in the Program ID field, enter net4abap (note that this program ID is case-sensitive). 4. In the Gateway Options section, specify the following:  In the Gateway host field, enter the name of the gateway of the CRM Server or Communication Station.  In the Gateway service field, enter the service of the gateway of the CRM Server or Communication Station. 5. Choose Save.

01 2017 61 5 Installation

5.3.4.4 Monitoring of the Communication Station The monitoring of the communication is now integrated with the Computing Center Management System (CCMS). This allows the CRM server to continuously monitor the status of the communication station. The monitoring primarily involves checking whether the communication station is running or not. NET4ABAP checks the status of the communication station and provides the same to the CRM server. If the communication station is not running:  The communication station node in CCMS changes to indicate the status.  An alert is triggered and an email is sent to the email ID of the person responsible.

The email is sent only if you specify the email ID under the Parameters tab of the CCMS_OnAlert_Email_COMM method. To specify the email ID of the person responsible, perform the following steps: 1. Start transaction (rz20). 2. Expand SAP CRM Monitor Templates. 3. Double-click CRM Middleware. 4. Expand the communication station node. 5. Select the communication station node and choose Properties. 6. Choose the Methods tab. 7. Double-click the CCMS_OnAlert_Email_COMM method. 8. Choose the Parameters tab. 9. Choose Display <-> Change. 10. In the Sender field, enter the name or email ID of the sender. 11. In the Recipient field, enter the email ID of the sender. 12. Choose Save.

01 2017 62

5 Installation

5.4 Installing Mobile Client Application No matter which type of Mobile Client Application you want to install, the installation program continues in the same way. You can install several Mobile Client Applications simultaneously. 5.4.1 Prerequisites The Mobile Client configuration depends on the type of scenario you want to implement.

Make sure, that the software and hardware requirements have been met. Workgroup Solution The workgroup solution requires that the User database be installed on the Workgroup Server. If you are using this solution and you have not yet installed the Workgroup Server, continue with Installing the Workgroup Server. Standard Solution The standard solution requires that the User database be installed on each Mobile Client. If you are using this solution, you must select the options that are specific to it. If you select Standard Solution, you install an empty local User database and the local CRM Client is connected to a central CRM Server. This means that the user data replication is made via this connection. After the installation of the CRM Client connected to Middleware on CRM Server the empty User database has to be filled by an initial download from the CRM Server. If you also select Demo Installation, you install a prefilled User database for demonstration or testing purposes. This configuration is not intended for a production environment. See Testing Scenario, below. Testing Scenario You must select both Standard Solution and Demo Installation for a test environment. It is not intended for a production environment. If you do not select Demo Installation, an empty local User database and the local CRM Client is connected to a central CRM Server. This means that the user data replication is made via this connection. After the installation of the CRM Client connected to Middleware on CRM Server the empty User database has to be filled by an initial download from the CRM Server.

01 2017 63 5 Installation

5.4.2 Procedure 1. Select the solution ‘Mobile Client Setup’ and ‘Standard Client’ by selecting the appropriate radio buttons.

The following options are available

Select… Then...

01 2017 64

5 Installation

Mobile Client Laptop The Mobile Client Laptop is selected by default and cannot be deselected. It installs the laptop setup. Mobile Applications Contains the setup for the Mobile Sales and Service Applications:  Mobile Sales Application (MSA)  MSA: Standard Mobile Sales Application  Mobile Service Application  MSV: Standard Mobile Service Application (MSV)  Mobile Sales  MSP: Sales Application containing special Pharmaceuticals (MSP) features for the Pharmaceutical Industry  Mobile Sales Consumer  MSC: Sales Application containing special Goods (MSC) features for the Consumer Goods Industry

You can install several mobile client applications simultaneously. Choose any application.

Mobile Addons Provides additional features for the Mobile Applications:  Internet Pricing and Configurator (IPC)  IPC: Used to enable Pricing, Taxation and Configuration.

'In case you do not select IPC, the following customizing setting is necessary after installation in Mobile System Maintenance / Sales Transaction Settings / General Settings / IPC Settings -> uncheck 'Enable IPC'.' Citrix Integration Used to run specific setup required for installations on Citrix environment

User Database You can choose the following options:  Demo User Database  The demo version uses a prefilled demo User database; this database is not replicated with the  Unicode Database CRM Server. If you do not choose this option, an empty User database will get installed. Select this option for Mobile Clients for demonstration purposes.

Do not select this option if you install a Mobile Client for the production environment

 Installs the User Database in Unicode Collation

Mobile Client Framework The Mobile Client Framework is selected by default and cannot be deselected. Provides the mobile framework which is common across all installations. 2. Choose Next.

01 2017 65 5 Installation

 Select the appropriate language or languages that you want to install.

You must ensure that the language(s) match the Microsoft SQL Server / Microsoft Data Engine code page. For more information, see Content of the Installation DVD and Appendix C.

You have to set at least one language, else you won’t be allowed to continue.

Microsoft SQL Server installs one default instance and allows you to install several (named) instances. The SAP CRM Mobile Client Component databases must be installed to the default instance of Microsoft SQL Server.  Provide the Configuration settings:

Some options in the configuration section of the screen might appear disabled based on the Addons that got selected.

When you have chosen to install the Demo User Database, the setting for the Communication Station will get disabled.

Field Description

Communication Station  Enter the IP Address or the Server name of the Communication Station.

Mobile Repository Server  For a standard client, this field is not enabled.

Workgroup Server  For a standard client, this field is not enabled.

01 2017 66

5 Installation

The installation does not check the connection to the Communication Station. Make sure that you have typed the IP address or the name properly. It is possible to keep the Connection to the Communication Station empty and update it later 3. Choose Next.

The prerequisite check tells you, if all necessary software requirements are met. If this is not the case, the installer will not allow you to continue.

Choosing the Button System Information will give you an overview of the hardware and software of the given machine. 4. Choose Next.

01 2017 67 5 Installation

01 2017 68

5 Installation

 If you want to change the items you selected to install, choose Back.  If you want to save the configuration for this installation, choose Save Configuration, and then choose the file to install. Saving the configuration allows you to install the same configuration repeatedly, by storing the settings in an IUP file. 5. Choose Install to start the installation process for the Mobile Client Installation.

6. When the installation process finishes, the following screen appears.

01 2017 69 5 Installation

 The Button View Log provides a log-file on the installation process. In case installation did not finish successfully, the logfile should help further in finding the reason.

7. Choose Done. You have installed the SAP CRM Mobile Client Component: Applications for the Mobile Client.

01 2017 70

5 Installation

5.5 Installing Workgroup Server 5.5.1 Prerequisites

Make sure, that the software and hardware requirements have been met.

. The Workgroup Server installation installs the same language version as the operating system uses. You cannot change this setting in the installation. You must ensure that the same language versions are installed on the Workgroup Server and the Workgroup Clients connected to that server. . Microsoft SQL Server installs one default instance and allows you to install several (named) instances. The SAP CRM Mobile Client Component databases must be installed to the default instance of Microsoft SQL Server. The Workgroup Server configuration depends on which environment you want to install. Workgroup Server for Production If you select Workgroup Solution, you establish the connection with the CRM Server. This means that the user data replication is made via this connection. After the installation of the CRM Client connected to Middleware on CRM Server, the empty User database has to be filled by an initial download from the CRM Server. This is the standard setting for a productive environment. 5.5.2 Procedure Select the solution ‘Mobile Client Setup’ and ‘Workgroup Setup’ by selecting the appropriate radio buttons.

01 2017 71 5 Installation

The following options are available

Select… Then...

Workgroup Server The Workgroup Server is selected by default and cannot be deselected. It installs the workgroup server setup. Internet Pricing and Configurator IPC: Used to enable Pricing, Taxation and (IPC) Configuration.

'In case you do not select IPC, the following customizing setting is necessary after installation in Mobile System Maintenance / Sales Transaction Settings / General Settings / IPC Settings -> uncheck 'Enable IPC'.' User Database You can choose the following options:

Do not select this option if you install a Workgroup Server for the production environment.

 Installs the User Database in Unicode Collation

Mobile Client Framework The Mobile Client Framework is selected by default and cannot be deselected. Provides the mobile framework which is common across all installations. Choose Next.

01 2017 72

5 Installation

 Select the appropriate language or languages that you want to install.

You have to set at least one language, else you won’t be allowed to continue.

You must ensure that the same language versions are installed on the Workgroup Server and the Workgroup Clients connected to that server.

You must ensure that the language(s) match the Microsoft SQL Server / Microsoft Data Engine code page. For more information, see Content of the Installation DVD and Appendix C.

Some options in the configuration section of the screen might appear disabled based on the Addons that got selected.

When you have chosen to install the Demo User Database, the setting for the Communication Station will get disabled. Field Description

Communication Station  Enter the IP Address or the Server name of the Communication Station.

Mobile Repository Server  For a workgroup server, this field is not enabled.

01 2017 73 5 Installation

Workgroup Server  For a workgroup server, this field is not enabled.

The prerequisite check tells you, if all necessary software requirements are met. If this is not the case, the installer will not allow you to continue.

Choosing the Button System Information will give you an overview of the hardware and software of the given machine.

01 2017 74

5 Installation

Choose Next.

01 2017 75 5 Installation

 If you want to change the items you selected to install, choose Back.  If you want to save the configuration for this installation, choose Save Configuration, and then choose the file to install. Saving the configuration allows you to install the same configuration repeatedly, by storing the settings in an IUP file. Choose Install to start the installation process for the Mobile Workgroup Server.

01 2017 76

5 Installation

When the installation process finishes, the following screen appears.

 The Button View Log provides a log-file on the installation process. In case installation did not finish successfully, the logfile should help further in finding the reason.  Choose Done. You have installed the SAP CRM Mobile Client Component: Applications for the Workgroup Server.

01 2017 77 5 Installation

5.6 Installing Workgroup Client No matter which type of Mobile Client Application you want to install, the installation program continues in the same way. You can install several Mobile Client Applications simultaneously.

Prerequisites

Make sure, that the software and hardware requirements have been met. Make sure that the operating system language of the Workgroup Server is the same as is used on the Workgroup Client.

You must ensure that the same language versions are installed on the Workgroup Server and the Workgroup Clients connected to that server. The Workgroup Server configuration depends on which environment you want to install.

Workgroup Client for Production If you select Workgroup Solution, you establish the connection with the CRM Server. This means that the user data replication is made via this connection. After the installation of the CRM Client connected to Middleware on CRM Server, the empty User database has to be filled by an initial download from the CRM Server. This is the standard setting for a productive environment. 5.6.1 Procedure 1. Select the solution ‘Mobile Client Setup’ and ‘Standard Client’ by selecting the appropriate radio buttons.

The following options are available

01 2017 78

5 Installation

Select… Then...

Workgroup Client Laptop The Workgroup Client Laptop is selected by default and cannot be deselected. It installs the workgroup client setup. Mobile Applications Contains the setup for the Mobile Sales and Service Applications:  Mobile Sales Application (MSA)  MSA: Standard Mobile Sales Application  Mobile Service Application  MSV: Standard Mobile Service Application (MSV)  Mobile Sales  MSP: Sales Application containing special Pharmaceuticals (MSP) features for the Pharmaceutical Industry  Mobile Sales Consumer  MSC: Sales Application containing special Goods (MSC) features for the Consumer Goods Industry

You can install several mobile client applications simultaneously. Choose all applications you would like to install. Mobile Addons Provides additional features for the Mobile Applications:  Internet Pricing and Configurator (IPC)  IPC: Used to enable Pricing, Taxation and Configuration.

Mobile Client Framework The Mobile Client Framework is selected by default and cannot be deselected. Provides the mobile framework which is common across all installations. Choose Next.

01 2017 79 5 Installation

 Select the appropriate language or languages that you want to install.

You must ensure that the same language versions are installed on the Workgroup Server and the Workgroup Clients connected to that server.

You must ensure that the language(s) match the Microsoft SQL Server / Microsoft Data Engine code page. For more information, see Content of the Installation DVD and Appendix C.

You have to set at least one language, else you won’t be allowed to continue.

Some options in the configuration section of the screen might appear disabled based on the Addons that got selected. Field Description

Communication Station  For a workgroup client, this field is not enabled.

Mobile Repository Server  For a workgroup client, this field is not enabled.

Workgroup Server  In the Server field, type the server name or IP Address of the workgroup server.

 In the Site-ID-field, type the SiteID assigned by the CRM Server to the Workgroup Server

01 2017 80

5 Installation

The installation uses the connection to the Workgroup Server to determine the collation. Make sure that you have typed the IP address or the name properly. It is not possible to continue without a working connection to a Workgroup Server. Choose Next.

The prerequisite check tells you, if all necessary software requirements are met. If this is not the case, the installer will not allow you to continue.

Choosing the Button System Information will give you an overview of the hardware and software of the given machine.

01 2017 81 5 Installation

Choose Next.

01 2017 82

5 Installation

 If you want to change the items you selected to install, choose Back.  If you want to save the configuration for this installation, choose Save Configuration, and then choose the file to install. Saving the configuration allows you to install the same configuration repeatedly, by storing the settings in an IUP file. Choose Install to start the installation process for the Mobile Workgroup Server.

01 2017 83 5 Installation

When the installation process finishes, the following screen appears.

 The Button View Log provides a log-file on the installation process. In case installation did not finish successfully, the logfile should help further in finding the reason.

Choose Done. You have installed the SAP CRM Mobile Client Component: Applications for the Workgroup Client.

01 2017 84

5 Installation

5.7 Restarting the Installation (Maintenance Mode) If you need to modify, repair or remove Mobile Client components or software, use the installation program to do so.

Use this function only to add or remove, repair or uninstall the SAP CRM Mobile Client Component Applications. This includes Internet Pricing and Configurator. 1. Go to Start, Control Panel, ‘Add or Remove Programs’ respectively ‘Programs and Features’ and choose SAP CRM Mobile Client 7.01 SP06.

In case of pending reboots you will receive a warning message on this screen. To avoid issues, we recommend you to do a reboot before continuing with the Mobile Installation.

Choosing the Question Mark on the top right hand side will open the installation Guide In case you have a running MSA-installation on your machine, the following error will be shown.

01 2017 85 5 Installation

You will not be able to go into maintenance mode as long as you have running Mobile Applications. You have to close all running Mobile Applications before restarting the setup. 2. Choose Next.

01 2017 86

5 Installation

3. Determine what you need to do.

If you want to... Then...

Modify an existing installation by Select Modify and choose Next. adding another application or removing Continue with Modifying Installed Applications. an application installed by mistake Repair programs which you have Select Repair and choose Next. already installed Continue with Repairing Installed Applications. Remove all applications you have Select Remove and choose Next. installed Continue with Removing All Installed Applications. 5.7.1 Modifying Installed Applications 1. Select Modify and click on Next. The appropriate machine type configuration for the current machine and the installed components will get selected automatically.

2. If you want to uninstall one of these components, clear that field.

01 2017 87 5 Installation

Make sure that you leave all components selected that you have installed on your machine already. If you clear selected fields for the software components you have installed already, these software components will be uninstalled. 3. Choose Next and follow the instructions for the software you want to add. The maintenance will provide similar screens as displayed in the installation mode. Please refer the appropriate sections for more information.

. Installing the Mobile Repository Server,

. Installing the Mobile Development Workstation,

. Installing the Mobile Client Application,

. Installing the Workgroup Server

. Installing the Workgroup Client 5.7.2 Repairing Installed Applications Selecting this option allows the installation tool to check the current configuration to determine whether or not there are files missing. It also checks whether or not there are Windows Registry keys missing. If the repair function finds any files or registry keys missing, it repairs them. You need not do anything further.

01 2017 88

5 Installation

If you choose to Repair the installation, the following screen appears.

The installation path that was chosen during the installation will get defaulted.  If you want to review the items that are installed, choose Selection Summary. This screen provides you the possibility to save the summary as textfile.

01 2017 89 5 Installation

 If you want to save the configuration for this installation, choose Save Configuration, and then choose the file to install. Saving the configuration allows you to install the same configuration repeatedly, by storing the settings in an IUP file. Click on the Repair button to start the repair of SAP CRM Mobile Client on the machine. 5.7.3 Removing All Installed Applications Selecting this option uninstalls all components of the CRM Mobile software that are installed on a machine.

If you have added any files to the default path, %mobilerootdir% directory, make sure to save them to another directory before starting the uninstallation process. The uninstallation routine deletes this directory and all subdirectories and files associated with it.

01 2017 90

5 Installation

Procedure

1. The Remove Database(s) after backup option backs up the database before uninstallation. 2. The Remove Database(s) without backup option deletes database during uninstallation. 3. The Do not Remove Database(s) option leaves the database intact and does not remove them.

1. When clicking on Remove, the following warning popup will appear. If you really want to remove the application, click on OK

2. Make sure that CRM Mobile Sales/Mobile Service client and any associated components are not active. You cannot remove files that are in use. Make sure that no one is connected to the server.

3. The installation path that was chosen during the installation will get defaulted.

01 2017 91 5 Installation

4. If you want to review the items that are installed, choose Selection Summary. This screen provides you the possibility to save the summary as textfile.

5. If you want to save the configuration for this installation, choose Save Configuration, and then choose the file to install. Saving the configuration allows you to install the same configuration repeatedly, by storing the settings in an IUP file.

6. Choose Remove to remove the CRM Mobile software.

01 2017 92

5 Installation

Result

You have successfully uninstalled the SAP CRM Mobile Client Component: Applications. You are ready to begin a fresh installation.

01 2017 93 6 Post-Installation

6 Post-Installation 6.1 Client Console Settings In the development workstation during customization, Client Console is used to set up the runtime environment of the mobile client. It is also used to administer and monitor the mobile client.

Furthermore it is used to set up the data transfer from the CRM server to the mobile client. It also monitors this transfer of data.

The features of Client Console can be classified into the following categories:

 Configuring the mobile client:

Set up communication between the mobile client and the CRM server. You can also check if the mobile client is connected at any given time to the CRM server.

 Updating the runtime environment of the mobile client:

Update the mobile client with data from the CRM server (Metadata and Tablescripts).

 Managing and monitoring data transfer

Check the status of the inbound and outbound queues of the mobile client. It also processes the BDoc messages in the inbound queue of the mobile client. (Queue Manager)

 Troubleshooting and customizing

For detailed information on the Client Console and it’s configuration, please use the Client Console Help-File:

You can find it in %mobilerootdir%\bin\ClientConsole.chm or you can open it via the Client Console directly: Go to Start → All Programs → SAP CRM Mobile → Administrative Tools → Client Console. There go to Help and Client Console Help 6.2 Patching IPC If you are using the IPC, make sure, that you are using the latest Patches for the IPC in CRM Mobile, which are available on the Service Market Place:

Latest IPC Patches are available under: http://service.sap.com/patches → Support Packages and Patches → SAP Application Components → SAP CRM → SAP CRM 7.01 → Entry by Component → CRM Mobile Client Patch Name: IPCMSAP_-10007505.CAR

Search for the latest patch for your release and follow Note 891963 Patching Internet Pricing Configurator for Mobile Client, which tells on how to deploy it. Only the most current patch will be available on the Service Market Place, as it contains all previous fixes as well.

01 2017 94

6 Post-Installation

6.3 Security Settings for Ides 1. Make sure the latest Commstation is installed and NET4ABAP is configured, before Mobile Users are created and/or their passwords are changed in CRM server /nSMOEAC transaction. This is MANDATORY to successfully login to the Mobile Client Application.

2. After complete installation/ upgrade, it is highly recommended to change the password of the Mobile Client database login ‘ides’. This password should be changed ONLY using the IdesConfigUtility.exe.

1. Manual Mode: o Invoke the tool IdesConfigUtility.exe in the %MobileRootDir%\Bin.Net. o Login (Standard Password is prefilled in the tool). o Change the password. 2. Commandline Mode: o This can be embedded in a Mobile upgrade Package (MUP) and deployed to Mobile Clients. o IDESConfigUtility.exe /DSN “ides“ /USER “ides“ /NPSWD ““ /S 3. Future, if the password needs to be changed again, following options can be used.

1. Manual Mode: o Invoke the tool IdesConfigUtility.exe in the %MobileRootDir%\Bin.Net. o Standard Password is prefilled in the tool. Remove it. Enter the current password. o Login. o On successful authentication, you can change the password in the next screen. 2. Commandline Mode: o This can be embedded in a Mobile upgrade Package (MUP) and deployed to Mobile Clients. o IDESConfigUtility.exe /DSN “ides“ /USER “ides“/OPSWD ““ /NPSWD ““

should meet the following mandatory requirements: Password should be minimum 12 characters in length and in combination of uppercase (A-Z), lowercase (a-z) letters, numbers (0-9) and symbols (! @ # ?)

4. After a Workgroup Scenario installation/ upgrade, IdesConfigUtility.exe should be run similarly to change the password on the Workgroup Server. It should also be run on all the Workgroup Clients connected to the same Workgroup Server with the same password (as in Workgroup Server).

01 2017 95 7 Additional Information

7 Additional Information 7.1 Appendix A: Central Service Reference Guide The Central Server is installed on the Mobile Repository Server. For more information, see Software Requirements for the Mobile Repository Server. 7.1.1 Command Line Options The Central Service provides the following command line options.

Command line options Function

/DNT[install or uninstall] Specifies the NT command  install  Installs a new NT Service  uninstall  Uninstalls an existing NT Service /PRT[Number] Specifies the port number /SNM[Service Name] Specifies the service name /SHD[Port Number] Shuts down the Central Service running on the specified port number /NAM[Information String] Displays the information string on the Central Service form 7.1.2 Guidelines for Using Command Line Options When you use a command line option, do not type a space between the command line option and its value. For example, specify port number 1002 as /PRT1002. To install a new NT Service, use the /DNTinstall option followed by a space and the /PRT option. If you want to add a service name, use the /SNM option followed by the name you want. If you want to include spaces in the service name, you must enclose the phrase in quotation marks. For example, use this command to install the Central Service as an NT Service with SCM named “Central Service For TextRep“. ARSCentralServerInstaller.exe /DNTinstall /SNM"Central Service For TextRep" /PRT1002

If you do not specify the port number, the installation fails. To uninstall an existing NT Service, use the /DNTuninstall option. If you want to add a service name, use the /NAM option. If you want to add a port number, use the /PRT option.

Use this command to uninstall the Central Service as an NT Service with name “CentralServiceForTextRep“. ARSCentralServerInstaller.exe /DNTuninstall /NAM"Central Service For TextRep" Use this command to uninstall the same Central Service as an NT Service ARSCentralServerInstaller.exe /DNTuninstall /PRT1002

01 2017 96

7 Additional Information

If you specify both a service name and a port number, the port number, /PRT, option has priority over the service name, /NAM, option. You can change the NT Service name from its default name, SAP Mobile Application Repository Central Service, to whatever name meets your business requirements using the /SNM option. If you want to include spaces in the service name, you must enclose the phrase in quotation marks. To start the Central Service from the command line, use the /PRT option to specify the port number. For example, use this command to start the Central Service on port number 1002. ARSCentralServerInstaller.exe /PRT1002

You can use the /SNM [Service Name] option only with the /DNT [install or uninstall] option. 7.1.3 Updating Central Service Port Number in the Application Repository Procedure 1. Start Microsoft SQL Server's Query Analyzer application.

Make sure that you have System Administrator rights. 2. In the DB combo field, select the name of the application repository, for which Central Service is installed as a service.

The default name of the repository, ars_db, already exists from the SAP CRM 5.0 Mobile Installation. 3. Use the following SQL script in the Query Analyzer.

/* Script: Begin */ Update ars_systable set value = '' where param = 'ServerMachineName' Update ars_systable set value = '' where param = 'RemoteSocketPort' /* Script: End */ 4. Replace all values in the SQL script for the required parameters.  Replace with the name of the Mobile Repository Server, on which the Central Service is installed.  Replace with the port number of the Mobile Repository Server, on which the Central Service is installed.

You must specify all values in the SQL script with single quotes. 5. Execute the SQL script.

01 2017 97 7 Additional Information

Result The ars_systable entries and for the selected application repository have been updated with the values specified.

01 2017 98

7 Additional Information

7.2 Appendix B: Installing Databases Using SwitchDB You can use the SwitchDB tool to install SAP Provided databases (user database IDES and Mobile Application Repository ARS Database) on many machines without having to go through the installation routine every time. SwitchDB and its associated reference components can be found in the %mobilerootdir%\Bin.NET folder, and also on the installation DVD. You can use SwitchDB either from the UI mode or the command line mode to install databases. SwitchDB uses the attachment method to install a database on a machine. It requires a compressed .mdf file that was created with the SAPCAR compression utility. The SwitchDB provided with this Service Pack onwards has better logging, both for UI and console mode. In either case, the log files are created in the directory %PROGRAMFILES%\sap\mobile_installation_logfiles in the format: switchdb- date-time-MachineName.log. Apart from that, the UI has a detailed event log in the main window which logs every activity the user performs. This is useful when debugging any issues. When faced with any issues from the UI mode, the user can select the entire text content from the text logger window and paste the same in the support message.

The SwitchDB available from 5.0 SP09 onwards, has been re-designed with .NET Framework 2.0. Hence, it cannot be run over the network directly. If you wish to install the database without installing SAP CRM Mobile Client Application, you need to copy the Folder SwitchDB from the DVD onto the local machine where you wish to install the database and then run the tool.

The compressed file (*.car file) and the database (*.mdf file) it contains must have the same name. Do not rename the database car files provided by SAP. Although you can rename the database using the Databasename parameter, the individual files, *.car and *.mdf, must remain as they are delivered. 7.2.1 General User Interface Information Options available under Menu → Help you find the following options:

01 2017 99 7 Additional Information

Show Command Line Menu This menu displays the command line parameters to be used in the command line mode.

Hide Command Line Menu This menu hides the command line parameters information from the main window. Options available on the screen directly

Database server This is the local machine name and it cannot be edited or changed.

Authentication Type Following are the two types of authentication:

01 2017 100

7 Additional Information

a) Windows Authentication: Uses the windows logon to connect to the SQL Server for further operation. b) SQL Server Authentication: Uses the SQL Server Administrator (equivalent) information to connect to the SQL Server for further operation. (Text fields User Name and Passwords editable only when SQL Server authentication type is selected).

Check connection to SQL Server This option checks if the connection to the SQL Server (Database Server name) is successful or not.

Set DB Compatibility level (For IDES) Selecting this check box sets the DB compatibility level for IDES. The following are the values for the DB Compatibility level on different versions of SQL Servers

SQL Server Version DB Compatibility Level

MSSQL Server 2005 SP02 and above 80

MSSQL Server 2008 80

01 2017 101 7 Additional Information

Install a database Clicking this button initiates the database installation process. (This button would be enabled only if all the fields are filled).

01 2017 102

7 Additional Information

Close Application Clicking this button closes the application/logger.

01 2017 103 7 Additional Information

Reload Database Clicking this button reloads the databases in the combo box.

01 2017 104

7 Additional Information

Drop Database Clicking this button drops the database selected in the combo box (this should be done only after reloading the database through the Reload Databases button). This button would be enabled only after selecting the proper database for uninstallation.

01 2017 105 7 Additional Information

Archive Database Clicking this button archives the database selected in the combo box and then uninstalls the same. (This should be done only after reloading the database through the Reload Databases button)

01 2017 106

7 Additional Information

Archive Database without Uninstalling Clicking this check box would archive the database in the SQL Server Backup folder without uninstalling it. The user could navigate to the backup folder clicking on the Go to Backup Folder link.

7.2.2 SwitchDB Application – UI Mode You can launch SwitchDB from the Bin.NET directory (or from the local folder to which you have copied the SwitchDB directory from the installation DVD), by double-clicking the file SwitchDB.exe.

The following components must be available in the same location as SwitchDB.exe or else the tool will fail to launch.

01 2017 107 7 Additional Information

 FunctionsLibrary.dll  CommandLine.dll  Sapcar.exe 7.2.3 Checking connection to the SQL Server To check the connection to the SQL Server: 1. Select the Check Connection to SQL Server check box. 2. If the connection to the SQL Server fails (This could happen if the SQL Server is not installed properly or the server is shutdown), the tool displays the error information in the status bar panel in the bottom of the screen. In such a case the user needs to check if: The SQL Server is installed and/or configured properly. The service is currently running. 7.2.4 Installing a Database To install a database:

01 2017 108

7 Additional Information

1. Browse for the path of the Compressed Archive (CAR) file using the browse button.

The tool will display a default name for the database. You can change this name to a name of your choice.

Before specifying a name for the db, make sure that a database with the same name does not exist in the local machine. 2. Hit the Start with the installation process button to begin with the installation process.

While the installation is in progress, all the controls on the screen would be disabled. This is to avoid the user from performing any actions when the connection to the master database is open. Once the installation is over, the controls would be enabled and the status bar in the bottom of the screen would display the status message.

01 2017 109 7 Additional Information

When the database is getting installed, a command prompt window would launch in minimized mode in the task bar. Do not close this window or else the database installation would fail.

The application can only be closed from the Close button. This button is available under all the three tabs Install, Uninstall and Archive). This is to close the logger properly or else the application log file would remain open and no information would be available for reference. 3. Run the following scripts after you have installed your Database. For IDES: On your installation DVD, open the following folder and run the script ides_empty_logins.sql: \Mobile_Client_Installation\databases\\ides_empty For ARS_DB: On your installation DVD, open the following folder and run all available scripts: \Mobile_Client_Installation\databases\\ars_db 7.2.5 Uninstalling a Database 1. Navigate to the tab control Uninstall a database. This contains a list box and three command buttons. 2. Click the Reload button on the right side of the list box. This populates the list box with the databases that are currently available on the machine (The list only displays databases that are properly attached to the enterprise manager and not files that are detached / orphaned from the SQL Server). 3. Select the button Drop the database. You will be prompted with the option of proceeding with the operation. Hit the Yes button to continue or the No button to cancel the operation and go back to the Uninstall tab page.

01 2017 110

7 Additional Information

7.2.6 Archiving and uninstalling a Database 1. Navigate to the tab page Archive and remove a database. 2. Similar to the Uninstall tab page, this page too has the Reload Database button. Before starting with the archive operation, click on the Reload Database button. This will refresh the combo box with the list of available databases on the machine. 3. Once you have selected the database that needs to be archived (and then uninstalled), click the Start with archiving and removing database button. 4. You will be prompted with the option to proceed with the operation or not. Click Yes to archive and then uninstall the database. Click No to return back to the Archive page.

01 2017 111 7 Additional Information

When a particular database is selected from the drop down combo box, the To be archived as text field is filled up with a default value for the database CAR file of type: dbname-Date-Time.CAR format. The CAR file would be copied to the Backup folder of the SQL Server installation directory.

The SwitchDB provided with SAP CRM Mobile Client 5.0 SP07 does not have an option to archive the database alone without uninstalling it. If a user chooses to archive a database, it will also uninstall the database along with creating a CAR file of the database.

Do not close the application from the task manager when a database is being archived, as this would leave the archiving process in an inconsistent state. Wait for the operation to finish before closing the tool. 7.2.7 SwitchDB Application-CommandLine Mode As in the previous tool, the command line mode is supported with this new release too. The command line arguments used are similar to the previous one. The one additional feature is the verbose logging which makes error tracking less tedious.

To check the list of command line options available for use, launch SwitchDB from the command line with the /? Or /help switches. This would display a message box with the list of parameters available for use.

Make sure the command line arguments cases are as mentioned in the help, as the tool is case sensitive and would not perform the requested operation if the parameters are not of the same case. Command Line options: Switches Description Required/Optional /mode Launches the tool in command Required SILENT line (Silent) mode. /login [user] Login information for SQL Optional Server. /pwd [password] Password for connecting to SQL Optional Server. /databasename Name to use when installing a Required [dbname] database. /Servername The server to attach DB to. (The Required [servername] tool only attaches db to the machine on which it is run (local installation). So either pass the local machine name or the value {local} (recommended with this switch) /SAPCarFileName The name of the car file to use Only required for installing [filename] for installing. operation. Do not use for uninstalling or archiving. /operation install Required

01 2017 112

7 Additional Information

uninstall Installs the database Required remove Uninstalls the database Required Archives and remove the database archive Required Archive but do not uninstall the database /dbcmptlevel Sets the DB Compatibility level. Required. (In case of ARS installation, set this value to False. For IDES set this value to True). 7.2.8 SwitchDB File Structure SwitchDB provides these files, which are located in the %mobileroot%\bin.NET folder.

File Name Definition

sapcar.exe The application used to compress or decompress database files SwitchDB.exe The program file Functionslibrary.dll Contains function definition for SwitchDB Commandline.dll Contains command line parser The databases decompress in a temporary folder during installation. Make sure that you have enough disk space. 7.2.9 Example Scenarios All examples included in this section use ides_empty.car as the database file name. 7.2.9.1 Installing a Database with Windows Authentication You can enter this command line to install a database named on a database server. switchdb.exe /operation install /mode SILENT /Servername /databasename ides /SAPCARFileName c:\ides_empty.car /dbcmptlevel True

7.2.9.2 Installing a Database without Windows Authentication You can enter this command line to install a database named on a database server with a login name and password . switchdb.exe /operation install /mode SILENT /Servername /databasename ides /SAPCARFileName c:\Temp\ides_empty.car /Login /Pwd /dbcmptlevel True

You can enter this command line to install a database named on a database server with a login name and no password. switchdb.exe /operation install /mode SILENT /Servername /databasename ides /SAPCARFileName c:\Temp\ides_empty.car /Login /dbcmptlevel True

When you install the CRM databases, follow these steps as well. 1. Create a directory (folder) on the local drive, for example, c:\temp\ides.

01 2017 113 7 Additional Information

2. Copy all .sql files from the DVD's Database directory (folder) to the directory you just created.

The installation DVD, SAPDVD: Mobile Client Installation, contains the files in the Database directory. 3. Run isql.bat file from the local directory (created in step 1). 7.2.9.3 Uninstalling a Database with Windows Authentication You can enter this command line to uninstall a database named on a database server. This command archives the database and subsequently uninstalls it. switchdb.exe /operation uninstall /mode SILENT /Servername /databasename ides

7.2.9.4 Uninstalling a Database without Windows Authentication You can enter this command line to uninstall a database named on a database server with a login name and password . This command archives the database and subsequently uninstalls it. switchdb.exe /operation uninstall /mode SILENT /Servername /databasename ides /Login /Pwd switchdb.exe /operation uninstall /mode SILENT /Servername /databasename ides /Login

Ensure that all files reside in the same directory. If you want to use SwitchDB more than once, you can set a path variable. If not, you can copy the files from the DVD to a directory (folder) on your machine and run SwitchDB from that directory. 7.2.9.5 Removing a Database with Windows Authentication You can enter this command line to uninstall a database named on a database server.

This command archives the database before removing it. switchdb.exe /operation remove /mode SILENT /Servername /databasename ides

7.2.9.6 Removing a Database without Windows Authentication You can enter this command line to uninstall a database named on a database server with a login name and password .

This command archives the database before removing it. switchdb.exe /operation remove /mode SILENT /Servername /databasename ides /Login /Pwd switchdb.exe /operation remove /mode SILENT /Servername /databasename ides /Login

01 2017 114

7 Additional Information

7.2.10 Log Files Every database operation creates a log file. The log file name format is Switchdb- -.log. You can find the log file in the ...\Program Files\SAP\Mobile_Installation_logfiles directory.

01 2017 115 7 Additional Information

7.3 Appendix C: Code Page Settings for Language Versions Database servers must be set up with the proper collation setting. Collation determines the character code page and the sorting order for data. Depending on which version of Microsoft SQL Server you use, you must choose the appropriate code page settings. Establish the code page settings while you install Microsoft SQL Server.

Code Page Settings for Microsoft SQL Server The SAP CRM Mobile Client: Applications support only the default instance of Microsoft SQL Server.

Microsoft SQL Server installs one default instance and allows you to install several (named) instances. The SAP CRM Mobile Client databases must be installed to the default instance of Microsoft SQL Server. For more information about SQL Server instances, see Microsoft's documentation. If you are installing Microsoft SQL Server, use the Custom installation type to set the collation. Choose one of the settings from the following table.

01 2017 116

7 Additional Information

Name Abbr. Sort Collation Name Code Page ID ID

Latin Latin1 52 SQL_Latin1_General_Cp1_CI_ Dictionary order, case- AS insensitive, for use with the 1252 character set Latin2 Latin2 82 SQL_Latin1_General_Cp1250_ Dictionary order, case- CI_AS insensitive, for use with the 1250 (Central European) character set Chinese ZH 199 Chinese_PRC_CI_AS Dictionary order, case- simple insensitive, for use with the 936 (Simplified Chinese) character set Chinese ZF 197 Chinese_Taiwan_Stroke_CI_A Dictionary order, case- traditional S insensitive, for use with the 950 (Traditional Chinese) character set Korean KO 195 Korean_Wansung_CI_AS Dictionary order, case- insensitive, for use with the 949 (Korean) character set Greek EL 114 SQL_Latin1_General_Cp1253_ Dictionary order, case- CI_AS insensitive, for use with the 1253 (Greek) character set Hebrew HE 138 SQL_Latin1_General_Cp1255_ Dictionary order, case- CI_AS insensitive, for use with the 1255 (Hebrew) character set Japanese JA 193 Japanese_CI_AS Dictionary order, case- insensitive, for use with the 932 (Japanese) character set Russian RU 106 SQL_Latin1_General_Cp1251_ Dictionary order, case- (Cyrillic) CI_AS insensitive, for use with the 1250 (Cyrillic) character set

01 2017 117 7 Additional Information

Name Abbr. Sort Collation Name Code Page ID ID

Turkish TR 130 SQL_Latin1_General_Cp1254_ Dictionary order, case- CI_AS insensitive, for use with the 1254 (Turkish) character set Arabic AR 146 SQL_Latin1_General_Cp1256_ Dictionary order, case- CI_AS insensitive, for use with the 1256 (Arabic) character set

01 2017 118

7 Additional Information

7.4 Appendix D: Mobile Repository Server Configuration 7.4.1 Configure the Mobile Repository Server Purpose This process describes how to configure a mobile repository server in the development environment. It requires:  Managing the multi-user development by providing the required services  Setting up communication with the CRM server and the Mobile Application Workstation to facilitate transport of the repository objects

For specific information regarding single and multiple environment transports, see SAP Note 429039. Process 1. Install the CRM transport component as a Microsoft Windows service and link the application repository to the CRM server using the Transport Installer. 2. Create a user account for access to the CRM server. 3. Assign the MAR ID and the Queue Locking parameters to the respective CRM server tables. 4. Add a namespace to the application repository.

You can add a customer namespace (Y or Z) or a top-level namespace. For more information, see Working with the Namespaces in the online help.

For the application repositories in the test and production environments, you must add subnamespaces only. For example, if Z were the namespace added to the development application repository, Z_Test would be the subnamespace to be added to the test application repository. 5. Create user accounts for development workstations to access the application repository. Result You have completed configuring the mobile repository server in the development environment. You can continue with configuring the mobile repository servers in the test and production environments using this process. 7.4.2 Installing the CRM Transport Component Use You perform this procedure to:  Install the transport component, Transport Agent as a service on the Mobile Repository Server (MRS).  Provide and test the logon and destination details. These details enable the MRS to establish a connection with a specific CRM Server.

01 2017 119 7 Additional Information

If you have established a three-system landscape, you must perform this procedure in all the three environments, development, test and production. The Transport Agent, which you install as a service, transports the metadata of a customized mobile client application from:  The development environment to the test environment, enabling you to test the changes made to the metadata during the customization of the mobile client application  The test environment to the production environment, enabling you to make the customized mobile client application available for creating client upgrades. Later, these upgrades are sent to all Mobile Clients, which enable the mobile client users to access and use the customized application. Prerequisites You have:  Established a system landscape that supports transports  Installed Mobile Application Repository (MAR) on each Mobile Repository Server (MRS) existing in the system landscape Procedure Choose Start  Programs  SAP CRM Mobile  Administrative Tools  SAP MAR Transport Configurator. The SAP MAR Transport Configurator appears.

01 2017 120

7 Additional Information

1. On the Repository tab, in the DSN, User, and Password fields, enter the details of the MAR. 2. Choose Login. The Properties group box displays the technical details of the MAR.

3. Choose the Service tab.

01 2017 121 7 Additional Information

4. In the Transport Agent Parameters group box, Service Name field, enter a name for the Transport Agent to be installed as a service.

The name that you enter for the TA service appears in Control Panel  Services. You must ensure that the name is unique and descriptive. (No other service can have the same name.) 5. Choose Install. The SAP MAR Transport Configurator installs the Transport Agent as a service. The text, appearing beside the Service Name field, changes to “Installed”.

When you start the SAP MAR Transport Configurator subsequently, the Service Name field displays the TA service that is installed already. The Install pushbutton appears as an Uninstall pushbutton. You can choose this Uninstall pushbutton to uninstall the existing TA service.

01 2017 122

7 Additional Information

The Repository log on as group box displays the logon details, which the TA service uses to connect to the MAR. The user and password that you specified on the Repository tab appear in this group box. However, if you do not want the TA service to use the user ID that appears here, you can specify a different service user ID and the corresponding password in the respective fields on this tab. a. Choose Test to check if the service user and password you have specified are valid and have administrative rights to access MAR. b. Choose Apply to save the service user and password.

If required, you can change the password of the user, which TA service applies. To do so, specify the new password, confirm it and choose Apply. 6. Choose the CRM Server Connection tab.

01 2017 123 7 Additional Information

7. Select the specific CRM Server from the Destination list box.

If the required CRM Server is not available in the list box, you can add it to the list. To do so, add a new CRM Server in the SAP Logon. a. In the Destination list box, select the entry of the relevant system. b. Enter a name for the destination, for example, TA_ and choose OK and then continue entering data on the CRM Server Connection tab.

It is recommended to establish a naming convention to start with “TA_” for all destinations used for transport. 8. In the Destination group box, choose the connection type you want to use.  The Load Balancing Server allows the message server to choose a free application server using a group logon.  The Dedicated Server allows a direct logon to the application server. 9. Use the following table to determine the appropriate information you need to add to the fields, based on the connection type you selected.

01 2017 124

7 Additional Information

If you selected the... Then this field... Requires the... Load Balancing Server Message Server IP address or DNS host name of the message server that has to be used for logon System Name Name of the CRM server Group Logon group of the SAP system, for example, PUBLIC Dedicated Server Application Server IP address or DNS host name of the application server that has to be used for logon System Number System number of the CRM Server

10. In the Login group box, specify the user, password, and client number that will be used to connect to the CRM Server.

11. Choose Test Connection to test whether or not a connection to the CRM Server is established successfully.

If the connection is not established, then verify and correct the information you provided in the CRM Server Connection tab. Then repeat step 12. 12. When the connection is established successfully, choose Save.

13. Choose OK. 7.4.3 Creating a CRM Server User Account Use Use this procedure to create a user account for the Transport Agent of the Mobile Application Repository. This user account must be unique. Make sure that it is not used in any other context. Prerequisites The system landscape is established and the software is installed. Procedure 1. Logon to the CRM Server. 2. Choose Tools  Administration  User Maintenance  User. The User Maintenance screen appears. 3. Enter the appropriate information into the fields.

• Choose the user account type as Communications. • Provide necessary rights for this user account to create, modify, and release transport orders.

01 2017 125 7 Additional Information

• For more information about creating user accounts, see the SAP online help. 4. Choose Save.

Result The user account you have created allows you to distinguish the transport orders created for the mobile application repository. This helps in identifying the required transport orders to be transported to the target system. 7.4.4 Assigning the MAR ID Use The Mobile Application Repository ID identifies the specific repository in the corresponding CRM server. The CRM server then identifies this repository while establishing a connection with it. Prerequisites You have obtained the ID of the repository you want to specify, from the ARS_SYSTABLE. Procedure 1. Logon to the CRM Server. 2. Locate the transaction SMOBREPMAIN under the folder User Menu for and double-click on it. The Display Mobile Application Repositories screen appears. It displays a list of repositories (if any exist) in the read-only mode. 3. Choose Repository  Change/Display. The Change Mobile Application Repositories screen appears, displaying the list of repositories (if any exist) in write mode. 4. Choose Repository  Create to specify the repository. An empty row appears in the list of repositories.

Specifying a repository in the CRM Server means creating the respective repository entry using the transaction SMOBREPMAIN. 5. Specify repository name and repository ID in the corresponding fields.

The option Client Upgrade allowed has no significance for the replication. It is required only to facilitate the client upgrades. This option indicates that the repository is permitted to send client upgrades through this CRM Server. 6. Repeat steps 4 and 5 to specify more than one repository in the CRM Server. When you are finished, continue with step 7. 7. Choose Repository  Save.

01 2017 126

7 Additional Information

Result The CRM server can receive the objects sent by the specified application repository during transport. You can continue with assigning the MAR ID for the test and production application repositories in their corresponding CRM servers using this procedure. You have completed the setup. You can start using the transport services. Make sure that the Central Service is also running on the repository to which the transport services connect. 7.4.5 Creating User Accounts in User Manager Use Create and maintain user accounts that require access to the Mobile Application Repository. For more information regarding User Manager, see the Mobile Application Studio online help. Procedure 1. Logon to the Mobile Application Studio. The SAP Mobile Application Studio screen appears. 2. Choose Tools  User Manager. The User Manager window appears. 3. Choose Create. 4. Enter the appropriate Name and Password. 5. Using the following table, assign a profile for this user account.

Profile Definition ARSAdmin Provides read and write access to all tables, such as, User, Profile, and MAR related tables. ARSDeveloper Provides read and write access to all MAR related tables, read-only access to the User table, with the exception of password modification, and no access to the Profile table. ARSUser Provides read-only access to all MAR related tables, read-only access to the User table, with the exception of password modification, and no access to the Profile table.

6. Choose Save. 7. Confirm the password.

You can create a user account without assigning a profile to it. If you do this, you must add a profile to the user account using Modify, before you log into the Mobile Application Studio. Result You have completed the configuration of the Mobile Repository Server. 7.4.6 Troubleshooting Transport Agent Service Failed

01 2017 127 7 Additional Information

Reason Solution

The Transport Agent (TA) cannot Check and correct the login parameters specified connect to the CRM Server. during the TA installation. The MAR initialization failed. See MAR Initialization Failed for possible causes. MAR Initialization Failed

Reason Solution

Invalid login parameters such as DSN,  Ensure that the DSN entered is available on the username and password local system and the username and password are valid.  Try using the parameters to logon to SAP Mobile Application Studio.  Although you modified the password after you configured the TA using TransportConfigurator, TA still uses the old password. Update the password using the Service tab of the TransportConfigurator.  If the user management feature is enabled, then make sure the user name is mapped to a valid profile. Invalid DSN The DSN does not refer to a valid application repository. Ensure that the default repository in the DSN is set to a valid repository. Incompatible database structure Ensure that the version of the ARS.DLL is compatible version with the current version of the application repository. For more information, contact your system administrator. Unknown error  Check whether the files ErrComp.DLL, ARS.DLL and LockManager.DLL are installed. If these files are not installed, install and register them now. If they are already installed, register them.  Check whether the Central Service is running. Unable to connect to the Central  Ensure that the Central Service has been started Service Component and is running.  Check if the entries ServerMachineName and RemoteSocketPort in the ARS_SYSTABLE are consistent with the Central Service. Incompatible build version Upgrade to the latest ARS.DLL file. If initialization still fails, contact your system administrator. Connection to the CRM Server Failed

Reason Solution

Password of the user on the CRM Stop the TA service. Update the password of the user Server has been changed. using the CRM Server Connection option in the

01 2017 128

7 Additional Information

TransportConfigurator. You have SAP GUI 7.1 installed which Kindly refer to SAP Note 1287556 for SAP GUI 7.1 supports only DotNet Connector. compatibility. Change Lists Are Not Moving from the Repository to the CRM Server

Reason Solution

The TA service is not started. Start the TA service. The CRM Server is not recognizing the  Check whether or not the repository ID is repository. specified in the CRM Server. If not, enter the ID using the SMOBREPMAIN transaction in the CRM Server.  Check whether or not the specified repository ID is correct. If not, make sure that there is not another repository specified in the CRM Server and then modify the ID using the SMOBREPMAIN transaction in the CRM Server. Connection to the CRM Server failed. Refer to the previous section.

The reasons and solutions provided in this table also apply if change lists are not moving from the CRM Server to the repository. Unable to Specify the Repository ID in the CRM Server

Reason Solution

You do not have the authorization to Contact your system administrator to get the specify the repository ID in the CRM SAP_MAS_TRANSPORT_ADMIN role authorization Server. and then try again. 7.4.7 Technical Details Ownership Transfer Parameters To enable ownership transfer, you must specify values for the corresponding parameters. Before specifying values, make sure that the repositories to which you want to transfer the ownership are specified in the ARS_KNOWNREP table. The following table describes the ownership transfer parameters to which values must be specified:

Parameter Description Value

OTALREP Contains a list of repository IDs. While transferring the , ownership of object(s), you can choose a repository to which , the ownership of the object(s) has to be transferred. ….. OTN Determines whether to allow ownership transfer from the Yes or No current repository. If values are not specified for the OTALREP parameter, the SAP Mobile Application Studio displays all repositories that are specified in the ARS_KNOWNREP table.

01 2017 129 7 Additional Information

The ARS_KNOWNREP table contains other repositories in addition to the repositories you specify. The other repositories include SAP delivery repository and repositories from the previous releases. If you do not specify values for OTALREP, the Mobile Application Studio user can see all available repositories in the ARS_KNOWNREP table. This can cause severe problems. If the Mobile Application Studio user selects SAP delivery repository or a repository from a previous release, the source repository transfers the ownership. However, this transferred ownership cannot reach the target repository.

01 2017 130

7 Additional Information

7.5 Appendix E: Mobile Application Repository Transport Concepts 7.5.1 Overview CRM Mobile Client Component software requires two transport types. One handles transports of development objects within a development landscape; the other handles the transport for deployment and installation of applications and runtime objects.  Transport delivers development results in a distributed development landscape. Development objects, such as source code or tile definitions, are distributed among multiple application repositories. The Mobile CRM transport functionality is based on the functionality of the R/3 transport system.  You can transport CRM server customizations and ABAP-Workbench changes along with changes made in the Mobile Application Studio in the same change request.  You can reuse the predefined transport paths between CRM servers.  Upgrade Console deploys and installs executable software and other runtime objects, such as HTML files, to the machines where the SAP Mobile Application Studio components are installed. Use the Upgrade Console functionality to send the upgrade files to these machines and it ensures that the upgrade is executed at the proper time. The Upgrade Console uses the BDoc distribution mechanism of the CRM Middleware. It sends an upgrade to all mobile clients that have subscribed to a specific publication. The upgrade software on the client machine automatically executes the upgrade after it has received the new software. To avoid sending large upgrades over a low-bandwidth network, such as a telephone line, the upgrade files can also be shipped on a DVD. In this case, only the trigger to execute the upgrade is transmitted via the BDoc distribution mechanism. 7.5.2 Transport Component The Transport Management services of the SAP Mobile Application Studio facilitate setting up distributed development landscapes. Landscapes typically consist of three systems; Development, Test (Quality Assurance), and Production. These three systems build a transport chain where the development systems deliver objects to the test system, which in turn delivers to the production system. The Transport Service (Transport.exe) is a Microsoft Windows service. The service uses:  A console, which allows the user to monitor (and configure) a number of transport related activities. This component is integrated into the Mobile Application Studio.  An agent, which monitors the local repository for data that needs to be transported, and the CRM server for data that needs to be imported. It also triggers the transport and import of this data. The transport component establishes the connection between the SAP Mobile Application Studio and the CRM server. A Mobile Application Studio user can query the server for existing Transport Orders and attach a change list to an existing transport order so that it is exported to the next (target) system in the landscape.

01 2017 131 7 Additional Information

7.5.3 Transport A development and customizing landscape typically contains at least three CRM servers. We recommend connecting a separate Mobile Application Repository to each CRM server. Doing so provides one repository for development (DEV), one for quality assurance (QA), and one for production (PROD).

Figure 1: A Three-Repository Landscape

A three-repository landscape isolates development from testing and production environments. You can proceed with new development after you have started testing, because the new development code is isolated in a QA repository for testing. This helps ensure that the code you are using in the production environment can be fixed quickly in the testing environment and transported immediately, if necessary. Having a QA repository allows you to test new development and maintain the consistency of the test and productive systems.

Figure 2: Fixing a critical issue in the PROD Repository

01 2017 132

7 Additional Information

6.5.4 Architecture Application Repository Transport

Figure 3: Mobile Application Repository Transport Architecture

The above diagram depicts the architecture of the MAR transport system. The architecture supports the transport process. To transport a change list from the DEV repository to the QA repository, use the following process. 1. Create a new change list in the SAP Mobile Application Studio. 2. Assign the change list to a change request on the CRM server. The Mobile Application Studio communicates with the CRM server via RFC using the R/3 DCOM connector. Assigning a change list to a change request means that a logical transport object is added to the request with the change list ID as a parameter. 3. Release the change list in the Mobile Application Studio. 4. The Transport Agent (service), which periodically polls the MAR to determine whether or not new change lists have been released, picks up the released change list and sends the change list data to the CRM server. 5. The data is put in a set of tables on the CRM server. These tables are depicted as MAR change list queue in Figure 3. 6. Use the Transport Organizer on the CRM server to release and export the change request. (You cannot release the change request before the change list data arrives, if you have assigned the change list to it. You receive an error during export). 7. The exported change request is transported along the default path and imported into the QA CRM server (Middleware). During the import the change list data are imported into the MAR change list queue of the target.

01 2017 133 7 Additional Information

For more information regarding transporting change requests, see SAP Note 429039 and the online help. 8. The transport agent, which periodically polls the queue on the QA CRM server, takes the imported change lists and imports them into the repository. The imported change lists are released. Download, import and release of change lists occurs automatically. 9. Using the Mobile Application Studio, check whether or not the import caused collisions. (This occurs when changes, such as bug fixes, were made in the target system.)

For more information regarding collisions, see the online help. 7.5.5 Client Upgrade The Transport Agent is required in order to move data from the Mobile Repository Server to the CRM Server. The transport must connect to the CRM server's transport system, because the Client Upgrade must send data to the inbound adapters of CRM Middleware. To minimize the number of services, the Upgrade Console reuses the Transport Agent to send data to the CRM server. Figure 4 depicts the architecture used for the Upgrade Console. After completing development, use the Mobile Application Studio to generate the runtime files. The Upgrade Console creates an upgrade configuration by selecting files and assigning target locations. In package mode you can send an upgrade you saved to the file system previously. Because the transport agent transports change lists between the Mobile Repository Server and the CRM server, the upgrade is created as a special type of change list and imported to the MAR. These are runtime object change lists, which contain compressed run time files (DLLs, HTML files, etc.) of the Mobile Client application. Runtime object change lists cannot be attached to change requests on the server. You send client upgrades only to mobile clients in the same system to upgrade their runtime environment. Runtime object change lists cannot be transported to any other system, for example, from a DEV system to a QA system. Once the runtime object change list has been created and released by the Upgrade Console, the Transport Agent sends it to the CRM server as any other change list. A function module on the server determines that it is a runtime object change list and moves it into a special queue for runtime objects. This queue is an intermediate buffer that stores the upgrade change lists. When the Transport Agent sends another command, push runtime objects to clients, to the CRM server, the upgrade moves into the queues of the subscribed clients as BDocs where the Middleware's inbound adapter can pick them up. All mobile clients that are subscribed for upgrade BDocs receive the upgrade the next time they connect to the server. After the last subscribed client receives the upgrade, it is removed from the queue. After the mobile client receives the upgrade data, the Client Upgrade target service executes the upgrade automatically.

01 2017 134

7 Additional Information

Figure 4: Mobile Client Upgrade Architecture

The upgrade configuration can contain any type of file and script, registry files and sql batch files that are executed on the target machine in a user defined order. In addition to the online upgrade, where the complete upgrade is sent via BDocs, a DVD upgrade can be used. With DVD upgrade, the upgrade files are copied to the target machine from DVD or from an ftp or http server. The middleware only sends the trigger to install the upgrade. The advantage is that the user can choose when the files are copied but the middleware still controls when the upgrade is activated. This way it ensures that upgrades of server and clients are synchronized.

If you do not want to grant administrator permissions to the mobile client users, you need to install the Client Upgrade Helper Service on the laptops. Doing so enables the Client Upgrade to install new software even if the user has no administrator permissions.

For more information regarding the Upgrade Console, see the online help in the Upgrade Console application on the Mobile Repository Server.

01 2017 135 7 Additional Information

7.6 Appendix F: Mobile Client Applications Installation with Initialization File You can replicate your installation process for installing the software on multiple laptops. Use this installation feature to create an initialization (.iup) file which you use to perform identical installations on each Mobile Client. This way you need not repeat the entire installation routine on each machine. 7.6.1 Creating the Initialization File You create the initialization (.iup) file during the installation process. This functionality is part of the installation routine. Procedure 1. When the following screen appears, choose Save Configuration.

A save file dialog appears select the file name to save it to. Note that you should save the file on a disk location that does not contain spaces. Also .iup file MUST NOT be on a read-only device.

2. Choose OK. 3. Continue with the installation.

01 2017 136

7 Additional Information

7.6.2 Installing Multiple Mobile Clients Use Use this procedure to install the identical software on all Mobile Clients using the IUP file you created. The installation from the IUP file installs in quiet mode, meaning that you do not need to provide information during this installation process. Procedure 1. Choose Start  Programs  Accessories  Command Prompt. The Command Prompt screen appears. 2. Type the appropriate command including the option and parameters you require, for example, setup.exe /qn RESPONSEFILENAME=""

For example, setup.exe /qn RESPONSEFILENAME="C:\TEST.IUP" 3. Press Enter to start the installation.

01 2017 137 7 Additional Information

7.7 Appendix G: Generation of Table Scripts To Generate the table scripts and corresponding TPS.Net files using Client Console follow the below mentioned steps: 1. Select the type of script to be generated. a. Client Console can generate scripts for Unicode and Non Unicode Solution. b. Please make sure that the option selected is compatible with the installed solution in terms of being Unicode or Non Unicode. 2. Select the generation type. a. The following options are available:  Tables and Indexes: Generates both tables and Indexes.  Tables Only: Generates the tables only without indexes  Indexes Only: Generates only the indexes for the selected tables. 3. Select tables a. The following options are available:  Selected Tables: Generates script for only the selected table.  All tables: Generates for all the tables fetched from the server.  Generates all tables fetched from a specified text file.  Advanced Selection Criteria: Lists additional parameters based on which tables can be further filtered. 4. Index Selection a. This Step is valid only if generation of Index has been selected in Step 3. b. The following options are available for this step:  All Indexes: Generates index for all tables listed  Delta Indexes: Generates all delta indexes by comparing the timestamp of the indexes created at the server.  Modified between: All indexes modified within the data range specified. 5. Select the type of script to be generated. The following options are available for this step.  Generate Delta Table Script: Generated only the delta changes in the tables. If this check box is not selected it will do a full generation of the selected tables.  It will generate additional scripts in for Upgrade.sql in the bin.net directory. Normally this is not required.  This is used for the generation of middleware specific and populating them with some specific values. This is not related to any application and is only used by middleware. 6. Log scripts  Log scripts to file: This is be used to log the generated script to a .sql file at a specific location.  Execute on user database: Executes the scripts directly on the ides.

01 2017 138

7 Additional Information

7.8 Appendix H: Mobile Client Rollout Manager Purpose This component facilitates easy rollout of new laptops at a customer site, with all the data that is necessary to begin using the laptop. It also allows the generation of a replacement laptop. When a CRM Mobile Sales user is unable to use his laptop, a replacement laptop may be the fastest solution that can be provided. The user will contact the support who in turn will provide a replacement laptop within a day with the same data that existed on the defective laptop. You use this tool to generate the replacement laptop. The Rollout Manager functions in two modes namely:  Replacement Mode  Rollout Mode Implementation Considerations To work in the replacement mode, the stationary site (the computer used by the laptop provider) must have:  CRM Mobile Sales installation and subscription to common data without any subscriptions to site-specific data.  ConnTrans running as a Microsoft Windows NT service configured to run at frequent intervals (This will keep the user database updated by getting the most recent data from the server).  The data directory under the on the target site shared.  Authorization to the following Administration Console functions on the CRM server:  SMOE_MITABT_SEL  SMOE_USER_SEL  SMOE_RECOVERY_SITE_SEL  SMOE_MITLINK_SEL  SMOE_GROUP_SEL  SMOE_GROUP_SITE_SEL  SMOH_SITE_RELEASE  SMOH_EXTRACT_DATA_FOR_SITELIST  SMOJOBSPENDING To do this, create a user of type communication in the CRM server using transaction (TU01). Assign an authorization profile for this user that includes the authorization for the authorization object S_RFC. In field RFC_NAME set the function groups SMOE_DATABASE_CARE, SMOH_DATABASE_CARE, SMOH_QUEUE.

The stationary site and the replacement laptop must have the same version of the CRM Mobile Sales installation.

01 2017 139 7 Additional Information

Integration To do this Use Send and receive data from the CRM server ConnTrans Extract data relevant to a laptop Administration Console Assigning a Site ID Client Console 7.8.1 Installing the Mobile Client Rollout Manager Prerequisites

System Requirements

The hardware requirements for the Mobile Client Rollout Manager, Stationary site can be found at section Hardware Requirements.

The Mobile Client Rollout Manager is installed along with the development workstation installation. 7.8.2 Setting up the Environment for the Stationary Site Setting up the environment for the stationary site involves the following steps. This is necessary so that the stationary site can generate replacement laptops and rollout laptops. 1. Install the operating system 2. Install Microsoft SQL Server  Install the development workbench. During this installation, choose the option Mobile Client Rollout Manager with communication to CRM server switched on. 3. Log on to the CRM server and create a Business Partner of type employee. 4. Log on to the Administration Console and create a site. The created site will be used as the stationary site. This site should contain all common subscriptions without any subscriptions to site-specific data. 5. Create subscriptions based on the employee and attach the subscriptions to this site. 6. Link the Business Partner created to this site. 7. Start Client Console and choose AssignSiteID to assign this site to the laptop.

ConnTransService must run as a Microsoft Windows service configured to run at frequent intervals. This will keep the user database updated by getting the most recent data from the CRM server. 8. Execute ConnTrans and start data download. 9. Start Microsoft SQL Server services if it is not already running. 10. Share the Backup folder .

01 2017 140

7 Additional Information

7.8.3 Setting up the Environment for the Rollout/Recovery Site 1. Install the operating system 2. Install Microsoft SQL Server 3. Start Microsoft SQL Server Services if it is not already running. 4. Install CRM Mobile Sales with communication to the CRM server switched on. 5. Create rollout sites using the Administration Console and assign subscriptions to the site. 6. Share the data folder . The data folder is shared for Read and write access to the data directory

Laptop(s), which are to be rolled-out, should be available on the network. The version of Microsoft SQL Server must be the same on both the stationary as well as the rollout/recoverysite. 7.8.4 Intermediate Step Execution of the Mobile Client Rollout Manager The activities performed by the Mobile Client Rollout Manager can be categorized into the following steps:

1. Common steps The steps that are common to all the rollout or replacement sites are listed below:  Read stationary site details  Check the inbound queue of the stationary site for pending records  Release selected sites for reuse  Clean the outbound queue on the CRM server for selected sites  Stop the ConnTransService.  Run ConnTrans application  Start the extract for selected sites  Backup the database  Start the ConnTransService 2. Restore Database 3. Assign site 4. Invoke ConnTrans The following figure illustrates the above mentioned steps that are involved during the execution of the Mobile Client Rollout Manager:

01 2017 141 7 Additional Information

All these steps are automatically executed in the above mentioned sequence when you rollout or replace laptops by using the Mobile Client Rollout Manager. However, if an error occurs during the execution of any of the steps, you have to repeat all the four steps, which is a time consuming process. The Mobile Client Rollout Manager is enhanced to allow you to execute from an intermediate step in which the error occurred. You can execute the application from any intermediate step starting from step 2 till step 4. As a result, the overall performance improves during the rollout of laptops.

During the rollout or replacement of laptops, if an error occurs in the assignment of sites (step 3), you can execute the application again from step 3. As a result, you do not have to repeat steps 1 and 2.

You can execute the application from an intermediate step only through the command line. The command line options are enhanced to execute the application from an intermediate step. For more information, see Executing Mobile Client Rollout Manager from the Command Line. When you execute the application from an intermediate step:  All the preceding steps must have been executed for that site.  All the succeeding steps are automatically executed. Therefore, you cannot execute an intermediate step only.  All the sites are executed from the same step. Therefore, you cannot execute different sites from different steps. For example, the Mobile Client Rollout Manager cannot simultaneously perform the database backup of Site A and Restoration of the database for Site B.

If you execute the application from an intermediate step, the same is indicated in the stationary site log file and the site specific log files (if enabled).

01 2017 142

7 Additional Information

7.8.5 Parallel Processing of the Rollout Manager Activities The activities performed by the Mobile Client Rollout Manager are executed in synchronous mode, which is a time consuming process and also affects the performance of the application. Therefore, the Mobile Client Rollout Manager is enhanced to allow parallel processing of the activities it performs. For information on the activities performed by the rollout manager, see Intermediate Step Execution of the Mobile Client Rollout Manager. However, parallel processing is enabled only for the time consuming activities that are executed on the rollout laptops as explained below:

Parallel processing occurs only when you execute the rollout manager from the command line. For more information, see Executing Mobile Client Rollout Manager from the Command Line. Common Steps The parallel processing of the execution of this step is not enabled, as the activities are not performed on the rollout laptops. 1. Restore Database The execution of this step is enabled for parallel processing as the activities performed by this step are time consuming. Parallel processing is achieved by two stored procedures that are executed asynchronously. The first stored procedure is executed on the Master database and performs the following activities:  Reads data from the hard disk of the stationary site  Copies the IDES.MDF and IDES.LDF files to the buffer

To enable file copy, you must ensure that Microsoft SQL Server service of all the rollout laptops running under an account (local account or windows domain account) has Read permissions on the IDES.MDF and IDES.LDF files of the stationary site.  Transfers these files through the network to the rollout laptop  Writes the IDES to the rollout laptop When the data transfer is in progress for the first laptop, the stationary site is released by the second stored procedure and the first stored procedure starts the above mentioned activities for the second laptop and so on. The performance significantly improves as a result of this asynchronous execution. 2. Assign site The assignment of sites on an average consumes about 30 seconds to 1 minute. As a result, the execution of this step is not enabled for parallel processing. 3. Invoke ConnTrans ConnTrans can be invoked on the rollout laptop in about 30 seconds to 1 minute. As a result, the execution of this step is not enabled for parallel processing.

7.8.6 Replacing Defective Laptops

01 2017 143 7 Additional Information

Purpose Using the replacement mode, you can generate a replacement laptop with the same data that existed on a defective laptop. To start the application in Replacement Mode, go to Start Programs SAP CRM Mobile Client  Administration Tools  Mobile Client Rollout Manager. The Rollout Manager is invoked in the replacement mode only for the first time. Process Flow A diagrammatic representation of the data recovery process follows

The process flow is described below:

... 1. Ordering a replacement laptop: The CRM Mobile Sales user communicates to the support group that his laptop is not functioning and needs to be replaced immediately. He also has to transfer data (if any) from his outbound queue to the CRM server and then stop using his defective laptop. 2. Executing the Rollout Manager: The laptop provider (support group in this case) executes the Rollout Manager on his computer (the stationary site that has a CRM Mobile Sales installation). 3. Connecting to the CRM Server: Once the tool has started, a connection must be established with the CRM server.  Choose OK. The CRM server Logon screen appears where you have to enter the login attributes to connect to the CRM server. Enter: Field Entry Destination name Name of the CRM server

01 2017 144

7 Additional Information

Application Server IP Address (SAP Router String) of the CRM server System Number System Number of the CRM server Client Number The client of the CRM server you want to connect to Login Your user name Password Your password

The details you entered are stored in the registry and retrieved the next time you start the application. However, the password is not stored in the registry.

4. Choosing the Site ID of the laptops that are to be replaced: a. Choose Replacement. All the mobile client replacement sites appear under Existing Sites (on the left side). b. Choose OK. The Mode combo box appears from which you must choose whether you want to view rollout sites or replacement sites. c. Select the Site ID (you can select more than one site at a time) of the laptop that needs to be replaced.

You can select the sites that you want, using the Advanced Find button. This allows you to choose sites based on organization or based on the user. d. Choose OK to continue. The processes that happen henceforth are automated. Background Processing

... 1. Reading the stationary site details: The details of the stationary site are read and recorded for further use. 2. Checking the inbound queue of the stationary site: The tool will check the inbound queue of the stationary site for unprocessed messages to avoid data loss. The messages are processed and the inbound queue is kept empty. 3. Deleting the Database ID of the defective laptop: The database ID(s) of the laptop that will be replaced is deleted from the CRM server. This ensures that the site which had the database id is free and can be used again. It also ensures that the CRM Mobile Sales user cannot use his site until the replacement laptop arrives. 4. Deleting outbound queue entries of the defective laptop: The outbound queue entries of the replacement site are deleted in the CRM server. When the Administration Console‘s extract functionality is later used to extract data, it would extract all site-specific data and this will result in duplication of data in the outbound queue if the entries already exist. 5. Stopping ConnTransService on the stationary site: Stopping the service avoids partial import of data during the backup process.

01 2017 145 7 Additional Information

If the process is unable to proceed beyond this, restart the computer and then continue. 6. Starting ConnTrans: ConnTrans must be executed to start receiving data from the CRM server. If there are any pending entries in the outbound queue on the CRM server, the Rollout Manager automatically starts the data transfer to receive these messages. 7. Starting the Admin Console extract functionality and getting site-specific data from the Consolidated Database: Since the site id of the replacement laptop has been freed by deleting the database id, the site can be reused and all data relevant for that site need to be extracted from the consolidated database. The tool triggers a site-specific extract (excluding the bulk data) for each of the replacement sites. 8. Backing up the user database on the stationary site: The user database (IDES) must be backed-up so that it can be restored on the replacement laptop. Since ConnTrans has been executed before the backup, the user database will have the newest data.

The backup of the database is not a backup literally. The Microsoft SQL Server is shutdown and the data and log files are copied to the backup directory and the server is restarted. Later, during the restore process, these files are copied to the data directory of the replacement site and are attached to the target SQL server. This optimizes the performance of the Rollout Manager. Before the backup begins, make sure that the IDES database is free and not being accessed. Also, Microsoft SQL Server must be running when the backup happens. 9. Restarting ConnTransService: Restarts data transfer from the CRM server to the stationary site to keep it in synchronization with the CRM server. 10. Restoring the user database from the stationary site to the replacement laptop: Enter the machine name of the replacement laptop on which the user database must be restored and then select the Process Selected Sites button.

The restore is a serial process, i.e., only one restore can be done at a time. No simultaneous restores are supported. 11. Deleting data relevant to the stationary site from the replacement laptop: This includes details like site-specific data present in the tables. During the restore process, even the site and queue-specific data that is relevant to the stationary site are sent across to the replacement site. This data must be deleted so that the site can be reused. The user information pertaining to CRM Mobile must also be recreated. This is automatically done. It runs an SQL Script "CleanDB.sql“ that is available in the installation path. 12. Reassigning the Assign Site ID: This will re-register the database id and queue id's of the replacement laptop with the CRM server. 13. Trigger ConnTrans: to start receiving data. If an instance of ConnTrans is already running on the stationary site, triggering ConnTrans via the Rollout Manager will fail.

Result

01 2017 146

7 Additional Information

The replacement laptop is now ready for shipment to the CRM Mobile Sales user whose laptop was defective. 7.8.7 Rollout Laptops

Purpose Using the rollout mode, you can generate a new laptop with data that is necessary to begin working with the SAP CRM Mobile Applications. This facilitates the Go-Live process. To start the application in Rollout Mode, go to Start Programs SAP CRM Mobile Client  Administration Tools  Mobile Client Rollout Manager.

Process Flow 1. Executing the Rollout Manager: The laptop provider executes the Rollout Manager on his computer. 2. Connecting to the CRM Server: Once the tool has started, a connection must be established with the CRM server.  Choose OK. The CRM server Logon screen appears where you have to enter the login attributes to connect to the CRM server. Enter: Field Entry Destination name Name of the CRM server Application Server IP Address (SAP Router String) of the CRM server System Number System Number of the CRM server Client Number The client of the CRM server you want to connect to Login Your user name Password Your password

The details you entered are stored in the registry and retrieved the next time you start the application. However, the password is not stored in the registry. 3. Choosing the Site ID of the laptops that are to be rolled out: . Choose OK. The Mode combo box appears from which you must choose whether you want to view rollout sites or replacement sites. . Choose Rollout. All the mobile client rollout sites appear under Existing Sites (on the left side). . Select the Site ID (you can select more than one site at a time) of the laptop that needs to be rolled out.

You can select the sites that you want, using the Find button. This allows you to choose sites based on organization or based on the user. . Choose OK to continue. The processes that happen henceforth are automated. 4. Reading the stationary site details: The details of the stationary site are read and recorded for further use.

01 2017 147 7 Additional Information

5. Checking the inbound queue of the stationary site: The tool will check the inbound queue of the stationary site for unprocessed messages to avoid data loss. The messages are processed and the inbound queue is kept empty. 6. Deleting the Database ID of the rollout laptop: The database Ids of the rollout sites are checked for their DBID entries and if filled, the value is deleted. 7. Deleting outbound queue entries of the rollout laptop: The outbound queue entries of the rollout site are deleted in the CRM server. When the Administration Console‘s extract functionality is later used to extract data, it would extract all site-specific data and this will result in duplication of data in the outbound queue if the entries already exist. 8. Stopping ConnTransService on the stationary site: Stopping the service avoids partial import of data during the backup process. 9. Starting ConnTrans: ConnTrans must be started to receive data from the CRM server. If there are any pending entries in the outbound queue on the CRM server, the Rollout Manager automatically starts the data transfer to receive these messages. 10. Starting the Admin Console extract functionality and getting site-specific data from the Consolidated Database: Since the site id of the rollout laptop has been freed by deleting the database id, the site can be reused and all data relevant for that site need to be extracted from the consolidated database. The tool triggers a site-specific extract (excluding the bulk data) for each of the rollout sites. 11. Backing up the user database on the stationary site: The user database (IDES) must be backed-up so that it can be restored on the rollout laptop. Since ConnTrans has been executed before the backup, the user database will have the newest data.

The backup of the database is not a backup literally. The Microsoft SQL Server is shutdown and the data and log files are copied to the backup directory and the server is restarted. Later, during the restore process, these files are copied to the data directory of the rollout site and are attached to the target SQL server. This optimizes the performance of the Rollout Manager. Before the backup begins, make sure that the IDES database is free and not being accessed. Also, Microsoft SQL Server must be running when the backup happens. 12. Restarting ConnTransService: Restarts data transfer from the CRM server to the stationary site to keep it in synchronization with the CRM server. 13. Restoring the user database from the stationary site to the rollout laptop: Enter the machine name of the rollout laptop on which the user database must be restored and then select the Process Selected Sites button.

The restore is a serial process, i.e., only one restore can be done at a time. No simultaneous restores are supported. 14. Deleting data relevant to the stationary site from the rollout laptop: This includes details like site-specific data present in the tables. During the restore process, even the site and queue-specific data that is relevant to the stationary site are sent across to the rollout site. This data must be deleted so that the site can be reused. The user information pertaining to CRM Mobile must also be recreated. This

01 2017 148

7 Additional Information

is automatically done. It runs an SQL Script "CleanDB.sql“ that is available in the installation path. 15. Reassigning the Site ID: Running this feature will register the database id and queue id's of the rollout laptop with the CRM server. 16. Trigger ConnTrans: to start receiving data. If an instance of ConnTrans is already running on the stationary site, triggering ConnTrans via the Rollout Manager will fail.

Result The laptop is now ready for the Go-Live process with all the data that is necessary to start using the CRM Mobile application. 7.8.8 Troubleshooting Options When an error occurs, the troubleshooting feature of the tool provides the reasons for the error. You view the type of error, source (which is more for the support group), possible causes, and suggestions.

The Rollout Manager can start the suggestion screen automatically whenever an error occurs or you can view the error by choosing.

If you are unable to solve the error, create an OSS message in the component CRM-MW-MRM. 7.8.9 Logging Options All the activities that happen in the background during the rollout/replacement process can be logged to a separate file for later use.

01 2017 149 7 Additional Information

1. Choose from the Rollout Manager. The File Logging Options screen appears.

01 2017 150

7 Additional Information

The following options are available: Field Description Default Values File Name Specify the system path where C:\Temp\Rolloutlog.txt you want to store the log file. Maximum File Size Specify the maximum amount of 1 MB information that can be stored in the log file. Append/Replace Specify whether the existing log Append file must be appended or replaced with a new log file whenever the application is restarted. Log Specify whether you want to log Errors errors, warnings or any information that the application provides during its functioning. Decentralized Creates individual log files for Unchecked Logging each rollout site in addition to the centralized log file 7.8.10 Filter Criteria Mobile client sites can be filtered based on user information or organization. Filtering based on user information allows you to search for sites based on user id, first name, or last name. You can select specific sites or all the sites linked to a user.

The need for organization-based filtering is to select sites linked to a particular organization and perform a replacement/rollout without individually selecting these sites. If you need to select sites linked to various levels in the organization hierarchy, use the filter criteria and search on organization including or excluding its sub-organizations. You can search based on organization name and description. However, sub-organizations are not included in the search by default. You must choose the sub-organizations explicitly along with the organization to select sites linked to the sub-organizations.

01 2017 151 7 Additional Information

7.8.11 Searching for Sites based on User Information

Procedure 1. Enter the search text in the Search Sites dialog box. You can use wildcards like * and %. These wildcards must be at the end of the search text. 2. In the Search In options, select the User radio button and then choose the filtering criteria (First Name, Last Name or User ID). 3. Click Find. The list of all users matching the search criteria is listed in the search results grid. 4. Choose the users and click on OK to select all the sites linked to them. The selected sites are displayed in the Site Selection screen. 5. If you want to select specific sites linked to users, choose the Select Sites button. By default, the list of all the sites linked to user(s) is displayed as selected sites in the SiteSelection screen. 6. Choose the necessary sites and click OK. 7. Click OK on the Search Sites dialog box. The selected sites are displayed in the Site Selection screen.

You can select and deselect all the users by using the Select All and De- Select All buttons. To continue selecting multiple sites, click Apply in the Search Sites dialog box. This allows you to append sites to your already existing selection. 7.8.12 Searching for Sites based on Organization

Procedure 1. Enter the search text in the Search Sites dialog box. You can use wildcards like * and %. These wildcards must be used at the end of search text. 2. In the Search In options, select the Organization radio button and then choose the filtering criteria (Name or Description). 3. Click Find. The list of all the organizations matching the search criteria is displayed in the search results grid. 4. Choose the organization including or excluding its sub-organizations and click OK to select all the linked sites. The selected sites are displayed in the Site Selection screen.

By default, the list of all the linked sites is displayed as selected sites in the SiteSelection screen.

5. To select specific sites linked to an organization including or excluding its sub- organizations, click the Select Sites button. 6. Choose the necessary sites and click OK. 7. Click OK on the Search Sites dialog box.

01 2017 152

7 Additional Information

The selected sites are displayed in the Site Selection screen. 8. If you directly click on the Select Sites button in a particular row, all the sites linked to the organization are displayed as selected sites in the Site Selection screen. Repeat steps 6 and 7.

You can select and deselect all the organizations and sub-organizations by using the Select All and De-Select All buttons. To continue selecting multiple sites, click Apply in the Search Sites dialog box. This allows you to append sites to your already existing selection. 7.8.13 Executing Mobile Client Rollout Manager from the Command Line

Prerequisites You have:  A user ID with the access rights of the system administrator on SQL Server and DBOwner on the IDES database.  Set the user database login parameters in the registry.  A user ID and a password for the CRM server you want to connect to. You must know the details of the CRM server you want to connect to.

You can get the server details in the SAP Logon screen. Procedure 1. On the Taskbar, choose Start  Run. The Run dialog box appears. 1. Enter cmd and choose OK. The Command Prompt appears. 2. Enter the following command:

\ LptProvider.exe/StartupOption –MW -F -I - NoConnTrans -DecentralizedLog

The default application path is %MOBILEROOTDIR%.

The following table explains the parameters of the command. Parameter Optional / Description Mandatory StartupOption Mandatory Indicates the startup option in which the Rollout Manager must be executed. You can specify one of the following values:  /Replacement Executes the application in the replacement mode

01 2017 153 7 Additional Information

 /Rollout Executes the application in the rollout mode  /LPTRestoresite Executes the application from the restoration of the application database from the stationary site till ConnTrans is invoked (Step 4) for all the mobile client rollout sites. For more information, see Intermediate Step Execution of the Mobile Client Rollout Manager.  /LPTAssignsite Executes the application from the assignment of site till ConnTrans is invoked (Step 4) for all the mobile client rollout sites /LPTConnTrans Invokes ConnTrans on all the replacement laptops for the mobile client sites that are already assigned.

This parameter is applicable only for the mobile client sites that are already assigned. Therefore, you cannot specify this parameter for the rollout sites. MW Mandatory The Middleware parameters that must be provided to connect to the CRM server. F Mandatory The site name and the machine name of the laptop that is being used to start the Rollout Manager. This information must be stored in a .txt file and the name of this file is given as a parameter when starting the command line option. Within the .txt file, the semicolon must be used as a separator between the site name and the machine name. Each line in the text file would correspond to a particular rollout/replacement site information. I Optional Specifies the file to which messages are to be logged. If not provided then the default application log settings are used. The default application log can be found at \temp\Rolloutlog.txt NoConnTrans Optional Specifying this parameter will not start ConnTrans by default on all laptops. DecentralizedLog Optional Creates individual log files for each rollout site in addition to the centralized log file. In such a case, the centralized log file contains information related to the stationary site only. The site specific information is logged to the individual log files. This allows the administrator to monitor individual sites and perform the required action (if any).The individual site specific log files are stored in the same location where the centralized log file is stored. The naming convention of the site specific log files is _.TXT. You can also enable decentralized logging by using the

01 2017 154

7 Additional Information

DecentralizedLog registry key that is available under HKEY_CURRENT_USER\SOFTWARE\SAP\MSA\MW\MCRM. However, this key is not available by default. It is created when you execute the application for the first time either through the UI or the command line. Therefore, if you do not specify this parameter (the next time you execute the application), the value of the registry key is used. However, if you specify this parameter, the value of the registry key is ignored.

Result The Rollout Manager is executed in the specified mode. When the command line option is used, an icon appears in the system tray indicating that the Rollout Manager is functioning.

Example 4. Enter the following command to execute the Rollout Manager in Rollout mode. %mobilerootdir%\LptProvider.exe /ROLLOUT –MW -F -I <%mobilerootdir%\rolloutlog.txt> 5. Enter the following command to execute the Rollout Manager from the restoration of the database (Step 2) till ConnTrans is invoked (Step 4). The command also creates site specific log files. %mobilerootdir%\LptProvider.exe /LPTRestoresite –MW -F -I <%mobilerootdir%\rolloutlog.txt> -DecentralizedLog

Note 894419: During the use of the rollout manager Problems or error messages occur. This note will give advice for the most common problems.

01 2017 155 7 Additional Information

7.9 Appendix I: Customer Namespace Tool Customer Namespace Tool is used to register the customer namespaces Y or Z that are provided by SAP by default.

Procedure 1. Choose Start  All Programs  SAP CRM Mobile  Administration Tools  Reservation Tool for Customer-Namespaces. The Reserve Customer Namespace window appears. 2. Login to the Mobile Application Repository (MAR) in which you want to register the customer namespace. Indicate the DSN, Login ID and Password. 3. Choose Login. The Reserve Customer Namespace window displays the customer namespaces Y and Z. 4. Select the desired namespace, Y or Z. 5. Choose OK.

01 2017 156

7 Additional Information

7.10 Appendix J: Steps to subscribe to a SAP Note There are number of notes which are often updated with new fixes. Following are the step by step procedure explaining how to go about subscribing a SAP Note which is often updated.  Go to Service Market Place  SAP Support Portal  Help & Support Tab  Search for SAP Notes  Specify the Note number as highlighted in the screenshot and search

 A new window pops up showing the content and subscription option

01 2017 157 7 Additional Information

 Top right hand side you get an option to subscribe  Once you click on subscribe you will be shown a pop-up asking for your confirmation

 If you say ‘yes’ you get a confirmation pop-up

 Click on continue and start subscribing for SAP Notes which are updated frequently.

01 2017 158

8 Reference

CRM Master Upgrade Guide http://service.sap.com/instguides → SAP Business Suite Applications → SAP CRM → SAP enhancement package 1 for SAP CRM 7.0 → Plan → Upgrade Master Guide SAP CRM 7.0 SR1 CRM Master Guide http://service.sap.com/instguides → SAP Business Suite Applications → SAP CRM → SAP enhancement package 1 for SAP CRM 7.0 → Plan → Master Guide SAP CRM 7.0 SR1 CRM Mobile Installation Guide http://service.sap.com/instguides → SAP Business Suite Applications → SAP CRM → SAP enhancement package 1 for SAP CRM 7.0 → CRM Mobile → CRM Mobile Client 7.01 SP06 Installation Guide CDB Upgrade Guide Upgrading the CDB from CRM 4.0 to CRM 7.01: http://service.sap.com/instguides → SAP Business Suite Applications → SAP CRM → SAP enhancement package 1 for SAP CRM 7.0 → CRM Mobile → CDB Upgrade Guide 7.01 Post-Migration-Guide http://service.sap.com/instguides → SAP Business Suite Applications → SAP CRM → SAP enhancement package 1 for SAP CRM 7.0 → CRM Mobile → Mobile Client 5.0 Post-migration Troubleshooting Guide Upgrade Console The Help Guide for the Upgrade Console is available: %mobilerootdir%\Bin.Net MAS Help Guide The Help Guide for the MAS is available: Start -> SAP CRM Mobile -> Administration Tools -> MAS.pdf ECMT http://service.sap.com/instguides → SAP Business Suite Applications → SAP CRM → SAP enhancement package 1 for SAP CRM 7.0 → CRM Mobile → CRM Mobile Environment Check Modeler Tool Usage Guide Client Console The Helpfile for the Client Console is available from the Tool itself: Start Client Console → Help → Client Console Help SAP Mobile Support Center Documentations on the different areas of the Support Center are available directly from the Tool for:  Environment Analyzer  Customer Modification Analyzer Tool  Mobile Runtime Analyzer – Log Viewer  Mobile Runtime Analyzer – SQL Log Viewer  Mobile Runtime Analyzer – UI Metadata Viewer  Mobile Runtime Analyzer – BOL Metadata Viewer  Mobile Runtime Analyzer – BDoc Consistency Analyzer  Mobile Runtime Analyzer – Trace Viewer  Metadata Consistency Checker  BOL Tester  MAR DB Consistency Checker  Environment Check Modeler Tool  Environment Analyzer Report Analyzer Tool

01 2017 159