ENOVIA Program Central Administrator's Guide (V6R2011)

ENOVIA Program Central™
V6R2011x
Administrator’s Guide
Copyright and Trademark Information
© Dassault Systèmes, 2000 - 2009
All rights reserved.

PROPRIETARY RIGHTS NOTICE: This documentation is proprietary property of Dassault Systèmes 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 Systèmes.
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 Systèmes.
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 Systèmes. 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 Systèmes
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 Administrator’s Guide.
Dassault Systèmes 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
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.
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."
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:
W3Cýý SOFTWARE NOTICE AND LICENSE
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:
W3Cýý SOFTWARE 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/
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.
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
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. Introduction ............................................................................................................... 7

Prerequisites .............................................................................................................................. 8
About the ENOVIA Product Line Shared Component................................................................ 8
Related Documentation ............................................................................................................. 8
Application Exchange Framework.............................................................................................. 9
Application Components .......................................................................................................... 10
Use of General ENOVIA Client Applications............................................................................ 11
User Roles ............................................................................................................................... 11
Chapter 2. Configuring ENOVIA Program Central .................................................................. 13

Working with the Properties File ..................................................................................................... 14
Vaults .............................................................................................................................................. 15
Configurable Tables and Forms ...................................................................................................... 16
Configuring Approvals .................................................................................................................... 18
Configuring Properties for Projects................................................................................................. 19
Configuring Financial Cost and Benefit Categories ................................................................. 19
Defining the Content of Project Folders ................................................................................... 21
Defining Access Grants for Project Folders ............................................................................. 21
Allowing Manual Date Entry..................................................................................................... 22
Configuring Project Alerts ........................................................................................................ 22
Configuring Project Access for Groups and Roles................................................................... 25
Showing Project Roles............................................................................................................. 25
Adding Project Subtypes.......................................................................................................... 25
Setting Budget Transaction Thresholds ................................................................................... 26
Configuring Properties for Tasks..................................................................................................... 28
Defining the WBS Task Type Hierarchy ................................................................................... 28
Defining WBS Task Deliverables.............................................................................................. 29
Automatically Completing WBS Tasks when Deliverables are Promoted ................................ 30
Configuring the Percentage Complete for WBS Tasks ............................................................ 31
Configuring the Response Types for a Gate’s Checklist Items ................................................ 31
Configuring Fiscal Year Properties ................................................................................................. 33
Fiscal Year Properties .............................................................................................................. 33
Previous Fiscal Years............................................................................................................... 33
Configuring General Properties ...................................................................................................... 35
Configuring Threshold Values.................................................................................................. 35
Configuring Threshold Colors .................................................................................................. 36
Configuring FTE Value for a Resource .................................................................................... 37
Define the Unit for Resource Request Number of People ....................................................... 37
Defining Alternate Menu Trees................................................................................................. 37
Configuring KavaCharts........................................................................................................... 38
Adding Document Sub-Types .................................................................................................. 38
Configuring Information to be Imported ................................................................................... 39
Customizing Values for Quality Metrics ................................................................................... 41
Customizing Project and WBS Task Promotion Triggers ......................................................... 41
Expanding Objects in the Structure Browser ........................................................................... 43
Table of Contents 3
User External Authentication.................................................................................................... 44
Multiple Timer Commands ....................................................................................................... 44
Properties for Lifecycle Mass Approval .................................................................................... 44
Customizing JPOs .......................................................................................................................... 46
ENOVIA Program Central’s Security Model .................................................................................... 48
Configuring Properties for ENOVIA Product Line ........................................................................... 50
Build Properties........................................................................................................................ 50
Model Properties...................................................................................................................... 50
Slip Days Icon Properties......................................................................................................... 50
Timeline Chart Properties ........................................................................................................ 51
Enterprise Project Management Triggers ....................................................................................... 54
Migrating Dashboard Data .............................................................................................................. 55
Automated Processes ..................................................................................................................... 56
Automation for All Types........................................................................................................... 56
Automation for All Deliverables ................................................................................................ 57
Automation for Project Concept Policy ..................................................................................... 57
Automation for Project Spaces................................................................................................. 58
Automation for WBS Tasks....................................................................................................... 59
Automation for Dates................................................................................................................ 61
Automation for Builds ............................................................................................................... 61
Automation for Product Lines ................................................................................................... 61
Automation for Portfolios .......................................................................................................... 62
Automation for Products........................................................................................................... 62
Automation for Models ............................................................................................................. 63
Automation for Test Execution Objects .................................................................................... 64
Tomcat Server Settings................................................................................................................... 65
Setting the Level of Sub Tasks Allowed ................................................................................... 65
Chapter 3. Setting Up VPLM Access........................................................................................ 67

ENOVIA Program Central and VPLM Objects ................................................................................ 68
Setting Up VPLM Access................................................................................................................ 69
Setup Overview........................................................................................................................ 69
Software Prerequisites ............................................................................................................. 71
VPLM Web Service Discovery ................................................................................................. 71
ENOVIA Web Service Discovery.............................................................................................. 72
Adaplet Deployment and Configuration ................................................................................... 73
Creating the Vault..................................................................................................................... 78
Configuring the VPLM V5 Server Environment........................................................................ 80
Unhiding the VPLM Task.......................................................................................................... 84
Lifecycle Setup......................................................................................................................... 85
ENOVIA Program Central Property Files and Ranges............................................................. 91
Chapter 4. VPLM Objects .......................................................................................................... 95

VPLM Task Behaviors ..................................................................................................................... 96
Overview of VPLM Task Behaviors .......................................................................................... 96
VPLM Instances ....................................................................................................................... 97
VPLM Users in ENOVIA Program Central ............................................................................... 98
VPLM Task Attributes............................................................................................................... 98
VPLM Task Policy..................................................................................................................... 98
Finish to Start VPLM Task Dependency and Inputs................................................................. 99
VPLM Action ............................................................................................................................ 99
4 ENOVIA Program Central Administrator’s Guide

VPLM Status Change ............................................................................................................ 100
Deliverable Behavior .............................................................................................................. 101
Triggers ......................................................................................................................................... 102
VPLM Task Delete ................................................................................................................. 102
VPLM Subtasks of VPLM Tasks ............................................................................................ 102
VPLM Task Promotion from Create to Assign........................................................................ 102
VPLM Task Demotion from Assign to Create......................................................................... 103
VPLM Task Promotion from Active to Review ........................................................................ 103
VPLM Task Demotion from Review to Active ......................................................................... 103
VPLM Task Promotion from Review to Complete .................................................................. 103
VPLM Task Demotion from Complete to Review ................................................................... 104
VPLM Task Change of Owner................................................................................................ 104
VPLM Initiated Actions in ENOVIA Program Central ............................................................. 104
VPLM Custom Objects in ENOVIA Program Central .................................................................... 105
Exposing the VPLM Custom Object....................................................................................... 105
Schema Translations for the VPLM-ENOVIA Program Central.............................................. 107
Introduce CUSTOM Design Action in Business Modeler ....................................................... 109
Chapter 5. Installing and Setting Up Microsoft Project Integration .................................... 111

Installing ENOVIA Microsoft Project Integration Server................................................................ 112
Installers................................................................................................................................. 112
Precautions During Installation on UNIX ............................................................................... 112
Installing ENOVIA Microsoft Project Integration Server on Windows .................................... 113
Post Installation Tasks for UNIX Users .................................................................................. 114
Post Installation Tasks for MS Project .................................................................................... 114
Installing ENOVIA Microsoft Project Integration Client ................................................................. 116
Installing ENOVIA Microsoft Project Integration Client on Windows ...................................... 116
Installing ENOVIA Integration Exchange Framework Client .................................................. 117
Installation Failure .................................................................................................................. 118
Setting Up and Configuring........................................................................................................... 119
Global Configuration Object................................................................................................... 119
Custom Mapping Fields Used................................................................................................ 119
Assigning and Unassigning the Integration............................................................................ 120
Updating Assignments and Assigning GCO .......................................................................... 120
Role Based Access to Integration.......................................................................................... 121
Integration FrameWork Encoding Support............................................................................. 121
Editing ENOVIA Program Central Projects from MS Project ................................................. 121
Support for Project SubTyping ............................................................................................... 121
Chapter 6. PLM Express.......................................................................................................... 123

User Roles .................................................................................................................................... 124
Index ...................................................................................................................... 125
Table of Contents 5
1
Introduction
This Administrator’s guide describes information the System Administrator for the host
company needs to know that is unique to setting up and configuring ENOVIA Program Central.
Most information that Administrators need is common to all ENOVIA products and is described
in the ENOVIA Business Process Services Administrator’s Guide, which is located in
ENOVIA_INSTALL/studio/Apps/Framework/Doc/pdf.
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, or
versions.
In this section:
• Prerequisites
• About the ENOVIA Product Line Shared Component
• Related Documentation
• Application Exchange Framework
• Application Components
• Use of General ENOVIA Client Applications
• User Roles
7
Prerequisites
To perform administrative setup and configuration tasks for ENOVIA Program Central, you need
to understand some or all of the following:
• The concepts, terminology, processes, and procedures in ENOVIA Program Central, as
described in the ENOVIA Program Central User’s Guide.
• The concepts, terminology, processes, and procedures in the Application Exchange
Framework. Refer to the ENOVIA Business Process Services Administrator’s Guide.
• The concepts, terminology, and processes related to the Business Modeler, System
Administration, and/or Matrix Query Language (MQL). See the following documents:
Business Modeler Guide, System Manager Guide, and MQL Guide.
Checklist
Below is a checklist of things you need to do before using ENOVIA Program Central.
1. Change the Company Name in the Administrator Menu to your company name.
2. Add vaults and stores that will be needed. Make sure all are registered.
3. Using the Administration pages, add locations, business units, and employees for your
company.
4. Using the Administration pages, add companies and add at least one person for each company
who is designated as a Company Representative. See the ENOVIA Common Components User
Guide.
5. Define sub-types for WBS tasks and documents. See Defining the WBS Task Type Hierarchy
and Adding Document Sub-Types.
6. Add signature requirements to policies. See Configuring Approvals in Chapter 2.
7. Configure the Cost and Benefit categories you will need. See Configuring Financial Cost and
Benefit Categories.
8. Configure threshold levels for red/green/yellow. See Configuring Threshold Values.
9. Configure any project alerts that you want to use. See Configuring Project Alerts.
10. Determine how you want to automate your business processes. See Customizing Project and
WBS Task Promotion Triggers and Automated Processes.
11. Define your project templates. See the Project Templates chapter in the ENOVIA Program
Central User’s Guide.
About the ENOVIA Product Line Shared Component

ENOVIA Product Line is a required shared component automatically installed with ENOVIA
Program Central. ENOVIA Product Line provides the tools for managing product lines, products,
models, portfolios, builds and other associated objects. Product Line functionality is described in
the ENOVIA Product Line User's Guide.
Related Documentation
In addition to this Administrator’s Guide, the following documents contain instructions for
installing and using ENOVIA Program Central.

Administrator Documentation
• Program Directory
Each version of the application comes with a media that includes the program directory for that
release. The program directory is a website that organizes all the release information for all
Dassault Systèmes products for a given release. It contains information about prerequisites,
installation, licensing, product enhancements, general issues, open issues, documentation
addenda, and closed issues.
• Visio Business Process Chart
This chart, PMCProcessFlow10.vsd, shows the business process flow for the application.
Administrators can use it to plan customizations.
• ENOVIA Business Process Services Administrator’s Guide
This PDF guide is for people in the host company who will configure the application. Some
understanding of ENOVIA products, such as Navigator and Business Modeler is required. It
also describes configuration options for features installed with common components, such as
checkin/checkout, routes, and the default vault preference. These configuration options include
triggers, configurable properties, and URL parameters.
• ENOVIA Business Process Services Schema Reference Guide
This guide describes the schema and data models that underlies the ENOVIA products.
• ENOVIA Live Collaborative Application Development Guide
This guide provides the details required to develop a custom program using the Application
Exchange Framework.
User Documentation
• Online Help
After logging into the application, click the Help (?) tool in the upper right corner of any page
to access online help.
• User Guide
The user guide is in pdf format and requires Acrobat Reader to view.
• ENOVIA Product Line User’s Guide
This guide describes all the features provided by the ENOVIA Product Line shared
component. This guide is available in .pdf format and is also part of online help.
• Common Components Help
This help system describes how to use features that are common across ENOVIA products,
such as profile management, document management, file checkin and checkout, routes, and the
like. Users can access this help system by clicking Common Components Help at the top of
any application help page.
• AEF Help
This help system describes how to use features installed with the Application Exchange
Framework, such as history pages and pages accessed from the toolbar. It also explains how to
navigate through the user interface, such as how to use table pages and the Context Navigator.
Users can access this help system by clicking AEF Help at the top of any application help
page.
Application Exchange Framework

ENOVIA Program Central is supported by a database schema, called the Application Exchange
Framework. The Application Exchange Framework contains all of the administrative objects
Chapter 1: Introduction 9
needed to run ENOVIA Program Central and other ENOVIA products. The framework must be
installed before you can install any ENOVIA application.
The Application Exchange Framework 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 ENOVIA Program Central. Examples of such business objects are projects,
programs, business goals, and WBS tasks.
When you install ENOVIA Program Central, the installation program adds programs and business
objects that make the application work with the framework. For example, business objects are
added that automatically name some types of business objects, such as Documents, and that control
trigger programs that automate business processes. The application also includes JavaServer Pages
(JSPs). JSPs contain HTML fragments, which create the application’s user interface, and Java code
that dynamically updates page content whenever the page is accessed. These JSPs reside in the
application server’s file system.
Application Components
Each ENOVIA application contains the items listed in this table.
Application Components
Item For information, refer to:

Web pages used by the The user guide for the application.
application’s users
Programs specific to the To configure programs and for descriptions of utility trigger programs, see
application “Configuring Using Schema” and “Triggers” in the ENOVIA Live Collaboration
Business Process Services Administrator’s Guide.
For application-specific trigger programs, see the Administrator’s Guide that
accompanies the application. The Administrator’s 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.
Other administrative objects The Administrator Guide for the application.
specific to the application, such as
formats
Business objects that accomplish For general information on how the objects function and how to configure them, see
system-related tasks, such as “Configuring Business Process Services Functions” and “Configuring Using Schema”
objects for automatically-naming in the ENOVIA Live Collaboration Business Process Services Administrator’s Guide.
objects and for executing trigger For a list of the objects included in the application, see the Administrator’s Guide that
programs 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.

The documentation that describes the common components that are installed with Business Process
Services can be found in the ENOVIA_INSTALL\studio\doc directory.
Use of General ENOVIA Client Applications

Some of the instructions in this and other administrator’s 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 User’s Guide and
applications’ administrator’s 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 application 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 application features require data that cannot be created within the ENOVIA
application 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 applications
built with ENOVIA Live Collaboration Studio Customization Toolkit or any programming interface
that does not go through the applications bean layer has the potential to cause undesirable results
within the ENOVIA application data.
User Roles
Each person using ENOVIA Program Central has been assigned one or more roles. The roles a
person is assigned determines what features and objects the person can access. Outlined in the table
Chapter 1: Introduction 11
below are the role assignments that affect a person’s ability to access links within ENOVIA
Program Central.
Role Description Available for:

Project User Basic role needed for any person to access ENOVIA host company employees only
Program Central. Project Users can view programs,
projects and project information they have access to and
routes they have access to. Project Users can create project
concepts. They can edit some of their own profile
information and change their password.
External Same as Project User role but for non-host companies. non-host company employees only
Project User
Project Lead Person responsible for creating and managing projects. host company employees only
External Same as Project Lead role but for non-host companies. non-host company employees only
Project Lead
Program Lead Person responsible for creating and managing programs. host company employees only
External Same as Program Lead role but for non-host companies. non-host company employees only
Program Lead
Project Person responsible for creating and managing project host company employees only
Administrator templates.
External Same as Project Administrator role but for non-host non-host company employees only
Project companies.
Administrator
Business Person responsible for creating and managing business host company employees only
Manager goals.
Because only the host company can create business goals,
there is no equivalent role for non-host companies.
Organization Automatically assigned to any person designated as a Both host and non-host company
Manager Company Representative and automatically removed if a employees.
person’s Company Representative designation is removed.
This role cannot be added and removed itself and is only
added and removed as the Company Representative
designation is added and removed.
Company Representatives can add, remove, and edit
information about their company, business units, locations,
and employees. Company Representatives for the host
company can also add companies and view and edit
information for other companies.

2
Configuring ENOVIA Program
Central
This section describes the ways in which you can configure ENOVIA Program Central.
In this section:
• Working with the Properties File
• Vaults
• Configurable Tables and Forms
• Configuring Approvals
• Configuring Properties for Projects
• Configuring Properties for Tasks
• Configuring General Properties
• Customizing JPOs
• ENOVIA Program Central’s Security Model
• Configuring Properties for ENOVIA Product Line
• Enterprise Project Management Triggers
• Migrating Dashboard Data
• Automated Processes
13
Working with the Properties File
The file called emxProgramCentral.properties contains properties that let you configure features.
All properties files are located in the ENOVIA_INSTALL/properties directory. This directory is
located in the staging directory under the RMI installation directory. After making changes to any
properties file, you must restart the application server for the changes to take effect. In a J2EE
environment, you must also run the warutil and deploy the archive file. You should also save
backups of any properties file that you configure.
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.
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 <STAGING>/
ENOVIA_INSTALL/properties 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 the Properties Files” chapter in the Business Process Services
Administrator's Guide for instructions on defining the name of your custom properties file in the
emxSystem.properties file.

Vaults
Project Vault
When Project Leads create a project, they can specify a vault for the project and can choose any
company vault. This is where the project and many items in the project will be stored.
Vaults and Searches

By default, searches are performed across all primary and secondary vaults for the user’s company.
During each basic search, users can choose to search in a specific company vault or in all company
local vaults. (Advanced searches are always executed across all company vaults.) Narrowing a
search to specific vaults speeds up the search but can lead to unexpected results if the user isn’t sure
where objects are stored.
If users typically want to search in one vault or all local vaults, they can set a global preference by
clicking Tools > Preferences on the main toolbar. This preference also affects the default vault
filter for summary table pages, such as Projects, Programs, and Project Templates.
Chapter 2: Configuring ENOVIA Program Central 15

Configurable Tables and Forms
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 Application Development Guide and the Business Modeler Guide.
Configurable Tables
• Assessment Summary
• Assignee Summary
• Benefit Summary
• Bookmark Summary
• Business Goal Summary
• Cost Summary
• Dashboards Summary
• Deliverables Summary
• Dependencies
• Edit All Members
• Edit Benefits
• Edit Costs
• Edit Member
• Financial List
• Folders Summary
• Program Summary
• Project Member Summary
• Project Summary
• Project Template Questions
• Project Template Summary
• Quality Metrics
• Quality Summary
• Questions Summary
• Risk Summary
• RPN Summary
• WBS Task Summary
Configurable Forms
• Create Assessment
• Create Bookmarks

• Create Business Goal
• Create Dashboard Collection
• Create Folder
• Create Folder Project Template
• Create Member
• Create Program
• Create Project Concept
• Create Project Template
• Create Quality
• Create Question
• Create Risk
• Create RPN
• Create WBS Task
• Edit Assessment
• Edit Bookmarks
• Edit Business Goal
• Edit Folder
• Edit Program
• Edit Project
• Edit Project Concept
• Edit Project Template
• Edit Quality
• Edit Question
• Edit Risk
• Edit RPN
• Submit Effort
• View Assessment Details
• View Bookmark Details
• View Business Goal Details
• View Folder Details
• View Program Details
• View Project Concept Details
• View Project Details
• View Project Template Details
• View Quality Details
• View Question Details
• View Risk Details
• View RPN

Configuring Approvals
Several types of objects have an Approvals category in their category list, including deliverables,
projects, project concepts, WBS tasks, and documents. The Approvals page lists all the signature
requirements that must be fulfilled before the item can be promoted through its lifecycle. These
requirements include signature requirements from the object’s policy and blocking routes. By
default, none of ENOVIA Program Central’s policies have signatures so the only items listed here
are blocking routes. You can add signature requirements to policies using Business Modeler. If you
do not add signature requirements, you may want to remove the Approvals category from the object
type’s tree menu.

Configuring Properties for Projects
This section describes settings for projects.
In this section:
• Configuring Financial Cost and Benefit Categories
• Defining the Content of Project Folders
• Defining Access Grants for Project Folders
• Allowing Manual Date Entry
• Configuring Project Alerts
• Configuring Project Access for Groups and Roles
• Showing Project Roles
• Adding Project Subtypes
Configuring Financial Cost and Benefit Categories

The Financial Cost Category and Financial Benefit Categories are business object instances used to
store the template cost and benefit categories. The template categories are the categories users can
choose to add to project budgets.
The following diagram shows an example of how business objects need to be related to define the
financial categories and their hierarchy.
To define the template categories

1. Log into Matrix Navigator.

2. For each category, create a business object named Financial Cost Category or Financial
Benefit Category using the following information:
Type: Financial Cost Category or Financial Benefit Category
Name: <NAME>
Revision:
Policy: Financial Categories
Vault: eService Administration
3. Change ownership to the role Project Lead.
4. Connect the top level categories to the company using the Company Financial Categories
relationship.
5. Connect subcategories to the top level categories using the Financial Sub Categories
relationship.
Like all onscreen text in the application, you configure the on screen names for categories using
string resource files.
To configure names for categories

1. Open emxProgramCentralStringResource.properties file.
2. For existing objects, change the right side of the key that corresponds to the category you want
to change. Don’t ever change the left side of the key. Changing it will cause a JSP to have
compilation errors.
For example, you could change:
emxProgramCentral.Common.Rents_and_Lease=Rents and Leases
to:
emxProgramCentral.Common.Rents_and_Leases=Rents

