MxCatia UsersGuide 10.7.SP1

Enovia MatrixOne Catia
Integration
Version 10.7
Users Guide
Copyright and Trademark Information
Dassault Systmes, 2005-2007.
All rights reserved.

PROPRIETARY RIGHTS NOTICE: This documentation is proprietary property of MatrixOne, Inc. and Dassault Systmes. In accordance with the terms and conditions of the Software
License Agreement between the Customer and MatrixOne, the Customer is allowed to print as many copies as necessary of documentation copyrighted by Dassault Systmes relating to the
ENOVIA MatrixOne software being used. This documentation shall be treated as confidential information and may only be used by employees or contractors with the Customer in accordance
with the Agreement.
MatrixOne, Adaplet, Compliance Connect, eMatrix, Matrix10, Synchronicity, DesignSync and Team Central are registered trademarks of Dassault Systmes.
Matrix Collaboration Server, FCS, AEF, Application Exchange Framework, Application Development Kit, MatrixOne Engineering Central, MatrixOne Library Central, MatrixOne Materials
Compliance Central, MatrixOne Product Central, MatrixOne Program Central, MatrixOne Sourcing Central, MatrixOne Specification Central, MatrixOne Supplier Central, MatrixOne
Semiconductor Accelerator, MatrixOne Aerospace and Defense Accelerator for Program Management, MatrixOne Apparel Accelerator for Design and Development, MatrixOne Automotive
Accelerator for Program Management, MatrixOne Medical Device Accelerator for Regulatory Compliance, MatrixOne Business Metrics Module, MatrixOne Cost Analytics Module,
MatrixOne Manufacturing Bill-of-Material Module, IconMail, ImageIcon and Star Browser are trademarks of Dassault Systmes.
Oracle is a registered trademark of Oracle Corporation, Redwood City, California. DB2, AIX, and WebSphere are registered trademarks of IBM Corporation. WebLogic is a registered
trademark of BEA Systems, Inc. Solaris, UltraSPARC, Java, JavaServer Pages, JDBC, and J2EE are registered trademarks of Sun Microsystems, Inc. Windows XP and Internet Explorer are
registered trademarks of Microsoft Corp. HP and HP-UX are registered trademarks of HP. All other product names and services identified throughout this book are recognized as trademarks,
registered trademarks, or service marks of their respective companies.
The documentation that accompanies ENOVIA MatrixOne applications describes the applications as delivered by MatrixOne, Inc. This documentation includes readme files, online help, user
guides, and administrator guides. If changes are made to an application or to the underlying framework, MatrixOne Inc. and Dassault Systmes cannot ensure the accuracy of this
documentation. These changes include but are not limited to: changing onscreen text, adding or removing fields on a page, making changes to the administrative objects in the schema, adding
new JSPs or changing existing JSPs, changing trigger programs, changing the installation or login process, or changing the values in any properties file. For instructions on customizing the
provided documentation, see the Application Exchange Framework Administrators Guide.
DM-MX-50-10-71
MatrixOne, Inc.
210 Littleton Road
Westford, MA 01886, USA
Telephone: 978-589-4000
Fax: 978-589-5700
Email: info@matrixone.com
Web Address: http://www.matrixone.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 Servlet-API
[under Apache License, Version 2.0 above]
FTP
Copyright (c) 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.
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.
distribution.
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
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ImageEncoder
ImageEncoder - abstract class for writing out an image
Copyright (C) 1996 by Jef Poskanzer <jef@acme.com>. All rights reserved.
distribution.
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
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
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
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.
distribution.
"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.]
Libxml2
The MIT License
Copyright (C) 1998-2003 Daniel Veillard. All Rights Reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do
so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR
ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
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.
distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission,
please contact openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
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.
distribution.
"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
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
The Apache Software License, Version 1.1
Copyright (c) 2000 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditionsare met:
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 "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.
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 IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIESOF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION ORITS
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OFUSE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED ANDON 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 OFSUCH 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, please see <http://www.apache.org/>.
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
THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND
DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the Government shall have only "Restricted Rights" in the software and related documentation as
defined in the Federal Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you are acquiring the software on behalf of the Department of Defense, the software shall be classified as
"Commercial Computer Software" and the Government shall have only "Restricted Rights" as defined in Clause 252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the authors grant
the U.S. Government and others acting in its behalf permission to use and distribute the software in accordance with the terms specified in this license.
Xalan
Xerces
Xerces2
Table of Contents
Chapter 1. Overview .................................................................................................................. 13

About Enovia MatrixOne Catia Integration .................................................................................... 13
Application Window and Features .................................................................................................. 14
Catia-centric or Client-centric Features ................................................................................... 15
Matrix-centric Features ............................................................................................................ 15
Advanced Features .................................................................................................................. 16
Before Reading This Guide .................................................................................... 16
Getting the Most Out of This Guide ....................................................................... 16
Chapter 2. CAD-Centric Features............................................................................................. 17

Connecting to Matrix....................................................................................................................... 18
Connecting to an Existing Session .......................................................................................... 18
Checking in Catia Design to Matrix................................................................................................. 19
Checking in the Active Model................................................................................................... 20
Change Type on Checkin ................................................................................................. 23
Checking In All Models ............................................................................................................ 23
Checking Out from Matrix to Catia.................................................................................................. 24
Checking Out using Open > Load............................................................................................ 24
Checkout Page Options ................................................................................................... 25
Using Open > Insert Option ..................................................................................................... 29
Using the Checkout Option ............................................................................................................. 29
Using Checkout > Load Option ................................................................................................ 30
Using Checkout > Insert Option............................................................................................... 31
Checking Out RFA Objects ...................................................................................................... 31
Lock/Unlock Option......................................................................................................................... 31
Lock/Unlock of RFA Objects .................................................................................................... 33
Synch Attributes From Matrix ......................................................................................................... 33
Attribute Synch To Matrix................................................................................................................ 35
Versions .......................................................................................................................................... 36
Recognizing Versions ..................................................................................................................... 37
Recognize Version Tab Options ...................................................................................... 40
Managing Workspace ..................................................................................................................... 41
Check For Update........................................................................................................................... 42
Check for Update > All Option ......................................................................................... 43
Start Design.................................................................................................................................... 44
Disconnect ...................................................................................................................................... 46
Preferences .................................................................................................................................... 46
Catia Preferences .................................................................................................................... 47
Derived Output Preferences ............................................................................................. 48
Checkin Preferences ........................................................................................................ 48
Checkout Preferences ...................................................................................................... 49
Miscellaneous Preferences .............................................................................................. 49
Setting Default Type Policy Settings ................................................................................ 50
Setting Default Tables ...................................................................................................... 50
Help ................................................................................................................................................ 50
Table of Contents 3
About ...................................................................................................................... 50
Chapter 3. Matrix-Centric Features .......................................................................................... 51

Introduction To Matrix Features ..................................................................................................... 51
Lateral Navigation (Virtual Compound Document)................................................................... 51
Related Views in Checkout ...................................................................................................... 52
Save As .................................................................................................................................... 52
Rename.................................................................................................................................... 52
Purge........................................................................................................................................ 52
Preview .................................................................................................................................... 53
EBOM Synchronization ............................................................................................................ 53
Baseline ................................................................................................................................... 53
Design Change Report ............................................................................................................ 53
Release CAD Tool.................................................................................................................... 53
CAD Structure Navigation ........................................................................................................ 54
Localized User Messages............................................................................................................... 54
Chapter 4. Advanced Features ................................................................................................. 55

Transformations Support ................................................................................................................ 55
Derived Output Support .................................................................................................................. 55
Native Derived Output Support ................................................................................................ 55
Supported Formats for CATParts and CATProducts ....................................................... 56
Supported Formats for CATDrawings .............................................................................. 56
Manual Derived Outputs .......................................................................................................... 56
Custom Derived Outputs.......................................................................................................... 57
Generate New Structure ................................................................................................................. 59
Prerequisites ............................................................................................................................ 59
New Attributes on the Object Node .................................................................................. 59
New Attribute on the Relationship Node ......................................................................................... 61
Relationship Modification Status in Matrix ............................................................................... 61
New Transformation Matrix ...................................................................................................... 62
Mandatory Attribute Support........................................................................................................... 62
Chapter 5. Appendix .................................................................................................................. 65

Working set (activity file): The Heart of Integration ........................................................................ 65
User Exits........................................................................................................................................ 66
Rapid File Access ........................................................................................................................... 66
Versions and Revisions................................................................................................................... 66
Using Applet Log and Setting Ping Interval .................................................................................... 67
Attribute Mapping From and To Matrix ............................................................................................ 67
Summary Attributes ................................................................................................................. 68
GCO Mapping for Summary Information .......................................................................... 68
Custom Properties ................................................................................................................... 69
GCO Mapping for Custom Properties .............................................................................. 69
Client Settings................................................................................................................................. 70
Server Section: ................................................................................................................. 70
Client Section: .................................................................................................................. 70
Rapid Version Detection ................................................................................................................. 71
Recognition Program ............................................................................................................... 74
LatestRevisionVersion ..................................................................................................... 74
UpdateNextInRevision ..................................................................................................... 74
4 Enovia MatrixOne Catia Integration Users Guide

