Apasham Jiboj

ENOVIA Engineering
Central
2011x
Administrators Guide
1
Copyright and Trademark Information
Dassault Systmes, 2001 - 2010
All rights reserved.

PROPRIETARY RIGHTS NOTICE: This documentation is proprietary property of Dassault Systmes and its subsidiaries. This documentation shall be treated as confidential information and may only be used by employees or contractors with the Customer in accordance with the applicable Software
License Agreement.
Adaplet, Compliance Connect, DesignSync, ENOVIA, MatrixOne, ProjectSync, Synchronicity, and Team Central are registered trademarks of Dassault Systmes.
ENOVIA Live Collaboration, ENOVIA Live Collaboration Business Process Services, ENOVIA Live Collaboration Server, ENOVIA Studio Modeling Platform, ENOVIA Studio Federation Toolkit, ENOVIA Studio Customization Toolkit, ENOVIA 3D Live, ENOVIA Engineering Central, ENOVIA
Library Central, ENOVIA Materials Compliance Central, ENOVIA Program Central, ENOVIA Sourcing Central, ENOVIA Specification Central, ENOVIA Supplier Central, ENOVIA Designer Central, ENOVIA Collaborative Interference Management, ENOVIA Semiconductor Accelerator for Team
Compliance, ENOVIA Aerospace and Defense Accelerator for Program Management, ENOVIA Apparel Accelerator for Design and Development, ENOVIA X-BOM Cost Analytics, ENOVIA X-BOM Manufacturing, ENOVIA Variant Configuration Central, ENOVIA Synchronicity DesignSync Data
Manager, IconMail, ImageIcon and Star Browser are trademarks of Dassault Systmes.
Oracle is a registered trademark of Oracle Corporation, Redwood City, California. DB2, AIX, and WebSphere are registered trademarks of IBM Corporation. WebLogic is a registered trademark of BEA Systems, Inc. Solaris, UltraSPARC, Java, JavaServer Pages, JDBC, and J2EE are registered
trademarks of Sun Microsystems, Inc. Windows XP and Internet Explorer are registered trademarks of Microsoft Corp. HP and HP-UX are registered trademarks of HP. All other product names and services identified throughout this book are recognized as trademarks, registered trademarks, or service
marks of their respective companies.
The documentation that accompanies ENOVIA products describes the applications as delivered by Dassault Systmes. This documentation includes readme files, online help, user guides, and administrator guides. If changes are made to an application or to the underlying framework, Dassault Systmes
cannot ensure the accuracy of this documentation. These changes include but are not limited to: changing onscreen text, adding or removing fields on a page, making changes to the administrative objects in the schema, adding new JSPs or changing existing JSPs, changing trigger programs, changing the
installation or login process, or changing the values in any properties file. For instructions on customizing the provided documentation, see the Business Process Services Administrators Guide.
Dassault Systmes Enovia Corp.
900 Chelmsford Street
Lowell, MA 01851
Telephone 978.442.2500
Email: enovia.info@3ds.com
http://www.3ds.com
Additional Components
This product also includes additional components copyrighted by other third parties. The sections that follow provide license and copyright notices of these software components.
Apache
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.
Apache Ant
=========================================================================
NOTICE file corresponding to the section 4 d of the Apache License, Version 2.0, in this case for the Apache Ant distribution.
=========================================================================
This product includes software developed by The Apache Software Foundation (http://www.apache.org/).
This product includes also software developed by :
- the W3C consortium (http://www.w3c.org) ,
- the SAX project (http://www.saxproject.org)
Please read the different LICENSE files present in the root directory of this distribution. [BELOW]
This license came from:

http://www.w3.org/Consortium/Legal/copyright-software-19980720
W3C SOFTWARE NOTICE AND LICENSE
2 ENOVIA Engineering Central Administrators Guide

Copyright 1994-2001 World Wide Web Consortium, <a href="http://www.w3.org/">World Wide Web Consortium</a>, (<a href= "http://www.lcs.mit.edu/">Massachusetts Institute of Technology</a>, <a href="http://www.inria.fr/">Institut National de Recherche en Informatique et en Automatique</
a>, <a href= "http://www.keio.ac.jp/">Keio University</a>). All Rights Reserved.
http://www.w3.org/Consortium/Legal/
This W3C work (including software, documents, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:
Permission to use, copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including
modifications, that you make:
The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a short notice of the following form (hypertext is preferred, text is permitted) should be used within the body of any redistributed or derivative code:
"Copyright 1999-2004 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/"
Notice of any changes or modifications to the W3C files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY
PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT,
SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.
This license came from: http://www.megginson.com/SAX/copying.html. However please note future versions of SAX may be covered under http://saxproject.org/?selected=pd
This page is now out of date -- see the new SAX site at http://www.saxproject.org/ for more up-to-date releases and other information. Please change your bookmarks.
SAX2 is Free!
I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release all of the SAX 2.0 source code, compiled code, and documentation contained in this distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of fitness for any purpose.
David Megginson, david@megginson.com
Apache Axis
=========================================================================
NOTICE file corresponding to section 4(d) of the Apache License, Version 2.0, in this case for the Apache Axis distribution.
=========================================================================
This product includes software developed by The Apache Software Foundation (http://www.apache.org/).
Apache Tomcat
[under Apache License, Version 2.0 above]
Apache Servlet-API
FTP
Copyright (c) 1983, 1985, 1989, 1993, 1994
The Regents of the University of California. 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 acknowledgement:
This product includes software developed by the University of California, Berkeley and its contributors.
4. Neither the name of the University 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 REGENTS AND CONTRIBUTORS `À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 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
WAYOUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Copyright (c) 1997-1999 The Stanford SRP Authentication Project
All Rights Reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL STANFORD BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER
Copyright 1990 by the Massachusetts Institute of Technology.
All Rights Reserved.
Export of this software from the United States of America may require a specific license from the United States Government. It is the responsibility of any person or organization contemplating export to obtain such a license before exporting.
WITHIN THAT CONSTRAINT, permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in
supporting documentation, and that the name of M.I.T. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. M.I.T. makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or
implied warranty.
Getline
Copyright (C) 1991, 1992, 1993 by Chris Thewalt (thewalt@ce.berkeley.edu)
Permission to use, copy, modify, and distribute this software for any purpose and without fee is hereby granted, provided that the above copyright notices appear in all copies and that both the copyright notice and this permission notice appear in supporting documentation. This software is provided "as is"
without express or implied warranty.
GifEncoder
GifEncoder - write out an image as a GIF
Transparency handling and variable bit size courtesy of Jack Palevich.
Copyright (C)1996,1998 by Jef Poskanzer <jef@acme.com>. All rights reserved.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS `À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 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
ImageEncoder
ImageEncoder - abstract class for writing out an image
Copyright (C) 1996 by Jef Poskanzer <jef@acme.com>. All rights reserved.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS `À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 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
JavaMail
Sun Microsystems, Inc.
Binary Code License Agreement
READ THE TERMS OF THIS AGREEMENT AND ANY PROVIDED SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY "AGREEMENT") CAREFULLY BEFORE OPENING THE SOFTWARE MEDIA PACKAGE. BY OPENING THE SOFTWARE MEDIA PACKAGE, YOU AGREE TO
THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCESSING THE SOFTWARE ELECTRONICALLY, INDICATE YOUR ACCEPTANCE OF THESE TERMS BY SELECTING THE "ACCEPT" BUTTON AT THE END OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL THESE
TERMS, PROMPTLY RETURN THE UNUSED SOFTWARE TO YOUR PLACE OF PURCHASE FOR A REFUND OR, IF THE SOFTWARE IS ACCESSED ELECTRONICALLY, SELECT THE "DECLINE" BUTTON AT THE END OF THIS AGREEMENT.
1. LICENSE TO USE. Sun grants you a non-exclusive and non-transferable license for the internal use only of the accompanying software and documentation and any error corrections provided by Sun (collectively "Software"), by the number of users and the class of computer hardware for which the
corresponding fee has been paid.
2. RESTRICTIONS. Software is confidential and copyrighted. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. Except as specifically authorized in any Supplemental License Terms, you may not make copies of Software, other than a single copy of
Software for archival purposes. Unless enforcement is prohibited by applicable law, you may not modify, decompile, or reverse engineer Software. You acknowledge that Software is not designed, licensed or intended for use in the design, construction, operation or maintenance of any nuclear facility. Sun
disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this Agreement.
3. LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90) days from the date of purchase, as evidenced by a copy of the receipt, the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use. Except for the foregoing,
Software is provided "AS IS". Your exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace Software media or refund the fee paid for Software.
4. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
3
5. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES,
HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Sun's liability to you,
whether in contract, tort (including negligence), or otherwise, exceed the amount paid by you for Software under this Agreement. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose.
6. Termination. This Agreement is effective until terminated. You may terminate this Agreement at any time by destroying all copies of Software. This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement. Upon Termination, you
must destroy all copies of Software.
7. Export Regulations. All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other countries. You agree to comply strictly with all such laws and regulations and acknowledge that you have the
responsibility to obtain such licenses to export, re-export, or import as may be required after delivery to you.
8. U.S. Government Restricted Rights. If Software is being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), then the Government's rights in Software and accompanying documentation will be only as set forth in this Agreement;
this is in accordance with 48 CFR 227.7201 through 227.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD acquisitions).
9. Governing Law. Any action related to this Agreement will be governed by California law and controlling U.S. federal law. No choice of law rules of any jurisdiction will apply.
10. Severability. If any provision of this Agreement is held to be unenforceable, this Agreement will remain in effect with the provision omitted, unless omission would frustrate the intent of the parties, in which case this Agreement will immediately terminate.
11. Integration. This Agreement is the entire agreement between you and Sun relating to its subject matter. It supersedes all prior or contemporaneous oral or written communications, proposals, representations and warranties and prevails over any conflicting or additional terms of any quote, order,
acknowledgment, or other communication between the parties relating to its subject matter during the term of this Agreement. No modification of this Agreement will be binding, unless in writing and signed by an authorized representative of each party.
JAVAMAILTM, VERSION 1.3.1

SUPPLEMENTAL LICENSE TERMS
These supplemental license terms ("Supplemental Terms") add to or modify the terms of the Binary Code License Agreement (collectively, the "Agreement"). Capitalized terms not defined in these Supplemental Terms shall have the same meanings ascribed to them in the Agreement. These Supplemental
Terms shall supersede any inconsistent or conflicting terms in the Agreement, or in any license contained within the Software.
1. Software Internal Use and Development License Grant. Subject to the terms and conditions of this Agreement, including, but not limited to Section 3 (Java(TM) Technology Restrictions) of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license to reproduce
internally and use internally the binary form of the Software, complete and unmodified, for the sole purpose of designing, developing and testing your Java applets and applications ("Programs").
2. License to Distribute Software.* Subject to the terms and conditions of this Agreement, including, but not limited to Section 3 (Java (TM) Technology Restrictions) of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable, limited license to reproduce and distribute the Software
in binary code form only, provided that (i) you distribute the Software complete and unmodified and only bundled as part of, and for the sole purpose of running, your Java applets or applications ("Programs"), (ii) the Programs add significant and primary functionality to the Software, (iii) you do not
distribute additional software intended to replace any component(s) of the Software, (iv) you do not remove or alter any proprietary legends or notices contained in the Software, (v) you only distribute the Software subject to a license agreement that protects Sun's interests consistent with the terms
contained in this Agreement, and (vi) you agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results
from the use or distribution of any and all Programs and/or Software.
3. Java Technology Restrictions.* You may not modify the Java Platform Interface ("JPI", identified as classes contained within the "java" package or any subpackages of the "java" package), by creating additional classes within the JPI or otherwise causing the addition to or modification of the classes in
the JPI. In the event that you create an additional class and associated API(s) which (i) extends the functionality of the Java platform, and (ii) is exposed to third party software developers for the purpose of developing additional software which invokes such additional API, you must promptly publish
broadly an accurate specification for such API for free use by all developers. You may not create, or authorize your licensees to create additional classes, interfaces, or subpackages that are in any way identified as "java", "javax", "sun" or similar convention as specified by Sun in any naming convention
designation.
4. Trademarks and Logos. You acknowledge and agree as between you and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, STAROFFICE, STARPORTAL and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, STAROFFICE, STARPORTAL and iPLANET-related
trademarks, service marks, logos and other brand designations ("Sun Marks"), and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to Sun's benefit.
5. Source Code. Software may contain source code that is provided solely for reference purposes pursuant to the terms of this Agreement. Source code may not be redistributed unless expressly provided for in this Agreement.
6. Termination for Infringement. Either party may terminate this Agreement immediately should any Software become, or in either party's opinion be likely to become, the subject of a claim of infringement of any intellectual property right.
For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A
/(LFI#132726/Form ID#011801)/
Jakarta POI
JDK
Sun Microsystems, Inc. Binary Code License Agreement
for the JAVA 2 PLATFORM STANDARD EDITION DEVELOPMENT KIT 5.0
SUN MICROSYSTEMS, INC. ("SUN") IS WILLING TO LICENSE THE SOFTWARE IDENTIFIED BELOW TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS BINARY CODE LICENSE AGREEMENT AND SUPPLEMENTAL
LICENSE TERMS (COLLECTIVELY "AGREEMENT"). PLEASE READ THE AGREEMENT CAREFULLY. BY DOWNLOADING OR INSTALLING THIS SOFTWARE, YOU ACCEPT THE TERMS OF THE AGREEMENT. INDICATE ACCEPTANCE BY SELECTING THE "ACCEPT"
BUTTON AT THE BOTTOM OF THE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY ALL THE TERMS, SELECT THE "DECLINE" BUTTON AT THE BOTTOM OF THE AGREEMENT AND THE DOWNLOAD OR INSTALL PROCESS WILL NOT CONTINUE.
1. DEFINITIONS. "Software" means the identified above in binary form, any other machine readable materials (including, but not limited to, libraries, source files, header files, and data files), any updates or error corrections provided by Sun, and any user manuals, programming guides and other
documentation provided to you by Sun under this Agreement. "Programs" mean Java applets and applications intended to run on the Java 2 Platform Standard Edition (J2SE platform) platform on Java-enabled general purpose desktop computers and servers.
2. LICENSE TO USE. Subject to the terms and conditions of this Agreement, including, but not limited to the Java Technology Restrictions of the Supplemental License Terms, Sun grants you a non-exclusive, non-transferable, limited license without license fees to reproduce and use internally Software
complete and unmodified for the sole purpose of running Programs. Additional licenses for developers and/or publishers are granted in the Supplemental License Terms.
3. RESTRICTIONS. Software is confidential and copyrighted. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. Unless enforcement is prohibited by applicable law, you may not modify, decompile, or reverse engineer Software. You acknowledge that
Licensed Software is not designed or intended for use in the design, construction, operation or maintenance of any nuclear facility. Sun Microsystems, Inc. disclaims any express or implied warranty of fitness for such uses. No right, title or interest in or to any trademark, service mark, logo or trade name
of Sun or its licensors is granted under this Agreement. Additional restrictions for developers and/or publishers licenses are set forth in the Supplemental License Terms.
4. LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90) days from the date of purchase, as evidenced by a copy of the receipt, the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use. Except for the foregoing,
Software is provided "AS IS". Your exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace Software media or refund the fee paid for Software. Any implied warranties on the Software are limited to 90 days. Some states do not allow limitations on duration
of an implied warranty, so the above may not apply to you. This limited warranty gives you specific legal rights. You may have others, which vary from state to state.
5. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
6. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES,
HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Sun's liability to you,
whether in contract, tort (including negligence), or otherwise, exceed the amount paid by you for Software under this Agreement. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose. Some states do not allow the exclusion of incidental or consequential
damages, so some of the terms above may not be applicable to you.
7. TERMINATION. This Agreement is effective until terminated. You may terminate this Agreement at any time by destroying all copies of Software. This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement. Either party may
terminate this Agreement immediately should any Software become, or in either party's opinion be likely to become, the subject of a claim of infringement of any intellectual property right. Upon Termination, you must destroy all copies of Software.
8. EXPORT REGULATIONS. All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other countries. You agree to comply strictly with all such laws and regulations and acknowledge that you have the
responsibility to obtain such licenses to export, re-export, or import as may be required after delivery to you.
9. TRADEMARKS AND LOGOS. You acknowledge and agree as between you and Sun that Sun owns the SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET trademarks and all SUN, SOLARIS, JAVA, JINI, FORTE, and iPLANET-related trademarks, service marks, logos and other brand designations
("Sun Marks"), and you agree to comply with the Sun Trademark and Logo Usage Requirements currently located at http://www.sun.com/policies/trademarks. Any use you make of the Sun Marks inures to Sun's benefit.
10. U.S. GOVERNMENT RESTRICTED RIGHTS. If Software is being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), then the Government's rights in Software and accompanying documentation will be only as set forth in this
Agreement; this is in accordance with 48 CFR 227.7201 through 227.7202-4 (for Department of Defense (DOD) acquisitions) and with 48 CFR 2.101 and 12.212 (for non-DOD acquisitions).
11. GOVERNING LAW. Any action related to this Agreement will be governed by California law and controlling U.S. federal law. No choice of law rules of any jurisdiction will apply.
12. SEVERABILITY. If any provision of this Agreement is held to be unenforceable, this Agreement will remain in effect with the provision omitted, unless omission would frustrate the intent of the parties, in which case this Agreement will immediately terminate.
13. INTEGRATION. This Agreement is the entire agreement between you and Sun relating to its subject matter. It supersedes all prior or contemporaneous oral or written communications, proposals, representations and warranties and prevails over any conflicting or additional terms of any quote, order,
acknowledgment, or other communication between the parties relating to its subject matter during the term of this Agreement. No modification of this Agreement will be binding, unless in writing and signed by an authorized representative of each party.
SUPPLEMENTAL LICENSE TERMS
These Supplemental License Terms add to or modify the terms of the Binary Code License Agreement. Capitalized terms not defined in these Supplemental Terms shall have the same meanings ascribed to them in the Binary Code License Agreement . These Supplemental Terms shall supersede any
inconsistent or conflicting terms in the Binary Code License Agreement, or in any license contained within the Software.
A. Software Internal Use and Development License Grant. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software "README" file, including, but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a
non-exclusive, non-transferable, limited license without fees to reproduce internally and use internally the Software complete and unmodified for the purpose of designing, developing, and testing your Programs.
B. License to Distribute Software. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software README file, including, but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive, non-transferable,
limited license without fees to reproduce and distribute the Software, provided that (i) you distribute the Software complete and unmodified and only bundled as part of, and for the sole purpose of running, your Programs, (ii) the Programs add significant and primary functionality to the Software, (iii) you
do not distribute additional software intended to replace any component(s) of the Software, (iv) you do not remove or alter any proprietary legends or notices contained in the Software, (v) you only distribute the Software subject to a license agreement that protects Sun's interests consistent with the terms
contained in this Agreement, and (vi) you agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results
from the use or distribution of any and all Programs and/or Software.
C. License to Distribute Redistributables. Subject to the terms and conditions of this Agreement and restrictions and exceptions set forth in the Software README file, including but not limited to the Java Technology Restrictions of these Supplemental Terms, Sun grants you a non-exclusive,
non-transferable, limited license without fees to reproduce and distribute those files specifically identified as redistributable in the Software "README" file ("Redistributables") provided that: (i) you distribute the Redistributables complete and unmodified, and only bundled as part of Programs, (ii) the
Programs add significant and primary functionality to the Redistributables, (iii) you do not distribute additional software intended to supersede any component(s) of the Redistributables (unless otherwise specified in the applicable README file), (iv) you do not remove or alter any proprietary legends or
notices contained in or on the Redistributables, (v) you only distribute the Redistributables pursuant to a license agreement that protects Sun's interests consistent with the terms contained in the Agreement, (vi) you agree to defend and indemnify Sun and its licensors from and against any damages, costs,
liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results from the use or distribution of any and all Programs and/or Software.
D. Java Technology Restrictions. You may not create, modify, or change the behavior of, or authorize your licensees to create, modify, or change the behavior of, classes, interfaces, or subpackages that are in any way identified as "java", "javax", "sun" or similar convention as specified by Sun in any
naming convention designation.
E. Distribution by Publishers. This section pertains to your distribution of the Software with your printed book or magazine (as those terms are commonly used in the industry) relating to Java technology ("Publication"). Subject to and conditioned upon your compliance with the restrictions and obligations
contained in the Agreement, in addition to the license granted in Paragraph 1 above, Sun hereby grants to you a non-exclusive, nontransferable limited right to reproduce complete and unmodified copies of the Software on electronic media (the "Media") for the sole purpose of inclusion and distribution
with your Publication(s), subject to the following terms: (i) You may not distribute the Software on a stand-alone basis; it must be distributed with your Publication(s); (ii) You are responsible for downloading the Software from the applicable Sun web site; (iii) You must refer to the Software as JavaTM 2
Platform Standard Edition Development Kit 5.0; (iv) The Software must be reproduced in its entirety and without any modification whatsoever (including, without limitation, the Binary Code License and Supplemental License Terms accompanying the Software and proprietary rights notices contained in
the Software); (v) The Media label shall include the following information: Copyright 2004, Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Sun, Sun Microsystems, the Sun logo, Solaris, Java, the Java Coffee Cup logo, J2SE , and all trademarks and logos based on Java are
trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. This information must be placed on the Media label in such a manner as to only apply to the Sun Software; (vi) You must clearly identify the Software as Sun's product on the Media holder or Media label, and
you may not state or imply that Sun is responsible for any third-party software contained on the Media; (vii) You may not include any third party software on the Media which is intended to be a replacement or substitute for the Software; (viii) You shall indemnify Sun for all damages arising from your
failure to comply with the requirements of this Agreement. In addition, you shall defend, at your expense, any and all claims brought against Sun by third parties, and shall pay all damages awarded by a court of competent jurisdiction, or such settlement amount negotiated by you, arising out of or in
connection with your use, reproduction or distribution of the Software and/or the Publication. Your obligation to provide indemnification under this section shall arise provided that Sun: (i) provides you prompt notice of the claim; (ii) gives you sole control of the defense and settlement of the claim; (iii)
provides you, at your expense, with all available information, assistance and authority to defend; and (iv) has not compromised or settled such claim without your prior written consent; and (ix) You shall provide Sun with a written notice for each Publication; such notice shall include the following
information: (1) title of Publication, (2) author(s), (3) date of Publication, and (4) ISBN or ISSN numbers. Such notice shall be sent to Sun Microsystems, Inc., 4150 Network Circle, M/S USCA12-110, Santa Clara, California 95054, U.S.A , Attention: Contracts Administration.
F. Source Code. Software may contain source code that, unless expressly licensed for other purposes, is provided solely for reference purposes pursuant to the terms of this Agreement. Source code may not be redistributed unless expressly provided for in this Agreement.
G. Third Party Code. Additional copyright notices and license terms applicable to portions of the Software are set forth in the THIRDPARTYLICENSEREADME.txt file. In addition to any terms and conditions of any third party opensource/freeware license identified in the
THIRDPARTYLICENSEREADME.txt file, the disclaimer of warranty and limitation of liability provisions in paragraphs 5 and 6 of the Binary Code License Agreement shall apply to all Software in this distribution.
For inquiries please contact: Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A.
(LFI#141623/Form ID#011801)
DO NOT TRANSLATE OR LOCALIZE.
The following software may be included in this product: CS CodeViewer v1.0;
Use of any of this software is governed by the terms of the license below:
Copyright 1999 by CoolServlets.com.

Any errors or suggested improvements to this class can be reported as instructed on CoolServlets.com. We hope you enjoy this program... your comments will encourage further development!
This software is distributed under the terms of the BSD License. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
Neither name of CoolServlets.com 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 COOLSERVLETS.COM AND CONTRIBUTORS `À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 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."
The following software may be included in this product: Crimson v1.1.1 ; Use of any of this software is governed by the terms of the license below:
The Apache Software License, Version 1.1
Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved.
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 "Crimson" 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 <http://www.apache.org/>.
The following software may be included in this product: Xalan J2;
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.
The following software may be included in this product: NSIS 1.0j; Use of any of this software is governed by the terms of the license below:
Copyright (C) 1999-2000 Nullsoft, Inc.
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute
it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.Justin Frankel justin@nullsoft.com"
Some Portions licensed from IBM are available at: http://oss.software.ibm.com/icu4j/
Portions Copyright Eastman Kodak Company 1992
Lucida is a registered trademark or trademark of Bigelow & Holmes in the U.S. and other countries.
Portions licensed from Taligent, Inc.
The following software may be included in this product:IAIK PKCS Wrapper; Use of any of this software is governed by the terms of the license below:
Copyright (c) 2002 Graz University of Technology. All rights reserved.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:
"This product includes software developed by IAIK of Graz University of Technology."
5
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
4. The names "Graz University of Technology" and "IAIK of Graz University of Technology" must not be used to endorse or promote products derived from this software without prior written permission.
5. Products derived from this software may not be called "IAIK PKCS Wrapper", nor may "IAIK" appear in their name, without prior written permission of Graz University of Technology.
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 LICENSOR 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.
The following software may be included in this product: Document Object Model (DOM) v. Level 3; Use of any of this software is governed by the terms of the license below:
http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231
This work (and included software, documentation such as READMEs, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following
terms and conditions.
Permission to copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including modifications:
1.The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
2.Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the W3C Software Short Notice should be included (hypertext is preferred, text is permitted) within the body of any redistributed or derivative code.
3.Notice of any changes or modifications to the files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)
PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
This formulation of W3C's notice and license became active on December 31 2002.
This version removes the copyright ownership notice such that this license can be used with materials other than those owned by the W3C, reflects that ERCIM is now a host of the W3C, includes references to this specific dated version of the license, and removes the ambiguous grant of "use". Otherwise,
this version is the same as the previous version and is written so as to preserve the Free Software Foundation's assessment of GPL compatibility and OSI's certification under the Open Source Definition. Please see our Copyright FAQ for common questions about using materials from our site, including
specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to site-policy@w3.org.
The following software may be included in this product: Xalan, Xerces; Use of any of this software is governed by the terms of the license below:
Copyright (c) 1999-2003 The Apache Software Foundation. All rights reserved.
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.
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,
The following software may be included in this product: W3C XML Conformance Test Suites v. 20020606; Use of any of this software is governed by the terms of the license below:
Copyright 1994-2002 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/
This W3C work (including software, documents, or other related items) is being provided by the copyright holders under the following license. By obtaining, using and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:
Permission to use, copy, modify, and distribute this software and its documentation, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the software and documentation or portions thereof, including
modifications, that you make:
1. The full text of this NOTICE in a location viewable to users of the redistributed or derivative work.
2. Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, a short notice of the following form (hypertext is preferred, text is permitted) should be used within the body of any redistributed or derivative code: "Copyright [$date-of-software] World Wide Web
Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/"
3. Notice of any changes or modifications to the W3C files, including the date changes were made. (We recommend you provide URIs to the location from which the code is derived.)
PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
This formulation of W3C's notice and license became active on August 14 1998 so as to improve compatibility with GPL. This version ensures that W3C software licensing terms are no more restrictive than GPL and consequently W3C software may be distributed in GPL packages. See the older
formulation for the policy prior to this date. Please see our Copyright FAQ for common questions about using materials from our site, including specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to site-policy@w3.org.
The following software may be included in this product: W3C XML Schema Test Collection v. 1.16.2; Use of any of this software is governed by the terms of the license below:
W3C DOCUMENT NOTICE AND LICENSE
Copyright 1994-2002 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved.
http://www.w3.org/Consortium/Legal/
Public documents on the W3C site are provided by the copyright holders under the following license. The software or Document Type Definitions (DTDs) associated with W3C specifications are governed by the Software Notice. By using and/or copying this document, or the W3C document from which
this statement is linked, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions:
Permission to use, copy, and distribute the contents of this document, or the W3C document from which this statement is linked, in any medium for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the document, or portions thereof, that
you use:
1. A link or URL to the original W3C document.
2. The pre-existing copyright notice of the original author, or if it doesn't exist, a notice of the form: "Copyright [$date-of-document] World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights
Reserved. http://www.w3.org/Consortium/Legal/" (Hypertext is preferred, but a textual representation is permitted.)
3. If it exists, the STATUS of the W3C document.
When space permits, inclusion of the full text of this NOTICE should be provided. We request that authorship attribution be provided in any software, documents, or other items or products that you create pursuant to the implementation of the contents of this document, or any portion thereof.
No right to create modifications or derivatives of W3C documents is granted pursuant to this license. However, if additional requirements (documented in the Copyright FAQ) are satisfied, the right to create modifications or derivatives is sometimes granted by the W3C to individuals complying with those
requirements.
THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER
RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to this document or its contents without specific, written prior permission. Title to copyright in this document will at all times remain with copyright holders.
----------------------------------------------------------------------------
This formulation of W3C's notice and license became active on April 05 1999 so as to account for the treatment of DTDs, schema's and bindings. See the older formulation for the policy prior to this date. Please see our Copyright FAQ for common questions about using materials from our site, including
specific terms and conditions for packages like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed to site-policy@w3.org. webmaster (last updated by reagle on 1999/04/99.)
The following software may be included in this product: Mesa 3-D graphics library v. 5; Use of any of this software is governed by the terms of the license below:
core Mesa code include/GL/gl.h Brian Paul Mesa
GLX driver include/GL/glx.h Brian Paul Mesa
Ext registry include/GL/glext.h SGI SGI Free B
include/GL/glxext.h
Mesa license:
The Mesa distribution consists of several components. Different copyrights and licenses apply to different components. For example, GLUT is copyrighted by Mark Kilgard, some demo programs are copyrighted by SGI, some of the Mesa device drivers are copyrighted by their authors. See below for a list
of Mesa's components and the copyright/license for each.
The core Mesa library is licensed according to the terms of the XFree86 copyright (an MIT-style license). This allows integration with the XFree86/DRI project. Unless otherwise stated, the Mesa source code and documentation is licensed as follows:
Copyright (C) 1999-2003 Brian Paul All Rights Reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT
SHALL BRIAN PAUL BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
SGI Free Software Licence B:
, or is under common control with Recipient. For purposes of this definition, "control" of an entity means (a) the power, direct or indirect, to direct or manage such entity, or (b) ownership of fifty percent (50%) or more of the outstanding shares or beneficial ownership of such entity.
1.12."Recipient Patents" means patent claims Licensable by a Recipient that are infringed by the use or sale of Original Code or any Modifications provided by SGI, or any combination thereof.
1.13."SGI" means Silicon Graphics, Inc.

1.14."SGI Patents" means patent claims Licensable by SGI other than the Licensed Patents.
2.License Grant and Restrictions.
2.1.SGI License Grant. Subject to the terms of this License and any third party intellectual property claims, for the duration of intellectual property protections inherent in the Original Code, SGI hereby grants Recipient a worldwide, royalty-free, non-exclusive license, to do the following: (i) under
copyrights Licensable by SGI, to reproduce, distribute, create derivative
The following software may be included in this product: Byte Code Engineering Library (BCEL) v. 5; Use of any of this software is governed by the terms of the license below:
Apache Software License
Copyright (c) 2001 The Apache Software Foundation. All rights reserved.
4. The names "Apache" and "Apache Software Foundation" and "Apache BCEL" 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", "Apache BCEL", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see <http://www.apache.org/>.
The following software may be included in this product: Regexp, Regular Expression Package v. 1.2; Use of any of this software is governed by the terms of the license below:
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" and "Apache Turbine" 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", "Apache Turbine", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation.
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see http://www.apache.org.
The following software may be included in this product: JLex: A Lexical Analyzer Generator for Java v. 1.2.5; Use of any of this software is governed by the terms of the license below:
JLEX COPYRIGHT NOTICE, LICENSE AND DISCLAIMER.
Copyright 1996-2003 by Elliot Joel Berk and C. Scott Ananian
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both the copyright notice and this permission notice and warranty disclaimer appear in supporting
documentation, and that the name of the authors or their employers not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.
The authors and their employers disclaim all warranties with regard to this software, including all implied warranties of merchantability and fitness. In no event shall the authors or their employers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss
of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of this software.
Java is a trademark of Sun Microsystems, Inc. References to the Java programming language in relation to JLex are not meant to imply that Sun endorses this product.
The following software may be included in this product: SAX v. 2.0.1; Use of any of this software is governed by the terms of the license below:
Copyright Status
SAX is free!
In fact, it's not possible to own a license to SAX, since it's been placed in the public domain.
No Warranty
Because SAX is released to the public domain, there is no warranty for the design or for the software implementation, to the extent permitted by applicable law. Except when otherwise stated in writing the copyright holders and/or other parties provide SAX "as is" without warranty of any kind, either
expressed or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The entire risk as to the quality and performance of SAX is with you.
Should SAX prove defective, you assume the cost of all necessary servicing, repair or correction.
In no event unless required by applicable law or agreed to in writing will any copyright holder, or any other party who may modify and/or redistribute SAX, be liable to you for damages, including any general, special, incidental or consequential damages arising out of the use or inability to use SAX
(including but not limited to loss of data or data being rendered inaccurate or losses sustained by you or third parties or a failure of the SAX to operate with any other programs), even if such holder or other party has been advised of the possibility of such damages.
Copyright Disclaimers
This page includes statements to that effect by David Megginson, who would have been able to claim copyright for the original work.
SAX 1.0
Version 1.0 of the Simple API for XML (SAX), created collectively by the membership of the XML-DEV mailing list, is hereby released into the public domain.
No one owns SAX: you may use it freely in both commercial and non-commercial applications, bundle it with your software distribution, include it on a CD-ROM, list the source code in a book, mirror the documentation at your own web site, or use it in any other way you see fit.
David Megginson, sax@megginson.com 1998-05-11
SAX 2.0
I hereby abandon any property rights to SAX 2.0 (the Simple API for XML), and release all of the SAX 2.0 source code, compiled code, and documentation contained in this distribution into the Public Domain. SAX comes with NO WARRANTY or guarantee of fitness for any purpose.
David Megginson, david@megginson.com
2000-05-05
The following software may be included in this product: Cryptix;
Cryptix General License
Copyright 1995-2003 The Cryptix Foundation Limited. All rights reserved.
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.
THIS SOFTWARE IS PROVIDED BY THE CRYPTIX FOUNDATION LIMITED AND CONTRIBUTORS `À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 CRYPTIX FOUNDATION LIMITED 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.
EXERPT FROM JavaTM 2 Platform Standard Edition Development Kit 5.0 README
You can freely redistribute the J2SE Runtime Environment with your application, according to the terms of the Runtime Environment's license. Once you have developed your application using the JDK, you can ship it with the Runtime Environment so your end-users will have a Java platform on which
to run your software.
Redistribution
--------------------------------------------------------------------------------
NOTE - The license for this software does not allow the redistribution of beta and other pre-release versions.
--------------------------------------------------------------------------------
Subject to the terms and conditions of the Software License Agreement and the obligations, restrictions, and exceptions set forth below, You may reproduce and distribute the Software (and also portions of Software identified below as Redistributable), provided that:
you distribute the Software complete and unmodified and only bundled as part of Your applets and applications ("Programs"),
your Programs add significant and primary functionality to the Software,
your Programs are only intended to run on Java-enabled general purpose desktop computers and servers,
you distribute Software for the sole purpose of running your Programs,
you do not distribute additional software intended to replace any component(s) of the Software,
you do not remove or alter any proprietary legends or notices contained in or on the Software,
you only distribute the Software subject to a license agreement that protects Sun's interests consistent with the terms contained in this Agreement, and
you agree to defend and indemnify Sun and its licensors from and against any damages, costs, liabilities, settlement amounts and/or expenses (including attorneys' fees) incurred in connection with any claim, lawsuit or action by any third party that arises or results from the use or distribution of any and all
Programs and/or Software.
The term "vendors" used here refers to licensees, developers, and independent software vendors (ISVs) who license and distribute the J2SE Development Kit with their programs.
Vendors must follow the terms of the J2SE Development Kit Binary Code License agreement.
Required vs. Optional Files
The files that make up the J2SE Development Kit are divided into two categories: required and optional. Optional files may be excluded from redistributions of the JDK at the vendor's discretion.
7
The following section contains a list of the files and directories that may optionally be omitted from redistributions of the JDK. All files not in these lists of optional files must be included in redistributions of the JDK.
Optional Files and Directories
The following files may be optionally excluded from redistributions. These files are located in the jdk1.5.0_<version> directory, where <version> is the update version number. Solaris and Linux filenames and separators are shown. Windows executables have the ".exe" suffix. Corresponding files with _g
in name can also be excluded.
jre/lib/charsets.jar
Character conversion classes
jre/lib/ext/
sunjce_provider.jar - the SunJCE provider for Java Cryptography APIs
localedata.jar - contains many of the resources needed for non US English locales
ldapsec.jar - contains security features supported by the LDAP service provider
dnsns.jar - for the InetAddress wrapper of JNDI DNS provider
bin/rmid and jre/bin/rmid
Java RMI Activation System Daemon
bin/rmiregistry and jre/bin/rmiregistry
Java Remote Object Registry
bin/tnameserv and jre/bin/tnameserv
Java IDL Name Server
bin/keytool and jre/bin/keytool
Key and Certificate Management Tool
bin/kinit and jre/bin/kinit
Used to obtain and cache Kerberos ticket-granting tickets
bin/klist and jre/bin/klist
Kerberos display entries in credentials cache and keytab
bin/ktab and jre/bin/ktab
Kerberos key table manager
bin/policytool and jre/bin/policytool
Policy File Creation and Management Tool
bin/orbd and jre/bin/orbd
Object Request Broker Daemon
bin/servertool and jre/bin/servertool
Java IDL Server Tool
bin/javaws, jre/bin/javaws, jre/lib/javaws/ and jre/lib/javaws.jar
Java Web Start
src.zip
Archive of source files
Redistributable JDK Files
The limited set of files from the JDK listed below may be included in vendor redistributions of the J2SE Runtime Environment. They cannot be redistributed separately, and must accompany a JRE distribution. All paths are relative to the top-level directory of the JDK.
jre/lib/cmm/PYCC.pf
Color profile. This file is required only if one wishes to convert between the PYCC color space and another color space.
All .ttf font files in the jre/lib/fonts directory.
Note that the LucidaSansRegular.ttf font is already contained in the J2SE Runtime Environment, so there is no need to bring that file over from the JDK.
jre/lib/audio/soundbank.gm
This MIDI soundbank is present in the JDK, but it has been removed from the J2SE Runtime Environment in order to reduce the size of the Runtime Environment's download bundle. However, a soundbank file is necessary for MIDI playback, and therefore the JDK's soundbank.gm file may be included
in redistributions of the Runtime Environment at the vendor's discretion. Several versions of enhanced MIDI soundbanks are available from the Java Sound web site: http://java.sun.com/products/java-media/sound/. These alternative soundbanks may be included in redistributions of the J2SE Runtime
Environment.
The javac bytecode compiler, consisting of the following files:
bin/javac [Solaris(TM) Operating System and Linux]
bin/sparcv9/javac [Solaris Operating System (SPARC(R) Platform Edition)]
bin/amd64/javac [Solaris Operating System (AMD)]
bin/javac.exe [Microsoft Windows]
lib/tools.jar [All platforms]
The Annotation Processing Tool, consisting of the following files:
bin/apt [Solaris(TM) Operating System and Linux]
bin/sparcv9/apt [Solaris Operating System (SPARC(R) Platform Edition)]
bin/amd64/apt [Solaris Operating System (AMD)]
bin/apt.exe [Microsoft Windows]
jre\bin\server\
On Microsoft Windows platforms, the JDK includes both the Java HotSpot Server VM and Java HotSpot Client VM. However, the J2SE Runtime Environment for Microsoft Windows platforms includes only the Java HotSpot Client VM. Those wishing to use the Java HotSpot Server VM with the J2SE
Runtime Environment may copy the JDK's jre\bin\server folder to a bin\server directory in the J2SE Runtime Environment. Software vendors may redistribute the Java HotSpot Server VM with their redistributions of the J2SE Runtime Environment.
Unlimited Strength Java Cryptography Extension
Due to import control restrictions for some countries, the Java Cryptography Extension (JCE) policy files shipped with the J2SE Development Kit and the J2SE Runtime Environment allow strong but limited cryptography to be used. These files are located at
<java-home>/lib/security/local_policy.jar
<java-home>/lib/security/US_export_policy.jar
where <java-home> is the jre directory of the JDK or the top-level directory of the J2SE Runtime Environment.
An unlimited strength version of these files indicating no restrictions on cryptographic strengths is available on the JDK web site for those living in eligible countries. Those living in eligible countries may download the unlimited strength version and replace the strong cryptography jar files with the
unlimited strength files.
jconsole
jconsole.jar
jconsole may be redistributed outside the JDK but only with Sun's JRE.
Endorsed Standards Override Mechanism
An endorsed standard is a Java API defined through a standards process other than the Java Community ProcessSM (JCPSM). Because endorsed standards are defined outside the JCP, it is anticipated that such standards will be revised between releases of the Java 2 Platform. In order to take advantage of
new revisions to endorsed standards, developers and software vendors may use the Endorsed Standards Override Mechanism to provide newer versions of an endorsed standard than those included in the Java 2 Platform as released by Sun Microsystems.
For more information on the Endorsed Standards Override Mechanism, including the list of platform packages that it may be used to override, see
http://java.sun.com/j2se/1.5.0/docs/guide/standards/
Classes in the packages listed on that web page may be replaced only by classes implementing a more recent version of the API as defined by the appropriate standards body.
In addition to the packages listed in the document at the above URL, which are part of the Java 2 Platform Standard Edition (J2SETM) specification, redistributors of Sun's J2SE Reference Implementation are allowed to override classes whose sole purpose is to implement the functionality provided by
public APIs defined in these Endorsed Standards packages. Redistributors may also override classes in the org.w3c.dom.* packages, or other classes whose sole purpose is to implement these APIs.
The cacerts Certificates File
Root CA certificates may be added to or removed from the J2SE certificate file located at <java-home>/lib/security/cacerts. For more information, see The cacerts Certificates File section in the keytool documentation.
Web Pages
For additional information, refer to these Sun Microsystems pages on the World Wide Web:
http://java.sun.com/
The Java Software web site, with the latest information on Java technology, product information, news, and features.
http://java.sun.com/docs
Java Platform Documentation provides access to white papers, the Java Tutorial and other documents.
http://developer.java.sun.com
Developer Services web site. (Free registration required.) Additional technical information, news, and features; user forums; support information, and much more.
http://java.sun.com/products/
Java Technology Products & API
--------------------------------------------------------------------------------
The J2SE Development Kit is a product of Sun MicrosystemsTM, Inc.
Copyright 2005 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A.

JDOM
Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin.
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 <request_AT_jdom_DOT_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 <request_AT_jdom_DOT_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 Jason Hunter <jhunter_AT_jdom_DOT_org> and Brett McLaughlin <brett_AT_jdom_DOT_org>. For more information on the JDOM Project, please see <http://
www.jdom.org/>.
Krypto
Copyright (c) 1997 Stanford University
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 notices and this permission notice appear in all copies of the software and related documentation.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL STANFORD BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE
POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Copyright (C) 1995-1997 Eric Young (eay@mincom.oz.au)

This package is an SSL implementation written by Eric Young (eay@mincom.oz.au). 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@mincom.oz.au).
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.
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
"This product includes cryptographic software written by Eric Young (eay@mincom.oz.au)"
The word 'cryptographic' can be left out if the routines 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@mincom.oz.au)"
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 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.
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.]
OpenLDAP
Public License for 2.3.34
The OpenLDAP Public License
Version 2.8, 17 August 2003
Redistribution and use of this software and associated documentation ("Software"), with or without modification, are permitted provided that the following conditions are met:
1. Redistributions in source form must retain copyright statements and notices,
2. Redistributions in binary form must reproduce applicable copyright statements and notices, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution, and
3. Redistributions must contain a verbatim copy of this document.
The OpenLDAP Foundation may revise this license from time to time. Each revision is distinguished by a version number. You may use this Software under terms of this license revision or under the terms of any subsequent revision of the license.
THIS SOFTWARE IS PROVIDED BY THE OPENLDAP FOUNDATION AND ITS CONTRIBUTORS `À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 OPENLDAP FOUNDATION, ITS CONTRIBUTORS, OR THE AUTHOR(S) OR OWNER(S) OF THE SOFTWARE 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.
The names of the authors and copyright holders must not be used in advertising or otherwise to promote the sale, use or other dealing in this Software without specific, written prior permission. Title to copyright in this Software shall at all times remain with copyright holders.
OpenLDAP is a registered trademark of the OpenLDAP Foundation.
Copyright 1999-2003 The OpenLDAP Foundation, Redwood City, California, USA. All Rights Reserved. Permission to copy and distribute verbatim copies of this document is granted.
OpenSSL
License
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 openssl-core@openssl.org.
OpenSSL License
Copyright (c) 1998-2007 The OpenSSL Project. All rights reserved.
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)
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.
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
"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 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
9
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.
The license 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 license [including the GNU Public License.]
Oracle
*****************************************************************
Oracle Instant client
End user license agreement ("Agreement")
*****************************************************************
MatrixOne Inc., ("MatrixOne") as licensor, has been given the right by Oracle Corporation (Oracle") to distribute the Oracle Instant Client software ("Program(s)") to you, an end user. Each end user hereby agrees: (1) to restrict its use of the Programs to its internal business operations; (2) that it is
prohibited from (a) assigning, giving, or transferring the Programs or an interest in them to another individual or entity (and if it grants a security interest in the Programs, the secured party has no right to use or transfer the Programs); (b) making the Programs available in any manner to any third party for
use in the third party's business operations (unless such access is expressly permitted for the specific program license or materials from the services acquired); and (3) that title to the Programs does not pass to the end user or any other party; (4) that reverse engineering is prohibited (unless required by law
for interoperability), (5) disassembly or decompilation of the Programs are prohibited; (6) duplication of the Programs is prohibited except for a sufficient number of copies of each Program for the end user's licensed use and one copy of each Program media; (7) that, to the extent permitted by applicable
law, liability of Oracle and MatrixOne for any damages, whether direct, indirect, incidental, or consequential, arising from the use of the Programs is disclaimed; (8) at the termination of the Agreement, to discontinue use and destroy or return to MatrixOne all copies of the Programs and documentation;
(9) not to publish any results of benchmark tests run on the Programs; (10) to comply fully with all relevant export laws and regulations of the United States and other applicable export and import laws to assure that neither the Programs, nor any direct product thereof, are exported, directly or indirectly,
in violation of applicable laws and are not used for any purpose prohibited by these laws including, without limitation, nuclear, chemical or biological weapons proliferation; (11) that Oracle is not required to perform any obligations or incur any liability not previously agreed to; (12) to permit MatrixOne
to audit its use of the Programs or to assign such audit right to Oracle; (13) that Oracle is a third party beneficiary of this end user license agreement; (14) that the application of the Uniform Computer Information Transactions Act is excluded.
Disclaimer of Warranty and Exclusive Remedies
THE PROGRAMS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MATRIXONE AND ORACLE FURTHER DISCLAIM ALL WARRANTIES, EXPRESS AND IMPLIED, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT.
IN NO EVENT SHALL MATRIXONE OR ORACLE BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE OR CONSEQUENTIAL DAMAGES, OR DAMAGES FOR LOSS OF PROFITS, REVENUE, DATA OR DATA USE, INCURRED BY YOU OR ANY THIRD PARTY,
WHETHER IN AN ACTION IN CONTRACT OR TORT, EVEN IF MATRIXONE OR ORACLE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. MATRIXONE'S AND ORACLE'S ENTIRE LIABILITY FOR DAMAGES HEREUNDER SHALL IN NO EVENT EXCEED
ONE THOUSAND DOLLARS (U.S. $1,000).
No Technical Support
Oracle and MatrixOne technical support organizations will not provide technical support, phone support, or updates to end users for the Programs licensed under this agreement.
Restricted Rights
For United States government end users, the Programs, including documentation, shall be considered commercial computer software and the following applies:
NOTICE OF RESTRICTED RIGHTS
"Programs delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, programs delivered
subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). Oracle Corporation, 500
Oracle Parkway, Redwood City, CA 94065."
End of Agreement
The end user may terminate this Agreement by destroying all copies of the Programs. MatrixOne and Oracle each have the right to terminate the end user's right to use the Programs if the end user fails to comply with any of the terms of this Agreement, in which case the end user shall destroy all copies
of the Programs.
Relationship Between the Parties
The relationship between the end user and MatrixOne and Oracle is that the end user is licensee, MatrixOne is distributor/licensor and Oracle is licensor. No party will represent that it has any authority to assume or create any obligation, express or implied, on behalf of any other party, nor to represent the
other party as agent, employee, franchisee, or in any other capacity. Nothing in this Agreement shall be construed to limit any party's right to independently develop or distribute software that is functionally similar to the other party's products, so long as proprietary information of the other party is not
included in such software.
Open Source
"Open Source" software - software available without charge for use, modification and distribution - is often licensed under terms that require the user to make the user's modifications to the Open Source software or any software that the user 'combines' with the Open Source software freely available in
source code form. If you as end user use Open Source software in conjunction with the Programs, you must ensure that your use does not: (i) create, or purport to create, obligations of MatrixOne or Oracle with respect to the Oracle Programs; or (ii) grant, or purport to grant, to any third party any rights
to or immunities under intellectual property or proprietary rights in the Oracle Programs. For example, you may not develop a software program using an Oracle Program and an Open Source program where such use results in a program file(s) that contains code from both the Oracle Program and the Open
Source program (including without limitation libraries) if the Open Source program is licensed under a license that requires any "modifications" be made freely available. You also may not combine the Oracle Program with programs licensed under the GNU General Public License ("GPL") in any manner
that could cause, or could be interpreted or asserted to cause, the Oracle Program or any modifications thereto to become subject to the terms of the GPL.
SSLUtils
4. The names "SOAP" 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.
OR SERVICES; LOSS OFUSE, 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
OUTOF 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) 2000, International Business Machines, Inc., http://www.apache.org. For more information on the Apache Software Foundation,
Sun RPC
Sun RPC is a product of Sun Microsystems, Inc. and is provided for unrestricted use provided that this legend is included on all tape media and as a part of the software program in whole or part. Users may copy or modify Sun RPC without charge, but are not authorized to license or distribute it to anyone
else except as part of a product or program developed by the user.
SUN RPC IS PROVIDED AS IS WITH NO WARRANTIES OF ANY KIND INCLUDING THE WARRANTIES OF DESIGN, MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE, OR ARISING FROM A COURSE OF DEALING, USAGE OR TRADE PRACTICE.
Sun RPC is provided with no support and without any obligation on the part of Sun Microsystems, Inc. to assist in its use, correction, modification or enhancement.
SUN MICROSYSTEMS, INC. SHALL HAVE NO LIABILITY WITH RESPECT TO THE INFRINGEMENT OF COPYRIGHTS, TRADE SECRETS OR ANY PATENTS BY SUN RPC OR ANY PART THEREOF.
In no event will Sun Microsystems, Inc. be liable for any lost revenue or profits or other special, indirect and consequential damages, even if Sun has been advised of the possibility of such damages.
Sun Microsystems, Inc.
2550 Garcia Avenue
Mountain View, California 94043
Tcl
This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.
The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose, provided that existing copyright notices are retained in all copies and that this notice is included verbatim in any distributions. No written agreement, license, or royalty fee
is required for any of the authorized uses. Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly indicated on the first page of each file where they apply.
IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY DERIVATIVES
THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS
PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the Government shall have only "Restricted Rights" in the software and related documentation as defined in the Federal Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you are acquiring the
software on behalf of the Department of Defense, the software shall be classified as "Commercial Computer Software" and the Government shall have only "Restricted Rights" as defined in Clause 252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the authors grant the U.S. Government and
others acting in its behalf permission to use and distribute the software in accordance with the terms specified in this license.
Xalan
Xerces
Xerces2

Table of Contents
Chapter 1. Overview .................................................................................................................. 13

Use of General ENOVIA Client Applications................................................................................... 16
Related Documentation .................................................................................................................. 17
Checklist for Setting Up and Configuring Engineering Central ....................................................... 19
Supporting Components .......................................................................................................... 19
Schema Requirements for Successful Login .................................................................................. 22
Chapter 2. Roles ........................................................................................................................ 23

Chapter 3. Setting Up Engineering Central ............................................................................. 27
Setup Tasks .................................................................................................................................... 28
Adding an ECO Implemented Route Template............................................................................... 29
Defining Unit of Measure Conversions ........................................................................................... 30
Setting up Design Responsibility .................................................................................................... 31
Promoting ECOs with Attached Development Part......................................................................... 32
Customizing Mapping File to Add New Subtypes ........................................................................... 33
Disabling the Part Specification Float Relationship Logic............................................................... 34
Browser Settings............................................................................................................................. 35
Email Settings................................................................................................................................. 36
Chapter 4. Configuring With the Properties File..................................................................... 37

Customizing Properties Files.......................................................................................................... 38
Search Properties .................................................................................................................... 38
BOM Properties ....................................................................................................................... 39
Part Where Used Page Properties........................................................................................... 40
ECR/ECO Properties ............................................................................................................... 41
MEP and Placeholder MEP Properties.................................................................................... 43
Find Number Properties........................................................................................................... 44
Reference Designator Properties............................................................................................. 46
Reference Document Properties.............................................................................................. 48
Specification Properties ........................................................................................................... 48
Lifecycle Mass Approval Properties ......................................................................................... 49
Miscellaneous Properties......................................................................................................... 49
Keys for Subtypes ........................................................................................................................... 51
........................................................................................................................................................ 52
Chapter 5. Default Lists for Engineering Change ................................................................... 53

Distribution List ........................................................................................................................ 53
Reviewer List............................................................................................................................ 54
Approval List ............................................................................................................................ 55
Chapter 6. Configuring Using Schema ................................................................................... 57

ECR / ECO Policies ................................................................................................................. 59
Table of Contents 11
Chapter 7. Configurable Objects, Pages, Forms..................................................................... 61
Configurable Automatically-Named Objects ................................................................................... 62
Configurable Pages......................................................................................................................... 63
Configurable Dynamic UI Form Components ................................................................................. 64
Implementing a Configurable UI Form in JSP Applications ..................................................... 64
Implementing a View Mode Form ............................................................................................ 64
Implementing an Edit Mode Form ............................................................................................ 65
Customizing the Part Specification Type......................................................................................... 66
Creating a Type as a Subtype to Part Specification ................................................................. 66
Creating a New Specification Type .......................................................................................... 66
Part Specification Policy States................................................................................................ 67
Customizing Views.......................................................................................................................... 69
Customizing BOM Views.......................................................................................................... 69
Customizing Affected Items View............................................................................................. 69
Chapter 8. Automated Processes............................................................................................. 71

Automation for All Types........................................................................................................... 72
Automation for ECRs................................................................................................................ 72
Automation for ECOs ............................................................................................................... 74
Automation for Parts................................................................................................................. 76
Automation for Drawing Prints.................................................................................................. 82
Automation for CAD Models..................................................................................................... 84
Automation for CAD Drawings ................................................................................................. 85
Automation for Part Specifications ........................................................................................... 86
Automation for ECR Supporting Documents............................................................................ 87
Email Notifications .......................................................................................................................... 88
Notifications Related to Routes................................................................................................ 90
Index ........................................................................................................................ 91

1
Overview
The ENOVIA Engineering Central Administrators Guide describes information the Business
Administrator needs to know that is unique to setting up and configuring Engineering Central.
Much of the information that administrators need is common to all ENOVIA applications. This
common information is described in the ENOVIA Live Collaboration - Business Process
Services - Administrators Guide which is installed as part of ENOVIA Studio Modeling
Platform documentation. It can be found in DOCINSTALLDIR\PDF.
In this section:
Before Reading This Guide
Business Process Services
Application Components
Before Reading This Guide

To perform administrative setup and configuration tasks, you need to understand some or all of the
following:
The concepts, terminology, processes, and procedures in Engineering Central, as described in
the ENOVIA Engineering Central Users Guide.
The concepts, terminology, processes, and procedures of Business Process Services. Refer to
the ENOVIA Live Collaboration - Business Process Services - Application Exchange
Framework Users Guide and ENOVIA Live Collaboration - Business Process Services -
Common Components Users Guide.
13
The concepts, terminology, and processes related to ENOVIA Live Collaboration products,
including Matrix Navigator, Business Modeler, System Manager, and/or Matrix Query
Language (MQL). See the following documents: ENOVIA Live Collaboration - Matrix
Navigator Guide, Studio Modeling Platform - Business Modeler Guide, System Manager
Guide, and MQL Guide.
Published examples in this document, including but not limited to scripts, programs, and related
items, are intended to provide some assistance to customers by example. They are for
demonstration purposes only. It does not imply an obligation for ENOVIA to provide examples for
every published platform, or for every potential permutation of platforms/ products/versions/etc.
Business Process Services

Engineering Central is supported by a database schema called Business Process Services. These
services contain all the administrative objects needed to run Engineering Central and other
ENOVIA products. Business Process Services must be installed before you can install any
ENOVIA product.
The schema defines the object types, relationships, attributes, policies, and rules that govern the
behavior of individual business objects that you create, modify, or manage using Engineering
Central. Examples of such business objects are ECOs, ECRs, Parts, CAD Models, CAD Drawings,
Drawing Prints, Sketches, and Companies.
When you install Engineering Central, the installation program adds programs and business objects
that make the application work with Business Process Services. For example, business objects are
added that automatically name some types of business objects such as Documents, and control
trigger programs that automate business processes. The application also includes JavaServer Pages
(JSPs). JSPs contain the HTML code that builds the applications user interface, and Java code that
dynamically updates page content whenever the page is accessed. These JSPs reside in the
application servers file system.
Each ENOVIA product contains the items listed in this table.
Item For information, refer to:

Web pages used by the applications users The users guide that accompanies the application.
Programs specific to the application To configure programs and for descriptions of utility trigger programs, see
Configuring Using Schema and Triggers in the ENOVIA Live Collaboration
- Business Process Services - Administrators Guide.
For application-specific trigger programs, see the administrators guide that
accompanies the application. The administrators guides are in PDF format and
are located in
ENOVIA_INSTALL\studio\Apps\APP_NAME\VERSION\Doc\pdf
For information on how to call the included JavaBeans in your custom
applications, see the Javadocs located at:
ENOVIA_INSTALL\studio\Apps\APP_NAME\VERSION\Doc\javadoc
Refer to Directories for Shared and Common Components for other details.

Item For information, refer to:

Other administrative objects specific to The administrators guide for the application.
the application, such as formats
Business objects that accomplish For general information on how the objects function and how to configure them,
system-related tasks, such as objects for see Configuring Business Process Services Functions and Configuring Using
automatically-naming objects and for Schema in the ENOVIA Live Collaboration - Business Process Services -
executing trigger programs Administrators Guide.
For a list of the objects included in the application, see the administrators guide
that accompanies the application.
Directories for Shared and Common Components

Some applications, such as ENOVIA Materials Compliance Central, install other components that
may be shared between applications. When this is the case there are 2 directories installed under
ENOVIA_INSTALL\studio\Apps\, one which includes base in the name, such as
MaterialsComplianceBase. These base directories are where the doc directories can be found. For
example c:\enovia\studio\Apps\APP_NAME\VERSION\Doc\pdf
The documentation that describes the common components that are installed with BPS can be
found in the ENOVIA_INSTALL\studio\doc directory.
Chapter 1: Overview 15
Use of General ENOVIA Client Applications
Some of the instructions in this and other administrators guides require the use of a general
Matrix client navigator, such as the:
desktop version of Matrix Navigator (also known as the thick client)
Web version of Matrix Navigator (also known as the thin client, PowerWeb, eMatrixApplet,
and the Web Navigator)
It is important to restrict the use of these general navigator applications to only a few
specially-trained business administrators and to only the purposes described in the ENOVIA Live
Collaboration - Business Process Services - Application Exchange Framework Users Guide and
applications administrators guides. ENOVIA applications run JavaBean code that requires data to
have specific characteristics and conditions. For example, objects may have to have certain
relationships defined, have specific values entered for attributes, be in specific lifecycle states, or be
in particular vaults. When a person works within the ENOVIA product user interface, these data
conditions are met. However, the general Matrix navigators are not necessarily aware of these
conditions and therefore a person working within the general navigators can easily compromise
data integrity.
Another reason to restrict access to the general clients is that certain actions have different results
depending on where the action is taken. A command on a JSP page may include options (such as
additional MQL clauses) to ensure that the operation is completed as the application expects, but a
user in a general client has no guidance on what options should be chosen. For example, when a file
is checked into ENOVIA Live Collaboration using a general client, the store set in the policy is
used; when using an ENOVIA product to check in a file, the person or company default store is
used regardless of the store set by the policy.
The general navigators must or can be used in situations such as:
ENOVIA product features require data that cannot be created within the ENOVIA product user
interface.
For example, some user profile information and template information must be created in a
general navigator.
Automated business rules and processes need to be configured, such as triggers and
autonamers.
Data needs to be investigated for troubleshooting, testing, or data conversion.
The general navigators should only be used in these situations, using the instructions provided in
ENOVIA documentation, and only by specially-trained business administrators. Standard users of
ENOVIA products should never be allowed to work with their data in a general navigator and
external customers should never be given access to a general navigator. Also, using ENOVIA Live
Collaboration Studio Customization Toolkit applications or any programming interface that does
not go through the applications bean layer has the potential to cause undesirable results within the
ENOVIA product data.

Related Documentation
In addition to this administrators guide, refer to the following documentation for information
about Engineering Central and ENOVIA product features in general.
All guides in PDF format require Acrobat Reader to view.
In this section:
Administrator Documentation
User Documentation
Administrator Documentation
Readme
Each version of the application comes with an HTML readme file that contains information
about new features, known issues, and closed issues.
ENOVIA Live Collaboration - Business Process Services - Administrators Guide
This guide is available in PDF format. It is for people in the host company who need to
configure and customize ENOVIA products. It describes the schema that underlies the
applications and how to configure it. The PDF version is located in
ENOVIA_INSTALL\studio\Apps\APP_NAME\VERSION\Doc\pdf.
ENOVIA Live Collaboration - Schema Reference Guide
This guide is available in PDF format. The guide provides a reference for all of the schema that
underlies ENOVIA products. The pdf version is located in
ENOVIA_INSTALL\studio\Apps\APP_NAME\VERSION\Doc\pdf.
Javadoc for BPS
For descriptions of methods in framework packages and classes, see
ENOVIA_INSTALL\studio\Apps\Framework\VERSION\Doc\javadoc
User Documentation
Engineering Central Users Guide and online help
This guide is available in PDF format. It is also available in HTML format as a
context-sensitive online help system. It describes how to use features installed with
Engineering Central. Access this help system by clicking the help button on any Engineering
Central-specific application page.
ENOVIA Live Collaboration - Business Process Services - Application Exchange Framework
Users Guide and online help
context-sensitive online help system. It describes how to use features installed with the
Application Exchange Framework portion of BPS, such as history pages and pages accessed
from the global toolbar. It also explains how to navigate through the user interface, such as how
to use table pages and the Context Navigator. Access this help system by clicking the help
button on any framework-specific application page or clicking AEF Help at the top of any
application help page.
ENOVIA Live Collaboration - Business Process Services - Common Components Users Guide
and online help
common components portion of BPS, such as the common document model. Access this help
system by clicking the help button on any common-specific application page or clicking
Common Components Help at the top of any application help page.
ENOVIA Live Collaboration - Business Process Services - Team Users Guide and online help
context-sensitive online help system. It describes how to use features installed with the Team
portion of BPS, such as routes. Access this help system by clicking the help button on any
team-specific application page.
ENOVIA Live Collaboration - Business Process Services - Metrics Users Guide and online
help
business metrics portion of BPS. Access this help system by clicking the help button on any
metrics-specific application page.

Checklist for Setting Up and Configuring
Engineering Central
To implement Engineering Central, the software components that support it must be installed, set
up, and configured to meet your business processes and environment. These supporting
components include the ENOVIA Live Collaboration applications, the application server,
Business Process Services and Engineering Central.
In this section:
Supporting Components
Supporting Components
The table below contains a list of supporting components that need to be installed and configured
and where to get more information about each.
Software Component Setup or Configuration Option Refer to:

Core technologies, Set up hardware, install and configure ENOVIA ENOVIA Live Collaboration -
application server, ENOVIA Studio Modeling Platform and application server. Installation Guide
Live Collaboration
applications
Business Process Services Define the name of the host company by changing the Defining Your Company section
name of the Company Name business object. of the ENOVIA Live Collaboration
- Business Process Services -
Common Components Users
Guide
Configure and customize Business Process Services. ENOVIA Live Collaboration -
Business Process Services -
Common Components Configure checkin and checkout using properties and ENOVIA Live Collaboration -
URL parameters. Business Process Services -
Administrators Guide and
emxComponents.properties
Configure triggers installed with Common Configuring Automatic Business
Components: Rules (Triggers) section of the
Turn off triggers that you do not want. ENOVIA Live Collaboration -
Change parameters passed to trigger programs, as Business Process Services -
needed. Administrators Guide
Integrations Install third party applications and integrations, such Documentation for the third party
as search engines and 2D and 3D viewer software and software
integrations. Documentation that accompanies
the integrations
Register viewers, define formats, and set up viewer Setting Up 2D and 3D Viewers
preference choices. section of the ENOVIA Live
Collaboration - Business Process
Services - Administrators Guide

Engineering Central Set up features available with default installation: Setting Up Engineering Central in
Define currencies that should be available for Chapter 3
conversion
Define unit of measure conversions
Determine method for defining part
subcomponents or remove category
Determine vaulting strategy and set up company Adding Vaults, Companies, and
vaults in the System Manager application. Users in the ENOVIA Live
In application, add companies, assign vaults, and add Collaboration - Business Process
at least one administrative user per company. Services - Administrators Guide.
Configure pages built using the Business Process For a list of configurable pages,
Services configurable components. see Configurable Pages in
Chapter 7.
For configuration options and
instructions, see the ENOVIA Live
Collaboration - Business Process
Services - Administrators Guide.
Determine whether some objects can be autonamed Configurable
and the autoname prefix to use. Automatically-Named Objects in
Chapter 7
Automated Processes in Chapter 8
Configure Engineering Central schema: Configuring Using Schema in
Modify attributes Chapter 6
Configure policy access
Configure triggers: Automated Processes in Chapter 8
Turn off triggers that you do not want. Configuring Automatic Business
Change parameters passed to trigger programs, Rules (Triggers) section of the
as needed. ENOVIA Live Collaboration -
Change onscreen text for Engineering Central, Changing Onscreen Text and
including internationalized text Internationalizing section of the
ENOVIA Live Collaboration -
Administrators Guide and
emxEngineeringCentralNetString
Resource.properties files
emxComponentsStringResource.p
roperties
emxFrameworkStringResource.pr
operties
Schema Requirements for Successful Login
The system fulfills all schema requirements automatically when companies and employees are
added using the applications Administration pages.
These are the schema requirements needed to successfully access Engineering Central.
To represent the persons company, a business object of type Company is created and promoted
to the Active state.
To represent the person, a person administrative object (Person in Business Modeler) is defined
using default settings for privileges.
Also to represent the person, a business object of type Person is created using the same name
as the administrative object. To log in, the Person business object must be in the Active state.
The Person business object must be connected to the Company business object using the
Employee relationship.
To access the Administration pages, the Person object must be assigned the Organization
Manager role. A Person in this role has access to company administrative features, such as the
ability to add companies and edit the profiles for employees.

2
Roles
This section describes the roles that are available by default for use in Engineering Central.
Additional roles can be added. For details about assigning access for different roles, see the
section Controlling User Access to User Interface Components in the ENOVIA Live
Collaboration - Business Process Services - Administrators Guide.
The following table summarizes the default roles in Engineering Central. The administrative object
for the person must be assigned to the roles that allow access to the tasks the person needs to use.
Though several companies can be assigned from within the ENOVIA products, a user that is added
to an external company (one that is not the host company) does not get access to Engineering
Central roles that derive from Employee.
Role Description
Organization Manager Maintains person and company definitions
Component Engineer Responsible for Manufacturer Equivalent Part maintenance.

Fully defines manufacturer equivalent parts
Edits manufacturer equivalent part details
Adds attachments
Promotes manufacturer equivalent parts to Release state
23
Role Description
Senior Design Engineer Role defined within organization with design responsibility.
Can create ECOs and MECOs
Has read and modify access to BOM in Engineering view and
Common view
Has only read access to BOM in Plant Specific view
Completes the ECR
Creates ECO objects and attaches the ECR to ECO
Assigns Draftsmen and Design Engineers to work on parts and
drawing prints
Promotes the drawing prints, parts, and ECO to the Review
state
Reviews the ECRs that are attached to the ECO and determines
which parts and which drawing prints need to be attached to the
ECO
Creates/revises and attaches objects to the ECO
Fills in Disposition Code and Change Description attributes
Promotes the ECO to the Design Work state
Design Engineer Role defined within organization with design responsibility.
Can create ECOs
Has read and modify access to BOM in Engineering view
Has only read access to BOM in Common view and Plant
Specific view
Works on ECO parts and drawing prints
Performs whatever CAD and Bill of Material work is necessary
for attached parts and drawing prints.
ECR Evaluator Reviews the change description, the supporting documentation,
and all attached parts and drawings
Adds additional information to the ECR and attaches more
supporting documentation
Can also attach additional parts and drawings or even change
some of the existing connections based on knowledge of how
the change is actually likely to be done
Ensures that all part Dispositions are set correctly
ECR Coordinator Assigns an ECR Evaluator
Promotes the ECR to the Evaluate state

Role Description
Senior Manufacturing Role defined within organization with design responsibility and
Engineer organization with manufacturing responsibility.
Can create ECOs and MECOs
Can create ECRs for parts with read access
Has read and modify access to BOM in Common view and
Plant Specific view
In Plant Specific view, can modify BOM only for plants with
manufacturing responsibility of the Manufacturing Engineer
Has only read access to BOM in Engineering view.
Reviews the disposition codes and set the effectivity dates on
the new parts accordingly.
Updates other part attributes like Lead Time and Estimated
Cost while reviewing the ECO.
If the package is not acceptable, demotes the ECO back to the
Design Work state
If the package is acceptable, promotes all drawing prints, parts,
and ECO to their Release states.
Manufacturing Engineer Role defined within organization with manufacturing responsibility.
Can create MCOs.
Can create ECRs for parts with read access
Has read and modify access to BOM in Plant Specific view
In Plant Specific view, can modify BOM only for plants with
manufacturing responsibility of the Manufacturing Engineer
Has read access only to BOM in Engineering view and
Common view.
Sets start date for MCOs and promotes MCOs for review.
Performs all the tasks related to manufacturing parts,
manufacturing bill of material page of part, affected part
revisions, manufacturing responsibility and affected MBOMs
pages of MCO and start date of Edit Attributes page in MCO.
Product Obsolescence Promotes objects to Obsolete.
Manager Demotes objects from Obsolete state back to the Release state.
Corporate Special user in the system, role is used to lock down ECRs, ECOs,
and parts so no additional changes can be made; removes the object
from the engineers desk.
Part Family Coordinator Manages part families, including creating, modifying and
deleting.
Creates ECRs, product lines, and sketches.
Edits details of ECRs, ECOs, product lines, and specifications.
Chapter 2: Roles 25
3
Setting Up Engineering Central
After installing Engineering Central, you will need to perform a few preliminary tasks in order
for all installed features to work correctly when users log in.
In this section:
Setup Tasks
Adding an ECO Implemented Route Template
Defining Unit of Measure Conversions
Setting up Design Responsibility
Promoting ECOs with Attached Development Part
Customizing Mapping File to Add New Subtypes
Disabling the Part Specification Float Relationship Logic
Browser Settings
Email Settings
27
Setup Tasks
These basic tasks describe how to set up Engineering Central to define your host company and
subsidiaries and configure policies for object types that can have multiple policies.
Log in as a user with the Organization Manager role and use the Administration pages to:
Name the host company. Edit the Company business object Company Name and change
the name to reflect the host companys name. (After changing the name, make sure you restart
the Web server before logging into the applications as an employee of the host company.)
Add Business Units and Departments. If you are using business units or departments within
companies, they must be added and connected to the appropriate Company business object.
See Setting up Design Responsibility.
Add Route Template for ECO Implemented. If you will be using the Implemented state for
ECOs, you can define tasks that should be completed before the ECO can be promoted to the
Implemented state, and assign people to complete them. See Adding an ECO Implemented
Route Template.
Configure Policies. Parts, drawing prints, and CAD models can have multiple policies. When
a new part is created, it can be created under the Development Part policy (default) or
Production Release (EC Part) policy.
Default policies can be defined to be used when the data is created in non-interactive functions
such as import or legacy data loading.
Policies can be tagged with a new property called PolicyClassification. This new symbolic
name ensures that Part policies are either classified as Development or Production policies.
All Part policies must have the property PolicyClassification; otherwise, the policies do not work as
desired.
The following MQL command can be used to add the administrative property:
MQL <1> modify policy "<policy name>" add property
"PolicyClassification" value "Production";
The Administrative property PolicyClassification has only three values: Production,
Development, or Other
Example: A new policy name is Development Part and it is a development policy:
MQL <1> modify policy "Development Part" add property
"PolicyClassification" value "Development";

Adding an ECO Implemented Route Template
If you will be using the Implemented state for ECOs, you can define tasks that should be
completed before the ECO can be promoted to the Implemented state, and assign people to
complete them.
The final state of the ECO lifecycle is Implemented, which closes the loop of the change process,
providing verification and visibility that a change, as published by Engineering, has in fact been
implemented in the factories.
When an ECO is promoted from the Review to the Release state, a route is automatically created to
block promotion of the ECO to the Implemented state until the route is complete. The route allows
you to notify or solicit approvals from a group of people. By default, the route has no members and
no tasks, but they can be added to the route in either of the following ways:
You can create and activate a route template named ECO Implemented. If this template is
active in the database, the route that is automatically created when the ECO is promoted to
Release is based on this template, with the members and tasks defined. As the ECO enters the
Release state, the route is started and initial tasks are sent to the appropriate people. This is the
option to choose if there are certain people that should be included in every ECO Implemented
route. Pending route tasks can always be changed by the ECO/route owner, so this method still
retains flexibility concerning who is included in the route and what their task actions will be.
If there is no ECO Implemented route template, the route must be modified manually. When
the ECO is promoted to Release, the ECO owner receives IconMail notification that the route
has been created and must have members and tasks added. This is the option to choose if
different people will often be included in the route.
To create an ECO Implemented route template
1. Create a route template named ECO Implemented. See Creating a Route Template in the
Routes chapter of the ENOVIA Live Collaboration - Business Process Services - Common
Components Users Guide for details.
2. Add members and tasks. For example, you may want to add tasks for project leads to add their
approvals, or tasks with a Notify Only action for the department head or other project
members.
3. Access the route Properties page of the ECO Implemented route and click Activate/Deactivate
to make the route active.
To use the default route
1. From the IconMail notification that a route has been created for the ECO, click the ECO name
to access the category list and Properties page.
2. Click Route from the ECOs category list and click the route name.
3. Click Access from the routes category list to add members. See Routes: Member Access in
the Routes chapter of the ENOVIA Live Collaboration - Business Process Services - Common
4. Click Task from the routes category list to assign tasks. See Defining the Tasks in a Route in
the Routes chapter of the ENOVIA Live Collaboration - Business Process Services - Common
5. Start the route. From the routes Properties page, click Start Route.
Chapter 3: Setting Up Engineering Central 29

Defining Unit of Measure Conversions
The data for some fields shown in Engineering Central is based on a particular unit of measure,
such as weight. The system displays this data based on the unit of measure used by the person
who enters the data. On a page by page basis, users can convert data entered in English units to
Metric units and vice versa. For example, if a user enters weight data using grams, another user
can convert this data to pounds. Each English unit can be converted to only one Metric unit.
To define the conversion rates for English and Metric units, perform these steps for each English
unit that you want users to be able to convert to a Metric unit:
1. In Business Modeler or MQL, add and remove range values for the Unit of Measure attribute
so they include all English and Metric units that you will define conversions for.
2. Using Matrix Navigator or Matrix Web Navigator, create a business object of Type Unit
Conversion. The Name should match the English unit and the Revision should match the
Metric unit. Both units must be added to the range values for the Unit of Measure attribute.
Make sure the object is stored in the eService Administration vault.
3. In the Rate attribute for the Unit Conversion object, enter the conversion rate between the
English and Metric unit.

Setting up Design Responsibility
Design responsibility can be set up to allow any subsidiary, business unit, or department of a host
company to manage parts and items. Employees who are members of an external company
cannot be assigned Engineering Central roles, and therefore external organizations or their child
objects cannot be assigned design responsibility.
For example, suppose a company, XYZ Corp., is developing a part and assigns design
responsibility to the Milford Engineering department within that company. Only users who are
assigned to Milford Engineering who have access to the part in a given stateas defined by the
parts policywill be able to manage the part. Managing consists of modify, connect, disconnect,
promote, and demote actions.
Since the Employee role is given read/show access on parts without any expressions, all employees
of the host company and its subsidiaries/business units/departments will have read/show access.
You can restrict who can view items by removing read/show access from the Employee role and
adding that to the individual roles. This will cause design responsibility expression evaluation for
all actions on the objects including searching for parts, and it can cause a small change in
performance.
Only the owner can change or remove the design responsibility on a part, and only if the part is in
the Preliminary state.
Engineering Central does not check access to the part in the Released state. Therefore, users other
than those who have design responsibility can work with the part, even if the design responsibility
was not removed from the part before it was promoted to Released.
A user assigned to the Company Representative role should set up subsidiaries, business units or
departments that will have design responsibility for a part. For details, see Creating a Company,
Subsidiary, Business Unit, or Department in the ENOVIA Live Collaboration - Business Process
Services - Common Components Users Guide.

Promoting ECOs with Attached Development Part
By default, you cannot promote an ECO to the Review state if a part using the Development
policy is attached. You can modify this behavior using the following procedure:
In Matrix Navigator, open the following business object:

Type = eServiceTriggerProgramParameters
Name = PolicyECOStandardStateDesignWorkPromoteCheck
Revision = CheckPartsInReview
Set the attribute eService Program Argument 7 = Optional

Customizing Mapping File to Add New Subtypes
When you create new subtypes, you must update the mapping file to include the subtype name.
You can also specify icons for the new subtypes. Use the following procedure to update the
mapping file.
1. Stop the application server.

2. Extract the mapping file, emxEngineeringCentralMappingFile.properties, from /WEB-INF/lib/
engineering.jar into the /WEB-INF/classes directory.
3. In the mapping file, add the subtype-to-bean mapping. For example:
If you create a new subtype of drawing called Drawing Print Minor, add the following
line to the mapping file:
type_DrawingPrintMinor=com.matrixone.framework.beans.DrawingPrint
This key is the symbolic name of the new subtype and the value is the bean to use as an
interface to the new subtype.
4. Save the changes to emxEngineeringCentralMappingFile.properties. In addition, replace the
original mapping file in engineering.jar with the updated file, respecting the original path
information.
5. Specify icons for the new subtypes as follows:
a ) In /WEB-INF/classes/emxSystem.properties, add a line such as:
emxFramework.smallIcon.type_DrawingPrintMinor =
iconSmallDrawingPrint.gif
b ) In /WEB-INF/classes/emxEngineeringCentral.properties, add lines such as
type_DrawingPrintMinor.SmallIcon = iconSmallDrawingPrint.gif
type_DrawingPrintMinor.LargeIcon = iconLargeDrawingPrint.gif
6. Restart the application server.