3. Add new keys and values for new objects.
Defining the Content of Project Folders

By default, only documents can be added to project folders but you can configure the system so
other types can be added.
To add types for project folder content

1. Log into Business Modeler as a user with business administrator privileges.
2. Find the Vaulted Documents Rev2 relationship and open it for editing.
3. Add the type to the To end of the relationship.
4. If you want the system to grant access to the object for all users who have access to the folder,
add the Access Grantor role to the policy that governs the type and add the type to a system
property as described in Defining Access Grants for Project Folders.
5. Restart the server.
6. Verify the type you added can be added to folders. From the category list for a project, click
Folders. Then click Add Project Content. From the Search page, click the ... button for the
Type field. The types you defined should be listed in the Chooser.
Defining Access Grants for Project Folders

The following property in emxSystem.properties lets you define the object types for which access
grants should be made when the objects are added to project folders.
emxFramework.FolderContentTypesThatTypesRequireGrants=type_Document,ty
pe_Part,type_RequestForQuote,type_Quotation,type_Package
The property applies to objects added to ENOVIA Program Central project folders. The schema
name for folder object is Workspace Vault. ENOVIA Program Central only grants for document
types and their sub-types are made. The property lets you specify the types for which grants should
be made. To add types, enter the symbolic type names separated by commas. Note that for the
accesses to be granted for a type, the type’s policy must have the Access Grantor role with the
appropriate permissions. The property also accepts All, which means grants will be made for all
types added to folders (again, the policy must support granting with the Access Grantor role).
The following types which can be added to project folders do not support this functionality (setting
those types in this property will not correctly grant access to objects added to a project folder):
Product Structure Reference, Functional Reference, Flow Reference, Logical Reference, System
Reference, System Type Reference, and DMU Validation.
The following property works in conjunction with the above property. When set to true, the access
grants for folders apply to any sub-type of a type defined in the above property. So any sub-type
defined for the Document type will be included in the access grants. When set to false, the grants
are made only for the specific types listed in the above property.
emxFramework.IncludeSubTypesForGrants=true
If you only allow documents and their subtypes to be added to folders and you want grants for those
objects, do not change the default values for the above properties. If you want to add parts, RFQs,

quotations, or packages to folders but don’t want accesses to be granted to them, remove them from
the first property. If you want grants to be made for additional object types, add the types to the first
property. Make sure new types are added to the Vaulted Documents Rev2 relationship as described
in Defining the Content of Project Folders.
Allowing Manual Date Entry

When users specify a date, they choose the date from a calendar popup. This prevents users from
having to remember the correct date format but can take more time than manually entering the date.
To allow users to manually enter dates, set the following property to TRUE.
emxProgramCentral.EnableManualDateEntry=FALSE
The property only affects high-use pages: the Create Project page, WBS Modify page, and the Risk
Edit page. When the property is FALSE, only the calendar can be used. When TRUE, users can use
the calendar or enter dates manually.
The date format allowed is based on the browser’s locale setting. Javascript validations are used to
verify format and will display correct format if user enters incorrect format.
If manual date entry is enabled, ENOVIA Program Central only supports the MEDIUM date
format, which is set in emxSystem.properties. The setting is
emxFramework.DateTime.DisplayFormat = MEDIUM. The MEDIUM format is Mmm
dd, yyyy, as in Dec 12, 2003.
For information on how ENOVIA products handle dates and date formats, see the Application
Exchange Framework User Guide.
Configuring Project Alerts

ENOVIA Program Central lets Project Leads and owners set up “Alert Preferences” settings
regarding tasks that are not yet completed. Project Alert Preferences are set on the Project Basic
Information page. This feature, called “Project Alert”, requires a timer servlet, which is installed
with the Collaboration Server but is commented out. Follow these steps to uncomment the servlet
and the properties that it uses.
Enabling the Timer Servlet

