Installation and Configuration Guide: HP Exstream Delivery Manager HP Exstream Command Center

HP Exstream Delivery Manager
Version 1.2.2
HP Exstream Command Center
Version 2.2.2
Installation and Configuration

Guide
© 2013 Hewlett-Packard Development Company, L. P.
Confidential computer software. Valid license from HP required for possession, use or copying. Con-
sistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Docu-
mentation, and Technical Data for Commercial Items are licensed to the U.S. Government under
vendor's standard commercial license.
The information contained herein is subject to change without notice. The only warranties for HP
products and services are set forth in the express warranty statements accompanying such products
and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Copyright © 2008, The Chromium Authors All rights reserved.
© Copyright 1999-2009 The Apache Software Foundation
Copyright (c) 2000-2005 INRIA, France Telecom All rights reserved.
Copyright (c) 2003-2007, Terence Parr All rights reserved.
Copyright (c) 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved.
Copyright (c) 2001-2004 The OpenSymphony Group. All rights reserved.
Copyright (c) 2002 Extreme! Lab, Indiana University. All rights reserved.
Copyright (c) 1989, 1999 Free Software Foundation, Inc.
Copyright (c) 2006-2007, XStream Committers All rights reserved.

Copyright (c) 2003-2006, Joe Walnes
Copyright (c) 2004-2008 QOS.ch All rights reserved.
© Copyright 2002-2010 NextApp, Inc.
Copyright (C) 2005 JGraph.com. All rights reserved.
Copyright © 2010 The Eclipse Foundation. All Rights Reserved.
Copyright ©1999, 2009 Tanuki Software, Ltd. All Rights Reserved.
Copyright 1994-2006 Sun Microsystems, Inc.
Copyright ©2000-2005 INRIA, France Telecom All rights reserved.
Copyright (c) 1995-2000 by the Hypersonic SQL Group. All rights reserved.
© Copyright 2010 SpringSource. All Rights Reserved.
Copyright © 2006. Adobe Systems Incorporated. All rights reserved.
Copyright 2009 Day Management AG
Copyright © 2002 JSON.org
Copyright © 1996-2001 Logica Mobile Networks Limited, all rights reserved.

Copyright © 2011 Red Hat, Inc.
Copyright 2002-2005, the Displaytag team
© 2007-2009 Object Refinery Limited
The MIT License (MIT) Copyright ©
Trademark Notices
Apache Tomcat is trademarks of the Apache Software Foundation
UNIX® is a registered trademark of The Open Group.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
HP and HP-UX are trademarks or registered trademarks of Hewlett-Packard Company
AIX, DB2, IBM, and WebSphere are registered trademarks and IBM mainframe is trademark of IBM
Corporation
Oracle is a registered trademark of Oracle Corporation
RED HAT is a registered trademark of Red Hat, Inc.
Solaris is a trademark of Sun Microsystems, Inc.
JBOSS is a registered trademark of Red Hat, Inc.

Contents
Contents
Contents .................................................................................................. 6
About HP Exstream Delivery Manager ...................................................... 10

About HP Exstream Command Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
HP Exstream Command Center Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
About HP Exstream Delivery Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
About HP Exstream Fulfillment Delivery Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
HP Exstream Delivery Manager System Requirements ............................... 13

Obtaining HP Exstream Delivery Manager and HP Exstream Command Center Licenses . . . . . . . . . . . . . . 13
HP Exstream Delivery Manager Application (Web) Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . 14
HP Exstream Delivery Manager Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Creating Databases for HP Exstream Delivery Manager Components . . . . . . . . . . . . . . . . . . . . . . . .14
HP Exstream Command Center-Specific Requirements . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

HP Exstream Command Center Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
HP Exstream Command Center Software Requirements .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
HP Exstream Command Center License Keys . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Operating System Patches . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Customer Environment . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
HP Exstream Delivery Engine-Specific System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

HP Exstream Delivery Engine System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Operating System and Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
JBOSS Specific Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
JMS Interface Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
JCR Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
HP Exstream Fulfillment Delivery Service-Specific System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 20

HP Exstream Fulfillment Delivery Service System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Operating System Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
HP Exstream Delivery Engine Requirements for HP Exstream Fulfillment Delivery Service . . . . . . . . . . . 22
HP Exstream Engine Requirement for HP Exstream Fulfillment Delivery Service . . . . . . . . . . . . . . . . . . 22
HP Exstream Fulfillment Delivery Service Document Composition Mode Requirements . . . . . . . . . . . . . 22
Web Container Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Installing and Deploying Command Center ............................................... 24

Pre-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Installation and Configuration Guide 6

Contents
Command Center Package File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Installing Command Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Preparing for Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Preparing for Command Center Deployment on Oracle Weblogic . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Preparing Command Center for Deployment on IBM Websphere . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Preparing Command Center for Deployment on Apache Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Deploying Command Center WebGUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Deploying Command Center Data Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Running Command Center Server and Command Center WebGUI on Different Domains . . . . . . . . . . . . . 29
Securing Communication with Command Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Securing the Server Side of Command Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Securing the Client Side of Command Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Securing a Web Connection to Command Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Command Center 2.2.0 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Preparing for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Migrating Command Center Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Command Center Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Installing and Deploying the HP Exstream Delivery Engine ......................... 37

HP Exstream Delivery Engine Package File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Installing the HP Exstream Delivery Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Deploying the HP Exstream Delivery Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Preparing for Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Deploying the HP Exstream Delivery Engine with WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Deploying the HP Exstream Delivery Engine with Weblogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Deploying the HP Exstream Delivery Engine with JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Deploying the HP Exstream Delivery Engine with Tomcat 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Validating the HP Exstream Delivery Engine Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Validating the HTTP Interface for the HP Exstream Delivery Engine . . . . . . . . . . . . . . . . . . . . . . . . . 41
Validating the JMS Interface for the HP Exstream Delivery Engine . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configuring the HP Exstream Delivery Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Software Requirements for Delivery Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Configuring Delivery Channels Using the HP Exstream Delivery Engine WebGUI . . . . . . . . . . . . . . . . 42
Enabling Communication with the HP Exstream Delivery Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Configuring the Callback URL for the HP Exstream Command Center . . . . . . . . . . . . . . . . . . . . . . . .43
Configuring the Callback URL for the HP Exstream Fulfillment Delivery Service . . . . . . . . . . . . . . . . . 43
HP Exstream Delivery Engine 1.2.0 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Preparing for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Migrating HP Exstream Delivery Engine Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Contents
Installing and Deploying HP Exstream Fulfillment Delivery Service ............. 46

HP Exstream Fulfillment Delivery Service Package File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Installing and Deploying HP Exstream Fulfillment Delivery Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
HP Exstream Delivery Manager Configuration Console .............................. 48

