Savvion BPM Installation Guide

Progress Savvion BusinessManager 7.6.
4:
Installation Guide
Notices
For details, see the following topics:
Documentation copyright notice
Third-party acknowledgments
Documentation copyright notice

2012 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.
These materials and all Progress software products are copyrighted and all rights are reserved
by Progress Software Corporation. The information in these materials is subject to change without
notice, and Progress Software Corporation assumes no responsibility for any errors that may
appear therein. The references in these materials to specific platforms supported are subject to
change.
Savvion BusinessManager: Installation Guide: Version 7.6.4
Notices
Actional, Apama, Artix, Business Empowerment, Business Making Progress, Corticon, Corticon
(and design), DataDirect (and design), DataDirect Connect, DataDirect Connect64, DataDirect
Technologies, DataDirect XML Converters, DataDirect XQuery, DataXtend, Dynamic Routing
Architecture, Empowerment Center, Fathom, Fuse Mediation Router, Fuse Message Broker, Fuse
Services Framework, IONA, Making Software Work Together, Mindreef, ObjectStore, OpenEdge,
Orbix, PeerDirect, Powered by Progress, PowerTier, Progress, Progress DataXtend, Progress
Dynamics, Progress Business Empowerment, Progress Empowerment Center, Progress
Empowerment Program, Progress OpenEdge, Progress Profiles, Progress Results, Progress
Software Business Making Progress, Progress Software Developers Network, Progress Sonic,
ProVision, PS Select, RulesCloud, RulesWorld, Savvion, SequeLink, Shadow, SOAPscope,
SOAPStation, Sonic, Sonic ESB, SonicMQ, Sonic Orchestration Server, SpeedScript, Stylus Studio,
Technical Empowerment, WebSpeed, Xcalia (and design), and Your Software, Our
TechnologyExperience the Connection are registered trademarks of Progress Software Corporation
or one of its affiliates or subsidiaries in the U.S. and/or other countries. AccelEvent, Apama
Dashboard Studio, Apama Event Manager, Apama Event Modeler, Apama Event Store, Apama
Risk Firewall, AppsAlive, AppServer, ASPen, ASP-in-a-Box, BusinessEdge, Cache-Forward,
CloudEdge, DataDirect Spy, DataDirect SupportLink, Fuse, FuseSource, Future Proof, GVAC,
High Performance Integration, Integration Everywhere, ObjectStore Inspector, ObjectStore
Performance Expert, OpenAccess, Orbacus, Pantero, POSSE, ProDataSet, Progress Arcade,
Progress CloudEdge, Progress Cloudware, Progress Control Tower, Progress ESP Event Manager,
Progress ESP Event Modeler, Progress Event Engine, Progress RFID, Progress RPM, Progress
Responsive Cloud, Progress Responsive Process Management, Progress Software, PSE Pro,
SectorAlliance, SeeThinkAct, Shadow z/Services, Shadow z/Direct, Shadow z/Events, Shadow
z/Presentation, Shadow Studio, SmartBrowser, SmartComponent, SmartDataBrowser,
SmartDataObjects, SmartDataView, SmartDialog, SmartFolder, SmartFrame, SmartObjects,
SmartPanel, SmartQuery, SmartViewer, SmartWindow, Sonic Business Integration Suite, Sonic
Process Manager, Sonic Collaboration Server, Sonic Continuous Availability Architecture, Sonic
Database Service, Sonic Workbench, Sonic XML Server, The Brains Behind BAM, WebClient,
and Who Makes Progress are trademarks or service marks of Progress Software Corporation
and/or its subsidiaries or affiliates in the U.S. and other countries. Java is a registered trademark
of Oracle and/or its affiliates. Any other marks contained herein may be trademarks of their
respective owners.
Notices
Third-party acknowledgments
Progress Savvion v7.6.4 incorporates Apache Avalon 2002/08/06, Apache Jakarta Commons
v1.0.2, Apache Batik v1.1, Apache Jakarta POI v1.1, Apache POI 2003/05/14, Apache Jasper
Regexp v1.2, xmltask 1.15.1, from The Apache Software Foundation. Such technologies are subject
to the following terms and conditions: The Apache Software License, Version 1.1 Copyright (c)
2000 The Apache Software Foundation. All rights reserved. Redistribution and use in source and
binary forms, with or without modification, are permitted provided that the following conditions are
met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions
and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution. 3. The end-user documentation included with the redistribution, if
any, must include the following acknowledgment: "This product includes software developed by
the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may
appear in the software itself, if and wherever such third-party acknowledgments normally appear.
4.The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote
products derived from this software without prior written permission. For written permission, please
contact apache@apache.org. 5. Products derived from this software may not be called "Apache",
nor may "Apache" appear in their name, without prior written permission of the Apache Software
Foundation. THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN
NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by
many individuals on behalf of the Apache Software Foundation. For more information on the Apache
Software Foundation, please see (http://www.apache.org/). Portions of this software are based
upon public domain software originally written at the National Center for Supercomputing
Applications, University of Illinois, Urbana-Champaign.
Notices
Progress Savvion v7.6.4 incorporates Apache JAXP v1.3.04 from The Apache Software Foundation.
Such technology is subject to the following terms and conditions: The Apache Software License,
Version 1.1 Copyright (c) 1999-2003 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted
provided that the following conditions are met: 1. Redistributions of source code must retain the
above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in
binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution. 3.The end-user
documentation included with the redistribution, if any, must include the following acknowledgment:
"This product includes software developed by the Apache Software Foundation
(http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if
and wherever such third-party acknowledgments normally appear. 4. The names "Xalan" and
"Apache Software Foundation" must not be used to endorse or promote products derived from
this software without prior written permission. For written permission, please contact
apache@apache.org. 5. Products derived from this software may not be called "Apache", nor may
"Apache" appear in their name, without prior written permission of the Apache Software Foundation.
THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software
consists of voluntary contributions made by many individuals on behalf of the Apache Software
Foundation and was originally based on software copyright (c) 1999, Lotus Development
Corporation., http://www.lotus.com. For more information on the Apache Software Foundation,
please see http://www.apache.org/.
Notices
Progress Savvion v7.6.4 incorporates Apache LogKit v1.2 from The Apache Software Foundation.
Such technologies are subject to the following terms and conditions: The Apache Software License,
Version 1.1 -- Copyright (C) 1997-2003 The Apache Software Foundation. All rights reserved.
provided that the following conditions are met: 1. Redistributions of source code must retain the
above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in
binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution. 3.The end-user
documentation included with the redistribution, if any, must include the following acknowledgment:
"This product includes software developed by the Apache Software Foundation
(http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if
and wherever such third-party acknowledgments normally appear. 4. The names "LogKit", "Jakarta"
and "Apache Software Foundation" must not be used to endorse or promote products derived from
this software without prior written permission. For written permission, please contact
apache@apache.org. 5. Products derived from this software may not be called "Apache", nor may
"Apache" appear in their name, without prior written permission of the Apache Software Foundation.
APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
(INCLUDING,BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software
consists of voluntary contributions made by many individuals on behalf of the Apache Software
Foundation. For more information on the Apache Software Foundation, please see
(http://www.apache.org/).
Progress Savvion v7.6.4 incorporates jfor v0.7.2 from jfor. Such technology is subject to the following
terms and conditions: jfor Apache- Style Software License. Copyright (c) 2002 by the jfor project.
All rights reserved. Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met: 1. Redistributions of source code
must retain the above copyright notice, this list of conditions and the following disclaimer. 2.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimer in the documentation and/or other materials provided with the
distribution. 3. The end-user documentation included with the redistribution, if any, must include
the following acknowledgment: "This product includes software developed by the jfor project
(http://www.jfor.org)." Alternately, this acknowledgment may appear in the software itself, if and
wherever such third-party acknowledgments normally appear. 4. The name "jfor" must not be used
to endorse or promote products derived from this software without prior written permission. For
written permission, please contact info@jfor.org. 5. Products derived from this software may not
be called "jfor", nor may "jfor" appear in their name, without prior written permission of info@jfor.org.
JFOR PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Notices
Progress Savvion v7.6.4 incorporates ANTLR Runtime v3.1.1 from antlr.org. Such technology is
subject to the following terms and conditions: SOFTWARE RIGHTS $Id:
//depot/code/org.antlr/main/main/RIGHTS#3 $ ANTLR 1989-2000 Developed by jGuru.com
(MageLang Institute), http://www.ANTLR.org and http://www.jGuru.com.
Progress Savvion v7.6.4 incorporates DOM4J v1.6.1 from MetaStuff, Ltd. Such technology is
subject to the following terms and conditions: Copyright 2001-2005 (C) MetaStuff, Ltd. All Rights
Reserved. Redistribution and use of this software and associated documentation ("Software"),
with or without modification, are permitted provided that the following conditions are met: 1.
Redistributions of source code must retain copyright statements and notices. Redistributions must
also contain a copy of this document. 2. Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer in the documentation and/or
other materials provided with the distribution. 3. The name "DOM4J" must not be used to endorse
or promote products derived from this Software without prior written permission of MetaStuff, Ltd.
For written permission, please contact dom4j-info@metastuff.com. 4. Products derived from this
Software may not be called "DOM4J" nor may "DOM4J" appear in their names without prior written
permission of MetaStuff, Ltd. DOM4J is a registered trademark of MetaStuff, Ltd. 5. Due credit
should be given to the DOM4J Project - http://www.dom4j.org THIS SOFTWARE IS PROVIDED
BY METASTUFF, LTD. AND CONTRIBUTORS "AS IS" AND ANY EXPRESSED OR IMPLIED
NO EVENT SHALL METASTUFF, LTD. OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Progress Savvion v7.6.4 incorporates java.net args4j v2.0.12 from Kohsuke Kawaguchi. Such
technology is subject to the following terms and conditions: Copyright (c) 2003, Kohsuke Kawaguchi
All rights reserved. Redistribution and use in source and binary forms, with or without modification,
are permitted provided that the following conditions are met: *Redistributions of source code must
retain the above copyright notice, this list of conditions and the following disclaimer. *Redistributions
in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution. THIS
SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
POSSIBILITY OF SUCH DAMAGE.
Notices
Progress Savvion v7.6.4 incorporates Castor 0.9.3 from castor.org. Such technology is subject to
the following terms and conditions: Original Intalio license - Copyright 1999-2004 (C) Intalio Inc.,
and others. All Rights Reserved. Redistribution and use of this software and associated
documentation ("Software"), with or without modification, are permitted provided that the following
conditions are met: 1. Redistributions of source code must retain copyright statements and notices.
Redistributions must also contain a copy of this document. 2. Redistributions in binary form must
reproduce the above copyright notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution. 3. The name "ExoLab" must
not be used to endorse or promote products derived from this Software without prior written
permission of Intalio Inc. For written permission, please contact info@exolab.org. 4. Products
derived from this Software may not be called "Castor" nor may "Castor" appear in their names
without prior written permission of Intalio Inc. Exolab, Castor and Intalio are trademarks of Intalio
Inc. 5. Due credit should be given to the ExoLab Project (http://www.exolab.org/). THIS SOFTWARE
IS PROVIDED BY INTALIO AND CONTRIBUTORS "AS IS" AND ANY EXPRESSED OR IMPLIED
NO EVENT SHALL INTALIO OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
Progress Savvion v7.6.4 incorporates Gwt Ext User Extension v0.3 from GWT-Ext. Such technology
is subject to the following terms and conditions: Copyright(c) 2007-2008, GWT-Ext All rights
reserved. Redistribution and use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met: * Redistributions of source code must
retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions
in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution. * Neither the
name of the GWT-Ext nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED
BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Notices
Progress Savvion v7.6.4 incorporates Jaxen v1.1-beta-3 from jaxen.org. Such technology is subject
to the following terms and conditions: Project License $Id: LICENSE.txt 1128 2006-02-05 21:49:04Z
elharo $ Copyright 2003-2006 The Werken Company. All Rights Reserved. Redistribution and use
in source and binary forms, with or without modification, are permitted provided that the following
conditions are met: * Redistributions of source code must retain the above copyright notice, this
list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the
above copyright notice, this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution. * Neither the name of the Jaxen Project nor
the names of its contributors may be used to endorse or promote products derived from this software
without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT
HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
Progress Savvion v7.6.4 incorporates Looks v2.1.2 from JGoodies. Such technology is subject to
the following terms and conditions: The BSD License for the JGoodies Looks - Copyright (c)
2001-2007 JGoodies Karsten Lentzsch. All rights reserved. Redistribution and use in source and
binary forms, with or without modification, are permitted provided that the following conditions are
met: o Redistributions of source code must retain the above copyright notice, this list of conditions
and the following disclaimer. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution. Neither the name of JGoodies Karsten Lentzsch nor the names of
its contributors may be used to endorse or promote products derived from this software without
specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS
AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;
OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Progress Savvion v7.6.4 incorporates slf4j v1.5.6 from sfl4j.org. Such technology is subject to the
following terms and conditions: Copyright (c) 2004-2007 QOS.ch All rights reserved. Permission
is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without
limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do so, subject to the
following conditions: The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH
THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
10
Notices
Progress Savvion v7.6.4 incorporates XStream v1.3.1 from XStream. Such technology is subject
to the following terms and conditions: Copyright (c) 2003-2006, Joe Walnes Copyright (c) 2006-2007,
XStream Committers All rights reserved. Redistribution and use in source and binary forms, with
or without modification, are permitted provided that the following conditions are met: Redistributions
of source code must retain the above copyright notice, this list of conditions and the following
disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials provided with
the distribution. Neither the name of XStream nor the names of its contributors may be used to
endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
Progress Savvion v7.6.4 incorporates Xpp3 v1.1.3.4 from Indiana University. Such technology is
subject to the following terms and conditions: Indiana University Extreme! Lab Software License
Version 1.1.1 Copyright (c) 2002 Extreme! Lab, Indiana University. All rights reserved. Redistribution
and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met: 1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must
reproduce the above copyright notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution. 3. The end-user documentation
included with the redistribution, if any, must include the following acknowledgment: "This product
includes software developed by the Indiana University Extreme! Lab
(http://www.extreme.indiana.edu/)." Alternately, this acknowledgment may appear in the software
itself, if and wherever such third-party acknowledgments normally appear. 4. The names "Indiana
University" and "Indiana University Extreme! Lab" must not be used to endorse or promote products
derived from this software without prior written permission. For written permission, please contact
http://www.extreme.indiana.edu/. 5. Products derived from this software may not use "Indiana
University" name nor may "Indiana University" appear in their name, without prior written permission
of the Indiana University. THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NO EVENT SHALL THE AUTHORS, COPYRIGHT HOLDERS OR ITS CONTRIBUTORS BE
11
Notices
Progress Savvion v7.6.4 incorporates Suns Jmaki framework v1.0, Suns Jmaki framework v1.0.3,
and Sun's Jmaki framework v1.8.0 from Sun Microsystems, Inc. Such technology is subject to the
following terms and conditions: Copyright 1994-2006 Sun Microsystems, Inc. All Rights Reserved.
provided that the following conditions are met: * Redistribution of source code must retain the
above copyright notice, this list of conditions and the following disclaimer. * Redistribution in binary
form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution. Neither the name of
Sun Microsystems, Inc. or the names of contributors may be used to endorse or promote products
derived from this software without specific prior written permission. This software is provided "AS
IS," without a warranty of any kind. ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE HEREBY EXCLUDED. SUN MICROSYSTEMS, INC. ("SUN") AND ITS LICENSORS SHALL
NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING,
MODIFYING OR DISTRIBUTING THIS SOFTWARE OR ITS DERIVATIVES. IN NO EVENT WILL
SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR
DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES,
HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF
THE USE OF OR INABILITY TO USE THIS SOFTWARE, EVEN IF SUN HAS BEEN ADVISED
OF THE POSSIBILITY OF SUCH DAMAGES.You acknowledge that this software is not designed,
licensed or intended for use in the design, construction, operation or maintenance of any nuclear
facility.
Progress Savvion v7.6.4 incorporates Mozilla Rhino v1.6 R1 and Saxon-B v8.9. Such technology
is subject to the following terms and conditions: The contents of this file are subject to the Mozilla
Public License Version 1.1 (the "License") provided below; you may not use this file except in
compliance with the License. You may also obtain a copy of the License at
http://www.mozilla.org/MPL/. Software distributed under the License is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the
specific language governing rights and limitations under the License. The Original Code is Rhino
code, released - May 6, 1999. - The Initial Developer of the Original Code is Netscape
Communications Corporation. Portions created by Netscape are Copyright (C) 1997-1999 Netscape
Communications Corporation. All Rights Reserved. Contributor(s): Norris Boyd, Igor Bukanov,
Roger Lawrence, Mike McCabe. (for Mozilla Rhino v1.6 R1) The Original Code is: All this file. The
Initial Developer of the Original Code is Michael H. Kay. Contributor(s): none. (for Saxon-B v8.9).
Progress Savvion v7.6.4 incorporates BeanShell v1.2b8. Sun Public License Notice: The contents
of this file are subject to the Sun Public License Version 1.0 (the "License"); you may not use this
file except in compliance with the License. A copy of the License is available at http://www.sun.com.
The Original Code is BeanShell. The Initial Developer of the Original Code is Pat Niemeyer. Portions
created by Pat Niemeyer are Copyright (C) 2000. All Rights Reserved. GNU Public License Notice:
Alternatively, the contents of this file may be used under the terms of the GNU Lesser General
Public License (the "LGPL"), in which case the provisions of LGPL are applicable instead of those
above. If you wish to allow use of your version of this file only under the terms of the LGPL and
not to allow others to use your version of this file under the SPL, indicate your decision by deleting
the provisions above and replace them with the notice and other provisions required by the LGPL.
If you do not delete the provisions above, a recipient may use your version of this file under either
the SPL or the LGPL.
12
Notices
Progress Savvion v7.6.4 incorporates LALR Parser Generator in Java v0.10k. Such technology is
subject to the following terms and conditions: CUP Parser Generator Copyright Notice, License,
and Disclaimer Copyright 1996-1999 by Scott Hudson, Frank Flannery, C. Scott Ananian Permission to use, copy, modify, and distribute this software and its documentation for any purpose
and without fee is hereby granted, provided that the above copyright notice appear in all copies
and that both the copyright notice and this permission notice and warranty disclaimer appear in
supporting documentation, and that the names of the authors or their employers not be used in
advertising or publicity pertaining to distribution of the software without specific, written prior
permission. The authors and their employers disclaim all warranties with regard to this software,
including all implied warranties of merchantability and fitness. In no event shall the authors or their
employers be liable for any special, indirect or consequential damages or any damages whatsoever
resulting from loss of use, data or profits, whether in an action of contract, negligence or other
tortious action, arising out of or in connection with the use or performance of this software.
13
Notices
14
Table of Contents
Preface...........................................................................................................19
About this documentation......................................................................................................................19
User types.............................................................................................................................................19
Information on documentation...............................................................................................................20
Conventions used in this manual...........................................................................................................21
Product Support contact information.....................................................................................................22
Chapter 1: Savvion BusinessManager overview.......................................23

BusinessManager components.............................................................................................................25
How BusinessManager works...............................................................................................................27
BusinessManager user types................................................................................................................28
Chapter 2: Introduction to installation........................................................31

Evaluation license..................................................................................................................................32
Terminology used..................................................................................................................................32
Chapter 3: Before installing BusinessManager.........................................35

Verifying system requirements..............................................................................................................35
Understanding the product information files..........................................................................................37
Preparing your database.......................................................................................................................37
Oracle 10g/11g enterprise edition, Oracle Express 10g, Oracle 11g/10g (RAC).......................38
Modifying maximum number of connections for Oracle Express edition....................................38
MS SQL server 2005, MS SQL server 2008..............................................................................38
IBM DB2.....................................................................................................................................39
OpenEdge 10.2B........................................................................................................................39
Organizing your system information......................................................................................................39
Chapter 4: Installing BusinessManager 7.6.4............................................43

Prerequisites for installation..................................................................................................................44
Installing BusinessManager using the installer.....................................................................................44
Specifying directory location.......................................................................................................45
Specifying local machine details.................................................................................................45
Specifying admin credentials .....................................................................................................46
Specifying processor type..........................................................................................................47
Selecting application server........................................................................................................47
Configuring BusinessManager security settings.........................................................................48
15
Specifying application server details..........................................................................................49

Specifying BusinessManager Portal URL...................................................................................55
Configuring email properties......................................................................................................56
Specifying User Management Realm details..............................................................................57
Specifying database details........................................................................................................59
Specifying JDK location..............................................................................................................64
Specifying shortcut for Windows operating system....................................................................66
Using the silent installation utility...........................................................................................................66
Recording the BusinessManager installation.............................................................................67
Installing with the silent installation utility...................................................................................67
Verifying the installation.........................................................................................................................68
Chapter 5: After installing BusinessManager 7.6.4...................................69

Configuring SBM for Oracle RAC..........................................................................................................70
Modifying SBM configuration files...............................................................................................70
Modifying Oracle sequence for BizEvent table...........................................................................71
Modifying WebLogic 10.3.0 data sources...................................................................................71
Modifying JBoss datasources.....................................................................................................72
Creating profile, servers and resources for WebSphere........................................................................74
Enabling MS SQL server for JDBC distributed transactions..................................................................75
Enabling XA transactions on Windows 7....................................................................................76
Setting up temporary table space for DB2.............................................................................................78
Initializing BusinessManager database repository................................................................................78
Creating BusinessManager database........................................................................................78
Additional steps for OpenEdge..............................................................................................................80
Starting servers.....................................................................................................................................81
Starting EJB and Portal servers.................................................................................................81
Starting BizLogic and BizPulse servers......................................................................................81
Verifying BusinessManager installation.................................................................................................82
Stopping servers...................................................................................................................................83
Chapter 6: Installing BusinessManager service pack 7.6.4......................85

Prerequisites.........................................................................................................................................85
Installing service pack 7.6.4..................................................................................................................86
After installing service pack 7.6.4..........................................................................................................87
Silent installation for service pack 7.6.4................................................................................................88
Enabling ApacheDS for SBM................................................................................................................88
Chapter 7: Setting up BusinessManager as service ................................91

Installing BusinessManager as a Windows service...............................................................................91
Install SBM Pramati services......................................................................................................92
Install SBM WebLogic services..................................................................................................92
Install SBM JBoss services........................................................................................................93
16
Removing Windows services......................................................................................................93

Monitor or Control SBM services................................................................................................94
Running BusinessManager as a Daemon in Linux ...............................................................................95
BusinessManager as a Daemon on JBoss.................................................................................95
Chapter 8: Uninstalling BusinessManager.................................................97

Before uninstalling.................................................................................................................................98
Using the Uninstaller.............................................................................................................................98
Using the silent uninstallation utility.....................................................................................................100
Recording the BusinessManager uninstallation.......................................................................100
Uninstalling with the silent uninstallation utility.........................................................................100
After uninstalling..................................................................................................................................101
Appendix A: Supported platforms and configurations...........................103

BusinessManager supported platforms...............................................................................................103
BusinessManager supported configurations.......................................................................................105
BusinessManager supported databases.............................................................................................108
Appendix B: Sample scripts for creating your database........................113

Sample scripts for Oracle 10g/11g enterprise edition, Oracle Express 10g, Oracle 11g/10g (RAC)...113
Sample scripts forMS SQL Server 2005, MS SQL Server 2008.........................................................114
Sample scripts for IBM DB2................................................................................................................115
Sample scripts for OpenEdge 10.2B...................................................................................................116
Appendix C: Customizing temporary directory and log level for installer.119

Customizing temporary directory.........................................................................................................119
Customizing log levels.........................................................................................................................120
Appendix D: Using BusinessManager command line utilities...............121

Initializing BusinessManager repository..............................................................................................121
Initializing specific BusinessManager components..................................................................121
Starting and stopping application servers...........................................................................................122
Pramati application server........................................................................................................122
WebLogic application server.....................................................................................................123
WebSphere application server..................................................................................................123
JBoss application server...........................................................................................................124
Starting and Stopping BusinessManager servers...............................................................................125
Starting BusinessManager servers...........................................................................................125
Stopping BusinessManager servers.........................................................................................125
17
Appendix E: Re-initializing BusinessManager database........................127

Re-initializing BusinessManager database.........................................................................................127
Appendix F: BizLogic and BizPulse auto-startup....................................129

BizLogic auto-startup...........................................................................................................................129
Disabling BizLogic auto-startup................................................................................................129
BizPulse auto-startup..........................................................................................................................130
Disabling BizPulse auto-startup................................................................................................130
Appendix G: Locating BusinessManager log files..................................131

Application server log files...................................................................................................................131
BusinessManager log files..................................................................................................................132
Appendix H: Setting up JBoss server to use SonicMQ as the JMS provider.133

Deploying the Sonic JCA adapter to JBoss.........................................................................................133
Testing the Sonic JCA deployment......................................................................................................134
Prerequisites for modifying Savvion to use Sonic JMS.......................................................................136
Modifying files in <SBM_HOME>........................................................................................................136
Appendix I: Configuring JBoss ports.......................................................141

For embedded JBoss..........................................................................................................................141
For JBoss enterprise edition 5.0.1.......................................................................................................142
Glossary......................................................................................................145
Index............................................................................................................151
18
Preface
About this documentation
User types
Information on documentation
Conventions used in this manual
Product Support contact information
About this documentation

This guide is part of the documentation set for Progress Savvion BusinessManager, version 7.6.4.
User types
Progress Savvion BusinessManager is a business process management system that can be used
by the following types of users:
19
Preface
User type
Application User
Responsibilities
Responsible for carrying out specific business tasks using
BusinessManager applications. Examples include:
An office administrator submitting an online purchase request.

HR personnel scheduling interviews for a potential hire.
A sales representative responding to a customer request.
An engineer reviewing a trouble ticket reported by a customer.
Manager
Responsible for automating business processes in a particular business

domain. BPM Portals Management module serves as the primary
interface to BusinessManager for the Manager, enabling the manager
to monitor, analyze, and control business processes. Also uses the
Process Modeler for modeling and simulation.
Application Developer Responsible for creating customized applications for implementing

business processes and developing interfaces associated with tasks.
Application developers may work closely with Managers to define the
requirements of an application, and determine the business processes.
BusinessManager
Administrator
Responsible for configuring BusinessManager components, managing

user/group profiles, maintaining the SBM environment, setting up and
managing cluster and administering BusinessManager utilities.
Information on documentation
This documentation contains information for the entire range of Progress Savvion BusinessManager
users. In the following table, we recommend the guides that are most relevant to each type of user.
If you are the
Application User
Read the
BPM Portal Users Guide
First Steps Guide
Terminology Guide
Tutorial Guide
Manager
BPM Portal Managers Guide

Terminology Guide
Tutorial Guide
20
Preface
If you are the

Application Developer
Read the
Application Developers Guide
BizLogic Developers Guide
BizPulse Users Guide
BPM Studio Users Guide
Customization Guide
Managed Adapters Guide
First Steps Guide
Terminology Guide
Server Administrators Guide
Tutorial Guide
Web services Developers Guide
Javadocs
BusinessManager Administrator
BizPulse Users Guide

BPM Portal Administrators Guide
Installation Guide
Managed Adapters Guide
Clustering Guide
Terminology Guide
Server Administrators Guide
Troubleshooting Guide for Administrators
Conventions used in this manual

This document uses the following conventions and terminology notations.
Convention
Purpose
bold
Indicates titles of command buttons, checkboxes, options, lists, dialog

boxes, and portal page names.
file path
Indicates folder paths and filenames.
italic
monospace
Indicates book titles.

Represents code segments or examples.
21
Preface
Convention
Purpose
backward slash "\"
Indicates the path in Windows environment. For UNIX environment,

replace with forward slash "/"
SBM_HOME or
%SBM_HOME%
Represents the installation folder of BusinessManager.
Product Support contact information

If the product documentation does not provide a solution to your specific issue, or if you need
clarification on the issue, then contact our Product Support team.You can contact the team through
the Internet, telephone, or postal mail, as per the details provided in Table 1 on page 22.
Table 1: Product Support Contact Information
To contact by
Web site
Use
http://progresslink.progress.com/supportlink
If you are an existing customer, then you can log in to the above site for
product support. If you are a first time user, then you need to create an
account first.
Telephone
1-781-280-4999 for US, Latin America and Canada

1-781-280-4543 for the Product Support Fax Line
1
Postal Address
Progress Software Corporation

14 Oak Park Drive
Bedford, MA 01730, USA.
To enable us to quickly answer your questions, please provide the following information:
Your name, installation site address and the license key for BusinessManager software.
Your BusinessManager version and build number.
Your operating system, application server and browser, with version and service pack details,
if any.
Your database management system and version, and information on JVM and JDBC used.
22
For support telephone numbers and offices in your region, visit the support web site above. This contact
information is for customer support only.
1
Savvion BusinessManager overview
Progress Software Corporation is a leading global provider of automated business process
management solutions. The companys product, Progress Savvion BusinessManager (henceforth
referred to as Savvion BusinessManager, BusinessManager or SBM), is a comprehensive business
process management platform, which enables companies to quickly transform their business
processes into flexible and manageable Web applications, distributed over intranets, extranets,
and the Internet.
23
Chapter 1: Savvion BusinessManager overview
BusinessManager addresses every stage in the business life cycle: define, integrate, deploy,
monitor, analyze, improve, and control. By adopting an end-to-end approach, BusinessManager
incorporates all the key elements required to meet the ever-changing demands of e-business while
ensuring e-business success. By providing integrated management tools, BusinessManager lets
you monitor operations proactively, modifying automated processes dynamically based on changing
external operations online. An overview of a typical automated business process management
solutions is shown in Figure 1 on page 24.
Figure 1: BusinessManager overview
24
BusinessManager components
How BusinessManager works
BusinessManager user types
BusinessManager is a suite of integrated components that enables you to easily build intranet,
extranet, and Internet applications and manage your e-business. BusinessManager consists of
the following components as in Figure 2 on page 25:
Figure 2: BusinessManager components
Table 2: BusinessManager components

Component
Description
BPM Portal Home
The Home module of BPM Portal is the primary interface for application
users, enabling them to interact with BusinessManager applications.
Users can complete entries to various tasks and applications, and link
to the support infrastructure required to complete these tasks.
BPM Portal
Management
The Management module enables managers to query, report on, and

control processes and resources, visible only to the managers.
25
Component
26
Description
BPM Portal
Administration
The Administration module enables BusinessManager Administrators to

modify configuration parameters, manage user or group access control,
and install or uninstall BusinessManager applications.
Web services
This component allows application developers to: a) publish their

applications as Web services, and b) find and convert other available
Web services on the Internet into BusinessManager applications.
BizSolo
This component provides a framework for developing and implementing

Web-enabled workflow applications.
BPM Studio
This is the primary application development tool for BusinessManager,

which provides an Eclipse-based integrated development environment
in which users can create BPM projects, processes, Web applications,
and rule files.
Process Modeler
This tool is used to design templates for basic business processes, and
to run simulations of processes and individual worksteps. Users can also
save or retrieve processes from the process repository.
BizLogic
This is a flexible, lightweight, scalable workflow process engine for

intranets, extranets, and the Internet.
BizPulse
This open, event-driven rule engine is used to formulate and enforce

policies in business applications.

Figure 3 on page 27 provides an overview of the interaction between BusinessManager components.
Figure 3: How BusinessManager works
The following explanations correspond to the labels shown in Figure 3 on page 27, and describe
how the components operate.
1. BPM Studio and Process Modeler provide an integrated development environment (IDE) for
BusinessManager, where you can design and deploy business processes. The application
developer designs a process template (with the *.spt or *.swt extension) in the IDE that reflects
the business flow and other business process requirements. Business rules for the process
template can be defined using the Rule Editor, a BizPulse component that is launched with
BPM Studio.
2. The Web Container specifies a runtime environment for servlet-based portals that include BPM
Portal, BizSolo, and Web services. BPM Portal provides user interfaces for the Home,
Management, and Administration modules.
3. Once the process template is defined, BusinessManager Administrators use the Administration
module to install the business process on the BizLogic server. Administrators can also configure
BusinessManager components, manage user or group access control, and publish
BusinessManager applications as Web services. Once installed, users access applications
through servlets that pass the requests over an RMI/IIOP connection to the BizLogic server
within an EJB Container.
4. The EJB Container provides a runtime environment that executes and manages Java-based
program components that run on the server side of a client/server network. Within the EJB
Container are the BizLogic server and BizPulse server.
5. The BizLogic server writes events to event tables in the database. Each BPM process uses
JDBC to connect to database server as well as store events in the database. Within the BizLogic
27
server, BizStore uses JDBC to connect to the database server process and retrieve the events
deposited by the BizLogic process. BizStore interprets the events and populates the process
tables. These populated tables are used by BPM Portal modules.
6. Once the process template is installed as a BusinessManager application, application users
can use the Home module to do the following:
Access applications
Obtain information to perform their tasks
Launch the application to start process instances from the BizLogic server
7. Once the process template is installed as an BusinessManager application, managers can use
the Management module (if they have access privileges) to monitor execution of process
instances and create reports. Servlets receive requests from managers and pass them onto
the BizLogic server over an RMI/IIOP connection. Managers use the Report Builder to define
management reports that retrieve information through JDBC to the database server.
8. BizPulse is a rule-based event or message processing server that loads application rules and
executes them against the BizLogic and/or external events or messages. This server persists
data in the database for recovery and with the help of JDBC connects to the database.
9. Managed Adapters exchange information between BusinessManager applications and external
applications by converting BusinessManager-specific protocol to the protocol of an external
system such as a database or ERP system. When users add a Managed Adapter to a workstep,
they can define complex mapping between BusinessManager dataslots and adapter inputs or
outputs of the external application. At runtime when the workstep is executed, the Managed
Adapter sets the adapter inputs and configuration, and maps the outputs to the appropriate
output dataslots.
10. BizSolo is a run-time component that executes the presentation flows. This component provides
a Model, View, Controller (MVC) paradigm for developing presentation flow-based applications
and executing them in a Web container.
11. BusinessManagers Web services component allows BizLogic applications to be published as
Web services.
12. The relational database management system serves as a persistent store for all
BusinessManager data storage needs. BPM Portal and the servers connect to DBMS using
the JDBC driver.

There are four user types within BusinessManager, Application users, Managers, Application
developers, BusinessManager administrators.
User types
Each BusinessManager user type is defined below:
Application users Application Users use BusinessManager applications to coordinate

specific business tasks with another department within their company, with another company
within their organization, and/or with a business partner in another organization. The Home
28
module in BPM Portal serves as the primary interface in which Application Users run
BusinessManager applications.
Managers Managers are typically experts in a particular business domain, such as quality
assurance or human resources. They might need to work with managers from other groups in
automating some of the business procedures that these groups share.The Management module
in BPM Portal serves as the primary BusinessManager interface for business managers to
coordinate and integrate business processes, enabling them to exchange information with one
other, and to share functionality over such standard communication channels as the Internet
or e-mail.
Application developers Application developers are responsible for analyzing business

processes and developing interfaces associated with creating tasks or processes. Application
developers are often not domain experts themselves, but work closely with Managers to define
business processes and determine the requirements of an application. Application developers
use BPM Studio or Process Modeler to define the business process; the resulting process
template file is tested, simulated, deployed, and run as a BusinessManager application.
BusinessManager administrators BusinessManager administrators are responsible for

configuring BusinessManager components, managing user or group profiles and access control,
and installing or uninstalling BusinessManager applications.The Administration module in BPM
Portal serves as the primary interface for BusinessManager Administrators to administer
applications.
All BusinessManager user types can communicate by using one or more BusinessManager
applications. They can also communicate with external applications.
Examples include:
A QA department manager requesting the human resources department to approve the hiring
of a QA engineer.
HR personnel coordinating interview scheduling with a regional office in another state.

Engineers collaborating with a business partners engineering department to develop
specifications for an application.
29
30
2
Introduction to installation
BusinessManager is delivered in a ZIP file or on a CD-ROM with the content listed in Table 3 on
page 31.
Table 3: BusinessManager installation contents
Directory/File
Contents
Installer
For Windows ( Server 2003, and XP), Redhat Linux 5.5 and
SUSE Linux Enterprise Server 11, IBM AIX 6.1 TL6 SP3, and
Sun Solaris 10 installations.
Install.cmd and
Install.sh
Install.cmd for Windows installation and Install.sh for

2
UNIX installation
docs
The BusinessManager documentation set contains the following:
api folder containing Javadocs.

pdf folder containing all user guides in PDF format.
These documents explain how to use BusinessManager. For a
complete listing, see BusinessManager Documentation in the
Preface.
images, releasenotes.htm
The images folder contains images for the Release Notes file.
license.htm
This file contains the license agreement for end user.
license.xml
This file also contains the license agreement for end user in an
xml format. This file is used by the Installer wizard.
UNIX installation procedures apply to Solaris, AIX, and Linux operating system.
31
Chapter 2: Introduction to installation
Directory/File
Contents
buildInfo
This file contains Product version, Build number, and related

data.
readme.txt
This is a readme file that provides information about the

buildinfo file, the installation log file, and Installer command
line options.
The installer by default includes Pramati and JBoss Community edition application servers.
BusinessManager can be installed on any one of these application servers or on any other supported
application server.
For supported platforms, and supported configurations, see Supported platforms and configurations
on page 103.
Evaluation license
Terminology used
Evaluation license
The evaluation license file is installed automatically by BusinessManager. The evaluation version
expires after 90 days. Contact Progress to upgrade to a full license. You may obtain the expiration
date from the expiration date attributes in the license file. The BusinessManager license file
is in XML format and is stored as license.xml in <SBM_HOME>/conf directory.
A license file based on the sales contract or an extended evaluation license file may be obtained
from a Progress sales representative, once the evaluation license file has expired. At
BusinessManager start up, the license file validity and expiration are checked. If your license file
has expired or damaged, then you cannot use Progress Savvion BusinessManager.
If you are using an evaluation version of BusinessManager, then you are licensed for 15 concurrent
Home sessions and 15 concurrent Management sessions. All other modules receive unlimited
sessions. A user logged in is considered a single session and uses a single license. A user logged
in multiple times with the same user name uses the corresponding number of sessions.The license
remains in use until the user logs out. After a period of inactivity (the length of time depends on
the application server), the session expires, requiring the user to login again. If the session expires,
then the license becomes available for use by another user.
Terminology used
Some of the terms used in this guide are listed below:
<BM_INSTALLER_HOME>: The directory where BusinessManager installer is extracted.

<SBM_HOME>: BusinessManager Installation directory.
<WEBLOGIC_SBM_DOMAIN_HOME>: The location of WebLogic domain for BusinessManager.
For example, C:\bea\user_projects\sbm75
<WEBSPHERE_HOME>: The directory where WebSphere application server is installed.
32
Terminology used
<JBOSS_HOME>: The directory where JBoss server is installed.

<PLUGIN_HOME>: The directory where WebSphere Proxy server plug-in is installed.
<HTTP_SERVER_HOME>: The directory where WebSphere HTTP server is installed.
<APACHE_HOME>: The directory where Apache HTTP server is installed.
33
Chapter 2: Introduction to installation
34
3
Before installing BusinessManager
This chapter describes the tasks you need to perform before you begin the BusinessManager
installation. They include:
Verifying System Requirements

Understanding the Product Information Files
Preparing your Database
Organizing your System Information
Verifying system requirements
Understanding the product information files
Preparing your database
Organizing your system information
Verifying system requirements

Table 4 on page 36 describes the minimum and recommended requirements for installing and
running BusinessManager 7.6.1 on Windows and UNIX (Procedures described under the UNIX
heading apply to the Solaris, AIX, and Linux operating system).
35
Chapter 3: Before installing BusinessManager
Table 4: System requirements

Equipment
Minimum
Processor
Recommended
Pentium IV 1GHz or
UltraSPARC-III 900 MHz
Dual CPU Pentium IV 1GHz & up orDual CPU

UltraSPARC-III 900 MHz and up
2 GB RAM
2 GB of RAM
Free disk space
2GB
2 GB and above. Depending on the application

server you are using, you may need additional
free disk space.
Peripherals
CD-ROM
CD-ROM
Memory
Table 5 on page 36 lists the software that must be installed on your system before you install
BusinessManager 7.6.1. If the required software is not already installed on your system, then install
them in the order listed.
Table 5: Software requirements
Software
Application server
Notes
Pramati 6.0 SP4 (embedded in BusinessManager)
WebLogic 10.3.0
WebSphere 6.1.0.31 or WebSphere 7.0.0.13
JBoss Community Edition 5.1 (embedded in BusinessManager)
and JBoss Enterprise Application Platform 5.0.1
Microsoft Internet Explorer

7.0/8.0 or Mozilla FireFox 3.6
Microsoft Internet Explorer is only supported on Windows. You

need to disable MS JVM. Both browsers require Java plugin (JRE
1.5.0).
Mozilla FireFox is supported on both, Windows and Solaris.
Requires Java plugin (JRE 1.5.0).
Oracle 10g, Oracle 10g

Express Edition, and Oracle
11g
or
Microsoft SQL Server 2005
or
Microsoft SQL Server 2008
or
IBM DB2 9.5
36
Before you install BusinessManager, have the database up and

running.If you are running an OCI driver, then you must install
the Oracle client on the machine where BusinessManager is
installed. For the thin driver, the Oracle client is not required.
Use MS Windows Server 2003 Standard/Enterprise R2. Both
case-sensitive and case-insensitive instances are supported.
Use MS Windows Server 2008 Standard/Enterprise R2. Both
case-sensitive and case-insensitive instances are supported.
Use MS Windows Server 2003 Standard/Enterprise R2 or AIX
5.2/5.3
Set your virtual memory setting to at least twice the recommended memory setting. You must restart your
machine to set the virtual memory. If you require more assistance in setting virtual memory then check with
your System administrator.
For installing BusinessManager on a FAT partition, it is recommended to have at least 2000MB of free disk
space. On NTFS or FAT 32, it is recommended to have at least 1000MB of free disk space.
Software
Java Development Kit
User Management
Notes
JDK 1.5/1.6 and J2EE 1.3/1.4.
Microsoft Active directory, on Windows Server 2003
Standard/Enterprise
Sun Java System Directory Server 5.2, on Windows Server 2003
Standard/Enterprise, and Solaris 10
Important: You may encounter problems with BusinessManager archiving utilities when using
old JDBC drivers.

Before starting the BusinessManager installation, ensure that the following items are available.
BusinessManager installer extracted from the ZIP file

BusinessManager license
The BusinessManager installer contains the readme.txt and releasenotes.htm files.
The releasenotes.htm file contains:
Supported Platforms
System Limitations
Information about the BusinessManager user guides
The readme.txt file contains:
The buildInfo file

The installation log file
Installer command line options
Read the above files before proceeding with the installation.
Preparing your database

The following sections guide you to prepare your BusinessManager database.
Important: Certain database configuration changes may be required to ensure optimal performance
for the expected volume of data for specific installations. Consult the database administrator and
database documentation for optimizing your BusinessManager database configuration.
If you are planning to set any other language other than English as the default language, then set
the same in your database. Refer your database documentation for more information.
37
Oracle 10g/11g enterprise edition, Oracle Express 10g,

Oracle 11g/10g (RAC)
To prepare your database:
1. Create a tablespace for BusinessManager.
2. Create a database user using the above tablespace.
3. Grant the following privileges to the user: create session, create table, create sequence, create
view.
4. Allocate unlimited quota on tablespace to the user.
5. BusinessManager with Oracle 10g, Oracle 10g Express Edition, and Oracle 11g needs at least
50 open cursors. Set this parameter in init.ora or the initorcl.ora file available within
the oracle home.
See Sample scripts for creating your database on page 113 for command syntax and sample
script.
Modifying maximum number of connections for Oracle

Express edition
Perform the following steps to modify maximum number of connections for Oracle Express
Edition database:
1. Log on to the oracle express edition database as system administrator. (In SQL Plus enter:
"connect / as sysdba")
2. Set the number of processes to 150. (In SQL Plus run "alter system set processes=150
scope=spfile")
3. Set the number of sessions to 150. (In SQL Plus run "alter system set sessions= 150
scope=spfile")
4. Shutdown the database, (In SQL Plus run "shutdown immediate") and then startup the
database (In SQL Plus run "startup").
5. Verify the changes reflected. (In SQL Plus run "show parameter sessions" and "show
parameter processes" ) The processes and sessions are reset to based on the new value
provided in steps 2 and 3.
6. After completing the above steps, restart oracle express edition database.
MS SQL server 2005, MS SQL server 2008

1. Create case sensitive or case insensitive database for BusinessManager as per your
requirement.
Note: Applications developed with case insensitive databases in earlier releases should be
used with case insensitive databases in this release.
2. Create a database user and grant database owner privileges to the user.
38
3. Set the ANSI null default option of the database to ON. By doing this, the CREATE TABLE
follows the ISO rules to determine whether a column allows null values.
4. Configure MS SQL server to handle distributed transactions (XA transactions). Refer MS SQL
2005/2008 online documentation for more information.
script.
IBM DB2
1. Create BusinessManager database.
2. Create a user in the operating system which will be used as the BusinessManager database
user.
3. Connect to BusinessManager database and grant database owner privileges to the created
user.
4. Create bufferpool for BusinessManager data and temporary data.
5. Create tablespace for BusinessManager data and temporary data.
6. Grant these tablespaces to the database user.
script.
OpenEdge 10.2B
To prepare your database, perform the following:
1. Set environment variables based on your operating system for Open Edge in the
setenv.cmd/sh file.
For Windows:
<SBM_HOME>/dbscripts/openedge/preparedatabase/windows/setenv.cmd
For Unix: <SBM_HOME>/dbscripts/openedge/preparedatabase/unix/setenv.sh
2.
3.
4.
5.
Create BusinessManager database.

Start the database to interact with it.
Create a DBA user and grant database admin privileges to the user.
Create a database user to be used as the BusinessManager database user.
See Sample scripts for creating your database on page 113 for command syntax and sample script.

When the Installer wizard guides you through the installation, you need to enter system information
as summarized in Table 6 on page 40.
39
Table 6: BusinessManager system information

Information
Machine Host Name and
Domain name
Notes
The host name and domain name of the machine on which
BusinessManager is being installed is required to configure
BusinessManager server URLs, using which BusinessManager
can be accessed.
BusinessManager destination By default, the installer uses C:\SBM76SP1. Ensure the drive is
folder
not a network drive.
Mail server address
BusinessManager uses email to notify the administrator and

users when certain events occur.
Mail server address format: MyMailServer.MyDomain
Example: mail.company.com
Incoming and outgoing mail servers should be running and
accessible via the network to the BusinessManager host machine.
System administrator's email

address
An email address in the following format:

sbmadmin@MyDomain.com. This person is responsible for
managing BusinessManager.
BizLogic email address
BusinessManager maintains a special user account for use by

BizLogic engine through email, that is, a company can send a
notification to an employee about a task to be performed in
BusinessManager through email.BizLogic email address format:
BLmail@MyDomain.com
User Management
Decide the user management realm you plan to use for your
installation:
For LDAP-Sun Java System Directory Server or LDAP-MS Active
Directory Realm, the following details are required:
LDAP Server Name: The name of the LDAP server.
LDAP Port: The number of the LDAP port.
LDAP DIT Information: Directory Information Tree (DIT)
information.
LDAP Login Information: Directory-specific login information.
In the case of LDAP realm, ensure that the machine on which
realm is installed is accessible via the network to
BusinessManager host machine.
EJB and Portal Server Port

Number
Application Server
Identify the port numbers that you want to use for EJB and Portal
servers in case you want to customize the port numbers used
by BusinessManager. Ensure that these ports are unused and
unique.
By default, Pramati is the application server.
You also have the option of installing BEA WebLogic Server, IBM
WebSphere or JBoss as your application server.
In case the application server is not embedded with
BusinessManager, ensure that the application server is installed
and is able to run without errors.
40
Information
Database
Notes
Consult with your local database administrator to get all the
database details required depending on the database with which
you are installing BusinessMananger.
For Example: The database URL, database name, the port
number on which the database is running, the System Identifier
for the database (for Oracle), database username and password.
Database should be running. If the database is on a remote
machine, then ensure that the database machine is accessible
through the network to BusinessManager host machine.
BusinessManager program
folder (Windows)
The default name is SBM 7.6.1.
Note: All details during the installation procedure are logged in install.log file within
<SBM_HOME> location. The default log level set for BusinessManager installation is INFO. To
customize the log level for installation procedure, see Customizing temporary directory and log
level for installer on page 119.
41
42
4
Installing BusinessManager 7.6.4
This chapter guides you to install BusinessManager.
Note: To install BusinessManager, you need administrator privileges on your machine.
Depending on the existing BusinessManager version, you can choose the installer type:
Table 7: BusinessManager 7.6.4 Installer
If you are ...
then ...
A new SBM user
Install using the full installer. Refer to:
An existing SBM user with version 7.6 or earlier
Installing BusinessManager using the

installer on page 44 or
Using the silent installation utility on page 66

An existing SBM user with version 7.6.1, 7.6.2, Install using the incremental installer. Refer to
or 7.6.3
Installing BusinessManager service pack 7.6.4
on page 85.
43
Chapter 4: Installing BusinessManager 7.6.4
Prerequisites for installation
Installing BusinessManager using the installer
Using the silent installation utility
Verifying the installation
Prerequisites for installation

Before installing BusinessManager:
1. Install and configure the application server properly.
2. Install the firewall, if required. Ensure that you have permissions to manage the firewall.
3. Ensure that you have installed the JDBC driver, and that you have access to the database
server.
4. Ensure that the database is up and running on a local or a remote machine, or ensure that the
database connection is established using a client or a server.

Provide valid information in the installation dialog boxes. These values are reflected in many
configuration and JAR files.
BusinessManager installer uses the default temporary directory of the operating system for
installation. If there is insufficient space in the default temporary directory, then you can install
BusinessManager using another temporary directory. See Customizing temporary directory and
log level for installer on page 119 for more information.
To launch the installer:
1. To launch the Installation wizard, execute Install.cmd/sh file available in the Installation
directory.
Installation wizard is launched and the Welcome page is displayed.
2. Review the text and click Next.
The End User License Agreement page appears.
3. Review the agreement, select the I accept... option, and click Next. The Directory Location
page appears.
44
Specifying directory location

In the Location page, you can retain the default installation folder, or specify a folder of your choice.
On Windows, the installer selects the bootup drive as the default installation folder for
BusinessManager installation. As shown in the following figure, C:\SBM764 is the default installation
folder for BusinessManager. For UNIX, the default installation directory is /opt/SBM764.
Figure 4: The Location page
To specify installation location:

1. In the Location page, accept the default installation folder, or enter a new location, or click
Browse to specify your preferred directory.
You can only use A-Z, a-z, 0-9, /,\, -, _ in a directory path and name.
2. Click Next.
The Local Machine Details page appears.
Specifying local machine details

The installer uses the local machine name as a default and it can be modified if required.
Figure 5: The Local Machine Details page
45
To specify local machine details:

1. In the Local Machine Details page, enter the Host name as the machine name of the local
machine.
2. Enter network Domain name of the machine on which BusinessManager will be installed.
3. Click Next.
The BusinessManager Admin Credentials page appears.
Specifying admin credentials

Identify a user who performs the role of BusinessManager administrator.
Figure 6: The BusinessManager Admin Credentials page
To specify admin credentials:

1. Enter the Username and Password of the admin user. Later, on initializing the BusinessManager
database, this user is assigned privileges to perform all operations in BusinessManager. The
same Username and Password is used as the default while running the setupSBM utility or
starting the BizLogic server.
You can change the user name and/or password later by using the User Configuration Tool.
For more information, refer to the Server Administrators Guide.
Note: For LDAP user realm, an existing LDAP user must be specified.
For JDBC user realm, on initializing BusinessManager database, the specified user is created
in the BusinessManager database.
2. Click Next.
The Processor Type page appears.
46
Specifying processor type

Identify the appropriate processor type based on your requirements.
Figure 7: The Processor Type page
To specify processor type:

1. Select the processor type.
2. Click Next.
The application server details page appears.
Selecting application server

Identify the application server on which BusinessManager will be installed.
Figure 8: The Application Server page
Specify application server:

1. Select the application server:
Embedded application server (Pramati 6.0 SP4) Provided with the installation ZIP file or
CD. If you select Pramati as your application server, then the Specifying Server Ports
page appears. See Specifying Pramati server ports on page 50.
WebLogic 10.3.0 If you select WebLogic as your application server, then the Application
Server Location page appears. See Specifying WebLogic server details on page 51.
Note: You can choose this option for WebLogic server 10.3.0 or 10.3.3.
WebSphere 6.1.0.31 or WebSphere 7.0.0.13 If you select WebSphere as your application

server, then the Application Server Location page appears. See Specifying WebSphere
server details on page 52.
47
Embedded JBoss AS 5.1.0 community edition Provided with the installation ZIP file or
CD. If you select JBoss community edition 5.1 as your application server, then the Specifying
Server Ports page appears. See Specifying JBoss server details on page 54.
JBoss Enterprise Application Platform 5.0.1 or JBoss Enterprise Application Platform
5.1.1 If you select JBoss Enterprise Application Platform 5.0.1 or 5.1.1 as your application
server, then the Application Server Location page appears. See Specifying JBoss server
details on page 54.
Note: Before installing BusinessManager using JBoss Enterprise Application Platform 5.0.1
or 5.1.1 application server, ensure that you have manually removed the ejbServer and
portalServer directories located in JBoss_Home\server folder, where JBoss_Home
represents the installation directory for JBoss Enterprise Application Platform 5.0.1 or 5.1.1
application server.
2. Optionally select the Go to advanced security options.

3. Click Next. The Security Details page appears.
Configuring BusinessManager security settings

Specifying security details is optional. Figure 9 on page 48 is for Pramati application server and
is different for other application servers.
Figure 9: The Security Details page
To configure security settings:

1. In the Security Details page, enter the following information. Refer to Table 8 on page 49.
48
Table 8: Security Details

Security parameter
JNDI protocol
Description
It is possible to configure BusinessManager to use secure JNDI
protocol only for the WebLogic application server.
For other application servers, it is not possible to configure
BusinessManager to use secure JNDI protocol.
BusinessManager can be configured to use HTTP(S) protocol, if
its application server is configured with this security feature.
Web Protocol
Note: If HTTP(S) is enabled, and if you are using WebServices

in SBM, then you must have valid certificates added to the JDK.
For more information about adding certificates to JDK, refer to JDK
documentation.
By default BusinessManager uses HTTP protocol.
Application server administrator credentials are required for
BusinessManager to connect to the application server.
The application server administrator has privileges to administer
application server resources used by BusinessManager.
Enter user name and password for application server
administrator.
Application Server Admin The default admin credentials for different application servers are
Credentials
as follows:
For Pramati: User name: root, Password: pramati

For WebLogic: User name: system, Password: wlsysadmin
For WebSphere: None (Global security is disabled by default.)
For JBoss: User name: guest, Password: guest
2. Click Next.
The application server specific page appears.
Specifying application server details

According to your application server, specify the server details.
49
Specifying Pramati server ports

For Pramati you need to specify only the port numbers. Application server location details are not
required for Pramati because it is installed within BusinessManager.
Figure 10: The Pramati Server Port page
To specify Pramati server details:

1. In the Pramati Server Ports page, use default port numbers or enter other unused port numbers
for Pramati application server.
2. Optionally select the Go to advanced port settings and click Next.
The Advanced Pramati Server Ports page appears.
Figure 11: The Advanced Pramati Server Ports page
3. Use default port numbers for other EJB and Portal server ports, or enter other unused port
numbers for Pramati port listener.
4. Click Next.
The BusinessManager Portal URL page appears. See Specifying BusinessManager Portal
URL on page 55.
50
Specifying WebLogic server details

For WebLogic application server 10.3.0 or 10.3.3, you must enter the server details as well as the
port numbers.
Figure 12: The WebLogic Server Details page
To specify WebLogic server details:

1. In the WebLogic Server Details page, enter the Server Location and Domain Name as
described in the following table.
Parameter
Description
Enter the location where WebLogic application server is
installed.
Server Location
For WebLogic 10.3.0 or 10.3.3, enter the location up to the

wlserver_10.3 directory. For example,
C:/bea/wlserver_10.3
To install BusinessManager on WebLogic application server,
you must create a domain name within the WebLogic
application server home for BusinessManager application.
Enter a name for BusinessManager domain.
Domain Name
Only the following set of characters are allowed for domain

name: A-Z, a-z, 0-9, -, _
Note: In the above character set, comma is used only to
separate the valid characters.
2. Click Next.
51
The WebLogic Server Ports page appears.

Figure 13: The WebLogic Server Port page
3. Use default port numbers or enter other unused port numbers for WebLogic application server.
4. Click Next.
The WebLogic Domain Location page appears.
Figure 14: The WebLogic domain location page
5. Use the default location, or enter another location, or click Browse to specify a location.
6. Click Next.The BusinessManager Portal URL page appears. See Specifying BusinessManager
Portal URL on page 55.
Specifying WebSphere server details

For WebSphere application server, you must enter the server details as well as the port numbers.
Figure 15: The WebSphere Server Details page
To specify WebSphere server details:

1. In the WebSphere Server Details page, enter Server Location and Profile Details as described
in the following table.
52
Parameter
Server Location
Description
Enter the location where WebSphere application server is installed.
To install BusinessManager on WebSphere application server,
you must create a profile for BusinessManager.
Profile Name
The profile name provided while installing is used by

BusinessManager.
Enter a name for BusinessManager profile. Do not use special
characters and spaces in the profile name.
A WebSphere cell contains software components that may be
installed on one node or distributed over multiple nodes.
Cell Name
Enter the name for the WebSphere cell that contains a node where
BusinessManager server instances are created.
Do not use special characters and spaces in the cell name.
A WebSphere node is a virtual unit containing server instances.
Node Name
Enter a name for the WebSphere node that is associated with the
BusinessManager servers.
This node contains BusinessManager EJB and Portal server
instances. Do not use special characters and spaces in the node
name.
Browse and select the profile location.
Profile Location
On the selected profile location, your Profile name, Cell name, and
a Node name are created.
Note: When you install multiple BusinessManager installations for setting up cluster, the profile
name must be the same in all installations whereas the node and cell names must be different
across installations.
2. Click Next. The WebSphere Server Ports page appears.
Figure 16: The WebSphere Server Port page
3. Use default port numbers or enter other unused port numbers for the WebSphere application
server.
53
Specifying JBoss server details

This section contains instructions for installing BusinessManager with enterprise JBoss application
server, where you can specify server location and server ports.
For embedded JBoss, you must specify only the port numbers. Application server location details
are not required because JBoss is installed within BusinessManager.
Figure 17: The JBoss Server Details page
To specify JBoss details:

1. Click Browse to locate your jboss-as folder and provide the fully qualified path for that folder.
2. Click Next. The JBoss Server Ports page appears.
Figure 18: The JBoss Server Port page
3. Use default port numbers or enter other unused port numbers for JBoss application server.
4. Optionally select Go to advanced port settings and click Next. The Advanced EJB Server
Listener Ports page appears.
Figure 19: The JBoss EJB Server Listener Ports page
54
6. Click Next. The Advanced Porter Server Listener Ports page appears.
Figure 20: The JBoss Portal Server Listener Ports page
Specifying BusinessManager Portal URL

The Portal URL is used to access BPM Portal.
If host name and domain name are provided while specifying BusinessManager local machine
details, then the BusinessManager portal URL is http://machine_name.domain name:
portal_http_port number.
If an IP address is specified, then the portal URL is http://IP_address: portal http port number.
Figure 21: The BusinessManager Portal URL page
To specify BusinessManager portal URL:

1. Review the URL.
2. Click Next. The Email Configuration page appears.
55
Configuring email properties

Enter the following details for configuring BusinessManager email properties:
Figure 22: The Email Configuration page
To specify email configuration:

1. Enter the following email properties.
Email properties
Description
The outgoing email server is used for sending emails from
BusinessManager.
Enter the IP address or the host name of the outgoing email

Outgoing Email Server
server.
All emails sent by BusinessManager are sent using the

configured outgoing mail server.
SMTP is the default protocol.

Enter the email ID of the BusinessManager administrator.
Administrator Email
Whenever a system error is encountered, an email is sent to

this mail account.
BizLogic Email
Enter the email ID using which BizLogic engine will send emails.
2. Optionally, select Go to Advanced Email Properties.

3. Click Next. The Advanced Email Properties of Task Completion page appears.
Figure 23: The Advanced Email properties for Task Completion page
56
4. Enter the credentials for BizLogic email account.

Email properties
Description
The incoming email server is used for receiving emails sent to

BusinessManager.
Enter the IP address or the host name of the incoming email

server.
Incoming Email server
All mails sent to BusinessManager will use the configured

incoming mail server.
IMAP is the default protocol.

BizLogic Email Account
Details
Username and Password of BizLogic email account are required

for BizLogic engine to have access to the email account. Enter the
Username and Password of BizLogic email account.
5. Click Next. The User Management page appears.
Specifying User Management Realm details

BusinessManager can be used with JDBC realm or LDAP.
Figure 24: The User Management page
To select user management realm:

1. Select the User Management:
JDBC realm: All user related data is stored in the BusinessManager database. See Specifying
database details on page 59.
LDAP Realm
LDAP Hybrid Realm
2. Click Next. If you select LDAP User Management, then select the LDAP realm type.
LDAP - Sun Java System Directory: All user related data is managed by LDAP server.
LDAP - Microsoft Active Directory: All user related data is managed by LDAP server.
Note: For SBM 7.6.2, you can also add ApacheDS 1.5.7 as your LDAP server.To set ApacheDS
as your LDAP server, refer Enabling ApacheDS for SBM on page 88 for more information.
3. Click Next.
57
The LDAP Server Configuration page appears.

Figure 25: The LDAP Server Configuration
4. Enter the following details.

Parameter
Description
LDAP Server
Enter the name or the IP address of the machine on which LDAP

server is installed.
LDAP Port
Enter the port number on which LDAP server is running.

Enter the entry point to the directory where users are stored in the
LDAP server.
UserRoot
The following Directory information tree needs to be provided to be

able to connect to LDAP active directory (Windows 2003):
CN=Progress\,Savvion,OU=Management
accounts,OU=Management,DC=corp,DC=espn,DC=pvt
Enter the entry point to the directory where groups are stored in the
LDAP server.
GroupRoot
The following Directory information tree needs to be provided to be

able to connect to LDAP active directory (Windows 2003):
CN=Progress\,Savvion,OU=Management
accounts,OU=Management,DC=corp,DC=espn,DC=pvt
5. Optionally select Enable LDAP SSL if you want BusinessManager to connect to LDAP using
SSL.
6. Click Next. The LDAP Server Credential page appears.
Figure 26: The LDAP Server Credentials page
58
7. Enter the Username and Password of an existing LDAP realm user. This user is used by
BusinessManager to connect to the LDAP server to fetch users and group details in the
organizations LDAP directory.
8. Click Next. The Verify LDAP Connection page appears.
Figure 27: The Verify LDAP Connection page
9. Select Yes to verify LDAP server connectivity. Verifying connectivity ensures that the LDAP
server details provided are appropriate and that the machine on which BusinessManager is
being installed is connected to the LDAP server.
Note: You can proceed with the installation without verifying the connectivity. However, you
are recommended to verify the LDAP server connectivity before proceeding.
10. Click Next. The Database page appears.
Specifying database details

Identify the database with which you want to install BusinessManager.
Figure 28: The Database page
To specify a database:
1. Select the database and click Next. The Database Properties page appears.
2. Enter the database details as described in the following sections.
59
Configuring Oracle database

BusinessManager can be installed on Oracle 10g, Oracle 10g Express or Oracle 11g database.
Figure 29: The Oracle Database Properties page
Specify Oracle server details:

Database properties
Description
The JDBC driver used by BusinessManager to connect to Oracle
database server is com.savvion.jdbc.oracle.OracleDriver.
This driver is installed along with BusinessManager.
JDBC Driver
Note: It is not possible to modify the JDBC driver used.
URL Prefix
The default URL prefix used to connect to the database is

jdbc:savvion:oracle://
The following URL prefix is also supported jdbc:oracle:oci:@
Server Host Name
Enter the host name or IP address of the machine on which Oracle

database is installed.
Port Number
Enter the port number on which Oracle server is running.
SID
Enter the system identifier of the Oracle database server used by

BusinessManager.
2. Click Next.The Database Credentials page appears. See Specifying database user credentials
on page 63.
60
Configuring MS SQL server

BusinessManager can be installed on MS SQL Server 2005 or MS SQL Server 2008 database.
Figure 30: The MS SQL Database Properties page
Specify MS SQL database properties:

Database properties
JDBC Driver
Description
The JDBC driver used by BusinessManager to connect to MS SQL
database server is
com.savvion.jdbc.sqlserver.SQLServerDriver. This driver
is installed along with BusinessManager.
URL Prefix
URL prefix used to connect to the database is

jdbc:savvion:sqlserver://
Server Host Name
Enter the host name or the IP address of the machine on which MS

SQL server is installed.
Port Number
Enter the port number on which MS SQL server is running.
DB Name
Enter the name of the database created for BusinessManager.
on page 63.
61
Configuring IBM DB2 database

BusinessManager can be installed on IBM DB2 database.
Figure 31: The DB2 database properties page
To specify DB2 database details:

Database properties
Description
The JDBC driver used by BusinessManager to connect to DB2
database server is com.savvion.jdbc.db2.DB2Driver. This
driver is installed along with BusinessManager.
JDBC Driver
URL Prefix
URL prefix used to connect to database isjdbc:savvion:db2:
Server Host Name
Enter the host name or the IP address of the machine on which DB2
database server is installed.
Port Number
Enter the port number on which DB2 server is running.
DB Name
on page 63.
OpenEdge
BusinessManager can be installed on OpenEdge 10.2B database.
Figure 32: The OpenEdge Database Properties page
62
Specify OpenEdge database details:

Database properties
Description
The jdbc driver used by BusinessManager to connect to DB2 database
server is com.savvion.jdbc.openedge.OpenEdgeDriver. This
driver is installed along with BusinessManager.
JDBC Driver
Note: It is not possible to modify the jdbc driver used.
URL Prefix
URL prefix used to connect to database

isjdbc:savvion:openedge://
Server Host Name
Enter the machine name or IP address of the machine on which

OpenEdge database server is installed.
Port Number
Enter the port number on which OpenEdge server is running.
DB Name
on page 63.
Specifying database user credentials

Specify the database user credentials.
Figure 33: The Database Credentials page
To specify database credentials:

1. Enter the user name and password of the database user account used to connect to the
BusinessManager database.
Important: If you are using OpenEdge database, then you must enter the OpenEdge user
ID in the Username text box.
2. Click Next. The Verifying the database connection page appears.
63
Verifying database connection

Verify database connectivity to ensure that database details provided are appropriate and that the
machine on which BusinessManager is being installed is connected to the database.
Figure 34: The Verifying the database connection page
To verify database connectivity:

1. Select Yes to verify the database connectivity. Verifying connectivity ensures that the database
server details provided are appropriate and that the machine on which BusinessManager is
being installed is connected to the database.
Note: You can proceed with the installation without verifying the connectivity. However, you
are recommended to verify the database connectivity before proceeding.
2. Click Next. If you have selected WebLogic as your application server, then the JDK Location
page appears.
If you are using Windows with Pramati or JBoss application server, then the The Product
Shortcut page appears. See Specifying shortcut for Windows operating system on page 66.
Specifying JDK location

You must specify the JDK Location.
Important: If you are using Windows 32/64 bit architecture with Pramati or JBoss application
server, then the JDK bundled with SBM is used. If you are using Unix 32 bit architecture with
Pramati or JBoss application server, then the JDK bundled with SBM is used.
In the following instances, you must specify the JDK location in the installer.
For Pramati application server with Unix 64 bit architecture: Specify external JDK home, JDK
1.6 minor version 20.
For WebLogic application server with Windows 32 bit architecture: Uses JDK bundled with
Weblogic.
For WebLogic application server with Windows 64 bit architecture: Specify external JDK home.
For WebLogic application server with Unix 32 bit architecture: Uses JDK bundled with Weblogic.
64
For WebLogic application server with Unix 64 bit architecture: Specify external JDK home. This
must be the same as the JDK used during Weblogic installation.
For JBoss application server with Unix 64 bit architecture: Specify external JDK home, JDK 1.6
minor version 20.
Note: For WebSphere application server BusinessManager uses the JDK bundled with WebSphere,
its static location is APPSERVER_HOME/java so the panel is not available.
Figure 35: The JDK Location page
To specify JDK location:

1. Accept the default JDK Location directory, or click Browse to specify a JDK directory.
2. Click Next. The Product Shortcut page appears.
65
Specifying shortcut for Windows operating system

After installation, all the BusinessManager shortcuts are available in the specified folder.
Figure 36: The Product Shortcut page
Perform the following:

1. Enter a folder name in which BusinessManager installation shortcuts need to be kept. The
shortcuts are available from Start > Programs > Savvion.
2. Optionally, select Launch FirstSteps Console after installation. First steps console is a GUI
provided to prepare BusinessManager database and administer the servers. After installation,
the First Steps console can also be launched from the command line and from Windows
shortcuts.
3. Click Next. The Installation Summary page appears.
4. Review the Installation Summary and click Next to install BusinessManager.
Note: If the disk space required for BusinessManager is not available, then the installer displays
a notification.
5. After the installation is complete, a Success message is displayed.
6. Click Next to complete the installation. If the Launch FirstSteps Console option is selected,
then the First Steps Console is launched.
After the installation is completed, BusinessManager is installed at the location specified during
installation.

You can install BusinessManager using the silent installation utility without any user intervention.
This can be done only after the BusinessManager has been installed once using the installation
wizard and the installation is recorded.
When you record the installation, a template response file is generated that contains all the
commands used while installing BusinessManager. Using this template response file, silent
BusinessManager installation can be done.
66
Recording the BusinessManager installation

To record the installation, execute the following command from <BM
installerHome>/Installer folder:
For Windows:
setupwin32.exe -options-record <response file name>
For Solaris:
setupsolarisSparc.bin -options-record <response file name>
For Linux:
setuplinux.bin -options-record <response file name>
For AIX:
setupaix.bin -options-record <response file name>
Note: The <response file name> must include the complete path information.
Installing with the silent installation utility

To install BusinessManager silently:
1. Due to a bug in InstallShield, the Silent Installation utility always installs BusinessManager at
the default location even when a new location is specified in the Silent Installation response
file. As a workaround for this problem, modify the response file as follows:
use "SBM.installLocation" instead of "installLocation", as shown in the following
line:
-P SBM.installLocation="C:\SBM75"
instead of
-P installLocation="C:\SBM75"
2. Modify the response file if any additional parameter needs to be changed. This is optional.
3. To use the silent installation mode, execute the following command from <BM
installerHome>/Installer:
For Windows:
setupwin32.exe -options <response file name> -silent
For Solaris:
setupsolarisSparc.bin -options <response file name> -silent
For Linux:
setuplinux.bin -options <response file name> -silent
For AIX:
setupaix.bin -options <response file name> -silent
Note: The response file name must include the complete path information.
67
Verifying the installation

On successful installation of BusinessManager, verify the following:
BusinessManager is installed at the location specified during the installation.

Based on your application server, verify the following:
For Pramati or embedded JBoss: It is installed in BusinessManager Home.
For WebLogic: A domain you have specified during installation is created within the application
server location for BusinessManager.
For WebSphere: A profile, cell, and node that you have specified during installation is created
within the application server location for BusinessManager.
For Enterprise JBoss: A folder you have specified during installation is created within the
application server location for BusinessManager.
All configuration and properties files are available under the <SBM_HOME>/conf directory.
These files contain configurable BusinessManager properties and the details specified during
installation are saved in them. For example, sbm.conf is updated with installation directory
and general parameters. sbmdb.properties is updated with database details, and
sbmemail.properties is updated with email configurations.
Check install.log in SBM_HOME directory for the message SBM installation

completed.
When BusinessManager is installed on Windows operating system, Windows shortcuts are

created as shown below.
Figure 37: Windows shortcuts
After completing the installation, follow the instructions specified in After installing BusinessManager
7.6.4 on page 69 to start the BusinessManager servers.
68
5
After installing BusinessManager 7.6.4
This chapter guides you to initialize BusinessManager database and manage BusinessManager
servers after BusinessManager has been installed.
You can use the FirstSteps Console to initialize BusinessManager database repository and
administer the servers. The FirstSteps console can be invoked by executing firststeps.cmd/sh
file in <SBM_HOME>/bin location. If BusinessManager is installed on Windows operating system,
then the FirstSteps console can be launched using Windows shortcut.
You can also initialize BusinessManager database repository and administer the servers using the
command line utilities. See Using BusinessManager command line utilities on page 121 for more
information.
If BusinessManager is installed on any application server other than WebSphere, then initialize
the BusinessManager database. See Initializing BusinessManager database repository on page
78 for more information.
If you are using MS SQL Server 2005 or MS SQL Server 2008 database and you need to enable
support for JDBC distributed transactions through JTA then see Enabling MS SQL server for JDBC
distributed transactions on page 75 for more information.
If your locale is not English, then set the following parameter values to 'UTF-8'.
In SBM_HOME/conf/sbm.conf file:
sbm.smtp.charset
sbm.characterencoding
69
Chapter 5: After installing BusinessManager 7.6.4
In SBM_HOME/conf/sbmemail.properties file:
sbm.email.outgoing.server.charset
Configuring SBM for Oracle RAC
Creating profile, servers and resources for WebSphere
Enabling MS SQL server for JDBC distributed transactions
Setting up temporary table space for DB2
Initializing BusinessManager database repository
Additional steps for OpenEdge
Starting servers
Verifying BusinessManager installation
Stopping servers

Installing SBM 7.6.1 with Oracle RAC is not supported in the installer.
You must perform the following to configure SBM WebLogic 10.3.0 with Oracle RAC.
A sample Oracle RAC URL for three node Oracle RAC is as follows.
Oracle RAC URL:
jdbc:savvion:oracle://host1:1628;ServiceName=FLIPPRD;AlternateServers=
( host2:1628, host3:1628, host4:1628);FailoverMode=select;
FailoverPreconnect=false;LoadBalancing=false;ServerType=dedicated;
serverName= host1;portNumber=1628
Modifying SBM configuration files

The database URL in the configuration files within SBM installation needs to be changed. The
changes required are listed in Table 9 on page 70:
Table 9: SBM configuration files
File to be modified
The changes to be done
sbm_home/adapters/db/conf Change the value of property "db0.url" to the RAC URL.

/db.properties
sbm_home/conf/sbmdb.properties Change the value of property "sbm.db.oracle.url" to the
RAC URL.
70
Modifying Oracle sequence for BizEvent table

The sequence defined for BIZEVENT table needs to be modified to disable caching of sequence
numbers. This is required as the next number retrieved should be in sequence every time
irrespective to which Oracle RAC node the request goes.
Create BusinessManager database (Refer to Creating BusinessManager database on page 78)
and execute the following before starting the servers:
DROP SEQUENCE EVENT_ID_SEQ;
CREATE SEQUENCE EVENT_ID_SEQ NOCACHE;
Modifying WebLogic 10.3.0 data sources

Within application server the database interaction is done using DataSources. The URL specified
for these DataSources needs to be changed to Oracle RAC URL. The datasources files are located
at - DOMAIN_HOME/config/jdbc. Refer to the property "sbm.weblogic.domain.location"
in sbm_home/conf/sbmjndi.properties to the get the value for DOMAIN_HOME. All the
DataSource xml files should be updated with Oracle RAC URL.
Note: In the case of cluster, the changes need to be done in all the nodes.
A sample is provided below (BizLogicDB-jdbc.xml):
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:sec="http://www.bea.com/ns/weblogic/90/security"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/920
http://www.bea.com/ns/weblogic/920.xsd">
<name>BizLogicDB</name>
<jdbc-driver-params>
<url>
jdbc:savvion:oracle://host1:2521;SID=orcl;serverName=
host1;portNumber=2521
</url>
<driver-name>com.savvion.jdbcx.oracle.OracleDataSource</driver-name>
<properties>
<property>
<name>user</name>
<value>savviondb</value>
</property>
</properties>
DataSource with Oracle RAC URL

<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://www.bea.com/ns/weblogic/90"
xmlns:sec="http://www.bea.com/ns/weblogic/90/security"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls"
xsi:schemaLocation="http://www.bea.com/ns/weblogic/920
http://www.bea.com/ns/weblogic/920.xsd">
<name>BizLogicDB</name>
<jdbc-driver-params>
<url> jdbc:savvion:oracle://host1:2521;ServiceName=orcl;AlternateServers=
(host2:2521,host3:2521);FailoverMode=select;FailoverPreconnect=false;
LoadBalancing=true;ServerType=dedicated;serverName=:host1;portNumber=2521
</url>
<driver-name>com.savvion.jdbcx.oracle.OracleDataSource</driver-name>
<properties>
<property>
<name>user</name>
71
<value>savviondb</value>
</property>
</properties>
Modifying JBoss datasources

You must modify both XA and Non-XA DataSources to configure SBM with Oracle RAC. The
changes are mentioned below.
Non-XA data source

The URL needs to be changed to RAC URL, for Non-XA DataSources. Please refer to the sample
provided below (sbmcommondb-ds.xml)
<?xml version="1.0" encoding="UTF-8"?>
<datasources>

<local-tx-datasource>
<jndi-name>jdbc/SBMCommonDB</jndi-name>

<connection-url>
jdbc:savvion:oracle://host1:2521;SID=orcl;serverName=host1;portNumber=2521
</connection-url>
<driver-class>com.savvion.jdbc.oracle.OracleDriver</driver-class>
<use-java-context>false</use-java-context>
<user-name>savviondb</user-name>
Datasource for Oracle RAC

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

<local-tx-datasource>
<jndi-name>jdbc/SBMCommonDB</jndi-name>

<connection-url>
jdbc:savvion:oracle://host1:2521;ServiceName=orcl;AlternateServers=
(host2:2521,host3:2521);FailoverMode=select;FailoverPreconnect=false;
LoadBalancing=true;ServerType=dedicated;serverName=:host1;portNumber=2521
</connection-url>
<driver-class>com.savvion.jdbc.oracle.OracleDriver</driver-class>
<user-name>savviondb</user-name>
XA data source
In the case of XA DataSource, we need to replace the URL property and pass it as separate
properties. Please refer to the sample provided below (bizlogicdb-ds.xml)
<datasources>
<xa-datasource>
<jndi-name>jdbc/BizLogicDB</jndi-name>
<xa-datasource-class>
com.savvion.jdbcx.oracle.OracleDataSource
</xa-datasource-class>
<xa-datasource-property name="ServerName">host1</xa-datasource-property>
<xa-datasource-property name="PortNumber">2521</xa-datasource-property>
<xa-datasource-property name="DatabaseName">orcl</xa-datasource-property>
<xa-datasource-property name="User">savviondb</xa-datasource-property>
Datasource for Oracle RAC

<datasources>
<xa-datasource>
<jndi-name>jdbc/BizLogicDB</jndi-name>
<xa-datasource-class>
72
com.savvion.jdbcx.oracle.OracleDataSource
</xa-datasource-class>
<xa-datasource-property name="ServerName">host1</xa-datasource-property>
<xa-datasource-property name="PortNumber">2521</xa-datasource-property>
<xa-datasource-property name="ServiceName">orcl</xa-datasource-property>
<xa-datasource-property name="AlternateServers">
(host2:2521,host3:2521,host4:2521)
</xa-datasource-property>
<xa-datasource-property
name="FailoverMode">select</xa-datasource-property>
name="FailoverPreconnect">false</xa-datasource-property>
<xa-datasource-property name="LoadBalancing">true</xa-datasource-property>
name="ServerType">dedicated</xa-datasource-property>
<xa-datasource-property name="User">savviondb</xa-datasource-property>
73
Creating profile, servers and resources for WebSphere

If BusinessManager is installed on WebSphere application server, then you need to perform the
following steps before initializing BusinessManager database repository:
1. Invoke the FirstSteps Console.
Figure 38: First Steps Console - WebSphere
2. Click Create Profile to create a profile in the application server where all the information related
to BusinessManager is stored. The profile is created with the name specified during
BusinessManager installation.
3. Click Create Server and resources to create EJB and Portal servers for BusinessManager
along with JDBC and JMS resources.
The following is the log file location for Create Server and Resources:
$SBM_HOME\websphere\logs\sbmwsadmin.log.
Note: Do not create server and resources in the case of cluster installation. See Clustering
Guide for more information.
74
Enabling MS SQL server for JDBC distributed

transactions
Perform the following steps to enable MS SQL Server 2005 and MS SQL Server 2008 to support
JDBC distributed transactions through JTA:
Note: Contact your Database administrator before preparing your database.
1. Navigate to <SBM_HOME>/lib/jdbc/datadirect/SQLServerJTA folder.
Note:
Perform step 2, only if MS SQL Server is installed on a machine other than SBM, if both are
installed on the same machine, then skip to step 3.
2. Copy the <SBM_HOME>/lib/jdbc/datadirect/SQLServerJTA folder to a temporary folder
on the MS SQL Server machine.
3. Copy sqljdbc.dll file to <MSSQLSERVER_HOME>/Binn folder. This file needs to be picked
up from 32-bit, 64-bit, or X64-bit folder under SQLServerJTA folder depending
upon the architecture of the MS SQL Server machine.
The following table lists the folder location for sqljdbc.dll file based on the MS SQL Server
machine architecture:
Architecture
Folder location
32-bit
SQLServerJTA\32-bit
Itanium 64-bit
SQLServerJTA\64-bit
AMD64 and Intel EM64T 64-bit
SQLServerJTA\x64-bit
4. Edit setsqlserverenv.cmd under SQLServerJTA folder and update the following

environment variables:
SERVER_NAME
ADMIN_USER
ADMIN_PWD
5. If MS SQL Server version is 2008, then execute preparesqlserver_2008.cmd file, else

execute preparesqlserver.cmd file.
6. Check the messages on the prompt for successful execution of the script file.
7. Start Distributed Transaction Coordinator (DTC) service. If it is already started,
please restart the DTC service.
75
Enabling XA transactions on Windows 7

Perform the following steps to enable XA transaction on Windows 7:
1. Open Control Panel > Administrative tool > Component Services.
Figure 39: Component services
2. Expand Console Root > Component Services > Computers > My Computer > Distributed
Transaction Coordinator > Local DTC.
Figure 40: Local DTC
76
3. Open Properties window by right clicking on Local DTC. Select Enable XA Transaction on
Security tab.
4. Click OK. The XA Transactions is enabled.
77
Setting up temporary table space for DB2

For DB2, the default system temporary tablespace TEMPSPACE1 has page size of 4K. This
restricts the max column count to 500 and max record length to 4005 bytes during query execution.
To overcome this restriction, create a new system temporary tablespace of page size of 8K.
Note: You need DBA privileges to execute the following scripts or please contact your DBA.
1. Execute the following script on DB2 console to create tablespace for database sbm
CREATE BUFFERPOOL tempsysbf8k SIZE 400 PAGESIZE 8 K ;
CONNECT RESET;
CONNECT TO sbm;
CREATE SYSTEM TEMPORARY TABLESPACE TEMPSPACESYS8K PAGESIZE 8 K MANAGED BY
AUTOMATIC STORAGE BUFFERPOOL tempsysbf8k;
2. For dropping the tablespace

DROP TABLESPACE TEMPSPACESYS8K;
DROP BUFFERPOOL tempsysbf8k;

If the database used by BusinessManager is installed in multi-byte mode, then set
sbm.db.multibyteschema parameter in <SBM_HOME>/conf/sbmdb.properties file to
true.
If BusinessManager database is already created, and then you need to re-initialize BusinessManager
database, see Re-initializing BusinessManager database on page 127 for more information.
Creating BusinessManager database

Ensure the following before initializing BusinessManager database repository:
BusinessManager servers and associated application servers must not be running while
initializing BusinessManager database repository.
The database server used by BusinessManager should be running and the database host
should be accessible (in the network of) to the BusinessManager host.
To initialize the BusinessManager database repository:
1. Invoke the FirstSteps Console.
78
Note: Step Figure 38 on page 74 is for Pramati application server FirstStep Console. For other
application servers, the console content may vary.
Figure 41: Initializing BusinessManager database
2. Click Prepare Repository. The Prepare BusinessManager Repository popup appears.

Figure 42: Repository configuration details
79
3. Click OK. The Success message appears.

Figure 43: Successful repository preparation
4. Click OK.
Information related to the tables dropped and created, errors while initializing BusinessManager
database repository are logged in <SBM_HOME>/logs/sbm.log file. See Locating
BusinessManager log files on page 131 for more information.
Username and password of the BusinessManager administrator specified during BusinessManager
installation are used to initialize the database. This user is given all BusinessManager privileges.
The BusinessManager administrator can be changed using User Configuration tool.
Additional steps for OpenEdge

Certain DDL SQL queries are inserted in the database table in the following scenarios:
Uninstalling BizLogic application

Reinstalling BizLogic application
Installing BizLogic application with monitoring worksteps
Reinstalling BizLogic application with monitoring worksteps
Uninstalling a BizPulse rules containing infopads
Reinstalling a BizPulse rules containing infopads
These DDL SQL queries cannot be executed online due to restrictions from OpenEdge database.
The task of OpenEdgeDDLOperationHandler process instance is to pick up all execution pending
queries from the database table and execute them one by one using direct JDBC connections.
Perform the following to create OpenEdgeDDLOperationHandler process instance:
1. Set bizlogic.ws.max.activationcount to -1 in bizlogic.conf file in
SBM_Home\conf folder.
2. Start EJB and Portal servers. Refer Starting EJB and Portal servers on page 81 for more
information.
3. Start BizLogic and BizPulse servers. Refer Starting BizLogic and BizPulse servers on page 81
for more information.
4. Start BPM Portal and log in as the SBM administrator.
5. From BPM Portal deploy OpenEdgeDDLOperationHandler application.
6. From BPM Portal create a single instance of this application.
80
Starting servers
Starting servers
Ensure the following before starting servers:
BusinessManager database is initialized

For WebSphere application server, ensure that WebSphere profile is created and WebSphere
servers and resources are created.
For JBoss application server, in addition to the EJB and Portal server ports specified during
installation, ensure that the default ports specified in the JBoss configuration files are available.
To verify default ports used and to change the port settings, Configuring JBoss ports on page
141.
Starting EJB and Portal servers

Before starting BusinessManager servers, EJB server of the application server on which
BusinessManager is installed should be started.
Use the FirstSteps Console for starting EJB and Portal servers of the application servers. See
Step Figure 38 on page 74.
On starting the severs, the server start up consoles are launched.

Once the servers are started, their status is updated in the respective server start up consoles
and in the application server log files. See Locating BusinessManager log files on page 131 for
more information.
Note: For WebLogic application server, Admin server is started along with EJB and Portal servers.
For Pramati application server, SBM JMS and datasource resources are created after the pramati
servers are started.
See Using BusinessManager command line utilities on page 121, Starting and stopping application
servers on page 122 for starting servers using command line utilities.
Starting BizLogic and BizPulse servers

By default, auto-startup is enabled for BusinessManager servers. If auto-startup is enabled for
BusinessManager servers, then the BusinessManager servers start automatically on EJB server
startup.
For more information on BusinessManager auto-startup feature see BizLogic and BizPulse
auto-startup on page 129.
If auto-startup is disabled for BusinessManager servers, then the BusinessManager servers need
to be started individually.
Use the FirstSteps Console for starting BusinessManager servers. See Step Figure 38 on page
74.
Once BusinessManager servers are started, the server status is updated in the respective
server log files under <SBM_HOME>/logs directory. See Locating BusinessManager log files
on page 131 for more information.
81
Verifying BusinessManager installation

To verify BusinessManager installation:
1. Launch BPM Portal from the FirstSteps Console. See Figure 44 on page 82.
2. Log in as BusinessManager administrator. BPM Portal home page appears.
Figure 44: BPM Portal
3. Verify BizLogic server status in bizlogic.log file under the <SBM_HOME>/logs location. If
BizLogic server status is logged as "BizLogic Server started successfully", then
it ensures that BizLogic server has been started.
4. Verify BizPulse server status as follows:
Start the BizPulse Admin utility by executing startBizPulseAdmin.sh/cmd from
<SBM_HOME>/bin location.
After starting the BizPulse Admin utility, use it as follows:
============ Host : sys128.tdiinc.com ============
0) Back
1) Server Monitor
2) Loader
3) Rule Manager
4) Persistent Structure Monitor
5) Event Manager
6) Scheduler
7) File Manager
8) JMS
Enter your selection ( 0 - 8 ) : 1
============ Server Monitor ============
0) Back
1) Print Status
2) Suspend
3) Resume
4) Stop
82
Stopping servers
5) Start
Enter your selection ( 0 - 5 ) : 1
BizPulse state: STARTED
EventsToBeProcessed: 0
State: run
FreeHeapMemory: 225234192
EventsProcessed: 127
HeapMemoryAllocated: 266076160
If "BizPulse state: STARTED" is displayed, then it indicates that the BizPulse server is running.
Stopping servers
Stop the servers using the FirstSteps Console, in the following sequence:
1. Stop BizLogic and BizPulse servers of BusinessManager.
Note: Ensure that BusinessManager servers are stopped before stopping the EJB and Portal
servers.
2. Stop EJB and Portal servers of the application server.
Note: For WebLogic application server, Admin server is stopped along with EJB and Portal
server.
Once the servers are stopped, their status is updated in the respective server log files. See
Locating BusinessManager log files on page 131 for more information.
See Using BusinessManager command line utilities on page 121, Starting and stopping application
servers on page 122 for stopping servers using command line utilities.
The out-of-box installation of BusinessManager is tuned for the development environment. To
improve the performance of your servers, see "Appendix A, Performance Tuning" in Server
Administrators Guide.
83
84
6
Installing BusinessManager service pack
7.6.4
If you have an existing Savvion installation that is an earlier release and you want to upgrade it to
this release, the upgrade procedure requires migration tools that are packaged in a separate
download at the Electronic Software Download site. Contact your Progress Software representative,
if you need assistance with migrations.
Prerequisites
Installing service pack 7.6.4
After installing service pack 7.6.4
Silent installation for service pack 7.6.4
Enabling ApacheDS for SBM
Prerequisites
The following prerequisites must be met before installing Savvion BusinessManager 7.6.4.
Important:
You can upgrade either from Savvion BusinessManager 7.6.1, 7.6.2, or 7.6.3 to Savvion
BusinessManager 7.6.4.
85
Chapter 6: Installing BusinessManager service pack 7.6.4
If you are upgrading from Savvion BusinessManager 7.6.1 or 7.6.2 or 7.6.3 to 7.6.4, then you do
not have to perform application or data migration steps.
1. Install SBM 7.6.1. Users who have already upgraded to 7.6.2 can ignore this and proceed to
step 4 on page 86.
2. Start the servers and log into the BPM Portal at least once.
3. After successful login, log out and shutdown the servers.
4. If you are using SBM 7.6.1, 7.6.2 or 7.6.3, then take a back up of all the files and directories
within SBM_HOME and APPSERVER_HOME.
Installing service pack 7.6.4