1. Open the web.xml file, which is located in the ematrixwarutil directory.
2. Uncomment the following lines by removing the () from the beginning and end. If
these lines aren’t in the file, add them.
<servlet id="Servlet_20">
<servlet-name>TimerServlet</servlet-name>
<servlet-class>com.matrixone.servlet.TimerServlet</servlet-class>
<load-on-startup>2</load-on-startup>
</servlet>
<servlet-mapping id="ServletMapping_17">
<servlet-name>TimerServlet</servlet-name>
<url-pattern>/servlet/timer/*</url-pattern>
</servlet-mapping>
...
<context-param id="ContextParam_15">
<param-name>ematrix.timer.agent</param-name>
<param-value></param-value>

</context-param>
<param-name>ematrix.timer.agent.key</param-name>
<param-value></param-value>
</context-param>
<param-name>ematrix.timer.interval</param-name>
<param-value>84600</param-value>
</context-param>
<param-name>ematrix.timer.command</param-name>
<param-value>execute program emxProjectSpace -method
performTaskEscalation</param-value>
</context-param>
If you had to enter the lines manually, make sure there isn’t already a servlet id=”Servlet_21” or
“ServletMapping_17” in the web.xml file. If there are, use the next number available for each id.
These numbers are simply identifiers, so it doesn’t matter what they are but they can’t be
duplicated in the file.
3. Enter username, password, and timer interval values between <param-value> and
<param-value> tags in the uncommented code in web.xml.
For the ematrix.timer.agent property, enter the username the servlet should use to set context in
MQL. This should be a system admin user. ematrix.timer.agent.key should be set to the
password for this user.
For the ematrix.timer.interval property, specify how often you want the system to check to see
if task due notifications need to be sent. The interval is in seconds. We recommend setting the
timer interval to be one day - 86400 - because this program should be kicked off on a daily
basis.
Keep in mind that the Project Lead/Owner specifies how long before or after the task due times
that the system should send the notification. The length can be set in days and so this timing
works in conjunction with the timer interval. For example, if the Project Lead/Owner sets up
the notifications to be sent one day before the task due time and the timer interval is configured
to check every day, the notifications should be sent when one day before due date has been
reached. The Recurrence Interval value set in Project Alert Preferences tells the system
whether to send additional notifications.
4. Save the web.xml file.
5. Run the warutil to create the archive files with the updated file included.
Setting Up Multiple TimerCommands on one Server

Each Timer command must have its own Interval and command line entry in web.xml.
For example, to set up the Alert Feature and Notification Feature on one server, use the following
commands in web.xml:
ematrix.timer.interval=84600
ematrix.timer.command=execute program emxProjectSpace
-method performTaskEscalation
ematrix.timer.interval1=21600
ematrix.timer.command1=execute program emxWorkspaceTimer -method
performTaskEscalation

Configuring Alert Reminder Options
A set of properties in emxProgramCentral.properties let you define the values that are available in
the Send Reminder and Recurrence Interval drop-down lists on the Alert Preferences page.
The first property, emxProgramCentral.ProjectDoNotSendReminder, defines an arbitrary
number for the do not send setting. This number must be equal to the
emxProgramCentral.ProjectSendReminder.DoNotSendReminder value. There should be no reason
to change either number.
By default, the Send Reminder list contains 1, 2, 3, 4, and 5 days before the due date, on the due
date, do not send reminder, and 1, 2, 3, 4, and 5 days after the due date. To change the values,
change the number to the right of the property key. For example, if you want to provide an option
for sending a reminder 10 days before the due date, change the -5 to -10 to the right of
emxProgramCentral.ProjectSendReminder.5DaysBefore.
Similarly, you can change the values in the Recurrence Interval list by changing the numbers in the
Recurrence Interval properties.
# Turn off sending notification at run-time

emxProgramCentral.ProjectDoNotSendReminder=99
# Send Reminder
# value pair: text displayed and its corresponding integer value
# The value following "Do not send reminder" should match with
emxProgramCentral.ProjectDoNotSendReminder's
emxProgramCentral.ProjectSendReminder =
emxProgramCentral.ProjectSendReminder.5DaysBefore, -5, \
emxProgramCentral.ProjectSendReminder.1DayBefore, -1, \
emxProgramCentral.ProjectSendReminder.OnDueDate, 0, \
emxProgramCentral.ProjectSendReminder.DoNotSendReminder, 99, \
emxProgramCentral.ProjectSendReminder.1DayAfter, 1, \
emxProgramCentral.ProjectSendReminder.2DaysAfter, 2, \
emxProgramCentral.ProjectSendReminder.5DaysAfter, 5
# Recurrence Interval
# value pair: text displayed and its corresponding integer value
emxProgramCentral.ProjectRecurrenceInterval =
emxProgramCentral.ProjectRecurrenceInterval.DoNotSendAdditionalReminde
rs, 0, \
emxProgramCentral.ProjectRecurrenceInterval.EachDay, 1, \
emxProgramCentral.ProjectRecurrenceInterval.Every2ndDay, 2, \
emxProgramCentral.ProjectRecurrenceInterval.Every3rdDay, 3, \
emxProgramCentral.ProjectRecurrenceInterval.Every4thDay, 4, \
emxProgramCentral.ProjectRecurrenceInterval.Every5thDay, 5

Configuring Project Access for Groups and Roles
By default, Project Leads and owners can add any group or role in the system as a member of a
project. When a group or role is a member, users assigned to the group or role can access the
project by searching but the project is not listed on their Projects list.
The following properties in emxProgramCentral.properties let you define which roles and groups
can be added as project members.
# Comma separated list of initial Roles that will be displayed when

adding
# role as a project member. Choices "All" "None" or a valid role
eServiceProgramCentral.SearchableRoles =All
# Comma separated list of initial Groups that will be displayed when
adding
# Group as a project member. Choices "All" "None" or a valid group
eServiceProgramCentral.SearchableGroups =All
• To allow any non-hidden role or group to be added as a member, enter All for the
corresponding property.
• To specify a list of groups or roles, enter a comma-separated list of symbolic names. Make sure
the role/group is registered and is defined in the string resource files.
• To disable the Add Group/Add Role links, specify None for the corresponding property.
Showing Project Roles

The property emxProgramCentral.showRDORoles controls whether only PMC-specific
roles are shown for the Project Role attribute on ENOVIA Program Central pages. When set to
false (the default value), the attribute “Project Role” will display only PMC-specific values. All
attributes starting with “role_” will be ignored.
If set to true, the attribute drop-down displays:
• The PMC-specific attributes ranges
• All role_ range values already defined in the attribute
• All Organization Roles that have been assigned to the user when connected to the Company.
Adding Project Subtypes

This section describes these procedures for creating a project subtype:
• creating a project subtype—the new subtype is derived from a project space object.
• creating a policy for the subtype—the subtype will be governed by the policy for the type.
• registering the subtype and policy—the symbolic name for the subtype administrative object
must be registered.
To create a project subtype

1. Log in to Business Modeler.
2. Choose Object > Find.
3. In the Find Objects window, select Type and enter Project Space in the Name field text box.
4. Click the Find button.
You see the Project Space type in the Business window.

5. Right-click on the Project Space type and select Clone.
You see the Clone-Type Project Space window.
6. In the Name text box, enter the new project subtype name and then click Create.
7. In the Edit Type window, click the ellipse button next to the Derived From text field.
8. In the Type Chooser, uncheck the Top Level check box and enter Project Space in the Name
field.
9. Select the type Project Space and click OK.
10. In the Edit Type window, click the Edit button.
The new project subtype is created and displayed in the Business window.
To create a policy for the subtype

1. In the Business window, choose Object > Find.
2. In the Find Objects window, select Policy and enter Project Space in the Name field text box.
3. Click the Find button.
You see the Project Space policy in the Business window.
4. Right-click on the policy Project Space type and select Clone.
You see the Clone-Policy Project Space window
5. Enter the new project subtype name in the Name text box and click Create.
You see the Edit Policy window.
6. Click on the Governed Types tab.
7. Select Type [subtype name].
8. In the Edit Policy window, click the Edit button.
The policy for the project subtype is created and displayed in the Business window.
To register the subtype and policy

1. Log in to ENOVIA Program Central with Business Admin privileges.
2. From the global toolbar, click > Admin Tools > Property Registration > Admin Types.
You see the Admin Type Property Registration page.
3. From the Admin Type drop-down, select Type.
4. Select Project Space from the Registered Admins list box and select the new project subtype
from the Un- Registered Admins list box. Then click the Retrieve Registration button.
5. Change the Symbolic Name text field to type_[subtype name].
6. Select the Installed Date from the Installed Date calendar field.
7. Click the Create Registration button.
You see the new subtype under the Registered Admins list box.
Setting Budget Transaction Thresholds

Threshold variance colors enable a user to see differences between Actual and Estimated amounts
in a project budget. The following properties can be configured to set the threshold levels. These
settings are applicable for both Estimate and Actual views.

Color Property Threshold % Meaning
Red emxProgramCentral.Budget.Failure > than 110% If estimates are met in this range,
it is indicated in Red font.
Yellow emxProgramCentral.Budget.PartialFailure 105% to 110% If estimates are met in this range,
it is indicated in Yellow font.
This indicates a failure but a
condition still in control.
Green emxProgramCentral.Budget.Success <= 95% Green indicates that the
estimates have exceeded
expectations.
Black emxProgramCentral.Budget.PartialSuccess 95% to 105% Indicates a partial success in
meeting estimates.

Configuring Properties for Tasks
This section describes settings for tasks.
In this section:
• Defining the WBS Task Type Hierarchy
• Defining WBS Task Deliverables
• Automatically Completing WBS Tasks when Deliverables are Promoted
• Configuring the Percentage Complete for WBS Tasks
Defining the WBS Task Type Hierarchy

ENOVIA Program Central uses the type hierarchy defined for the Task Management type to
determine the rules behind the creation of the WBS structure. For example, some customers may
want to ensure that a project can only have “Phase” as parent tasks or summary tasks. By default,
there is only one sub-type and it is called “Task”.
When importing a project from an ASCII file, only the standard task type can be used. The ASCII
import does not currently recognize additional task types.
Here are examples of two task hierarchies.
If you create a task under the project node with Structure 1, the task types you have available
include Task and Phase. If you create a child task of Phase, you can choose SubPhase1 or
SubPhase 2 as the task type. If, however, you create a child of SubPhase 2, which does not have
any children, the system lets you select from a list of SubPhase 3 and any of its siblings that also
include SubPhase 1.
If you created a task under the project node with Structure 2, the task types available include Task,
SubTask1, Phase, SubPhase1, SubPhase 1.1 and SubPhase 2. When you create a child of any of
these tasks, since they do not have children, the parent and all its siblings are displayed.
To add additional task types to the WBS structure

2. Create a new type that is derived from Task Management.
Sub-types called Milestone and Phase are common customizations.
The Status attribute from type Task should be added to any type derived from Task Management.
3. Assign attributes to the new sub-type as needed. It automatically inherits all attributes of Task
Management.

4. Assign the new sub-type to the Project Task policy or to a custom policy.
To get the same access model used for the Project Task policy, create any new custom policies
by cloning the existing Project Task policy.
All policies for WBS task types must have a state registered as state_Complete for filters and
triggers.
5. Extract emxCommonMappingFile.properties from common.jar and edit the file to
contain the new subtypes.
For example, if adding a new subtype called Phase, the line in
emxCommonMappingFile.properties would look like:
type_Phase=com.enovia.apps.common.Task
6. Using Matrix Navigator, register the new sub-type and any new policy. Use the eService
Change Administration Property wizard.
To use the wizard, you must log into Navigator as a person assigned to the Administration
Manager role. For details on registering new schema, see the “Configuring Schema” section in
the Business Process Services Administrator's Guide.
7. Add the new sub-type (and any new policies) to the Framework string resource file:
a ) Open emxFrameworkStringResource.properties, located in ENOVIA_INSTALL/
properties.
b ) Add a key and value for the new type using the format
emxFramework.Type.NAME=DISPLAY_NAME. For example:
emxFramework.Type.Milestone=Milestone
c ) Repeat these steps for each language and new type/policy, as needed.
8. Rebuild the archive files and restart the server.
9. Verify the new sub-type is listed in ENOVIA Program Central by adding a new WBS task to a
project. The Task Type drop-down list should include all new sub-types. If multiple policies
exist, the New Task page includes a policy drop-down list.
Defining WBS Task Deliverables

By default, WBS task deliverables can be documents and types appropriate for use with ENOVIA
X-BOM Engineering, such as parts, ECRs, and CAD drawings. You can configure the system so
users can add other types and add an association that gives the project owner access to see task
deliverables. You can also remove some of these types. The types you define are available in the
Chooser when users search for project content to add as a task deliverable.
To add types for WBS task deliverables

2. Find the Task Deliverable relationship and open it for editing.
3. To add a type, add the type to the To end of the relationship.
4. Open the corresponding policy for the type.
For every state in the policy:
a ) Edit the state.
b ) Add the association Public Inherited to the state.

c ) Edit the Access for Public Inherited by selecting Read, Checkout, and Show access; in the
Filter field type:
to[Task Deliverable].from.current.access[read,show] == true
6. Verify the types you defined can be added as a deliverable. From the category list for a WBS
task, click Deliverables. Then click Add Project Content. From the Search page, click the ...
button for the Type field. The types you defined should be listed in the Chooser.
Now that the type is available as a deliverable, you can configure a trigger so the WBS task is
auto-promoted to Complete when the deliverable is promoted. See Automatically Completing
WBS Tasks when Deliverables are Promoted.
To remove types for WBS task deliverables

2. Find the Task Deliverable relationship and open it for editing.
3. Remove the type from the To end of the relationship.
4. Open the corresponding policy for the type.
For every state in the policy:
a ) Edit the state.
b ) Remove the association Public Inherited.
Automatically Completing WBS Tasks when Deliverables are Promoted

The application includes a trigger that automatically promotes a WBS task to Review when its
deliverable is completed. For Enterprise Project Management, the expected result would be to
promote the task to Complete. Since the out-of-the-box functionality promotes the task to Review,
if you want to change the default functionality, you must write custom code.
By default, this trigger is not implemented for any policy. Use these instructions to implement the
trigger. The trigger is:
Type: eService Trigger Program Parameters
Name: DeliverablesPromoteTaskComplete
Rev: SetStateComplete
To configure a trigger to complete a WBS task when a deliverable is completed

2. Find the policy that governs the type that is defined as a deliverable.
For example, suppose ECRs are defined as WBS task deliverables (they are by default, see
Defining the Content of Project Folders). You want to configure a trigger so when an ECR that
is added as a deliverable is promoted to Complete, the WBS task is also promoted. To do this,
you would find the policy that govern ECRs.
3. Add the trigger as a promote action trigger on the state the promotion from which should cause
the trigger to fire. The Action should be emxTriggerManager and the Input should be
DeliverablesPromoteTaskComplete.

If the state already has an action trigger executed by the trigger manager, add a space after the
name of the first trigger, in the Input field, and enter DeliverablesPromoteTaskComplete.
4. If there are multiple triggers, update the eService Sequence Number for the eService Trigger
Program Parameters objects so the triggers fire in the correct sequence. Do this in Matrix
Navigator.
5. Make sure the eService Trigger Program Parameters object is Active.
Configuring the Percentage Complete for WBS Tasks

Users with editing access for a WBS task assign a % complete to indicate progress on completing
the task. You can define the values available in the % Complete drop-down list.
To define the % complete values

1. Open the ENOVIA_INSTALL/properties/emxComponents.properties file.
2. Add or remove percentages in the following property.
# Task Percentages
emxProgramCentral.TaskPercentages = 0.0%, \
10.0%, \
20.0%, \
25.0%, \
30.0%, \
40.0%, \
50.0%, \
60.0%, \
70.0%, \
75.0%, \
80.0%, \
90.0%, \
100.0%
Configuring the Response Types for a Gate’s Checklist Items

Response types set the allowable responses to a checklist item, which is used in evaluating a project
gate.
The following properties are defined in emxProgramCentral.properties:
emxProgramCentral.Checklist.Item.TotalResponseTypes=3
emxProgramCentral.Checklist.Item.ResponseType1.Options=Yes|No
emxProgramCentral.Checklist.Item.ResponseType2.Options=Make|Buy
emxProgramCentral.Checklist.Item.ResponseType3.Options=Approved|Condit
ionally_Approved|Not_Approved
emxProgramCentral.Checklist.Item.ResponseType1.IsMultiSelect=true
emxProgramCentral.Checklist.Item.ResponseType2.IsMultiSelect=false
emxProgramCentral.Checklist.Item.ResponseType3.IsMultiSelect=true
The following properties are defined in emxProgramCentralStringResource.properties:
emxProgramCentral.Checklist.Item.ResponseType.Approve=Approve
emxProgramCentral.Checklist.Item.ResponseType.ConditionallyApproved=Co
nditional_Approved
emxProgramCentral.Checklist.Item.ResponseType.NotApproved=Not_Approved

emxProgramCentral.Checklist.Item.ResponseType.Yes=Yes
emxProgramCentral.Checklist.Item.ResponseType.No=No
emxProgramCentral.Checklist.Item.ResponseType.Make=Make
emxProgramCentral.Checklist.Item.ResponseType.Buy=Buy
To add any other response type, use these entries below:
emxProgramCentral.Checklist.Item.ReponseType<N>.Options
emxProgramCentral.Checklist.Item.ReponseType<N>.IsMultiSelect.
To define the corresponding string resource entries, use:
emxProgramCentral.Checklist.Item.ResponseType.<the option name>

Configuring Fiscal Year Properties
Several features in ENOVIA Program Central take advantage of a system-configurable fiscal

year and fiscal year timeline. Features which use the fiscal year include timesheet reports, and
the financial data of budget and forecasting.
In this section:
• Fiscal Year Properties
• Previous Fiscal Years
Fiscal Year Properties

The following properties in the emxProgramCentral.properties file configure aspects of the fiscal
year:
emxProgramCentral.CompanyStandards.FiscalYear.StartMonth=10
This property setting defines the start month to be considered for the fiscal year. In the above
example, October is defined as the start of the Fiscal Year.
The month is a numeric value and corresponds to 1 for January, 2 for February, etc.
emxProgramCentral.CompanyStandards.FiscalYear.StartMonth.StartDate=3
This property setting defines the date from which the fiscal month of the fiscal year should start. In
above example, October 3rd is defined as the start date for the fiscal month.
It is general, this is the date of the day defined by the property
emxProgramCentral.CompanyStandards.FiscalYear.StartDayOfWeek. However, there
is no validation for this rule.
The start date is a numeric value and corresponds to the date of a day in the month. The start date
must be a day in the fiscal month.
emxProgramCentral.CompanyStandards.FiscalYear.WeeksPerMonth=4,4,5,4,4,5,4,4,5,4,5,5
This property defines the number of weeks combined to be considered as a month. In above
example, in a fiscal year which starts from October 3rd, 4 weeks will be considered to be part of
October, 4 weeks comprises November, 5 weeks comprises of December, and so on.
This is a comma-separated set of 12 numeric values, which all sum to 52 (the total weeks in a year).
emxProgramCentral.CompanyStandards.FiscalYear.StartDayOfWeek=1
This property defines the start day of the week. In above example, Sunday (1) is configured as the
start day of the week and hence Saturday will be the end of the week.
This is a numeric value from 1 to 7, where 1=Sunday, 2=Monday, 3=Tuesday, 4=Wednesday,
5=Thursday, 6=Friday and 7=Saturday.
Previous Fiscal Years

Fiscal year property settings are configured typically once in a financial year. However, it is also
important to preserve configurations for last years. The properties values described above can be
overridden by a set of property keys explicitly defined for a fiscal year, as shown in the examples

below, for the year 2009. If year-specific properties are not defined, the system will use the default
configuration settings defined above.
emxProgramCentral.CompanyStandards.FiscalYear.2009.StartMonth=4
emxProgramCentral.CompanyStandards.FiscalYear.2009.StartMonth.StartDate=1
emxProgramCentral.CompanyStandards.FiscalYear.2009.WeeksPerMonth=4,4,5,4,4,5,4,4,5,4,4,5
emxProgramCentral.CompanyStandards.FiscalYear.2009.StartDayOfWeek=1
In these examples, the properties are defined explicitly for fiscal year 2009. For year 2010, an
administrator is expected to define 2010-specific keys, or the system will use the default properties.
Including the year as a parameter is a way in which configured settings can be preserved for each
year.

Configuring General Properties
This section describes settings for items used across ENOVIA Program Central.
In this section:
• Configuring Threshold Values
• Configuring Threshold Colors
• Configuring FTE Value for a Resource
• Defining Alternate Menu Trees
• Configuring KavaCharts
• Adding Document Sub-Types
• Configuring Information to be Imported
• Customizing Values for Quality Metrics
• Customizing Project and WBS Task Promotion Triggers
• Expanding Objects in the Structure Browser
• User External Authentication
• Multiple Timer Commands
• Properties for Lifecycle Mass Approval
Configuring Threshold Values

You can configure the values that define the point at which an item’s status is green, yellow, or red.
You can configure threshold values for risk RPN (Risk Priority Numbers), slip days, and cost
ratios. All configurations are made in emxProgramCentral.properties, which is in
ENOVIA_INSTALL/properties.
For instructions on configuring the colors for these thresholds, see Color Definitions.
Risk RPN Thresholds

The following entries in the emxProgramCentral.properties file determine the point at which a
project is in a good (green), cautious (yellow), or risky (red) state based upon the RPN value. This
provides a visual change in the state of the project and is displayed on the Risk summary page and
the project dashboards.
# RPN,Slip,Cost Ratio threshold values
eServiceApplicationProgramCentralRPNThreshold.Yellow = 7
eServiceApplicationProgramCentralRPNThreshold.Red = 16
eServiceApplicationProgramCentralRPNThreshold.Max = 25
The yellow and red properties accept any number from 0 to the Max value. If the Max is changed
from 25, the ranges for the Risk Impact and Risk Probability attributes should also be changed. By
default, they are 1, 2, 3, 4, and 5 so the maximum RPN can never be greater than 25 (highest
probability multiplied by the highest impact).
The RPN status flags are defined as follows:
• Green=0 through (Yellow value –1)

• Yellow=(Yellow value) through (Red value – 1)
• Red=(Red value) through 25
Slip Thresholds
The following entries in the emxProgramCentral.properties file determine the point at which the
slip values display as green, yellow, or red on the WBS Summary and Project Summary pages.
eServiceApplicationProgramCentral.SlipThresholdGreenYellow=0
eServiceApplicationProgramCentral.SlipThresholdYellowRed=5
The SlipThresholdGreenYellow property defines the number of days prior to the Due Date that the
status flag will display as yellow. The SlipThresholdYellowRed property defines the number of
days prior to the Due Date that the flag displays as red. Project and WBS color displays Red when
project or task is not complete by estimated due date.
Cost Ratio Thresholds

The following entries in the emxProgramCentral.properties file determine the point at which the
Cost Ratio value on the project dashboard displays as green, yellow, or red.
eServiceApplicationProgramCentral.CostRatioThresholdGreenYellow=100
eServiceApplicationProgramCentral.CostRatioThresholdYellowRed=110
The ratio calculation is Actual Cost / Planned Cost and is green if no Actual Costs exist or if the
ratio is below the CostRatioThresholdGreenYellow value. It’s yellow if the ratio is between
CostRatioThresholdGreenYellow and CostRatioThresholdYellowRed, and red if over
CostRatioThresholdYellowRed.
Configuring Threshold Colors

Threshold colors are configurable in ENOVIA Program Central. Some default color definitions are
provided in emxProgramCentral.properties. This section provides the information you need to
define the color settings for your own configuration and specify them in the properties file.
Color Definitions
Colors are defined with a # followed by sequence of three hexadecimal numbers with values
ranging from 00 - FF (values 0-255 in decimal). Each of the hexadecimal numbers defines the color
value for one of the color components. The definition is in this format:
#RRGGBB
where RR is the value of the red color component, GG is the value of the green color component,
and BB is the value of the blue color component.
The combination of the three components determines the final color. A value of 00 is the darkest
shade and a value of FF is the lightest shade for a color component. For example, a value of
#000000 represents pure black, and a value of #FFFFFF represents pure white. A value of FF for
each of the three color components with 00 for the other two components will result in pure red,
pure green, and pure blue, respectively.

Defining Colors in the Properties File
Colors are defined in the properties file. The lines listed below are included in the
emxProgramCentral.properties file to set the color defaults. You may change the values as
explained above to set the colors to satisfy your preferences.
Open the emxProgramCentral.properties file. Change the values to change the color.
These colors are in Hex numbers.
eServiceApplicationProgramCentral.SlipThreshholdColor1=008000
eServiceApplicationProgramCentral.SlipThreshholdColor2=FFCC00
eServiceApplicationProgramCentral.SlipThreshholdColor3=FF0000
eServiceApplicationProgramCentral.RiskThreshholdColor1=008000
eServiceApplicationProgramCentral.RiskThreshholdColor2=FFCC00
eServiceApplicationProgramCentral.RiskThreshholdColor3=FF0000
eServiceApplicationProgramCentral.CostRatioThreshholdColor1=008000
eServiceApplicationProgramCentral.CostRatioThreshholdColor2=FFCC00
eServiceApplicationProgramCentral.CostRatioThreshholdColor3=FF0000
For example, change:

eServiceApplicationProgramCentral.SlipThreshholdColor1=008000 to
eServiceApplicationProgramCentral.SlipThreshholdColor1=FFFFFF
Configuring FTE Value for a Resource

The Resource Loading Report shows the full time equivalent (FTE) for the selected resource over
the time period specified for the report. The value of the FTE can be configured in the properties
file.
The emxProgramCentral.properties file contains the property
emxProgramCentral.ResourceRequest.FTE which can be set for the desired FTE
value. The default value is 1.
Define the Unit for Resource Request Number of People

This setting defines resource requests in either hours or FTE for each project phase or time line
interval displayed for a resource plan.
emxProgramCentral.ResourcePlan.NumberofPeopleUnit=Hours
When set to Hours, the system stores all the resource request number of people value in Hours
units. This enables users to toggle between Hours and Cost when working with resource plans. The
user will be able to add and edit number of people values only in Hours.
emxProgramCentral.ResourcePlan.NumberofPeopleUnit=FTE
This will allow system to store all the resource request number of people value in FTE units. This
enables users to toggle between FTE and Cost when working with resource plans. The user will be
able to add and edit number of people values only in FTE.
Defining Alternate Menu Trees

You can define alternate tree menu objects for common types. These properties define tree menu
objects to be used for types that are also used in other ENOVIA products. Types used in multiple

applications, referred to as common types, include persons, companies, documents, and locations.
The alternate tree menus let each application define its own tree categories for these common types.
When a user views details for one of these common objects from ENOVIA Program Central, the
system uses the tree menu object listed here instead of the standard tree menu object. (The standard
tree menu object for a type has the same name as the symbolic name for the type. For example, the
standard tree menu for meetings is named type_Meeting). If you want to configure the trees for
these types, as described in the ENOVIA Live Collaboration Application Development Guide, make
sure you edit the menu object named here. The naming convention for the alternate tree properties
and their values is:
eServiceSuiteProgramCentral.emxTreeAlternateMenuName.SYMBOLIC_NAME_OF_
TYPE=PMCSYMBOLIC_NAME_OF_TYPE.
Here are a few examples of ENOVIA ENOVIA Program Central’s alternate category list
properties. See the properties file for a complete list.
eServiceSuiteProgramCentral.emxTreeAlternateMenuName.type_Message=PMCt
ype_Message
eServiceSuiteProgramCentral.emxTreeAlternateMenuName.type_Location=PMC
type_Location
eServiceSuiteProgramCentral.emxTreeAlternateMenuName.type_Person=PMCty
pe_Person
Configuring KavaCharts
ENOVIA Program Central uses KavaCharts for Dashboard Metrics. KavaCharts can be created on
the server-side, as well as on the client-side. The client-side creation is done using applets.
ENOVIA Program Central only uses the server-side implementation. There are API's for a variety
of charts like Piecharts, Barcharts, Linecharts, etc. The required parameters like no. of items, color,
font, etc. need to be passed in. Images created can be saved in a specific location or displayed in the
HTML page. Display of KavaCharts requires server access to xterm.
If you intend to customize or extend the functionality of KavaCharts beyond the software delivered
with ENOVIA Program Central, you must purchase a KavaChart development license. See the
Visual Engineering homepage at www.ve.com.
Use these properties in emxProgramCentral.properties to change the fonts used on KavaCharts.

#Kava Chart Fonts.
eServiceProgramCentral.kcTitleFont = Arial
eServiceProgramCentral.kcLavelFont = Monospaced
eServiceProgramCentral.kcLegendFont = TimesRoman
Adding Document Sub-Types

When users add a file to ENOVIA Program Central, they can choose the type of document. All
sub-types of the Document type are listed. By default, there are no sub-types but you can use the
instructions below to add sub-types. Adding document sub-types lets:
• users categorize documents
• you apply different business rules to documents by assigning different policies to each
sub-type
• you assign different formats to sub-types
To add a new document sub-type


2. Create a new type that is derived from Document.
3. Assign attributes to the new sub-type as needed. It automatically inherits all attributes of
Document.
4. Assign the new sub-type to the Document policy or to a custom policy. The policy must have
at least one format.
To get the same access model used for the Document policy, create any new custom policies
by cloning the existing Document policy.
5. Using Matrix Navigator, register the new sub-type and any new policy. Use the eService
Change Administration Property wizard.
To use the wizard, you must log into Navigator as a person assigned to the Administration
Manager role. For details on registering new schema, see the Application Exchange
Framework Administrator Guide.
6. Add the new sub-type (and any new policies) to the Framework string resource file:
a ) Open emxFrameworkStringResource.properties, located in ENOVIA_INSTALL/
properties.
b ) Add a key and value for the new type using the format
emxFramework.Type.NAME=DISPLAY_NAME. For example:
emxFramework.Type.Spec_Document=Spec Document
c ) Repeat these steps for each language and new type/policy, as needed.
7. Rebuild the archive files and restart the server.
8. Verify the new sub-type is listed in ENOVIA Program Central by uploading an external file.
The new sub-type should be listed in the Type Chooser and the Upload Dialog should display
the sub-type specific policy selection and attributes.
Configuring Information to be Imported

Users can import information from .csv files (ASCII files with fields separated by commas) to
create projects and their associated WBS structures, risks and RPNs, quality and quality metrics,
and financials (project budgets). The attributes to be imported and the order in which they should
be imported are defined in the emxProgramCentral.properties file. These properties are listed
below. For example the key, eServiceProgramCentral.Import.Risk defines the list of attributes
expected in the csv file for a risk, in the order the attributes should be entered. The only restriction
is that the first field must always be the type.
You can add attributes to be imported for a type by adding it to the corresponding import property.
The attribute must be added to the type and registered. Validation is not performed on custom
attributes. If the attribute added is not a standard attribute shipped with the Framework, an entry
may need to be added to the emxFrameworkStringResource.properties files so the
internationalization of the attribute names will continue to work. Similarly, you can remove
attributes that you do not want to import.
Dates used in importing and exporting must be in the mm/dd/yy format. For instructions on how to
import each type, see the user guide or online help.
# Comma delimited list of attributes to be read from ascii import
# They are displayed in the order they are entered.
eServiceProgramCentral.Import.Risk = Type, \
Name, \
Title, \

Description, \
Risk Visibility, \
Estimated Start Date, \
Estimated End Date, \
Actual Start Date, \
Actual End Date, \
Risk Type, \
Measure of Success, \
Abatement Plan
eServiceProgramCentral.Import.RPN = Type, \
Name, \
Risk Impact, \
Risk Probability, \
Risk RPN Value, \
Effective Date, \
Status
eServiceProgramCentral.Import.Quality = Type, \
Name, \
Quality Type, \
Problem Statement, \
Operational Definition, \
Defect Definition, \
Goal, \
Comments, \
Opportunity, \
Out Of Bounds, \
Constraints
eServiceProgramCentral.Import.DiscreteMetric = Type, \
Name, \
Metric Source, \
Defects Per Million Opportunities, \
Defects Per Unit, \
Sigma, \
Comments
eServiceProgramCentral.Import.ContinuousMetric = Type, \
Name, \
Metric Source, \
Mean, \
Standard Deviation, \
Upper Specification Limit, \
Lower Specification Limit, \
Sigma, \
Comments
eServiceProgramCentral.Import.FinancialItem = Type, \
Planned Spread Option, \

Estimated Spread Option, \
Actual Spread Option, \
Benefit Interval, \
Benefit Interval Start Date, \
Benefit Interval End Date, \
Cost Interval, \
Cost Interval Start Date, \
Cost Interval End Date
eServiceProgramCentral.Import.CostItem = Type, \
Name, \
Ledger Account Number, \
Planned Cost, \
Estimated Cost, \
Actual Cost, \
Notes
eServiceProgramCentral.Import.BenefitItem = Type, \
Name, \
Ledger Account Number, \
Planned Benefit, \
Estimated Benefit, \
Actual Benefit, \
Notes
Customizing Values for Quality Metrics

You can specify the values that display in the drop-down list for the Source field on the Create
Quality Metric page.
To do this, use the following property in the emxProgramCentral.properties file:
emxProgramCentral.MetricSource.Ranges=Goal,Predicted,Allocated,Measured,
Controlled
The drop-down list will display these values in the order listed in the above property.
Customizing Project and WBS Task Promotion Triggers

Summary WBS tasks cannot be promoted to Review or Complete unless all children tasks are
Complete. Sometimes there is a need to promote a parent task and demote all subtasks as Complete.
To support this, the system administrator could disable the promote checks. However, disabling the
triggers allows the parent to be promoted, but leaves children in their current state. The following
describes triggers that support a more flexible process management.
Active State Promote Check

By default, a WBS task cannot be promoted past the Active state unless all subtasks, including
optional and mandatory, are at least in the Review state. Similarly, a project cannot be promoted
from Active unless all tasks are at least in Review.
These are check triggers for the project space and WBS task. Both triggers are configured using
eService Trigger Program Parameters objects, as per standard AEF triggers:

• The name for the project space trigger object is PolicyProjectSpaceStateActivePromoteCheck
and the revision is CheckChildrenStates.
• The name for the task trigger object is PolicyProjectTaskStateActivePromoteCheck and the
revision is CheckChildrenStates.
There are 3 changes you can make for these triggers:
• Disable the triggers by making the business object Inactive.
• Require that all children be in the Complete state instead of the Review state for the project/
task to be promoted from Active. To do this, edit the attributes for the trigger business object
and change the eService Program Argument 3 value to state_Complete.
• Require that only Mandatory tasks be in Review (or Complete, if configured that way) for the
parent to be promoted. To do this, edit the attributes for the trigger business object and change
the eService Program Argument 4 to True.
Review State Promote Check

By default, a WBS task cannot be promoted past the Review state unless all subtasks, including
optional and mandatory, are at least in the Complete state. Similarly, a project cannot be promoted
from Review unless all tasks are at least in Complete.
These are check triggers for the project space and WBS task. Both triggers are configured using
eService Trigger Program Parameters objects, as per standard AEF triggers:
• The name for the project space trigger object is PolicyProjectSpaceStateReviewPromoteCheck
and the revision is CheckChildrenStates.
• The name for the task trigger object is PolicyProjectTaskStateReviewPromoteCheck and the
revision is CheckChildrenStates.
There are 3 changes you can make for these triggers:
• Disable the triggers by making the business object Inactive.
• Require that all children be in the Review state instead of the Complete state for the project/
task to be promoted from Review. To do this, edit the attributes for the trigger business object
and change the eService Program Argument 3 value to state_Review.
• Require that only Mandatory tasks be in Complete for the parent to be promoted. To do this,
edit the attributes for the trigger business object and change the eService Program Argument 4
to True.
Task Percent Rollup

Task Percent Complete reflects the amount of work completed while the task is in the Active state.
A task can take many days to complete. The task owner/assignee is encouraged to update the
percentage on a daily basis to provide actual progress in completing the task. While task assignees
maintain their percentages, these updates are rolled up to higher-level tasks. Several triggers are
needed to maintain “percent complete” for parent tasks. For example, when a task percentage is
updated, the parent task will reflect a new percentage based on the current state of its subtasks.
In the following plan, everything is set to 0 percent.
Project A Duration Estimated Estimated % Complete

Start Finish
Task 1 3 days 12/20/03 12/22/03 0%

Subtask a 2 days 12/20/03 12/21/03 0%
Subtask b 3 days 12/20/03 12/22/03 0%
When Task 3 is completed, notice that the percent complete for the parent reflects 60%.
Project A Duration Estimated Estimated % Complete

Start Finish
Task 1 3 days 12/20/03 12/22/03 60%
Subtask a 2 days 12/20/03 12/21/03 0%
Subtask b 3 days 12/20/03 12/22/03 100%
The rollup of percentage is calculated in the following way:

Sum of (% Complete * Duration) for all subtasks divided by the sum of subtask days.
The parent rolled up percentage is rounded down to the nearest task complete percentage value (as
defined in the emxProgramCentra.TaskPercentages property). So if the percent is 55 for the parent,
the parent will reflect 50. This ensures the value is in the range of the drop-down list in the WBS
edit page.
This calculation is automatic and cannot be turned off. You can change the JPO method to change
the logic and/or turn off the feature. The emxTask JPO includes a default method called
calculatePercentComplete.
Expanding Objects in the Structure Browser

The following properties in emxProgramCentral.properties can be configured to control the
expansion of objects in the search results pages of the structure browser:
##----------Relationships and Types for indented table expands --------------##

eServiceProgramCentral.IndentedTable.GeneralTypes=type_Route,type_ECR,type_Part,type_Drawi
ngPrint,type_CADModel,type_CADDrawing,type_PartSpecification,\
type_Sketch,type_Markup,type_EBOMMarkup,type_PartMaster,type_MPN,type_COM
PLIANCEPART,type_Model,type_ProductLine,\
type_ENOVIA_VPMProductRootClass,type_VPMBOProductInstance,type_VPMBOPartI
nstance
eServiceProgramCentral.IndentedTable.GeneralRelationships=relationship_ObjectRoute,relatio
nship_ECOChangeRequestInput,relationship_MakeObsolete,relationship_NewPartPartRevision,\
relationship_NewSpecificationSpecificationRevision,relationship_ECRSuppor
tingDocument,relationship_RequestPartObsolescence,\
relationship_RequestPartRevision,relationship_RequestSpecificationRevisio
n,relationship_ReferenceDocument,relationship_MBOM,\
relationship_ManufacturerEquivalent,relationship_EBOM,relationship_PartSp
ecification,relationship_CBOM,relationship_ProductLineModels,relationship
_SubProductLines,\
relationship_ENOVIA_VPMPRCtoPartIRel,relationship_ENOVIA_VPMPartItoPartIR
el,relationship_ENOVIA_VPMPRCtoDocRel,relationship_ENOVIA_VPMPartItoDocRe
l,\
relationship_ENOVIA_VPMPRCtoProdIRel
eServiceProgramCentral.IndentedTable.GeneralDirection=Both

eServiceProgramCentral.IndentedTable.DeliverableTypes=type_Route,type_ECR,type_Part,type_D
rawingPrint,type_CADModel,type_CADDrawing,type_PartSpecification,\
type_Sketch,type_Markup,type_EBOMMarkup,type_PartMaster,type_MPN,type_COM
PLIANCEPART,type_Model,type_ProductLine,\
type_ENOVIA_VPMProductRootClass,type_VPMBOProductInstance,type_VPMBOPartI
nstance
eServiceProgramCentral.IndentedTable.DeliverableRelationships=relationship_ObjectRoute,rel
ationship_ECOChangeRequestInput,relationship_MakeObsolete,relationship_NewPartPartRevision
,\
relationship_NewSpecificationSpecificationRevision,relationship_ECRSuppor
tingDocument,relationship_RequestPartObsolescence,\
relationship_RequestPartRevision,relationship_RequestSpecificationRevisio
n,relationship_ReferenceDocument,relationship_MBOM,\
relationship_ManufacturerEquivalent,relationship_EBOM,relationship_PartSp
ecification,relationship_CBOM,relationship_ProductLineModels,relationship
_SubProductLines,\
relationship_ENOVIA_VPMPRCtoPartIRel,relationship_ENOVIA_VPMPartItoPartIR
el,relationship_ENOVIA_VPMPRCtoDocRel,relationship_ENOVIA_VPMPartItoDocRe
l,\
relationship_ENOVIA_VPMPRCtoProdIRel
eServiceProgramCentral.IndentedTable.DeliverableDirection=Both
User External Authentication

To set up external authentication for users accessing ENOVIA products, see “Login Behavior
When External Authentication is Used” in the ENOVIA Live Collaboration Installation Guide.
If you are using Site Minder or Clear Trust for user authentication, custom JPOs and special APIs
must be set up in order to authenticate users accessing lifecycles, routes, and FDA approvals. To
enable custom JPO authentication, see “Enabling External Authentication” in the ENOVIA Live
Collaboration Installation Guide.
Multiple Timer Commands

To Set Up Multiple Timer Commands on one Server
Each Timer command must have its own Interval and command line entry in web.xml.
For example, to set up the ENOVIA Program Central Alert and Notification features on one server,
use the following commands in web.xml:
ematrix.timer.interval=84600
ematrix.timer.command=execute program emxProjectSpace -method
ematrix.timer.interval1=21600
ematrix.timer.command1=execute program emxWorkspaceTimer -method
Properties for Lifecycle Mass Approval

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_Book.RelatedObjects.Connections=
relationship_HasDocuments
LifecycleMassApproval.type_Book.RelatedObjects.ConnectionDirection=to
This example would allow a user to make sure that all Documents to be included in a book have
been approved prior to promoting the Book to the Active state, the above properties would show all
tasks/signature requirements for the Documents that have been added to the Book.
See the Application Exchange Framework User’s Guide to see how lifecycle mass approval works.

Customizing JPOs
Base JPOs:
• Contains all code required by the application.
• Should never be modified.
• Upgraded at each product release.
• Name includes “Base” such as emxProjectSpaceBase.
JPO Extender:
• Exists only to extend the Base JPO.
• Available for Customization.
• Not touched during product upgrades.
• Named emx{AdminName}, such as emxProjectSpace.
List of Base JPOs:
• emxMemberRelationshipBase
• emxProgramBase
• emxProjectAccessListBase
• emxProjectConceptBase
• emxProjectSpaceBase
• emxProjectTemplateBase
• emxQualityBase
• emxQuestionBase
• emxRiskBase
• emxTaskBase
• emxAssessmentBase
• emxFinancialItemBase
• emxFinancialTemplateCategoryBase
• emxProjectAssessmentRelationshipBase
• emxProjectFinancialItemRelationshipBase
• emxProjectManagementBase
• emxProgramBusinessGoalBase
List of Extender JPOs:
• emxMemberRelationship
• emxProgram
• emxProjectAccessList
• emxProjectConcept
• emxProjectSpace
• emxProjectTemplate
• emxQuality
• emxQuestion

• emxRisk
• emxTask
• emxAssessment
• emxFinancialItem
• emxFinancialTemplateCategory
• emxProjectAssessmentRelationship
• emxProjectFinancialItemRelationship
• emxProjectManagement
• emxProgramBusinessGoal

ENOVIA Program Central’s Security Model
ENOVIA Program Central’s security model is as follows. For more information, see “Controlling
Visibility” in the user’s guide.
1. Role Based Menus
2. Project Visibility
3. Project Ownership
4. Project Membership
5. Task Assignee
Role Based Menus

The application uses roles to display menus, submenus, and links on pages. These roles are
assigned to command and menu objects in Business Modeler. For example, the Organization
Manager role, assigned to Company Representatives, is given access to links for adding business
units, adding people, and editing the company profile.
You can also control access to menus and links using access masks, select expressions, and JPOs.
For information, see the ENOVIA Live Collaboration Application Development Guide.
Project Visibility
When creating a project, the owner has the ability to define the project as visible to all company
employees or visible only to members. If visibility is set to Company, non-members must search
for the project to access it. Projects are only listed on a person’s Projects page if the person is a
member of the project (an individual member, not a member by virtue of being assigned to a role or
group that is a member).
Project Ownership
By default, the person who creates the project is the project owner. The project can be owned by
only one user. The project owner has all access, including the ability to delete and delegate the
project (change ownership).
The project owner can assign other project members as leads. Project Leads have the same access
as project owner with the exception of being able to change ownership and delete the project. This
attribute is called Project Access and it exists internally in the data model under the type Project
Member. This attribute cannot be deleted or modified. The range values on this attribute are used to
control project membership and security.
Project Membership
Project Membership is the next level of security. Being a member of a project means:
• the project is listed on your Projects page (unless you are a member only because you are
assigned to a role or group that is a member)
• you can be assigned a project role that lets you edit certain aspects of the project; for example,
Financial Reviewers can edit the project budget

• for projects with Member visibility, you and other members are the only people who can
access project information
Task Assignee
A task can be assigned to a non-member of the project or to any member of the project. A task
assignee can:
• View their task and the task parent.
• Add and remove subtasks.
• Create routes on their tasks.
• Delegate their assignment to someone else.
• Cannot delete the top level task assigned to them.

Configuring Properties for ENOVIA Product Line
To change any of the properties for ENOVIA Product Line, open the emxProductLine.properties
file for editing.
In this section:
• Build Properties
• Model Properties
• Slip Days Icon Properties
• Timeline Chart Properties
Build Properties
• Default Build Type—Use this property to set the default build type that is used during build
creation. Valid values are Hardware Build or Software Build. The default is Hardware Build.
emxProductLine.Build.CreateBuild.DefaultType=Hardware Build
• Maximum Number of Builds Generated—Use this property to set the maximum number of
builds that can be generated from a single build creation. This property limits the maximum
value that can be entered in the Number of Builds field in the Create Build page. The Default is
100.
emxProductLine.Build.CreateBuild.NumberLimit=100
Model Properties
• Product Prefix—Use this property to set the maximum number of alphanumeric characters
that can be used for the Product Prefix attribute. This attribute is defined for a model and
inherited by those products and product configurations related to that model. The default is 3.
emxProductLine.Model.ProductPrefixLength=3
Slip Days Icon Properties

• Specify maximum filed length—Specifies the maximum length of a field that is permissible
for any field in the create dialogs, especially used for the object “Name” fields.
emxProduct.MAX_FIELD_LENGTH = 100
• Specify Icon Red Days—The number of days which determines the threshold value to display
the slip days icon on the builds list page. If the actual build date is greater than the planned
build date by this number of days, it displays the red icon.
emxProduct.Build.IconRedDays = 5
• Specify Icon Green Days—The number of days which determines the threshold value to
display the slip days icon on the builds list page. If the actual build date is less than the planned
build date by this number of days, it displays the green icon.
emxProduct.Build.IconGreenDays = -2
For any case in between these it displays the yellow icon.

Timeline Chart Properties
The timeline chart is obtained using the timeline functionality provided by the Framework. In this
chart, the user can configure the fields that are displayed for roadmap objects (for example,
Product) and milestone objects (for example, Task) using settings in the
emxProductLine.properties file as explained below.
Out of the box timeline functionality is provided for products and tasks but you can configure these
settings to get the timeline chart for some other objects.
• Milestone Relationship—This is the symbolic name of the relationship that is used to retrieve
all the milestones for the roadmap object. By default, it is set to
relationship_RoadmapTasks.
emxProduct.Roadmap.Milestone.Relationship
• Milestone Type Attribute—This is the attribute on the milestone relationship that is used to
retrieve the milestone type information. By default, it is set to
attribute_MilestoneType.
emxProduct.Roadmap.Milestone.Title
• Additional Title for the roadmap object—This setting is used to display the additional label
information for roadmap object of a particular type.
emxProduct.Roadmap.Object.Details.Labels.<type symbolic name>
By default, we are displaying the marketing name of the product on the timeline chart hence
the above setting will look like:
emxProduct.Roadmap.Object.Details.Labels.type_Products =
$<[attribute_MarketingName]>
• Details of the roadmap object to be displayed as tool tip above the image—These settings
are used to display the details of the roadmap object of each type as tool tip over the object
image. If more than one field is to be displayed then it is specified using a comma separated
string.
emxProduct.Roadmap.Object.Details.<type symbolic name>
emxProduct.Roadmap.Object.DetailLabels.<type symbolic name>
The first setting is used to determine the actual field value to be displayed. The second setting
is used to determine the label for the field. If any attribute is to be displayed, then the symbolic
name of the attribute must be specified. The label must be a key in the
emxProductStringResource.properties file, to support internationalization.
By default, we are displaying the description of the product as a tool tip, hence the above
settings will look like:
emxProduct.Roadmap.Object.Details.type_Products = description
emxProduct.Roadmap.Object.DetailLabels.type_Products =
emxFramework.Basic.Description
• Details of the milestones to be displayed as tool tip above the milestone image—These
settings are used to display the details of the milestone object of each type as tool-tip over the
milestone image. If more than one field is to be displayed then it is specified using a comma
separated string.
emxProduct.Roadmap.Milestone.Details.<type symbolic name>
emxProduct.Roadmap.Milestone.DetailLabels.<type symbolic name>
The first setting is used to determine the actual field value to be displayed while the second
setting is used to determine the label for the field. If any attribute is to be displayed then the
symbolic name of the attribute has to be specified. The label must be a key in the application
string-resource file, to support internationalization.

The two words startdate and finishdate are reserved for this setting and if these
words are specified in then the estimated start date and end date of the milestone object will be
displayed. But if the milestone is finished then actual start date and actual end date will be
displayed. The following attributes of the milestone object will be used for fetching these
fields:
– Task Estimated Start Date
– Task Estimated End Date
– Task Actual Start Date
– Task Actual End Date
By default, the start date and end date of the task are displayed in the timeline chart hence this
setting will look like:
emxProduct.Roadmap.Milestone.Details.type_Task = startdate, enddate
emxProduct.Roadmap.Milestone.Labels.type_Task = startdate,enddate
• Support subtypes of task in the product roadmap—To support subtypes of task in the
product roadmap, you need to add a property for each subtype. For example, suppose you add
subtypes of Task Management called Phase and Milestone. You would then need to add the
following entries to the ENOVIA Product Line properties file:
emxProduct.Roadmap.Milestone.Details.type_Phase=startDate,finishDate
emxProduct.Roadmap.Milestone.DetailLabels.type_Phase=startDate,FinishD
ate
emxProduct.Roadmap.Milestone.Details.type_Milestone=startDate,finishDa
te
emxProduct.Roadmap.Milestone.DetailLabels.type_Milestone=startDate,fin
ishDate
• Default image for the roadmap object—This setting is used to specify the default image to
be used for the roadmap object if there is no primary image set for the object.
emxProduct.Roadmap.Object.Image.Default
By default, this is set to “${COMMON_DIR}/images/utilUndefinedImage.gif”.
• Image icon to be displayed for the different types of milestones—This setting is used to
specify the display image for each milestone type. The different milestone types are nothing
but the range values of the attributes specified in the setting
emxProduct.Roadmap.Milestone.Title. For each range value one setting has to be added in the
property file.
emxProduct.Roadmap.Milestone.Icon.<Range Value(Replacing space with
_)>
By default, we are using the attribute Milestone Type. So the above settings will look like as
follows:
emxProduct.Roadmap.Milestone.Icon.Start=${COMMON_DIR}/images/
iconStatusStarted.gif
emxProduct.Roadmap.Milestone.Icon.Launch=${COMMON_DIR}/images/
iconStatusLaunched.gif
emxProduct.Roadmap.Milestone.Icon.Milestone=${COMMON_DIR}/images/
iconStatusVendorReviewed.gif
emxProduct.Roadmap.Milestone.Icon.End=${COMMON_DIR}/images/
iconStatusFinished.gif
• Date preference attribute—This setting is used to specify the symbolic name of the attribute
on the roadmap relationship that is used to retrieve the date preference (Start or Finish) to be
used to plot the particular milestone. By default, it is set to attribute_Date.
emxProduct.Roadmap.Milestone.Date
The following two settings are used to specify the range values of the above attribute:

emxProduct.Roadmap.Milestone.Date.Start = Start
emxProduct.Roadmap.Milestone.Date.End = End
• Primary Image for the Product—In the product timeline chart, the primary image associated
with the product is displayed along with its marketing name. If there is no image for the
product then a default image is displayed as defined in the property file.
To display the primary image, the image icon associated with primary image object is
retrieved. The method createPrimaryImage () has been added to emxImageBase.java to set the
icon of the image object. This method is invoked when the image file is checked into the image
object.
This method first checks out the image file into the temporary location.
After the file is checked out, first it is converted to a thumbnail using a third part tool called
Image Magick and then the thumbnail is set as icon of the image object. If Image Magick is not
installed then the same file is set as image icon.
If the generation of the image object icon is not required, then you can disable this
functionality with the following steps:
Comment call to the method createPrimaryImage() in method checkin() of
emxImageBase.java.
Compile the JPOs emxImageBase.java and emxImage.java.

Enterprise Project Management Triggers
This section lists triggers that are installed with Enterprise Project Management.
Trigger Name Trigger Information

T: eService Trigger Program Parameter The following are the Program trigger parameters:Program:
emxICMethod:
N: AttributeICURLModifyCheck triggerCheckModifyOnICUrlAttributeConstructor argument:
${OBJECTID}Constructor argument:
R: triggerCheckModifyOnICUrlAttribute ${ATTRVALUE}Constructor argument:
${NEWATTRVALUE}Sequence: 1Description:Check trigger
on event Modify of attribute "IC URL" in Type "IC Document"
and "IC Folder"; On modification, trigger invokes the
"unsubscribe" and "subscribe" Synchronicity Server Web
service methods will be called based on the context to keep
the IC Objects in sync with the ENOVIA Live Collaboration
server.
N: AttributeICProjectURLModifyCheck emxICMethod:
R: triggerCheckModifyOnICProjectUrlAttribute triggerCheckModifyOnICProjectUrlAttributeConstructor
argument: ${OBJECTID}Constructor argument:
${ATTRVALUE}Constructor argument:
${NEWATTRVALUE}Sequence: 1Description:Check trigger
on event Modify of attribute "IC Project URL" in Type
"Project Space"; On modification, trigger will force the modify
check trigger of "IC URL" attribute of associated IC objects.
N: TypeICDeleteCheck emxICMethod: triggerICDeleteCheckConstructor argument:
R: triggerCheckDeleteOnIC ${OBJECTID}Sequence: 1Description:Delete Check trigger
on type "IC Document" and "IC Folder". On deletion, trigger
invokes the "unsubscribe" Synchronicity Server Web service
method to keep the IC Objects in ENOVIA Live Collaboration
server in sync with the Sync Server.
N: StandardICPromoteAction emxICMethod: triggerActionPromoteStandardICConstructor
R: triggerActionPromoteStandardIC argument : ${OBJECTID} Constructor argument : ${
NEXTSTATE } Sequence: 1Description:Promote Action
trigger invokes the "tag" IC Server Web service method by
verifying the Global Environment value to keep the IC
Server's Deliverable file in sync with ENOVIA Live
Collaboration server and promotes its associated Tasks to
Complete state based on Completion State Attribute Value
of Task Deliverable Relationship

Migrating Dashboard Data
If you are upgrading to ENOVIA Program Central from a pre-10.5 version of the application,
which was called Program Central, you must migrate all dashboards from the pre-10.5 format
(unhidden Sets that begin with "dashboard-") to the new 10.5 format (hidden Sets that begin with
".dashboard-").
The migration process involves executing a method of a JPO with a parameter that specifies a
directory on the local disk. When the JPO method executes, all dashboards in the old format are
converted to the new format. The dashboards are renamed and copied to a log file specified by the
directory parameter in the JPO argument.
To migrate dashboards
From MQL, type:
execute program emxProgramCentralUtil -method migrateDashboards "parameter1";
where “parameter1” is the directory name where the log file will be written.
Migration Logic
1. The JPO method migrateDashboards retrieves all the Person objects in the database.
2. For each person object, the dashboards are retrieved. This is the list of sets for each person that
begins with "dashboard-".
3. Each set is cloned to begin with ".dashboard-" so that the dashboards are converted to the new
format.
4. Dashboards in the old format are then deleted from the database.
5. Each of the converted dashboards is then written to a file named
convertedDashboardList.log. This file is created under the directory specified in the
method argument when executing the JPO. The file contains entries in the following format:
<username>:<old dashboard name>

Automated Processes
This section lists the triggers that need to be configured to support this release of the application.
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]
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 object’s attributes also contain the specific method to call and
constructor arguments.
For more information about the Trigger Manager and eService Trigger Program Parameters
objects, see the Business Process Services Administrator's Guide.
In this section:
• Automation for All Types
• Automation for All Deliverables
• Automation for Project Concept Policy
• Automation for Project Spaces
• Automation for WBS Tasks
• Automation for Dates
• Automation for Builds
• Automation for Product Lines
• Automation for Portfolios
• Automation for Products
• Automation for Models
• Automation for Test Execution Objects
Automation for All Types

All types in the framework have two triggers that are used in ENOVIA Program Central. These
triggers maintain 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 Trigger Program and JPO Method
Parameters
TypeAllCreateAction emxcommonSetOriginator_if
PopulateOriginator attribute_Originator
Automation for All Deliverables

ENOVIA Program Central’s project schedule is dynamic and is an integral part of the business
process. As deliverables are completed, the associated WBS Task needs to be completed. The
following is a generic promote action trigger that can be placed on any of the deliverable policies,
such as EC Part, ECR Standard, Documents for the purpose of promoting the associated WBS Task
to completion. Deliverables are often of types ECR, ECO, Document, Part, etc.
eService Trigger Program Trigger Program and JPO Description of action

Parameters Method
DeliverablesPromoteTaskComplete triggerSetParentTaskToCompleteAction Promotes the task to complete when the

SetStatComplete emxTask $(OBJECTID) assigned deliverable is promoted to a specific
state.
Promote Action triggers are placed on the
previous state.
Automation for Project Concept Policy

All triggers used in the project concept policy are described in this section.
For more information about automation on Routes or Inbox Tasks please refer to the Application

Parameters Method
PolicyProjectConceptStateReviewPromoteAction emxProgramTriggerApproveConceptProject.tcl When the Project Concept is approved, the

ApproveConceptProject project is converted to a standard project. The
type is changed from Project Concept to Project
Space. The policy is changed from Project
Concept to Project Space.
PolicyProjectConceptStateConceptPromoteCheck eServiceCheckRoutes_if.tcl This trigger prevents the object from moving to

CheckRouteStatus the next state until all related State BGased
Routes are in the complete state.
PolicyProjectConceptStatePrototypePromoteCheck eServiceCheckRoutes)_if.tcl This trigger prevents the object from moving to

Routes are in the complete state
PolicyProjectConceptStateReviewPromoteCheck eServiceCheckRoutes_if.tcl This trigger prevents the object from moving to

Routes are in the complete state

Automation for Project Spaces
Project Spaces are governed by the Project Space Policy. All triggers used in this policy are
described in this section.

Parameters Method
PolicyProjectSpaceStateCreatePromoteCheck eServiceCheckRoutes_if.tcl Prevents the object from moving to the next

CheckRouteStatus state until all related State Based Routes are in
the complete state.
This Promotion Check Trigger has been placed
on all the states of the Project Task policy. For
information on this trigger, refer to the
Application Exchange Framework User Guide
PolicyProjectSpaceStateCreatePromoteAction triggerPromoteAction When a parent task is promoted from state

AutoMoveChildren emxTask Create to state Assign, all related children are
The following setting must be configured on the also promoted to state Assigned. A parameter
web server startup to activate the recursive setting on this trigger allows you to check for
trigger feature. The following setting must be the assignment of tasks. By setting parameter
set to “signature’ if you want this trigger to setting to “false” the system first checks to see
work recursively. if the child task is assigned. If the child task is
set not assigned, the child task is not promoted. To
MX_TRIGGER_RECURSION_DETECTION turn this check off, change the parameter setting
=signature to “true”.
PolicyProjectSpaceStateActiveDemoteAction triggerModifyAttributes Demotes the parent task back to state “Active”

ModifyAttributeActuals emxTask if one of its children is demoted out of state
“Complete” or “Review”.
PolicyProjectSpaceStateActiveDemoteCheck triggerDemoteCheck Prevents the project space from being demoted

CheckDemoteOfSummarySpace emxTask out of its “Active” state, if all its children tasks
have past the “Active” state or are on the
“Active” state. The user must demote the parent
first to allow for children to be demoted.
PolicyProjectSpaceStateActivePromote triggerSetPercentageCompletion
Action,setPercentageComplete emxTask
PolicyProjectSpaceStateAssignPromoteCheck eServiceCheckRoutes_if.tcl Prevents the object from moving to the next

CheckRouteStatus state until all related state based routes are in the
complete state.
PolicyProjectSpaceStateAssignPromoteAction Action,emxTask When a parent task is promoted from state

AutoMoveParent,triggerPromote Create to state Assign, all related children are
also promoted to state Assigned. A parameter
setting on this trigger allows you to check for
the assignment of tasks. By setting parameter
setting to “false” the system first checks to see
if the child task is assigned. If the child task is
not assigned, the child task is not promoted. To
turn this check off, change the parameter setting
to “true”.
PolicyProjectSpaceStateAssignPromoteAction TriggerModifyAttributes
ModifyAttributeActuals emxTask
PolicyProjectSpaceStateAssignDemoteAction TriggerDemoteAction
PolicyProjectSpaceStateActivePromoteCheck triggerCheckChildrenStates,emxTask
CheckChildrenStates

PolicyProjectSpaceStateActivePromoteCheck eServiceCheckRoutes_if.tcl
CheckRouteStatus
PolicyProjectSpaceStateReviewPromoteCheck triggerCheckChildrenStates
CheckChildrenStates emxTask
PolicyProjectSpaceStateReviewPromoteCheck eServiceCheckRoutes_if.tcl
CheckRouteStatus
PolicyProjectSpaceStateReviewDemoteAction triggerDemoteAction
AutoMoveParent emxTask
PolicyProjectSpaceStateReviewPromoteAction triggerPromoteAction
AutoMoveParent emxTask
PolicyProjectSpaceStateReviewPromoteAction triggerModifyAttributes
ModifyAttributeActuals emxTask
PolicyProjectSpaceStateCompleteDemoteActio triggerModifyAttributes
n emxTask
ModifyAttributeActuals
PolicyProjectSpaceStateCompletePromoteChec eServiceCheckRoutes_if.tcl
k
CheckRouteStatus
Automation for WBS Tasks

WBS Tasks are governed by the Project Task policy. All triggers used in this policy are described
in this section.

Parameters Method
PolicyProjectTaskStateCreatePromoteCheck eServiceCheckRoutes_if.tcl
Check Route Status
PolicyProjectTaskStateCreate PromoteAction triggerPromoteAction

AutoMoveChildren exmTask $(OBJECTID) $(STATENAME)
$(NEXTSTATE)\
false
PolicyProjectTaskStateCreatePromoteAction notifyTaskAssignees
NotifyAssignedMembers emxTask
$(OBJECTID)
true
PolicyProjectTaskStateAssignPromoteCheck triggerCheckDependency
CheckDependency emxTask $(OBJECTID) $(STATENAME)
$(NEXTSTATE)
PolicyProjectTaskStateAssignPromoteCheck eServiceCheckRoutes_if.tcl
CheckRouteStatus
PolicyProjectTaskStateAssignPromoteAction triggerPromoteAction
AutoMoveParent emxTask $(OBJECTID) $(STATENAME)
$(NEXTSTATE)

PolicyProjectTaskStateAssignPromoteAction triggerModifyAttributes
ModifyAttributeActuals emxTask $(OBJECTID) $(STATENAME)
$(NEXTSTATE)
PolicyProjectTaskStateAssignDemoteAction triggerDemoteAction
$(NEXTSTATE)
PolicyProjectTaskStateActivePromoteCheck triggerCheckChildrenStates
CheckChildrenStates EmxTask
$(OBJECTID)
relationship_Subtask
state_Complete
PolicyProjectTaskStateActivePromoteCheck eServiceCheckRoutes_if.tcl
CheckRouteStatus
PolicyProjectTaskStateActivePromoteAction triggerSetPercentageCompletion
setPercentageComplete emxTask $(OBJECTID) $(STATENAME)
$(NEXTSTATE)
PolicyProjectTaskStateActiveDemoteCheck triggerDemoteCheck
CheckDemoteOfSummaryTask emxTask $(OBJECTID) $(STATENAME)
$(NEXTSTATE)
PolicyProjectTaskStateActiveDemoteAction triggerDemoteAction
$(NEXTSTATE)
PolicyProjectTaskStateActiveDemoteAction triggerModifyAttributes
$(NEXTSTATE)
PolicyProjectTaskStateReviewPromoteCheck triggerCheckChildrenStates
CheckChildrenStates emsTask $(OBJECTID) relationsiip_Subtask
state_Complete
PolicyProjectTaskStateReviewPromoteCheck triggerCheckDependency
CheckDependency emxTask $(OBJECTID) $(STATENAME)
$(NEXTSTATE)
PolicyProjectTaskStateReviewPromoteCheck eServiceCheckRoutes_if.tcl
CheckRouteStatus
PolicyProjectTaskStateReviewPromoteAction triggerPromoteAction
$(NEXTSTATE)
PolicyProjectTaskStatReviewPromoteAction triggerModifyAttributes
$(NEXTSTATE)
PolicyProjectTaskStateReviewDemoteAction triggerDemoteAction
$(NEXTSTATE)
PolicyProjectTaskStateCompletePromoteCheck eServiceCheckRoutes_if.tcl
CheckRouteStatus
PolicyProjectTaskStateCompleteDemoteCheck triggerDemoteCheck
CheckParentStatus emxTask $(OBJECTID) $(STATENAME)
$(NEXTSTATE)
PolicyProjectTaskStateCompleteDemoteAction triggerModifyAttributes
$(NEXTSTATE)

Automation for Dates

Parameters Method
eServiceTriggerProgramParameter AttributeTaskActualStartDateModifyAction Recalculates finish date & performs date rollup

when a task is started.
eServiceTriggerProgramParameter AttributeTaskActualFinishDateModifyAction Performs data rollup when a task is finished to

better predict the estimated & start time of
future tasks.
Automation for Builds

Build objects are governed by the Build policy. Configurable automation is described in the table
that follows.
eService Trigger Program Trigger Program and JPO Description of Action

Parameters Object method
RelationshipProductConfiguration ConnectBuildToProduct This action trigger connects a build
BuildCreateAction connected to a product configuration to
the product of that product configuration.
After a build is connected to a product
configuration, it is then connected to the
product associated with that product
configuration.
RelationshipProductBuildCreateA AssignBuildUnitNumberAndShorthandN This action trigger does the following
ction otation when a build is connected to a product:
• Query the model of the product for the
next unit number.
• Update the last build unit number for
the model.
• Assign the unit number to the build.
• Calculate and assign the shorthand
notation to the build.
RelationshipProductBuildDeleteA DisconnectBuildFromProductConfigurati This action trigger disconnects a build
ction on that has been disconnected from a
product from all the product
configurations associated with that
product.
Automation for Product Lines

Product Line objects are governed by the Product Line policy. Configurable automation is
described in the table that follows.

TypeAllCreateActionPopulateOri eeServiceSetOriginator_if.tcl Set Originator Attribute
ginator
PolicyProductLineStatePlannedPr eServicecommonTrigcAttribute_if.tcl Change Board group must be assigned
omoteCheck CheckChangeBoard
Automation for Portfolios

Portfolio objects are governed by the Portfolio policy. Configurable automation is described in the
table that follows.

RelationshipPortfolioCreateAction IncrementItemCount This action trigger increases the attribute
Count of portfolio when a model or
product gets connected to it.
RelationshipPortfolioDeleteAction DecrementItemCount This action trigger decreases the attribute
Count of product when a model or
product gets disconnected from
relationship Portfolio.
Automation for Products

Product objects are governed by the Products policy. Configurable automation is described in the
table that follows.

PolicyProductStateReviewPromot emxProduct/promoteRules Promotes the rules to the Release state if
eAction1 they are not in that state.
TypeProductsDeleteCheck CompatibilityRuleCheck Checks for connected product
compatibility rules for deleting a product
object.
TypeProductsReviseAction ConnectRules Action trigger to connect the revised
Product to product compatibility rules if
the product being revised is connected to
some product compatibility rules (with
attribute Compatibility Option =Upward/
All) by right expression relationship.
TypeProductsCreateAction CreateModelOnCreate Action trigger to implement
Model-Product synchronization. This
trigger creates a model when a product is
created. Model type is passed as
arguments.
By default, this trigger is in the Active
state, that is, auto-creation takes place.
You can disable this by demoting this to
the Inactive state.
You can configure the type by changing
the attribute “eService Program
Argument 2" of the trigger objects to the
symbolic name of the required type.
PolicyProductStateReviewPromot emxProduct/ To check if the previous revision of the
eCheck2 checkPreviousRevisionForProductPromo product is in release state.
te
PolicyProductStateReviewPromot emxProduct/ To check if the features associated with
eCheck3 checkFeatureForProductPromote the product are in Complete state or not.
PolicyProductStateReviewPromot emxProduct/ To check if the parts associated with the
eCheck4 checkPartForProductPromote product are in Complete state or not.
PolicyProductStateDesignEnginee emxValidateRules/ Validate rules of the product structure
ringPromoteCheck validateAllRuleExpressions
Automation for Models

Model objects are governed by the Models policy. Configurable automation is described in the
table that follows.

TypeModelCreateAction CreateProductOnCreate Action trigger to implement
Model-Product synchronization. This
trigger creates a product when a model is
created. Product type is passed as
arguments (by default, it is Hardware
Product).
By default, this trigger is in the Active
state, that is, auto-creation takes place.
You can disable this by demoting this to
the Inactive state.
You can configure the type by changing
the attribute “eService Program
Argument 2” of the trigger objects to the
symbolic name of the required type.
Automation for Test Execution Objects

Test Execution objects are governed by the Test Execution Object policy. Configurable automation
is described in the table that follows.

RelationshipAssignedTestExecuti NotifyAssignee This action trigger will notify the newly
onCreateAction added assignee in In Progress state of test
execution object.
PolicyTestExecutionObjectStateC PopulateActualStartDate This trigger sets the attribute Actual Start
reatePromoteAction Date of test execution object to the
system date.
PolicyTestExecutionObjectStateC NotifyAssignees This action trigger notifies all the
reatePromoteAction assignees of test execution object when
the test execution object goes to In
Progress state.
PolicyTestExecutionObjectStateI PopulateActualEndDate This trigger sets the attribute Actual End
nProgressPromoteAction Date of test execution object to the
system date.
RelationshipAssignedTestExecuti NotifyAssignee This action trigger notifies the newly
onCreateAction added assignee in In Progress state of test
execution object.

Tomcat Server Settings
This section describes suggested settings for the Apache Tomcat server.
In this section:
• Setting the Level of Sub Tasks Allowed
Setting the Level of Sub Tasks Allowed

Below is a configurable setting for the levels of sub tasks allowed in a WBS. This should be
configured to prevent a system failure when promoting a WBS task in a project.
Add the following setting in the catalina.bat file of the Apache Tomcat server:
set CATALINA_OPTS=%CATALINA_OPTS% -Xms512m -Xmx512m -Xss1024k
-XX:NewSize=230m -XX:MaxNewSize=230m -XX:SurvivorRatio=2
-XX:MaxPermSize=128m -Dfile.encoding=Shift_JIS -server
This setting should be sufficient for medium to large systems.

3
Setting Up VPLM Access
This section describes setting up VPLM access with ENOVIA Program Central..
In this section:
• ENOVIA Program Central and VPLM Objects
• Setting Up VPLM Access
67
ENOVIA Program Central and VPLM Objects
ENOVIA Program Central can expose VPLM objects for the purpose of searching for and adding
VPLM objects as deliverables. These VPLM objects are stored in the ENOVIA VPM V5 database
and are exposed to the application via the ENOVIA Web Services Adaplet.
ENOVIA Program Central provides a link to VPLM Actions, as well as general visibility into
VPLM in-work environments from ENOVIA.
The following functionality is available within ENOVIA ENOVIA Program Central:
• Search for VPLM objects
• Navigate the search results for the following searches within ENOVIA Program Central:
• General Search
• Folder Search
• Add Existing Deliverables Search
• Add VPLM objects as task deliverables
• Create VPLM Actions that correspond to and interact with a specialized type of WBS task.
For more information about the above functionality, see the ENOVIA Program Central User’s
Guide.

Setting Up VPLM Access
This section contains topics for setting up the ENOVIA Program Central to expose VPLM
objects.
In this section:
• Setup Overview
• Software Prerequisites
• VPLM Web Service Discovery
• ENOVIA Web Service Discovery
• Adaplet Deployment and Configuration
• Creating the Vault
• Configuring the VPLM V5 Server Environment
• Unhiding the VPLM Task
• Lifecycle Setup
• ENOVIA Program Central Property Files and Ranges
Setup Overview
The diagram below presents a comprehensive view of the various ENOVIA applications and
technologies involved when ENOVIA Program Central is set up to access VPLM objects.
Chapter 3: Setting Up VPLM Access 69

where:
• 1—ENOVIA Program Central
• 2—ENOVIA Adaplet
• 3—VPLM Web Services
• 4—VPLM V5
• 5—ENOVIA Web Services for ENOVIA Program Central
Integration is between ENOVIA Program Central and ENOVIA VPM V5. For information on the
required versions of the applications, see Software Prerequisites.
ENOVIA Adaplet, which employs Web Services Adaplet Architecture, facilitates the integration of
ENOVIA Program Central and VPM V5. The Settings information, as shown in the diagram above,
is used when 2. Create the Vault Definition. This information includes:
• serviceURL—The URL of the ENOVIA Adaplet
• CATJWSServiceDirectory—The URL of the VPLM Web Services, provided by VPM V5
• CATInstallPath—Location of the VPLM1Adaplet_ws.jar and VPLM1AdapletEAR.ear files,
referred to in Adaplet Deployment and Configuration. Please note that while The Settings File,
you must copy VPLMschema.xml to this location.
Configuring the VPLM V5 Server Environment requires:
• Apache Axis Libraries—This is explained in Installing Apache Axis Libraries. The diagram
above includes an entry in CATEnv for AxisInstallPath.
• The diagram above also includes an entry in CATEnv for AUTO_COMIT_DISABLE=TRUE.
This allows VPLM V5 to roll back changes.

• VPMEVENTS in the diagram refers to Configuring the VPLM Event Dictionary. This is used
in conjunction with Defining ENOVIA Credentials, and allows VPM V5 to notify ENOVIA
Program Central of lifecycle events in VPM V5.
• VPMSETTINGS in the diagram above refers to Defining ENOVIA Credentials.
ENOVIA Program Central can introduce (push) objects into VPM V5, as well as get (pull)
information from VPM V5. VPM V5 however, can only notify (push) ENOVIA Program Central
of certain lifecycle events.
Please note that key setup information, indicated by in the diagram above, must all be in place
for the proper functioning of ENOVIA Program Central for VPM V5. This includes:
• Settings:
• serviceURL
• CATJWSServiceDirectory
• CATInstallPath
• CATEnv:
• AxisInstallPath
• AUTO_COMIT_DISABLE=TRUE
• VPM EVENTS:
• StringURL
• WsEncodingStyleURL
• VPM SETTINGS:
• MATRIX_DB_AUTHUSER
• MATRIX_DB_AUTH
In addition, you must also make sure that VPLM Web Services and ENOVIA Web Services have
been deployed.
Software Prerequisites
Following are the software prerequisites:
• ENOVIA Platform Modeling Studio
• ENOVIA Framework
• ENOVIA Platform Server
• ENOVIA Program Central
• VPLM V5R18 SP2
• Apache Axis 1.4
• WebSphere Application Server v6.1
VPLM Web Service Discovery

To obtain information about the VPLM Web services, you must obtain the URL for the Web
Services provider from the VPLM System Administrator responsible for the deployment of VPLM
Web Services. (e.g. http://host.eno.ds:50015/B18/html/CATJadOptions/.)

For more information on installing VPLM Web Services and applicable credentials, refer to
Installation and Deployment Guide : Installing and Deploying Version 5 : Deploying ENOVIA
Applications : Deploying ENOVIA (VPLM) Web Services.
1. Open the URL provided by your VPLM System Administrator to verify that VPLM Web
Services are installed. You must have VPLM credentials for authentication.
2. The root context portion of the Web Service provider URL (http://host.eno.ds:50015/B18) will
be used when 2. Create the Vault Definition.
<CATJWSServiceDirectory value=”http://host.eno.ds:50015/B18”/>
3. Expand the Administration folder and go to General > Environment.
4. The CATInstallPath variable is also used when 2. Create the Vault Definition, as well as
configuring the VPLM Schema.
<CATInstallPath value =
”C:\\DS\\B18\\intel_a;\\fire\CXR18rel\bsf\intel_a”/>
ENOVIA Web Service Discovery

To obtain information about the ENOVIA Web services, you must obtain the URL for the
ENOVIA Web Services provider from the ENOVIA System Administrator responsible for the
deployment of ENOVIA Web Services. (e.g. http://host.3ds.com:9081/enovia/services.)
1. Open the URL provided by your ENOVIA System Administrator to verify that ENOVIA Web
Services are installed.

2. The ENOVIA Web Services provider URL, http://host.3ds.com:9081/enovia/services, is the
base URL used to construct the stringURL during the Configuring the VPLM Event Dictionary
step.
Adaplet Deployment and Configuration

This section describes how to deploy and configure the Adaplet, which enables real-time
interoperation between ENOVIA and VPLM and provides integrated information. The setup
described in this section occurs on the VPM V5 side of the integration.
Deploying the Adaplet EAR

The Application should not be deployed on the application server where the VPLM WebServices
have been deployed. Deploy the Adaplet EAR file on a dedicated WebSphere Application Server
(WAS) profile.
The Adaplet applications require the definition of a shared library that references:
<install_path>\<os>\docs\javaserver\VPLM1Adaplet_ws.jar file
In addition, you must define the classpath to the shared library.
Define the shared library

1. At the main WebSphere screen, choose Environment > Shared Libraries.
2. At the Shared Libraries screen, first set the scope to
Node=yourNode, Server=yourServer
then, click the New button.

To deploy the archive
1. Use the application located in <install_path>/<os>/resources/ear/WAS61/
VPLM1AdapletEAR.ear
where:
<install_path> is the directory in which you installed ENOVIA
<os> is the operating system you are using.
For information on how to deploy the ear file, refer to your WebSphere documentation.

2. Once deployed, from the Integrated Solutions Console choose Applications > Enterprise
Applications. Then select IntR18EAR.
3. Click Shared library references.
4. Select IntR18EAR in the Application column and click Reference shared libraries.
5. Send the VPLM1Adaplet_ws.jar file from the Available box to the Selected box. Click OK on
this panel and the next panel.
6. Save the changes to the configuration.

7. Restart the WebSphere server.
The IntR18EAR application will fail to start (class not found) until the library reference has been
saved and the WebSphere Application Server has been restarted.

Executing the Adaplet EAR
In order for the Adaplet EAR to execute correctly, ensure the class loader uses the application class
loader first.
1. In the Enterprise Applications > IntR18EAR page, select Class loading and update
detection.
2. On the Class loader page, make sure the Classes loaded with application class loader first
option is selected and click OK.

Validating the Deployment
To validate whether the service is available, enter the serviceURLvalue into a browser Address bar,
and check that you receive an appropriate display. The URL is http://host:9084/IntR18/services/
VPLMAdapletService?wsdl, for example:
The service URL http://host:9084/IntR18/services/VPLMAdapletService?wsdl will be used when

2. Create the Vault Definition.
<serviceURL value=”http://host:9084/IntR18/services/
VPLMAdapletService?wsdl”/>

Creating the Vault
To create a vault in ENOVIA, perform the topics in this section in the order listed.
1. Configure the VPLM Schema

The schema map file, VPLMAschema.xml, which is part of the release distribution, needs to be
copied into the VPLM runtime view in the first directory path listed in the <install_dir>/
<os>/resources/xml directory. This schema must be copied into place BEFORE the vault is
created in 2. Create the Vault Definition.
2. Create the Vault Definition

When creating the adaplet vault definition, please refer to the Web Service Adaplet Programming
Guide. An excerpt is included here for your convenience.
A parameter file, referred to here as the Settings file, is used for supplying configuration settings.
This file is referred to as the Params file in the WSA documentation.
The Settings File
The adaplet provides a mechanism for making configuration settings. There is an XML file stored
in the database along with the adaplet vault description. This XML file is parsed and passed into the
adaplet provider’s init() entry point as a Java map. In MQL, the name of this file is given when the
adaplet vault is created (or in a subsequent modify command) as an argument to the “file” keyword.
There are predefined settings to control work done by the client side of the adaplet, but you can
extend the server side of the provider by adding additional settings.
The option vaultStore is a new kind of store. This kind of store is not supported in the initial
release.
Provider Subsection
The Provider subsection can have a server subsection. It must consist of simple name/value pairs.
These name/value pairs are passed to the init call by the client in the form of an array of FfNVPair
instance objects.
Option Description
localUpdates This value should be true if data from the adapted vault
can be extended by storing data in ENOVIA tables.
remoteUpdates This value should be true if the adaplet is bi-directional
and supports updates.
normalizeDates This value should be true if the adaplet expects date/
time information in GMT.
defaultType This value is the Business Type to assign to objects with
a blank or null type field.
defaultOwner Person, group, or role to assign to objects with a blank
or null owner field.
defaultPolicy Policy to assign to objects with a blank or null policy
field.
defaultRelationship Relationship type to assign to relationships with a blank
or null type field.

serviceURL URL of the service endpoint for the adaplet web server.
authUsername User name associated with authType.
authPassword Password associated with authType password.
timeout This value is the amount of time ENOVIA Program
Central will wait before aborting the transaction, if the
adaplet’s Web service is offline. This value is given in
seconds and the default is 300.
symbolicNames This value should be true if the adaplet expects symbolic
names for administration objects (types, attributes, etc.)
Server Subsection
Set the following parameters when defining the VPLM ENOVIA adaplet vault in the <provider/>
section of the <server/> sub-section of the vault parameters file:
DebugClassLoader This should only be specified for debugging the

VPLM1AdapletEAR deployment. Be sure to
set it to false once the installation has been
validated.
CATJWSServiceDirectory This is the URL of the service provider
deployed in VPLM1AdapletEAR.
CATInstallPath This is the ENOVIA VPLM Server installation
directory where CAA Web Services have been
deployed.
enoviaUsername ENOVIA CAA WebServices SSO user. (It is
recommended to be the same as
BasicAuthUsername and the same as the
VPLM session user. Refer to ENOVIA
documentation.)
VPLMAdptSessionLife The number of milliseconds for which the
VPLM1Adaplet will keep the ENOVIA CAA
WebServices session open when not actively
being used.
ReturnVPLMUsersAsM1users If user synchronization has been maintained
(all VPLM users are also defined in ENOVIA
Program Central with the same usernames), set
this value to TRUE. If FALSE (the default if
not defined), no user value is returned and the
Vault defaultOwner value is used.
enoviaUserContext Default value =
VPMADMIN.ADMIN.DEFAULT. This is the
context to use for the ENOVIA VPLM session
user.
basicAuthUsername This is the CAA Web Service SSO user name.
basicAuthPassword This is the CAA Web Service SSO user
password.
Sample Settings File

A sample settings file is shown below. The file containing this XML should be provided as part of
the definition of the vault.
Once you have created your settings file, for example C:\settings.txt, use the MQL commands
given in Creating a Vault in ENOVIA to either define or update your vault.
Creating a Vault in ENOVIA

To create a vault, use the following command:
add vault VAULTNAME external file c:\settings.txt;
where settings.txt is the parameter file containing the configuration settings.
To update a vault after changing the configuration settings in the parameter file, use:
mod vault VAULTNAME file c:\settings.txt;
Configuring the VPLM V5 Server Environment
Installing Apache Axis Libraries

Obtain the Axis 1.4 libraries from Apache, and extract the jar files into a directory structure ending
with docs/javacommon sub-directories. If your install path is /u/users/vpmadm/, for example,
and you create a directory axis_1_4, and the sub-folders lib, docs, and javacommon, then you will
see:

You must ensure that the path /u/users/vplmadm/axis_1_4/lib has rwx privileges for
all users of the VPLM Environment where this directory is set as the AxisInstallPath. These same
access rights are required for the sub-directories docs and javacommon.
Configuring the VPLM Environment Variables

VPLM Web Services will autocommit after each service call. For ENOVIA Program Central
transaction control, this feature must be disabled. To do so, you must add this variable to the VPLM
Environment (e.g., /u/users/vplmadm/CATEnv/ENOVIA_LCA.V5R18SP2_WS.B17.txt ):
AUTO_COMMIT_DISABLED=TRUE
Also, add the following variable with a value that matches the Axis library path found above:
AxisInstallPath=/u/users/vplmadm/axis_1_4/lib
Note that the complete path to the libraries would then be $AxisInstallPath/docs/javacommon/./.
Configuring the VPLM Event Dictionary

Locate the ChangeStatus_ENOVIA_Action_Design.xml file in your <install_path>/<os>/ code/
dictionary directory. (e.g., /u/users/vpmadm/solaris_a/code/dictionary). You should create one file
for each action type you choose to enable for calling the ENOVIA Program Central Web Service.
Each file would start with the ChangeStatus_ prefix and end with the type name of the VPLM
Action.
Contents of the file should look as follows, with the stringURL value being the service url for the
VPLMStatusChangeEvent eMatrix service:

Defining ENOVIA Credentials
This section describes how to define ENOVIA Program Central credentials used by the VPLM call
to the ENOVIA Program Central Service. When calling a ENOVIA Program Central Web Service,
VPLM must authenticate as a valid ENOVIA Program Central user (with password). This
information must be set using the VPMSettings application. The two parameters used are
MATRIX_DB_AUTH_USER (user name) and MATRIX_DB_AUTH (password).
The VPMSettings application may be run as follows (your VPLM administrator must do this, and
should know how to set this up for each user, or default for all users).
./code/command/catstart -run “VPMSettings -a -n MATRIX_DB_AUTH_USER -v
matrixUser”
./code/command/catstart -run “VPMSettings -a -n MATRIX_DB_AUTH -v
matrixpw”
This will update a file in the configure settings directory, for example:
/u/users/vpmadm/CATSettings/VPMAdmin.CATSettings
Once defined, the values will be retrieved and used to call the ENOVIA Program Central Web
Service.
The ENOVIA Program Central user used by the call back must have Project Lead access, Show and
Execute privileges, any other privileges required for the VPLM Task triggers to execute, and the
ability to change the owner/status of any VPLM task.
For more information about deploying web services, see the ENOVIA Live Collaboration
Application Development Guide.
Exposing Integration Attributes in VPLM

Several attributes must be exposed in VPLM for ENOVIA Program Central to manage VPLM
Tasks. Overview of VPLM Task Behaviors explains this in detail.
To expose the Duration Time Unit and Task Documentation attributes mentioned in VPLM Action
in Chapter 4, append the following, in RED, to the entity (ENOVIA Action) in play for ENOVIA
Program Central:

The VPLM Action type - ENOVIA_Action_Design, specified by entity above, is used as an
example. You can choose one or more VPLM Action types described in the APLAFL.custo file.
Having updated the APLAFL.custo file, you must run VPMPeopleUpdate. This is typically
performed by the VPLM System Administrator.
Launching ENOVIA Program Central from ENOVIA V5 VPM

You can launch ENOVIA Program Central from the ENOVIA V5 VPM application. This
capability is limited to viewing VPLM Tasks in ENOVIA Program Central when a VPLM Action
is selected in VPM. The steps required to enable this feature are:
1. Ensure that Configuring the VPLM Event Dictionary is completed.
2. Modify <install_path>\os\code\dictionary\default.xml by providing the server:port value for
the stringURL, as indicated in red below.

To launch ENOVIA Program Central, select a VPLM Action in ENOVIA V5 VPM and click
Access M1 Task in the contextual menu, as shown below:
The VPLM Task appears in ENOVIA Program Central:
Unhiding the VPLM Task

You must unhide the object type named “VPLM Task” so that it will be usable.
1. Log in to the Business Modeler application.
2. Click the Find button in the toolbar or choose Object > Find from the menu.
3. Select Type in the Find Objects list.
4. Type in VPLM Task or *VPLM Task*.
5. Open the Type VPLM Task for edit by double-clicking the object.

6. Uncheck the Hidden check box.
7. Click Edit.
Lifecycle Setup
Several lifecycles need to be configured in VPLM to enable the ENOVIA Program Central to
expose VPLM objects. Sample lifecycles with the appropriate configuration are shown below. The
sample lifecycles contained in this section can be found in the *.VGraph files that are part of the
release distribution.
To import lifecycles, use the following command:
catstart -run “VPMGRAPHADM Import <import graphname> <import graph
location>
ENOVIA Program Central for VPM V5 ENUM Lifecycle

The lifecycle VPM_DIRINT_ENUMS.VGraph is required for ENOVIA Program Central and must
be the first of the ENOVIA Program Central lifecycles to be imported.
VPM_DIRINT_ENUMS.VGraph Lifecycle Example:
ISO-10303-21;
HEADER;
FILE_DESCRIPTION((''),'1');
FILE_NAME('VPM_DIRINT_ENUMS.VGraph','2007-03-13T12:53:34+00:00',(''),$,$,$,$);
FILE_SCHEMA(('ENOTemplateSch'));
!FILE_SCHEMA_VERSION(1,1);
ENDSEC;
DATA;
/*
ENUMERATIONS FOR ERROR MESSAGES
*/
#1317=enum_predicat('DIR_M1_ACTIVE',('Action.V_name'));
#1318=enum_predicat('DIR_M1_IN_CONTROL',('Action.V_name'));
#1319=enum_predicat('DIR_M1_NOT_COMPLETE_READY',('Action.V_name'));
#1320=enum_predicat('DIR_M1_IN_CONTROL_CO',('Action.V_name'));
/*
ENUMERATIONS FOR OPERATIONS AVAILABILITY
*/
#1301=enum_predicat('DIRECT_INTEGRATION_M1_IN_CONTROL_ENUM',('DirectIntegration01','Di
rectIntegration03'));
#1302=enum_predicat('DIRECT_INTEGRATION_ACTIVE_ENUM',('DirectIntegration01','DirectInt
egration02','DirectIntegration03'));
#1303=enum_predicat('DIRECT_COMPLETE_NOT_READY_ENUM',('DirectIntegration00','DirectInt
egration01','DirectIntegration02'));

