Application Lifecycle Manager Deployment Guide

(1)

Application Lifecycle Manager

Deployment Guide

(2)

Application Lifecycle Manager June 2011

Important Notice to Users

No part of this document may be reproduced or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the express permission of Motive, Inc. (“Motive”) and/or Alcatel-Lucent. This document and the related software may only be used pursuant to a Software License Agreement or other similar written agreement in place between you and either Motive or Alcatel-Lucent. Furthermore, Motive and Alcatel-Lucent expressly disclaim any and all warranties regarding the information contained in, and the products and systems described in, this document, whether express, implied, or statutory, including without limitation implied warranties of merchantability or fitness for a particular purpose. Furthermore, this document is subject to change without notice.

There may exist in this document references to using this product and the systems described herein in connection with products and/or systems owned by third parties. Please note that this information is provided as a courtesy to assist you. Such references are not intended to imply the granting of a license to use such products and/or systems. Such licenses shall result only from separately executed agreements between you and the owner of such products and/or systems. Neither Motive nor Alcatel-Lucent assume any responsibility or liability for incorrect or incomplete information provided about such third-party products.

Alcatel, Lucent, Alcatel-Lucent, the Alcatel-Lucent logo, Motive and the Motive logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners.

The products and systems described herein may be covered by the various patents that have been issued to Motive and/or Alcatel-Lucent.

Disclaimers

This product is intended for commercial uses. Without the prior written consent of either Motive or Alcatel-Lucent it must not be used, sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. You hereby agree that the use, sale, license or other distribution of the products for any such application without the prior written consent of either Motive or Alcatel-Lucent, shall be entirely at your sole risk. You hereby agree to defend and hold Motive and Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications.

This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail.

3JB-00068-AAAC-TPZZA

(3)

Introduction ... vii

Audience ... viii

Conventions ... viii

Support and contact information ... viii

1 Installation ... 1

Previewing the ALM installation process ... 2

Conducting the required pre-installation tasks ... 3

Understanding the ALM deployment scenarios ... 3

Understanding the ALM pre-requisites ... 4

Understanding the required ports ... 6

Creating an Oracle user manually (optional) ... 7

Creating backups for the installation environment ... 8

Installing ALM ... 8

Understanding answer files ... 8

Understanding the ALM sample answer file ... 9

Understanding the unique answer variables ... 11

Invoking answer file for ALM installation ... 20

Conducting the post-installation and deployment tasks ... 23

Configuring the ALM license ... 23

Setting properties for using MDM with ALM (if applicable) ... 24

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

Uninstalling and undeploying the ALM application ... 29

2 Administration and Configuration ... 31

Locating and logging onto the ALM Management Console ... 32

Managing users and user authentication ... 32

Understanding ALM groups ... 33

Understanding the ALM users ... 34

Understanding ALM licenses ... 34

iii

Understanding the ALM interfaces ... 36

Understanding the ALM Management Console ... 36

Understanding the ALM Northbound Interface (NBI) ... 36

Finding and configuring application trace logging ... 36

Trace logging levels ... 37

Understanding the default ALM logging and top-level Java packages ... 37

Configuring ALM application trace log levels ... 38

Configuring an MDM installation to send notifications to ALM ... 39

Setting up additional search profiles for policies ... 43

Flavor examples ... 43

Policy examples ... 44

Policies to manage applications ... 44

Policies to manage device health ... 45

Configuring OSGi security ... 45

Configuring system settings ... 46

3 Administering the Dashboard Console ... 47

Finding Dashboard resources ... 48

Installing the Dashboard Console ... 48

Licensing the Dashboard Console ... 49

Logging into Dashboard Console ... 50

Dashboard Console GUI ... 50

Understanding a Dashboard Console deployment ... 51

Understanding the

dashboard-config.xml

file ... 52

Sample XML Configuration File ... 53

Threshold Configuration ... 72

Uploading and downloading the configuration file ... 73

