Escolar Documentos
Profissional Documentos
Cultura Documentos
Integration
Version 10.7
Users Guide
Copyright and Trademark Information
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.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 ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY 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.
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.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE 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.
ImageEncoder
ImageEncoder - abstract class for writing out an image
Copyright (C) 1996 by Jef Poskanzer <jef@acme.com>. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
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.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE 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.
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.
Jakarta POI
[under Apache License, Version 2.0 above]
JDOM
Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin.
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the disclaimer that follows these conditions in the documentation and/or other materials
provided with the distribution.
3. The name "JDOM" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact
<request_AT_jdom_DOT_org>.
4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior written permission from the JDOM Project Management
<request_AT_jdom_DOT_org>.
In addition, we request (but do not require) that you include in the end-user documentation provided with the redistribution and/or in the software itself an acknowledgement equivalent to the
following:
"This product includes software developed by the JDOM Project (http://www.jdom.org/)."
Alternatively, the acknowledgment may be graphical using the logos available at http://www.jdom.org/images/logos.
THIS SOFTWARE IS PROVIDED ''AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally created by Jason Hunter <jhunter_AT_jdom_DOT_org> and Brett
McLaughlin <brett_AT_jdom_DOT_org>. For more information on the JDOM Project, please see <http://www.jdom.org/>.
Krypto
Copyright (c) 1997 Stanford University
Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notices and this permission
notice appear in all copies of the software and related documentation.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY
WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
IN NO EVENT SHALL STANFORD BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT OR CONSEQUENTIAL DAMAGES OF ANY KIND, OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER OR NOT ADVISED OF THE POSSIBILITY OF DAMAGE, AND ON ANY THEORY OF
LIABILITY, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
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 ``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
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.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the
distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse or promote products derived from this software without prior written permission. For written permission,
please contact openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written permission of the OpenSSL Project.
6. Redistributions of any form whatsoever must retain the following acknowledgment:
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``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 OpenSSL PROJECT OR ITS
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are aheared to. The following conditions apply to all code found in this distribution, be it the RC4,
RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson
(tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of
the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the
distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgement:
"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)"
The word 'cryptographic' can be left out if the rouines from the library being used are not cryptographic related :-).
4. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: "This product includes software written by
Tim Hudson (tjh@cryptsoft.com)"
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license
[including the GNU Public License.]
Oracle
*****************************************************************
Oracle Instant client
End user license agreement ("Agreement")
*****************************************************************
MatrixOne Inc., ("MatrixOne") as licensor, has been given the right by Oracle Corporation (Oracle") to distribute the Oracle Instant Client software ("Program(s)") to you, an end user. Each end
user hereby agrees: (1) to restrict its use of the Programs to its internal business operations; (2) that it is prohibited from (a) assigning, giving, or transferring the Programs or an interest in them to
another individual or entity (and if it grants a security interest in the Programs, the secured party has no right to use or transfer the Programs); (b) making the Programs available in any manner to
any third party for use in the third party's business operations (unless such access is expressly permitted for the specific program license or materials from the services acquired); and (3) that title to
the Programs does not pass to the end user or any other party; (4) that reverse engineering is prohibited (unless required by law for interoperability), (5) disassembly or decompilation of the
Programs are prohibited; (6) duplication of the Programs is prohibited except for a sufficient number of copies of each Program for the end user's licensed use and one copy of each Program media;
(7) that, to the extent permitted by applicable law, liability of Oracle and MatrixOne for any damages, whether direct, indirect, incidental, or consequential, arising from the use of the Programs is
disclaimed; (8) at the termination of the Agreement, to discontinue use and destroy or return to MatrixOne all copies of the Programs and documentation; (9) not to publish any results of
benchmark tests run on the Programs; (10) to comply fully with all relevant export laws and regulations of the United States and other applicable export and import laws to assure that neither the
Programs, nor any direct product thereof, are exported, directly or indirectly, in violation of applicable laws and are not used for any purpose prohibited by these laws including, without limitation,
nuclear, chemical or biological weapons proliferation; (11) that Oracle is not required to perform any obligations or incur any liability not previously agreed to; (12) to permit MatrixOne to audit
its use of the Programs or to assign such audit right to Oracle; (13) that Oracle is a third party beneficiary of this end user license agreement; (14) that the application of the Uniform Computer
Information Transactions Act is excluded.
Disclaimer of Warranty and Exclusive Remedies
THE PROGRAMS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MATRIXONE AND ORACLE FURTHER DISCLAIM ALL WARRANTIES, EXPRESS AND
IMPLIED, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT.
IN NO EVENT SHALL MATRIXONE OR ORACLE BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, PUNITIVE OR CONSEQUENTIAL DAMAGES, OR DAMAGES FOR
LOSS OF PROFITS, REVENUE, DATA OR DATA USE, INCURRED BY YOU OR ANY THIRD PARTY, WHETHER IN AN ACTION IN CONTRACT OR TORT, EVEN IF MATRIXONE
OR ORACLE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. MATRIXONE'S AND ORACLE'S ENTIRE LIABILITY FOR DAMAGES HEREUNDER SHALL IN
NO EVENT EXCEED ONE THOUSAND DOLLARS (U.S. $1,000).
No Technical Support
Oracle and MatrixOne technical support organizations will not provide technical support, phone support, or updates to end users for the Programs licensed under this agreement.
Restricted Rights
For United States government end users, the Programs, including documentation, shall be considered commercial computer software and the following applies:
NOTICE OF RESTRICTED RIGHTS
"Programs delivered subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the
licensing restrictions set forth in the applicable Oracle license agreement. Otherwise, programs delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use,
duplication, and disclosure of the programs, including documentation, shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). Oracle
Corporation, 500 Oracle Parkway, Redwood City, CA 94065."
End of Agreement
The end user may terminate this Agreement by destroying all copies of the Programs. MatrixOne and Oracle each have the right to terminate the end user's right to use the Programs if the end user
fails to comply with any of the terms of this Agreement, in which case the end user shall destroy all copies of the Programs.
Relationship Between the Parties
The relationship between the end user and MatrixOne and Oracle is that the end user is licensee, MatrixOne is distributor/licensor and Oracle is licensor. No party will represent that it has any
authority to assume or create any obligation, express or implied, on behalf of any other party, nor to represent the other party as agent, employee, franchisee, or in any other capacity. Nothing in
this Agreement shall be construed to limit any party's right to independently develop or distribute software that is functionally similar to the other party's products, so long as proprietary
information of the other party is not included in such software.
Open Source
"Open Source" software - software available without charge for use, modification and distribution - is often licensed under terms that require the user to make the user's modifications to the Open
Source software or any software that the user 'combines' with the Open Source software freely available in source code form. If you as end user use Open Source software in conjunction with the
Programs, you must ensure that your use does not: (i) create, or purport to create, obligations of MatrixOne or Oracle with respect to the Oracle Programs; or (ii) grant, or purport to grant, to any
third party any rights to or immunities under intellectual property or proprietary rights in the Oracle Programs. For example, you may not develop a software program using an Oracle Program and
an Open Source program where such use results in a program file(s) that contains code from both the Oracle Program and the Open Source program (including without limitation libraries) if the
Open Source program is licensed under a license that requires any "modifications" be made freely available. You also may not combine the Oracle Program with programs licensed under the GNU
General Public License ("GPL") in any manner that could cause, or could be interpreted or asserted to cause, the Oracle Program or any modifications thereto to become subject to the terms of the
GPL.
SSLUtils
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:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the
distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software
Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
4. The names "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 ``AS 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
POSSIBILITY OF SUCH DAMAGE.
THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND
DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the Government shall have only "Restricted Rights" in the software and related documentation as
defined in the Federal Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If you are acquiring the software on behalf of the Department of Defense, the software shall be classified as
"Commercial Computer Software" and the Government shall have only "Restricted Rights" as defined in Clause 252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, the authors grant
the U.S. Government and others acting in its behalf permission to use and distribute the software in accordance with the terms specified in this license.
Xalan
[under Apache License, Version 2.0 above]
Xerces
[under Apache License, Version 2.0 above]
Xerces2
[under Apache License, Version 2.0 above]
Table of Contents
Table of Contents 3
About ...................................................................................................................... 50
Table of Contents 5
6 Enovia MatrixOne Catia Integration Users Guide
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
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
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
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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
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.
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.
Custom Attributes: Custom attributes can be seen in the Properties dialog under the Product
tab. The custom attributes are treated as normal attributes.
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).
Versions
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
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.
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.
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.
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
Upon initiating the process, MCAD designers are shown a list of templates (as shown below) from
which to create the CAD Models:
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.
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
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 .
Checkout Preferences
The following preferences can be set for Checkout in the Checkout section in Preferences page:
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.
Help
About
Click Matrix > About to view the MatrixOne Catia Integration version and the compatible
Designer Central version.
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.
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.
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.
For more details, see the Designer Central User Guide.
Batch Rename does not update references in drawing when the drawing is connected to multiple
objects.
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.
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.
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.
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).
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
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.
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
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.
There is a new entry in the GCO to allow the System Administrator to provide the mapping:
IEF-CADToMxMandatoryAttrMapping
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:
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.
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
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.
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.
The summary attributes have to be mapped in the GCO using English names even on a Japanese
OS.
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.
Chapter : Appendix 69
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 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.