MDM Server Deployment Guide

(1)

MDM Server Deployment Guide

(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

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)

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

2 Standalone MDM Server Setup ... 11

MDM Server installation process overview ... 12

Preparing for the installation ... 12

Installing the MDM Server ... 16

Starting and stopping the MDM Server ... 24

3 MDM Cluster Setup ... 27

MDM Cluster installation process overview ... 28

Preparing for the installation ... 28

Installing the MDM Cluster ... 32

Installing the MDM Administration Server ... 32

iii

Installing the MDM Managed Server ... 40

Starting and stopping the cluster ... 48

Starting the MDM Cluster ... 48

Stopping the MDM Cluster ... 49

Updating the MDM Cluster ... 50

Uninstalling the Managed Server ... 51

4 Configuration and Post-Installation Activities ... 53

Configuring the MDM Server ... 54

Configuring the MDM WebLogic domain ... 54

Creating the MDMAdmin role ... 55

Creating a user for WiDM webservice calls ... 56

Configuring multicasting ... 56

Licensing the installation ... 56

Storing your MDM product license ... 57

Initial data creation ... 58

Profile naming in a WiDM deployment ... 58

Creating notification links ... 59

Creating tenants ... 59

Load setup data ... 62

5 User Management on the MDM Server ... 65

User roles and access permissions ... 66

Adding a user ... 77

6 Troubleshooting ... 79

Verifying WebLogic is running ... 80

Verifying Oracle database and database connection ... 80

Managing Oracle database processes ... 81

Verifying Oracle database processes are running ... 81

Verifying the Oracle listener process is running ... 82

Viewing the services for which Oracle is listening ... 82

Checking client/server communications ... 83

Understanding error codes ... 84

7 Oracle Installation and Configuration Checklist ... 85

Verifying system requirements ... 86

iv

(5)

Performing prerequisite setup tasks as root user ... 86

Performing prerequisite setup tasks as the oracle user ... 87

Installing the Oracle 10g Enterprise Edition Server ... 87

Verifying your Installation ... 88

Installing the Oracle Client ... 88

Creating the MDM database and schema ... 89

8 BEA WebLogic Installation and Configuration Checklist ... 91

Verifying system requirements ... 92

Performing prerequisite setup tasks as root user ... 92

Installing WebLogic Server 9.2 ... 93

Verifying the installation ... 94

9 SMSC and Kannel Gateway Client Installation and Configuration ... 95

Installing Kannel ... 96

Starting the gateway components ... 97

10 Apache Installation and Configuration ... 101

Installing Apache ... 102

Configuring Apache ... 102

Configuring the Apache proxy server ... 103

11 Sample Database Installation for Standalone Server ... 105

Creating the database ... 106

Verifying the installation ... 106

12 MDM Server Monitoring ... 107

PART II

ADMINISTERING THE MDM SERVER

13 Mobile Device Manager Overview ... 111

Modular platform architecture ... 112

CP device provisioning ... 113

DM device provisioning ... 114

Firmware update ... 114

Diagnostics ... 115

v

(6)

Alerts ... 116

ICE™ workflows ... 116

Automated device configuration ... 116

Comprehensive profile management ... 117

Granular scheduling ... 120

Web services APIs ... 120

Highly scalable ... 120

Fault tolerance ... 120

Internationalization ... 120

Accessing the MDM console ... 121

Accessing the WebLogic Server Console ... 121

Mobile Device Manager integration with operator systems ... 121

Web service APIs ... 122

Mobile Device Manager data model ... 122

Countries, tenants, and subscribers ... 123

Manufacturers, models, and devices ... 124

Models and updates ... 124

Profile templates and profiles ... 124

Profiles and service tags ... 125

Profile templates, profile mappings, and models ... 126

Provisioning requests (jobs) ... 126

MDM Console ... 127

14 Managing SMSC/Notification Objects ... 129

Managing Connection Types ... 130

Managing notification links ... 130

