Index
A B C E I M N O S V W X
A
- APIs
- adding a new partner link, 3.2.2.2
- configuring OracleAS Adapter for Oracle Applications, 3.2.2
- configuring the Invoke activity, 3.2.2.5
- configuring the Transform activity, 3.2.2.6
- creating a new BPEL project, 3.2.2.1
- deploying the BPEL process, 3.3.1
- design-time steps, 3.2
- overview, 3.1
- prerequisites to configure, 3.2.1
- run-time steps, 3.3
- testing the BPEL process, 3.3.2
B
- B2B, 6.1.2
- base tables, 2.1.1
C
- concurrent programs
- adding a partner link, 4.2.2.2
- configuring OracleAS Adapter for Oracle Applications, 4.2.2
- configuring the Invoke activity, 4.2.2.3
- configuring the Transform activity, 4.2.2.4
- creating a new BPEL project, 4.2.2.1
- deploying the BPEL process, 4.3.1
- design-time steps, 4.2
- overview, 4.1
- prerequisites to configure, 4.2.1
- run-time steps, 4.3
- testing the BPEL process, 4.3.2
- verifying records, 4.3.3
E
- EDI
- adding a partner link, 5.2.2.2
- configuring OracleAS Adapter for Oracle Applications, 5.2.2
- configuring the Invoke activity, 5.2.2.3
- configuring the Transform activity, 5.2.2.4
- creating a new BPEL project, 5.2.2.1
- deploying the BPEL process, 5.3.1
- design-time steps, 5.2
- overview, 5.1
- prerequisites to configuring OracleAS Adapter for Oracle Applications, 5.2.1
- run-time steps, 5.3
- testing the BPEL process, 5.3.2
- verifying records in Oracle Applications, 5.3.3
I
- integration architecture, 6.1.2
- interface tables, 2.1
- adding a partner link, 2.1.2.2.2
- configuring OracleAS Adapter for Oracle Applications, 2.1.2.2
- configuring the Assign activity, 2.1.2.2.4
- configuring the Invoke activity, 2.1.2.2.3
- creating a new BPEL project, 2.1.2.2.1
- deploying the BPEL process, 2.1.3.1
- design-time steps, 2.1.2
- overview, 2.1.1
- prerequisites to configure, 2.1.2.1
- run-time steps, 2.1.3
- testing the BPEL process, 2.1.3.2
M
- message queues, 6.1.3
- inbound queues, 6.1.3.1
- outbound queues, 6.1.3.2
N
- new features, 1.3
O
- Oracle Applications
- overview, 1.1
- OracleAS Adapter for Oracle Applications
- architecture, 1.2.2
- features, 1.2.1
- installating e-Business Suite Adapter, 1.3.1
- interfaces, 1.2.3
- issues and workarounds, 1.3.3
- new features, 1.3.2
- overview, 1.2
S
- sample oc4j-ra.xml file, A.2
- sample WSDL file, A.1
- standards-based messaging, 6.1.1
V
- views, 2.2
- adding a partner link, 2.2.2.2.2
- configuring Oracles Adapter for Oracle Applications, 2.2.2.2
- configuring the Assign activity, 2.2.2.2.4
- configuring the Invoke activity, 2.2.2.2.3
- creating a new BPEL project, 2.2.2.2.1
- deploying the BPEL process, 2.2.3.1
- design-time steps, 2.2.2
- overview, 2.2.1
- prerequisites to configure, 2.2.2.1
- run-time steps, 2.2.3
- testing the BPEL process, 2.2.3.2
W
- wrapper APIs, 3.2.2.3
- describing DEFAULT clause handling in wrapper procedures, 3.2.2.4.1
- describing parameters with DEFAULT clause, 3.2.2.4
- WSDL, A.1
X
- xml
- overview, 6.1
- XML gateway envelope, 6.1.4
- ATTRIBUTE3, 6.1.4
- DOCUMENT_NUMBER, 6.1.4
- MESSAGE_STANDARD, 6.1.4
- MESSAGE_TYPE, 6.1.4
- parameters defined by the application, 6.1.4
- parameters not used, 6.1.4
- PARTY_SITE_ID, 6.1.4
- PASSWORD, 6.1.4
- PAYLOAD, 6.1.4
- PROTOCOL_ADDRESS, 6.1.4
- PROTOCOL_TYPE, 6.1.4
- SOURCE_TP_LOCATION_CODE, 6.1.4
- TRANSACTION_SUBTYPE, 6.1.4
- TRANSACTION_TYPE, 6.1.4
- USERNAME, 6.1.4
- XML gateway inbound
- adding a partner link for the file adapter, 6.2.2.4
- configuring OracleAS Adapter for Oracle Applications, 6.2.2
- configuring the Assign activity, 6.2.2.6
- configuring the Invoke activity, 6.2.2.3
- configuring the Receive activity, 6.2.2.5
- creating a new BPEL project, 6.2.2.1
- creating a partner link, 6.2.2.2
- deploying the BPEL process, 6.3.1
- design-time steps, 6.2
- prerequisites to configure, 6.2.1
- run-time steps, 6.3
- testing the BPEL process, 6.3.2
- using transaction monitor, 6.3.3.1
- verifying records, 6.3.3
- XML gateway outbound
- configuring OracleAS Adapter for Oracle Applications, 6.4.2
- design-time steps, 6.4
- prerequisites to configure, 6.4.1
- run-time steps, 6.5