#1304=enum_predicat('DIRECT_UNCOMPLETE_NOT_READY_ENUM',('DirectIntegration03'));
ENDSEC;
END-ISO-10303-21;
Delete Action Business Graph Lifecycle

The Delete Action business graph(s) governing the Action Types to be created via ENOVIA
Program Central require modification to enable this integration.
Delete Action Lifecycle Example:
Following is an example where the required changes have been made to one of the default Action
Delete business graphs. The required changes are shown in red.
/* ON DESTROY ACTION */
ISO-10303-21;
HEADER;
FILE_NAME('VPM_GT_DESTROY_ACTION_AFLBASE.VGraph','1998-10-08T14:56:14+00:00',(''),$,$,
$,$);
ENDSEC;
DATA;
#10000=GIMaster($,$,$,$,$,$,$,$,$,$,$,$,$,'GT_destroy_action_ENOVIA_AFLBaseAction',$,$
,$,$,$,$,'','') ;
#10001=GIVersion($,$,$,$,$,$,$,$,$,$,$,$,$,'---',1,'Active',$,$,$,#10000,$,#10010,(#10
010, #10011),$) ;
#10010=status((#10100),'ST_destroy_action_ENOVIA_AFLBaseAction',' ') ;
#10011=status($, 'ST_destroy_action_ENOVIA_AFLBaseAction_ok',' ') ;
#10100=transition('RUN',1,0,#10200,#10222,
'ST_destroy_action_ENOVIA_AFLBaseAction_ok',' ') ;
#10200=condition('DI_Condition_Destroy_Availiable','VPMAFLGeneralCondition',(#10215),
'DIR_M1_ACTIVE');
#10215=predicat('Action','V_durationUnit','NOT_IN_ENUM','DIRECT_INTEGRATION_M1_IN_CONT
ROL_ENUM');
#10222=operation('OP_destroy_action_DIR_ENOVIA_AFLBaseAction',$, $) ;
ENDSEC;
END-ISO-10303-21;

