Progress Sonic Product Update Bulletin 8.5.1

® 

® 

PROGRESS® 

SONIC® 

Product Update Bulletin 8.5.1

Progress® Sonic® Product Update Bulletin 8.5.1 

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

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 Technology-Experience 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. 

Third Party Acknowledgements: One or more products in the Progress Sonic v8.5.1 release includes third party components 

covered by licenses that require that the following documentation notices be provided: 

Progress Sonic v8.5.1 incorporates Another Tool for Language Recognition v2.7.4. Such technologies are subject to the 

following terms and conditions: ANTLR Software License http://www.antlr.org/rights.html We reserve no legal rights to 

the ANTLR--it is fully in the public domain. An individual or company may do whatever they wish with source code 

distributed with ANTLR or the code generated by ANTLR, including the incorporation of ANTLR, or its output, into 

commercial software. We encourage users to develop software with ANTLR. However, we do ask that credit is given to us 

for developing ANTLR. By "credit", we mean that if you use ANTLR or incorporate any source code into one of your 

programs (commercial product, research project, or otherwise) that you acknowledge this fact somewhere in the 

documentation, research report, etc... If you like ANTLR and have developed a nice tool with the output, please mention that 

you developed it using ANTLR. In addition, we ask that the headers remain intact in our source code. As long as these 

guidelines are kept, we expect to continue enhancing this system and expect to make other tools available as they are 

completed. 

Progress Sonic v8.5.1 incorporates Apache Ant-Contrib 1.0B3. Such technology is subject to the following terms and

conditions: The Apache Software License, Version 1.1 - Copyright (c) 2001-2003 Ant-Contrib 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 acknowlegement: "This product includes 

software developed by the Ant-Contrib project (http://sourceforge.net/projects/ant-contrib)." Alternately, this 

acknowlegement may appear in the software itself, if and wherever such third-party acknowlegements normally appear. 4. 

The name Ant-Contrib must not be used to endorse or promote products derived from this software without prior written 

permission. For written permission, please contact ant-contrib-developers@lists.sourceforge.net. 5. Products derived from 

this software may not be called "Ant-Contrib" nor may "Ant-Contrib" appear in their names without prior written permission 

of the Ant-Contrib project. THIS SOFTWARE IS PROVIDED `ÀS 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 ANT-CONTRIB 

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. 

Progress Sonic v8.5.1 incorporates BasicLogin.java, SimpleCallbackHandler.java, SimplePasswordUser.java, 

SampleLoginModule.java, SamplePrincipal.java from Sun Microsystems, Inc. These technologies are subject to the 

following terms and conditions: Copyright 2000-2002 Sun Microsystems, Inc. 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. - 

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 AND ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES OR LIABILITIES 

SUFFERED BY LICENSEE AS A RESULT OF OR RELATING TO USE, MODIFICATION OR DISTRIBUTION OF 

THE 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 SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE 

POSSIBILITY OF SUCH DAMAGES. You acknowledge that Software is not designed, licensed or intended for use in the 

design, construction, operation or maintenance of any nuclear facility. 

Progress Sonic v8.5.1 incorporates Colt cern.colt* packages v1.0.3 (ca1420-20040626). Such technology is subject to the 

following terms and conditions: Packages cern.colt* , cern.jet*, cern.clhep - Copyright (c) 1999 CERN - European 

Organization for Nuclear Research. Permission to use, copy, modify, distribute and sell this software and its documentation 

for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both 

that copyright notice and this permission notice appear in supporting documentation. CERN makes no representations about 

the suitability of this software for any purpose. It is provided "as is" without expressed or implied warranty. 

Progress Sonic v8.5.1 incorporates Crimson v1.1.3. 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 

"Xerces" 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 `ÀS 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, International Business Machines, Inc., http://www.ibm.com. For more information on the 

Apache Software Foundation, please see . 

Progress Sonic v8.5.1 incorporates DSTC Xs3P version 1.1 from DSTC Pty Ltd. PSC will, at Licensee's request, provide 

copies of the source code for this third party technology, including modifications, if any, made by PSC. PSC may charge 

reasonable shipping and handling charges for such distribution. Licensee may also obtain the source code through 

http://communities.progress.com/pcom/docs/DOC-16051 by following the instructions set forth therein. - DSTC Public 

License. The contents of this file are subject to the DSTC Public License Version 1.1 (the 'License') (provided herein); you 

may not use this file except in compliance with the License. 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 xs3p. The Initial Developer of the Original Code 

is DSTC. Portions created by DSTC are Copyright © 2001, 2002 DSTC Pty Ltd. All Rights Reserved. 

Progress Sonic v8.5.1 incorporates Jing 20030619 and Trang 20030619. Such technology is subject to the following terms 

and conditions: Copyright (c) 2002, 2003 Thai Open Source Software Center Ltd. 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 Thai Open Source 

Software Center Ltd 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 REGENTS 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 Sonic v8.5.1 incorporates Model Objects Framework v2.0 from ModelObjects Group. Such technology is subject 

to the following terms and conditions: The ModelObjects Group Software License, Version 1.0 - Copyright (c) 2000-2001 

ModelObjects Group. 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 acknowledgement: "This product includes software developed by the ModelObjects Group 

(http://www.modelobjects.com)." Alternatively, this acknowledgement may appear in the software itself, if and wherever 

such third-party acknowledgements normally appear. 4. The name "ModelObjects" must not be used to endorse or promote 

products derived from this software without prior written permission. For written permission, please contact 

djacobs@modelobjects.com. 5. Products derived from this software may not be called "ModelObjects", nor may 

ModelObjects" appear in thier name, without prior written permission of the ModelObjects Group. 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 MODEL OBJECTS GROUP 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. 

Progress Sonic v8.5.1 incorporates Mozilla Rhino v1.5R3. The contents of this file are subject to the Netscape Public 

License Version 1.1 (the "License"); you may not use this file except in compliance with the License. You may obtain a 

copy of the License at http://www.mozilla.org/NPL/. 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 Mozilla Communicator client code, released March 

31, 1998. The Initial Developer of the Original Code is Netscape Communications Corporation. Portions created by 

Netscape are Copyright (C) 1998-1999 Netscape Communications Corporation. All Rights Reserved. PSC will, at 

Licensee's request, provide copies of the source code for this third party technology, including modifications, if any, made 

by PSC. PSC may charge reasonable shipping and handling charges for such distribution. Licensee may also obtain the 

source code through http://communities.progress.com/pcom/docs/DOC-16051 by following the instructions set forth 

therein. 

Progress Sonic v8.5.1 incorporates NET Security Library v1.0. Such technologies are subject to the following terms and 

conditions: Copyright © 2002-2003, The KPD-Team All rights reserved. http://www.mentalis.org/ 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. - 

Neither the name of the KPD-Team, 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. Copyright © 2002-2003, The KPD-Team.

Progress Sonic v8.5.1 incorporates OpenSAML Java Distribution v1.0.1. Such technology is subject to the following terms 

and conditions: The OpenSAML License, Version 1. Copyright (c) 2002 - University Corporation for Advanced Internet 

Development, Inc. 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, if any, must include the following acknowledgment: "This product includes software developed by the 

University Corporation for Advanced Internet Development Internet2 Project. Alternately, this 

acknowledegement may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 

Neither the name of OpenSAML nor the names of its contributors, nor Internet2, nor the University Corporation for 

Advanced Internet Development, Inc., nor UCAID may be used to endorse or promote products derived from this software 

without specific prior written permission. For written permission, please contact opensaml@opensaml.org. Products 

derived from this software may not be called OpenSAML, Internet2, UCAID, or the University Corporation for Advanced 

Internet Development, nor may OpenSAML appear in their name, without prior written permission of the University 

Corporation for Advanced Internet Development. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 

AND CONTRIBUTORS "AS IS" AND WITH ALL FAULTS. ANY EXPRESS OR IMPLIED WARRANTIES, 

INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A 

PARTICULAR PURPOSE, AND NON-INFRINGEMENT ARE DISCLAIMED AND THE ENTIRE RISK OF 

SATISFACTORY QUALITY, PERFORMANCE, ACCURACY, AND EFFORT IS WITH LICENSEE. IN NO EVENT 

SHALL THE COPYRIGHT OWNER, CONTRIBUTORS OR THE UNIVERSITY CORPORATION FOR ADVANCED 

INTERNET DEVELOPMENT, INC. BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, 




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 Sonic v8.5.1 incorporates OpenSSL toolkit v0.9.8i. Such technologies are subject to the following terms and 

conditions: LICENSE ISSUES ============== The OpenSSL toolkit stays under a dual license, i.e. both the conditions 

of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually 

both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact opensslcore@openssl.org. 

OpenSSL License --------------- 

==================================================================== 

Copyright (c) 1998-2008 The OpenSSL 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. All advertising materials mentioning features or use of this software must display the following acknowledgment: "This 

product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)" 

4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from 

this software without prior written permission. For written permission, please contact openssl-core@openssl.org. 

5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without 

prior written permission of the OpenSSL Project. 

6. Redistributions of any form whatsoever must retain the following acknowledgment: "This product includes software 

developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)" THIS SOFTWARE IS 

