MDM Server Deployment Guide

Transcription

1 MDM Server Deployment Guide Version 2.1

2 Mobile Device Manager 2.1 Mobile Device Sync Manager 1.2 Mobile Consumer Device Management Template 1.2 Mobile Device Backup & Restore Template 1.1 Mobile Device Remote Control Template 1.2 Dual Mode Phone Management Template 1.1 February 2010 Copyright Alcatel-Lucent [ All rights reserved. Important Notice to Users No part of this document may be reproduced or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the express permission of Motive, Inc. ( Motive ) and/or Alcatel-Lucent. This document and the related software may only be used pursuant to a Software License Agreement or other similar written agreement in place between you and either Motive or Alcatel-Lucent. Furthermore, Motive and Alcatel-Lucent expressly disclaim any and all warranties regarding the information contained in, and the products and systems described in, this document, whether express, implied, or statutory, including without limitation implied warranties of merchantability or fitness for a particular purpose. Furthermore, this document is subject to change without notice. There may exist in this document references to using this product and the systems described herein in connection with products and/or systems owned by third parties. Please note that this information is provided as a courtesy to assist you. Such references are not intended to imply the granting of a license to use such products and/or systems. Such licenses shall result only from separately executed agreements between you and the owner of such products and/or systems. Neither Motive nor Alcatel-Lucent assume any responsibility or liability for incorrect or incomplete information provided about such third-party products. Motive, the Motive logo, and any Motive product names contained herein are trademarks or registered trademarks of Motive, Inc. Alcatel-Lucent and the Alcatel-Lucent logo are registered trademarks of Alcatel-Lucent. All other company and product names mentioned herein are the trademarks or service marks of their respective owners. The products and systems described herein may be covered by the various patents that have been issued to Motive and/or Alcatel-Lucent. Disclaimers This product is intended for commercial uses. Without the prior written consent of either Motive or Alcatel-Lucent it must not be used, sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. You hereby agree that the use, sale, license or other distribution of the products for any such application without the prior written consent of either Motive or Alcatel-Lucent, shall be entirely at your sole risk. You hereby agree to defend and hold Motive and Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications. This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail. PID MDM100-mdmDeployAdmin

3 Contents Preface... xi Audience... xi Conventions... xi Support and contact information... xii PART I INSTALLING THE MDM SERVER 1 Getting Started... 3 Standalone MDM Server installation and configuration overview... 4 Host server requirements... 4 Network and administration requirements... 5 Installation prerequisites... 5 Installation process summary... 6 MDM Cluster installation and configuration overview... 6 Host server requirements... 6 Network and administration requirements... 7 Installation prerequisites... 8 Installation process summary Standalone MDM Server Setup MDM Server installation process overview Preparing for the installation Installing the MDM Server Starting and stopping the MDM Server MDM Cluster Setup MDM Cluster installation process overview Preparing for the installation Installing the MDM Cluster Installing the MDM Administration Server iii

4 Installing the MDM Managed Server Starting and stopping the cluster Starting the MDM Cluster Stopping the MDM Cluster Updating the MDM Cluster Uninstalling the Managed Server Configuration and Post-Installation Activities Configuring the MDM Server Configuring the MDM WebLogic domain Creating the MDMAdmin role Creating a user for WiDM webservice calls Configuring multicasting Licensing the installation Storing your MDM product license Initial data creation Profile naming in a WiDM deployment Creating notification links Creating tenants Load setup data User Management on the MDM Server User roles and access permissions Adding a user Troubleshooting Verifying WebLogic is running Verifying Oracle database and database connection Managing Oracle database processes Verifying Oracle database processes are running Verifying the Oracle listener process is running Viewing the services for which Oracle is listening Checking client/server communications Understanding error codes Oracle Installation and Configuration Checklist Verifying system requirements iv

5 Performing prerequisite setup tasks as root user Performing prerequisite setup tasks as the oracle user Installing the Oracle 10g Enterprise Edition Server Verifying your Installation Installing the Oracle Client Creating the MDM database and schema BEA WebLogic Installation and Configuration Checklist Verifying system requirements Performing prerequisite setup tasks as root user Installing WebLogic Server Verifying the installation SMSC and Kannel Gateway Client Installation and Configuration Installing Kannel Starting the gateway components Apache Installation and Configuration Installing Apache Configuring Apache Configuring the Apache proxy server Sample Database Installation for Standalone Server Creating the database Verifying the installation MDM Server Monitoring PART II 13 ADMINISTERING THE MDM SERVER Mobile Device Manager Overview Modular platform architecture CP device provisioning DM device provisioning Firmware update Diagnostics v

6 Alerts ICE workflows Automated device configuration Comprehensive profile management Granular scheduling Web services APIs Highly scalable Fault tolerance Internationalization Accessing the MDM console Accessing the WebLogic Server Console Mobile Device Manager integration with operator systems Web service APIs Mobile Device Manager data model Countries, tenants, and subscribers Manufacturers, models, and devices Models and updates Profile templates and profiles Profiles and service tags Profile templates, profile mappings, and models Provisioning requests (jobs) MDM Console Managing SMSC/Notification Objects Managing Connection Types Managing notification links Viewing notification links Notification link parameters Testing notification links Creating or modifying a notification link Notification link XML file structure Deleting a notification link Managing Tenants About tenants Viewing tenants Creating a tenant Troubleshooting tenant creation vi

7 Editing tenant properties Deleting a Tenant Managing Countries Country file format Uploading countries Exporting countries Managing Profiles Understanding profiles Creating a profile Modifying a profile Deleting a profile Managing Subscribers Viewing subscribers Creating subscribers (bootstrap) Changing the status of a subscriber Activating a subscriber Deactivating a subscriber Deleting a subscriber Managing Models Viewing models Creating a model Editing model properties Deleting a model Updating CP models Managing Manufacturers Viewing manufacturers Creating a manufacturer Deleting a manufacturer Managing Devices Viewing subscriber devices Bootstrapping or rebootstrapping a device Creating a device Changing the status of a device Activating a device Deactivating a device vii

8 Clearing jobs for a device Editing device properties Deleting a device Managing profile assignments Uploading a profile assignments file for multiple devices Assigning a profile to a single device Comparing a profile assignment Fetching a profile assignment Resending a profile assignment Editing a profile assignment Deleting a profile assignment Scheduling device management jobs Discovering a device node Sending a command script to a device Assigning an image to a device Assigning an image to multiple devices Managing workflows Creating a workflow job Viewing workflow jobs Renaming a workflow job Updating a workflow job Deleting a workflow job Displaying a device tree Managing Updates Viewing updates Uploading an update package Uploading a workflow Discarding an update Deleting an update Bulk Management Managing bulk operations Creating bulk operations Deleting bulk operations Viewing bulk operations Canceling a bulk operation Managing device groups viii

9 Creating a device group Deleting a device group Managing search templates Creating a search template Updating a search template Deleting a search template A Managing Provisioning Requests Viewing Provisioning Requests Cancelling a Provisioning Request Logging, Reporting, and Monitoring the System MDM Server Logs Reporting system operations Device Activity Log Purging Device Activity Logs Audit Logs Reporting Statistics Understanding the Mobile Service Management Solution reports Reports provided Adding reports to new managed servers Monitoring Mobile Device Manager with SNMP Monitoring the provisioning request timer Monitoring notifications Managing Roles Modifying a role Adding new roles Advanced Operations Profiles, profile templates, and attributes About profiles Profile concepts diagram Profile metadata XML file reference Managing profile templates Managing Attribute Types Uploading a profile metadata file ix

10 Uploading a profile service file Managing DDFs Viewing a DDF Node Tree Uploading a DDF File Deleting a DDF Node Tree Managing profile mappings Managing CP profile mappings Configuring bootstrap templates Bootstrap Template Examples B Quick Start Reference Setting up initial database information Getting started Glossary Index x

11 Preface Motive Mobile Device Manager allows service providers to remotely provision, update, and manage mobile devices and services throughout the device life cycle. The product provides for single and bulk device provisioning, configuration and management, problem resolution, firmware upgrades, event management, and reporting. MDM Server uses the standards-based OMA DM protocol to communicate with the native DM client installed on mobile devices. Audience The MDM Server Deployment Guide provides all the information necessary to install and configure the MDM Server, a Mobile Service Management Suite software component, in either a standalone or clustered server deployment. This guide is intended for system administrators responsible for installing, configuring, deploying, and administering the MDM Server (Mobile Device Management Server). Part Part I, Installing the MDM Server on page 1 Part II, Administering the MDM Server on page 109 Audience Deployment team responsible for installing and configuring the MDM Server deployment (standalone or cluster). Typically, the team includes an architect, database administrator (DBA), network administrator, security administrator, and system administrator. Production team responsible for administering system information and managing devices by configuring and monitoring provisioning requests. Assumptions Familiarity with networks, web application servers such as BEA WebLogic, WebLogic cluster deployment, and Oracle database technologies. Familiarity with OMA (Open Mobile Alliance) standards, OTA (over-the-air) update technologies, notification mechanisms, and network infrastructures. Conventions This document uses the following typographic conventions: Audience xi

12 Bold Identifies the names of graphical user interface buttons, options, commands, fields, and labels. Italic Identifies variable placeholders such as function or method parameters representing information that must be provided by the implementation or user. Also identifies documentation titles and certain terms to emphasize meaning. Monospace Identifies information that you are required to type exactly as shown. This convention also identifies code and command samples, screen prompts, messages, and filenames. Monospace italic Identifies parameters whose actual names or values you must provide at a screen prompt or in a text field. UPPERCASE Identifies the names of keys on the keyboard. In multi-line code listings, the symbol indicates that the text was wrapped for typographical reasons. Support and contact information If you encounter issues with this product, visit the Online Customer Support (OLCS) [ website. After registering and logging on, you can access troubleshooting information. In addition, you can contact Alcatel-Lucent Motive Support by phone, fax, or , as follows: Toll-free phone (within U.S.) Outside U.S. Fax , option (United States) <[email protected]> The Motive Product Group and its parent company, Alcatel-Lucent, are interested in feedback about your experience with this product and its documentation. If you have comments or suggestions, send to <[email protected]>. xii Preface

13 Installing the MDM Server This part covers: Chapter 1, Getting Started Chapter 2, Standalone MDM Server Setup Chapter 3, MDM Cluster Setup Chapter 4, Configuration and Post-Installation Activities Chapter 5, User Management on the MDM Server Chapter 6, Troubleshooting Chapter 7, Oracle Installation and Configuration Checklist Chapter 8, BEA WebLogic Installation and Configuration Checklist Chapter 9, SMSC and Kannel Gateway Client Installation and Configuration Chapter 10, Apache Installation and Configuration Chapter 11, Sample Database Installation for Standalone Server Chapter 12, MDM Server Monitoring

14

15 This chapter covers: 1 Getting Started Standalone MDM Server installation and configuration overview MDM Cluster installation and configuration overview 3

16 This chapter introduces the installation and configuration processes for the MDM Server component of the Mobile Device Manager software suite. System Overview. Mobile Device Manager is a J2EE application that operators and mobile handset manufacturers can use to publish, store, and manage device firmware updates, and subsequently activate secure over-the-air update delivery to subscriber handsets. Motive Mobile Device Manager allows comprehensive management of subscribers, devices, and provisioning requests. Motive Mobile Device Manager supports user input in all languages supported by the UTF-8 encoding scheme. The Mobile Device Manager system capabilities are managed through the web-based MDM Console or Web Service APIs. Deployment topologies. deployment strategy. Before beginning to install and configure the Mobile Device Manager system, plan your Standalone MDM Server deployment. The MDM Server is deployed on a BEA WebLogic container installed on a single host server system. A network accessible Oracle server and database must also be configured. MDM Cluster deployment. The MDM Server is deployed on multiple hosts in the WebLogic cluster model. A network accessible Oracle server and database must also be configured. MDM Console. The MDM Console is the primary point of control for mobile operators and device manufacturers to perform over-the-air firmware updates. Through a web-based interface, operators can manage subscribers, devices, provisioning, and updates. Standalone MDM Server installation and configuration overview In a standalone MDM Server deployment, the MDM Server is deployed on a BEA WebLogic container installed on a single host server system. A network accessible Oracle server and database must also be configured. To ensure a successful installation, review the topics in this section before beginning the multi-step installation process. Host server requirements Prior to installation, verify that the machine you plan to use meets or exceeds the requirements described in Host server requirements on page 4. If you have a separate database server, it must meet the same requirements. Host server requirements MDM Server requirements Operating system Application server SMS gateway Description Solaris 10 BEA WebLogic SMSC 4 Getting Started

17 Host server requirements (continued) MDM Server requirements Database client Description Oracle Client version 10g Note The versions of the Oracle client on the Administration Server host and the Oracle server software on the database host must match. Database server Oracle 10g Enterprise Edition Note Install the Oracle server and client on the same machine if you do not have another machine hosting the Oracle server. Hard disk space (minimum required) RAM requirements Processor Access 36 GB disk space 2 GB RAM (4 GB recommended) 1 GHz UltraSparc IIIi processor (2 processors recommended) Administrative privileges required to complete these installations Network and administration requirements The person who installs the MDM Server must have system and network administration knowledge and access privileges: Knowledge of the IP address/host name and administrative privileges to the host machine where the BEA WebLogic application server and the MDM Server are installed. Knowledge of the IP address/host name and administrative privileges to the host machine(s) where Oracle is installed. Understanding of port connectivity requirements to connect to the company's data network, if required. These ports are often configured for the company s application proxy server (firewall) and/or web site security requirements. Installation prerequisites Before you install the MDM Server, ensure that the following installation requirements are met: Network and administration requirements 5

18 Oracle server. Ensure that a base Oracle server is installed and configured before the MDM Server is installed. Oracle Client. Install an Oracle client on the standalone application server system. The Oracle client should be installed before the MDM Server is installed. Refer to the Oracle product documentation for more detailed installation instructions. WebLogic Server the MDM Server is installed. A standalone BEA WebLogic application server must be installed and configured before Installation process summary This section summarizes the MDM Server installation process for the standalone server deployment topology. Before proceeding, ensure that the system requirements listed in Host server requirements on page 4 and Network and administration requirements on page 5 are met. Summary of the MDM Server installation process 1. Install and configure the Oracle server and database. 2. Install and configure the standalone application server. 3. Install the Oracle client on the application server machine. 4. Install the MDM Server. See Chapter 2, Standalone MDM Server Setup on page Install the Motive Reporting application on the MDM server. MDM Cluster installation and configuration overview Installation and configuration of the Mobile Device Manager system varies depending on the planned deployment topology. Differences are not only in the multi-step installation and configuration process, but also in the system resource (hardware, software, and network) requirements for supporting the different topologies. In an MDM Cluster deployment, the MDM Server is deployed on multiple hosts in the WebLogic cluster model. A network accessible Oracle server and database must also be configured. Review the topics in this section to ensure that you are prepared to install and configure your system before beginning this multi-step process. Host server requirements Prior to installation, verify that all machines that are part of your MDM Cluster deployment topology meet or exceed the requirements described in Cluster host server requirements on page 7. 6 Getting Started

19 System resources should be sufficient enough that products running simultaneously on the same machine(s) are not competing for the same resources. Cluster host server requirements MDM Server requirements Operating system Application server Database client Description SunOS version 5.10 WebLogic Oracle Client version 10g Note The versions of the Oracle client on the Administration Server host and the Oracle server software on the database host must match. Also ensure that the SQLLDR is installed in the bin directory where the Administration Server's Oracle client is installed. Database server Oracle 10g Enterprise Edition Note Install the Oracle server and client on the same machine if you do not have another machine hosting the Oracle server. Minimum hard disk space for MDM Administration Server host Minimum hard disk space for MDM Managed Server host RAM Access MDM Administration Server: minimum 65 MB; WebLogic: 125MB; Oracle Client: 125 MB MDM Managed Server: minimum 65 MB; WebLogic: 125MB; Oracle Client: 125 MB 2 GB recommended for Administration Server and Managed Servers Administrative privileges required to complete these installations Network and administration requirements The person who installs the MDM Server cluster must have system and network administration knowledge and access privileges: Network and administration requirements 7

20 System administrator knowledge to manage the particular application server cluster configurations. Knowledge of the IP address/host name and administrative privileges to the host machine(s) where the application server, MDM Administration Server, and MDM Managed Server are installed. Note Motive Product Group recommends that you place the MDM Administration Server and MDM Managed Servers on the same subnet. Knowledge of the IP address/host name and administrative privileges to the host machine(s) where Oracle is installed. Understanding of port connectivity requirements to connect to the company's data network, if required. These ports are often configured for the company s application proxy server (firewall) and/or web site security requirements. Installation prerequisites Before you install the MDM Server, ensure that the following installation requirements are met: Oracle server. Ensure that a base Oracle server is installed and configured before the MDM Server is installed. WebLogic Server For a cluster configuration, the WebLogic server should be installed on all the machines hosting the MDM Administration Server and the MDM Managed Servers. The WebLogic application server must be installed and configured on each machine before the MDM Administration Server and Managed Servers are installed and deployed. Oracle Client. Install an Oracle client on the machine hosting the MDM Administration Server on the clustered application server systems. Refer to the Oracle product documentation for more detailed installation instructions. Installation process summary This section summarizes the MDM installation process for the clustered server deployment topology. Before proceeding, ensure that the system requirements listed in Host server requirements on page 6 and Network and administration requirements on page 7 are met. Summary of the MDM Cluster installation process 1. Install and configure the Oracle server and database. 2. Install the Oracle client on the application server (only if the Oracle server is installed on a separate machine from the application server). 3. Install and configure the MDM Administration Server. See Chapter 3, MDM Cluster Setup on page 27 for more information. 8 Getting Started

21 4. Install and configure the MDM Managed Servers. See Chapter 3, MDM Cluster Setup on page 27 for more information. 5. Install the Motive Reporting application on at least one server in the MDM cluster. Installation process summary 9

22 10 Getting Started

23 This chapter covers: 2 Standalone MDM Server Setup MDM Server installation process overview Preparing for the installation Installing the MDM Server Starting and stopping the MDM Server 11

24 This chapter describes how to install and set up the MDM Server on a previously installed and configured BEA WebLogic application server. For details on installing and setting up the WebLogic server, see Chapter 8, BEA WebLogic Installation and Configuration Checklist on page 91 as well as the BEA WebLogic documentation. Important Before installing the MDM Server, you must install and configure a WebLogic server. Also, you must have access to an Oracle database server, and an Oracle client must be installed on the host machine. MDM Server installation process overview The MDM installation process includes the following steps: 1. Ensure system requirements are met. System and network requirements are summarized in Host server requirements on page 4. In most cases, however, these requirements should have been met before installing the BEA WebLogic application server or networked Oracle server (and thus before installing the MDM Server). 2. Prepare for the installation. See Preparing for the installation on page 12 to properly prepare for the installation. 3. Install the MDM Server. Installing the MDM Server involves running an installer and entering required configuration details. See Installing the MDM Server on page 16. Preparing for the installation To properly prepare for the MDM Server installation, perform the following tasks: Ensure that the installed BEA WebLogic application server meets or exceeds the physical hardware, software, and network requirements listed in Standalone MDM Server installation and configuration overview on page 4. Obtain the Solaris account information (a user name and password with administrative privileges) for the machine hosting the MDM Server. Review the details described in Configuration data for MDM Server installation on standalone BEA WebLogic server on page 13 and be prepared to enter accurate data configuration details relevant to your server and network configuration when installing the MDM Server. The table has a column named silent_installer.properties, which lists the corresponding property fields in the silent_installer.properties file. You can set the corresponding values in that file and use the file for silent installation. 12 Standalone MDM Server Setup

25 Configuration data for MDM Server installation on standalone BEA WebLogic server Configuration data Type of installation MDM Server installation directory Database user name Password for database user name MDM Server Oracle network information silent_installer.properties CHOSEN_INSTALL_SET USER_INSTALL_DIR dbuser dbpassword dbhost dbservice dbtnsname dbport Description Single_Server The directory where the MDM Server is to be installed. Typically, this directory is in the MDM Server user s home directory. For example: $HOME/mdmserver. The user who will be the owner of the MDM schema on the Oracle database. For example: MOTIVE. The password for the MDM schema owner the database script is to create. Network information about the configured MDM database: Note All of this Oracle database information can be found in the $ORACLE_HOME/ network/admin/ tnsnames.ora file. dbhost The Oracle host name, which is the fully qualified address of the host on which the Oracle database instance is installed. For example: db.mycompany.com. dbservice The Oracle service name, which is the network service name set up for the connection between the MDM Server host and the database instance. When using local naming, the value is defined Preparing for the installation 13

26 Configuration data for MDM Server installation on standalone BEA WebLogic server (continued) Configuration data BEA home directory WebLogic host name WebLogic ports where MDM is deployed silent_installer.properties beahome adminserverhost adminserverport adminserversslport Description in the Oracle client's tnsnames.ora file. dbtnsname The Oracle TNS name specified when Oracle was installed on the WebLogic server machine. dbport The port number where the Oracle server is running. Path to the directory where WebLogic is installed. For example: /opt/bea. The fully qualified domain name of the machine hosting the WebLogic server on which the MDM Server is deployed. Ports that allow administrative communication with the MDM Server: adminserverport The non-ssl port, which is the unsecured access port for the MDM Console. For example: User name for the WebLogic server username Password for the WebLogic server user password adminserversslport The SSL port, which is the secured access port for the MDM Console. For example: The user name used to log in to the WebLogic Server Console and perform WebLogic administrative activities. The password used to log in the WebLogic Server Console and perform WebLogic administrative activities. 14 Standalone MDM Server Setup

27 Configuration data for MDM Server installation on standalone BEA WebLogic server (continued) Configuration data External server information Java home directory Phone number format silent_installer.properties externalurlhost externalurlport externalurlsslport externalurlcontextpath javahome displaytrunkcode phonenumbermode CountryIsoCode Description The URL of the machine placed in the DMZ zone, which is used by external devices to connect to the MDM Server: externalurlhost The host name of the MDM Server. externalurlport The port number of the external host. externalurlsslport The secure port number of the external host. externalurlcontextpath The context path that is appended to the redirected URL. The directory where JDK is installed. It is preferred that you use the JDK that comes with the WebLogic installation. For example: /opt/bea/jdk150_06. Properties that specify the format in which the phone information appears. The following values are allowed: displaytrunkcode Either True or False. phonenumbermode Either single_country or multi_country. CountryIsoCode The two-digit country code of the required country. Preparing for the installation 15

28 Configuration data for MDM Server installation on standalone BEA WebLogic server (continued) Configuration data Audit logging level information JMX port number silent_installer.properties auditlogginglevel jmxport Description The level of audit information you want logged. The following values are allowed: full intermediate none The MDM server includes a client application for performing JMX monitoring. The default port number for communicating with JMX is 1100, but if the system you are installing on already has a service using port 1100, then select a different port number. Installing the MDM Server Before installing the MDM Server, you must install and configure a standalone BEA WebLogic application server. Also, you must have access to an Oracle database server. The MDM Server has three modes of installation: GUI installation. An XWindows-based installation using a graphical user interface. Console installation. A command-line based installation. Silent installation. An installation that runs in the background once it is initiated and uses a properties file for its input. A silent installation is useful for remote and mass installation. To install the MDM Server from the GUI 1. Using an XWindows-based emulation application (such as XWin32), log in to the preconfigured standalone BEA WebLogic server machine as the Solaris user created for the MDM Server installation (for example, motive ). Important Logging in to the server is done from a Windows machine. GUI installation directly on the Solaris server is not tested yet. For a direct installation, use the console installation process. Do not run the installation as the root user, but ensure that the user created for the installation has administrative privileges. This is the accepted best practice on Solaris machines for security reasons. 16 Standalone MDM Server Setup

29 2. Launch the GUI MDM Server installation program:./mobiledevicemanager_installer.bin -i GUI Note The installer needs to have executable permissions set. If the installer does not start, run the command chmod +x MobileDeviceManager_Installer.bin and then run the installer. Click Next. Note The MDM Server version to be installed appears in the title of the Welcome screen. Once installed, this information is available in the About area of the MDM Console. 3. The License Agreement screen appears. Review the agreement, then select I accept the terms of the License Agreement, and then click Next. 4. The Install Set screen appears. Select the Single Standalone Server option. 5. The Installation Directory screen appears. Enter the path to the directory where the MDM Server is installed. For example: /opt/mdmsingleserver. 6. The BEA Home Directory screen appears. Enter the path to the directory where WebLogic is installed. For example: /opt/bea 7. The Java Home Directory screen appears. Enter the path to the directory where JDK is installed. It is recommended that you use the JDK that comes with the WebLogic installation. For example: /opt/bea/jdk150_06 8. The Oracle Information screen appears. Enter appropriate values in the data fields as described in Configuration data for MDM Server installation on standalone BEA WebLogic server on page 13. Click Next. 9. The WebLogic Server Information screen appears. Enter appropriate values in the data fields as described in Configuration data for MDM Server installation on standalone BEA WebLogic server on page 13. Click Next. 10. The Phone Service Provider Information screen appears: Display Trunk Code. Specify whether to display the trunk code in the MDM Console. Phone Number Mode. Specify whether the tenant supports subscribers in a single country or multiple countries. If you select Single Country for the Phone Number Mode, go to step 9. Otherwise, go to step The Get Phone Country ISO Code Information screen appears. Enter the ISO code for the single country phone number mode setting. Installing the MDM Server 17

30 These codes can be found at the following site: 02iso-3166-code-lists/list-en1.html 12. The Get Audit Logging Level Information screen appears. Specify one of the following audit logging levels: full. All the actions declared in the src/auditlogging/sspauditlogging.xml file are logged. intermediate. An action is logged only if the value of the tag in the SSPAuditLogging.xml file is optional and the action is false. none. None of the actions are logged. The information in the log files corresponds to actions available in the MDM Console. 13. The Standalone Server specific information screen appears. Enter the JMX port and click Next. The JMX port is the RMI registry port for connecting to the JMX agent. The MDM server includes a client application for performing JMX monitoring. The default port number for communicating with JMX is 1100, but if the system you are installing on already has a service using port 1100, then select a different port number. 14. The External facing URL information screen appears. Enter appropriate values in the data fields as described in Configuration data for MDM Server installation on standalone BEA WebLogic server on page 13, then click Next to continue. 15. The Summary (Single Server) screen appears, showing all the data configuration values entered in previous screens. Review this screen carefully, and ensure that the values are accurate. Click Install to continue. 16. The Installing Mobile Device Manager progress screen appears as files are copied to the host server and installed. When the installation is complete, an Install Complete screen appears. Click Done to quit the installer. 17. After a successful installation, go to Chapter 4, Configuration and Post-Installation Activities on page 53. To install the MDM Server from the console 1. Log in to the preconfigured standalone BEA WebLogic application server machine as the Solaris user created for the MDM Server installation (for example, motive). Caution Do not run the installation as the root user, but ensure that the user created for the installation has administrative privileges. This is the accepted best practice on Solaris machines for security reasons. 18 Standalone MDM Server Setup

31 2. Make sure the installation.bin file is executable; if necessary, run the following command to make it executable:chmod +x./mobiledevicemanager_installer.bin. 3. Change your working directory to the one containing the installer executable. Launch the console MDM Server installation program by using the command./mobiledevicemanager_installer.bin. You should see the following output on the console: bash-3.00#./mobiledevicemanager_installer_1_1_0_190_ bin Preparing to install... Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... Launching installer... Preparing CONSOLE Mode Installation... =============================================================================== Mobile Device Management Server 1.1.0(created with InstallAnywhere by Macrovision) =============================================================================== Welcome The Mobile Device Management Installer guides you through the installation and configuration of your Mobile Device Management Server. It is strongly recommended that you quit all programs before continuing with this installation. You may cancel this installation at any time by clicking the 'Cancel' button. Click the 'Next' button to proceed to the next screen. PRESS <ENTER> TO CONTINUE: Press ENTER. 4. The License Acceptance information appears: =============================================================================== License Acceptance (license text omitted here) ->1- Agree 2- Disagree Installing the MDM Server 19

32 ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT: Review the agreement. If you agree with the license terms, press ENTER to accept the default of The Choose Install Set output appears on the console: =============================================================================== Choose Install Set Please choose the Install Set to be installed by this installer. ->1- Single Standalone Server 2- Administration Server for Cluster 3- Managed Server for Cluster ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS <ENTER> TO ACCEPT THE DEFAULT : 2 Enter 2 to install the MDM Administration server. 6. The Installation Directory output appears on the console: =============================================================================== Installation Directory Where would you like to install Standalone Server? Default Install Folder: /DMSuite ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT : /opt/mdm INSTALL FOLDER IS: /opt/mdm IS THIS CORRECT? (Y/N): y Enter the path to the directory where the MDM Server is to be installed, for example: /opt/mdmsingleserver. Press ENTER. 7. The BEA Home Directory output appears on the screen. Enter the BEA home directory. For example: /opt/bea. 8. The Oracle Information - Username output appears on the console. Enter appropriate values in the Enter DM Suite Oracle username: field as described in Configuration data for MDM Server installation on standalone BEA WebLogic server on page 13. Press ENTER when done. You are prompted to enter the password for the Oracle user name you provided. Enter the password and press ENTER. You are prompted to confirm the password. Enter the password again and press ENTER. You are prompted to enter the Hostname/IP address of the machine hosting the Oracle database server. Enter the value and press ENTER. You are prompted to provide the port number for the Oracle database. Enter the port number and press ENTER. 20 Standalone MDM Server Setup

33 Enter the Oracle service name and TNS name as you are prompted for them. 9. The JDK Home Directory output appears on the screen. Enter the JDK home directory. For example: /opt/bea/jdk150_ The Hostname output appears on the screen. Enter the host name of the machine hosting the BEA WebLogic application server. Enter the port number and press ENTER. The WebLogic non-ssl Port output appears on the screen. Enter the non-ssl port number and press ENTER. The WebLogic SSL Port output appears on the screen. Enter the SSL port number and press ENTER. The DM Suite Server External IP Address output appears on the screen. Enter the IP address of the proxy server you are using and press ENTER 11. The Phone Display - Trunk Code Option output appears on the screen. Enter 1 if you want the trunk code to be displayed on the phone; otherwise, enter 2. Press ENTER. The Phone Display - Single/Multi Country Code output appears on the screen. Enter 1 if you want a single country code to be used; otherwise, enter 2 for multiple country codes. Press ENTER. The Phone Display - Country ISO Code output appears on the screen. Enter the ISO code of the country you are in and press ENTER. 12. The Get Audit Logging Level output appears on the screen. Enter 1 if you do not want any audit information to be logged. Enter 2 if you want an intermediate level of audit information to be logged. Enter 3 if you want high-level audit information to be logged. Press ENTER. 13. The External facing URL Host information output appears on the screen. Enter the fully qualified domain name of the external facing host, and press ENTER. 14. The External facing URL non-ssl port output appears on the screen. Enter the non-ssl port number for the external facing host, and press ENTER. 15. The External facing URL ssl port output appears on the screen. Enter the SSL port number of the external facing host and press ENTER. 16. The External facing URL context path output appears on the screen. Enter the context path to be appended to the redirected URL, and press ENTER. For example: /omadm/omadm. 17. The Current Parameters output appears on the screen. Review the information that you have provided so far, and press ENTER to start the installation process. Installing the MDM Server 21

34 18. The Installation Complete output appears on the screen. Press ENTER to exit the installer. 19. After the installation is successful, go to Chapter 4, Configuration and Post-Installation Activities on page 53. To perform a silent installation 1. Log in to the preconfigured standalone BEA WebLogic application server machine as the Solaris user created for the MDM Server installation (for example, motive ). Note Do not run the installation as the root user, but ensure that the user created for the installation has administrative privileges. This is the accepted best practice on Solaris machines for security reasons. 2. To perform a silent installation, you must set up a silent_installer.properties file. This properties file has all the relevant information required for the installation wizard to install the MDM Administration Server. To create a silent_installer.properties file, use an installer.properties file generated from a prior installation (in the /temp directory) as a starting point, or get a sample silent_installer.properties file from the product distribution. Edit the following sample silent_installer.properties file with a simple text editor, and replace the sample values with the required values. # This indicates the type of installation, allowed values are: Admin_Server/ Managed_Server/Single_Server. #If you comment out CHOSEN_INSTALL_SET standalone single server will be created by default. CHOSEN_INSTALL_SET=Single_Server #Do not change this value. This is the default installation mode. INSTALLER_UI=silent # Directory where the MDM server is installed. # USER_INSTALL_DIR=/opt/scandium/manageserver #Specify the folder where Weblogic 9.2 is installed. The default value is provided below. beahome =/opt/bea #Specify the folder where JDK is installed. It is preferred that you use the JDK that is provided with the Weblogic 9.2 installation. javahome =/opt/bea/jdk150_06 # # Cluster information required only for admin server installation. # multicastaddress= multicastport=234 # 22 Standalone MDM Server Setup

35 # Admin server information for cluster deployment or single server information for standalone deployment. # adminserverport =7001 adminserverhost =niobium.idc.devlab.motive.com adminserversslport =7002 username =weblogic password =weblogic # # The port where Node manager is running. This is required only for the Managed Server in a clustered deployment. # nodemanagerport=5556 # # Manage server information # managedserverhost=scandium.idc.devlab.motive.com managedserverport=7001 managedserversslport=7002 # # Database information. This is required for Admin server or Single server deployment. # dbhost= dbport=1521 dbservice=mdm dbuser =motive_mdm dbpassword =motive dbtnsname =tnsname # MDM Server specific information. The values provided below are the default values. Set the required values from the specified values. This is required for Admin server or Single server deployment. #multi-country/single-country phonenumbermode =single-country # specify true/false displaytrunkcode =false #Provide the country code below. The default value provided below is for INDIA. countryisocode =IN # specify full/intermediate/none auditlogginglevel =intermediate #External url information which is sent to device while bootstrap for communication with MDM server. externalurlhost= externalurlport= externalurlsslport= externalurlcontextpath= # JMX monitoring information applicable for single server and manage server Installing the MDM Server 23

36 jmxport= Change your working directory to the one containing the installer executable. Launch the silent MDM Server installation program by using the following command:./mobiledevicemanager_installer.bin -i silent -f Path-to-silent_installer.properties. Press ENTER to start the installation process. Note The silent installation does not show any status on the console after the installation is complete. Verify that the Mobile_Device_Management_Server_InstallLog.log is generated, and confirm successful installation from the logs. The log files are err.properties, script.log, and wslt.log. They are in the MDMAdmin-Installation-directory/temp directory. 4. Then complete the steps in Chapter 4, Configuration and Post-Installation Activities on page 53 Starting and stopping the MDM Server To start the MDM Server 1. Open a command shell, and change the directory to the DM Server installation directory. 2. Run the command:./startdmserver.sh To stop the MDM Server 1. Open a web browser window and log in to the WebLogic Server Console: Note Use the same user name and password provided when installing the MDM Server. 2. In the main pane, click on Servers in the Environment list in the Domain Configurations area. 3. In the Summary of Servers window, the MDM Server is listed in the Name column in the Servers table. Click the server name to access the Settings for managed- server-name window. 4. Click the Control tab, then click the Start/Stop tab. You have the option of forcing an immediate shutdown by using Shutdown->Force Shutdown Now, or requesting a shutdown after it completes all the jobs by using Shutdown->when work completes. The State of the machine should indicate STOPPED. 24 Standalone MDM Server Setup

37 To stop/start the MDM application from the WebLogic Server Console 1. Open a web browser window and log in to the WebLogic Server Console: Note Use the same user name and password provided when installing the MDM Server. 2. In the Domain Structure panel on the left, click on Deployments. 3. In the Summary of Deployments window on the right, the MDM application Viper is listed in Deployments. 4. Click the check box to select the application. 5. To start the application: To start the application and service all requests, select Servicing all requests from the Start menu. To start the application and service only administrative requests, select Servicing only administration requests from the Start menu. Click Yes in the Start Application Assistant window. The State of the application should indicate Active. 6. To stop the application: To stop the application after it completes all pending requests, select When work completes from the Stop menu. To stop the application immediately, select Force Stop Now from the Start menu. To stop the application but continue servicing administrative requests, select Stop, but continue servicing administration requests from the Stop menu. Click Yes in the Stop Application Assistant window. The State of the application should indicate Stopped. Starting and stopping the MDM Server 25

38 26 Standalone MDM Server Setup

39 This chapter covers: 3 MDM Cluster Setup MDM Cluster installation process overview Preparing for the installation Installing the MDM Cluster Starting and stopping the cluster Updating the MDM Cluster Uninstalling the Managed Server 27

40 This chapter describes how to install and set up the MDM Cluster. As part of the cluster deployment, you install the MDM Administration Server and the MDM Managed Server. For details on installing and setting up the BEA WebLogic application server on each cluster machine, see Chapter 8, BEA WebLogic Installation and Configuration Checklist on page 91 as well as BEA WebLogic documentation. Important Before installing the MDM Server on each host, you must install and configure a WebLogic server on it. Also, you must have access to an Oracle database server. MDM Cluster installation process overview The MDM Cluster installation process includes the following steps: 1. Ensure system requirements are met. System and network requirements are summarized in Cluster host server requirements on page Prepare for the installation. See Preparing for the installation on page 28 to properly prepare for the installation. 3. Install the MDM Cluster. See Installing the MDM Cluster on page 32 for details on installing the MDM Administration Server and the MDM Managed Servers. Preparing for the installation To properly prepare for the MDM Cluster installation, perform the following tasks: Ensure that the installed BEA WebLogic application server meets or exceeds the physical hardware, software, and network requirements listed in MDM Cluster installation and configuration overview on page 6. Obtain the Solaris account information (user name and password) created on the BEA WebLogic application server for the MDM Server. Review the details described in Configuration data for MDM Server installation on clustered WebLogic Server on page 28 and be prepared to enter accurate data configuration details relevant to your server and network configuration when installing the MDM Server. The table has a column named silent_installer.properties, which lists the corresponding property fields in the silent_installer.properties file. You can edit the properties and use the file for silent installation. Configuration data for MDM Server installation on clustered WebLogic Server Configuration Data Type of installation silent_installer.properties CHOSEN_INSTALL_SET Description Admin server or Managed server. 28 MDM Cluster Setup

41 Configuration data for MDM Server installation on clustered WebLogic Server (continued) Configuration Data MDM Server installation directory Database user name Password for the database user name MDM Server Oracle network information silent_installer.properties USER_INSTALL_DIR dbuser dbpassword dbhost dbservice dbtnsname dbport Description The directory where the MDM Server is to be installed. For example: /opt/ mdmserver. The user who will be the owner of the MDM schema on the Oracle database. For example: MOTIVE. The password for the MDM schema owner the database script is to create. Network information about the configured MDM database: Note All of this Oracle database information can be found in the $ORACLE_HOME/ network/admin/ tnsnames.orafile. dbhost The Oracle host name, which is the fully qualified address of the host on which the Oracle database instance is installed. For example: db.mycompany.com. dbservice The Oracle service name, which is the network service name set up for the connection between the MDM Server host and the database instance. When using local naming, the value is defined in the Oracle client's tnsnames.ora file. Preparing for the installation 29

42 Configuration data for MDM Server installation on clustered WebLogic Server (continued) Configuration Data BEA home directory WebLogic host name WebLogic ports where MDM Administration Server is deployed Administrative user name for the WebLogic Administration Server Password for the WebLogic Administration Server user Administration Server information silent_installer.properties beahome adminserverhost adminserverport adminserversslport username password adminserverhost adminserverport adminserversslport adminserverusername adminserverpassword Description dbtnsname The Oracle TNS name specified when Oracle was installed on the WebLogic server machine. dbport The port number where the Oracle server is running. Path to the directory where WebLogic is installed. For example: /opt/bea. The fully qualified domain name of the machine hosting the WebLogic server on which the MDM Server is deployed. Ports that allow administrative communication with the MDM Server: adminserverport The non-ssl port, which is the unsecured access port for the MDM Console. For example: adminserversslport The SSL port, which is the secured access port for the MDM Console. For example: The user name used to log in to the WebLogic Server Console and perform WebLogic administrative activities. The password used to log in to the WebLogic Server Console and perform WebLogic administrative activities. The host name of the Administration Server, the port number, the secure port number, the admin user name, and the corresponding password. 30 MDM Cluster Setup

43 Configuration data for MDM Server installation on clustered WebLogic Server (continued) Configuration Data Cluster information for Administration Server Managed Server External facing URL information Java home directory silent_installer.properties Multicast Address Multicast Port managedserverhost managedserverport managedserversslport managedserverusername managedserverpassword nodemanagerport externalurlhost externalurlport externalurlsslport externalurlcontextpath javahome Description The password used to log in to the WebLogic Server Console and perform WebLogic administrative activities. The host name of the Administration Server, the port number, the secure port number, the admin user name of the Managed Server, the corresponding password, and the port number of the node manager. The externally available IP address for the MDM Server. Note In a clustered environment, this IP address is the URL of the load balancer. externalurlhost The external host name of the MDM Server. externalurlport The port number of the external host. externalurlsslport The secure port number of the external host. externalurlcontextpath The context path that is appended to the redirected URL. The directory where JDK is installed. It is preferred that you use the JDK that comes with the WebLogic installation. For example: /opt/bea/jdk150_06. Preparing for the installation 31

44 Configuration data for MDM Server installation on clustered WebLogic Server (continued) Configuration Data Phone number format Audit logging level information JMX port number silent_installer.properties displaytrunkcode phonenumbermode CountryIsoCode auditlogginglevel jmxport Description Properties that specify the format in which the phone information appears. The following values are allowed: displaytrunkcode Either True or False. phonenumbermode Either single_country or multi_country. CountryIsoCode The two-digit country code of the required country. The level of audit information you want logged. The following values are allowed: full intermediate none The MDM server includes a client application for performing JMX monitoring. The default port number for communicating with JMX is 1100, but if the system you are installing on already has a service using port 1100, then select a different port number. Installing the MDM Cluster Installing the MDM Administration Server Note Before installing the MDM Server, you must install and configure a BEA WebLogic application server. Also, you must have access to an Oracle database server. 32 MDM Cluster Setup

45 The MDM Administration Server has three modes of installation: GUI installation. An XWindows-based installation using a graphical user interface. Console installation. A command-line based installation. Silent installation. An installation that runs in the background once it is initiated and uses a properties file for its input. A silent installation useful for remote and mass installation. To install the MDM Administration Server from the GUI 1. Using an XWindows-based emulation application (such as XWin32), log in to the preconfigured standalone BEA WebLogic application server as the Solaris user created for the MDM Server installation (for example, motive ). Important Logging in to the server is done from a Windows machine. GUI installation directly on the Solaris server is not tested yet. For a direct installation, use the console installation process. Do not run the installation as the root user, but ensure that the user created for the installation has administrative privileges. This is the accepted best practice on Solaris machines for security reasons. 2. Launch the GUI MDM Server installation program:./mobiledevicemanager_installer.bin -i GUI. Note The installer program needs to have executable permissions set. If the installer does not start up, run the command Chmod +x MobileDeviceManager_Installer.bin and then run the installer. Click Next. Note The MDM Server version to be installed appears on the Welcome screen. Once installed, this information is available in the About area of the MDM Console. 3. The License Agreement screen appears. Review the agreement, then select I accept the terms of the License Agreement, then click Next. 4. The Install Set screen appears. Select the Administration Server For Cluster option. 5. The Installation Directory screen appears. Enter the path to the directory where the MDM Server is installed. For example: /opt/mdmmanagedserver. 6. The BEA Home Directory screen appears. Enter the path to the directory where WebLogic is installed. For example: /opt/bea. Installing the MDM Administration Server 33

46 7. The Java Home Directory screen appears. Enter the path to the directory where JDK is installed. It is recommended that you use the JDK that comes with the WebLogic installation. Example: /opt/bea/jdk150_ The Oracle Information screen appears. Enter appropriate values in the data fields as described in Configuration data for MDM Server installation on clustered WebLogic Server on page 28. Click Next. 9. The WebLogic Server Information screen appears. Enter appropriate values in the data fields as described in Configuration data for MDM Server installation on clustered WebLogic Server on page 28. Click Next. 10. The Phone Service Provider Information screen appears. Select from among the following options: Display Trunk Code. Specify whether to display the trunk code in the MDM Console. Phone Number Mode. Specify whether the tenant supports subscribers in a single country or multiple countries. Country ISO Code. Enter the ISO code for the default country phone number mode setting. For example, the country code for the United States is US. The country codes can be found at the following site: iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html. 11. The Get Audit Logging Level Information screen appears. Specify one of the following audit logging levels: full. All the actions declared in the src/auditlogging/sspauditlogging.xml file are logged. intermediate. An action is logged only if the value of the tag in the SSPAuditLogging.xml file is optional and the action is false. none. None of the actions are logged. The information in the log files corresponds to actions available in the MDM Console. 12. The Cluster Information screen appears. 13. The External facing URL information screen appears. Provide the required values. Enter appropriate values in the data fields as described in Configuration data for MDM Server installation on clustered WebLogic Server on page 28, then click Next to continue. 14. The Summary (Admin Server) screen appears, showing all the data configuration values entered in previous screens. Review this screen carefully, and ensure that the values are accurate. Click Install to continue. 15. The Installing Mobile Device Manager progress screen appears as files are copied to the host server and installed. 34 MDM Cluster Setup

47 When the installation is complete, an Install Complete screen appears. Click Done to quit the installer. 16. After a successful installation, go to Chapter 4, Configuration and Post-Installation Activities on page 53 To install the MDM Administration Server from the console 1. Log in to the preconfigured WebLogic Administration Server machine as the Solaris user created for the MDM Server installation (for example, motive ). Caution Do not run the installation as the root user, but ensure that the user created for the installation has administrative privileges. This is the accepted best practice on Solaris machines for security reasons. 2. Make sure the installation.bin file is executable; if necessary, run the following command to make it executable:chmod +x./mobiledevicemanager_installer.bin. 3. Change your working directory to the one containing the installer executable. Launch the console MDM Server installation program by using the command./mobiledevicemanager_installer.bin. You should see the following output on the console: Preparing to install... Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... Launching installer... Preparing CONSOLE Mode Installation... =============================================================================== Mobile Device Management Server 1.00(created with InstallAnywhere by Macrovision) =============================================================================== Welcome The Mobile Device Management Installer guides you through the installation and configuration of your Mobile Device Management Server. It is strongly recommended that you quit all programs before continuing with this installation. You may cancel this installation at any time by clicking the 'Cancel' button. Click the 'Next' button to proceed to the next screen. PRESS <ENTER> TO CONTINUE: Press ENTER. 4. The License Acceptance information appears. =============================================================================== License Acceptance Installing the MDM Administration Server 35

48 (license text omitted here) ->1- Agree 2- Disagree ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT: 1 ->1- Agree 2- Disagree ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT: Review the agreement. If you agree with the license terms, press ENTER to accept the default of The Choose Install Set output appears on the console: =============================================================================== Choose Install Set Please choose the Install Set to be installed by this installer. ->1- Single Standalone Server 2- Administration Server for Cluster 3- Managed Server for Cluster ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS <ENTER> TO ACCEPT THE DEFAULT : 2 Enter 2 to install the MDM Administration server. 6. The Installation Directory output appears on the console: =============================================================================== Installation Directory Where would you like to install the selected MDM server? Default Install Folder: /DMSuite ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT : /opt/mdmadminserver INSTALL FOLDER IS: /opt/mdmadminserver IS THIS CORRECT? (Y/N): Enter the path to the directory where the MDM Administration server is to be installed (for example: /opt/mdmadminserver). Press ENTER. 7. The BEA Home Directory output appears on the screen. Enter the BEA home directory. For example: /opt/bea. 8. The JDK Home Directory output appears on the screen. Enter the JDK home directory. For example: /opt/bea/jdk150_ MDM Cluster Setup

49 9. The Oracle Information - Username output appears on the console. Enter the MDM schema user name in the Username : (DEFAULT: ): field as described in Configuration data for MDM Server installation on clustered WebLogic Server on page 28. Press ENTER when done. a. You are prompted to enter the password for the Oracle user name you provided. Enter the password and press ENTER. You are prompted to confirm the password. Enter the password again and press ENTER. b. You are prompted to enter the Hostname/IP address of the machine hosting the Oracle database server. Enter the value and press ENTER. c. You are prompted to provide the port number for the Oracle database. Enter the port number and press ENTER. d. Enter the Oracle service name and Oracle TNS name when you are prompted for them. e. The Enter the name of the machine hosting the MDM Server output appears on the screen. Enter the host name of the machine hosting the MDM Administration Server, and press ENTER. f. The non-ssl Port output appears on the screen. Enter the non-ssl port number, and press ENTER. g. The SSL Port output appears on the screen. Enter the SSL port number, and press ENTER. h. The User name output appears on the screen. Enter the WebLogic user name, and press ENTER. i. The Password output appears on the screen. Enter the WebLogic password, and press ENTER. 10. The Phone Display - Trunk Code Option output appears on the screen. Enter 1 if you want the trunk code to be displayed on the phone; otherwise, enter 2, and press ENTER. The Phone Display - Single/Multi Country Code output appears on the screen. Enter 1 if you want a single country code to be used; otherwise, enter 2 for multiple country codes, and press ENTER The Phone Display - Country ISO Code output appears on the screen. Enter the ISO code of the country, and press ENTER. 11. The Get Audit Logging Level output appears on the screen. Enter 1 if you do not want any audit information to be logged. Enter 2 if you want an intermediate level of audit information to be logged. Enter 3 if you want high-level audit information to be logged. Press ENTER. 12. The server-specific information output appears on the screen. Enter the JMX port and press ENTER. The JMX port is the RMI registry port for connecting to the JMX agent. Installing the MDM Administration Server 37

50 The MDM server includes a client application for performing JMX monitoring. The default port number for communicating with JMX is 1100, but if the system you are installing on already has a service using port 1100, then select a different port number. 13. The Multicast address output appears on the screen. Enter the multicast address, and press ENTER. For example: The Multicast address is the address for the group of hosts that are to be addressed by multicast messages. For more information on multicasting, see Configuring multicasting on page The External facing URL Host information output appears on the screen. Enter the fully qualified domain name of the external facing host, and press ENTER. 15. The External facing URL non-ssl port output appears on the screen. Enter the non-ssl port number for the external facing host, and press ENTER. 16. The External facing URL ssl port output appears on the screen. Enter the SSL port number of the external facing host and press ENTER. 17. The External facing URL context path output appears on the screen. Enter the context path to be appended to the redirected URL, and press ENTER. For example: /omadm/omadm. 18. The Current Parameters output appears on the screen. Review the information that you have provided so far, and press ENTER to start the installation process. 19. The Installation Complete output appears on the screen. Press ENTER to exit the installer. To perform a silent installation 1. To perform a silent installation, you must set up the silent_installer.properties file. This properties file has all the relevant information required for the installation wizard to install the MDM Administration Server. Edit the following sample silent_installer.properties file with a simple text editor, and replace the sample values with the required values. # This indicates the type of installation, allowed values are: Admin_Server/ Managed_Server/Single_Server. #If you comment out CHOSEN_INSTALL_SET standalone single server will be created by default. CHOSEN_INSTALL_SET=Admin_Server #Do not change this value. This is the default installation mode. INSTALLER_UI=silent # Directory where the MDM server is installed. # USER_INSTALL_DIR=/opt/scandium/manageserver #Specify the folder where Weblogic 9.2 is installed. The default value is provided below. 38 MDM Cluster Setup

51 beahome =/opt/bea #Specify the folder where JDK is installed. It is preferred that you use the JDK that is provided with the Weblogic 9.2 installation. javahome =/opt/bea/jdk150_06 # # Cluster information required only for admin server installation. # multicastaddress= multicastport=234 # # Admin server information for cluster deployment or single server information for standalone deployment. # adminserverport =7001 adminserverhost =niobium.idc.devlab.motive.com adminserversslport =7002 username =weblogic password =weblogic # # The port where Node manager is running. This is required only for the Managed server in a clustered deployment. # nodemanagerport=5556 # # Manage server information # managedserverhost=scandium.idc.devlab.motive.com managedserverport=7001 managedserversslport=7002 # # Database information. This is required for Admin server or Single server deployment. # dbhost= dbport=1521 dbservice=mdm dbuser =motive_mdm dbpassword =motive dbtnsname =tnsname # MDM Server specific information. The values provided below are the default values. Set the required values from the specified values. This is required for Admin server or Single server deployment. #multi-country/single-country phonenumbermode =single-country # specify true/false displaytrunkcode =false #Provide the country code below. The default value provided below is for INDIA. countryisocode =IN Installing the MDM Administration Server 39

52 # specify full/intermediate/none auditlogginglevel =intermediate #External url information which is sent to device while bootstrap for communication with MDM server. externalurlhost= externalurlport= externalurlsslport= externalurlcontextpath= # JMX monitoring information applicable for single server and manage server jmxport= Change your working directory to the one containing the installer executable. Launch the silent MDM Server installation program by using the following command:./mobiledevicemanager_installer.bin -i silent -f Path-to-silent_installer.properties. Press ENTER to start the installation process. Note The silent installation does not show any status on the console after the installation is complete. Verify that the Mobile_Device_Management_Server_InstallLog.log is generated, and confirm successful installation from the logs. The log files are err.properties, script.log, and wslt.log. They are in the MDMAdmin-Installation-directory/temp directory. Installing the MDM Managed Server The MDM Managed Server has three modes of installation: GUI installation. An XWindows-based installation using a graphical user interface. Console installation. A command-line based installation. Silent installation. An installation that runs in the background once it is initiated and uses a properties file for its input. A silent installation is useful for remote and mass installation. Note Before you install the MDM Managed Server, ensure the following: The Administration Server must be installed, configured, and running for successful installation of the Managed Server. The node manager is not running. 40 MDM Cluster Setup

53 To install the Managed Server from the GUI 1. Using an XWindows-based emulation application (such as XWin32), log in to the preconfigured BEA WebLogic application server as the Solaris user created for the MDM Server installation (for example, motive ). Important Logging in to the server is done from a Windows machine. GUI installation directly on the Solaris server is not tested yet. For a direct installation, use the console installation process. Do not run the installation as the root user, but ensure that the user created for the installation has administrative privileges. This is the accepted best practice on Solaris machines for security reasons. 2. Launch the GUI MDM Server installation program:./mobiledevicemanager_installer.bin -i GUI. Note The installer program needs to have executable permissions set. If the installer does not start up, run the command Chmod +x MobileDeviceManager_Installer.bin and then run the installer. Click Next. Note The MDM Server version to be installed appears on the Welcome screen. Once installed, this information is available in the About area of the MDM Console. 3. The License Agreement screen appears. Review the agreement, then select I accept the terms of the License Agreement, then click Next. 4. The Install Set screen appears. Select the Managed Server For Cluster option. 5. The Installation Directory screen appears. Enter the path to the directory where the MDM Server is installed. Typically, this directory is in the MDM Server user s home directory. For example, if the user name is motive, then the installation directory is /opt/mdmadmin. 6. The BEA Home Directory screen appears. Enter the path to the directory where WebLogic is installed. Typically, WebLogic is installed in /opt/bea. 7. The Java Home Directory screen appears. Enter the path to the directory where JDK is installed. It is recommended that you use the JDK that comes with the WebLogic installation. Example: /opt/bea/jdk150_ The WebLogic Managed Server Information screen appears. Enter appropriate values in the fields as described in Configuration data for MDM Server installation on clustered WebLogic Server on page 28. Click Next.. Installing the MDM Managed Server 41

54 9. The Node Manager Settings screen appears. Enter the port number where the Node manager is running, as described in Configuration data for MDM Server installation on clustered WebLogic Server on page 28. Click Next. 10. The Admin Server information screen appears. Enter the Administration Server details as described in Configuration data for MDM Server installation on clustered WebLogic Server on page 28. Click Next. 11. The Managed Server specific information screen appears. Enter the JMX port and click Next. The JMX port is the RMI registry port for connecting to the JMX agent. The MDM server includes a client application for performing JMX monitoring. The default port number for communicating with JMX is 1100, but if the system you are installing on already has a service using port 1100, then select a different port number. 12. The Summary (Managed Server) screen appears, showing all the data configuration values entered in previous screens. Review this screen carefully, and ensure that the values are accurate. Click Install to continue. 13. The Installing Mobile Device Manager progress screen appears, as files are copied to the host server and installed. When the installation is complete, an Install Complete screen appears. Click Done to quit the installer. 14. After a successful installation, go to Chapter 4, Configuration and Post-Installation Activities on page 53. To install the Managed Server from the console 1. Log in to the preconfigured BE WebLogic server machine as the Solaris user created for the MDM Server installation (for example, motive ). Important Do not run the installation as the root user, but ensure that the user created for the installation has administrative privileges. This is the accepted best practice on Solaris machines for security reasons. 2. Change your working directory to the one containing the installer executable. Launch the console MDM Server installation program by using the command./mobiledevicemanager_installer.bin. If you are unable to launch the installer, then run the following command before launching the installer: Chmod +x MobileDeviceManager_Installer.bin. To generate the silent_installer.properties file for use in a silent installation, use the command./mobiledevicemanager_installer.bin -r. The silent_installer.properties file is generated in the same directory. You should see the following output on the console: 42 MDM Cluster Setup

55 Preparing to install... Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... Launching installer... Preparing CONSOLE Mode Installation... =============================================================================== Mobile Device Management Server 1.00(created with InstallAnywhere by Macrovision) =============================================================================== Welcome The Mobile Device Management Installer guides you through the installation and configuration of your Mobile Device Management Server. It is strongly recommended that you quit all programs before continuing with this installation. You may cancel this installation at any time by clicking the 'Cancel' button. Click the 'Next' button to proceed to the next screen. PRESS <ENTER> TO CONTINUE: Press ENTER. 3. The License Acceptance output appears: =============================================================================== License Acceptance Copyright 2007, Motive Communications This software is the intellectual property of Motive and/or its licensors. You may not use this software for any purpose other than those indicated in the applicable software license between yourself and Motive. Other than as permitted under the Software License, you may not: - disclose this software code to a third party - copy the software, except as per license or with prior written permission from Motive Motive Communications specifically retains title to and interest in all Motive software. The Device Management Suite Software is furnished under a license and all use of this software product is strictly limited by its terms. The software may only be installed, used or copied in accordance with the terms of the license. Some or all of this work is covered by patent and/or copyright laws in the US, UK and other countries. If You have a license with Motive for the Device Management Suite Software, check Agree to continue. If You do not have a license with Motive for the Device Management Suite Installing the MDM Managed Server 43

56 Software, check Disagree. The install will cease. Contact Motive for an applicable license. ->1- Agree 2- Disagree ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT: 1 ->1- Agree 2- Disagree ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT: Review the agreement. If you agree with the license terms, press ENTER to accept the default of The Choose Install Set output appears on the console: =============================================================================== Choose Install Set Please choose the Install Set to be installed by this installer. ->1- Single Standalone Server 2- Adminstration Server for Cluster 3- Managed Server for Cluster ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS <ENTER> TO ACCEPT THE DEFAULT : 3 Enter 3 to install the MDM Managed server. 5. The Installation Directory output appears on the console: =============================================================================== Installation Directory Where would you like to install the selected MDM server? Default Install Folder: /DMSuite ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT : /opt/mdmmanagedserver INSTALL FOLDER IS: /opt/mdmmanagedserver IS THIS CORRECT? (Y/N): Enter the path to the directory where the MDM Managed Server is to be installed (for example, /opt/mdmmanagedserver). Press ENTER. 6. The BEA Home Directory output appears on the screen. Enter the BEA home directory. For example: /opt/bea. 7. The JDK Home Directory output appears on the screen. Enter the JDK home directory. For example: /opt/bea/jdk150_ MDM Cluster Setup

57 8. The Enter the name of the machine hosting the MDM Server output appears on the screen. Enter the host name of the machine hosting the MDM Administration Server. Press ENTER. The non-ssl Port output appears on the screen. Enter the non-ssl port number, and press ENTER. The SSL Port output appears on the screen. Enter the SSL port number, and press ENTER. The User name output appears on the screen. Enter the WebLogic admin user name, and press ENTER. The Password output appears on the screen. Enter the WebLogic admin password and press ENTER. 9. The Node Manager Port output appears on the screen. Enter the port where the node manager is active. 10. The User name output appears on the screen. Enter the user name for the Administration Server, and press ENTER. The Password output appears on the screen. Enter the password for the Administration Server user, and press ENTER. The Admin server host output appears on the screen. Enter the host name of the machine hosting the MDM Administration Server, and press ENTER. The Admin server port output appears on the screen. Enter the port number where the Administration Server is active, and press ENTER. The SSL Port output appears on the screen. Enter the SSL port number and press ENTER. 11. The Get Audit Logging Level output appears on the screen. Enter 1 if you do not want any audit information to be logged. Enter 2 if you want an intermediate level of audit information to be logged. Enter 3 if you want high-level audit information to be logged. Press ENTER. 12. The server-specific information output appears on the screen. Enter the JMX port and press ENTER. The JMX port is the RMI registry port for connecting to the JMX agent. The MDM server includes a client application for performing JMX monitoring. The default port number for communicating with JMX is 1100, but if the system you are installing on already has a service using port 1100, then select a different port number. 13. The Summary (Managed server) output appears, showing all the information entered so far. Review this screen carefully, and ensure that the values are accurate. Press ENTER to start the installation process. 14. The Installation Complete output appears on the screen. Press ENTER to exit the installer. Installing the MDM Managed Server 45

58 15. After the installation is successful, go to Chapter 4, Configuration and Post-Installation Activities on page 53. To perform a silent installation 1. To perform a silent installation, you must set up the silent_installer.properties file. This properties file has all the relevant information required for the installation wizard to install the MDM Administration Server. Edit the following sample silent_installer.properties file with a simple text editor, and replace the sample values with the required values. # This indicates the type of installation, allowed values are: Admin_Server/ Managed_Server/Single_Server. #If you comment out CHOSEN_INSTALL_SET standalone single server will be created by default. CHOSEN_INSTALL_SET=Managed_Server #Do not change this value. This is the default installation mode. INSTALLER_UI=silent # Directory where the MDM server is installed. # USER_INSTALL_DIR=/opt/scandium/manageserver #Specify the folder where Weblogic 9.2 is installed. The default value is provided below. beahome =/opt/bea #Specify the folder where JDK is installed. It is preferred that you use the JDK that is provided with the Weblogic 9.2 installation. javahome =/opt/bea/jdk150_06 # # Cluster information required only for admin server installation. # multicastaddress= multicastport=234 # # Admin server information for cluster deployment or single server information for standalone deployment. # adminserverport =7001 adminserverhost =niobium.idc.devlab.motive.com adminserversslport =7002 username =weblogic password =weblogic # # The port where Node manager is running. This is required only for the Managed server in a clustered deployment. # nodemanagerport=5556 # 46 MDM Cluster Setup

59 # Manage server information # managedserverhost=scandium.idc.devlab.motive.com managedserverport=7001 managedserversslport=7002 # # Database information. This is required for Admin server or Single server deployment. # dbhost= dbport=1521 dbservice=mdm dbuser =motive_mdm dbpassword =motive dbtnsname =tnsname # MDM Server specific information. The values provided below are the default values. Set the required values from the specified values. This is required for Admin server or Single server deployment. #multi-country/single-country phonenumbermode =single-country # specify true/false displaytrunkcode =false #Provide the country code below. The default value provided below is for INDIA. countryisocode =IN # specify full/intermediate/none auditlogginglevel =intermediate #External url information which is sent to device while bootstrap for communication with MDM server. externalurlhost= externalurlport= externalurlsslport= externalurlcontextpath= 2. Log in to the preconfigured BEA WebLogic server machine as the Solaris user created for the MDM Server installation (for example, motive ). Note Do not run the installation as the root user, but ensure that the user created for the installation has administrative privileges. This is the accepted best practice on Solaris machines for security reasons. 3. Change your working directory to the one containing the installer executable. Launch the silent MDM Server installation program by using the following command:./mobiledevicemanager_installer.bin -i silent -f Path-to-silent_installer.properties. Press ENTER to start the installation process. Installing the MDM Managed Server 47

60 Note The silent installation does not show any status on the console after the installation is complete. Verify that the Mobile_Device_Management_Server_InstallLog.log is generated, and confirm successful installation from the logs. The log files are err.properties, script.log, and wslt.log. They are in the MDMAdmin-Installation-directory/temp directory. 4. After the installation is successful, go to Chapter 4, Configuration and Post-Installation Activities on page 53 Starting and stopping the cluster Starting the MDM Cluster To start the MDM Cluster, you need to start the Administration Server first and then the Managed Servers. Managed Servers can be started from the WebLogic Server Console or from a command console. To start the Administration Server 1. Change directories to the MDM Administration Server installation directory. For example: cd /opt/mdmadmin-installation-directory 2. Run the command./startadminserver.sh. 3. Once the Administration Server is running, start the Managed Servers. To start the Managed Server from the WebLogic Server Console 1. Ensure that the Administration Server is running before logging into the WebLogic Server Console. 2. Open a web browser window and log in to the WebLogic Server Console: Note Use the same user name and password provided when installing the MDM Server. 3. In the main pane, click on Servers in the Environment list in the Domain Configurations area. 4. In the Summary of Servers window, the Managed Servers present in the domain are listed in the Name column of the Servers table. Click on a Managed Server to access the Settings for managed-server-name window. 48 MDM Cluster Setup

61 Note Each of the Managed Servers should be started individually. Repeat these steps for each Managed Server. 5. Click the Control tab, then Click the Start/Stop tab. 6. Review the status of the Managed Server, and click Start. The State of the machine should indicate Active. To start the Managed Server from the command line Important Before you start the Managed Server using the command script, ensure that the MDM bits are deployed to the Managed Server. This happens when you start the Managed Servers from the WebLogic Server Console as described in the Starting the MDM Cluster on page 48 procedure. 1. Change directories to the MDM Managed Server installation directory. For example: cd /opt/mdm-managed-server-installation-directory 2. Run the command./startmanagedserver.sh. To start the Node Manager from the command line 1. Change to the nodemanager directory in the MDM Managed Server installation directory. For example: cd /opt/mdm-managed-server-installation-directory/nodemanager 2. Run the command./startnodemanager.sh. Alternatively, you can start the node manager as a background process using the script startnodemanager_bgservice.sh in the same directory. Stopping the MDM Cluster To stop the MDM Cluster, you use the WebLogic Server Console. First, you stop the Managed Servers and then the Administration Server. To stop the Managed Servers 1. Open a web browser window and log in to the WebLogic Server Console: Note Use the same user name and password provided when installing the MDM Server. Stopping the MDM Cluster 49

62 2. In the main pane, click on Servers in the Environment list in the Domain Configurations area. 3. In the Summary of Servers window, the Managed Servers present in the domain are listed in the Name column of the Servers table. Click on a Managed Server to access the Settings for managed-server-name window. Note Each of the Managed Servers should be stopped individually. 4. Click the Control tab, then click the Start/Stop tab. 5. Review the status of the Managed Server. You have the option of forcing an immediate shutdown by using Shutdown->Force Shutdown Now, or requesting a shutdown after it completes all the jobs by using Shutdown->when work completes. The State of the machine should indicate STOPPED. 6. Repeat these steps for each of the Managed Servers. Updating the MDM Cluster Updating the Managed Servers is required when changes are made to the Administration server. The changes to the Administration Server are propagated to the Managed Servers. To update the MDM Cluster 1. Open a web browser window and log in to the WebLogic Server Console: Note Use the same user name and password provided when installing the MDM Server. 2. In the Domain Structure panel on the left, click on Deployments. 3. In the Summary of Deployments window, click the check box beside the deployed application Viper. Select Force Stop Now from the Stop menu. 4. Make the required changes to the application on the Administration Server. 5. In the WebLogic Server Console, click Lock & Edit in the Change Center panel. Click the check box beside the Viper application to select it. 6. Click Update to access the Update Application Assistant window. Click Finish. 50 MDM Cluster Setup

63 7. In the Summary of Deployments window, click the check box beside the deployed application Viper. Click Activate in the Change Center panel. 8. Click the check box to select the Viper application. Then select Servicing all requests from Start menu. 9. Click Yes in the Start Application Assistant window. 10. Now stop and start all the Managed Servers in the cluster to propagate the update to all the Managed Servers. Refer to Stopping the MDM Cluster to stop the Managed Servers. Refer to Starting the MDM Cluster to start the Managed Servers. Note All the Managed Servers must be running for the update to be successful. Uninstalling the Managed Server To uninstall the Managed Server 1. Perform the steps described in stopping the managed server. 2. Log in to the Solaris machine hosting the Managed Server as a user with root privileges. 3. Change the current working directory to the installation directory for the Managed Server. For example: cd /opt/dmsuite_152/cluster/ms 4. Change directories to the temp directory. For example: cd temp 5. Run the following script:./uninstallmanageserver.sh. Uninstalling the Managed Server 51

64 52 MDM Cluster Setup

65 This chapter covers: 4 Configuration and Post-Installation Activities Configuring the MDM Server Configuring the MDM WebLogic domain Licensing the installation Initial data creation 53

66 Configuring the MDM Server After you install the MDM Server, perform the following initial configuration steps: To initially configure the MDM server 1. Set the JAVA_HOME variable, and then add $JAVA_HOME/bin to the Path environment variable. Note It is recommended to use the JDK that comes with the BEA WebLogic installation. 2. At a bash command line, run the database schema creation script. 1. cd path-to-dmserver-install-directory 2../createSchema.sh The script prompts you for the information required to create the schema with a detailed description of the required information. During the script, you can choose which notification link connection types to configure as part of your deployment, by selecting the SMSG options. You can select All, CDMA, GSM, or WiMAX connection types. 3. The MDM Server automatically cancels any in-progress device management session that has timed out depending on the CancelInProgressInActiveTimeout parameter value set in the dmsuite.env file located in the MDM Administration Server install directory. Set it to the following value: CancelInProgressInActiveTimeout = JobCompletionTimeout + five minutes where JobCompletionTimeout is the maximum amount of time allocated to a device to complete any job. For example, if the JobCompletionTimeout is 10 minutes, then CancelInProgressInActiveTimeout is set to 15 minutes. Note The timeout values should be set so that CancelInProgressInActiveTimeout is greater than NotificationRetryTimeout and NotificationRetryTimeout is greater than JobCompletionTimeout. Configuring the MDM WebLogic domain You must make some configuration changes in the MDM server's BEA WebLogic domain to complete its configuration. 54 Configuration and Post-Installation Activities

67 Creating the MDMAdmin role This procedure describes how to create an MDMAdmin role in the WebLogic Server Console. To create the MDMAdmin role 1. Start the MDM Administration Server. See Starting and stopping the MDM Server on page 24 for standalone servers or Starting and stopping the cluster on page 48 for clusters. 2. Log in to the WebLogic Server Console. Open a web browser window and log in to the WebLogic Server Console: Note Use the same user name and password provided when installing the MDM Server. 3. In the Domain Structure box, select the Security Realms link for your domain. 4. In the main pane's list of security realms, click the link for the myrealm realm, then click the Roles and Policies tab and then the Realm Roles subtab. 5. In the Roles table, expand the Global Roles item, and then click on Roles; the Global Roles table appears. 6. In the Global Roles table, click the New button. The Create a New Role for this Realm page appears. 7. Enter MDMAdmin in the Name field. 8. Make sure the Provider Name field is set to XACMLRoleMapper. 9. Click the OK button. The system again displays the Global Roles table. 10. Click MDMAdmin in the table. The system displays the Edit Global Role - Global Role Conditions page. 11. Click the Add Conditions button. The system displays the Edit Global Role - Choose a Predicate page. 12. In the Predicate List field, select User. Creating the MDMAdmin role 55

68 13. Click the Next button. The system displays the Edit Global Role - Edit Arguments page. 14. Add sspadmin as an argument. In the User Argument Name field, enter sspadmin and then click the Add button. 15. Click the Finish button. The system displays the Edit Global Role - Global Role Conditions page again. 16. Click the Save button. The system displays the message, Changes saved successfully. Creating a user for WiDM webservice calls When the system is being used with a WiDM deployment, you must create a user with the following characteristics: Username: webserviceuser Password: webserviceuser Roles: MDMAdmin Use the WebLogic Server Console to create the user. See Adding a user on page 77. Configuring multicasting The system depends on multicast JMS messages which pass information to the managed servers in clusters. Before you install the system, review the BEA documentation at Troubleshooting Multicast Configuration [ download.oracle.com/docs/cd/e12840_01/wls/docs103/cluster/multicast_configuration.html]. After you install, use the MulticastTest utility (as described in the BEA documentation) to test your configuration, and then make any needed configuration changes. Licensing the installation To obtain a new MDM license after installation or upgrade, contact your MDM sales representative. Upon acquiring a new license key, you must update the License property through the Configuration Manager. 56 Configuration and Post-Installation Activities

69 Storing your MDM product license Until the MDM license is stored, the product is not licensed for use. To store your MDM product license 1. From Alcatel-Lucent's Motive Product Group, acquire a valid product license for MDM. Typically, the license string is provided in a text file. For example: license.txt 2. Log into the Configuration Manager: Logging into the Configuration Manager URL Or a User credentials configuser/configuser The configuser account was created during MDM installation. Until reset, the password is the same as the user name. a where: mgdhost.mycompany.com is the address of a load balancer that fronts the cluster of Managed Servers or the host on which a Managed Server instance is installed is the clear port is the SSL port. An Invalid license page is displayed. Upon each login, the page displays until a valid license is stored. 3. Click OK. 4. On left, click Application Administration. The Application Administration page is displayed with the Application Properties tab in focus. 5. In the License text box, paste a copy of the license string that you acquired in Step Click the Save Changes button. 7. In the upper-right corner, click the Publish to Server button to make the configuration active. Storing your MDM product license 57

70 Initial data creation You must create or load data into the system to describe devices, tenants, and the profiles and DDF files that describe how the devices work. All of the setup files required are provided in the product distribution's setup data folder. Perform the following general steps to set up the system. Refer to the topics in this section for more information. 1. Set up devices. 2. Create notification links (see Creating notification links on page 59. ) 3. Create tenant(s) (see Creating tenants on page 59). 4. Load setup data (see Load setup data on page 62). During this process, you will: Add models. Upload the DDFs that are representative of the set of devices that are supported under the models Upload the bootstrap workflow defined for the device models. Load the profile templates and mappings that are specific to each model. 5. Add a subscriber. The subscriber s device gets provisioned. 6. Assign a profile to the subscriber s device. The assigned profile does not assign all the services, but depends on the business logic, and customer s service request. Profile naming in a WiDM deployment For an installation to be used with a WiDM deployment, profile naming must match the names used in WiDM: H-NSP CAPL Policy RAPL Policy ChannelPlan RootCA Primary 58 Configuration and Post-Installation Activities

71 OtherSubscriptions Creating notification links Create one or more notification links for connecting to SMS providers. You must create these links before you create tenants. For each tenant, you can choose a notification link. See Creating or modifying a notification link on page 132 for information on creating the links. For a WiDM deployment, a sample WiMAX notification link file, WiMAX_Sample.xml, is provided in the setup data directory of the MDM distribution. Creating tenants This section provides instructions for creating default tenants for specific deployments. Create only the tenants needed for your deployment. Creating the wimax tenant This section provides instructions for creating the default tenant for a WiDM installation. Note The selection of wimax as the connection type is what makes a tenant a wimax tenant. To create the wimax tenant 1. Select Tenants->Create Tenant. 2. Specify values for the fields as follows: Field Name URI External Id Country DM Server Authentication Value wimax (none) wimax Select an appropriate country from the list Digest 3. Click Continue. Creating notification links 59

72 The Notification Properties screen appears. Specify values for the fields as follows. Under NOTIFICATION OPTIONS: Field Timeout to enqueue Bootstrap Timeout to enqueue Notification Maximum Notification/Bootstrap Retries Value 600 WIMAX 15 Specify values for the fields as follows. Under NOTIFICATION CONFIGURATION: Field Connection Type Protocol Name SMSC Link Value WIMAX WIMAX Use the name of the link you created for this tenant in the earlier procedure (see Creating notification links on page 59). Click Continue when you are done. 4. Enter AAA configuration values. Enter appropriate values for the AAA URL,User Name, and Password. Then click Continue. The system displays a confirmation page. 5. Click Confirm. 6. After creating the wimax tenant, complete AAA configuration with a database update. Update the Notify_URL field in the MOTV_CONFIG_PARAMETERS table. Run the following SQL query: update MOTV_CONFIG_PARAMETERS set VALUE=' EndpointEventService' where KEY='NOTIFY_URL'; Creating Mobility tenants This section provides instructions for creating default tenants that are typically used for Mobility testing. 60 Configuration and Post-Installation Activities

73 To create the T-Mobile tenant 1. Select Tenants->Create Tenant. 2. Specify values for the fields as follows: Field Name URI External Id Country DM Server Authentication Value T-Mobile T-Mobile United States Digest 3. Click Continue. The Notification Properties screen appears. 4. Select the check box for Add Country Code, and accept the defaults for the other fields. 5. Click Continue. To create a NAP profile for the tenant 1. Select the GPRS NAP template. 2. Click Continue. 3. Specify values for the fields as follows: Field Profile Name NAP ID Display Name Bearer Direction NAP Address Address Type DNS Address Internet Locked Value T-Mobile Data - T-Mobile Data Outgoing wap.voicestream.com APN - Yes Yes Creating tenants 61

74 Field Authentication Type Authentication Username Authentication Password AuthPrompt Value PAP - - Yes To create the Cingular tenant To create the Cingular tenant, you perform the same steps that were performed for T-Mobile with the following differences: 1. Specify values for the fields on the Create Tenant page as follows: Field Name URI External Id Country DM Server Authentication Value Cingular Cingular United States Digest 2. When creating the NAP profile, specify the following values: Field Profile Name NAP Address Value Cingular NAP wap.cingulargprs.com Load setup data The MDM distribution includes a setup data directory that contains profile data stored in TAR files. Upload the profile data using the import tool, as described in Importing profile templates on page 231. For a general installation, the following setup files are provided for Nokia S60 series, Windows Mobile 5, Windows Mobile 6 and Motorola V300 mobile devices: Bootstrap Templates DDF 62 Configuration and Post-Installation Activities

75 Profile MetaData Profile Mappings For a WiDM deployment, the directory also contains a sample WiMAX notification link XML file, WiMAX_Sample.xml. Load setup data 63

76 64 Configuration and Post-Installation Activities

77 This chapter covers: 5 User Management on the MDM Server User roles and access permissions Adding a user 65

78 The MDM Server administrator can add and delete users and assign roles to the users. Roles determine the set of activities a user can perform on the MDM Server. The roles to be assigned to a user are placed as comma separated values in a text file. The edited text file is provided when a user is added to the MDM Server. User roles and access permissions MDM Console users can be assigned roles to permit or limit access to the various sections of the MDM Console application. The table below shows the relationship between the roles assigned to a user and the sections of the user interface the role is allowed to access. Note Access to a tab automatically grants access to all the submenus of that tab. User roles and console access Tab name Devices Updates Subscribers Models Manufacturer Tenants Submenu/option name Upload Profile Assignments Device Detail View Subscribers Subscriber Detail Add Subscriber Update CP Models View site code Create Model View Manufacturers Create Manufacturer View Tenants Tenant Detail User roles SSPAdmin, SSPDeviceViewer All roles SSPAdmin, SSPDeviceViewer SSPAdmin, SSPUpdateViewer SSPAdmin, SSPSubscriberViewer SSPSubscriberViewer All SSPAdmin, SSPModelViewer All All SSPAdmin, SSPModelViewer SSPAdmin, SSPManufacturerViewer SSPAdmin, SSPManufacturerViewer All SSPAdmin, SSPCarrierViewer SSPAdmin, SSPCarrierViewer SSPAdmin, SSPCarrierViewer 66 User Management on the MDM Server

79 User roles and console access (continued) Tab name Provisioning Bulk Management Activity Logs Workflows Submenu/option name Edit Tenant Details Manage Profiles Create Tenant Manage Countries, Upload Profile Metadata, Manage Profile Templates, Delete Profile Template Upload Profile Service View Provisioning Requests Assign Image to Device Assign Image to Multiple Devices Create Workflow Job Manage Bulk Operations Bulk Operation Details Cancel Bulk Operation Edit Bulk Operation Delete Bulk Operation(s) Manage Device Groups Create Device Group Manage Search Templates Upload Search Template Cancel Job View Device Activity Log View Audit Log User roles SSPOperator, SSPCarrierEditor All SSPAdmin, SSPCarrierCreator All All SSPProvisioningRequestViewer, SSPProvisioningRequestCanceler SSPProvisioningRequestViewer, SSPProvisioningRequestCanceler SSPAdmin, SSPDeviceViewer SSPAdmin, SSPImageViewer, SSPUpdateViewer All SSPAdmin, SSPBulkDeviceManager SSPBulkDeviceManager SSPBulkDeviceManager All SSPBulkDeviceManager SSPBulkDeviceManager All All All All All SSPAdmin, SSPActivityLogViewer SSPAdmin, SSPActivityLogViewer SSPAdmin, SSPAuditLoggingViewer All User roles and access permissions 67

80 User roles and console access (continued) Tab name Reports Submenu/option name Upload Workflow Jobs User roles All All The table below lists the default users provided in the system, the default roles assigned to the users, and the operations permitted to the user. Default users, roles, and permitted operations User Roles Tabs Operations sspimageinstaller SSPImageInstaller, SSPImageViewer, SSPProvisioningRequestViewer Provisioning Assign Image to Multiple Devices, Create Workflow Job Updates View Updates Reports Generate Report Workflows View Workflow Jobs SSPImageAssigner SSPImageAssigner, SSPImageViewer, SSPDeviceViewer, SSPProvisioningRequestViewer Devices Provisioning Workflows View Subscriber Devices Assign Image to Device View Workflow Jobs Reports View Report Templates Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs sspimageuploader SSPImageUploader, SSPImageViewer Updates Upload Image Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspupdatecreator sspupdatecreator, SSPImageViewer, SSPUpdateViewer Updates View Updates, Upload Update Packages 68 User Management on the MDM Server

81 Default users, roles, and permitted operations (continued) User sspimageapprover sspupdateapprover sspupdateremover Roles sspimageapprover, SSPImageViewer, SSPUpdateApprover, SSPUpdateViewer sspupdateapprover, SSPUpdateViewer sspupdateremover, SSPUpdateViewer Tabs Bulk Management Workflows Reports Updates Bulk Management Workflows Reports Updates Bulk Management Workflows Reports Updates Operations Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs View Workflow Jobs View Report Templates View Updates Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs View Workflow Jobs View Report Templates View Updates Update Details, Details Do Action Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs View Workflow Jobs View Report Templates View Updates->Update Details->Do Action(Failed Testing/Passed Testing, View updates->update details->delete Bulk Management Workflows Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs View Workflow Jobs User roles and access permissions 69

82 Default users, roles, and permitted operations (continued) User Roles Tabs Operations Reports View Report Templates sspupdateworkflowloader sspupdateworkflowloader, SSPUpdateViewer Updates View Updates->Update Details->Do Action(Failed Testing/Passed Testing Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspdeviceactivator SSPDeviceActivator, SSPDeviceViewer Devices View Subscriber Devices, Deactivate, Display Known Device Tree, Upload Profile Assignments Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports Generate Report sspsubscriberactivator SSPSubscriberActivator, SSPSubscriberViewer Subscribers View Subscribers, Delete, Deactivate, Reactivate, Bootstrap Bulk Management Manage templates,manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspmodelcreator SSPModelCreator, SSPModelViewer Models View Models, Upload, View site code, Create 70 User Management on the MDM Server

83 Default users, roles, and permitted operations (continued) User Roles Tabs Operations Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspmanufacturercreator SSPManufacturerCreator, SSPManufacturerViewer Models View Manufacturers, Create Manufacturer, Manufacturer Detail Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspmodeleditor SSPModelEditor, SSPModelViewer Models View Models, Manage DDF, Manage Profile Mappings, Edit Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspimageremover SSPImageRemover, SSPImageViewer Updates Updates->Images Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates User roles and access permissions 71

84 Default users, roles, and permitted operations (continued) User Roles Tabs Operations sspdeviceremover SSPDeviceRemover, SSPDeviceViewer Devices Upload, View Subscriber Devices, Delete Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspprovisioningrequestcanceler SSPProvisioningRequestCanceler, SSPProvisioningRequestViewer Provisioning View Provisioning Requests Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspmodelremover SSPModelRemover, SSPModelViewer Models View Models, Delete Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspmanufacturerremover SSPManufacturerRemover, SSPManufacturerViewer Models View Manufacturers, Manufacturer Detail ->Delete Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs 72 User Management on the MDM Server

85 Default users, roles, and permitted operations (continued) User Roles Tabs Operations Reports View Report Templates sspdeviceeditor SSPDeviceEditor, SSPDeviceViewer Devices View Subscriber Devices, Edit Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspdeviceviewer SSPDeviceViewer, SSPImageViewer Devices View Subscriber Devices, Device Detail, Upload Profile Assignments Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspupdateviewer SSPUpdateViewer Updates View Updates, Update Detail Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspsubscriberviewer SSPSubscriberViewer Subscribers View Subscriber, Subscriber Detail Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs User roles and access permissions 73

86 Default users, roles, and permitted operations (continued) User Roles Tabs Operations Workflows View Workflow Jobs Reports View Report Templates sspmodelviewer SSPModelViewer Models View Models, Model Detail Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspmanufacturerviewer SSPManufacturerViewer Models View Manufacturers Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspprovisioningrequestviewe SSPProvisioningRequestViewer Provisioning View Provisioning Requests Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspactivitylogviewer SSPActivityLogViewer Activity Logs View Device Activity Log Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs 74 User Management on the MDM Server

87 Default users, roles, and permitted operations (continued) User Roles Tabs Operations Reports View Report Templates sspreportingviewer SSPReportingViewer Reports Generate Report Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspcarrierviewer SSPCarrierViewer Tenants Upload Profile Service, View Tenants, Tenant Detail Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspcarriercreator SSPCarrierCreator Tenants View Tenants, Manage Countries, Upload Profile Metadata, Manage Profile Templates, Upload Profile Service Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs Workflows View Workflow Jobs Reports View Report Templates sspcarriereditor SSPCarrierEditor Tenants View Tenants, Edit, Manage Profiles Bulk Management Manage templates, Manage Groups, Bulk Device Management Jobs, User roles and access permissions 75

88 Default users, roles, and permitted operations (continued) User sspcarrierremover sspauditloggingviewer sspadmin Roles SSPCarrierRemover SSPAuditLoggingViewer SSPAdmin, SSPUserAdministrator, SSPUpdateRemover, SSPImageCarrierAssociator, SSPCarrierRemover, SSPCarrierRemover, SSPAuditLoggingViewer, SSPActivityLogViewer, SSPDeviceEditor, SSPDeviceRemover, SSPImageAssigner, SSPUpdateWorkflowLoader, SSPUpdateWorkflowLoader, SSPUpdateViewer, SSPImageUploader, SSPUpdateCreator, SSPImageInstaller, SSPManufacturerViewer, SSPImageApprover, SSPUpdateApprover, SSPManufacturerRemover, Tabs Workflows Reports Tenants Bulk Management Workflows Reports Activity Logs Bulk Management Workflows Reports This user can access all tabs. Operations Bulk device management scheduled jobs View Workflow Jobs View Report Templates Delete Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs View Workflow Jobs View Report Templates View Audit Logs Manage templates, Manage Groups, Bulk Device Management Jobs, Bulk device management scheduled jobs View Workflow Jobs View Report Templates Can perform all available operations. 76 User Management on the MDM Server

89 Default users, roles, and permitted operations (continued) User Roles Tabs Operations SSPCarrierEditor, SSPCarrierCreator, SSPCarrierViewer, SSPOperator, SSPManufacturerCreator, SSPProvisioningRequestViewer, SSPSubscriberActivator, SSPProvisioningRequestCanceler, SSPSubscriberViewer, SSPDeviceViewer, SSPDeviceActivator, SSPImageViewer, SSPModelCreator, SSPModelViewer, SSPModelEditor Adding a user Use the WebLogic Server Console to add a user to the system. Note Adding a user Prior releases of the system included a script for user management. In this release, use the Administration Console instead. 1. Log in to the WebLogic Server Console as an admin user. Open a web browser window and log in to the WebLogic Server Console: Note Use the same user name and password provided when installing the MDM Server. 2. In the Domain Structure box on the left, select Security Realms. 3. In the Summary of Security Realms page in the main pane, click the myrealm link. 4. Select the Users and Groups tab. 5. Click the New button. 6. Enter a name and password for the new user. 7. Click OK. Adding a user 77

90 78 User Management on the MDM Server

91 This chapter covers: 6 Troubleshooting Verifying WebLogic is running Verifying Oracle database and database connection Managing Oracle database processes Checking client/server communications Understanding error codes 79

92 This chapter describes troubleshooting suggestions to help you resolve server issues. Verifying WebLogic is running You can verify that BEA WebLogic Application Server is running in one of the following ways: Run the following two commands: $ export CLASSPATH=$BEA_HOME/weblogic92/server/lib/weblogic.jar $ java weblogic.admin -username sspadmin_user -password sspadmin_password PING The first line sets the CLASSPATH before the java command is used. The expected response is: $ Sending 1 ping of 100 bytes. $ RTT = ~180 milliseconds, or ~180 milliseconds/packet If you receive a Failed to connect response, WebLogic is not running. Alternatively, run the following command: $ java weblogic.admin -username sspadmin_user -password sspadmin_password GETSTATE sspserver The expected response is: $ Current state of "sspserver": RUNNING Again, if you receive a Failed to connect message, WebLogic is not running. Verifying Oracle database and database connection To verify that the Oracle server is running and that you can connect to it from the MDM server machine, run the following command as an MDM Server user on the MDM server machine. $ tnsping oracle_tnsname Note If you have deployed a WebLogic clustered environment, the command should be run on every WebLogic Managed Server machine, to verify that each server can connect to the Oracle database 80 Troubleshooting

93 The expected response is similar to the following: TNS Ping Utility for Solaris: Version Production on 25-SEP :37:29 ) Copyright 1997 Oracle Corporation. All rights reserved. Attempting to contact (ADDRESS=(PROTOCOL=TCP)(HOST=: oracle_host )(PORT=1521)) OK (950 msec) If you do not get a message similar to this, refer to Managing Oracle database processes on page 81 to check the Oracle processes. Managing Oracle database processes This section describes how to verify that Oracle processes are running, verify the Oracle listener process is running, and view the services for which Oracle is listening. Verifying Oracle database processes are running Using a terminal window, log in as the oracle Solaris user on the Oracle server and run the following command to determine if Oracle database processes are running: $ ps -ef grep ora The expected response is similar to the following: oracle :52:38? 0:00 ora_pmon_webdb1 oracle :52:38? 0:00 ora_smon_webdb1 oracle :52:38? 0:00 ora_reco_webdb1 oracle :52:38? 0:01 ora_ckpt_webdb1 oracle :52:38? 0:00 ora_lgwr_webdb1 oracle :52:38? 0:00 ora_snp0_webdb1 oracle :52:38? 0:00 ora_dbw0_webdb1 oracle :52:38? 0:00 ora_s000_webdb1 oracle :52:38? 0:00 ora_d000_webdb1 oracle :52:38? 0:00 ora_snp2_webdb1 oracle :52:38? 0:00 ora_snp1_webdb1 oracle :52:38? 0:00 ora_snp3_webdb1 oracle :51:02 pts/3 0:00 grep ora_ Managing Oracle database processes 81

94 Verifying the Oracle listener process is running Using a terminal window, log in as the oracle Solaris user on the Oracle server and run the following command to determine is the Oracle listener process is running: $ ps -ef grep lsn The expected response is similar to the following: oracle :52:57? 0:00 /export/home/apps/oracle/ product/817/bin/tnslsnr LISTENER -inherit oracle :52:16 pts/3 0:00 grep lsn Viewing the services for which Oracle is listening Using a terminal Window, log in as the oracle Solaris user on the Oracle server and run the following command to view the services for which Oracle is listening: $ lsnrctl status The expected response is similar to the following: LSNRCTL for Solaris: Version Production on 02-OCT :52:59 ) Copyright 1998 Oracle Corporation. All rights reserved. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC))) STATUS of the LISTENER Alias LISTENER Version TNSLSNR for Solaris: Version Production Start Date 02-OCT :52:57 Uptime 0 days 2 hr. 0 min. 1 sec Trace Level off Security OFF SNMP OFF Listener Parameter File /export/home/apps/oracle/product/817/network/admin/listener.ora Listener Log File /export/home/apps/oracle/product/817/network/log/listener.log Services Summary... PLSExtProc has 1 service handler(s) webdb1 has 1 service handler(s) webdb1 has 2 service handler(s) The command completed successfully If the listener process is not running, it displays the following response instead: LSNRCTL for Solaris: Version Production on 02-OCT :56:53 ) Copyright 1998 Oracle Corporation. All rights reserved. Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC))) TNS-12541: TNS:no listener TNS-12560: TNS:protocol adapter error 82 Troubleshooting