Action Change Owner Business Graph Lifecycle
The Action Change Owner business graph(s) governing the Actions Types to be created via
ENOVIA Program Central require modification to enable this integration.
Action Change Owner Business Graph Lifecycle Example:
Following is an example where the required changes have been made to one of the default Action
Change Owner business graphs. The required changes are shown in red.
/* ON CHANGE OWNER */
ISO-10303-21;
HEADER;
FILE_NAME('VPM_GT_CHANGE_OWNER.VGraph','1998-10-08T14:56:14+00:00',(''),$,$,$,$);
ENDSEC;
DATA;
#13000=GIMaster($,$,$,$,$,$,$,$,$,$,$,$,$,'GT_change_owner_ENOVIA_AFLAction',$,$,$,$,$
,$,'','') ;
#13001=GIVersion($,$,$,$,$,$,$,$,$,$,$,$,$,'---',1,'Active',$,$,$,#13000,$,#13010,(#13
010, #13011),$) ;
#13010=status((#13100),'ST_change_owner_ENOVIA_AFLAction',' ') ;
#13011=status($,'ST_change_owner_ENOVIA_AFLAction_ok',' ') ;
#13100=transition('RUN',1,0,#13700,#13500, 'ST_change_owner_ENOVIA_AFLAction_ok',' ') ;

