Wiki
Interstage BPM Advanced Edition v8.1 Build 123
Task » Versions & Releases » Interstage BPM Advanced Edition v8.1 Build 123
(0 rating)
FUJITSU SOFTWARE RELEASE GUIDE
Interstage Business Process Manager Advanced Edition 8.1
July 2007
Thank you for choosing Interstage Business Process Manager!
The products described in this guide are abbreviated as follows: "Interstage Business Process Manager" is abbreviated as "Interstage BPM", "ARIS Process Performance Manager" is abbreviated as "ARIS PPM".
1. Interstage BPM CD Contents
The Interstage BPM CD consists of the following directory structure:
(CD Root)
+-- InterstageBPM_AE8.1_ReleaseNotes.htm (This file)
+-- docs\
| +-- AdministrationGuide.pdf (Administration Guide)
| +-- DevelopersGuide.pdf (Developer's Guide)
| +-- InstallationGuide_AE.pdf (Installation Guide)
| +-- StudioUserGuide.pdf (Studio User's Guide)
| +-- UsersGuide.pdf (User's Guide)
| +-- PPMIntegrationGuide.pdf (ARIS PPM Integration Guide)
| +-- ecma-262.pdf (ECMAScript Language Specification)
| +-- apidocs\
| +-- index.html (Javadoc)
| +-- ...
+-- install\
| +-- setupwin32.exe (Interstage BPM Installer for Windows)
| +-- setupSolaris.bin (Interstage BPM Installer for Solaris)
| +-- setupLinux.bin (Interstage BPM Installer for Linux)
| +-- setupaix.bin (Interstage BPM Installer for AIX)
| +-- ...
+-- studio\
+-- setup.exe (Interstage BPM Studio installer)
+-- Readme.txt (Interstaeg BPM Studio readme file)
+-- ...
2. Interstage BPM User Documentation
Interstage BPM provides the following set of user documentation:
- Installation Guide
- Administration Guide
- Developer's Guide
- Studio User's Guide
- User's Guide
- ARIS Process Performance Manager Integration Guide
- Javadoc (API reference)
- Online help for the Console, Administration Facility, and Studio
The guides are provided in PDF format, Javadoc and online help are provided in HTML format. To read PDF files, you can download the Adobe Reader for free from http://www.adobe.com/ .
3. Software Requirements
- Certified Combinations for Server: Interstage BPM supports many operating systems, databases, and directory servers. The following platform combinations are certified by Fujitsu.
- Windows 2003 + SQL Server 2005 + Active Directory 2003
- Windows 2003 + SQL Server 2005 + NT Native Directory 2003
- Windows 2003 + SQL Server 2005 + CentraSite 2.2 URM (Windows; local)
- Windows 2003 + Oracle 10g R2 + Sun Java System Directory 5.1
- Solaris 9 + Oracle 10g R2 + Sun Java System Directory 5.1
- Solaris 9 + SQL Server 2000 + Sun Java System Directory 5.1
- Solaris 10 + Oracle 10g R2 + Sun Java System Directory 5.1
- Red Hat Enterprise Linux ES 4.0 + Oracle 10g R2 + Sun Java System Directory 5.1
- AIX + Oracle 10g R2 + Sun Java System Directory 5.1
Note:
(1) See the "Minimum Software Requirements for ..." sections below for the full product names, the precise software editions, versions or service packs.
For 1-4, please refer to “2. Minimum Software Requirements for Server on Windows”.
For 5-7, please refer to “3. Minimum Software Requirements for Server on Solaris”.
For 8, please refer to “4. Minimum Software Requirements for Server on Linux”.
For 9, please refer to “5. Minimum Software Requirements for Server on AIX”.
(2) Only English software versions are supported.
(3) For the latest information on certified combinations, supported versions or service packs of the products, contact your local Fujitsu Support organization. - Minimum Software Requirements for Server on Windows
- Operating System - one of the following:
- Microsoft Windows Server 2003 Standard Edition / Enterprise Edition SP2 (x32)
- Microsoft Windows Server 2003 R2 Standard Edition / Enterprise Edition SP2 (x32)
Note: The hostname (computer name) of the computer where Interstage BPM Server will be installed must not contain underscores (_).
- Database - one of the following:
- Microsoft SQL Server 2005 Standard Edition / Enterprise Edition SP1
- Oracle 10g R2 Standard Edition / Standard Edition One / Enterprise Edition (Windows version)
- Directory Server - one of the following:
- Sun Java System Directory Server 5.1
- Microsoft Active Directory (Windows 2003)
- NT Native Directory (Windows 2003)
- CentraSite 2.2 URM (Windows version) combined with NT Native Directory or Microsoft Active Directory
Note: NT Native Directory and CentraSite URM must be installed on the same computer as the Interstage BPM Server.
- Java Environment
- J2SE Development Kit (JDK) 5.0 Update 10
- Operating System - one of the following:
- Minimum Software Requirements for Server on Solaris
- Operating System - one of the following:
- Solaris 9 Operating System for SPARC Platforms (64bit)
- Solaris 10 Operating System for SPARC Platforms (64bit)
- Database - one of the following:
- Oracle 10g R2 Standard Edition / Standard Edition One / Enterprise Edition (Solaris version)
- Microsoft SQL Server 2000 Standard Edition / Enterprise Edition SP4
- Directory Server
- Sun Java System Directory Server 5.1
- Java Environment
- J2SE Development Kit (JDK) 5.0 Update 10
- Operating System - one of the following:
- Minimum Software Requirements for Server on Linux
- Operating System
- Red Hat Enterprise Linux ES 4.0 (x86)
- Database
- Oracle 10g R2 Standard Edition / Standard Edition One / Enterprise Edition (Linux version)
- Directory Server
- Sun Java System Directory Server 5.1
- Java Environment
- J2SE Development Kit (JDK) 5.0 Update 10
- Operating System
- Minimum Software Requirements for Server on AIX
- Operating System
- AIX 5L V5.3 (POWER 64bit)
- Database
- Oracle 10g R2 Standard Edition / Standard Edition One / Enterprise Edition (AIX version)
- Directory Server
- Sun Java System Directory Server 5.1
- Java Environment
- IBM JDK 1.5.0
- Operating System
- Minimum Software Requirements for Clients
- Operating System
- Microsoft Windows XP Professional SP2
- Microsoft Windows Server 2003 Standard Edition / Enterprise Edition SP2 (x32)
- Microsoft Windows Server 2003 R2 Standard Edition / Enterprise Edition SP2 (x32)
- Web Browser
- Microsoft Internet Explorer 6.0 SP1
- Operating System
- Minimum Software Requirements for Studio: Please refer to the Readme.txt of Interstage BPM Studio.
- SVG Viewer: To correctly display process definition graphics on Administration Facility, you need to install an SVG viewer into your browser. You can get an SVG viewer from the Adobe web site. Adobe SVG Viewer 3.02 works well with this version of Interstage BPM.
4. Hardware Requirements
Please refer to the Interstage Business Process Manager Installation Guide.
5. Installation and Uninstallation
Please refer to the Interstage Business Process Manager Installation Guide for the system requirements and detailed instructions on how to install and uninstall Interstage Business Process Manager. To get started with Interstage Business Process Manager after installation, we suggest that you first take a look at Chapter 2 "Using the Administration Facility" in the Interstage Business Process Manager Administration Guide.
Note: Concerning security issues, please read "Appendix A Security" in the Interstage Business Manager Installation Guide as well as the following additional information.
(1) After installation Interstage BPM Server is configured for running in "Demo Mode". You should switch the mode to "Security Mode" using the SecuritySwitch property in the ibpm.properties file. Refer to "Appendix A ibpm.properties File" in the Interstage Business Process Manager Administration Guide for details.
(2) 'Logon as a batch job' user right (privilege) is given to the Interstage Business Process Manager administrator account, typically 'ibpm_server1', which is created during the installation process. (on Windows platforms)
(3) Fujitsu strongly recommends you not to use words found in dictionaries for any password. Also, easy-to-guess passwords such as real name, phone number, birthday and so on should not be used.
When you want to install Interstage BPM Studio, which is a standalone process design tool, please refer to the Readme.txt file in the studio directory of the Interstage BPM CD for the system requirements and instructions on how to install and uninstall Interstage BPM Studio. Please refer to the the Interstage Business Process Manager Studio User's Guide for the usage of Interstage BPM Studio. Please note that Interstage BPM Studio itself can be used in a Windows environment only, but you can download/upload from/to an Interstage BPM Server running on an other operating system.
6. Known Issues
Notes for upgrading:
- Upgrading from Previous Version: While upgrading from a previous Interstage BPM Advanced Edition version (prior to 8.1 (this version)), it is necessary to provide the same ‘Database non-administrator user name’ that was already used in the earlier version. You can confirm the name by looking at the value of the
DBALoginNameproperty in \bin\ibpm.properties or iflow.properties. Please note down theDBALoginNamevalue before uninstalling the previous version.
Common issues :
- Installation (1): Do not use more than one '$' character in passwords that you enter during an Interstage BPM installation. For example, "mypa$sword" is valid, whereas "mypa$$word" is not. The Interstage BPM installer will not display an error message. However, after the installation, you will not be able to log in to the corresponding system.
- Installation (2): If the "JDK" directory path contains space, Interstage BPM installation will fail. Please setup JDK to the directory of which the directory path does not contain any spaces.
- Installation (3): When Interstage BPM Server and Interstage BPM Clients are installed on different machines, Decision Tables are not working. Workaround: Please manually adjust the parameters 'DefaultFileName' and 'ActiveDtmFileName' in the file \taskmanager\iflowjsp\jsp\dtmconfig.properties on client side for pointing to the files ActiveDtm.dat and dtm.dat in the specified attachment folder on server side.
- Starting Interstage BPM Server after installation: You must perform directory setup to import the iFlowLDAPAdd.ldif file BEFORE starting Interstage BPM Server. Otherwise, starting Interstage BPM Server will fail. Please refer to "4.2 Setting Up Microsoft Active Directory" for Microsoft Active Directory or "4.3 Setting Up Sun Java System Directory Server" for Sun Java System Directory Server.
- Uninstallation (1): When uninstallation failed for some reasons, use the following workaround.
[For Windows platforms]
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs.- Delete the Gen1 directory from C:\Program Files\Common Files\InstallShield\Universal\common\
- Delete the registry keys under the following registry location:
HKEY_LOCAL_MACHINE\Software\Fujitsu\Install\Interstage BPM Server\
HKEY_LOCAL_MACHINE\Software\Fujitsu\Install\Interstage BPM Clients\
HKEY_LOCAL_MACHINE\Software\Fujitsu\Install\Interstage BPM DBConfig Tool\
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Interstage Business Process Manager 8.1\ - Delete the Interstage BPM directory and remove its shortcut too.
- Delete the Gen1 directory from /InstallShield/Universal/common/ for UNIX and Linux platforms
- Delete the Interstage BPM directory
- On a Solaris platform, remove the Interstage BPM-related packages which are installed. The procedure for removing the packages is as mentioned below:
- Create a file ibpm.uninst with some contents in the /tmp location.
- Execute the commands “pkgrm FJSVibpm” and “pkgrm FJSVibpmc”for removing the Interstaeg BPM server and client packages
- Delete the file ibpm.uninst from /tmp.
- Uninstallation (2): When the vpd.script file (in /InstallShield/Universal/common/Gen1/_vpddb/ for UNIX, C:\Program Files\Common Files\InstallShield\Universal\common\Gen1\_vpddb/ for Windows) was corrupted for some reasons, uninstallation will fail. In such a case, use the workaround described in "Uninstallation (1)".
- UDA Variable Names (1): If a UDA shall be used within a Trigger, it must not contain any other characters than: 'a'-'z', 'A'-'Z', '0'-'9' and '_'. Blanks are also not allowed.
- UDA Variable Names (2): The Interstage Business Process Manager User's Guide states that non-ASCII characters cannot be used for UDA Variables names. In fact, in certain situations, you are allowed to use non-ASCII characters in the name of the UDA, but when you do, you must keep a couple of restrictions in mind. There are actually "two names" for every UDA: the descriptive name and the identifier name. The one that you specify for the UDA is a descriptive name and can contain any characters. The other, the identifier name, must contain only ASCII letters('a'-'z', 'A'-'Z'), numerals ('0'-'9'), and underscores ('_'). The identifier name is formed by taking the descriptive name and removing all of the characters except for ASCII letters, numerals, and underscores. For example, if you create a UDA with a descriptive name "Service, External", it will automatically be assigned the identifier name of "ServiceExternal".
Users don't usually see the identifier name of a UDA variable, but it is used in the JavaScript environment and in web pages to identify the UDA. Care must be taken to avoid having two UDA variables with the same identifier name. For example, if you create the UDA above, and you also create a UDA named "Service--External", this latter UDA will have the same identifier name as the first, and the system will in certain situations assign the value to the wrong UDA variable. If you create a UDA with a name that consists entirely of non-ASCII characters, then the identifier name will be empty, and this will not work at all. You must have some ASCII letters, and the letters must be unique across UDAs. In this release, the Studio and the Process Designer cannot handle names that consist entirely of non-ASCII characters, so such settings are difficult to accomplish without using the API directly. - Optimized Worklist UDA: If you chose Microsoft SQL Server 2000 as database, you cannot use optimzed worklist UDAs. This is because Microsoft SQL Server 2000 has a limitation of record size (8K). Therefore the following method always returns an empty array:
package com.fujitsu.iflow.model.workflow;
DataItem[] WFAdminSession.getOptimizedWorkListUDAs(); - Agents: If an agent is not able to complete its task successfully within the number of attempts specified in the agentsConfig.xml file as parameter 'EscalationInterval' any further attempt will be prevented. The process instance this agent belongs to is set to the error state. In case an FTPAgent is used and an exception occurs during its execution the system will automatically catch the exception and retry to invoke the agent again, as long as no escalation is necessary. The corresponding process instance is only put to the error state if the number of agent invocations exceeds the specified escalation limit. The information on the caught exception is not stored in the UDAs specified in the file ftp.xml as parameters 'ServiceStatusUDA' and 'ServiceResultUDA'.
- Java Actions: To run the Remote Command Invoker Java Action, \bin\StartJACommandServer.bat needs to be changed as follows.
[OLD] start "JACommandServer" %JDK_HOME% com.fujitsu.iflow.utilities.JACommandServer %1 %2
[NEW] start "JACommandServer" %JDK_HOME%\jre\bin\java com.fujitsu.iflow.utilities.JACommandServer %1 %2 - Administration Facility: In the "Search Filter Criteria" page of the "Process Instances" tab, if you press the 'Enter' key while the cursor placed in any text field or any check box, the calendar will pop up. To close the calendar, click the 'x' button or press the 'Esc' key. If you click a date in the calendar, it is entered in the "Date - From" field.
- BPM Console (Handling of Spaces in Search Conditions): In the Console, in several forms spaces are not handled correctly in search conditions such as name and date. Workaround: Remove unnecessary spaces in search conditions.
- BPM Console (Handling of Decimal Separators): Currently integer values are not handled consistently in the Task Manager. In some situations decimal separators are removed. Thus, if “20.0” is specified for an integer UDA, “200” will be stored in the database. Workaround: Don’t use decimal separators for integer UDA values.
- BPM Console (Decision Tables): After setting the ForceDeploy property in the dtmconfig.properties file to true, it won't be set back to false automatically. So it has to be reverted to false manually.
- ARIS PPM integration (1): You need to install ARIS PPM into a directory which does not contain spaces in the directory path. This is an ARIS PPM issue, and you will get a warning message with ARIS PPM 4.0.1 installer if the installation directory path contains spaces.
- ARIS PPM integratio (2): ARIS PPM supports a maximum of 100 characters for dimension values. If you try to import process instances from Interstage BPM having dimension values with more than 100 characters, import errors may occur. To prevent these errors, you are recommended to change the ARIS PPM import configuration as follows:
- Edit the database configuration file: /config/ibpm/Database_settings.properties
- Change the settings of the parameters
TRUNCATE_DIMENSION_STRINGandTRUNCATE_DIMENSION_MARKas follows:
TRUNCATE_DIMENSION_STRINGS=MARK
TRUNCATE_DIMENSION_MARK=#ERROR: Too many characters
With these settings, dimension values and descriptions exceeding 100 characters are replaced by the string defined inTRUNCATE_DIMENSION_MARKduring the import. Make sure that the length of this string does not exceed 100 characters.
- XPDL 2.0 support: XPDL 2.0 requires that any XML tags nested inside an extended attribute tag must be declared to be in a namespace other than the default "xpdl" namespace. Previous versions of Interstage BPM have not enforced this. The current release upgrades the behavior in two ways to conform to the XML standard:
- Namespace declarations and tag name prefixes will be preserved when an extended attribute is copied between an XPDL file and Interstage BPM internal extended attribute values. Thus if you read a valid XPDL file with namespace qualified extended attribute tags, you will now receive those namespace declarations and prefixes when you export XPDL (Administration Facility, BPM Console, Studio) files or call
getExtendedAttributes(Model API). - In order to guarantee that the XPDL is valid, if an extended attribute tag has a child tag that is NOT namespace qualified, then the "ibpm" prefix will be added to that tag, so that the tag will properly be considered part of the ibpm namespace. The XPDL schema simply says that the namespace must be something other than "xpdl", so the choice of "ibpm" is an arbitrary choice necessary to make the file valid according the XML Schema rules. Again, this will only be added when a tag is missing a required prefix.
Windows-specific issues:
- Namespace declarations and tag name prefixes will be preserved when an extended attribute is copied between an XPDL file and Interstage BPM internal extended attribute values. Thus if you read a valid XPDL file with namespace qualified extended attribute tags, you will now receive those namespace declarations and prefixes when you export XPDL (Administration Facility, BPM Console, Studio) files or call
- CentraSite URM as directory (1): During the CentraSite installation you need to specify a CentraSite Administrator user who is also an Operating System Administrator (a member of the Administrators group). In a Windows 2000 environment, the user must be included in the 'Act as part of the operating system' policy. You can check this using Start > Settings > Control Panel > Administrative Tools > Local Security Policy > Local Policies > User Rights Assignment.
- CentraSite URM as directory (2): During the CentraSite installation the domain name of the installing user seems to be wrong if the Actice Directory Server is configured to have a different domain name for "pre Windows 2000" domains. The authentication uses the 2000/XP domain name, but the installation enters the pre Windows 2000 domain name.
Thus, if "user1" is the local user ID of the installing user and "AAA" is the pre Windows 2000 domain name and "BBB" is the new domain name, the installation currently will add the user "AAA\USER1" to the CentraSiteAdmin role instead of "BBB\USER1".
To add "BBB\USER1" to the CentraSiteAdmin group, issue the following request via an HTTP client on the machine where the CentraSite Application Server Tier is running:
http://localhost:53305/CentraSite/CentraSite/ino:security?_xquery=declare%20namespace%20ino="http://namespaces.softwareag.com/tamino/response2"%20update%20insert%20BBB\UUU%20into%20input()/ino:group[@ino:groupname="CentraSiteAdmin"]
Make sure that the domain name and the user ID are all in upper-case. When prompted for a user ID and password please use "DefaultUser" / "PwdFor_CS21". (SAGSIS P280912) - CentraSite URM as directory (3): If you are using CentraSite URM as directory and changed the computer name, you need to reinstall CentraSite.
Common issues during development:
- Parallel operations: If one or more of the following operations is executed in the same session (WFSession/WFAdminSession) while getting the process instance history, wrong result could be returned.
- ProcessInstance.getHistory(int[]) // Retrieve all history records of this process instance.
Remedy: Please execute the operations above after getting the process instance history. Please don't reuse the IflowEnumeration which was used for retrieving the history.
7. API Reference Supplements
7.1 Custom Directory APIs
Javadoc (API Reference) contains the information about the following packages for custom directory APIs.
- com.fujitsu.iflow.ddframework.intf
- com.fujitsu.iflow.diradapter.intf
The Interstage Business Process Manager Developer's Guide does not describe how to use the APIs. When you create your own custom directory adapter using the APIs, please contact your local Fujitsu Support Organization.
7.2 Deprecated Methods
The following methods in the Model API have been deprecated in this release. It is not recommended to use these methods in the future, for backward compatibility they have been retained.
package com.fujitsu.iflow.model.util;
public class ModelException extends Exception
{
// Please use method getCause() instead.
public Throwable getSource();
// Please use the Java standard method "Throwable.getCause() instead.
public Throwable getCause();
}
package com.fujitsu.iflow.model.workflow;
public interface ProcessInstance
{
// This field is not used on neither server nor model side.
public final static int STATE_OPEN;
// Please use constant HISTORY_ISHANDLED_CODE instead.
public final static int HISTORY_ISHANDLED;
}
package com.fujitsu.iflow.model.workflow;
public interface WFObjectList
{
// This method is only supported in normal list mode. Instead of using the
// normal list mode it is recommended to use the batched mode.
public Object getObject(long id);
}
package com.fujitsu.iflow.model.wfadapter;
public interface DocRepository
{
// This method is no longer required since files that are stored on the
// server can be directly retrieved from the server, e.g. via the method
// getDocument.
public String pathToLocalHostFormat(String path);
}
8. Restrictions
There are no restrictions.
Appendix A High Risk Activity
The Customer acknowledges and agrees that the Product is designed, developed and manufactured as contemplated for general use, including without limitation, general office use, personal use, household use, and ordinary industrial use, but is not designed, developed and manufactured as contemplated for use accompanying fatal risks or dangers that, unless extremely high safety is secured, could lead directly to death,personal injury, severe physical damage or other loss (hereinafter "High Safety Required Use"), including without limitation, nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control, medical life support system, missile launch control in weapon system. The Customer shall not use the Product without securing the sufficient safety required for the High Safety Required Use. In addition, Fujitsu (or other affiliate's name) shall not be liable against the Customer and/or any third party for any claims or damages arising in connection with the High Safety Required Use of the Product.
Appendix B Acknowledgements
- This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
- This product includes software developed by the JDOM Project (http://www.jdom.org/).
- This product includes Eclipse SDK 3.1.1 and Graphical Editing Framework 3.1.1 developed by the Eclipse Foundation (http://www.eclipse.org/). Eclipse SDK 3.1.1 includes software developed by the MX4J project (http://mx4j.sourceforge.net/).
- This product includes WSDL4J. WSDL4J is licensed under IBM Common Public License. You can obtain the source code on demand. Contact your local Fujitsu Support organization when you need the source code.
- This product includes UDDI4J. UDDI4J is licensed under IBM Public License. You can obtain the source code on demand. Contact your local Fujitsu Support organization when you need the source code.
- This product includes CUP Parser Generator for Java.
- This product includes Tanuki Software Java Service Wrapper.
Appendix C The Apache Software License
The license of "The Apache Software License, Version 1.1" is as follows:
/* ==================================================================== * 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 * . * * Portions of this software are based upon public domain software * originally written at the National Center for Supercomputing Applications, * University of Illinois, Urbana-Champaign. */
The license of "Apache License Version 2.0" is as follows:
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.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.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Appendix D License of JDOM
The license of JDOM is as follows:
/*--
Copyright (C) 2000-2002 Brett McLaughlin & Jason Hunter.
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 disclaimer that follows
these conditions in the documentation and/or other materials
provided with the distribution.
3. The name "JDOM" must not be used to endorse or promote products
derived from this software without prior written permission. For
written permission, please contact license@jdom.org.
4. Products derived from this software may not be called "JDOM", nor
may "JDOM" appear in their name, without prior written permission
from the JDOM Project Management (pm@jdom.org).
In addition, we request (but do not require) that you include in the
end-user documentation provided with the redistribution and/or in the
software itself an acknowledgement equivalent to the following:
"This product includes software developed by the
JDOM Project (http://www.jdom.org/)."
Alternatively, the acknowledgment may be graphical using the logos
available at http://www.jdom.org/images/logos.
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 JDOM AUTHORS OR THE PROJECT
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 JDOM Project and was originally
created by Brett McLaughlin and
Jason Hunter . For more information on the
JDOM Project, please see .
*/
Appendix E Eclipse Public License
The license of "Eclipse Public License v1.0" is as follows:
Eclipse Public License - v 1.0
THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.
1. DEFINITIONS
"Contribution" means:
a) in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and
b) in the case of each subsequent Contributor:
i) changes to the Program, and
ii) additions to the Program;
where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. A Contribution 'originates'
from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. Contributions do not
include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license
agreement, and (ii) are not derivative works of the Program.
"Contributor" means any person or entity that distributes the Program.
"Licensed Patents " mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or
when combined with the Program.
"Program" means the Contributions distributed in accordance with this Agreement.
"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.
2. GRANT OF RIGHTS
a) Subject to the terms of this Agreement, each Contributor hereby grants
Recipient a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display, publicly perform,
distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.
b) Subject to the terms of this Agreement, each Contributor hereby grants
Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise
transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of
the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such
combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution.
No hardware per se is licensed hereunder.
c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any
Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability
to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising
the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights
needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility
to acquire that license before distributing the Program.
d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license
set forth in this Agreement.
3. REQUIREMENTS
A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:
a) it complies with the terms and conditions of this Agreement; and
b) its license agreement:
i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions
of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose;
ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and
consequential damages, such as lost profits;
iii) states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and
iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable
manner on or through a medium customarily used for software exchange.
When the Program is made available in source code form:
a) it must be made available under this Agreement; and
b) a copy of this Agreement must be included with each copy of the Program.
Contributors may not remove or alter any copyright notices contained within the Program.
Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to
identify the originator of the Contribution.
4. COMMERCIAL DISTRIBUTION
Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this
license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering
should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in
a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor
("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal
actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor
in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or
Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and
b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement
negotiations. The Indemnified Contributor may participate in any such claim at its own expense.
For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties
are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other
Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the
Commercial Contributor must pay those damages.
5. NO WARRANTY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.
6. DISCLAIMER OF LIABILITY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), 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 OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY
OF SUCH DAMAGES.
7. GENERAL
If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.
If Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed.
All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and
does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations
under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.
Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only
be modified in the following manner. The Agreement Steward reserves the right to publish new versions (including revisions) of this Agreement from
time to time. No one other than the Agreement Steward has the right to modify this Agreement. The Eclipse Foundation is the initial Agreement
Steward. The Eclipse Foundation may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of
the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version
of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute
the Program (including its Contributions) under the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no
rights or licenses to the intellectual property of any C