Installing the HP Exstream Delivery Manager Configuration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Deploying the HP Exstream Delivery Manager Configuration Console . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Managing Configuration Settings in the Configuration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
HP Exstream Command Center Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Engine Pool Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
HP Exstream Delivery Engine Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Delivery Report Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
JMS CallBack Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Action Handler Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Data Channel - General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Data Channel - Watch Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
LPR/LPD Delivery Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Internal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Java Content Repository (JCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Job Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
File Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
JMS Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
RMI Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
General Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Job Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Schedule Entity Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Engine Pool Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Engine Pool Slot Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Cluster Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configuring the HP Exstream Command Center Data Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configuring the HP Exstream Command Center Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
HP Exstream Delivery Engine Configuration . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 76

Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 76
JNDI Context for datasources . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 76
Output Document Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 77
Temp Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 77
JMS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 77
Java Content Repository (JCR) Settings . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . .78
BATCH Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 79
Callback and Cleanup Threads Configuration . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 79
ExactTarget Query Configuration . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 79
Operation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . 80

Contents
HP Exstream Fulfillment Delivery Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Database Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Delivery Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
HP Exstream Delivery Engine Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Database Clean-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
FDS Filestore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
FDS EWS & Realtime Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Appendix ............................................................................................... 86
HP Exstream Delivery Engine Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Sizing Requirements for HP Exstream Delivery Engine When Using JBoss with Oracle Database . . . . . 86
Sizing Requirements for HP Exstream Delivery Engine when Using WebLogic . . . . . . . . . . . . . . . . . . 89
Configuring the deglobal.properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Creating a Database Instance and Users for HP Exstream Delivery Engine . . . . . . . . . . . . . . . . . . . . 94
Configuring Java Content Repository Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
HP Exstream Fulfillment Delivery Service Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Setting up the Real-time Composition Engine for HP Exstream Fulfillment Delivery Service . . . . . . . . . . 96
Troubleshooting ................................................................................... 103

Common Issues that can occur in HP Exstream Command Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Bug Reporting in HP Exstream Command Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Common Issues that can occur in HP Exstream Delivery Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Common Issues that can occur in HP Exstream Fulfillment Delivery Service . . . . . . . . . . . . . . . . . . . . . . 105
Index .................................................................................................. 106

About HP Exstream Delivery Manager
HP Exstream Delivery Manager is an Enterprise solution that creates business workflows and delivers multi-
channel documents electronically to different destinations such as email, SMS, FTP, CMIS, and so on.
Compared to a service provider or an enterprise that delivers documents to a fixed destination, HP Exstream
Delivery Manager can deliver a composed document to the end customer’s preferred destination channel.
Optionally, if the delivery of the document to the customer’s preferred delivery channel fails, HP Exstream
Delivery Manager can route the document to an alternate or business preferred destination. The workflow
component of the solution helps in setting up the delivery for a customer’s preferred channel or a business
preferred channel.
HP Exstream Delivery Manager 1.2 consists of the following products:
 HP Exstream Command Center 2.2
 HP Exstream Delivery Engine 1.2
 HP Exstream Fulfillment Delivery Service 1.2
The following are the prerequisites and dependent components for HP Exstream Delivery Manager 1.2:
 Multi-Channel HP Exstream 8.0.301 or later
 HP Exstream XML Component
 Engine as Web Service
 HP Exstream Real-time Engine
HP Exstream Command Center is the workflow component and HP Exstream Delivery Engine is the delivery
component of the HP Exstream Delivery Manager solution. HP Exstream Fulfillment Delivery Service (FDS) is an
additional component of HP Exstream Delivery Manager that runs as a REST-based service to fulfill the high-
volume, concurrent, on-demand requests for HP Exstream Delivery Manager. HP Exstream Fulfillment Delivery
Service provides tight coupling between HP Exstream and HP Exstream Delivery Engine components to compose
and deliver the documents over customer preferred channel.
This chapter discusses the following topics:
 About HP Exstream Command Center on page 10
 About HP Exstream Delivery Engine on page 11
About HP Exstream Command Center

HP Exstream Command Center:
 Is an enterprise job scheduling and job management software.
 Integrates with the HP Exstream enterprise document automation system and enables you to compose high-
volume, on-demand, interactive documents for multi-channel delivery.
 Enables you to plan, schedule, and optimize document processing requirements for a complex application.
 Is capable of handling the scheduling and managing HP Exstream-related jobs and processes.
 Enables you to choose standard templates or create custom life-cycles to manage data retrieval, compose
documents, generate output, and deliver output to multiple channels.
 Provides you with status updates on job execution through preferred notification channels.

 Supports batch and on-demand processing, as well as the integration of the interactive document capabilities of
HP Exstream to create, schedule, and process jobs for Live document creation and fulfillment.
 Is a single platform that integrates with HP Exstream Production Engine, providing the capability to integrate and
automate processes related to HP Exstream with other enterprise document processing systems.
 Offers a range of unique capabilities to support automated document processing and printing requirements
through an easily defined, reliable environment.
HP Exstream Command Center Components

HP Exstream Command Center has two main components:
 A server that is the core part of the HP Exstream Command Center, and supports multiple client interfaces.
HP Exstream Command Center Server is a stand-alone Java application providing a variety of job management
services that can be run as a Windows Service or a UNIX daemon.
 A Web-based graphical user interface (WebGUI) that enables users to define, manage, schedule, and configure
job notifications. WebGUI provides a visual representation that enables you to depict user-defined job cycles and
the logical job flow.
The client application interacts with the HP Exstream Command Center Server using either RMI, HTTP Provider,
SOAP provider, or JMS provider. WebGUI is an AJAX-based Web application running on any Java-enabled
Web container (such as Apache Tomcat and IBMWebSphere) and is accessible through a Web browser.
The basic setup is a single computer running HP Exstream Command Center Server (with integrated database),
HP Exstream Command Center WebGUI (with embedded Jetty Web server) and a Web browser for accessing
the WebGUI as shown in the Fig1.1 Overview on page 11.
Fig1.1 Overview
About HP Exstream Delivery Engine

HP Exstream Delivery Engine is a component of the HP Exstream Delivery Manager product. HP Exstream
Delivery Engine is a single platform for the delivery of any type of document, regardless of complexity or
variability.
HP Exstream Delivery Engine receives job delivery requests from HP Exstream Command Center or HP Exstream
Fulfillment Delivery Service and supports batch and on-demand requests. These requests are sent either through
an HTTP interface or through a JMS interface and contain information about the composed document and the
customer’s preferred delivery channel.
If the delivery of the documents to the customer’s preferred channel fails, HP Exstream Delivery Engine sends a
failure notification to HP Exstream Command Center. As a result, HP Exstream Command Center generates a
request to the HP Exstream Delivery Engine and receives the document in a format required for an alternate
delivery channel, and then sends the job delivery request again to the HP Exstream Delivery Engine.

For example, suppose the delivery of a telephone bill through email fails. You might then receive a short text
message from HP Exstream Command Center, containing select information from the telephone bill. Next,
HP Exstream Command Center sends a job delivery request to the HP Exstream Delivery Engine to deliver the
new document to the customer through the alternate delivery channel.
HP Exstream Delivery Engine has two main components, a server and a Web-based Graphical User Interface
(WebGUI).
 HP Exstream Delivery Engine Server—The server is the core component of HP Exstream Delivery Engine
that supports multiple client interfaces.
 HP Exstream Delivery Engine WebGUI—The WebGUI enables users to define and manage delivery
channels.
About HP Exstream Fulfillment Delivery Service

HP Exstream Delivery Manager also includes the HP Exstream Fulfillment Delivery Service (FDS). HP Exstream
Fulfillment Delivery Service runs as a REST-based service to fulfill the high-volume, concurrent, on-demand
requests for HP Exstream Delivery Manager. HP Exstream Fulfillment Delivery Service provides close integration
between HP Exstream and HP Exstream HP Exstream Delivery Engine components to compose and deliver the
documents over a customer’s preferred channel.
HP Exstream Fulfillment Delivery Service supports the delivery of on-demand documents in the following use
cases:
 Delivery to a customer’s preferred channel
 Delivery to an alternate business preferred channel when the primary user’s preferred channel delivery fails
 Delivery of multichannel documents to multiple destinations (more than one document delivered as part of single
customer request)

HP Exstream Delivery Manager System Requirements
HP Exstream Delivery Manager System

Requirements

 Obtaining HP Exstream Delivery Manager and HP Exstream Command Center Licenses on page 13
 HP Exstream Delivery Manager Application (Web) Server Requirements on page 14
 HP Exstream Delivery Manager Database Requirements on page 14
 HP Exstream Command Center-Specific Requirements on page 15
 HP Exstream Delivery Engine-Specific System Requirements on page 18
 HP Exstream Fulfillment Delivery Service-Specific System Requirements on page 20
Obtaining HP Exstream Delivery Manager and HP Exstream

Command Center Licenses
You can purchase three types of licenses:
 HP Exstream Delivery Manager license (includes HP Exstream Command Center, HP Exstream Delivery
Engine, and HP Exstream Fulfillment Delivery Service)
 HP Exstream Command Center license
To obtain the license keys, contact software.keys@hp.com. The license key files are shipped, based on user require-
ments. The following table lists the options and modules that are available.
License options and modules

HP Exstream Delivery Manager HP Exstream Command Center
Options/Modules
License License
Distribution • HP Exstream Command Center • HP Exstream Command Center

• HP Exstream Delivery Engine distribution distribution only
Assured Delivery • Available • Not available
job definition template • Supports Alternate Delivery feature • Alternate Delivery feature is not
• Ability to use delivery queues of supported
(in the New Job
Definition window) HP Exstream Command Center for non- • Job delivery handling through the
assured delivery templates existing Delivery Queues in
HP Exstream Command Center in
Fire and Forget mode only
HP Exstream Delivery • Available • Not available
Engine
Delivery Reporting • Available • Not available
module
HP Exstream • Available • Not available
Fulfillment
Delivery Service

HP Exstream Delivery Manager Application (Web) Server

Requirements
HP Exstream Delivery Manager can be hosted on the following application (Web) servers:
 Apache Tomcat 7.0.X
 IBM WebSphere application server 7
 JBoss application server 5.1 (for HP Exstream Delivery Engine only)
 Oracle (BEA) WebLogic Server 11g (10.3.5 or later)
HP Exstream Delivery Manager Database Requirements

HP recommends the following database management systems, which have been tested for use with HP Exstream
Delivery Manager:
Database Requirements for HP Exstream Delivery Manager
HP Exstream Fulfillment Delivery Service

HP Exstream Delivery Engine
Database Requirement
Supported in
Supported in
Supported in
IBM DB2 9.7 x x x

IBM DB2 9.5 x x x
MS SQL Server 2005 x
MS SQL Server 2008 x x x
MySQL 5.5.17 x x x
Oracle 10g R2 x
Oracle 11g R2 x x x
Creating Databases for HP Exstream Delivery Manager Components

You must create a database schema for every HP Exstream Delivery Manager component so that the tables of
individual components are in separate schemas. Each HP Exstream Delivery Manager component includes SQL
scripts that can be executed by database administrators and a database utility to run the SQL scripts.

To create a database for HP Exstream Delivery Manager components:

1. Copy the JDBC driver to the database-setup/lib directory.
NOTE: JDBC drivers can be obtained from the database provider.
2. Depending on your operating system, run one of the following scripts:
Operating system Script
Windows database-setup/bin/dm-sqlexecutor.bat
UNIX/Linux database-setup/bin/dm-sqlexecutor.sh
3. Use the following arguments to run the script:

usage: dm-sqlexecutor
-c,--continue <arg> true if execution should continue on error, false
otherwise; default is true
-d,--driver <arg> hsql/mysql/oracle/mssql/db2 or driver class name
e.g. com.mysql.Driver
-l,--url <arg> connection URL
-p,--password <arg> database password
-s,--script <arg> SQL script file
-u,--username <arg> database username
Keep the following in mind when applying arguments to the script:

• SQL scripts are stored in the database-setup/sql directory.
• A log file of script execution (dm-sqlexecutor.log) can be found in directory where you are running
dm-sqlexecutor.
• Make sure that the JDBC driver is installed in your application server (for example, copy the driver to
classpath).
Example of Oracle syntax

dm-sqlexecutor.bat -d oracle -l jdbc:oracle:thin:@localhost:1521:<instance> -u
<username> -p <password> -s ../sql/oracle_init.sql
Example of MySQL syntax

dm-sqlexecutor.bat -d mysql -l jdbc:mysql://localhost:3306/<schema> -u <username>
-p <password> -s ../sql/mysql_init.sql
HP Exstream Command Center-Specific Requirements

This section describes the hardware, software, and operating system requirements for HP Exstream Command
Center.
This section discusses the following topics:
 HP Exstream Command Center Hardware Requirements on page 16
 HP Exstream Command Center Software Requirements on page 16
 HP Exstream Command Center License Keys on page 16
 Customer Environment on page 17
 Operating System Patches on page 17

HP Exstream Command Center Hardware Requirements

HP Exstream Delivery Manager requires a minimum free disk space of 1GB and a minimum free physical
memory of 2GB.
HP Exstream Command Center Software Requirements

HP Exstream Command Center requires the following software:
Software Description
Operating system for An operating system running Java Runtime Environment (JRE) version 6.0
HP Exstream Command or later.
Center Server and
Oracle provides JRE for several platforms including Windows, Linux, and
HP Exstream Command
Oracle Solaris at www.oracle.com/technetwork/java/
Center WebGUI
index.html. For other platforms, see your operating system vendor
manual.
Additional components for • JDK 1.6.0.x (Update 18 or later)
HP Exstream Command • HP UX JDK 6.0.x
Center Server • IBM Java 6.0
• HP Exstream Production Engine 8.0.301 or later
• A license key for installing and configuring HP Exstream Command
Center. To obtain the license key, contact software.keys@hp.com.
HP Exstream Command Center License Keys

You can verify the license key configuration by inspecting the HP Exstream Command Center Server startup
output (printed to a standard output/console or found in logs/cc-wrapper.out).
HP Exstream Command Center Server prints license information of the used license key on startup.
License Key Expiration

If your license has expired, you must renew your license key. Replace the conf/license with the new license key.
If the HP Exstream Command Center license key expires, you receive the following message:
License key has expired.
To renew the license, contact the HP Exstream Command Center support team. Send an email to the technical
contact listed on the software agreement, 15 to 30 days before an old key expires. If you do not receive a new
key, send an email to software.keys@hp.com.

Operating System Patches

HP recommends the following operating system patches, which have been tested for use in HP Exstream
Command Center. More recent operating system patches, quality releases, or service packs might exist.

Operating System and Hardware Patch Level
HP-UX 11.31 on Itanium (IA-64) • HWEnable11i(B.11.31.0909.341b) Hardware Enablement Patches

(64-bit kernel) for HP-UX 11i v3, September 2009
• FEATURE11i(B.11.31.0909.341b) Feature Enablement Patches for
HP-UX 11i v3, September 2009
• QPK1131(B.11.31.0909.341a) Quality Pack Depot for 11i v3,
September 2009
Oracle Solaris 10 (64-bit kernel) Oracle Solaris 05/09 Patch Bundle
IBM AIX 7 (64-bit kernel) Service Pack Level 06
Red Hat Enterprise Linux 5.0 ES Update 3
64-bit kernel on x64
SUSE Linux Enterprise Server 11
Windows Server 2008, Enterprise x64 Service Pack 1
(64-bit kernel)
HP Exstream Command Center User Interface

Windows Vista Enterprise Service Pack 2

Windows 7 Enterprise NA
Customer Environment
For the customer environment, set up the following:
 Software for the middleware infrastructure, if applicable.
For example, if IBM WebSphere MQ is used, it must be installed and configured before installing HP Exstream
Command Center.
 Software for implementing the necessary interactions with HP Exstream Command Center.
For example, you must configure JMS dependency files.
JMS Dependencies
A JMS provider is a messaging system that implements JMS API interfaces to enable interaction between
HP Exstream Command Center and external clients or services. It helps the clients or services leverage the JMS
functionality of HP Exstream Command Center.
JMS vendor jars are required for running JMS delivery queues and JMS service providers. You can get the
necessary jar files from JMS vendors. For example, to use IBM WebSphere MQ, you need the following jars:
 com.ibm.mqjms.jar, com.ibm.mq.jar
 com.ibm.mq.pcf-6.1.jar
 connector.jar, dhbcore.jar, mqcontext.jar

When you have the required jar files, perform the following steps:
1. Copy the jar files into the wrapping jar examples/wrappers/com.hp.exstream.
cc.jms.ibmmq.wrapper.fragment.jar and move the wrapping jar to the var/bundles directory.
2. To provide additional jar files, manually edit wrapping jar manifest
com.hp.exstream.cc.jms.ibmmq.wrapper.fragment.jar/META-INF/MANIFEST.MF and add
the names of the jar files into the Bundle-ClassPath property.
The com.hp.exstream.cc.jms.ibmmq.wrapper.fragment.jar file is shipped with HP Exstream
Command Center for IBM WebSphere MQ JMS implementation. For other implementations, be sure the
Bundle-ClassPath property in the manifest is set to a list of jar files copied into the wrapping jar.
HP Exstream Command Center WebGUI

You must meet the following requirements for HP Exstream Command Center WebGUI:
Parameter Minimum Requirement
Monitor resolution 1024x768 pixels

It is best viewed with 1280 X 1024 pixels
Supported Web browser Internet Explorer 7.0 (or later) or Mozilla Firefox 3.0 (or later)
Network connection HTTP or HTTPS network connection with HP Exstream Command Center
Server
HP Exstream Delivery Engine-Specific System Requirements

To install HP Exstream Delivery Engine, you need to manually deploy the database setup files and HP Exstream
Delivery Engine setup files on an application server. You must follow the prerequisites section before deploying
the HP Exstream Delivery Engine.
 HP Exstream Delivery Engine System Requirements on page 18
 Operating System and Patches on page 19
 JBOSS Specific Requirement on page 19
 JMS Interface Requirements on page 20
 JCR Requirements on page 20
HP Exstream Delivery Engine System Requirements

Before you begin, make sure you meet the following minimum requirements:
Component Requirements
Monitor 1280 x 1024 pixels resolution

Hardware Dual-Core Intel® Pentium® or similar with processor speed of 2.6 Ghz,
4GB RAM or more, 1GB free disk space
Software JDK—Oracle JDK 1.6 SP 26
Browser Internet Explorer 7.0 or Mozilla Firefox 3.6

Operating System and Patches

The following table identifies the recommended operating systems certified by HP with HP Exstream Delivery
Engine:
HP-UX 11.31 on PA-RISC HWEnable11i(B.11.31.0909.341b) Hardware Enablement Patches

FEATURE11i(B.11.31.0909.341b) Feature Enablement Patches for
QPK1131(B.11.31.0909.341a) Quality Pack Depot for 11i v3,
September 2009
HP-UX 11.31 on Itanium (IA-64) HWEnable11i(B.11.31.0909.341b) Hardware Enablement Patches
September 2009
Technology Level 03
SUSE Linux Enterprise Server 10 Service Pack 2
SEUS Linux Enterprise Server 11 —
Windows Server 2003 R2, Enterprise Service Pack 2
x64 Edition (64-bit kernel)
(64-bit kernel)
JBOSS Specific Requirement

If you run JBoss 5.X that is compiled for Java 5 on Java 6, you must manually copy the following libraries from the
JBoss_HOME/client directory to the JBoss_Home/lib/endorsed directory, so that JAX-WS 2.0 API’s
supported by JBoss are used:
 jbossws-native-saaj.jar
 jbossws-native-jaxrpc.jar
 jbossws-native-jaxws.jar
 jbossws-native-jaxws-ext.jar
NOTE: This specific requirement is required only if you use the SOAP delivery channel.
You can view the Java version on console while starting your JBoss instance.

No action is required if you run JBoss 5.x compiled for Java 6.
JMS Interface Requirements

To enable JMS interface for communication between HP Exstream Command Center/HP Exstream Fulfillment
Delivery Service and HP Exstream Command Center, you must install ActiveMQ 5.5.X.
JCR Requirements
JCR can be installed on any hosts other than HP Exstream Command Center and HP Exstream Delivery Engine.
For better performance, install the Jackrabbit implementation of JCR from Apache Jackrabbit Version 2.2.5
available on the Apache Jackrabbit Web site.
For more information, see http://jackrabbit.apache.org/
To install the JCR, download and unzip the package file.
For more information about configuring JCR for HP Exstream Delivery Engine, see Configuring Java Content
Repository Details on page 96.
HP Exstream Fulfillment Delivery Service-Specific System

Requirements
To install HP Exstream Fulfillment Delivery Service (FDS), you need to deploy the database setup files and
HP Exstream Fulfillment Delivery Service setup files on an application server.
 HP Exstream Fulfillment Delivery Service System Requirements on page 20
 Operating System Patches on page 21
 HP Exstream Delivery Engine Requirements for HP Exstream Fulfillment Delivery Service on page 22
 HP Exstream Engine Requirement for HP Exstream Fulfillment Delivery Service on page 22
 HP Exstream Fulfillment Delivery Service Document Composition Mode Requirements on page 22
 Web Container Requirements on page 23
HP Exstream Fulfillment Delivery Service System Requirements

The basic requirement for FDS server and FDS WebGUI is an operating system running Java Runtime Environment
(JRE) Version 6.0 or later. Oracle provides JRE for several platforms including Windows, Linux, and Oracle Solaris on
Oracle Web site. For other platforms, see your operating system manual.
Before you begin, make sure you meet the following minimum requirements.
Type Requirements
Monitor 1280 x 1024 pixels

Hardware Dual-Core Intel® Pentium® or similar with processor speed of 2.6 Ghz,
4GB RAM or more, 1GB free disk space.

Type Requirements
Software JDK 1.6.0.x (Update 27 or later)

HP-UX JDK 6.0.x
IBM Java 6.0
HP Exstream Production Engine 8.0.301 or later
HP Exstream EWS 2.0.0002 (EWS)
A license key is required for installing and configuring HP Exstream Fulfillment Delivery
Service. To obtain the license key, contact software.keys@hp.com.
Browser Internet Explorer 7.0, Mozilla Firefox 6.00
Operating System Patches

The following table identifies the recommended operating system patches that HP has tested for use with HP Exstream
Fulfillment Delivery Service. More recent operating system patches, quality releases, or service packs might exist. For
the latest information, you must check the Web sites of the respective products.
Supported operating systems and patch levels in HP Exstream Fulfillment Delivery Service
HP-UX 11.31 on PA-RISC HWEnable11i(B.11.31.0909.341b) Hardware Enablement

(64-bit kernel) Patches for HP-UX 11i v3, September 2009
September 2009
HP-UX 11.31 on Itanium (IA-64) HWEnable11i(B.11.31.0909.341b) Hardware Enablement
(64-bit kernel) Patches for HP-UX 11i v3, September 2009
September 2009
Technology Level 03
SUSE Linux Enterprise Server 10 Service Pack 2
(64-bit kernel)

HP Exstream Delivery Engine Requirements for HP Exstream Fulfillment

Delivery Service
HP Exstream Delivery Engine is required for on-demand delivery of composed documents.
NOTE: This setup is mandatory to integrate HP Exstream Fulfillment Delivery Service with
HP Exstream Delivery Engine.
You must set up and start HP Exstream Delivery Engine.
For more information about deploying HP Exstream Delivery Engine, see Installing and Deploying the
HP Exstream Delivery Engine on page 37.
HP Exstream Engine Requirement for HP Exstream Fulfillment Delivery

Service
HP Exstream engine, version 8.0.301 or later must be installed.
For more information about installing HP Exstream engine, see the HP Exstream documentation set.
HP Exstream Fulfillment Delivery Service Document Composition Mode

Requirements
Before you configure a document in composition mode, make sure that you have the HP Exstream application
enabled for HP Exstream Delivery Manager integration.
For more information about enabling an HP Exstream application for HP Exstream Delivery Manager
integration, see the HP Exstream Delivery Manager User’s Guide.
To compose documents on demand in HP Exstream Fulfillment Delivery Service, you must configure the HP Exstream
Production Engine 8.0.301 or later with EWS or with real-time support.
HP Exstream Fulfillment Delivery Service supports the following modes of document composition:
• HP Exstream Production Engine 8.0.301 or later installed with EWS
• HP Exstream Production Engine 8.0.301 or later installed with real-time support
 EWS Document Composition Mode on page 22
 Real-time Composition Mode on page 23
EWS Document Composition Mode

When using EWS as the document composition mode in HP Exstream Fulfillment Delivery Service, users can
remotely submit customer driver file data to the HP Exstream engine to compose output and receive composed output
from HP Exstream.
To configure the EWS as the document composition mode in HP Exstream Fulfillment Delivery Service, set up and
start EWS.
For more information about setting up EWS, see the EWS and SOAP Connector chapter in the Connecting
HP Exstream to an Enterprise Architecture guide of the HP Exstream documentation.

Real-time Composition Mode

Make sure that HP Exstream Production Engine 8.0.301 or later is installed with real-time support. There are
multiple ways of setting up real-time engines. The below mentioned procedure is one of the ways of setting up
real-time engine in HP Exstream. If you have expertise in using HP Exstream Production Engine, you can go
forward with your own way of setting up the real-time engine.
To configure the real-time engine as the document composition mode in HP Exstream Fulfillment Delivery Service:
1. Set up and start ActiveMQ 5.5.X.
If ActiveMQ is already installed and running in your system, ignore this step.
2. Set up real-time engines by using the realtime-util utility provided as part of the HP Exstream Fulfillment
Delivery Service distribution file.
For more information about setting up real-time engine, see Setting up the Real-time Composition Engine for
HP Exstream Fulfillment Delivery Service on page 96.
Web Container Requirements

Download and install one of the Web containers (Apache Tomcat 7.0.0, WebLogic 10.3.5 or later, and IBM
WebSphere 7) to deploy the HP Exstream Fulfillment Delivery Service.

Installing and Deploying Command Center

 Pre-Installation Checklist on page 24
 Command Center Package File Contents on page 25
 Installing Command Center on page 25
 Preparing for Deployment on page 26
 Deploying Command Center WebGUI on page 28
 Deploying Command Center Data Channels on page 29
 Running Command Center Server and Command Center WebGUI on Different Domains on page 29
 Securing Communication with Command Center on page 30
 Command Center 2.2.0 Migration on page 31
 Command Center Commands on page 35
NOTE: To integrate Command Center with the Delivery Engine, you must install the Delivery Engine
before you install Command Center.
Pre-Installation Checklist
Before you install Command Center, verify the following:
 Is your platform supported?
 Do you have the recommended patches for your platform?
 Does your platform require specific procedures or considerations?
 Are patches available for Command Center?
 Do you have sufficient swap space?
 Do you have sufficient disk space?
 Do you have sufficient physical memory?
 What are the device dependencies and limitations?
 Are permissions set correctly on your system?
 Do you have the required ports for Command Center installation?
 Do you have a valid license key?

Command Center Package File Contents

Command Center can be delivered individually (in the Command_Center_2_2_0.zip file) or as a part of the
full Delivery Manager package file (in the delivery-engine-1.2.0.zip file). Each package file contains
the following Command Center content:
Delivery Engine package contents

This content is provided in
Description
the Delivery Engine package
bin/ directory This directory contains the files needed to migrate an existing
Command Center database.
conf/ directory This directory contains configuration files for Command Center.
database-setup/ directory This directory contains utility and SQL scripts to initialize database.
db/ directory This directory contains embedded HSQLDB content (not intended for
production).
docs/ directory This directory contains licenses and source code for the open source
resources used by Delivery Manager.
examples/ directory This directory contains data for sample job definitions and actions.
lib/ directory This directory contains Command Center libraries.
var/ directory This directory is used to store temporary files or customer files (such as
packages and job outputs).
Installing Command Center

1. Depending on the package file you received, do one of the following:
For this package Do this
Command Center only package Unzip the Command_Center_2_2_0.zip package file.

file
Delivery Manager package file Unzip the Delivery_Manager_1_2_0.zip package file.
2. Create a database.
For more information about creating a database for use with Delivery Manager components, see Creating
Databases for HP Exstream Delivery Manager Components on page 14.
3. Copy the JDBC driver to the following directory:

<CC_HOME>/lib/user
4. Setup the database connection using the following file:
<CC_HOME>/conf/server.properties
5. Depending on your operating system, run one of the following scripts:
Windows <CC_HOME>/bin/command-center.bat
UNIX <CC_HOME>/bin/command-center.sh

6. Use the Configuration Console to update any configuration settings that are required for Command Center.
For more information about Command Center configuration settings, see HP Exstream Delivery Manager
Configuration Console on page 48.
Preparing for Deployment

The Web user interface and Data Channel Web services are distributed as independent WAR files. Wars files
for these two applications are located in the <CC_HOME>/lib/bundles/cc directory. By default, the WAR
files should be deployed with Command Center; however, you can move the files so that they can be deployed
on separate application servers.
For more information about deploying WebGUI and Data Channels on separate application servers, see
Running Command Center Server and Command Center WebGUI on Different Domains on page 29.

 Preparing for Command Center Deployment on Oracle Weblogic on page 26
 Preparing Command Center for Deployment on IBM Websphere on page 27
 Preparing Command Center for Deployment on Apache Tomcat on page 27
Preparing for Command Center Deployment on Oracle Weblogic

1. To prepare for deployment, you must copy the following files in order to deploy Command Center on Oracle
Weblogic:
To deploy this Copy these files From this location To this location
WebGUI user • cc-webgui- <CC_HOME>/conf <Weblogic domain>/

interface security.xml conf
• cc-webgui-
If the <Weblogic
server-list.xml
domain>/conf
directory does not exist,
you must create it.
Data Channel WAR • data- <CC_HOME>/conf <Weblogic domain>/
file channels.propert conf
ies
If the <Weblogic
• cc-channels- domain>/conf
security.xml directory does not exist,
you must create it.

2. Make sure that the <Weblogic domain>/conf directory is in the classpath. To add this information to the
classpath, do the following:
For this Platform Do this
Windows 1. Open the following file:

setDomainEnv.bat
2. Add the following syntax:
set CLASSPATH=%CLASSPATH%;%DOMAIN_HOME%\conf
UNIX 1. Open the following file:
<Weblogic domain>/bin/setDomainEnv.sh
export CLASSPATH=$CLASSPATH:$DOMAIN_HOME/conf
Preparing Command Center for Deployment on IBM Websphere

To prepare for deployment, you must copy the following files in order to deploy Command Center on IBM
WebSphere:
WebGUI user interface • cc-webgui- <CC_HOME>/conf classpath

security.xml
• cc-webgui-
server-list.xml
Data Channel WAR file • data- <CC_HOME>/conf classpath
channels.proper
ties
• cc-channels-
security.xml
Preparing Command Center for Deployment on Apache Tomcat

To prepare for deployment, you must copy the following files in order to deploy Command Center on Apache
Tomcat:
WebGUI user interface • cc-webgui- <CC_HOME>/conf classpath

security.xml
• cc-webgui-
server-list.xml
Data Channel WAR file • data- <CC_HOME>/conf classpath
channels.proper
ties
• cc-channels-
security.xml

Enabling SSL Communication on Tomcat with Command Center Server

If you want to enable SSL communication on an Apache Tomcat server, you must complete the following task for
both data channel and WebGUI deployment.
To enable SSL communication on Tomcat:
1. Add your SSL trusted certificate to classpath.
2. Depending on your operating system, edit one of the following files:
Operating system File
Windows setclasspath.bat
UNIX setclasspath.sh
3. Depending on your operating system, add the following syntax:
Operating system Syntax
Windows set JAVA_OPTS=%JAVA_OPTS% -

Djavax.net.ssl.trustStore=cc-jetty-keystore.jks -
Djavax.net.ssl.trustStorePassword=<jettystorepasswo
rd>
UNIX export JAVA_OPTS="$JAVA_OPTS -
Djavax.net.ssl.trustStore=cc-jetty-keystore.jks -
Djavax.net.ssl.trustStorePassword=<jettystorepasswo
rd>"
4. Complete any additional tasks needed to secure communication with Command Center.
For more information about securing Command Center communications, see Securing Communication with
Command Center on page 30.
Deploying Command Center WebGUI

Command Center WebGUI can be deployed using the following Web/application servers:
 Apache Tomcat
 IBM WebSphere
 Oracle WebLogic
For more information about Web/application server requirements, see HP Exstream Delivery Manager
Application (Web) Server Requirements on page 14.
To deploy Command Center WebGUI:

1. Copy the cc-webgui-security.xml file and cc-webgui-server-list.xml file to the appropriate
directory for your application server.
For more information about where to locate and copy the files that are required to deploy WebGUI, see
Preparing for Deployment on page 26.

2. Deploy the cc-webgui.war file. By default, the WAR file is at the following location:
<CC_ROOT>/lib/bundles/cc
For more information about deploying to a specific application server, see the application server documen-
tation.
3. To verify the deployment, use a Web browser to go to the application home page (http://<host>:<port>/
cc-webgui). If the deployment was successful, the main page opens. If the Web page does not load or if an
error message is issued, you must verify your deployment and configuration settings.
Deploying Command Center Data Channels

Command Center Data Channels supports the following Web services:
 SOAP
 REST
Command Center Data Channels can be deployed using the following Web/application servers:
 Apache Tomcat
 IBM WebSphere
 Oracle WebLogic
To deploy Command Center Data Channels:

1. Copy the data-channels.properties file and the cc-channels-security.xml file to the appro-
priate directory for your application server.
For more information about where to locate and copy the files that are required to deploy Command Center
Data Channels, see Preparing for Deployment on page 26.
2. Deploy the cc-channels.war file. By default, the WAR file is at the following location:
<CC_ROOT>/lib/bundles/cc
3. To verify the deployment, use a Web browser to go to the application home page (http://<host>:<port>/
cc-channels).If the deployment was successful, the main page opens. If the Web page does not load or if an
error message is issued, you must verify your deployment and configuration settings.
Running Command Center Server and Command Center WebGUI

on Different Domains
If the Command Center server and WebGUI client are run on different domains, you must set the
java.rmi.server.hostname property to ensure that RMI uses a host name (or IP address) that is routable
from all potential clients.
The java.rmi.server.hostname property is located in the following file:
<CC_ROOT>/bin/wrapper/wrapper.conf
The java.rmi.server.hostname property specifies the host name or address to put in the stubs for remote
objects that are exported to this Java virtual machine. The value of the java.rmi.server.hostname
property is the host name or address used by clients when they attempt to communicate remotely. By default, the

RMI implementation uses the server's IP address as indicated by the

java.net.InetAddress.getLocalHost API; however, some clients require a fully qualified host name.
For example:
wrapper.java.additional.14=-
Djava.rmi.server.hostname=your.cc.server.host.name.your.domain.com
On some operating systems, you might also need to specify the RMI server host name. By default, the RMI
registry is exported to the 'localhost'.
Securing Communication with Command Center

Data Channels and WebGUI communicate with Command Center server using RMI. By default, this communi-
cation is not secured; however you can use certificate-based encryption to activate secured communication. To
set up encrypted communication between the Command Center server and other endpoints, you must have a
private key and the appropriate security certificate. The private key and certificate must be created for the full
domain name of the computer where Command Center is running. The computer name is the value for the CN
attribute in both the key and the certificate.
 Securing the Server Side of Command Center on page 30
 Securing the Client Side of Command Center on page 31
 Securing a Web Connection to Command Center on page 31
Securing the Server Side of Command Center

To setup secured communication on the Command Center server, a server certificate and key must be stored in
a Java keystore file. You must use only one certificate and one private key per keystore file.
To configure secure communication on the server side of Command Center:
1. Open the server.properties file. By default this file is at the following location:
<cc_root>/conf/server.properties
2. Change value of the provider.rmi.ssl.enabled property to true.
3. Open the wrapper.conf file. By default this file is at the following location:
<cc_root>/bin/wrapper/wrapper.conf
4. Update the values of the following properties with the appropriate information:
Property Description
javax.net.ssl.keyStore Path to keystore with private key and certificate

javax.net.ssl.trustStore Path to keystore with trusted certificate (for the server,
this property can have the same value as the
previous property)
javax.net.ssl.keyStorePassword Password for keystore
javax.net.ssl.trustStorePassword Password for keystore with trusted certificates
5. You can confirm whether RMI is running over SSL by verifying if RMI over SSL enabled messages was logged.

Securing the Client Side of Command Center

Before you set up SSL on the client side of Command Center, keep in mind the following considerations:
 Any application server that is used to connect Data Channels and WebGUI to the Command Center server must
have a server certificate in a Java keystore file.
 You must store only trusted certificates using the Java keystore.
 The certificate password must be the same as the keystore password.
 Applications must have access to the following Java system properties:
• javax.net.ssl.trustStore
• javax.net.ssl.trustStorePassword
To secure the client side of Command Center, run the client with the following JVM options:
 -Djavax.net.ssl.trustStore=<path to keystore>
 -Djavax.net.ssl.trustStorePassword=<keystore password>
For more information about applying SSL to a Tomcat application server, see Enabling SSL Communication
on Tomcat with Command Center Server on page 28.
Securing a Web Connection to Command Center

When you access the Command Center user interface, the communication can be encrypted with server certif-
icate over HTTPS protocol.
You must configure HTTPS access to fileview servlets and (in case of a standalone Command Center installation)
configure access to WebGUI over HTTPS.
To secure a Web connection to Command Center:
1. Open the following properties file:
edit <cc_root>/conf/internal/platform.properties
2. Set the org.osgi.service.http.secure.enabled property to true.
3. Open the server.properties file.
4. Update the URL values for the following properties to use the HTTPS prefix:
• jobmng.reports.fileview.urlprefix
• jobmng.jobstore.fileview.urlprefix
• poolmng.fileview.urlprefix
• cluster.fileview.urlprefix
5. Update any port numbers where HTTPS will run. By default, the port is 8082.
Command Center 2.2.0 Migration

You can migrate databases from Command Center versions 1.1, 1.1.1, or 2.1.1 to Command Center version 2.2.0.
Keep in mind that you can migrate databases only if there were no updates to the database schema since the
original installation of Command Center.
After Command Center 2.2.0 is installed, the migration scripts are located in the <cc_root>/database-
setup/migration directory. Scripts are titled by product, database, source version, and target version (for
example, cc_oracle_1.1.0_to_2.2.0).


 Preparing for Migration on page 32
 Migrating Command Center Databases on page 32
Preparing for Migration

Before migrating to Command Center 2.2.0, complete the following:
1. Stop and exit the previous version of Command Center.
2. Install Command Center 2.2.0.
For more information about installing Command Center, see Installing Command Center on page 25.
3. Set up the database drivers that are required for Command Center 2.2.0.
For more information about setting up database drivers, see Creating Databases for HP Exstream Delivery
Manager Components on page 14.
4. If Command Center is using a HSQL database, delete the <cc_root>/db directory in the Command Center
2.2.0 installation and copy the <cc_root>/db directory from the previous installation.
5. Update the Command Center configuration for the Command Center 2.2.0 installation (for example, setting up
the database connection and jobstore directory). In most cases, you can update the configuration according to the
settings that were used in the previous installation.
For more information about Command Center configuration settings, see HP Exstream Delivery Manager
Configuration Console on page 48.
6. Copy the job directory that is specified by the jobmng.jobstore.dir property in the <cc_root>/conf/
server.properties file in the Command Center 2.2.0 installation directory.
7. Migrate the command center database.
For more information about migrating Command Center databases, see Migrating Command Center
Databases on page 32.
8. Start the latest version of Command Center.
Migrating Command Center Databases

After Command Center 2.2.0 is installed, the migration scripts are located in the <cc_root>/database-
setup/migration directory. Scripts are titled by product, database, source version, and target version (for
example, cc_oracle_1.1.0_to_2.2.0).
 Migrating HSQL Databases on page 32
 Migrating MySQL, MSSQL, DB2, and Oracle Databases on page 33
Migrating HSQL Databases

To migrate a HSQL database, the HSQL database must be running in server mode.
The following task assumes that the HSQL database is located in the <cc_root>/db directory and that the
default database name is cc-server. If the HSQL database uses different settings, you must modify this task
as needed to use the correct paths and database name for your system.

To migrate a HSQL database:

1. Back up the HSQL database that you want to migrate by copying the <cc_root>/db directory to a backup
location.
2. Rename the directory to <cc_root>/database-setup/bin.
3. Start the HSQL database in server mode. For example:
-run java -cp ../lib/hsqldb-1.8.0.1.jar org.hsqldb.Server -database.0 file:../
../db/cc-server -dbname.0 cc-server
4. Run the dm-sqlexecutor script and use jdbc:hsqldb:hsql://localhost/cc-server as the
database connection string.
Example for Windows

dm-sqlexecutor.bat -d hsqldb -l jdbc:hsqldb:hsql://localhost/cc-server -u sa -s
../migration/cc_hsqldb_<source version>_to_2.2.0.sql
Example for Linux or UNIX

dm-sqlexecutor.sh -d hsqldb -l jdbc:hsqldb:hsql://localhost/cc-server -u sa -s
../migration/cc_hsqldb_<source version>_to_2.2.0.sql
After the SQL script has completed, you receive a message that provides the number of successfully executed
queries.
5. Stop the HSQL database in server mode.
Migrating MySQL, MSSQL, DB2, and Oracle Databases

1. Back up the database that you want to migrate.
2. If you are upgrading from Command Center version 1.1.1, complete the following steps based on the type of
database that you are migrating:
For this
Do this
database type
MS SQL 1. Run the following query:
SELECT CONSTRAINT_NAME FROM
INFORMATION_SCHEMA.TABLE_CONSTRAINTS WHERE TABLE_NAME LIKE
'SignatureValidation' AND CONSTRAINT_TYPE NOT LIKE
'PRIMARY_KEY';
2. Write down the value of the CONSTRAINT_NAME column.
3. Run the following query:
ALTER TABLE dbo.SignatureValidation DROP CONSTRAINT
enter_previously_written_constraint_name_here;

For this
database type Do this
MySQL 1. Run the following query:

SELECT constraint_name FROM
information_schema.table_constraints WHERE table_schema =
schema() AND table_name = 'signaturevalidation' AND
constraint_name NOT LIKE "PRIMARY";
2. Write down the value(s) of the constraint_name column.
3. For each value, run the following query:
ALTER TABLE signaturevalidation DROP FOREIGN KEY
enter_previously_written_constraint_name_here;
SHOW INDEX FROM signaturevalidation WHERE key_name NOT LIKE
'PRIMARY';
5. If the query returns any results, write down the value(s) provided in the
key_name column.
6. For each value, run the following query:
ALTER TABLE signaturevalidation DROP KEY
enter_previously_written_key_name_here;
DB2 1. Run the following query:
SELECT CONSTNAME FROM SYSCAT.TABCONST WHERE TYPE IN ('F')
AND TABNAME='SIGNATUREVALIDATION';
2. Write down the value of the CONSTNAME column.
ALTER TABLE signaturevalidation DROP CONSTRAINT
enter_previously_written_CONSTNAME_here;
Oracle 1. Run the following query:
SELECT constraint_name FROM all_constraints WHERE
constraint_type IN ('R') AND
table_name='SIGNATUREVALIDATION';
2. Write down the value of the constraint_name column.
ALTER TABLE signaturevalidation DROP CONSTRAINT
enter_previously_written_name_here;
4. Copy the database driver to the following directory:

<cc_root>/database-setup/lib
5. Go to the <cc_root>/database-setup/bin directory for the new Command Center installation.
6. Depending on your operating system, execute the migration script using one of the following scripts:
Windows dm-sqlexecutor.bat
UNIX/Linux dm-sqlexecutor.sh

7. Depending on your operating system, use the following syntax in the migration script:
Operating
Syntax
system
Windows dm-sqlexecutor.bat -d <oracle/mssql/mysql/hsql>

-l <database connection string>
-u <username>
-p <password>
-s ../migration/<migration script>
UNIX/Linux dm-sqlexecutor.sh -d <oracle/mssql/mysql/hsql>
-u <username>
-p <password>
Keep the following considerations in mind when creating the syntax for the migration script:
• In the -d parameter, mssql denotes the jTDS JDBC Driver.
• If you're using Microsoft JDBC Driver for SQL Server, the -d parameter must be set to mssqlsrv.
• The -l parameter (the database connection string) is the JDBC connection URL for your database.
Example migration script syntax:

dm-sqlexecutor.bat -d mssql -l jdbc:jtds:sqlserver://localhost/CC111 -u CC111 -p
CC111 -s ../migration/cc_mssql_1.1.1_to_2.2.0.sql
When the migration script completes, you receive a message that provides the number of successfully executed
queries.
Command Center Commands

You can use the following commands to run Command Center from the command line:
Command Usage
active Start the server in active mode in load balancing.

passive Start the server in passive mode in load balancing.
install Install the distribution as a Windows Service.
This option is available only on Windows operating systems.
start Start a distribution registered as a Windows Service. Before you use the start
command, you must complete the Command Center installation or use the install
command; otherwise, the operation will fail.
stop Stop a distribution registered as a Windows Service. Before you use the stop
command, you must complete the Command Center installation or use the install
command; otherwise, the operation will fail.
status Print the current status of the application (running/not running).

Command Usage
restart Restart an application running in the background. If the application was not running,
start the package.
remove Remove the distribution from Windows Service.
This option is available only on Windows operating systems.
console Start the application in the foreground.
dump Instructs the JVM to dump debugging information (stack traces for all threads). This
information is available in the logs/Command Center-wrapper.out file.
help Print all available commands.
• -b,--benchmark: run performance benchmark, create report and shutdown
Command Center (warning: benchmark will modify current database)
• --create-examples: insert examples into the database
• -e,--export <file>: export from database into the given file
• -f,--export-configuration <file>: export of configuration entities (i.e. jobs
are not included) from database into the given file
• -h,--help: print this help
• -i,--import <file>:import data from given file into the database
• usage Same as help.

Installing and Deploying the HP Exstream Delivery Engine
Installing and Deploying the HP Exstream

Delivery Engine

 HP Exstream Delivery Engine Package File Contents on page 37
 Installing the HP Exstream Delivery Engine on page 37
 Deploying the HP Exstream Delivery Engine on page 38
 Validating the HP Exstream Delivery Engine Installation on page 41
 Configuring the HP Exstream Delivery Channels on page 42
 Enabling Communication with the HP Exstream Delivery Engine on page 42
NOTE: To integrate HP Exstream Command Center with the HP Exstream Delivery Engine, you must
install the HP Exstream Delivery Engine before you install HP Exstream Command Center.
HP Exstream Delivery Engine Package File Contents

The delivery-engine-1.2.0 package file contains the following content:
HP Exstream Delivery Engine package contents

the HP Exstream Delivery Description
Engine package
conf/ directory This directory contains the following configuration files for the
HP Exstream Delivery Engine:
• de.properties
• deglobal.properties
• de-security.xml
database-setup/ directory This directory contains utility and SQL scripts to initialize database.
licenses/ directory This directory contains licenses and source code for third party open
source libraries used in the HP Exstream Delivery Engine.
Two WAR files: • The de-distribution.war file is the HP Exstream Delivery Engine
server.
• de-distribution.war
• The deWebUi.war is the HP Exstream Delivery Engine UI.
• deWebUi.war
Installing the HP Exstream Delivery Engine

1. Unzip the Delivery_Manager_1_2_0.zip package file.

For more information about creating a database for use with HP Exstream Delivery Manager components,
see Creating Databases for HP Exstream Delivery Manager Components on page 14.
3. Copy configuration files from the conf/ directory to application server classpath.
4. Use the Configuration Console to update any configuration settings that are required for the HP Exstream
Delivery Engine.
For more information about the HP Exstream Delivery Engine configuration settings, see HP Exstream
Delivery Engine Configuration on page 76.
5. Copy the JDBC driver to the application server classpath.

6. Deploy the de-distribution.war file to the application server.
7. Deploy the deWebUi.war file to application server.
Deploying the HP Exstream Delivery Engine

The HP Exstream Delivery Engine can be deployed using the following Web/application servers:
 Apache Tomcat
 IBM WebSphere
 JBoss
 Oracle WebLogic

 Preparing for Deployment on page 38
 Deploying the HP Exstream Delivery Engine with WebSphere on page 39
 Deploying the HP Exstream Delivery Engine with Weblogic on page 39
 Deploying the HP Exstream Delivery Engine with JBoss on page 39
 Deploying the HP Exstream Delivery Engine with Tomcat 7 on page 40
Preparing for Deployment

1. Connect to the administration console of your application server.
2. Create a JDBC data source named DEDS.
NOTE: If you want to deploy the HP Exstream Delivery Engine application with a different JNDI
data source name than DEDS, edit the deglobal.properties and set the
DE_DATASOURCE_NAME property to the JNDI name you want to use.
3. Start ActiveMQ.

Deploying the HP Exstream Delivery Engine with WebSphere

If you deploy any HP Exstream Delivery Manager component with WebSphere, then all components must use
the Classes loaded with local class loader first (parent last) setting.
To deploy the HP Exstream Delivery Engine with WebSphere:
1. Connect to the administration console. For WebSphere, the administration console address is similar to the
following:
http://localhost:9060/ibm/console/login.do
2. Go to Application > Application Types > WebSphere enterprise applications.
3. Select the application that you want to update and click Manage Module.
4. Select the HP Exstream Delivery Engine WAR file.
5. Change the Class loader option to Class loaded with local class loader first (parent last).
6. Open the deglobal.properties file.
7. Edit the following settings:
• [DS_INIT_CONTEXT_FACTORY=com.ibm.websphere.naming.WsnInitialContextFactory
• DS_PROVIDER_URL=corbaloc:iiop:localhost:2809
– If there is another port configured in the profile where the application is being deployed, use that port
instead of the default, 2809.
• DE_DATASOURCE_NAME=DEDS
– If you used a different JNDI data source name, then use that name instead of DEDS.
Deploying the HP Exstream Delivery Engine with Weblogic

To deploy the HP Exstream Delivery Engine with Weblogic, you must make sure that the following parameters
are empty in the deglobal.properties file:
• DS_INIT_CONTEXT_FACTORY=
• DS_PROVIDER_URL=
• DS_FACTORY_URL_PKGS=
Deploying the HP Exstream Delivery Engine with JBoss

1. Deploy the Web application to the JBoss server.
For information about deploying the Web application, locating the JBoss application server classpath for
the deployed application, and creating a data source, see the JBoss documentation.
2. In JBoss 5, make sure that the application can access classpath files at the following locations:
• server/<deployed application server>/conf
• server/<deployed application server>/lib
3. In the deglobal.properties file, update the values of the following properties:
• DS_INIT_CONTEXT_FACTORY=org.jnp.interfaces.NamingContextFactory
• DS_PROVIDER_URL=jnp://localhost:1099
• DS_FACTORY_URL_PKGS=org.jnp.interfaces
• DE_DATASOURCE_NAME=java:DEDS
HP Exstream Delivery Engine data source example

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<datasources>
<local-tx-datasource>
<jndi-name>DEDS</jndi-name>
<rar-name>jboss-local-jdbc.rar</rar-name>
<use-java-context>true</use-java-context>
<connection-definition>javax.sql.DataSource</connection-definition>
<jmx-invoker-name>jboss:service=invoker,type=jrmp</jmx-invoker-name>
<min-pool-size>0</min-pool-size>
<max-pool-size>10</max-pool-size>
<blocking-timeout-millis>30000</blocking-timeout-millis>
<idle-timeout-minutes>30</idle-timeout-minutes>
<prefill>false</prefill>
<background-validation>false</background-validation>
<background-validation-millis>0</background-validation-millis>
<validate-on-match>true</validate-on-match>
<statistics-
formatter>org.jboss.resource.statistic.pool.JBossDefaultSubPoolStatisticFormatte
r</statistics-formatter>
<isSameRM-override-value>false</isSameRM-override-value>
<allocation-retry>0</allocation-retry>
<allocation-retry-wait-millis>5000</allocation-retry-wait-millis>
<application-managed-security xsi:type="securityMetaData"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<metadata/>
<local-transaction/>
<user-name>de</user-name>
<password>de</password>
<prepared-statement-cache-size>0</prepared-statement-cache-size>
<share-prepared-statements>false</share-prepared-statements>
<set-tx-query-timeout>false</set-tx-query-timeout>
<query-timeout>0</query-timeout>
<use-try-lock>0</use-try-lock>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<connection-url>jdbc:mysql://localhost:3306/de</connection-url>
</local-tx-datasource>
</datasources>
Deploying the HP Exstream Delivery Engine with Tomcat 7

1. Open the following file:
conf/server.xml
2. Update the GlobalNamingResources section. For example:
<Resource name="DEDS" auth="Container"
type="javax.sql.DataSource"driverClassName="oracle.jdbc.OracleDriver"
url="jdbc:oracle:thin:@localhost:1521:ORCL"
username="deadmin" password="deadmin" maxActive="20" maxIdle="10"
maxWait="-1"/>
3. Open the following file:
conf/context.xml
4. Update the Context section. For example:
<ResourceLink global="DEDS" name="DEDS"
type="oracle.jdbc.pool.OracleDataSource"/>
5. In the deglobal.properties file, update the values of the following properties:

• DS_INIT_CONTEXT_FACTORY=org.apache.naming.java.javaURLContextFactory
• DS_FACTORY_URL_PKGS=org.apache.naming
• DE_DATASOURCE_NAME=java:comp/env/DEDS
Validating the HP Exstream Delivery Engine Installation

1. Open a Web browser.
2. In the address bar, enter the following address:
http://<IP address>:<port>/deWebUi
3. Log in to the HP Exstream Delivery Engine administration console.
If the HP Exstream Delivery Engine main page appears, HP Exstream Delivery Engine was successfully
installed.
Validating the HTTP Interface for the HP Exstream Delivery Engine

http://<IP address>:<port>/de-distribution/DEHttpProvider
For example, http://16.14.214.244:8090/de-distribution/DEHttpProvider
If a blank screen appears, the HTTP interface is functioning properly. If the HTTP interface is not functioning
properly, you receive an error message. To resolve the issue, you must review the application log file.
Validating the JMS Interface for the HP Exstream Delivery Engine

http://localhost:8161/admin/queues.jsp
If the ActiveMQ administration page appears, the JMS interface is functioning properly.

Configuring the HP Exstream Delivery Channels

After you have installed the HP Exstream Delivery Engine, you must configure the various delivery channels used
by the HP Exstream Delivery Engine. If the delivery channels are not configured, you cannot deliver documents
using the HP Exstream Delivery Engine.
 Software Requirements for Delivery Channels on page 42
 Configuring Delivery Channels Using the HP Exstream Delivery Engine WebGUI on page 42
Software Requirements for Delivery Channels

Depending on the delivery channels that you want to use in the HP Exstream Delivery Engine, you must install the
following software:
Delivery Channel software requirements

To use this
delivery channel You must have installed this software
SMPP Any gateway that supports SMPP protocol

CMIS Any CMIS-compliant content management system
JMS Any JMS provider (HP recommends ActiveMQ)
SMTP-SMS Any gateway that supports SMTP protocol
SMTP-Email Any exchange server that supports SMTP protocol
FTP/FTPS Any FTP server must be configured
SOAP/REST Web services must be configured, deployed, and running
ET_Email An ExactTarget account
Configuring Delivery Channels Using the HP Exstream Delivery Engine

WebGUI
After the HP Exstream Delivery Engine is installed, you can configure delivery channels using the HP Exstream
Delivery Engine WebGUI. The following table lists the relevant sections in the user guide to complete the tasks
associated with configuring delivery channels:
See this section of the HP Exstream

For this task
Delivery Engine User Guide
Logging in to the HP Exstream Delivery Engine WebGUI Logging in to HP Exstream Delivery Engine
WebGUI
Creating a destination and adding fields related to protocol Creating a Destination and the Fields
Creating a delivery channel Creating a Channel
Enabling Communication with the HP Exstream Delivery Engine

After creating destinations and delivery channels, you must enable communication between the HP Exstream Delivery
Engine, HP Exstream Fulfillment Delivery Services (FDS), and HP Exstream Command Center by configuring the
callback URL.


 Configuring the Callback URL for the HP Exstream Command Center on page 43
 Configuring the Callback URL for the HP Exstream Fulfillment Delivery Service on page 43
Configuring the Callback URL for the HP Exstream Command Center

The HP Exstream Delivery Engine uses a callback URL to send the status of the delivery jobs to HP Exstream
Command Center. The delivery status is sent through a simple HTTP post. The callback URL must point to the
HTTP listener on HP Exstream Command Center.
You must configure a callback URL, using the HP Exstream Delivery Engine Administration WebGUI.
For more information, see Configuring the Callback URL for HP Exstream Command Center section of the
HP Exstream Delivery Manager User Guide.
Configuring the Callback URL for the HP Exstream Fulfillment Delivery

Service
The HP Exstream Delivery Engine uses the FDS_callback URL to send job delivery report notifications to the
HP Exstream Fulfillment Delivery Service (FDS). The FDS_callback URL contains the necessary information
required to communicate with the FDS service.
You must configure the FDS_callback URL using the HP Exstream Delivery Engine Administration WebGUI.
For more information, see Configuring the FDS_Callback URL section of the HP Exstream Delivery Manager
User Guide.
HP Exstream Delivery Engine 1.2.0 Migration

You can migrate the database for the HP Exstream Delivery Engine from version 1.1.2 to version 1.2.0 only if
there was not a database schema update since the original installation of 1.1.2.
 Preparing for Migration on page 43
 Migrating HP Exstream Delivery Engine Databases on page 44
Preparing for Migration

1. Stop and exit the previous version of HP Exstream Delivery Engine
2. Install HP Exstream Delivery Engine 1.2.0.
For more information about installing HP Exstream Delivery Engine, see Installing the HP Exstream Delivery
Engine on page 37.
3. Set up the database drivers required for HP Exstream Delivery Engine 1.2.0.
For more information about setting up database drivers, see Creating Databases for HP Exstream Delivery
Manager Components on page 14.

4. Update the HP Exstream Delivery Engine configuration for the HP Exstream Delivery Engine 1.2.0 installation
(such as setting up the database connection). In most cases, you can update configuration according to the
settings that were used in the previous installation.
For more information about HP Exstream Delivery Engine configuration settings, see HP Exstream Delivery
Engine Configuration on page 76.
5. Run the database migration.
For more information about migrating HP Exstream Delivery Engine databases, see Migrating HP Exstream
Delivery Engine Databases on page 44.
6. Start the latest version of HP Exstream Delivery Engine.
Migrating HP Exstream Delivery Engine Databases

After the HP Exstream Delivery Engine is installed, the migration scripts are located in the <cc_root>/
database-setup/migration directory. Scripts are titled by product, database, source version, and target
version (for example, de_oracle_1.1.2_to_1.2.0.sql).
To migrate a HP Exstream Delivery Engine database:
1. Back up the database that you want to migrate by copying the delivery-engine-1.2.0/database-
setup/lib directory to a backup location.
2. Go to the delivery-engine-1.2.0/database-setup/bin directory for the new HP Exstream Delivery
Engine installation.
3. Depending on your operating system, execute one of the following migration scripts:
Windows dm-sqlexecutor.bat
UNIX/Linux dm-sqlexecutor.sh
4. Depending on your operating system, use the following syntax with the migration script:
Operating
Syntax
system
Windows dm-sqlexecutor.bat -d <oracle/mssql/mssqlsrv/db2/mysql/hsqldb>

-u <username>
-p <password>
UNIX/Linux dm-sqlexecutor.sh -d <oracle/mssql/mssqlsrv/db2/mysql/hsqldb>
-u <username>
-p <password>
Keep in mind that the database connection string is the JDBC connection URL for your database.

Migration script example:

dm-sqlexecutor.bat -d oracle -l jdbc:oracle:thin:@localhost:1521/XE -u deadmin -p
deadmin -s ../migration/de_oracle_1.1.2_to_1.2.0.sql
When the migration script completes, you receive a message that provides the number of successfully executed
queries.

Installing and Deploying HP Exstream Fulfillment Delivery Service
Installing and Deploying HP Exstream Fulfill-

ment Delivery Service

 HP Exstream Fulfillment Delivery Service Package File Contents on page 46
 Installing and Deploying HP Exstream Fulfillment Delivery Service on page 46
HP Exstream Fulfillment Delivery Service Package File Contents

The fulfillment-delivery-service-1.2.0 package file contains the following content:
HP Exstream Delivery Engine package contents

the HP Exstream Delivery Description
Engine package
client/ directory This directory contains an example client to call FDS.

conf/ directory This directory contains all configuration files for FDS
(lclj.properties, fds-security.xml)
database-setup/ directory Utility and SQL scripts to initialize database
realtime-util/ directory Utility to start realtime engine pool
HP Exstream Fulfillment Delivery —
Service application WAR

HP Exstream Fulfillment Delivery Service can be deployed using the following Web/application servers:
 Apache Tomcat
 IBM WebSphere
 Oracle WebLogic
To install and deploy HP Exstream Fulfillment Delivery Service:

1. Unzip the Delivery_Manager_1_2_0.zip file.
For more information about creating a database for use with HP Exstream Delivery Manager components,
see Creating Databases for HP Exstream Delivery Manager Components on page 14.

3. If you are deploying the application to Weblogic, make sure that the <Weblogic domain>/conf directory is
in classpath. If the directory is not in the classpath, do one of the following to add the directory:
For this Platform Do this
Windows 1. Open the following file:

setDomainEnv.bat
set CLASSPATH=%CLASSPATH%;%DOMAIN_HOME%\conf
UNIX 1. Open the following file:
<Weblogic domain>/bin/setDomainEnv.sh
export CLASSPATH=$CLASSPATH:$DOMAIN_HOME/conf
4. Copy the configuration files from the conf/ directory to the <Weblogic domain>/conf directory. If the
<Weblogic domain>/conf directory does not exist, you must create it.
5. Use the Configuration Console to update any configuration settings that are required for HP Exstream Fulfillment
Delivery Service.
For more information about HP Exstream Fulfillment Delivery Service configuration settings, see HP Exstream
Fulfillment Delivery Service Configuration on page 80.
6. Deploy the fulfillment-delivery-service.war file.

HP Exstream Delivery Manager Configuration Console
HP Exstream Delivery Manager Configuration

Console
HP Exstream Delivery Manager Configuration Console (DMCC) is a Web application for managing the
HP Exstream Delivery Manager settings. You can use the HP Exstream Delivery Manager Configuration Console
to do the following:
 Configure all HP Exstream Command Center, HP Exstream Delivery Engine, and HP Exstream Fulfillment
Delivery Service settings using a single interface.
 Share the common settings across all HP Exstream Delivery Manager features.
 Save the properties of HP Exstream Command Center, HP Exstream Delivery Engine, and HP Exstream
Fulfillment Delivery Service.
 Import/export property files when the HP Exstream Delivery Manager Configuration Console runs on a remote
server and retain the same settings for different installations.
 Configure the connection parameters to the existing databases for each HP Exstream Delivery Manager
component.
The HP Exstream Delivery Manager Configuration Console main window contains the configuration settings
for each of the three HP Exstream Delivery Manager components (HP Exstream Command Center, HP Exstream
Delivery Engine, and HP Exstream Fulfillment Delivery Service).
Required configuration settings appear with an asterisk (*) in the console.
 Installing the HP Exstream Delivery Manager Configuration Console on page 48
 Deploying the HP Exstream Delivery Manager Configuration Console on page 49
 Managing Configuration Settings in the Configuration Console on page 49
 HP Exstream Command Center Configuration on page 50
 HP Exstream Delivery Engine Configuration on page 76
 HP Exstream Fulfillment Delivery Service Configuration on page 80
Installing the HP Exstream Delivery Manager Configuration

Console
The HP Exstream Delivery Manager Configuration Console is distributed as a WAR file and should be
deployable to any application server supported by HP Exstream Delivery Manager.

The license file must be available in the classpath of the application server. The name of the license file must use
the .license file extension. The classpath for the licence file can be found at the following locations in the
application server:
License file locations for each application server

For this
The licence file is at the following location
Application Server
Apache Tomcat {tomcat_home}/lib/dm.license

JBoss {jboss_home}/server/{jboss_server_name}/conf/dm.license
WebLogic {wls_domain_root}/dm.license
IBM WebSphere {was_home}/profiles/{profile_name}/properties/dm.license
NOTE: You do not need to restart the application server after replacing/renaming the license file;
however, you must restart the HP Exstream Delivery Manager Configuration Console.
Deploying the HP Exstream Delivery Manager Configuration

Console
To deploy the HP Exstream Delivery Manager Configuration Console, deploy the dmc-webgui.war file. By
default, the WAR file is at the following location:
<CC_ROOT>/lib/bundles/cc directory)
Managing Configuration Settings in the Configuration Console

As you work in the HP Exstream Delivery Manager Configuration Console, keep in mind that the configuration
settings are stored in the following properties files:
Component Properties File Name(s)
HP Exstream Command • server.properties

Center • platform.properties
• data-channels.properties
HP Exstream Delivery Engine deglobal.properties
HP Exstream Fulfillment lclj.properties
Delivery Service

To manage the configuration settings that you apply in the Configuration Console, you can complete any of the
following tasks:
To Do this
Import existing Configuration 1. From the Configuration Console, click Import.

Console settings from a The Choose File to Upload dialog box opens.
specific properties file 2. Go to the configuration file that you want to import and click Open.
The properties file that you import must have the .properties file
extension. If you want to import settings that are stored in different
files, then you must import each file separately.
The configuration settings are imported into the Configuration Console.
Export Configuration From the Configuration Console menu, select Other Options >
Console settings Export.
Save the configuration 1. From the Configuration Console, click Save.
settings for only the The Select a directory to save the property file(s) dialog box
component that is currently opens.
open
2. From the Select a directory to save the property file(s)
dialog box, select the directory where you want to save the configuration
settings.
3. Click OK.
The single properties file is saved to the directory you specified.
Save all configuration 1. From the Configuration Console, click Other Options > Save All.
settings in the Configuration The Select a directory to save the property file(s) dialog box
Console opens.
2. From the Select a directory to save the property file(s)
dialog box, select the directory where you want to save the configuration
settings.
3. Click OK.
All of the configuration files are saved to the directory you specified.
Restore all settings to the From the Configuration Console, select Other Options > Restore
original default settings Defaults.
Keep in mind that you cannot recover previous settings after you have
restored the default Configuration Console settings.
Apply any Configuration In order to complete and apply any changes you make in the Configu-
Console changes to active ration Console, you must restart any affected deployments.
deployments
HP Exstream Command Center Configuration

HP Exstream Delivery Manager Configuration Console checks the license file from classpath and enables the
components based on key content. For example, if the client has the license only for HP Exstream Command
Center, the HP Exstream Delivery Manager Configuration Console will allow user to edit properties only under
HP Exstream Command Center category.
This section discusses the following configuration options:
 License on page 51
 Database Configuration on page 52
 Engine on page 55

 Engine Pool Management on page 56

 Connector on page 56
 Delivery Report Configuration on page 60
 JMS CallBack Module on page 60
 Action Handler Configuration on page 60
 Cluster on page 61
 Data Channel - General on page 64
 Data Channel - Watch Folder on page 64
 LPR/LPD Delivery Configuration on page 64
 Internal on page 65
 Java Content Repository (JCR) on page 65
 Job Management on page 66
 File Provider on page 68
 JMS Provider on page 69
 RMI Provider on page 70
 General Logging on page 70
 Job Logging on page 71
 Schedule Entity Logging on page 71
 Engine Pool Logging on page 72
 Engine Pool Slot Logging on page 72
 Cluster Logging on page 73
 Configuring the HP Exstream Command Center Data Channels on page 73
 Configuring the HP Exstream Command Center Platform on page 74
License
You can configure the following option for the Licence area of the HP Exstream Command Center properties:
Property Name in Use

Properties File
File license.file Enter the location of the file from which the license key is
read. You can use relative locations if needed. For
example, the following is the default file location for the
license:
../conf/demo-license
the .license file. The classpath for the licence file can be found at the following locations in the application
server:

For this The licence file is at the following location
Application Server



For this
The licence file is at the following location
Application Server
Database Configuration
Before you apply database configuration settings, be sure that you have met all the database requirements for
HP Exstream Delivery Manager.
For more information about creating databases for use with HP Exstream Delivery Manager, see Creating
Databases for HP Exstream Delivery Manager Components on page 14.
You can configure the following options for the Database Configuration area of the HP Exstream Command
Center properties:
Name in
Property Use
Properties File
Select supported database.type Specifies the type of database you want to use to configure
database HP Exstream Command Center.
By default, HP Exstream Command Center is configured
to use the embedded SQL database (HSQLDB) that is
included in the distribution.If you need support for an
additional SQL database, contact HP support. The data
storage layer of HP Exstream Command Center is
generic and can be adapted for most RDBMS systems.
Advanced users can override the JDBC driver class and
hibernate dialect using properties database.driver
and hibernate.dialect respectively.
Database Server Specifies the hostname of the server where the database
Hostname is located.
Database Server Specifies the port number of the database server located
Port under the host.
Database Name Specifies the name of the database that you want to
connect with HP Exstream Command Center.
Username database.userna Specifies the user name of the user who is allowed to
me access the database. The default value is sa.
For more information about users, see your database

manual.
Password database.passwo Specifies the password required by the user defined in
rd the Username box. This password will be used by
HP Exstream Command Center when the user logs into the
database.
For more information about passwords, see your

database manual.

Name in
Property Use
Properties File
URL database.url Represents the JDBC connection URL used by

HP Exstream Command Center Server to connect to an
SQL database.

Examples of Database Configuration Based on Database Type
Database Type Explanation
HSQLDB (Default) Example of HSQLDB Server Configuration

Select supported database - hsqldb
username = <username>
password = <password>
URL - jdbc:hsqldb:file:db/<database_name>
MSSQL Server The jTDS JDBC driver[4] is bundled with the HP Exstream Command
Center distribution, you do not have to add any specific JAR files to the
classpath.
If you want to use the domain username or password for connecting to
database, you must append the domain=<DomainName> parameter to
the database.url with the name of the domain.
Example of Microsoft SQL Server Configuration (use jTDS JDBC
driver)
database.type = mssql
database.url = jdbc:jtds:sqlserver://
<hostname>or<IPAddress>[:<port>]/
<DBNAME>[;<instance=sqlexpress>]
database.username = <username>
database.password = <passwd>
Make sure the MSSQL database user you define for
HP Exstream Command Center is assigned all available roles in the
database.
MySQL Specific Notes You must download the JDBC driver for MySQL (Connector/J) from the
MySQL Web site[6]. Only version 5.x of MySQL is supported.
The value of the database.url should be in the form jdbc:mysql:/
/<server>[:<port>]/<database>.
Example of MySQL configuration
database.type = mysql
database.url = jdbc:mysql://
<database_hostname>:<db_portnumber>/<database_name>
database.password = <password>
Oracle 10g/11g R2 Specific Example of Oracle 10g/11g R2 Server Configuration
Notes
database.type = oracle
database.url = jdbc:oracle:thin:@//
<database_hostname>or<database_host_ip>:<listner_por
t>/<service_name>

Database Type Explanation
IBM DB2 The DB2 distribution contains the DB2 JDBC connector driver[5]
contained in the db2jcc.jar and db2jcc_license_cu.jar files.
Example of IBM DB2 Configuration
database.type = db2
database.url = jdbc:db2://
<database_hostname>or<database_host_ip>:<db_portnumb
er>/<database_name>
The HP Exstream Command Center database should contain table space
of least 16 KB, otherwise some tables may not be created properly.
Engine
You can configure the following options for the Engine area of the HP Exstream Command Center properties:

Properties File
Executable engine.executab Specifies the path to the HP Exstream Production Engine
le executable. The default value is (relative to your
installation directory) is ../../<HP Exstream-
engineinstall>/Engine.
Key engine.key Specifies the HP Exstream Engine license key which
overrides the key in the HP Exstream application
packages.
This switch is used to apply a specific key to an Engine
run. For instance, you can use it when you need an
expired key to run package files with a prior date.
When non-empty, the property generates
-KEY=<value> switch to the engine control file. The
default is empty.

Engine Pool Management

You can configure the following options for the Engine Pool Management area of the HP Exstream
Command Center properties:

Properties File
Enabled poolmng.enabled Enables or disable engine pool management.

Acceptable values are true and false. The pool
management is enabled by default. The default value is
true.
If pool management is disabled, then a client connected
through WebGUI cannot see the engine pool
management control.
Dir poolmng.dir Specifies the path to the pool management root directory
(relative to the root directory of HP Exstream Command
Center). A specific sub-directory for each engine pool is
created in this directory to store logs, message files, and
all other pool-specific resources.
Example: engine pool management
poolmng.enabled = true
poolmng.dir = var/pools
poolmng.fileview.urlprefix= http://
localhost:8081/pools
File-view URL poolmng.filevie http://localhost:8081/pools
Prefix w.urlprefix
Connector
You can configure the following options for the Connector area of the HP Exstream Command Center
properties:
Name in the
Property Use
Properties File
Java Enabler connector.def.n Specifies name of the library routine used by the
Function ative.java_enab HP Exstream Engine. This is a predefined connector: Java
ler.function Enabler with key java_enabler
Java Enabler connector.def.n Specifies path to the connector's library file. If it is not
Module ative.java_enab absolute, then it is relative to the path defined by
ler.module connector.dir.

Name in the
Property Properties File Use
Java Enabler connector.def.n Specifies connectors compiled for the target platform.
Name ative.java_enab
The properties start with connector.def.native.
ler.name
The following predefined connectors are available:
WebSphere MQ Connector with key websphere_mq
Do not change the keys. The connections wizards in
WebGUI rely on them.
The native connector must have the following additional
attributes defined:
Name: This attribute defines the name of the connector.
Module: This attribute defines the path to the connector's
library file. If it is not absolute, then it is relative to the
path defined by connector.dir.
Function: This attribute defines the name of the library
routine used by HP Exstream Production Engine.
Websphere MQ connector.def.n Specifies the name of the Websphere MQ library routine
Function ative.websphere used by HP Exstream Engine. The default value is
_mq.function processRec.
Websphere MQ connector.def.n Specifies the path to the Websphere MQ connector's
Module ative.websphere library file. If it is not absolute, then it is relative to the
_mq.module path defined by "connector.dir" For example,
MQ/ExMQConnect.dll
Websphere MQ connector.def.n Specifies the path name of the connector.
Name ative.websphere
The default value is WebSphere MQ Connector. For
_mq.name
example, WebSphere MQ Connector
Dir connector.dir Specifies the path to the directory containing connectors
libraries (for example, the DLL for WebSphere MQ
Connector or the jar file for JMS Connector). For
example, var/connectors.
HP Exstream Delivery Engine Configuration

HP Exstream Delivery Engine configuration setup is required for the communication between HP Exstream
Command Center and HP Exstream Delivery Engine.
You can configure the following options for the Delivery Engine Configuration area of the HP Exstream
Property Name in the Description

Properties File
Interface de.interface Defines Communication protocol between HP Exstream

Command Center and HP Exstream Delivery Engine. The
options available are—HTTP and JMS.

HP Exstream Delivery Engine Configuration for HTTP Interface

Command Center properties if you use the HTTP interface:
Name in the
Properties File
Connection Pool de.connection.p Specifies the pool size of HP Exstream Delivery Engine.
Size ool.size By default, it is set to 5.
HTTP Interface de.httpinterfac Specifies the URL of the HTTP interface servlet in
Url e.url HP Exstream Delivery Engine for remote or local
connections.
To configure a HP Exstream Delivery Engine instance, the
default HTTP URL property should be:
• de.httpinterface.url
It only available value is string.
Report Chunks de.reportchunks Number of the customers extracted from the
Size .size ReportFile.xml for processing in one cycle.
Example: HP Exstream Delivery Engine HTTP configuration

de.httpinterface.url=http://localhost:8080/de-distribution/DEHttpProvider
de.httpinterface.url.1=http://localhost:8081/de-distribution/DEHttpProvider
de.httpinterface.url.2=http://localhost:8082/de-distribution/DEHttpProvider
de.httpinterface.url.3=http://localhost:nn/de-distribution/DEHttpProvider
de.reportchunks.size=2
de.interface=jms

HP Exstream Delivery Engine Configuration for JMS Interface

Command Center properties if you use the JMS interface:
Name in the
Properties File
JMS Provider Url de.jms.provider Specifies the JMS provider URL that HP Exstream
.url Command Center posts JMS messages to HP Exstream
Delivery Engine.
Select the following related property check boxes to
retain the same value under corresponding category:
• Provider URL under Delivery Engine/JMS
Settings
• JMS Provider URL under Fulfillment Delivery
Service/FDS EWS & Realtime Configuration
JMS Context de.jms.contextf Specifies the JMS Initial Context Factory class.
Factory acotry
• Initial Context Factory under Delivery
Engine/JMS Settings
JMS Queue de.jms.queue.fa Displays the name of the JMS Queue Factory. This
Factory ctory information is used by HP Exstream Command Center to
connect with JMS destinations.
• Connection Factory under Delivery Engine/
JMS Settings
JMS Consumer de.jms.consumer Specifies the name of the JMS Queue. HP Exstream
Queue .queue Delivery Engine posts messages to this queue.
Select the following related property check box to retain
the same value under corresponding category:
• Output Queue under Delivery Engine/JMS
Settings
JMS Producer de.jms.producer Specifies the name of the JMS Queue. HP Exstream
Queue .queue Command Center posts messages to this queue and
HP Exstream Delivery Engine receives them.
Select the following related property check box to retain
the same value under corresponding category:
• Input Queue under Delivery Engine/JMS
Settings

Delivery Report Configuration

You can configure the following options for the Delivery Report Configuration area of the HP Exstream
Name in
Property Use
Properties File
CC HTTP Location report.cc.http. Specifies the file path where the Delivery Reports is stored.
location This path should be <install_dir>/var/delivery-
reports, where install_dir represents the <HP
Exstream Command Center>/<Web server>
home directory (depending on where HP Exstream
Command Center WebGUI is deployed), and var/
delivery-reports represents the default property in
jobmng.reports.dir configuration.
CC Location report.cc.locat Specifies the file location where the HP Exstream
ion Command Center picks up the delivery reports that are
transferred from the HP Exstream Delivery Engine.
DE Location report.de.locat Specifies the file location to which the HP Exstream
ion Delivery Engine places the delivery reports.
JMS CallBack Module

The following properties are configured for JMS CallBack Module. These are applicable Applicable when
HP Exstream Delivery Engine posts the callback for ASYNC Assured Delivery Jobs through JMS channel. It is
advised to have a Single JMS instance for provider as well as callback, in which case the configuration
properties would be similar to the provider properties listed below. You should have a Single JMS instance for
provider as well as callback.
You can configure the following options for the JMS CallBack Module area of the HP Exstream Command
Center properties:
Name in
Properties Description
Properties File
JMS Callback de.jms.callback Indicates whether the JMS callback listener in

Enabled .enabled HP Exstream Command Center is active.
JMS Callback de.jms.callback Specifies the URL on which the callback listener listens on
Provider Url .provider.url and respond to.
JMS Callback de.jms.callback Specified the fully-qualified name of the Factory class
Context Factory .contextfactory that will be used to create an initial context which
contains ConnectionFactory instances
JMS Callback de.jms.callback Specifies name of the JMS connection factory.
Queue Factory .queue.factory
JMS Callback de.jms.callback Specifies queue name in which HP Exstream Command
Queue .queue Center would listen for callback messages.
Action Handler Configuration

Action handler configuration properties are used based on the concurrent request or load received from
HP Exstream Command Center.

You can configure the following options for the Action Handler Configuration area of the HP Exstream
Name in
Property Use
Properties File
Min Threadpool actionhandler.m Specifies the minimum size of the Action Handler Thread
in.threadpool Pool. Configure this property based on the concurrent
request or load received from HP Exstream Command
Center. The default value is
actionhandler.min.threadpool=10
Max Threadpool actionhandler.m Specifies the maximum size of the Action Handler Thread
ax.threadpool Pool. Configure this property based on the concurrent
actionhandler.max.threadpool=30
Queue Size actionhandler.q Specifies the queue size of the Action Handler Thread
ueue.size Pool. Configure this property based on the concurrent
actionhandler.queue.size=60
Cluster
Clustering is not enabled by default. If you want to use clustering, you must enable the HP Exstream Command
Center Cluster option.
The following cluster configurations are available:
 Failover scenario managed by HP Exstream Command Center
 Failover scenario not managed by HP Exstream Command Center (managed by an external cluster environment)
NOTE: The userid/username and groupid/groupname in all mounted servers must be the same
when HP Exstream Command Center is installed in a cluster setup for load balancing by a
non-root user.
You can configure the following options for the Cluster area of the HP Exstream Command Center properties:
Name in
Property Use
Properties File
Enabled cluster.enabled By default clustering is not enabled. There are two

available values. if you want to run HP Exstream
Command Center in a clustered environment, set this
property to true.
Failback cluster.failbac Applies only when cluster.failover.enabled is true. To
k avoid failback set this parameter to true.
For example, the following default settings for configuration
of failover are managed by HP Exstream Command
Center:
cluster.failover.enabled = true
cluster.failback = true


Properties File
Failover Enabled cluster.failove Enables HP Exstream Command Center servers in a

r.enabled cluster to detect the failure of an active server and
automatically perform a failover by getting a passive
node in the cluster to run in the active mode. The default
value is true.
The following cluster configurations are available:
• If you want HP Exstream Command Center to manage
failover in the cluster, set the value to true.
• If you want to use an external Cluster Management
software to manage failover, set the value to false.
Fileview URL cluster.filevie The files in the cluster node directories can be viewed
Prefix w.urlprefix from HP Exstream Command Center WebGUI. By
default, this property points to http://
localhost:8081/cluster.
Name cluster.name Enter a name for the cluster of HP Exstream Command
Center Servers. The default name is cc-cluster.
Cluster names must be unique if multiple clusters are
configured in the same network. This is used only when
the property cluster.enabled is set to true.

Name in
Property Use
Properties File
Node Load- cluster.node.lo Specify the number of tasks a node can run concurrently.
Capacity Default ad- For example, if a cluster node has a load capacity value
capacity.defaul of 10, the node can process 10 tasks concurrently. If
t another task is routed to that node, the eleventh task
waits in the queue for a task to complete. The load
capacity range is between 0 and 100000000. The
default value for load capacity is 2.
For example, the following settings are configurable for
HP Exstream Command Center in a clustered
environment.
cluster.enabled true
cluster.name cc-cluster
cluster.nodestore.dir var/nodes
cluster.fileview.urlprefix http://
localhost:8081/cluster
cluster.default.load_capacity 2
An administrator can set a different default value for the
cluster.default.load_capacity, property, in the
server.properties file.
In the WebGUI while creating a node, a user can also
set a different load capacity value by entering the value
in the Load Capacity field. If a value is not entered
while creating a node, the default value set by the
administrator in the server.properties file, is used
by the new node.
Nodestore Dir cluster.nodesto This parameter defines the path to the root directory for
re.dir cluster nodes. The default path is var/nodes. The log
files and any of the runtime files specific to a node are
available in the corresponding subdirectory.
You can export the server.properties file and manually configure failover parameters in the file to enable
the cluster and failover scenario managed by HP Exstream Command Center.
The general cluster properties and failover properties must be configured based-on your cluster setup.
To start a HP Exstream Command Center cluster in active mode, go to the bin directory of the installation folder
in the command prompt and execute the following command:
command-center.bat active

Data Channel - General

You can configure the following options for the Data Channel - General area of the HP Exstream Command
Center properties:
Name in the
Property Use
Properties File
Repository Path de.repository.p Specifies the path to the directory for Data Channel file
ath operations
RMI Registry Port datachannel.rmi Specifies the port number on which the second RMI
.registry.port registry for Data Channel is running. The default is
2000.
RMI Registry datachannel.rmi Specifies the time-out (milliseconds) for communication
Timeout .registry.timeo with HP Exstream Command Center. The default is
ut 60000.
RMI Registry datachannel.rmi Specifies the time-out (milliseconds) for send document
Document .registry.sendd requests. The default is 300000.
Sending Timeout ocument.timeout
Data Channel - Watch Folder

You can configure the following options for the Data Channel - Watch Folder area of the HP Exstream
Name in the
Property Use
Properties File
Input Folder datachannel.wat Specifies the path to the directory where Watch Folder
chfolder.input service listens for Data Channel requests.
Output Folder datachannel.wat Specifies the path to the directory where the response is
chfolder.output written in the form of a composed document
Error Folder datachannel.wat Specifies the path to the location where you want to
chfolder.error generate an error response if an error occurs. Error
reports are generated in XML format.
LPR/LPD Delivery Configuration

The system deliveries supported are LPR/LPD, FTP, JMS, JCR, and file system. If you need a special delivery sub-
system, contact HP for more information.

You can configure the following options for the LPR/LPD Delivery Configuration area of the HP Exstream
Name in the
Property Explanation
Properties File
Socket Timeout delivery.lpr.so The socket timeout of the TCP/IP connection while
cket_timeout communicating with LPR/LPD server is expressed in
milliseconds. Zero is interpreted as an infinite timeout.
The default value is 10,000.
Use RFC 1179 delivery.lpr.us Due to RFC 1179, LPR clients should use TCP/IP ports in
Ports e_rfc1179_ports range 721 – 731 as source of the connection. However
TCP/IP requires that any port used will not be released
for three minutes. To avoid this situation, set
delivery.lpr.use_-rfc1179_-ports to true. To
be RFC-compliant, set it to false. The default value is
true.
Internal
HP strongly recommends not to change these properties until you are fully aware of the possible results/conse-
quences. The internal configuration properties directly impact the internal behavior of HP Exstream Command
Center. Making changes to these properties severely affects the expected behavior of HP Exstream Command
Center.
You can use these properties to configure multiple instances of HP Exstream Command Center Server on the
same machine, each instance must have a unique port for services.
You can configure the following options for the Internal area of the HP Exstream Command Center properties:
Name in the
Property Use
Properties File
Action Timeout internal.action Specifies the Action execution time-out in milliseconds.

.timeout Actions are small atomic units of work and must be
handled quickly. This time-out is a protective early
warning mechanism that indicates an issue. Do not
extend the time-out unless it is absolutely necessary. By
default, the value is set to 10000 milliseconds.
Job Creation internal.optimi Specifies the Optimization detail. Optimization can
Optimization zation.job.crea improve the performance of Job creation. The default
tion value is false. Turn it on only when you are not using
the bundling feature.
Java Content Repository (JCR)

This configuration is required for pulling the Report XML file from the JCR that has the failure customer details
after the HP Exstream Delivery Engine completes deliveries.

You can configure the following options for the Java Content Repository (JCR) area of the HP Exstream
Name in
Provider Use
Properties File
Repository Host jcr.repository. Specifies the IP Address on which the JCR is configured.
host
Repository Port jcr.repository. Specifies the port that is configured for the JCR.
port
Repository User jcr.repository. Specifies the name of the repository file that will be used
user by HP Exstream Command Center.
Repository jcr.repository. Specifies the password to access the repository file.
Password password
Repository RMI jcr.repository. Enables remote access to a JCR. It is compatible with all
Context rmi_context JCR implementations.
Job Management
Job management is responsible for a job life cycle. You can configure this based on the number of engines
running simultaneously and where the jobs and HP Exstream application packages are stored. All paths are
relative to the HP Exstream Command Center installation directory.
You can configure the following options for the Job Management area of the HP Exstream Command Center
properties:
Name in the
Property Use
Properties File
Jobstore Dir jobmng.jobstore Specifies the file system storage of jobs (for example,
.dir their output, logs, and so on). The default value is var/
jobs.
Jobstore Fileview jobmng.jobstore Defines how the jobstore directory is exported (for
URL Prefix .fileview.urlpr example, files in job directories can be viewed from
efix WebGUI). By default, this property is set to http://
localhost:port/jobstore, where the embedded
File View servlet (extension of HP Exstream Command
Center WebGUI) is running in most cases (for example,
when bundle distribution is used). If your jobstore
directory is exported using an external Web server, set
this property to
https://yourserver.yourdomain.com:8081/
jobstore.

Name in the
Property Use
Properties File
Packages jobmng.packages Specifies the directory where HP Exstream application

Archive Dir .archive.dir packages are archived. The default value is var/
archive.
Sample job management configuration
jobmng.jobdriver.count = 2
jobmng.jobstore.dir = var/jobs
jobmng.packages.dir = var/packages
jobmng.packages.archive.dir = var/archive
In the example, you can see a configuration with up to
five engines running in parallel.
Jobs are stored in /storage/jobstore and
HP Exstream application packages are taken from /
storage/packages directory.
Packages Dir jobmng.packages Specifies the directory where HP Exstream application
.dir packages are stored. The default value is var/
packages.
Reports Dir jobmng.reports. Path to directory where the delivery reports are stored
dir
Reports Fileview jobmng.reports. Defines how the reports directory exported (for example,
URL Prefix fileview.urlpre files in reports directory can be viewed from WebGUI).
fix By default, this property points to
http:\\localhost:8081\delivery-reports

Name in the
Property Use
Properties File
Jobdriver jobmng.jobdrive Specifies the count of job-drivers that accept jobs with
Priority r.priority.X.co the specified or higher priority (the number between
unt “priority” and “count”). Job drivers can be specified for
priorities from 1 to 10, where 10 is the highest. If you do
not need to prioritize jobs execution, fill the count of job
drivers only for the lowest priority.
If you need prioritization, specify the count for higher
priorities—this guarantees that not all job drivers will be
taken by lower-priority jobs, but some will be reserved
only for higher-priority jobs.
The number of job drivers indicate the number of
HP Exstream Production Engine instances that are
running in parallel.
Set this value carefully. It should reflect the hardware
capabilities of the target machine.
jobmng.jobstore.dir = var/jobs
jobmng.reports.dir = var/delivery-
reports
jobmng.reports.fileview.urlprefix=
http://<hostname>:<port>/delivery-
reports
jobmng.jobstore.fileview.urlprefix=
http://<hostname>:<port>/jobstore
jobmng.packages.dir = var/packages
jobmng.packages.archive.dir= var/
archive
jobmng.jobdriver.priority.1.count = 20
File Provider
A file provider provides an alternate way to access HP Exstream Command Center Server in addition to
WebGUI. It is a watched directory in the file system that is scanned at predefined intervals.

You can configure the following options for the File Provider area of the HP Exstream Command Center
properties:
Name in the
File Provider provider.file.e Specifies whether the file provider is enabled or

Enabled nabled disabled. There are two available values true and
false. The default value is false. To enable file
provider, set the value to true.
File Provider provider.file.c Specifies a directory so that, if you make a syntax error
Corrupt Dir orrupt.dir in an XML action, the file will be moved here, so you can
fix the error and move the action file back to
provider.file.input.-dir.
The default (relative to your installation directory) value is
file_corrupt.
File Provider provider.file.i Specifies the directory accessible in a file system that will
Input Dir nput.dir be scanned for the XML actions. The default (relative to
your installation directory) value is file_input.
File Provider provider.file.i Specifies the time interval in milliseconds and states how
Interval nterval often provider.file.input.dir is scanned for new
actions. The default is 2000.
File Provider provider.file.c Specifies the interval in milliseconds after which a file
Corrupt Interval orrupt.interval copied to provider.file.input.dir can be
considered corrupt, in case it is invalid. Default value is
5000.
File Provider provider.file.r Specifies the directory accessible in the file system where
Response Dir esponse.dir responses to XML actions will be placed. The default
(relative to your installation directory) is
file_response.
For more information about XML actions, see the HP Exstream HP Exstream Command Center Developer’s
Guide.
JMS Provider
The JMS provider helps the clients or services to leverage the JMS functionality of HP Exstream Command
Center.
You can configure the following options for the JMS Provider area of the HP Exstream Command Center
properties:

Properties File
JMS Provider provider.jms.en Enable or disable the JMS action provider. It accepts the
Enabled abled following values: true or false.
JMS Provider provider.jms.qu JNDI name of the JMS queue where the output composed
Queue Docq eue.docq documents are delivered from the dc.

Name in
JMS Provider provider.jms.qu JNDI name of the JMS queue where Data Channels JMS
Queue Ibq eue.ibq provider listens for incoming messages.
JMS Provider provider.jms.qu JNDI name of the JMS queue where messages carrying
Queue Obq eue.obq datachannels\' responses are sent after executing
the request message.
RMI Provider
The RMI Provider provides an interface to execute actions via programmable interface. You can use this provider
to write your own clients. WebGUI uses this mechanism to communicate with HP Exstream Command Center
Server.
You can configure the following options for the RMI Provider area of the HP Exstream Command Center
properties:
Name in the
Property Use
Properties File
RMI Provider provider.rmi.en Enables the RMI provider to be enabled or disabled. The
Enabled abled allowed values: true or false. The default value is true.
RMI Provider provider.rmi.po Allows the port of the RMI registry to be used by the RMI
Port rt provider. RMI provider first tries to connect to this port on
the localhost and verify that a functional RMI registry
listens there. If it fails, it tries to create an RMI registry
that listens on this port.
The RMI provider must create its own registry in most
cases so a safe configuration is to leave the non-standard
port 1199[8] here or use some other free TCP/IP port.
The default value is 1199.
RMI SSL Enabled provider.rmi.ss Enables a secured RMI action provider.
l.enabled
General Logging
You can configure the following options for the General Logging area of the HP Exstream Command Center
properties:
Name in the
Property Use
Properties File
Common logging.common. Specifies the common directory used by Schedule
directory dir logging.

Job Logging
You can configure the following options for the Job Logging area of the HP Exstream Command Center
properties:
Name in the
Property Use
Properties File
Job Log Level logging.job.level Specifies log levels: ALL, DEBUG, INFO, WARN, ERROR,
FATAL, OFF.
Job History logging.job.history.fi Specifies the name of a history file that will be located in
Filename lename job folder for each job.
Job History logging.job.history.l Specifies the History entry layout.
Layout ayout
Job Log Enabled logging.job.log.enab Specifies whether you can create a log file.
led
Job Log Filename logging.job.log.filen Specifies the name of the log file that will be located in
ame job folder for each job.
Job Log Layout logging.job.log.layo Specifies log entry layout.
ut
Schedule Entity Logging

You can configure the following options for the Schedule Entity Logging area of the HP Exstream Command
Center properties:
Name in the
Property Use
Properties File
Sch Log Level logging.sch.lev Specifies log levels: ALL, DEBUG, INFO, WARN, ERROR,
el FATAL, OFF.
Sch Dirname logging.sch.dir Specifies the name of a directory relative to logs, where
name history and log files will be created for all schedule
instances.
Sch History logging.sch.his Specifies whether you can create a history file.
Enabled tory.enabled
Sch History logging.sch.his Specifies the history entry layout.
Layout tory.layout
Sch Log Enabled logging.sch.log Specifies whether you can create a log file.
.enabled
Sch Log Layout logging.sch.log Specifies the log entry layout.
.layout

Engine Pool Logging

You can configure the following options for the Engine Pool Logging area of the HP Exstream Command
Center properties:
Name in the
Property Use
Properties File
Pool Log Level logging.pool.le Specifies log levels: ALL, DEBUG, INFO, WARN, ERROR,
vel FATAL, OFF.
Pool History logging.pool.hi Specifies the name of history file (which is located in
Filename story.filename pool folder).
Pool History logging.pool.hi Specifies the history entry layout.
Layout story.layout
Pool Log Enabled logging.pool.lo Specifies whether you can create a log file.
g.enabled
Pool Log logging.pool.lo Specifies the name of log file (located in the job folder
Filename g.filename for each job).
Pool Log Layout logging.pool.lo Specifies the log entry layout.
g.layout
Engine Pool Slot Logging

You can configure the following options for the Engine Pool Slot Logging area of the HP Exstream Command
Center properties:
Name in the
Property Use
Properties File
Pool Slot Log logging.pool.sl Specifies log levels: ALL, DEBUG, INFO, WARN, ERROR,
Level ot.level FATAL, OFF.
Pool Slot History logging.pool.sl Specifies the name of history file (which is located in slot
Filename ot.history.file folder).
name
Pool Slot History logging.pool.sl Specifies the history entry layout.
Layout ot.history.layo
ut
Pool Slot Log logging.pool.sl Specifies whether you can create a log file.
Enabled ot.log.enabled
Pool Slot Log logging.pool.sl Specifies the name of log file (located in the job folder
Filename ot.log.filename for each job).
Pool Slot Log logging.pool.sl Specifies the log entry layout.
Layout ot.log.layout

Cluster Logging
You can configure the following options for the Cluster Logging area of the HP Exstream Command Center
properties:
Name in the
Property Use
Properties File
Cluster Log Level logging.cluster Specifies log levels: ALL, DEBUG, INFO, WARN, ERROR,
.level FATAL, OFF.
Cluster History logging.cluster Specifies the name of history file (which is located in slot
Filename .history.filena folder). For example, history.txt
me
Cluster History logging.cluster Specifies the history entry layout.
Layout .history.layout
Cluster Log logging.cluster Specifies whether you can create a log file.
Enabled .log.enabled
Cluster Log logging.cluster Specifies the name of log file (located in node-specific
Filename .log.filename folder).
Cluster Log logging.cluster Specifies the log entry layout.
Layout .log.layout
Configuring the HP Exstream Command Center Data Channels

The Data Channel Web Services interface enables the HP Exstream Command Center application to inter-
operate between various heterogeneous systems. The protocol used by Web Services to communicate internally
with HP Exstream Command Center is RMI.
 RMI Settings on page 73
 Watch Folder Settings on page 74
 JMS Settings on page 74
RMI Settings
You can configure the following options for the RMI Settings area of the HP Exstream Command Center Data
Channels properties:
Name in the
Property Use
Properties File
RMI Host RMI_HOSTNAME Specifies the IP address or host name of the machine
where HP Exstream Command Center is running.
RMI Port RMI_PORT Specifies the port on which the HP Exstream Command
Center RMI is listening.

Watch Folder Settings

You can configure the following options for the Watch Folder Settings area of the HP Exstream Command
Center Data Channels properties:
Name in the
Property Use
Properties File
Watch-Folder - WATCHFOLDER_INP Specifies the directory where the request files are placed.
Input Folder UT
Watch-Folder - WATCHFOLDER_OUT Specifies the directory where the response files are
Output Folder PUT generated.
Watch Folder - WATCHFOLDER_ERR Specifies the directory where the request files which
Error folder OR cause any error are placed.
JMS Settings
You can configure the following options for the JMS Settings area of the HP Exstream Command Center Data
Channels properties:
Name in the
Property Use
Properties File
Initialcontext JMS_initialCont Specifies the fully qualified name of the Factory class that
Factory Class ext_factory_cla will be used to create an initial context witch contains
ss ConnectionFactory instances.
Connection JMS_connection_ Specifies the name of the Factory class that encapsulates
Factory Name factory_name a set of connection configuration parameters.
Provider URL JMS_provider_ur Specifies the URL of the JMS provider's broker.
l
JMS_ibq JMS_ibq Specifies the JNDI JMS queue name for HP Exstream
Command Center requests.
JMS_obq JMS_obq Specifies the JNDI JMS queue name for HP Exstream
Command Center responses.
Configuring the HP Exstream Command Center Platform

 HTTP Settings on page 75
 HTTPS Settings on page 75
 TLS Encryption on page 75

HTTP Settings
You can configure the following options for the HTTP Settings area of the HP Exstream Command Center
Platform properties:
Name in the
Properties File
HTTP Enabled org.osgi.servic Enables HP Exstream Command Center to use HTTP

e.http.enabled
HTML port org.osgi.servic Enables the HP Exstream Command Center platform to
number e.http.port serve all resources using HTTP
HTTPS Settings
You can configure the following options for the HTTPS Settings area of the HP Exstream Command Center
Name in the
Properties File
HTTPS Enabled org.osgi.servic Enables HP Exstream Command Center to use HTTPS

e.http.secure.e
nabled
HTTPS port org.osgi.servic Enables the HP Exstream Command Center platform to
number e.http.port.sec serve all resources using HTTPS
ure
TLS Encryption
In order to allow encrypted communication between the HP Exstream Command Center server and other
endpoints, you must have a private key and the appropriate certificate. Both the key and the certificate must be
created for the full domain name of the computer where is HP Exstream Command Center running. The
computer name is the value of the CN attribute in the key and the certificate.
You can configure the following options for the TLS Encryption area of the HP Exstream Command Center
Name in the
Properties File
Keystore Path org.ops4j.pax.w Specifies the path to the keystore to be used

eb.ssl.keystore
Keystore org.ops4j.pax.w Specifies the password used for keystore integrity checks
Password eb.ssl.password
Key Password org.ops4j.pax.w Specifies the password used for keystore
eb.ssl.keypassw
ord
You can verify that RMI is running using SSL by reviewing the RMI log messages.


This section discusses the following configuration settings:
 Database on page 76
 JNDI Context for datasources on page 76
 Output Document Storage on page 77
 Temp Storage on page 77
 JMS Settings on page 77
 Java Content Repository (JCR) Settings on page 78
 BATCH Settings on page 79
 Callback and Cleanup Threads Configuration on page 79
 ExactTarget Query Configuration on page 79
 Operation Mode on page 80
Database
You can configure the following options for the Database area of the HP Exstream Delivery Engine properties:
Name in the
Property Properties File Description
Type DBMS_TYPE Specifies the type of database to use in connection with

the HP Exstream Delivery Engine. Supported databases
are: MySQL, DB2, Oracle, and MS SQL.
Data Source DE_DATASOURCE_N Specifies the name of the data source configured to
Name AME access HP Exstream Delivery Engine database under
application server.
JNDI Context for datasources

HP Exstream Command Center uses an external JNDI service to locate specific administrative objects (for
example, JMS queues) when needed. You do not have to configure JNDI if you do not use components of
HP Exstream Command Center that depend on JNDI lookups.
You can configure the following options for the JNDI Context for datasource area of the HP Exstream
Delivery Engine properties:
Name in the
Properties File
JNDI Provider DS_PROVIDER_URL Defines the configuration information for the JNDI service
URL provider.
It holds connection URL (for example, ldap://
somehost:389)
JNDI Initial DS_INIT_CONTEXT Defines the class name of the initial context factory. For
Context Factory _FACTORY example,
org.jnp.interfaces.NamingContextFactory
URL Package DS_FACTORY_URL_ Specifies a list of package prefixes that are used to load
Prefixes PKGS URL context factories.

Output Document Storage

You can configure the following options for the Output Document Storage area of the HP Exstream Delivery
Engine properties:
Name in the
Properties File
Location OUTPUT_DOCUMENT Specifies the spool directory engine. For best results, do
_STORAGE_LOCATI not share this directory with any other application.
ON
For example: C:/Temp_Spool
This storage location is platform-specific and must be
changed, based on the platforms.
After Delivery OUTPUT_DOCUMENT This specifies the spool directory engine. For best results,
Location _STORAGE_AFTER_ do not share this directory with any other application.
DELIVERY_LOCATI
For example: C:/Temp_Archive
ON
changed based on the platforms.
Temp Storage
You can configure the following option for the Temp Storage area of the HP Exstream Delivery Engine
properties:
Name in the
Properties File
Location ATTACHEMENTS_TE The value is the temporary storage location for a

MP_STORAGE_LOCA multipart attachment.
TION
This location must be different from the location
mentioned in the
OUTPUT_DOCUMENT_STORAGE_LOCATION property.
changed based on the platforms.
JMS Settings
You can configure the following options for the JMS Settings area of the HP Exstream Delivery Engine
properties:
Name in the
Provider URL JMS_END_POINT_P Enter the URL of the provider used for JMS
ROVIDER_URL
Connection JMS_CONNECTION_ The name of the fully qualified Factory class that will be
Factory FACTORY used to create an initial context which contains
ConnectionFactory instances.

Name in the
Initial Context JMS_INIT_CONTEX Enter the name of the JNDI Initial context factory class.
Factory T_FACTORY
For example:
org.apache.activemq.jndi.ActiveMQInitialC
ontextFactory
URL Package JMS_FACTORY_URL Specify a list of package prefixes that are used to load
Prefixes _PKGS URL context factories.
Input Queue DELIVERY_INPUT_ The destination name for input requests.
QUEUE
Output Queue DELIVERY_OUTPUT The destination name for output responses.
_QUEUE
Process Queue DELIVERY_PROCES The destination name for internal job processing.
S_QUEUE
Callback Queue DELIVERY_CALLBA The destination name for internal ready callback
CK_QUEUE messages.
Java Content Repository (JCR) Settings

You can configure the following options for the Java Content Repository (JCR) Settings area of the
HP Exstream Delivery Engine properties:
Name in the
Properties File
Host JCR_REPOSITORY_ IP address/host name of the host on which JCR is

HOST running. For example: 127.0.0.1
Port JCR_REPOSITORY_ Port on which JCR is listening. For example: 12345
PORT
User JCR_REPOSITORY_ User name used to connect to the JCR repository
USER
Password JCR_REPOSITORY_ Password used to connect to the JCR repository.
PASSWORD
RMI Context JCR_REPOSITORY_ The RMI context for remote access to the JCR
RMI_CONTEXT

BATCH Settings
You can configure the following options for the BATCH Settings area of the HP Exstream Delivery Engine
properties:

Properties File
Chunk Size CHUNK_SIZE Number of the customers extracted from the

ReportFile.xml for processing in one cycle.
For more information, see Increasing Concurrency

and Reducing Repeated Disk Access on page 94.
Thread No NO_OF_DELIVERY_ Number of the simultaneous threads for processing
PROCESSING_THRE customers extracted from the ReportFile.xml file.
ADS
For more information, see Increasing Concurrency
and Reducing Repeated Disk Access on page 94.
Callback and Cleanup Threads Configuration

You can configure the following options for the Callback and Cleanup Threads Configuration area of the
HP Exstream Delivery Engine properties:
Name in the
Properties File
Polling Thread POLLING_THREAD_ Number of minutes between two consecutive poll thread
Time Interval TIME_INTERVAL runs. For example, if the value is set to 3, then the
HP Exstream Delivery Engine will run the poll thread
every 3 minutes.
Cleanup Thread CLEANUP_THREAD_ Number of minutes between two consecutive cleanup
Time Interval TIME_INTERVAL thread runs. For example, if the value is set to 3, then the
HP Exstream Delivery Engine will run the cleanup thread
every 3 minutes.
ExactTarget Query Configuration

You can configure the following options for the ExactTarget Query Configuration area of the HP Exstream
Delivery Engine properties:
Name in the
Thread Time ET_QUERY_THREAD The query thread run interval (in minutes).
Interval _TIME_INTERVAL
Update Times ET_QUERY_UPDATE The query update times (in minutes) after sending emails.
_TIMES Multiple values must be separated using commas (,).

Operation Mode
You can configure the following options for the Operation Mode area of the HP Exstream Delivery Engine
properties:
Name in the
Properties File
Mode DELIVERY_ENGINE_ The available modes are Production/simulation. The

OPERATION_MODE default is Production.
HP Exstream Fulfillment Delivery Service Configuration

This section discusses the following configuration settings:
 License on page 80
 Database Configuration on page 81
 Delivery Report on page 81
 Database Clean-up on page 82
 FDS Filestore on page 83
 FDS EWS & Realtime Configuration on page 83
License
You can configure the following option for the License area of the HP Exstream Fulfillment Delivery Service
properties:
Name in the
Properties File
File license.file.lo license.file is a file from which the license key is read.
cation
c:\hpexstream\keys\HP_Production.license
the .license file. The application server classpath locations for the license file are as follows:
Application server classpath locations for license files

For this Application The licence file is at the following location
Server


Database Configuration
You can configure the following options for the Database Configuration area of the HP Exstream Fulfillment
Delivery Service properties:

Properties File
Type database.type Specifies the type of database. The available options are
Oracle, MySQL, DB2 and MS SQL.
Username database.userna Specifies the user name of the user allowed to access the
me database.
For more information about users, see your database

manual.
Password database.passwo Specifies the password for the user name as defined in
rd the
database.username, which FDS uses for connecting in to
the database.
Driver database.driver Defines the database driver class name. For example,
Classname classname com.mysql.jdbc.Driver
URL database.url Specifies JDBC connection URL used by FDS Server to
connect to the database. The following path is the
default:
jdbc:mysql://localhost:3306/fdsdb
NOTE: Examples for the database URL are provided in

the lclj.properties file.
Delivery Report
You can configure the following options for the Delivery Report area of the HP Exstream Fulfillment Delivery
Service properties:
Name in the
Report URL report.cc.url Specifies location inside the server where the report
HTML files should be placed. Create the URL manually
and make sure it is directly accessible from the browser.
Report Location report.cc.http. Specifies the file path where the Delivery Reports is stored.
location The following path is the default:
/opt/apache-tomcat-7.0.0/webapps/report.
CC Location report.cc.locat Specifies the file location where the HP Exstream
ion Command Center picks up the delivery reports that are
transferred from the FDS.
DE Location report.de.locat Specifies the file location to which the HP Exstream
ion Delivery Engine places the delivery reports. The
following path is the default:
/opt/DeliveryManager/Deliveryreports.


HP Exstream Delivery Engine configuration is required for FDS and HP Exstream Delivery Engine communi-
cation.
Fulfillment Delivery Service properties:
Name in the
Properties File
HTTP Interface de.httpinterfac The value of this property is the HTTP URL for FDS to
URL e.url communicate with HP Exstream Delivery Engine.
Checksum de.checksum.ena The value of this property determines if a checksum
Enabled bled validation is required during sending the composed
documents to HP Exstream Delivery Engine.
If the value is true, validation is performed. Enabling
this feature might reduce performance as validating the
checksum increases the processing time. The default
value of this property is false.
Database Clean-up
The cleanup process runs periodically to move jobs from transaction tables to history tables. You can configure
the below properties to get better performance while generating delivery reports.
By setting the below properties, the data gets moved to the history tables.
You can configure the following options for the Database Clean-up area of the HP Exstream Fulfillment
Delivery Service properties:
Name in the
Properties File
Start delay cleanup.startde Specifies the delay in milliseconds after which the first
lay database cleanup process starts.
Period cleanup.period Specifies the duration in milliseconds in which the database
cleanup is performed periodically.

FDS Filestore
You can configure the following options for the FDS Filestore area of the HP Exstream Fulfillment Delivery
Service properties:

Properties File
Filestore lclj-filestore This property specifies the absolute path of the FDS job
store. You need to manually create the ‘FileStore’ folder
with read and write permissions.
For example, on Windows operating systems,
C:\FileStore
On UNIX operating systems, /home/FileStore
For more information on FDS FileStore, see the

HP Exstream Delivery Manager User’s guide.
FDS EWS & Realtime Configuration

You can configure the following options for the FDS EWS & Realtime Configuration area of the HP Exstream
Fulfillment Delivery Service properties:
Name in the
Properties File
Composition composition- Specifies the mode to apply to composition. Options are

Mode factory- EWS or Realtime. The options beneath this setting differ
classpath depending on which composition mode you select.

FDS Configuration for EWS Composition Mode

Fulfillment Delivery Service properties if you use the EWS composition mode:
Name in the
Properties File
Ip 1 ews.ip.1 Specifies the IP of the configured EWS. Multiple

instances of EWS can be configured by specifying
multiple IP.
For a new instance of EWS, increment the value by 1. For
example: Specify a second instance as ews.ip.2
Here, <ip> is the IP address of the machine where EWS
is deployed.
ews.ip.1=16.181.214.30
Port 1 ews.port.1 Specifies the Port number of the configured EWS.
Multiple instances of EWS can be configured by
specifying multiple Port numbers.
For a new instance of EWS, increment the value by 1. For
example: Specify a second instance as ews.port.2.
Here, <port> is Web container port.
ews.port.1=8581
Connection ews.connection. Specifies the amount of time, in milliseconds, that the
Timeout timeout FDS client will take to establish a connection with EWS
before it times out.
Response ews.response.ti Specifies the amount of time, in milliseconds, that the
Timeout meout FDS client will wait for a response from EWS before it
times out.
FDS Configuration for Realtime Composition Mode

Fulfillment Delivery Service properties if you use the Realtime composition mode:
Name in the
JMS Provider URL lcl.rt.jms.prov The value of this property points to the JMS provider URL
ider.url required for FDS real-time engine pool communication.
For example, if you are using ActiveMQ as the JMS
provider for real-time engine pool communication, then
the value of this property is tcp://localhost:61616
where <localhost> is the host name of the ActiveMQ
and 61616 is the port.
JMS Context lcl.rt.jms.cont Specifies the JMS Provider Factory configuration.
Factory extfactory

Name in the
Properties File
JMS Connection lcl.rt.jms.queu Specifies the JNDI name of the JMS connection factory.
Factory econn.factory
JMS Timeout lcl.rt.jms.time Specifies the JMS message time-out in seconds. The
out default value is 60.

Appendix
Appendix
This chapter contains additional information to deploy HP Exstream Delivery Engine and HP Exstream Fulfillment
Delivery Service.
 HP Exstream Delivery Engine Appendix on page 86
 HP Exstream Fulfillment Delivery Service Appendix on page 96
HP Exstream Delivery Engine Appendix
This section provides additional information to deploy the HP Exstream Delivery Engine.
 Sizing Requirements for HP Exstream Delivery Engine When Using JBoss with Oracle Database on page 86
 Sizing Requirements for HP Exstream Delivery Engine when Using WebLogic on page 89
 Configuring the deglobal.properties File on page 90
 Creating a Database Instance and Users for HP Exstream Delivery Engine on page 94
 Configuring Java Content Repository Details on page 96
Sizing Requirements for HP Exstream Delivery Engine When Using JBoss

with Oracle Database
You must make sure to follow the sizing measures required to effectively run HP Exstream Delivery Engine, which
includes:
• Memory Requirements on page 86
• File Descriptor Requirements on page 87
• Database Requirements on page 87
• Tuning JBoss Specific Parameters to Run HP Exstream Delivery Engine on page 88
Memory Requirements
Typically to run HP Exstream Delivery Engine, a minimum of 512MB of RAM is required. However, the memory
requirements increase as the volume of delivery requests increase. During load testing of HP Exstream Delivery
Engine, on an average, around 1.5GB of RAM was required. Therefore, for best results you must plan for using
minimum 3GB of RAM for HP Exstream Delivery Engine.
To improve performance of HP Exstream Delivery Engine:
NOTE: Before you modify the run.conf file, back up the file.
1. Open the <JBoss-5.1.0.GA>/bin/run.conf file.

2. Under JAVA_OPTS, modify the following parameters:

Appendix
• Xms—The Xms parameter specifies the minimum heap size. Heap size is the amount of memory JBoss uses
during startup. If the value of Xms is more than the available RAM, JBoss fails to start.
• Xmx—The Xmx parameter specifies the maximum heap size available to JBoss. If JBoss requires more memory
than the configured heap size, you receive an Out of Memory error message. For best results make sure
that you set a reasonably high value for the maximum heap size.
• MaxPermSize—The MaxPermsize specifies the maximum size for the permanent generation heap. This
heap is used to store information that keeps track of objects stored in the heap sized by the Xms and Xmx.
The following code illustrates the values that were set during load testing of HP Exstream Delivery Engine:
JAVA_OPTS="-Xms1024m-Xmx2048m-XX:MaxPermSize=1024m -
Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -
Dsun.rmi.dgc.server.gcInterval=3600000"
For more information on each of these parameters and on monitoring the heap size used by JBoss, see the
JBOSS WIKI page at http://community.jboss.org/wiki/HowCanIDisplayTheMemoryPoolUsage.
File Descriptor Requirements

By default, on UNIX operating systems, 1024 open file descriptors are assigned to each process. This value is
not sufficient to run HP Exstream Delivery Engine. For best results, you must increase the number of open file
descriptors per process to 5120.
Database Requirements
To manage high load scenarios, HP Exstream Delivery Engine requires approximately 300 connections to the
Oracle database. The total number of connections to the database are specified in the <JBoss-5.1.0.GA>/
server/<engine-instance>/deploy/oracle-ds.xml file. By default, the min-pool-size property
for the DEADMIN and the JMSORACLE user is set to 120 each. Similarly, the max-pool-size property for the
DEADMIN and the JMSORACLE user is set to 175 each.
NOTE: When changing connections to the Oracle database, you must be careful. If you plan to run
the HP Exstream Delivery Engine on a developer environment, where you cannot allocate
many connections to the Oracle database, reduce the min-pool-size value. You can
leave the max-pool-size values intact, so that it can be used by HP Exstream Delivery
Engine when required.
In your environment, monitor the connections that HP Exstream Delivery Engine makes to the Oracle database
before changing the max-pool-size values. Ask your database administrator to monitor the v$session
view and inform you about the connections to the Oracle database.
Best Practices for Using JBOSS with Oracle database

• Run Oracle in a shared server mode.
• Set the value of shared_servers to 30, and the max_shared_servers to 60.
• Increase the number of dispatchers to 2 and the max_dispatchers to 4.
• Increase the value of the processes parameter to at least 1000.
• HP Exstream Delivery Engine uses JBoss JMS technology to persist message requests to a queue before they
are drained. The engine requires around 1.5GB of PGA memory to support persistence of messages.
• Allocate at least 6GB of RAM to the memory_target parameter for the Oracle instance. This allocation
enables Oracle to auto-size the memory requirements for SGA and PGA.

Appendix
Tuning JBoss Specific Parameters to Run HP Exstream Delivery Engine

To enhance the performance of HP Exstream Delivery Engine during high loads, modify the following properties
in JBoss:
• Modifying MBean Thread Pool on page 88
• Modifying MBean Instances on page 88
Modifying MBean Thread Pool

In the <JBoss-5.1.0.GA>/server/<engine-instance>/deploy/jca-jboss-beans.xml file,
modify the maximumPoolSize parameter to 170.
For example:
<jboss-home>/server/<engine-instance>/deploy/jca-jboss-beans.xml
<bean name="WorkManagerThreadPool"
class="org.jboss.util.threadpool.BasicThreadPool">

<annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.jca:servic
e=WorkManagerThreadPool",
exposedInterface=org.jboss.util.threadpool.BasicThreadPoolMBean.class)</
annotation>