You can install SBM 7.6.4 using the Installation wizard.
1. Unzip PROGRESS_SAVVION_BUSINESSMANAGER_7.6.4_INC.zip.
2. Run install.cmd/sh from the extracted
PROGRESS_SAVVION_BUSINESSMANAGER_7.6.4_INC/servicepack-bm764 location.
The Progress Savvion Servicepack 7.6.4 Installer Welcome page appears. It may take few
minutes.
3. Click Next.
Savvion Install Location page appears.
4. Click Choose and browse and select the SBM_HOME location for SBM 7.6.1.
5. Click Next.
Backup Savvion message box appears.
Note: Backing up the data is a prerequisite.
6. Click OK.
Pre-Installation Summary page appears.
7. Click Install.
Installing Progress Savvion Servicepack 7.6.4 page appears.
8. Click Done once the installation is complete.
86
Progress Savvion service pack 7.6.4 is installed.

After installing the service pack 7.6.4:
1. Run bpmigration.cmd/sh from SBM_HOME/servicepack/sp763/bin. Ignore this step,
if you are upgrading from 7.6.2 or 7.6.3 to 7.6.4, and you have already performed this step.
2. Run setupsbm c ProcessViews. Ignore this step, if you are upgrading from 7.6.2 or 7.6.3
to 7.6.4, and you have already performed this step.
Refer to "Reporting tables and views" chapter in BizLogic Developer's Guide.
3. If your application server is JBoss 5.0.1 (Enterprise server) then you have to perform the following
step, otherwise ignore this step:
Single server installation: Update file