Show Only Nodes Currently Unrecognized ...................................................................... 74
System Defined Attributes .............................................................................................................. 74
Table of Contents 5
1
Overview
The MatrixOne Catia integration under the new JSP-based architecture is part of the Designer
Central Integrations from MatrixOne.
Application Window and Features
Catia-centric or Client-centric Features
Matrix-centric Features
Advanced Features
About Enovia MatrixOne Catia Integration
The MatrixOne Catia integration under the new JSP-based architecture is part of the Designer
Central Integrations from MatrixOne. These integrations use the browser as the integration agent.
To install and run the MatrixOne Catia integration, you must first install Designer Central from
MatrixOne.
The integration has two components:
A server component, which enhances Designer Central
A client component, which connects the Catia to Designer Central.
13
This document provides information on using the integration from a CAD users perspective. The
client side (Catia side) component of the integration is also referred to as CSE (Client Specific
Extension).
The CSE (Client Specific Extension) can be installed on the Catia client or server machine. Before
installing the CSE, it is important to install the Matrix server side harness for the CSE to work
successfully.
The MatrixOne Catia integration is web-based by default . It can interact with Matrix either through
an intranet or the Internet. All file upload or download handled by the integration is secure. Once
the client is installed, the upgrade of the client is done automatically through the web.
The MatrixOne Catia integration supports the following languages:
English
Japanese
French
German
Application Window and Features
Features can be categorized as Catia-centric features, Matrix-centric features, and Advanced

features.
After successful installation of the MatrixOne Catia CSE, the main menu of Catia displays a
pulldown Matrix menu., as shown below:

Catia-centric or Client-centric Features
The Matrix menu has the following options for all Matrix-related operations:
Connect
CheckIn
Active Model
All Open Models
Open
Load
Insert
Checkout
Load
Insert
Lock/Unlock
Synch. Attributes From Matrix
Active File
Active Structure
Synch. Attributes To Matrix
Active File
Active Structure
Versions
Recognize Version
Check for Update
All
Current
Start Design
Manage Workspace
Disconnect
Preferences
Help
About
Matrix-centric Features
The following features are mainly Matrix-specific. The CAD tool is not involved in executing these
features.
Lateral Navigation (Virtual assembly creation)
Related Views in checkout
Save as
Rename
Finalization
EBOM Synchronize
Chapter 1: Overview 15
Labeling
Preview
Purge
Advanced Features
The following options are the advanced features:
Configuration Support
EFCS Support
Before Reading This Guide
You should already:

Know how to use your CAD tool
Have the MatrixOne Designer Central integration installed
Have the Enovia MatrixOne Catia integration installed
MatrixOne Designer Central must be configured by an Integration Administrator
Be assigned a username, password, roles and access privileges to the objects you need to work
with
Getting the Most Out of This Guide
This guide describes how you use the Enovia MatrixOne Catia integration menus and windows to
perform tasks. MatrixOne Deisgner Central features are used to complete the tasks. Refer to the
MatrixOne Deisgner Central Users Guide for detailed description of each feature. Use the
following sections to find information and instructions for using Enovia MatrixOne Catia
integration:
Chapter 2, CAD-Centric Features
Chapter 3, Matrix-Centric Features
Chapter 4, Advanced Features

2
CAD-Centric Features
The Matrix menu in Catia contain items that let you perform Matrix operations from the CAD
tool.
In this section:
Connecting to Matrix
Checking in Catia Design to Matrix
Checking Out from Matrix to Catia
Lock/Unlock Option
Synch Attributes From Matrix
Attribute Synch To Matrix
Versions
Recognizing Versions
Managing Workspace
Check For Update
Start Design
Disconnect
Preferences
17
Connecting to Matrix
After you install Catia CSE, the menu Matrix is displayed in the Catia application. You must
first connect to Matrix to start using the integration. When finished you need to log out and
disconnect from Matrix.
Before you begin:

Your Integration Administrator must assign the integration to you.
The integration must be installed and the Matrix menu must be displayed in the CAD tool.
1. In Catia application, click Matrix > Connect.

2. If there are no previous sessions of Matrix running, the URL for integration opens in your
default browser.
3. Specify your Username and Password and click Login to connect to Matrix. Upon successful
login, a signing certificate is displayed to load an applet. Click Yes to accept the applet.
If you are already logged in to Designer Central, click Connect to join an existing session.
Connecting to an Existing Session

If your default browser is Internet Explorer, then the Catia Integration opens Internet Explorer
when you click Connect. If you want to run the application in Mozilla or Firefox, you can go to the
integration URL in the browser, and click Connect from Catia.
If you already have a browser with a valid connection to the server site, the Matrix > Connect
operation displays a message box as shown below and disables the Matrix > Connect menu:
Chapter 2: CAD-Centric Features 19

Checking in Catia Design to Matrix
When you create a new CAD object or edit an existing CAD object, you need to check it into
Matrix to save the changes in Matrix.
In this section:
Checking in the Active Model
Checking In All Models
Use the Matrix > Checkin option in the Catia application to check in the active design or all open
designs in the application.
Checking in the Active Model

1. Click Matrix > Checkin > Active Model in the Catia application.

2. An activity bar is displayed as the Checkin page is built for the active model and is displayed
in the browser.
Options in Checkin Page

The Checkin page has a tree table for the CAD objects. The tree table for the objects selected
has various columns displaying the information specific to the object in each row. Multiple
root nodes are displayed in the Checkin page if the design for the selected objects for checkin
have multiple root nodes.
The left side of the tree-table control shows the tree. It displays the object structure (compound
document) in the form of a tree. This tree also displays the lock status for the object using the
following icons:
icon indicates that no user has locked the object.
icon indicates that some user, whose name is displayed in the Locked By column,
has locked the object.
The following lists the various columns that are displayed in the Checkin page.
Selection CheckboxThe first column is a checkbox column, which allows you to select
the objects for checkin. You can select the objects for checkin even if you do not have the
lock for the design. Upon checkin, the lock for the design is automatically aqquired if you
have the permission to lock and checkin the design.

Derived OuputThe second column with the icon [ ] is for the selection of derived
outputs for the Catia Document. The Catia Document can have more than one derived
output. You can indicate your choice by clicking this image. You can change the default
value of this checkbox from the Preferences page. Click to display a pop-up dialog
listing the derived output.
If SmartBOM is not installed, CATIA cannot save ".CATProduct" files as ".stbom" or ".exe".
Creating Derived outputs for these file types fails and an error message is displayed.
Check in of Derived Outputs fail with the message, Store Not Found if the integration is
installed on AEF versions 10.6.3 or 10.7. A Store must be assigned manually before you start using
the integration if the integration is installed on AEF 10.6.3 or 10.7 stack. This issue is resolved for
all later versions of AEF.
Assign FolderClick Browse and the Select Folder page opens.

Select the folder from the list of available folders displayed. This folder is the location
where the object is stored on checkin.
StatusThe Status column displays the status of the object as:
New: if the object does not exist in Matrix
Exists: if the object exists in Matrix
Modified: if the object is modified in the Catia Application since last checkin/
checkout

Locked ByIf the Catia design being checked in already exists in Matrix, and is locked
by any user, then this column indicates the name of this user. In the case of new document
checkin, this is set to the default value --.
Target RevisionYou can check in with any target revision you want by selecting the
target revision or clicking Next to start a new revision cycle. In the case of a new CAD
design checkin, this is set by default to Next. For example, if the policy has the revision
sequence of A, B, C, the first checkin results in the revision A.
TypeSelect the DesignType you want to apply to the object in the DesignType column
where the available design types are displayed as a dropdown list.
Design PolicyIf the object is new, the integration shows the possible Designs (types) for
the particular Catia design.
Your system administrator creates these administrative objects for you. The Design Policy
combo box lists the possible policies for the given types. If you change the type, then the
policy list is updated.
If the object you are checking in is not new, then the Design Policy columns are not
displayed and the exact type and policy of the object the user is checking in is displayed.
StateYou can see the current state of the design in the lifecycle.
Current RevisionYou can see the Current Revision of the Catia design being checked
in. In the case of new CAD design checkin, this is set by default to --.
VersionThe version column shows the version you are working with. In the case of a
new document checkin, this is set by default to --.
VersionPolicyYou can see the Version Policy used by the document being checked in.
If the CAD design being checked in is new, then the Version Policy combo box lists the
possible policies for this type of Catia design.
If the object checked in is not new, the Version Policy indicates the exact policy of the
object.
DescriptionYou can see the description specified by the user for the design.
3. The bottom panel of the Checkin page has the following options:
Select New and ModifiedClick the Select New and Modified option to select all the
objects for which the status is shown as MODIFIED or NEW in the Status column. This
flag is obtained from the CAD application based on the files modified by the user. All
modified or new objects are shown sorted in the list.
Assign FolderClick the Assign Folder option to assign a location for all the objects to
be stored on checkin. Click Browse and the Select Folder page opens.
Select the folder from the list of available folders displayed. This folder is the location
where the object is stored on checkin.
4. Click Checkin to checkin the selected document-objects or click Cancel to cancel the
Checkin.
Options during Checkin
The following section describes the various options available during checkin:
Check in CommentYou can specify any comment during checkin in the Checkin
Comments text area. The comments are stored as an attribute in the CAD-object in the
Matrix. You can search for the CAD-objects based on the comments.
Delete Local filesSelect this check box to delete the local file on the disk.