#13500=operation('DI_OP_change_owner_ENOVIA_AFLAction',(#13600),$) ;
#13600=command('DI_Notify','VPMAFLCmdNotify',$,(#13300),$,'OK') ;
#13300=predicat('Action','V_user','NOTIFY_CHANGE_OWNER_HEADER','NOTIFY_CHANGE_OWNER_ME
SSAGE');
#13700=condition('CO_DIR_VPLM_IN_CONTROL','VPMAFLGeneralCondition',(#13710),'DIR_M1_IN
_CONTROL_CO');
#13710=predicat('Action','V_durationUnit','NOT_IN_ENUM','DIRECT_INTEGRATION_M1_IN_CONT
ROL_ENUM');
ENDSEC;
END-ISO-10303-21;

Action Lifecycles
Lifecycles for each Action Type created via the Integration must be identical and coordinated with
those of VPLM Tasks. The ENOVIA Program Central Project Task lifecycle has five states:
Create, Assign, Active, Review and Complete, as shown below:
The lifecycles of the Actions corresponding to ENOVIA Program Central VPLM Tasks must either
have five corresponding states or four states, where one state represents a combined Assign and
Active state. Additionally, certain Promote and Demote transitions among these states are required.
An Action Lifecycle with five states is shown below:

An Action Lifecycle with four states is shown below:
Action Lifecycle Example:

Following is an example Action lifecycle that has been modified for use with ENOVIA Program
Central. Items in red are the required commands and conditions for ENOVIA Program Central.
ISO-10303-21;
HEADER;
FILE_NAME('VPM_ACTION_DESIGN_LOW.VGraph','2007-01-29T08:33:34+00:00',(''),$,$,$,$);
ENDSEC;
DATA;
/*
Substatus:
1. Modification availability state

2. N (for future use)
3. Ready for Release state
4. Delete availability state
5. Release state

*/
#03=GIMaster($,$,$,$,$,$,$,$,$,$,$,$,$,'ENOVIA_Action_Design_Low',$,$,$,$,$,$,'','') ;
#93=GIVersion($,$,$,$,$,$,$,$,$,$,$,$,$,'---',1,'Active',$,$,$,#03,$,#1,(#01, #60,
#15, #17, #25, #26, #27),$) ;
#01=status((#61,#8,#13),'Proposed' ,'YNNYNNNNNN') ;
#60=status((#2,#23,#13),'Assigned' ,'YNNYNNNNNN') ;
#15=status((#13,#19,#62),'In Work' ,'YNNNNNNNNN') ;
#17=status((#16,#18),'In Review','NNNNNNNNNN') ;
#25=status((#70),'Completed','NNNNYNNNNN') ;
#26=status($,'Rejected', 'NNNNYNNNNN') ;
#27=status($,'Obsoleted','NNNNYNNNNN') ;
#61=transition('Promote',1,0,#64,#6 ,'Assigned' ,' ') ;

#02=transition('Promote',1,0,$,#63 ,'In Work' ,' ') ;
#08=transition('Demote' ,1,0,#66,#12,'Obsoleted',' ') ;
#13=transition('Reject' ,1,0,#66,#14,'Rejected' ,' ') ;
#19=transition('Promote',1,0,$,#40,'In Review',$) ;
#16=transition('Promote',1,0,#28,#20,'Completed',' ') ;
#23=transition('Demote' ,1,0,$,#24,'Proposed' ,' ') ;
#62=transition('Demote' ,1,0,$,#24,'Assigned' ,' ') ;
#18=transition('Demote',1,0,#64,$,'In Work',$) ;
#70=transition('Demote',1,0,#72,$,'In Review',$) ;
#06=operation('WEBAction_Design_Assignment',$, $) ;
#63=operation('WEBAction_Design_Activation',(#50), $) ;
#71=operation('WEBAction_Design_Review',(#50), $) ;
#12=operation('WEBAction_Design_Obsoleting',$, $) ;
#14=operation('WEBAction_Design_Rejecting',$, $) ;
#20=operation('WEBAction_Design_Completion',(#30,#32,#34,#36,#38), $) ;
#24=operation('WEBAction_Design_Demotion',(#50), $) ;
#40=operation('WEBAction_Design_InReview',(#41,#50), $) ;
#50=command('WS_Activation','ENOVWSLCInvoke',$,(#54),$,'ChangeStatus') ;
#54=predicat('DirectAction','V_durationUnit','DirectIntegration02','Extra1') ;
#41=command('DirCATEnovCMCmdChildActions','CATEnovCMCmdChildActions',$,$,$,' ') ;
#42=enum_predicat('AFLBASE_PARENT_FINAL_AVAILABILITY_STATUS_ENUM',('Completed','Obsole
ted','Reviewed','Signed','Recalled','Accepted'));
#28=condition('DirCondChildActionCompleted','VPMAFLGeneralCondition',(#69,#29),'DIR_M1
_NOT_COMPLETE_READY');
#29=predicat('Action>AFLParent','V_status','IN_ENUM','AFLBASE_PARENT_FINAL_AVAILABILIT
Y_STATUS_ENUM');

#64=condition('DIR_VPLM_IN_CONTROL','VPMAFLGeneralCondition',(#65),'DIR_M1_IN_CONTROL'
);
#65=predicat('Action','V_durationUnit','NOT_IN_ENUM','DIRECT_INTEGRATION_M1_IN_CONTROL
_ENUM');
#66=condition('DIR_INT_ACTIVE','VPMAFLGeneralCondition',(#67),'DIR_M1_ACTIVE');
#67=predicat('Action','V_durationUnit','NOT_IN_ENUM','DIRECT_INTEGRATION_ACTIVE_ENUM')
;
#68=condition('DIR_OK_TO_COMPLETE','VPMAFLGeneralCondition',(#69),'AFL_CHILD_NOT_COMPL
ETED');
#69=predicat('Action','V_durationUnit','NOT_IN_ENUM','DIRECT_COMPLETE_NOT_READY_ENUM')
;
#72=condition('DIR_OK_TO_UNCOMPLETE','VPMAFLGeneralCondition',(#73),'DIR_M1_IN_CONTROL
');
#73=predicat('Action','V_durationUnit','NOT_IN_ENUM','DIRECT_UNCOMPLETE_NOT_READY_ENUM
');
#30=command('DirPromote','VPMAFLCmdPromoteConfiguration',$,(#31),$,' ') ;
#31=predicat('Action','Design',' ',' ');
#32=command('DirNotifyCompleted','VPMAFLCmdNotify',$,(#33),$,'OK') ;
#33=predicat('Action','V_creator','NOTIFY_COMPLETED_DES_HEADER','NOTIFY_COMPLETED_DES_
MESSAGE');
#34=command('DirNotifyUser','VPMAFLCmdMessage',$,(#35),$,' ') ;
#35=predicat('NOTIFY_SENT_COMPLETE_CREATOR',' ',' ',' ');
#36=command('DirRealizeCancel','VPMAFLCmdRealizeCancel',$,(#37),$,'OK');
#37=predicat('Action',' ',' ',' ');
#38=command('DirRealizeSuperseed','VPMAFLCmdRealizeSuperseed',$,(#39),$,'OK');
#39=predicat('Action',' ',' ',' ');
ENDSEC;
END-ISO-10303-21;
ENOVIA Program Central Property Files and Ranges

The section contains tasks that need to be performed on the ENOVIA Program Central side in order
to complete the integration.
VPLM Instance Range

Once the vaults are named, use the Business Modeler application to modify the range value for the
attribute named VPLM Instance.
The values should be the names of the VPLM Vaults.

VPLM Action Type Range
Once the vaults are named, use the Business Modeler application to update the VPLM action type
range.
The VPLM Action Type attribute comes with four default range values: Design Action,
Manufacturing Action, Documentation Action, and Maintenance Action. If any additional Action
Types are to be created, they must be set up in the range values. You should remove any default
values that will not be used.
ENOVIA Program Central Properties

Configuration of portions of the integration are governed by values in the
emxProgramCentral.properties file. The remainder of this section describes the integration related
entries in the emxProgramCentral.properties.file. Whenever changes are made to entries in the
emxProgramCentral.properties file, the ENOVIA Program Central server must be restarted for the
changes to become effective.
Lifecycle State Mapping

Each Action type in a given VPLM Instance supports various lifecycle states. The mapping of the
VPLM lifecycle states to M1 lifecycle states is done in the emxProgramCentral.properties file.
Entries in the file are as follows:
The format of each entry is:
where:

Value Description
Property File Name The property file name, static value
emxProgramCentral.
Mapping Set The section within the property
file, static value VPLMMapping
VPLM Instance The VPLM instance name with all
blanks removed
Action Type An Action type name with all
blanks removed.
Task Status Value A Task lifecycle status value.
Possible values are: Create,
Assign, Active, Review, or
Complete.
VPLM Status Value The VPLM status value that
corresponds to the Task Status
Value for an Action, with the
specified Action Type in the given
VPLM instance.
Corresponding Action Deletion

The following emxProgramCentral.properties file entry controls whether a VPLM action is deleted
when its corresponding VPLM Task is deleted.
VPLM Action deletion should only be enabled (value set to Y) if VPLM is configured to allow
action deletion for all of the VPLM action types that are enabled to be created via ENOVIA
Program Central. VPLM Action deletion is controlled by lifecycles and lifecycle substances.
Creating Child Actions

The following emxProgramCentral.properties file entry controls whether a VPLM action is created
as a child action when one VPLM Task is created as a subtask of another VPLM Task.
Allowed VPLM Task Deliverable Object Types

The set of allowed object types that can be attached as deliverables on VPLM Tasks can be reduced
from the set allowed for project Tasks. This is done through the following setting in the
emxProgramCentral.properties file.