<JBOSS_AS_HOME>/server/ejbServer/deploy/bmjms/bm-<database>persistence-service.xml as per the instructions below.
Cluster installation: For each EJB node, update file
<JBOSS_AS_HOME>/server/<ejbNode>/deploy/bmjms/bm-<database>persistence-service.xml as per the instruction below.
In the above file(s), replace line

'LOAD_UNPAGED_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, SCHED_DELIVERY FROM
JBM_MSG_REF WHERE STATE = 'C' AND CHANNEL_ID = ? AND PAGE_ORD IS NULL ORDER
BY ORD'
with
'LOAD_UNPAGED_REFS=SELECT MESSAGE_ID, DELIVERY_COUNT, SCHED_DELIVERY, PAGE_ORD
FROM JBM_MSG_REF WHERE STATE = 'C' AND CHANNEL_ID = ? ORDER BY ORD'.
Here, <JBOSS_AS_HOME> is the JBoss_5.0.1 application server home. This can be found from
APPSERVER_HOME in <SBM_HOME>/bin/sbmclientenv.cmd(.sh).<database>. This is
the same as the value of sbm.db.default in <SBM_HOME>/conf/sbmdb.properties.
Here <ejbNode> is the name of the EJB node.
4. Clear your Web browser cache and JRE cache and restart the browser before logging into BPM
Portal.
Note: Clear any application server temporary folders.
5. Disable the JSP compilation, if you have enabled it before applying the patch.
6. After upgrading to BPM Studio 7.6.4, re-build all the installed applications in BPM Studio and
select the Copy files to server only option from BPMStudio to SBM server.
7. Optionally, if you plan to use ApacheDS as your LDAP server, perform the steps listed in
Enabling ApacheDS for SBM on page 88.
8. Restart all the servers.
Note: In the case of clusters, perform the steps 3 to 8 on all the nodes of each cluster
individually.
87
Silent installation for service pack 7.6.4