Disabling the Part Specification Float Relationship
Logic
Deleting an object related to a part such as a CAD Model, Drawing Print or CAD Drawing
makes the previous revision of that object related to the part.
Example:
Part PT rev C has CAD Drawing CD rev C related to it with a Part Specification relationship.
Part PT rev D has CAD Drawing CD rev D related to it with a Part Specification relationship.
If CAD Drawing CD rev D is deleted, CAD Drawing CD rev C becomes related to Part PT rev D. It
also stays related to Part PT rev C.
This behavior is invoked by delete override triggers placed on each of the specification types
provided with the Engineering Central application (that is, CAD Drawing, CAD Model, and
Drawing Print types). When any instantiated specification type is deleted, these delete override
triggers call a type-specific Program Parameter object (for example,
TypeCADDrawingDeleteOverride, TypeCADModelDeleteOverride, and
TypeDrawingPrintDeleteOverride) which invokes a program object named
eSerivceCommonTrigDeleteDrawing.tcl. This program object contains logic that performs the
reconnection of a part object to an earlier version of a specification object upon deletion of a later
version.
This behavior can be disabled by setting TypeCADDrawingDeleteOverride,
TypeCADModelDeleteOverride, and TypeDrawingPrintDeleteOverride Program Parameter objects
to the Inactive state from within Matrix Navigator, followed by performing a reload cache within
Engineering Central. Once in the Inactive state, all program logic is ignored and the default part
specification float logic is disabled.