where type_xxx, type_yyy, ... are the top level types enabled for addition as deliverables on project
Tasks, but should be disabled for addition as deliverables on VPLM Tasks.
Disabling Apostrophes in Task Names

The apostrophe character (‘) must be added to the set of characters not allowed in Task names. This
is done by adding it to the emxFramework.Javascript.NameBadChars property in the
emxSystem.properties file. After adding the apostrophe to the character set, the property file entry
should be similar to the following example:
Finish to Start Behavior

The following emxProgramCentral.properties file entries control whether deliverables from a
predecessor task are added as Input Affected Objects on the VPLM Actions corresponding to
VPLM Tasks, where the VPLM Tasks have a Finish to Start dependency from other tasks.
FinishStart enables or disables the Finish to Start behavior. AOFinishStart controls whether Output
Affected Objects on VPLM Actions corresponding to VPLM Tasks that are predecessors to other
VPLM Tasks in terms of Finish to Start dependencies are added as Input Affected Objects on the
VPLM Actions corresponding to the successor VPLM tasks.
Action Promote to Complete

Depending on individual customers’ requirements, the promotion of a corresponding VPLM
Action to Complete may not be desired. The following property controls this promotion. For
example, this promotion might be disabled if additional VPLM Action lifecycle states exist
between Review and Complete.

4
VPLM Objects
This section describes the task behaviors of VPLM objects and custom VPLM objects in
ENOVIA Program Central.
In this section:
• VPLM Task Behaviors
• Triggers
• VPLM Custom Objects in ENOVIA Program Central
95
VPLM Task Behaviors
ENOVIA Program Central provides a WBS task type, called VPLM Task, which is integrated
with VPLM Actions. This section describes the behaviors of VPLM Tasks, including
information about attributes, VPLM Actions, policies, and triggers.
In this section:
• Overview of VPLM Task Behaviors
• VPLM Instances
• VPLM Users in ENOVIA Program Central
• VPLM Task Attributes
• VPLM Task Policy
• Finish to Start VPLM Task Dependency and Inputs
• VPLM Action
• VPLM Status Change
• Deliverable Behavior
Overview of VPLM Task Behaviors

When a VPLM Task is created so is a VPLM Action. This Action is associated to the VPLM Task
via the “VPLM Action” relation.
When the task is ready for a VPLM user, the ENOVIA Program Central user promotes the VPLM
Task to Assign status. This promotion triggers updates of attributes on the VPLM Action and a
promotion of the VPLM Action to its equivalent of Assign status. At this point, VPLM is in control
of the task, meaning that ENOVIA Program Central users other than the project leader cannot
change the status or owner of the VPLM Task.
Depending on the configuration of VPLM, either a promotion of the VPLM Action to an Active
state or some other event will trigger the promotion of the corresponding VPLM Task to Active
status. VPLM is still in charge of the task at this point. While VPLM is in charge of the task, a
change of owner of the Action triggers a corresponding ownership change of the VPLM Task at the
next status change. As Output Affected Objects are added to the VPLM Action, they immediately
appear as Deliverables on the corresponding VPLM Task. Likewise, when an object is removed
from being an Output Affected Object of a VPLM Action, it no longer appears as a Deliverable on
the corresponding VPLM Task. ENOVIA Program Central users are not permitted to remove
Deliverables that are in fact Output Affected Objects on the corresponding Action.

Below is a conceptual diagram showing VPLM Task deliverable behavior:
Once the VPLM user completes work on the Action, he promotes it to a Review status. This
promotion triggers the promotion of the corresponding VPLM Task to Review status. At this point,
ENOVIA Program Central is again in control of the task. Assuming the review is successful, the
VPLM Task is promoted to “Complete”, which in turn promotes the corresponding VPLM Action
to Complete. If the VPLM Task is demoted to Active, a demotion of the VPLM Action is triggered
and the cycle is repeated.
Deletion of the VPLM Action (only allowed in Create status) marks the corresponding VPLM
Action as being defunct.
VPLM Instances
A VPLM instance is an ENOVIA Program Central external vault corresponding to a specific
VPLM instance. External vaults representing VPLM instances are a prerequisite for ENOVIA
Program Central using VPLM objects.
Chapter 4: VPLM Objects 97

VPLM Users in ENOVIA Program Central
To insure that valid VPLM users are identified as Action owners when creating VPLM Actions via
ENOVIA Program Central, VPLM users will be setup in ENOVIA Program Central in the Group
structure shown below.
There is a root VPLM Direct Integration Group whose children correspond to the sets of VPLM
users appropriate for specific VPLM instances. The VPLM Direct Integration Group is used for
access and security purposes. A user can belong to multiple Instance Specific Groups. The VPLM
Direct Integration Group does not exist out of the box and must be created by an administrator. For
information about creating groups, see the “Profile Management” section in the ENOVIA Common
Components User Guide.
The names of the Instance Specific Groups must exactly match the names of their corresponding
VPLM vaults.
VPLM Task Attributes

VPLM Tasks have the same attributes as WBS Tasks, with the following additional attributes:
Attribute Description
VPLM Action The type of VPLM Action to create. Values shown to the user are
Type translatable, while the values stored in the DB are the internal values
required by VPLM. This attribute cannot be updated after VPLM Task
creation.
VPLM The external vault that represents the specific VPLM instance where the
Instance VPLM Action is to be created. This attribute cannot be updated after
VPLM Task creation.
VPLM Task Policy

The VPLM Tasks use the same policies as WBS tasks. The policy states are:
• Create
• Assign

• Active
• Review
• Complete
VPLM Tasks can have extra behaviors governed by the VPLM Task Policy.
Finish to Start VPLM Task Dependency and Inputs

When two tasks have a Finish to Start dependency defined between them, the predecessor task must
finish before the dependent task can start. If the dependent task is a VPLM Task, when the
predecessor task finishes, the deliverables on the predecessor task are added as inputs to the Action
corresponding to the dependent VPLM Task. This is accomplished via a new VPLM Task trigger.
The following diagram illustrates this feature:
VPLM Action
The creation of a VPLM Task also creates a VPLM Action. A VPLM Action relation is created
from the VPLM Task to the VPLM Action. VPLM Tasks can also be added to a Project Template
or a Concept. When a VPLM Task is added to a Project Template, an Action corresponding to that
VPLM Task is not created. However, when a Project is created from a Project Template containing
VPLM Tasks, the VPLM Tasks in the created Project will have the corresponding Actions created.

The following table shows the attribute mapping from the VPLM Task to the VPLM Action when
the Action is created.
VPLM Task Attribute VPLM Comment

Action
Attribute
Name Abstract
Description Description
Duration Duration
Estimated Start Planned Start
Date
Estimated End Planned End
Date
--- Duration Time Flag to indicate whether ENOVIA
Unit Program Central or VPLM is in
control at a given point. It is also
used to distinguish Actions created
by ENOVIA Program Central from
those created by CUS. Duration
Time Unit is a hidden VPLM
attribute.
--- Task The ENOVIA Program Central
Documentation object ID at the end of the URL to
hyperlink to the VPLM Task from an
e-mail.
For example:
60174.65398.28710.62612.
Task Documentation is a hidden
VPLM attribute.
VPLM Action Type --- The action type is not an Action
attribute, but is used to specify the
object type for the type of Action to
create.
VPLM Status Change

There is a ENOVIA Program Central web service called by VPLM to promote VPLM Tasks.
Two JPOs are involved:
• VPLMStatusChangeEvent_mxJPO.java
• VPLMStatusChangeEventBase_mxJPO.java
Only VPLMStatusChangeEventBase_mxJPO.java needs to be deployed as a web service.
The other (non-base) JPO is used for any customizations that might be needed. These two JPOs are
installed into the database when installing ENOVIA Program Central. Compiling
VPLMStatusChangeEventBase_mxJPO.java will generate the .wsdd and wsdl files that
can be deployed as web services.
For more information about deploying web services, see the ENOVIA Live Collaboration
Application Development Guide.

Deliverable Behavior
If a user attempts to remove a deliverable that is actually an Output Affected Object on the
corresponding VPLM Action, the removal will fail and the user will receive the warning message,
“VPLM added Deliverables may only be removed within VPLM.”
The Deliverables Report contains a rollup of all the deliverables for each Task in the WBS
structure. If a VPLM Object is added as a deliverable to a VPLM Task, additional processing is
needed to pick up the deliverables on the VPLM Action that corresponds to the VPLM Task. In
addition to retrieving the objects connected to each task via the Task Deliverable relationship, the
outputs on the corresponding VPLM Actions are also retrieved and displayed in the Deliverables
Report.
VPLM Tasks and Tasks can have distinct sets of allowed deliverable types.

Triggers
This section describes VPLM Task triggered behaviors.
In this section:
• VPLM Task Delete
• VPLM Subtasks of VPLM Tasks
• VPLM Task Promotion from Create to Assign
• VPLM Task Demotion from Assign to Create
• VPLM Task Promotion from Active to Review
• VPLM Task Demotion from Review to Active
• VPLM Task Promotion from Review to Complete
• VPLM Task Demotion from Complete to Review
• VPLM Task Change of Owner
• VPLM Initiated Actions in ENOVIA Program Central
VPLM Task Delete

When VPLM Tasks are deleted, their corresponding Actions are also deleted. Previously, they were
just marked as defunct. The following emxProgramCentral.properties file entry enables Action
deletion:
emxProgramCentral.VPLMMapping.DeleteAction=Y
VPLM Subtasks of VPLM Tasks

When a VPLM Task is added as a subtask of another VPLM Task, a parent-child link is created
between the two corresponding Actions, provided the two corresponding Actions are in the same
VPLM Instance, the Action types allow such links to be created, and Child Actions are enabled in
emxProgramCentral.properties.
VPLM Task Promotion from Create to Assign

The Check trigger on the Promote from Create to Assign does the following:
1. The VPLM task owner is checked to verify that he is in the Group corresponding to the VPLM
instance specified on the VPLM Task create page. If the user is not in this Group, the
promotion fails and the user receives the following error message, “The task owner must be in
the xxx Group” where xxx is the VPLM instance specified on the VPLM Task create page.
2. Gets the status and direct integration flag attribute values from the corresponding Action.
3. If this update fails, the promotion fails and the user receives an error message.
4. If this succeeds and the VPLM Action state is its equivalent of Create, the Action is promoted
to its equivalent of Assign.

VPLM Task Demotion from Assign to Create
The Action trigger on the Demote from Assign to Create updates the VPLM Action direct
integration flag attribute to “DirectIntegration01”.
VPLM Task Promotion from Active to Review

The Action trigger on the Promote from Active to Review updates the following VPLM Action
attributes:
VPLM Action Comment

Attribute
Duration Set to Estimated Duration value
Planned Start Date Set to Estimated Start value
Planned End Date Set to Estimated End value
Duration Time Set to “DirectIntegration01”
Unit ENOVIA in control.
VPLM Task Demotion from Review to Active

The Check trigger on the Demote from Review to Active does the following:
• If the direct integration flag value is not “DirectIntegration02”, the VPLM Action direct
integration flag attribute is updated to “DirectIntegration02”.
VPLM Task Promotion from Review to Complete

The Check trigger on the Promote from Review to Complete does the following:
1. If the Action status is not its equivalent of Review or Complete, the promotion fails and the
user receives an error message similar to “The VPLM Task and its corresponding VPLM
Action are not synchronized. Manual intervention is required.”
2. If the direct Action status is Review, the VPLM Action direct integration flag attribute is
updated to “DirectIntegration03”.
The Action trigger on the Promote from Review to Complete does the following:
1. Gets the Action status value.
2. If the Action status is its equivalent of Complete, the trigger completes successfully.
3. If not, updates are done to VPLM Action attributes as follows:
VPLM Action Comment

Attribute
Duration Set to Actual Duration value
Planned Start Date Set to Actual Start value
Planned End Date Set to Actual End value
4. The Action is promoted to its equivalent of Complete.

VPLM Task Demotion from Complete to Review
The Check trigger on the Demote from Complete to Review does the following:
1. Gets the status and direct integration flag attribute values from the corresponding Action.
2. If the Action status is in its equivalent of Complete, it is demoted to its equivalent of Review.
3. If this demotion fails, the demotion of the VPLM Task fails and the user receives the error
message, “Unable to demote the task from its “Complete” status since its corresponding
Action could not be demoted from its “Complete” status.”
The Action trigger on the Demote from Complete to Review updates the VPLM Action direct
integration flag attribute to “DirectIntegration01”.
VPLM Task Change of Owner

Changes are synchronized at every change of status. If the Task Owner and Action Owner are the
same at a status change, they are synchronized as follows:
Transition Behavior
Create to Assign Action owner is set to that of the Task
Assign to Active Task owner is set to that of the Action
Active to Review Task owner is set to that of the Action
Complete to Review Action owner is set to that of the Task
Review to Active Action owner is set to that of the Task
Active to Assign Task owner is set to that of the Action
Assign to Create Task owner is set to that of the Action
VPLM Initiated Actions in ENOVIA Program Central

The change of status web service doesn't just do simple promotes and demotes. Rather, it
synchronizes the lifecycle states of the VPLM Task and its corresponding VPLM Action. The Web
Service receives the state to which the VPLM Action has just attained. It will first verify the state is
the equivalent of Create, Assign, Active, or Review. If the target status is verified, the current
VPLM Task status is obtained and the required Promotes or Demotes are done to bring the task to
the target status.

VPLM Custom Objects in ENOVIA Program Central
VPLM Custom Objects can be included in ENOVIA Program Central, just as VPLM base
objects are. First, expose the VPLM custom objects to ENOVIA CAA Web Services, then
provide the necessary schema transactions to the VPLM-ENOVIA Adaplet, and lastly introduce
them in Business Modeler. This section contains the steps to include VPLM custom objects in
ENOVIA Program Central.
In this section:
• Exposing the VPLM Custom Object
• Schema Translations for the VPLM-ENOVIA Program Central
• Introduce CUSTOM Design Action in Business Modeler
Exposing the VPLM Custom Object

This topic is covered in detail in the Technical Article section of the ENOVIA CAA Web Services
documentation. The following example for an ENOVIA_CusAction_Design object details an
end-to-end scenario.
To expose the CUSTOM Design Action, you must update ENOVIA.xsd with
ENOVIA_CusAction_Design. The CusAction.custo file describes the
ENOVIA_CusAction_Design object. You must have a .custo file in order to update the
ENOVIA.xsd file. To update the ENOVIA.xsd file, do the following:
1. Introduce the CUSTOM Design Action key into the ENOVIA type by pasting
ENOVIA_CusAction_Design”>
<xs:selector xpath=”ENOVIA_CusAction_Design”/>
<xs:field xpath=”@id”/>
</xs:key>
after
<xs:key name=”ENOVIA_Action_Design”>
in the ENOVIA.xsd file, as shown below:
2. Introduce ENOVIA_CusAction_Design in the ENOVIA sequence by pasting:

<xs:element name=”ENOVIA_CusAction_Design”
type=”ENOVIA_CusAction_Design” minOccurs=”0” maxOccurs=”unbounded”/>
after

<xs:element name=”ENOVIA_Action_Design”>
in ENOVIA.xsd.
3. Finally, introduce ENOVIA_CusAction_Design as a complexType by pasting:

after
<xs:complexType name=”ENOVIA_Action_Design”>
in ENOVIA.xsd. Note that all attributes from CusAction.custo have been introduced into
ENOVIA.xsd, as well as a couple of special attributes. Note that ENOVIA_AFLAction is the
attribute’s prefix. You must append the masks, indicated below in RED, to the
ENOVIA_AFLAction.custo file, and load them in the database, in order for them to be taken
into consideration.
Schema Translations for the VPLM-ENOVIA Program Central

You must modify three schema files used by the VPLM-ENOVIA Program Central Adaplet.

1. VPLMDomain.xml keeps a record of VPLM Objects and the domain to which they belong. To
be consistent, even though the order is not important, insert the following:
<type name=”CUSTOM Design
Action”symbolic=”type_ENOVIA_CusAction_Design”domain=”CusAction”/>
somewhere after
<type name=”Design Action”.../>
2. Next, add the basic attributes of the Business Object to the VPLMBasics.xml file for
“CUSTOMDesign.” Paste the following:
after
in the VPLMBasics.xml file.
3. Also in the VPLMBasics.xml file, do the following, soon after
Add type_ENOVIA_CusAction_Design as the from type belonging to relationships Action to
Input Affected Object and Action to Output Affected Object.
4. Finally, add the remaining attributes for “CUSTOM Design Action” to VPLMSchema.xml.
Add the following:
somewhere after
in the VPLMBasics.xml file. Note that “CUSTOM Design Action” is derived from “External
Task”.

Introduce CUSTOM Design Action in Business Modeler
CUSTOM Design Action is introduced automatically to Business Modeler when you create or
modify a VPLM Vault in ENOVIA Program Central. The CUSTOM Design Action from VPLM
can be viewed from ENOVIA Program Central, which supports many languages. Please update the
emxFrameworkStringResource.properties base file with the Type and Attribute names of
CUSTOM Design Action. Also, provide translations for each of the languages in their respective
emxFrameworkStringResource_xx.properties file.
Custom objects that participate in the Structure Browser’s expand capability require special setup.
For more information, refer to Expanding Objects in Structure Browser in the ENOVIA Program
Central Administrator’s Guide.

5
Installing and Setting Up
Microsoft Project Integration
This section provides the System Administrator and Integration Administrator with the
information and instructions needed to install, configure, and maintain an ENOVIA Microsoft
Project Integration system.
The ENOVIA Microsoft Project Integration has two components:
• A server component, which enhances the Integration Framework
• A client component, which connects the MS Project application and IEF Client to the
Integration Exchange Framework
The ENOVIA Microsoft Project Integration Server requires installation of the Integration
Framework prior to installing ENOVIA Microsoft Project Integration Server. Refer to the
pre-requisites of the Integration Framework and install it before you install ENOVIA Microsoft
Project Integration Server.
For instructions on using Microsoft Project Integration to transfer project data between
Microsoft Project and ENOVIA Program Central, see the ENOVIA Program Central User’s
Guide.
In this section:
• Installing ENOVIA Microsoft Project Integration Server
• Installing ENOVIA Microsoft Project Integration Client
• Setting Up and Configuring
111
Installing ENOVIA Microsoft Project Integration
Server
The ENOVIA Microsoft Project Integration Server schema installation calls a JPO for
registration to the Integration Exchange Framework. You should check that the ENOVIA
installation has been properly configured for compilation of JPOs for a successful schema
selection.
This section describes how to install the ENOVIA Microsoft Project Integration Server.
In this section:
• Installers
• Precautions During Installation on UNIX
• Installing ENOVIA Microsoft Project Integration Server on Windows
• Post Installation Tasks for UNIX Users
• Post Installation Tasks for MS Project
Installers
To install the ENOVIA Microsoft Project Integration Server, you use these installers:
• ENOVIA Microsoft Project Integration Server Installer
• Windows—ENOVIAMicrosoftProjectIntegrationServer-V6R<version>.exe
• UNIX—ENOVIAMicrosoftProjectIntegrationServer-V6R<version>.Unix.bin
• ENOVIA Microsoft Project Integration Client Installer
• ENOVIAMicrosoftProjectIntegration-V6R<version>.exe
Precautions During Installation on UNIX

You must log in as a user with administration rights. Log in as root to install the ENOVIA
Microsoft Project Integration on UNIX. The user must have the following permissions:
• Permission to run the installer
• Permission to run MQL
• Write permission on the Platform Server staging directory
• Write permission to the user installation directory
• Java needs to be in the system PATH environment variable of the logged-in user
Before you start, make sure
• The TEMP variable (for Windows) or TMP (for UNIX) must be set to a valid directory.
• The drive where the TEMP variable points should have sufficient free space. The installer
executable size is approximately 4 MB.
• The Security Alert message is granted permission to proceed.
Ensure that the compatible version of JVM is installed. The JVM is available for download from
Sun’s Java web site.

Installing ENOVIA Microsoft Project Integration Server on Windows
1. Run ENOVIAMicrosoftProjectIntegrationServer-V6R<version>.exe. The Introduction dialog
box opens.
The Introduction dialog box specifies the component you are installing.
2. Click Next. The "Choose the ENOVIA Platform Server Folder" dialog box opens.
Select the location where the ENOVIA Platform Server folder is present.
3. Click Next. The “Enter the Bootstrap File Name” dialog box opens.
Specify the name of the bootstrap file for the schema installation in the “Enter bootstrap file
name” dialog box.
4. Click Next. The “Choose the Components to Install” dialog box opens.
Choose one of the following options in the Choose the Components to Install dialog box:
Full Installation. Installs both schema and user interface files. You must select this option if
you are installing ENOVIA Microsoft Project Integration Server the first time.
Schema. Installs only necessary schema components.
Update CSE Installer. Updates the ENOVIA Microsoft Project Integration CSE installer and
makes UI-related property file changes.
You must select Full Installation if it is a first time installation.
5. Click Next. The installer checks if the Integration Framework is installed. If it does not detect
a Integration Framework installation, the ENOVIA Microsoft Project Integration Server
installation does not proceed.
If you have already implemented/installed ENOVIA Designer Central in your environment,

you do not need to install the Integration Exchange Framework.
If the installer does not detect Designer Central or Integration Framework installation of the
same version, then a mismatch error is displayed and the installation is aborted.
The “Choose Install Folder” dialog box opens.