Understanding Dashboard counters and graphs ... 73

Configuring counters and graphs ... 74

Dashboard Console administration ... 76

4 SMP Data Source ... 79

Understanding the ALM SMP data source ... 80

Requirements for deploying the ALM data source ... 81

Installing and configuring the ALM data source ... 81

Installing the ALM Synchronous REST Service ... 81

Installing the ALM data source in SMP applications ... 82

Setting up SSL for the ALM data source ... 82

iv

(5)

ALM data source reference ... 84

Connection parameters ... 85

Best practices ... 85

Data types ... 85

Methods ... 86

5 Troubleshooting ... 93

Glossary ... 95

Index ... 113

v

(6)

vi

(7)

An offering in the portfolio of Alcatel-Lucent digital life management solutions,Application Lifecycle Managerenables broadband providers to remotely deploy and manage applications and services ondevices. ALM supports dynamic installation and upgrading of application components and provides configuration and event notification services. A flexible

northbound interfacesupports 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 into}

added-value home services and applications. It helps to relieve your team of manual checks for component dependencies and compatibility.

■ _{Application Lifecycle Management.} _{Coordinates the installation and deployment of end-user services on}

managed devices.

Application Lifecycle Manager functionality includesapplication,deployment unit, and individual device life cycle management, as well as the ability to applypolicieson multiple devices. ALM enables you to upload deployment units (software components) to aFile Serveror specify the URL of a File Server where the deployment units already reside, in preparation 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 on the device in the future.

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

ALM is installed on top of one or more device managers, through which it communicates with clients using theTR-069

protocol or theDM (device management)protocol. Its interfaces include the ALM Management Console and the Application Lifecycle Manager Northbound Interface (NBI). The ALM Management Agent provides a client-side interface that enables communication between the device and Application Lifecycle Manager through Home Device Manager.

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

vii

Introduction

(8)

Audience

TheApplication Lifecycle Manager Deployment Guidedescribes 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 the applicable northbound interfaces (NBI). In addition, you should understand theOSGi frameworkand the architecture, terminology, and supported device protocols for your device manager..

Conventions

This document uses the following typographic conventions:

■ _Bold_{—Identifies the names of graphical user interface buttons, options, commands, fields, and labels.}

■ _Italic_{—Identifies variable placeholders such as function or method parameters representing information that must be}

provided by the implementation or user. Also identifies documentation titles and certain terms to emphasize meaning.

■ _Monospace_{—Identifies information that you are required to type exactly as shown. This convention also identifies}

code and command samples, screen prompts, messages, and filenames.

■ _{Monospace italic}_{—Identifies parameters whose actual names or values you must provide at a screen prompt or}

in a text field.

■ _{UPPERCASE—Identifies the names of keys on the keyboard.}

■ _{In multi-line code listings, the}_⇦_{symbol indicates that the text was wrapped for typographical reasons.}

Support and contact information

If you encounter issues with this product, visit theOnline Customer Support (OLCS)[https://support.alcatel-lucent.com] website. After registering and logging on, you can access troubleshooting information.

In addition, you can contact Alcatel-Lucent Motive Support by phone, fax, or email, as follows:

1-866-582-3688, option 1

Toll-free phone (within U.S.)

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

The Motive Product Group and its parent company, Alcatel-Lucent, are interested in feedback about your experience with this product and its documentation. If you have comments or suggestions, send email to<[email protected]>.

Introduction

viii

(9)

1

This 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

(10)

Previewing the ALM installation process

InstallingApplication Lifecycle Managerinvolves 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 Managed}

Servers for ALM

This deployment scenario isrecommended, and it is required for deployments in which ALM is only using MDM without also using HDM. See“ALM deployed in its own WebLogic domain (recommended)” on page 3

and the applicable procedure,“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 and deploy ALM on Managed Servers in a HDM installation}