Browser Settings
When dealing with large structure in the Structure Browser, such as when performing Copy
From in the BOM PowerView on large assemblies, a max-script-run-time message may be
displayed.
Follow these steps for each client machine:

For Internet Explorer:
1. Open this key in the registry.
HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Styles
If the Styles key is not present, create a new key that is called Styles.
2. Create a new DWORD value called "MaxScriptStatements" under this key and set the value to
0xFFFFFFFF.
For Mozilla Firefox:
1. Type about:config in the URL and hit enter.
2. Type max_script_run_time in the filter and set this value to 0.

Email Settings
If the email option is enabled, ECO approval requires MX_SMTP_HOST to be configured.
For Windows, add the following to ematrix.ini:

MX_SMTP_HOST=MailName
For UNIX, add the following to the mxEnv.sh under rmi/scripts:
MX_SMTP_HOST=MailName
where MailName is the mail for your company, for example, engmail1.mycompany.net

4
Configuring With the Properties
File
The file called emxEngineeringCentral.properties contains properties that let you configure the
content and appearance of the Engineering Central banner and configure some features. This file
is located in ..\RMI_HOME\distrib\WEB_APPS_NAME\WEB-INF\classes. For details
regarding the properties and values to use, refer to the file, which contains detailed comments
about how to use the properties.
You can also configure the login pages using properties files called emxLogin.properties and
emxSystem.properties, also located in the same path. For information about these files, see the
ENOVIA Live Collaboration - Business Process Services - Administrators Guide.
This feature works for application properties only; it does not work for string resource property
files.
In this section:
Customizing Properties Files
Keys for Subtypes
37
Customizing Properties Files
You can customize many properties as described in this administrators guide. To make sure your
customizations are not overwritten when you install a new version of software, you should place
your custom properties in a separate file instead of editing the existing properties file.
In this section:
Search Properties
BOM Properties
Part Where Used Page Properties
ECR/ECO Properties
MEP and Placeholder MEP Properties
Find Number Properties
Reference Designator Properties
Reference Document Properties
Specification Properties
Lifecycle Mass Approval Properties
Miscellaneous Properties
To create the custom file, copy the properties whose values you want to change to the custom file
and edit as needed. The property name in the custom file must exactly match the property name in
the primary properties file, including case. The file must be stored in the
..\RMI_HOME\distrib\WEB_APPS_NAME\WEB-INF\classes directory, and must have a different
name than the properties file distributed with the software. The file must use the .properties
extension without other periods in the file name, for example, ECcustom.properties.
For performance reasons, you should not copy the entire primary properties file into the custom
file.
The system loads the primary properties file first, then the custom properties file. If your system
includes customized code and applications, the custom properties file can contain additional
key-value pairs that are not included in the primary properties file.
Refer to the Configuring System Properties chapter in the ENOVIA Live Collaboration - Business
Process Services - Administrators Guide for instructions on defining the name of your custom
properties file in the emxSystem.properties file.
Search Properties
Specify search results window actionBy default, the search results window remains open
when the user clicks on a name hyperlink, bringing up the respective navigation tree in the
main window. Set the CloseSearchResultsOnNameClick property to true if you want the
search results window to close automatically after the user clicks a name hyperlink.
# Flag to set the closing of Common Search Results page upon click on
name hyperlink
emxEngineeringCentral.CloseSearchResultsOnNameClick = true