6. Click Next. The “Specify the Application Name” dialog box opens.
Specify the name of the web application with which EAR and WAR archives are used for
J2EE deployment.
7. Click Next. The “Inputs for Schema Selection” dialog box opens.
The Inputs for schema Selection dialog box is displayed only if you choose Full Installation
or Schema installation options in the Select Components to Install dialog box. The list of
vaults present in the database is shown for your selection. The user name and password to be
used for installing the schema should be specified.
8. Click Next. The “Pre-Installation Summary” dialog box opens.
The Pre-Installation Summary dialog box displays the components and the available disk space
for the installation.
9. Click Install to start installation. The schema files and CSE are installed on your computer.
The installer runs the MQL in silent mode, and schema components are installed.
10. Click Next. The Installation Complete dialog box opens.
Chapter 5: Installing and Setting Up Microsoft Project Integration 113

After successful installation, you must restart the Application server in the case of non-J2EE
installations. For a J2EE installation, you need to create the EAR and WAR archives and deploy
them in the web server.
Post Installation Tasks for UNIX Users

UNIX users must perform the following steps after ENOVIA Microsoft Project Integration server
is installed.
1. Go to the home directory of the stack, where ENOVIA Platform Modeling Studio and
ENOVIA Platform Server are installed. For example, /data1/MSPIV6R<version>.
2. Go to /core/scripts and add the path, /rmi/java/msoilib to the environment variable
MX_CLASSPATH in the business, matrix, mql, and system files.
Post Installation Tasks for MS Project

This section describes the tasks that must be done after ENOVIA Microsoft Project Integration
is installed.
By default, the GCO attribute MSPIntegrationLocalTransactionXMLPath assigns
C:\temp as the path for dumping the xml files created by ENOVIA Microsoft Project
Integration for MS Project in UNIX.
UNIX users must create a temp folder and update the path as /temp/ in the GCO attribute
MSPIntegrationLocalTransactionXMLPath. The user must have Write permission for the
temp directory. This must be done for MSProject integration to function.
1. Search for an object with Type "MSProjectInteg-GlobalConfig" and name "*MS*New*"

in the thick client.

2. The object with TNR—MSProjectInteg-GlobalConfig MSProjectNewArch 1 is
found.
3. In the attribute "MSPIntegrationRunningInRIPMode" enter "FALSE" if the Application

server and Platform Server are on two different machines. If the Platform Server and
Application Server are on same machine, the RIP mode value should be TRUE.
4. Create a directory called temp in the server machine. For example, /temp/. The root user
should have read and write permissions for the directory.
5. In the attribute "MSPIntegrationLocalTransactionXMLPath" store the directory path
and directory name.
6. The path must be defined in the format shown in the following table:
Server Platform Example of Directory to be Created

UNIX /temp/
The directory path should have:

"\" at the end for Windows.
"/" at the end for UNIX.
The trailing slash is extremely important. If the slash is missing, then an error message, Error
while reading parameters. Error :null is displayed when you use the integration.
In J2EE, the files are installed to the eMatrixRMI\STAGING directory.
The Admin type for GCO is installed by the Integration Exchange Framework and the
ENOVIA Microsoft Project Integration creates a business object of this type.

Installing ENOVIA Microsoft Project Integration
Client
This section describes how to install the client for ENOVIA Microsoft Project Integration. The
Windows installer for ENOVIA Microsoft Project Integration is
ENOVIACollaborationforMicrosoftProjectClient-V6R<version>. Microsoft Office and MS
Project applications are not compatible with UNIX.
Before you begin:

• The ENOVIA Microsoft Project Integration client needs .NET Framework 2.0 to be
installed before installing the client.
• On Windows Vista for Internet Explorer 7, protected mode should be turned off for the
application url.
• Close the MS Project application before you start installing the ENOVIA Microsoft Project
Integration Client.
• Uninstall any existing client installation. Close the MS Project application before you start
uninstalling the client installation.
In this section:
• Installing ENOVIA Microsoft Project Integration Client on Windows
• Installing ENOVIA Integration Exchange Framework Client
• Installation Failure
Installing ENOVIA Microsoft Project Integration Client on Windows

Use the following steps to install the ENOVIA Microsoft Project Integration Client. The client
version must match the server version. For example, only ENOVIA Microsoft Project
Integration Client version V6R2011x should be connected to ENOVIA Microsoft Project
Integration Server version V6R2011x.
The Integration Exchange Framework client is required for communication between ENOVIA
the Microsoft Project Integration Client and Server. The Integration Exchange Framework
provides folder navigation in the ENOVIA Open dialog in MS Project through the Namespace
extension.
Before you begin:

• Uninstall any previous version of ENOVIA Microsoft Project Integration Client before you
start installing the latest version of the ENOVIA Microsoft Project Integration Client.
1. Run ENOVIAMicrosoftProjectIntegration-V6R<version>.exe. The Introduction dialog box

opens.
The Introduction dialog box describes the component you are installing.

2. Click Next. If an existing ENOVIA Integration Exchange Framework client installation is
detected, then skip to step 3. If the Integration Exchange Framework client installation is not
detected, then install the ENOVIA Integration Exchange Framework client installable. See
Installing ENOVIA Integration Exchange Framework Client for details on installing the
ENOVIA Integration Exchange Framework client.
3. The “Choose Install Folder” dialog box opens.
Specify the location in your computer where you want to install the ENOVIA Microsoft
Project Integration Client.
4. Click Next. The “Specify Microsoft Project Version” dialog box opens.
Select the Microsoft MS Project version for which you want to install the integration in the
“Specify Microsoft Project Version” dialog box. Select one version from the list of supported
versions.
5. Click Next. The “Choose Microsoft Project Folder” dialog box opens.
Click Choose to browse and select a directory where the Microsoft Project executable,
winproj.exe, is located.
6. Click Next. The “SSO Environment setting” dialog box opens.
Select the SSO Enabled checkbox to enable Single Sign On environment. Enabling SSO
launches the browser and redirects the page to SSO for you to login when you click File >
ENOVIA > Connect from Microsoft applications.
7. Click Next. The “Close MSProject applications” dialog box opens.
A message to close all office applications at the time of installation is displayed. You must
close all Office applications for a successful installation.
8. Click Next. The “Pre-Installation Summary” dialog box opens.
In the Pre-Installation Summary, the Product Name and Version, Install Folder, and the Disk
Space information is displayed. You can review your selections before proceeding to the actual
installation.
9. Click Install to start your installation. The Installation Complete dialog box opens.
10. Click Done to complete the installation. Re-boot the machine for the client to function
properly.
Installing ENOVIA Integration Exchange Framework Client

Use the following steps to install the ENOVIA Integration Exchange Framework Client. It is
mandatory to install the ENOVIA Integration Exchange Framework Client. The ENOVIA
Integration Exchange Framework Client is not supported on UNIX platforms.
The Integration Exchange Framework client is required for communication between the
ENOVIA Microsoft Project Integration Client and Server. The Integration Exchange
Framework provides folder navigation in the ENOVIA Open dialog in MS Project through the
Namespace extension.
1. Run the ENOVIAIntegrationExchangeFrameworkClient-V6R<version>.exe. The

Introduction dialog box opens.
2. Click Next. The “Choose Install Folder” dialog box opens. Enter the path where you want to
install the ENOVIA Integration Exchange Framework Client.

If a previous installation of the client exists on your machine, the “Do you want to Continue”
dialog box opens. Click Next to overwrite the previous installation or click Cancel to exit.
3. Click Next. The “Select the server” dialog box opens. Enter the following:
Hostname. Specify the server you want to connect to. The default values of the Port number
and Application Name are displayed.
Port Number. Enter the port number you want to connect to. Port number 7001 is the default.
Application Name. Enter the appropriate application name. ENOVIA is the default.
JRE Path. Enter the path where Java is installed. For example, C:\Java\jre6.
4. Click Next. The “SSO Environment setting” dialog box opens. Click the SSO Enabled check
box to enable SSO settings.
5. Click Next. The Pre-Installation dialog box opens.
6. Click Install to start the installation.
7. Click Done to complete the installation. A warning message displays. Click Later to restart
your machine at some other time or click Reboot to restart your machine now.
Installation Failure
In case of failure when installing the ENOVIA Microsoft Project Integration client, do the
following.
1. Close the MS Project application and retry the installation.
2. Check the log file
ENOVIA_Microsoft_Project_Integration-V6R<version>_InstallLog.log in the
ENOVIA Microsoft Project Integration client install folder for errors, and report them to the
system administrator.

Setting Up and Configuring
This section explains the configuration of ENOVIA Microsoft Project Integration for System
Administrators who want to optimize the integration.
Before you begin:

• System Administrators need to know the MSProjectInteg-GlobalConfig Object and its
attributes.
In this section:
• Global Configuration Object
• Custom Mapping Fields Used
• Assigning and Unassigning the Integration
• Updating Assignments and Assigning GCO
• Role Based Access to Integration
• Integration FrameWork Encoding Support
• Editing ENOVIA Program Central Projects from MS Project
• Support for Project SubTyping
Global Configuration Object

The Administrator installs a sample Global Configuration Object based on the user
requirements. For ENOVIA Microsoft Project Integration, the Global Configuration Object
(GCO) is MSProjectNewArch with Revision 1.
The Global Configuration Objects set by the ENOVIA Microsoft Project Integration Server
Installation are specific to the ENOVIA Microsoft Project Integration.
This section lists the attributes that are specific to ENOVIA Microsoft Project Integration.
Custom Mapping Fields Used

If you are customizing a project, you should refrain from using the following custom fields in your
customization since ENOVIA Microsoft Project Integration is already using some of these. The
following custom mapping fields are used for XML mapping in the integration.
Attribute Mapped To Notes
FieldName Text1 Used by MSP Integration
State Text2 Used by MSP Integration
Owner Text3 Used by MSP Integration
TaskReq Text4 Used by MSP Integration
NodeType Text5 Used by MSP Integration

ProjectName Text21 Used by MSP Integration
Policy Text6 Used by MSP Integration
The user is advised to avoid using these fields for any custom mapping. If you must use these
characters, then a system administrator must re-map the Microsoft Project mapping file.
Assigning and Unassigning the Integration

The system administrator can assign or un-assign integration for a user. Only the user who has
system administrative privileges can do this operation.
Upon ENOVIA Microsoft Project Integration server installation, the MicrosoftProject User role is
installed. This role is specific to the integration.
This role is derived from the Integration User installed by the Integration Exchange Framework and
contains all the privileges of the Integration User role. The Integration User role will be installed as
the Parent role.
The User must be assigned the MicrosoftProject User role to access and use the ENOVIA
Microsoft Project Integration.
To unassign the integration, remove the MicrosoftProject User role from the user.
For details on assigning and unassigning a role for a user, see Business Process Services
Installation and Administrator’s guide.
You cannot assign the MicrosoftProject User role to a group.
Updating Assignments and Assigning GCO

For a specific user, you can use the Update Assignments function so that they will be assigned
collaborative products from the role they are assigned to. Update assignments for groups is not
supported.
This function can be used to select appropriate GCOs for ENOVIA Microsoft Project
Integration.
1. Click Actions > Designer > Update Assignments. The Select User page opens.
2. Select the user for whom you want to update assignments. See “Select Users” in the Business
Process Services User’s Guide.
3. Click Next. The “Step 2 of 2:Select GCOs for Assigned Integrations” lists all the integrations
that the user is assigned to.
4. Click the button corresponding to ENOVIA Microsoft Project Integration to open the GCO
Chooser page. Select the required GCO and click Submit.
5. Click Done.

Role Based Access to Integration
To use MS Project integration, the System Administrator needs to add the user to the
MicrosoftProject User role. This role MicrosoftProject User is created OOTB when ENOVIA
Microsoft Project Integration is installed.
Integration FrameWork Encoding Support

In IEF, encoding is made configurable, so that a user can have suitable encoding based on the
browser's support. Since the browser's default JVM (Java Virtual Machine) can support only a
specific set of encodings, a user needs to verify the JVM support before setting this property. By
default this property is set as UTF8 in ief.properties.
mcadIntegration.MCADCharset=UTF8
In addition to setting this property, the user needs to change the value of charset in the
“contentType” page directive from the common include file MCADTopInclude.inc located in the
Matrix/integrations/ief directory.
<%@page contentType="text/html; charset=UTF-8"%>
Editing ENOVIA Program Central Projects from MS Project

System Administrators should use the following steps to enable editing of ENOVIA Program
Central projects from MS Project:
1. Set the property emxProgramCentral.MSDI.MSPComponentInstalled to true in the
emxProgramCentral.properties file located in the staging and ematrix folder before
the warutil is built and deployed.
2. Set the property emxProgramCentral.MSDI.MSPComponentInstalled to true in the
RMI, Java, and Properties folders. The default value for the property is false.
3. Add the MicrosoftProject User role to the user. This allows all Program Central projects to be
editable in MS Project.
Support for Project SubTyping

You can create a project in ENOVIA Program Central using a subtype of ProjectSpace using the
Create Project option from ENOVIA Program Central. The features available for the project
created in ENOVIA Program Central are:
• Browse inside a Project of a derived type using ENOVIA Microsoft Project Integration
using Windows Explorer.
• Edit or view the derived project in Microsoft Project according to the user privileges by
using right-click menus from Windows Explorer, MS Project, or from the browser
interface.
• Search derived projects, if the integration is configured to support projects.
• View Properties of the derived project.
To enable support for project subtyping, do the following:

1. Create a type (for example, SubProjectSpace) from “Project Space”.
2. Click My Desk > Admin Tools >Property Registration > Admin Type in ENOVIA from
the browser in order to register this type.

3. Map Symbolic Name (type_name which is used to register this type) to command
MsoiProjectFolderContent in the typeNavigationMappings of
IEFDesktopConfigurations JPO. A sample mapping is
type_SubProjectSpace|@command_MsoiProjectFolderContent.
4. Restart the servers.

6
PLM Express
This chapter describes the administration required for PLM Express deployment.
In this section:
• User Roles
123
User Roles
The following table shows the mapping of ENOVIA Program Central privileges to roles available
in PLM Express:
:
Program Central Purpose PLM Express Role

Privilege
Program Lead Creates a program which becomes VPLMProjectAdministrator
a collection point for associating under ProgramManagement public Team working space
multiple PRG projects.
Project Lead (PRG) Creates PRG project and manages VPLMProjectLeader
its definition, such the WBS under ProgramManagement public Team working space
scheduling, project financials.
Defines resource plans, quality
and assessments.
Project Assessor Assesses the current health of a VPLMExperimenter
(PRG) project based on evaluation of the under ProgramManagement public Team working Space
project data. Produces resulting
status.
Project User (PRG) Views programs, projects and VPLMViewer
project information for which they under ProgramManagement public Team working space
have access routes. Project Users
can become members of a project
team and are assigned tasks such
as WBS Tasks, Routes, Issues,
Quality.
Project Creates and defines the project VPMADM
Administrator (PRG) templates for a company which are under ProgramResource public Team working space
used by project leaders in creating
PRG projects.
Microsoft Project User Role

The Microsoft Project User role can be manually assigned to users by doing the following:
1. Choose Tools > Administration > View My Company > People.
2. Click on the person you want to assign the Microsoft Project User role to.
3. Click Role in the category list.
4. Click Add Role from the page toolbar.
5. Use the Find Role page to locate and select the Microsoft Project User role for the person.

Index
A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W |X | Y | Z
Symbols content 21
% complete cost categories 19
defining percentages 31 cost ratio thresholds 36
rollup formula 42
D
A database schema 9
access date
for folders 21 manual entry 22
for groups and roles 25 triggers 61
alerts 22 deliverable
alternate menu trees 37 defining 29
application promotion completes task 30
Also see ENOVIA applications and suite. triggers 57
Application Exchange Framework DeliverablesPromoteTaskComplete 30
how related to Program Central 9 document sub-types 38
approvals 18 documentation 8
authentication of users 44
automation 56 E
emxFramework.FolderContentTypesThatTypesRe-
B quireGrants property 21
benefit categories 19 emxFramework.IncludeSubTypesForGrants
blocking routes 18 property 21
Business Manager role emxProgramCentral.EnableManualDateEntry 22
described 12 emxProgramCentral.properties 14
emxProgramCentral.TaskPercentages 31
ENOVIA applications
C items in 10
categories 19 eServiceApplicationProgramCentral.CostRatioThr
color definitions 36 esholdGreenYellow 36
configurable pages 16
125
eServiceApplicationProgramCentral.CostRatioThr J
esholdYellowRed 36 JPOs 46
eServiceApplicationProgramCentral.SlipThreshhol
dColor 37
eServiceApplicationProgramCentral.SlipThreshold K
GreenYellow 36 KavaCharts 38
eServiceApplicationProgramCentral.SlipThreshold
YellowRed 36
eServiceApplicationProgramCentralRPNThreshold M
.Max 35 manual entry for dates 22
eServiceApplicationProgramCentralRPNThreshold menus, alternate 37
.Red 35 Microsoft Project data transfers 123
eServiceApplicationProgramCentralRPNThreshold Microsoft Project Integration 111
.Yellow 35 model
eServiceProgramCentral.SearchableGroups 25 automation 63
eServiceSuiteProgramCentral.emxTreeAlternateM
enuName 38 O
External Program Lead role
online help 8
described 12
Organization Manager role
External Project Administrator role
described 12
described 12
External Project Lead role
described 12 P
External Project User role PDF files 8
described 12 percentage complete 31
PLM Express 123
F policy signatures 18
PolicyProjectSpaceStateActivePromoteCheck 42
financial categories 19
PolicyProjectSpaceStateReviewPromoteCheck 42
folder content 21
PolicyProjectTaskStateActivePromoteCheck 42
folder grants 21
PolicyProjectTaskStateReviewPromoteCheck 42
FolderContentTypesThatTypesRequireGrants
portfolio
property 21
automation 62
primary image 53
G product
grants for folder 21 automation 62
group access 25 product line
automation 61
Program Central
H checklist for setup 8
help, online 8 database schema 9
how related to AEF 9
related documentation 8
I Program Lead role
image, primary 53 described 12
imported information 39 project
IncludeSubTypesForGrants property 21 access
Installing ENOVIA Microsoft Project Integration group and roles 25
Client 116 alerts 22, 24
Installing ENOVIA Microsoft Project Integration import information 39
Server 112 promotion trigger 41

triggers 58 U
vault 15 user authentication 44
Project Administrator role user guides 8
described 12
project concept
triggers 57 V
project folder vault
access 21 project 15
content 21 searches 15
Project Lead role
described 12
project roles 25 W
project space WBS task
triggers 58 % complete 31, 42
Project User role, described 12 completing 30
properties 14 deliverables 29
promotion trigger 41
reminders 24
R triggers 59
readme 8 Workspace Vault grants 21
related documentation 8
reminders 24
roadmap settings 51
role
summary of roles 11
role access 25
routes, blocking 18
S
searches 15
signature requirements 18
slip thresholds 36
suite
Also see application.
T
test execution object
automation 64
threshold colors 36
timeline chart settings 51
trigger
dates 61
deliverables 57
for completing tasks 30
Originator attribute 56
project 58
project concept 57
project promotion 41
WBS task 59
WBS task promotion 41
Index 127

ENOVIA Program Central Administrator's Guide (V6R2011)

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

ENOVIA Program Central Administrator's Guide (V6R2011)

Uploaded by

Copyright:

Available Formats

ENOVIA Program Central™

© Dassault Systèmes, 2000 - 2009

All rights reserved.

This license came from:

JAVAMAILTM, VERSION 1.3.1

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

Chapter 1. Introduction ............................................................................................................... 7

Chapter 2. Configuring ENOVIA Program Central .................................................................. 13

Chapter 3. Setting Up VPLM Access........................................................................................ 67

Chapter 4. VPLM Objects .......................................................................................................... 95

4 ENOVIA Program Central Administrator’s Guide

Chapter 5. Installing and Setting Up Microsoft Project Integration .................................... 111

Chapter 6. PLM Express.......................................................................................................... 123

Index ...................................................................................................................... 125

About the ENOVIA Product Line Shared Component

8 ENOVIA Program Central Administrator’s Guide

Application Exchange Framework

Item For information, refer to:

Directories for shared and common components

10 ENOVIA Program Central Administrator’s Guide

Use of General ENOVIA Client Applications

Role Description Available for:

12 ENOVIA Program Central Administrator’s Guide

14 ENOVIA Program Central Administrator’s Guide

Vaults and Searches

Chapter 2: Configuring ENOVIA Program Central 15

16 ENOVIA Program Central Administrator’s Guide

Chapter 2: Configuring ENOVIA Program Central 17

18 ENOVIA Program Central Administrator’s Guide

This section describes settings for projects.

Configuring Financial Cost and Benefit Categories

To define the template categories

Chapter 2: Configuring ENOVIA Program Central 19

To configure names for categories

20 ENOVIA Program Central Administrator’s Guide

Defining the Content of Project Folders

To add types for project folder content

Defining Access Grants for Project Folders

Chapter 2: Configuring ENOVIA Program Central 21

Allowing Manual Date Entry

Configuring Project Alerts

Enabling the Timer Servlet

22 ENOVIA Program Central Administrator’s Guide

Setting Up Multiple TimerCommands on one Server

Chapter 2: Configuring ENOVIA Program Central 23

# Turn off sending notification at run-time

24 ENOVIA Program Central Administrator’s Guide

# Comma separated list of initial Roles that will be displayed when

Showing Project Roles

Adding Project Subtypes

To create a project subtype

Chapter 2: Configuring ENOVIA Program Central 25

To create a policy for the subtype

To register the subtype and policy

Setting Budget Transaction Thresholds

26 ENOVIA Program Central Administrator’s Guide

Chapter 2: Configuring ENOVIA Program Central 27

This section describes settings for tasks.

Defining the WBS Task Type Hierarchy

Here are examples of two task hierarchies.

To add additional task types to the WBS structure

28 ENOVIA Program Central Administrator’s Guide

Defining WBS Task Deliverables