Using the silent installer, you can upgrade either from Savvion BusinessManager 7.6.1, 7.6.2, or
7.6.3 to Savvion BusinessManager 7.6.4.
To install service pack 7.6.4 using the silent installer:
1. Unzip the PROGRESS_SAVVION_BUSINESSMANAGER_7.6.4_ALL.zip file.
2. Open the installer.properties file in the extracted location.
3. Provide the absolute SBM installed location in the installer.properties file. For example:
USER_INSTALL_DIR = C:\\USERS\\SBM76SP2
4. Optionally, if you want to upgrade to WebLogic server to 10.3.3, then provide option then provide
WEBLOGIC_USER_SELECTED=1 otherwise retain the default value "0"
WEBLOGIC_USER_SELECTED=0
5. Open a command prompt and go to the install.exe location that is extracted location of
the Zip file.
6. Execute the following command:
install.exe i silent f (Absolute location of the installer.properties
file)
For example:
C:\servicepack-bm763> cd Installer
C:\servicepack-bm763\Installer>install.exe -i silent -f
C:\servicepack-bm763\installer.properties
Note: For cluster, use silent installation on all the nodes of the cluster.

SBM supports Apache DS 1.5.7 LDAP server.
If you must integrate SBM with ApacheDS, then perform the following:
1. Navigate to umacl.conf file in SBM_Home/conf folder.
2. Set the following attributes in umacl.conf file as listed in the following Table 10 on page 89:
88
Table 10: Configuring umacl.conf