This deployment scenario isnot recommended; however, it is supported for deployments in which ALM is using HDM. See“ALM deployed in same domain as HDM” on page 3and the applicable procedure,“To install 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)}

Installation

2

(11)

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 Server and 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 same domain 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 Administration Server in addition to one or more hosts slated for Managed Server instances. ALM is installed and deployed on each of the 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 Managed Server” 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 as HDM. 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

Characteristics Type

Dedicated Managed Server ■ _{Instance created by the ALM installer as a part of the ALM}

installation/deployment processes

■ _{Installed as an instance}_either_:

❐ _{On the HDM Administration Server host}

Or

3

Conducting the required pre-installation tasks

(12)

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

Characteristics Type

❐ _{A remote host on which an instance of the HDM Managed Server is}

installed

■ _{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 (not recommended)

■ _{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 theApplication 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 theHome Device Manager Installation Guide, version 3.0.3. For system requirements, see theHome Device Manager Release Notes, version 3.1.

Mobile Device Manager 3.1. For Mobile Device Manager installation or upgrade instructions, see theMobile Device Manager Deployment Guide, version 3.1. For system requirements, see theMobile Device Manager Release Notes, version 3.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

Installation

4

(13)

■ _{11g version 11.2.0.2}

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

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

Note

If using ALM with HDM, it isrecommendedto create the ALM database user on the same database instance 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 the target machines. Alternatively, you can use the ALM installer to silently install WebLogic with an applicable installer (for example,wls1034_generic.jar). For related information, see the answer variables in“WebLogic Installer answer

variables” 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 and

Java Installation answer variables” on page 12.

File Server for deployment units (bundles)

Application Lifecycle Managerdepends on a File Server to storedeployment unitsfor download bydevicesin the customer base. The File Server includes a component server for deployment unit uploading and a component server for deployment unit downloading. Most standard FTP and HTTP server components work with ALM, as long as the components support user name/password authentication or no authentication. Typically, the components are installed on the same host. For more information, see the “File server requirements” section in theApplication Lifecycle Manager Release Notes.

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

■ _{Uploading bundles}_{. FTP and SFTP}

■ _{Downloading bundles}_{. FTP, HTTP, and HTTPS}

5

Understanding the ALM pre-requisites

(14)

Before continuing, install a File Server with the FTP and HTTP components. In advance of each ALM installation, you need 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 Home Device Manager.

ALM required ports

Purpose Source

Destination Protocol

Port Number

Access to the ALM Application Tier: Management ALM Application server HTTPS 7006 ■ _Management Console ■ _NBI Used by BEA WebLogic tools to BEA WebLogic administrator tools ALM Application server T3S 9004

administer and monitor the server. This port is not required for normal operation. Database access. ALM Application server Oracle server JDBC 1521 Upload of deployment units and configuration files. ALM Application server ALM repository SFTP 22 Download of

deployment units and configuration files. ALM repository

CPE (service gateway) HTTPS

443

An NBI system can register a SOAP ALM Application

Server ALM NBI system

HTTP(S)

SOAP port

endpoint in ALM to received asynchronous notifications. To make this work, the appropriate port must be accessible. If the NBI system uses JMS

Installation

6

(15)

ALM required ports (continued)

Purpose Source Destination Protocol Port Number

for notifications, this is not required.

Creating an Oracle user manually (optional)

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

Note

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

Comparison: Creation methods for ALM database user

Characteristics Method

Manually using a database tool such as SQL*Plus

■ _{Enables configuring the ALM database user in a custom manner (for}

example, with dedicated tablespaces)

The user createdmustinclude the connect and resource privileges (for

■ _{Eliminates requirement to define the Database Administrator (DBA)}

credentials while installing ALM; this is only required when the installer is to create the ALM database user

example,grant connect, resource to username)

■ _{Requires setting the}

DROP_USER=nvariable 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 answer files to know the Database Administrator (DBA) credentials

■ _{Requires setting the}

DROP_USER=yvariable in the answer file used for

installing the ALM Administration Server or only the first Managed Server forALM deployments in a HDM installation. In turn, the ALM installer:

❐ _{Drops the specified user (if the user exists in the specified database}

instance). For example, this is useful in a re-installation scenario.

7

Creating an Oracle user manually (optional)

(16)

Comparison: Creation methods for ALM database user (continued)

Characteristics Method

❐ _{Creates or re-creates the specified database user, whichever applicable.}

Important

For each ALM installation occurring after the database user for ALM is created, set theDROP_USER=nvariable in the

answer file. For example,DROP_USER=nis 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.

If the manual option is preferable, create the user now before continuing. For related information, see the

DB_USER=ALM_DBandDB_USER_PW=ALM_DBentry in“Database answer variables” on page 14.

Creating backups for the installation environment

It ishighly recommendedto create backups of the following components before installingApplication 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 useanswer.txtfiles to install ALM.Answer filesdefine variables and deployment-specific values for installations. There are two ways to use answer files:

1. Includeallthe deployment-specific values required to install.

Installation

8

(17)

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

2. Includesomeof 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 for any required valuesnotdefined 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. TheMANAGED_SERVER_NAMEproperty requires a

unique value for each server instance. Similar to value forINSTALL_DIR, the port values must be unique for server instances on the same host. For related guidance, see“ALM File System answer variables” on page 13and“Managed Server answer variables” on page 16.

# # Managed Server # MANAGED_SERVER_CREATE=y MANAGED_SERVER_NAME=ALM-Server MANAGED_SERVER_PORT=7005 MANAGED_SERVER_SSL_PORT=7006 MANAGED_SERVER_ADMIN_PORT=9004 MANAGED_SERVER_MACHINE=M_host DEPLOY_APPLICATION=y # ⇦

Important

For each ALM installation occurring after the database user for ALM is created, set theDROP_USER=n

variable in the answer file. For example,DROP_USER=nis 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 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 applicable sections in“Understanding the unique answer variables” on page 11.

# # WebLogic Installer # BEA_INSTALL_FILE=/opt/installers/wls1034_generic.jar PROXY_HOST=proxy.mycompany.com PROXY_PORT=8080 # 9

Understanding the ALM sample answer file

(18)

# WebLogic and Java Installation # WL_HOME=/opt/alm30/wlserver_10.3 JAVA_INSTALLER=/opt/installers/jdk-6u24-solaris-sparc.sh #JAVA_HOME=/opt/alm30/jdk160_24 CREATE_SEPARATE_BEA_DOMAIN=y #

# ALM File System # INSTALL_DIR=/data/alm/install_3.0_separate/ALM-Server INSTALL_OVERWRITE=y # # Administration Server # BEA_ADMIN_HOST=admin.mycompany.com BEA_ADMIN_PORT=9002 BEA_ADMIN_SERVER_SSL_PORT=9001 BEA_ADMIN_USER=weblogic BEA_ADMIN_PW=w3blog!c AUTH_TYPE=default # # Cluster # CLUSTER_NAME=ALMCluster CLUSTER_MULTICAST_ADDRESS=224.22.22.22 CLUSTER_MULTICAST_PORT=3456 # # Database # DROP_USER=y DB_EXE=/opt/oracle/product/10.2.0.4/bin/sqlplus DB_SERVER=dbhost.mycompany.com DB_PORT=1521 DB_SERVICE=serviceName DB_DBA=system DB_DBA_PW=password DB_USER=ALM_DB DB_USER_PW=ALM_DB # # Node Manager # NODEMGR_PORT=5560 # # Managed Server # MANAGED_SERVER_CREATE=y MANAGED_SERVER_NAME=ALM-Server MANAGED_SERVER_PORT=7005 MANAGED_SERVER_SSL_PORT=7006 MANAGED_SERVER_ADMIN_PORT=9004 MANAGED_SERVER_MACHINE=M_host DEPLOY_APPLICATION=y # # HDM Applications # HNM_MANAGED_SERVER_NAME=hdm_7004 HNM_JNDI_URL=t3s://hdm.mycompany.com:7004 HNM_NBI_URL=https://hdm.mycompany.com:7004/remotehdm/NBIService Installation 10

(19)

HNM_NBI_USER=nbi_user HNM_NBI_USER_PW=password # # File Server # REPOSITORY_DOWNLOAD_SERVER=repository.mycompany.com REPOSITORY_DOWNLOAD_ROOT=/download REPOSITORY_DOWNLOAD_PORT=443 REPOSITORY_DOWNLOAD_PROTOCOL=ftp REPOSITORY_DOWNLOAD_USER=anonymous REPOSITORY_DOWNLOAD_PASSWORD=password REPOSITORY_UPLOAD_SERVER=repository.mycompany.com REPOSITORY_UPLOAD_ROOT=/upload REPOSITORY_UPLOAD_PORT=22 REPOSITORY_UPLOAD_PROTOCOL=ftp REPOSITORY_UPLOAD_USER=anonymous REPOSITORY_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.jarfile), Java starts the silent installation process.

Note that the parent directory set in theWL_HOMEvariable is implemented for BEA_HOME. The parent directory is

everything in the string value except forwlserver_10.3(for example,/opt/alm30/).

PROXY_HOST=proxy.mycompany.comandPROXY_PORT=8080

Only applicable when settingBEA_INSTALL_FILEto silently install WebLogic.

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

11

Understanding the unique answer variables

(20)

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, theJAVA_HOMEvariable is applicable.

Specify the path to the JDK1.6 installer, which can be downloaded from the Oracle site. In turn, the JDK is installed in theBEA_HOME/jdk160directory. At the same time, theJAVA_HOMEvariable is automatically set to

BEA_HOME/jdk160.

whereBEA_HOMEis the parent directory set in theWL_HOMEvariable. The parent directory is everything in the string value except forwlserver_10.3(for example,/opt/alm30/).

For subsequent Managed Server installations on the same host, comment out theJAVA_INSTALLERvariable by inserting 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, theJAVA_INSTALLERvariable 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}

TheCREATE_SEPARATE_BEA_DOMAINvariablemustbe set toyif ALM is installed only for MDM. That is

because ALM is installed on a JBoss application server. The ALM installerdoes notsupport installing ALM on JBoss.

Or

■

nto install ALM in the domain for an existing HDM installation.

Installation

12

(21)

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 including an uninstall script there.

Note

For cluster installations with multiple Managed Servers on the same physical host, the valuemustbe unique 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 withINSTALL_DIRvariable 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 default port number (9002) is in use on the Administration Server host, change the value; otherwise, leave the setting unchanged.

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 the Administration 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:

■

defaultto implement fewer password constraints. The default configuration only permits authentication for

account passwords that include eight or more characters, including at least two lowercase characters (for example,

fandl).

13

(22)

Or

■ _advanced_{to implement additional password constraints. The advanced configuration only permits authentication}

for 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,}