95 TNS-00511: No listener Solaris Error: 2: No such file or directory Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=sspsweb)(PORT=1521))) TNS-12541: TNS:no listener TNS-12560: TNS:protocol adapter error TNS-00511: No listener Solaris Error: 146: Connection refused Checking client/server communications To check client/server communications 1. Open a web browser window and access the MDM Console: 2. If you can successfully access the MDM Console, then the problem may be in the firewall or proxy configuration. 3. On the client (a Mobile Device Manager enabled handset), select Update Handset. The handset should attempt to connect to the MDM Server. If the connection is unsuccessful, continue with the following steps. 4. View the access log file to see client communications with the server, as follows: For example: [23/Sep/2002:19:19: ] "POST /download/authorization HTTP/1.1" [23/Sep/2002:19:19: ] "POST /download/authorization HTTP/1.1" [23/Sep/2002:19:19: ] "POST /download/discovery HTTP/1.1" [23/Sep/2002:19:19: ] "GET /download/download/1 HTTP/1.1" [23/Sep/2002:19:19: ] "POST /download/received HTTP/1.1" [23/Sep/2002:19:19: ] "POST /download/confirmed HTTP/1.1" [23/Sep/2002:19:19: ] "POST /download/completed HTTP/1.1" Other than the initial 401 entry, all other entries should be either 200 or Correct the setting and path for ssp.proxy.server.url in the file: install_dir/mdmserver/properties/local.properties 6. Stop and start the MDM Server to initialize the changes made to the local.properties file. 7. Retry the client-server communication. If the ssp.proxy.server.url property specifies the host/port correctly but not the right path, then the invalid download attempts would show up in the following file: Checking client/server communications 83