Viewing notification links ... 130

Notification link parameters ... 131

Testing notification links ... 132

Creating or modifying a notification link ... 132

Notification link XML file structure ... 133

Deleting a notification link ... 134

15 Managing Tenants ... 137

About tenants ... 138

Viewing tenants ... 139

Creating a tenant ... 139

Troubleshooting tenant creation ... 142

vi

(7)

Editing tenant properties ... 143

Deleting a Tenant ... 144

Managing Countries ... 144

Country file format ... 145

Uploading countries ... 146

Exporting countries ... 147

Managing Profiles ... 147

Understanding profiles ... 147

Creating a profile ... 148

Modifying a profile ... 150

Deleting a profile ... 150

16 Managing Subscribers ... 151

Viewing subscribers ... 152

Creating subscribers (bootstrap) ... 153

Changing the status of a subscriber ... 154

Activating a subscriber ... 154

Deactivating a subscriber ... 155

Deleting a subscriber ... 155

17 Managing Models ... 157

Viewing models ... 158

Creating a model ... 161

Editing model properties ... 162

Deleting a model ... 162

Updating CP models ... 163

Managing Manufacturers ... 163

Viewing manufacturers ... 164

Creating a manufacturer ... 164

Deleting a manufacturer ... 165

18 Managing Devices ... 167

Viewing subscriber devices ... 168

Bootstrapping or rebootstrapping a device ... 171

Creating a device ... 171

Changing the status of a device ... 171

Activating a device ... 172

Deactivating a device ... 172

vii

(8)

Clearing jobs for a device ... 172

Editing device properties ... 173

Deleting a device ... 173

Managing profile assignments ... 173

Uploading a profile assignments file for multiple devices ... 174

Assigning a profile to a single device ... 174

Comparing a profile assignment ... 175

Fetching a profile assignment ... 176

Resending a profile assignment ... 177

Editing a profile assignment ... 178

Deleting a profile assignment ... 178

Scheduling device management jobs ... 179

Discovering a device node ... 180

Sending a command script to a device ... 180

Assigning an image to a device ... 181

Assigning an image to multiple devices ... 182

Managing workflows ... 184

Creating a workflow job ... 184

Viewing workflow jobs ... 184

Renaming a workflow job ... 185

Updating a workflow job ... 185

Deleting a workflow job ... 185

Displaying a device tree ... 186

19 Managing Updates ... 187

Viewing updates ... 188

Uploading an update package ... 189

Uploading a workflow ... 189

Discarding an update ... 190

Deleting an update ... 191

20 Bulk Management ... 193

Managing bulk operations ... 194

Creating bulk operations ... 194

Deleting bulk operations ... 197

Viewing bulk operations ... 198

Canceling a bulk operation ... 201

Managing device groups ... 201

viii

(9)

Creating a device group ... 202

Deleting a device group ... 202

Managing search templates ... 203

Creating a search template ... 203

Updating a search template ... 203

Deleting a search template ... 204

21 Managing Provisioning Requests ... 205

Viewing Provisioning Requests ... 206

Cancelling a Provisioning Request ... 209

22 Logging, Reporting, and Monitoring the System ... 211

MDM Server Logs ... 212

Reporting system operations ... 213

Device Activity Log ... 213

Purging Device Activity Logs ... 213

Audit Logs ... 214

Reporting Statistics ... 214

Understanding the Mobile Service Management Solution reports ... 215

Reports provided ... 215

Adding reports to new managed servers ... 216

Monitoring Mobile Device Manager with SNMP ... 216

Monitoring the provisioning request timer ... 216

Monitoring notifications ... 216

23 Managing Roles ... 219

Modifying a role ... 220

Adding new roles ... 220

A

Advanced Operations ... 221

Profiles, profile templates, and attributes ... 222

About profiles ... 222

Profile concepts diagram ... 223

Profile metadata XML file reference ... 224

Managing profile templates ... 231

Managing Attribute Types ... 255