0and9)

❐ _{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 Managed Servers 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 4and“Creating an Oracle user manually (optional) ” on page 7.

Note

DROP_USER=y

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

■

yto drop the specified database user and then to create or re-create the specified database user, whichever

applicable

Or

■ _n_{to configure installation with the specified database user. The user}_must_{already exist in the specified database}

instance.

Installation

14

(23)

Important

For each ALM installation occurring after the database user for ALM is created, set theDROP_USER=n

variable in the answer file. For example,DROP_USER=nis 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.

DB_EXE=/opt/oracle/product/10.2.0.4/bin/sqlplus (conditionally required)

Specify the absolute path to the Oracle client on the host.

IfDROP_USER=yis specified, theDB_EXEvariablemustbe 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 instance slated 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 running on the Oracle database. Sometimes this value is referred to as the SID.

DB_DBA=systemandDB_DBA_PW=password(conditionally required)

If a database user was created according to“Creating an Oracle user manually (optional) ” on page 7, youdo not

need to specify the DBA credentials.

ForDB_DBA, specify the user name for the Database Administrator (DBA) account. This account has permissions

for creating the ALM tables.

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

IfDROP_USER=yis specified, theDB_EXEvariablemustbe specified with the applicable value. DB_USER=ALM_DBandDB_USER_PW=ALM_DB

Specify 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, youmustalso specify the DBA credentials for the database instance with theDB_DBAandDB_DBA_PWvariables.

Or

■ _{An existing database user in the specified database instance}

15

(24)

In this case, youdo notneed 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 default port 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

■

nto skip the installation process and configure an existing Managed Server in theHDMDomain.

If you specify the name for an existing Managed Server in theALMDomainor theHDMDomain(with MANAGED_SERVER_NAME), the installerdoes notapply this answer variable.

MANAGED_SERVER_NAME=ALM-Server

Specify the name of the Managed Server. The name iseitherthe 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}

