application lifecycle manager deployment guide version 3 · application lifecycle manager ......

Application Lifecycle ManagerDeployment Guide

Version 3.0

Application Lifecycle ManagerJune 2011Copyright 2008-2011 Alcatel-Lucent [http://www.alcatel-lucent.com]. 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, orotherwise, without the express permission of Motive, Inc. (Motive) and/or Alcatel-Lucent. This document and the related software may only beused 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 andsystems described in, this document, whether express, implied, or statutory, including without limitation implied warranties of merchantability orfitness 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 systemsowned by third parties. Please note that this information is provided as a courtesy to assist you. Such references are not intended to imply thegranting of a license to use such products and/or systems. Such licenses shall result only from separately executed agreements between you andthe owner of such products and/or systems. Neither Motive nor Alcatel-Lucent assume any responsibility or liability for incorrect or incompleteinformation provided about such third-party products.

Alcatel, Lucent, Alcatel-Lucent, the Alcatel-Lucent logo, Motive and the Motive logo are trademarks of Alcatel-Lucent. All other trademarks are theproperty 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, licensedor otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraftnavigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products couldlead directly to death, personal injury, or severe physical or environmental damage. You hereby agree that the use, sale, license or other distributionof the products for any such application without the prior written consent of either Motive or Alcatel-Lucent, shall be entirely at your sole risk. Youhereby agree to defend and hold Motive and Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise outof 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 adocument, the English version shall prevail.

3JB-00068-AAAC-TPZZA

http://www.alcatel-lucent.comhttp://www.alcatel-lucent.com

Introduction ................................................................................................................. viiAudience ..................................................................................................................... viiiConventions ................................................................................................................. viiiSupport and contact information ...................................................................................... viii

1 Installation .................................................................................................................... 1Previewing the ALM installation process .............................................................................. 2Conducting the required pre-installation tasks ....................................................................... 3

Understanding the ALM deployment scenarios ................................................................... 3Understanding the ALM pre-requisites .............................................................................. 4Understanding the required ports .................................................................................... 6Creating an Oracle user manually (optional) ..................................................................... 7Creating backups for the installation environment .............................................................. 8

Installing ALM ................................................................................................................. 8Understanding answer files ............................................................................................. 8Understanding the ALM sample answer file ....................................................................... 9Understanding the unique answer variables ..................................................................... 11Invoking answer file for ALM installation ......................................................................... 20

Conducting the post-installation and deployment tasks ......................................................... 23Configuring the ALM license ......................................................................................... 23Setting properties for using MDM with ALM (if applicable) ................................................ 24

Completing post-deployment tasks for using HDM with ALM (if applicable) .......................... 24Uninstalling and undeploying the ALM application ............................................................... 29

2 Administration and Configuration ............................................................................... 31Locating and logging onto the ALM Management Console ..................................................... 32Managing users and user authentication ............................................................................. 32

Understanding ALM groups ........................................................................................... 33

Understanding the ALM users ........................................................................................ 34Understanding ALM licenses ............................................................................................ 34

iii

Contents

Understanding the ALM interfaces ..................................................................................... 36Understanding the ALM Management Console ................................................................. 36Understanding the ALM Northbound Interface (NBI) ......................................................... 36

Finding and configuring application trace logging ................................................................ 36Trace logging levels ..................................................................................................... 37Understanding the default ALM logging and top-level Java packages .................................... 37Configuring ALM application trace log levels .................................................................... 38

Configuring an MDM installation to send notifications to ALM ............................................... 39Setting up additional search profiles for policies .................................................................. 43Flavor examples ............................................................................................................. 43Policy examples ............................................................................................................. 44

Policies to manage applications ..................................................................................... 44Policies to manage device health .................................................................................... 45

Configuring OSGi security ................................................................................................ 45Configuring system settings .............................................................................................. 46

3 Administering the Dashboard Console ........................................................................ 47Finding Dashboard resources ............................................................................................ 48Installing the Dashboard Console ...................................................................................... 48Licensing the Dashboard Console ...................................................................................... 49Logging into Dashboard Console ....................................................................................... 50Dashboard Console GUI ................................................................................................... 50Understanding a Dashboard Console deployment ................................................................. 51Understanding the dashboard-config.xml file ............................................................. 52

Sample XML Configuration File ..................................................................................... 53Threshold Configuration ............................................................................................... 72Uploading and downloading the configuration file ............................................................. 73

Understanding Dashboard counters and graphs ................................................................... 73Configuring counters and graphs .................................................................................... 74

Dashboard Console administration ................................................................................. 76

4 SMP Data Source .......................................................................................................... 79Understanding the ALM SMP data source ........................................................................... 80Requirements for deploying the ALM data source ................................................................ 81Installing and configuring the ALM data source ................................................................... 81

Installing the ALM Synchronous REST Service .................................................................. 81Installing the ALM data source in SMP applications .......................................................... 82Setting up SSL for the ALM data source .......................................................................... 82

iv

ALM data source reference ............................................................................................... 84Connection parameters ................................................................................................. 85Best practices ............................................................................................................ 85Data types .................................................................................................................. 85Methods ..................................................................................................................... 86

5 Troubleshooting ........................................................................................................... 93Glossary ....................................................................................................................... 95

Index .......................................................................................................................... 113

v

An offering in the portfolio of Alcatel-Lucent digital life management solutions, Application Lifecycle Manager enablesbroadband providers to remotely deploy and manage applications and services on devices. ALM supports dynamicinstallation and upgrading of application components and provides configuration and event notification services. A flexiblenorthbound interface supports integration into business networks.

Application Lifecycle Manager management capabilities include:

Device Management. Supports the necessary functions to inspect and update software on devices.

Application Creation Framework. Offers service providers a framework to assemble software components intoadded-value home services and applications. It helps to relieve your team of manual checks for component dependenciesand compatibility.

Application Lifecycle Management. Coordinates the installation and deployment of end-user services onmanaged devices.

Application Lifecycle Manager functionality includes application, deployment unit, and individual device life cyclemanagement, as well as the ability to apply policies on multiple devices. ALM enables you to upload deployment units(software components) to a File Server or specify the URL of a File Server where the deployment units already reside, inpreparation for download to a service device. It also features deployment unit management through the use of applications,which can be flagged for testing, for production, or for deprecation, the latter preventing them from being installed onthe device in the future.

Applications are defined using flavorss, which allow each application to store variant sets of deployment units andconfiguration information for devices with different requirements, and which allow the system to automatically choosethe appropriate flavor to install on a particular device. The system supports maintenance of configuration files and managedobjects for applications.

ALM is installed on top of one or more device managers, through which it communicates with clients using the TR-069protocol or the DM (device management) protocol. Its interfaces include the ALM Management Console and the ApplicationLifecycle Manager Northbound Interface (NBI). The ALM Management Agent provides a client-side interface that enablescommunication between the device and Application Lifecycle Manager through Home Device Manager.

This guide contains installation, administration, and configuration information for Application Lifecycle Manager. Fordetailed information about the ALM Management Console, see the ALM Management Console Help. For details about theALM Northbound Interface (NBI), see the Application Lifecycle Manager Programming Guide and the Application LifecycleManager: WSDL Reference.

vii

Introduction

Audience

The Application Lifecycle Manager Deployment Guide describes how to install, administer, and configure the product.This guide assumes that you understand how to use the device manager(s) you have selected for you deployment and theapplicable northbound interfaces (NBI). In addition, you should understand the OSGi framework and the architecture,terminology, and supported device protocols for your device manager..

Conventions

This document uses the following typographic conventions:

BoldIdentifies the names of graphical user interface buttons, options, commands, fields, and labels.

ItalicIdentifies variable placeholders such as function or method parameters representing information that must beprovided by the implementation or user. Also identifies documentation titles and certain terms to emphasize meaning.

MonospaceIdentifies information that you are required to type exactly as shown. This convention also identifiescode and command samples, screen prompts, messages, and filenames.

Monospace italicIdentifies parameters whose actual names or values you must provide at a screen prompt orin a text field.

UPPERCASEIdentifies 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) [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 1Toll-free phone (within U.S.)

+1 613 784 6100 (United States)Outside U.S.

1-512-339-9040Fax

Email

The Motive Product Group and its parent company, Alcatel-Lucent, are interested in feedback about your experience withthis product and its documentation. If you have comments or suggestions, send email to .

Introductionviii

https://support.alcatel-lucent.comhttps://support.alcatel-lucent.com

1This chapter covers: Previewing the ALM installation process

Conducting the required pre-installation tasks

Installing ALM

Conducting the post-installation and deployment tasks

Uninstalling and undeploying the ALM application

1

Installation

Previewing the ALM installation process

Installing Application Lifecycle Manager involves the following tasks:

Conduct the required pre-installation tasks:

Understand the ALM deployment scenarios

Understand the ALM prerequisites

Understand the required ports

Create an Oracle database user manually (optional)

Create backups for the installation environment

Use the ALM installer:

To create a standalone WebLogic Domain, Administration Server and a cluster with n number of ManagedServers for ALM

This deployment scenario is recommended, and it is required for deployments in which ALM is only usingMDM without also using HDM. See ALM deployed in its own WebLogic domain (recommended) on page 3and the applicable procedure, To install ALM in its own domain on a host slated for the Administration Serverand/or a Managed Server on page 20.

Or

To install and deploy ALM on Managed Servers in a HDM installation

This deployment scenario is not recommended; however, it is supported for deployments in which ALM isusing HDM. See ALM deployed in same domain as HDM on page 3 and the applicable procedure, Toinstall ALM on a Managed Server in a HDM domain on page 21.

Conduct the post-installation and post-deployment tasks:

Configure the ALM license unless configuring it with the LICENSE_STRING variable during ALM installation.For related information, see SSL and License answer variables on page 20.

Set the properties for using MDM with ALM (if applicable)

Complete the post-deployment tasks for using HDM with ALM (if applicable)

Installation2

Conducting the required pre-installation tasks

Understanding the ALM deployment scenarios

The recommended deployment scenario involves creating a WebLogic domain for ALM, including an Administration Serverand a cluster of one or more Managed Servers on which to install and deploy the product.

If the ALM deployment is to use HDM, other scenarios are supported. For information, see ALM deployed in samedomain as HDM on page 3.

ALM deployed in its own WebLogic domain (recommended)

In the recommended deployment scenario, your team invokes the ALM installer on the host slated for the AdministrationServer in addition to one or more hosts slated for Managed Server instances. ALM is installed and deployed on each ofthe latter instances.

The installer creates a domain named ALMDomain for the system, and the managed servers become part of an ALMCluster.

For instructions, see To install ALM in its own domain on a host slated for the Administration Server and/or a ManagedServer on page 20.

ALM deployed in same domain as HDM

If using ALM with HDM, it is supported to install and deploy ALM on Managed Servers created in the same domain asHDM. In the following table, compare the types of Managed Servers on which you can install and deploy ALM.

For instructions, see To install ALM on a Managed Server in a HDM domain on page 21.

Comparison: Managed Server types for the ALM application

CharacteristicsType

Dedicated Managed Server Instance created by the ALM installer as a part of the ALMinstallation/deployment processes

Installed as an instance either:

On the HDM Administration Server host

Or

3Conducting the required pre-installation tasks

Comparison: Managed Server types for the ALM application (continued)

CharacteristicsType

A remote host on which an instance of the HDM Managed Server isinstalled

Added to the HDMDomain but not added to the HDMCluster; instead,it is added to a cluster created for one or more ALM Managed Servers.

Runs a JMS Server and the ALM application

HDM Managed Server (notrecommended)

Instance created by HDM installer

Installed on any host in the Home Device Manager environment

Added to both the HDMDomain and the HDMCluster

Runs both the HDM applications and the ALM application

Understanding the ALM pre-requisites

For minimum system requirements and known issues, see the Application Lifecycle Manager Release Notes.

Home Device Manager and/or Mobile Device Manager

Before installing Application Lifecycle Manager (ALM), at least one of the following products must be installed, configured,and functioning correctly.

Home Device Manager 3.1. For Home Device Manager installation or upgrade instructions, see the Home DeviceManager Installation Guide, version 3.0.3. For system requirements, see the Home Device Manager Release Notes, version3.1.

Mobile Device Manager 3.1. For Mobile Device Manager installation or upgrade instructions, see the Mobile DeviceManager Deployment Guide, version 3.1. For system requirements, see the Mobile Device Manager Release Notes, version3.1.

Database Server

ALM requires a database instance running on one of the following Oracle Enterprise Edition server packages:

10g R2 version 10.2.0.4

Or

Installation4

11g version 11.2.0.2

The Oracle client version installed on the Administration Server should match the version of the Oracle server installedfor the database.

For related information, see Creating an Oracle user manually (optional) on page 7 and Database answervariables on page 14.

NoteIf using ALM with HDM, it is recommended to create the ALM database user on the same databaseinstance in which the HDM database user is created.

Oracle BEA WebLogic Server

ALM requires Oracle BEA WebLogic 11g PS2 (10.3.3 or 10.3.4). Before installing ALM, you can install WebLogic on thetarget machines. Alternatively, you can use the ALM installer to silently install WebLogic with an applicable installer (forexample, wls1034_generic.jar). For related information, see the answer variables in WebLogic Installer answervariables on page 11.

Java Development Kit (JDK)

ALM requires Java Development Kit (JDK) 1.6. Before installing ALM, you can install the JDK on the target machines.Alternatively, you can use the ALM installer to silently install the JDK with an applicable installer (for example,jdk-6u24-solaris-sparc.sh). For related information, see the entries for the Java variables in WebLogic andJava Installation answer variables on page 12.

File Server for deployment units (bundles)

Application Lifecycle Manager depends on a File Server to store deployment units for download by devices in the customerbase. The File Server includes a component server for deployment unit uploading and a component server for deploymentunit downloading. Most standard FTP and HTTP server components work with ALM, as long as the components supportuser name/password authentication or no authentication. Typically, the components are installed on the same host. Formore information, see the File server requirements section in the Application Lifecycle Manager Release Notes.

Supported protocols. Beginning with ALM 3.0, SFTP servers are supported for uploading bundles. Typically, SFTPservers are available on UNIX systems when the SSH daemon is installed.

Uploading bundles. FTP and SFTP

Downloading bundles. FTP, HTTP, and HTTPS

5Understanding the ALM pre-requisites

Before continuing, install a File Server with the FTP and HTTP components. In advance of each ALM installation, youneed to define the applicable variables. For details, see File Server answer variables on page 19.

Understanding the required ports

The following table lists the ports that must be open for an ALM deployment. It does not include ports required by HomeDevice Manager.

ALM required ports

PurposeSourceDestinationProtocolPort Number

Access to the ALMApplication Tier:

ManagementALM Applicationserver

HTTPS7006

ManagementConsole

NBI

Used by BEAWebLogic tools to

BEA WebLogicadministrator tools

ALM Applicationserver

T3S9004

administer and monitorthe server. This port isnot required for normaloperation.

Database access.ALM Applicationserver

Oracle serverJDBC1521

Upload of deploymentunits and configurationfiles.

ALM Applicationserver

ALM repositorySFTP22

Download ofdeployment units andconfiguration files.

ALM repositoryCPE (service gateway)HTTPS443

An NBI system canregister a SOAP

ALM ApplicationServer

ALM NBI systemHTTP(S)SOAP port

endpoint in ALM toreceived asynchronousnotifications. To makethis work, theappropriate port mustbe accessible. If theNBI system uses JMS

Installation6

ALM required ports (continued)

PurposeSourceDestinationProtocolPort Number

for notifications, this isnot required.

Creating an Oracle user manually (optional)

Application Lifecycle Manager depends on a database user to persist ALM data in an existing Oracle database instance.For related information, see Database Server on page 4.


The following table outlines the two ways to handle creation of the ALM database user.

Comparison: Creation methods for ALM database user

CharacteristicsMethod

Manually using a database tool suchas SQL*Plus

Enables configuring the ALM database user in a custom manner (forexample, with dedicated tablespaces)

The user created must include theconnect and resource privileges (for

Eliminates requirement to define the Database Administrator (DBA)credentials while installing ALM; this is only required when the installeris to create the ALM database userexample, grant connect,

resource to username) Requires setting the DROP_USER=n variable in the answer files for ALM

installations. In turn, the ALM installer:

Does not issue a drop user command for the specified database user

Does not attempt creating the specified database user

Automatically using the ALM installer Requires person who invokes the ALM installer and defines the answerfiles to know the Database Administrator (DBA) credentials

Requires setting the DROP_USER=y variable in the answer file used forinstalling the ALM Administration Server or only the first Managed ServerforALM deployments in a HDM installation. In turn, the ALM installer:

Drops the specified user (if the user exists in the specified databaseinstance). For example, this is useful in a re-installation scenario.

7Creating an Oracle user manually (optional)

Comparison: Creation methods for ALM database user (continued)

CharacteristicsMethod

Creates or re-creates the specified database user, whichever applicable.

Important For each ALM installation occurring after the database userfor ALM is created, set the DROP_USER=n variable in theanswer file. For example, DROP_USER=n is applicable when:

The DBA manually created the user before your team beganinstalling ALM on target hosts.

Or

Installing ALM subsequently after the user was createdduring the first ALM installation process, either for anAdministration Server and Managed Server or for the firstManaged Server in a HDM installation.

If the manual option is preferable, create the user now before continuing. For related information, see theDB_USER=ALM_DB and DB_USER_PW=ALM_DB entry in Database answer variables on page 14.

Creating backups for the installation environment

It is highly recommended to create backups of the following components before installing Application Lifecycle Manager:

Oracle database instance slated for ALM data

File system of all target hosts slated for ALM installations

Installing ALM

The primary method for installing and deploying ALM is invoking the provided ALM installer with an answer file.

Understanding answer files

You can use answer.txt files to install ALM. Answer files define variables and deployment-specific values for installations.There are two ways to use answer files:

1. Include all the deployment-specific values required to install.

Installation8

In this case, the installer does not prompt you for any values.

2. Include some of the required values to install.

In this case, the installer pre-populates the prompts with the values defined in your answer file, and it prompts forany required values not defined there.

Managed Server installations. For a cluster, you run the ALM installer once for each Managed Server instance;some configuration values must be unique per instance. As a result, edit your answer file before each installation.Alternatively, leave the Managed Server-specific values undefined in the answer file, and then provide them when prompted.

For example, pay special attention to the following answer variables. The MANAGED_SERVER_NAME property requires aunique value for each server instance. Similar to value for INSTALL_DIR, the port values must be unique for serverinstances on the same host. For related guidance, see ALM File System answer variables on page 13 and ManagedServer answer variables on page 16.

## Managed Server#MANAGED_SERVER_CREATE=yMANAGED_SERVER_NAME=ALM-ServerMANAGED_SERVER_PORT=7005MANAGED_SERVER_SSL_PORT=7006MANAGED_SERVER_ADMIN_PORT=9004MANAGED_SERVER_MACHINE=M_hostDEPLOY_APPLICATION=y#

Important For each ALM installation occurring after the database user for ALM is created, set the DROP_USER=nvariable in the answer file. For example, DROP_USER=n is applicable when:

The DBA manually created the user before your team began installing ALM on target hosts.

Or

Installing ALM subsequently after the user was created during the first ALM installation process, eitherfor an Administration Server and Managed Server or for the first Managed Server in a HDM installation.

Understanding the ALM sample answer file

This section provides a sample answer file for installing ALM. For guidance on setting the values, see the applicablesections in Understanding the unique answer variables on page 11.

## WebLogic Installer#BEA_INSTALL_FILE=/opt/installers/wls1034_generic.jarPROXY_HOST=proxy.mycompany.comPROXY_PORT=8080#

9Understanding the ALM sample answer file

# WebLogic and Java Installation#WL_HOME=/opt/alm30/wlserver_10.3JAVA_INSTALLER=/opt/installers/jdk-6u24-solaris-sparc.sh#JAVA_HOME=/opt/alm30/jdk160_24CREATE_SEPARATE_BEA_DOMAIN=y## ALM File System#INSTALL_DIR=/data/alm/install_3.0_separate/ALM-ServerINSTALL_OVERWRITE=y## Administration Server#BEA_ADMIN_HOST=admin.mycompany.comBEA_ADMIN_PORT=9002BEA_ADMIN_SERVER_SSL_PORT=9001BEA_ADMIN_USER=weblogicBEA_ADMIN_PW=w3blog!cAUTH_TYPE=default## Cluster#CLUSTER_NAME=ALMClusterCLUSTER_MULTICAST_ADDRESS=224.22.22.22CLUSTER_MULTICAST_PORT=3456## Database#DROP_USER=yDB_EXE=/opt/oracle/product/10.2.0.4/bin/sqlplusDB_SERVER=dbhost.mycompany.comDB_PORT=1521DB_SERVICE=serviceNameDB_DBA=systemDB_DBA_PW=passwordDB_USER=ALM_DBDB_USER_PW=ALM_DB## Node Manager#NODEMGR_PORT=5560## Managed Server#MANAGED_SERVER_CREATE=yMANAGED_SERVER_NAME=ALM-ServerMANAGED_SERVER_PORT=7005MANAGED_SERVER_SSL_PORT=7006MANAGED_SERVER_ADMIN_PORT=9004MANAGED_SERVER_MACHINE=M_hostDEPLOY_APPLICATION=y## HDM Applications#HNM_MANAGED_SERVER_NAME=hdm_7004HNM_JNDI_URL=t3s://hdm.mycompany.com:7004HNM_NBI_URL=https://hdm.mycompany.com:7004/remotehdm/NBIService

Installation10

HNM_NBI_USER=nbi_userHNM_NBI_USER_PW=password## File Server#REPOSITORY_DOWNLOAD_SERVER=repository.mycompany.comREPOSITORY_DOWNLOAD_ROOT=/downloadREPOSITORY_DOWNLOAD_PORT=443REPOSITORY_DOWNLOAD_PROTOCOL=ftpREPOSITORY_DOWNLOAD_USER=anonymousREPOSITORY_DOWNLOAD_PASSWORD=passwordREPOSITORY_UPLOAD_SERVER=repository.mycompany.comREPOSITORY_UPLOAD_ROOT=/uploadREPOSITORY_UPLOAD_PORT=22REPOSITORY_UPLOAD_PROTOCOL=ftpREPOSITORY_UPLOAD_USER=anonymousREPOSITORY_UPLOAD_PASSWORD=password## SSL and License## If installing into environment with# demonstration certificates, you must# remove the pound sign (#) to uncomment# and apply the FAKE_SSL_TRUST=y answer# variable.##FAKE_SSL_TRUST=y#LICENSE_STRING=125hwyuguabacwjfs

Understanding the unique answer variables

WebLogic Installer answer variables

BEA_INSTALL_FILE=/opt/installers/wls1034_generic.jar

Only applicable if Oracle BEA WebLogic 11g PS2 (10.3.3 or 10.3.4) is not yet installed on the host.

To have the ALM installer silently install WebLogic, specify the path up to and including the WebLogic installer.

If the WebLogic installer is generic (a .jar file), Java starts the silent installation process.

Note that the parent directory set in the WL_HOME variable is implemented for BEA_HOME. The parent directory iseverything in the string value except for wlserver_10.3 (for example, /opt/alm30/).

PROXY_HOST=proxy.mycompany.com and PROXY_PORT=8080Only applicable when setting BEA_INSTALL_FILE to silently install WebLogic.

Optionally, specify the fully qualified host name and port configured for an available Proxy Server. This helps overcomewaiting times when the installation host is on a system with blocked Internet access. Instead, you can apply emptyvalues for these variables.

11Understanding the unique answer variables

WebLogic and Java Installation answer variables

WL_HOME=/opt/alm30/wlserver_10.3

Specify the absolute path for the Oracle BEA WebLogic Server on the host. For example:

/opt/alm30/wlserver_10.3

where:

/opt/alm30/ is the root directory in which WebLogic is either to be installed or is installed on the host.

JAVA_INSTALLER=/opt/installers/jdk-6u24-solaris-sparc.sh

Only applicable when JDK 1.6 is not yet installed on the host; otherwise, the JAVA_HOME variable is applicable.

Specify the path to the JDK1.6 installer, which can be downloaded from the Oracle site. In turn, the JDK is installedin the BEA_HOME/jdk160 directory. At the same time, the JAVA_HOME variable is automatically set toBEA_HOME/jdk160.

where BEA_HOME is the parent directory set in the WL_HOME variable. The parent directory is everything in thestring value except for wlserver_10.3 (for example, /opt/alm30/).

For subsequent Managed Server installations on the same host, comment out the JAVA_INSTALLER variable byinserting a pound sign in front of it (for example, #JAVA_INSTALLER).

#JAVA_HOME=/opt/alm30/jdk160_24

Only applicable when JDK 1.6 is already installed; otherwise, the JAVA_INSTALLER variable is applicable.

To specify the path to an existing JDK installation on the host, uncomment the variable by removing the pound sign(#), and then configure the value as applicable.

CREATE_SEPARATE_BEA_DOMAIN=y

Specify whether to create a separate domain for ALM.

y to create a separate domain for the ALM deployment

The CREATE_SEPARATE_BEA_DOMAIN variable must be set to y if ALM is installed only for MDM. That isbecause ALM is installed on a JBoss application server. The ALM installer does not support installing ALM onJBoss.

Or

n to install ALM in the domain for an existing HDM installation.

Installation12

ALM File System answer variables

INSTALL_DIR=data/alm/install_3.0_separate/ALM-Server

Specify the path for the ALM file system. The installer creates the directory and copies various ALM files includingan uninstall script there.

NoteFor cluster installations with multiple Managed Servers on the same physical host, the value must beunique per Managed Server. That way, each Managed Server on the host has its own file system.

INSTALL_OVERWRITE=y

Specify whether to overwrite the directory specified with INSTALL_DIR variable given the directory exists.

y to overwrite the existing installation

Or

n to stop the installation process without overwriting the existing installation

Administration Server answer variables

BEA_ADMIN_HOST=almadmin.mycompany.com

Specify the fully qualified host name for the Administration Server.

BEA_ADMIN_PORT=9002

Specify the administrative port number for domain-wide administration on the Administration Server. If the defaultport number (9002) is in use on the Administration Server host, change the value; otherwise, leave the settingunchanged.

BEA_ADMIN_SERVER_SSL_PORT=9001

Specify the SSL port number for the Administration Server. If the default port number (9001) is in use on theAdministration Server host, change the value; otherwise, leave the setting unchanged.

BEA_ADMIN_USER=weblogic

Specify the user name for the Application Server Administrator account.

BEA_ADMIN_PW=w3blog!c

Specify the password for the Application Server Administrator account.

AUTH_TYPE=default

Specify the set of password requirements to implement:

default to implement fewer password constraints. The default configuration only permits authentication foraccount passwords that include eight or more characters, including at least two lowercase characters (for example,f and l).


Or

advanced to implement additional password constraints. The advanced configuration only permits authenticationfor account passwords with eight or more characters, including at least:

Two lowercase characters (for example, f and l)

Two uppercase characters (for example, F and L)

Two integers (for example, 0 and 9)

Two special characters (for example, & and !)

Cluster answer variables

CLUSTER_NAME=ALMCluster

Specify the name of the cluster.

CLUSTER_MULTICAST_ADDRESS=224.22.22.22

Specify the IP address configured or to configure for multicasting. The address is for messages used by ManagedServers within the cluster for server-to-server communications.

CLUSTER_MULTICAST_PORT=3456

Specify the port number configured or to configure for multicasting.

Database answer variables

For related information, see also Database Server on page 4 and Creating an Oracle user manually (optional) on page 7.


DROP_USER=y

Specify whether to create the specified database user or to use an existing user for ALM data.

y to drop the specified database user and then to create or re-create the specified database user, whicheverapplicable

Or

n to configure installation with the specified database user. The user must already exist in the specified databaseinstance.

Installation14

Important For each ALM installation occurring after the database user for ALM is created, set the DROP_USER=nvariable in the answer file. For example, DROP_USER=n is applicable when:

The DBA manually created the user before your team began installing ALM on target hosts.

Or

Installing ALM subsequently after the user was created during the first ALM installation process,either for an Administration Server and Managed Server or for the first Managed Server in a HDMinstallation.

DB_EXE=/opt/oracle/product/10.2.0.4/bin/sqlplus (conditionally required)Specify the absolute path to the Oracle client on the host.

If DROP_USER=y is specified, the DB_EXE variable must be specified with the applicable value.

DB_SERVER=dbhost.mycompany.com

Specify the fully qualified name of the host on which the Oracle database instance is installed (that is, the instanceslated for ALM tables and data).

DB_PORT=1521

Specify the port number for communication with the database instance. The default Oracle port value is: 1521.

DB_SERVICE=serviceName

Specify the Oracle database service name. The service name is used to uniquely identify the Oracle instance runningon the Oracle database. Sometimes this value is referred to as the SID.

DB_DBA=system and DB_DBA_PW=password (conditionally required)If a database user was created according to Creating an Oracle user manually (optional) on page 7, you do notneed to specify the DBA credentials.

For DB_DBA, specify the user name for the Database Administrator (DBA) account. This account has permissionsfor creating the ALM tables.

For DB_DBA_PW, specify the password for the Database Administrator (DBA) account.

If DROP_USER=y is specified, the DB_EXE variable must be specified with the applicable value.

DB_USER=ALM_DB and DB_USER_PW=ALM_DBSpecify the user name and password for the database user, either:

A database user that the installer is to create with default tablespaces in the specified database instance

To have the installer create the user, you must also specify the DBA credentials for the database instance withthe DB_DBA and DB_DBA_PW variables.

Or

An existing database user in the specified database instance


In this case, you do not need to specify the DBA credentials.

Node Manager answer variable

NODEMGR_PORT=5560

Specify the node manager port number configured or to configure for the Managed Server instance. If the defaultport number (5556) is in use on the host, change the default value; otherwise, leave it unchanged.

Managed Server answer variables

MANAGED_SERVER_CREATE=y (conditionally required)Specify whether to have the installer proceed with creating a Dedicated Managed Server:

y to create a Managed Server on the host from which the ALM installer is run.

Or

n to skip the installation process and configure an existing Managed Server in the HDMDomain.

If you specify the name for an existing Managed Server in the ALMDomain or the HDMDomain (withMANAGED_SERVER_NAME), the installer does not apply this answer variable.

MANAGED_SERVER_NAME=ALM-Server

Specify the name of the Managed Server. The name is either the name:

For a Managed Server that the installer is to create on the host from which the ALM installer is run. In this case,use the default value (ALM-Server) or a similar value. When creating multiple Managed Servers for a cluster,this value must be unique for each server instance.

Or

For an existing Managed Server in the ALMDomain or the HDMDomain. In this case, the value must be definedexactly as configured for the applicable server instance. By default, the HDM installer creates Managed Serverinstances with the host_7004 name format, where:

host is the short name for the Managed Server host

7004 is the SSL port configured for the Managed Server

MANAGED_SERVER_PORT=7005 (conditionally required)Specify the clear port number to configure for the Dedicated Managed Server. For example, the default value is:7005


Installation16

MANAGED_SERVER_SSL_PORT=7006 (conditionally required)Specifies the SSL port number to configure for the Dedicated Managed Server. For example, the default value is:7006


MANAGED_SERVER_ADMIN_PORT=9004 (conditionally required)Specifies the administration port number to configure for the Dedicated Managed Server. For example, the defaultvalue is: 9004

The administration port is used for communication with the Administration Server.


MANAGED_SERVER_MACHINE=M_host

Host computer (machine) on which the Dedicated Managed Server is to run. The default value is created dynamically.For example: M_host

where:

host is the short name for the host on which to create the Dedicated Managed Server and from which the ALMinstaller is run.


DEPLOY_APPLICATION=y

Specify whether to deploy the ALM application to the Managed Server during installation.

y: Deploys the ALM application. For deployments with a cluster, it is typical only to deploy on the first ManagedServer instance. WebLogic automatically deploys applications on subsequent instances in the cluster.

Or

n: Does not deploy the ALM application.

HDM Applications answer variables

If using ALM only with MDM (without HDM), the variables in this section are not applicable. In that case, apply emptyvalues for them.

HNM_MANAGED_SERVER_NAME=hdm_7004

Specify the exact name configured in the HDMDomain for the Managed Server on which the HDM applications aredeployed. For example: hdm_7004


where:

hdm is the short name for the Managed Server host

7004 is the SSL port configured for the Managed Server

HNM_JNDI_URL=t3s://hdm.mycompany.com:7004

Specify the JNDI URL over which JMS communication between ALM and HDM will occur. For example:

t3s:hdm.mycompany.com:7004/remotehdm/NBIService

Or

t3:hdm.mycompany.com:7003/remotehdm/NBIService

where:

hdm.mycompany.com is the fully qualified address for one of the following:

Northbound load balancer that fronts the HDMCluster

Instance of the application tier Managed Server

7004 is the SSL port

7003 is the clear port

HNM_NBI_URL=https://hdm.mycompany.com:7004/remotehdm/NBIService

Specify the URL for access to the Home Device Manager NBI. For example:

https:hdm.mycompany.com:7004/remotehdm/NBIService

Or

http:hdm.mycompany.com:7003/remotehdm/NBIService

where:

hdm.mycompany.com is the fully qualified address for one of the following:

Northbound load balancer that fronts the HDMCluster

Instance of the application tier Managed Server

7004 is the SSL port

7003 is the clear port

Installation18

HNM_NBI_USER=nbi_user

Specify the user name for an account that includes the permissions necessary for using the HDM NBI. By default,the HDM installer creates the nbi_user with these permissions.

HNM_NBI_USER_PW=password

Specifies the password for the Home Device Manager NBI user.

File Server answer variables

REPOSITORY_DOWNLOAD_SERVER=repository.mycompany.com

Specify the fully qualified address of the File Server host for bundle downloading.

REPOSITORY_DOWNLOAD_ROOT=/download

Specifies the root directory from which bundles are downloaded.

REPOSITORY_DOWNLOAD_PORT=443

Specifies the port for downloading bundles from the File Server.

REPOSITORY_DOWNLOAD_PROTOCOL=ftp

Specify the protocol for downloading bundles from the File Server.

REPOSITORY_DOWNLOAD_USER=anonymous

Specifies the user name for downloading bundles from the File Server.

REPOSITORY_DOWNLOAD_PASSWORD=password

Specifies the password of the user for downloading bundles from the File Server.

REPOSITORY_UPLOAD_SERVER=repository.mycompany.com

Specify the fully qualified address of the File Server host for bundle uploading.

REPOSITORY_UPLOAD_ROOT=/upload

Specifies the root directory in which bundles are uploaded.

REPOSITORY_UPLOAD_PORT=22

Specifies the port for uploading bundles to the File Server.

REPOSITORY_UPLOAD_PROTOCOL=ftp

Specifies the protocol for uploading bundles to the File Server.

REPOSITORY_UPLOAD_USER=anonymous

Specifies the user name for uploading bundles to the File Server.

REPOSITORY_UPLOAD_PASSWORD=password

Specifies the password of the user for uploading bundles to the File Server.


SSL and License answer variables

#FAKE_SSL_TRUST=y (conditionally required)Uncomment by removing the pound sign (#) to specify this only for a test environment in which the applicableWebLogic Server domain is not configured with production SSL certificates. In that case, the installation is dependenton demonstration certificates, and the FAKE_SSL_TRUST=y variable is required.

LICENSE_STRING=125hwyuguabacwjfs

Specify the license string for the application. For subsequent ALM installations, it is unnecessary to set the variable.Alternatively, your team can configure the license after installation. For instructions, see Configuring the ALMlicense on page 23.

Invoking answer file for ALM installation

To install ALM with an answer file, use the applicable procedure below:

To install ALM in its own domain on a host slated for the Administration Server and/or a Managed Server on page 20

Or

To install ALM on a Managed Server in a HDM domain on page 21

To install ALM in its own domain on a host slated for the Administration Server and/or a ManagedServer

1. Confirm that you have completed the tasks under Conducting the required pre-installation tasks on page 3.

2. On the host on which you are installing, perform the following commands to add a UNIX group and user:

groupadd almusersuseradd -m -d /opt/alm30 -g almusers almadmin

where:

/opt/alm30 is the ALM installation directory.

almusers is the new group.

almadmin is the new user.

3. On the command line, enter the following prompt to change the almadmin user password, and then type the newpassword at the prompts:

passwd almadmin

4. As the user created in Step 2, complete the following steps:

Installation20

a. Create a staging directory for the ALM installer, and then extract the alm-3.0-dist.tar file from theproduct CD into the directory. For example:

mkdir /opt/staging/alm30cd /opt/staging/alm30tar -xvf /dev/cdrom/alm-3.0-dist.tar

where:

/opt/staging/alm30 is the staging directory for the ALM installer.

/dev/cdrom/ is the location of the mounted ALM CD.

b. Create a text file with the installation-specific values for this ALM installation. For guidance, see the followingresources:

Understanding answer files on page 8

Understanding the ALM sample answer file on page 9

Understanding the unique answer variables on page 11

Important If installing into a test environment configured with demonstration certificates instead ofproduction SSL certificates, you must set the FAKE_SSL_TRUST=y property in the answerfile.

c. Run the installer:

cd /opt/staging/alm30sh ./alm-server-3.0.bin /full_path_to/answers.txt

where:

/opt/staging/alm30 is the staging directory created in Step 4.a.

/full_path_to/answer.txt is the path up to and including the name of the answer file created inStep 4.b.

The installer prompts for any invalid or missing values in the answer file. If successful, the following lineappears in output: Installation ok.

5. After a successful installation, continue with Conducting the post-installation and deployment tasks on page 23.If unsuccessful, try re-running the installer with careful attention to the values you type.

To install ALM on a Managed Server in a HDM domain

1. Confirm that you have completed the tasks under Conducting the required pre-installation tasks on page 3.

2. Open a shell and connect to the host in the Home Device Manager environment on which to install ALM. For relatedinformation, see ALM deployed in same domain as HDM on page 3.

21Invoking answer file for ALM installation

3. In the shell opened in Step 2, conduct the following steps:

a. Switch to the Solaris user that is configured to run the Home Device Manager processes on the host.

b. Create a staging directory for the ALM installer, and then extract the alm-3.0-dist.tar file from theproduct CD into the directory. For example:

mkdir /opt/staging/alm30cd /opt/staging/alm30tar -xvf /dev/cdrom/alm-3.0-dist.tar

where:

/opt/staging/alm30 is the staging directory for the ALM installer.

/dev/cdrom/ is the location of the mounted ALM CD.

c. Create a text file with the installation-specific values for this ALM installation. For guidance, see the followingresources:

Understanding answer files on page 8

Understanding the ALM sample answer file on page 9

Understanding the unique answer variables on page 11

Important If installing into a test environment configured with demonstration certificates instead ofproduction SSL certificates, you must set the FAKE_SSL_TRUST=y property in the answerfile.

d. Run the installer:

cd /opt/staging/alm30sh ./alm-server-3.0.bin /full_path_to/answers.txt

where:

/opt/staging/alm30 is the staging directory created in Step 3.b.

/full_path_to/answer.txt is the path up to and including the name of the answer file created inStep 3.c. The answer file defines the installation-specific values for installing and deploying the ALM on asingle Managed Server instance.

The installer prompts for any invalid or missing values in the answer file. If successful, the following lineappears in output: Installation ok.

4. After a successful installation, continue with Conducting the post-installation and deployment tasks on page 23.If unsuccessful, try re-running the installer with careful attention to the values you type.

Installation22

Conducting the post-installation and deployment tasks

Configuring the ALM license

If the ALM license was not configured during installation using LICENSE_STRING variable, use the following procedure;otherwise, skip to the next section.

To configure the ALM license

For more information on license options, see Understanding ALM licenses on page 34.

1. Acquire your license string from the Motive Product Group (if you do not already have it).

2. Log into the ALM Management Console:

a. In a browser, go to the following URL:

https://alm.mycompany.com:7006/alm

or

http://alm.mycompany.com:7005/alm

where:

alm.mycompany.com is the fully qualified address for one of the following:

Load balancer that fronts the ALM cluster.

One of the Managed Servers that hosts the ALM application.

7006 is the SSL port for the Managed Server.

7005 is the clear port Managed Server.

The login page appears.

b. In the Username field, type: almopmgr

c. In the Password field, type: password

NoteThe almopmgr/password credentials are for the default user created during the ALM installation.You can reset the almopmgr password through the WebLogic Server Console. For guidance, seeModify users [http://e-docs.bea.com/wls/docs92/ConsoleHelp/taskhelp/security/ModifyUsers.html]in Oracle's online BEA WebLogic Server documentation.

23Conducting the post-installation and deployment tasks

http://e-docs.bea.com/wls/docs92/ConsoleHelp/taskhelp/security/ModifyUsers.htmlhttp://e-docs.bea.com/wls/docs92/ConsoleHelp/taskhelp/security/ModifyUsers.html

d. Click the Log On button.

Until configuring the valid license string in the next step, the console is displayed with access to limitedfunctionality.

3. Configure the ALM license:

a. Click the System Settings tab.

b. On the row with the License property, paste your license string in the Value field.

Important The string must be pasted into the field as a single concatenated line.

c. Click the Save Changes button. The change is applied immediately.

4. Confirm that additional tabs are displayed in the interface now. With a valid license, more tabs should display,depending on the privileges configured for the logged-in user. By default and until otherwise changed, the almopmgruser includes all privileges for the ALM Management Console.

You can also select About->About, then select the License tab in the About dialog box to display details aboutthe installed license, such as the expiration date and capacity of the license.

Setting properties for using MDM with ALM (if applicable)

If the ALM deployment is not using Mobile Device Manager (MDM), skip this section and continue with Completingpost-deployment tasks for using HDM with ALM (if applicable) on page 24.

In the ALM Management Console, use the System Settings tab to set appropriate values for Mobile Device Managerby editing values on the MDM page in the Connectors folder of the System Settings. For instructions, see MDM in ALMManagement Console Help.

Completing post-deployment tasks for using HDM with ALM (if applicable)

If the ALM deployment is not using Home Device Manager (HDM), skip the following tasks; otherwise, complete them.

Enabling trust between separate ALM and HDM domains (if applicable)

For ALM deployments using HDM and for which the two products are installed in separate WebLogic domains(recommended scenario), you must enable trust between the domains. This applies even if the two domains are namedidentically.

Installation24

For instructions, see Enable trust between domains [http://download.oracle.com/docs/cd/E13222_01/wls/docs92/ConsoleHelp/taskhelp/security/http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/taskhelp/security/EnableGlobalTrustBetweenDomains.html] in the WebLogic documentation.

Creating the minimum ALM data objects in HDM

To use Application Lifecycle Manager with HDM, you need to create or import some data objects in the Home DeviceManager environment. To do so, create the data objects referenced in the table below.

ALM data objects to create through the HDM Management Console

Associated topic in HDM ManagementConsole Help

RequirementsData object

Adding device typesUse the ALM-provided device type XMLfile on the product CD:

OSGi framework devicetype

acs/hdm/devicetype/osgi1.0.xml

Depending on what the deploymentrequires, configure the device type forzero touch activation or pre-provisioned.

Adding actionsName: Enable active notificationsAction for enablingactive notifications

Action type: Set Parameter Attributes

Parameter: InternetGatewayDevice.Services.OSGi.BundleNumberOfEntitieswith:

Attribute Name: Notification

Attribute Value: Active

Adding policiesName: Force active notificationsPolicy for forcing activenotifications

Protocol: TR069v1

Action: Enable active notifications

Configure policy to be event-based andtriggered on Activation event

Set Initiate Connection on Requestdevice

25Completing post-deployment tasks for using HDM with ALM (ifapplicable)

http://download.oracle.com/docs/cd/E13222_01/wls/docs92/ConsoleHelp/taskhelp/security/http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/taskhelp/security/EnableGlobalTrustBetweenDomains.htmlhttp://download.oracle.com/docs/cd/E13222_01/wls/docs92/ConsoleHelp/taskhelp/security/http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/taskhelp/security/EnableGlobalTrustBetweenDomains.htmlhttp://download.oracle.com/docs/cd/E13222_01/wls/docs92/ConsoleHelp/taskhelp/security/http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/taskhelp/security/EnableGlobalTrustBetweenDomains.htmlhttp://download.oracle.com/docs/cd/E13222_01/wls/docs92/ConsoleHelp/taskhelp/security/http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/taskhelp/security/EnableGlobalTrustBetweenDomains.html

ALM data objects to create through the HDM Management Console (continued)



Managing criteria templatesName: Find failed or aborted devices forALM policy

Criteria template forenabling ALM toreinvoke policies onfailed devices 1. From the staging directory in which

the ALM installer was extracted(alm-3.0-dist.tar), open thefollowing file in a text editor:

acs/hdm/criteriatemplates/

findDevByALMBulkOperation

IdAndOperationState.xml

2. In the file, replace all instances ofALM_USER with the exact databaseuser name configured for the ALMdeployment (for example, ALM_DB).

That name was defined with theDB_USER variable in the answer fileused for installation or by the DBAwho manually created the user beforeALM was installed on target hosts.For related information, see theDatabase answervariables on page 14.

3. As the ALM database user (forexample, ALM_DB), use SQL*Plus tolog into the database instance thatincludes the ALM tables; then,execute the following commands.

GRANT SELECT ON GATEWAY to HDM_DB;GRANT SELECT ON COMMAND_HISTORY TO HDM_DB;

where HDM_DB is the name of thedatabase user originally definedduring HDM installation.

Installation26

ALM data objects to create through the HDM Management Console (continued)



NoteThe ALM and HDMdatabase tables mustbe created with userson the same Oracledatabase instance.

4. Upload the updated findDevByALMBulkOperationIdAnd

OperationState.xml file throughthe HDM Management Console. Asreferenced in next column, see theManaging criteria templates sectionin the HDM Management ConsoleHelp for guidance.

Configuring the JMS event notification settings in HDM

Application Lifecycle Manager depends on some JMS notification events of Home Device Manager. By default, the HDMinstaller sets the associated system settings to true, which is the configuration required for ALM. Even so, it is importantto validate that the properties have not been configured from their default values. As a result, complete the To validatethat the HDM JMS event notification properties are set to true on page 27 procedure. To identify the properties thatare a factor, see HDM JMS event properties that must be set to true on page 27 within the procedure.

To validate that the HDM JMS event notification properties are set to true

1. Log into the Server Configuration Console in the HDMDomain.

For guidance, see the Server Configuration Console entry in the Finding the HDM user interfaces topic of theHome Device Manager Deployment Guide.

2. For the applicable server instances and/or globally, double-check that the properties in the following list are set totrue; if not, change the values from false to true.

HDM JMS event properties that must be set to true

nbi.notification.send.DeviceActionResultEvent

nbi.notification.send.EventTriggeredPolicyResultEvent

27Completing post-deployment tasks for using HDM with ALM (ifapplicable)

nbi.notification.send.single.device.action.result

For guidance on editing property values, see the Server Configuration Console Help.

Confirming Java Messaging Service (JMS) communication

Once devices are active in your customer base and/or test environment, you can determine whether the associated JMScommunication between ALM and HDM is occurring. When a JMS connection is not established, server warning messagesabout failed JMS connections get written to the application trace log (every 5 seconds). If you are unsure of the log filelocation, see Finding and configuring application trace logging on page 36.

Log messages indicating a successful connection appear similar to the following:

14:59:55,270 INFO [DefaultMessageListenerContainer] Successfullyrefreshed JMS Connection

Error messages look similar to the following:

14:59:02,318 INFO [DefaultMessageListenerContainer]Could not refresh JMS Connection - retrying in 5000 ms:org.springframework.jndi.JndiLookupFailureException: JndiObjectTargetSourcefailed to obtain new target object; nested exception isjavax.naming.CommunicationException [Root exception isjava.net.ConnectException: t3://172.31.110.224:7003: Destination unreachable;nested exception is:java.net.ConnectException: Connection refused: connect;No available router to destination]

Filtering JMS messages

The following properties are available for filtering or blocking JMS messages in HDM:

nbi.notification.blocked.inform.eventcodes

nbi.notification.jms.blocked.events

nbi.notification.jms.blocked.registrations

nbi.notification.jms.blocked.results


nbi.notification.send.DeviceEvent



nbi.notification.send.UnknownGatewayEvent

NoteFor details on these properties, see the Home Device Manager Deployment Guide.

Because ALM relies on JMS notifications, the following properties must be set to true:

Installation28

nbi.notification.send.DeviceEvent

If this property is set to false, the following conditions occur:

Activation events are not sent to ALM. Thus, a device that is registered in HDM will not be registered in ALM.

Value Change Inform events are not sent. These events are generated by the Management Agent when the commandline of the device is used to make a manual state change of a bundle or property of an application. Thus, the ALMdatabase will not be synchronized automatically with the state change of the device.


If this property set to false, policies are not invoked on the devices.

Policies are specified in the ALM Management Console. Policies in ALM schedule the instant triggered policy witha simple CR action. As a result, every device that is targeted by the policy generates an NBI notification with theobject NBIDeviceActionResult. ALM listens for these messages, and based on the device ID and operation ID(which is the policy ID in ALM), ALM schedules an application operation per device.


If this property set to false, policies are not invoked on the devices.

Certain notifications should not be specified in the following properties:

nbi.notification.jms.blocked.results

This property should not contain NBIOperationResult, NBIBulkOperationResult, orNBIDeviceActionResult.

nbi.notification.jms.blocked.events

This property should not contain NBIDeviceInformEvent or NBIDeviceActivationNotification.

nbi.notification.blocked.inform.eventcodes

This property should not contain 2 PERIODIC if you want ALMs event-triggered policies to be able to receive theNEXTCONNECTION.

ALM is not dependent on the following properties:

nbi.notification.jms.blocked.registrations


nbi.notification.send.UnknownGatewayEvent

Uninstalling and undeploying the ALM application

Use the following procedure to uninstall Application Lifecycle Manager and undeploy the application from the applicableManaged Server without uninstalling Home Device Manager or other applications in the environment.

29Uninstalling and undeploying the ALM application

To uninstall and undeploy the ALM application

1. Before uninstalling components on the Solaris host:

Back up the data in the OLTP database.

Take a backup image of the host on which ALM is installed.

NoteIf reinstalling components after removing some or all of them, it is important to have the backups ofthe OLTP database and all local files and directories. That way, if necessary, you can restore the backupdata in future software versions.

2. As the Solaris user configured to run the ALM applications on the host, run the following commands:

cd /data/alm/install_3.0_separate/sh ./ALM-Server/uninstall.sh

where:

/data/alm/install_3.0_separate/ is the path to the top-level directory in which the ALM file system is located.

If you do not run the uninstaller from the top-level directory, the process cannot complete the last step ofremoving the ALM-Server directory.

install_3.0_separate is the root directory of the ALM file system for a Managed Server instance.

If successful, the following line appears in output:

Uninstallation ended successfully

3. Drop the ALM database user from the applicable Oracle database instance.

4. If the ALM application was deployed on a HDM Managed Server instead of a Dedicated Managed Server created bythe ALM installer, restart that server; otherwise, skip this step.

To do so, stop the Managed Server instance, and then start it again. For step-by-step instructions, see the stop andstart procedures in the Restarting application tier servers section of the Home Device Manager Deployment Guide.

Installation30

2This chapter covers: Locating and logging onto the ALM Management Console

Managing users and user authentication

Understanding ALM licenses

Understanding the ALM interfaces

Finding and configuring application trace logging

Configuring an MDM installation to send notifications to ALM

Setting up additional search profiles for policies

Flavor examples

Policy examples

Configuring OSGi security

Configuring system settings

31

Administration and Configuration

Locating and logging onto the ALM Management Console

Use the information in the following table to log onto the ALM Management Console.

ALM Management Console

The ALM Management Console is a secure, web-based user interface that enables remotemanagement of applications), deployment units, and the execution environments that run ondevices in the home environment.

Description

URL https://alm.mycompany.com:7006/alm

or

http://alm.mycompany.com:7005/alm

where:

alm.mycompany.com is the fully qualified address for one of the following:

Load balancer that fronts the ALM cluster.

One of the Managed Servers that hosts the ALM application.

7006 is the SSL port for the Managed Server.

7005 is the clear port Managed Server.

almopmgrDefault user name

passwordDefault password

Managing users and user authentication

User management involves configuring what constitutes a valid user name and password and what privileges (roles)groups and users have. The ALMDomain includes several default users and groups typically needed for a deployment.Each product installation process adds applicable minimum users, groups, and roles for using associated new functionality.

Roles can be assigned to users and groups. Users can be members of groups, and groups can be members of other groups.Role assignment is additive. If a user is a member of more than one group, that user has the roles of all the groups:

Administration and Configuration32

Users, groups, and roles

Roles

Users

Groups

In an Application Lifecycle Manager environment, you perform all user, group, and role management through the WebLogicServer Console. The console is accessible at: https://adminhost.yourcompany.com:9002/console where:

adminhost.yourhost is the address of the host on which the Administration Server for the ALMDomain (ortheHDMDomain, if installed along with HDM) is installed.

9002 is the domain-wide administration port of the Administration Server.

For information on the default users, groups, and roles for HDM, see the Home Device Manager Deployment Guide.

Understanding ALM groups

In installing ALM, several default users, groups, and roles are added to the ALMDomain (or the HDMDomain, wheninstalled along with HDM). Membership in a particular group adds to the roles (privileges) a user has. Users can also beadded to individual roles for a more granular control of privileges. In the following table, see the default group and roleassociations configured for ALM.

ALM groups

Associated privilegesGroup

Configure ALM system settingsALM_SYSTEM_MANAGER

33Understanding ALM groups

ALM groups (continued)

Associated privilegesGroup

Filter and delete devicesALM_DEVICE_MANAGER

Install, start, stop and uninstall deployment unitsALM_DU_LIFECYCLE_MANAGER

Create, update and delete applicationsALM_APPLICATION_MANAGER

Install draft applicationsALM_DRAFT_APPLICATION_MANAGER

Create, start, stop and delete policiesALM_POLICY_MANAGER

Perform NBI operationsALM_NBI_MANAGER

To view and modify group configuration, log onto the WebLogic Server Console and navigate toYourDomainName->Security Realms->myrealm->Users and Groups->Groups. For complete guidance onconfiguring groups, see Modify Groups [http://edocs.bea.com/wls/docs92/ConsoleHelp/taskhelp/security/ModifyGroups.html] in BEA's 9.2 version of Administration Console Online Help.

Understanding the ALM users

ALM adds the following users to the ALMDomain or the HDMDomain:

almopmgr user: Assigned to the ALM_SYSTEM_MANAGER, ALM_DEVICE_MANAGER,ALM_DU_LIFECYCLE_MANAGER, ALM_APPLICATION_MANAGER, and ALM_POLICY_MANAGER groups.

alm_nbi_user user: Assigned to ALM_NBI_MANAGER group.

Before any post-installation configuration occurs, the default users include group memberships, which in turn are associatedwith roles. For more information, see Understanding ALM groups on page 33.

To view user configuration from the WebLogic Server Console, navigate to YourDomainName->SecurityRealms->myrealm->Users and Groups->Users. For complete guidance on configuring users, see Modify Users[http://edocs.bea.com/wls/docs92/ConsoleHelp/taskhelp/security/ModifyUsers.html] in BEA's 9.2 version of AdministrationConsole Online Help.

Understanding ALM licenses

The ALM Management Console requires a license to access tabs in the user interface. Until a valid license has beenapplied, all tabs except the System Settings tab are deactivated.

To install an ALM license, log on to the ALM Management Console, click the System Settings tab, and paste the licensestring into the ALM license field. For more information, see Configuring the ALM license on page 23.


http://edocs.bea.com/wls/docs92/ConsoleHelp/taskhelp/security/ModifyGroups.htmlhttp://edocs.bea.com/wls/docs92/ConsoleHelp/taskhelp/security/ModifyGroups.htmlhttp://edocs.bea.com/wls/docs92/ConsoleHelp/taskhelp/security/ModifyGroups.htmlhttp://edocs.bea.com/wls/docs92/ConsoleHelp/taskhelp/security/ModifyUsers.htmlhttp://edocs.bea.com/wls/docs92/ConsoleHelp/taskhelp/security/ModifyUsers.html

License status. To view the status of the license of an ALM server, select the About link in the ALM console, andthen click the License tab.

License options. An ALM license provides the right to use the software on specific servers.

License tab fields

The License tab displays the following fields to describe your options.

License MessageIndicates whether the license is valid or not.

License Expiration DateThe date when the license expires.

Licensed Host IDsA list of host IDs that are allowed for this host.

Actual Host IDThe ID of the current host, for comparison with the Licensed Host IDs field.

Number of Active DevicesThe total number of devices that the system has communicated with. A device is considered active if the system hasreceived an activation event (from the relevant device manager) for that device, and the device has not been removedfrom the device manager.

Number of Licensed DevicesThe number of devices that the server is licensed to communicate with.

Number of Locked DevicesThe number of devices that have been activated, but can't be used because they exceed your license and have beenlocked. For example, if your license supports 100 devices, all devices activated after the first 100 will be in the lockedstate, and ALM will not perform operations on them.

PluginsThis section lists the available execution environment plugins and indicates, for each plugin, whether your licenseallows you to use it (indicated with true or false.

The available plugins are android, linux, and osgi.

Dashboard license. The Dashboard Console requires its own license, an HDM Dashboard License. Consult yoursales representative to get a license, in the form of a text file.

35Understanding ALM licenses

Understanding the ALM interfaces

Application Lifecycle Manager communicates with Home Device Manager through the Home Device Manager NorthboundInterface (NBI) (web services) and through the JMS channel of HDM NBI notifications. Using the ALM ManagementConsole, you can configure the HDM NBI URL, the HDM NBI user name and password, and the connection settings toHDM JMS topics.

Understanding the ALM Management Console

The ALM Management Console is a secure, web-based user interface that enables remote management of applications),deployment units, and the execution environments that run on devices in the home environment.

For log on instructions, see Locating and logging onto the ALM Management Console on page 32. For completeinstructions on using the console, see the ALM Management Console Help.

Understanding the ALM Northbound Interface (NBI)

The ALM Northbound Interface (NBI)provides methods that allow you to manage the life cycle of applications on devices.An application is something that can be started, stopped, installed, and uninstalled on a device. The applications thatyou manage with the NBI are referred to as applications in the ALM Management Console. The reason for this inconsistencyis that the ALM NBI is intended for other technologies (non-OSGi) as well, and those may not include the notion ofdeployment units.

For more information, see the Application Lifecycle Manager Programming Guide and the Application Lifecycle Manager:WSDL Reference.

Finding and configuring application trace logging

ALM writes its log entries to the Home Device Manager application trace on the Managed Server host on which it isinstalled:

/opt/alm/domains/ALMDomain/servers/managedserver_port/logs/trace_managedserver_port.log

where:

/opt/alm/ is the root installation directory.

managedserver is the name of the application tier Managed Server on which ALM is deployed.

port is the SSL port number of the Managed Server.


Trace logging levels

The installation process does not configure particular settings for ALM application logging. By default, ALM defaults tothe error level, which is the root log level for all Java packages set in the log4j.xml file on each Managed Server,including the Managed Server on which ALM is installed. You can override the root log level for particular Java packagesby configuring log levels in the log4j log file on a Managed Server, and then restarting the Managed Server. The supportedlog levels are:

debug

Writes all trace messages to the applicable log file, including debugging, informational, warning, error, and criticalfailure messages.

Debug messages are intended to provide detailed information about events useful for debugging an application.

info

Writes informational, warning, error, and critical failure messages to the applicable log file.

Info messages are intended to summarize the status of the application.

warn

Writes warning, error, and critical failure messages to the applicable log file.

Warn messages are intended to document potentially harmful events.

error

Writes error and critical failure messages to the applicable log file.

Error messages are intended to document events that are problematic yet may allow an application to continue running.

fatal

Writes only critical failure messages to the applicable log file.

Fatal messages are intended to document events that cause the application to stop running.

Understanding the default ALM logging and top-level Java packages

At installation, the root logging level is set to error. As a result, ALM system activity is logged at the error level untilthe global setting is changed or otherwise overridden for some of the log activity with a more granular log level property.The top-level ALM Java packages for which you can set a logging level are:

com.alcatel_lucent

37Trace logging levels

com.alcatel

com.alu

Configuring ALM application trace log levels

Configure application trace log levels through the log4j.xml file on the Managed Server host on which ALM is deployed.The log4j.xml file is located as follows:

On a dedicated Managed Server. alm_install_dir/log4j.xml. For more information about the dedicatedManaged Server deployment scenario, see Understanding the ALM deployment scenarios on page 3.

On an HDM Managed Server in a fresh HDM 3.0.0installation. /opt/hdm/domains/HDMDomain/servers/managedserver_port/logconfig/log4j.xml

On an HDM Managed Server in an installation upgraded to HDM 3.0.0. During an upgrade to 3.0.0, thelocation of the file is changed to /opt/hdm/domains/HDMDomain/servers/managedserver_port/logconfig/log4j.xml unless its location was changed from the default in 2.3.0. If the location was changed fromthe default in the 2.3.0 installation, that location is still used in 3.0.0.

where:

alm_install_dir is the root installation directory on a Managed Server in a dedicated Managed Server deploymentscenario (for details, see Understanding the ALM deployment scenarios on page 3).

/opt/hdm/ is the root installation directory on an HDM Managed Server.

managedserver is the name of the Managed Server.

port is the SSL port number of the Managed Server.

Configure the level in this section of the file:

For example, you might insert the following entries to change the logging level for the top-level ALM Java packages todebug:

For a description of valid values, see Trace logging levels in this section.

To identify more specific ALM packages for which to change the logging level, see the Java package hierarchy in the .jarfile in the WEB-INF/lib directory of the deployed application (webgui.war). The .war file is on a Managed Serverin the HDMDomain in the following directory:

path_to/domains/HDMDomain/servers/mgdName_port/stage/HSMApplication

where:

path_to is the path to the HDM installation on the Managed Server host on which ALM is installed.

mgdName is the name of the Managed Server.

port is the SSL port configured for the Managed Server.

Configuring an MDM installation to send notifications to ALM

When ALM is used with Mobile Device Manager (MDM), you must configure MDM to send notifications to ALM, byupdating the MDM system's Apache Camel configuration file and updating some of MDM's Server Configuration Consoleproperties. You must also create a device type in the ALM console.

The steps in this topic can also serve as a guide to the configuration required for any device manager, as similar stepswould be required for a different device manager.

To configure MDM to send notifications to ALM

1. Determine if you need to install security certificates.

If you are using production certificates, install the appropriate certificate to allow your managed server(s) tocommunicate with MDM.

If you are using a demo certificate in your WebLogic Application Server installation, and want to use it tocommunicate with MDM, then complete the following steps to configure it:

a. Copy the file DemoTrust.jks from the WebLogic installation (in the$BEA_HOME/wlserver_10.3/server/lib/DemoTrust.jks) to the MDM machine.

b. Add the following property to the runjboss.sh file (in the $MDM_JBOSS_HOME/bin directory):

-Djavax.net.ssl.trustStore=/full_path_to/DemoTrust.jks

c. Restart the MDM server. See the MDM Server Deployment Guide for instructions.

39Configuring an MDM installation to send notifications to ALM

2. Add elements to your Apache Camel configuration file (camelcontext.xml). For instructions, see Configuringnotifications through the Camel XML file in the MDM Server NBI Guide.

The following sample file defines an endpoint with the id alm and creates routes that send specific events to it.

java.lang.Exception

true


41Configuring an MDM installation to send notifications to ALM

3. Update MDM Server Configuration Console properties as described in the following table. For more information,see Setting server properties in the MDM Server Deployment Guide.

New valueProperty

truenbi.send.devicebootstrapped.event

truenbi.send.devicejobresult.event

truenbi.send.devicedeleted.event

The folder containing the updated camel configuration file.camel.file.reload

4. In the MDM Console, create an action that executes a DM Bootstrap command. For instructions, see Addingactions in the MDM Console Help.

5. As a final step, configure ALM to receive notifications. In the ALM Management Console, create at least one devicetype for devices managed through MDM:

a. Select the Device Types tab, then click the Add Device Types button.


b. For a device type, you can specify three values. For an MDM device, select IMEI in the Address Class field,then enter a Make and Model (for example, Nokia and E61.

c. Click the Ok button.

Setting up additional search profiles for policies

Search profiles determine the initial list of devices that are addressed by an instant-triggered policy; this list is then filteredby the constraints you establish for the policy.

The list of search profiles that is available in ALM is derived from the criteria templates loaded in Home Device Manager.To add a new search profile, create a new criteria template (or import one) in the Home Device Manager console, thenrefresh the list of search profiles as described in the ALM Management Console Help.

One criteria template, FindDevicesByServiceTag, is required to enable ALM to reinvoke policies on devices where thepolicy failed initially. The template is provided with Home Device Manager, but must be imported. See Creating theminimum ALM data objects in HDM on page 25 for more information.

Flavor examples

Each application contains one or more flavors. A flavor defines a set of deployment units and configuration informationthat are appropriate for some set of devices. Each flavor also contains constraints that can limit which devices it is installedon.

When more than one flavor is defined, the system compares the properties of a target device with the constraints andexecution environments defined for each flavor until it finds the appropriate flavor to install on that device. Flavors allowyou to target the installation of a particular application version to multiple devices, and have the system determine whichflavor is appropriate for each device.

The following examples may help provid

application lifecycle manager deployment guide version 3 · application lifecycle manager ......

Documents