Copy AttributesSelect this option to copy the attributes from an Catia design being
checked into Matrix. Only modified or new attributes are updated during the Checkin.
Attribute synchronization requires attribute mapping in the Integration Global Config
Object. Refer to the Synch Attributes From Matrix section for more details.
Create VersionSelect this option for the integration to create a new version every time
checkin is performed. If it is not checked, then checkin is done to the same business object
from where the file was checked out. The earlier copy of the file is lost, if you prefer to
check in to the same business object (switching off the check box).
If the Create Version check box is not selected and a new object is being checked in, the integration
creates a new version in Matrix.
Retain LockThe default behaviour of the integration is to remove the lock on the business
object once a user checks in the business object (file). Select the Retain Lock check box to
retain the lock after checkin. This effectively means that the user does not need to checkout/
lock again to checkin again.
Background CheckinSelect this option to use the CAD tool even when the checkin is in
progress in the background for the selected designs. A success message is displayed once the
checkin is complete. A BackgroundCheckinSuccessLog<date>_<time>.htm log
file is created for each checkin, and the location of the log file is the default directory. For more
details on log files, see Designer Central System Administrators Guide.
Select all ChildrenSelect this option to select all the children recursively once the parent
component is selected for checkin.
Change Type on Checkin

When you check in an object using the Matrix > Checkin option from the CAD tool, Designer
Central recognizes the object from the entry in your working set.
Designer Central verifies whether the document type sent by the CSE and the object type for which
the entry was found in the working set matches the bus-type mapping defined in the GCO for that
particular document type when an entry is found in the working set for the design that is
checked-in. There is no change in type if the entry in the working set matches the bus type mapping
for the design.
To change the type of the object in Matrix to match the type with the input document type, select
the type from the dropdown list in the DesignType column in the Checkin page. The DesignType
dropdown list displays all types that are mapped against the input document type in the bus-type
mapping of the GCO. Check in the object to change the type of object in Matrix.
For more details on changing the type on checkin, see the MatrixOne Designer Central Users
Guide.
Checking In All Models

1. Click Matrix > Checkin > All Open Models.
The Checkin page opens displaying all open models. An activity bar is displayed as the
Checkin page is built.
2. Select the models you want to check in and click Checkin. See Options during Checkin for
details for the options available in the Checkin page.

The integration identifies the file being checked in. Refer to Appendix A on working set (activity
file) for details. In case it cant identify the file being checked in (for example, the file is copied or
renamed but Matrix has an object of the same name), the checkin command fails displaying a
message stating which file it could not identify. If this happens, you need to use the Versions option
and identify the version using the preview facility. The Versions dialog can be edited for
un-recognized files.
The system administrator must set the Global Config Object attribute
MCADInteg-AcquireLockOnCheckin. to TRUE to aqquire a lock on checkin by default. For
more details, see the Designer Central System Administrators Guide.
Checking Out from Matrix to Catia
To edit an existing CAD object you need to check out the file from Matrix.
In this section:
Using Open > Load
Using Open > Insert
You can check out objects from Matrix using the following methods:
Using the Open optionTo check out a CAD object of the Catia type, click the Open option
from the Catia application. The Open menu option has the following options:
LoadClick this option to load the files after checkout in Catia depending on your choice
in the checkout page. You can select the objects you want to check out from the Designer
Central PowerView page or find the objects you want to check out using the Search
option.
InsertThis option can be used to find an object for checkout in Designer Central and
insert the first selected object in the assembly that is currently in session. There should be
an active CATProduct in session in order to insert component.
Selecting Objects for Checkout: You can select objects for checkout using the following
options:
Using SearchFrom the Matrix page, click Search > Designer > Search to find the
objects you want to check out using Designer Central. You can then open the documents
in Catia applications by using the Checkout menu from Catia.
Using Designer Central PowerViewFrom the Matrix page, click My Desk > Designer
> My View to open the PowerView page and select the objects you want to check out.
Using Open > Load

The following procedure describes the Open > Load method of checking out objects from Matrix.

1. Click Matrix > Open > Load in the Catia application.
2. The Matrix page opens. You can select the objects you want to check out using the following
options:
Using the Designer Central PowerView Page The following steps describe the procedure
for checking out objects from the PowerView page:
a ) In the Matrix page, click My Desk > Designer > My View and the Designer Central
PowerView page opens.
b ) Click the Recently Checkin Objects, Workspaces, or Locked Objects tab and the
available objects are listed.
c ) Select the objects you want to check out and click Actions > Checkout.
d ) The Checkout page opens. Select the objects in the Checkout page and click
Checkout to check out the selected objects.
Using the Search PageThe following steps describe the procedure for checking out objects
using the Search option:
a ) In the Matrix page, click Search > Designer > Search and the Search page opens.
b ) Specify values in the Type, Name, Revision, Owner, or Vault and click Find. The
Search Results page opens.
c ) Click the name of the object you want to check out and the PortalView page for the
object opens.
3. Click Actions > Checkout in the Summary, Navigate tab in the CAD Portal View page.

The Checkout page for the object opens.
Checkout Page Options

The following columns are displayed in the Checkout page for the selected object or objects:.
Checkout Tree
The left side of the tree-table control shows the tree. It displays the object structure (compound
objects) in the form of a tree.
Selection checkbox
The first column is a checkbox column, which allows you to select the objects for checkout.
Preview
Click the icon for the preview of the object if the object was previously checked in with
preview.
Locked by
If the object being checked out is locked by any user, this column indicates the name of this
user.
Lock checkbox
Select this checkbox to lock the object during checkout.
Local Checkout
Select this checkbox to check out the selected objects to the Checkout directory in your local
machine.
Other information columns
The other columns include Design, Revision and Version which help you to identify the
CAD-object during checkout.
Access Status Column

The Access Status is shown as VIEW, EDIT if the user has permissions for Checkout, Lock,
Checkin, Revise and Modify for the object.
The Access Status is shown as VIEW if the user only has permissions to Read and Checkout
the object
Document Version
This column displays the current lateral view applied to the objects in the Checkout page.
The following options are available in the Checkout page for selecting objects for Checkout:
Local Checkout All
Click this option to select all the objects on the Checkout page for checking out locally.
Local Checkout None
Click this option to cancel the selection for local checkout for all the objects on the Checkout
page.
Select Required
Selects all the objects, which must be included in the structure for proper loading of the CAD
model in the CAD Tool.
Lock All
Click this option to select all the lockable objects on the Checkout page for checking out with a
lock.
Lock None
Click this option to deselect all objects on the Checkout page that are selected for locking.
The following options are available for setting the lateral views on the top frame of the Checkout
page.
Document Version Options
The Document Version drop-down contains the names of user-configured programs in
Matrix that automatically apply some lateral navigation rule to a selected design node and
refresh its underlying structure.
Manual lateral navigation modifies the revision and version of the design by picking the
appropriate values in the revision and version drop-down. The program picked from the
drop-down applies the user-defined program logic to accomplish the same thing. The
following options are available:
As StoredGives you the precise structure stored at the time of checkin
LatestVersion-Finds the latest version of all nodes of a selected node and its underlying
structure
LatestRevisionFinds the latest finalized revisions of all nodes of the selected node and
its underlying structure.
Related Documents Options
The Related Documents drop-down contains the names of user-configured programs in
Matrix that will retrieve related documents of each document node displayed in the checkout
dialog. The particular document node/s to apply the selected program to will have to be
selected before the program is selected. OOTB Designer Central delivers the Related
Drawing program that finds and displays for each design node the associated drawing if it
exists. This drawing can now be selected for checkout if needed. Administrators may configure
additional programs that look for other kinds of related documents.
Default values for both Related Documents and Document Version programs can be
configured in the GCO which applies the lateral views by default as the Checkout page is
initially rendered.

Refresh Selected
Click Refresh Selected to refresh the view of the selected components after you change the
views through the Document Version and Related Documents options. Only the views of the
selected components are refreshed.
Refresh All
Select the Refresh All option to refresh the view of all the components listed in the Checkout
page.
Reset To As Stored
Select this option to reset the view to the As Stored type for the selected objects on the
Checkout page.
The following options are available in the bottom frame of the Checkout page:
Checkout directory
This shows the default checkout directory. If you want to check out to a different directory,
click Choose on the Checkout page, which opens the Select Directory dialog box. Select the
directory where you want to check out the objects and click OK.
Reset the default directory setting in the Preferences page if you want to permanently change
the default directory.
Copy attributes on checkout
Check the Copy Attributes option for the integration to copy the attributes from Matrix to
Catia. These attributes are set when opening the CAD model.
The attributes are mapped in Matrix before copying them. These mappings are done as a part of
Integration installations.
Load files on checkout:

Check the Load files check box to load the CAD objects after checkout. If this option is not
selected, the files are stored in the local machine, but not loaded in Catia.
Apply View to Children Only:

Check the Apply View to Children Only option to apply the view selected to only the
children of selected objects. If not selected, the view is applied to children as well as selected
objects.
If during checkout, the files selected for checkout are found in the same directory, then a
Confirm File Overwrite dialog is displayed with the list of files already existing on the your
machine. Check the files you want to overwrite and click Submit to overwrite the files.
Select First Level Children
Select this option to select only the first-level children when you select the parent nodes.
Select All Children
Select this option to select all the child components when you select the parent node of the
child components.
Using Open > Insert