<property name="name">WorkManager</property>


<property name="maximumQueueSize">1024</property>


<property name="maximumPoolSize">170</property>

<property name="keepAliveTime">60000</property>
</bean>
Modifying MBean Instances

In the <JBoss-5.1.0.GA>/server/<engine-instance>/conf/standardjboss.xml file
modify the MinimumSize and MaximumSize parameters to 110 and 160 respectively.

Appendix
For example:
<invoker-proxy-binding>
<name>message-driven-bean</name>
<invoker-mbean>default</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
<JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<CreateJBossMQDestination>false</CreateJBossMQDestination>

<MinimumSize>110</MinimumSize>
<MaximumSize>160</MaximumSize>
<KeepAliveMillis>30000</KeepAliveMillis>
<MaxMessages>1</MaxMessages>
<MDBConfig>
<ReconnectIntervalSec>10</ReconnectIntervalSec>
<DLQConfig>
<DestinationQueue>queue/DLQ</DestinationQueue>
<MaxTimesRedelivered>10</MaxTimesRedelivered>
<TimeToLive>0</TimeToLive>
</DLQConfig>
</MDBConfig>
</proxy-factory-config>
</invoker-proxy-binding>
NOTE: If the JBoss JMS queues are clogged, it is possible that JBoss will drop message delivery.
This will lead to job failures in the HP Exstream Delivery Engine. To prevent the flooding of
the queues, you must increase the values in the afore mentioned parameters.
Sizing Requirements for HP Exstream Delivery Engine when Using

