Oracle® Application Server Integration Adapter for VSAM Installation and User's Guide 10g (9.0.4) Part Number B10457-01 |
|
After the VSAM data source and the Oracle Connect for VSAM backend adapter have been modeled as described in Chapter 3, "Modeling Interactions for Oracle Application Server Integration Adapter for VSAM", the interactions can be used in a business process in Oracle Application Server ProcessConnect. You define a delivery channel for the VSAM adapter part of the Oracle Application Server Integration Adapter for VSAM. This delivery channel is used during the modeling in Oracle Application Server ProcessConnect with the interactions defined for the adapter in Oracle Studio in a business process.
This chapter contains the following sections:
When adding the adapter type during the application definition, specify VSAM Adapter
.
See Also:
Oracle Application Server ProcessConnect User's Guide for details of setting up applications in Oracle Application Server ProcessConnect |
Part of the application definition includes adding a delivery channel for the Oracle Application Server Integration Adapter for VSAM.
The delivery channel identifies where the OS/390 database adapter is located and the necessary security and encryption requirements to access the adapter.
The delivery channel is defined for the application and the Delivery Channels Details page for the added delivery channel is displayed.
You can now select any of the interactions defined for the adapter.
The procedure for making changes in Oracle Studio to an interaction or to the interaction input and output records and having the change reflected in Oracle Application Server ProcessConnect depends on whether the configuration was deployed or not.
Before the configuration has been deployed, delete the interaction from the application (and all relevant items that reference the interaction) and after making the change in Oracle Studio, add the changed interaction to the application.
After the configuration has been deployed, you cannot change the interaction until you have performed the following procedure:
The interaction that is modeled in Oracle Studio is automatically translated to an xsd presentation in Oracle Application Server ProcessConnect. The xsd can be viewed by displaying the record in the Native Dataypes window (under Modeling > Datatypes).
The following example shows the Oracle Application Server ProcessConnect xsd for an input record.
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="noNamespace://OS390/Navigator/CustAccount#findCustAccountInput" targetNamespace="noNamespace://OS390/Navigator/CustAccount#findCustAccountInput" elementFormDefault="qualified"> <xsd:element name="findCustAccountInput" type="findCustAccountInput"/> <xsd:complexType name="findCustAccountInput"> <xsd:attribute default="ATCLIENT" name="EYE-CATCH" type="xsd:string"/> <xsd:attribute name="ACCT-NUM" type="xsd:string"/> </xsd:complexType> </xsd:schema>
The Oracle Connect metadata for the input record, which was the source for the above xsd, is part of the metadata definition:
<record name="findCustAccountInput"> <field name="EYE-CATCH" type="string" default="ATCLIENT" size="8" nativeType="string"/> <field name="ACCT-NUM" type="string" size="9" nativeType="numstr_u"/> </record>
The Oracle Connect metadata definition can be viewed in Oracle Studio as follows:
The metadata definition includes the following parts:
The following example shows the Oracle Application Server ProcessConnect xsd for an output record.
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="noNamespace://OS390/Navigator/CustAccount#findCustAccountResponse" targetNamespace="noNamespace://OS390/Navigator/CustAccount#findCustAccountRespon se" elementFormDefault="qualified"> <xsd:element name="findCustAccountResponse" type="findCustAccountResponse"/> <xsd:complexType name="findCustAccountResponse"> <xsd:attribute name="RET-CODE" type="xsd:string"/> <xsd:attribute name="ACCT-ID" type="xsd:string"/> <xsd:attribute name="ACCT-FIRST-NAME" type="xsd:string"/> <xsd:attribute name="ACCT-LAST-NAME" type="xsd:string"/> <xsd:attribute name="ACCT-BIRTH-DATE" type="xsd:string"/> <xsd:attribute name="ACCT-MARRIED" type="xsd:int"/> <xsd:attribute name="ACCT-CHILDREN" type="xsd:int"/> <xsd:attribute name="ACCT-TOTAL-ASSETS" type="xsd:int"/> <xsd:attribute name="ACCT-EMPLOYED" type="xsd:int"/> <xsd:attribute name="ACCT-OVERTIME-HOURS" type="xsd:int"/> <xsd:attribute name="ACCT-COMMISSION" type="xsd:float"/> <xsd:attribute name="ACCT-SALARY" type="xsd:double"/> <xsd:attribute name="ACCT-BALANCE" type="xsd:decimal"/> <xsd:attribute name="ACCT-VACATION-DAYS" type="xsd:string"/> </xsd:complexType> </xsd:schema>
The Oracle Connect metadata for the output record has the following structure:
<record name="findCustAccountResponse"> <field name="RET-CODE" type="string" nativeType="int4"/> <field name="ACCT-ID" type="string" size="9" nativeType="numstr_u"/> <field name="ACCT-FIRST-NAME" type="string" size="20" nativeType="string"/> <field name="ACCT-LAST-NAME" type="string" size="20" nativeType="string"/> <field name="ACCT-BIRTH-DATE" type="string" size="8" nativeType="numstr_u"/> <field name="ACCT-MARRIED" type="int" nativeType="int2"/> <field name="ACCT-CHILDREN" type="int" nativeType="int4"/> <field name="ACCT-TOTAL-ASSETS" type="int" nativeType="int8"/> <field name="ACCT-EMPLOYED" type="int" nativeType="int2"/> <field name="ACCT-OVERTIME-HOURS" type="int" nativeType="int4"/> <field name="ACCT-COMMISSION" type="float" nativeType="single"/> <field name="ACCT-SALARY" type="double" nativeType="dfloat"/> <field name="ACCT-BALANCE" type="numeric" size="9" scale="-2" nativeType="decimal"/> <field name="ACCT-VACATION-DAYS" type="string" size="3" nativeType="numstr_s"/> </record>
|
![]() Copyright © 2003 Oracle Corporation. All Rights Reserved. |
|