This option can be used to find an object for checkout in Designer Central and insert the first
selected object in the assembly that is currently in session. There should be an active CATProduct
in session in order to insert component.
If the component is already loaded in session, then this feature should not be used. The standard
CATIA command "Add Existing" must be used to eliminate the risk of overwriting file during
checkout which is already loaded in CATIA.
The integration inserts the checked out part in "0,0,0" position of the current part in session.
Selection of checkout on a non-versioned object results in the following message. "There are no
files in the current object. Going to checkout Cat Versioned Part block-xyz A.0 instead.
Using the Checkout Option
Click Matrix > Checkout for the following options:

Checkout > Load
Checkout > Insert
Using Checkout > Load Option

Choose Matrix > Checkout > Load from Catia for checking out and loading the objects in Catia
after you locate the objects you want to check out using the Designer Central functions Designer
Central PowerView and Search in the browser.

1. Select the objects using the PowerView or the Search option in DesignerCentral and click
Checkout. The Checkout page opens.
2. Select the objects in the Checkout page and click Checkout. A message asks you to select
Checkout from the Matrix menu in the Catia application.
3. Click Matrix > Checkout > Load in Catia.
The selected objects are checked out to Catia.

If you do not select the Load files on checkout option on the Checkout page, the objects you
selected for checkout are downloaded to your machine to the location specified in checkout
directory field in the absence of CAD tool.
All the checkout options available are similar to options explained in Checkout Page Options.

Using Checkout > Insert Option
1. Click Matrix > Checkout > Insert to insert the file in the active file existing in the CAD tool.
You can select where you want to insert the file in the already active file open in Catia.
2. Click Escape or Ctrl+C to cancel the operation.
Checking Out RFA Objects

When the user selects checkout for an object, the user will be displayed in the Checkout page with
an additional Local Checkout check-box against each cadobject. If the user does not select this
checkbox, the file will not be downloaded to the local disk; instead, the integration will load the file
from the RFA locationall such files will be loaded in Read-Only mode.
If the user selects the local checkout option then the file will be downloaded from the RFA
location to the local disk (to the directory specified in the Checkout Directory text box in the
checkout page) and will be loaded from there. If the user chooses not to load the files from the RFA
location then the files will be loaded in Read-Only mode and the files will not be editable. The user
needs to attain lock to such files which will cause the file to get downloaded to the local-disk and
will become editable (writable).
Lock/Unlock Option
The Lock/Unlock command helps the user to lock/unlock the active model in Catia. The
integration allows you to check in the CAD-object only if you have the lock on it.
To Lock/Unlock Object in Matrix
1. Click Matrix > Lock/Unlock after you modify an object to lock the object during checkin to
prevent other users from modifying the object you locked.

2. Click the Lock/Unlock option to open the Lock/Unlock page. The current status of the
CAD-object in Matrix is displayed in this page. You can change the lock status by selecting the
objects for which you want to change the status on the Lock/Unlock page.
3. Select an option below:

Click Submit to change the lock or unlock status.
Click Lock All to select all objects for locking.
Click Lock Modified to select all objects for which the status is shown as modified in the
status column. This flag is obtained from the CAD tool based on the files that are modified
by the user. All modified objects are shown sorted in the list.
Click Unlock All to select all the objects for unlocking.
If the Integration cannot detect the exact version of the file, an error message is displayed. You can
use the Versions dialog to identify the version.
In Catia if a file is read-only, a LOCK icon is displayed. If the file subsequently becomes writable
then CATIA displays the icon as UNLOCKED.The integratrion sets the file as read-only if the user
does not have lock and makes the file writable once the user attains lock.
Lock/Unlock of RFA Objects

If a file is opened in the CAD tool from an RFA location then the file will not be editable. The user
needs to attain a lock on the file to be able to make changes to the file. When the user selects
Lock-Unlock menu item the Lock-Unlock page will display. The user needs to Lock the
RFA files which he/she intends to lock. Upon clicking Submit the RFA files will be downloaded to
the hard-disk and the integration will re-load the file from the local-disk. The file is loaded in
writable mode and the user can edit the changes if required. The file from the hard-link opeartion is
deleted by the integration.
Synch Attributes From Matrix
Attribute synch allows you to transfer attributes from Matrix and set them in the active file or the
active structure open in the Catia application. To make attribute synch active, the attributes must be

mapped in your Global Configuration Object. The system administrator must map the attributes of
your choice in the Global Configuration Object.
The attributes are synchronized if the object is modified or new during the checkin /checkout
process if you select the Copy Attributes check box. Attribute Synch is the function which
synchronizes the attribute without the checkin/checkout operation.
Due to Catia API limitations, Parameter attributes are not mapped for drawings and PDM
attributes are not also not mapped during Attribute Synchronization.
PDM attributes are not mapped for Analysis and AnalysisResults.
If the value of an attribute received from Matrix is same as that existing in the CAD tool, the CSE
does not update the attribute.
For details on mapping the attributes in GCO, see the MatrixOne Catia System Administrator
Guide.
1. Click Matrix > Attrib Synch From Matrix to see the following options:
Active Modelsynchs attributes from the Matrix database to the CAD object open in the
Catia application.
Active Structuresynchs attributes from the Matrix database to the active CAD
structure open in the Catia application.
The Synch. Attributes command supports following types of attributes:

Summary information: These attributes can be seen by selecting Edit > Properties in Catia.
These are treated as system attributes.
Custom Attributes: Custom attributes can be seen in the Properties dialog under the Product
tab. The custom attributes are treated as normal attributes.
Param AttributesClick in Catia to view or add param attributes.

PDM AttributesThese attributes are handled internally by Catia.
2. A message is displayed after the attribute synchronization is completed successfully.

Attribute Synch To Matrix
Attribute synch allows you to transfer attributes to Matrix from the active file or the active
structure open in the Catia application. To make attribute synch active, the attributes must be
mapped in your Global Config Object. The system administrator must map the attributes of your
choice in the Global Configuration Object.
1. Click Matrix > Attrib Synch To Matrix to see the following options:
Active Filesynchs attributes to the Matrix database from the CAD object open in the
Catia application.
Active Structuresynchs attributes to the Matrix database from the active CAD
structure open in the Catia application.
You can transfer the System, Custom, Param, and PDM attributes to the Matrix database.
Catia drawing title blocks are also examples of attributes managed by Matrix. You must
associate the drawing title block notes to a file attribute. Catia attributes must be mapped properly
to the Matrix attributes for the attribute transfer to function. In CATIA V5, AttrSynch will work only
on the user-defined Parameters (Set Up > Parameters > Info).
2. A message is displayed after the attribute synchronization is completed successfully.
Versions
1. Click Matrix > Versions.

The Versions page opens listing all the revisions of the CAD objects in the current viewport of
Catia.
2. The highlighted row indicates the version the you are using. Click ) for the review of the
version to open in a new browser window.
If you open a file having a version that could not be detected by the integration (multiple versions
of the current model is existing in Matrix, but integration cannot recognize the version user is
working on), you can use the Versions dialog to recognize the version. For example, you might be
working on a file c:\bolt.prt. If you copy this file to D:\, the integration cannot recognize the
version in D:\. In that case, commands like Attribute Synch fail with the message shown below,
which asks the user to recognize the version using the Versions command.
Recognizing Versions

If you open a file whose version could not be detected by the integration (multiple versions of the
current design exist in Matrix, but integration cannot recognize the version you are working on),
then you cannot perform functions such as Checkin, Lock-UnLock, Synchronize Attributes.
When you try to perform the Lock/Unlock operation for an unrecognized version, the following
message is displayed:
You need to recognize the version of the CAD object in Matrix to perform the operations
mentioned above. The procedure below is used to recognize a version.
1. Click Matrix > Recognize Version from the Catia application.

The Recognize Version page opens in your browser.
The Recognize Version page has the following tabs:

Recognize Version
Unrecognized Nodes
Custom View
The following columns are available in the table displayed in the Recognize Version page
under the Recognize Version tab:
Namethe name of the object
Statusthe status of the document. This can hold the following two values:
UNRECOGNIZED or RECOGNIZED
DesignTypethe matrix type of the document.
Revisionthe Revision of the document, which is blank () if the document status is
UNRECOGNIZED
Versionthe version of the document, which is blank () if the document status is
UNRECOGNIZED
CurrentPaththe current path of the document
2. Select the Unrecognized Nodes tab in the Recognize Version page
The Unrecognized Nodes are listed:

The following columns are also available in the table displayed under the Unrecognized Nodes tab
in the Recognize Version page:
Document Namethe name of the UNRECOGNIZED document
Document Typethe cad-type of the of the UNRECOGNIZED document
MatrixTypethe cad-type of the of the UNRECOGNIZED document
Revisionthe available revisions of this document on the Matrix with which the document
can be recognized
Versionthe available versions of the selected Revsion of this document on the Matrix with
which the document can be recognized
Statusthe status of the document, which can be either UNRECOGNIZED or
RECOGNIZED
Actionthe user can use this hyperlink to recognize or unrecognize the document. If the
status of this document is UNRECOGNIZED the user can recognize the document
using this hyperlink and vice-versa.
The following options are available under the Unrecognized Nodes tab in the Recognize Version
page:
Show Only Nodes Currently Unrecognizedif selected, this check box if selected shows
only the UNRECOGNIZED documents
Recognize All Selectedallows the user to RECOGNIZE all the selected Documents.
Unrecognize All Selectedallows the user to UNRECOGNIZE all the selected Documents.
3. Select the object for which you want to recognize the version and specify the Revision and
Version of the object with which the object is recognized. Then click Recognize All Selected
to recognize the nodes.
You can also click the icon in the Action column to recognize the version of the object.
The status of the selected node changes to Recognized.
4. After you recognize the objects using the options available under the Unrecognized Nodes tab,
click the Recognize Version tab and click the Recognize Version link available to complete
the recognition of the object.