96 install_dir/mdmserver/sspdomain/sspserver/access.log For example: [15/Jan/2003:04:05: ] "POST /download/discovery HTTP/1.1" [15/Jan/2003:04:05: ] "GET //Download/2000 HTTP/1.1" [15/Jan/2003:04:05: ] "POST /download/authorization HTTP/1. 1" [15/Jan/2003:04:05: ] "POST /download/authorization HTTP/1. 1" [15/Jan/2003:04:05: ] "GET //Download/2000 HTTP/1.1" [15/Jan/2003:04:05: ] "POST /download/authorization HTTP/1. 1" [15/Jan/2003:04:05: ] "POST /download/authorization HTTP/1. 1" This example shows a valid discovery request (200) followed by an unsuccessful download (404). The client retries beginning with an Authorization request. Understanding error codes For information on error codes such as 404, 405, and so on, refer to the protocol documents provided at the OMA site: 84 Troubleshooting

97 This chapter covers: 7 Oracle Installation and Configuration Checklist Verifying system requirements Performing prerequisite setup tasks as root user Performing prerequisite setup tasks as the oracle user Installing the Oracle 10g Enterprise Edition Server Verifying your Installation Installing the Oracle Client Creating the MDM database and schema 85

98 This chapter provides a basic checklist of the Oracle operations and configurations that the database administrator must perform when setting up the MDM database. Note This checklist does not include every possible Oracle operation. For further details on Oracle database and configuration operations, refer to the Oracle documentation distributed with the Oracle software. Important The Oracle server and database must be installed before installing the application server software or the MDM Server. Adjustments to the Oracle database can be made after initial installation, but the base installation must be completed beforehand. Verifying system requirements Refer to the Oracle documentation for system requirements. Adjust these requirements based on the estimated additional needs of your service and network requirements. At a minimum, consider the following areas: RAM, swap space, disk space, and temporary disk space requirements for installer Operating system compatibility including OS patch installations and OS package installations XWindows emulation software (such as XWin32) installed Release note considerations Oracle file size limitations and settings (that is, the ulimit command) JRE (use the version installed by the Oracle installer) Performing prerequisite setup tasks as root user To perform setup tasks as the root user prior to installation 1. Configure the Solaris kernel IPC parameters to accommodate the SGA structure of Oracle 10g (located in /etc/system file). 2. Create mount points for the Oracle software and additional ones for database files. 3. Create Solaris groups for database administrators (for example, SYSDBA, SYSOPER, and DBA ). Use the admintool or groupadd utility. 86 Oracle Installation and Configuration Checklist

99 4. Create a Solaris group for the Oracle installer (for example, oinstall ). Use the admintool or groupadd utility. 5. Create a Solaris account to own the Oracle database (for example, oracle/oracle with a user name/password that is part of the oinstall group and dba as a secondary group). The login shell must be defined as a Bourne shell for the MDM Server installations. Use the admintool or useradd utility. This account is used for installing and maintaining MDM databases. Performing prerequisite setup tasks as the oracle user To perform setup tasks as the oracle user prior to installation 1. Establish application and database directories (for example, /export/home/apps and /export/home/database). The oracle user needs to have read/write access to these directories. 2. Set these environment variables: DISPLAY. The name, server number, and screen number of the system where the Oracle installer is run. ORACLE_BASE. The top directory of the Oracle software and administrative file structure. ORACLE_HOME. The directory containing the Oracle software. ORACLE_SID. The Oracle server instance identifier to use during installation. PATH. The shell s search path for executables. 3. Update the environment for the current shell session. 4. Load the Oracle Distribution. Installing the Oracle 10g Enterprise Edition Server Using an XWindows emulation application (such as XWin32), log in to the server as the oracle user to install the Oracle software. Run the Oracle installation program from the Oracle Distribution directory. For example: /ORACLE_DISTRIBUTION/Disk1/runInstaller In general, the default values of the Oracle GUI installer should be accepted except for the following values: Solaris Group Name screen. Enter the oinstall group. Available Products screen. Select Oracle 10g Enterprise Edition. Performing prerequisite setup tasks as the oracle user 87

100 Privileged Operating System Groups screen. For example, DBA. Database Identification screen: Global Database Name. For example, ssps.domain.com. Oracle System Identifier (SID). For example, ssps. The SID must match the ORACLE_SID defined in the.profile file. Database File Location screen. For example, /db_dir/database/ora817. Do you really want to exit? dialog box. Click Yes. Verifying your Installation To verify your installation 1. Verify that SQL*Plus is running on the installed machine. 2. Determine if the Oracle listener is running (for example, $ lsnrctl status). 3. Verify TCP/IP connectivity by using ftp to send a test file to the installed server. Installing the Oracle Client The Oracle Client software must be installed on the standalone application server (unless the Oracle server is installed on the same machine) or on each node in an application server cluster. To install the Oracle Client 1. Log in as oracle user, and accept all installation defaults. 2. Add a network reference to the Oracle server on every machine where the Oracle Client is installed. 3. Edit the tnsnames.ora file, and save it to the $ORACLE_HOME/network/admin directory: $ORACLE_HOME/network/admin/samples/tnsnames.ora 88 Oracle Installation and Configuration Checklist

101 Creating the MDM database and schema Several factors must be taken into consideration when creating the production MDM database and schema, including existing network infrastructure, system resources, load balancing, and so on. Consult Motive Consulting Services after all installation and configuration requirements have been met. Creating the MDM database and schema 89

102 90 Oracle Installation and Configuration Checklist

103 This chapter covers: 8 BEA WebLogic Installation and Configuration Checklist Verifying system requirements Performing prerequisite setup tasks as root user Installing WebLogic Server 9.2 Verifying the installation 91

104 This chapter provides a basic checklist of the BEA WebLogic operations and configurations that the system administrator must perform when setting up the standalone WebLogic Server or WebLogic Server Cluster. Note This checklist does not include every possible WebLogic operation. For further details on WebLogic configuration operations, refer to the BEA documentation distributed with the WebLogic software. Important The WebLogic server (standalone or cluster configuration) must be installed and configured before installing the MDM Server (and preferably after installing the Oracle server and database). Verifying system requirements System requirements are provided in the BEA WebLogic documentation. In addition, review the system requirements mentioned in Standalone MDM Server installation and configuration overview on page 4 and MDM Cluster installation and configuration overview on page 6. Adjust these requirements based on the known additional needs of your service and network requirements. At a minimum, consider the following areas: RAM, swap space, disk space, and temporary disk space requirements for the installer Operating system compatibility including OS patch installations and OS package installations XWindows emulation software (such as XWin32) installed Release note considerations JRE (installed by the BEA WebLogic application server installer) Performing prerequisite setup tasks as root user To perform setup tasks as the root user prior to installation 1. Create a Solaris group for the WebLogic Server and MDM Server installation (for example, motive). Use the admintool or groupadd utility. 2. Create a Solaris account to install WebLogic Server, and subsequently the MDM Server (for example, motive/motive with a user name/password that is part of the motive group). The login shell must be defined as a Bourne shell for the MDM Server installations. 92 BEA WebLogic Installation and Configuration Checklist

105 Use the admintool or useradd utility. This account is used for installing and maintaining WebLogic and MDM Servers. 3. Set the following environment variables: DISPLAY. The name, server number, and screen number of the system where the WebLogic installer is run. BEA_HOME. A repository for common files that are used by multiple BEA products installed on the same machine. For example: BEA_HOME=/export/home/apps/bea WL_HOME. The product installation directory that contains all the software components to be installed on your system, including program files and examples. For example: WL_HOME=$BEA_HOME/weblogic92 JAVA_HOME. The JDK installation directory that contains the JDK program files installed with the WebLogic installation. For example: JAVA_HOME=$BEA_HOME/jdk131_08 ORACLE_BASE. The top directory of the Oracle software and administrative file structure. ORACLE_HOME. The directory containing the Oracle software. ORACLE_SID. The Oracle server instance identifier to use during installation. PATH. The shell s search path for executables. 4. Update the environment for the current shell session. 5. Load the WebLogic Distribution. Installing WebLogic Server 9.2 Using an XWindows emulation application (such as XWin32), log in to the target server as the motive user to install the software. Run the WebLogic installation program from the WebLogic distribution directory. For example: /WEBLOGIC_DISTRIBUTION/server_solaris.bin In general, the default values of the WebLogic installer can be accepted except for the following values: Choose BEA Home Directory screen. For example, /export/home/apps/bea Choose Installation Type screen. Select Custom. Choose Components screen. Do not select the Server Examples option. Choose Product Directory screen. For example, /export/home/apps/bea/weblogic92 Run Configuration Wizard screen. Select No, skip Configuration Wizard. Installing WebLogic Server

106 Verifying the installation Refer to Verifying WebLogic is running on page BEA WebLogic Installation and Configuration Checklist

107 This chapter covers: 9 SMSC and Kannel Gateway Client Installation and Configuration Installing Kannel Starting the gateway components 95