Uploading a profile metadata file ... 256

ix

(10)

Uploading a profile service file ... 257

Managing DDFs ... 258

Viewing a DDF Node Tree ... 258

Uploading a DDF File ... 259

Deleting a DDF Node Tree ... 260

Managing profile mappings ... 260

Managing CP profile mappings ... 261

Configuring bootstrap templates ... 262

Bootstrap Template Examples ... 262

B

Quick Start Reference ... 267

Setting up initial database information ... 268

Getting started ... 269

Glossary ... 271

Index ... 273

x

(11)

Motive Mobile Device Managerallows 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 Serveruses the standards-basedOMADM protocol to communicate with the native DM client installed on mobile devices.

Audience

TheMDM Server Deployment Guideprovides 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).

Assumptions Audience

Part

Familiarity with networks, web application servers such as BEA WebLogic, WebLogic cluster deployment, and Oracle database technologies. Deployment team responsible

for installing and configuring the MDM Server deployment

Part I, “Installing the MDM Server” on page 1

(standalone or cluster). Typically, the team includes an architect, database administrator (DBA), network administrator, security administrator, and system administrator.

Familiarity with OMA (Open Mobile Alliance) standards,OTA (over-the-air)update technologies, Production team responsible

for administering system

Part II, “Administering the MDM

Server” on page 109 notification mechanisms, and network infrastructures.

information and managing devices by configuring and monitoring provisioning requests.

Conventions

This document uses the following typographic conventions:

xi

Audience

Preface