5. A message is displayed in your SolidWorks application that displays the objects that were
recognized successfully along with their Revision or Version for which they were recognized.
Check For Update
If auser (for example, user1) has checked out a document in read-only mode (i.e. without
acquiring a lock) then the document may undergo changes by another user (user2). If user1
wants to update his local copy of the document with the current one then he can use the feature
Check for Update.
The Check for Update > All allows you to update all files that you checked out without lock.

Check for Update > All
1. Click Matrix > Check for Update-All to update all the documents that you checked out
without a lock.
The Design Change Report opens in your browser.
Click (+) to expand the drawings displayed in the Design Change Report. The latest structure
of the drawing is displayed. All the components are preselected on the Design Change Report.
The new components and sub-assemblies are highlighted in a green color, and the deleted
structure is highlighted in a red color. The components or drawings that are not modified or
deleted cannot be selected.
The following options are available in the table displayed in the Design Change Report:
Namethe name of the document
Design Typethe type of document in Matrix
Current Revisionthe current revision as available in the CAD tool
Current Versionthe current version of the document as available in the CAD tool
Updated Revisionthe updated / latest revision as available in Matrix
Updated Version:the updated / latest revision as available in Matrix
File Locationthe location of the file
Click the icon displayed in the Design Change Report table if you want to change the
location of the design download to your local disk for reference. The Select Directory
dialog box opens
Reason for changethis describes the reason for change. For example, the reason can be
Later Version in System.
LockedBythe person who has a lock on the document
Ownerthe person who owns the document
2. Select the objects you want to update and click Submit.
A message is displayed stating that the objects selected are updated and the objects that could
not be updated are also listed.
If there are design files currently open in Catia that are checked out without lock, then
Designer Central cannot over-write such files, and the files are not updated. A message is
displayed which lists the files that were successfully updated along with a list of files that
could not be updated.
For more details on generating the Design Change Report from the browser, see the Designer
Central User Guide.
Start Design

MCAD Designers can initiate the process of creating a new CAD Model using the Start Design
feature.
Upon initiating the process, MCAD designers are shown a list of templates (as shown below) from
which to create the CAD Models:

After you choose a template and click the Submit button, Designer Central displays the Create
Object page associated with the selected template object, as shown below:
The MCAD Designer must enter the values for Type, Name, Policy, Autoname Series, and Custom
Revision Level.
Click the Submit button. The Checkout page opens which you can use to check out the newly
created CAD Object.
For more details on Start Design, see MatrixOne Designer Central Users Guide.
Managing Workspace
A workspace is a collection of folders that contains objects, documents, and other information that
you use while working with MatrixOne Catia integration. The workspace allows you to manage the
objects that are in your machine using the Local Workspace as well as share the data with other
users using the Matrix workspaces. You can access the workspaces using the Matrix > Manage
Workspace option available in the Matrix menu in Catia.
1. In Catia, click Matrix > Manage Workspace.

The Workspaces page opens.
2. The Workspaces page displays the Local Workspace and the Matrix Workspaces in the left
frame of the page.
3. Click (+) to expand and view the folder in Local Workspaces that shows all the files in your
default directory. The Type, Revision, Version, and the Size of the files are displayed. Using
the Actions menu, you can copy, move, revert, refresh, lock, or unlock the selected objects in
the workspace. Only you can view your Local Workspaces.
4. Click (+) to expand and view the workspace folders in the Matrix Workspaces. You can create
new workspaces or assign permissions to other users for viewing Matrix Workspaces.
For more details on Workspace Management, see the Designer Central User Guide.
Disconnect
Click Matrix > Disconnect to disconnect Catia from Matrix. A message displays for confirming
the disconnect:
Click Yes to disconnect from Catia. The browser session may continue to be active.
Preferences

This section describes the various server-side preferences and their options.
1. Click Matrix > Preferences in the Catia application.
The Preferences page opens in your browser.
The Preferences page has the following tabs:

Global

MxCatiaV5
Catia Preferences
Using the Preferences page, you can set the preferences for the following functions :
Checkin
Checkout
Miscellaneous
DerivedOutput
Default Type Policy Settings
Selected Default Tables
Checkin Preferences
You can set the following preferences for Checkin:
Delete local filesSelect this option to select the Delete Local Files option in the Checkin
page by default
Retain LockSelect this option to select the Retain Lock option in the Checkin page by
default.
Copy AttributesSelect this option to select the Copy Attributes option in the Checkin page
by default.
Copy Relationship AttributesSelect this option to copy the Relationship attributes upon
checkin by default.
Create versionSelect this option to select the Create Version option in the Checkin page by
default.
Apply to ChildrenSelect this option to select the Apply to Children option in the Checkin
page by default
Use Bulk LoadingSelect this option to use bulk loading for checkin by default.
Show Object Details Page After CheckinSelect this option to open the object details page
of the object that is checked in.
Background CheckinSelect this option to select the Background Checkin option in the
Checkin page by default.
Delete Files BehaviourSelect DeleteSelectedLocalFiles or DeleteAllFiles from the drop
down. Select DeleteSelectedLocalFiles to delete only the files that are selected in the Checkin
page. Select DeleteAllFiles to delete the files that are selected in the Checkin page as well as
the files with EXISTS and EXIST_TypeChange .
BackgroundCheckinDirectoryClick and select a directory in your machine where you

want to store the objects upon background checkin.
AutoGenerationForManualDerivedOutputSelect this option to enable auto generation of
manual derived output option in the Derived Output page.
Checkout Preferences
The following preferences can be set for Checkout in the Checkout section in Preferences page:

Load ObjectsSelect this option to select the Load Objects option by default in the
Checkout page.
Lock ObjectsSelect this option to select the objects in the Checkout page for lock by
default.
Copy AttributesSelect this option to select the Copy Attributes option by default in the
Checkout page.
Select First Level ChildrenSelect this option to select the Select First Level Children
option by default in the Checkout page.
Copy Relationship AttributesSelect this option to Copy the Relationship Attributes by
default during Checkout.
Warn for File OverwriteSelect this option to enable a warning page before any existing
files are overwritten due to checkout.
Related View registryYou can select your choice of related views registry here. Views in
the particular view registry appear here.
User Directory Alias ModeSelect the user directory alias mode to allow the DL Names or
aliases for the directory from the options:
not allowedthe DLNames are not allowed and displayed.
allowedthe DLNames and the other directories are displayed when you browse to select
a location for checkout.
currentonly the DLNames are displayed when you browse to select a location for
checkout.
Default Checkout Directory You can also set your default checkout directory in the
Checkout Preferences.
Miscellaneous Preferences
You can set the following preferences in this section:
Select Children if parent is selectedSelect this option to select the child components by
default when a parent node is selected.
Use Zip in File OperationsSelect this option to enable zip compression for file transactions
in Matrix.
Progressive LoadingSelect this option to bring the structure information while selecting
checkout from the object or upon expanding the structure in the Checkout or the Promote
page
ProcessInactiveInstancesSelect this option for all the instances in the CAD tool to be
considered for processing such as, Checkin, Checkout, Lock and so on
Default Expand LevelSet the default number of levels of expansion of a CAD structure
when displayed.
Derived Output Preferences

The Derived Output section on the Preferences page lists all the Derived Output types, listed in the
Integration Global Config Object, with checkboxes. The selected types from this list are shown
pre-selected during Checkin.
Select the Derived Output types by selecting the check boxes from the list.
The following file formats are supported:

image_jpg
postscript
cgrOutput
igesOutput
stepOutput
sessionOutput
exeOutput
hsfOutput
txtOutput
wrlOutput
stbomOutput
3dxmlOutput
stlOutput
modelOutput
3dmapOutput
hcgOutput
vpsOutput
dxfOutput
dwgOutput
cgmOutput
svgOutput
gl2Output
catalogOutput
pdfOutput
tifOutput
ig2Output
Setting Default Type Policy Settings

The Default Type Policy Settings in the Preferences page display the policy set for the CAD type
by the administrator. The administrator can enforce a default a policy for a particular Type.
Setting Default Tables

You can set the default table to be applied to the list of Designer Central pages on the Preferences
page. Select the default table you want to apply to the appropriate pages in Designer Central from
the drop-down list of workspace tables displayed.
Help

Click Matrix > Help to open the Help for Catia CSE.
About
Click Matrix > About to view the MatrixOne Catia Integration version and the compatible
Designer Central version.

3
Matrix-Centric Features
Introduction To Matrix Features
Matrix features are available only in Designer Central through your browser while using the
MatrixOne Catia integration. The features listed are not available in the Matrix menu in the Catia
application. The following sections describe the features available in Designer Central.
Lateral Navigation (Virtual Compound Document)