WebLogic
To effectively run HP Exstream Delivery Engine, you must make sure to follow the sizing measures required:
 Memory Requirements on page 89
 Modifying the Connection Pool on page 90
Memory Requirements
When deploying the HP Exstream Delivery Engine on WebLogic it is important to make sure that the engine has
been allocated enough heap memory to process delivery requests. The amount of memory required depends on
the load that the engine has to process. HP recommends setting the initial heap size to at least 1024MB and the
maximum heap size to at least 2048MB. A minimum of 1024MB is required for the max perm size parameter. If
enough physical RAM is not available, delivery requests will fail with the an OutOfMemory exception.
To improve performance of HP Exstream Delivery Engine:
1. Go to DeliveryEngine domain directory under user_projects.
For example:
<weblogic_home>\user_projects\domains\<Domain Directory>
2. To set the domain environment, open the setDomainEnv script:
• On Windows operating systems, use setDomainEnv.bat file.
• On UNIX operating systems, use setDomainEnv.sh file.

Appendix
3. In the setDomainEnv script file, change the Java opts values as follows:
JAVA_OPTS="-Xms1024m -Xmx2048m -XX:MaxPermSize=1024m"
4. Restart the WebLogic application server.
The server logs the startup Command Line.
5. Verify that the values are reflected.
Modifying the Connection Pool