ALMDomainor theHDMDomain. In this case, the valuemustbe defined

exactly as configured for the applicable server instance. By default, the HDM installer creates Managed Server instances with thehost_7004name format, where:

❐ _host_{is the short name for the Managed Server host}

❐ ₇₀₀₄_{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

If you specify the name for an existing Managed Server in theALMDomainor theHDMDomain(with

MANAGED_SERVER_NAME), the installerdoes notapply this answer variable.

Installation

16

(25)

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 default value is:9004

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

If you specify the name for an existing Managed Server in theALMDomainor theHDMDomain(with

MANAGED_SERVER_NAME), the installerdoes notapply this answer variable. 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:

hostis the short name for the host on which to create the Dedicated Managed Server and from which the ALM installer 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 Managed}

Server 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 empty values for them.

HNM_MANAGED_SERVER_NAME=hdm_7004

Specify the exact name configured in theHDMDomainfor the Managed Server on which the HDM applications are

deployed. For example:hdm_7004

17

(26)

where:

■ _hdm_{is the short name for the Managed Server host}

■ ₇₀₀₄_{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}

■ ₇₀₀₄_{is the SSL port}

■ ₇₀₀₃_{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}

■ ₇₀₀₄_{is the SSL port}

■ ₇₀₀₃_{is the clear port}