Lateral Navigation is a way of creating a virtual compound document.
Suppose you created a compound document with two documents in it. Compound document A1
has documents C1 and C2. Now you check them in for the first time to create A1: A.0, C1: A.0 and
C2: A.0. You check out documents C1 and C2 several times and create their versions A.2. The
Compound document A1: A.0 is still pointing to documents C1 and C2 of Version A.0.
In the checkout page of the Compound Document A1: A.0, you see the tree with documents in A.0.
Suppose you want to move to document versions C1 A.1 and C2 A.2, you can select the combo box
of the Versions in the Checkout page and change them. Check out Compound Document A1 with
A.0 version, document C1 with A.1 version, and document C2 with A.2 version. This structure
does not exist in Matrix but virtually can be created during checkout.
With the help of the virtual assembly feature, you can re-use almost all referenced files checked
into Matrix. You can create many combinations and re-use all referenced files in Matrix.
51
Related Views in Checkout
There are two combo boxes appearing on the top of the Checkout page. The combo box on the right
hand side is for Document Version. The combo box on the left hand side is for Related
Documents. Related Documents has one program for showing the Related Drawing.
Related Documents is not valid for Catia.
When you select one row and click for a particular view, the integration displays the selected view
for its children (not for the selected node). If you do not select anything, the integration applies
views to all the nodes in selection. Using this feature, you can verify whether the structure being
checked out is loaded in Catia.
The following Lateral Views for objects are available:
AsStored
This view shows the default version of the CAD-objects in the tree table that are stored in Matrix.
LatestVersion
This view shows the latest version of the CAD-objects in the tree table.
LatestRevision
This view gives the latest finalized revision for the document-objects in the tree table. This revision
may or may not be in the final state. If no such objects exist, it will show the same
document-object.
Depending upon your requirements, the system administrator can create new programs and register
them. The new programs appear as an option after they are registered.
For more details, see the Designer Central User Guide.
Save As
Save As is a Matrix-centric operation which allows you to save an object with a different name.
The Save As option is available in Designer Central in the Search Results page, the objects
PortalView page, or the PowerView page. For more details, see the Designer Central User Guide.
Rename
The Rename option allows you to rename the selected object and store the object in Matrix using
the new name. The Rename option is available in Designer Central in the Search Results page, the
objects PortalView page, or the PowerView page.
Due to Catia API limitations, rename of design tables is not supported.
Batch Rename does not update references in drawing when the drawing is connected to multiple
objects.

Purge
The Purge option in Designer Central allows you to purge all minor versions of a major object.
When purge is done, the finalized major revision replaces the where used cases of versions purged.
You cannot purge the version from which you have finalized.
Preview
The Preview option allows you to preview a design before you perform any function on the design.
The Preview option is available using the icon in several places in Designer Central.
EBOM Synchronization
EBOM synchronization appears after finalization of the stream. A default implementation for
creating an EBOM for a design file with references has been provided. Part objects are created
corresponding to each design file object. These Part objects are then connected using the EBOM
relationship.
The EBOM Synchronization option is available in the PortalView page, Search Results page, and
PowerView page in Designer Central. For more details, see the Designer Central User Guide.
Baseline
You can label any particular compound document using the Baseline option available in Designer
Central.
You can add any baseline of your choice for the selected compound document. If the same baseline
is present in any of the versions of the document, the baseline is not allowed. Baselines should be
unique in the version stream. For more details, see the Designer Central User Guide.
Design Change Report

In a collaborative authoring environment, designers should be informed of the changes being made
to the designs that are authored collaboratively.
If multiple integrations are assigned to you, this feature allows you to select the integration for
which you want to generate the report.
The Design Change Report provides the following functions for the MCAD user:
Notification when changes occur to the CAD design or when a design is undergoing some
changes
Generation of the design change report for all the CAD designs checked out without a lock
Flagging the outdated designs
Updating or refreshing the local copy of this design with the latest version of the design
The Design Change Report option is available in Designer Central using Actions > Designer >
Design Change Report in the MatrixOne application. For details on generating the Design Change
Report using the CAD tool, see the Design Change Report section.
Chapter 3: Matrix-Centric Features 53

Release CAD Tool
Click the Release CAD Tool button ( ) in the Tools menu in a MatrixOne application page to
release the Catia application or to cancel operations such as Checkin, Open, or Checkout.
CAD Structure Navigation

The Navigate option is available on the Portal View page in Designer Central for the Catia design
which allows you to view the child objects and the related items for the object.

4
Advanced Features
Transformations Support
The Integration supports Transformations. The CSE checks for attribute mapping on the
relationship CADSubComponent. If the relativeXform attribute is mapped on the
relationship then the Transformations functionality starts working.
During checkin the relative Transformations information is extracted and set on the corresponding
relationship in the design structure. Similarly during checkout this information is received and set
on the corresponding parent-child (assembly-component) relationship and the model is rebuilt.
Derived Output Support
Integration supports checkin of derived output files of derived output files. These derived output
files can be dynamically generated (native) or may already exist on disk (user-defined).
Native Derived Output Support

The integration uses the native CAD tool API's to programmatically generate these file during
checking based on the users' preferences and selections. The files are generated in the same
directory as the CATIA V5 files and are deleted upon completion of the checkin depending on the
55
value of delete_on_checkin in the CatDerivedOutputOptions. The integration supports the
following native derived outputs with the necessary additions to the global configuration object.:
image_jpg
postscript
cgrOutput
igesOutput
stepOutput
sessionOutput
exeOutput
hsfOutput
txtOutput
wrlOutput
stbomOutput
3dxmlOutput
stlOutput
modelOutput
3dmapOutput
hcgOutput
vpsOutput
dxfOutput
dwgOutput
cgmOutput
svgOutput
gl2Output
catalogOutput
pdfOutput
tifOutput
ig2Output
Manual Derived Outputs

Manual Derived Output option is available in the Derived Output page. The Manual Derived
Output files should be present in your machine and are not generated by the CSE. Select the
checkbox under the Manual Generation column and click Submit in the Derived Output page to
generate the Manual Derived Output for the selected formats.
If the Manual Derived Output files are not present in you machine, then the GCO flag,
IEF-AllowAutoGenerationForManualDerivedOutput must be set to true to enable
automatic generation of Manual Derived Outputs and allow checkin of the derived output files.

When IEF-AllowAutoGenerationForManualDerivedOutput flag is set to false,
and an user tries to auto generate and checkin the files, the following error message is displayed
and checking in of files is not allowed.
Custom Derived Outputs

Custom derived outputs are user-defined or third party output files. The Integration supports the
checkin of these types of derived outputs. To use this feature, a user needs to note the following
points:
Third Party files or user-defined custom files must reside in the local working directory.
A Derived file should have the same name as the file it was created from.
Example: For a TestPart.sldprt, if the Custom Derived Output has a .zip format, the
file name should be TestPart.zip.
Within the GCO the Customer should define the types using the postfix (Example: gli, .zip) so
that such files are considered as Custom Derived Output.
Steps to get support for Custom/User-Defined Derived Output:
The user-defined derived outputs must be added to the global configuration object. The following
attributes of the global configuration object must be edited,
MCADInteg-BusTypeMapping
MCADInteg-TypeClassMapping
MCADInteg-TypeDerivedOutputMapping
MCADInteg-TypeFormatMapping
The chosen format may also need to be added to Matrix and to the allowed formats of the
governing policies, and the range for the 'CAD Type' attribute will have to be updated.
For example, to add support for third party .zip files, use the following steps:
Represent the Custom Derived Output type using the userfile_extension convention.
In a case where the file has a .zip extension, this type should be userfile_zip. Update
the MCADInteg-BusTypeMapping attribute in GCO as follows:
userfile_zip|Derived Output
Chapter 4: Advanced Features 57

It is very important to follow the convention userfile_extension for representing the custom derived
output type. During checkin operation, the CSE will check for the prefix userfile_ to identify
user-defined or third party derived output types. In such a case, the CSE will search for the files
with the extension as defined using the userfile_extension convention, in the same folder as the
model file.
Update the GCO attribute MCADInteg-TypeClassMapping as follows:

TYPE_DERIVEDOUTPUT_LIKE|userfile_zip
Categorize this derived output type depending on the CAD type as follows and update the
GCO attribute MCADInteg-TypeDerivedOutputMapping. In this case if .zip files are
used for all types Parts, Assemblies and Drawings, then the following mappings must be
added:
assembly|userfile_zip
component|userfile_zip
drawing|userfile_zip
In the Business module, add the format for the derived output type. In this case, the user can add the
format ZIP:
In Business module, search for the Attribute with name CAD Type. Open this attribute
for editing and go to the Ranges tab. Add to the range of the values the type representation
userfile_extension for this custom derived output type. In this case, it would be
userfile_zip.
In the Business module, add this newly added format to the Allowed Formats of the following
policies:
Derived Output Policy
Design Policy
Versioned Design Policy
Update the GCO attribute MCADInteg-TypeFormatMapping as follows:
userfile_zip|Derived Output, ZIP
After checkin the CSE will delete these derived output files if Delete Files on Checkin is
selected.
All the derived outputs will be checked in with separate formats of the same Derived Output Object
or the CAD Type Object depending on the user setting as follows:
If the MCADInteg-CreateDerivedOutoutObj flag in the GCO is set to TRUE, the
derived outputs will be checked in the corresponding formats of the same Derived Output
object linked to the CAD Model.
If the MCADInteg-CreateDerivedOutoutObj flag in the GCO is set to FALSE, the
derived outputs will be checked in the corresponding formats of the same CAD Model object.
The user can change the default settings for native derived outputs using the Preferences
command.
The user can also make the selections on the Checkin page using the column with the icon for
derived output files for the CAD model.
If SmartBOM is not installed, CATIA cannot save ".CATProduct" files as ".stbom" or ".exe".
Creating Derived outputs for these file types fails and an error message is displayed.