Specify states to ignore for unreleased searchWhen searching for unreleased parts,
generally parts that are in the Release state or greater are not included in the search results. You
can specify additional states to ignore for this search.
emxEngineeringCentral.ReleaseAndGreaterStates=state_Release,state_Obsolete
Specify types for Find Related searchYou can use this property to customize the types to
search on in a Find Related search.
eServiceEngineeringCentral.FindRelatedTypes = type_CADDrawing,\
type_CADModel, \
type_DrawingPrint, \
type_ECO, \
type_ECR, \
type_Markup, \
type_Part, \
type_PartFamily, \
type_ProductLine, \
type_Sketch, \
type_Company, \
type_Organization, \
type_Location
Specify whether FindLike search is case-sensitive or notFind Like search is not

case-sensitive by default. You can make the Find Like search case-sensitive by changing the
following property to true:
emxEngineeringCentral.Search.FindLike.CaseMatchOption = false
BOM Properties
Include Development parts when selecting Show Highest Released and un-Released
RevisionsBy default, the BOM search to connect parts via many relationships finds only
parts that use the EC Part policy when Show Highest Released & un-Released Revisions is
selected as part of the search criteria. To include Development parts, set
emxEngineeringCentral.omitAllRevisions to false. When set to false, it shows another radio
button to show all revisions of the parts and all policies. Development parts show up in this
result.
# Flag for parts BOM find part, determines if All Revisions radio
button is omitted
emxEngineeringCentral.omitAllRevisions = FALSE
Set levels for mass BOM changeWhen selecting assemblies for a mass BOM change, the
level at which the assemblies can be selected is restricted by the
AllowMassEBOMChangeUptoLevel property. Valid values for this are 0,1,2,(any integer).
If the property is set to 0, it implies that there is no restriction and assemblies at any level can
be chosen for a mass BOM change.
emxEngineeringCentral.AllowMassEBOMChangeUptoLevel=3
Chapter 4: Configuring With the Properties File 39

Part Where Used Page Properties
Specify relationships to expand on the part Where Used pageThe page contains show/
hide icons that allow expanding the part to show related items. Change the value of the
PartRelsToExpand property to indicate the list of relationships to be expanded. These
relationships must have the type Part on their from end. The default is Specifications, but
you could choose to expand on BOM, alternate parts, substitutes parts, etc.
emxEngineeringCentral.PartRelsToExpand=relationship_EBOM
Specify how levels are shown on the part Where Used pageThe page shows level
numbers preceded by a minus sign. To show levels with no sign, change the
ShowNegativeInWhereUsed property to false.
emxEngineeringCentral.ShowNegativeInWhereUsed=false
Specify BOM level filter on the part Where Used pageThe default is Upto and a level of
1. Use the DefaultEBOMLevelFilter if you want to change the default. Valid values are
UpTo, All or Highest. If UpTo is specified, you can also specify the level using the
DefaultEBOMLevel property. (This setting is ignored if the default filter is anything other than
UpTo.)
emxEngineeringCentral.DefaultEBOMLevelFilter=UpTo...
emxEngineeringCentral.DefaultEBOMLevel=3
Specify revision filter on the part Where Used page Use the WhereUsedRevFilter if you
want to change the default. Valid values are All, LatestReleased or Last. By default, the
property is configured:
eServiceEngineeringCentral.WhereUsedRevFilter =
emxEngineeringCentral.Part.WhereUsedRevisionLast, \
emxEngineeringCentral.Part.WhereUsedRevisionLatestReleased, \
emxEngineeringCentral.Part.WhereUsedRevisionAll
You can remove any of the entries in this list.
If this list is set to nothing, then the revision filter will default to Latest Released.
Specify revision level on the part Where Used page Use the WhereUsedLevelFilter if you
want to change the default. Valid values are All, UpTo or Highest. By default, the
property is configured:
eServiceEngineeringCentral.WhereUsedLevelFilter =
emxEngineeringCentral.Part.WhereUsedLevelAll, \
emxEngineeringCentral.Part.WhereUsedLevelHighest, \
emxEngineeringCentral.Part.WhereUsedLevelUpTo
You can remove any of the entries in this list.
If this list is set to nothing, then the revision filter will default to UpTo.
Specify products filter on the part Where Used page Use the WhereUsedProductsFilter if
you want to change the default. By default, the property is configured:
eServiceEngineeringCentral.WhereUsedProductsFilter =
emxEngineeringCentral.Part.WhereUsedProductsAll, \
emxEngineeringCentral.Part.WhereUsedProductsNone, \
emxEngineeringCentral.Part.WhereUsedProductsFeatures, \
emxEngineeringCentral.Part.WhereUsedProductsProducts, \
emxEngineeringCentral.Part.WhereUsedProductsBuilds, \
emxEngineeringCentral.Part.WhereUsedProductsProductConfigurations

ECR/ECO Properties
Change the sections included in the ECR Summary ReportBy default, the following
sections are included in the ECR summary report, in addition to basic information. The basic
information section is required, but all other sections are optional. To exclude a section from
the report, set its property to false.
emxEngineeringCentral.ECRSummary.Attributes=true
emxEngineeringCentral.ECRSummary.Approvals=true
emxEngineeringCentral.ECRSummary.Routes=true
emxEngineeringCentral.ECRSummary.Tasks=true
emxEngineeringCentral.ECRSummary.AffectedItems=true
emxEngineeringCentral.ECRSummary.Assignees=true
emxEngineeringCentral.ECRSummary.RelatedECO=true
emxEngineeringCentral.ECRSummary.Markups=true
emxEngineeringCentral.ECRSummary.ReferenceDocuments=true
emxEngineeringCentral.ECRSummary.ResolvedItems=true
** By default, the following sections are NOT included in the ECR summary report. To
include a section in the report, set its property to true.
emxEngineeringCentral.ECRSummary.ObsoleteParts=false
emxEngineeringCentral.ECRSummary.RevisedParts=false
emxEngineeringCentral.ECRSummary.RevisedSpecs=false
emxEngineeringCentral.ECRSummary.SupportingDocuments=false
Change the sections included in the ECO Summary ReportBy default, the following
sections are included in the ECO summary report, in addition to basic information. The basic
information section is required, but all other sections are optional. To exclude a section from
the report, set its property to false.
emxEngineeringCentral.ECOSummary.Attributes=true
emxEngineeringCentral.ECOSummary.Approvals=true
emxEngineeringCentral.ECOSummary.Routes=true
emxEngineeringCentral.ECOSummary.Tasks=true
emxEngineeringCentral.ECOSummary.AffectedItems=true
emxEngineeringCentral.ECOSummary.Assignees=true
emxEngineeringCentral.ECOSummary.RelatedECR=true
emxEngineeringCentral.ECOSummary.Markups=true
emxEngineeringCentral.ECOSummary.ReferenceDocuments=true
emxEngineeringCentral.ECOSummary.ResolvedItems=true
** By default, the following sections are NOT included in the ECO summary report. To
include a section in the report, set its property to true.
emxEngineeringCentral.ECOSummary.NewParts=false
emxEngineeringCentral.ECOSummary.NewSpecs=false
emxEngineeringCentral.ECOSummary.ObsoleteParts=false
emxEngineeringCentral.ECOSummary.RevisedParts=false
emxEngineeringCentral.ECOSummary.RevisedSpecs=false
emxEngineeringCentral.ECOSummary.SupportingDocuments=false
emxEngineeringCentral.ECOSummary.NetBOMComparison=false

Disable ECR/ECO Delegation Notification. Whenever a relationship Assigned Affected
Item is established between the Assigned EC and Affected Item relationships, a trigger is
fired to send a mail notification to the new user indicating the delegation for specific affected
items of an ECR or ECO has taken place and the user is assigned to them.
By default the mail notification is enabled, but it is configurable and can be turned off. To
specify that you do not want new assignees to be automatically notified when someone
delegates assignments to them, change the following to FALSE.
emxEngineeringCentral.IconMail.DelegateAssignment = TRUE
Specify settings for change processes. This setting is used to switch between serial and
parallel change processes. When Check.PartVersion is set to true, the parallel change process is
used: instead of creating a new part revision during the change process, it will create a part
version object that is later inserted in the revision change when the part version is released.
When Check.PartVersion is set to false, the serial change process is used which creates a new
part revision during the change process.
emxEngineeringCentral.Check.PartVersion=TRUE
Specify states for Raise ECR wizardWhen raising an ECR using an existing ECR, the
search includes only ECRs in the states shown in the drop-down list. These states can be
specified using the MassUpdateECRStates property.
emxEngineeringCentral.MassUpdateECRStates=state_Create,state_Submit, state_Evaluate
Specify states for Active ECR or ECOThe part, drawing print, CAD model and CAD
drawing pages indicate if the item has an active ECR or ECO connected. The active ECR must
be in one of the following states (by default): Create, Review, or Plan ECO. The active ECO
must be in one of the following states (by default): Create, Define Components, Design Work,
or Review. The states are controlled by the ActiveECRStates and the ActiveECOStates
properties.
emxEngineeringCentral.ActiveECRStates=state_Create,state_Review,state_PlanECO
emxEngineeringCentral.ActiveECOStates=state_Create,state_DefineComponents,state_Design
Work,state_Review
Specify whether an ECO is required to release manufacturer equivalent partsThe ECO

to Release attribute is shown on manufacturer equivalent part pages only if the following
property is set to true:
emxEngineeringCentral.AllowChangeManagementForManufacturerEquivalentParts=true
The state of the EnsureECOConnected triggers should coincide with the
AllowChangeManagementForManufacturerEquivalentParts flag. If this flag is false then the
EnsureECOConnected triggers for the Preliminary state and Review state for manufacturer
equivalent parts should be Inactive. When this flag is set to true, then the
EnsureECOConnected triggers should be changed to be Active.
Specify the states in which an ECO is allowed to be associated with an ECRBy default,
only ECOs in the Create state can be associated with an ECR. A wizard pops up automatically
when the ECR is promoted to the Plan ECO state and the user can specify search criteria to
search for an existing ECO. If you want to allow the user to select existing ECOs in other the
Create state, specify additional states using the ECOStateList property. For example:
emxEngineeringCentral.ECOStateList=Create,Define Components,Define Work

