Oracle® Agile Engineering Data Management
Release Notes
Release e6.2.0.0
E52566-02
September 2015
This document outlines the enhancements and additions to the core product.
A detailed list of supported platforms can be found in the document Release Notes Platform Support for Agile Release e6.2.0.0.
A detailed list of all bug fixes which have been rolled up in Agile Release e6.2.0.0 can be found in the document Release Notes - Bug Fixes for Agile Release e6.2.0.0. This document also contains a list of Known Issues which will be fixed in the first hot fix.
Platform Support
Please see Platform Release Notes for a complete and detailed list of platforms.
Major Platform Changes in Agile e6.2 are:
Operation Systems
-
Added support of Microsoft Windows 8.1 (Client)
-
Added support of Microsoft Windows Server 2012 R2 (Server & Client)
-
Added support of Oracle Linux (Server)
Agile e6.1.x Fileserver (which exact releases?) are supported on Oracle Linux to allow smooth transition.
-
De-Support of Microsoft Windows XP
-
De-Support of SUSE Linux
-
De-Support of Microsoft Windows Server 2008
Support of Multi-byte Characters
More and more customers develop, manufacture and market their products all around the world. This requires to provide product information in various languages. Agile e6 supports the management of data in 10 different languages. However, so far the capabilities of Agile e6 were limited to so-called single byte characters. In other words Agile e6 was able to handle single byte character sets only, which obviously did not allow to support for instance Chinese language properly.
|
Note: For several releases, there was a very limited solution to add multi-byte support for specific attributes and languages by means of customization. However critical functional restrictions applied to this solution. This limited solution is now replaced by a generic multi-byte character support in Agile e6.2. Please see upgrade tool manual on how to migrate limited solution into the standard multi-byte support of Agile 6.2. |
Capabilities
In Agile e6.2 the whole string handling was enhanced to support utf-8 characters out of the box. UTF-8 is a character encoding capable of encoding all possible characters in Unicode. UTF-8 encodes each character using one to four 8-bit bytes. The first 128 characters of utf-8 correspond one-to-one with ASCII.
Utf-8 is allowing to input and display non-Latin characters. For instance the system is now able to handle Chinese language or even a mixture of Cyrillic and Chinese in a single string attribute.
Obviously the Java-Client needs to be able to visualize the multi-byte characters properly. Thus it is required to configure the Java-Client to use a Unicode character set (see Figure 2). Please be aware the appropriate Unicode character sets are not provided by Oracle but might be provided by Microsoft or can be purchased by third party companies.
Following a few examples where you can benefit from the utf-8 support in Agile 6.2:
-
Java Client and Web Client User Interface
Allow you to define field titles with Non-Latin characters
-
User Data
User object data attributes like "Item name" can make use of utf-8 encoded characters (Figure 1).
-
User and Password management, including remote user definition Agile e6 user names as well as remote user names (LDAP users and Kerberos Users) can contain utf-8 encoded characters. Also the passwords for these user names can consist of utf-8 encoded characters.
-
Fileserver
The file server is enabled to handle filenames containing utf-8 encoded characters properly.
-
Office Properties
Object attributes like "Item Status" containing utf-8 characters can be used as properties in the MS-Office documents leveraging Office Suite capabilities
-
AutoVue Properties
Object attributes like "Item Creator" Agile e6 attributes which are used as base t
-
Logiview functions
String handling functions will allow you to manipulate strings properly. For instance concatenate and split functions take into account the correct character based length instead of previously used byte length. Additionally the file handling function are able to consider a certain file encoding when reading/writing file content.
-
Loader
Loader is using utf-8 character encoding
-
Number Server
Number server is used to generate auto-numbers. The static text of a number server definition does support utf-8 encoded character now.
-
Longtext handling improved to manage up to 2000 characters in any language Longtext fields are able to handle now up to 2000 characters in character length. Previously with the restricted multi-byte support solution, the max length of strings was limited to 667 characters.
Additional Information
External Mailing exm_snd_ext
Server side mailing uses the parameter -k to define the encoding. The behavior of parameter -k has slightly changed in Agile e6.2.
By default the external mailing will use utf-8 encoding. If parameter -k is specified (e.g. -k'windows-1252'), the specified encoding will be used. If encoding fails for any reason the text will be send unencoded.
Java Client Font Selection
The default Java client font is still Courier-New, which is not a suitable font for I18N data.
Microsoft supplies a variety of fonts out of the box, one of them is the Microsoft JhengHei. Most of these fonts are hidden by default in a Western Windows installation, so the customer must unhide the font in the Windows Font control panel to make them available to the Java client in the Field Font mask preferences.
If the customer has a Microsoft Office product installed, then another good universal font is Arial Unicode MS.
ECI-Clients
ECI clients talking to the Java Client will get data in ISO-8859-1 encoding unless eci_set_enc is used to define a different encoding.
ECI clients connecting to the e6 server will get UTF-8 data by default unless different encoding is set using eci_set_enc.
Configuration Parameters
The following configuration parameters are relevant for I18N setup
| Name | Rubric | Default value | Description |
|---|---|---|---|
| EDB-CHR-ENC | EDB-NLS | ISO-8859-15 | The encoding that the server should use for a file specified / owned by the user. The new C API function xcfg_get_enc will read this parameter and return the encoding name. For example, see LogiView function open. It is our assumption that most of the customers will not use UTF-8 as encoding for their own file content, therefore the default value is not set to UTF-8. Internal Agile EDM Server files will always use UTF-8.In previous versions, this parameter had the content "western", and was only used in special file server related code to provide support for file names encoded in - for instance - Shift-JIS.With e6.2, this special code has been removed, because UTF-8 is the only internal character set. |
| EDB-CHR-ENC-JVM | EDB-NLS | UTF-8 | The encoding to use by Java applications when connecting to the e6 server using the ECI. This parameter has not changed in this release 6.2. UTF-8 is a requirement to be able transfer non-Latin characters from/to the Java application. In the Java client, the encoding is displayed in the status line. |
| EDB-EPQ-USE-CHAR-CONVERSION | EDB-EPQ | off | Activates or deactivates the character conversion. |
| EDB-EPQ-USE-SUBST-CHARACTER | EDB-EPQ | off | Activates or deactivates the character substitution if the character to convert is not in the codepage (EDB-EPQ-USE-CHAR-CONVERSION must have value "ON"). |
C/C++ Coding
More information on Coding Guidelines for C/C++ with respect to multi-byte support can be found in the online documentation:
http://dev.mysql.com/doc/refman/5.5/en/multibyte-characters.html
Restrictions/Limitations
For detailed list of restrictions and limitations for utf-8 support, please see Document … to be completed
-
Office-Suite
Office Suite does not support utf-8 filenames
-
Client side external mailing does not support utf-8. There is a limitation in Windows 7 MAPI, which does not support Unicode characters.
-
Using Java Client http/s and login with LDAP does not support utf-8 user names
-
Installer only supports ASCII characters for domain and application names, and for installation directories
-
ECI test program
Programs linked for use on the client - like eci_test - do not fully support Unicode file names or command line arguments. Nevertheless, eci_test can read and write UTF-8 data when communicating with the server process.
-
DB-Query behavior
To support DB query strings with more than 2000 bytes content a different database data types needs to be used. This will result in an application behavior change if more than 2000 bytes are required.
-
Behavior for query strings < 2000 bytes: Trailing blanks (at the end of query string) will be supported (compatible behavior to 6.1.x releases)
-
Behavior for query strings>= 2000 bytes: Trailing blanks will cause a "Validation Error" (Error Code -912)
-
-
Code attributes
Several fields do not yet support non-Latin characters. Fields affected are for instance:
-
Attribute Set Id
-
Item Finish Code and Color Code
-
Organization Code
-
String attributes in attribute pool
-
-
Log4j Log files
Log4j Log files do not support utf-8 characters out of the box. If utf-8 support is required, utf-8 support can be activated in the corresponding property and ini files.
-
Workflow Editor
When Drag and Drop is used with objects (activities, users, groups, roles) carrying utf-8 data, to design a workflow process, you will need to right click after dropping the activity, in order to see the activity.
Furthermore some Unicode character sets (e.g. Bengali) cause issues in Workflow Editor
-
Fonts with right to left writing direction
Browser and Language form have issues when using fonts which use right to left writing direction.
AutoVue
Augmented Business Visualization
Augmented Business Visualization (ABV) is a new paradigm in visualization which provides rich and actionable visual decision making environments by connecting portions of documents to business data found in enterprise applications. With ABV, information and business data is synthesized from multiple sources into a single visual environment, delivering rich information context to users.
Partners and systems integrators can develop ABV solutions which enable users to access Agile e6 data via hotspot links directly from documents and trigger actions, such as creating an engineering change request, in Agile e6. In this scenario, the document becomes the entry point into key enterprise applications. Data from Agile e6 and other enterprise applications can be dynamically displayed in documents via AutoVue and turned into color-based visual reports, helping users identify important elements, trends and patterns in a visual context.
Be aware: Augmented Business Visualization is available for local installed AutoVue Client Integration only.
Agile e6.2 provides the framework on the Agile e6 side to leverage AutoVue's ABV capabilities in the context of Agile e6. This framework delivers an ECI connection from within the Viewer instance, which allows to communicate with the Agile e6 client in order to query data or to trigger actions.
Figure 5 shows a Java code snippet which can be deployed in the AutoVue Viewer to get access to information about the current document in Agile e6.
|
Note: For further information about AutoVue Augmented Business Visualization, please refer to the latest AutoVue documentation on OTN:
|
Performance Improvements
AutoVue QuickLaunch
Quicklaunch allows you to download and pre-start the AutoVue Viewer when the Java Client is started. Obviously Quicklaunch will significantly reduce the time to view the first document, because everything is in place already.
Quicklaunch is activated in the Java Client settings.
Be aware: Quicklaunch is available for local installed AutoVue Client Integration only.
Optimize retrieval of repository information and default values
PLM Repository definition and Default data is required to be available when running the AutoVue integration. In Agile e6.2, the code has been optimized to share repository information and default data where possible instead of loading it repeatedly from the server.
Memory Settings
The Agile e6 AutoVue Integration runs now as external 64bit application. Thus the limitation of 4GB RAM with the 32 Bit JRE has gone and you can completely leverage the RAM which is installed on your client machine. Thanks to that, you can now view/markup more files in parallel using the AutoVue Integration
The default memory setting is 512MB.
Other Improvements
Using IP address instead of Alias Name
After initial connect, the ECI connections which are used by the AutoVue Integration will make use of IP address instead of Alias names in order to improve compatibility with Load Balancer infrastructures.
Java Client
Refreshing a form always shows first record
In Java Client when refreshing the content in a form (e.g. Projects), always the first record is shown. This issue is fixed. After refresh the system will still show the record which was presented the before the refresh.
German/Swiss Locale support
The German/Swiss locale support has been implemented in Java Client to handle the requirements of german speaking user community in Switzerland. For instance it is now possible to use the point as the decimal delimiter. With German locale, the decimal delimiter has to be the comma.
Document Management
Notes
The old mechanism to generate the position number for notes was reactivated. To allow the mechanism to be deactivated again, the parameter /NO_POS of the userexit xntm_eda was added.
|
Note: For further information about this userexit please refer to the Online Help > Customizing Agile e6 > Parameters > Userexits. |
|
Note: See also BugID 19354887. |
Item/BOM Management
Default Unit in BOM
For some item BOM masks, there was an issue with the default Unit when inserting an item in a BOM. The default unit of the mask was applied instead of the items default unit. The following masks have been modified to have the corrected behavior:
-
EDB-ART-STR-RLI
-
EDB-ART-STR-ALI
-
EDB-CHG-ART-STR-RLI
Classification
System performance has been improved when searching for an empty attribute by implementing a better search algorithm.
Change and Release management
xstate_nxt_sta with additional "/GROUP" parameter
The userexit xstate_nxt_sta now supports an additional option "/GROUP=group-name" to choose the group that is used to find the desired transition.
This is needed for calls without interaction, if more than one transition is possible and the transitions are assigned to different group IDs.
Example:
xstate_nxt_sta 120 /GROUP=EDB
xstate_nxt_sta with additional "/RCODE" parameter
The userexit xstate_nxt_sta now supports an additional option "/RCODE ". If /RCODE is given, the errorcode of the failed stats transition will be returned as return value of xstate_nxt_sta.
If more than one record is selected, then the transfer for each record is executed. The error code is returned if at least one transfer failed.
Example:
xstate_nxt_sta 120 /RCODE /GROUP=EDB
Enhanced Change Management
Copy with Structure
Copy with Structure failed when trying to copy a structure where part of the structure relationship records used an (object specific) change management level of 0 or 1.
Copy with Structure has been enhanced in Agile e6.2 to work properly in such a case. In case of an ADD operation (which is used to when doing Copy with Structure) relation objects with change level 0 and level 1 are copied to the new parent. However they are not assigned to the workset. This is why these relation records will not show up in the Change Operations tab of the corresponding Change Request respectively the Change Order.
Be aware: Before executing an Undo operation, objects that have been copied but are not assigned to the work set needs to be deleted manually. Otherwise the Undo operation will fail.
Configurator
New Selection EDB-CNF-BOM-CLEAR
This new selection was introduced to refresh the modular BOM cache, after changing the modular BOM (especially the variants and rules). This selection will clean the cache. When running a calculation with the configurator next time, it will load the updated information and will to calculate up-to-date results.
EDB-CNF-BOM-CLEAR is to be found in the no-selection context menu on the mask "Order" (EDB-CNF-ORD-CFR) and in the no-selection context menu on the sub mask "Variants" (EDB-CPS-MDL-SOL-C).
Office Suite
The following changes have been implemented to the Office Suite with the Agile release e6.2.0.0.
Distributed File Management
Other Enhancements
Access to certain objects requires "Manager" flag
For user who do not have "Manager" flag, the access to the following application areas is prohibited.
-
Internal Loader
-
Logiview
-
Repository
Be aware, there is read-only access for Non-Manager User for the following objects:
-
Event Data
-
System Configuration
-
Messages
-
User and Group Data
-
Connection pool of business service
The setup for connection pooling parameters have changed. The parameters are defined in
%EP_ROOT%\build\applicationServer\weblogic_121\tpl_app\ear\tpl_eSeriesDataSource-jdbc.xml
The new default values are:
<jdbc-connection-pool-params>
<pinned-to-thread>true</pinned-to-thread>
<initial-capacity>10</initial-capacity>
<max-capacity>150</max-capacity>
<statement-cache-size>100</statement-cache-size>
<statement-cache-type>LRU</statement-cache-type>
<connection-reserve-timeout-seconds>120</connection-reserve-timeout-seconds>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
</jdbc-connection-pool-params>
Enterprise Communication Interface (ECI)
Extended ECI Function eci_cki_typ_fil
ECI Function eci_cki_typ_fil supports a new value "4" for parameter cpSelFlg.
If cpSelFlg = 4, the function calls copyonwrite even if only one document is assigned to file.
This enhancement was needed to support a use case of snapshot management.
Snapshot management uses the concept of empty snapshot ID to indicate the most current file. Now when checking in new file content, the system did not create a new file but did overwrite the latest file. However, the latest file might have been referenced in other snapshots as well, so the respective CAD assembly was modified too.
Making use of cpSelFlg = 4, this use case can be handled properly.
|
Note: See also BugID 19435325. |
Single-Sign-On with WAFFLE
Agile e6.2 comes with the integration of WAFFLE. Waffle is a native Java library that supports Windows authentication, e.g. Kerberos. WAFFLE stands for the Windows Authentication Functional Framework (Light Edition).
One of the benefits of using WAFFLE for SSO with Kerberos is the ability to get access to Microsoft's SSO API. Thanks to that it is no longer required to grant access to the Windows Logon TGT by setting the registry key "AllowTgtSessionKey" accordingly.
Due to the switch to Waffle, remote user names have to use a different format, which is ”DOMAIN\username” instead of ”username@FULL-QUALIFIED-DOMAIN”. The upgrade tool will take care of the conversion.
Database
Templates
Database templates have been adapted to reflect the new template structure required for Oracle database 12c. The templates include the necessary configuration to setup the new database administration tool EM EXPRESS.
Database Parameter max_string_size
The database initialization parameter max_string_size has been changed to "Extended" to support up to 2000 characters in longtext field even when using multi-byte characters.
Please be aware that export/import with the Oracle tools "exp" and "imp" will fail with errors/warnings. Reason is a bug in these Oracle tools when exporting table with long varchar2 columns which are able to store more than 4000 byte. Server site export/import (data pump) however with "expdp" and "impdp" works fine.
Logiview
Size of Logiview Array
The maximum size of Logiview arrays has been increased. An array can now have up to 999999 elements.
Function Sel_Value
Function Sel_Value in some cases auto-interpreted a select value as a date and converted it internally. Obviously for non-date fields that led to issues. In Agile e6.2 sel_value converts the select value only if the underlying field is of type date.
Function getenv
As the Agile e6 server internally uses the UTF-8 encoding to store string data, it needs to convert strings provided by the operating system - e.g. by the getenv function - to the internal encoding.
To achieve this, the e6 server will use the default converter provided by the ICU library function ucnv_getDefaultName().
This function evaluates the current operating system settings and returns a converter name that the e6 server then uses to convert the value returned by the C function getenv to UTF-8. The name of an environment variable must always be in ASCII.
Function Open
There is new optional parameter "/ENC=STR_ENC" for open to specify the encoding to open a file. If /ENC is not set, the value from configuration parameter EDB-CHR-ENC is used.
If "/ENC=STR_ENC" and the configuration parameter EDB-CHR-ENC both are not specified, the system default encoding will be used.
Userexits
Port of TCL Functions
As a replacement of TCL functions, which have been available in former releases, the following userexits have been provided to be callable from within LogiView:
-
xutil_but_ret_actf
-
xutil_but_ret_but
-
xutil_but_rfr_but
-
xutil_but_set_tit
-
xutil_iwf_def_cns
-
xutil_mas_ret_acc_fld
-
xutil_mas_ret_drt_rec
-
xutil_mas_ret_fld
-
xutil_mas_ret_flg_rec
-
xutil_mas_ret_joi_mas
-
xutil_mas_ret_tit_mas
-
xutil_mas_set_joi_mas
-
xutil_mas_set_tit_mas
-
xutil_mas_tit_fld
-
xutil_wdg_ret_act
-
xutil_wdg_ret_mas
For further information about these userexits please refer to the Online Help > Customizing Agile e6 > Parameters > Userexits.
|
Note: See also BugID 19420024. |
Batch Client
Batch Client supports client modes to define the widget behavior on client side. Valid values are BATCH and TEST
-
BATCH: no widgets will be opened on client side.
-
TEST: widgets will be opened on client side virtually
Enterprise Integration Platform (EIP)
EIP Queue
The former internal queue of EIP is de-supported. That means, the file eai_ini.xml supports queues of type 'oracle' only (see controller section and admin section in eai_ini.xml).
The EIP Database Maintainer is de-supported, too. The script dbmaint was removed from EIP package.
New SQL script (db_util/cre_eip_db.sql) are provided to create the EIP database.
Installer
Custom specific Wallets
Custom specific Wallets The GUI and the Batch Installer as well generate now custom specific wallets and deploy them to the correct location within the e6 installation. An adapted epkeytool and a new easy to use batchkey tool is deployed to manage password encryption.
Installation of AutoVue Integration
The installer supports the local installation of the AutoVue Integration as well as a WebStart Deployment.
Java Version
The Server side components require Java 7 to be installed
The Client side components require Java 8 to be installed. Java Client will require JRE 8 32-Bit while AutoVue Integration requires JRE 8 64-Bit.
Enterprise Manager Database Express Console
The Enterprise Manager Database Express console is now activated both with manual installation using templates and with Agile e6 Installer. It can be accessed via:
Upgrade
The upgrade tool allows dump upgrade from e6.1.x directly to e6.2.0.0. Upgrades of older version can be done on request. Patch upgrade is not supported.
The upgrade tool updates all objects to the new Agile e6.2 data model. Beside the cleanup of old no-longer-needed upgrade steps the following new features are provided:
-
Migration of the Kerberos user names from JAAS specific yntax to new WAFFLE syntax.
-
Take over of the current database sequence values from the old production system to the new one.
-
Convert all database columns introduced with the limited I18n support (customer specific implementation) in older releases of Agile e6 from data type nvarchar2 to varchar2.
Integration with Oracle Fusion Innovation Management Cloud
Oracle Fusion Innovation Management Cloud is a new solution that helps organizations increase revenue growth from new products and achieve a competitive advantage by introducing a systematic approach to capturing, selecting and investing in the right ideas and product concepts.
Innovation Management (IM) is part of Oracle Product Value Chain solutions. Offering a 360-degree view of the product innovation, Innovation Management enables organizations to:
-
Build an innovation pipeline that is fueled by a steady stream of high-value ideas that can be translated into profitable offerings.
-
Analyze the impact of alternate investment scenarios against business objectives, such as revenue, cost, profit and resources constraints, to determine the best opportunities to commercialize.
-
Develop product requirements that translate ideas into concepts and products that will achieve stated success criteria.
-
Create product concepts and alternative approaches to meeting product requirements and analyze against product supply chain and cost metrics.
-
Increase productivity and reduce product development costs by strategic focus on fewer, better products that align with the business growth strategies.
Using Agile e6.2 you can run Fusion Innovation Management Cloud integrated with Agile e6. The integration enables you to:
-
Morph IM concept structures into Agile e6 item structure.
-
Derive/create new Agile e6 Items from concept components.
-
Build IM concept structures from Agile e6 item structures
-
Re-Use and integrate Agile e6 items in IM concept structures
De-Supported
Deprecated
DTV Client
The DTV Client is no longer part of Agile e6. This includes the deprecation of the following modules/features:
-
Mask Generator
-
Userexits
-
xvardf_var_def (select menu userexit)
Option /MASGEN no longer supported.
-
xvar_cal_mas_gen (select menu userexit)
No longer supported
-
-
DTV API calls
-
dal_wdh_cal_mgn/wdh_cal_mgn:
Calls function of the user mask generator stack
-
dal_wdh_fnc_mgn/wdh_fnc_mgn:
Adds a function to the user mask generator stack
-
dal_mgn_gen_mas/mgn_gen_mas:
Select menu userexit to open mask generator
-
dal_mgn_usr_drp:
Drop field userexit of mask generator
-
dal_wdg_drg_mgn:
Drag'n'Drop userexit of mask generator
-
-
DTV Dynamic Query Form
DocumentType REDLINE
The old redline functionality is deprecated and will be removed in one of the next releases:
-
Document type REDLINE
-
Table T_DOC_RDL
-
Forms and list of redline entity type
-
Configuration Parameters EDB-RDL-...
-
LGV procedures referencing old redlining
|
Note: See also BugID 19539206. |
Wizard / EDB-ASSISTANT
The entity EDB-ASSISTANT (Wizard) is now removed with all its assigned forms, lists, menus, selections, fields, and constraints.
The following has been removed:
-
Table T_ASS_DAT
-
LogiView model EP_ASS
-
Task EDB-WIZ-OPN
-
Assistant entries in T_ACT_DAT/T_ACT_TEM
-
Userexits
-
xform_ass_exc
-
xform_dlg_act
-
xform_dlg_exc
-
xform_get_ass_wdg
-
xform_poa_mask
-
xform_sav_rec_pom
-
|
Note: See also BugID 19500738. |
Online Documentation
As we are no longer supporting the DataView client and thus the Microsoft Help Format (.chm), the Online Help is now available in a Web Help format. The Web Help format can be viewed using a regular Internet browser (compared to the specific help viewer installed locally for the Microsoft Help Format) and includes a full text search across all modules.
Please see the Agile Engineering Data Management Administration Guide for setting up the Online Help.
The Online Help file is available for download on OTN (Online Help for Agile e6.2.0.0)
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at:
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit:
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info
or, if you are hearing impaired visit:
Oracle Agile Engineering Data Management/Release Notes Release e6.2.0.0
E52566-02
Copyright © September 15, 2015 Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