The HP Exstream Delivery Engine requires a minimum of around 200 connections with the database to handle
concurrent requests. You will have to monitor the number of sessions taken by the HP Exstream Delivery Engine
to tune the number of connections required. This will change according to customer environment and delivery
requirement. HP recommends having a buffer of at least 50 connections between what is required by the engine
and the maximum number of connections available. In general if the HP Exstream Delivery Engine does not
have the required number of connections in its connection pool, delivery requests will be significantly delayed.
In extreme cases, this might lead to job delivery failure as well.
To modify the Connection Pool in WebLogic:
1. Login to the WebLogic Console, using the following WebLogic credentials:
http://<hostname>:<port>/console
where:
<host> is the IP address of the server where WebLogic server is installed, and
<port> is the port for the administration server (typically 7001)
username: weblogic
password: <password that you have chosen for the user>
2. On the navigation pane of the WebLogic administrative console, select DeliveryEngine domain, and then
click Services.
3. Click Data sources,
Two data sources are created:
a. DEDS
b. WLDS
4. Click DEDS, and then select Connection Pool tab.
5. Click Lock, and then click Edit.
6. Change the initial capacity and maximum capacity values for the connection pool to 110 and 160 respectively.
Configuring the deglobal.properties File

To customize your installation of HP Exstream Delivery Engine, you can modify the properties in the
deglobal.properties file located on the application server classpath.
The following table describes the properties that can be configured in the deglobal.properties file:
deglobal.properties file properties