PROVIDED BY THE OpenSSL PROJECT `ÀS 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 OpenSSL 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. 

==================================================================== 

This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software 

written by Tim Hudson (tjh@cryptsoft.com). 

Original SSLeay License ----------------------- Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) All rights 

reserved. This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was 

written so as to conform with Netscapes SSL. This library is free for commercial and non-commercial use as long as the 

following conditions are aheared to. The following conditions apply to all code found in this distribution, be it the RC4, 

RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by 

the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com). Copyright remains Eric Young's, and 

as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be 

given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup 

or in documentation (online or textual) provided with the package. 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 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. All advertising materials mentioning features or use of this software must display the following acknowledgement: "This 

product includes cryptographic software written by Eric Young (eay@cryptsoft.com)" The word 'cryptographic' can be left 

out if the rouines from the library being used are not cryptographic related :-). 

4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must 

include an acknowledgement: "This product includes software written by Tim Hudson (tjh@cryptsoft.com)" 

THIS SOFTWARE IS PROVIDED BY ERIC YOUNG `ÀS 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 AUTHOR OR CONTRIBUTORS 

BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 





POSSIBILITY OF SUCH DAMAGE. The licence and distribution terms for any publically available version or derivative 

of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including 

the GNU Public Licence.] 

Progress Sonic v8.5.1 incorporates RSS4J v0.9.2. Such technology is subject to the following terms and conditions: 

Copyright (c) 1999-2002 ChurchillObjects.com 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 copyright holder 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 REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, 




OR TORT, INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; 




POSSIBILITY OF SUCH DAMAGE. The licence and distribution terms for any publically available version or derivative 

of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including 

the GNU Public Licence.] 

Progress Sonic v8.5.1 incorporates RSSUTILS v1.1. Such technology is subject to the following terms and conditions: 

Copyright 2003 Sun Microsystems, Inc. ALL RIGHTS RESERVED Use of this software is authorized pursuant to the terms 

of the license found at http://developer.java.sun.com/berkeley_license.html Copyright 2003 Sun Microsystems, Inc. All 

Rights Reserved. Redistribution and use in source and binary forms, with or without modification, are permitted 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 Sonic v8.5.1 incorporates Saxon XSLT and XQuery Processor v8.9.0.4 from Saxonica Limited 