Specify whether items can be deleted from Cancel ECO pageThe enabling and disabling
of the Delete Selected Items command depends on the following property setting. By default,
the property setting is true and items cannot be deleted in the Cancel ECO dialog. To enable
the Delete Selected command, set this to false.
emxEngineeringCentral.CancelECO.disableDeleteAffectedItems=true
PDF Rendering for Summary ReportsThe following properties are used for PDF
Rendering. If AdLib eXpress is not installed, these properties are not used. If AdLib eXpress is
installed, you must change the RenderPDF property to true if you want the Summary Report -
PDF link to appear in ECR/ECO category lists for users who are assigned the Administration
Manager role.
emxEngineeringCentral.RenderPDF=No
emxEngineeringCentral.PDF.InputFolderPath=C:/AdLib eXpress/input/
emxEngineeringCentral.PDF.OutputFolderPath=C:/AdLib eXpress/Output
emxEngineeringCentral.PDF.SleepInterval=30
emxEngineeringCentral.PDF.SuccessMessage=Rendering Successful
emxEngineeringCentral.PDF.ErrorMessage=Rendition Process Failed
Change the sections included in the ECR/ECO Summary ReportBy default, all sections
listed below are included in the ECR/ECO summary report, in addition to basic information.
The basic information section is required, but all other sections are optional. To exclude a
section from the report, set its property to false.
emxEngineeringCentral.ECRSummary.Routes=true
emxEngineeringCentral.ECRSummary.Tasks=true
emxEngineeringCentral.ECRSummary.Approvals=true
emxEngineeringCentral.ECRSummary.SupportingDocuments=true
emxEngineeringCentral.ECRSummary.ImpactAnalysis=true
emxEngineeringCentral.ECRSummary.TestCase=true
emxEngineeringCentral.ECRSummary.TestExecution=true
emxEngineeringCentral.ECRSummary.RelatedECO=true
emxEngineeringCentral.ECRSummary.EBOMMarkups=true
emxEngineeringCentral.ECRSummary.AffectedItems=true
emxEngineeringCentral.ECRSummary.Assignees=true
emxEngineeringCentral.ECRSummary.ResolvedItems=true
emxEngineeringCentral.ECRSummary.ImplementedItems=true
emxEngineeringCentral.ECRSummary.RelatedECR=true
MEP and Placeholder MEP Properties

It is a common practice in the manufacturing industry to give the same part name to Manufacturer
Equivalent Parts (MEPs) from different manufacturers. In Engineering Central, a MEP is unique
because it has a unique identifier for the revision. Therefore you can create MEPs with the same
part name but a different revision.
The revision identifier can be:
The manufacturers Company ID (the default)
The manufacturers Cage Code
A revision specified by the policy governing the MEP

Engineering Central uses the revision identifier in combination with the MEP name and type to
determine if a MEP is unique.
As Engineering Central Administrator, you can use property settings to:
Specify the revision identifier that makes a MEP uniqueTo specify the kind of revision
identifier that makes a MEP unique, set the
emxEngineeringCentral.MEP.UniquenessIdentifier property. The values can
be:
Company ID (the default). This value sets the manufacturer Company ID as the unique
revision identifier. When users create or edit a MEP, the Revision field shows the
Company ID. If a user changes the Manufacturer, Engineering Central changes the
revision identifier to match.
Cage Code. This value sets the manufacturer Cage Code as the unique revision identifier.
When users create or edit a MEP, the Revision field shows the Cage Code. If a user
changes the Manufacturer, Engineering Central changes the revision identifier to match.
Policy. This value sets the revision sequence specified by the policy governing the MEP as
the unique revision identifier. When users create or edit a MEP, the dialog shows the first
value of that revision sequence specified by the policy.
Specify that the manufacturers Cage Code be uniqueTo specify that the Cage Code be
unique, set the following property to true. (The default value is false.)
emxComponents.cageCode.Uniqueness=true
The Create New Company dialog and the Edit Company Details dialog show the Cage Code
field as a required field. If you change the manufacturer, changes the revision accordingly
Allow users to edit the identifier in the Revision fieldTo allow users to edit the default
identifier in the Revision field when they create or edit a MEP, set the following property to
true. (The default value is false.)
emxEngineeringCentral.MEP.allowCustomRevisions=true
Specify how a Placeholder MEP is displayed in Equivalents listIn a parts Equivalents
list, the Name column for a Placeholder MEP can be blank or display a default value, for
example, TEMP.
To show a blank for the Placeholder MEPs name, set the following property to true:
emxEngineeringCentral.EngrPlaceholderMEP.ShowBlankName=true
To specify a value for the Name of the Placeholder MEP object, set the ShowBlankName
property to false and specify a value for the
emxEngineeringCentral.EngrPlaceholderMEP.DefaultName property. For example:
emxEngineeringCentral.EngrPlaceholderMEP.ShowBlankName=false
emxEngineeringCentral.EngrPlaceholderMEP.DefaultName=TEMP
Find Number Properties

A Find Number is used on a Bill of Materials (BOM) as an identifier for a component. As business
administrator, you can use property settings to specify the format of the Find Number and whether
it must be unique. You can also specify whether the Find Number is a required field.
Either a Find Number or a Reference Designator is required. If both are set to not required, the
system defaults to Find Number required. This setting is independent from the uniqueness setting.
If uniqueness is set for Find Number or Reference Designator, then if a value is entered it must be
unique compared to all other values. A blank is not considered a value and is allowed if the attribute
is not required.

To specify that the Find Number be uniqueTo specify whether the Find Number must be a
unique value, use the FindNumber.Unique global property. This setting applies to all parts
regardless of type. The default value for this property is true:
emxEngineeringCentral.FindNumber.Unique=true
If this property is set to true, Engineering Central dialogs in which users enter or edit the Find
Number validate the Find Number for uniqueness within the assembly. In addition, the Find
Number value is case sensitive.
You must set either the FindNumber.Unique property or the ReferenceDesignator.Unique
property to true. (The Engineering Central installation sets both properties to true by default.)
When Engineering Central is installed alone, if both properties are set to false, Engineering
Central behaves as if the Find Number is unique.
When X-BOM Manufacturing is also installed, you must set at least one of the properties to be
unique in order to use the actions available in BOM Common View.
To specify that both the Find Number and Reference Designator be uniqueTo specify
whether both the Find Number and Reference Designator must be unique values, use the
EBOMUniquenessOperator property. Engineering Central uses the
EBOMUniquenessOperator property when both the FindNumber.unique property and the
ReferenceDesignator.Unique properties are set to true. (The Engineering Central installation
sets both properties to true by default.)
The default value for this global property is or.
emxEngineeringCentral.EBOMUniquenessOperator=or
To require that both Find Number and Reference Designator be unique, set the
EBOMUniquenessOperator to and.
If the EBOMUniquenessOperator property is set to or, users can enter either the Find Number
or the Reference Designator. In either case, the value must be unique.
If the EBOMUniquenessOperator property is set to and, users must enter both the Find
Number and the Reference Designator and both values must be unique.
To specify fixed or variable length for the Find Number attribute in the BOMUse the
FindNumberLength property to specify whether the Find Number has a fixed length or variable
length, By default this global property is set to 0, specifying that the length can vary:
emxEngineeringCentral.FindNumberLength=0
To specify a fixed length for the Find Number, set the FindNumberLength property to a
positive integer value. When you specify a FindNumberLength greater than 0 and a
FindNumberDisplayLeadingZeroes of true, Engineering Central uses the two settings to
determine how to display an integer Find Number value.
To specify the display of leading zeroes in the Find NumberTo specify whether the
display of the Find Number shows leading zeroes, use the FindNumber.Unique property. This
setting applies to all parts regardless of type. The default value for this global property is false:
emxEngineeringCentral.FindNumberDisplayLeadingZeroes=false
To specify that display of the Find Number shows leading zeroes, set the property to true.
Engineering Central applies this setting only when the FindNumberLength property is greater
than 0 and the Find Number value is an integer. For example, suppose you set the
FindNumberDisplayLeadingZeroes property to true and set the FindNumberLength to 8, If the
Find Number value is 10, Engineering Central displays the Find Number as 00000010.
If the FindNumberLength property is not greater than 0 or the Find Number value is not an
integer, the FindNumberDisplayLeadingZeroes defaults to false.

Engineering Central uses the Find Number together with the
FindNumberDisplayLeadingZeroes property setting to determine how to sort values in the
Find Number column. If the Find Number is a number, Engineering Central sorts values
numerically. If the Find Number value is alphanumeric, Engineering Central sorts values
alphabetically.
To specify that the Find Number field is a required fieldTo specify whether the Find
Number is required, use the FindNumberRequired property. You can specify this property
according to major part type (Part, Electrical Part, or Mechanical Part). The default settings
are:
type_Part.FindNumberRequired=true
type_ElectricalPart.FindNumberRequired=false
type_MechanicalPart.FindNumberRequired=true
If this property is set to true, when users enter or edit a Find Number, Engineering Central
validates the Find Number based on the FindNumberRequired setting for the part being added
or edited.
If you add a type that needs a different setting, you must define properties for that type. The
format is: symbolic name for the type, followed by the property setting. For example:
type_ResistorPart.FindNumberRequired=true
If a setting is not defined for a subtype, Engineering Central looks for a setting for the parent
type. If no setting for the parent type is defined, Engineering Central looks up the type
hierarchy until it finds a setting.
If either the FindNumberUnique or ReferenceDesignatorUnique global property setting is set
to true (but not both), Engineering Central shows that value as a required field, regardless of
the settings for type_Part, type_ElectricalPart, or type_MechanicalPart.
If this property is set to true, when users enter or edit a Find Number, Engineering Central
validates the Find Number based on the ReferenceDesignatorRequired setting.
Reference Designator Properties

A Reference Designator is used on a Bill of Materials (BOM) as an identifier for a component. As
business administrator, you can use property settings to specify the format of the Reference
Designator and whether it must be unique. You can also specify whether the Reference Designator
is a required field.
Either a Find Number or a Reference Designator is required. If both are set to not required, the
system defaults to Find Number required. This setting is independent from the uniqueness setting.
If uniqueness is set for Find Number or Reference Designator, then if a value is entered it must be
unique compared to all other values. A blank is not considered a value and is allowed if the attribute
is not required.
To specify the Reference Designator be unique. To specify whether or not the Reference
Designator must be a unique value, use the ReferenceDesignator.Unique global property. This
setting applies to all parts, regardless of type. The default value for this property is true:
emxEngineeringCentral.ReferenceDesignator.Unique=true
If this property is set to true, Engineering Central dialogs in which users enter or edit the
Reference Designator validate the Reference Designator for uniqueness within the assembly.
In addition, the Reference Designator value is case sensitive.
You must set either the FindNumber.Unique property or the ReferenceDesignator.Unique
property to true. (The Engineering Central installation sets both properties to true by default.)
When Engineering Central is installed alone, if both properties are set to false, Engineering
Central behaves as if the Find Number is unique.

When X-BOM Manufacturing is also installed, you must set at least one of the properties to be
unique in order to use the actions available in BOM Common View.
To specify that both the Find Number and Reference Designator be unique. To specify
whether or not both the Find Number and Reference Designator must be unique values, use the
EBOMUniquenessOperator property. Engineering Central uses the
EBOMUniquenessOperator property when both the FindNumber.Unique property and the
ReferenceDesignator.Unique property are set to true. The Engineering Central installation sets
both properties to true by default.
The default value for this global property is or.
emxEngineeringCentral.EBOMUniquenessOperator=or
To require that both Find Number and Reference Designator be unique, set the
EBOMUniquenessOperator to and.
If the EBOMUniquenessOperator property is set to or, users can enter either the Find Number
or the Reference Designator. In either case, the value must be unique.
If the EBOMUniquenessOperator property is set to and, users must enter both the Find
Number and the Reference Designator and both values must be unique.
To specify fixed or variable length for the Reference Designator attribute in the EBOM.
Use the ReferenceDesignatorLength property to specify whether the Reference Designator has
a fixed length or variable length, By default this global property is set to 0, specifying that the
length can vary:
emxEngineeringCentral.ReferenceDesignatorLength=0
To specify a fixed length for the Reference Designator, set the ReferenceDesignatorLength
property to a positive integer value. For example, the following setting specifies that the
Reference Designator must be 8 characters or less:
emxEngineeringCentral.ReferenceDesignatorLength=8
To specify that the Reference Designator field is a required field. To specify whether or not
the Reference Designator is required, use the ReferenceDesignatorRequired property. You can
specify this property according to major part type (Part, Electrical Part, or Mechanical Part).
The default settings are:
type_Part.ReferenceDesignatorRequired=true
type_ElectricalPart.ReferenceDesignatorRequired=true
type_MechanicalPart.ReferenceDesignatorRequired=false
If this property is set to true, when users enter or edit a Reference Designator, Engineering
Central validates the Reference Designator based on the ReferenceDesignatorRequired setting
for the part being added or edited.
If you add a type that needs a different setting, you must define properties for that type. The
format is: symbolic name for the type, followed by the property setting. For example:
type_ResistorPart.ReferenceDesignatorRequired=true
If a setting is not defined for a subtype, Engineering Central looks for a setting for the parent
type. If no setting for the parent type is defined, Engineering Central looks up the type
hierarchy until it finds a setting.
If either the FindNumberUnique or ReferenceDesignatorUnique global property setting is set
to true (but not both), Engineering Central shows that value as a required field, regardless of
the settings for type_Part, type_ElectricalPart, or type_MechanicalPart.
To specify the separator for Reference Designator values. Engineering Central users can
specify a Reference Designator as a single value, a group of values delimited by a separator, or
a range of values. As business administrator, you can specify the separator for delimited values
and the separator for a range of values.

To define the separator used to delimit Reference Designator values, use the
DelimitedReferenceDesignatorSeparator property setting: The default setting is a comma
(,):
emxEngineeringCentral.DelimitedReferenceDesignatorSeparator=,
For example, if you have 3 instances of the same part that you want to identify in one
BOM record, you can specify the Reference Designator as R1,R2,R3. This action creates
only one EBOM relationship and defines the Reference Designator attribute with the
string value of R1,R2,R3.
To define the separator for a range of Reference Designator values, use the
RangeReferenceDesignatorSeparator property setting: The default setting is a hyphen (-):
emxEngineeringCentral.RangeReferenceDesignatorSeparator=-
Reference Document Properties

You can specify properties that identify which object types are reference documents.
To specify the list of types that con be connected as Reference Documents. The Reference
Document relationship is used for regulatory or internal business requirements. Use the
ReferenceDocumentTypes property to define which object types can be used as reference
documents.
eServiceEngineeringCentral.ReferenceDocumentTypes=type_DOCUMENTS
Specification Properties
To specify the types that do not require a checked-in file. When a CAD object is promoted
to the Review state, no check is performed to ensure a file is present. However, when the
associated part object is promoted to Review, a check is run to make sure that there is an
attached CAD object and that the object has at least one file checked into it. This property
allows you to skip the check for certain specification types that can be promoted. This setting
will be empty by default. Specification types included in this setting will skip the check for a
checked-in file.
emxEngineeringCentral.PartSpecification.NoFileRequiredTypes
Specification Type Properties. For each specification type in Engineering Central, the
emxEngineeringCentral.properties file contains a property that defines the base
type of the object. The file contains these definitions:
type_CADDrawing.BaseTypeObjectGenerator = type_CADDrawing
type_CADModel.BaseTypeObjectGenerator = type_CADModel
type_PartSpecification.BaseTypeObjectGenerator = type_PartSpecification
type_DrawingPrint.BaseTypeObjectGenerator = type_DrawingPrint
type_ECADModel.BaseTypeObjectGenerator = type_CADModel
type_MCADModel.BaseTypeObjectGenerator = type_CADModel
type_MCADAssembly.BaseTypeObjectGenerator = type_CADModel
type_MCADAssemblyInstance.BaseTypeObjectGenerator = type_CADModel
type_MCADComponent.BaseTypeObjectGenerator = type_CADModel
type_MCADComponentInstance.BaseTypeObjectGenerator = type_CADModel
type_MCADParameterizedAssemblyModel.BaseTypeObjectGenerator = type_CADModel
type_MCADParameterizedComponentModel.BaseTypeObjectGenerator = type_CADModel
type_MCADParameterizedModel.BaseTypeObjectGenerator = type_CADModel

type_Sketch.BaseTypeObjectGenerator = type_Sketch
type_Markup.BaseTypeObjectGenerator = type_Markup
Engineering Central uses these definitions in autonaming to get the base type of a subtype to
determine which object generator to use. If the base types setting for SubTypeObjectGenerator =
true, then Engineering Central uses it to generate the new object. Otherwise, Engineering Central
uses the base type object generator to generate an object of that type. For details, see Configurable
Automatically-Named Objects in Chapter 7.
If you create a new specification subtype, you must define a base type generator property for it in
the properties file. For example, if you create a new specification subtype, XCADModel, derived
from CADModel, you would add this property to the properties file:
type_XCADModel.BaseTypeObjectGenerator = type_CADModel
When users create a specification of the XCADModel type, Engineering Central uses the
CADModel object type generator to create the object.
Lifecycle Mass Approval Properties

The Lifecycle page for an object can be configured to display tasks and signature requirements for
related objects. As installed, the Lifecycle page only shows the tasks and signature requirements for
the selected object. To include related objects in the list, you need to add these properties to the
emxSystem.properties file.
LifecycleMassApproval.<type>.RelatedObjects.Connections=<relationship>
LifecycleMassApproval.<type>.RelatedObjects.ConnectionDirection=
<direction>
where:
<type> is the symbolic name of the object for which you also want to include related objects
<relationship> is a comma-separated list of symbolic names of relationships
<direction> is one of these options:
to
from
both
For example:
LifecycleMassApproval.type_ECO.RelatedObjects.Connections=
relationship_AffectedItems
LifecycleMassApproval.type_Book.RelatedObjects.ConnectionDirection=to
This example would show all tasks/signature requirements necessary for the ECOs affected items.
See the AEF Help to see how lifecycle mass approval works.
Miscellaneous Properties
Enable Part Series. If enabled, users can create and manage part series from the Masters page.
The Masters page is accessible from the part family category list. Also, the part family part list
includes columns to indicate whether a part is in a series and whether it is a master or reference
part and filters to limit the list. If disabled, all user interface features related to part series are
inaccessible to users.

By default part series is disabled, but it is configurable and can be turned on. To specify that
you want part series functionality, change the following to TRUE.
emxEngineeringCentral.PartSeries.PartSeriesActive=TRUE
Restrict removing/adding parts under Related Parts category of Specification. Parts that
are allowed to be added/deleted is determined based on states included in the following
property:
emxEngineeringCentral.Part.RestrictSpecConnectStates =
state_Review,state_Approved,state_Release,state_Obsolete
An error is shown listing the non-removable parts selected.
Set default time for Effectivity Report. This property defines the default time shown on the
Set Date page when creating an Effectivity Report.
emxEngineeringCentral.DefaultEffectivityTime=12:00 AM
Specify the list of state-policy pairs to be considered frozen. By default, only production
parts in the Release state and development parts in the Complete state can be connected to a
BOM. Use the EBOMFrozenStates property to change the allowed states.
emxEngineeringCentral.EBOMFrozenStates =
policy_ECPart,state_Release,policy_DevelopmentPart,state_Complete
Specify whether the part policy can be changed. By default, part policies can be changed
when the part is revised or edited, depending on the users role and change policy access.
Engineering Central allows only the following changes:
Users can change the policy of an EC part only to another policy that is classified as a
Production policy.
Users can change the policy of a Development part only to another policy that is classified
as a Development Policy.
Users can change the policy of a Manufacturer Equivalent Part (MEP) only to another
policy that is classified as an Equivalent policy.
Users can change a Development part to an EC part only by using the Go To Production
action to revise the part from the development process into a production release process.
To prevent all policy changes, set the following property to false:
emxEngineeringCentral.Policy.EnablePartPolicyEditing = true
Create one vault per company. A vault is a container for business objects created within
ENOVIA products. When the VaultAwareness property is TRUE, there must be a unique vault
created for each company that is added to Engineering Central. This vault must be specified
when a company is added to the application using the New Company page. The application
will not accept a vault that already contains a Company business object. For more information
about vaulting, see Adding Vaults, Companies, and Users in the ENOVIA Live Collaboration
- Business Process Services - Common Components Users Guide.
If VaultAwareness is TRUE, there is one vault for each company and all objects are stored in
this vault. The Vault Name list is not available when adding companies.
If VaultAwareness is FALSE, then there is no requirement for one vault per company. It allows
all vaults in the system to be searched. This may cause unnecessary performance and security
issues, and is not recommended.
eServiceEngineeringCentral.VaultAwareness=true

Keys for Subtypes
When working with subtypes of parts, you must add keys to the properties file to load the
required JSP for the Create New Revision page for the subtype.
1. Create new subtypes according to the instructions in the ENOVIA Live Collaboration -
Business Process Services - Administrators Guide.
2. Stop the application server.
3. Open the emxEngineeringCentral.properties file.
4. In the properties file, add the key for the JSP. For example:
If you create a new subtype of Part called Aluminium Part, add the following line to the
properties file:
type_AluminiumPart.ReviseDialog =
emxpartCreatePartRevisionDialogFS.jsp.
This key is used to load the required JSP for the revision of the new subtype and the value is
used as an interface to the new subtype.
5. Save the changes to emxEngineeringCentral.properties.
6. Restart the application server.
7. Register the Admin Type under My Desk->Admin Tools->Property Registration->Admin
Type.
This calls the revision page (emxpartCreatePartRevisionDialogFS.jsp) for the new custom
type, once it is created and registered by the administrator.

5
Default Lists for Engineering
Change
The engineering change process uses member lists and route templates for reviews, approvals,
and notifications. This reflects changes in ECR and ECO policies as of version V6R2009.
Distribution List
A distribution list is a member list used for notifications. The ECR and ECO processes use
distribution lists as a means to notify users of process changes. The distribution list is assigned on
create of the ECR or ECO and can be edited from the Edit dialogs.
When an ECR with a route-based policy is promoted from the Review to Plan ECO state, all
members of all attached distribution lists are automatically notified that the ECR is being promoted.
No duplicate notifications are sent if a person is a member of multiple lists and no notification is
sent to the user who promotes the ECR.
The distribution list is not seen or used by an ECR with an old (signature-based) policy since the
old product lines change board members are used for notifications.
When an ECO with a route-based policy is promoted from the Review to Release state, all members
of all attached distribution lists are automatically notified that the ECO is being promoted. No
duplicate notifications are sent if a person is a member of multiple lists and no notification is sent to
the user who promotes the ECO.
There is also a trigger configured to notify the originator. This trigger is added on the same states
where the members of the distribution list are notified. The trigger is active by default, but can be
turned off if desired.
53
The distribution list is not seen or used by an ECO with an old (signature-based) policy.
Reviewer List
A reviewer list is a route template with a base purpose of Review that defines the list of people who
should review the ECR or ECO before it is promoted to a specified state. The route template, which
will be used for creating the reviewer route, is connected to the ECR or ECO. This replaces the
signatures used in the old policy. The reviewer list can be assigned when the ECR or ECO is created
and can be edited from the Edit dialogs.
When an ECR with a route-based policy is promoted from the Evaluate to Review state, a trigger
fires to automatically create a route using the reviewer list route template. This route is placed
between the Review and Plan ECO states and is a state-blocking route, which means that all tasks
must be completed before the ECR can be promoted to Plan ECO. The route template that is used
here must have a Route Base Purpose of Review, but the route that is created from the template
must have a Route Base Purpose of Standard. This allows the tasks to have an action of either
Approve or Reject, among others. The route must also have a Route Completion Action of
Promote Connected Object. When the last signature is approved, the ECR is promoted to the Plan
ECO state.
When an ECO with a route-based policy is promoted from the Define Components to Design Work
state, a trigger fires to automatically create a route using the reviewer list route template. This route
is placed between the Design Work and Review states and is a state-blocking route, which means
that all tasks must be completed before the ECO can be promoted to Review. The route template
that is used here must have a Route Base Purpose of Review, but the route that is created from the
template must have a Route Base Purpose of Standard. This allows the tasks to have an action of
either Approve or Reject, among others. The route must also have a Route Completion Action of
Notify Route Owner.
The Reviewer List is not seen or used by an ECR or ECO with an old (signature-based) policy since
signatures are used for reviews.
Default Reviewer Route Templates

The table below describes recommended default reviewer route templates for ECRs and ECOs.
Template Route Route Base Task Edit Description

Name Instructions Purpose Setting
ECO Review The ECO needs Review Extend Task This Route Template is used to create the Route
review List placed between the Define Work and Review
states on the ECO.
ECR Review The ECR needs Review Extend Task This Route Template is used to create the Route
review List placed between the Review and Plan ECO states
on the ECR.
The template should have Enterprise Availability and be connected to Company Company Name.
The scope of the template is the Change Responsibility organization. The Route Base Purpose is
Review. The default route template should have a Task Edit Setting of Extend Task List so
that mandatory tasks cannot be removed, but additional ones can be added.

