1. Log in to the preconfigured BE WebLogic server machine as the Solaris user created for the MDM Server installation (for example,motive).
Important
Do not run the installation as 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. 2. Change your working directory to the one containing the installer executable. Launch the console MDM Serverinstallation program by using the command./MobileDeviceManager_Installer.bin.
■ If you are unable to launch the installer, then run the following command before launching the installer:Chmod +x MobileDeviceManager_Installer.bin.
■ To generate thesilent_installer.propertiesfile for use in a silent installation, use the command ./MobileDeviceManager_Installer.bin -r. Thesilent_installer.propertiesfile is generated
in the same directory.
You should see the following output on the console:
MDM Cluster Setup
42
Preparing to install...
Extracting the installation resources from the installer archive... Configuring the installer for this system's environment...
Launching installer...
Preparing CONSOLE Mode Installation...
=============================================================================== Mobile Device Management Server 1.00(created with InstallAnywhere by Macrovision) --- =============================================================================== Welcome
---
The Mobile Device Management Installer guides you through the installation and configuration of your Mobile Device Management Server.
It is strongly recommended that you quit all programs before continuing with this installation. You may cancel this installation at any time by clicking the 'Cancel' button.
Click the 'Next' button to proceed to the next screen. PRESS <ENTER> TO CONTINUE:
Press ENTER.
3. The License Acceptanceoutput appears:
=============================================================================== License Acceptance
---
Copyright 2007, Motive Communications
This software is the intellectual property of Motive and/or its licensors. You may not use this software for any purpose other than those indicated in the applicable software license between yourself and Motive. Other than as permitted under the Software License, you may not:
- disclose this software code to a third party
- copy the software, except as per license or with prior written permission from Motive
Motive Communications specifically retains title to and interest in all Motive software.
The Device Management Suite Software is furnished under a license and all use of this software product is strictly limited by its terms. The software may only be installed, used or copied in accordance with the terms of the license. Some or all of this work is covered by patent and/or copyright laws in the US, UK and other countries.
If You have a license with Motive for the Device Management Suite Software, check Agree to continue.
If You do not have a license with Motive for the Device Management Suite
43
Installing the MDM Managed Server
Software, check Disagree. The install will cease. Contact Motive for an applicable license.
->1- Agree 2- Disagree
ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT: 1
->1- Agree 2- Disagree
ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT:
Review the agreement. If you agree with the license terms, press ENTER to accept the default of 1. 4. 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- Adminstration Server for Cluster 3- Managed Server for Cluster
ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS <ENTER> TO ACCEPT THE DEFAULT : 3
Enter 3 to install the MDM Managed server.
5. The Installation Directory output appears on the console:
=============================================================================== Installation Directory
---
Where would you like to install the selected MDM server? Default Install Folder: /DMSuite
ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT : /opt/mdmManagedServer
INSTALL FOLDER IS: /opt/mdmManagedServer IS THIS CORRECT? (Y/N):
Enter the path to the directory where the MDM Managed Server is to be installed (for example,
/opt/mdmManagedServer). Press ENTER.
6. The BEA Home Directoryoutput appears on the screen. Enter the BEA home directory. For example:/opt/bea
.
7. The JDK Home Directoryoutput appears on the screen. Enter the JDK home directory. For example:
/opt/bea/jdk150_04.
MDM Cluster Setup
44
8. TheEnter the name of the machine hosting the MDM Server output appears on the screen. Enter the host name of the machine hosting the MDM Administration Server. Press ENTER.
Thenon-SSL Portoutput appears on the screen. Enter the non-SSL port number, and press ENTER. TheSSL Portoutput appears on the screen. Enter the SSL port number, and press ENTER.
TheUser nameoutput appears on the screen. Enter the WebLogic admin user name, and press ENTER. ThePasswordoutput appears on the screen. Enter the WebLogic admin password and press ENTER. 9. TheNode Manager Portoutput appears on the screen. Enter the port where the node manager is active. 10. TheUser nameoutput appears on the screen. Enter the user name for the Administration Server, and press
ENTER.
ThePasswordoutput appears on the screen. Enter the password for the Administration Server user, and press ENTER.
TheAdmin server hostoutput appears on the screen. Enter the host name of the machine hosting the MDM Administration Server, and press ENTER.
TheAdmin server portoutput appears on the screen. Enter the port number where the Administration Server is active, and press ENTER.
TheSSL Portoutput appears on the screen. Enter the SSL port number and press ENTER. 11. TheGet Audit Logging Leveloutput appears on the screen.
■ Enter1if you do not want any audit information to be logged.
■ Enter2if you want an intermediate level of audit information to be logged.
■ Enter
3if you want high-level audit information to be logged.
Press ENTER.
12. The server-specific information output appears on the screen. Enter theJMX portand press ENTER. The JMX port is the RMI registry port for connecting to the JMX agent.
The MDM server includes a client application for performing JMX monitoring. The default port number for communicating with JMX is 1100, but if the system you are installing on already has a service using port 1100, then select a different port number.
13. The Summary (Managed server) output appears, showing all the information entered so far. Review this screen carefully, and ensure that the values are accurate. Press ENTER to start the installation process.
14. TheInstallation Completeoutput appears on the screen. Press ENTER to exit the installer.
45
Installing the MDM Managed Server
15. After the installation is successful, go toChapter 4, “Configuration and Post-Installation Activities” on page 53.
To perform a silent installation
1. To perform a silent installation, you must set up thesilent_installer.propertiesfile. Thisproperties
file has all the relevant information required for the installation wizard to install the MDM Administration Server. 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=Managed_Server
#Do not change this value. This is the default installation mode. INSTALLER_UI=silent
# Directory where the MDM server is installed. #
USER_INSTALL_DIR=/opt/scandium/manageserver
#Specify the folder where Weblogic 9.2 is installed. The default value is provided ↲
below.
beaHome =/opt/bea
#Specify the folder where JDK is installed. It is preferred that you use the JDK ↲
that is provided with the Weblogic 9.2 installation. javaHome =/opt/bea/jdk150_06
#
# Cluster information required only for admin server installation. #
multicastAddress=234.234.234.234 multicastPort=234
#
# Admin server information for cluster deployment or single server information for ↲
standalone deployment. # adminServerPort =7001 adminServerHost =niobium.idc.devlab.motive.com adminServerSSLPort =7002 userName =weblogic password =weblogic #
# The port where Node manager is running. This is required only for the Managed ↲
server in a clustered deployment. # nodeManagerPort=5556 # MDM Cluster Setup 46
# 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=
2. Log in to the preconfigured BEA WebLogic server machine as the Solaris user created for the MDM Server installation (for example,motive).
Note
Do not run the installation as 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. 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.
47
Installing the MDM Managed Server
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. After the installation is successful, go toChapter 4, “Configuration and Post-Installation Activities” on page 53