Property Description Required
PROVIDER_URL The host and port information available Required

for WebLogic Server.
For example, t3://localhost:7001

Appendix

INITIAL_CONTEXT_FACTORY The value must point to the ActiveMQ Required

initial context factory.
For example:
org.apache.activemq.jndi.Acti
veMQInitialContextFactory
OUTPUT_DOCUMENT_STORAGE_ This specifies the spool directory Required
LOCATION engine. For best results, do not share
this directory with any other
application.
For example: C:/Temp_Spool
This storage location is platform-specific
and must be changed, based on the
platforms.
OUTPUT_DOCUMENT_STORAGE_ This specifies the spool directory Required

engine. For best results, do not share
AFTER_DELIVERY_LOCATION
this directory with any other
application.
For example: C:/Temp_Archive
This storage location is platform-specific
and must be changed based on the
platforms.
ATTACHMENTS_TEMP_ The value is the temporary storage Required
STORAGE_LOCATION location for a multipart attachment. This
location must be different from the
location mentioned in the
OUTPUT_DOCUMENT_STORAGE_LOCAT
ION property. This storage location is
platform-specific and must be changed
based on the platforms.
JMS_PROVIDER_URL The value must point to the ActiveMQ Required if using JMS
provider URL and port. interface for communication
For example: tcp://
localhost:61616
JCR_REPOSITORY_HOST IP address/host name of the host on Required if using only JCR
which JCR is running.
For example: 127.0.0.1
JCR_REPOSITORY_PORT Port on which JCR is listening. Required if using only JCR
For example: 12345
JCR_REPOSITORY_USER User name used to connect to the JCR Required if using only JCR
repository
JCR_REPOSITORY_PASSWORD Password used to connect to the JCR Required if using only JCR
repository
JCR_REPOSITORY_RMI_ RMI context for the JCR Required if using only JCR
CONTEXT

