Oracle Applications InterConnect Release Notes Release 4.1 for Windows NT and UNIX Part Number A90368-01 |
|
Oracle is a registered trademark, and Oracle Applications InterConnect is a trademark or registered trademark of Oracle Corporation. Other names may be trademarks of their respective owners.
Copyright © 2001, Oracle Corporation.
All Rights Reserved.
Release 4.1 for Windows and UNIX
May 2001
Part No. A90368-01
These release notes accompany Oracle Applications InterConnect Release 4.1. This document contains the following topics:
Apply the latest Oracle Applications InterConnect 4.1 patches available at MetaLink <http://metalink.oracle.com
>.
The following features are new in this release of Oracle Applications InterConnect.
The name of Oracle Applications InterConnect has been changed to Oracle9iAS InterConnect. This new name will be reflected in the documentation for the next release.
Oracle Applications InterConnect works with Oracle Workflow for business process collaborations. Oracle Workflow does not exist on Linux, therefore, Oracle Workflow and Oracle Applications InterConnect business collaboration is not supported for Linux.
The AQ adapter has been enhanced to handle more than just XML payload. The payload can be RAW with XML data or it can be an Oracle Object where any field can contain XML data. This Oracle Object can be directly imported in iStudio.
The SAP adapter is available on the UNIX platform.
The SAP adapter supports ABAP function modules in addition to BAPIs and IDOCs.
iStudio provides graphical mapping of array attributes.
All passwords stored in configuration files can now be encrypted. For more information, see the Oracle Applications InterConnect Installation Guide.
When changes are made to the metadata through iStudio, an option to push this new metadata to any of the already running adapters is available. This can be accomplished using the Push Metadata option on the File menu in iStudio.
The Oracle Enterprise Manager Console includes the following features for remotely managing the adapters and repository. This list only represents a few of the available features.
Throughput management allows the user to monitor the throughput of adapters using the Oracle Enterprise Manager Console.
Message tacking provides the ability to track any messages that flow through Oracle Applications InterConnect. To use this feature, select at least one Tracking field in iStudio. Messages can now be tracked by specifying values for any of these tracking fields in the Oracle Enterprise Manager Console.
Email and pager alerts can now be set using the Oracle Enterprise Manager Console to be triggered if an adapter or repository goes down.
Similar to previous releases, all errored-out messages are stored in the database. The Oracle Enterprise Manager Console now allows these messages to be viewed, modified, and resubmitted.
The following topics describe changes made to Oracle Applications InterConnect since the last release.
Oracle Internet Directory is no longer necessary with Oracle Applications InterConnect Release 4.1. All necessary configuration is stored directly in the hub database. When creating a project in iStudio, the hub database connection information needs to be provided along with repository information.
Oracle Message Broker is no longer necessary with Oracle Applications InterConnect Release 4.1. Oracle Applications InterConnect uses the Oracle JMS interface to Advanced Queues.
All Oracle Applications InterConnect configuration parameters are now stored in one adapter.ini
file, as opposed to many files such as the adapter.ini
, Agent.ini
, and service.ini
.
To avoid overwriting log files from a previous run, log files are created in a different directory every time the adapter is started. The timestamp is used as the name of the directory to keep it unique across various runs. All logging is done to only one oailog.txt
file, as opposed to several files such as AgentLog.txt
, <Adapter>Log.txt
, service.log
. As in previous releases when the size of this file exceeds 1MB, new files are created, such as oailog-1.txt
, oailog-2.txt
, and so on.
To avoid filling the adapter directory with files, all persistence files containing persisted messages, cached metadata, and other information to ensure guaranteed and exactly once delivery, are stored in a the persistence
directory.
The performance of the database adapter has been enhanced. This is realized only if the database hosting the Oracle Applications InterConnect schema has support for Oracle Objects (Oracle8i and higher).
When deleting an object, any objects referred to by that object are deleted if they are not referenced by other objects. For example, a Customer object contains an Address object. When the Customer object is deleted, the Address object is also deleted. If another object exists, such as Purchase Order that contains Address, then Address is not deleted. In addition, the Address object can not be deleted directly because it is referenced by another object.
iStudio supports importing attributes of other iStudio data types.
The following lists the system limitations and known issues of specific Oracle Applications InterConnect components.
The size of the messages is limited by Advanced Queue. See the Oracle Advanced Queue and the accompanying Oracle JMS interface for the Oracle Advanced Queues for maximum message sizes.
The publishing and invoking adapter may display the following exception which can be safely ignored:
A nonfatal internal JIT (3.00.072b(x)) error 'ResolveItem64' has occurred in: 'oracle/sql/NUMBER.toBytes (Ljava/math/BigDecimal;)[B': Interpreting method. Please report this error in detail to http://java.sun.com/cgi-bin/bugreport.cgi
This is a known issue which has already been reported to Sun Microsystems, Inc. For further details see:
http://developer.java.sun.com/developer/bugParade/bugs/4237260.html
In case of application errors when trying to deliver a message, the Oracle Applications InterConnect runtime tries to deliver this message every minute until it succeeds or until it is informed to ignore the error message. The user should run the ignoreErrors <error code>
command from within the adapter directory to inform Oracle Applications InterConnect to ignore this application error and proceed with the next message. It only stores this error code in memory, so if this adapter is restarted, it does not remember to ignore this error code. The workaround is for the user to store these error codes in a file called ErrorCodes.ini
in the adapter directory with one error code per line.
If any OutOfMemory
exceptions are noticed, it is possible the specified Maximum Heap Size for the Java Virtual Machine is not sufficient. Increase this by completing the following:
In previous versions of Oracle Applications InterConnect, users imported the DTD in iStudio and configured an application queue where the corresponding XML message could be picked up or placed in by the Oracle Applications InterConnect adapter. If the Advanced Queue had a RAW payload, the payload would be plain XML. If the Advanced Queue's payload was an ADT, the first CLOB attribute of this ADT should have contained the XML message.
Note: For Advanced Queues with a RAW payload containing the XML string, there is no change in this release. This issue only affects users using Advanced Queues with an ADT payload. |
In this release, the AQ adapter supports Oracle ADTs in addition to XML. This adapter provides complete flexibility to import the Advanced Queue's payload ADT. Therefore, any, some, or all of the attributes can be associated within this ADT to be of different XML types.
For example, a user needs to send a Customer and PurchaseOrder as part of one Oracle Applications InterConnect message. The corresponding DTDs are contained in the Customer.DTD
and PurchaseOrder.DTD
files. If an Oracle Advanced Queue is "inQueue" which contains an ADT payload (Customer CLOB
, CreationDate DATE
, and PurchaseOrder BLOB
). In this example, the application is enqueuing an Oracle Object containing Customer XML adhering to Customer.DTD
, a creation date, and a Purchase Order XML adhering to PurchaseOrder.DTD
.
The following steps describe the tasks to perform in iStudio to perform the example above in iStudio:
For example, create an application datatype called DTDs
and then select Import from XML to import Customer.DTD
. Similarly import PurchaseOrder.DTD
as well. After this step, select the Reload option from the File menu, then select the current project. This is a workaround for a known iStudio issue.
The three corresponding Oracle Applications InterConnect attributes: Customer String
, CreationDate Date
, and PurchaseOrder String
are created in iStudio.
Customer.DTD
was imported. Similarly, change the datatype for the PurchaseOrder
attribute to correspond to the one created using PurchaseOrder.DTD
.
The rest of the process is the same as for other messages.
The following are known issues for Oracle Applications InterConnect infrastructure.
The following are recommended minimum database parameter values for Oracle Applications InterConnect adapters. These values must be changed in the init.ora
file.
db_block_buffers = 3200
shared_pool_size = 314572800
large_pool_size = 61440000
java_pool_size = 60971520
The following bugs are known to exist in the Oracle Applications InterConnect Release 4.1. Workarounds are provided when appropriate. The known bugs are grouped by process or component:
Bug 1761263 | Cannot use ID as the name for an attribute. |
Description: |
ID is used internally therefore, an attribute cannot be named ID. |
Action: |
None. |
|
Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|