Generate New Structure
This feature allows users of the MatrixOne Catia integration to create new CAD files and structures
and to modify the existing structures.
After creating or modifying the structures you can check out that structure to the CAD-Tool and the
structure will be modified accordingly. Information regarding newly created structures or modified
structures is provided to the CSE who uses this information to modify and/or create new files to
generate the desired structure on the design files on the desktop.
The New Structure Generation allows a third party product Configurator/Viewer to generate new
structure in Matrix and set attribute values on that CAD structure and relationships, according to
the Designer Central guidelines.
Prerequisites
The following are prerequisites for Generate New Structure to function properly:
In the GCO, MCADInteg-MxToCADRelAttribMapping should be populated with the
following value to ensure that the transformations from the CAD tool are mapped with the
Spatial Location attribute of the server:
CAD SubComponent, Spatial
Location|CADSubcomponent,relativeXform
In the LCO, MCADInteg-CopyRelAttribOnCheckin should be set to true to ensure
relationship attributes are taken into consideration during checkin
In the LCO, MCADInteg-CopyRelAttribOnCheckout should be set to true to ensure
relationship attributes are taken into consideration during checkout
New Attributes on the Object Node

Following are the new attributes on CAD Object Node as reflected in the CADObjects details
page:
Modified in Matrix : This attribute signifies whether the structure of the CAD Object has
been modified or not. Possible values are true or false. The default value is
false. If the user leaves this blank then a false value is interpreted and the structure is
not modified.
Newly Created in Matrix: This attribute signifies whether the CAD Object has been newly
created in the Matrix database. Possible values are true or false. If the user specifies
true then this object has been newly created in the Matrix database and has no file
associated with it in Matrix. When the user does a checkout operation the CSE is informed that
this object is newly created in Matrix and the CSE creates a file for this object. The default
value is false. If the user leaves this blank then a false value is interpreted and the
CAD object is not newly created in Matrix.
When the relationship provided while generating a new structure is "new", then the user must
specify the instance name in reference designator so that the original instance is not renamed and
the newly added instance will have the new transformation matrix and new instance name.

New Attribute on the Relationship Node
Relationship Modification Status in Matrix

This attribute signifies the modified relationship between the Parent and Child objects. Possible
values are new, modified, deleted, or existing. The meaning of each of value is explained
below:
Newthe relationship between the parent and the child is new. For example, a component is
being newly added to an assembly.
Modified the relationship between the parent and child has been modified, for example,
because the child component was moved to a new position in the parent assembly.
Deletedthe child is being deleted from the parent. When the user checks out the assembly,
the child component should not participate as a child component in the assembly.
Existingthere is an existing relationship between the parent and the child and the
relationship has not been modified in any of the above ways.
If the user doesnt specify any of the above values, by default, its value is interpreted as existing.
New Transformation Matrix

This attribute is the new transformation matrix that is applicable for modified, new, and
deleted relationships of the Matrix. It is a string of 16 double values separated by commas in a
4X4 transformation matrix by the CSE. The significance of this attribute is dependent upon the
value of the relationship modification Status in Matrix and is discussed below:
Newnew Transformation Matrix signifies the position at which the child component will
be positioned in the parent assembly.
Modifiedthe CSE will apply the new transformation to an existing child component in the
parent assembly thus re-positioning the child component in the parent-assembly.
Deletedthe new transformation has no meaning in this case and will not be used. The CS
picks-up the old transformation and searches for the child component and deletes the child
component from the parent assembly.
Existingthe new transformation has no meaning in this case and will not be used.
Using the above attributes in the CADOBJECT node and the relationship node, you can do the
following:
Create a new structure
Add a new node to the structure
Delete an existing node from a structure
Reposition an existing node in a structure
Mandatory Attribute Support
There is a new entry in the GCO to allow the System Administrator to provide the mapping:
IEF-CADToMxMandatoryAttrMapping

Mandatory Attributes are supported for the following reasons:
1. To allow the user to synchronize certain attributes from CAD to Matrix, whether or not the
user has selected the copy attributes or not in the checkin page.
2. To allow the system administrator to provide mandatory attributes for a value that should be
used, whether or not the value exists on the CAD tool.
3. To allow the system administrator to provide a value that can be over-written by the CSE if the
CSE chooses.
4. To allow the CSE to provide the value of the mandatory attributes.
Point 1 is mandatory. If the System Administrator marks some attributes to be required by
specifying the attributes in the IEF-CADToMxMandatoryAttrMapping in the GCO, then
the attributes are always synchronized whether or not copy-Attributes is selected or not.
Additionally, one of points 2, 3, or 4 is applicable for a given required attribute. To enable this, the
format of the mandatory attribute defines the type of the required attribute as discussed below.
The format of the CAD-to-Matrix required attribute name is shown below:
attributeName,attributeValue,attributeType
Each section of this format is discussed below:
attributeNamethe name of the attribute, e.g., $$Description$$.
attributeValuethe value of the attribute, e.g., Catia File.
attributeTypethe type of value. There are three values that this can hold, which are
discussed below:
mandatoryimplies that the value specified in attributeValue should be used by
the CSE as the value of the attribute. The CSE must ignore the value of such attributes as
they exist in the File Summary Properties or the custom properties. The system
administrator must provide a value in attributeValue since mandatory attributes
cannot be blank.
defaultimplies that the value specified in the attributeValue can be used by the
CSE as the value of the attribute, or the CSE can choose to over-write this value with a
value of its own based on some criteria. Currently, the CSE picks up the
attributeValue and synchronizes this with the IEF. In future releases of CSE, CSE
may choose to over-write this attributeValue with a value of its own. The system
administrator MUST provide a value in attributeValue since mandatory attributes
cannot be blank.
nullimplies that the CSE should search this attribute in the File Summary Properties or
in the File Custom Properties and pick its value to synchronize it with the IEF attribute. If
a file or custom attribute is specified as null then that property should contain a value
because mandatory attributes are intended to have a value. The system administrator
should not provide a value in the attributeValue, since it will not be used by the
CSE.
A few rules regarding mandatory attributes:
If an attribute is to be declared mandatory then it should be present in
IEF-CADToMxMandatoryAttrMapping as well as in
MCADInteg-CADToMxAttribMapping.
All mandatory attributes must have a value:

If the system administrator sets the attributeType as mandatory or default then the
system administrator should provide a value in the attributeValue and MUST NOT
leave it empty. If it is empty an error message will be displayed to the user saying
mandatory attributes cannot be empty.
If the system administrator sets attributeType as null then the CAD-user must
ensure that the attribute, if it exists in File Summary Properties or File Custom Properties,
should hold a value and not be empty. If it is empty an error message will be displayed to
the user saying mandatory attributes cannot be empty.
The above mandatory attribute rules are applied in the following cases:
During checkin with Copy Attributes
During checkin without copy-attributes
When doing a Synch Attributes > To Matrix operation

Appendix
Working set (activity file): The Heart of Integration
Integration keeps track of the files a user works with. This helps the integration to locate the exact
business object in Matrix when a user selects Lock/Unlock, Attribute Synch and Versions.
Integration assumes that in one directory the user can keep only one version of the given
component (part). For example, a user can keep any version (A.0 or A.1 etc.) of part center in his
C:\temp directory. He is allowed to keep the different versions of the same component as long as he
uses a different directory.
Integration enforces the rule of one version at a time, when a user locks the version. For instance, a
user may have checked out Center A.1 with lock (lock means he wants to modify it) in C:\temp.
Integration will NOT allow him to check out any other version, for example, A.0/B.0 etc. of the
same component to C:\temp until he checks in or unlocks the version he is working on. In the same
way, if a user has checked out an assembly crank_assembly with a lock, checked out component
center A.0 (which is a part of crank_assembly) without a lock, the integration still will NOT
allow user to check out center A.1 to the same directory. This is because version A.0 of
center is being referred to in the assembly crank_assembly which has a lock.
When integration cant identify the version of the cad-object, it displays a message. A user can go
to the Versions dialog and recognize the version he is using. Here is an example of such a case:
Suppose a user checks in (or works with) a part center.sldprt from C:\temp. Now if he copies this
file to D:\temp (a different directory) and tries to check in /lock / unlock / Attribute synch, the
integration will NOT recognize it. It will display the message to the user to use the versions dialog
65
and choose the version he is working with. The versions dialog will become editable in this case. It
shows different versions with the Preview facility. A user can preview and choose a version.
User Exits
User Exit functions are entry points into the integration that allow for customization and
modification of basic integration functionality. They are function calls that are which are called by
the integration to do specific operations before or after certain integration functions. A template is
provided for each of the user functions. These functions, as delivered with the integration, perform
no actions; they must be programmed to perform whatever tasks may be desired. These user
functions are written in the C language. This document assumes the programmer of these user
functions is proficient in the C programming language and is familiar with the Matrix MQL
interface.
The CSE installer installs the source code of the User Exits project along with a build and usage
guideline document at the following location:
<Root CSE Installation directory>/UserExits/src_UserExit.zip