(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 theOnline Customer Support (OLCS)[https://support.alcatel-lucent.com] website. After registering and logging on, you can access troubleshooting information.

In addition, you can contact Alcatel-Lucent Motive Support by phone, fax, or email, as follows: 1-866-582-3688, option 1

Toll-free phone (within U.S.)

+1 613 784 6100 (United States) Outside U.S. 1-512-339-9040 Fax <[email protected]> Email

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 email to<[email protected]>.

Preface

xii

(13)

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”

Installing the MDM Server

(14)

(15)

1

This chapter covers:

■ Standalone MDM Server installation and configuration overview

■ MDM Cluster installation and configuration overview

3

Getting Started

(16)

This chapter introduces the installation and configuration processes for theMDM Servercomponent of theMobile Device Managersoftware 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-basedMDM Consoleor Web Service APIs.

Deployment topologies. Before beginning to install and configure the Mobile Device Manager system, plan your deployment strategy.

■ _{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. TheMDM Consoleis 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

Description MDM Server requirements Solaris 10 Operating system BEA WebLogic 9.2.2 Application server SMSC SMS gateway Getting Started 4

(17)

Host server requirements (continued)

Description MDM Server requirements

Oracle Client version 10g

Note

The versions of the Oracle client on the Administration Server host and the Database client

Oracle server software on the database host must match.

Oracle 10g Enterprise Edition

Note

Install the Oracle server and client on the same machine if you do not have Database server

another machine hosting the Oracle server.

36 GB disk space Hard disk space (minimum required)

2 GB RAM (4 GB recommended) RAM requirements

1 GHz UltraSparc IIIi processor (2 processors recommended) Processor

Administrative privileges required to complete these installations

Access

Network and administration requirements

The person who installs theMDM Servermust 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 theMDM Server, ensure that the following installation requirements are met:

5

Network and administration requirements

(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 9.2.2. A standalone BEA WebLogic application server must be installed and configured before the MDM Server is installed.

Installation process summary

This section summarizes theMDM Serverinstallation process for the standalone server deployment topology. Before proceeding, ensure that the system requirements listed in“Host server requirements” on page 4and“Network and administration requirements” on page 5are 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 theMDM Server. SeeChapter 2, “Standalone MDM Server Setup” on page 11.

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

Getting Started

6

(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

Description MDM Server requirements SunOS version 5.10 Operating system WebLogic 9.2.2 Application server

Oracle Client version 10g

Note

The versions of the Oracle client on the Administration Server host and the Database client

Oracle server software on the database host must match. Also ensure that the

SQLLDRis installed in thebindirectory

where the Administration Server's Oracle client is installed.

Oracle 10g Enterprise Edition

Note

Install the Oracle server and client on the same machine if you do not have Database server

another machine hosting the Oracle server.

MDM Administration Server: minimum 65 MB; WebLogic: 125MB; Oracle Client: 125 MB

Minimum hard disk space for MDM Administration Server host

MDM Managed Server: minimum 65 MB; WebLogic: 125MB; Oracle Client: 125 MB

Minimum hard disk space for MDM Managed Server host

2 GB recommended for Administration Server and Managed Servers

RAM

Administrative privileges required to complete these installations

Access

Network and administration requirements

The person who installs theMDM Servercluster must have system and network administration knowledge and access privileges:

7

Network and administration requirements

(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 theMDM 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 9.2.2. 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 6and“Network and administration requirements” on page 7are 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. SeeChapter 3, “ MDM Cluster Setup” on page 27for more information.

Getting Started

8

(21)

4. Install and configure the MDM Managed Servers. SeeChapter 3, “ MDM Cluster Setup” on page 27for more information.

5. Install the Motive Reporting application on at least one server in the MDM cluster.

9

Installation process summary

(22)

Getting Started

10

(23)

2

■ MDM Server installation process overview

■ Preparing for the installation

■ Installing the MDM Server

■ Starting and stopping the MDM Server

11

Standalone MDM Server Setup

(24)

This chapter describes how to install and set up theMDM Serveron a previously installed and configured BEA WebLogic application server.

For details on installing and setting up the WebLogic server, seeChapter 8, “BEA WebLogic Installation and Configuration Checklist” on page 91as 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 12to 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 theMDM Serverinstallation, 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 13and 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 namedsilent_installer.properties, which lists the corresponding property fields in thesilent_installer.propertiesfile. You can set the corresponding

values in that file and use the file for silent installation.

Standalone MDM Server Setup

12

(25)

Configuration data for MDM Server installation on standalone BEA WebLogic

server

Description silent_installer.properties Configuration data Single_Server

Type of installation CHOSEN_INSTALL_SET

The directory where the MDM Server is to be installed. Typically, this MDM Server installation directory USER_INSTALL_DIR

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.

Database user name dbuser

The password for the MDM schema owner the database script is to create. Password for database user name dbpassword

Network information about the configured MDM database:

Note

All of this Oracle database MDM Server Oracle network

information dbHost dbService dbTnsName dbPort 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

13

Preparing for the installation

(26)

Configuration data for MDM Server installation on standalone BEA WebLogic

server (continued)

Description silent_installer.properties

Configuration data

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.

BEA home directory beaHome

The fully qualified domain name of the machine hosting the WebLogic server on which the MDM Server is deployed.

WebLogic host name adminServerHost

Ports that allow administrative communication with the MDM Server:

adminServerPort

The non-SSL port, which is the unsecured access port for the WebLogic ports where MDM is

deployed

adminServerPort adminServerSSLPort

MDM Console. For example:

7001.

adminServerSSLPort

The SSL port, which is the secured access port for theMDM Console. For example:7002.

The user name used to log in to the WebLogic Server Console and perform WebLogic administrative activities. User name for the WebLogic server userName

The password used to log in the WebLogic Server Console and perform WebLogic administrative activities. Password for the WebLogic server user password

14

(27)

Configuration data for MDM Server installation on standalone BEA WebLogic

server (continued)

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.

External server information externalUrlHost externalUrlPort externalUrlSSLPort externalUrlContextPath

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

Java home directory javaHome

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

EitherTrueorFalse.

Phone number format displayTrunkCode phoneNumberMode CountryIsoCode phoneNumberMode Eithersingle_countryor multi_country. CountryIsoCode

The two-digit country code of the required country.

15

(28)

Configuration data for MDM Server installation on standalone BEA WebLogic

server (continued)

The level of audit information you want logged. The following values are allowed:

Audit logging level information auditLoggingLevel

full

intermediate none

The MDM server includes a client application for performing JMX

JMX port number jmxPort

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 therootuser, 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

(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.binand then run the installer.

ClickNext.

Note

The MDM Server version to be installed appears in the title of theWelcomescreen. Once installed, this information is available in theAboutarea of theMDM Console.

3. TheLicense Agreementscreen appears. Review the agreement, then selectI accept the terms of the License Agreement, and then clickNext.

4. TheInstall Setscreen appears. Select theSingle Standalone Serveroption.

5. TheInstallation Directoryscreen appears. Enter the path to the directory where the MDM Server is installed. For example:/opt/mdmSingleServer.

6. TheBEA Home Directoryscreen appears. Enter the path to the directory where WebLogic is installed. For example:

/opt/bea

7. TheJava Home Directoryscreen appears. Enter the path to the directory where JDK is installed. It is recommended that you use the JDK that comes with the WebLogic 9.2.2 installation. For example:

/opt/bea/jdk150_06

8. TheOracle Informationscreen 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. ClickNext.

9. TheWebLogic Server Informationscreen 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. ClickNext.

10. ThePhone Service Provider Informationscreen 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 10.

11. TheGet Phone Country ISO Code Informationscreen appears. Enter the ISO code for the single country phone number mode setting.

17

Installing the MDM Server

(30)

These codes can be found at the following site:http://www.iso.org/iso/en/prods-services/iso3166ma/ 02iso-3166-code-lists/list-en1.html

12. TheGet Audit Logging Level Informationscreen 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 theSSPAuditLogging.xmlfile isoptional

and the action isfalse.

■

none. None of the actions are logged.

The information in the log files corresponds to actions available in the MDM Console.

13. TheStandalone Server specific informationscreen appears. Enter theJMX portand clickNext. 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. TheExternal facing URL informationscreen 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 clickNextto continue.

15. TheSummary (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.

ClickInstallto continue.

16. TheInstalling Mobile Device Managerprogress screen appears as files are copied to the host server and installed.

When the installation is complete, anInstall Completescreen appears. ClickDoneto quit the installer. 17. After a successful installation, go toChapter 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

administrative privileges. This is the accepted best practice on Solaris machines for security reasons.

18

(31)

2. Make sure the installation.binfile 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_05032008.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. TheLicense Acceptanceinformation appears:

=============================================================================== License Acceptance

---(license text omitted here)

->1- Agree 2- Disagree

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

5. TheChoose Install Setoutput 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

Enter2to install the MDM Administration server.

6. TheInstallation Directoryoutput 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. TheBEA Home Directoryoutput appears on the screen. Enter the BEA home directory. For example:/opt/bea.

8. TheOracle Information - Usernameoutput appears on the console. Enter appropriate values in theEnter 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

(33)

Enter the Oracle service name and TNS name as you are prompted for them.

9. TheJDK Home Directoryoutput appears on the screen. Enter the JDK home directory. For example:

/opt/bea/jdk150_04.

10. TheHostnameoutput appears on the screen. Enter the host name of the machine hosting the BEA WebLogic application server. Enter the port number and press ENTER.

TheWebLogic non-SSL Portoutput appears on the screen. Enter the non-SSL port number and press ENTER. TheWebLogic SSL Portoutput appears on the screen. Enter the SSL port number and press ENTER.

TheDM Suite Server External IP Addressoutput appears on the screen. Enter the IP address of the proxy server you are using and press ENTER

11. ThePhone Display - Trunk Code Optionoutput appears on the screen. Enter1if you want thetrunk codeto

be displayed on the phone; otherwise, enter2. Press ENTER.

ThePhone Display - Single/Multi Country Codeoutput appears on the screen. Enter1if you want a single country code to be used; otherwise, enter2for multiple country codes. Press ENTER.

ThePhone Display - Country ISO Codeoutput appears on the screen. Enter the ISO code of the country you are in and press ENTER.

12. TheGet Audit Logging Leveloutput appears on the screen.

■ _Enter₁_{if you do not want any audit information to be logged.}

■ _Enter₂_{if you want an intermediate level of audit information to be logged.}

■ _Enter

3if you want high-level audit information to be logged.

Press ENTER.

13. TheExternal facing URL Host information output appears on the screen. Enter the fully qualified domain name of the external facing host, and press ENTER.

14. TheExternal facing URL non-ssl portoutput appears on the screen. Enter the non-SSL port number for the external facing host, and press ENTER.

15. TheExternal facing URL ssl portoutput appears on the screen. Enter the SSL port number of the external facing host and press ENTER.

16. TheExternal facing URL context pathoutput appears on the screen. Enter the context path to be appended to the redirected URL, and press ENTER. For example:/omadm/omadm.

17. TheCurrent Parametersoutput appears on the screen. Review the information that you have provided so far, and press ENTER to start the installation process.

21

(34)

18. TheInstallation Completeoutput appears on the screen. Press ENTER to exit the installer.

19. After the installation is successful, go toChapter 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

administrative privileges. This is the accepted best practice on Solaris machines for security reasons. 2. To perform a silent installation, you must set up asilent_installer.propertiesfile. Thisproperties

file has all the relevant information required for the installation wizard to install the MDM Administration Server. To create asilent_installer.propertiesfile, use aninstaller.propertiesfile generated from a prior installation (in the/tempdirectory) as a starting point, or get a samplesilent_installer.properties

file from the product distribution.

Edit the following samplesilent_installer.propertiesfile 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=234.234.234.234 multicastPort=234

#

22

(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=10.5.16.31 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

23

(36)

jmxPort=1100

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.

Note

The silent installation does not show any status on the console after the installation is complete. Verify that theMobile_Device_Management_Server_InstallLog.logis generated, and confirm

successful installation from the logs. The log files areerr.properties,script.log, and

wslt.log. They are in theMDMAdmin-Installation-directory/tempdirectory.

4. Then complete the steps inChapter 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:

http://admin-server-domain-name:7001/console/

Note

Use the same user name and password provided when installing the MDM Server.

2. In the main pane, click onServersin theEnvironmentlist in theDomain Configurationsarea.

3. In theSummary of Serverswindow, the MDM Server is listed in theNamecolumn in theServerstable. Click the server name to access theSettings for managed- server-namewindow.

4. Click theControltab, then click theStart/Stoptab. You have the option of forcing an immediate shutdown by usingShutdown->Force Shutdown Now, or requesting a shutdown after it completes all the jobs by using

Shutdown->when work completes. TheStateof the machine should indicateSTOPPED.

24

(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:

http://admin-server-domain-name:7001/console/

Note

Use the same user name and password provided when installing the MDM Server. 2. In theDomain Structurepanel on the left, click onDeployments.

3. In theSummary of Deploymentswindow on the right, the MDM applicationViperis listed inDeployments. 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}

requestsfrom theStartmenu.

■ _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 requestsfrom theStopmenu.

■ _Click_Yes_{in the}_{Stop Application Assistant}_window. ■ _The_State_{of the application should indicate}_Stopped_.

25

Starting and stopping the MDM Server

(38)

26

(39)

3

■ 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

MDM Cluster Setup

(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, seeChapter 8, “BEA WebLogic Installation and Configuration Checklist” on page 91as 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 7.

2. Prepare for the installation. See“Preparing for the installation” on page 28to properly prepare for the installation.

3. Install the MDM Cluster. See“Installing the MDM Cluster” on page 32for 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 28and 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 namedsilent_installer.properties, which lists the corresponding property fields in thesilent_installer.propertiesfile. You can edit the properties

and use the file for silent installation.

Configuration data for MDM Server installation on clustered WebLogic Server

Configuration Data

Admin server or Managed server. Type of installation CHOSEN_INSTALL_SET

MDM Cluster Setup

28

(41)

Configuration data for MDM Server installation on clustered WebLogic Server

(continued)

The directory where the MDM Server is to be installed. For example:

/opt/ mdmserver. MDM Server installation directory USER_INSTALL_DIR

The user who will be the owner of the MDM schema on the Oracle database. For example:MOTIVE.

Database user name dbuser

The password for the MDM schema owner the database script is to create. Password for the database user name dbpassword

Network information about the configured MDM database:

Note

All of this Oracle database MDM Server Oracle network

information dbHost dbService dbTnsName dbPort 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.

29

(42)

Configuration data for MDM Server installation on clustered WebLogic Server

(continued)

Description silent_installer.properties Configuration Data 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.

BEA home directory beaHome

The fully qualified domain name of the machine hosting the WebLogic server on which the MDM Server is deployed.

WebLogic host name adminServerHost

Ports that allow administrative communication with the MDM Server:

adminServerPort

The non-SSL port, which is the unsecured access port for the WebLogic ports where MDM

Administration Server is deployed

adminServerPort adminServerSSLPort

MDM Console. For example:

7001.

adminServerSSLPort

The SSL port, which is the secured access port for theMDM Console. For example:7002.

The user name used to log in to the WebLogic Server Console and perform WebLogic administrative activities. Administrative user name for the

WebLogic Administration Server

userName

The password used to log in to the WebLogic Server Console and perform WebLogic administrative activities. Password for the WebLogic

Administration Server user

password

The host name of the Administration Server, the port number, the secure Administration Server information adminServerHost

adminServerPort

port number, the admin user name, and the corresponding password.

adminServerSSLPort adminServerUserName adminServerPassword MDM Cluster Setup 30

(43)

Configuration data for MDM Server installation on clustered WebLogic Server

(continued)

The password used to log in to the WebLogic Server Console and perform WebLogic administrative activities. Cluster information for Administration

Server

Multicast Address Multicast Port

The host name of the Administration Server, the port number, the secure

Managed Server managedServerHost

managedServerPort

port number, the admin user name of

managedServerSSLPort

the Managed Server, the corresponding

managedServerUserName

password, and the port number of the node manager.

managedServerPassword nodeManagerPort

The externally available IP address for the MDM Server.

Note

In a clustered environment, this External facing URL information externalUrlHost

externalUrlPort externalUrlSSLPort externalUrlContextPath

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

Java home directory javaHome

comes with the WebLogic installation. For example:/opt/bea/jdk150_06.

31

(44)

Configuration data for MDM Server installation on clustered WebLogic Server

(continued)

Properties that specify the format in which the phone information appears. The following values are allowed:

displayTrunkCode

EitherTrueorFalse.

Phone number format displayTrunkCode phoneNumberMode CountryIsoCode phoneNumberMode Eithersingle_countryor 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:

Audit logging level information auditLoggingLevel

full

intermediate none

The MDM server includes a client application for performing JMX

JMX port number jmxPort

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.

MDM Cluster Setup

32

(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}

propertiesfile

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 commandChmod +x MobileDeviceManager_Installer.binand then run the installer.

ClickNext.

Note

The MDM Server version to be installed appears on theWelcomescreen. Once installed, this information is available in theAboutarea of theMDM Console.

3. TheLicense Agreementscreen appears. Review the agreement, then selectI accept the terms of the License Agreement, then clickNext.

4. TheInstall Setscreen appears. Select theAdministration Server For Clusteroption.

5. TheInstallation Directoryscreen appears. Enter the path to the directory where the MDM Server is installed. For example:/opt/mdmManagedServer.

6. TheBEA Home Directoryscreen appears. Enter the path to the directory where WebLogic is installed. For example:/opt/bea.

33

Installing the MDM Administration Server

MDM Server Deployment Guide