Property name
Property value
usermgr.realm.type ldap
ldap.server.provider ApacheDS
Description
Realm type
This property specifies

the realm type.
Possible values:
jdbc|ldap|
ldaphybrid|custom
Directory Server
Provider

the directory server
provider name. Legal
values are: Netscape
|MSActive |ApacheDS
The URL of the

directory server
Directory Server
ldap.server.location
(Example:
location
ldap://localhost:10389)
ldap.user.name
Comment
The admin user name

for connecting to the
Admin user name of
directory server
directory server
(Example:
uid=admin,ou=system)
This property stores

the location / URL of
the directory server.
This property stores
the admin user name
for connecting to the
directory server.
the admin user
password. Provide the
encrypted password.
ldap.user.password
The password of the

admin user
Admin user password Note: You can

encrypt the password
using
encrypt.cmd/sh file
in SBM_Home/bin.
LDAP root which the

ldap.user.search.
LDAP user search root search for User start
root
with
Example: ou=Users,
dc=progress,dc=com
ldap.group.search. LDAP group search

root
root
LDAP root which the

Example: ou=Groups,
search for Group start
dc=progress,dc=com
with
usermgr.
casesensitive
false
Specifies whether the

user and group names
are case sensitive.
false
For ApacheDS, if the

LDAP SSL is enabled,
This value is blank by
the value must be
default.
true otherwise, set it
to false.
ldap.ssl
Note:
89
The LDAP API provides an LDAP server failover mechanism by a | separated list of LDAP
servers the property name is ldap.server.location in umacl.conf.
The '|' character must be preceded and followed by a space character in the property file. Also,
instead of the pipeline character, you can use comma as delimiter.
For using ApacheDS LDAP Server from PCT, the following attributes must have the values
mentioned against them:
group.object.class = groupOfUniqueNames
group.name.attr = cn
90
7
Setting up BusinessManager as service
This chapter describes installing BusinessManager as Windows service on Pramati, WebLogic
or JBoss application server and installing BusinessManager as Linux service on JBoss.
Installing BusinessManager as a Windows service
Running BusinessManager as a Daemon in Linux

You can install BusinessManager as Windows service when it is installed on PramatiWebLogic,
or JBoss (both Community and Enterprise edition), application server.
The generic script installSBMService.cmd can be used to install the SBM servers as Windows
services on JBoss, Pramati and Weblogic application servers. The script calls Apache commons
daemon prunsrv.exe to install SBM servers as services in single server and clustered
environment.
Note:
The generic uninstallSBMService.cmd is used to uninstall the SBM services.
91
Chapter 7: Setting up BusinessManager as service
Install SBM Pramati services

You can install SBM Pramati Servers as Windows services in both single server and clustered
environment.
Single server environment To install SBM Pramati Ejb server and Portal server as Windows
services, execute installSBMService.cmd from SBM_HOME/pramati/server/bin
location. This command installs the SBM Ejb server and Portal server as Windows services.
This script by default installs SBM Ejb server and Portal server services. It is also possible to
install one service at a time as follows.
installSBMService.cmd ejbServer ejb
Clustered environment To install SBM Pramati cluster nodes as Windows services, execute
installSBMService.cmd as shown below from SBM_HOME/pramati/server/bin location.
installSBMService.cmd [nodeName] [nodeType]
Examples:
installSBMService.cmd ejbnode1 ejb
installSBMService.cmd webnode1 web
installSBMService.cmd jmsnode1 jms
installSBMService.cmd proxy proxy
Install SBM WebLogic services

You can install SBM Weblogic Servers as Windows services in both single server and clustered
environment.
Single server environment To install SBM Weblogic Ejb server and Portal server as
Windows services, execute installSBMService.cmd from DOMAIN_LOCATION location.
This command installs the Admin server, Ejb server and Portal server as Windows services.
It is also possible to install one service at a time as follows.
installSBMService.cmd [nodeName] [nodeType] [adminUrl]
Examples:
installSBMService.cmd adminServer admin
installSBMService.cmd ejbServer ejb localhost:14002
Important: The adminUrl parameter is not required for admin server installation.
Clustered environment To install SBM Weblogic cluster nodes as Windows services,

execute installSBMService.cmd as follows from the DOMAIN_LOCATION.
installSBMService.cmd [nodeName] [nodeType] [adminUrl]
Example:
installSBMService.cmd adminServer admin
installSBMService.cmd ejbnode1 ejb localhost:14002
92
installSBMService.cmd webnode1 web localhost:14002

installSBMService.cmd proxy proxy localhost:14002
Important: The adminUrl parameter is not required for admin server installation. Ensure that
admin server and proxy is installed on master node. In the case of horizontal cluster, ensure
that admin server is started on master node before startup of SBM cluster nodes on slave node.
Note:
After installation of SBM services based on the application server, log files get generated for all
installed services at SBM_HOME/logs location.
Install SBM JBoss services

You can install SBM JBoss Servers as Windows services in both single server and clustered
environment.
Single server environment To install SBM Joss Ejb server and Portal server as Windows
services, execute installSBMService.cmd from SBM_HOME/jboss/bin location. This
command by default installs the SBM Ejb server and Portal server as Windows services. It is
also possible to install one service at a time as follows.
Example: installSBMService.cmd ejbServer ejb
Clustered environment To install SBM Joss cluster nodes as Windows services, execute
installSBMService.cmd as follows from SBM_HOME/jboss/bin location.
installSBMService.cmd [nodeName] [nodeType]
Examples:
installSBMService.cmd ejbnode1 ejb
installSBMService.cmd webnode1 web
Removing Windows services

The uninstallSBMService.cmd is used to uninstall the SBM servers services in single server
and cluster environment.
This script can be located depending on the application server.
JBoss: SBM_HOME/jboss/bin
Pramati: SBM_HOME/pramati/server/bin
WebLogic: DOMAIN_LOCATION
Single Server Environment To uninstall SBM servers services in single server environment,
execute uninstallSBMService.cmd. By default this script uninstalls ejbServer and portalServer.
In the case of Weblogic appServer ejb, portal and admin servers gets uninstalled. It is also possible
to uninstall single service at a time.
uninstallSBMService.cmd
[nodeName]
Example: uninstallSBMService.cmd ejbServer
93
Clustered Environment To uninstall SBM cluster node services in clustered environment,

execute uninstallSBMService.cmd as shown below.
uninstallSBMService.cmd
[nodeName]
Example: uninstallSBMService.cmd ejbnode1
Monitor or Control SBM services

You can monitor a service using control or monitor window which gets launched on the execution
of monitorSBMService.cmd.
This script location depends on the application server.
JBoss - SBM_HOME/jboss/bin
Pramati - SBM_HOME/pramati/server/bin
WebLogic DOMAIN_LOCATION
To monitor or control SBM service in single server environment, execute
monitorSBMService.cmd. By default this script launches Ejb server and Portal server control
GUI in system. In the case of Weblogic application server ejb, portal and admin service control
GUI gets launched.
To monitor SBM cluster node services in a cluster environment, execute monitorSBMService.cmd
as follows.
monitorSBMService.cmd [nodeName]
Example: monitorSBMService.cmd ejbnode1
The following is the monitor/control GUI for ejbnode1. You can start/stop service from this control
GUI.
Figure 45: Monitoring node
94

You can run BusinessManager as a daemon in Linux when it is installed JBoss (both Community
and Enterprise edition) as application server.
Note:
To start Pramati servers as a cornjob on Linux, refer to Pramati server documentation.
BusinessManager as a Daemon on JBoss

To run BusinessManager as daemon in Linux:
1. Set the value for the property RUN_AS_DAEMON as true in sbmserverenv.sh in
SBM_Home/jboss/bin.
2. Start EJB server as daemon by executing startEjbServer.sh in SBM_Home/bin.
3. Start Portal server as daemon by executing startPortalServer.sh in SBM_Home/bin.
95
96
8
Uninstalling BusinessManager
This chapter guides you to uninstall BusinessManager 7.6.4.
Important: Currently, uninstalling BusinessManager service pack 7.6.4 is not supported. If you
have installed using incremental installer, you must uninstall 7.6.1 and remove 7.6.4 files manually.
On uninstalling BusinessManager, all BusinessManager related files are removed from the file
system. Even the files modified after 7.6.4 installation are removed. Only the new files specific to
7.6.4 remain in the folder.
You can uninstall BusinessManager 7.6.4 in the following ways:
Using the interactive Uninstallation Wizard

Using the Silent Uninstallation Utility
They are described in the following sections.
97
Chapter 8: Uninstalling BusinessManager
Before uninstalling
Using the Uninstaller
Using the silent uninstallation utility
After uninstalling
Before uninstalling
Do the following before uninstalling BusinessManager:
1. Stop BusinessManager servers and application servers. See Using BusinessManager command
line utilities on page 121 for more information.
2. Before uninstalling the BusinessManager installed on WebSphere application server:
a) Remove the server and resources created for BusinessManager by executing the following
command from <SBM_HOME>/websphere/bin:
removesbm.cmd/sh
Note: If this installation is a part of a cluster setup, then you need not perform this step.
b) Remove the WebSphere profile created for BusinessManager by executing the following
command from <SBM_HOME>/websphere/bin:
removeprofile.cmd/sh
Note: In the case of a cluster setup, perform the above step on all the nodes of the cluster.
c) If this installation is part of a cluster, then remove the WebSphere admin profile created for
BusinessManager by executing the following command from <SBM_HOME>/cluster/bin
on the machine on which admin profile is created:
removeadminprofile.cmd/sh

To uninstall BusinessManager:
1. To uninstall BusinessManager on Windows:
Select Start > Programs > Savvion > SBM 7.6 SP1 (or 7.6.4) > Uninstall.
Optionally, execute the following command from <SBM_HOME>/_uninst to invoke the

Uninstallation wizard.
98
uninstall.cmd/sh
The Uninstaller wizard the Welcome page appears.

Figure 46: The Uninstallation - Welcome page
2. Review the text and click Next. The Installation Summary page appears.
Figure 47: Uninstallation - summary
3. Review the summary and click Next. The Remove Existing Files dialog box appears.
Figure 48: Uninstallation - remove files
Uninstaller provides an option to delete or retain the files that are modified after BusinessManager
installation. This option is provided for the following files:
Files in BusinessManager home.