The ECO Review template should have the following role-based task.
Task Name Route Task Approvers Comments Instructions Route Seq

User Responsibility Action
RT-SDE role_SeniorDes Engineering This change Need your Comment 1
ignEngineer requires your approval.
approval.
The ECR Review template should have the following role-based tasks.
Task Name Route Task Approvers Comments Instructions Route

User Responsibility Action Seq
RT-SDE role_SeniorDes Engineering This change Need your Comment 1
ignEngineer requires your approval.
approval.
RT-SME role_SeniorMa Manufacturing This change Need your Comment 1
nufacturingEng requires your approval.
ineer approval.
RT-Chairman role_ECRChair Engineering This change Need your Comment 2
man requires your approval.
approval.
Approval List
An approval list is a route template with a base purpose of Approve that defines the list of people
that must sign or approve an ECR or ECO before it is promoted to a specified state. The approval
list can be assigned when the ECR or ECO is created and can be edited from the Edit dialogs.
When an ECO with a route-based policy is promoted from the Define Components to the Design
Work state, a trigger fires to automatically create a route using the approval list route template with
a Route Base State of Design Work. This route is placed between the Design Work and Review
states and is a state-blocking route, which means that all tasks must be completed before the ECO
can be promoted to Review.
When the ECO is promoted from the Design Work to Review state, a trigger fires to create a route
using the approval list route template with a Route Base State of Review. This route is placed
between the Review and Release states and is a state-blocking route, which means that all tasks
must be completed before the ECO can be promoted to Release. The route templates that are used
here must have a Route Base Purpose value of Approve, but the routes that are created from the
templates have a Route Base Purpose value of Standard. This allows added tasks to have more
choices for the task action.
The approval list is not seen or used by an ECR or ECO with an old (signature-based) policy since
signatures are used for approvals.
Chapter 5: Default Lists for Engineering Change 55

Default Approval Route Template
The table below describes the recommended Approval Route Template.
Template Route Route Base Task Edit Description

Name Instructions Purpose Setting
ECO Approval The ECO needs Approve Extend Task This Route Template is used to create the Route
approval List placed between the Review and Release states on
the ECO.
The template should have Enterprise Availability and be connected to Company Company Name.
The scope of the Template is the Change Responsibility organization. The Route Base Purpose is
Approve. The default route template should have a Task Edit Setting of Extend Task List so
that the mandatory tasks cannot be removed, but additional ones can be added.
The ECO Approval template should have the following role based tasks.
Task Name Route Task Approvers Comments Instructions Route Seq

User Responsibility Action
RT-SME role_SeniorMa Manufacturing This change Need your Approve 1
nufacturingEng requires your approval.
ineer approval.

6
Configuring Using Schema
Many aspects of the application are controlled through the administrative objects installed with
ENOVIA products. For example, the policy that governs a business object type controls who can
work with that kind of business object, what they can do, and during which states. This section
describes some common configuration changes that you may want to make. All these changes
can be made using Business Modeler or MQL.
When making changes to schema, remember these important points:

When changing names of administrative objects, change only the administration object name,
not the symbolic name. For more information on changing administration object names and on
symbolic names, see the ENOVIA Live Collaboration - Business Process Services -
Administrators Guide.
Whenever you remove the Originator attribute from a type, make sure you turn off the trigger
that populates the attribute by removing the Create and Revision triggers from the type.
Because the application internationalizes all onscreen text, including schema names, using a
string resource properties file, changing schema names does not change the names displayed
onscreen. For instructions on how to change the onscreen names for internationalized schema,
including policy states and attributes ranges, see the ENOVIA Live Collaboration - Schema
Reference Guide.
57
The following table contains business object types and attributes that you will most likely want to
change. All other business objects can also be configured to reflect your specific business
terminology.
Type Attribute Function Defaults

Part Number Series different types of part A Size, B Size, C Size, D Size
number series
Material Category composition of the part Metal, Plastic, Glass, Rubber, Concrete.
Service Make Buy Code whether the services are Unassigned, Make (in-house services), or Buy
in-house or contracted (services provided from outside sources).
Unit of Measure how the part is measured LB(pound), IN(inch), GA(gallon), FT(feet),
EA(each)
Production Make Buy Code whether the parts are Select a Production Make Buy Code:
made in-house or bought Unassigned, Make (items designed and
fabricated in house), or Buy (items bought
from outside sources).
Lead Time time that it will take to Selection of week numbers
manufacture the part.
Classification what category the part is Unassigned, Wiring Harness, Software, Sheet
in Metal, Printed Circuit Board, Molded,
Machined, Hardware, Extrusion, Other.
Design Responsibility company responsible for -
part design
Part Family Part Family Last Used last used sequence must be integer and hidden
Sequence
Part Family Sequence sequence pattern 0001,0002,0003,
Pattern
Drawing Number Series different types of drawing A Size, B Size, C Size, D Size
Print print number series
Designated User the person who will work All users
on the drawing print
CAD Model Number Series different types of CAD A Size, B Size, C Size, D Size
Model number series
on the CAD Model
CAD Number Series different types of CAD A Size, B Size, C Size, D Size
Drawing Drawing number series
on the CAD Drawing
Part Number Series different types of Part A Size, B Size, C Size, D Size
Specification Specification series
on the Part Specification

Type Attribute Function Defaults
Product Line Change Board group that reviews ECRs All defined Change Boards
for the Product Line.
ECR Category of Change the general nature of the Unassigned, Vendor Requirement, Product
ECR Improvement, New Production Introduction,
Marketing Requirement, Facilitate
Manufacturing, Drafting Error, Cost
Reduction.
Responsible Design the person who completes All users defined in the Senior Design
Engineer the ECR Engineer role
ECR Evaluator the person who decides if All users defined in the ECR Evaluator role
the request should
become an engineering
change order
Supporting Documents attachments that explain Sketch, EBOM Markup, Markup.
the ECR
ECO Responsible Design the person who creates All users defined in the Senior Design
Engineer ECOs Engineer role
Responsible Manufacturing the person who reviews All users defined in the Senior Manufacturing
Engineer ECOs and updates Engineer role
attributes
Release Distribution Group the group notified when All groups derived from 'Distribution Groups'
the ECO and all of its will be notified. The administrator must create
related parts are released. these groups prior to implementing the ECO
process.
Priority to define the importance Low, Medium, High
of the ECO
Sketch Designated User the person who will work All users
on the sketch
ECR / ECO Policies

The ECR(Standard) policy has been replaced by the ECR policy. The ECO(Standard) policy has
been replaced by the ECO policy. All new ECRs and ECOs are governed by the new policies and
follow those lifecycles. Objects already created with the Standard policies are supported for
backwards compatibility so they can be released.
The principal differences between the two is that the Standard policies rely on a connection to a
specific product line, whereas the new policies are route-based and rely on a relationship to a
specific change organization (Change Responsibility attribute) and use Reviewer lists and Approval
lists to determine which people need to review and approve the change request. See ECR
Lifecycle and ECR(Standard) Lifecycle and ECO Lifecycle and ECO(Standard) Lifecycle
in the ENOVIA Live Collaboration - Business Process Services - Application Exchange Framework
Users Guide.
Chapter 6: Configuring Using Schema 59

7
Configurable Objects, Pages,
Forms
This section lists configurable objects, pages and forms within Engineering Central.
In this section:
Configurable Automatically-Named Objects
Configurable Pages
Configurable Dynamic UI Form Components
Customizing the Part Specification Type
Customizing Views
61
Configurable Automatically-Named Objects
For information about how the autonaming process works and how to configure autonaming, see
Configuring Automatic Business Object Naming in the ENOVIA Live Collaboration - Business
Process Services - Administrators Guide.
Engineering Central includes two business objects for each type that is named automatically: an
eServices Object Generator object and an eServices Number Generator object. For example, these
are the business objects that let the system name ECO objects:
eService Object Generator
type_ECO
eService Number Generator
type_ECO
To see how the automatic names for an object type are constructedfor example, the numbering
sequence, prefix, and suffix usedlook at the attributes on the Object Generator that corresponds
to the object type. The automatic names are suggestions only. You probably want to customize the
naming to suit your business processes.
Engineering Central provides the option to automatically name these types of business objects
when they are created:
Part
Drawing Print
CAD Model
CAD Drawing
ECR
ECO
Sketch
Markup

Configurable Pages
The application pages that have been built using configurable tables and forms are listed below.
You edit configurable table pages using table and inquiry administrative objects and by passing
parameters to emxTable.jsp. You edit configurable form pages using Web form objects and by
passing parameters to emxForm.jsp. For instructions on how to configure tables and forms, see
the ENOVIA Live Collaboration - Business Process Services - Administrators Guide and the
ENOVIA Studio Modeling Platform - Business Modeler Guide.
The following are the configurable table pages and forms:

BOM summary page
Consolidated BOM report
Multi-level BOM report
ECO /ECR Affected Items
Edit Part Family: Owner field
Edit Part Details: Part Family field, ECO to Release field, Owner field
Edit ECR: Owner field
Edit Specification Details: Owner field
Edit Sketch: Owner field, ECR field
Create Part: Owner field, Part Family chooser
Chapter 7: Configurable Objects, Pages, Forms 63

Configurable Dynamic UI Form Components
The Web Form administrative object can be used to configure the Properties pages of parts,
MEPs, part families, ECRs and ECOs. The schema contains a specific Web Form administrative
object for each of the types. Each Web Form administrative object contains all attributes of the
specific item. The configurable form can be implemented as a read-only property page (View
form) or an editable property page (Edit form) as part of the application or as a custom page, as
required for the business process. The web form is dynamically displayed as a View or Edit page
based on the parameter mode included in the emxForm.jsp URL.
In this section:
Implementing a Configurable UI Form in JSP Applications
Implementing a View Mode Form
Implementing an Edit Mode Form
Implementing a Configurable UI Form in JSP Applications

A read-only property page can be configured using the View Form component. The following is a
sample URL for calling emxForm.jsp in View mode:
${COMMON_DIR}/
emxForm.jsp?form=ENCECOForm&objectId=3243.32424.232&relId=3432.2342.23
44&formHeader=ECO&topActionbar=ENCECOTopActionbar&editLink=true
Implementing a View Mode Form

1. Create and configure a web form administration object and then define the required form fields
to be displayed in the form page. See Building Form Pages in the ENOVIA Live
Collaboration - Application Development Guide.
2. If any action links are to be shown in the form header, create an Action menu and Action Link
command objects (or use already existing ones). For details, see Using Action Menus with a
Configurable Form in the ENOVIA Live Collaboration - Application Development Guide.
3. The View form supports a default Edit link to display in the header as an action link, just by
passing a URL parameter called editLink=true to emxForm.jsp; there is no need to create
any Action menu or command object.
4. Construct the emxForm.jsp?mode=view& URL to display the form page and assign it to
any command object that will call the form. If the mode parameter is not passed, the form
component defaults to View mode.
The emxForm.jsp page located in the common directory and the URL must be referenced
relative to this directory.
An editable property page can be configured using the Edit Form component. The following is a
sample URL for calling emxForm.jsp in Edit mode:
${COMMON_DIR}/
emxForm.jsp?form=ENCECOForm&mode=edit&objectId=3243.32424.232&relId=34
32.2342.2344&formHeader=ECO&topActionbar=ENCECOTopActionbar.

Implementing an Edit Mode Form
1. Create and configure a web form administration object and then define the required form fields
to be displayed in the form page. See Building Form Pages in the ENOVIA Live
Collaboration - Application Development Guide.
2. Construct the emxForm.jsp?mode=edit& URL to display the form page and assign it to
any command object that will call the form in Edit mode. You must include the mode
parameter, otherwise the form component defaults to View mode.
The emxForm.jsp page located in the common directory and the URL must be referenced
relative to this directory.
When the Done button is clicked in the edit form, the fields for which the logged-in user has modify
access are updated.
Fields with an associated ellipsis (...) button will pop up a new window to select required data.
The following shows the creation of a new web form using the thick client:

Customizing the Part Specification Type
In Engineering Central, specifications are objects connected to a part with the Specification
relationship. Specification types are: CAD Model, CAD Drawing, Drawing Print, and Part
Specification. CAD Model, CAD Drawing, and Drawing Print are types for those three kinds of
drawings.
Part Specification is a specification type not specific to a certain kind of document. The Part
Specification type can include any other kind of document your users want to connect to the part
with the Specification relationship.
To expand the Part Specification type to include other kinds of documents, you can customize the
Part Specification type to add a subtype for a document. You can also create a new Specification
type that is not a subtype of the Part Specification type.
Creating a Type as a Subtype to Part Specification

As business administrator, you can create a new type of specification by extending the Part
Specification type to include any kind of document that users want to connect to a part with the
Specification relationship.
To create a subtype of the Part Specification type

1. To create your the subtype, extend it from the abstract type Part Specification.
2. Register the new subtype. For details, see the ENOVIA Live Collaboration - Business Process
3. In the emxFrameworkStringResource.properties file define the string resource for the new
subtype. Use this format for the definition:
emxFramework.Type.<New_Spec_Type> = <New Spec Type Name>
For example:
emxFramework.Type.Test_Specification = Test Specification
4. Create a small icon image to represent the new type. Use the following format to name the
image:
iconSmall<NewSpecType>.gif
Store the image in the common/images directory.
5. Optionally, set up autonaming so users creating new specification objects of this subtype can
select the Autoname option to have specifications automatically named and numbered. For
information about how the autonaming process works and how to configure autonaming, see
Configuring Automatic Business Object Naming in the ENOVIA Live Collaboration -
Business Process Services - Administrators Guide.
Creating a New Specification Type

Instead of creating a new type of specification as a subtype of Part Specification, you can create a
new Specification type. This type can include any kind of document that users want to connect to a
part with the Specification relationship.

To create a new Specification type
1. Register the new type. For details, see the ENOVIA Live Collaboration - Business Process
2. In the emxFrameworkStringResource.properties file define the string resource for the new
subtype. Use this format for the definition:
emxFramework.Type.<New_Spec_Type> = <New Spec Type Name>
For example:
emxFramework.Type.Test_Specification = Test Specification
3. Create a small icon image to represent the new type. Use the following format to name the
image:
iconSmall<NewSpecType>.gif
Store the image in the common/images directory.
4. Modify the following relationships:
Part Specification
New Specification - Specification Revision
Request Specification Revision
Raised Against ECR
5. Define the Check Create trigger for the relationship Part Specification such that the trigger
checks that the policy of the specification object is compatible with that of a specification. (The
specification object should have these policy states: Review, Approved, and Released. See Part
Specification Policy States.)
6. To have the ECR Find Specification dialog display the document type that you created, modify
the eServiceEngineeringCentral.Types property in the
emxEngineeringCentral.properties file. To this property, add the new document
type.
eServiceEngineeringCentral.Types=[existing types],<New Type>
7. Optionally, set up object generation and autonaming so users creating new specification
objects of this type can select the Autoname option to have specifications automatically named
and numbered. For details, see Configurable Automatically-Named Objects.
Part Specification Policy States

In order to use a Document as a Part Specification, the document policy must have the following
states mapped:
state_Review. This must not be the first state in the policy.
state_Approved. This must come after state_Review.
state_Release. This must come after state_Approved.
For example the Type Technical Specification currently has the following states:
property = state_Draft value Draft
property = state_PeerReview value Peer Review
property = state_FormalApproval value Formal Approval
property = state_Issued value Issued
property = state_Obsolete value Obsolete

In order to connect this Type as a Part Specification, you would need to add the following symbolic
names to the Technical Specification policy:
property = state_Review value Peer Review
property = state_Approved value Formal Approval
property = state_Release value Issued
Register these symbolic names as described in the ENOVIA Live Collaboration - Business Process

Customizing Views
Custom views are available for many pages within Engineering Central. (See Designing Your
Own Page Views in AEF Help.)
Customizing BOM Views

If you are customizing the BOM view, there are certain columns that must be included in order to
either create or edit BOMs. The minimum columns required differs depending on which BOM
view you want to customize, as shown in the following table.
View Minimum Columns Required

Engineering Type, Name, Rev, Ref Designator, FN, Qty
Common or Type, Name, Rev, Ref Designator, FN, Qty, Manufacturing Part
Plant-Specific Usage, Auth Status, Usage, Switch, Pref Rank, Manufacturing
Type, Target End Date, Target Start Date, ERP-Status, Plant
Type
Customizing Affected Items View

If you are customizing the Affected Items view under ECR/ECO, the Requested Change column
is required in order to edit the Affected Item attributes.

8
Automated Processes
This section lists the triggers that have been added to policies and other administrative objects.
In this section:
Automation for All Types
Automation for ECRs
Automation for ECOs
Automation for Parts
Automation for Drawing Prints
Automation for CAD Models
Automation for CAD Drawings
Automation for Part Specifications
Automation for ECR Supporting Documents
All trigger programs are run using a Trigger Manager program called emxTriggerManager. This
Java program is specified as the Action for all triggers. The name of the eService Trigger Program
Parameters business object that represents the specific trigger program to run is specified as the
Input to pass to the Trigger Manager. The naming convention for the eService Trigger Program
Parameters object indicates the schema object the trigger is associated with, trigger event, and the
type of trigger.
[ADMIN OBJECT TYPE][ADMIN OBJECT NAME][TRIGGER EVENT][TYPE OF TRIGGER]
71
For example, an object named RelationshipVaultedDocumentsCreateAction indicates that the
trigger is a Create Action trigger on the Vaulted Documents relationship.
Trigger programs can be Tcl programs or Java programs. Attributes on the eService Trigger
Program Parameters object contain the name of the trigger program to run and parameters to pass to
it. For Java programs, the objects attributes also contain the specific method to call and constructor
arguments. Commented sections within each trigger program describe the parameters accepted by
the program.
For a trigger program to run, its eService Trigger Program Parameters object must be in the Active
state. To turn off a trigger, demote its eService Trigger Program Parameters object to Inactive.
For more information about the Trigger Manager and eService Trigger Program Parameters objects,
see the ENOVIA Live Collaboration - Business Process Services - Administrators Guide.
Automation for All Types

All types in the framework have two triggers that populate the Originator attribute. The table below
describes the automation.
If you remove the Originator attribute from a type, make sure you turn off the trigger that populates
the attribute by removing the Create and Revision triggers from the type.
eService Trigger Program Parameters Object Trigger Program Description of Action

TypeAllCreateAction emxcommonSetOriginator_if.tcl Store users name in Originator attribute
For information on this trigger program, see
the ENOVIA Live Collaboration - Business
TypeAllRevision Action emxcommonSetOriginator_if.tcl Store users name in Originator attribute
For information on this trigger program, see
the ENOVIA Live Collaboration - Business
Automation for ECRs

ECR objects are governed by the ECR policy. Configurable automation is described in the table that
follows.
ECRs using the ECR policy can be cancelled using the Cancel ECR command from the Properties
page, which moves the ECR to the Cancelled state.
ECRs using the obsolete ECR (Standard) policy cannot be cancelled (the Cancel ECR command is
removed for these objects). In order to reject these ECRs, users must edit and update the policy to
ECR Rejected. Doing this moves the object to the Rejected state.
eService Trigger Program Parameters Trigger Program and JPO Method Description of Action
Object
PolicyECRPromoteDemoteAction PDF Generation Whenever an ECR is promoted or demoted, a .pdf
is generated with the summary report and checked
into the ECR object.
PolicyECRStateCreatePromoteCheck CheckECRCoordinator Check if the ECR Coordinator has been assigned
for the assigned Change Responsibility.
PolicyECRStateCreatePromoteCheck CheckRouteCompleteForState Check if the state blocking routes are completed.
PolicyECRStateCreatePromoteAction RouteToECRCoordinator Assign the ECR to the ECR Coordinator on
promote.

Object
PolicyECRStateSubmitPromoteCheck CheckResponsibleDesignEngineer Check if the Responsible Design Engineer has been
assigned for the ECR.
PolicyECRStateSubmitPromoteCheck CheckRouteCompleteForState Check if the state blocking routes are completed.
PolicyECRStateSubmitPromoteAction RouteToResponsibleDesignEngineer Assign the ECR to the Responsible Design
Engineer.
PolicyECRStateSubmitPromoteAction NotifyAssignees Send a notification to the Responsible Engineer and
all assignees that the ECR has been promoted to the
Evaluate state.
PolicyECRStateSubmitPromoteAction AssignAffectedItemsToResponsibleDesignEngineer Assign all effected items of the current ECR to the
Responsible Design Engineer.
PolicyECRStateSubmitDemoteAction RouteToOriginator Reassign the ECR to the Originator on demote.
PolicyECRStateEvaluatePromoteCheck CheckECRChairman Check if the ECR Chairman has been assigned for
the RCO.
PolicyECRStateEvaluatePromoteCheck CheckProposedMarkupsECParts Check if all markups (BOM or Item) attached to an
ECR have been Approved or Rejected.
PolicyECRStateEvaluatePromoteCheck CheckRouteTemplateForState Check if the reviewer list is defined for the next
state and the route templates are connected to the
object.
If no reviewer list is added, an error message is
shown that the reviewer list must be selected and
the route templates are to be connected to the
object.
Notice: Review route template is not assigned.
PolicyECRStateEvaluatePromoteCheck CheckRouteCompleteForState Check if the state blocking routes are completed.
PolicyECRStateEvaluatePromoteAction RouteToECRChairman Assign the ECR to the ECR Chairman.
PolicyECRStateEvaluatePromoteAction CreateRouteForState Create a route if the reviewer list is defined for the
next state.
If a route already exists with same template (may
happen on demote and subsequent promote), then
do not create another route but send a notification to
the route owner (ECR Chairman) to restart the
route.
PolicyECRStateEvaluateDemoteAction RouteToECRCoordinator Assign the ECR to the ECR Coordinator on
demote.
PolicyECRStateReviewPromoteCheck CheckResponsibleDesignEngineer Check if the Responsible Design Engineer has been
assigned.
PolicyECRStateReviewPromoteCheck CheckRouteCompleteForState Check if the state blocking routes are completed.
PolicyECRStateReviewPromoteAction RouteToResponsibleDesignEngineer Assign the ECR to the Responsible Design
Engineer.
PolicyECRStateReviewPromoteAction NotifyDistributionList Send a notification to distribution list members that
the ECR is being promoted. No notification is sent
to the context user who is promoting the object. If
no distribution list is assigned, then no notifications
are sent. No duplicate notifications are sent.
PolicyECRStateReviewPromoteAction NotifyOriginator Send a notification to the originator of the ECR that
the ECR is being promoted. The originator is
notified separately from the NotifyDistributionList
trigger so that it can be turned off if desired.
PolicyECRStateReviewPromoteAction MergeallProposedMarkups Merge all the approved markups for an affected
item.
PolicyECRStateReviewDemoteAction RouteToResponsibleDesignEngineer Assign the ECR to the ResponsibleDesignEngineer
on demote.
PolicyECRStateReviewDemoteAction NotifyAssignees Send a notification to the Responsible Engineer and
all assignees that the ECR has been demoted and
needs additional work.
PolicyECRStatePlanECOPromoteCheck EnsureECOsAreAttached Check that there is a released ECO attached.
Chapter 8: Automated Processes 73

Object
PolicyECRStatePlanECOPromoteCheck CheckRouteCompleteForState Check if the state blocking routes are completed.
PolicyECRStatePlanECOPromoteAction ChangeOwnerToCorporate Assign the ECR to Corporate.
PolicyECRStatePlanECODemoteAction RouteToECRChairman Reset the owner back to the previous owner (ECR
Chairman).
Automation for ECOs