Refer to the User_Exit_Build_and_Usage.doc document for details on how to customize
the user Exits DLL.
The user Exits is enabled only if the users event registration entries are provided in the GCO
attribute. Contact your System Administrator to set the event registration. The list of the UserExit
event registration is provided in the User_Exit_Build_and_Usage.doc.
Rapid File Access
Rapid File Access enables you to view CAD files directly from the Matrix stores without checking
out the files into local disks. Using this feature you can create a hardlink within the Matrix stores
and view the required files. Each user should have a directory or folder in FCS (File collaboration
Server), which must be on the same network to enable Rapid File Access. The System
Administrator must create folders or user-specific directories for each user before you start using
this feature.
In GCO, you must set the IEF-EnableRapidFileAccess attribute to TRUE to enable Rapid
File Access.
For more details on Rapid File Access, see the Designer Central System Administrator Guide.
Versions and Revisions
By default, the integration creates versions of the CAD-object when you check in. You can override
this behavior by unselecting the checkbox Create Version during Checkin. In this case, it checks
in the object into the existing business object. When the CAD-object is new, it ignores this

directive. The Checkin operation removes the lock on the object in either case (create version or
not).
All the major objects (non-versioned) are called Revisions in the integration. All the minor objects
(versioned) objects are called Versions. For example, A.0, A.1, A.2 etc are minor versions of major
revision A. Similarly, B.0, B.1 are versions of B. During finalization, the files are moved from
minor version to major revision.
If any one user has locked any one of the versions (say A.2) in one revision stream (A), no other
user can lock any version (say, A.0, A.1, A.2) in that revision stream (A). Once the user checks in
the version he has, the lock on the stream gets opened.
You can check out A.2 from A stream and check in to B stream to create B.1. The lock on A stream
is unlocked.
Using Applet Log and Setting Ping Interval
An Applet log file is created at the location <user profile directory>/ief/ if the Turn
On Debugging option in the Preferences page is selected.
This file contains all debug statements related to the current browser's session, if the browser
session is active. If the browser session is not active, then it displays the last browser session's
debug statements.
The following is a sample of the applet log file that is created:
[04/11/05 11:27:27]: [MCADApplet.init] Starting the MCADApplet.......
[04/11/05 11:27:27]: [MCADAppletController.initialize] IsOSWindows
:true
[04/11/05 11:27:27]: [MCADAppletController.initialize]
IsJVMVendorMicrosoft :false
[04/11/05 11:27:27]: [MCADApplet.init] Starting the MCADAppletServer
with charset : UTF8
For more details of the log files such as Back Ground Checkin log, IEF Applet Debug log, see the
Designer Central System Administrator Guide.
You can set the interval for ping between applet and server to avoid session and request-response
timeout. This can be set in the local config object using the attribute
MCADInteg-PingInterval. This can have values between 1 to 3600 seconds.
Attribute Mapping From and To Matrix
The Matrix Catia integration supports the following types of attributes:

System Attributes
Custom Attributes
Param Attributes
PDM Attributes
Chapter : Appendix 67
System Attributes
These are the File Properties of the file. You can view these properties by selecting the Edit >
Properties option in Catia.
GCO Mapping for System Attributes

You may have a custom attribute named Description, whereas these attributes already exist in the
Summary information. In order to differentiate between the Summary information and Custom
attributes, the integration specifies syntax to state the GCO mapping. The integration treats the
summary information as System attributes to differentiate it from Custom attributes with the same
name. While specifying the GCO mapping, the CAD side summary attribute name is enclosed
between $$ signs.
For example, the mapping for the Catia summary attribute description with the Matrix system
attribute description will be as follows:
MCADInteg-CADToMxAttribMapping:
Syntax:
CATIA V5 type,CATIA V5 attribute|Matrix type,Matrix attribute
Example:
component,sys:Material|Cat Part,CatMaterial
MCADInteg-MxToCADAttribMapping:
Syntax:
Matrix type,Matrix attribute|CATIA V5 type,CATIA V5 attribute
Example:
Cat Part,CatMaterial|component,sys:Material
The following table explains the supported system attributes in Matrix for a to and from transfer:
Direction Description Revision Definition Nomencl Part Source

ature Number
To Matrix
From
Matrix
Direction Material RefMaterial

To Matrix
From
Matrix
The summary attributes have to be mapped in the GCO using English names even on a Japanese
OS.

Custom Properties
These are the custom properties defined by users. You can view these attributes by choosing Edit >
Properties on Catia:
GCO Mapping for Custom Properties

The mapping for a custom attribute Subject with the Matrix attribute Subject is as follows:
component,Subject|Cat Part,Subject.
Notice that system attributes are enclosed between $$ symbol. This helps the integration
distinguish between a System attribute and a custom attribute of the same name.
Client Settings
The CSE-specific settings are stored in the settings.ini file in the CSE installation directory.
The settings file has the following default settings:
[SERVER]
address=http://<server>:<port>/<appname>/emxLogin.jsp
clientname=localhost
appletloglevel=5
[CLIENT]
xmldump=false
debugflag=false
clientloglevel=7
performanceloglevel=2
performancelogflag=false
helpfilepath=http://<server>:<port>/<appname>/integrations/MxCATIAV5/
docs/MatrixOne_CatiaV5Integration_UserGuide-10.7.SP1.htm
compatibledscversion=<compdscversion>
The significance of each key is discussed below.
Server Section:
address: This specifies the server URL which the browser starts with when the Connect
menu is clicked.
clientName: This is the client machine name.
Client Section:
xmldump: This is a Boolean debug setting. This can have values true or false. If set to
true, the integration creates a xmldump folder in the Catia Integration Installation folder and
all the xml files are dumped in the folder.
debugflag: This is a Boolean debug setting. This can have values true or false. If set to
true a log file mxSEinteg.log is created in the CSE installation folder which contains the
log for all the commands executed. This can be used for troubleshooting.
clientloglevel: This is a numeric setting. It can accept values within a range of 1-4. By
default the value will be set to 1. This will log only the error messages by the MatrixOne
Catia integration. A value of 4 indicates that all message will be logged by the CSE. These
messages include debug, information, and error messages.
helpfilepath: This is a string setting. This value indicates the path of the help file that is
used to launch the online html format of the MxACADUserManual help file. The user can
move the html help file in any desired location, and update the string setting helpfilepath
to the new location. The value of this setting can be a URL, or a file on the network, or a file on
local machine.
You should not change the value of any entry in the settings.ini file, when any of the
integration commands are active.
System Defined Attributes
System Property attributes are created for each Product and Part via CATIA V5.
Part Number
Revision
Definition
Nomenclature
Source
Description
System Parameter attributes must be created by the system in order to be properly maintained
(modified). Material (RefMaterial) is a unique parameter used to reference an external catalog.
Material
RefMaterial
All system attributes must be defined and mapped correctly in Matrix.
None of these System Attributes as user defined attributes or parameters must be duplicated.


MxCatia UsersGuide 10.7.SP1

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

MxCatia UsersGuide 10.7.SP1

Hochgeladen von

Copyright:

Verfügbare Formate

Enovia MatrixOne Catia

Dassault Systmes, 2005-2007.

All rights reserved.

This license came from:

JAVAMAILTM, VERSION 1.3.1

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

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

Chapter 2. CAD-Centric Features............................................................................................. 17

Chapter 3. Matrix-Centric Features .......................................................................................... 51

Chapter 4. Advanced Features ................................................................................................. 55

Chapter 5. Appendix .................................................................................................................. 65

4 Enovia MatrixOne Catia Integration Users Guide

About Enovia MatrixOne Catia Integration

Application Window and Features

Features can be categorized as Catia-centric features, Matrix-centric features, and Advanced

14 Enovia MatrixOne Catia Integration Users Guide

Before Reading This Guide

You should already:

Getting the Most Out of This Guide

16 Enovia MatrixOne Catia Integration Users Guide

Before you begin:

1. In Catia application, click Matrix > Connect.

18 Enovia MatrixOne Catia Integration Users Guide

Connecting to an Existing Session

Chapter 2: CAD-Centric Features 19

Checking in the Active Model

20 Enovia MatrixOne Catia Integration Users Guide

Options in Checkin Page

icon indicates that no user has locked the object.

Chapter 2: CAD-Centric Features 21

Assign FolderClick Browse and the Select Folder page opens.

22 Enovia MatrixOne Catia Integration Users Guide

Chapter 2: CAD-Centric Features 23

Change Type on Checkin

Checking In All Models

24 Enovia MatrixOne Catia Integration Users Guide

Checking Out from Matrix to Catia

Using Open > Load

Chapter 2: CAD-Centric Features 25

26 Enovia MatrixOne Catia Integration Users Guide

Checkout Page Options

Chapter 2: CAD-Centric Features 27

28 Enovia MatrixOne Catia Integration Users Guide

Load files on checkout:

Chapter 2: CAD-Centric Features 29

Using Open > Insert

Using the Checkout Option

Click Matrix > Checkout for the following options:

Using Checkout > Load Option

30 Enovia MatrixOne Catia Integration Users Guide

The selected objects are checked out to Catia.

Chapter 2: CAD-Centric Features 31

Checking Out RFA Objects

32 Enovia MatrixOne Catia Integration Users Guide

3. Select an option below:

Lock/Unlock of RFA Objects

Synch Attributes From Matrix

Chapter 2: CAD-Centric Features 33

PDM attributes are not mapped for Analysis and AnalysisResults.

The Synch. Attributes command supports following types of attributes:

34 Enovia MatrixOne Catia Integration Users Guide

Param AttributesClick in Catia to view or add param attributes.

Chapter 2: CAD-Centric Features 35

2. A message is displayed after the attribute synchronization is completed successfully.