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) <support@motive.com> 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 <pubs@motive.com>. 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