Appendix

NO_OF_DELIVERY_PROCESSING_ Number of the simultaneous threads for Optional

THREADS processing customers extracted from the
ReportFile.xml file.
For more information, see

Increasing Concurrency and
Reducing Repeated Disk Access
on page 94.
CHUNK_SIZE Number of the customers extracted from Required
the ReportFile.xml for processing in
one cycle.
For more information, see

Increasing Concurrency and
Reducing Repeated Disk Access
on page 94.
POLLING_THREAD_TIME_ Number of minutes between two Required
INTERVAL consecutive poll thread runs. For
example, if the value is set to 3, then the
HP Exstream Delivery Engine will run
the poll thread every3 minutes.
For more information, see Polling

Thread Time Interval on page 93.
CLEANUP_THREAD_TIME_ Number of minutes between two Required
INTERVAL consecutive cleanup thread runs. For
example, if the value is set to 3, then the
HP Exstream Delivery Engine will run
the cleanup thread every 3 minutes.
For more information, see Cleaning

up the Thread Time Interval
on page 94.
ET_QUERY_THREAD_TIME_INTER The query thread run interval (in Required only if you are
VAL minutes). using the ET_Email delivery
channel
ET_QUERY_UPDATE_TIMES The query update times (in minutes) Required only if you are
after sending emails. Multiple values using the ET_Email delivery
must be separated using commas (,). channel
FTP_THREAD_SENDFILE_POOL_SI Number of threads that can be used to Required

ZE send files by using FTP. The default
value is 10.
FTP_THREAD_SENDFILE_TIMEOU Number of milliseconds that the Required
T HP Exstream Delivery Engine will wait
for each thread to send a file before
timing out. The default value is 60000
milliseconds (one minute).

Appendix

BATCH_REQUEST_THREAD_DELA Number of milliseconds that the Required

Y HP Exstream Delivery Engine will wait
after creating the jobs defined by the
CHUNK_SIZE property. The default
value is 2000 milliseconds (two
seconds).
AMQ_MEMORY_USAGE Maximum amount of memory that can Required
be used to store NON-PERSISTENT
messages. The default value is 128MB.
NOTE: The Delivery Engine embedded

ActiveMQ broker does not persist
messages.
AMQ_TEMP_USAGE Maximum amount of memory that can Required
be used to store temporary messages.
The default value is 50GB.
AMQ_QUEUE_PREFETCH_SIZE Maximum number of messages that can Required
be streamed to a customer at the same
time. The default value is 100.
TIME_TO_LIVE Number of seconds that an object is Required
maintained before it expires. The default
value is 3600 seconds.
NOTE: If HP Exstream Delivery Engine and HP Exstream Command Center are installed on different
systems, then HP Exstream Command Center must be updated with the URL through which
the HP Exstream Delivery Engine can be accessed. The URL can be configured in the
server.properties file available in the HP Exstream Command Center installation.
Additional Functions of the deglobal.properties files

This section provides additional information to modify the properties in the deglobal.properties file. The
information added here can be used when configuring the poll thread, cleanup thread and chunk size ratio
information in the deglobal.properties file.
Polling Thread Time Interval

This interval decides the time in minutes between two successive runs of the poll thread in the HP Exstream
Delivery Engine. The poll thread is responsible for providing callbacks to HP Exstream Command Center on
status of batch jobs [response type equals batch summary]. You would typically set the response type to batch
summary, for small batch jobs. A batch summary response type, instructs the engine to provide a single
summary response indicating the number of failed and successful jobs. This mode is in contrast to the batch
query mode where HP Exstream Command Center periodically polls the engine to get the status of the batch
job. The batch summary mode reduces the poll overhead on HP Exstream Command Center and shifts it to the
HP Exstream Delivery Engine. HP recommends the default 3 second poll interval. Reducing this further will have
an impact on the performance of the engine. If you do not use the batch summary mode for your batch jobs (all
your batch jobs have sizes in excess of 5000 or so) then it is beneficial to increase the poll interval to say
around 20. This will reduce the time interval between two successive runs of the poll thread and free up engine
resources to focus on delivery.

Appendix
Cleaning up the Thread Time Interval

The HP Exstream Delivery Engine has a cleanup thread that periodically checks for jobs that have been
completed. Once the engine detects that a job has been completed it cleans up any temporary files that are
spooled in the spool directory, and deletes the corresponding job record in the engine job table. Periodic runs
of the cleanup thread is required to have optimum performance levels (too many records in the engine job table
will slow down inserts and updates and hence affect throughput). It is also necessary to keep the spool directory
clutter free.
Reducing the cleanup thread interval will cause the thread to run more frequently, HP recommends keeping the
default value [3 minutes]. Increase this value only if you generally do not have high volumes of request to
process.
Increasing Concurrency and Reducing Repeated Disk Access

To process any batch, the HP Exstream Delivery Engine functions as follows:
1. It parses the ReportFile.xml serially. The report file has metadata information for all the delivery requests in
the batch job.
2. Every delivery request that is extracted is queued to an engine job thread pool that is maintained internally.
To increase concurrency and to reduce repeated disk access the engine reads the XML file in chunks. The
CHUNK SIZE parameter decides the number of delivery requests read by the engine and queued for delivery in
one disk access. The number of delivery processing threads decides the size of the engine thread pool. The
delivery requests read by the engine are processed by the delivery threads in the engine thread pool. In
general, the recommended ratio of chunk size to delivery processing threads is 4:1. [200:50]. Increasing the
engine job thread pool size would increase the number of available threads to process the delivery requests.
This does not necessarily mean an increased through put. Each delivery request read by the processing threads
in the engine job thread pool is queued internally in a JMS queue for final delivery.
Increase the ratio only if you are confident that the final delivery destination has the capability to process that
many delivery requests concurrently. For example, if you have a batch job for FTP, increase the ratio only if you
are confident that the FTP server can handle that many concurrent requests simultaneously. If your FTP server can
handle 200 concurrent requests simultaneously, then shifting to a 2:1 ratio may be beneficial. Otherwise, it
would only clog the internal JMS queues of the engine.
Creating a Database Instance and Users for HP Exstream Delivery Engine

In order to use the database, you need to create database instance and users. Complete the following tasks as
needed:
• Configuring MySQL for Distributed Deployment on page 94
• Creating a User on UNIX on page 95
Configuring MySQL for Distributed Deployment

To run the MySQL database on a different system other than JBoss or WebLogic, you must complete the
following tasks:
• Allowing remote access for the DEADMIN user
• Granting privileges to the remote host user
Allowing Remote Access for the DEADMIN User

To allow remote access for the DEADMIN user, from the MySQL Command Line Client terminal, execute the
following command:
CREATE USER 'DEADMIN'@'%' IDENTIFIED BY 'password_for_new_username';

Appendix
Where % is the hostname of the machine that runs HP Exstream Delivery Engine.
Granting All Privileges for the Remote Host User

To grant all the privileges to the remote host user, from the MySQL Command Line Client terminal, execute
the following command:
GRANT ALL PRIVILEGES ON DELENGINEDB.* TO 'DEADMIN'@'%' WITH GRANT OPTION;
Where % is the hostname of the machine that runs HP Exstream Delivery Engine.
Creating a User on UNIX

1. To create a user by using the console command interface in UNIX, execute the following command:
useradd -d /home/<username> -p password <password>
Where, the -d switch specifies the home directory.
2. To add a user to a group, execute the following command:
useradd -G <group> -m <username> passwd <password>
Creating a Database Instance and a User in MS SQL

If you plan to use an MSSQL database, you must create two tablespaces and two users in the MS SQL
database.
One tablespace and user will be used by HP Exstream Delivery Engine and the other tablespace instance and
the user will be used by the application server to store and queue the JMS messages for processing the delivery
requests.
Creating a Database and a User in MS SQL for HP Exstream Delivery Engine

To create a DELENGINEDB database instance and DEADMIN user in MS SQL for HP Exstream Delivery Engine,
complete the following tasks:
Creating the DELENGINEDB Database Instance

To create the DELENGINEDB database:
1. Right click Database in Object Explorer pane and then select New Database.
The New Database window appears.
2. In the Database name field enter a name for the database to be created.
3. In the Owner field enter the username.
4. Click OK.
A new database is created. It is populated under the Database folder in the Object Explorer pane.
Creating the DEADMIN User

To create the DEADMIN user:
1. Click Start > All Programs > Microsoft SQL Server 2008 R2 > SQL Server Management Studio.
The Microsoft SQL Server Management Studio window appears.
2. In the Login and Password fields enter the user name and password, which are created during installation of
MS SQL.
3. Click Connect.

Appendix
4. In the Object Explorer pane go to Security and right click Login and then select New Login.
The Login-New window appears.
5. In the Login Name field enter the user name.
a. Select SQL Server authentication option.
b. Enter the Password and Confirm Password fields.
6. Click OK.
The Login Properties window appears.
7. In the Select a page section select Server Roles.
In the Server roles section, the check box public is by default selected.
8. Select the check box sysadmin and then click OK.
A new database user is created.
Configuring Java Content Repository Details

If HP Exstream Command Center and HP Exstream Delivery Engine are installed on two separate hosts, you can
configure HP Exstream Command Center to send the output files and the report_manifest.xml file either
through the HTTP or JMS interface, or share the output files and the report_manifest.xml file through a
Java Content Repository (JCR).
If you are planning to use JCR, you must configure HP Exstream Delivery Engine to access the JCR. The following
JCR properties must be modified in the deglobal.properties file:
 JCR_REPOSITORY_HOST
 JCR_REPOSITORY_PORT
 JCR_REPOSITORY_USER
 JCR_REPOSITORY_PASSWORD
 JCR_REPOSITORY_RMI_CONTEXT
For more information about the deglobal.properties file, see Configuring the deglobal.properties File
on page 90.
HP Exstream Fulfillment Delivery Service Appendix

This section provides additional information to be considered when deploying HP Exstream Fulfillment Delivery
Service.
Setting up the Real-time Composition Engine for HP Exstream Fulfillment

Delivery Service
NOTE: Before you set up the real-time engine, make sure that HP Exstream Production Engine
8.0.301 or later is installed with real-time support. There are multiple ways of setting up
real-time engines. The below mentioned procedure is one of the ways of setting up real-time
engine in HP Exstream. If you have expertise in using HP Exstream Production Engine, you
can go forward with your own way of setting up the real-time engine as it involves mostly
configurations on the HP Exstream side.
Verify that you have the HP Exstream real-time application file, and other related static reference files (customer
data file) before you begin your real-time engine set up in HP Exstream Fulfillment Delivery Service.

Appendix
To use real-time engine in the document composition mode in HP Exstream Fulfillment Delivery Service, you
need to perform the following tasks:
• Creating an INI File on page 97
• Creating an Engine Pool XML File on page 98
• Setting up Real-time Composition Engine in HP Exstream Fulfillment Delivery Service on page 101
NOTE: The following sections requires prior knowledge of HP Exstream Production Engine as the
various terminologies used while creating an INI File is mainly part of HP Exstream
component.
Creating an INI File

HP Exstream Fulfillment Delivery Service uses JMS Connector for real-time implementation. The INIFILE has
the details of the JMS connection parameters and the JMS input and output queue information. The INIFILE
contains the Java Enabler open parameters for the HP Exstream Production Engine to read and use at run time.
For more information about using an INIFILE in HP Exstream Production Engine, see the Preparing Appli-
cation for Production guide in the HP Exstream documentation.
The following is a sample INI file:

CLASS=com/hp/exstream/cc/connector/LCLConnector
CLASSPATH=C:\DM 1.1\lcl\cc-connector-data.jar;C:/Assured Delivery/Engine
application server/Dialogue/x86/DBCS/JavaEnabler.jar;
INSTANCE=SHARED
TRACE=N
JNDI_CONTEXT_FACTORY=org.apache.activemq.jndi.ActiveMQInitialContextFactory
JNDI_PROVIDER_URL=tcp://localhost:61616
CONNECTION_FACTORY=QueueConnectionFactory
INPUT_QUEUE=INPUT_QUEUE_dm_demo_dda
INPUT_QUEUE_dm_demo_dda=dynamicQueues/dm_demo_dda.data.INPUT
OUTPUT_QUEUE=OUTPUT_QUEUE_dm_demo_dda
OUTPUT_QUEUE_dm_demo_dda=dynamicQueues/dm_demo_dda.data.OUTPUT
To create an INI file:
1. Update the following four parameters in the INIFILE, which are required for HP Exstream Fulfillment Delivery
Service configuration:
• CLASS—The CLASS parameter points to the custom JMS connector implemented for HP Exstream Fulfillment
Delivery Service.
• CLASSPATH—Set the absolute path of the cc-connector-data.jar in the CLASSPATH parameter of
the INIFILE.
The CLASSPATH parameter indicates the absolute path where the custom JMS Connector class specified in
the CLASS parameter resides.
As part of the HP Exstream Fulfillment Delivery Service distribution file in the real-time util folder, a
cc-connector-data.jar is provided.
For example, C:\temp\fulfillment-delivery-service1.2.0\realtime-util\cc-
connector-data.jar
• INPUT_QUEUE—The INPUT_QUEUE parameter points to a parameter that in turn points to the JMS input
queue name from which the input driver file sent by HP Exstream Fulfillment Delivery Service is read and
sent to the HP Exstream.

Appendix
• OUTPUT_QUEUE—The OUTPUT_QUEUE parameter points to a parameter that in turn points to the JMS output
queue name into which the HP Exstream generated output and manifest report files are written for the
HP Exstream Fulfillment Delivery Service application to pick it up.
NOTE: Each real-time application used in HP Exstream Fulfillment Delivery Service must have its
unique JMS input and output queue. You must use the following convention for the input and
the output JMS Queue names to be used in HP Exstream Fulfillment Delivery Service. For
example, Input Queue name is dynamicQueues/<packagename>.data.INPUT and
Output Queue name is dynamicQueues/<packagename>.data.OUTPUT
For example, if the package file name is dm_demo_dda.pub, then the input and output JMS queue names
will be:
– Input Queue—dynamicQueues/dm_demo_dda.data.INPUT
– Output Queue—dynamicQueues/dm_demo_dda.data.OUTPUT
2. After specifying all the previous parameters, save the INI file in any location.
You must specify the location of the INI file during the configuration of engine pool XML file in the following
section.
Creating an Engine Pool XML File

The engine pool XML file is used to generate the control file required by the HP Exstream Production Engine. The
engine pool XML file contains the configurations to start the engine pool in the real-time mode.
A sample engine pool XML file (SampleEnginePool.xml) is provided with the HP Exstream Fulfillment Delivery
Service distribution file that you can use as a reference or template to create the engine pool configuration XML
file.
NOTE: The following sections requires prior knowledge of HP Exstream Production Engine as the
various terminologies used while creating an engine pool XML file is mainly part of
HP Exstream.
For more information about the various terminologies used in the engine pool XML file, see the Preparing
Applications for Production Guide in HP Exstream documentation.
On Windows Operating System

To create an engine pool XML file:
1. Go to the temporary folder created initially from the HP Exstream Fulfillment Delivery Service distribution file.
2. Go to the realtime-util folder and open the SampleEnginePool.xml file.
3. In the SampleEnginePool.xml, edit and specify the following parameters:
• engineEnvironment—This parameter defines the engine environment key value pair that is set in the
environment of each engine process running in the engine pool.
For example:
– Key—Path
– Value—C:\Program Files\Java\jdk1.6.0_18\jre\bin\client
The value of this parameter is reference to the path name for the directory that contains jvm.dll
• engineExecutable—The value of this parameter is the absolute path of the engine executable.
For example, C:\Program Files\Hewlett-Packard\HP Exstream\HP Exstream
application server\Engine.exe.

Appendix
• engineKeyFilePath—The value of this parameter is the absolute path of the HP Exstream Production
Engine license key file.
For example, C:\Program Files\Hewlett-Packard\HP Exstream\HP Exstream
application server\ enginekeyfile.ekf.
• engineMessageResources—The value of this parameter is the absolute path of the Message resource
file required for the HP Exstream Production Engine to run.
• For example, C:\Program Files\Hewlett-Packard\HP Exstream\HP Exstream
application server\ MsgResource_en-us.dat.
• enginePools—The XML must have one or more engine pool information, each corresponding to a real-
time application.
– controlFilePath—The value of this parameter is the absolute path of the folder to store the control
file generated by real-time utility.
– engineCount—The value of this parameter is the number of engine instances to be started for the real-
time application
– logicalNames—The value of this parameter is to map each logical name corresponding to each driver,
reference and output files used in the HP Exstream real-time application (package file).
– Name—The value of this parameter is the unique name for the logical name mapping and it is mapped to
the symbolic name used in the HP Exstream real-time application.
– Type—The value of this parameter is the file type, which can be REFERENCE, DRIVER or OUTPUT.
– REFERENCE—The value of this parameter is the reference file types that are used to map the input
reference files used by the HP Exstream real-time application and it is mapped to “-FILEMAP” switch in
the control file used by the HP Exstream application.
– DRIVER—The value of this parameter are the driver file types that are used to map the input driver file to
the “-DDAFILEMAP” switch used by the engine control file.
– OUTPUT—The value of this parameter is the output file type that maps to the “-DDAOUTPUT” switch used
in the HP Exstream engine control file and is used to specify a DDA routine for receiving the buffered
output, with one output write per record.
– fileLocation—This parameter is used to specify the path of the reference files used in the
HP Exstream application and this field is used if the type specified is “REFERENCE.”
– ddaProgramType—This parameter defines the language used to create the DDA Module. The field is
used only if the type specified is “DRIVER” or “OUTPUT”. For example, “DLL”.
– connectorMethod—This parameter is specified only if the type is “DRIVER” or “OUTPUT”. The field
is used to specify the function name used in the DLL routine.
– connectorModule—This parameter is used to specify the absolute path of the DDA routine used. The
field is used only if the type specified is “DRIVER” or “OUTPUT”.
– bufferSize—This parameter specifies the size of the buffer (in bytes), which must accommodate the
size of the output.
– openParams—The value of this parameter is to specify the parameters used in the connector module.
The field is used only if the type specified is “DRIVER” or “OUTPUT”. Of the open parameters supported
by the HP Exstream, HP Exstream Fulfillment Delivery Service uses mainly the “INIFILE” parameter.
The INIFILE parameter indicates the file that contains the Java Enabler open parameters for the engine
to read and use at run time. If used, the INIFILE parameter must be the only parameter specified in the
Open parameters box on the connector object’s properties.
– iniFilePath—The field is used to specify the path of INIFILE used by the connector. This field is an
optional field as the information is specified in the openParams section. The field is used only if the type
specified is “DRIVER” or “OUTPUT”.
– You need to specify the path of the INIFILE saved in the earlier section.
– packageFileName—The value of this parameter is to specify the absolute path of the HP Exstream
Production Engine package (.PUB) file
– varsets—This field is used to specify the value of the variable used in the HP Exstream application.

Appendix
4. After specifying all the previous parameters, save the engine pool XML file in any location.
You must specify the location of the engine pool XML file during the real-time engine set up.
On UNIX operating systems