108 Installing Kannel The Kannel SMS Gateway client can be compiled from the source code, or the precompiled binary version can be obtained for the Fedora Linux and Debian platforms from the following location Kannel: Download Page [ download.shtml#current]. This chapter describes how to compile Kannel on the Windows platform using the Cygwin shell. If you need more information about compiling Kannel for other platforms, refer to Chapter 2. Installing the gateway [ To install Kannel 1. If Cygwin is not installed, install it now. You can install it from the install link at Important When using the Select Packages page during the Cygwin installation, select the Devel category, then select gcc, make, and libxml12 for inclusion in the installation. 2. If Cygwin is installed, determine if the gcc, make, and libxml12 packages in the Devel category are installed. If not, use the Cygwin installer at Kannel SMS Gateway client [ to add these packages. 3. Go to page, select the gateway.zip source as a ZIP file link, and then save the file to the host. 4. In Windows Explorer, find the downloaded file (gateway zip), and extract its content to the root of the C directory. By default, the extraction process puts the content files into a directory named gateway From a Cygwin shell, run the following commands: cd /cygdrive/c/gateway /configure The process first checks for dependencies and stops if it identifies a dependency that is not installed. You can use the Cygwin installer to add uninstalled dependencies. At the end, the license information appears. 6. From the same Cygwin shell, run the following commands: cd /cygdrive/c/gateway make The process begins running with several lines of output. 7. Install the gateway: cd /cygdrive/c/gateway make bindir=/gw install 96 SMSC and Kannel Gateway Client Installation and Configuration

109 Starting the gateway components To start the gateway components 1. Back up the following file by renaming it pushkannel.conf.orig or something similar: C:\gateway-1.4.1\gw\pushkannel.conf 2. Change the property values in the pushkannel.config file. A sample file is provided: # SAMPLE CONFIGURATION FOR KANNEL PPG (PUSH OVER SMS) # BEARERBOX SETUP, for Kannel core operations group = core admin-port = smsbox-port = wapbox-port = admin-password = bar #status-password = foo #admin-deny-ip = "" #admin-allow-ip = "" wdp-interface-name = "*" log-file = "bearerbox.log" #log-level = 0 box-deny-ip = "*.*.*.*" box-allow-ip = " " unified-prefix = "+358,00358,0;+,00" #access-log = "access.log" #store-file = "kannel.store" #ssl-server-cert-file = "cert.pem" #ssl-server-key-file = "key.pem" # WAPBOX SETUP, for pushing and for pulling (fetching) the wap data group = wapbox bearerbox-host = localhost #log-file = "/tmp/wapbox.log" #log-level = 0 syslog-level = none # PPG CORE SETUP, for defining the push request interface group = ppg ppg-url = /cgi-bin/wap-push.cgi ppg-port = 8080 #ppg-ssl-port = 8081 concurrent-pushes = 100 trusted-pi = true users = 1024 ppg-deny-ip = ; ppg-allow-ip = ; ; ; #ssl-server-cert-file = "/Users/aarno/gateway/test/cert.pem" #ssl-server-key-file = "/Users/aarno/gateway/test/key.pem" # PPG USER SETUP, for authorizing a specific push user Starting the gateway components 97

110 group = wap-push-user wap-push-user = foo-wap ppg-username = foo-ppg ppg-password = bar-ppg # Note that prefixes must have an international format. So the country # prefix must be added here. country-prefix = +358 allowed-prefix = 40;60;70 denied-prefix = 50 white-list = black-list = allow-ip = ; ; deny-ip = , # SMSC CONNECTIONS, for pushing SI or SL over SMS group = smsc smsc = smpp host = # host = # host = this can be used as well transceiver-mode=false port = 8011 system-type = SMPP smsc-username = smsc-password = address-range = interface-version=33 enquire-link-interval=60 source-addr-ton=6 source-addr-npi=6 dest-addr-ton=1 dest-addr-npi=1 # SMSBOX SETUP (a kludge!) group = smsbox bearerbox-host = localhost sendsms-port = #global-sender = #sendsms-chars = " " log-file = "smsbox.log" log-level = 0 #access-log = "access.log" # SEND-SMS USERS group = sendsms-user username = company-name password = bar-foo Important For details on the configuration properties, see Configuring the gateway [ download/1.4.1/userguide-1.4.1/userguide.html#aen418] in the Kannel User's Guide. You can make server-specific configurations and then restart the components. 3. In a separate Cygwin shell, start bearerbox.exe, and leave the shell open: 98 SMSC and Kannel Gateway Client Installation and Configuration

111 cd /cygdrive/c/gateway-1.4.1/gw./bearerbox.exe -v 1 pushkannel.conf The following text should appear at the end of the output: MAIN: Start-up done, entering mainloop 4. In a separate Cygwin shell, start smsbox.exe, and leave the shell open: cd /cygdrive/c/gateway-1.4.1/gw./smsbox.exe -v 1 smskannel.conf The following text should appear at the end of the output: MAIN: Connected to bearerbox at <IP address> port 1301 In the bearerbox shell, the following text should appear in the output: MAIN: Client connected from <IP address> Starting the gateway components 99

112 100 SMSC and Kannel Gateway Client Installation and Configuration

113 This chapter covers: 10 Apache Installation and Configuration Installing Apache Configuring Apache Configuring the Apache proxy server 101

114 This chapter describes procedures for the installation and configuration of the Apache proxy server. Installing Apache To install Apache 1. Download the software (for SPARC/Solaris 9) from SunFreeware: 2. Install these modules on the Administration Server: apache sol9-sparc-local.gz expat sol9-sparc-local.gz libiconv-1.8-sol9-sparc-local.gz gdbm sol9-sparc-local.gz db nc-sol9-sparc-local.gz openssl-0.9.8b-sol9-sparc-local.gz libgcc sol9-sparc-local.gz 3. Extract these files into a temporary directory and decompress them. Then install them on the Administration Server using pkgadd and answering Yes to the Install conflicting files? prompt. gzip -d expat sol9-sparc-local.gz gzip -d libiconv-1.8-sol9-sparc-local.gz gzip -d gdbm sol9-sparc-local.gz gzip -d db nc-sol9-sparc-local.gz gzip -d openssl-0.9.8b-sol9-sparc-local.gz gzip -d libgcc sol9-sparc-local.gz gzip -d apache sol9-sparc-local.gz pkgadd -d expat sol9-sparc-local.gz pkgadd -d libiconv-1.8-sol9-sparc-local.gz pkgadd -d gdbm sol9-sparc-local.gz pkgadd -d db nc-sol9-sparc-local.gz pkgadd -d openssl-0.9.8b-sol9-sparc-local.gz pkgadd -d libgcc sol9-sparc-local.gz pkgadd -d apache sol9-sparc-local.gz Configuring Apache Make Apache start as user apache and NOT user oracle (should start as root). To configure Apache 1. Stop Apache if it is running: su - oracle usr/local/apache2/bin/apachectl stop 102 Apache Installation and Configuration

115 2. Edit /usr/local/apache2/conf/httpd.conf: Group to apache User to apache ServerAdmin to ServerName to solaris3.internal.local:80 3. Change the ownership of certain files from Oracle to Apache: cd $ORACLE_HOME/Apache/Apache su chown apache:apache logs logs/* cd../modplsql chown apache:apache log log/* cfg/wdbsvr.app cd../jserv chown apache:apache logs logs/* 4. Create the Apache users.bash_profile file: su - apache cp ~oracle/.bash_profile. 5. Set up Apache to run as a proxy by pasting the following code into httpd.conf: # # Configure the proxy module of Apache # <IfModule mod_proxy.c> ProxyRequests Off <Proxy *> Order deny,allow Allow from all </Proxy> ProxyPass / for WL>/ ProxyPassReverse / for WL>/ </IfModule> 6. Start Apache by going to /usr/local/apache2/bin/ and using this command:./apachectl start 7. Verify that Apache is running: ps -ef grep httpd Configuring the Apache proxy server To set up Apache as a proxy server, include the following ProxyPass and ProxyPassReverse directives in the proxy module in httpd.conf: Configuring the Apache proxy server 103

116 # # Configure the proxy module of Apache # <IfModule mod_proxy.c> ProxyRequests Off <Proxy *> Order deny,allow Allow from all </Proxy> ProxyPass /mdm ProxyPassReverse /mdm ProxyPass / ProxyPassReverse /omadm ProxyPass /soap/devicemanagementws ProxyPassReverse /soap/devicemanagementws devicemanagementws ProxyPass /soap/enterpriseportalws ProxyPassReverse /soap/enterpriseportalws enterpriseportalws ProxyPass /oamp ProxyPassReverse /oamp ProxyPass /myphoneportalws ProxyPassReverse /myphoneportalws ProxyPass /healthmonitor/healthcheck ProxyPassReverse /healthmonitor/healthcheck healthcheck </IfModule> 104 Apache Installation and Configuration

117 This chapter covers: 11 Sample Database Installation for Standalone Server Creating the database Verifying the installation 105

118 If you have a test system and would like to start looking at the MDM Server (standalone configuration only), you can install a sample database included with the MDM Server installation files. Creating the database To create a test database on your test system 1. Log into the system as the SSPS user. 2. Set the variables: % ant.sh create-setenv 3. Create the database schema and load the sample data in the database: % ant-sh create-db 4. Start the WebLogic server: % ant.sh wlrun Important When you have finished using the test database, the administrator must delete the user and recreate the database schema before using the test machine in a production environment. Verifying the installation To verify that the database installation was successful 1. Access the MDM Console by entering the following URL in your web browser. Note The port value in the URL should be the non-ssl port value entered during installation. 2. At the login screen, enter the default user name (sspadmin) and password (motive). Note The default user name and password can be changed through the WebLogic Server Console. 3. If the MDM Console is launched, the installation was successful. Refer to Chapter 6, Troubleshooting on page 79 for more details. 106 Sample Database Installation for Standalone Server

119 12 MDM Server Monitoring 107

120 To monitor the health of the MDM Server, enter the following secure URL in the address bar of a web browser: The browser should return the following message: Hello from MDM Server, Current Local Time = Local-Time Note Nothing is displayed if the MDM Server is down. 108 MDM Server Monitoring

121 Administering the MDM Server This part covers: Chapter 13, Mobile Device Manager Overview Chapter 14, Managing SMSC/Notification Objects Chapter 15, Managing Tenants Chapter 16, Managing Subscribers Chapter 17, Managing Models Chapter 18, Managing Devices Chapter 19, Managing Updates Chapter 20, Bulk Management Chapter 21, Managing Provisioning Requests Chapter 22, Logging, Reporting, and Monitoring the System Chapter 23, Managing Roles Appendix A, Advanced Operations Appendix B, Quick Start Reference

122

123 This chapter covers: 13 Mobile Device Manager Overview Modular platform architecture Accessing the MDM console Accessing the WebLogic Server Console Mobile Device Manager integration with operator systems Mobile Device Manager data model MDM Console 111

124 Motive's Mobile Device Manager brings intelligence to device management and promotes subscriber satisfaction with increasingly complex mobile services. Mobile Device Manager allows mobile operators to remotely provision, update, and manage devices and services throughout the device life cycle. Mobile Device Manager features ICE, providing intelligent targeted provisioning and automated device management to further enhance the subscriber's experience, drive new revenue generating services, and reduce customer care costs. Motive Mobile Device Manager supports user input in all languages supported by the UTF-8 encoding scheme. Modular platform architecture Mobile Device Manager provides a flexible and modular server platform that provides advanced device management capabilities for today s increasingly complex population of mobile devices. The Mobile Device Manager can be deployed with one or more of the following device management capabilities to provide an economical and easily expanded solution for current and future requirements: CP device provisioning on page 113 DM device provisioning on page 114 Firmware update on page 114 Diagnostics on page 115 Alerts on page 116 ICE workflows on page 116 Additional capabilities can be added with simple upgrades. 112 Mobile Device Manager Overview

125 Mobile Device Manager components CP device provisioning A multitude of configuration parameters must be entered into a mobile device to activate advanced mobile data services like web browsing, MMS, and . The error-prone manual configuration requiring several minutes of work with a customer service representative (CSR) can now be done automatically in a matter of seconds. CP (client provisioning) provides device provisioning capabilities for hundreds of existing mobile devices. CP Device Provisioning supports the following standards and protocols: OMA (Open Mobile Alliance) CP 1.1 Nokia-Ericsson OTA Specification 7.0/7.1 Openwave Primary Provisioning Browser v3-6.x Smart Messaging WAP 2.0 Provisioning Bootstrap CP Device Provisioning supports the following settings: WAP MMS GPRS/APN/Internet CP device provisioning 113

126 Bookmarks Push to Talk Video Streaming Wireless Village Home Page Presence DM device provisioning DM Device Provisioning provides secure, behind-the-scenes provisioning transactions over any network. Devices are provisioned and managed over the entire device life cycle with an efficient and highly extensible OMA (Open Mobile Alliance) DM protocol that supports virtually all future device functionality. DM Device Provisioning supports OMA DM and 1.2. Using OMA DM device provisioning, virtually any parameter or application that is presented on a device s management tree can be configured or updated. DM Device Provisioning also provides the capability to read the contents of the DM tree on a device (discovery job), and to execute SyncML commands on the device (command script job). Firmware update FOTA (firmware over-the-air) provides remote updates to keep the devices up-to-date and provide quick fixes without taking the device to a service center. Dual-mode support Motive's Mobile Device Manager provides dual-mode support for both OMA DM and OMA DL methods for firmware updating. The OMA DM "In-session" method accomplishes firmware updates using a single OMA DM session between the mobile device and the OMA DM server. The FOTA download parameters are provisioned, and the firmware update package is downloaded in the same OMA DM session. The OMA DL "Alternative" method uses an OMA DM session to provision the FOTA download parameters, and OMA DL protocols to download the firmware update package. 114 Mobile Device Manager Overview

127 The OMA DM client and an OMA DM compliant firmware update client in the device interoperate using standard hand-off mechanisms to achieve an end-to-end solution for downloading firmware packages into the mobile device. Firmware update life cycle management Life cycle management delivers reliable updates more efficiently by managing the testing, approval, and provisioning process. The life cycle process can be customized to meet the requirements of any mobile operator or device manufacturer to ensure quality and efficiency. OEM portal A SOAP/XML-based web services API provides simple integration with OEM build systems to allow the OEM to upload firmware to mobile devices. Diagnostics The Mobile Device Manager provides visibility, configuration, and diagnostic capabilities to aid in the quick resolution of problems with these sophisticated devices. Concise information on the status, configuration, and operation of the device is presented to a customer service representative (CSR) to provide a clear understanding of how to restore proper operation of the device. Some information and configuration capabilities can also be provided directly to the customer through a support portal on the website. Visibility and device configuration. A CSR instantly sees the device's status and configuration including firmware, service settings, and applications. Device settings are compared to the expected values and can often be resolved in one operation. For even more detailed information, the device's DM tree can be read to provide complete information on all aspects of device status and configuration. Device diagnostics. Many devices also support diagnostic information to provide instant insight into the device's physical capabilities and operation. Information includes memory size and usage, screen metrics, battery life, and operating system information. Device and service history. A complete history of device management activity is provided for each device. Detailed information on device activation/deactivation, updates, configuration changes, and other activities are stored and available to provide the context of previous management activities to help solve the current problem. This information is useful in identifying problematic devices and the most commonly recurring problems with various device models. Complete historical records of CSR actions are also stored to enable the generation of customer care service metrics. Diagnostics 115

128 Alerts The Mobile Device Manager supports complete OMA DM 1.2 alert functionality. The mobile device client can create alerts such as change in status, failure of a managed element, or completion of a firmware update. The Mobile Device Manager's alert capability also supports model specific alerts and user interaction alerts that display messages and confirm actions. All alerts are logged, and ICE workflows can be designed to analyze alerts and initiate appropriate actions. ICE workflows Motive's ICE allows quick implementation of customized intelligent workflows that automatically configure and update mobile devices based on a variety of available data. Targeted provisioning and automated updates provide opportunities for dynamic service delivery, optimized revenues, and significantly lower support costs. ICE workflows are used to: Deliver targeted content, applications, and services based on demographics. Automate updates with closed-loop responses to alerts and failures. Deploy customized services to enterprise customers. Customize the subscriber experience based on usage patterns and billing data. Control how, when, and where devices are configured and updated Automated device configuration Automated Device Configuration (ADC) provides automatic configuration of mobile devices at the instant they are detected on the network. Subscribers can begin using their devices and services right out of the box. 116 Mobile Device Manager Overview

129 Automated device configuration The network is monitored by a number of optional methods to detect the presence of a new mobile device. The new IMSI/MSISDN/IMEI combination is forwarded to the ADC module of the Mobile Device Manager. Mobile devices new to the network are added to the database and automatically configured. Devices that have altered configurations or have changed ownership are also configured if necessary. Various methods of automatic detection can be used to detect a new device in the network. A detection node can detect device changes in real time by monitoring SS7 links and extracting the triplet (IMSI, MSISDN, and IMEI) information. Triplet information can also be obtained from a network element such as a database or directly from a billing gateway. SIM cards can send the triplet information directly to the ADC Module, providing a very cost effective method of automated configuration. The ADC Module's adapter can be customized to accommodate the accumulation of triplet information using any of these methods. When a new device/subscriber is detected, it is added to the MDM database. The model's capabilities are then compared to the available operator-defined configuration profiles to determine a set of profiles to be assigned. The mobile device is then configured through CP or DM provisioning methods depending on the model's capabilities, and the device is ready to use. The ADC Module uses web service operations to perform the automatic configuration. This confines any customization to that of the ADC adapter used to obtain the triplet information. It also allows operators to develop an ADC service external to Mobile Device Manager, and simply use the web services to create the device and execute the configuration. Comprehensive profile management Mobile Device Manager manages device settings through profile management. A profile specifies settings for a specific service or application on a mobile device. For example: (POP/SMTP server) Comprehensive profile management 117

130 WAP browser (home page and proxy) MMS (MMS relay) Profile management allows an operator to configure the service or application on a device without knowing the specific details of the device. For example, a Hotmail profile, created using the profile template, has corresponding Hotmail-specific values for receiving/sending server addresses, mailbox protocol, and so on. A Yahoo profile, created from the same template, has Yahoo-specific values. Subscriber-specific information is specified when the Yahoo profile is assigned to a specific device. Other aspects of profile management are: profile template Defines the structure and attributes of a type of profile supported by the Mobile Device Manager. For example, the Mobile Device Manager provides templates for , MMS, GPRS NAP, and so on. The profile template specifies the structure and attributes required for an service. The profile template also specifies which attributes are subscriber-specific. DDF (Device Description Framework) Describes the structure of the device tree in every DM enabled device model. Tree nodes, or management objects, define the device s capabilities and configurable attributes. DDFs are distributed by the manufacturer. profile mapping Maps the attributes of a profile template to device management tree nodes (defined by the DDF) for a particular DM enabled device model. Therefore, each model would have a profile mapping for each profile template that it supports. For example, a Nokia 7610 model has a mapping for the template, which specifies how each attribute maps to the management objects on the device. For CP enabled device models, the template attributes are mapped to SMS messages used to configure the settings on the device. profile assignment Assigns a profile to a device so that a provisioning request is created to configure the device for the service specified by the profile. For example, a Yahoo profile is assigned to a device to configure it for Yahoo . Because the profile is now being associated with a particular device/subscriber, the subscriber-specific information is specified during the profile assignment. A device has profile assignments for each configured service or application. The key concepts of Mobile Device Manager profile management and configuring devices using profiles are illustrated in Figure 13.3, Profile management and device provisioning key concepts on page 119, with a step-by-step description provided afterwards. 118 Mobile Device Manager Overview

131 Profile management and device provisioning key concepts Manufacturer Tenant Model Subscriber Device Profile mapping All attributes mapped to each model Profile assignment Subscriber-specific attributes are defined Profile Templates Profiles Profile template Provided for each type of service or application Profile (based on template) Service and tenant-specific attributes are defined Profile management and device provisioning works as follows: 1. A profile template is defined for each service or application provided by the mobile operator. For example, an template. 2. As new device models become available, the applicable profile template attributes are mapped to the model to remove this complexity from day-to-day tenant operations. 3. Profiles (based on profile templates) are created to define specific services or applications with tenant-specific and service-specific attribute settings. For example, a Yahoo profile (created from the template) includes tenant and service-specific attribute settings for Yahoo (service name, sending/receiving server, mailbox protocol, and so on). 4. Profiles are then assigned to a device to provision the appropriate services and applications on the device. A list of applicable profiles is provided, depending on the capabilities of the selected device. As profiles are assigned, any subscriber-specific attributes for a service or application are defined. For example, the user name, password, and address are specified when assigning the Yahoo profile to a device. The Mobile Device Manager creates an Assign Profile job to send the settings to the device immediately or at a scheduled time and date. Comprehensive profile management 119

132 5. Provisioning requests, such as the Assign Profile job, are sent to a queue for processing and can be monitored and canceled. Granular scheduling Provisioning requests can be created to update a single device or group of devices and ensure management tasks are unintrusive to the subscriber. You can control how and when updates are done by specifying parameters such as start time, time periods for updates, geographic groups, and the order and rate of execution. Web services APIs Mobile Device Manager provides standard SOAP APIs for simple integration with other tenant systems. Mobile Device Manager provides flexible security and allows the use of basic authentication, digest authentication, or digital certificates. HTTPS provides authentication and encryption of all communication between the client and the server. Highly scalable The Mobile Device Manager components are built using J2EE technology and run on enterprise-class application servers to offer superior scalability. Fault tolerance Designed to provide % uptime, the Mobile Device Manager fault-tolerant architecture ensures that there is no single point of failure in the system. Internationalization Motive Mobile Device Manager supports user input in all languages supported by the UTF-8 encoding scheme. The user input in native languages is supported for the following profiles and activities: Bootstrap Rebootstrap with NAP Secure 120 Mobile Device Manager Overview

133 Secure with NAP GPRS NAP WLAN NAP MMS MMS with Proxy Install App Accessing the MDM console The MDM console is a web-based application. To access the MDM console Open a web browser window and access the MDM Console: Accessing the WebLogic Server Console Use the WebLogic Server Console for application server configuration. To access the WebLogic Server Console Open a web browser window and log in to the WebLogic Server Console: Note Use the same user name and password provided when installing the MDM Server. Mobile Device Manager integration with operator systems Motive's Mobile Device Manager is a highly extensible platform utilizing web services to share information with other systems or applications. Web services are exposed as SOAP/XML-based APIs to simplify the integration with CRM and other operator systems. Accessing the MDM console 121

134 Web service APIs The web service APIs allow simple integration with a number of systems for direct access to device management capabilities and information. The Mobile Device Manager provides the following web services: Note Web Services Basic, which consists of only the OAMP Web Service, is included with a standard Mobile Device Manager license. All other web services are included with a Web Services Premium license. OAMP Web Service. Provides operations to manage the activation and deactivation of subscribers and devices, and also to retrieve device information. Device Management Web Service. Provides operations to configure, update, and manage mobile devices over their entire life cycle. My Phone Portal Web Service. Provides device management information and functions for a single device, given a subscriber ID or device ID. Enterprise Portal Web Service. Provides device management information and functions for a set of subscribers or devices. OEM Portal Web Service. Provides operations to allow device manufacturers to upload and manage firmware update packages. Mobile Device Manager data model Understanding the interdependent relationships between the various Mobile Device Manager data elements is fundamental to understanding how device management jobs are performed. MDM Server data elements Data element Subscribers Tenants Manufacturer Model Device Service tag Description Specify the owners of devices who subscribe to mobile services. Specify mobile operators that provide services to their subscribers. Specifies the manufacturer of device models. Defines the specific model type and version of the device. Specifies a subscriber s mobile device. Specifies a descriptive name/value pair that determines the service type to apply to the device. 122 Mobile Device Manager Overview

135 MDM Server data elements (continued) Data element Firmware Updates Profile template Profile mapping Profile Profile assignment Provisioning Requests data elements Firmware update job Device configuration job Discovery job Command script job Workflow job Description Provides computer code distinguished from software by being stored in read-only memory and distinguished from hardware in that they are replaceable. These programming instructions include operating systems, drivers, call processing stacks, roaming instructions, phone book in a mobile device, and so on. Specify the difference between an existing device firmware image and a new firmware image on a device. Defines all attributes of a type of service or application. A set of templates is provided for each device model. For example, an template defines all attributes needed for any service. Maps service or application attributes defined by profile templates to each device model to remove this complexity from tenant operations. Mapping is provided to the model's DDF for DM enabled devices and to configure SMS messages for CP enabled devices. Based on a profile template and created by the tenant, specifies the service and tenant-specific attributes for a service or application. For example, a Yahoo profile (created from the template) includes tenant and service-specific attribute settings for Yahoo (service name, sending/receiving server, mailbox protocol, and so on). Assigns a profile to a device to provision a service or application on the device. Subscriber-specific attributes are specified. For example, user name, password and address are specified when assigning the Yahoo profile to a device. Mobile Device Manager creates an Assign Profile job to send the settings to the device. Updates devices. Configures devices by assigning, deleting, and resending profiles. Discovers DM tree nodes in a device. Executes one or more DM commands. Contains one or more OMA (Open Mobile Alliance) tasks based on rule criteria. Countries, tenants, and subscribers A mobile operator is known as a tenant. Each tenant can be associated with one country. If an operator provides services in multiple countries, a separate tenant is added for each country. Mobile Device Manager supports both a single tenant model and a hosted model in regard to subscribers and tenants. In the single tenant model, all subscribers in the system belong to the same tenant. In the hosted model, multiple tenants are supported. Countries, tenants, and subscribers 123

136 A subscriber is identified with a subscriber ID. A subscriber also has a DM account user name and password used for authenticating DM sessions. Manufacturers, models, and devices A device manufacturer has a set of models, and a model describes the characteristics of a set of devices. A device represents the physical mobile device that belongs to a subscriber. A device is identified by its Device ID, and a device can have a status of either activated or deactivated. For GSM devices, the Device ID is its IMEI code; for CDMA devices, the ESN or MEID is used. Models and updates Updates are specific to a model and can be assigned to one or multiple devices. Depending on the requirements of the update, one or more update paths (single or multiple-step) are made available. Once the operator assigns an update and selects an update path, a provisioning request for a firmware update job is generated. The operator can specify several parameters such as when the update should take place and what the user experience should be, in the provisioning request. Profile templates and profiles Profiles are customizations of particular profile templates. The MDM Server provides the following profile templates: Bookmark Bookmark with NAP CSD NAP Data Sync Data Sync with NAP Data Sync with Proxy Device Lock Device Wipe with NAP GPRS NAP 124 Mobile Device Manager Overview

137 Install App MMS MMS with NAP MMS with Proxy Proxy with NAP Push to Talk Push to Talk with NAP Push to Talk with Proxy Video Streaming Video Streaming with NAP Video Streaming with Proxy Each of these profile templates can be customized to create profiles used to provision parameters for a service or application. For example, the template can be used to create a Yahoo profile with attribute settings specific to Yahoo . Profiles and service tags A service tag is a descriptive name/value pair that determines the type of service that is provided to the device. A service tag can be used by the service provider to list all devices using a particular service. Service tag values are provided when assigning a profile to a device. For the service tag to be available to a device, the profile template needs to be modified. It takes the following parameters: Service tag name. A case-insensitive text name given to the service tag. Value. An alphanumeric string assigned to the service tag. Each profile template uploaded has a service tag associated with it that indicates the type of service the profile template configures on the device. For example: = -yahoo The service tag name is , and its value is -yahoo. Now it would be easy to find all devices using the Yahoo service. Profiles and service tags 125

138 Profile templates, profile mappings, and models For OMA (Open Mobile Alliance) DM enabled devices, profile mappings align the attributes of a profile template to the device model s DM tree nodes. Each device model has a manufacturer defined DDF file that describes its DM tree, supported parameters, and any constraints to that model s capabilities. Therefore, each model would have a profile mapping for each profile template that it supports. For example, a Nokia 7610 model has a mapping for the template (among others), which specifies how each of its attributes maps to management objects on the device. For OMA CP (client provisioning) enabled devices, profile mappings align the attributes of a profile to the known capabilities of the device model. When the profile is assigned to a device, the proper configuration SMS messages are generated and sent to the device based on the device model. Provisioning requests (jobs) This section describes the types of provisioning requests, also known as jobs, that can be created in the MDM Server to be executed on a single device or multiple devices specified as part of a group (defined by matching search criteria). Firmware update jobs. A job that updates the image on a device(s) from one software image to another software image (either to a newer image or to restore an older image). This job type can be assigned to single or multiple devices. Note If you initiate successive firmware update jobs on a device, the updates should be on sequential versions of the firmware; otherwise, the firmware update fails. For example, if your initiate an upgrade from version 1.0 to 2.0 and initiate another upgrade from version 1.0 to 3.0, then this upgrade fails. The correct upgrade path should be from version 1.0 to 2.0 and subsequently from 2.0 to 3.0. Node discovery jobs. DM nodes of the device are displayed (discovered). This type of job is applied to one device at a time. Device configuration (profile assignment) jobs. A device profile configuration can be assigned to a device to configure or update device settings, to restore settings (from an older profile), or to delete settings. The jobs are specifically called Assign Profile, Resend Profile, and Delete Profile. This type of job is applied to one device at a time. Command script jobs. One or more DM commands can be invoked on a particular device. This type of job is applied to one device at a time. Workflow jobs. Workflow jobs are created through the Motive ICE Workflow Designer application. The MDM Server includes some generic workflows that can be used as templates to create other workflows based on the specific needs of the operator. 126 Mobile Device Manager Overview

139 All of these jobs can be scheduled to be run immediately or at a specified future date. Optional notifications or prompts can be sent to the subscriber before executing the job. The status and details of each provisioning request can be tracked because all device activity is logged by the system. MDM Console The MDM Console is the primary point of control for mobile operators and terminal manufacturers who perform OTA (over-the-air) firmware and device configuration updates to their subscribers devices. Through this console, operators are able to plan and manage Mobile Device Manager data required to implement the updates. After populating the MDM Server with property details for data elements such as tenants, subscribers, devices, models, manufacturers, updates, and profiles, the operator uses the stored data to create provisioning requests (or jobs) to provision and update devices in the field. Provisioning requests are scheduled based on the timing requirements of the operator. The URL required to log in to the MDM Console is based on the installation configuration parameters set up by your system administrator. Consult your system administrator to obtain the URL for the MDM Console, as well as a user name and password. MDM Console 127

140 128 Mobile Device Manager Overview

141 This chapter covers: 14 Managing SMSC/Notification Objects Managing Connection Types Managing notification links 129

142 Managing Connection Types You can configure the connection types that are available in your deployment at installation time, using options in the createschema.sh script. You can also configure them after installation, them using a command-line interface. To configure connection types after installation, start the SMSGW console by executing the smsgwmgmt.sh script, found in the smsgwmanagement directory of your installation. After you start it, the script prompts you for some initial values. Enter the following values to continue: Enter Server Host: Enter the hostname of the MDM server. Enter Server Username: Enter the username for your BEA WebLogic administration console. Enter Server Password: Enter the password for your BEA WebLogic administration console. Enter Server Non-SSL Port: Enter the port for your BEA WebLogic administration console. When you correctly enter these values, the script displays a menu, offering you options for adding, removing, or viewing SMSGW types. You can add specific types or add all of the available types at once by selecting the All option. Note You cannot remove a connection type if it is being used by a notification link; if you do, the system displays an error message indicating that a child record for the type was found. Managing notification links This section describes the Notification Links tab of the MDM Console. From this window, the operator can perform management tasks on notification links and associated properties, including viewing links, creating them, editing their properties, and deleting links. Viewing notification links When you click the Notification Links tab in the MDM Console main window, the currently configured links in Mobile Device Manager are displayed on the Notification Links page. The system displays only the links that are asssociated with the tenants associated with the current user. This list is unfiltered; it can be filtered by search criteria. To filter the contents of the Notification Links page, enter search criteria in the left SEARCH panel. Any combination of Notification Id, Notification Link Name, and Connection Type can be used to search for links. The Free Text Search field allows the entry of an arbitrary string that can match any field. The fewer criteria entered, the less constrained the search. 130 Managing SMSC/Notification Objects

143 When done, click Search, and the Notification Links page is updated to display notification links that meet the search criteria. To display a Notification Link Detail page, click an Notification Link ID on the Notification Links page. Detailed properties about the selected notification link are displayed; these vary according to the connection type associated with the notification link. For more information on these properties, see Notification link parameters on page 131. Notification link parameters When a notification link is created, the system parses the provided XML file and displays the parameters contained within it. Each link can have different mandatory and optional parameters, depending on its connection type. The folllowing table details some of the common parameters. Note This is not a comprehensive list; consult the connection protocol documentation for the parameters expected by a particular protocol. Notification link properties Property Notification Link Name Connection Type Protocol Type Description Name of the notification link. Describes the network type, such as GSM or CSDMA The type of protocol, such as KANNEL, WSP, WDP, UDP, or UDP_WIMAX Notification link mandatory parameters Parameter Name HOST_NAME PORT URL USERNAME PASSWORD MAX_RETRIES MESSAGE_EXPIRY_TIME Type string int string string string int int Description Hostname of the notification server Port number of the notification server Path which when combined with the hostname and port creates a URL to the notification server Username for connecting to the notification server Password for connecting to the notification server Number of times the system will resend a failed message Time in seconds which must elapse before the message is considered expired Notification link parameters 131

144 Testing notification links To test a notification link, display the link's Notification Link Detail page by clicking the Notification Link ID on the Notification Links page. Then click the Test Notification Link button. The system displays the Test Notification Link page. Enter values in the Destination Phone Number and Test Message fields, then click the Test Notification Link button. The system sends a test message to the designated phone and then displays a status message, such as Message Status: MESSAGE_DELIVERED Creating or modifying a notification link You can create a notification link, or modify an existing one, by uploading an XML file with appropriate code. This topic describes how to upload a file when creating and when modifying a link. For information on how to set up an appropriate XML file for a notification link, see Notification link XML file structure on page 133. To create a new notification link 1. Click the Notification Links tab in the MDM Console main window. The Notification Links page appears. 2. Click Create Notification Link. The Upload Connection Details XML page appears. 3. Click the Browse button and select an XML file to upload, then click the Upload button. Note For a sample XML file, see the setup data directory in your MDM distribution. If you selected a valid file, the system displays the link properties. If the file was not XML or does not contain valid properties the system displays an error message. 4. Click Confirm to complete the creation operation. To upload connection details 1. Click the Notification Links tab in the MDM Console main window. The Notification Links page appears. 2. Click the Notification Link ID of the notification link to edit. The Notification Link Detail page appears, including the currently defined values of the fields that can be edited. 3. At the bottom of the page, click Edit. The Upload Connection Details XML page appears. 4. Click the Browse button and select an XML file to upload, then click the Upload button. 132 Managing SMSC/Notification Objects

145 If you selected a valid file, the system displays the link properties. If the file was not XML or does not contain valid properties the system displays an error message. 5. Click Confirm to complete the creation operation. Notification link XML file structure Notification links are configured by uploading XML files as described in Creating or modifying a notification link on page 132. This topic describes the XML language used to define notification links and provides examples of it. The XML language defines a name and type for the XML link, then provides for a list of mandatory parameters followed by a list of optional parameters. Mandatory parameter. A parameter which must be supplied when contacting the notification server. Optional parameter. A parameter which may be supplied when contacting the notification server. The message body is one optional parameter. The uploaded files must use the following structure: <?xml version="1.0" encoding="utf-8"?> <connection_details xmlns:xsi=" xsi:nonamespaceschemalocation="/connection_details.xsd"> <name>my Kannel</name> <type>kannel</type> <mandatory_params> <mandatory_param> <param_name>name</param_name> <param_type>type</param_type> <param_value>value</param_value> </mandatory_param>...additional mandatory parameters as needed... </mandatory_params> <optional_params> <optional_param> <param_name>name</param_name> <param_type>type</param_type> <param_value>value</param_value> </optional_param>...additional optional </optional_params> </connection_details> parameters as needed... The following example shows how a Kannel notification link can be configured: <?xml version="1.0" encoding="utf-8"?> <connection_details xmlns:xsi=" xsi:nonamespaceschemalocation="/connection_details.xsd"> <name>testkannel1</name> <type>kannel</type> <mandatory_params> <mandatory_param> Notification link XML file structure 133

146 <param_name>host_name</param_name> <param_type>string</param_type> <param_value>blr-mobility.motive.com</param_value> </mandatory_param> <mandatory_param> <param_name>port</param_name> <param_type>int</param_type> <param_value>13013</param_value> </mandatory_param> <mandatory_param> <param_name>url</param_name> <param_type>string</param_type> <param_value>/cgi-bin/sendsms</param_value> </mandatory_param> <mandatory_param> <param_name>username</param_name> <param_type>string</param_type> <param_value>insignia</param_value> </mandatory_param> <mandatory_param> <param_name>password</param_name> <param_type>string</param_type> <param_value>insign1a</param_value> </mandatory_param> <mandatory_param> <param_name>message_expiry_time</param_name> <param_type>int</param_type> <param_value>30</param_value> </mandatory_param> <mandatory_param> <param_name>max_retries</param_name> <param_type>int</param_type> <param_value>5</param_value> </mandatory_param> <mandatory_param> <param_name>from_number</param_name> <param_type>string</param_type> <param_value> </param_value> </mandatory_param> </mandatory_params> </connection_details> Deleting a notification link To remove a notification link from the Mobile Device Manager, you can delete it. However, once a link is deleted from the system, it cannot be restored and has to be created again. Therefore, before deleting, ensure there are no subscribers or devices associated with the notification link, and ensure there are no pending notifications for subscribers or devices associated with the notification link. To delete a notification link 1. Click the Notification Links tab in the MDM Console main window to display the Notification Links page. 134 Managing SMSC/Notification Objects

147 2. Click the Notification Link ID of the notification link to delete. The Notification Link Detail page appears. 3. At the bottom of the page, click the Delete button. A confirmation page appears. Note If any tenants are linked to the notification link, the Delete button is disabled. You must edit the tenant to remove the link to the notification link before deleting the notification link. 4. If there are no subscribers or devices associated with the notification link, click the Confirm button to complete the delete operation. The notification Link page is again displayed. The deleted notification link does not appear. Deleting a notification link 135

148 136 Managing SMSC/Notification Objects

149 This chapter covers: 15 Managing Tenants About tenants Viewing tenants Creating a tenant Troubleshooting tenant creation Editing tenant properties Deleting a Tenant Managing Countries Managing Profiles 137

150 This chapter describes the Tenants configuration tab of the MDM Console. From this window, the operator can perform management tasks on tenants and associated properties, including viewing tenants, creating tenants, editing tenant properties, and deleting tenants. Note At least one tenant must exist before any subscribers can be created in the MDM Server. In addition to these tasks, see the following topics for details on submenus in the Tenants tab: Manage Countries. See Managing Countries on page 144. Upload Profile Metadata. See Uploading a profile metadata file on page 256. Manage Profile Templates. See Managing profile templates on page 231. Upload Profile Service. See Uploading a profile service file on page 257. About tenants In the MDM Console a tenant represents the set of subscribers, devices, and CSRs associated with a particular company or subset of a company. Tenants allow a service provider to manage devices and subscribers for several companies within the same device management system, without making information about individual tenants available to other tenants in the same system. Many settings are tenant-specific. Prerequisites. applications: Before you can create a tenant in the MDM console, you must complete the following steps in other Create a global role for the tenant in the WebLogic Server Console. Assign the new role to groups and users in the WebLogic Server Console so that one or more users are associated with the tenant. Create a notification link for the tenant. There is a one-to-one correspondence between notification links and tenants: each notification link can only be linked to one tenant. Filtering. All system data is filtered by tenant. The system displays only the tenants and devices associated with the current user, so the user can only work on devices for the tenants he is associated with. The system displays only the tenants associated with the currently logged-in user; furthermore, each user of the MDM Console must be associated with one or more tenants 138 Managing Tenants

151 Viewing tenants When you click the Tenants tab in the MDM Console main window, the system displays the tenants associated with the current user in a list on the Tenants page. This list is unfiltered; it can be filtered by search criteria. For information on the relationship between users and tenants, see About tenants on page 138. To filter the contents of the Tenants page, enter search criteria in the left SEARCH panel. Any combination of Tenant Id, Tenant Name, and Country can be used to search for tenants. The Free Text Search field allows you to enter an arbitrary string that could match any field. The fewer criteria you enter, the less constrained your search will be. When done, click Search, and the Tenants page is updated to display tenants that meet the search criteria. To display a Tenant Detail page, click a tenant ID on the Tenants page. Detailed properties about the selected tenant are displayed, depending on the notification type associated with the tenant. Note For details on tenant properties, see Tenant properties on page 141. Creating a tenant When you create a tenant, you must also create a NAP profile for it to ensure that the tenant s notification protocol is properly set up and configured. You can set these properties (by creating NAP for bootstrap or Proxy for bootstrap profiles) during the tenant creation process, or afterward: During the tenant creation process, the system prompts you to create a NAP profile. If you do not create the NAP profile during the tenant creation process, create it afterward by selecting the tenant and then clicking the Manage Profiles button to enter the profile creation process. The system filters the data displayed for a user based on the tenants associated with that user, displaying only tenants and devices associated with the currently logged-in user. Mobile Device Manager supports Short Message Peer-to-Peer (SMPP) notifications, the standard messaging protocol for SMS enabled devices. To create a tenant 1. Create a role for the new tenant in the WebLogic Server Console. Create a role for the tenant and set the predicate or group membership of the role so that appropriate users are members of the role. The MDM console will not list a tenant for a user who does not have a role with the same name as that tenant. Viewing tenants 139

152 Note You must use the same name for the role and the tenant; this is how the console determines a link between the two. 2. Log into the MDM Console as a user who has the new role. Open a web browser window and access the MDM Console: 3. Create a notification link for the tenant. See Creating or modifying a notification link on page 132. Each tenant must have its own notification link. 4. Click the Tenants tab in the MDM Console main window to display the Tenants page. 5. Click Create Tenant to display the Create Tenant page. 6. Enter the general tenant properties, which are described in Tenant properties on page Click Continue to display the Notification Properties page. 8. Specify values for the remaining properties to properly configure notification for the tenant. Among other things, these properties must be defined in order to bootstrap device(s). See Tenant properties on page 141 for descriptions. Click Continue when done. If the tenant is a WiMAX tenant (because you chose a notification link with the WiMAX connection type), the system displays the Create AAA Server Details page. 9. Enter AAA configuration values. Enter appropriate values for the AAA URL,User Name, and Password. Then click Continue. 10. The system displays the confirmation page. Review the displayed tenant details. Click Confirm to complete the operation. A page appears that states the tenant has been successfully created, and offering a list of NAP profile templates to choose from. 11. Select a NAP profile template and click Continue, or select Cancel to skip associating a NAP profile with this tenant. The NAP profile is used to bootstrap devices for the tenant. If you select Cancel, the tenant creation process is complete, but you cannot bootstrap devices for the tenant until a NAP profile exists. Use one of the system NAP profile templates to create a NAP profile. 140 Managing Tenants

153 GPRS NAP template. Used when defining an access point that is accessed through the GSM GPRS network. CSD NAP template. Used when defining an access point that is accessed through the GSM CSD network. WLAN NAP template. Used when defining an access point that is accessed through a WLAN network. WLAN NAP with WPA template. Used when defining an access point that is accessed through a WLAN network using WPA encryption. 12. Configure the NAP template attributes, as described in GPRS or CSD NAP template attributes on page 142. When finished, click the Create button. Note Consult the tenant s network administrator for further assistance in configuring the notification parameters. Tenant properties Property Name a URI External Id a Country a DM Server Authentication Description Name of the tenant. Must match a role defined in the WebLogic Server Console. Tenant company URL. Used to send with notification messages. Unique ID of the tenant. Select a country for the tenant. Choices are None: no authentication. Basic: requires username and password. Digest: uses MD5 digest. HMAC: uses HMAC authentication. NAP for bootstrap b Lists the NAP used when bootstrapping a device fro this tenant. Phone number options Add Country Code Add Prefix(+) If checked, the system adds the country code to phone numbers used to notify devices for this tenant. If checked, the system adds the prefix (+) to phone numbers used to notify devices for this tenant. Notification options Creating a tenant 141

154 Tenant properties (continued) Property Timeout to enqueue Bootstrap (sec) Timeout to enqueue Notification (sec) Maximum Notification/Bootstrap Retries Description Number of seconds before bootstrap message is sent again. Number of seconds that the notification message is queued before a timeout. Number of times the notification message is resent before giving up. a Search fields to filter the contents of a displayed Tenants page. b Edit only field. Not shown when creating a tenant. GPRS or CSD NAP template attributes Attribute Name Profile Name NAP ID Display Name Bearer Direction NAP Address Address Type Call Type (CSD NAP only) Link Speed (CSD NAP only) DNS Address Internet Locked Authentication Type Authentication Username Authentication Password AuthPrompt Description Name of the profile template ID value for the NAP String of the profile being defined Possible values are Outgoing and Incoming IP address for the NAP Possible values are: APN, E164, IPV4, and IPV6 Bearer call type Bearer link speed IP address of the domain name server Can be set to Yes or No to enable/disable internet access for this profile Set to Yes to lock, or No to unlock this profile Possible values are: CHAP, MD5, or PAP. The default value is PAP. Login name Password associated with the login name Can be set to Yes or No to enable/disable prompting for authorization for this profile. Troubleshooting tenant creation This topic addresses potential problems with tenant creation. My new tenant does not appear in the list of tenants on the Tenants tab. system but cannot list it or view it, the problem is likely a permissions issue: If you added the tenant to the 142 Managing Tenants

155 Verify that you created a role in the WebLogic Server Console with the same name as the tenant. If an appropriate role exists, then make sure the user you are logged in as in the MDM console has that role. Check the predicate properties or group membership of the role, or log in as a different user who has the appropriate role, and you should see the tenant. To verify that the tenant was created, inspect the INSG_CARRIER table in the MDM database. I could not create a NAP profile after creating my tenant. are mapped to the appropriate tenant. Verify that profile templates for a NAP exist, and Editing tenant properties Tenant properties are described in Tenant properties on page 141. To edit tenant properties 1. Click the Tenants tab in the MDM Console main window. The Tenants page appears. 2. Click the tenant ID of the tenant to edit. The Tenant Detail page appears, including the currently defined values of the fields that can be edited. 3. At the bottom right of the page, click the Edit button. The Modify Tenant page appears. 4. Modify the fields, as necessary. See Tenant properties on page 141 for a description of tenant properties. 5. Click the Continue. The Notification Properties page appears. 6. Modify the Notification Properties fields as necessary. Click Continue. 7. Specify values for the remaining properties to properly configure notification for the tenant. Among other things, these properties must be defined in order to bootstrap device(s). See Tenant properties on page 141 for descriptions. Click Continue when done. If the tenant is a WiMAX tenant (because you chose a notification link with the WiMAX connection type), the system displays the Create AAA Server Details page. 8. Enter AAA configuration values. Enter appropriate values for the AAA URL,User Name, and Password. Then click Continue. 9. Any pending notifications to any devices or subscribers that would be affected by the modifications for the tenant are displayed. Editing tenant properties 143

156 Note Modifying a tenant with pending notifications to subscribers disrupts the pending notifications. Wait until all pending notifications are completed before editing tenant properties. 10. Click Confirm to complete the edit operation. Deleting a Tenant To remove a tenant from the Mobile Device Manager, you can delete it. However, once a tenant is deleted from the system, it cannot be restored and has to be created again. Therefore, before deleting, ensure there are no subscribers or devices associated with the tenant, and ensure there are no pending notifications for subscribers or devices associated with the tenant. To delete a tenant 1. Click the Tenants tab in the MDM Console main window to display the Tenants page. 2. Click the tenant ID of the tenant to delete. The Tenant Detail page appears. 3. At the bottom of the page, click Delete. A confirmation page appears. 4. If there are any associated subscribers or devices with the tenant, click the linked number of subscribers or devices to review the subscribers and devices that would be deleted if you deleted the tenant. Note Deleting a tenant with associated subscribers, devices, and provisioning requests also deletes the associated subscribers and devices. Click Continue if you still wish to delete the tenant or Cancel to cancel the deletion. 5. If there are no subscribers or devices associated with the tenant, click Confirm to complete the delete operation. The Tenant page is again displayed. The deleted tenant does not appear. Managing Countries This section describes the Countries subtab. From this page, the operator can define country codes and country-based dialing requirements. Given the differences in dialing patterns between countries, per country numbering patterns should be defined in the MDM Server. 144 Managing Tenants

157 Country file format Countries are used as an attribute of tenants. Country lists, supported by a particular tenant, are imported and exported using a CSV (comma separated values) text file. Each country in the file must include attributes (as described in Country file format on page 145), and each attribute must appear in the file in the order shown, separated from the next attribute by a comma. The following sample file contains a list of countries: 100,US,1,United States,1,1,1,1 101,GB,44,United Kingdom,0,1,1,1 102,FR,33,France,0,1,1,1 103,IT,39,Italy,0,1,1,1 104,DE,49,Germany,0,1,1,1 105,SG,65,Singapore,,1,0,1 106,CN,86,China,0,1,1,1 107,ES,34,Spain,0,1,1,1 108,HK,852,Hong Kong,0,1,1,1 109,TH,66,Thailand,0,1,1,1 110,SE,46,Sweden,0,1,1,1 111,CA,1,Canada,1,1,1,1 112,IN,91,India,1,1,1,1 113,MX,52,Mexico,0,1,1,1 Note To add countries to the database, export the current list of countries to a CSV file by using Export, edit the file to add the new countries to the file, and import the file using Load countries from a CSV File. Country file format Order 1 2 Field country ID ISO code Description An internal number ID assigned to the country. ISO code value for the country based on ISO by the International Organization for Standardization (ISO) at country code country name trunk code display country code International dial code, as defined by the International Telecommunication Union (ITU). For example, 1 for US and 44 for UK. Name of the country in English text. The number entered before an area code when dialing long distance numbers within a country. In the console, it is used to parse phone numbers appropriately when they are entered in the search field. For example, 0 for UK and 1 for US. Boolean that indicates whether the country code appears to the subscriber. Possible values are: 1 for true 0 for false Country file format 145

158 Country file format (continued) Order 7 Field display trunk code Description Boolean that indicates whether the trunk code appears to the subscriber. Possible values are: 1 for true 0 for false 8 Display Prefix Number Boolean that indicates whether the + is used to display a phone number to the subscriber. Possible values are: 1 for true 0 for false Uploading countries To import a countries file 1. Click the Tenants tab, then click Manage Countries on the Tenants page. The Manage Countries page appears. 2. Click the Browse button to locate the country CSV file to upload. Note When a country file is imported, countries currently in the database that are not in the file are deleted, including any tenants belonging to the country. Countries in the database that appear in the country file are updated with the data in the file. 3. Click the Load button after the country file is specified. The confirmation page appears summarizing the country file details. 4. Click Confirm to accept the displayed country details, Cancel to return to the View Tenants page, or Back to return to the Manage Countries page. 5. A confirmation page appears when the country file upload is complete. 146 Managing Tenants

159 Exporting countries To export a country file (list of countries) 1. Click the Tenants tab, then click Manage Countries on the Tenants page. The Manage Countries page appears. 2. Click Export to save the country file on the local file system. Managing Profiles This section describes the management of profiles, which are used to configure devices in a model-independent manner. Understanding profiles Profiles are created by tenants to provision or configure subscribers devices. More specifically, a profile is a tenant-specific collection of attribute names and values created to provision a service or application. Profiles are based on profile templates provided with the MDM Server. For example, a Hotmail profile created using the template has Hotmail-specific values for receiving/sending server addresses, mailbox protocol, and so on. A Yahoo profile, created from the same template, has Yahoo-specific values. Subscriber-specific values are specified when the profile is assigned to a subscriber/device. Other aspects of a profile are described as follows: profile template Defines the structure and attributes of a type of profile supported by the Mobile Device Manager. For example, the Mobile Device Manager provides templates for , MMS, GPRS NAP, and so on. The profile template specifies the structure and attributes required for an service. The profile template also specifies which attributes are subscriber-specific. For more information, see Managing profile templates on page 231. DDF (Device Description Framework) Describes the structure of the device tree in every DM enabled device model. Tree nodes, or management objects, define the device s capabilities and configurable attributes. DDFs are distributed by the manufacturer. For more information, see Managing DDFs on page 258. profile mapping Maps the attributes of a profile template to device management tree nodes (defined by the DDF) for a particular DM-enabled device model. Therefore, each model would have a profile mapping for each profile template that it supports. For example, a Nokia 7610 model has a mapping for the template, which specifies how each attribute maps to the management objects on the device. For CP enabled device models, the template attributes are mapped to SMS messages used to configure the settings on the device. For more information, see Managing profile mappings on page 260. Exporting countries 147

160 profile assignment Assigns a profile to a device so that a provisioning request is created to configure the device for the service specified by the profile. For example, a Yahoo profile is assigned to a device to configure it for Yahoo . Because the profile is now being associated with a particular device/subscriber, the subscriber-specific information is specified during the profile assignment. A device has profile assignments for each configured service or application. For more information, see Managing profile assignments on page 173. Profiles are based on profile templates defined by a profile metadata file provided by Motive Product Group. As new profile templates become available, Motive Consulting Services sends updated profile metadata files with additional template definitions. Once the profile metadata file has been uploaded to the MDM Server (see Uploading a profile metadata file on page 256), profiles can be created. Creating a profile To create a profile for a specific tenant 1. Click the Tenants tab in the MDM Console main window. The Tenants page appears. 2. Click a tenant ID for which you want to create a profile. The Tenant Detail page appears. 3. Click Manage Profiles at the bottom of the page. The Manage Profiles page appears. If no profiles have been created yet, no profiles are listed. 4. Click Create Profiles and the Create Profile page appears, listing the available profile templates from which to create a profile. The MDM Server is prepopulated with the following profile templates: Bookmark Template Bookmark with NAP Template CSD NAP Template Data Sync Template Data Sync with NAP Template Data Sync with Proxy Template Device Lock Template Device Wipe Template with NAP Template -WM 148 Managing Tenants

161 GPRS NAP Template Install App Instant Messaging Instant Messaging with Nap Instant Messaging with Proxy MMS Template MMS with NAP Template MMS with Proxy Template MS wifi Proxy with NAP Template Push to Talk Template Push to Talk with NAP Template Push to Talk with Proxy Template Secure Video Streaming Template Video Streaming with NAP Template Video Streaming with Proxy Template 5. Select the desired template to create a profile for the tenant, then click Next. Depending on the selected template, required profile attributes are displayed for definition. Mandatory attributes are tagged with a red * (asterisk) next to the field name. 6. Enter a profile name and any required and optional values in the template page. For more details about the attributes that define these templates, see Managing profile templates on page When complete, click Create. A confirmation page appears. All associated attributes and values for the profile are displayed. 8. Review the field details for the profile you are creating, then click Confirm to accept the values and save the defined profile. The Profile Detail page appears confirming the profile was created. Creating a profile 149

162 Modifying a profile To modify a profile 1. Click the Tenants tab in the MDM Console main window. The Tenants page appears. 2. Click the tenant ID for which you want to modify the profile. The Tenant Detail page appears. 3. Click Manage Profiles at the bottom of the page. The Manage Profiles page appears, listing previously created profiles for the selected tenant. 4. Click the name of the profile that you want to modify, and the Profile Detail page appears. 5. Click Modify, and the Modify Profile Detail page appears. 6. Modify the editable fields as appropriate. Attributes displaying a red * (asterisk) are mandatory. Click Submit when done. 7. A confirmation page appears. Click Confirm to complete the profile modification. Deleting a profile To delete a profile 1. Click the Tenants tab in the MDM Console main window. The Tenants page appears. 2. Click the tenant ID for which you want to delete the profile. The Tenant Detail page appears. 3. Click Manage Profiles at the bottom of the page. The Manage Profiles page appears, listing profiles previously created for the selected tenant. 4. Click the name of the profile that you want to delete, and the Profile Detail page appears. 5. Click Delete, and the Delete Profile page appears. If applicable, devices that the profile has been assigned to are shown at the base of the page. If the profile is yet to be assigned, this is stated instead. Note When you delete a profile that has profile assignments, the profile and profile assignments are deleted simultaneously. 6. Click Confirm, and the profile and any associated profile assignments are deleted. The Manage Profiles page is again displayed, and the deleted profile is no longer listed. 150 Managing Tenants

163 This chapter covers: 16 Managing Subscribers Viewing subscribers Creating subscribers (bootstrap) Changing the status of a subscriber 151

164 This chapter describes the Subscribers tab, which allows you to perform management tasks for subscribers assigned to devices. Note At least one tenant must exist before any subscribers can be created in the MDM Server. See Chapter 15, Managing Tenants on page 137 for more details. Viewing subscribers Subscribers configured in Mobile Device Manager are viewable as a list that can be filtered by search criteria. When you click the Subscribers tab in the MDM Console main window, all currently configured subscribers are displayed on the Subscribers page. This list is unfiltered. To filter the contents of the Subscribers page, enter search criteria in the left SEARCH panel. The fewer criteria entered, the less constrained the search. Note See Subscriber Detail properties on page 152 for descriptions of the search fields. The Free Text Search field allows the entry of an arbitrary string that can match any search field. When done, click Search, and the Subscribers page is updated to display subscribers that meet your search criteria. To display a Subscriber Detail page, click on a subscriber ID on the Subscribers page. The subscriber properties are described in the Subscriber Detail properties on page 152 table. Subscriber Detail properties Property External Subscriber Id Subscriber ID Network ID Tenant State #Devices Description Name of the subscriber who has a service subscription with the tenant. Value used to identify the subscriber. For some devices, this is the phone number. For others, it maybe the IMEI number. If you use the subscriber ID as a search criteria, you can enter one or more IDs with multiple IDs separated by spaces. A unique number that designates the subscriber. This number is used for provisioning in network elements. For GSM networks, this is the IMSI number; for CDMA network, this is the ESN/SPC number. Name of the tenant that hosts the subscriber s service. State of the subscriber in Mobile Device Manager. Possible values are Activated and Deactivated. The number of devices provisioned to the subscriber. 152 Managing Subscribers

165 Subscriber Detail properties (continued) Property Device ID Manufacturer Model Name Active For Subscriber Status Description A unique number that identifies the device. Manufacturer of the device. Model of the device. Indicator of whether the device is active for the subscriber. Only one of a subscriber s devices can be active at a time, and only the active device can be managed. Possible values are Yes and No. This value is independent of a device s status, which is indicated by Status. Status of a device from the MDM Server perspective. Possible values are Activated and Deactivated. Creating subscribers (bootstrap) In the single tenant model, the tenant s OAMP or CRM systems create subscribers in Mobile Device Manager by using the OAMP Web Service API. Note At least one tenant must exist before any subscribers can be created in the MDM Server. See Chapter 15, Managing Tenants on page 137 for more details. The following parameters can have values in all languages supported by the UTF-8 encoding scheme: Tenant External ID Manufacturer External Id Model Name To create a subscriber for a Nokia device 1. Click the Subscribers tab in the MDM Console main window to display the Subscribers page. 2. Click Add Subscriber. 3. Enter values for Phone Number and Tenant External ID. 4. Provide a value for Device Id, or provide values for Manufacturer External Id and Model Name. 5. Select a Bootstrap Type. Creating subscribers (bootstrap) 153

166 To prepare (bootstrap) the subscriber's device for both DM and CP operations, select the DM and CP Operation button. If the device only supports CP, or you only want to enable CP, select CP Operation. 6. Click Confirm. To create a subscriber for a Windows Mobile device 1. Click the Subscribers tab in the MDM Console main window to display the Subscribers page. 2. Click Add Subscriber. 3. Enter values for Network ID, Phone Number, and Tenant External ID. 4. Provide values for Manufacturer External Id and the Model Name. 5. Select a Bootstrap Type. To prepare (bootstrap) the subscriber's device for both DM and CP operations, select the DM and CP Operation button. If the device only supports CP, or you only want to enable CP, select CP Operation. 6. Click Confirm. Changing the status of a subscriber Subscribers in Mobile Device Manager can have one of two types of status: activated or deactivated. In order to update a device, the device s subscriber must be activated. Subscribers are automatically activated when they are created. However, sometimes a subscriber s service account is temporarily disabled because of extended absence or billing issues. In these cases, the subscriber might be deactivated. When the subscriber s service is restored, the subscriber is activated again. Activating a subscriber To activate a subscriber 1. Click the Subscribers tab in the MDM Console main window to display the Subscribers page. 2. Click the subscriber ID to activate the subscriber. The Subscriber Detail page appears. The subscriber s status shows Deactivated. 3. Click Reactivate. After reactivating, a confirmation page states that the subscriber has been reactivated. 154 Managing Subscribers

167 Deactivating a subscriber To temporarily deactivate a subscriber's account Note If the subscriber is deactivated, all of the subscriber s devices are also deactivated. They cannot download from the server or receive notifications. 1. Click the Subscribers tab in the MDM Console main window to display the Subscribers page. 2. Click the subscriber ID to deactivate the subscriber. The Subscriber Detail page appears. The subscriber s status shows Activated. 3. Click Deactivate. After deactivating, a confirmation page states that the subscriber has been deactivated. Deleting a subscriber To delete a subscriber Note If the subscriber is deleted, all of the subscriber s devices are also deleted. 1. Click the Subscribers tab in the MDM Console main window to display the Subscribers page. 2. Click the subscriber ID. The Subscriber Detail page appears. 3. Click Delete. The system asks you to confirm that you want to delete the subscriber. After deleting, a confirmation page states that the subscriber has been deleted. Deactivating a subscriber 155

168 156 Managing Subscribers

169 This chapter covers: 17 Managing Models Viewing models Creating a model Editing model properties Deleting a model Updating CP models Managing Manufacturers 157

170 This chapter describes the Models tab, which allows you to perform management tasks for models that are associated with your devices. In addition to the model management topics described here, also refer to Uploading a profile metadata file on page 256, which describes a key step to model management. The profile metadata file includes profile template mappings that directly correlate to model device management tree nodes. If the metadata files has not been uploaded, model-independent device management is not possible. Viewing models Models configured in the Mobile Device Manager are viewable as a list that can be filtered by search criteria. When you click the Models tab in the MDM Console main window, all currently configured models are displayed in the Models page. This list is unfiltered. To filter the contents of the Models page, enter search criteria in the left SEARCH panel. The fewer criteria entered, the less constrained the search. Note See Model Detail properties on page 158 for descriptions of the search fields. The Free Text Search field allows the entry of any arbitrary string that can match any search field. When done, click Search, and the Models page is updated to display models that meet your search criteria. To display a Model Detail page, click a model name on the Models page. The model properties are described in Model Detail properties on page 158. Model Detail properties Property Model Name Description Manufacturer Model Id TACs Manufacturer Description Name that uniquely identifies the model. Long description of the model type. ID assigned by the manufacturer of the model, which is unique for models for the same manufacturer. TAC codes for the model. The TAC code is the first 8 digits of the Device ID number, which indicates the device model. Multiple TAC codes should be separated by a comma (,). Name of the manufacturer. If the correct manufacturer is not available, see Creating a manufacturer on page Managing Models

171 Model Detail properties (continued) Property #Devices Description Number of devices registered in Mobile Device Manager that matches this model type. Note This field is only displayed on the Model Detail page, not when creating or editing model properties. The remaining properties are for DM models only. OMA DM Version DM Server Authentication Currently supported OMA DM versions are 1.1 and 1.2. The type of DM server authentications. Possible values are: Use Tenant Setting. Uses the specified tenant setting for server authentication. None. No authentication. Basic. HTTP authentication in which the subscriber authenticates by presenting credentials consisting of a user name/password pair. See RFC2617 ( Digest. HTTP authentication in which the subscriber authenticates by presenting credentials consisting of an MD5 digest. See RFC2617 ( rfc2617.html). HMAC. A mechanism for the subscriber to authenticate by using cryptographic hash functions. See RFC 2104 ( Bootstrap Type Type of bootstrap notification. Possible values are: WAP. This profile defines a number of parameter extensions to the WAP Provisioning Content Format. This profile also defines how these and other parameters are mapped in to the DM management object. This type is recommended. plain. This profile specifies how the SyncML DM management object can be bootstrapped using a SyncML DM format. For security, it leverages the methods developed for WAP Provisioning. Use Encoding for Bootstrap Message The bootstrap message content-type is Encoded when this box is checked. Note If you do not set this value by checking the box, the device user is not prompted to enter a PIN number, and the mobile device displays a message stating: the message received is from an untrusted server Viewing models 159

172 Model Detail properties (continued) Property Use New Nonce per package Always support Large Objects Supports HTTPS The OMA DM URL Other DM properties Description Credentials computed for HMAC authentication use the nonce sent in each package if this box is checked. Some models support Large Objects. To always support large objects, check this box. Check this box if the model supports the HTTPS protocol. URL for device management. DM properties that are to be set differently than the default should be added here: supportsatomic. Either true or false; the default is true. Use the following properties when creating the Windows Mobile model: userealuuid=true;supportsatomic=true; autocreatesdynamicchildnodes=true; Firmware Version Node Node for where the firmware version is listed. The default is:./devdetail/fwv FOTA Download Method Type of FOTA (firmware over-the-air) download. Possible values are: FOTA Download Not Supported. Inline Download. Alternate Download. If you select FOTA Download Not Supported, then the corresponding manufacturer name and/or model are not displayed in the search for devices in the Updates tab and in the searches in Provisioning->Assign Image to Device and Provisioning->Assign Image to Multiple Devices. This also applies to Device Detail->Assign Image. If you select Inline Download or Alternate Download, then you also have to provide the values for these fields: Firmware Update Node The Node to Replace during a FOTA operation The Node to Exec during a FOTA operation The Node that has the result of the FOTA operation 160 Managing Models

173 Model Detail properties (continued) Property Firmware Update Node The Node to Replace during a FOTA operation The Node to Exec during a FOTA operation The Node that has the result of the FOTA operation Bootstrap Template Description In addition to these fields, you must provide the firmware upgrade package by using Updates->Upload Update Packages for the models to be displayed in the search. The root node that is to be replaced during the FOTA. See FOTA Download Method for more information. The node containing the image binary data. See FOTA Download Method for more information. The note that triggers the firmware upgrade. See FOTA Download Method for more information. The node showing the success or failure of the upgrade operation. See FOTA Download Method for more information. A template that accommodates variations required by the implementation of some model s bootstrap process. Templates for both plain and WAP bootstrap types define parameter values for various bootstrap characteristics. For examples of WAP and plain bootstrap templates, see Bootstrap Template Examples on page 262. At the bottom of the Model Detail page, the buttons for functions that may be performed on the selected model are listed: Manage DDF. Uploads manufacturer-specified device definition files (DDFs) for a model s supported services and features. Once the files are on the MDM Server, you can view them in a hierarchical tree format. See Managing DDFs on page 258 for more details. Manage Profile Mappings. Displays the profile mapping details for a particular model. The model mapping shows the node relative paths for all defined attributes defined by a particular profile. In addition, the generic profile template can also be viewed, which is unmapped, yet shows the details of each profile attribute (that is, attribute types, default values, whether multi-values, user attributes, displayed, required, or unique values). See Modifying a profile on page 150 for more details. Edit. Edits the model details. See Editing model properties on page 162. Delete. Deletes the model. See Deleting a model on page 162. Creating a model To create a DM model 1. Click the Models tab in the MDM Console main window to display the Models page. Creating a model 161

174 2. Click Create Model to display the Create Model page. 3. Enter the model properties as described in Model Detail properties on page 158. When done, click Save. 4. A confirmation page appears. Review the displayed model details. Click Confirm to complete the operation. The model completion page appears. After you create the model, you should upload the DDF and then a profile metadata file as described in: Uploading a DDF File on page 259 Uploading a profile metadata file on page 256 Editing model properties All model definitions include the following editable properties: Name, Description, Manufacturer Model ID, and release date. To edit model properties 1. Click the Models tab in the MDM Console main window to display the Models page. 2. Click the name of the model to edit. The Model Detail page appears and includes the currently defined values of the editable fields. 3. Click Edit to display the Edit Model page appears. 4. Enter new property information for the model by referring to Model Detail properties on page 158. Then click Update to display the edit confirmation page. 5. Click Confirm to complete the edit operation. The Model Detail page is again displayed. Deleting a model Models that are no longer supported by Mobile Device Manager should be deleted from the system. Note Deleting a model also deletes the associated devices and updates. Currently scheduled provisioning requests involving these devices are also deleted. Only delete the model if you are absolutely sure that this is what you intend. 162 Managing Models

175 To delete a model 1. Click the Models tab in the MDM Console main window to display the Models page. 2. Click the name of the model to delete. The Model Detail page appears. 3. Click Delete. A confirmation page appears. 4. If there are no devices associated with the model, click Confirm to complete the delete operation. 5. If there are any devices associated with the model, these are highlighted: a. Click the linked number of devices to review what would be deleted if you deleted the model. b. Click Continue if you still want to delete the model, or Cancel to cancel the deletion. 6. If you continued when there are associated devices, a second confirmation page appears. Click Confirm to delete the model. Updating CP models Motive certifies new CP (client provisioning) models as they become available from the manufacturers, and Motive provides updates based on your service agreement. The MDM Server is updated by uploading an XML file provided by Motive Product Group (the file has a.upgrade extension. To update CP models 1. Click the Models tab in the MDM Console main window to display the Models page. 2. Click Update CP Models. 3. Enter the path and filename, or click the Browse button to select the appropriate upgrade file. 4. Click Upload at the bottom of the page to upload the file. If there is an error when loading the file, an error message appears. Contact Motive Customer Support for a new file or to receive help with the update. Managing Manufacturers This section describes the Manufacturers subtab, which allows you to perform management tasks for manufacturers that own a set of models. Updating CP models 163

176 Viewing manufacturers Manufacturers configured in Mobile Device Manager are viewable as a list that can be filtered by search criteria. When you click the View Manufacturers link in the Models tab (on the MDM Console main window), all currently configured manufacturers are displayed on the Manufacturers page. This list is unfiltered. To filter the contents of the Manufacturers page, enter search criteria in the left SEARCH panel. The fewer criteria entered, the less constrained the search. Note See Manufacturer Detail properties on page 164 for descriptions of the search fields. The Free Text Search field allows the entry of any arbitrary string that can match any search field. When done, click Search, and Manufacturers page is updated to display manufacturers that meet your search criteria. To display a Manufacturer Detail page, click a manufacturer name on the Manufacturers page. The manufacturer properties are described in Manufacturer Detail properties on page 164. Manufacturer Detail properties Property Manufacturer External Id Description #Models Description Name of the manufacturer External ID of the manufacturer Free text description of the manufacturer Number of models associated with this manufacturer Creating a manufacturer To create a manufacturer 1. Click the View Manufacturers link in the Models tab (on the MDM Console main window) to display the Manufacturers page. 2. Click Create Manufacturer to define a new manufacturer in the system. The Create Manufacturer page appears. 3. Enter manufacturer information for the displayed fields, which are described in Manufacturer Detail properties on page 164. Click Continue when done. 4. A confirmation page appears. Click Confirm to complete the operation. A page appears that states the manufacturer has been successfully created. 164 Managing Models

177 Deleting a manufacturer Manufacturers that are no longer supported by Mobile Device Manager should be deleted. Note Deleting a manufacturer with associated models or devices also deletes the associated objects. Currently scheduled provisioning requests involving these models or devices are also deleted. Delete the manufacturer only if you are absolutely sure that this is what you intend. To delete a manufacturer 1. Click the View Manufacturers link in the Models tab (on the MDM Console main window) to display the Manufacturers page. 2. Click the manufacturer name to delete. The Manufacturer Detail page appears. 3. Click Delete. A confirmation page appears. 4. If there are no models or devices associated with the manufacturer, click Confirm to complete the delete operation. 5. If any models or devices are associated with the manufacturer, these are highlighted: a. Click the linked Model Name of a model or device to review what would be deleted if you deleted the manufacturer. b. Click Continue if you still want to delete the manufacturer, or Cancel to cancel the deletion. 6. If you continued when there are associated models or devices, a second confirmation page appears. Click Confirm to delete the manufacturer. Deleting a manufacturer 165

178 166 Managing Models

179 This chapter covers: 18 Managing Devices Viewing subscriber devices Bootstrapping or rebootstrapping a device Creating a device Changing the status of a device Clearing jobs for a device Editing device properties Deleting a device Managing profile assignments Scheduling device management jobs Discovering a device node Sending a command script to a device Assigning an image to a device Assigning an image to multiple devices Managing workflows 167

180 This chapter describes the Devices tab, which allows you to perform tasks on devices that are provisioned to your subscribers. Viewing subscriber devices Devices configured in Mobile Device Manager are viewable as a list that can be filtered by search criteria. When you click the Devices tab in the MDM Console main window, all currently configured devices are displayed in the Devices page. This list is unfiltered. To filter the contents of the Devices page, enter search criteria in the left SEARCH panel. The fewer criteria entered, the less constrained the search. Note See Device Detail page properties on page 168 for descriptions of the search fields. The Free Text Search field allows the entry of any arbitrary string that can match any search field. When done, click Search, and the Devices page is updated to display devices that meet your search criteria. To display a Device Detail page, click a Device Id on the Devices page. Detailed properties about the selected device are displayed. Properties and buttons on the Device Detail page are described in Device Detail page properties on page 168 and Device Detail page buttons on page 170. Device Detail page properties Property Device ID Phone Number Manufacturer Model Tenant Active for Subscriber Status Description Description A 15-digit device ID. Phone number assigned to this device. If you use the phone number as a search criteria, you can enter one or more phone numbers with multiple phone numbers separated with spaces. Manufacturer of the device s model. Model of the device. Provisioning tenant of the device (and ultimately, the subscriber). Indicator of whether the device is active for the subscriber. Only one of a subscriber s devices can be active at a time, and only the active device can be managed. Possible values are Yes and No. This value is independent of a device s status, which is indicated by Status. Status of a device from the MDM Server perspective. Possible values are Activated and Deactivated. Free text description of the device. 168 Managing Devices

181 Device Detail page properties (continued) Property Current Image Id Description ID of the image currently on the device. Note The Current Image Id and Assigned Image Id values dynamically change as provisioning requests that affect the displayed device details are completed. Assigned Image Id ID of the update image. Note The Current Image Id and Assigned Image Id values dynamically change as provisioning requests that affect the displayed device details are completed. Initial BootstrapType Describes how the device was bootstrapped the first time. Possible values are: DM_Bootstrap. The device was bootstrapped with the DM protocol. Factory_Bootstrap. a customer. The device was bootstrapped at the factory, before being sent to DM Bootstrap CP_Operations. The devices was added to the system as a result of a CP operation, which does not require a bootstrap message. Status of DM Bootstrap. Possible states include: Idle Waiting to send, attempt #X of X Not delivered. Last failed attempt at :44:57 PM Unresponsive Unknown State DM Notification Applied Jobs N/A Status of notification. Possible states are the same as for DM Bootstrap. A list of all pending jobs, including their scheduling information and status. Click the Job ID of any pending job to view its details. Viewing subscriber devices 169

182 Device Detail page buttons Button DM bootstrap Rebootstrap Assign Image Activate and Deactivate Delete Edit Clear Jobs Manage Profile Assignments Enter Node To Discover Enter Command Script Create Workflow Job Display Known Device Tree Description Bootstraps a device to allow it to be managed using DM operations (without bootstrapping, a device is limited to CP operations) Reruns the bootstrap process for a device that has already been bootstrapped. Allows the administrator to create an image update provisioning request for the device. See Assigning an image to a device on page 181 for more details. Allow the administrator to activate or deactivate a device. These buttons are toggled depending on the status of the device. See Changing the status of a device on page 171 for more details. Deletes the device displayed. See Deleting a device on page 173 for more details. Edits the properties of the device displayed. See Editing device properties on page 173 for more details. Cancels all pending provisioning requests (outstanding jobs) for the device. Jobs for the device are displayed on the Provisioning tab. See Chapter 21, Managing Provisioning Requests on page 205 for more details. Allows the administrator to apply a custom profile to the device. See Managing Profiles on page 147 for more details. Allows the MDM Server to discover the device node and is available to anyone with permissions set by the administrator. The root node is./. Other general nodes are./devinfo or./ /xxx (where xxx is the name of a particular account on the device). See Discovering a device node on page 180 for more details. Displays an input area for invoking OMA SyncML commands. See Sending a command script to a device on page 180 for more details. Creates a workflow job. See Creating a workflow job on page 184 for more details. Displays the MDM Server's current knowledge of the Device Management (DM) tree that exists on the phone. See Viewing workflow jobs on page 184 for more details. 170 Managing Devices

183 Bootstrapping or rebootstrapping a device You can bootstrap a device to bring it under management, or you can rebootstrap a device that has already been bootstrapped if the device is not responding. You access these functions from the Device Detail page. Only one of the two functions (DM Bootstrap or Rebootstrap) can be enabled. A device that supports only CP functionality cannot be bootstrapped or rebootstrapped. If a device is DM-enabled, but it has not yet been bootstrapped, the DM Bootstrap button is enabled. If you DM Bootstrap the phone, you can then use both CP and DM functions with the device. Once a device has been DM bootstrapped, it can be rebootstrapped. To bootstrap or rebootstrap a device 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. 3. Click the DM Bootstrap or Rebootstrap (only one of these buttons is enabled). The system displays the DM Bootstrap Device page, which lists some of the device properties. 4. Enter a PIN number in the PIN field, then click the Confirm button. The system displays a Bootstrap Message Sent page. Creating a device Devices are created automatically when a subscriber is created in the MDM Server. The operator s OAMP or CRM system creates subscribers by using the OAMP Web Service API. Note At least one tenant must exist before any subscribers can be created in the MDM Server. See Chapter 15, Managing Tenants on page 137 for more details. Changing the status of a device Devices in the Mobile Device Manager are either activated or deactivated. Bootstrapping or rebootstrapping a device 171

184 Activating a device All new devices added to the Mobile Device Manager need to be activated. In most cases, all devices are activated. Devices that are not activated have a Deactivated status on the Devices page. To activate a device 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. The value of the Status field should be Deactivated. 3. Click Activate. A confirmation page states that the device has been activated. The value of the Status field should now be Activated. Deactivating a device When a device configured in the Mobile Device Manager has reached an end of life status, it should be deactivated. If there is no chance that the device might be used by a subscriber again, it should be deleted from the Mobile Device Manager (see Deleting a device on page 173). To deactivate a device 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. The value of the Status field should be Activated. 3. Click Deactivate. A confirmation page appears. Click Confirm to deactivate the device. The value of the Status field should now be Deactivated. Clearing jobs for a device To cancel jobs for a device 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. The Applied Jobs field lists the pending jobs. 3. Click Clear Jobs to cancel all provisioning requests currently in the queue to be applied to the device. 172 Managing Devices

185 Editing device properties All devices have an optional long description field that provides greater detail about the device. The device description is the only editable property of a device at this time. To edit a device 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. The page displays the current value of the Description field. 3. Click Edit to display the Edit Device page. 4. Enter a new description for the device, then click Update. A confirmation page appears. 5. Click Confirm to perform the edit. Deleting a device Devices that are no longer used can be deleted from Mobile Device Manager. Note A device that has been deleted is automatically recreated if it contacts the server again. To delete a device 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. 3. Click Delete. A confirmation page appears. 4. Click Confirm to complete the delete operation. A page indicates the device has been deleted. Managing profile assignments Managing Profile Assignments includes the following topics, described in greater detail in the following sections. Editing device properties 173

186 Uploading a profile assignments file for multiple devices Profile assignments files are created in order to perform mass updates, by way of a distributed profile, to multiple devices. Properly formatted XML-based profile assignments must be uploaded to the MDM Server so they can be later assigned to devices. For more details on attributes of the profile assignment XML file, see the Assign profiles to devices DTD file. To upload a profile assignments file 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click Upload Profile Assignments to display the Upload Profile Assignments XML File page. 3. Click Browse to locate the profile assignments XML file that has been provided by Motive Product Group. 4. When located, select the file and click Open. The local path to the filename is added to the file input field. 5. Click the Upload button. A confirmation page appears. 6. Click Submit to complete the upload operation. The Devices page appears again with a confirmation message at the top of the page. Assigning a profile to a single device An OMA-compliant device can have one or more profile assignments. To assign a profile to a device 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. 3. Click Manage Profile Assignments to display the Manage Profile Assignments page. If profiles are currently assigned, they are displayed on this page. 4. Click Assign profiles to select a profile to assign to the selected device. The Assign Profiles page appears. Both CP and DM profiles are displayed, depending on the capabilities of the device. 5. Click the radio button adjacent to the profile name, then click Add (or Add another if profiles exists) to assign a profile to the device. To add another profile, repeat this step. 6. For profiles that require subscriber-specific information such as an profile, a page appears where you enter the information. 174 Managing Devices

187 7. For CP profiles, another page appears where you enter CP message options. If User Pin is selected, a user PIN must be entered. Click Next once the options have been selected. 8. Provide a value in the Value field for the service named in the Service Tag section. Service tags are useful when you want to group devices using a particular type of service. For example, if you want to be able to find all devices using the service or devices using the MMS service, you tag the devices with the service type to enable the search. See Profiles and service tags on page 125 for more information. 9. When you have selected the profiles to assign, click Next on the main Assign Profiles page. The scheduling and notification options page appears. 10. Review the scheduling and notification options (as described in Scheduling and notification options on page 179). Make appropriate selections based on your profile requirements. The Send Notification and Ask User options are provided if one or more DM profiles have been selected. When done selecting all options, click Submit. 11. A confirmation page appears. This page summarizes the selected profile options. Click Confirm to continue. The Manage Profile Assignments page is again displayed, this time showing the new profile assignments for the device. Check the status column to determine if the assignment is pending or complete. Comparing a profile assignment The MDM Server maintains a device tree for each DM device. Whenever data is sent to a device or the MDM Server reads data from a device, the values stored in the device tree (on the MDM Server) are updated for that DM device. The compare feature compares the values in the profile assignment to the values in the device tree that is stored on the MDM Server. An operator may want to compare the values to see if a device s profile was changed or became corrupted at some point. To compare a profile assignment 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. 3. Click Manage Profile Assignments to display the Manage Profile Assignments page. This page lists the currently assigned profiles for the device. 4. Check the name of the profile to be compared with the profile on the device. You can check more than one profile to perform a multiple profile assignment comparison. Comparing a profile assignment 175

188 Note Profile assignments with a Pending status cannot be compared because the assignment has not been applied to the device yet. Only completed assignments can be compared (that is, status of Done). 5. Click Compare to display the Profile Comparison page. The columns are: Parameter. The list of attributes that make up the profile. Expected. The value of the attribute in the profile assignment. Actual. The value of the attribute in the device tree, which is updated on the MDM Server whenever the device communicates with the server. Comparison. The matching status. The values either match, do not match, or cannot be compared. If the MDM Server cannot communicate with the device at this time, a? (question mark) indicates the values cannot be compared. Last Read Time. The last time that the attributes were updated in the device tree (stored on the MDM Server). If the time is several days or weeks old, a Fetch operation is recommended and then a Compare operation again. 6. If the Expected and Actual attributes are different and need to be updated, click Resend to resend the profile assignment to the device again. Fetching a profile assignment The MDM Server maintains a device tree for each DM device, and updates the values in the tree whenever it sends data to ro receives data from the device. After a profile assignment comparison, if the values in the device tree are old (Last Read Time shown is several days or weeks old), a fetch operation can be done to refresh the values in the device tree. The fetch operation performs a discover on the nodes that make up the profile in the device. To fetch a profile assignment 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. 3. Click Manage Profile Assignments to display the Manage Profile Assignments page. This page lists the currently assigned profiles for the device. 4. Check the name of the profile to be compared with the profile on the device. 5. Click Compare to display the Profile Comparison page. 176 Managing Devices

189 6. Check the name of the profile to be fetched in the profile assignment table. 7. Click Fetch. The Fetch Profiles page appears. 8. Review the scheduling and notification options (as described in Scheduling and notification options on page 179). Make appropriate selections based on your profile requirements; when done, click Submit. 9. A confirmation page appears. This page summarizes the selected profile scheduling and notification options. Click Confirm to complete the fetch operation. The Manage Profile Assignments page is again displayed. Resending a profile assignment After a comparison, the operator may want to resend a profile assignment. To resend a profile assignment 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. 3. Click Manage Profile Assignments to display the Manage Profile Assignments page. This page lists the currently assigned profiles for the device. 4. Check the name of the profile to be compared with the profile on the device. 5. Click Compare to display the Profile Comparison page. 6. Check the name of the profile to be resent in the profile assignments table. 7. Click Resend to display the Resend Profile Assignments page. Note Only profile assignments with a Done, Failed, or Resending_Failed status can be resent. 8. Review the scheduling and notification options (as described in Scheduling and notification options on page 179). Make appropriate selections based on your profile requirements; when done, click Submit. A confirmation page appears. This page summarizes the selected profile scheduling and notification options. 9. Click Confirm to complete the resend operation. The Manage Profile Assignments page is again displayed. Resending a profile assignment 177

190 Editing a profile assignment Profile assignments can be edited, as necessary. This is particularly important with profiles, where over time, a subscriber s information can change, requiring modification. To edit a profile assignment 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. 3. Click Manage Profile Assignments to display the Manage Profile Assignments page. This page lists the currently assigned profiles for the device. 4. Check the name of the profile to edit, then click the associated Edit link in the rightmost column. The Modify Profile Assignment page appears. 5. Modify the parameters, as applicable, then click Submit. A confirmation page appears. 6. Click Submit again to complete the operation. The Manage Profile Assignments page is again displayed. 7. To apply the modifications to the device, perform a resend operation as described in Resending a profile assignment on page 177. Deleting a profile assignment To delete a profile assignment 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. 3. Click Manage Profile Assignments to display the Manage Profile Assignments page. This page lists the currently assigned profiles for the device. 4. Check the name of the profile to delete from the device, and click Delete. A confirmation page appears. 5. Click Confirm to complete the delete operation. A confirmation page appears with the following message: The selected profile assignment(s) are deleted (or scheduled to be deleted) successfully. 178 Managing Devices

191 Scheduling device management jobs Mobile Device Manager provides several options for scheduling device management jobs and handling the notification of mobile devices. Once a job is created and scheduled, it is placed in the Provisioning Request queue to await being performed based on the scheduling information. Scheduling and notification options on page 179 describes the common scheduling and notification options available for all jobs. Note that different options are provided for single-device and multiple-device jobs. Scheduling and notification options Option Now or Later Time and Date All Some Area Codes Send Notification Ask User Anytime During From and To Notification Rate Single/multiple device jobs Both Both Multiple Devices Multiple Devices Single Both Multiple Devices Multiple Devices Multiple Devices Multiple Devices Description Perform the device management job on the device(s) immediately or at the time specified in the Time and Date fields. Specify the date and time at which the device management job should be performed on the device(s). The Later radio button must be selected. Installs the update on all devices that have the image to be updated. Installs the update on some devices based on specified area codes. Specify multiple area codes with a space, comma, or semicolon delimiter. Sends a notification to the device user. By default, this option is enabled. Prompts the user to let the user know when a trigger message has been received by the device. This prompt appears before contacting the server. Notifies the devices to be updated anytime (after creating the provisioning request). Notifies the device some time during the time interval specified in the From and To fields. Specifies the interval of time when the device should be notified of the update. The During radio button must be selected. Number of devices to notify per minute. Possible options are: Never Slow (10/minute) Normal (80/minute) Scheduling device management jobs 179

192 Scheduling and notification options (continued) Option Single/multiple device jobs Description Fast (200/minute) Discovering a device node To discover a device node 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. 3. Click Enter Node To Discover. The Discover Node page appears. 4. The root node is./. Other general nodes are./devinfo or./ /xxx (where xxx is the name of a particular account on the device). 5. Enter a node, then click Discover. The Discover Node page appears. 6. Review the scheduling and notification options (as described in Scheduling and notification options on page 179). Make appropriate selections based on your profile requirements; when done, click Submit. 7. A confirmation page appears. This page summarizes the device to be discovered as well as the scheduling and notification options selected. 8. Click Confirm to continue and return to the Devices page. The Discover job appears in the Provisioning Requests page. Sending a command script to a device To execute DM commands on a device directly 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. 3. Click Enter Command Script. The Command Script page appears. 4. Specify the commands to be executed. Either type in the commands, or copy them from a text file. For example, 180 Managing Devices

193 <Script> <Delete> <Target>./ /jmg</Target> </Delete> </Script> Refer to the OMA SyncML standard at the following URL for more details: tech/affiliates/syncml/syncmlindex.html#v11 5. Click Execute to display scheduling and notification options page. 6. Review the scheduling and notification options (as described in Scheduling and notification options on page 179). Make appropriate selections based on your profile requirements; when done, click Submit. 7. A confirmation page appears. This page summarizes the device details to which the command script is applied, as well as the selected scheduling and notification options. 8. Click Confirm to continue and return to the Devices page. The Script job appears on the Provisioning Requests tab. Assigning an image to a device If you want to update a single device, you use the Assign Image to Device option on the Provisioning tab or the Assign Image option on the Device Detail page. Ths option displays all compatible updates from which you can select. Installation options can also be specified, such as: When should the update take place? Now or later at a specified date and time. What should the subscriber s experience be? Does the subscriber have the choice to install the update, or is it mandatory? If the update is silent, should the subscriber be prompted or notified, and if so, how often? As an alternative to single device assignment option, images can be installed on many devices of a particular model. See Assigning an image to multiple devices on page 182 for more details. To assign an image to a device 1. Click the Provisioning tab in the Provisioning RequestsMDM Console main window to display the page. 2. Click the Assign Image to Device link. The Devices page appears. This option is also available through the Device Detail page. Click the Assign Image button. Note If you initiate successive firmware update jobs on a device, the updates should be on sequential versions of the firmware; otherwise, the firmware update will fail. For example, if your initiate an upgrade from Assigning an image to a device 181

194 version 1.0 to 2.0 and initiate another upgrade from version 1.0 to 3.0, then this will fail. The correct upgrade path should be from version 1.0 to 2.0 and subsequently from 2.0 to Select the radio button for the Device Id of the device to which to assign the image, and click Select. The Device Detail page appears. Note See Scheduling and notification options on page 179 for more details on the properties and button options available on the Device Detail page. 4. At the bottom of the page, click Assign Image to Device. The Assign Image to Device page appears. All compatible images (in Mobile Device Manager) that can be used to update the device are displayed at the bottom of the page. 5. From the available update images, select an image that updates the device s existing image. Click Next to continue. 6. If the image can be updated through multiple paths, a page listing the paths appears. Select a path, then click Next. 7. A page appears with an update path declaration statement at the top of the page and scheduling and notification options below. 8. Review the scheduling and notification options (as described in Scheduling and notification options on page 179). Make appropriate selections based on your profile requirements; when done, click Next. 9. A confirmation page appears. This page summarizes the device to be updated, the image install options selected, as well as the update path that is followed to install the image. Click Assign to continue. 10. An Image Assignment Completed page appears, with the following statement: The image has been assigned to the device successfully. 11. Click the Provisioning tab to view the provisioning request. If the request was scheduled immediately, it may have a Done status. Otherwise, a Pending or Applied status appears. Assigning an image to multiple devices To update multiple devices, the Assign Image to Multiple Devices option is available on the Provisioning tab. This option creates a provisioning request that updates an image on all devices of a certain model, all devices of a certain model in specified area codes, or all devices matching specified phone numbers. When creating the provisioning request, installable images are displayed from which you can select. Further, installation options can be specified, such as: 182 Managing Devices

195 Which devices should be updated? All devices for certain tenants, or all devices that match specified phone numbers? Of those devices, which devices should be updates? All devices of a selected model, or all devices of a selected model in specified area codes? When should the update take place? Now or later at a specified date and time. What should the subscriber s experience be? Does the subscriber have the choice to install the update, or is it mandatory? If the update is silent, should the subscriber be prompted or notified, and if so, how often? What device notification parameters should be set? Notify the device of an update anytime or during a specified interval of time? Notify how many devices at a time? In what priority order should devices be updated, if any? As an alternative to the Assign Image to Multiple Devices option, images can also be assigned to specific devices independently. See Assigning an image to a device on page 181 for more details. To install an image on multiple devices 1. Click the Provisioning tab in the MDM Console main window to display the Provisioning Requests page. 2. Click the Assign Image to Multiple Devices link. The Assign Image to Multiple Devices page appears. 3. Select the radio button for the ID of the image to install. 4. Click Select at the bottom of the page. The Assign Image to Multiple Devices options page appears. 5. Select from among the three radio options: Install on Devices for Tenants. Select one or more tenants on which to install on the image. To select more than one tenant, hold the SHIFT key down while selecting successive tenants, or CTRL to select tenants that are not successively shown in the list. Install on Devices with Phone Numbers. List phone numbers in the text box, delimited by commas, for the devices that have the new image. Note The phone number format should follow the format specified for the MDM Server when the administrator configured phone number properties. Typical US format is [country code][areacode][phonenumber], for example, Contact your administrator to determine the expected format for other countries. Install on Devices with Phone Numbers from File. Browse to a text file with phone number strings. These phone numbers should be delimited with commas, with no other punctuation in the phone number. Assigning an image to multiple devices 183

196 Click Next when done. 6. The Compatible Images page appears. Images that are compatible to be updated on the devices are displayed. Select one or more images that you want to update, then click Install. 7. If multiple update paths exist for updating the device with the new image, these paths are displayed in the Update Path page. Select an update path for each tenant group by selecting the appropriate radio buttons, then click Install. 8. The Assign Image to Multiple Devices options page appears to confirm what has been chosen so far for the provisioning request and to display installation options. If the confirmation statement is not correct, click Cancel or Back to cancel the operation or go back to select other image options, respectively. To proceed, review the scheduling and notification options (as described in Scheduling and notification options on page 179). Make appropriate selections based on your requirements. 9. Click Install after selecting the image options. An confirmation page appears. 10. Click Confirm. A Provisioning Request Created page appears. 11. Click the View Provisioning Requests link at the top of the page to view the created provisioning request. If the request is scheduled immediately, it displays a Done status; otherwise, a Pending status appears. Managing workflows Creating a workflow job ICE workflows provide a way to automate device management tasks with intelligent branching based on definable rule sets and any internal or external information, such as demographics. ICE workflows can be designed and provided by Motive Consulting Services. Workflow jobs are created by assigning a workflow to a device. Once assigned, the progress of the job can be monitored in the Provisioning tab. Viewing workflow jobs To view workflow jobs 1. Click the Workflows tab in the MDM Console main window to display the Workflow Jobs page. 184 Managing Devices

197 This page shows a list of all ICE workflows that have been uploaded to the MDM Server. New workflows may be uploaded by using the Upload Workflow Jobs link. 2. Click a workflow name to view, rename, update, or delete a workflow job. Renaming a workflow job To rename the workflow job 1. Click the Workflows tab in the MDM Console main window to display the Workflow Jobs page. 2. Click a workflow name to display the Workflow Job Detail page. 3. Click Rename to display the Rename Workflow Job page. 4. Enter the new name for the workflow job and click Submit, or click Cancel to cancel the operation. Updating a workflow job If changes are made to a workflow, it must be updated on the server. To update a workflow 1. Click the Workflows tab in the MDM Console main window to display the Workflow Jobs page. 2. Click a workflow name to display the Workflow Job Detail page. 3. Click Update to display the Update Workflow Job page. 4. Enter the pathname including the filename, or browse to the updated workflow file. 5. Click Submit to update the workflow, or click Cancel to cancel the operation. If the workflow is being used by a provisioning job that is pending, an error message appears. The workflow cannot be updated until all provisioning jobs using the workflow are complete or canceled. Deleting a workflow job To delete a workflow job 1. Click the Workflows tab in the MDM Console main window to display the Workflow Jobs page. Renaming a workflow job 185

198 2. Click a workflow name to display the Workflow Job Detail page. 3. Click Delete to display the Delete Workflow Job page. 4. Click Submit to delete the workflow, or click Cancel to cancel the operation. If the workflow is being used by a provisioning job that is pending, an error message appears. The workflow cannot be deleted until all provisioning jobs using the workflow are complete or canceled. If there are no provisioning jobs pending, the workflow does not affect any pending provisioning jobs and the workflow can be deleted. Displaying a device tree To display a device tree 1. Click the Devices tab in the MDM Console main window to display the Devices page. 2. Click the Device Id of the device to display the Device Detail page. 3. Click Display Known Device Tree. The Currently Known Device Tree page appears. 4. For more details on the device management tree, refer to the OMA DM specifications. Click Back to return to the Device Detail page. 186 Managing Devices

199 This chapter covers: 19 Managing Updates Viewing updates Uploading an update package Uploading a workflow Discarding an update Deleting an update 187

200 This chapter describes the Updates tab, which allows you to perform management tasks for firmware update packages stored on the MDM Server. Viewing updates Updates configured in Mobile Device Manager are viewable as a list that can be filtered by search criteria. When you click the Updates tab in the MDM Console main window, all currently configured updates are displayed on the Updates page. This list is unfiltered. To filter the contents of the Updates page, enter search criteria in the left SEARCH panel. The fewer criteria entered, the less constrained the search. Note See Updates Detail properties on page 188 for descriptions of the search fields. The Free Text Search field allows the entry of any arbitrary string that can match any search field. When done, click Search, and the Updates page is updated to display devices that meet your search criteria. To display an Update Detail page, click on a update ID on the Updates page. The Update Detail page differs depending on whether the update has been assigned to any tenants. The properties are described in Updates Detail properties on page 188. Updates Detail properties Property Update Id Manufacturer Description Mobile Device Manager assigned ID of the update. Manufacturer of the device s model. Note The list contains only the manufacturers who have provided updated firmware configurations for their models. These upgrades are uploaded by using Uploading an update package on page 189. Model Name Model of the device. Note The list contains the models with firmware upgrades provided by the model manufacturers. These upgrades are uploaded by using Uploading an update package on page 189. From Image Id To Image Id ID of the image to be updated. ID of the update image. 188 Managing Updates

201 Updates Detail properties (continued) Property Description Size Applicable Tenants Description Free text description of the update. Size of the update. If tenants have been associated with the update, a list of tenants appears. The list includes the Tenant Name and Status and allows selection of an action. The Status and Action fields represent the Update Lifecycle Workflow states and actions that are permitted for each state. Clicking the Do Action button executes the displayed action. Uploading an update package To upload an update package file 1. Click the Updates tab in the MDM Console main window to display the Updates page. 2. Click the Upload Update Packages link to display the Upload Update Packages page. 3. Click Browse to navigate to the directory containing the update package ZIP file. Then click Upload. The MDM Server ensures that the update package file is readable by the MDM Server. If not, a validation error appears. If the format is correct, more information about the update package file appears in the Upload Update Package Information page. Information such as the following is included: whether the update contains a new update, a new from image, a new to image, or if there are provisioning requests to cancel. 4. Click Submit to continue the operation and upload the update package file. When confirmed, the update package file is uploaded to the MDM Server (and ultimately persisted to the MDM database). 5. The Updates page is again displayed. A confirmation statement about the update package file upload is also displayed. Uploading a workflow Workflows define the life-cycle management process of update packages. In short, they are used to set an update package to Ready for Deployment status. Uploading an update package 189

202 Correctly formatted and configured workflow files can be uploaded to the MDM Server for later use in update package provisioning requests. When a new workflow is uploaded to Mobile Device Manager, it supersedes the existing workflow. Updates that are part of new provisioning requests use the new workflow; previously existing provisioning requests follow the old workflow until they are exhausted. To create a properly formatted workflow contact Motive Consulting Services, or refer to the workflow DTD file. To upload a workflow file 1. Click the Updates tab in the MDM Console main window to display the Updates page. 2. Click the Upload Update Workflow link. The Upload Update Workflow page appears. 3. Name the update workflow, and click Browse to navigate to the directory containing the update workflow file. Then click Upload. The MDM Server ensures that the update workflow file, an XML file, is formatted correctly and readable by the MDM Server. If not, a validation error appears. Assuming that the format is correct, the workflow file appears in a confirmation page. 4. Click Confirm to continue the operation and upload the workflow file. When confirmed, the workflow file is uploaded to the MDM Server (and ultimately persisted to the MDM database). 5. The Updates page is again displayed. A confirmation statement about the workflow upload is also displayed. Discarding an update The Updates tab includes a discard option that disables updates but keeps them visible in Mobile Device Manager for operator reference. Note Discarded updates cannot be made active again, so use this feature carefully. If you want to make a discarded update active again, you must delete it and then recreate it. To discard an update 1. Click the Updates tab in the MDM Console main window to display the Updates page. 2. Click the update ID of the update to discard. The Update Detail page appears. 3. Select Discard in the workflow Action column of each tenant for which the update is to be discarded. 190 Managing Updates

203 4. Click Do Action to complete the operation. You are asked to confirm or cancel the discard operation. Upon confirmation, the Update Detail page appears again; the Status column of the selected tenants in the Applicable Tenants list displays Discarded. Deleting an update Updates that are no longer used can be deleted from Mobile Device Manager. To delete an update 1. Click the Updates tab in the MDM Console main window to display the Updates page. 2. Click the update ID of the update to delete. The Update Detail page appears. 3. Click Delete. A confirmation page appears. If provisioning requests or devices are associated with the update, they are identified on this page. If applicable, click the linked number of provisioning requests or devices to review which ones would be affected if you deleted the update. 4. Click Continue to continue the delete operation. Another confirmation page appears. Note When an update is deleted, associated provisioning requests are canceled and the update is no longer available for a client download. 5. Click Confirm to delete the update. Any associated provisioning requests are also deleted. Deleting an update 191

204 192 Managing Updates

205 This chapter covers: 20 Bulk Management Managing bulk operations Canceling a bulk operation Managing device groups Managing search templates 193

206 Bulk device management allows you to select a set of devices and then have the system perform DM operations on the whole set of devices, one device at a time. For example, bulk management allows you to assign profiles to a set of devices, or assign firmware images to them. You can select groups of devices based on a variety of criteria such as the model, tenant, or manufacturer. You can also select CP-only devices for many of the same criteria. With bulk management, you define the set of devices to be operated on, and then schedule the operation; the system then performs the operations on all the selected devices. Each time you create a bulk operation, you can choose an existing group of devices, or define new search criteria. After you search for devices, you can: Further refine the list by individually selecting or deselecting devices, creating a static set of devices for the operation. Or you can leave the set of devices defined as a dynamic set, where the search criteria you used continue to be applied while the operation is running. In that case, the system may continue to add new devices to the set during the run, and future runs using the same criteria pick up the current set of devices that meet the criteria. Managing bulk operations The Manage Bulk Operations page allows you to create or delete bulk operations. Creating bulk operations To create a bulk operation, complete the following steps. 1. Click the Bulk Management tab in the MDM Console main window to display the Manage Bulk Operations page. 2. Click the Create Bulk Operation link. 3. Select a group or a search template. To search for devices using a group, click the Select Device Group radio button. Select the required device group name from the drop down list. Click Search go to step 3. To search for devices using template, click the Select Search Template radio button, then select the template from the drop down list. The page will then display the template criteria property field; make a selection (or enter a value) in the field, then click Search. 194 Bulk Management

207 Note This following wild characters are allowed in a search string: %: Use this as a substitute for part of a search string, for example if you want to list all devices with phone numbers starting with 990, then use 990%. _: Use this as a substitute for a single character in a search string, for example if you want to list all devices with phone numbers starting at and ending at , then use _. 4. The system lists the devices satisfying the search template criteria. Choose one of two options: Select Dynamically apply to all devices that match selection criteria to apply the bulk operation to all the devices listed. Or click Select devices to target and select the devices by clicking the check box beside each device. Then provide a name for the bulk operation in the Enter bulk operation name. Click Next. 5. Note This page comes up only if you are using criteria template to search for devices. Go to the next step if you are using device groups. If you selected a search template, the system displays the Create Device Group page. Provide a group name for the devices selected for the bulk operation. You can use this group name later from the drop down list of Select Device Group to re-select the same devices again. 6. In the Select Operation page, select the operation to apply to the devices selected. Only one operation can be selected. Assign Profile; Get Profile Details; Assign Firmware Image. Click Next. Go to step 6 for Get Profile Details operation or step 7 for Assign Profile or step 8 Assign Firmware Image. 7. You get the Select Profile page. Select a profile you want to retrieve by clicking the radio button beside it. Click Next to get the Select Bulk Operation Schedule Details page. Go to step You get the Assign Profile page. The profiles that can be assigned to the selected devices are listed. Select the profile you want to assign to the devices by clicking the radio button beside the profile name. Click Next to get the Specify Profile Parameters page. 9. Specify the required profile parameters' values and click Next to get the Select Bulk Operation Schedule Details page. Go to step You get the Select Firmware Image page. The images that can be assigned to the selected devices are listed. Select the image you want to assign to the devices by clicking the radio button beside the image name. Click Next. You get the Assign Image page, this page lists the available firmware upgrade paths for the specified target image. Select the required upgrade path and click Next. to get the Select Bulk Operation Schedule Details page. Go to step 10. Creating bulk operations 195

208 Note If you initiate successive firmware update jobs on a device, the updates should be on sequential versions of the firmware, else the firmware update will fail. For example, if your initiate an upgrade from version 1.0 to 2.0 and initiate another upgrade from version 1.0 to 3.0 then this will fail. The correct upgrade path should be from version 1.0 to 2.0 and subsequently from 2.0 to You get the Select Bulk Operation Schedule Details page. On this page you schedule the bulk operation and also set options for the subscriber. You can schedule a operation using either the Simple schedule or the Advanced schedule. Note All scheduling information should be provided in GMT and not in local time. Simple Scheduling: a. Bulk Management Job Schedule: To schedule a job, provide the Scheduled Start Date and Time, the Scheduled End Date and Time. The date should be in the format mm/dd/yyyy. Note The start time could be now, or it could be a specific time, to be provided. And the end time should always be provided. b. Failure Threshold: This is the maximum number of job failures allowed in the scheduled bulk job. Note The bulk job is considered a failure if the number crosses this threshold value. c. Options: The options available are: Send Notification to the user; Ask User before you perform the operation on a device. Click Submit. Advanced Scheduling: This option allows you to repeat the scheduled bulk jobs on a daily, weekly, or monthly basis in the specified time period. a. Bulk Management Job Schedule: To schedule a job, provide the Scheduled Start Date and Time, the Scheduled End Date and Time. The date should be in the format mm/dd/yyyy. Note The start time could be now, or it could be a specific time, to be provided. And the end time should always be provided. b. Failure Threshold: This is the maximum number of job failures allowed in the scheduled bulk job. 196 Bulk Management

209 Note The bulk job is considered a failure if the number crosses this threshold value. c. Repeating: The bulk job can be repeated daily; weekly; or monthly. Daily: Provide the daily bulk job schedule:enable: This is the time when the bulk job is started. Disable: This is the time when the bulk job is stopped, if it has not completed. Weekly: Select the weekdays and the time to run the scheduled bulk jobs :Enable: Provide the start time and select the day(s) of the week to start the bulk job. Disable: Provide the end time and select the day(s) of the week to end the bulk job. Note You can select multiple days of the week to run the bulk jobs. But you cannot have overlapping days of the week between multiple runs of the scheduled bulk jobs. For example: You can run a bulk job activated on Sunday and disabled on Tuesday and similarly scheduled to run from Thursday to Saturday. Monthly: Select the months and the days in the month to run the bulk jobs: Enable: Provide the start time and select the start day(s) of the months to start the bulk job. Disable: Provide the end time and select the day(s) of the months to end the bulk job. Note You can select multiple days of the month to run the bulk jobs. But you cannot have overlapping days of the month between multiple runs of the scheduled bulk jobs. For example: You can run a bulk job enabled on 1st and disabled on 10th and similarly scheduled from 20th to 31st for the selected months. You should take into account that February does not have 31 days. So you cannot select Feb if you schedule the bulk job as above. d. Options: The options available are: Send Notification to the user; Ask User before you perform the operation on a device. Click Next to get the Confirm Bulk Operation Details. 12. The Confirm Bulk Operation Details Page summarizes the Profile name, Job schedule details and Notification options provided. Click Confirm. 13. You get the Bulk Operation Scheduled. Details page listing the bulk operation details. Deleting bulk operations You can delete a bulk operation if: The scheduled start time is in the future (the job has not yet started), or Deleting bulk operations 197

210 The scheduled end time is in the past (the job is complete). To delete a bulk operation, click the Bulk Management tab. The Manage Bulk Operations page displays a table that lists the bulk operations. Click the check boxes for the operations you want to delete, then click the Delete button. The system displays a confirmation page; click the Confirm button. Viewing bulk operations To view the bulk operations in the system, click the Bulk Management tab. The Manage Bulk Operations page displays a table that lists the bulk operations. The table provides the following information: Operation Id. The ID given to a bulk operation when it is initiated. Operation Name. The name of the bulk operation. Operation Type. One of the operation types: Assign Profile, Get Profile Details, or Assign Firmware Image. Status. The status of the bulk operation. The following states are possible: Timed Out. The bulk operation has exceeded its scheduled end time. In Progress. The bulk operation is in progress. The bulk operation retains this status until the scheduled end time is reached. Scheduled. Indicates that the bulk operation is scheduled but is not presently in progress. Success. All the devices in this bulk operation were managed, with the number of failures less than the failure threshold. Registering Devices. The devices are being registered with different Managed Servers before starting the individual device job. Aborted. The system stopped the bulk operation because there was a problem that prevented its completion, such as if the profile or firmware image to be applied was not available in the system. N/A. The system has not yet tried to create a device job for the specified device. Start Time (GMT). The time at which the bulk operation is scheduled to start. End Time (GMT). The time at which the bulk operation is scheduled to be completed. Note If any operations remain after the end time, the operations are terminated. Device Jobs Failed. The number of device jobs in the bulk operation that failed. Device Jobs Succeeded. The number of device jobs in the bulk operation that succeeded. 198 Bulk Management

211 To view the details about a particular operation, click the Operation Id link in the table view. See Bulk operation details on page 199. Bulk operation details To view the details of a job listed on the Manage Bulk Operations page, click the Operation Id link in the table view. The following device job details are listed: Device Job Id. The ID of the job initiated on the device. This ID is generated by the system for each device in a bulk operation. External Device Id. The external ID of the device on which the device job is being executed. Status. The status of the device job initiated as part of the bulk operation. The possible device job status values are: Unresponsive. The maximum six notifications have been sent to the device, but the device has not connected back. Session Time Out. The time taken by the session has exceeded the time out interval. Job Creation Failed. The system has failed to create a device job for this device. Job Cancelled Manually. The device job was canceled manually. Scheduled. The device job was created successfully, and the server is waiting for the device to connect back to initiate the job. Job Started. The device has successfully connected back to the server, and the job was initiated. Job Failed. The device job initiated on the device failed. Note A device job failure could be on the device or on the server side. Job Succeeded. The device job has finished successfully. Device Job Creation Status. The status of the device job creation process. The status could be any of the following: Device Not Found. The device with the specified ID was not found in the system. Profile not Found. The profile to be assigned was not available in the system. Template not Found. The profile details required to populate a profile template were not found in the system. Firmware Image not Found. The target firmware image for a specific image ID was not found in the system. Viewing bulk operations 199

212 Firmware Update not Found. The required firmware update package for a specific update ID was not found in the system. Device Image Manager Failed. There is a problem with the device image manager. Unidentifiable Entity Not Found. A database level entity was not found, and the entity type could not be identified. For example, the entity types could be Device, Profile, Subscriber, Image, and so on. Current Firmware Image mismatch. The firmware present on the device and the image used for the firmware update job do not match. Empty Firmware Update Path. The firmware update path for a job was not provided. Firmware Update not applicable for tenant. The specified firmware update is not applicable to the tenant to which the device belongs. Firmware Image Mismatch. The target firmware image and the firmware image found on the device after the firmware update do not match. Invalid CP signature. The CP signature provided is invalid. Invalid User Pin. The user PIN provided is invalid. Invalid CP Profile Assignment. The CP profile to be assigned to a device is invalid. User Pin not Required. The user PIN to create a job was specified when it was not required. Signature Mismatch. The CP signature provided and a signature applicable for a device do not match. Device not active for subscriber. The subscriber's device is not active. Subscriber deactivated. The subscriber did not respond to the notification messages and was deactivated. Device deactivated. The device was deactivated by an MDM Server user. Service tag value too long. The service tag value provided to create an Assign Profile job was too long. Concurrent update. Multiple device jobs were created on the device at the same time. Unknown error. An unidentifiable error occurred when creating a device job. Job created successfully. The required device job was created. Click Home to go back to the bulk operations listed on the Manage Bulk Operations page. To cancel a bulk operation, see Canceling a bulk operation on page 201. Click Edit Job if you want to modify the bulk operation details. Only scheduling and grouping details can be changed. 200 Bulk Management

213 Note If a bulk operation has started, then it cannot be edited. Canceling a bulk operation To cancel a bulk operation, view its details by selecting the Manage Bulk Operations page, and then clicking the Operation Id link for the job you want to cancel, in the table view. Then click the Cancel Job button; when the system asks for confirmation, click the Submit button. Note If an operation is in progress, then the bulk operation cannot be canceled. Managing device groups Grouping of devices could be done dynamically. Dynamic groups are created by an operator on the fly by providing values to the search parameters in a search template. Once the device group is created then it remains a static group, with fixed constraint values. Grouping of devices is also done dynamically using pre-created Criteria Templates. Criteria Templates can be created and uploaded from the Manage Templates link. The system includes the following default templates, which allow you to select devices by a number of common attributes, and to select CP-only devices for most of the same attributes. Tenant Device Id Manufacturer Model Model and Manufacturer Model and Image ID Phone Number Service Tag Name Value Status CP and Tenant CP and Device Id Canceling a bulk operation 201

214 CP and Manufacturer CP and Model CP and Model and Manufacturer CP and Phone Number CP and Service Tag Name Value CP and Status Creating a device group To create a new device group: 1. Click Bulk Management tab and then click Manage Device Groups link. 2. In the Manage Device Groups page, click the Create Group link to get the Device Group page. 3. Select a search template from the Template Name drop down box. The search template name is the basis for the group that you want to create. 4. The page displays the template name and the associated constraints of the selected template. Select a specific value for the constraint, if you are presented with a drop down list or enter the value for the constraint property if it is a text field. After doing the above, enter a name for the group you are creating in the Group Name field. Click Save. Note You cannot create a group that has the same name as an existing device group for the same tenant. Note If you search using the template find devices by status, 0 should be selected for deactivated subscriber and 1 for activated subscriber. 5. The next page lists all the group properties you selected. Click Confirm to create the Criteria Group. The Manage Criteria Groups page appears with the name of the new list. Deleting a device group To delete a device group: 1. Click Bulk Management tab and then click Manage Device Groups link. 2. The Device Group page displays a list of existing groups with a check box beside each device group. 202 Bulk Management

215 3. Select a device group file by clicking the checkbox beside the device group. Click Delete. The page lists the selected device groups with the prompt Are you sure you want to delete these groups?. Click Confirm. Managing search templates Search templates provide default options for grouping devices. You can upload new search templates, delete them, or update them. Creating a search template Use the following procedure to create a new search template. To create a new search template 1. Click Bulk Management tab and then click Manage Search Templates link. 2. In the Manage Search Templates page, click the Upload Search Template link to get the Upload Search Template page. 3. Select a search template file by entering the path to the file in the Search Template text field. Alternatively you can use the Browse button to navigate to and select the required file. 4. Click Load to upload the search Template File. 5. You are asked to confirm that you want to upload the search template file. Click Confirm to upload the search template. Note If you are creating a search template that is currently in the system, you are asked to confirm if you want to overwrite the older similarly named search template. This action is similar to updating the search Template file. Click Next to go to Update Search Template section. Updating a search template Use the following procedure to update an existing search template. To update an existing search template 1. Click Bulk Management tab and then click Manage Search Templates link. 2. Click the Upload Template link to display the Upload Search Template page. Managing search templates 203

216 3. Select the updated search template file by entering the path to the file in the MetaData File text field. Alternatively you can use the Browse button to navigate and select the required file. 4. Click Load to upload the search Template File. 5. You are prompted with the following message "Please check the details current search template will be overwritten". Click Confirm to update an existing search template. Deleting a search template To delete a search template: 1. Click Bulk Management tab and then click Manage Search Templates link. 2. The Manage search Templates page displays a list of existing templates with a check box beside each search template. 3. Select a search template by clicking the checkbox beside the desired search template. Click Delete. 4. You will be prompted with the following message Groups associated with the criteria templates will also be deleted. Are you sure you want to delete these templates?. 5. Click Confirm to delete the selected search template. 204 Bulk Management

217 This chapter covers: 21 Managing Provisioning Requests Viewing Provisioning Requests Cancelling a Provisioning Request 205

218 This chapter introduces the Provisioning tab, an area where provisioning requests generated by assigning profiles or updates may be monitored and cancelled. Links to assign firmware updates and to create workflow jobs are also provided. These functions are described in Chapter 18, Managing Devices on page 167. Viewing Provisioning Requests Provisioning requests configured in Mobile Device Manager are viewable as a list that can be filtered by search criteria, or one by one in detail. On clicking the Provisioning tab, all currently configured provisioning requests are displayed in the Provisioning Requests page. This list is unfiltered. To filter the contents of the Provisioning Requests page, enter search criteria in the left Search panel. The fewer criteria entered, the less constrained the search. Note See Provisioning Request Detail Properties on page 206 for descriptions of the search fields. The Free Text Search field allows the entry of any arbitrary string that can match any search field. When done, clicksearch and the Provisioning Requests page is updated to display provisioning requests that meet your search criteria. To display a Provisioning Request Detail page, click on a Job ID of a provisioning request on the Provisioning Requests page. The Provisioning Request Detail page shows request properties, depending on the type of request, as described in Provisioning Request Detail Properties on page 206. Provisioning Request Detail Properties Property Job Id Target Job Type Job Type All PR List only All Description Mobile Device Manager defined identifier for tracking provisioning requests in Mobile Device Manager. Click the Id label to toggle the sort order of the table by Id. Device that is affected by the change or action associated with the request. Defines the type of provisioning request. Possible values are: Discover - Request to discover the node. Firmware - Firmware update. Assign Profile - Assigning a profile (CP or DM) to configure the device(s) 206 Managing Provisioning Requests

219 Provisioning Request Detail Properties (continued) Property Job Type Description Resend Profile - Resend a profile to the device(s) Delete Profile - Delete a profile from the device(s) Command Script - Invoked by a command script. Image Status Devices Affected Devices Waiting Devices Updated Devices Failed Devices Cancelled Scheduled Time Script Node Node > Value pairs UI Mode Firmware All All All All All All All Script Discover Assign Profile Firmware Workflow - The workflow job may contain several DM tasks. Declares the affected image associated with the request. Indicates progress status of the provisioning request. Possible values are: Pending, Applied, Done, and Cancelled. Number of devices affected by the provisioning request. Number of devices waiting to be updated by the provisioning request. These devices have been or will be notified of the pending update. Number of devices updated by the provisioning request. Number of devices where the update failed. Refer to the Activity Log to see if there are one or more devices in this class, since this could indicate a serious service failure. Number of devices whereby a job was cancelled after being initially scheduled. Scheduled time for the update to be implemented. Click the Time label to toggle the sort order of the table by time. Displays the script invoked in command script requests. Displays the node that the associated device belongs to in a discovery job. Displays the defined profile configuration in an applied Profile update. See Managing Profiles on page 147 for more details. Indicates the UI mode that the update should implement. Possible values are: Optional - The user can chose to never download this update Mandatory - The user can chose to postpone the update, but eventually must download the update. Silent - Update is done silently. Viewing Provisioning Requests 207

220 Provisioning Request Detail Properties (continued) Property Ask Count Ask Interval Ask User Ask Before Downloading Ask Before Applying Area Codes Rate Order Notification Time Target Image ID Manufacturer Model Capabilities Version Source Image ID Source Image Capabilities Source Image Version Device Id Phone Number Current Image External ID Current Image Capabilities Current Image Version Update Path Job Type Firmware Firmware Firmware Firmware Firmware Firmware Firmware Firmware Firmware Firmware Firmware Firmware Firmware Firmware Install Image Install Image Install Image Discover Script Config Discover Script Config Install Image Install Image Install Image Firmware Description Number of times to ask the user on receipt of a trigger message before going ahead and contacting the server and doing a discovery. How often to ask the user, in minutes. Prompt the user to let them know when a trigger message has been received (but before contacting the server). Prompt the user before performing the download. Prompt the user before applying the update. Devices in the specified area code(s) are all affected by the update. Number of devices to notify per minute. Comma separated area codes that defines priority order. Indicates when the devices are notified of the update. Possible values are: any time or during an interval specified. Image ID of the resulting image when the update of the device has been completed. Manufacturer of the model of device(s) that are affected. Model of the device(s) that are affected. Capabilities of the target image. Version of the target image. ID of the source image. Capabilities of the source image. Version of the source image. Device Id of source image. Phone number of device. External ID of the current image. Capabilities of the current image. Version of the current image. Image update path. 208 Managing Provisioning Requests

221 Cancelling a Provisioning Request Provisioning requests that are still Pending can be cancelled without any other consequences. However, cancelling a provisioning request that has been applied and has updated one or more devices will not undo the changes that have been made. A new provisioning request to reverse the completed update(s) should be created. To cancel a provisioning request, follow these steps: 1. Click the Provisioning tab in the MDM Console main window. The Provisioning Request page appears. 2. Click the PR ID link for the pending provisioning request that you want to cancel, then at the bottom of the page, click Cancel. Note Provisioning requests with APPLIED or DONE states cannot be cancelled. 1. When you are prompted with Are you sure you want to cancel this provisioning request? click Confirm. 2. The Provisioning Request appears, with the state changed for the provisioning request that was cancelled. The new state reflects CANCELLED. Cancelling a Provisioning Request 209

222 210 Managing Provisioning Requests

223 This chapter covers: 22 Logging, Reporting, and Monitoring the System MDM Server Logs Reporting system operations Reporting Statistics Monitoring Mobile Device Manager with SNMP 211

224 MDM Server Logs All activities performed by the MDM Server are categorized and logged in four different log files. The log files are maintained at <MDM_INSTALL_FOLDER>\logs. A brief description of the information maintained by the log files are provided below: dmsuite.log: This is the main log file and maintains the general output from the MDM Server. DM-messages.log: Information about all activities implementing the OMA DM protocol is maintained in this log file. CP-messages.log: Information about all activities implementing the OMA CP protocol is maintained in this log file. Command-session.log: Information about all the DM command session activities are maintained in this file. The level of information logged in the log files can be specified in the log4j.xml file, in the <MDM_INSTALL_FOLDER>\properties directory. These values are provided to the priority property element in the log4j.xml file, for example: <priority value="inherited"/> Note For clustered deployments, the log files are located in the corresponding install directorys of the Administration Server and Managed Servers. Each server on the cluster maintains its own logs and hence the Administration Server and Managed Servers on the cluster need separate configuration. The allowed logging levels and a brief description about information logged for each level is provided below: DEBUG - Setting the DEBUG level captures fine-grained information that are most useful to debug an application. INFO - Setting the INFO level captures messages that highlight the progress of the application at coarse-grained level. WARN - Setting the WARN level results in capture of information that indicate potentially harmful situations. ERROR - Setting the ERROR level results in capture of detection of error events that might still allow the application to continue running. FATAL - Setting the FATAL level designates very severe error events that presumably leads the application to abort. INHERITED - Setting INHERITED results in the logger inheriting a level from its closest ancestor with an assigned level. 212 Logging, Reporting, and Monitoring the System

225 Reporting system operations The MDM Server monitors and logs client and server events through activity logs in the MDM Console. There are two different logs available: Device Activity Log - This log tracks all client device communications with the MDM Server. Audit Log - This log tracks all Web Service APIs (calls from the MDM Server to a subscriber s device, for example) and administrative actions performed in the MDM Console. The following sections describe these logs in greater detail. Device Activity Log The Device Activity Log tracks all device activity from creation to job execution. Access the Device Activity Log by clicking the Activity Logs tab in the MDM Console main window. A Device Activity Log page appears. To filter the displayed Device Activity Log, enter search criteria in the available fields of the Search panel. The less criteria entered, the less constrained the search. The search fields are: Device Id - Enter an exact ID of a device, or partial code to Search for. Phone Number - Enter the phone number of the device. Job Id - Enter the phone number of the device. Job Type - Search for device activities by job type. Show Actions - Click All to display all log entries, or click Filter By to select entries of certain action types. To select more than one entry, hold the CTRL key down while selecting. When - Select from the For drop-down options (All, Today, Past 7 Days) or provide a data interval using the From/To fields. When done, click Search and the Device Activity Log displays only entries that meet your Search criteria. Purging Device Activity Logs In order to purge the device activity log files, perform the following steps: 1. Log in to the machine deploying the Administration Server. Reporting system operations 213

226 2. Set the environment variables: export ORACLE_HOME=%ORACLE_HOME% export PATH=$PATH:$ORACLE_HOME/bin export LD_LIBRARY_PATH=$ORACLE_HOME/lib 3. Change directories to the Administration Server installation directory. cd <Admin_Server_Install_Folder>/purgeDeviceActivityLog 4. Run the command script./purge.sh Audit Logs The Audit Log tracks Web service calls (calls from the MDM Server to a subscriber s device, for example) and administrative actions performed in the MDM Console. Access the Audit Log by clicking the View Audit Log link in the Activity Logs tab. An Audit Log page appears. To filter the displayed Audit Log, enter search criteria in the available fields of thesearch panel. The less criteria entered, the less constrained the search. The search fields are: All - Click on this option if you to view audit of all activities. Some -. Job Id - Enter the phone number of the device. Job Type - Search for device activities by job type. Show Actions - Click All to display all log entries, or click Filter By to select entries of certain action types. To select more than one entry, hold the CTRL key down while selecting. When - Select from the For drop-down options (All, Today, Past 7 Days) or provide a data interval using the From/To fields. Reporting Statistics To report statistics of Mobile Device Manager operations, use the Motive Reporting Console. Consult the Motive Reporting Console Help for information on using the console. For information on installing and configuring the Motive Reporting Console, see the Mobile Services Management Reporting Deployment Guide. 214 Logging, Reporting, and Monitoring the System

227 Understanding the Mobile Service Management Solution reports Use the Motive Reporting Console to view reports. Install the Motive Reporting Console on at least one of the Managed Servers in the MDM cluster. For information on deploying the Motive Reporting Console, see the MSM Reporting Deployment Guide. For information on using the Motive Reporting Console, see the Motive Reporting Console Help. Reports provided Reports provided with the Mobile Device Manager Report name Number of Active users per Phone Model Number of FOTA per Phone Model Number of OTA CP WAP Messages Successful Jobs Successful Jobs for a Tenant Description This report displays information about the number of active users for each phone model in a timeframe. This report displays information about the number of firmware updates done per phone model in a timeframe. This report displays information about the number of OTA (Over the Air) messages sent in a timeframe. This report displays information about the number of successful jobs completed in a timeframe, per job type. This report displays information about the number of successful jobs completed in a timeframe, per job type, for a selected tenant. Input fields Start Date, End Date, Interval Type, Tenant Name (can select All) Start Date, End Date, Interval Type, Tenant Name (can select All) Start Date, End Date, Interval Type, Tenant Name (can select All) Start Date, End Date Start Date, End Date, Tenant Name Sorted by... Start Date/Time, Manufacturer Name, Model Name Start Date/Time, Manufacturer Name, Model Name Start Date/Time Job Type Job Type Filename NumberofActiveUsersPerPhone Model.zip NumberofFOTAPerPhoneModel.zip NumberofOTACPWAPMessages.zip SuccessfulJobs.zip SuccessfulJobsForATenant.zip Understanding the Mobile Service Management Solution reports 215

228 Adding reports to new managed servers If you add a new managed server to the system, you must perform the following steps to ensure that the Motive Reporting console can display reports for the system: Run the setup_weblogic.sh script (provided with MotiveReporting). For details, see the MSM Solution Reporting Deployment Guide. If you did not deploy Motive Reporting to the cluster, then you must also manually deploy Motive Reporting to the new managed server if you want it to be deployed there. Monitoring Mobile Device Manager with SNMP Mobile Device Manager integrates SNMP monitoring traps into its server operations to allow for tracking of key system activities, such as details about its provisioning request timer and notifications. Working with the SNMP monitoring tools used by your data center or network services organizations, the system operator can monitor these critical areas of the MDM Server system. Monitoring the provisioning request timer Mobile Device Manager asserts monitoring traps for the following provisioning request timer information: Number of times the Provisioning request timer ran Number of times the Provisioning request timer ran successfully Number of times the Provisioning request timer ran unsuccessfully Last time the Provisioning request timer ran Last time the Provisioning request timer ran unsuccessfully Monitoring notifications For each tenant, a Notification Processor instance is created. Each instance has a Notification Queue Startup and a Notification Queue Receiver instance. The following list shows the attributes (columns) that are monitored. Request name of notification queue Respond with name of notification queue 216 Logging, Reporting, and Monitoring the System

229 Total number of objects notified by the notification timer Number of objects notified in last timer poll by the notification timer Number of times the notification timer ran Number of times the notification timer ran successfully Number of times the notification timer ran unsuccessfully Total number of messages that couldn t be delivered to the message adapter Total number of messages delivered to message adapter Last time the notification timer ran Last time the notification timer ran unsuccessfully Monitoring notifications 217

230 218 Logging, Reporting, and Monitoring the System

231 This chapter covers: 23 Managing Roles Modifying a role Adding new roles 219

232 This chapter describes the Role Management tab of the MDM Console. From this tab, the operator can select the functions associated with a role, or create new roles. Modifying a role You modify an existing role by choosing the functions associated with it. To modify the functions associated with a role 1. Click the Role Management tab in the MDM Console main window. The Roles & Associated Functions page appears. 2. Select a role in the Role list. The All Functions and Selected Functions lists appear. The All Functions list shows any functions not currently assigned to the selected role. The Selected Functions list shows all the functions currently assigned to the selected role. 3. Move functions from one list to another by selecting them and clicking the << or >> buttons. 4. Click Confirm to complete the reassignment of functions. Adding new roles You can add new roles to the system via the Role Management tab's Add Role subtab. To add a new role 1. Click the Role Management tab in the MDM Console main window. The Roles & Associated Functions page appears. 2. Click the Add Role subtab. The Add Roles page appears. 3. Enter a role name in the Role field, and select a Home Page for the role, which becomes the starting tab for that role. 4. Click Confirm to complete the creation of the new role. 220 Managing Roles

233 This appendix covers: A Advanced Operations Profiles, profile templates, and attributes Uploading a profile metadata file Uploading a profile service file Managing DDFs Managing profile mappings Managing CP profile mappings Configuring bootstrap templates 221

234 This section includes tasks and features of the MDM Server for advanced system operators. Normal day-to-day operations do not typically require the operators to work with these tasks, however, some of these tasks are required for initial setup of system parameters. Profiles, profile templates, and attributes Included with the MDM Server is a set of profile templates that are configured on the MDM Server. These templates are based on defined system and custom attributes. Some of the profile template user data can be provided in native languages that are supported by the UTF-8 encoding. The profile templates allow you to configure the system to provision sets of attributes to OMA-DM devices in meaningful units. About profiles Profiles, profile templates, and profile mappings are data objects used by the MDM console to manage the provisioning of OMA-DM devices. These data objects allow console users to work with meaningful containers (an profile) rather than dealing directly with OMA-DM nodes. Node locations vary from one device model to another, and profiles provide a level of indirection so that users can use one profile to provision multiple device models. Profiles are created using the MDM Console, while profile templates and profile mappings are defined in profile metadata XML files that are uploaded to the console (see Profile metadata XML file reference on page 224 for more information). The following terms have specific meanings when used with profiles: Services. A service is a device feature which requires specific data fields to work. In terms of the MDM console, a service is a container for a set of fields called attributes; the main task of the console is to provision devices with appropriate values for these attributes. Profiles. Profiles are sets of values tied to specific tenants. A profile contains values for the attributes of a single profile template. Profile templates. Profile templates specify the attributes of a service. You need one profile template for each service. Profile templates are defined in profile metadata XML files. For more information, see ProfileTemplates in the profile metadata file on page 226. Profile mappings. Profile mappings tie the attributes of a profile template to specific nodes for a model. Profile mappings are defined in profile metadata XML files. For more information, see Profile Mappings in the profile metadata file on page 227. Profile links. You can link some profiles so that one profile becomes a prerequisite for another. A linked profile's values are sent to the device before the linking profiles values are sent. 222 Advanced Operations

235 Profile links are defined within profile templates, using the NeedsNAP and NeedsProxy elements. The link mechanism uses specific XML elements; only certain profile types can be linked. For more information, see ProfileTemplates in the profile metadata file on page 226. Profile concepts diagram The following diagram shows the relationships between some of the data objects relevant to profiles. Profile concepts diagram 223

236 Profile concepts diagram Tenant 1-many Profile Service Profile Template Profile Mapping Device Model attribute1 1-1 nodea attribute2 1-1 nodef Profile metadata XML file reference This topic describes the possible values for profile metadata XML files. A profile metadata XML file (also called a profile template file) is an XML file that defines profile templates, profile categories, profile mappings, and attributes types for a deployment. 224 Advanced Operations

237 After you define the properties of these various data objects in one or more profile metadata files, you import the file(s) into the MDM console to make those properties active. See Importing profile templates on page 231. Basic structure of the file. A profile metadata file has a root element, ProfileMetadata, that contains three elements to define the three main sections of the file: ProfileCategories - Defines categories for grouping profiles. AttributeTypes - Defines custom types for validating attribute values. ProfileTemplates - Defines profile templates. ProfileCategories in the profile metadata file The ProfileCategories element establishes the list of valid profile categories. Categories from this list are referenced in profile template definitions. To create a new category, add a new ProfileCategory element to the ProfileCategories element. To assign a profile template to the new category, use the new category's Name in a profile template's CategoryName element (see ProfileTemplates in the profile metadata file on page 226). A ProfileCategories section in a profile metadata XML file looks like this: <ProfileCategories> <ProfileCategory> <Name>AppManagement</Name> <Description>Ability to install applications via profiles</description> <ProfileCategory>...additional profile categories here... </ProfileCategories> AttributeTypes in the profile metadata file The AttributeTypes element allows you to create custom attribute types to be used in profile templates. There are two default attribute types, String and Boolean. You can define more specific types, which only allow values from a list of specified values. This allows the system to validate values before passing them down to a device. To create a new type, add a new AttributeType element to the AttributeTypes element. To use an attribute type in a profile template, use the attribute type's Name element in one of the profile templates's TypeName elements. The value of the TypeName must match the value of the Name exactly. See ProfileTemplates in the profile metadata file on page 226 for an example of how to use an attribute type. An AttributeTypes section in a profile metadata XML file looks like this: Profile metadata XML file reference 225

238 <AttributeTypes> <AttributeType> <Name>Mailbox Protocol</Name> <Description>Mailbox protocol selection for </description> <Values> <Value>POP</Value> <Value>IMAP</Value> <Value>Active Sync</Value> </Values> </AttributeType>...additional attribute types here... </AttributeTypes> ProfileTemplates in the profile metadata file The ProfileTemplates element allows you to define profile templates for a deployment. The element includes metadata that defines the category of the template, links to other templates, the service for the template, and the attributes that the template includes. A ProfileTemplates section in a profile metadata file has the following structure: <ProfileTemplates> <ProfileTemplate> <CategoryName>Category name</categoryname> 1 <Name>template name</name> 2 <NeedsNAP>true or false</needsnap> 3 <NeedsProxy>true or false</needsproxy> 4 <Service>Service name</service> 5 <UserSpecifiedRoot>true or false</userspecifiedroot> 6 <Attributes> <Attribute> <Name>Attribute name</name> <TypeName>String or Boolean or Attribute Type</TypeName> <IsRequired>true or false</isrequired> <IsUserAttribute>true or false</isuserattribute> <IsMultiValued>true or false</ismultivalued> <DisplayValue>true or false</displayvalue> <ValueUnique>true or false</valueunique> </Attribute>...other attributes... </Attributes> </ProfileTemplate>...other profile templates... </ProfileTemplates> 1 <CategoryName>. The category to which this template belongs. Must match a Name from a ProfileCategory exactly. 2 <Name>. The name of the profile template. 3 <NeedsNAP>. Determines whether or not the NAP profile should be sent to the device along with this profile. Values can be true or false. For any one profile, either NeedsNAP or NeedsProxy can be true, but not both. 226 Advanced Operations

239 4 <NeedsProxy>. Determines whether or not the proxy profile should be sent to the device along with this profile. Values can be true or false. Note Since proxy profiles are always linked to a NAP profile, the system always sends NAP profile attributes along with proxy ones. 5 <Service>. A service name (one of the predefined service names, such as , NAP, etc.). 6 <UserSpecifiedRoot>. The system allows a dynamic or variable root node name; this element specifies whether the root node name is user-specified or should be chosen by the system. Values can be true or false. If this element is set to true, the profile template should contain an attribute type/name RootNodeName, which will determine the root node value. The value of the attribute is collected by the console interface when the profile is created. When the profile is assigned to a device, the system uses the user-supplied value. For example, if the value globecomwifi is used, the system creates a replace command as follows: <Replace> <CmdID>6</CmdID> <Item> <Target> <LocURI>./Vendor/MSFT/Wi-Fi/access-point/VAMSIWIFI/DestId</LocURI> </Target> <Data>{436EF144-B4FB-4863-A041-8F905A62C572}</Data> </Item> </Replace> If this element is set to false, the system generates a random value for the root, resulting in the following replace command: <Replace> <CmdID>6</CmdID> <Item> <Target> <LocURI>./Vendor/MSFT/Wi-Fi/access-point/ %7B8a2303c0-54c3-11de %7D/DestId</LocURI> </Target> <Data>{436EF144-B4FB-4863-A041-8F905A62C572}</Data> </Item> </Replace> Profile Mappings in the profile metadata file The ProfileMappings element allows you to define profile mappings for a deployment. The profile mapping connects the attributes of a profile template to the DM tree nodes of a specific device model. A ProfileMappings section in a profile metadata file has the following structure: Profile metadata XML file reference 227

240 <ProfileMapping> <ModelName>Model Name</ModelName> 1 <ManufacturerExternalId>Manufacturer External Id</ManufacturerExternalId> 2 <TemplateName>Template Name</TemplateName> 3 <RootNodePath>Root Path node of the mapping</rootnodepath> 4 <ShareRootNode>true or false</sharerootnode> 5 <LinkedProfileCategoryName>Category Name</LinkedProfileCategoryName> 6 <UseReplaceCommandsOnly>true or false</usereplacecommandsonly> 7 <NodeNames> 8 <NodeName> <NodeRelativePath>Path of node on device</noderelativepath> <Name>Name</Name> </NodeName> </NodeNames> <NodeMappings> 9 <AttributeMapping> <AttributeName>Name of the attribute</attributename> <NodeRelativePath>Relative path of node on device</noderelativepath> </AttributeMapping>...other attribute mappings... </NodeMappings> <CanAssignToDevice>true or false</canassigntodevice> 10 </ProfileMapping> 1 <ModelName>. The name of the device model that the mapping applies to. Must exactly match a model name in the MDM server database. 2 <ManufacturerExternalId>. The manufacturer value for the device model. Must exactly match the value used in the MDM database. 3 <TemplateName>. The name of the profile template that the mapping applies to. Must exactly match a template name defined in this file or previously uploaded. 4 <RootNodePath>. The absolute path in the device tree that should be used when profile assignment is initiated. 5 <ShareRootNode>. Determines whether or not the mapping shares the root node for its category (as specified in the LinkedProfileCategoryName element. Values can be true or false. 6 <LinkedProfileCategoryName>. The category of the profile in the mapping. 10 <CanAssignToDevice>. Determines whether or not the profile can be assigned to the device. Can be true or false. 7 <UseReplaceCommandsOnly>. Can be true or false. When true, this directs the system to create only replace commands when provisioning. 8 <NodeNames>. Used to name nodes in the device tree, identifying them using the Name and NodeRelativePath elements. 9 <NodeMappings>. Used to map nodes in the device tree. See NodeMappings in a ProfileMapping element on page 229 for detailes of the structure of this element. 228 Advanced Operations

241 NodeMappings in a ProfileMapping element The NodeMappings element in a ProfileMapping element defines how the system gets the values of individual nodes. There are several methods, described in the subsections that follow. AttributeMapping and value translation The <AttributeMapping> element links an attribute name to a node-relative path on the device, so that you can set the value of a node from an attribute. If the device requires a specific value, you can also include an optional ValueTranslation element to change specific attribute values to different values. This means that you can select the value to send down to the device based on the value of an attribute, but you can send a value that is different than the attribute value. For example, the generic values used by the system for mailbox protocols are POP and IMAP, but Windows Mobile devices expect values of POP3 and IMAP4. To map these attributes, use code like the following: <AttributeMapping> <AttributeName>Mailbox Protocol</AttributeName> <NodeRelativePath>SERVICETYPE</NodeRelativePath> <ValueTranslations> <ValueTranslation> <Value>POP</Value> <DeviceValue>POP3</DeviceValue> </ValueTranslation> <ValueTranslation> <Value>IMAP</Value> <DeviceValue>IMAP4</DeviceValue> </ValueTranslation> </ValueTranslations> </AttributeMapping> where <AttributeName> is the attribute defined in profile template file <NodeRelativePath> is the relative path to the corresponding node on the device <Value> is the value defined in the AttributeType segment of profile template file <DeviceValue> is the value that needs to be sent to the device instead of <value> The result of using this mapping is that in the MDM console, the values displayed are still POP and IMAP, but when a CSR select either of these values for this model, then the value that is sent to the device is the <DeviceValue>. Profile metadata XML file reference 229

242 ValueMapping Use ValueMapping when you know that a particular node will always have a specific value for a certain profile. For example, the E61 GPRS NAP profile always has a bearer of GSM-GPRS because it is a NAP that uses GPRS. A value mapping like the following handles this case: <ValueMapping> <Name>Bearer Type</Name> <Value>GSM-GPRS</Value> <NodeRelativePath>NAPDef/#NoName#/Bearer/#NoName#/BearerL</NodeRelativePath> </ValueMapping> Note The #NoName# items are replaced with the value of the root node when the value is resolved. LinkedAttributeMapping Use LinkedAttributeMapping when you want to populate the value of a node with an attribute from a different category. For example, if the display name of the NAP service has to be the same as the one used for the Proxy profile template, then you could used LinkedAttributeMapping. If you have a GPRS NAP profile with the following mapping for its display name: <TemplateName>GPRS NAP</TemplateName> <RootNodePath>./AP/#NoName#</RootNodePath> <ShareRootNode>false</ShareRootNode> <NodeMappings> <AttributeMapping> <AttributeName>Display Name</AttributeName> <NodeRelativePath>NAPDef/#NoName#/Name</NodeRelativePath> </AttributeMapping> then you can use the same value in the Proxy profile template by coding it as follows: <TemplateName>Proxy with NAP</TemplateName> <RootNodePath>./AP/#NoName#</RootNodePath> <ShareRootNode>true</ShareRootNode> <LinkedProfileCategoryName>NAP</LinkedProfileCategoryName> <NodeMappings> <LinkedAttributeMapping> <LinkedAttributeName>Display Name</LinkedAttributeName> <LinkedProfileCategoryName>NAP</LinkedProfileCategoryName> <NodeRelativePath>Px/#NoName#/Name</NodeRelativePath> </LinkedAttributeMapping> Note The #NoName# items are replaced with the value of the root node when the value is resolved. 230 Advanced Operations

243 LinkedValueMapping Use LinkedValueMapping when you want to reuse a value you defined elsewhere. Using this method allows you to define a value in one place and refer to it from other places in the file. For example, suppose you wanted to reuse a value from your GPRS NAP profile in an with NAP profile. If the GPRS NAP has a value named Locked, defined as follows: <ValueMapping> <Name>Locked</Name> <Value>1</Value> <NodeRelativePath>NAPDef/#NoName#/Locked</NodeRelativePath> </ValueMapping> then the With NAP profile can use the following node mapping to reference the Locked value: <LinkedValueMapping> <LinkedName>Locked</LinkedName> <LinkedProfileCategoryName> NAP</LinkedProfileCategoryName> <NodeRelativePath>Locked</NodeRelativePath> </LinkedValueMapping> With these mappings, you can change the GPRS NAP value, and the with NAP profile will use the new value the next time it is assigned. Managing profile templates To access profile templates, click the Tenants tab, then click the Manage Profile Templates subtab. Details of each profile template may be viewed by clicking the Template Name. To delete a profile template, click the template name that you wish to delete and click Delete on the Profile Template Detail page. Importing profile templates Profile templates are provided as TAR package files. You can import new templates into the system via a command-line utility, the import utility. The import utility is provided as a shell script and a batch file (for use in both Solaris and Windows environments): startimport.sh and startimport.bat. The import-export utility takes an XML file, import.xml, as input. Before you run the utility, you must edit import.xml to indicate the location of the TAR file containing the new profile template, as described in the procedure below. The default location for initial data files is the setup data directory provided with the MDM distribution. Managing profile templates 231

244 Note Data in an import overrides any data currently residing in the system. If an import file contains the same models, profile templates, or profile mappings, the new data overrides the old. Importing a profile template 1. Make sure the environment variable JAVA_HOME is set to the directory that contains your Java installation. 2. Make sure the MDM Administration Server is running. 3. Copy the DM_server\importTool directory from the MDM distribution to a machine on the same network as the MDM managed servers. 4. Edit the provided import.xml file from the importtool directory. The import.xml file has the following structure. You only need to change values in the file; you do not need to add or change tags. <?xml version="1.0" encoding="utf-8"?> <import> <MDM> <dm-package-loc>/tmp/import/dm_dsl_package.tar</dm-package-loc> <mdm-server>holmium.idc.devlab.motive.com</mdm-server> <port>7001</port> <user-name>sspadmin</user-name> <password>motivemdm</password> </MDM> </import> Edit the <dm-package-loc> element to indicate the location of the TAR file that you plan to import, as a universal network location that is accessible to all of the MDM managed servers. Edit the <mdm-server> element to indicate the URL of the MDM server. Edit the <port> element to indicate the port number of the MDM server. Edit the <user-name> and <password> elements to indicate the username and password of the MDM server. 5. If you do not want to upload all of the devices in the TAR package, edit the list of devices within it. Each TAR package contains a file DeviceList.txt which lists the devices in the package. Each device is listed on a single line as two comma-separated fields, manufacturer and model: Nokia,E61 HTC,S620 These values correspond to directorys within the TAR file. To change the list, delete the lines for the devices you do not want to upload, then refresh the DeviceList.txt file within the TAR package. Note Do not modify the directory structure within the TAR file. 232 Advanced Operations

245 6. Execute the startimport.sh or startimport.bat file in the importtool directory. The system attempts to import profiles for each model listed in the DeviceList.txt file. If an import fails, the system moves on to the next model in the list until it has completed the list. When importing is complete, the system reports the number of successfully imported and failed models. If model mapping for a profile template fails, the system still imports the template. However, if model definition, bootstrap template or ddf import fails, then it does not import the template. Note If the system displays an error message like the following one, the Administration Server is not running. Start the Administration Server, then rerun the script. Error - Unable to call the service on MDM server, Check the server :( 500)Internal Server Error Standard profile templates This section contains descriptions of the standard templates. Bookmark Template Bookmark Template Details Managing profile templates 233

246 Bookmark with NAP Template Bookmark with NAP Template Details CSD NAP Template CSD NAP Template Details 234 Advanced Operations

247 Data Sync Template Data Sync Template Details Managing profile templates 235

248 Data Sync with NAP Template Data Sync with NAP Template Details 236 Advanced Operations

249 Data Sync with Proxy Template Data Sync with Proxy Template Details Device Lock Device Lock Template Details Managing profile templates 237

250 Device Wipe Template Device Wipe Template Details Template The following input parameters can be provided in any language that is supported by UTF-8 encoded scheme: Display name User Display Name Username Password Receiving Server Address Sending Server Address 238 Advanced Operations

251 Template Details with NAP Template The following input parameters can be provided in any language that is supported by UTF-8 encoded scheme: Display name Username Password Receiving Server Address Sending Server Address Managing profile templates 239

252 with NAP Template Details 240 Advanced Operations

253 Windows Mobile Template Windows Mobile 5 Template Details GPRS NAP Template The following input parameters can be provided in any language that is supported by UTF-8 encoded scheme: NAP ID Display name Bearer Direction NAP Address Address Type DNS Address Internet Managing profile templates 241

254 Locked Authentication Type Authentication Username Authentication Password AuthPrompt Install Application Template The following input parameters can be provided in any language that is supported by UTF-8 encoded scheme: AppName AppVersion Install App Template Details 242 Advanced Operations

255 Instant Messaging Template Instant Messaging Template Details Instant Messaging with NAP Instant Messaging with NAP Details Managing profile templates 243

256 Instant Messaging with Proxy Instant Messaging with Proxy Details MMS Template MMS Template Details 244 Advanced Operations

257 MMS with NAP Template MMS with NAP Template Details MMS with Proxy Template The following input parameters can be provided in any language that is supported by UTF-8 encoded scheme: Relay Server Address MMS with Proxy Template Details Managing profile templates 245

258 MS wifi Template MS wifi Template Details Proxy with NAP Template Proxy with NAP Template Details 246 Advanced Operations

259 Push to Talk Template Push to Talk Template Details Managing profile templates 247

260 Push to Talk with NAP Template Push to Talk with NAP Template Details 248 Advanced Operations

261 Push to Talk with Proxy Template Push to Talk with Proxy Template Details Secure Mail Template The following input parameters can be provided in any language that is supported by UTF-8 encoding scheme: Display name User Display Name Receiving Username Receiving Password Receiving Server Address Sending Server Address Sending Username Sending Password Managing profile templates 249

262 Secure Mail Template Details Secure Mail With NAP The following input parameters can be provided in any language that is supported by UTF-8 encoded scheme: Display name User Display Name Receiving Username Receiving Password Receiving Server Address Sending Server Address Sending Username 250 Advanced Operations

263 Sending Password Secure Mail With NAP Details Managing profile templates 251

264 Video Streaming Template Video Streaming Template Details Set a Policy Template Set a Policy Template Details 252 Advanced Operations

265 Video Streaming with NAP Template Video Streaming with NAP Template Details Video Streaming with Proxy Template Video Streaming with Proxy Template Details Managing profile templates 253

266 WiFi Template WiFi Template Details WLAN NAP The following input parameters can be provided in any language that is supported by UTF-8 encoded scheme: Display name SSID WepKeyData WepKeyId 254 Advanced Operations

267 WiFi Template Details Managing Attribute Types As profile templates are created, or need to be edited, attributes can be added or deleted. To review the attributes that make up Mobile Device Manager profile templates, click the Manage Attribute Types button at the bottom of the Manage Profile Templates page. To access profile templates, click the Tenants tab, then click the Manage Profile Templates subtab. Mobile Device Manager Attribute Types (continued) Attribute Type Name System Attribute Types APLink Binary Boolean Integer String Custom Attribute Types Description AP Link Binary Boolean Integer String Values <AP link value> <binary value> <true or false> <integer> <string> Managing Attribute Types 255

268 Mobile Device Manager Attribute Types (continued) (continued) Attribute Type Name Address Type Authentication Type Bearer Call Type Bearer Direction Bearer Link Speed Mailbox Protocol Proxy Service Type Description Format of the address Type of Authentication Data exchange protocol for CSD bearers Direction for the network type Speed on the channel for CSD bearers Mailbox protocol for Service used over Proxy Values APN E164 IPV4 IPV6 CHAP MD5 PAP ANALOG-MODEM ISDN V.110 ISDN V.120 Incoming Outgoing IMAP, POP HTTP, HTTP Secure, WAP, WAP Connectionless, WAP Secure, WAP Secure Connectionless To add an attribute 1. Click the Manage Attribute Types button on the Manage Profile Templates page (under the Tenant tab). The Manage Attribute Types page appears. 2. Click Add to use the Choose File dialog to locate the profile metadata XML file that has been provided by Motive Product Group. 3. Enter the attribute name and values (separate multiple possible values with a semicolon (;) and include a description of the attribute type. To delete an attribute type 1. Select one or more custom attribute types to be deleted. 2. Click Delete. Note System attribute types cannot be deleted. Uploading a profile metadata file The profile metadata file is required by the MDM Server so profiles can be created and assigned to devices. The profile metadata file is provided to the tenant by Motive Consulting Services. If upon uploading the profile metadata file you encounter any errors, contact Motive Consulting Services. 256 Advanced Operations

269 Note You cannot create or assign profiles to devices until you have successfully uploaded a properly formatted and validated Mobile Device Manager profile metadata file provided by Motive Product Group. To upload a profile metadata file 1. Click the Tenants tab, then click the Upload Profiles Metadata link in the header of the Tenants page. The Upload Profile Metadata page appears. 2. Click Browse to use the Choose File dialog to locate the profile metadata XML file that has been provided by Motive Product Group. 3. When located, select it and click Open, and the filename (and local path) is populated in the Metadata File input box. 4. Click the Load button. A very detailed Upload Profile Metadata Confirmation page appears, showing all of the details of the profile metadata to be uploaded. This page displays profile categories, attribute types, profile templates, and profile mappings for different OMA device models. See Understanding profiles on page 147 for more details about these different profile components that make up a profile metadata file. The MDM Server includes support for numerous models. Contact your Motive Sales representative for the latest list of supported device models. 5. After reviewing the details of the Upload Profile MetaData Confirmation page, click Confirm at the bottom of the page to accept the displayed profile details. The file was uploaded successfully appears when the profile upload is complete. Uploading a profile service file The profile service file is a comma delimited csv file. It carries a list of ServiceTag name and ServiceTagID number pairs. The file should be updated when a service provider wishes to provide a new service offering. The ServiceTag name when provided along with a profile template when assigning a profile. The profile template then becomes a part of the service. To Upload a profile Service file do the following: 1. Click the Tenants tab, then click the Upload Profile Service link in the header of the Tenants page. The Upload Profile Service File page appears. 2. Click Browse to use the Choose File dialog to locate the profile service file that has been provided by Motive Product Group. 3. When located, select it and click Open, and the filename (and local path) is populated in the CSV File input box. Uploading a profile service file 257

270 4. Click the Upload. A very detailed Upload Profile Services page appears, showing all of the details of the profile metadata to be uploaded. This page displays profile services that are created under The following profile services will be created, the profile services that are modified under The following profile services will be modified, the profile services that will be deleted under The following profile services will be permanently deleted. Profiles associated with templates will not be deleted. Note Profile templates that are associated with the deleted profile services are not deleted. 5. Click Submit to get the Upload Profile Services page. The text The file was uploaded successfully appears when the profile upload is complete. Managing DDFs Device Description Framework files, or DDF files, are files released by the mobile device manufacturers that specify the device management tree and its management objects for a device model. The MDM Server includes support for numerous models. Contact your Motive Sales representative for the latest list of supported device models. Note Under normal circumstances, the operator should not have to upload a DDF file, given that Motive s profile metadata file defines the appropriate profile mappings per model for supported profile templates. However, if the database becomes corrupt or you wish to perform OMA (Open Mobile Alliance) DM operations on a new model, then the model s DDF file needs to be uploaded via this option. Viewing a DDF Node Tree 1. Click the Models tab in the MDM Console main window. The Models page appears. 2. Click on a Model name in the list. The Model Detail page appears, including the currently defined values for the selected model. 3. At the bottom of the page, click Manage DDF. The DDFs page appears, for the selected model (if no DDFs exist for the selected model, this is indicated in place of a list). 4. Click View DDF. The View DDF page appears, for the selected model. Figure A.33, View DDF on page 259 shows an example of such a DDF, for the Nokia In the tree, each plus (+) node can be clicked on to expand additional nodes/node levels. Note also that the DTD version of the DDF is also shown in the right panel. 258 Advanced Operations

271 View DDF Uploading a DDF File To upload a DDF files to the MDM Server, follow these steps: Uploading a DDF File 259

272 1. Click the Models tab in the MDM Console main window. The Models page appears. 2. Click on a Model name in the list. The Model Detail page appears, including the currently defined values for the selected model. 3. At the bottom of the page, click Manage DDF. The DDFs page appears, for the selected model (if no DDFs exist for the selected model, this is indicated in place of a list). 4. Click Upload DDF. The Upload DDF page appears, for the selected model. Figure A.33, View DDF on page 259 shows an example of such a DDF, for the Nokia Click Browse and use the Choose file dialog to navigate to the properly formatted DDF file for the selected model. Select it and click [Open], and the filename (and local path) appears in the Upload DDF page. 2. Click Upload. An Upload DDF Confirmation page appears, showing listing the DDF filename that is being uploaded for the selected model. When done, the Model Detail page for the selected mode is again displayed. Deleting a DDF Node Tree To delete a DDF node tree, which may or may not be part of a larger DDF for a particular model, follow these steps: 1. Click the Models tab in the MDM Console main window. The Models page appears. 2. Click on a Model name in the list. The Model Detail page appears, including the currently defined values for the selected model. 3. At the bottom of the page, click Manage DDF. The DDFs page appears, for the selected model (if no DDFs exist for the selected model, this is indicated in place of a list). 4. Among the displayed DDF nodes, select the Node tree to be deleted by checking the adjacent box. 5. Click Delete. The Confirm Delete DDF page appears, for the selected DDF tree to be deleted. If the DDF is part of an assigned profile mappings, a warning statement appears. 6. Click Confirm to complete the deletion. Managing profile mappings Managing profile mappings allows the operator to either view available and generic profile templates stored in the MDM Server, or more importantly, view the profile mappings applied to and associated with a particular device model. 260 Advanced Operations

273 To review profile mapping options 1. Click the Models tab in the MDM Console main window. The Models page appears. 2. Click on a model name in the list. The system displays the Model Detail page, which shows the currently defined values for the selected model. 3. At the bottom of the page, click the Manage Profile Mappings button. The system displays the Manage Profile Mappings page, listing available templates for the selected device model. 4. Click on any template name link, to view a detailed list of attributes that make up a particular template. 5. Click the adjacent View link to view the mapped attributes for the selected template and device model. A View Profile Mapping Detail page appears. For more details on profile template attributes, see Managing profile templates on page 231. Managing CP profile mappings Managing profile mappings allows the operator to view, delete, and update CP profiles for a model. You update CP profiles by uploading a CP XML file, which you get from your Motive deployment team. Initial CP profiles are uploaded via the import tool (see Importing profile templates on page 231). To review and change CP profile mapping options 1. Click the Models tab in the MDM Console main window. The Models page appears. 2. Click on a model name in the list. The system displays the Model Detail page, which shows the currently supported profile template categories for the selected model. 3. At the bottom of the page, click the Manage CP Profiles button. The system displays the Manage CP Profile Mappings page, listing the supported template categories for the model. 4. To update the profile mappings: a. Click the Delete button to delete the existing CP profiles associated with the model. b. Click the Update button. Managing CP profile mappings 261

274 The system displays the Update CP Profiles page. c. Click the Browse button, then select the CP XML file to upload. d. When the appropriate file is selected, click the Upload button. Configuring bootstrap templates Bootstrap templates can accommodate variations required by the implementation of some model s bootstrap process. Templates for both plain and wap bootstrap types define parameter values for various bootstrap characteristics. Bootstrap Template Examples Provided below are examples for Both WAP and Plain Bootstrap types. WAP bootstrap template example #if ($omadevicebootstrapinfo.authenticationtype == "syncml:auth-basic") #set ($AUTH_PREF="BASIC") #end #if ($omadevicebootstrapinfo.authenticationtype == "syncml:auth-md5") #set ($AUTH_PREF="DIGEST") #end #if ($omadevicebootstrapinfo.authenticationtype == "syncml:auth-mac") #set ($AUTH_PREF="HMAC") #end ## Begin WAP Bootstrap document <wap-provisioningdoc version="1.0"> <characteristic type="bootstrap"> <parm name="provurl" value=" </characteristic> <characteristic type="napdef"> <parm name="napid" value="insgnapid"/> <parm name="name" value="$accesspointinfo.napname"/> <parm name="bearer" value="$accesspointinfo.napbearer"/> <parm name="nap-address" value="$accesspointinfo.napaddr"/> <parm name="nap-addrtype" value="$accesspointinfo.napaddrtype"/> #if( $accesspointinfo.napcalltype ) <parm name="calltype" value="$accesspointinfo.napcalltype"/> #end #if( $accesspointinfo.naplinkspeed ) 262 Advanced Operations

275 <parm name="linkspeed" value="$accesspointinfo.naplinkspeed"/> #end #if( $accesspointinfo.napauthtype ) <characteristic type="napauthinfo"> <parm name="authtype" value="$accesspointinfo.napauthtype"/> #if( $accesspointinfo.napauthname ) <parm name="authname" value="$accesspointinfo.napauthname"/> #end #if( $accesspointinfo.napauthsecret ) <parm name="authsecret" value="$accesspointinfo.napauthsecret"/> #end </characteristic> #end </characteristic> <characteristic type="application"> <parm name="appid" value="w7"/> <parm name="provider-id" value="$omadevicebootstrapinfo.omaserverid"/> <parm name="name" value="$omadevicebootstrapinfo.omaserveraccountname"/> <parm name="addr" value="$omadevicebootstrapinfo.omaserveraddress"/> <parm name="to-napid" value="insgnapid"/> <parm name="init"/> <characteristic type="appauth"> <parm name="aauthlevel" value="appsrv"/> <parm name="aauthname" value="$omadevicebootstrapinfo.omaserverid"/> <parm name="aauthsecret" value="$omadevicebootstrapinfo. omaserverpassword"/> <parm name="aauthdata" value="$omadevicebootstrapinfo. decodedomaservernonce"/> </characteristic> <characteristic type="appauth"> <parm name="aauthlevel" value="client"/> <parm name="aauthname" value="$omadevicebootstrapinfo.omaclientusername"/ > #if ($AUTH_PREF) <parm name="aauthtype" value="$auth_pref"/> #end <parm name="aauthsecret" value="$omadevicebootstrapinfo. omaclientpassword"/> <parm name="aauthdata" value="$omadevicebootstrapinfo. decodedomaclientnonce"/> </characteristic> </characteristic> </wap-provisioningdoc> Plain bootstrap template example #set ($SERVER_ID = "$omadevicebootstrapinfo.omaserverid") #set ($SERVER_NAME = "$omadevicebootstrapinfo.omaserveraccountname") #set( $DMACC_ROOT = "./SyncML/DMAcc/$SERVER_NAME" ) #set ($CON_ROOT = "./SyncML/Con/$SERVER_NAME" ) Bootstrap Template Examples 263

276 #set( $NAP_ROOT = "$CON_ROOT/NAP" ) #if ( $omadevicebootstrapinfo.omaserverportnbr == "" ) #set ($PORT_NBR = "80" ) #else #set ($PORT_NBR = $omadevicebootstrapinfo.omaserverportnbr ) #end #if ( $EXCLUDE_PORT_FROM_ADDRESS ) #set ( $OMA_SERVER_ADDRESS = $omadevicebootstrapinfo.omaserveraddressexcludingport ) #else #set ( $OMA_SERVER_ADDRESS = $omadevicebootstrapinfo.omaserveraddress ) #end #if ( $EXCLUDE_PORT_FROM_SOURCE_ADDRESS ) #set ( $OMA_SERVER_SOURCE_ADDRESS = $omadevicebootstrapinfo. omaserveraddressexcludingport ) #else #set ( $OMA_SERVER_SOURCE_ADDRESS = $omadevicebootstrapinfo.omaserveraddress ) #end <SyncML> <SyncHdr> <VerDTD>1.1</VerDTD> <VerProto>DM/1.1</VerProto> <SessionID>0</SessionID> <MsgID>0</MsgID> <Target> <LocURI>IMEI:$omaDeviceBootstrapInfo.deviceExternalId</LocURI> </Target> <Source> <LocURI>$OMA_SERVER_SOURCE_ADDRESS</LocURI> </Source> </SyncHdr> <SyncBody> <Add> <CmdID>1</CmdID> <Item> <Target> <LocURI>$DMACC_ROOT</LocURI> </Target> <Meta> <Format>node</Format> </Meta> </Item> <Item> <Target> <LocURI>$DMACC_ROOT/Addr</LocURI> </Target> <Data>$OMA_SERVER_ADDRESS</Data> </Item> <Item> <Target> <LocURI>$DMACC_ROOT/PortNbr</LocURI> </Target> <Data>$PORT_NBR</Data> </Item> 264 Advanced Operations

277 <Item> <Target> <LocURI>$DMACC_ROOT/AddrType</LocURI> </Target> <Data>$omaDeviceBootstrapInfo.omaServerAddressType</Data> </Item> <Item> <Target> <LocURI>$DMACC_ROOT/ServerId</LocURI> </Target> <Data>$SERVER_ID</Data> </Item> <Item> <Target> <LocURI>$DMACC_ROOT/ServerPW</LocURI> </Target> <Data>$omaDeviceBootstrapInfo.omaServerPassword</Data> </Item> <Item> <Target> <LocURI>$DMACC_ROOT/ServerNonce</LocURI> </Target> <Data>$omaDeviceBootstrapInfo.decodedOmaServerNonce</Data> </Item> <Item> <Target> <LocURI>$DMACC_ROOT/UserName</LocURI> </Target> <Data>$omaDeviceBootstrapInfo.omaClientUserName</Data> </Item> <Item> <Target> <LocURI>$DMACC_ROOT/ClientPW</LocURI> </Target> <Data>$omaDeviceBootstrapInfo.omaClientPassword</Data> </Item> <Item> <Target> <LocURI>$DMACC_ROOT/ClientNonce</LocURI> </Target> <Data>$omaDeviceBootstrapInfo.decodedOmaClientNonce</Data> </Item> <Item> <Target> <LocURI>$DMACC_ROOT/AuthPref</LocURI> </Target> <Data>$omaDeviceBootstrapInfo.authenticationType</Data> </Item> </Add> <Final/> </SyncBody> </SyncML> 265 Bootstrap Template Examples

278 266 Advanced Operations

279 This appendix covers: B Quick Start Reference Setting up initial database information Getting started 267

280 This section provides quick reference charts to illustrate the sequence of steps involved in the setup of initial database information. Setting up initial database information The following quick reference chart describes the steps involved in setting up initial database information for Mobile Device Manager. Note that subscribers and subscriber information is not added via the GUI, but rather through the Mobile Device Manager s OAMP web service or other means of import from the operator s subscriber database. 268 Quick Start Reference

281 Setup of Initial Database Information Getting started The following quick reference chart describes the navigation and use of the GUI functions to assign profiles (provision settings) and assign images (update a device s firmware) to a single device or a set of devices. Getting started 269

282 Basic Use of Mobile Device Manager 270 Quick Start Reference

283 Glossary bootstrapping The process of configuring a device or mobile handset such that it can establish a management session with a secure management server. Configuration Manager Browser-based interface that customer teams use to control the CSR experience within the applicable problem resolution application. In the Configuration Manager Console, a user sets up test modules that define a group of applicable tests; creates security groups to control CSR access, and sets properties to affect general behavior of the CSR application. CP (client provisioning) Initial over-the-air configuration of mobile devices through SMS messaging as defined by OMA CP. DS Server The application server component of Mobile Device Manager that enables backing up and restoring data on mobile handsets. FOTA (firmware over-the-air) Wireless mechanism for mobile subscribers to install and configure firmware upgrades on their handsets eliminating trips to a service center. MDM Console Browser-based application for mobile operators and terminal manufacturers who run FOTA and other device configuration updates OTA. Operators use the MDM Console to plan and manage data required to implement firmware and device configuration updates. For example, an operator populates the MDM Server with property details for data elements such as tenants, subscribers, devices, models, manufacturers, updates, and profiles; then, the operator uses the stored data to create jobs for provisioning and updating devices within the field. Provisioning requests are scheduled based on the timing requirements of the operator. At the scheduled times, applicable devices are updated. MDM Server The IP-based over-the-air server component of Mobile Device Manager. The Mobile Device Management Servers provide the core functionality to send configuration settings and firmware updates to mobile handsets. The servers support OMA-based CP and DM specifications. Mobile Device Manager Motive product that allows service providers to remotely provision, update, and manage mobile devices and services throughout the device life cycle. The product provides for individual and bulk device configuration, problem resolution, firmware upgrades, event management, user management, and reporting. 271

284 Mobile Device Manager includes two primary components, the MDM Server and the DS Server. Both use standards-based protocols, OMA DM and OMA DS, to communicate with the native DM and DS clients installed on mobile devices. OMA (Open Mobile Alliance) Organization that develops open specifications designed to facilitate interoperability in the mobile industry based on market requirements. For more information, see the OMA [ site. OTA (over-the-air) Wireless mechanism for sending provisioning data or updating firmware or software on mobile handsets. Typically, a device management client enables an OTA configuration. profile A collection of attributes for configuring a mobile device to provide for a particular service or function. Mobile Device Manager provides standard profile templates on which to base new profiles such as bookmark, data synchronization, , MMS, push to talk, and video streaming. SMS Short message service. SMS is available on most digital mobile phones that support short messages or text messaging between mobile devices. trunk code A number entered before the area code when dialing a long-distance number within the same country; it is omitted when dialing internationally. 272 Glossary

285 Index A AAA server, 60, 140, 143 advanced operations, 222 alerts OMA-DM 1.2 alert functionality user interaction alerts, model specific alerts, 116 Apache configuration, 102 configuring as proxy server, 103 installation, 102 installation and configuration, 102 assigning image to a device, 181 attribute types managing attribute types, 255 automated device configuration (ADC), 116 how ADC works? triplet information, 116 B bootstrap, 171 bootstrap template configuring bootstrap templates, 262 example, plain bootstrap template, 263 example, wap bootstrap template, 262 bulk management about bulk management, 194 device groups about, 201 creating, 202 deleting, 202 search templates about, 203 creating, 203 deleting, 204 updating, 203 uploading, 203 bulk operations canceling, 201 creating, 194 deleting, 197 details of a bulk operation, 199 managing search templates, 203 viewing bulk operations, 198 C command script sending a command script to a device, 180 comprehensive profile management, 117 DDF (device description framework), 118 profile assignment, 118, 148 profile mapping, 118 profile template, 118 configuration Apache, 102 configuration and post-installation activities, 54 configuration data for MDM Server installation clustered, 32 stand-alone, 16 connection types, 130 console installation Administration Server for clustered configuration, 35 Managed Server for clustered configuration, 42 standalone, 18 conventions documentation, xi countries about managing countries, 144 exporting countries, 147 uploading countries, 146 CP device provisioning, 261 standards and protocols, 113 supported settings, 113 D database, 89 database schema, 54 DDF (device description framework), 118, 147 deployment topologies, 4 273

286 device assigning an image to multiple devices, 182 assigning image to a device, 181 automated device configuration, 116 bootstrapping a device, 153 device activity logs, 213 diagnostics, 115 discovering a device node, 180 displaying a device tree, 186 firmware update, 126 history, 115 profile management, 119 provisioning, 119 sending a command script to a device, 180 device description format (DDF) deleting a DDF node tree, 260 managing DDFs, 258 uploading a DDF file, 259 viewing a DDF node tree, 258 device history, 115 device management capabilities, 112 device node, 180 devices about managing devices, 168 activating a device, 172 bootstrapping a device, 171 clearing jobs for a device, 172 creating a device, 171 deactivating a device, 172 deleting a device, 173 device properties description table, 169 editing device properties, 173 rebootstrapping a device, 171 viewing subscriber devices, 168 diagnostics, 115 device and service history, 115 device diagnostics, 115 visibility and device configuration, 115 DM device provisioning, 114 E error codes, 84 F fault tolerance, 120 firmware update dual-mode support OMA DM and OMA DL protocols, 114 firmware update life cycle management, 115 FOTA (firmware over-the-air), 114 G getting started, 4 granular scheduling, 120 GUI installation Administration Server for clustered configuration, 33 Managed Server for clustered configuration, 41 standalone, 16 H highly scalable, 120 host server requirements cluster, 6 standalone, 4 table, 5 I ICE workflows, 116 workflow uses, 116 IMEI, 117 IMSI, 117 initial data creation, 58 installation multicast, 56 installation and configuration clustered, 6 standalone, 4 installation prerequisites clustered, 8 standalone, 5 installation process summary cluster, 8 standalone, 6 Installing Kannel, 96 integrating the Mobile Device Manager with third party operators using web services APIs, 121 J JAVA_HOME environment variable, Index

287 L licensing, 56 logging audit logs, 214 device activity logs, 213 purging device activity logs, 213 system operations, 213 logging into the MDM console, 127 M managed servers, 216 managing countries country file format, 145 managing profiles about profiles, 147 manufacturers about managing manufacturers, 163 creating a manufacturer, 164 deleting a manufacturer, 165 viewing manufacturers, 164 MDM console, 127 MDM Server logs, 212 Mobile Device Manager components diagram, 113 Mobile Device Manager data model, 122 countries, tenants, and subscribers, 123 data elements, 123 manufacturers, models, and devices, 124 models and updates, 124 profile templates and profiles, 124 profile templates, profile mappings, and models, 126 profiles and service tags, 125 provisioning requests (jobs), 126 models about managing models, 158 creating a model, 161 deleting a model, 162 editing model properties, 162 model properties description table, 161 update CP models, 163 viewing models, 158 modular platform architecture, 112 monitoring mobile device manager with SNMP, 216 monitoring the provisioning request timer, 216 notifications, 216 monitoring the MDM Server, 108 MSISDN, 117 N notification links creating, 131, 132 creating (table of notification link properties), 131 deleting, 134 managing, 130 modifying, 132 testing, 132 uploading connection details, 132 viewing, 130 O OEM portal, 115 OMA (Open Mobile Alliance), 113 Oracle installation and configuration checklist, 86 installing, 87 installing the client, 88 pre-installation setup tasks as root user, 86 pre-installation setup tasks as the Oracle user, 87 verifying system requirements, 86 verifying the installation, 88 OTA (over-the-air), 127 P post-installation, 56 post-installation activities, 58 preparing for the installation clustered, 28 stand-alone, 12 profile assignments about managing profile assignments, 173 assigning a profile (for single device update), 174 comparing a profile assignment, 175 deleting a profile assignment, 178 editing a profile assignment, 178 fetching an assigned profile, 176 resending a profile assignment, 177 uploading a profile assignments file (for multiple device updates), 174 profile management and device provisioning how it works?,

288 profile management and device provisioning key concepts - diagram, 119 profile mappings managing CP profile mappings, 261 managing profile mappings, 260 profile metadata uploading a profile metadata file, 256 profile service file uploading my profile service file, 257 profile template bookmark template, 233 bookmark with NAP template, 234 CSD NAP template, 234 data sync template, 235 data sync with NAP template, 236 data sync with proxy template, 237 device lock template, 237 device wipe template, 238 template, 238 Windows mobile template, 241 with NAP template, 239 GPRS NAP template, 241 how to import, 231 install application template, 242 instant messaging template, 243 instant messaging with NAP, 243 instant messaging with proxy, 244 MMS template, 244 MMS with proxy template, 245 MS wifi template, 246 MS with NAP template, 245 proxy with NAP template, 246 push to talk template, 247 push to talk with NAP template, 248 push to talk with proxy template, 249 secure mail template, 249 secure mail with NAP, 250 set a policy template, 252 video streaming template, 252 video streaming with NAP template, 253 video streaming with proxy template, 253 wifi template, 254 wlan NAP, 254 profile templates managing, 231 reference to standard templates, 233 profiles about managing profiles, 147 creating a profile, 148 deleting a profile, 150 modifying a profile, 150 properties file silent-installer.properties, 22, 38, 46 silent_installer.properties, 47 provisioning requests about provisioning requests, 206 cancelling provisioning requests, 209 viewing provisioning requests, 206 provisioning requests (jobs) command script jobs, 126 device configuration (profile assignment) jobs, 126 firmware update jobs, 126 workflow jobs, 126 Q Quick Start Reference setting up initial database information, 268 R rebootstrap, 171 reports reporting statistics, 214 roles, 220 adding, 220 creating, 220 managing, 220 modifying, 220 S sample database creation, 106 installation, 106 verification, 106 scheduling device management jobs about scheduling device management jobs, 179 scheduling and notification options, 180 search criteria, 203 search templates, 203 service history, 115 silent installation Administration Server for clustered configuration, Index

289 Managed Server for clustered configuration, 46 standalone, 22 SMSC and Kannel gateway client installation and configuration, 96 starting and stopping the MDM Server stand-alone, 24 starting the gateway components, 97 starting the MDM Cluster, 48 stopping the MDM Cluster, 49 subscribers about managing subscribers, 152 activating a subscriber, 154 changing the status of a subscriber, 154 creating subscribers (bootstrap), 153 deactivating a subscriber, 155 deleting a subscriber, 155 subscriber properties description table, 153 viewing subscribers, 152 system overview, 4 T tenants about, 138 creating a tenant, 139 creating a tenant (table of tenant properties), 142 deleting a tenant, 144 editing tenant properties, 143 GPRS or CSD NAP template attributes, 142 managing, 138 viewing tenants, 139 troubleshooting checking the client/server communications, 83 error codes, 84 Oracle, 80 weblogic, 80 user adding a user, 77 user management on the MDM Server, 66 user roles and access permissions console access, 66 default users, roles, and permitted operations, 68 W web services APIs, 120 WebLogic adding new managed servers, 216 installation and configuration checklist, 92 installing the WebLogic server, 93 pre-installation setup task as root user, 92 verifying system requirements, 92 verifying the installation, 94 workflow job creating a workflow job, 184 deleting a workflow job, 185 renaming a workflow job, 185 updating a workflow job, 185 viewing a workflow job, 184 U updates about managing updates, 188 deleting an update, 191 discarding an update, 190 updates properties description table, 189 uploading a workflow, 189 uploading an update package, 189 viewing updates, 188 updating the MDM Cluster,

290 278 Index