Installation

18

(27)

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

19

(28)

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 applicable

WebLogic Server domainis not configured with production SSL certificates. In that case, the installation is dependent on demonstration certificates, and theFAKE_SSL_TRUST=yvariableis 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 ALM license” 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 Managed

Server

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 almusers

useradd -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 thealmadminuser password, and then type the new password at the prompts:

passwd almadmin

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

Installation

20

(29)

a. Create a staging directory for the ALM installer, and then extract thealm-3.0-dist.tarfile from the

product CD into the directory. For example:

mkdir /opt/staging/alm30 cd /opt/staging/alm30

tar -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 following resources:

■ _{“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 certificatesinstead of

production SSL certificates, youmustset theFAKE_SSL_TRUST=yproperty in the answer

file.

c. Run the installer:

cd /opt/staging/alm30

sh ./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 in}

Step 4.b.

The installer prompts for any invalid or missing values in the answer file. If successful, the following line appears 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 related information, see“ALM deployed in same domain as HDM” on page 3.

21

Invoking answer file for ALM installation

(30)

3. In the shell opened inStep 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 thealm-3.0-dist.tarfile from the product CD into the directory. For example:

mkdir /opt/staging/alm30 cd /opt/staging/alm30

tar -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 following resources:

■ _{“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 certificatesinstead of

production SSL certificates, youmustset theFAKE_SSL_TRUST=yproperty in the answer

file.

d. Run the installer:

cd /opt/staging/alm30

sh ./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 in}