To create an engine pool XML file:
2. Go to realtime-util folder and open the SampleEnginePool.xml file.
3. Using the SampleEnginePool.xml as a template, create your own engine pool XML file, by specifying the
following parameters:
• engineEnvironment—This parameter defines the engine environment key value pair that is set in the
environment of each engine process running in the engine pool.
For example:
– Key—Path
– Value—/home/tmp/jdk1.6.0_18/jre/lib/amd64/server
The value of this parameter is reference to the path name for the directory that contains libjvm.so
• engineExecutable—The value of this parameter is the absolute path of the engine executable.
For example, /usr/engine/Engine.
• engineKeyFilePath—The value of this parameter is the absolute path of the HP Exstream Production
Engine license key file.
For example, /usr/engine/ enginekeyfile.ekf.
• engineMessageResources—The value of this parameter is the absolute path of the Message
resource file required for the HP Exstream Production Engine to run.
For example, /usr/engine/ MsgResource_en-us.dat.
• enginePools—The XML shall have one or more engine pool information, each corresponding to a real-
time application.
– controlFilePath—The value of this parameter is the absolute path of the folder to store the control
file generated by real-time utility.
– engineCount—The value of this parameter is the number of engine instances to be started for the real-
time application
– logicalNames—The value of this parameter is to map each logical name corresponding to each driver,
reference and output files used in the HP Exstream real-time application (package file).
– Name—The value of this parameter is the unique name for the logical name mapping and it is mapped to
the symbolic name used in the HP Exstream real-time application.
– Type—The value of this parameter is the file type, which can be REFERENCE, DRIVER or OUTPUT.
– REFERENCE—The value of this parameter is the reference file types that are used to map the input
reference files used by the HP Exstream real-time application and it is mapped to “-FILEMAP” switch in
the control file used by the HP Exstream application.
– DRIVER—The value of this parameter are the driver file types that are used to map the input driver file to
the “-DDAFILEMAP” switch used by the engine control file.
– OUTPUT—The value of this parameter is the output file type that maps to the “-DDAOUTPUT” switch used
in the HP Exstream engine control file and is used to specify a DDA routine for receiving the buffered
output, with one output write per record.
– fileLocation—This parameter is used to specify the path of the reference files used in the
HP Exstream application and this field is used if the type specified is “REFERENCE”.
– ddaProgramType—This parameter defines the language used to create the DDA Module. The field is
used only if the type specified is “DRIVER” or “OUTPUT”. For example, “DLL”.

Appendix
– connectorMethod—This parameter is specified only if the type is “DRIVER” or “OUTPUT”. The field
is used to specify the function name used in the DLL routine.
– connectorModule—This parameter is used to specify the absolute path of the DDA routine used. The
field is used only if the type specified is “DRIVER” or “OUTPUT”.
– bufferSize—This parameter specifies the size of the buffer (in bytes), which must accommodate the
size of the output.
– openParams—The value of this parameter is to specify the parameters used in the connector module.
The field is used only if the type specified is “DRIVER” or “OUTPUT”. Of the open parameters supported
by the HP Exstream, HP Exstream Fulfillment Delivery Service uses mainly the “INIFILE” parameter.
The INIFILE parameter indicates the file that contains the Java Enabler open parameters for the engine
to read and use at run time. If used, the INIFILE parameter must be the only parameter specified in the
Open parameters box on the connector object’s properties.
– iniFilePath—The field is used to specify the path of INIFILE used by the connector. This field is an
optional field as the information is specified in the openParams section. The field is used only if the type
specified is “DRIVER” or “OUTPUT”.
– You need to specify the path of the INIFILE saved in the earlier section.
– packageFileName—The value of this parameter is to specify the absolute path of the HP Exstream
Production Engine package (.PUB) file
– varsets—This field is used to specify the value of the variable used in the HP Exstream application.
4. After specifying all the previous parameters, save the engine pool XML file in any location.
You must specify the location of the engine pool XML file during the real-time engine set up.
Setting up Real-time Composition Engine in HP Exstream Fulfillment Delivery

Service
To set up and configure the real-time engine in HP Exstream Fulfillment Delivery Service, a real-time utility is
provided as part of HP Exstream Fulfillment Delivery Service distribution package in the real-time util
folder.
On Windows Operating Systems

To set up and start the real-time composition engine in HP Exstream Fulfillment Delivery Service:
For example, C:\temp\FulfillmentDeliveryService_1_0_1_Windows
2. Go to realtime-util folder and, using a text editor, open the dm-realtime-mgmt.bat file.
3. In the dm-realtime-mgmt.bat file, edit the following parameters:
a. Path of the engine pool XML file
b. Target folder where the HP Exstream Messages.dat files and log files are saved.
For example:
java -jar dm-realtime-mgmt.jar START C:\temp\fulfillment-delivery-service-
1.2.0\realtime-util\SampleEnginePool.xml c:\DM\realtime\logs
4. Save and close the dm-realtime-mgmt.bat file.
5. Start the real-time engine pool by executing the dm-realtime-mgmt.bat
This generates the control file and starts the engine instances.
6. Validate the successful starting of engine instances by viewing the Engine.exe running as a process in
Windows Services.
NOTE: You must start the HP Exstream engine instances on a machine that is remote to where
HP Exstream Fulfillment Delivery Service is installed. You can start as many HP Exstream

Appendix
engine instances as required for your business scenario, however make sure that all the
HP Exstream instances for the same package file listens to the same JMS Queue.
On UNIX operating systems

To set up and start the real-time composition engine in HP Exstream Fulfillment Delivery Service:
1. Go to the temporary folder created initially from the HP Exstream Fulfillment Delivery Service distribution file. For
example:
/home/tmp/fulfillment-delivery-service-1.2.0
2. Go to realtime-util folder and open dm-realtime-mgmt.sh file using a text editor. For example:
/home/tmp/fulfillment-delivery-service-1.2.0/realtime-util/dmrealtime-mgmt.sh
3. In the dm-realtime-mgmt.sh file, edit the path of the engine pool XML file and then specify a target folder.
The target folder specified contains the HP Exstream Messages .dat files where logs are saved.
For example:
java -jar dm-realtime-mgmt.jar START /home/tmp/fulfillment-delivery-service-
1.2.0/realtime-util/SampleEnginePool.xml c:\DM\realtime\logs
4. Save and close the dm-realtime-mgmt.sh file.
5. Start the real-time engine pool by executing the dm-realtime-mgmt.sh.
This generates the control file and starts the engine instances.
NOTE: You must start the HP Exstream engine instances on a machine that is remote to where
HP Exstream Fulfillment Delivery Service is installed. You can start as many HP Exstream
engine instances as required for your business scenario, however make sure that all the
HP Exstream instances for the same package file listens to the same JMS Queue.

Troubleshooting
Troubleshooting
The easiest, most effective way to begin troubleshooting is to examine log files for clues that can identify the
issue. Log files are located in the var/logs directory in your installation directory.
This method is most effective when the logging level is set to warning or lower.
Common Issues that can occur in HP Exstream Command Center

The following are common issues that can occur:
Issue Explanation
ERROR: Validation of database This error occurs if you did not create a database schema in the custom
schema failed database (for example, MySQL) before starting the application.
WARN: Engine executable If you receive this warning message, HP Exstream Command Center
does not exist Server cannot access the HP Exstream Production Engine.
You can use HP Exstream Command Center without the Production
Engine. Some of the functionality will not function properly and you
cannot use all the job definition types.
Could not load JDBC driver If you are using a custom database server, HP Exstream Command
class Center requires a driver (JDBC Connector) for the database. If you do
not have connector, contact your database provider for a “JDBC
connector”, but make sure you receive the connector in a single .jar
file.
For more information about setting the database, see HP Exstream

Delivery Manager Database Requirements on page 14.
Unknown error HP Exstream Command Center is a complex system and errors might
be reported by components provided by the external system. If
HP Exstream Command Center Server is unable to recognize the error,
you see an Unknown Error in the output. Information is available in the
HP Exstream Command Center Server log file located at the following
location in the installation directory:
var/logs/cc-server.log
ERROR: Job history file could The file with job history could not be found in job folder. This usually
not be located occurs when the job folder is deleted using the cleanup functionality
provided in Jobs menu. This is usually not an error, but an expected
state.
ERROR: CC_PROPERTIES value If you receive this message when clicking New Job Definition in the
is not set Job Definition window on the WebGUI, verify whether the conf
directory and its contents are in the Web application directory.

Troubleshooting
Issue Explanation
ERROR: Connection to server The error message appears while logging into the WebGUI, when a
failed user has enabled the Command Center Cluster option, and started
the server in passive mode. To start the server in active mode, go to the
bin directory of the installation location and execute the following
command:
For Windows: command-center.bat active
For UNIX: ./command-center active
After starting the server in active mode, you can login to the WebGUI.
Real-time App Fails to Start in If the active node started first in Windows and Start Up type as Real-
Passive Node time Apps is automatic (in case of three nodes); the engine pool will
fail to start in the second passive server.
ERROR: Nodes are unavailable If you are using the WebGUI in Create New Job window, if you do
not select an engine and try to create a job, this error message
appears. Select an engine to avoid this error.
ERROR: Out of memory If this message appears while exporting or importing large number of
job definitions, change max.memorysize to 1024 in the
wrapper.conf located under <install dir>/bin/wrapper
and restart the server.
ERROR: “Couldn't find While running the migration utility, if you get this message, make sure
appropriate jdbc driver” that the path for database.source.driver.path,
database.target.driver.path, are correct.
In Windows, if you used backward slash (\) to specify the path of the
driver file, then use double backward slash (\\).
In UNIX, use forward slash (/) to specify the path of the driver file.
ERROR: Database locked while If you get this message while running the migration utility, make sure
running the migration utility that the database of HP Exstream Command Center 1.1 or 2.1 are not
used by another application.
Warning or Info messages are If you encounter the following message, followed by the message:
displayed while running the “Data Migration Completed Successfully”. You can ignore these
migration utility messages.
• WARNING: XML configuration warning in file:<cc_install_dir>/bin/
dbmigration/tmp.xml(1:6): Document root element "etl", must match
DOCTYPE root "null".
• WARNING: XML configuration warning in file:<cc_install_dir>/bin/
dbmigration/tmp.xml(1:6): Document is invalid: no grammar found.
• INFO: Connection JdbcConnection{org.hsqldb.jdbc.jdbcConnection}
doesn't support transactions. Commit ignored.
cc : 8072,8078,8079,8082,8085
WEBGUI :8077,8076,8075,8074,8073
Make sure these ports are not used in HP Exstream Fulfillment Delivery
Service/HP Exstream Delivery Engine or any other places.
Bug Reporting in HP Exstream Command Center

If you receive errors and the problem is not in your configuration, report the behavior to HP. To make the process
of debugging and fixing the problem easier, include the following data:
• A step-by-step instruction to reproduce the bug (if you can reproduce it).

Troubleshooting
• Your Java version and provider.

• The type of distribution used such as “full” or “server distribution”.
• If you are use a custom servlet container or application server, the version and provider of the application.
• If you use a custom SQL database, provide the version and provider of your database sub-system.
• A brief description of the hardware or software you use (architecture, operating system, number of processors,
and so on).
• For WebGUI, a screenshot of the problem and the version of your Web browser.
• The HP Exstream Command Center version and build number.
Common Issues that can occur in HP Exstream Delivery Engine

Issue Resolution
Failed jobs are available in Clean up the following ActiveMQ queues:

the ActiveMQ queue.
• DELIVERY_LISTENER_INPUT_QUEUE
• DELIVERY_LISTENER_OUTPUT_QUEUE
Large number of job Before starting HP Exstream Delivery Engine, clean up the content in the following
backlogs are created. tables:
• engine_job_table
• engine_job_history_table
• batch_metadata_table
Not enough information is Change the log level in <jboss-5.1.0.GA folder>\server\DE\conf\jboss-
available in the logs for log4j.xml to debug.
debugging.
For example:
<category name="com.hp">
<priority value="DEBUG" />
<appender-ref ref="DE"/>
</category>
Driver not found while If you get the error "Couldn't find appropriate jdbc driver", then make sure that the
running the migration utility path for these parameters-database.source.driver.path,
database.target.driver.path, are correct.
In case of Windows if you are using backward slash (\) to specify the path of the
driver file, then use double forward slash (\\).
In case of UNIX use forward slash (/) to specity the path of the driver file.
Common Issues that can occur in HP Exstream Fulfillment Delivery

Service
Issue Resolution
If you fail to create database though you have entered all the valid values Try to download the JDBC jar file again from
in the dm-fds-db-config.properties file, then you must check the respective vendor site and use it for
the JDBC driver file. It might have got corrupted. database creation.

Index
Index
A commands, in Command Center .................... 35

action handler .............................................60 common issues
Command Center ................................. 103
Delivery Engine .................................... 105
Fulfillment Delivery Service .................... 105
B configuring
BATCH settings ............................................79 Command Center Data Channels .............. 73
bug reporting, in Command Center ...............104 Command Center platform ....................... 74
Delivery Channels .................................. 42
connectors .................................................. 56
C
callback and cleanup threads ........................79
callback URL ...............................................43 D
for Command Center ...............................43 databases
for Fulfillment Delivery Service ..................43 clean-up, for Fulfillment Delivery Service .... 82
cluster logging .............................................73 configuring for Command Center .............. 52
clustering ....................................................61 configuring for Delivery Engine ................ 76
CMIS delivery channel ..................................42 configuring for Fulfillment Delivery Service . 81
Command Center ................................... 10, 24 creating for Command Center .................. 14
bug reporting .......................................104 creating for Delivery Engine ..................... 14
callback URL ..........................................43 creating for Delivery Manager ................. 14
commands .............................................35 creating for Fulfillment Delivery Service ..... 14
common issues .....................................103 migrating for Command Center ................ 31
database migration .................................31 requirements .................................... 86 , 87
deploying ..............................................26 delivery channels
deployment preparation ...........................26 configuring ............................................ 42
HTTP settings ..........................................75 requirements .......................................... 42
HTTPS settings ........................................75 Delivery Engine ..................................... 11 , 37
installation check list ...............................24 common issues ..................................... 105
installing ...............................................25 communicating with ................................ 42
licenses .................................................13 deploying ............................................. 38
migrating ..............................................31 deploying with JBoss ............................... 39
package file contents ..............................25 deploying with Tomcat ............................ 40
platform configuration .............................74 deploying with WebLogic ........................ 39
securing communication with .............. 28, 30 deploying with WebSphere ..................... 39
TLS encryption ........................................75 installing ............................................... 37
Command Center Data Channels preparing for deployment ........................ 38
configuring ...................................... 64, 73 validating installation .............................. 41
deploying ..............................................29 Delivery Manager ........................................ 10
running on a separate domain ..................29 licenses ................................................ 13
watch folder ..........................................64 overview ............................................... 10
Command Center WebGUI system requirements ................................ 13
deploying ..............................................28
running on a separate domain ..................29

Index
Delivery Manager Configuration Console ........48 HTTP

completing configuration .........................49 settings for Command Center ................... 75
deploying ..............................................49 HTTPS settings, for Command Center .............. 75
exporting settings from ............................49
importing settings into .............................49
installing ...............................................48
I
restoring default settings ..........................49
INIFILE ....................................................... 97
saving settings in ....................................49
installing
delivery report
Command Center ................................... 25
configuring for Command Center ..............60
Delivery Engine ...................................... 37
configuring for Fulfillment Delivery Service ..81
Delivery Manager ................. 25 , 37, 46, 48
deploying
Delivery Manager Configuration Console .. 48
Command Center Data Channels ..............29
Fulfillment Delivery Service ...................... 46
Command Center WebGUI ......................28
Delivery Engine ......................................38
Delivery Manager Configuration Console ...49
Fulfillment Delivery Service .......................46 J
Java Content Repository ................................ 96
Java content repository (JCR) ................... 65 , 78
JBoss requirements ....................................... 88
E
JMS
engine pool
delivery channel ..................................... 42
logging .................................................72
dependencies ........................................ 17
management ..........................................56
provider ................................................ 69
slot logging ...........................................72
settings, for Command Center .................. 74
xml file ..................................................98
settings, for Delivery Engine ..................... 77
EWS
JMS CallBack module ................................... 60
configuring for Fulfillment Delivery Service ..83
JNDI context for datasources ......................... 76
document composition mode ....................22
job logging ................................................. 71
ExactTarget query ........................................79
job management ......................................... 66
F L
failback, for clustering ..................................61
license keys
failover, for clustering ...................................61
expiration ............................................. 16
FDS filestore ................................................83
renewal ................................................ 16
file descriptor requirements ............................87
licenses
FTP/FTPS delivery channel .............................42
configuring for Command Center .............. 51
Fulfillment Delivery Service ...................... 12, 46
configuring for Fulfillment Delivery Service . 80
callback URL ..........................................43
logging
common issues .....................................105
cluster logging ....................................... 73
deploying ..............................................46
engine pool logging ............................... 72
filestore .................................................83
engine pool slot logging .......................... 72
installing ...............................................46
general logging ..................................... 70
licenses .................................................80
job logging ........................................... 71
schedule entity logging ........................... 71
LPR/LPD delivery ......................................... 64
G
general logging ...........................................70
Granting All Privileges ..................................96
M
MBean
instances ............................................... 88
H thread pool ........................................... 88
HP Exstream Production Engine ......................55 memory requirements ................................... 86

Index
O S
operating system schedule entity logging ................................. 71
patches ........................................... 17, 21 securing communication
requirements for Command Center ............17 Command Center ........................28 , 30, 75
requirements for Delivery Engine ...............19 Command Center client side .................... 31
requirements for Fulfillment Delivery Service 19 Command Center server side ................... 30
operation mode, for Delivery Engine ...............80 Command Center Web connection ........... 31
output document storage ...............................77 SMPP delivery channel ................................. 42
SMTP-Email delivery channel ......................... 42
SMTP-SMS delivery channel .......................... 42
SOAP/REST delivery channel ........................ 42
P
SSL communication ...................................... 30
package file contents
for Command Center on Apache Tomcat .... 28
Command Center ...................................25
system requirements
Delivery Manager .................................. 13
R
realtime
T
composition mode ..................................23
temp storage ............................................... 77
configuration, for Fulfillment Delivery Service 83
TLS Encryption
util folder .............................................101
for Command Center .............................. 75
requirements
troubleshooting ......................................... 103
delivery channel-specific ..........................42
Command Center ................................. 103
licenses .................................................13
Delivery Engine .................................... 105
RMI
Fulfillment Delivery Service .................... 105
provider ................................................70
settings .................................................73
W
watch folder settings .................................... 74
Web container requirements ......................... 23

Installation and Configuration Guide: HP Exstream Delivery Manager HP Exstream Command Center

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation and Configuration Guide: HP Exstream Delivery Manager HP Exstream Command Center

Uploaded by

Copyright:

Available Formats

HP Exstream Delivery Manager

Installation and Configuration

Copyright © 2008, The Chromium Authors All rights reserved.

© Copyright 1999-2009 The Apache Software Foundation

Copyright (c) 2000-2005 INRIA, France Telecom All rights reserved.

Copyright (c) 2003-2007, Terence Parr All rights reserved.

Copyright (c) 2001-2004 The OpenSymphony Group. All rights reserved.

Copyright (c) 1989, 1999 Free Software Foundation, Inc.

Copyright (c) 2006-2007, XStream Committers All rights reserved.

Copyright (c) 2004-2008 QOS.ch All rights reserved.

© Copyright 2002-2010 NextApp, Inc.

Copyright (C) 2005 JGraph.com. All rights reserved.

Copyright © 2010 The Eclipse Foundation. All Rights Reserved.

Copyright ©1999, 2009 Tanuki Software, Ltd. All Rights Reserved.

Copyright 1994-2006 Sun Microsystems, Inc.

Copyright ©2000-2005 INRIA, France Telecom All rights reserved.

© Copyright 2010 SpringSource. All Rights Reserved.

Copyright © 2006. Adobe Systems Incorporated. All rights reserved.

Copyright 2009 Day Management AG

Copyright © 2002 JSON.org

Copyright © 1996-2001 Logica Mobile Networks Limited, all rights reserved.

Copyright 2002-2005, the Displaytag team

© 2007-2009 Object Refinery Limited

The MIT License (MIT) Copyright ©

Apache Tomcat is trademarks of the Apache Software Foundation

UNIX® is a registered trademark of The Open Group.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

HP and HP-UX are trademarks or registered trademarks of Hewlett-Packard Company

Oracle is a registered trademark of Oracle Corporation

RED HAT is a registered trademark of Red Hat, Inc.

Solaris is a trademark of Sun Microsystems, Inc.

JBOSS is a registered trademark of Red Hat, Inc.

About HP Exstream Delivery Manager ...................................................... 10

About HP Exstream Delivery Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About HP Exstream Fulfillment Delivery Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

HP Exstream Delivery Manager System Requirements ............................... 13

HP Exstream Delivery Manager Application (Web) Server Requirements . . . . . . . . . . . . . . . . . . . . . . . . 14

HP Exstream Delivery Manager Database Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

HP Exstream Command Center-Specific Requirements . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

HP Exstream Delivery Engine-Specific System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

HP Exstream Fulfillment Delivery Service-Specific System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installing and Deploying Command Center ............................................... 24

Installation and Configuration Guide 6

Command Center Package File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Installing Command Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Preparing for Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Deploying Command Center WebGUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Deploying Command Center Data Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Securing Communication with Command Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Command Center 2.2.0 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Command Center Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Installing and Deploying the HP Exstream Delivery Engine ......................... 37

Installing the HP Exstream Delivery Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Deploying the HP Exstream Delivery Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Validating the HP Exstream Delivery Engine Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Configuring the HP Exstream Delivery Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Enabling Communication with the HP Exstream Delivery Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

HP Exstream Delivery Engine 1.2.0 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Installation and Configuration Guide 7

Installing and Deploying HP Exstream Fulfillment Delivery Service ............. 46

Installing and Deploying HP Exstream Fulfillment Delivery Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

HP Exstream Delivery Manager Configuration Console .............................. 48

Deploying the HP Exstream Delivery Manager Configuration Console . . . . . . . . . . . . . . . . . . . . . . . . . . 49