Oracle® Application Server Release Notes
10g (9.0.4) for Solaris Operating System (SPARC) Part No. B10629-15 |
|
![]() Previous |
![]() Next |
This chapter describes issues with Oracle Application Server InterConnect (OracleAS InterConnect). It features the following topic:
This section describes general issues and their workarounds for OracleAS InterConnect. It includes the following topic:
The OracleAS InterConnect Adapter for Siebel 2000 supports 6.2.1 Enterprise Edition with patch 110 or higher. The patch is necessary to resolve a memory leak on the Siebel server when any kind of remote client is used. All instructions in the patch 110 Maintenance Release Guide from Siebel Systems must be followed carefully. The most important instruction that addresses the server side memory leak is the setting of the Siebel server recyclefactor
component parameter. Set the recyclefactor
parameter to a value greater than the default value of zero. The Maintenance Release Guide recommends a value of 3. This will improve server performance and memory usage. This step must be completed for all object managers in use.
Oracle supports using Microsoft Internet Information Server (IIS) with the HTTP adapter for Oracle Application Server 10g(9.0.4). This support is provided through use of the OracleAS Proxy Plugin for Microsoft IIS for inbound communications.
This section describes administration issues and their workarounds for OracleAS InterConnect. It includes the following topic:
This section describes data definition description language enhancements. It includes the following topics:
This enhancement allows the Data Definition Description Language (D3L) author to add a new type of member, property. Syntax, to a D3L structure, in addition to fields
and pads
. For example:
<struct ... ... <property name="prop_name" /> ... </struct>
Note: There is no type definition associated with this structure element. |
The modified D3L Data Type Definition (DTD) for this new structure element is:
<!ENTITY % StructElements "field | property | pad" > <!ELEMENT property EMPTY > <!ATTLIST property %FieldAttributes; >
The semantics of this new structure element is to link data in a transport protocol header with the message payload. In other words, when a D3L containing a structure with one, or more, property member(s) is imported in iStudio, it will create a String OAI
attribute with the name specified in the property name
attribute.
At runtime, this OAI
attribute will be populated with the value of a transport protocol header, inbound–to-hub
, which name matches the name
attribute of the property member. Vice versa, for outbound messages, the OracleAS InterConnect message payload
property value will define the value of the corresponding protocol header.
For example, if using OracleAS InterConnect Adapter for FTP, the file structure would be:
<struct ..> <property name="filename" /> <field ...
In this case, the OracleAS InterConnect Application View attribute filename
, that is derived from the D3L definition, would be assigned the name of the actual file being passed to D3L. For outbound message, the value will determine the physical filename being used to store the file.
If using OracleAS InterConnect Adapter for HTTP, an example file structure would be:
<struct ..> <property name="Host" /> <property name="Referer" /> <field name="...> < ...
Note: This is a dynamic payload dependent feature, which will override settings in theadapter.ini file and/or Application View Meta Data Modify Fields. Therefore, the property ota.send.endpoint could be overridden by a corresponding message attribute defined via the D3L.
|
The D3L syntax allows you to create multiple nested imparrays for outbound translations (app-to-native
or hub-to-spoke
).
Intuitively it makes sense to allow multiple nested imparrays to match multiple nested arrays in XML since XML does not have the need to declare the length of an array. For example:
<array1> <array2>..</array2> <array2>..</array2> </array1> <array1> <array2>..</array2> <array2>..</array2> <array2>..</array2>
If this XML message was published by OracleAS InterConnect Adapter for AQ, and consumed by OracleAS InterConnect Adapter for FTP that is running in D3L mode, the above structure would then be matched by the following D3L structure:
<imparray id="array1"> <imparray id="array2"> ..
Since D3L does not perform parsing for app-to-native
translation, also known as production
, the above D3L is entirely possible. However, for native-to-app
translations, the above D3L would be invalid since a single imparray by itself would consume the rest of the native message.
Note: This new imparray semantics depart from the design principle that D3L is a fully bidiretional symmetric translator and can perform bothnative-to-app and app-to-native translation using just one the same D3L definition.
|
Finally, the D3L translator will determine, at runtime, whether multiple nested imparrays exist in a D3L. If multiple nested imparrays are detected, the translator will prevent the D3L from being used for parsing purposes (native-to-app
translations). If not detected, the D3L translator will flag an error condition.
This section describes known errors in the documentation. It includes the following topic:
Section 22.3.1, "Oracle Application Server InterConnect Installation Guide"
Section 22.3.2, "Oracle Application Server InterConnect Users Guide"
Section 22.3.3, "Incorrect Operating System Requirement Listed in OracleAS InterConnect Guides"
Chapter 4 of the Oracle Application Server InterConnect Installation Guide has the following incorrect statement:
"1. Start the hub database. This is the Oracle8i or Oracle9i database." The Oracle8i database cannot be used as a hub database.
This section describes known errors in the Oracle Application Server InterConnect Users Guide. It includes the following topics:
The screen shots shown in Chapter 9, "Runtime Management" on pages 9-3, 9-4, and Figure A-8 in Appendix A, "Integration Scenario" are incorrect.
The following user interface descriptions are incorrect:
On Page 2-10, under the Procedure Menu heading:
Invoke should be Invoke Procedure
Implement should be Implement Procedure
On Page 2-12, under the Design Navigation Tree heading:
Each object type in the Deploy Navigation tree is..... should be Each object type in the Design Navigation tree is.....
On Page 2-13, under the Context Menus heading, in the Context Menu Options table:
WF Builder, Launch WF Home Page should be Workflow Builder, Launch Workflow Home Page
Deploy, Edit Configuration, Launch WF Home Page should be Deploy to Workflow, Edit Workflow Configuration, Launch Workflow Home Page
On page 2-13, under the Creating a New Workspace heading:
The New Workspace Dialog displays should be The Create Workspace Dialog displays.
On page 6-12, under the Adding Mapping Variables heading:
To add mapping variables, use the Mapping dialog should be To add mapping variables, use the Mapping Parameter dialog.
On page 7-12, the first sentence on the page:
The Subscribe Activity Wizard displays should be The Subscribe Wizard displays.
On page A-9, Step 7:
Click OK should be Click Save.
The Operating System Requirements table in the OracleAS InterConnect guides list the incorrect version of IBM-AIX 5. The Oracle Application Server 10g (9.0.4) version of InterConnect can run on IBM-AIX 5L 5.2 or higher versions and not 5.1. The incorrect requirement is listed in the following guides:
OracleAS InterConnect Installation Guide
OracleAS InterConnect Adapter for AQ Installation and User's Guide
OracleAS InterConnect Adapter for DB Installation and User's Guide
OracleAS InterConnect Adapter for MQSeries Installation and User's Guide
OracleAS InterConnect Adapter for FTP Installation and User's Guide
OracleAS InterConnect Adapter for HTTP Installation and User's Guide
OracleAS InterConnect Adapter for SMTP Installation and User's Guide
OracleAS InterConnect Adapter for OA Installation and User's Guide