(http://www.saxonica.com/) which is available from SourceForge (http://sourceforge.net/projects/saxon/). PSC will, at 

Licensee's request, provide copies of the source code for this third party technology, including modifications, if any, made 

by PSC. PSC may charge reasonable shipping and handling charges for such distribution. Licensee may also obtain the 

source code through http://communities.progress.com/pcom/docs/DOC-16051 by following the instructions set forth 

therein. - Mozilla Public License Version 1.0 (the "License"); you may not use this file except in compliance with the 

License. You may 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 of Saxon comprises all those 

components which are not explicitly attributed to other parties. The Initial Developer of the Original Code is Michael Kay. 

Until February 2001 Michael Kay was an employee of International Computers Limited (now part of Fujitsu Limited), and 

original code developed during that time was released under this license by permission from International Computers 

Limited. From February 2001 until February 2004 Michael Kay was an employee of Software AG, and code developed 

during that time was released under this license by permission from Software AG, acting as a "Contributor". Subsequent 

code has been developed by Saxonica Limited, of which Michael Kay is a Director, again acting as a "Contributor". A small 

number of modules, or enhancements to modules, have been developed by other individuals (either written specially for

Saxon, or incorporated into Saxon having initially been released as part of another open source product). Such contributions 

are acknowledged individually in comments attached to the relevant code modules. All Rights Reserved. 

Progress Sonic v8.5.1 incorporates Xalan Java XSLT Parser v2.4.1 from the Apache Foundation. Such technology is subject 

to the following terms and conditions: The Apache Software License, Version 1.1 - Copyright (c) 1999 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 


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 `ÀS 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 . 

Progress Sonic v8.5.1 incorporates Xerces v2.6.2 from the Apache Foundation. Such technology is subject to the following 

terms and conditions: The Apache Software License, Version 1.1 - Copyright (c) 1999-2004 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 


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 thirdparty 

acknowledgments normally appear. 4. The names "Xerces" 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 

`ÀS 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 



THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE


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, International Business Machines, Inc., http://www.ibm.com. For 

more information on the Apache Software Foundation, please see . 

March 2012

Contents 

1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 

Accessing Progress Sonic 8.5.1 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 

Installing Progress Sonic 8.5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 

Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 

Compatibilities with Other Progress Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 

Supported Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 

2. What’s new and changed in 

Sonic 8.5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 

What’s New in Sonic ESB and Sonic Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 

Enhanced ESB Endpoints to allow use of the bus connection . . . . . . . . . . . . . . . . . . . . . 18 

Domain View Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 

Create Artifacts from the Domain view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 

View properties of a selected artifact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 

Deploy artifacts on a container quickly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 

Import ESB Processes and Services into Sonic Workbench . . . . . . . . . . . . . . . . . . . 20 

Startup priority for ESB services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 

Improved Workbench support for WSDL and Operation level changes . . . . . . . . . . . . . . 21 

Message mapping enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 

New web service property to specify published endpoint URL . . . . . . . . . . . . . . . . . . . . . 21 

Creation of an XML file from a WSDL file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 

Updated Sonic Connect Integrated (SCI) editor layout for better visibility . . . . . . . . . . . . 22 

What’s New in SonicMQ and Management Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 

Fault tolerant container failure detection using non-MF connections . . . . . . . . . . . . . . . . 22 

New queue metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 

Support for adding multiple containers to the activation list of the activation domain . . . 24 

Mechanism that diagnoses and protects against EMsgTooBigException in mgmt layer . 24 

Support for Undelivered Destination in C, C++, and COM clients . . . . . . . . . . . . . . . . . . 24 

Improvements for Sonic - Actional Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 

Actional ESB Interceptor support for querying Non-Primary Parts . . . . . . . . . . . . . . . . . . 25 

Actional visibility for Faults and RMEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 

Improvements for Sonic - DataXtend SI Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 

Auto Deploy ESB Services to Sonic Container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 

What’s New in Sonic Deployment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 

Progress Sonic Update Bulletin 8.5.1 11

Contents 

New parameter for DSHost element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 

Commandline parameter to incorporate deploy tool merge enhancements . . . . . . . . . . . 26 

Commandline parameter to wait for Host Managers to come online . . . . . . . . . . . . . . . . 26 

What’s New in JCA Resource Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 

Version Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 

New Samples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 

What’s Changed in Sonic 8.5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 

Sonic Management Console changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 

Sonic Configuration API changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 

SDM’s schema modification for Fault Tolerant container . . . . . . . . . . . . . . . . . . . . . . . . . 28 

SDM’s schema modification for Backup container . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 

Undefined Cluster Queues element Ids in SDM models . . . . . . . . . . . . . . . . . . . . . . . . . 29 

ReadExclusive=true is not allowed in the tuning parameters of Cluster Queues in an SDM model 

29 

What’s Changed in Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 

Database Service Reconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 

Setting a Socket Connect Timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 

C, C++, and COM Client API Documentation update . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 

3. Learning More About the Progress Sonic Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 

Progress Sonic Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 

SonicMQ Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 

Other SonicMQ Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 

Sonic ESB Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 

Progress Sonic Infocenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 

Progress Sonic Education and Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 

Progress Software Developers Network (PSDN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 

Progress Sonic Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 

Progress Sonic Evaluation Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 

12 Progress Sonic Update Bulletin 8.5.1

Overview 

This is Progress Sonic 8.5.1, a service pack release that contains new features that 

enhance the product and fixes for defects in Sonic 8.5.0. 

Progress Sonic is delivered in three installers: 

Progress Sonic Update Bulletin 8.5.1 13 

1 

• Progress Sonic Installer sets up Sonic 8.5 development environments, deployment 

Domain Managers, Sonic Deployment Manager, and administrative tools. The utilities 

that upgrade from 7.5, 7.6, and 8.0 Domain Managers are included. When 

downloaded, unpack it. Installer requires a 1.5 or 1.6 JVM on UNIX and Linux 

machines to run the installer; it can use and install its preferred 1.6 JVM on Windows. 

Run install.exe (Windows) or install.bin (UNIX, Linux.) 

• Progress Sonic Container Launcher installs lightweight resources on systems that 

run Sonic containers, and the utilities for upgrading Sonic 7.5 and 7.6 installations. A 

Launcher installation will be dynamically upgraded and updated by the domains to 

which its containers connect. When downloaded, unpack it. Installer requires a 1.5 or 

1.6 JVM on UNIX and Linux machines to run the installer; it can use and install its 

preferred 16 JVM on Windows. Run install_container_launcher.exe (Windows) or 

install_container_launcher.bin (UNIX, Linux.) 

• Progress Sonic Updater, this release, advances a Sonic Installer location to the 

Updater's version, typically a Service Pack. Service Packs are cumulative so if you 

skipped a service pack, a higher version will include all changes in earlier Service 

Packs. When downloaded, unpack it. Updater requires a 1.5 or 1.6 JVM to run the 

installer, which should be the JVM that supports the installation you intend to update. 

Confirm that the JVM is on the path before you launch the updater. Run install.exe 

(Windows) or install.bin (UNIX, Linux.) 

Download packages are available at the Progress Electronic Software Download (ESD) 

site for additional SonicMQ clients (C, C++, COM, and .NET) and JCA Resource Adapters 

for JBoss, WebSphere, and WebLogic.

Chapter 1: Overview 

Accessing Progress Sonic 8.5.1 Documentation 

Sonic 8.5.1 products are installed with a welcome page at their installation root for access 

to Progress resources and documentation. You can access Sonic 8.5.1 documentation at 

its remote site. See the downloads page at the remote site for documentation packages and 

archives. Take time to review the Sonic 8.5.1 release notes list of known issues, and—for 

current customers—a listing of the resolved issues in this release. 

Installing Progress Sonic 8.5.1 

The following procedures provide the general idea of how new and existing Sonic users 

advance their Sonic products to this release, 8.5.1. Open the Progress Sonic Installation 

and Upgrade Guide for detailed instructions on installing, and upgrading installations as 

well as information about silent installations. 

If You Are New to Sonic... 

1. Use the Sonic Installer 8.5 to establish each development environment (Sonic ESB or 

SonicMQ Development), start its Domain Manager, and then run the updater to 

advance the release to 8.5.1. 

2. Use the Sonic Installer 8.5 to establish each deployment environment (Domain 

Manager), start its Domain Manager, and then run the updater to advance the release 

to 8.5.1. 

3. Use the Sonic Installer 8.5 to distribute just Administration Tools, and then run the 

updater to advance the tools installation to 8.5.1. 

4. Use the Container Launcher Installer 8.5.1 to enable each distributed system to 

connect and run containers in one of your installed domains. 

5. Unpack downloaded 8.5.1 C clients, .NET client, and JCA adapters on development 

and distributed deployment systems. 

If You Are Upgrading a Sonic 8.5 Topology... 

1. Start each SonicMQ development or deployment Domain Manager (for ESB 

development, stop everything), stop all associated tools, and then run the Sonic 

Updater pointing to the Progress Sonic Domain Manager’s installation location. 

2. Stop tools in each Administration Tools installation, and then run the Sonic Updater to 

install the latest tools. 

3. Unpack downloaded 8.5.1 C clients, .NET client, and JCA adapters in a new location 

on development and deployment systems, and then use them to run the clients. 

Open the Progress Sonic Installation and Upgrade Guide for additional information. You 

might also want to review the resolved issues in the Sonic 8.5.1 release notes. 


If You Have an earlier Sonic release... 

Installing Progress Sonic 8.5.1 

1. Refer to the Sonic 8.5 documentation for details on upgrading from that earlier release 

to 8.5. Open the Progress Sonic Installation and Upgrade Guide for detailed 

procedures for basic upgrades as well as zero-downtime upgrades for replicated 

brokers, clusters, and fault-tolerant management frameworks. 

2. After upgrading to 8.5, use the Sonic Installer 8.5.1 to install this service pack. 

3. Unpack downloaded 8.5.1 C clients, .NET client, and JCA adapters on development 

and distributed deployment systems, and then use them to run the clients. You should 

not have to recompile applications. 

Java Runtime Environment 

Important: Accessing Java for the Updater — Unlike Sonic installers, Sonic updaters and 

patches generally do not include the appropriate Java to run the updater itself. 

In most cases where the target is a 64-bit Windows machine, reference a 

32-bit Java runtime to run the updater. The Java that supports runtime of the 

underlying installation that is being updated will be unchanged. 

Compatibilities with Other Progress Products 

This release of Sonic requires that associated Progress products use specific versions: 

• Actional — Management servers and agents must be release 8.2.5 

• Dataxtend SI — Must be at release 8.5.1 and its Eclipse at 3.6 

Install or upgrade these products to ensure compatibility. 


Chapter 1: Overview 

Supported Standards 

Standards supported in Progress Sonic 8.5.1 include the following: 

Table 1: Supported standards 

Group Standard Version 

Web Services REST 

Transports and 

Protocols 

SOAP 1.1 

SOAP 1.2 

SOAP with Attachments 2000 

WSDL 1.1 

WS-BP 1.0 

WS-Addressing 

WS-Policy 2004 

WS-Policy 1.2 

WS-Security 1.0 

WS-RM 

JAX-WS 2.1 

JAX-RS 1.0 

BPEL 2.0 

MTOM 2005 

JMS 1.0/1.1 

HTTP 1.0/1.1 

HTTPS 


What’s new and changed in 

Sonic 8.5.1 

This chapter describes new and enhanced functionality in release 8.5.1 of the Progress 

Sonic products in the following sections: 

• What’s New in Sonic ESB and Sonic Workbench on page 18 

• What’s New in SonicMQ and Management Framework on page 22 

• Improvements for Sonic - Actional Integration on page 25 

• Improvements for Sonic - DataXtend SI Integration on page 25 

• What’s New in Sonic Deployment Manager on page 26 

• What’s New in JCA Resource Adapter on page 27 

• What’s Changed in Sonic 8.5.1 on page 28 

• What’s Changed in Documentation on page 30 


2

Chapter 2: What’s new and changed in Sonic 8.5.1 

What’s New in Sonic ESB and Sonic Workbench 

The following features are also introduced in Sonic ESB and the Sonic Workbench in the 

8.5.1 release: 

• Enhanced ESB Endpoints to allow use of the bus connection on page 18 

• Domain View Enhancements on page 19 

• Startup priority for ESB services on page 20 

• Improved Workbench support for WSDL and Operation level changes on page 21 

• Message mapping enhancements on page 21 

• New web service property to specify published endpoint URL on page 21 

• Creation of an XML file from a WSDL file on page 21 

• Updated Sonic Connect Integrated (SCI) editor layout for better visibility on page 22 

Enhanced ESB Endpoints to allow use of the 

bus connection 

The following new features are provided in the existing ESB endpoint (SMC only) and ESB 

container (SMC and Workbench) creation pages: 

• Enable an endpoint to inherit the ESB (JMS) connection of its ESB container. 

This allows an endpoint to be defined without linking it to a physical JMS connection. 

This is useful when sharing configurations, or when deploying an ESB application to 

multiple sites in a distributed domain. 



For more information, see the section “To view and configure Progress SonicMQ 

endpoints” in the Progress Sonic ESB Configuration and Management Guide. 

• Provide an EL expression for the ESB (JMS) connection for an ESB container. 

This allows the container's ESB (JMS) connection to be bound dynamically at startup. 

This is useful when deploying an ESB container to multiple sites in a distributed 

domain. Each instance can use a local broker connection. 

For more information, see the section “To create a new ESB Container” in the Progress 

Sonic ESB Configuration and Management Guide and the section “Creating ESB 

containers” in the Progress Sonic ESB Getting Started with Sonic Workbench guide. 

Domain View Enhancements 

The functionality of the Domain node in the Project Explorer has been enhanced. It now 

enables you to: 

• Create Artifacts from the Domain view 

• View properties of a selected artifact 

• Deploy artifacts on a container quickly 

• Import ESB Processes and Services into Sonic Workbench 



Create Artifacts from the Domain view 

You can now create artifacts such as ESB endpoints, ESB processes, and service 

configurations from the Domain view. You can right-click the corresponding option and use 

the context menu for creating these artifacts. 

View properties of a selected artifact 

You can now view the properties of artifacts such as ESB Process, ESB Service, and 

endpoint from the Domain view. To view the properties, right-click the artifact and select 

Show In > Properties. 

Deploy artifacts on a container quickly 

You can now deploy artifacts such as ESB Processes and ESB Services on a container 

from the Domain view. To deploy the artifacts, right-click the artifact and select 

Deploy To > . You can select multiple processes or services to deploy 

on a container. 

Import ESB Processes and Services into Sonic 

Workbench 

You can now import artifacts such as ESB Processes and ESB Services from the Domain 

view. You can right-click the Processes or Services node and select the Import 

Processes or Import Service Configs option to import the processes and services. 

This information is added to the Sonic Workbench online help in the Workbench and in its 

PDF version, Sonic ESB Development Tools guide. 

Startup priority for ESB services 

You can now specify the startup priority for services in an ESB container. This is used to 

control the order in which services are started. Services with a lower priority value are 

started before services with a higher value.The default value is 0. The value must be a 

positive integer. You can specify a startup priority from the following locations: 

• Manage Processes and Services for page in Sonic Workbench 

• Service/Process Maintenance page in Sonic Management Console 

• Service configuration editor 

This information is added to the Sonic Workbench online help in the Workbench and in its 

PDF version, Progress Sonic ESB Development Tools guide and Progress Sonic ESB 

Getting Started with Sonic Workbench guide. 

For information regarding change in Sonic Management Console, see the chapter “ESB 

Containers” in the Progress Sonic ESB Configuration and Management Guide. 



Improved Workbench support for WSDL and 

Operation level changes 

The following new features are provided in the existing web service creation wizard: 

• Map an existing ESB Process to an existing WSDL's operation in a Bottom Up Web 

Service wizard. 

• Validate process interface against WSDL operation interface. 

• Expose only unimplemented operations from a Top Down Web Service wizard. 

• Display tooltip information when users hover the mouse pointer over an operation 

under the Domain node in Project Explorer and in the Sonic Connect Integrated (SCI) 

editor. 

Message mapping enhancements 

This feature enables you to delete a mapping rule by pressing the DELETE key. Deleting a 

mapping rule using the DELETE key is supported only in the graphical view of message 

mapping. 

New web service property to specify published 

endpoint URL 

A new service property, publishedEndpointUrl, is available for exposing web services 

with Sonic Connect. This property specifies the web service address to be used in the 

published WSDL. The host of the publishedEndpointUrl must be reachable from client 

hosts. The clients use the web service address to call web service. 

Creation of an XML file from a WSDL file 

This feature enables you to create an XML file from a WSDL file. To create an XML file from 

a WSDL file, right-click the WSDL file in the Project Explorer, and select Generate > XML 

File. The New XML File wizard opens. Follow the steps in the wizard to create the XML file. 



Updated Sonic Connect Integrated (SCI) editor 

layout for better visibility 

The Input, Output, and Fault parameters are now arranged in the tabbed layout for better 

visibility. 

What’s New in SonicMQ and Management 

Framework 

The following features are introduced in SonicMQ in 8.5.1: 

• Fault tolerant container failure detection using non-MF connections on page 22 

• New queue metrics on page 23 

• Support for adding multiple containers to the activation list of the activation domain on 

page 24 

• Mechanism that diagnoses and protects against EMsgTooBigException in mgmt layer 

on page 24 

• Support for Undelivered Destination in C, C++, and COM clients on page 24 

Fault tolerant container failure detection using 

non-MF connections 

Progress ® Sonic ® 8.5.1 introduces the ability to configure fault tolerant containers to allow 

fault detection using MQ connections other than the container’s own management 

connection. 

The backup container gets its fault tolerant connection details from the primary container's 

configuration. If no fault tolerant connection details are provided by the new container 

configuration attributes, the current (8.5) behavior continues where the primary and backup 

containers default to use their existing management connection. 


What’s New in SonicMQ and Management Framework 

There is no support for dynamic changes to the fault tolerant connection details; if changes 

are made to those details the MF container needs to be recycled. 

An advantage of using non-MF connections is that failover detection can be performed over 

the same JMS broker(s) serving application traffic to the services the container is hosting, 

rather than depending upon availability of the container’s connection to the management 

broker. 

When configuring a fault-tolerant container in Progress Sonic 8.5.1, the Fault Tolerance 

tab of the Edit Container Properties dialog is modified as shown: 

For more information, see Progress SonicMQ Deployment Guide. 

New queue metrics 

Two new queue metrics and alerts are added to allow customers to monitor how quickly 

messages are moving in a queue. 

The new metrics are added to the queue.messages.* instance, and are: 

• MaxAge — Age, in seconds, of the oldest message in a queue. The age of a message 

is the interval of time that starts when the message is loaded into the queue within the 

current broker startup, and ends with the current time. 

• TimeInQueue — Average time, in seconds, that messages reside in a queue. The 

TimeinQueue of a message is the interval of time that starts when the message is 

loaded into the queue within the current broker startup, and ends when the message 

is dequeued from the queue for delivery to a consumer. 



The new alerts are added to broker-wide application.alert.* are: 

• queue.messages.MaxAge — Alert for queue instance metric, MaxAge (high 

thresholds) 

• queue.messages.TimeInQueue — Alert for queue instance metric, TimeinQueue 

(high thresholds) 

For more information, see Progress SonicMQ Configuration and Management Guide. 

Support for adding multiple containers to the 

activation list of the activation domain 

This feature enables you to select multiple containers, and then add them to the activation 

list of the activation domain. 

Mechanism that diagnoses and protects 

against EMsgTooBigException in mgmt layer 

The size of each mgmt message is now checked before being published. If it exceeds a 

pre-defined limit (configured via Java system property 'sonicsw.mf.msgSizeMaxMb', 

default 9.9Mb) the message is rejected. This avoids large messages reaching the broker 

and causing the mgmt connection to be dropped. 

For this to be effective the msgSizeMaxMb setting must be lower than the max message 

size configured on the mgmt broker(s), default 10Mb. If the size exceeds a warning 

threshold ('sonicsw.mf.msgSizeWarnMb', default 8.0Mb), a warning message is logged. 

The first time one of these thresholds is exceeded, the body of the offending message is 

written to a file with the extension '.mdump'. This file can be provided to Progress Technical 

Support to help determine the cause of the large message. By default, this file is written to 

the mgmt container's/client's working directory, but the location can be changed 

('sonicsw.mf.msgSizeDumpDir'). 

Support for Undelivered Destination in C, C++, 

and COM clients 

The C, C++, and COM clients now provide support for specifying the Undelivered 

Destination, explicitly overriding the default Dead Message Queue. If a message is 

undelivered, it is placed in the destination queue specified in the code. 

Sample code for setting the message property that will override the Dead Message Queue 

is detailed in Progress SonicMQ C Client Guide, Progress SonicMQ C++ Client Guide, and 

Progress SonicMQ COM Client Guide books in the 8.5.1 C/C++/COM documentation 

package. 


Improvements for Sonic - Actional Integration 

Improvements for Sonic - Actional Integration 

Progress® Sonic® 8.5.1 introduces the following features to improve integration with 

Progress® Actional® 8.2.5: 

• Actional ESB Interceptor support for querying Non-Primary Parts on page 25 

• Actional visibility for Faults and RMEs on page 25 

Actional ESB Interceptor support for querying 

Non-Primary Parts 

You can report ESB message parts in the Actional Management Server audit log or use 

them to form XPath field definitions where an XPath expression can be applied to any part 

in a multi-part message. 

For more information, see the chapter “Using Actional with Sonic Components” in the 

Progress Sonic ESB Configuration and Management Guide. 

Actional visibility for Faults and RMEs 

This feature provides Actional visibility of abnormal process termination due to Faults and 

RMEs. Error-handling steps, such as Fault, Reject, Rethrow, and Resubmit will now be 

reported in Actional. 

For more information, see the chapter “Using Actional with Sonic Components” in the 

Progress Sonic ESB Configuration and Management Guide. 

Improvements for Sonic - DataXtend SI 

Integration 

Progress® Sonic® 8.5.1 introduces the following feature to improve Progress® 

DataXtend® Semantic Integrator (SI) 8.5.1 integration: 

Auto Deploy ESB Services to Sonic Container 

This feature enables you to deploy the service configurations of the Deploy folder 

automatically on their default containers as specified in the properties file. It also enables 

you to undeploy the service configurations from the Directory Service and their respective 

containers automatically. 

For more information, see the section “Enabling or disabling the deployment of a service 

configuration” in the Progress Sonic ESB Getting Started with Sonic Workbench guide. 



What’s New in Sonic Deployment Manager 

The Sonic Deployment Manager added elements and parameters that enable the 

configuration of features in the Sonic 8.5.1 release: 

New parameter for DSHost element 

The DSHost element now includes a new element ShutdownAfterRun. If the element is 

set to true, the cleanDomain command shuts down the Directory Service after execution. 

Commandline parameter to incorporate deploy 

tool merge enhancements 

The SDM commands now include a new commandline parameter altXarMergeMode. If 

the parameter is set to true, XAR merge mode is enabled. SDM merges the contents of the 

XAR files in the model with the contents of the DS without listing every configuration 

element in the DS initially. 

Commandline parameter to wait for Host 

Managers to come online 

The SDM commands now include a new commandline parameter hm_wait_time. It 

specifies the duration, in seconds, that the cleanDomain command will wait for 

HostManagers on remote hosts to become fully functional before proceeding to use those 

HostManagers to deploy containers on the remote hosts. The default value is 30 seconds. 


What’s New in JCA Resource Adapter 

What’s New in JCA Resource Adapter 

The following changes are made for the JCA Resource Adapters in the 8.5.1 release: 

• Version Support 

• New Samples 

Version Support 

JCA Resource Adapters are updated to support: 

• WebSphere Application Server 7.0 

• WebLogic Application Server 10.3.4 

• Ant 1.7.1 

New Samples 

The following samples are added to JCA Resource Adapters for Weblogic and Websphere: 

• SonicEJB3QueueMDB 

• SonicEJB3QueueSSB 

• SonicEJB3TopicMDB 

• SonicEJB3TopicSSB 

• SonicEJB3XAQueueMDB 

• SonicEJB3XAQueueSSB 

• SonicEJB3XATopicMDB 

• SonicEJB3XATopicSSB 



What’s Changed in Sonic 8.5.1 

The following changes in Sonic 8.5.1 have an impact on existing deployments: 

• Sonic Management Console changes on page 28 

• Sonic Configuration API changes on page 28 

• SDM’s schema modification for Fault Tolerant container on page 28 

• SDM’s schema modification for Backup container on page 29 

• Undefined Cluster Queues element Ids in SDM models on page 29 

• ReadExclusive=true is not allowed in the tuning parameters of Cluster Queues in an 

SDM model on page 29 

Sonic Management Console changes 

The FaultDetectionTimeout and FaultDetectionInterval parameters in the 

Fault Tolerance tab are only settable on Primary MF containers. 

Sonic Configuration API changes 

The implementation of the following methods has changed to throw a MgmtException if 

the MF container is not a Primary Fault Tolerant Container: 

• com.sonicsw.mf.mgmtapi.config.gen.IAbstractContainerBean.IAbstrac 

tFaultToleranceType.setFaultDetectionInterval(int value) 

• com.sonicsw.mf.mgmtapi.config.gen.IAbstractContainerBean.IAbstrac 

tFaultToleranceType.setFaultDetectionTimeout(int value) 

SDM’s schema modification for Fault Tolerant 

container 

The following elements are added to the Fault Tolerance parameters of a container: 

 

 

 

 

... 

... 

 

 

 

 


What’s Changed in Sonic 8.5.1 

 

 

 

 

 

SDM processing fails the SDM run if any of these attributes are set for a non-primary FT 

container. 

SDM’s schema modification for Backup 

container 

The following elements are no longer supported on the Fault Tolerance parameters of the 

Backup container: 

• FaultDetectionInterval 

• FaultDetectionTimeout 

The Backup container only supports the StartActive element. The SDM build fails if 

FaultDetectionInterval or FaultDetectionTimeout are used for a container that 

is not a primary FT container, or if StartActive is specified on a non-FT container. The 

SDM migration utility removes the attributes that are not allowed on a backup or non fault 

tolerant container from the model. The user is notified of the removal. 

Undefined Cluster Queues element Ids in SDM 

models 

The SDM build fails if a reference to an unidentified Queues Id in a cluster element exists. 

SDM migration removes a Cluster Queues element if the Queues Id is undefined, and 

notifies the user. 

ReadExclusive=true is not allowed in the 

tuning parameters of Cluster Queues in an 

SDM model 

The SDM build fails if the tuning parameters for a Cluster Queue includes the element 

true. 



What’s Changed in Documentation 

The following sections are updated/added to the existing documentation: 

• Database Service Reconnect on page 30 

• Setting a Socket Connect Timeout on page 31 

• C, C++, and COM Client API Documentation update on page 31 

Database Service Reconnect 

Database Service resiliency to failed JDBC connections is provided by a number of 

mechanisms. At the database driver level, reconnect attempts may be specified where 

supported by the driver. 

The Database Service may also attempt to reconnect. This logic is triggered in part when 

database validation queries are configured and fail. The Database Service runs a validation 

query prior to performing each database operation or prior to a series of database 

operations implemented as a sequence of Database Service steps. The Database Service 

pools database connections. So it is when connections are borrowed from the pool that the 

validation query is run. 

You should therefore specify a simple, fast-running validation query that is guaranteed to 

succeed if the database connection is working. A validation query can be any simple query 

using SQL syntax, but must return at least one row of data. A validation query should be a 

simple stored procedure call that will always work and does not depend on database tables 

being available. 

If there are multiple available connections in the connection pool validation queries will be 

run until a good connection is found or until no good connections can be found, and no new 

connection can be created and validated. As validation queries work its way through the 

available connections, stale connections are detected and cleared from the pool. 

Irrespective of whether validation queries are performed to obtain a good connection, one 

of the following actions occurs when the actual Database Service operation fails: 

• If no validation query is specified for the connection - Reconnect is not attempted and 

the received message is sent to the rejected message endpoint (RME). 

• If a validation query is specified and executes successfully over the connection - The 

failure is assumed to be due to an invalid database operation. So, the service 

generates and sends a the message to the RME. The connection is considered good 

and is maintained in the connection pool. 

• If a validation query is specified and does not execute correctly, the service makes 

another attempt to borrow from the pool, connect to the database and retry the failed 

operation. If this attempt fails, the service generates and sends the message to the 

RME. If this happens when the connection is shared with a previous step in the 

itinerary, then the service does not attempt to obtain another connection and the 

current message is sent to the RME. 


What’s Changed in Documentation 

This process is repeated each time a database operation run by the service fails (that is, if 

the service fails to run a database operation continues attempting to run other operations). 

The Database Service attempts to reconnect to the database once per failed database 

operation. The maximum time the service waits while attempting to connect is determined 

by the service parameter Timeout. 

Examples of commonly used validation queries include the following: 

• For Sybase and SQL Server databases: select 1 

• For Oracle databases: select * from dual 

This improved documentation has been added to the Progress Sonic Database Service 

Developer's Guide and InfoCenter. It is not available in Sonic Workbench online help. 

Setting a Socket Connect Timeout 

You can specify a timeout to be used when establishing a socket connection to a broker. 

The ConnectionFactory method setSocketConnectTimeout (int timeout) lets 

you set the number of milliseconds to allow for the socket connection to be established, as 

shown: 

try { 

Sonic.Jms.ConnectionFactory factory; 

Sonic.Jms.Cf.Impl.ConnectionFactory cf = (new 

Sonic.Jms.Cf.Impl.ConnectionFactory(broker)); 

cf.setSocketConnectTimeout(3000); 

factory = cf; 

connect = factory.createConnection(username, password); 

} 

Setting a value of 0, the default value, means the socket connect request does not time out. 

If the socket connection is not established within the timeout interval, an exception is 

returned to the caller with the error message “Connection attempt timed out”. 

This improved documentation has been added to the Progress SonicMQ .NET Client 

Guide. 

C, C++, and COM Client API Documentation 

update 

The unit of the following methods are updated to seconds in the C, C++, and COM Client 

API documentation: 

• getTCPConnectionTimeout 

• setTCPConnectionTimeout 

Note: The corresponding methods in the JAVA Client are: 

getSocketConnectTimeout and setSocketConnectTimeout. The unit of 

methods is milliseconds. 




Learning More About the Progress 

Sonic Products 

This chapter describes where to find more information on the Progress Software products, 

as detailed in the following sections: 

• Progress Sonic Documentation on page 34 

• Progress Sonic Infocenter on page 36 

• Progress Sonic Education and Training on page 37 

• Progress Software Developers Network (PSDN) on page 37 

• Progress Sonic Technical Support on page 37 

• Progress Sonic Evaluation Support on page 38 


3

Chapter 3: Learning More About the Progress Sonic Products 

Progress Sonic Documentation 

Sonic installations always have a welcome page that provides links to Sonic 

documentation, release notes, communities, and support. See the release’s Product 

Update Bulletin book to see what’s new and what’s changed since prior releases. 

The Sonic 8.5.1 documentation set—accessed at PSDN or at its remote site—includes the 

following books and API references. 

SonicMQ Documentation 

SonicMQ installations provide the following documentation: 

• Progress Sonic Installation and Upgrade Guide — The essential guide for 

installing, upgrading, and updating SonicMQ on distributed systems, using the 

graphical, console or silent installers, and scripted responses. Describes on-site tasks 

such as defining additional components that use the resources of an installation, 

defining a backup broker, creating activation daemons and encrypting local files. Also 

describes the use of characters and provides local troubleshooting tips. 

• Getting Started with Progress SonicMQ — Provides an introduction to the scope 

and concepts of SonicMQ messaging. Describes the features and benefits of 

SonicMQ messaging in terms of its adherence to the JavaSoft JMS specification and 

its rich extensions. Provides step by step instructions for sample programs that 

demonstrate JMS behaviors and usage scenarios. Concludes with a glossary of terms 

used throughout the SonicMQ documentation set. 

• Progress SonicMQ Configuration and Management Guide — Describes the 

configuration toolset for objects in a domain. Also shows how to use the JNDI store for 

administered objects, how integration with Progress Actional is implemented, and how 

to use JSR 160 compliant consoles. Shows how to manage and monitor deployed 

components including metrics and notifications. 

• Progress SonicMQ Deployment Guide — Describes how to architect components 

in broker clusters, the Sonic Continuous Availability Architecture and Dynamic 

Routing Architecture®. Shows how to use the protocols and security options that 

make your deployment a resilient, efficient, controlled structure. Covers all the facets 

of HTTP Direct, a Sonic technique that enables SonicMQ brokers to send and receive 

pure HTTP messages. 

• Progress SonicMQ Administrative Programming Guide — Shows how to create 

applications that perform management, configuration, runtime and authentication 

functions. 

• Progress SonicMQ Application Programming Guide— Takes you through the 

Java sample applications to describe the design patterns they offer for your 

applications. Details each facet of the client functionality: connections, sessions, 

transactions, producers and consumers, destinations, messaging models, message 

types and message elements. Complete information is included on hierarchical 

namespaces, recoverable file channels and distributed transactions. 


Progress Sonic Documentation 

• Progress SonicMQ Performance Tuning Guide — Illustrates the buffers and 

caches that control message flow and capacities to help you understand how 

combinations of parameters can improve both throughput and service levels. Shows 

how to tune TCP under Windows and Linux for the Sonic Continuous Availability 

Architecture. 

• SonicMQ API Reference — Online JavaDoc compilation of the exposed SonicMQ 

Java messaging client APIs. 

• Management Application API Reference — Online JavaDoc compilation of the 

exposed SonicMQ management configuration and runtime APIs. 

• Metrics and Notifications API Reference — Online JavaDoc of the exposed 

SonicMQ management monitoring APIs. 

• Progress Sonic Event Monitor User’s Guide — Packaged with the SonicMQ 

installer, this guide describes the Progress Sonic logging framework to track, record 

or redirect metrics and notifications that monitor and manage applications. 

Other SonicMQ Documentation 

The Progress Sonic download site provides access to additional client, and JCA adapter 

products and documentation: 

• Progress SonicMQ .NET Client Guide — Packaged with the SonicMQ .NET client 

download, this guide takes you through the C# sample applications and describes the 

design patterns they offer for your applications. Details each facet of the client 

functionality: connections, sessions, transactions, producers and consumers, 

destinations, messaging models, message types and message elements. Includes 

complete information on hierarchical namespaces and distributed transactions. The 

package also includes online API reference for the Sonic .NET client libraries, and 

samples for C++ and VB.NET. 

• Progress SonicMQ C Client Guide — Packaged with the SonicMQ C/C++/COM 

client download, this guide presents the C sample applications and shows how to 

enhance the samples, focusing on connections, sessions, messages, producers and 

consumers in both the point-to-point and publish/subscribe messaging models. 

Provides tips and techniques for C programmers and gives detailed information about 

releasing objects and about using XA resources for distributed transactions. The 

package also includes online API reference for the SonicMQ C client. 

• Progress SonicMQ C++ Client Guide — Packaged with the SonicMQ C/C++/COM 

client download, this guide presents the C++ sample applications and shows how to 

enhance the samples, focusing on connections, sessions, messages, producers and 

consumers in both the point-to-point and publish/subscribe messaging models. 

Provides tips and techniques for C++ programmers and gives detailed information 

about using XA resources for distributed transactions. The package also includes 

online API reference for the SonicMQ C++ client. 



• Progress SonicMQ COM Client Guide — Packaged with the SonicMQ C/C++/COM 

client download for Windows, this guide presents the COM sample applications under 

ASP, and Visual C++. Shows how to enhance the samples, focusing on connections, 

sessions, messages, producers and consumers in both the point-to-point and 

publish/subscribe messaging models. Provides tips and techniques for COM 

programmers. The package also includes online API reference for the SonicMQ COM 

client. 

• Progress SonicMQ 8.5.1 Resource Adapter for JCA User’s Guide for WebSphere 

— Packaged with this JCA adapter in a separate download, this guide describes the 

Sonic Resource Adapter for JCA and using it with a WebSphere application server. 

• Progress SonicMQ 8.5.1 Resource Adapter for JCA User’s Guide for Weblogic 

— Packaged with this JCA adapter in a separate download, this guide describes the 

Sonic Resource Adapter for JCA and using it with a Weblogic application server. 

• Progress SonicMQ 8.5.1 Resource Adapter for JCA User’s Guide for JBoss — 

Packaged with this JCA adapter in a separate download, this guide describes the 

Sonic Resource Adapter for JCA and using it with a JBoss application server. 

Sonic ESB Documentation 

The Sonic ESB product family provides the following documentation: 

• Progress Sonic Installation and Upgrade Guide — Provides information about 

installing, updating, and upgrading Sonic ESB components. 

• Progress Sonic Workbench User Guide (Progress Sonic Workbench Online 

Help) — Provides information about developing, testing, and debugging applications 

on the Progress Sonic Workbench. Describes the Sonic Workbench, its editors, and 

tools. Provides information about how to get started with each component of the Sonic 

ESB Product Family and describes sample applications. 

• Progress Sonic ESB Configuration and Management Guide — Provides 

information about configuring and managing components used by the Sonic ESB 

Product Family. Describes deployment configurations for Sonic ESB, Sonic Database 

Service, and Sonic BPEL Server 

• Progress Sonic ESB Deployment Guide — Provides information about moving 

development projects into test and production environments. Describes 

recommended build procedures, domain mappings, and reporting features. 

• Progress Sonic BPEL Server: Management API Guide — Describes how to use the 

management API to programatically access BPEL server functionality. 

• Sonic ESB API Reference — Online JavaDoc compilation of the Sonic ESB APIs. 

Progress Sonic Infocenter 

The Progress Sonic Infocenter provides an Eclipse-independent deployment of the Sonic 

Workbench online help in the Progress Sonic Workbench User Guide. Just use your 

preferred browser to access the Infocenter at: 

http://documentation.progress.com/infocenter/sonic/8.5.1 


Progress Sonic Education and Training 

Choose from: 

Progress Sonic Education and Training 

• Instructor-led Training — Progress Software offers instructor-led lecture and 

exercise style training on-site at your location. Courses are taught by field consultants 

who have certified on the courseware, yet also bring practical experience to the 

classroom. 

• Subscription-based eLearning Service — Gives you access to the Progress Sonic 

Catalog, which is part of the Enterprise Infrastructure eLearning Library. Each student 

has unlimited online access to the Progress Sonic Catalog as well as the entire 

Enterprise Infrastructure library of eLearning titles. 

Progress Software Developers Network (PSDN) 

The Progress Software Developers Network, PSDN Online, is the technical community 

website for all Progress Software products. Browse through current technical whitepapers, 

shared code, evaluation versions, demonstrations, video presentations, and product 

documentation. PSDN Online is a dynamic, interactive, 24x7 community where developers 

contribute to the forums, blogs, ratings, watches, and comments. Access is free—just go 

to www.psdn.com and register. 

Progress Sonic Technical Support 

Progress Software’s Sonic support staff can provide assistance using the resources on 

their Web site at www.progress.com/sonic. There you can access technical support 

for licensed Progress Sonic editions to help resolve technical problems that you encounter 

when installing or using Sonic products. 

The Progress Sonic support program offerings include: 

• Tiered support services 

• Support centers located around the world 

• Electronic knowledge center for self-service 

• Access to our on-line developers network and related Web sites 

• Electronic software download capability 



When contacting Technical Support, please have the following information available: 

• The release version number and serial number of SonicMQ that you are using. This 

information is listed on the license addendum. It is also at the top of the SonicMQ 

Broker console window and might appear as follows: 

SonicMQ Continuous Availability Edition [Serial Number 

nnnnnnn]Release nnn Build Number nnn Protocol nnn 

• The release version number and serial number of Sonic ESB that you are using. This 

information is listed on the license addendum. It is also near the top of the console 

window for a Sonic ESB Container. For example: 

Sonic ESB Continuous Availability Edition [Serial Number: 

nnnnnnn]Release nnn Build Number nnn 

• The platform on which you are running Progress Sonic products, and any other 

relevant environment information. 

• The Java Virtual Machine (JVM) your installation uses. 

• Your name and, if applicable, your company name. 

• E-mail address, telephone, and fax numbers for contacting you. 

Progress Sonic Evaluation Support 

• United States, Canada & Latin America — +1 781 999 7100 eval@progress.com 

• Europe, Middle East & Africa — +44 (0) 1753 217000 info-emea@progress.com 

• Asia Pacific — sonic-eval-ap@progress.com

Progress Sonic Product Update Bulletin 8.5.1

Create successful ePaper yourself

Delete template?

Save as template?