Step 3.c. The answer file defines the installation-specific values for installing and deploying the ALM on a single Managed Server instance.

The installer prompts for any invalid or missing values in the answer file. If successful, the following line appears 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.

Installation

22

(31)

Conducting the post-installation and deployment tasks

Configuring the ALM license

If the ALM license was not configured during installation usingLICENSE_STRINGvariable, 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 theALM 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.}

❐ ₇₀₀₆_{is the SSL port for the Managed Server.}

❐ ₇₀₀₅_{is the clear port Managed Server.}

The login page appears.

b. In theUsernamefield, type:almopmgr

c. In thePasswordfield, type:password

Note

Thealmopmgr/passwordcredentials are for the default user created during the ALM installation. You can reset thealmopmgrpassword through the WebLogic Server Console. For guidance, see

Modify users[http://e-docs.bea.com/wls/docs92/ConsoleHelp/taskhelp/security/ModifyUsers.html] in Oracle's online BEA WebLogic Server documentation.

23

Conducting the post-installation and deployment tasks

(32)

d. Click theLog Onbutton.

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

3. Configure the ALM license:

a. Click theSystem Settingstab.

b. On the row with theLicenseproperty, paste your license string in theValuefield.

Important

The string must be pasted into the field as a single concatenated line. c. Click theSave Changesbutton. 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, thealmopmgr

user includes all privileges for the ALM Management Console.

You can also selectAbout->About, then select theLicensetab in the About dialog box to display details about the 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“Completing post-deployment tasks for using HDM with ALM (if applicable)” on page 24.

In the ALM Management Console, use theSystem Settingstab to set appropriate values for Mobile Device Manager by editing values on the MDM page in the Connectors folder of the System Settings. For instructions, see “MDM” inALM Management 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), youmustenable trust between the domains. This applies even if the two domains are named identically.

Installation

24

(33)

For instructions, seeEnable 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 useApplication Lifecycle Managerwith HDM, you need to create or import some data objects in theHome Device Manager 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 Management

Console Help

Requirements Data object

Adding device types Use the ALM-provided device type XML

file on the product CD:

OSGi frameworkdevice type

acs/hdm/devicetype/osgi1.0.xml

Depending on what the deployment requires, configure the device type for zero touch activation or pre-provisioned.

Adding actions Name: Enable active notifications

Actionfor enabling active notifications

Action type: Set Parameter Attributes

Parameter: InternetGatewayDevice. Services.OSGi.BundleNumberOfEntities with:

■ _{Attribute Name: Notification}

■ _{Attribute Value: Active}

Adding policies Name: Force active notifications

Policyfor forcing active notifications

Protocol: TR069v1

Action: Enable active notifications

Configure policy to be event-based and triggered on Activation event

Set Initiate Connection on Request device

25

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

(34)

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

Console Help

Managing criteria templates Name: Find failed or aborted devices for

ALM policy

Criteria templatefor enabling ALM to reinvoke policies on

failed devices 1. From the staging directory in which the ALM installer was extracted (alm-3.0-dist.tar), open the

following file in a text editor:

acs/hdm/criteriatemplates/ findDevByALMBulkOperation IdAndOperationState.xml

2. In the file, replace all instances of

ALM_USERwith the exact database user name configured for the ALM deployment (for example,ALM_DB).

That name was defined with the

DB_USERvariable in the answer file

used for installation or by the DBA whomanually created the userbefore ALM was installed on target hosts. For related information, see the

“Database answer variables” on page 14.

3. As the ALM database user (for example,ALM_DB), use SQL*Plus to

log into the database instance that includes the ALM tables; then, execute the following commands.

GRANT SELECT ON GATEWAY ⇦

to HDM_DB;

GRANT SELECT ON ⇦

COMMAND_HISTORY TO HDM_DB;

whereHDM_DBis the name of the

database user originally defined during HDM installation.

Installation

26

(35)

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

Console Help

Note

The ALM and HDM database tables must be created with users on the same Oracle database instance.