Application server files used by BusinessManager within the application server home.
All the files that are not modified since the BusinessManager is installed, are removed
automatically during uninstallation.
Note: Files that are used during uninstallation and the files copied into any directory within
BusinessManager home after BusinessManager installation are not removed by the uninstaller.
4. Click Yes to all. The Uninstaller Successful page appears.
5. Click Finish. The BusinessManager is usinstalled.
6. When uninstallation is completed, back up the required files that are retained after uninstallation
and then remove BusinessManager Home directory manually.
Note: The uninstaller does not support module level uninstalling.
99
Using the silent uninstallation utility

You can uninstall BusinessManager using the silent installation utility.
This can be done only after the a BusinessManager installation has been uninstalled once using
the uninstallation wizard and the uninstallation was recorded.
On recording the uninstallation, a template response file containing all the commands used while
uninstalling BusinessManager is generated. Using this template response file, silent
BusinessManager uninstallation can be done.
Recording the BusinessManager uninstallation

To record the uninstallation, execute the following command from <BM installerHome>/_uninst
location:
Note: The response file name includes the complete path information.
For Windows:
uninstaller.exe -options-record <response file name>
For UNIX:
uninstaller.bin -options-record <response file name>
During interactive uninstallation, using an Uninstallation wizard it is possible to specify whether

the product files that are modified after installation need to removed or retained. However, while
using silent uninstallation utility, these values must be specified in the response file by adding the
following lines in the generated response file:
- G removeExisitingResponse=yesToAll
- G removeModifiedResponse=yesToAll
Uninstalling with the silent uninstallation utility

To silently uninstall BusinessManager, execute the following command from <BM
installerHome>/_uninst:
For Windows:
uninstaller.exe -options <response file name> -silent
For Linux, Solaris and AIX:

uninstaller.bin -options <response file name> -silent
Note: The response file name includes the complete path information.
100
After uninstalling
After uninstalling
Based on the application server used, the following additional steps must be performed to
complete the uninstallation of BusinessManager.
1. WebLogic application server: Navigate to <WebLogic_HOME>/user_projects/domains
folder and delete the domain directory created for BusinessManager.
2. WebSphere application server: Navigate to
<WEBSPHERE_HOME>/WebSphere/AppServer/profiles and delete the profile directory
created for BusinessManager.
Note: For application servers embedded within BusinessManager, the application server directory
is deleted during uninstallation.
101
102
A
Supported platforms and configurations
This appendix lists supported platforms and configurations for BusinessManager.
BusinessManager supported platforms
BusinessManager supported configurations
BusinessManager supported databases
BusinessManager supported platforms

The following Table 11 on page 104 lists the platforms supported by BusinessManager 7.6.4.
103
Appendix A: Supported platforms and configurations
Table 11: BusinessManager supported platforms

Category
Application servers
Software
Pramati 6.0 SP4 (Embedded in BusinessManager)
WebLogic 10.3.0 and 10.3.3
WebSphere 6.1.0.31 and 7.0.0.13
JBoss Community Edition 5.1 (Embedded in BusinessManager) and JBoss Enterprise
Application Platform 5.0.1/5.1.1.
Operating systems
Microsoft Windows Server 2003 Standard/Enterprise R2, 32-bit and 64-bit (Process
Modeler and BPM Studio are not supported on Windows 2003)
Microsoft Windows Server 2008 Standard/Enterprise R2, 32-bit and 64-bit (Process
Modeler and BPM Studio are not supported on Windows 2008)
Microsoft Windows XP SP3, 32-bit (Process Modeler and BPM Studio are supported)
Except WebSphere application server, all application servers are supported only for
application development, not for production.
Microsoft Windows 7 Professional/Enterprise (32/64 bit) (For Pramati, WebLogic,
and JBoss application servers. Not for production environment)
Sun Solaris 10 (SPARC), 64-bit (Solaris SPARC only supported for BusinessManager
servers; BPM Studio and Process Modeler only supported on Windows). Only Pramati
and WebLogic application servers are supported on Sun Solaris.
IBM AIX 6.1 TL6 SP3, 64-bit (for WebSphere application server only. BPM Studio
and Process Modeler only supported on Windows)
Redhat Linux 5 update 5, 64-bit (with Oracle 10g, and Oracle 11g R2 databases only;
BPM Studio and Process Modeler only supported on Windows)
SUSE Linux Enterprise Server 11 SP1 64-bit (for WebSphere and JBoss application
servers with Oracle 10g, and Oracle 11g R2 databases only; BPM Studio and Process
Modeler only supported on Windows)
Oracle Enterprise Linux 5.5
Browsers
Internet Explorer (IE) 7.0/8.0 (32 bit) (Requires Java plugin 1.5.0; Supported on
Windows only; Needs to disable MS JVM)
Mozilla FireFox 3.6 (32 bit) (Requires Java plugin 1.5.0; Supported on both Windows
and Solaris)
Java Technology (J2EE)

(32 or 64 bit JDK depending
on the application servers
support)
J2SDK 1.6 is supported for Process Modeler and BPM Studio. (BEA JRockit is not
supported.).
JDK 1.6.20 for Pramati, JBoss 5.1 community edition, JBoss Enterprise Application
Platform 5.0.1, and Tomcat 6.x (JDK bundled with product installer)
JDK 1.5.xx for WebSphere 6.1.0.31 (JDK bundled with application server)
JDK 1.6.xx for WebSphere 7.0.0.13 (JDK bundled with application server)
JDK 1.6.xx for WebLogic 10.3.0 and 10.3.3 (JDK bundled with application server)
JDK 1.6.20 for BPM Studio and Process Modeler
Specific service information depends on your application server.
104
Category
J2EE 1.3/1.4
Software
Supported for all application servers. Specific J2EE service information depends on
application server.
Database / JDBC Driver
Oracle 10g/11g R2 Enterprise Edition (J2SDK 5.0; MS Windows 2000 SP4, Windows
Server 2003 Std/Ent; Solaris 10; Redhat Linux 5.5; SUSE Linux Enterprise Server
11); Windows Server 2008 Std/Ent Edition (64 bit)
Oracle Express 10g (J2SDK 5.0; Windows 2003/XP; RedHat 5.5. Not supported on
WebSphere)
Oracle Real Application Clusters (RAC) - 11g R1, R2 and10g R2 (J2SDK 5.0; Windows
Server 2003 Std/Ent; Solaris 10; Redhat Linux 5.x; SUSE Linux Enterprise Server
11; Only on WebLogic and JBoss)
MS SQL Server 2005 (J2SDK 5.0; MS Windows Server 2003 Std/Ent. MS Windows
XP Professional SP3. Not supported on WebSphere)
IBM DB2 9.5 (J2SDK 5.0; Windows Server 2003 Std/Ent; IBM AIX 6.1 TL6 SP3; Only
on WebSphere)
MS SQL Server 2008 (MS Windows Server 2003 Std/Ent.; MS Windows XP
Professional SP3, Windows Server 2008 Std Edition: Not supported on WebSphere)
OpenEdge 10.2B06 (Microsoft Windows Server 2003/2008; Windows XP; Windows
7; Redhat Linux; SUSE Linux. Supported on Pramati and JBoss)
Compatible mail servers
Sendmail (UNIX)
Exchange or IMAP compatible (Windows)
User managementLDAP
BusinessManager Realm (Database-based)

Microsoft Active directory, on Windows Server 2008 Standard/Enterprise
Sun Java System Directory Server 5.2, on Windows Server 2003 Standard/Enterprise,
and Solaris 10
Oracle Directory Server Enterprise Edition 11g R1
ApacheDS 1.5.7
Document Management
5
Server
EMC Documentum DMS Adapter (XP Professional SP2/Vista/Windows 7 are

supported.)
Alfresco DMS Adapter (XP Professional SP2/Vista/Windows 7 are supported.)

BusinessManager has been extensively tested on the platforms, tools, and systems listed in the
following Table 12 on page 106.
Connectors for the Document Management Servers are available as separate Progress Savvion component
products.
105
Table 12: Tested and Supported Configurations

Server operating
system
Browser
Application server
DBMS
MS Windows Server IE 7.0/8.0

Pramati 6.0 SP4
2003 Standard/
or Mozilla
(embedded in
Enterprise R2 (64 bit) FireFox
BusinessManager)
3.6
JBoss Community
Edition 5.1 (embedded
in BusinessManager;
only for development.)
JBoss Enterprise
Application Platform
5.0.1/5.1.1
Oracle 10g/ 11g

R2 Ent Edition,
Oracle 10g
Express Edition
Oracle (RAC) 11g R1, R2 and
10g R2
MS SQL Server
2005/2008
IBM DB2 9.5
WebLogic 10.3.0 and

OpenEdge
Weblogic 10.3.3
10.2B06
WebSphere 6.1.0.31
or WebSphere
7.0.0.13
MS Windows Server as above JBoss Enterprise
MS SQL Server
2008 Standard(64 bit)
2008
5.0.1/5.1.1 and JBoss
community edition 5.1 OpenEdge
10.2B06
J2SDK
User Management
J2SDK 6.0
BusinessManager
DB-based (JDBC)
Note: For
WebSphere
and
WebLogic
the JDK
bundled with
the
application
server is
used.
LDAP Realm:
Sun Java System
Directory Server 5.2
Oracle Directory
Server Enterprise
Edition 11g R1
MS Active Directory
5.2
ApacheDS 1.5.7
as above
BusinessManager
DB-based (JDBC)
LDAP Realm:MS
Active Directory 6.1
ApacheDS 1.5.7
Oracle 10g/11g R2
Enterprise Edition
MS Windows Server as above
Pramati 6.0 SP4
2008 Enterprise
(embedded in
BusinessManager)
MS SQL Server
2008
OpenEdge
JBoss Community
10.2B06
Edition 5.1 (embedded
Oracle 10g/11g R2
in BusinessManager;
Enterprise Edition
only for development.)
as above
BusinessManager
DB-based (JDBC)
LDAP Realm:
MS Active Directory
6.1
ApacheDS 1.5.7
JBoss Enterprise
5.0.1/5.1.1
WebLogic 10.3.0
WebSphere 6.1.0.31
or WebSphere
7.0.0.13
106
Server operating
system
Browser
Application server
Windows XP
as above
Pramati 6.0 SP4
Professional SP3 (32
(embedded in
bit)
BusinessManager)
DBMS
Oracle 10g
Express
J2SDK
as above
User Management
BusinessManager
DB-based (JDBC)
ApacheDS 1.5.7
MS SQL Server
2005/2008
JBoss Community
Edition 5.1 and JBoss
OpenEdge
Enterprise Application
10.2B06
Platform 5.0.1/5.1.1
WebLogic 10.3.0
Windows 7
Professional/Ent.
(32/64 bit)
as above as above
Oracle 10g/ 11g

R2 Ent Edition,
Oracle 10g
Express Edition
as above
BusinessManager
DB-based (JDBC)
ApacheDS 1.5.7

10g R2
MS SQL Server
2005/2008
IBM DB2 9.5
OpenEdge
10.2B04, 10.2B05
Sun Solaris 10
Mozilla
FireFox
3.6
Pramati 6.0 SP4

(embedded in
BusinessManager)
Oracle 10g/11g R2 as above

Ent

WebLogic 10.3.0 and
10g R2
Weblogic 10.3.3
BusinessManager
DB-based (JDBC)
LDAP Realm:
Sun Java System
Directory Server 5.2
Oracle Directory
Server Enterprise
Edition 11g R1
ApacheDS 1.5.7
IBM AIX 6.1 TL6 SP3 as above WebSphere 6.1.0.31

(64 bit)
or WebSphere
7.0.0.13
IBM DB2 9.5
1.5.x
BusinessManager
DB-based (JDBC)
107
Server operating
system
Redhat Linux
5update 5 (64 bit)
Browser
N/A
Application server
Pramati 6.0 SP4

(embedded in
BusinessManager)
DBMS
Oracle 10g/11g R2
Ent
J2SDK
as above
User Management
BusinessManager
DB-based (JDBC)
ApacheDS 1.5.7

10g R2
JBoss Enterprise
5.0.1/5.1.1 and JBoss
OpenEdge
Community Edition 5.1
10.2B04, 10.2B05
WebLogic 10.3.0
WebSphere 6.1.0.31
or 7.0.0.13
SUSE Linux
N/A
Enterprise Server 11
SP1 (64 bit)
WebSphere 6.1.0.31
or 7.0.0.13
Oracle Enterprise
Linux
WebLogic 10.3.0
Oracle 10g/11g R2
Ent
Oracle (RAC) JBoss Enterprise
Application Platform 11g R1, R2 and
5.0.1/5.1.1 and JBoss 10g R2
Community Edition 5.1 OpenEdge
10.2B04, 10.2B05
WebLogic 10.3.3
and
as above
as above

10g R2
JBoss EAP 5.1.1
Important: WebLogic 10.3.3 is supported only on MS Windows Server 2003, Sun Solaris 10 and
Oracle Enterprise Linux operating system with Oracle 10g/11g R2 Ent or Oracle 10g/11g R2 (RAC)
database. However, note that it has following limitations because of WebLogic 10.3.3 for which a
service request is filed with Oracle Corporation.
You must disable the BizLogic and BizPulse auto-startup feature. That means, you will have
to manually start BizLogic and BizPulse servers. For more details, refer to BizLogic and BizPulse
auto-startup on page 129.
You cannot create custom report in BPM Portal.

The following Table 13 on page 109 lists the supported databases for all application servers for
specific operating systems.
108
Table 13: Supported databases for all application servers

Operating Systems Pramati 6.0 SP4
Microsoft Windows
Oracle 10g/11g
Server 2003
R2 Enterprise
Standard/Enterprise
Edition
R2 (64 bit)
Oracle Express
10g
MS SQL Server
2005
MS SQL Server
2008
OpenEdge
10.2B04
Microsoft Windows
Server 2008
Std/Enterprise
Edition (64 bit)
Oracle 10g/11g
R2 Enterprise
Edition
Weblogic 10.3.0
WebLogic
10.3.3
Oracle 10g/11g R2
Enterprise Edition
Oracle
10g/11g
R2
Enterprise
Edition
Oracle Express 10g

Oracle (RAC) - 11g
R1, R2 and 10g R2
Oracle
MS SQL Server 2005 Express
MS SQL Server 2008 10g
MS SQL
Server
2005
WebSphere
6.1.0.31 and
7.0.0.13
Oracle 10g/11g Oracle 10g/11g R2

R2 Enterprise Enterprise Edition
Edition
Oracle Express 10g
IBM DB2 9.5
MS SQL Server
2005
MS SQL Server
2008
OpenEdge 10.2B06
Oracle (RAC) - 11g
R1, R2 and 10g R2
MS SQL
Server
2008
Oracle 10g/11g R2
Enterprise Edition
MS SQL Server 2008
MS SQL Server
2008
Oracle 10g/11g Oracle 10g/11g R2

R2 Enterprise Enterprise Edition
Edition
MS SQL Server
IBM DB2 9.5
2008
OpenEdge 10.2B06
OpenEdge
10.2B04, 10.2B05
Windows XP
Professional SP3
(32 bit)
Oracle Express
10g
MS SQL Server
2005
JBoss 5.1
community edition
and JBoss
Enterprise
Application
Platform
5.0.1/5.1.1
Oracle (RAC) - 11g

R1, R2 and 10g R2
Oracle Express 10g
MS SQL Server 2005
MS SQL Server 2008
MS SQL Server
2008
OpenEdge
10.2B04, 10.2B05
IBM DB2 9.5
Oracle Express 10g

MS SQL Server
2005
MS SQL Server
2008
OpenEdge 10.2B06
Oracle (RAC) - 11g
R1, R2 and 10g R2
109
Operating Systems Pramati 6.0 SP4
Windows 7
Professional/Ent.
(32/64 bit)
Oracle 10g/11g
R2 Enterprise
Edition
Oracle Express
10g
MS SQL Server
2005
Weblogic 10.3.0
WebLogic
10.3.3
WebSphere
6.1.0.31 and
7.0.0.13
IBM DB2 9.5
Oracle 10g/11g R2
Enterprise Edition
Oracle Express 10g
MS SQL Server 2005
MS SQL Server
2005
MS SQL Server 2008
MS SQL Server
2008
OpenEdge 10.2B06
Oracle (RAC) - 11g
R1, R2 and 10g R2
OpenEdge
10.2B04, 10.2B05
Oracle 10g/11g
R2 Enterprise
Edition
Oracle 10g/11g R2
Enterprise Edition
Oracle (RAC) - 11g
R1, R2 and 10g R2
Oracle
(RAC) 11g R1,
R2 and
10g R2
IBM AIX 6.1 TL6

SP3 (64 bit)
Redhat Linux 5
update 5 (64bit)
IBM DB2 9.5
Oracle 10g/11g
R2 Enterprise
Edition
Oracle 10g/11g
Oracle 10g/11g R2
R2 Enterprise
Enterprise Edition
Edition
OpenEdge 10.2B06
Oracle 10g/11g R2
Enterprise Edition
Oracle (RAC) - 11g

OpenEdge
R1, R2 and 10g R2
10.2B04, 10.2B05
SUSE Linux
Enterprise Server
11 SP1 (64 bit)
Oracle (RAC) - 11g

R1, R2 and 10g R2
Oracle 10g/11g
Oracle 10g/11g R2
R2 Enterprise
Enterprise Edition
Edition
OpenEdge 10.2B06
Oracle 10g/11g R2
Enterprise Edition
Oracle (RAC) - 11g
R1, R2 and 10g R2
R2
Oracle Enterprise
Linux
110
Oracle 10g/11g R2
Enterprise Edition
Oracle Express 10g
MS SQL Server
2008
Sun Solaris 10
(SPARC) (64 bit)
JBoss 5.1
community edition
and JBoss
Enterprise
Application
Platform
5.0.1/5.1.1
Oracle (RAC) - 11g

R1, R2 and 10g R2
Note:
WebSphere
7.0.0.23
application
server is
supported.
Oracle (RAC) - 11g

R1, R2 and 10g R2
Oracle
(RAC) 11g R1,
R2 and
10g R2
Note: JBoss Enterprise Application Platform 5.1.1 supports DB2 9.5 database for the supported
Operating Systems.
111
112
B
Sample scripts for creating your database
This appendix provides command syntax and sample scripts for creating your database.
Note: Values used in these sample scripts may not be optimum for Production installations. Please
consult you database administrator before using these sample scripts in production.
Sample scripts for Oracle 10g/11g enterprise edition, Oracle Express 10g, Oracle 11g/10g
(RAC)
Sample scripts forMS SQL Server 2005, MS SQL Server 2008
Sample scripts for IBM DB2
Sample scripts for OpenEdge 10.2B
Sample scripts for Oracle 10g/11g enterprise edition,

Oracle Express 10g, Oracle 11g/10g (RAC)
To create Oracle database:
1. Create tablespace and temporary tablespace for BusinessManager by executing the following
statements:
CREATE TABLESPACE EBMS_USER_DATA
DATAFILE 'EBMS_USER_DATA.ORA' SIZE 256M
DEFAULT STORAGE
(INITIAL 16K
113
Appendix B: Sample scripts for creating your database
NEXT 16K
MINEXTENTS 1
MAXEXTENTS UNLIMITED
PCTINCREASE 50
)ONLINE;
CREATE TEMPORARY TABLESPACE EBMS_TEMPORARY_DATA
TEMPFILE 'EBMS_TEMPORARY_DATA.ORA' SIZE 64M
EXTENT MANAGEMENT LOCAL;
2. Verify the tablespace created by executing the following statement:

SELECT TABLESPACE_NAME, STATUS FROM DBA_TABLESPACES;
3. Create a database user by executing the following statements:

CREATE USER ebms
IDENTIFIED BY ebms
DEFAULT TABLESPACE EBMS_USER_DATA
TEMPORARY TABLESPACE EBMS_TEMPORARY_DATA;
4. Verify the database user created by executing the following statement:

SELECT USERNAME FROM sys.dba_users;
5. Grant create session, create table, create sequence, and create view privileges to the user by
executing the following statement:
GRANT create session, create table, create sequence, create view To ebms;
6. Allocate unlimited quota on tablespace to the database user by executing the following
statements:
ALTER USER ebms
QUOTA UNLIMITED ON EBMS_USER_DATA;
Sample scripts forMS SQL Server 2005, MS SQL

Server 2008
To create MS SQL Server 2005 or MS SQL Server 2008 database:
1. Create a database for BusinessManager in MS SQL server by executing the following statements:
CREATE DATABASE sbmdb
ON PRIMARY
( NAME = sbm_1_dat,
FILENAME = 'c:\mssqlserver\data\sbm.mdf',
SIZE=256MB,
FILEGROWTH=10% ),
( NAME = sbm_2_dat,
FILENAME = 'c:\mssqlserver\data\sbm.ndf',
SIZE=64MB,
FILEGROWTH=10% )
LOG ON
( NAME = sbm_log,
FILENAME = 'c:\mssqlserver\data\sbm.log',
SIZE=5MB,
FILEGROWTH=10% )
COLLATE SQL_Latin1_General_CP1_CS_AS;
114
The above script creates a Case Sensitive MS SQL database.

2. Verify the database created by executing the following statements:
USE master;
EXEC sp_databases;
3. Create a database user and grant database owner privileges to the user by executing the
following statements:
USE sbmdb;
EXEC sp_addlogin 'sbm','sbm','sbmdb';
EXEC sp_addrolemember 'db_owner','sbm';
EXEC sp_adduser 'sbm','sbmdb';
4. Set the ANSI null default option of the database to ON by executing the following
statements:
EXEC sp_dboption @dbname='sbmdb',@optname='ANSI null default',@optvalue='on';