ECO objects are governed by the ECO policy. Configurable automation is described in the table
that follows..
eService Trigger Program Parameters Object Trigger Program and JPO Method Description of Action
PolicyECOPromoteDemoteAction PDF Generation Whenever an ECO is promoted or demoted, a .pdf
is generated with the summary report and checked
into the ECO object. By default, this is an inactive
trigger.
PolicyECOStateCreatePromoteCheck CheckResponsibleDesignEngineer Check if a Responsible Design Engineer has been
assigned. If the RDE is not assigned, the promotion
fails.
PolicyECOStateCreatePromoteAction RouteToResponsibleDesignEngineer Assign the ECO to the Responsible Design
Engineer by making the RDE the owner of the
ECO.
PolicyECOStateCreatePromoteAction ReviseAffectedItems Create a new revision for all affected items having a
Requested Change value of 'Revise.' The new
revisions are connected to the ECO as affected
items. If the old revision contained approved
markups, these markups are copied to the new
revisions.
PolicyECOStateCreatePromoteAction CreateNewRevisions Create new version of the part.
PolicyECOStateDefineComponentsPromoteCheck CheckRouteTemplateForState Check that a reviewer list has been assigned. If a
reviewer list has not been assigned, then the
promotion fails.
PolicyECOStateDefineComponentsPromoteAction CreateRouteForState Create a route between the Design Work and
Review states based on the reviewer list. This route
uses the reviewer list route template that has a
Route Base State value of "Design Work".
If a route already exists (this may happen on
demote and subsequent promote), then another
route is not created, but a notification is sent to the
route owner (Responsible Design Engineer) to
restart the route.
This handles approvals between the Design Work
and Review states.
PolicyECOStateCreatePromoteAction ReviseAffectedItems Create a new revision for all affected items that
have a Requested Change value of Revise. The
new revisions are connected to the ECO as affected
items. If the old revision contained approved
markups, these markups are copied to the new
revisions.
PolicyECOStateDefineComponentsPromoteAction CreateNewRevisions Create the version of the part.
PolicyECOStateDefineComponentsDemoteAction ResetOwner Reset the owner to the previous owner.
PolicyECOStateDesignWorkPromoteCheck CheckResponsibleManufacturingEngineer Check if a Responsible Manufacturing Engineer
has been assigned.
PolicyECOStateDesignWorkPromoteCheck CheckAffectedInApproved Check if the parts and specifications connected to
the ECO are in or beyond Approved state.
PolicyECOStateDesignWorkPromoteCheck CheckRouteTemplateForState Check that an approval list has been assigned.
PolicyECOStateDesignWorkPromoteCheck CheckRouteCompleteForState Check if the state blocking routes are completed.

PolicyECOStateDesignWorkPromoteCheck CheckProposedMarkupsECParts Check if the proposed markups are in Approve
state. Check for conflicts across the markups for
affected items.
PolicyECOStateDesignWorkPromoteCheck MergeallApprovedMarkups Merge all approved markups for an affected item.
PolicyECOStateDesignWorkPromoteAction CreateRouteForState Create a route based on the approval list. This route
uses the approval list route template.
If a route already exists (this may happen on
demote and subsequent promote), then a new route
is not created but a notification is sent to the route
owner (Responsible Design Engineer) to restart the
route.
This handles approvals between the Review and
Release states.
PolicyECOStateDesignWorkPromoteAction RouteToResponsibleManufacturingEngineer Assign the ECO to the Responsible Manufacturing
Engineer and sends a notification to RME that the
ECO requires attention.
PolicyECOStateReviewPromoteCheck CheckDistributionList Check if the distribution list has been assigned.
PolicyECOStateReviewPromoteCheck CheckRouteCompleteForState Check if the state blocking routes are completed.
PolicyECOStateReviewtoCancel PromoteCheckCheckAnyAppliedMarkupsFor Check (when ECO is promoted from Review to
State Cancel) for any applied markups attached to ECO,
Presence of any such markups will stop the ECO
promotion to Cancelled.
PolicyECOStateReviewPromoteAction ECOChangeProcessAction Check the Requested Change attribute and then
processes the change accordingly.
If the Requested Change value is "Release," then
the item is promoted to its Release state. If the
Requested Change value is "Revise," then the
affected item would have previously been revised
and the new revision is promoted to its Release
state. If the Requested Change value is "Obsolete,"
then the affected item is promoted to its Obsolete
state.
This trigger handles both parts and specs and is not
type-specific, meaning that any type should be
handled correctly. It takes advantage of the
background process feature.
PolicyECOStateReviewPromoteAction ChangeOwnerToCorporate Change the owner of the ECO to "Corporate" after
promotion.
PolicyECOStateReviewPromoteAction NotifyDistributionList Notify the members of the distribution list that the
ECO has been promoted. All duplicates are filtered
out.
PolicyECOStateReviewPromoteAction NotifyOriginator Notify the originator of the ECO that the ECO is
being promoted. The originator is notified
separately from the NotifyDistributionList trigger
so that it can be turned off if desired.
PolicyECOStateReviewPromoteAction PromoteAttachedECR Promote all attached ECRs that are in the Plan ECO
state to the Complete state.
PolicyECOStateReviewPromoteAction ApplyApprovedMarkups Apply all approved markups.
PolicyECOStateReviewDemoteAction RouteToResponsibleDesignEngineer On demote, reassign the ECO back to the
Responsible Design Engineer and send a
notification that it has been reassigned.
Note the state blocking routes on the Create state are inactive by default. This is because approvals
or reviews on this state are not enforced, but they can be easily added by a customer
implementation if the business process requires it.

Top-down ECO Release Process
The Top-down ECO Release Process releases all affected items connected to the ECO when the
ECO is released.
AutoPromoteChangedItemToReleaseState - This configurable check trigger (this can be turned off
by the Administrator by making it inactive) activates when the ECO is promoted from the Review
state. This trigger automatically tries to release all the ECO affected items that are in the Approved
state. If they are not in the Approved state, an error message is shown. If a part has a child part and
they are both on the same ECO, the parent part will be promoted first. If this trigger fails, then it
will not allow the ECO to be promoted to the Release state. If this trigger passes, then the ECO will
be promoted to the Release state.
Additional triggers related to the ECO Release Process.
AutoPromoteECOToReviewState - When the last changed item associated with the ECO
reaches its pre-release state, the ECO is automatically promoted to its Review state. A
configurable action trigger (this can be turned off by the Administrator by making it inactive)
activates when a part, drawing print, CAD model or CAD drawing is promoted from the
Review state to the Approved state, and after that object successfully enters the Approved state.
This trigger checks whether all other affected items connected to the ECO are in the Approved
state. If it finds that all other affected items connected to the ECO are in the Approved state,
then it will try to automatically promote the ECO to the Review state. If it finds a single
affected item connected to the ECO still in a state prior to Approved, then it will not promote
the ECO to the Review state.
A configurable check trigger (this can be turned off by the Administrator by making it
inactive) activates when a user attempts to promote an ECO from the Design Work state to
the Review state, and before the ECO successfully enters the Review State. This trigger checks
whether all affected items connected to the ECO are in the Approved state. If yes, then it
allows the ECO to be promoted to the Review state. If it finds a single affected item connected
to the ECO still in a state prior to Approved, then it will not allow the ECO to be promoted to
the Review state.
AutoCheckChangedItemToReleaseState - No affected items can be promoted to their Release
state unless their associated ECO has reached its Release state. (This trigger is inactive by
default as this stops the Top-Down ECO Release Process.) A configurable check trigger
activates when a part, drawing print, CAD model or CAD drawing is promoted from the
Approved state to the Release state, but before that object successfully enters the Release state.
This trigger checks whether the connected ECO is in Release state. If yes, then it will allow the
object to be promoted to the Release state. If it finds the connected ECO is not in the Release
state, then it will not allow the object to be promoted to the Release state.
Automation for Parts

Part objects can be governed by the EC Part Production policy or the Development Part policy. The
Manufacturer Equivalent policy controls the lifecycle of manufacturer equivalent parts.
Configurable automation is described in the tables that follow.
EC Part Policy
TypePartReviseAction CopySubstitutes Copy substitute parts to the revised part.
RelationshipEBOMDeleteOverride RemoveSubstitutes Remove substitute parts that are connected, when a
part is disconnected from an assembly.
RelationshipEBOMModifyAttributeAction SyncSubstitutes When a part is updated, ensure that Find Number
and Reference Designator attributes are in sync.

TypePartCreateCheck eServiceValidRevisionChange_if.tcl Ensure no revisions of the same Type and Name
EnsureNoRevisionsExist exist.
TypePartCreateAction NotifyComponentEngineerOfMECreate Notify Component Engineer role when user without
Component Engineer role creates a Manufacturer
Equivalent Part
TypePartReviseAction ClearEffectivityDate When an assembly part is revised, the Start
Effectivity Date and the End Effectivity Date on the
EBOM relationships between the in-process rev of
this assembly and the children parts are set to blank.
TypePartReviseAction ClearMEEffectiveDates Clear the start and end effectivity dates on the
Manufacturer Equivalent relationship.
TypePartReviseAction EnsureDesignReponsibility Ensure that Responsible Design Organization has
been specified.
Type PartRevisionAction SendSubscriptionNotification Notify subscribers when the part is revised.
TypePartDeleteAction SendSubscriptionNotification Notify subscribers when the part is deleted.
PolicyECPartStatePreliminaryPromoteCheck CheckAttachedPartsBeyondReview Ensure attached parts are beyond the Review state.
PolicyECPartStatePreliminaryPromoteCheck CheckAttachedSpecsBeyondReview Attachments via part specification must be in
Review state or beyond. This is inactive by default.
PolicyECPartStatePreliminaryPromoteCheck EnsureECOConnected ECOs must be connect via New Part / Part Revision
relationship
PolicyECPartStatePreliminaryPromoteCheck CheckPreviousRevsInReviewOrBeyond Previous revisions of this part must be in Review or
beyond.
PolicyECPartStatePreliminaryPromoteCheck CheckForEBOMRecursion Ensure that no EBOM recursive references
exist.
PolicyECPartStatePreliminaryPromoteCheck EnsureFindNumbersAreFilledIn Ensure Find Numbers are not default values and are
unique.
PolicyECPartStatePreliminaryPromoteCheck CheckRoutesForPreliminaryState Ensure routes in preliminary state.
PolicyECPartStatePreliminaryPromoteCheck EnsureSpecsConnected Ensure that specifications are connected to the part.
By default, this trigger is inactive.
PolicyECPartStatePreliminaryPromoteCheck EnsureDesignResponsiblity Ensure that Design Responsibility has been
specified.
PolicyECPartStatePreliminaryPromoteCheck EnsureCATIAProductExistsAndReleased Check whether corresponding VPM product by
"Product Specification" relationship is in Released
state or not. This trigger checks for the state of the
VPM product if and only if the product is
connected to the part.
VPM user cannot add specifications manually to
the part. If the part is created in Engineering
Central, the user can add reference documents in
the absence of specifications to promote the part.
RelationshipEBOMSubstituteCreateAction AssignManufacturingResponsibilityForSubstitutePa When a substitute part is defined for a part, assigns
rt the same manufacturing responsibility to the
substitute part.
RelationshipEBOMCreateCheck eServicecommonTrigcLastRevAtState_if.tcl Child components must be latest released revision.
CheckIfLatestReleasedRevision
RelationshipManufacturingResponsibilityModifyAt assignManufResForChildAndSubstitutePart When MBOM is installed, assigns manufacturing
tributeAction responsibility for the substitute part, alternate part,
and child part based on the attributes End Item and
End Item Override.
RelationshipEBOMModifyAttributeOverride SyncSubstitutes When the Find Number or Reference Designator
attributes are updated on an EBOM, the same
attributes will be updated on any of its Substitute
objects.
PolicyECPartStateReviewPromoteCheck EnsureECOConnected ECOs must be connect via New Part / Part Revision
relationship.

PolicyECPartStateReviewPromoteCheck eServicecommonTrigcPreviousRevPromotion_if.tcl Previous revisions of this part must be in Release or
CheckPreviousRevsInReleaseOrBeyond beyond.
PolicyECPartStateReviewPromoteCheck eServicecommonCheckRelState_if.tcl Attachments via EBOM must be in Release or
CheckAttachedPartsBeyondRelease beyond.
PolicyECPartStateReviewPromoteCheck eServicecommonCheckRelState_if.tcl Check if the attached part specification is in the
CheckAttachedSpecsBeyondRelease Approved state.
PolicyECPartStateReviewPromoteCheck eServicecommonCheckRelState_if.tcl Check that if there are any equivalent parts
CheckEquivalentPartStateToRelease connected to this part, at least one of the equivalent
parts must be released. If none of the attached
equivalent parts are released, the following error
message appears: The Part has one or more
equivalent parts connected. One or more of the
equivalent parts must be in the Release state.
PolicyECPartStateReviewPromoteAction eServicecommonRelativeFloatAction_if.tcl Upon entering the Release state all unfulfilled
FloatUnfulfilledECRToReleasedPart ECRs must be copied to the newly released part.
PolicyECPartStateReviewPromoteAction eServicecommonRelativeFloatAction_if.tcl See Float EBOM to End.
FloatEBOMToEnd
PolicyECPartStateReviewPromoteAction SetEffectivityStartDate When an assembly part is released, the Start
Effectivity Date on the EBOM relationships
between this assembly part and the connected
children parts is set to the released date of this
assembly.
PolicyECPartStateReviewPromoteAction eServicecommonRelativeFloatAction_if.tcl Check the previous revisions of this part for
FloatUnfulfilledECRs connected ECRs that are not fulfilled or rejected.
Float them to this revision if they do not have an
ECO attached.
PolicyECPartStateReviewPromoteAction AutoPromoteECOToReviewState When the last affected item EC Part goes to
Approved state, auto promote the connected ECO
to Review state.
PolicyECPartStateReviewPromoteAction EServicecommonTrigcChangeOwner_if.tcl Change owner to Corporate.
ChangeOwnerToCorporate
PolicyECPartStateReviewPromoteAction SendSubscriptionNotification Notify subscribers that the part has been Approved.
PolicyECPartStateApprovedPromoteAction FloatEBOMToEnd When both a parent part and its children are revised
and released on the same ECO, substitute parts are
copied to the revised part and its children.
PolicyECPartStateApprovedPromoteCheck AutoCheckChangedItemToReleaseState When the EC Part goes to Release state, check
whether the connected ECO is in Release state.
PolicyECPartStateApprovedPromoteCheck CheckVPMProductState Check that the associated VPM product is in the
Release state before the EC part is promoted to
Release state. (TBE environment only)
PolicyECPartStateApprovedPromoteAction SendSubscriptionNotification Notify subscribers that the part has been Released.
PolicyECPartStateReleasePromoteCheck AutoCheckOneEquivalentToReleaseState When an enterprise part is released, ensure that at
least one of its proposed equivalents is in the
released state. This check is configurable.
PolicyECPartStateReleasePromoteAction SetEffectivityEndDate When a child part is promoted to Obsolete, a trigger
will set the End Effectivity Date on the EBOM
relationship between that part and its parent
assembly to the date this part enters the Obsolete
state.
PolicyECPartStateReleasePromoteAction SendSubscriptionNotification Notify subscribers that the part has been made
Obsolete.

Float EBOM to End
The action trigger on the promote of a part to the release state is updated to handle the EBOM
History relationship. This trigger currently loops through all EBOM relationships for the
component part and evaluates which EBOM connections need to float to the new released part.
If the EBOM connection is from the highest release of a part, the following steps are
performed:
An identical EBOM History relationship is created between the parts. This connection has
all the same attribute values as the EBOM connection.
Then, the End Effectivity Date on the EBOM History connection is set to (the date the
component part is released - 1 sec)
The EBOM connection is floated to the newly released component part.
The Start Effectivity Date on the EBOM connection is set to the date the component part is
released.
The End Effectivity Date on the EBOM connection is kept blank (no end effectivity date).
If the EBOM connection is from an in-process part, then the EBOM relationship is floated to
the new released part. There is no need for an EBOM History connection here.
If attributes are added to the EBOM relationship, they also need to be added to the EBOM History
relationship. The EBOM and EBOM History relationships' attributes must always be in sync!
Development Part Policy
PolicyDevelopmentPartStatePreliminaryPromoteCheck EnsureCATIAProductExistsAndReleased Check whether corresponding VPM product by
"Product Specification" relationship is in Released
state or not. This trigger checks for the state of the
VPM product if and only if the product is
connected to the part.
VPM user cannot add specifications manually to
the part.
PolicyDevelopmentPartStateCreatePromoteCheck EnsureSpecsConnected Ensure that specifications are connected to the part.
By default, this trigger is inactive. This trigger is
inactive for TBE customization.
PolicyDevelopmentPartStateCreatePromoteCheck EnsureDesignResponsiblity Ensure that Responsible Design Organization has
been specified. By Default, this is set to inactive.
This trigger is inactive for TBE customization, as
Design Responsibility is removed from part
creation for TBE.
PolicyDevelopmentPartStateCompletePromoteAction SendSubscriptionNotification Notify subscribers when a development part is
promoted to Complete.
Manufacturer Equivalent Policy
Type MEPRevisionAction SendSubscriptionNotification Notify subscribers when a Manufacturer Equivalent
Part is revised.
Type MEPDeleteAction SendSubscriptionNotification Notify subscribers when a Manufacturer Equivalent
Part is deleted.
Type PartCreateAction NotifyComponentEngineerOfMECreation If a Design Engineer creates a Manufacturer
Equivalent Part, an optional notification is sent to
the Component Engineer. An implementation
property setting controls this message.

PolicyManufacturerEquivalentStatePreliminaryPromoteCheck EnsureSpecsConnected Ensure at least one specification is connected with a
file checked in. By default, this trigger is inactive.
PolicyManufacturerEquivalentStatePreliminaryPromoteCheck EnsureFindNumbersAreFilledIn Ensure Find Numbers are filled in.
PolicyManufacturerEquivalentStatePreliminaryPromoteCheck EnsureECOConnected Ensure ECO connected and in Release state.
The state of this trigger should coincide with the
AllowChangeManagementForManufacturerEquival
entParts flag. If it is false then the
EnsureECOConnected trigger should be Inactive.
PolicyManufacturerEquivalentStatePreliminaryPromoteCheck CheckPreviousRevsInReviewOrBeyond Check that previous revisions, if exist, are in the
Review state or beyond.
PolicyManufacturerEquivalentStatePreliminaryPromoteCheck CheckRoutesforPreliminaryState This trigger is inactive by default.
PolicyManufacturerEquivalentStatePreliminaryPromoteCheck EnsureDesignResponsibilityExists Ensure a Design Responsibility connection exists.
This trigger is inactive by default.
PolicyManufacturerEquivalentStatePreliminaryPromoteCheck CheckAttachedPartsBeyondReview Check that attached parts are beyond the Review
state.
PolicyManufacturerEquivalentStatePreliminaryPromoteCheck CheckAttachedSpecsBeyondReview Check that attached specifications are beyond the
Review state. This is inactive by default.
PolicyManufacturerEquivalentStatePreliminaryPromoteCheck CheckForEBOMRecursion Ensure that no EBOM recursive references exist.
PolicyManufacturerEquivalentStateReviewPromoteCheck CheckAttachedPartsBeyondApproved Check that attached parts are beyond the Approved
state.
PolicyManufacturerEquivalentStateReviewPromoteCheck CheckAttachedSpecsBeyondApproved Check that attached specifications are beyond the
Approved state.
PolicyManufacturerEquivalentStateReviewPromoteCheck CheckPreviousRevsInApprovedOrBeyond Check that previous revisions, if exist, are in the
Approved state or beyond.
PolicyManufacturerEquivalentStateReviewPromoteCheck EnsureECOConnected Ensure ECO connected and in Release state.
The state of this trigger should coincide with the
AllowChangeManagementForManufacturerEquival
entParts flag. If it is false then the
EnsureECOConnected trigger should be Inactive.
PolicyManufacturerEquivalentStateReviewPromoteAction AutoPromoteECOToReviewState When the last affected item EC Part goes to
to Review state.
PolicyManufacturerEquivalentStateReviewPromoteAction FloatMEPToEnd Float the Manufacturer Equivalent relationship.
(same as EC Part Policy triggers)
PolicyManufacturerEquivalentStateReviewPromoteAction SetEffectiveStartDate Set the Effectivity Start date on the Manufacturer
Equivalent relationship (same as EC Part Policy
triggers)
PolicyManufacturerEquivalentStateReviewPromoteAction FloatEBOMToEnd Float the EBOM relationship
PolicyManufacturerEquivalentStateReviewPromoteAction FloatMEToEnd Float the Manufacturer Equivalent relationship.
(same as EC Part Policy triggers)
PolicyManufacturerEquivalentStateReviewPromoteAction FloatUnfulfilledECRs Float unfulfilled ECRs
PolicyManufacturerEquivalentStateReviewPromoteAction SetEffectiveStartDate Set the Effectivity Start date on the EBOM
relationship
PolicyManufacturerEquivalentStateReviewPromoteAction SetMEEffectiveStartDate Set the Effectivity Start date on the Manufacturer
triggers)
PolicyManufacturerEquivalentStateReviewPromoteAction SendSubscriptionNotification Notify subscribers when a Manufacturer Equivalent
Part is Approved.
PolicyManufacturerEquivalentStateApprovedPromoteAction SendSubscriptionNotification Notify subscribers when a Manufacturer Equivalent
Part is Released.
PolicyManufacturerEquivalentStateReleasePromoteAction SendSubscriptionNotification Notify subscribers when a Manufacturer Equivalent
Part is promoted to Obsolete.
PolicyManufacturerEquivalentStateAprovedPromoteCheck AutoCheckChangedItemToReleaseState When the EC Part goes to Release state, check
whether the connected ECO is in Release state
PolicyManufacturerEquivalentStateAprovedPromoteAction ChangeOwnerToCorporate Change owner to Corporate

PolicyManufacturerEquivalentStateReleasePromoteAction SetEffectiveEndDate Set the Effectivity End date on the Manufacturer
Equivalent History relationship (same as EC Part
Policy triggers)
Sets the Effectivity End date on the EBOM
relationship
PolicyManufacturerEquivalentStateReleasePromoteAction SetMEEffectiveEndDate Set the Effectivity End date on the Manufacturer
triggers)
A MEP can be a normal MEP (corporate) or a location-specific MEP.

When a location-specific MEP is created and a location is selected, an intermediate location
equivalent object is created and relationships are created between the enterprise part, location
selected, and MEP as shown in the diagram below.
An intermediate object, location equivalent object, will model a MEP that has context to a
specific location. For each location one intermediate object is created. (Similar to substitute
part functionality).
The Location Equivalent relationship is used as the intermediate relationship between the
enterprise part and the intermediate location equivalent object. This relationship is from the
enterprise part to the location equivalent object.
The location equivalent object is associated with the enterprise parts MEP with the
Manufacturing Equivalent relationship. The cardinality is restricted to 1:1.
The intermediate location equivalent object is associated with the location with the Allocation
Responsibility relationship. The cardinality is restricted to 1:1.
The above Figure is with understanding that a Corporate MEP can exist with location(s) (via
Allocation Responsibility) and with out location(s) also. MEP #4454 MOT, TI and IBM are
corporate MEPs with association to locations, while MEP #4454 XXX is a corporate MEP with no
location association.
In the example above, there are four corporate approved MEPs for EP # 4454, MEP # 4454-IBM,
MOT, TI and MEP # XXX.
The MEPs available for use for EP # 4454 in the context of location 1 are MEP # 4454-ONS and
TI. The MEP # 4454-TI is corporate approved with location association; ONS is a location 1
specific MEP.
The MEPs available for use for EP # 4454 in the context of location 2 are MEP # 4454-ONS, MOT
and IBM.