4. Upload the updatedfindDevByALM BulkOperationIdAnd

OperationState.xmlfile through the HDM Management Console. As referenced in next column, see the “Managing criteria templates” section in theHDM Management Console Helpfor guidance.

Configuring the JMS event notification settings in HDM

Application Lifecycle Managerdepends on some JMS notification events ofHome Device Manager. By default, the HDM installer sets the associated system settings to true, which is the configuration required for ALM. Even so, it is important to validate that the properties have not been configured from their default values. As a result, complete the“To validate that the HDM JMS event notification properties are set to true” on page 27procedure. To identify the properties that are a factor, seeHDM JMS event properties that must be set to true on page 27within the procedure.

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

1. Log into theServer Configuration Consolein theHDMDomain.

For guidance, see the “Server Configuration Console” entry in the “Finding the HDM user interfaces” topic of the

Home Device Manager Deployment Guide.

2. For the applicable server instances and/or globally, double-check that the properties in the following list are set to

true; if not, change the values fromfalsetotrue.

HDM JMS event properties that must be set to true

■

nbi.notification.send.DeviceActionResultEvent

■ _{nbi.notification.send.EventTriggeredPolicyResultEvent}

27

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

(36)

■

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

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

Confirming Java Messaging Service (JMS) communication

Oncedevicesare active in your customer base and/or test environment, you can determine whether the associated JMS communication between ALM and HDM is occurring. When a JMS connection isnot established, server warning messages about failed JMS connections get written to the application trace log (every 5 seconds). If you are unsure of the log file location, 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] Successfully refreshed 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: JndiObjectTargetSource failed to obtain new target object; nested exception is

javax.naming.CommunicationException [Root exception is

java.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.DeviceActionResultEvent nbi.notification.send.DeviceEvent nbi.notification.send.EventTriggeredPolicyResultEvent nbi.notification.send.single.device.action.result nbi.notification.send.UnknownGatewayEvent

Note

For details on these properties, see theHome Device Manager Deployment Guide.

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

Installation

28

(37)

nbi.notification.send.DeviceEvent

If this property is set tofalse, 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 command}

line of the device is used to make a manual state change of a bundle or property of an application. Thus, the ALM database will not be synchronized automatically with the state change of the device.

nbi.notification.send.DeviceActionResultEvent

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

Policies are specified in the ALM Management Console. Policies in ALM schedule the instant triggered policy with a simple CR action. As a result, every device that is targeted by the policy generates an NBI notification with the objectNBIDeviceActionResult. 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.

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

If this property set tofalse, 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 containNBIOperationResult,NBIBulkOperationResult, or NBIDeviceActionResult.

nbi.notification.jms.blocked.events

This property should not containNBIDeviceInformEventorNBIDeviceActivationNotification. nbi.notification.blocked.inform.eventcodes

This property should not contain2 PERIODICif you want ALM’s event-triggered policies to be able to receive the

NEXTCONNECTION.

ALM isnotdependent on the following properties:

nbi.notification.jms.blocked.registrations

nbi.notification.send.EventTriggeredPolicyResultEvent nbi.notification.send.UnknownGatewayEvent

Uninstalling and undeploying the ALM application

Use the following procedure to uninstallApplication Lifecycle Managerand undeploy the application from the applicable Managed Serverwithoutuninstalling Home Device Manager or other applications in the environment.

29

Uninstalling and undeploying the ALM application

(38)

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

Note

If reinstalling components after removing some or all of them, it is important to have the backups of the OLTP database and all local files and directories. That way, if necessary, you can restore the backup data 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 processcannotcomplete the last step of removing theALM-Serverdirectory.

■ _{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 Serverinstead ofa Dedicated Managed Server created by the 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 and start procedures in the “Restarting application tier servers” section of theHome Device Manager Deployment Guide.

Installation

30

(39)

2

This 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

Application Lifecycle Manager Deployment Guide