To create IBM DB2 database:
1. Create BusinessManager database by executing the following statements:
CONNECT RESET;
CREATE DATABASE sbmdb;
2. Verify the database created by executing the following statement:

list database directory
Database names and the their details are listed in the log file.
3. Create a user in the operating system or use an existing operating system user by the name,
sbm_user as the BusinessManager database user.
4. Connect to BusinessManager database and grant database owner privileges to the above user
by executing the following statements:
CONNECT TO sbmdb;
GRANT DBADM, CREATETAB, CONNECT, IMPLICIT_SCHEMA, LOAD on DATABASE to USER
sbm_user;
5. Create Bufferpool for BusinessManager data and temporary data by executing the following
statements:
CREATE BUFFERPOOL sbmbf8k SIZE 800 PAGESIZE 8 K;
CREATE BUFFERPOOL sbmtemp SIZE 400 PAGESIZE 8 K;
CONNECT RESET;
Note: The database page size for IBM DB2 is 8 K.
115
6. Create tablespace for BusinessManager data and temporary data by executing the following
statements:
CONNECT TO sbmdb;
CREATE TABLESPACE sbm_user_data PAGESIZE 8 K MANAGED BY DATABASE USING (file
'D:\DB2\sbm_appl_data' 64000) BUFFERPOOL sbmbf8k;
CREATE USER TEMPORARY TABLESPACE sbm_temp_data PAGESIZE 8 K MANAGED BY SYSTEM
USING ('D:\DB2\sbm_temp_datadir') BUFFERPOOL sbmtemp;
7. Grant privileges to use the above created tablespaces to the database user by executing the
following statements:
GRANT USE OF TABLESPACE sbm_user_data TO USER sbm_user;
GRANT USE OF TABLESPACE sbm_temp_data TO USER sbm_user;

To create OpenEdge 10.2B SP04 or 10.2B SP05 database:
1. Following environment variable need to be set before creating BusinessManager database in
setenv.cmd/sh.
Note: In <SBM_HOME>/dbscripts/openedge/preparedatabase folder windows and
unix folders are available. The setenv.cmd file is available within windows folder and
setenv.sh file is available within unix folder.
a) DLC : This is your machine path where OpenEdge is installed.
b) OE_WSDIR : This is OpenEdge working directory, usually machine path of "WRK" folder in
OpenEdge working directory.
c) DATAFOLDER_NAME : This folder is inside "OE_WSDIR" directory. BusinessManager
database gets created within DATAFOLDER_NAME directory.You can change the default
name if it conflicts with the existing one.
2. Create BussinessManager database by running the following command file.
createsbmdb.cmd/sh
Note: If you run this script on unix, then it creates database administrator as dbadmin and
database user as dbuser. To achieve this in Windows, perform steps Step 4 and Step 5 .
If environment variables in "setenv.cmd/sh" are set properly, then the database is created
successfully.
If there are errors, then it will terminate with an error message.
3. Start the BusinessManager database using the following command:
startsbmdb.cmd/sh
This allows to interact with newly created database.
4. Create a DBA user by using following command.
createdbadmin.cmd
5. To create a database user run the following command.
createdbuser.cmd
116
6. To drop a database user execute the following command.

dropdbuser.cmd
7. You need to delete BusinessManager database first, in order to create a fresh copy of database.
To delete the database use the following command:
deletesbmdb.cmd
8. JTA-enabling the OpenEdge sbmdb database can be done using the following OpenEdge
command line when the database is offline.
proutil <db pathname> -C enablejta
117
118
C
Customizing temporary directory and log
level for installer
This appendix guides you to customize the temporary directory and the log level for
BusinessManager installer.
Customizing temporary directory
Customizing log levels
Customizing temporary directory

While installing BusinessManager, if there is insufficient space in the default temporary directory,
then another temporary directory having 2 GB of available space can be used.
To use a non-default temporary directory, use the following command while invoking the installer:
On Windows: setupwin32.exe -is:tempdir <directory_name>

On Solaris: setupsolarisSparc.bin -is:tempdir <directory_name>
On AIX: setupaix.bin -is:tempdir <directory_name>
On Linux: setuplinux.bin -is:tempdir <directory_name>
Where, <directory_name> is the fully qualified name of the temporary directory.
119
Appendix C: Customizing temporary directory and log level for installer
Customizing log levels

The following Table 14 on page 120 provides information about various log level options available
for BusinessManager installation.
Table 14: Log level information
Log level
Description
INFO
Provides a basic set of details on the BusinessManager installation.

Installer wizard will be invoked in INFO level by default.
DEBUG
Provides a more comprehensive detail about the installation, which can

be used for debugging an installation.
To set DEBUG log level for BusinessManager installation process, use the following command while
invoking the installer:
On Windows: setupwin32.exe -W logger.logLevel=DEBUG

On Solaris: setupsolarisSparc.bin -W logger.logLevel=DEBUG
On AIX: setupaix.bin -W logger.logLevel=DEBUG
On Linux: setuplinux.bin -W logger.logLevel=DEBUG
120
D
Using BusinessManager command line
utilities
This appendix lists the BusinessManager command line utilities.
Initializing BusinessManager repository
Starting and stopping application servers
Starting and Stopping BusinessManager servers
Initializing BusinessManager repository

To create or recreate tables related to all BusinessManager components, execute the following
command present under <SBM_HOME>/bin directory.
setupSBM.cmd/sh -c all
For more information about recreating tables, see Re-initializing BusinessManager database on
page 127.
Initializing specific BusinessManager components

To use the setupSBM utility for an individual component, execute the following command from
<SBM_HOME>/bin directory and with one of the component names mentioned in Table 15 on
page 122.
setupSBM.cmd/sh -c <Component Name>
121
Appendix D: Using BusinessManager command line utilities
In the example below, the setupSBM utility is used for BizLogic.

setupSBM -c BizLogic
Table 15: BusinessManager components

Component
Description
all
Recreates all tables.
UserManager
Recreates user management and access control management tables.
Archiver
Recreates all archiver related tables.
BizPulse
Recreates all BizPulse tables except those of the Database Event

Channel.
BizLogic
Recreates all BizLogic tables except those of the Database Event

Channel.
BizRules
Recreates all BizRules repository tables.
BizSolo
Recreates all BizSolo tables except those of the Database Event

Channel.
Event
Recreates all BizEvent, BizStoreEvent, and BizPulseEvent tables,

butdoes not change BizLogic or BizPulse tables.
ProcessViews
Recreates all BizEvent, BizStoreEvent, and BizPulseEvent tables,

butdoes not change BizLogic or BizPulse tables.
noUserManager
If specified with -c all, then it does not recreate tables, views and
indexes for the User Management component
Note: If you run the setupSBM utility for one component, then be aware that data pertaining to
other components may remain in the system, causing application data inconsistency.

You can use command line utilities to start and stop application servers.
Pramati application server

Execute the following commands from <SBM_HOME>/pramati/server/bin location to start
and stop EJB or portal server.
Starting Pramati servers

Start EJB server as follows:
startEjbServer.cmd/sh
Start Portal server as follows:

startPortalServer.cmd/sh
122
Stopping Pramati servers

Stop Portal server as follows:
stopserver.cmd/sh portalServer
Stop EJB server as follows:

stopserver.cmd/sh ejbServer
WebLogic application server

Execute the following commands from <WEBLOGIC_SBM_DOMAIN_HOME> location to start and
stop Admin, EJB or portal server.
Starting WebLogic servers

Start Admin server as follows:
startAdminServer.cmd/sh


Stopping servers
stopserver.cmd/sh portalServer

stopserver.cmd/sh ejbServer
Stopping Admin server as follows:

stopserver.cmd/sh adminServer
WebSphere application server

Execute the following commands for creating profile, servers, and resources; and to start and stop
Admin, EJB, or portal server.
Creating WebSphere profile

Create a WebSphere Profile for BusinessManager by executing the following command from
<SBM_HOME>/websphere/bin location.
createprofile.cmd/sh
Note: To remove profile created for WebSphere, refer to Step 2 on page 98 in Before uninstalling
on page 98 for more information.
123
Creating servers and resources

Create a EJB and Portal servers and other resources required by BusinessManager by executing
the following command from <SBM_HOME>/websphere/bin location.
createsbm.cmd/sh
Important: Do not create server and resources on any of the nodes of the cluster. For more
information, see Clustering Guide.
Starting servers
Execute the following command from <SBM_HOME>/websphere/bin location to start EJB or
Portal server.

Stopping servers
Execute the following command from <SBM_HOME>/websphere/bin location to stop EJB or
Portal server.
stopPortalServer.cmd/sh

stopEjbServer.cmd/sh
JBoss application server

Execute the following command from <SBM_HOME>/jboss/bin location to start and stop EJB
or portal server.
Starting JBoss servers


Stopping JBoss servers

stopPortalServer.cmd/sh

stopEjbServer.cmd/sh
124

Execute the following command from <SBM_HOME>/bin location to start and stop BizLogic and
BizPulse servers of BusinessManager:
Starting BusinessManager servers

Start BizLogic server as follows:
startBizLogicServer.cmd/sh
Start BizPulse server as follows:

startBizPulseServer.cmd/sh
Both BizLogic and BizPulse servers can be started simultaneously using the following command:
startSBM.cmd/sh
Stopping BusinessManager servers

Stop BizLogic server as follows:
stopBizLogicServer.cmd/sh
Stop BizPulse server as follows:

stopBizPulseServer.cmd/sh
Both BizLogic and BizPulse servers can be stopped simultaneously using the following command:
stopSBM.cmd/sh
125
126
E
Re-initializing BusinessManager database

If your BusinessManager database is already created, then you need to re-initialize the database
after BusinessManager installation.
To re-initialize the BusinessManager database:
1. Re-initialize BusinessManager tables as described in the Creating BusinessManager database
on page 78 as the procedure for re-initializing BusinessManager related tables is same as that
of initializing BusinessManager database.
During re-initialization, only BusinessManager tables are dropped and recreated. Other tables
are unaffected.
2. If BusinessManager is installed on JBoss or WebSphere application servers, then ensure that
the following tables do not exist in the database user's account.
WebSphere: Drop the following tables:
SIB000
SIB001
SIB002
SIBCLASSMAP
127
Appendix E: Re-initializing BusinessManager database
SIBKEYS
SIBLISTING
SIBOWNER
SIBOWNER1
SIBXACTS
JBoss: Drop the following tables:
JBM_COUNTER
JBM_DUAL
JBM_ID_CACHE
JBM_MSG
JBM_MSG_REF
JBM_POSTOFFICE
JBM_ROLE
JBM_TX
JBM_USER
128
F
BizLogic and BizPulse auto-startup
The BizLogic and BizPulse auto-startup feature is useful in the case of a single server because
you do not have to manually start/stop the BizLogic/BizPulse server. However, it is more useful in
a cluster. See Clustering Guide for more information.
BizLogic auto-startup
BizPulse auto-startup
BizLogic auto-startup
If bizlogic.autostart parameter is set to true in bizlogic.conf file available in
<SBM_HOME>/conf location, then the BizLogic server starts automatically on EJB server startup.
This parameter is set to true by default.
Disabling BizLogic auto-startup

To disable BizLogic auto-startup, set the bizlogic.autostart parameter to false. If auto-startup
is disabled, then BizLogic server needs to be started explicitly after starting EJB server.
129
Appendix F: BizLogic and BizPulse auto-startup
BizPulse auto-startup
If bizpulse.autostart parameter is set to true in bizpulse.conf file present under
<SBM_HOME>/conf location, then BizPulse server starts automatically on EJB server startup.
This parameter is set to true by default.
Disabling BizPulse auto-startup

To disable BizPulse auto-startup, set the bizpulse.autostart parameter to false. If auto-startup
is disabled, then BizPulse server needs to be started explicitly after starting EJB server.
130
G
Locating BusinessManager log files
This appendix lists all the log files used by BusinessManager servers.
Application server log files
BusinessManager log files
Application server log files

The application server log files can be found at the following locations:
Pramati
EJB Server log: <SBM_HOME>/pramati/server/nodes/ejbServer/logs folder
Portal Server log: <SBM_HOME>/pramati/server/nodes/portalServer/logs folder
WebLogic
Admin Server log:
<WEBLOGIC_SBM_DOMAIN_HOME>/servers/adminServer/logs/adminServer.log
EJB Server log:

<WEBLOGIC_SBM_DOMAIN_HOME>/servers/ejbServer/logs/ejbServer.log
Portal Server log:

<WEBLOGIC_SBM_DOMAIN_HOME>/servers/portalServer/logs/portalServer.log
131
Appendix G: Locating BusinessManager log files
WebSphere
EJB Server log: <WEBSPHERE_HOME>/profiles/<BusinessManager
Profile>/logs/ejbServer/SystemOut.log
Portal Server log: <WEBSPHERE_HOME>/profiles/<BusinessManager

Profile>/logs/portalServer/SystemOut.log
Embedded JBoss community edition 5.1

EJB Server log: <SBM_HOME>/jboss/server/ejbServer/log/server.log
Portal Server log: <SBM_HOME>/jboss/server/portalServer/log/server.log
JBoss Enterprise Application Platform 5.0.1
EJB Server log: <JBoss_HOME>/jboss-as/server/ejbServer/log/server.log
Portal Server log: <JBoss_HOME>/jboss-as/server/portalServer/log/server.log
BusinessManager log files

The BusinessManager components log files are located in SBM_HOME/logs.
BizLogic server
BizLogic server log: <SBM_HOME>/logs/bizlogic.log.
BizPulse server
BizPulse server log: <SBM_HOME>/logs/bizpulse.log.
BusinessManager portal
BusinessManager Portal server log: <SBM_HOME>/logs/bpmportal.log.
132
H
Setting up JBoss server to use SonicMQ as
the JMS provider
This appendix lists the procedures to setup Savvions embedded JBoss 5.1 (Community Edition)
server to use SonicMQ as the JMS provider.
Deploying the Sonic JCA adapter to JBoss
Testing the Sonic JCA deployment
Prerequisites for modifying Savvion to use Sonic JMS
Modifying files in <SBM_HOME>
Deploying the Sonic JCA adapter to JBoss

There is no existing out-of-the-box support for SonicMQ from Savvion. The Sonic JBoss JCA
adapter is used to set up the Sonic specific resources in Savvions embedded JBoss. This section
explains how to deploy a Sonic JCA adapter on JBoss. In the code snippets provided in the
procedure, the following assumptions are made: The Sonic Domain Manager is located at
tcp://SonicDomain:2506(Update this for your environment); the Sonic messaging broker is located
at tcp://SonicMessaging:2507(Update this for your environment); all broker username/passwords
are Administrator/Administrator (Update this for your environment).
133
Appendix H: Setting up JBoss server to use SonicMQ as the JMS provider
To deploy the Sonic JCA Adapter:

1. Copy or unzip the Sonic JBoss JCA adapter to <SBM_HOME>.
2. If Sonic is installed on a remote host, copy the <SONICMQ_HOME>/lib from the Sonic host to
the Savvion host.
3. Set the <sonicmq.home> property in the next step according to the directory structure of the
Savvion host.
4. Edit the installation.properties file under <SBM_HOME> (The changes to be made
are highlighted in bold).The sample configuration is as follows:
jboss.home=c:/Progress/SBM76/jboss
jboss.server=${jboss.home}/server/ejbServer
jndi.provider.url=jnp://<Savvion_hostname>:16003
sonicmq.home=c:/Progress/Sonic/MQ8.0
sonicmq.brokerurl=tcp://<sonic_hostname>:2506
sonicmq.username=Administrator
sonicmq.password=Administrator
Note: The ejbServer node of the embedded JBoss must be used.The sonicmq.brokerurl
represents the broker used for Savvion messaging. The sonicmq.home directory represents
the location of the SonicMQ libraries.
5. Stop the Savvion servers and any JBoss instances of the embedded JBoss in Savvion.
6. Start the SonicMQ broker to which the Savvion server will connect to.
7. Make sure ant is set in the classpath.
The ant version should be 1.6.5 or later. Ant requires Java. Set JAVA_HOME if it is not already
set.
8. Run ant by providing the build.xml filepath.
This deploys the JCA adapter on Savvions JBoss based on the properties configured.
9. Restart the Savvion ejbServer. You can view the following result on the ejbServer console:
15:36:45,242 INFO [JNDILoader]
Loaded SonicJMS/Queues/SampleQ1(progress.message.jclient.Queue)
15:47:39,588 INFO [ConnectionFactoryBindingService]
Bound connection factory for resource adapter for ConnectionManager
'jboss.jca:name=SonicJMS/default/ConnectionFactory,service=ConnectionFactoryBi
nding to JNDI name 'java:SonicJMS/default/ConnectionFactory'
10. Check the <SBM_HOME>\jboss\server\ejbServer\log for logs.

To ensure that the deployment of the Sonic JCA adapter to JBoss is successful, test run a JCA
sample. We recommend that you first shut down all of the Savvion servers before completing the
following procedure.
To test the whether Sonic JCA Adapter is deployed successfully:
1. Edit the build.properties file under <JCA_Home>\samples to the appropriate setup.
134
Note: The appserver client jars might differ based on the appserver and appserver version.
This is for JBoss 5.1.
2. Replace <SBM_HOME> with the appropriate directory structure in the build.properties file
(The changes to be made are highlighted in bold).
# Root directory of app server installation
appserver.home=<SBM_HOME>/jboss
# Root directory of running app server
appserver.run=${appserver.home}/server/ejbServer
# App server deployment directory
appserver.deploy.dir=${appserver.run}/deploy
# App server data directory
appserver.data.dir=${appserver.run}/data
# App server client directory
appserver.client=${appserver.home}/client
# Full pathname of app server client jar
appserver.client.jar=${appserver.client}/jbossall-client.jar
# App Server common directory
appserver.common=${appserver.home}/common
# Full pathname of j2ee api jar
j2ee.jar=${appserver.common}/lib/jboss-javaee.jar
# Full pathname of ejb3x api jar
ejb3x.jar=${appserver.common}/lib/jboss-ejb3x.jar
# Full pathname of Sonic App Server Integration interface jar
sonic.api.jar=${appserver.run}/lib/sonic-jms-api.jar
# URL of JBoss server
tailor.jndiurl=jnp://<Savvion_hostname>:16003
# Configuration attributes for the SonicMQ broker used by the samples
# BROKER_URL
tailor.brokerurl=tcp://<sonic_hostname>:<Savvion_messaging_broker_port>
# CONNECTION_URLs
tailor.connectionurls= tcp://<sonic_hostname>:<Savvion_messaging_broker_port>
# USERNAME
tailor.username=Administrator
# PASSWORD
tailor.password=Administrator
3. Ensure that in the ejb-jar.xml file located in META-INF directory of the sample directory
(for example, SonicTopicMDB or SonicQueueMDB) has the line
<transaction-type>Container</transaction-type> placed before the line
<activation-config>.
Ensure that there are no other <transaction-type> elements in the file.
4. Run ant from one of the sample directories (for example, SonicTopicMDB or SonicQueueMDB).
This deploys the sample on the JBoss server.
5. If the servers are not running, start only the ejbServer. (The other servers are not required
for performing this test).
6. Send a JMS text message to SampleQ1 of the Sonic broker used for Savvion messaging (you
can use the Sonic JMS Test client).
The ejbServer console of JBoss shows the receipt of the message sent from the console.
This confirms successful deployment of the JCA adapter through the sample.
135
Prerequisites for modifying Savvion to use Sonic JMS

Before modifying Savvion to use Sonic JMS, ensure that:
You are using the embedded JBoss 5.1 Server (Community Edition) as the application server
for Savvion.
SonicMQ 8.0.1 is installed, is running and is accessible to Savvion.

You have successfully configured the JBoss EJB Server (located at
<SBM_HOME>/jboss/server/ejbServer) to use the Sonic 8.0.1 JBoss Resource Adapter. For
more information, refer to Deploying the Sonic JCA adapter to JBoss on page 133.
Create queues on the broker used for Savvion messaging. The broker could be the MgmtBroker
or another broker specifically used for messaging. The following queues are to be created::
AlertQueue: This is used by Savvion to receive alerts for external events.

EventQueue: This is used by Savvion to receive events for External Adapters.
Modify the sonic-jndiloader-conf.xml file located in the
<SBM_HOME>/jboss/server/ejbServer/data directory, as follows:
Add the following code snippet to the <entities> node:

<entity jndiName="SonicJMS/Queues/AlertQueue"
class="progress.message.jclient.Queue">
<property name="queueName">AlertQueue</property>
</entity>
<entity jndiName="SonicJMS/Queues/EventQueue"
class="progress.message.jclient.Queue">
<property name="queueName">EventQueue</property>
</entity>
Optionally, remove SampleQ2 to SampleQ3, and all sample topic entries. If you have removed
the SonicQueueMDB JCA sample from Savvions JBoss, you can also remove SampleQ1
from the entries.
Save the sonic-jndiloader-conf.xml file.

This section describes the procedure to modify the bizlogic.jar file located in bizlogic.ear
file.
Before modifying the bizlogic.jar file, reconfigure the following MDBs:
BMExternalEventMDB listens to jms/BMExternalEventQueue and takes care of

process-related and workstep-related event messages. Replace BMExternalEventMDB with
EventQueue in Sonic.
BLMessageReceiverXMDB listens to jms/sbmMessageQueue and takes care of processing

alerts from External Events. Replace BLMessageReceiverXMDB with AlertQueue in Sonic.
136
To modify the bizlogic.jar file located in the bizlogic.ear file:

1. Take a backup of the bizlogic.ear file from the <SBM_HOME>\ejbapps directory. Put the
backup in another directory.
2. Stop the BusinessManager servers.
3. Stop the ejbServer.
4. Unzip bizlogic.ear, and then unzip bizlogic.jar.
5. Edit the ejb-jar.xml located in bizlogic\META-INF as follows:
Open ejb-jar.xml and move to BMExternalEventMDB. Modify the code snippet within
the <messagedriven> tag for the above bean, so that it appears as follows (The changes
to be made are highlighted in bold):
<message-driven>
<display-name>BMExternalEventMDB</display-name>
<ejb-name>BMExternalEventMDB</ejb-name>
<ejb-class>com.savvion.sbm.bizlogic.smp.gateway.jms.ejb.BMExternalEventMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Bean</transaction-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
</activation-config-property>
<activation-config-property-name>destination</activation-config-property-name>
<activation-config-property-value>SonicJMS/Queues/EventQueue</activation-config-property-value>
<activation-config-property-name>faultTolerant</activation-config-property-name>
<activation-config-property-value>false</activation-config-property-value>
<activation-config-property-name>brokerURL</activation-config-property-name>
<activation-config-property-value>tcp://SonicMessaging:2507</activation-config-property-value>
<activation-config-property-name>username</activation-config-property-name>
<activation-config-property-value>Administrator</activation-config-property-value>
<activation-config-property-name>password</activation-config-property-name>
</activation-config>
<resource-ref>
<res-ref-name>jdbc/BizLogicDB</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<resource-ref>
<res-ref-name>SonicJMS/default/XAConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<res-auth>Application</res-auth>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>SonicJMS/Queues/EventQueue</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
</resource-env-ref>
</message-driven>
137
Open ejb-jar.xml and move to BLMessageReceiverXMDB. Modify the code snippet

within the <messagedriven> tag for the above bean, so that it appears as follows (The
changes to be made are highlighted in bold):
<message-driven>
<ejb-name>BLMessageReceiverXMDB</ejb-name>
<ejb-class>com.savvion.sbm.bizlogic.messaging.ejb.BLMessageReceiverXMDB</ejb-class>
<messaging-type>javax.jms.MessageListener</messaging-type>
<transaction-type>Bean</transaction-type>
<activation-config>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
<activation-config-property-name>destination</activation-config-property-name>
<activation-config-property-value>SonicJMS/Queues/AlertQueue</activation-config-property-value>
<activation-config-property-name>faultTolerant</activation-config-property-name>
<activation-config-property-value>false</activation-config-property-value>
<activation-config-property-name>brokerURL</activation-config-property-name>
<activation-config-property-value>tcp://SonicMessaging:2507</activation-config-property-value>
<activation-config-property-name>username</activation-config-property-name>
<activation-config-property-name>password</activation-config-property-name>
</activation-config>
<resource-ref>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-ref>
<res-type>javax.jms.ConnectionFactory</res-type>
<res-auth>Application</res-auth>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>SonicJMS/Queues/AlertQueue</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
</resource-env-ref>
</message-driven>
6. Edit the Jboss.xml located at bizlogic\META-INF as follows:
Open Jboss.xml and move to BMExternalEventMDB. Modify the code snippet within the
<messagedriven> tag for the above bean, so that it appears as follows (The changes to
be made are highlighted in bold):
<message-driven>
<ejb-name>BMExternalEventMDB</ejb-name>
<destination-jndi-name>SonicJMS/Queues/EventQueue</destination-jndi-name>
<resource-adapter-name>sonic-jms-ra.rar</resource-adapter-name>
<configuration-name>MDBPoolConf1025</configuration-name>
<resource-ref>
<resource-name>jdbc/BizLogicDB</resource-name>
</resource-ref>
138
<resource-ref>
<resource-name>SonicJMS/default/XAConnectionFactory</resource-name>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>SonicJMS/Queues/EventQueue</resource-env-ref-name>
<jndi-name>SonicJMS/Queues/EventQueue</jndi-name>
</resource-env-ref>
</message-driven>
Open Jboss.xml and move to BLMessageReceiverXMDB. Modify the code snippet within
the <messagedriven> tag for the above bean, so that it appears the same as the following
code snippet (The changes to be made are highlighted in bold):
<message-driven>
<ejb-name>BLMessageReceiverXMDB</ejb-name>
<destination-jndi-name>SonicJMS/Queues/AlertQueue</destination-jndi-name>
<resource-adapter-name>sonic-jms-ra.rar</resource-adapter-name>
<configuration-name>MDBPoolConf1530</configuration-name >
<resource-ref>
<resource-name>jdbc/BizLogicDB</resource-name>
</resource-ref>
<resource-ref>
<resource-name>SonicJMS/default/XAConnectionFactory</resource-name>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>SonicJMS/Queues/AlertQueue</resource-env-ref-name>
<jndi-name>SonicJMS/Queues/AlertQueue</jndi-name>
</resource-env-ref>
</message-driven>
7. After making the changes to the deployment descriptors, rebuild the bizlogic.jar using the
JAR utility.
Note: Using a ZIP utility to rebuild might cause some issues. While building the JAR file, include
the manifest file.
8. Rebuild the bizlogic.ear with the modified bizlogic.jar within it using the JAR utility of
JDK.
9. Copy the new bizlogic.ear into the <SBM_HOME>/ejbapps directory.
10. Start the JBoss servers of Savvion.
11. Start the BusinessManager servers (bizlogic and bizpulse).
12. To check whether the servers have started successfully, check the server.log and boot.log
located in the <SBM_HOME>\jboss\server\ejbServer\log directory.
139
140
I
Configuring JBoss ports
In addition to the server port values specified for EJB Server and Portal Server during
BusinessManager installation, default port values are stored in the Jboss application server
configuration files.
For embedded JBoss
For JBoss enterprise edition 5.0.1
For embedded JBoss

For JBoss Community Edition 5.1 application server, if you want to run two BusinessManager
installations simultaneously on the same machine, or the specified ports are not free on your
machine, then you must modify the port values from the values listed in the following files after
BusinessManager installation as in Table 16 on page 141.
<SBM_HOME>/jboss/server/ejbServer/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml
<SBM_HOME>/jboss/server/portalServer/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml
Valid port values for JBoss application server
Table 16: JBoss ports
EJB server ports
Portal server ports
51090
61090
51100
61100
141
Appendix I: Configuring JBoss ports
EJB server ports
Portal server ports
51101
61101
51102
61102
51161
61161
51162
61162
53528
63528
54446
64446
54447
64447
54448
64448
54457
64457
54712
64712
54713
64713
54714
64714
54444
64444
55445
64445
55446
65445
58009
65446
58888
67777
68009
68888

For JBoss application server, if you want to run two BusinessManager installations simultaneously
on the same machine, or the specified ports are not free on your machine, then you must modify
the port values from the values listed in the following files after BusinessManager installation.
1. For EJB Server
<JBOSS_HOME>/server/ejbServer/conf/jboss-service.xml
16004
54444
54445
54446
54447
<JBOSS_HOME>/server/ejbServer/conf/jacorb.properties
142
53528
53529
<JBOSS_HOME>/server/ejbServer/deploy/snmp-adaptor.sar/META-INF/jboss-service.xml
51161
51162
<JBOSS_HOME>/server/ejbServer/deploy/cluster-service.xml
51100
51101
54447
54448
<JBOSS_HOME>/server/ejbServer/deploy/hajndi-jms-ds.xml
51100
2. For Portal Server

<JBOSS_HOME>/server/portalServer/conf/jboss-service.xml
68083
64444
64445
64446
64447
<JBOSS_HOME>/server/portalServer/conf/jacorb.properties
63528
63529
<JBOSS_HOME>/server/portalServer/deploy/snmp-adaptor.sar/META-INF/jboss-service.xml
61161
61162
<JBOSS_HOME>/server/portalServer/deploy/cluster-service.xml
61100
61101
64447
64448
<JBOSS_HOME>/server/portalServer/deploy/hajndi-jms-ds.xml
61100
143
Appendix I: Configuring JBoss ports
144
Glossary
This is a listing of common BusinessManager terminology. For a full version of terms used in
BusinessManager documentation, refer to the Terminology Guide in the SBM_HOME\docs\pdf
folder.
ACL manager
In BusinessManager, Access Control List Manager provides a finer, more

precise control over user access rights for resources and actions.
Activity workstep In BusinessManager, the basic unit of work; must be performed by one or
more human performers (valid individual user, multiple users or user group).
Adapter
A Java class that integrates remote, third party classes and actions with
BusinessManager. An adapter can automate certain functions and tasks
performed by a remote server or other external systems.
Administration
A module in BPM Portal enabling the administrator to perform tasks such as

installing/uninstalling applications, modifying configuration parameters
controlling BusinessManager operations, and manage users, groups and
access control.The Administration module is visible only to application users
who have permissions to access it.
Application
In BusinessManager, an application is an installed, executable business

process that automates a business flow.
Balanced
scorecard
A management application in the Management module that measures

performance by analyzing how an organizations business activities help it
achieve its strategic goals. The Balanced Scorecard provides an analysis
from a range of perspectives.
BAM
Business Activity Management combines Business process management

with strategic and analytical information on specific business performance
indicators, providing real-time status information and identifying critical events
to assist senior management in making informed business decisions.
BizLogic
A BusinessManager component that provides a flexible, lightweight, scalable

workflow process engine for intranets, extranets, and the Internet.
BizPulse
A BusinessManager component that provides an open event-driven rule

engine to formulate and enforce policies in business applications.
145
Glossary
BizRules
A BusinessManager add-on component that is an efficient data driven rule

inference engine.
BizSolo
A BusinessManager component that enables users to develop customizable,

sophisticated presentation flows for business processes, install them as Web
applications, and execute them on their Web browsers.
BizStore
An open repository of rich e-business information collected from different

BusinessManager modules.
BPEL
BPEL (Business Process Execution Language) for Web services is an

XML-based language designed to enable task-sharing for a distributed
computing or grid computing environment - including across multiple
organizations - using a combination of Web services.
BPMN
BPMN (Business Process Modelling Notation) provides businesses with the

capability of defining and understanding their internal and external business
procedures through a Business Process Diagram giving organizations the
ability to communicate these procedures in a standard manner.
BPM Portal
A BusinessManager component that offers users, managers, administrators

and developers a unified, customizable portal for single sign-on access to all
BusinessManager functionalities to which they are granted permission.
BPM Studio
A BusinessManager component that is an Integrated Development

Environment for BusinessManager and enables application users to develop
and deploy a BusinessManager application without leaving the development
environment.
BRMS Portal
Business Rules Management System (BRMS) Portal provides a rich user

interface for creating/editing business rules and technical rules.
Business
calendar
A BusinessManager feature that accurately calculates the Due Date of tasks,

and provides support for multiple business calendars across different time
zones.
Business flow
The logical sequence of process activities, related to one another by a

triggering activity, to achieve an outcome. It represents a business process
that begins with a commitment and ends with the termination of that
commitment. In BusinessManager, business flow includes workflow (the flow
of all human-performed activities), integration flow (the flow of activities
performed by systems) and presentation flow (from a users viewpoint, the
flow of data from one Web page to the next).
Business logic
The control flow and information flow among worksteps that define a business
process.
BusinessManager An application is an implementation of a business process. It can contain one

application
or more process templates, performers, adapters, customized forms or rules.
An application can be deployed, installed and run on BizLogic servers. In
BusinessManager, an application is an installed, executable business process
that automates a workflow.
BusinessManager A BusinessManager component that allows application developers to; a)
Web services
publish their applications as Web services, and b) find and convert other
available Web services on the Internet into BusinessManager applications.
Business object A representation of an activity in the business domain, including its name,
definition, attributes, behavior, relationships and constraints.
Business
process
146
A process involving multiple worksteps in the form of operations, interactions

and notifications performed by a user, group of users, an external adapter,
or a script. Examples of internal business processes are purchasing, expense
Glossary
reporting, help desk, and time card. External processes may include order
processing, sales, and customer service.
Business
process
management
The concept of guiding work activities through a multi-step business process

in order to improve performance and reduce costs within and across functional
business units.
Business rule
A combination of elements, including validation edits, logon verifications,

database lookups, policies and transformations, that represent an enterprises
way of doing business.
Cluster
In BusinessManager, an integrated set of multiple, electronically connected

but physically separated servers. This loosely coupled group of nodes
collaborate to provide shared access to the services that each node hosts.
To other systems, the cluster appears as a single system.
Control flow
The sequences of worksteps and workstep conditions, as defined in a process

template in BPM Studio or Process Modeler.
Dashboard
A BusinessManager feature that provides a graphic overview of the status of

several business processes on a single Web page, enabling users to monitor
the progress of each process. Users can view business processes across all
applications or for a selected application.
Dataslot
A data placeholder that persists through the entire process and defines the
information flow of the business process. Dataslots are associated with
processes, where they can add information into (Input type) or out of (Output
type) worksteps, and appear as editable or read-only fields on a users
interface.
Expression
editor
A BusinessManager tool that enables users to define complex conditional

expressions within a Decision gateway to support their business requirements.
Group
In BusinessManager, an entity that has as members valid users or other

groups who perform related work and have authorized access to specific
components.
Heatmap
A BusinessManager feature that provides a convenient, graphical tool for

managers to visually locate the bottlenecks in the process execution. It helps
managers to get an overview of the status of the currently active instances,
identify suspended instances, and analyze the history of the completed
instances.
Home
A module in BPM Portal through which users interact with BusinessManager.

Using the Home module, users complete entries to various tasks and
applications, update profile, set preferences, and link to the support
infrastructure required to achieve these tasks.The Home module is the primary
interface for application users.
Infopad
In BusinessManager, a data structure used to capture business metrics,

typically displayed as a table with one or two dimensions.
Instance
An individual object within a specific class. In BusinessManager, a

self-contained unit that is created each time you use a process template to
run a BusinessManager application.
KPI
Key Performance Indicator, used in the Balanced Scorecard system, that

provides the data translating enterprise goals into a set of measurable
objectives.
Management
A module in BPM Portal enabling the managers to query, report, and control
processes and resources for application users. The Management module is
visible only to application users who have permissions to access it.
147
Glossary
Managed adapter In BusinessManager, a Managed Adapter is an implementation of an adapter

interface that facilitates data exchange between BusinessManager processes
and external applications.
Migration
The process of moving from the use of one operating environment to another
operating environment that is typically seen as improvement. Migration can
involve moving to new hardware, new software, or both. It may involve a new
application, another type of database, or a redesigned network. Migration is
also used to refer simply to the process of moving data from one storage
device to another. BusinessManager supports data migration as well as
application migration.
PAM
Process Asset Management recognizes that a companys processes are a

unique asset and provides a structure that organizes, stores, and secures
process data, enabling users to retrieve information on any of the companys
processes.
Performer
An entity that executes a workstep. Depending on the workstep type, the

performer can be a human user, a group of users, an adapter or other external
performer, or a script.
Presentation flow The flow of information and user input from one interface to the next. Typically
related to a single Activity workstep in the process and generated in a BizSolo
environment.
Process engine
Orchestrates the execution of business processes and also coordinates

conversations among process engines based on public processes, which
forms the backbone of global business collaboration.
Process Modeler A stand-alone component that enables users to design templates for basic
business processes and store or retrieve them from the central process
repository, and to design and run simulations of processes.
Process refresh
A BusinessManager feature for replacing the installed process without

versioning, facilitating the running process instances to refresh and seamlessly
adapt to the new workflow.
Process
repository
A central place (can contain several databases) in which a group of processes

is stored and maintained in an organized way, and can be accessed to retrieve
information.
Process template In BusinessManager, a model of business flow that includes worksteps,

connectors and dataslots. After users deploy and install it as an application
in the BusinessManager folder structure, they can use the application to create
process instances.
148
Rollback
In BusinessManager, a feature that restarts the workflow from a workstep

previously selected as the rollback point in the process, performed
automatically in the event of a failure.
Role
The actions and activities assigned to a valid application user who is a member
of a group. In BusinessManager, only members of a group can be assigned
a role. A role indicates the relationships of the user in a group context.
Rule wizard
An interactive utility that enables application users to quickly develop rules

that can be applied to a business process.
Swim lanes
Used in workflow diagrams to organize complex processes across functional

boundaries. For example, seen as horizontal lines on a process map, swim
lanes can be used to place individual task steps into different categories that
depend on task ownership.
Glossary
Task
In BusinessManager, a performer is assigned one or more work items that

the performer sees as tasks. There are two types of tasks: Assigned, which
are assigned specifically to you; and Available, which are available to be
performed by you or other members of your user group.
User
In BusinessManager, a valid human performer with authorized access to

specific modules.
Workflow
The logical sequence of activities performed by human performers. Workflow

includes the tasks, procedural steps, organizations or people involved, required
input and output information, and tools needed for each activity in a business
process.
149
Glossary
150
Index
Index
A
admin credentials
46
specifying 46
application servers
35, 47, 49, 81, 83, 103, 131
log files 131
selecting 47
specifying details 49
starting 81
stopping 83
supported by BusinessManager 35, 103
B
browsers
103
supported by BusinessManager 103
BusinessManager
1920, 25, 2728, 31, 91, 93, 98, 103, 105
components 25
documentation list 20
documentation set 31
installing as Windows service 91
interaction between components 27
removing Windows service 93
supported configurations 105
supported platforms 103
uninstalling 98
user types 19, 28
C
configurations
105
Customer support 22
customizing
119120
log levels 120
temporary directory 119
disk space required 35

Docs directory 31
Documentation information 20
I
installing
35, 44
prerequisites for 44
software requirements 35
J
Java Technology
103
L
License Agreement 44
M
memory required 35
O
OCI driver 35
operating systems
103
P
platforms, supported by BusinessManager 103
Product Support Team 22
Progress Savvion BusinessManager
23
about 23
Remove Existing Files dialog 98
database
103
destination location, selecting 45
silent uninstallation utility 100

software prerequisites 44
151
Index
software requirements 35
system requirements for installation 35
user management (continued)

uninstalling
98
BusinessManager 98
user management
103
Windows service
91, 93
installing BusinessManager 91
removing 93
152

Savvion BPM Installation Guide

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Savvion BPM Installation Guide

Transféré par

Droits d'auteur :

Formats disponibles

Progress Savvion BusinessManager 7.6.

Documentation copyright notice

Documentation copyright notice

Savvion BusinessManager: Installation Guide: Version 7.6.4

Savvion BusinessManager: Installation Guide: Version 7.6.4

Savvion BusinessManager: Installation Guide: Version 7.6.4

Savvion BusinessManager: Installation Guide: Version 7.6.4

Savvion BusinessManager: Installation Guide: Version 7.6.4

Savvion BusinessManager: Installation Guide: Version 7.6.4

Savvion BusinessManager: Installation Guide: Version 7.6.4

Savvion BusinessManager: Installation Guide: Version 7.6.4

Savvion BusinessManager: Installation Guide: Version 7.6.4

Savvion BusinessManager: Installation Guide: Version 7.6.4

Savvion BusinessManager: Installation Guide: Version 7.6.4

Savvion BusinessManager: Installation Guide: Version 7.6.4

Chapter 1: Savvion BusinessManager overview.......................................23

Chapter 2: Introduction to installation........................................................31

Chapter 3: Before installing BusinessManager.........................................35

Chapter 4: Installing BusinessManager 7.6.4............................................43

Savvion BusinessManager: Installation Guide: Version 7.6.4

Specifying application server details..........................................................................................49

Chapter 5: After installing BusinessManager 7.6.4...................................69

Chapter 6: Installing BusinessManager service pack 7.6.4......................85

Chapter 7: Setting up BusinessManager as service ................................91

Savvion BusinessManager: Installation Guide: Version 7.6.4

Removing Windows services......................................................................................................93

Chapter 8: Uninstalling BusinessManager.................................................97

Appendix A: Supported platforms and configurations...........................103

Appendix B: Sample scripts for creating your database........................113

Appendix C: Customizing temporary directory and log level for installer.119

Appendix D: Using BusinessManager command line utilities...............121

Savvion BusinessManager: Installation Guide: Version 7.6.4

Appendix E: Re-initializing BusinessManager database........................127

Appendix F: BizLogic and BizPulse auto-startup....................................129

Appendix G: Locating BusinessManager log files..................................131

Appendix H: Setting up JBoss server to use SonicMQ as the JMS provider.133

Appendix I: Configuring JBoss ports.......................................................141

Savvion BusinessManager: Installation Guide: Version 7.6.4

About this documentation

Conventions used in this manual

Product Support contact information

About this documentation

Savvion BusinessManager: Installation Guide: Version 7.6.4

An office administrator submitting an online purchase request.

Responsible for automating business processes in a particular business

Application Developer Responsible for creating customized applications for implementing

Responsible for configuring BusinessManager components, managing

BPM Portal Managers Guide

Savvion BusinessManager: Installation Guide: Version 7.6.4

If you are the

BizPulse Users Guide

Conventions used in this manual

Indicates titles of command buttons, checkboxes, options, lists, dialog

Indicates folder paths and filenames.

Indicates book titles.

Savvion BusinessManager: Installation Guide: Version 7.6.4

backward slash "\"

Indicates the path in Windows environment. For UNIX environment,

Represents the installation folder of BusinessManager.

Product Support contact information

1-781-280-4999 for US, Latin America and Canada

Progress Software Corporation

Savvion BusinessManager: Installation Guide: Version 7.6.4

Savvion BusinessManager: Installation Guide: Version 7.6.4