The MOT and IBM are corporate approved with location association; ONS is a location 2 specific
MEP. The MEP # XXX is corporate MEP but has no location context.
Substitute Part Policy
RelationshipSubstituteCreateAction SendSubscriptionNotification Notify subscribers that a substitute has been created
for the part.
RelationshipSubstituteDeleteAction SendSubscriptionNotification Notify subscribers that a substitute has been deleted
from the part.
Alternate Part Policy
RelationshipAlternateCreateAction SendSubscriptionNotification Notify subscribers that an alternate has been created
for the part.
RelationshipAlternateDeleteAction SendSubscriptionNotification Notify subscribers that an alternate has been deleted
from the part.
Spare Part Policy
RelationshipSparePartCreateAction SendSubscriptionNotification Notify subscribers that a spare part has been created
for the part.
RelationshipSparePartDeleteAction SendSubscriptionNotification Notify subscribers that a spare part has been deleted
from the part.
Part Family Subscription Events
RelationshipPartFamilyMemberAddedAction SendSubscriptionNotification Notify subscriber that a member was added to a part
family.
RelationshipPartFamilyMemberRemovedAction SendSubscriptionNotification Notify subscriber that a member was removed from
a part family.
Automation for Drawing Prints

Drawing Print objects are governed by the Drawing Print policy. Configurable automation is
described in the table that follows.
TypeDrawingPrintCreateCheck eServicecommonValidRevisionChange_if Ensure no revisions of the same Type and Name
PolicyDrawingPrintStatePreliminaryPromoteCheck EnsureECOConnected ECO must be connected via the New Specification /
Specification Revision relationship. See Specifying
ECO Requirements for Promoting Specifications.
PolicyDrawingPrintStatePreliminaryPromoteCheck eServicecommonTrigcPreviousRevPromotion_if.tcl Previous revisions of this Drawing Print must be in
CheckPreviousRevsInReviewOrBeyond Review or beyond.
PolicyDrawingPrintStateReviewPromoteCheck eServicecommonTrigcPreviousRevPromotion_if.tcl Previous revisions of this Drawing Print must be in
CheckPreviousRevsInReleaseOrBeyond Release or beyond.
PolicyDrawingPrintStateReviewPromoteCheck EnsureECOConnected ECO must be connected via the New Specification /

PolicyDrawingPrintStateReviewPromoteAction eServicecommonRelativeFloatAction_if.tcl Float all Part Specification Relationships in TO
FloatPartSpecificationToNewRev direction
PolicyDrawingPrintStateReviewPromoteAction eServicecommonRelativeFloatAction_if.tcl Release drawings
ReleaseDrawing
PolicyDrawingPrintStateReviewPromoteAction eServicecommonRelativeFloatAction_if.tcl Float unfulfilled ECRs
FloatUnfulfilledECRs
PolicyDrawingPrintStateReviewPromoteAction AutoPromoteECOToReviewState When the last affected Drawing Print goes to
to Review state.
PolicyDrawingPrintStateReviewPromoteAction eServicecommonTrigcChangeOwner_if.tcl Change owner to Corporate
PolicyDrawingPrintStateApprovedPromoteCheck AutoCheckChangedItemToReleaseState When the Drawing Print goes to Release state,
check whether the connected ECO is in Release
state
PolicyDrawingPrintStateApprovedPromoteCheck EnsureECOConnected ECO must be connected via the New Specification /
PolicyDrawingPrintStateApprovedPromoteAction FloatReferenceDocumentsOnRelease * Delayed float logic is implemented to float the
reference documents when a new version of these is
released. See Float Reference Documents on
Release.
Specifying ECO Requirements for Promoting Specifications

Whether an ECO is required to promote a specification (CAD drawing, CAD model, drawing print)
to the Released state is governed by the relationship used to connect the specification to the part and
by the promote check trigger for the specification.
By default:
If a specification is connected to a part using the New Specification/Specification Revision
relationship, an ECO is always required to promote the specification to the Released state.
If a specification is connected to a part using the Reference Documents relationship, no ECO is
required to promote the specification to the Released state.
If a specification is not connected to a part (no relationship), no ECO is required to promote the
specification to the Released state.
If you are not using the New Specification/Specification Revision relationship, you can still require
an ECO to promote specifications by changing the eService Program Argument1 attribute to false
on the check trigger program object. This attribute governs the
NoChangeManagementIfReferenceOnly flag in the code. If the value is true, no ECO is required.
If the value is false, an ECO is required.
For example, the following is the Type, Name, and Revision for the Promote Check Trigger
program on policy DrawingPrint on state Review:
Type : eService Trigger Program Parameters
Name: PolicyDrawingPrintStateReviewPromoteCheck
Revision: EnsureECOConnected
Attribute: eService Program Argument1
Value: true
The following is the list of names of eService Trigger Program Parameters objects where you can
change the eService Program Argument1 attribute to false require an ECO for promotion.
PolicyCADDrawingStatePriliminaryPromoteCheck

PolicyCADDrawingStateReviewPromoteCheck
PolicyCADDrawingStateApprovedPromoteCheck
PolicyCADModelStatePriliminaryPromoteCheck
PolicyCADModelStateReviewPromoteCheck
PolicyCADModelStateApprovedPromoteCheck
PolicyDrawingPrintStatePriliminaryPromoteCheck
PolicyDrawingPrintStateReviewPromoteCheck
PolicyDrawingPrintStateApprovedPromoteCheck
Automation for CAD Models

CAD Model objects are governed by the CAD Model policy. Configurable automation is described
in the table that follows.
TypeCADModelCreateCheck eServicecommonValidRevisionChange_if Ensure no revisions of the same Type and Name
PolicyCADModelStatePreliminaryPromoteCheck EnsureECOConnected ECO must be connected via the New Specification /
PolicyCADModelStatePreliminaryPromoteCheck eServicecommonTrigcPreviousRevPromotion_if.tcl Previous revisions of this CAD Model must be in
PolicyCADModelStateReviewPromoteCheck eServicecommonTrigcPreviousRevPromotion_if.tcl Previous revisions of this CAD Model must be in
PolicyCADModelStateReviewPromoteCheck EnsureECOConnected ECO must be connected via the New Specification /
PolicyCADModelStateReviewPromoteAction eServicecommonRelativeFloatAction_if.tcl Float all Part Specification Relationships in TO
PolicyCADModelStateReviewPromoteAction ReleaseDrawing
PolicyCADModelStateReviewPromoteAction eServicecommonRelativeFloatAction_if.tcl Float unfulfilled ECRs
PolicyCADModelStateReviewPromoteAction AutoPromoteECOToReviewState When the last affected item CAD Model goes to
to Review state.
PolicyCADModelStateReviewPromoteAction eServicecommonTrigcChangeOwner_if.tcl Change owner to Corporate
PolicyCADModelStateReviewPromoteAction FloatUnfulfilledECRToReleasedCADModel Copy all unfulfilled ECRs
PolicyCADModelStateApprovedPromoteCheck AutoCheckChangedItemToReleaseState When the CAD Model goes to Release state, check
whether the connected ECO is in Release state
PolicyCADModelStateApprovedPromoteCheck EnsureECOConnected ECO must be connected via the New Specification /
PolicyCADModelStateApprovedPromoteAction FloatReferenceDocumentsOnRelease * Delayed float logic is implemented to float the
Release.

Automation for CAD Drawings
CAD Drawing objects are governed by the CAD Drawing policy. Configurable automation is
TypeCADDrawingCreateCheck eServicecommonValidRevisionChange_if Ensure no revisions of the same Type and Name
PolicyCADDrawingStatePreliminaryPromoteCheck EnsureECOConnected ECO must be connected via the New Specification /
PolicyCADDrawingStatePreliminaryPromoteCheck eServicecommonTrigcPreviousRevPromotion_if.tcl Previous revisions of this CAD Drawing must be in
PolicyCADDrawingStateReviewPromoteCheck eServicecommonTrigcPreviousRevPromotion_if.tcl Previous revisions of this CAD Drawing must be in
PolicyCADDrawingStateReviewPromoteCheck EnsureECOConnected ECO must be connected via the New Specification /
PolicyCADDrawingStateApprovedPromoteAction ReleaseDrawing Promotes the CAD Drawing to the Released state.
PolicyCADDrawingStateApprovedPromoteAction eServicecommonRelativeFloatAction_if.tcl Float all Part Specification Relationships in TO
PolicyCADDrawingStateApprovedPromoteAction eServicecommonRelativeFloatAction_if.tcl Float unfulfilled ECRs
PolicyCADDrawingStateApprovedPromoteAction AutoPromoteECOToReviewState When the last affected item CAD Drawing goes to
to Review state.
PolicyCADDrawingStateApprovedPromoteAction eServicecommonTrigcChangeOwner_if.tcl Change owner to Corporate
PolicyCADDrawingStateApprovedPromoteCheck AutoCheckChangedItemToReleaseState When the CAD Drawing goes to Release state,
state
PolicyCADDrawingStateApprovedPromoteCheck EnsureECOConnected ECO must be connected via the New Specification /
PolicyCADDrawingStateApprovedPromoteAction FloatReferenceDocumentsOnRelease * Delayed float logic is implemented to float the
Release.
Float Reference Documents on Release

The ReferenceDocumentTypes property specifies which types of objects can be used as reference
documents. For those objects (by default, CAD model, CAD drawing, and drawing print), you
should configure the FloatReferenceDocumentsOnRelease trigger on the states in which you
consider the document to be locked-down, that is, no further changes can be made to it.

The following diagram shows that when the new revision of CAD Model (Rev 2) is released, the
Reference Document relationship between the latest released revision of the parent part (Rev 2) and
CAD Model (Rev 1) is disconnected and connected to the new revision of the CAD Model (Rev 2).
Part A Part A Part A Part A

Rev 1 Rev 2 Rev 1 Rev 2
Reference Reference Reference Reference

Document Document Document Document
CAD Model CAD Model

Rev 1 Rev 1
CAD Model CAD Model

Rev 2 Rev 2
Automation for Part Specifications

Part Specification objects are governed by the Part Specification policy. Configurable automation is
TypePartSpecificationCreateCheck EnsureNoRevisionsExist Ensure no revisions of the same Type and Name
exist.
TypePartSpecificationReviseAction RevisePartSpecification Revise the part specification.
TypePartSpecificationDeleteOverride eServicecommonTrigaDeleteDrawing_of.tcl Reconnects a part object to an earlier version of a
DeletePartSpecification Part Specification object upon deletion of a later
version.
TypePartSpecificationChangeOwnerAction NotifyNewOwner When ownership of a part specification changes,
this trigger notifies the new owner.
PolicyPartSpecificationStatePreliminaryPromoteCheck eServicecommonTrigcPreviousRevPromotion_if.tcl Previous revisions of this Part Specification must be
CheckPreviousRevsInReviewOrBeyond in Review or beyond.
PolicyPartSpecificationStatePreliminaryPromoteCheck EnsureECOConnected ECO must be connected via the New Specification /
PolicyPartSpecificationStateReviewPromoteCheck eServicecommonTrigcPreviousRevPromotion_if.tcl Previous revisions of this Part Specification must be
CheckPreviousRevsInReleaseOrBeyond in Release or beyond.
PolicyPartSpecificationStateApprovedPromoteCheck AutoCheckChangedItemToReleaseState When the Part Specification goes to Release state,
state
PolicyPartSpecificationStateApprovedPromoteCheck EnsureECOConnected ECO must be connected via the New Specification /
PolicyPartSpecificationStateApprovedPromoteAction ReleaseDrawing Promote the part specification to Released.
PolicyPartSpecificationStateApprovedPromoteAction FloatReferenceDocumentsOnRelease Delayed float logic is implemented to float the
Release.
PolicyPartSpecificationStateApprovedPromoteAction sServicecommonTrigcChangeOwner_if.tcl Change ownership to Corporate.

PolicyPartSpecificationStateApprovedPromoteAction FloatUnfulfilledECRs Float the unfulfilled ECRs attached to the previous
revision to this revision.
PolicyPartSpecificationStateApprovedPromoteAction eServicecommonRelativeFloatAction_if.tcl Float all Part Specification relationships in TO
FloatPartSpecificationToNewRev direction.
For Engineering Central business logic, any specification that is attached to a part must have states
that map to Review, Approved and Release states. These states must be sequenced in this order, that
is, Review before Approved, which is before Release. Also Review cannot be the first state. In
order for the Create trigger for Relationship Part Specification to pass, the specifications policy
must have symbolic names for state_Review, state_Approved, and state_Release that map to
corresponding states in the Specification policy along with the criteria given above. Any
integrations or other applications that use different specification types that are connected to parts
must meet this criteria.
Automation for ECR Supporting Documents

Sketch objects are governed by the ECR Supporting Document policy. Configurable automation is
PolicyECRSupportingDocumentStatePreliminaryPromot eServicecommonTrigcChangeOwner_if.tcl Change owner to Corporate
eAction ChangeOwnerToCorporate

Email Notifications
Engineering Central generates the following email notifications. The

emxEngineeringCentralStringResource.properties file contains the message text
and trigger names for the notifications. You can change the message text by editing the properties
file.
To configure the recipient list, change the respective code/trigger.
ECR to be Reviewed
Message The attached ECR is ready for review.
How Sent When the ECR is promoted from the Evaluate state to the Review state, the trigger
PolicyECRStandardStateEvaluatePromoteAction with revision NotifyChangeBoard gets fired. The
program eServicecommonTrigcAutoRouteByNavigation_if.tcl gets executed.
Property Keys emxEngineeringCentral.IconMail.Subject1 and emxEngineeringCentral.IconMail.Message1

Associated
Recipients ECR Chairman -- On promotion of ECR from Evaluate to Review
ECO Promoted to Release State

Message You have been identified as the Release Distribution Group for the attached ECO. It requires your
attention.
How Sent When the ECO is promoted from the Review state to the Release state, the trigger Policy
ECOStandardStateReviewPromoteAction with revision RouteToReleaseDistributionGroup gets fired.
The program sServicecommonTrigcAutoRouteByAttribute_if.tcl gets executed.

Associated
Recipients Senior Manufacturing Engineer

Ownership Notification
Message You have been given ownership of the attached object.
How Sent Whenever the owner of a business object (ECO, ECR, Sketch, Drawing Print, etc.) is changed, the
appropriate trigger (TypeECRChangeOwnerAction or TypeECOChangeOwnerAction or
TypeSketchChangeOwnerAction or TypeDrawingPrintChangeOwnerAction or
TypePartChangeOwnerAction) with revision NotifyNewOwner gets fired and the program
emxcommonTrigaNotifyNewOwner_if.tcl gets executed, producing this notification.

Associated
Recipients ECR creator -- On promotion of ECR from the assignment screen to Create
ECR Coordinator -- On promotion of ECR from Create to Submit
ECR Evaluator -- On promotion of ECR from Submit to Evaluate
ECR Chairman -- On promotion of ECR from Evaluate to Review
Responsible Design Engineer -- On promotion of ECR from Review to Plan ECO
Responsible Design Engineer -- On promotion of ECO from Create to Define Components
ECO creator -- On promotion of ECO from the assignment screen to Create
Sketch creator -- When a sketch is created
Drawing Print creator -- When a drawing print is created
Part creator -- On promotion of a part from the assignment screen to Preliminary
Manufacturer Equivalent Part created

Message The attached Manufacturer Equivalent Part has been created.
How Sent When a Manufacturer Equivalent part is created, the trigger TypePartCreation with revision
NotifyComponentEngineerOfMECreate gets fired. The program emxPart:
notiftComponentEngineerOfMEPCreate gets executed.
Property Keys emxEngineeringCentral.IconMail.SubjectMEPCreated and

Associated emxEngineeringCentral.IconMail.MessageMEPCreated
Recipients Component Engineer Role

Notifications Related to Routes
New Task Assignment Notice

Message New Task Assignment Notice
How Sent The trigger PolicyRouteStateInProcessPromoteAction is fired and invokes the method InitiateRoute()
of JPO emxCommonInitiateRoute, which sends the notification to the Owner of the Inbox Task
object.
Property Keys The above method uses the property key

Associated emxFramework.ProgramObject.eServicecommonTriggerEvent.NewTaskAssignmentNotice to get the
subject of the message.
Recipients The task assignee (Owner of the Inbox Task object) receives this notification when a route is started.
Route Completion Notice

Message Route Completion Notice
How Sent The trigger PolicyInboxTaskStateReviewPromoteAction is fired and invokes the method
completeTasks() of JPO emxCommonCompleteTaskBase, which sends the notification to the Owner
of the Route object.

Associated emxFramework.ProgramObject.eServicecommonCompleteTask.SubjectRouteComplete to get the
subject of the message.
Recipients Route creator (Owner of the Route object) - When all tasks have been approved and completed
Task Rejection Notice

Message Task Rejection Notice
How Sent The trigger PolicyInboxTaskStateReviewPromoteAction is fired and invokes the method
completeTasks() of JPO emxCommonCompleteTaskBase, which sends the notification to the Owner
of the Route object.

Associated emxFramework.ProgramObject.eServicecommonCompleteTask.SubjectReject to get the subject of
the message.
Recipients Route creator (Owner of the Route object) receives this notice upon rejection of a task by any user

Index
A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W
A requires ECO 83
access triggers 84
assigning 23 cage code
affected item as unique revision identifier for MEP 43, 44
customizing view 69 change process
application part versioning 42
Also see ENOVIA applications closing search results window 38
approval list 55 company
approval route template naming host 28
default 56 vaults 50
automatically-named business object 62 company ID
automation 71 as unique revision identifier for MEP 43
autonaming 48 Component Engineer
access for role 23
configurable components
B for forms 64
base type objects configuring
for specifications 48 automatically-named objects 62
BOM dynamic UI form components 64
customizing views 69 Engineering Central 19
specifying reference designator properties 46 pages 63
business object using properties file 37
automatically-named 62 using schema 57
Corporate, access for role 25
C
CAD drawing D
lifecycle and policy 85 database schema 14
requires ECO 83 department, setting up 31
triggers 85 Design Engineer
CAD model access for role 24
lifecycle and policy 84 design responsibility 31
91
development part search 39 display of leading zeroes in 45
distribution list 53 specifying as required field 46
documentation 17 specifying length of 45
drawing print specifying properties of 44
lifecycle and policy 82 specifying to be unique value 45
requires ECO 83 form
triggers 82 configurable components 64
dynamic UI form components 64
G
E group, corresponding to department 31
ECO
configuring pages 64
email settings for approval 36
H
lifecycle and policy 74 help, online 17
required for specification 83 history
triggers 74 EBOM History relationship 79
ECR host company, naming 28
lifecycle and policy 72 L
triggers 72
lifecycle
ECR Coordinator
CAD drawing 85
access for role 24
CAD model 84
ECR Evaluator
drawing print 82
access for role 24
ECO 74
ECR summary report 41, 43
ECR 72
ECR supporting document
part 76
lifecycle and policy 87
sketch 87
editing tables
login requirements 22
required columns 69
email settings for ECO approval 36
emxEngineeringCentralNet.properties 37 M
emxFrameworkMappingFile.properties 33 Manufacturing Engineer
Engineering Central access for role 25
automation for 71 manufacturing plant
configuring 19 managing 38, 62, 63
configuring using schema 57 mapping file
setting up 19, 27 updating for new subtypes 33
engineering change MEP
default lists 53 Revision field
ENOVIA applications specifying edit of 44
items in 14 revision identifier for 43
ENOVIA Engineering Central
database schema 14
how related to AEF 14 N
related documentation 17 naming, automatic 62
eService Number Generator 62
eService Object Generator 62
O
online help 17
F organization
find number Also see company.

Organization Manager reviewer route template
access for role 23 default 54
role 22 revision
include development parts 39
Revision field
P specifying edit of in MEP 44
parallel change process 42 revision page for subtypes 51
part role
configuring pages 64 assigning access 23
development 39 summary 23
lifecycle and policy 76 route template
triggers 76 approval 56
part family reviewer 54
Part Family Coordinator
access for role 25 S
part series 49 schema
part specification configuring 57
customizing 66 requirements 22
part versioning 42 search results window action 38
PDF files 17 Senior Design Engineer
Placeholder MEP access for role 24
display of in Equivalents list 44 Senior Manufacturing Engineer
revision identifier for 43 access for role 25
policy serial change process 42
as unique revision identifier for MEP 43 sketch
CAD drawing 85 lifecycle and policy 87
CAD model 84 triggers 87
drawing print 82 specification
ECO 74 base type object generator for 48
ECR 72 requires ECO 83
ECR supporting document 87 subtype
part 76 adding 33
sketch 87 automatic naming of 48
Product Obsolescence Manager keys 51
access for role 25 summary reports, ECO and ECR 41, 43
properties file
for configuring application 37
T
trigger
R CAD drawing 85
readme 17 CAD model 84
reference designator drawing print 82
specifying as required field 47 ECO 74
specifying length of 47 ECR 72
specifying properties of 46 ECR supporting document 87
specifying separator for values of 47 introduction 71
specifying to be unique value 46 Originator attribute 72
reference document part 76
float on release 85 sketch 87
related documentation 17 triggers 71
reviewer list 54
Index 93
U
user guides 17
V
vault 50
awareness 50
W
web form
to configure pages 64

Apasham Jiboj

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Apasham Jiboj

Uploaded by

Copyright:

Available Formats

ENOVIA Engineering

Dassault Systmes, 2001 - 2010

All rights reserved.

This license came from:

2 ENOVIA Engineering Central Administrators Guide

JAVAMAILTM, VERSION 1.3.1

4 ENOVIA Engineering Central Administrators Guide

6 ENOVIA Engineering Central Administrators Guide

8 ENOVIA Engineering Central Administrators Guide

Copyright (C) 1995-1997 Eric Young (eay@mincom.oz.au)

10 ENOVIA Engineering Central Administrators Guide

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

Chapter 2. Roles ........................................................................................................................ 23

Chapter 4. Configuring With the Properties File..................................................................... 37

Chapter 5. Default Lists for Engineering Change ................................................................... 53

Chapter 6. Configuring Using Schema ................................................................................... 57

Chapter 8. Automated Processes............................................................................................. 71

12 ENOVIA Engineering Central Administrators Guide

Before Reading This Guide

Business Process Services

Item For information, refer to:

14 ENOVIA Engineering Central Administrators Guide

Item For information, refer to:

Directories for Shared and Common Components

16 ENOVIA Engineering Central Administrators Guide

All guides in PDF format require Acrobat Reader to view.

18 ENOVIA Engineering Central Administrators Guide

Software Component Setup or Configuration Option Refer to:

20 ENOVIA Engineering Central Administrators Guide

22 ENOVIA Engineering Central Administrators Guide

Component Engineer Responsible for Manufacturer Equivalent Part maintenance.

24 ENOVIA Engineering Central Administrators Guide

28 ENOVIA Engineering Central Administrators Guide

Chapter 3: Setting Up Engineering Central 29

30 ENOVIA Engineering Central Administrators Guide

Chapter 3: Setting Up Engineering Central 31

In Matrix Navigator, open the following business object:

32 ENOVIA Engineering Central Administrators Guide

1. Stop the application server.

Chapter 3: Setting Up Engineering Central 33

34 ENOVIA Engineering Central Administrators Guide

Follow these steps for each client machine:

Chapter 3: Setting Up Engineering Central 35

If the email option is enabled, ECO approval requires MX_SMTP_HOST to be configured.

For Windows, add the following to ematrix.ini:

36 ENOVIA Engineering Central Administrators Guide

38 ENOVIA Engineering Central Administrators Guide

Specify whether FindLike search is case-sensitive or notFind Like search is not

Chapter 4: Configuring With the Properties File 39

40 ENOVIA Engineering Central Administrators Guide

Chapter 4: Configuring With the Properties File 41

Specify whether an ECO is required to release manufacturer equivalent partsThe ECO

42 ENOVIA Engineering Central Administrators Guide

MEP and Placeholder MEP Properties

Chapter 4: Configuring With the Properties File 43

Find Number Properties

44 ENOVIA Engineering Central Administrators Guide

Chapter 4: Configuring With the Properties File 45

Reference Designator Properties

46 ENOVIA Engineering Central Administrators Guide

Chapter 4: Configuring With the Properties File 47

Reference Document Properties

48 ENOVIA Engineering Central Administrators Guide