Creating Native Schema Files with the Native Format Builder Wizard

Defining Complex Condition in choice Condition

Using Native format builder we can pick different kind of records from flat file.

Sample file:

016404460A  TCHAPRASTE VASKEN          M19480901016404460D 120A86   200305      201308             967465840040 E

016463006ABARLLESLEYAF19541129016463006P120B1161 2013012013050005245020130501049000000000{    967459010010  0001031458310485698TBIDDLE MARILYN JF19450807310485698    120C2361  307322486D  20130320130330              0001282100575470305A  PARK   YOUNG OF19470823575470305P  120D3061 201203 2013033060048    020  0001282324

Native Data Format to Be Translated:

The choiceCondition construct is used along with the conditionValue construct for records that are complex and may have fields delimited by fixed length. The other choiceCondition types available are FixedLength, Variable. The following example is for the variable choiceCondition type.

Native Schema:

<?xml version="1.0" encoding="UTF-8" ?>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"

            xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd"

            xmlns:tns="http://TargetNamespace.com/filewrite"

            targetNamespace="http://TargetNamespace.com/filewrite"

            elementFormDefault="qualified"

            attributeFormDefault="unqualified"

            nxsd:version="NXSD"

            nxsd:stream="chars"

            nxsd:encoding="US-ASCII"

> 

  <xsd:element name="Root-Element">

    <xsd:complexType>

      <xsd:choice minOccurs="0" maxOccurs="unbounded" nxsd:choiceCondition="${X}" nxsd:lookAhead="75" nxsd:scanLength="1" nxsd:assignTo="${X}">

        <xsd:element name="RecordA" type="tns:RecordIdentificationCodeAType" nxsd:conditionValue="A" />

        <xsd:element name="RecordB" type="tns:RecordIdentificationCodeBType" nxsd:conditionValue="B" />

                                <xsd:element name="RecordC" type="tns:RecordIdentificationCodeCType" nxsd:conditionValue="C" />

                                <xsd:element name="RecordD" type="tns:RecordIdentificationCodeDType" nxsd:conditionValue="D" />

                               

      </xsd:choice>

    </xsd:complexType>

  </xsd:element>

<xsd:complexType name="RecordIdentificationCodeAType">

    <xsd:sequence>

      --------------------

---------------------------------

</xsd: sequence>

</xsd:complexType>

<xsd:complexType name="RecordIdentificationCodeBType">

    <xsd:sequence>

      --------------------

---------------------------------

</xsd: sequence>

</xsd:complexType>

<xsd:complexType name="RecordIdentificationCodeCType">

    <xsd:sequence>

      --------------------

---------------------------------

</xsd: sequence>

</xsd:complexType>

<xsd:complexType name="RecordIdentificationCodeDType">

    <xsd:sequence>

      --------------------

---------------------------------

</xsd: sequence>

</xsd:complexType>

Translated XML Using Native Schema:

<?xml version = '1.0' encoding = 'UTF-8'?>

<Root-Element xmlns="http://TargetNamespace.com/filewrite">

   <RecordA></RecordB>

   <RecordB></RecordB>

   <RecordC></RecordC>

   <RecordD></RecordD>

</Root-Element>

E-Business Suite Integration Components

E-Business Suite Integration Components

It is important to understand different integration components available within EBS to make informed decision about using one or more for your SOA integration project. Selecting one or more of them depends upon the requirements and the interaction pattern determined to be best fit for the service oriented architecture based integration.
Following are the integration mechanisms available within e-Business suite.

Oracle XML Gateway:

E-Business Suite utilizes the Oracle Workflow Business Event System to support event-based XML message creation and consumption. It can consume events raised by the Oracle E-Business Suite and can subscribes to inbound events for processing. It can be leveraged for Business-to-Business (B2B) and Application-to-Application (A2A) integration scenarios. Majority of messages delivered with the Oracle E-Business Suite are mapped using the Open Application Group (OAG) standard.

Business Events:

The Oracle Workflow Business Event System is an application service that leverages the Oracle Advanced Queuing (AQ) infrastructure to communicate business events between systems. There are more than 1000 built in events with in EBS that can be leveraged for event-based integration of business processes.

Concurrent Programs:

A concurrent program is an instance of an execution file. Concurrent programs use a concurrent program executable to locate the correct execution file. Several concurrent programs may use the same execution file to perform their specific tasks, each having different parameter defaults.

Interface Tables:

Interface tables are intermediate tables into which the data is inserted first. Once the data gets inserted into the interface tables, the data is validated, and then transferred to the base tables. Base tables are real application tables that reside in the application database. The data that resides in the interface tables is transferred to the base tables using concurrent programs. Interface views provide a way to retrieve data from Oracle Applications. By using views, you can get synchronous data access to Oracle Applications.

PL/SQL APIs:

These are stored procedures that enable you to insert and update data in Oracle Applications.
Oracle e-Commerce (EDI) Gateway: Oracle e-Commerce Gateway provides a common, standards-based approach for Electronic Data Interchange (EDI) integration between Oracle Applications and third party applications. It is the EDI integration enabler for Oracle Applications.

UDDI clients and UDDI implementations

UDDI clients and UDDI implementations

Oracle Application Integration Architecture 11g Installation Guide

Introduction to AIA Foundation Pack:

         The Oracle Application Integration Architecture (AIA) Foundation Pack: Development Guide defines in detail how you can use the Oracle AIA Foundation Pack to conceptualize AIA projects and, using the AIA FP Project Lifecycle Management application, implement a solution conforming to the AIA FP in a structured fashion based on a functional design document. You can use this guide to implement additional functionalities in the form of new services extending the AIA Process Integration Packs (PIP) functionalities.

Oracle Application Integration Architecture (AIA FP) is a complete integration solution for orchestrating agile, user-centric, business processes across enterprise applications. AIA FP offers prebuilt solutions at the data, process, and user interface levels delivering a complete process solution to business end users. All of the AIA FP components are designed to work together in a mix-and-match fashion. They are built for configurability, ultimately helping to lower IT costs and the burden of building, extending, and maintaining integrations.

Powered by Oracle Fusion Middleware, AIA FP enables organizations to utilize the applications of their choice and create Composite Business Processes (CBPs) following these guiding principles that define the ground rules for development, maintenance, and usage of a service-oriented architecture (SOA):

1. Reuse, granularity, modularity, compose ability, componentization, and interoperability.

2. Standards-compliance (both common and industry-specific).

3. Service identification and categorization, provisioning and delivery, and monitoring and tracking.

With AIA FP, business processes can be engineered according to the following types of integrations:

1.       User Interface Integration

                A User Interface Integration connects disparate systems to provide a unified view to the user. It is a single view to many heterogeneous systems that are integrated at the user-interface level. It significantly increases the productivity to the end user by eliminating the need for the user to toggle back and forth between these systems. For example, in the Siebel Order Capture application, the order configuration capability of the Oracle E-Business Suite application has been embedded. Although this approach provides a unified approach to the users, there is no aggregation of data at the applications level.

2. Data Integration

             A Data Integration connects at the logical level of data, making the same data available to more than one application. This is accomplished by relying upon database technologies. This type of integration is a good candidate when there is a minimal amount of business logic to be reused across applications.

2.       Functional Integration

         A Functional Integration connects applications at the business-logic layer. This type of integration is a good candidate when there is a need for reuse of functionality, such as business logic or processing.

4. Process Integration

          A Process Integration is primarily accomplished by exposing object interfaces that can be consumed by other systems, by using message-oriented middleware (MOM) systems to send messages to the destinations, or by exposing web service interfaces that can be consumed by the clients.

1. Oracle AIA FP Installation on windows 7 64 bit:

1.1. Go to AIA FP Patch Setup file location inside we have win64bit click on setup file.

 1.2. Next enter JDK location click on enter.

 

              

 1.3. Welcome Screen click on next.

1.4. Create AIA FP Home folder in middleware.

1.5. Select AIA Home location and give AIA Instance name, select JDK location click on next.

1.6. Enter SOA Server Details click on next.

1.7. Next we need start the Node manager from web logic server.

1.8. Start the Node Manager.

1.9. Node manager running on 5556 port.

1.10. Server Validation ok click on next otherwise retry.

1.11. Next enter DB details for AIA FP Schemas.

1.12. Enter MDS details.

1.13. Click on next this screen is optional if you have OER provide details.

1.14. Click on install button.

2. Configuration progress

3. End Processes

Note: SOA Server Shut Down itself .after few minutes it will restart otherwise we need restart manual.

Any Java related Process are running close the process remove lok files and temp, cache from our servers.

Note: Don’t close javaw.exe..Because this is related to our setup file.

3.1. AIA FP Configuration success.

4. AIA Console

4.1 we can open AIA FP Console from below link.

   http://localhost:8001/AIA

Login details are same as em console.

4.2 AIA FP Home Page:

5. AIA FP Adapter Starts from Console:

SOA Domain Configured in development mode we need to start the AIA FP Adapters manually.

Go to Admin Console -> click on Deployments ->start AIA FP related Adapters (AIA_AQ, AIA_JMS, AIA_DB, AIA_OracleApps).

6. AIA Foundation Pack Service Constructor for JDeveloper 11.1.1.6.0:

          

       This extension creates Application Integration Architecture (AIA FP) Service Constructor to create an AIA FP based service component project. This extension is an online JDeveloper update. Start JDeveloper. From the menu choose Help > Check for Updates. In the Update Wizard, select Search Update Centers and ensure the first and second options are checked (screenshot). Then ensure that Oracle AIA Foundation Pack Service Constructor is checked.

Step1: Open Oracle JDeveloper go to help ->click on check for Updates.

Step2: Select oracle fusion updates and oracle extensions click on next.

Step3: Select AIA FP Service Constructor click on next.

Step4: Download start for AIA FP extension file.

Step5: Click on finish.

7. Oracle AIA FP reference links:

Download Oracle AIA foundation Pack patch setup from below link:

http://www.oracle.com/technetwork/middleware/foundation-pack/downloads/fpdownloads-152617.html

Download Oracle AIA foundation Pack reference guide from below link:

http://www.oracle.com/technetwork/middleware/foundation-pack/documentation/index.html#111160

Cleanup Instances from Dehydration Tables

Cleanup Instances from Dehydration tables:

TRUNCATE TABLE INSTANCE_PAYLOAD DROP storage;

TRUNCATE TABLE REFERENCE_INSTANCE DROP storage;

TRUNCATE TABLE REJECTED_MSG_NATIVE_PAYLOAD DROP storage;

TRUNCATE TABLE INSTANCE_PAYLOAD DROP storage;

TRUNCATE TABLE COMPOSITE_INSTANCE_FAULT DROP storage;

TRUNCATE TABLE COMPOSITE_SENSOR_VALUE DROP storage;

TRUNCATE TABLE COMPOSITE_INSTANCE_ASSOC DROP storage;

TRUNCATE TABLE COMPOSITE_INSTANCE DROP storage;

TRUNCATE TABLE AUDIT_TRAIL DROP storage;

TRUNCATE TABLE CUBE_INSTANCE DROP storage;

TRUNCATE TABLE CUBE_SCOPE DROP storage;

TRUNCATE TABLE AUDIT_DETAILS DROP storage;

DELETE FROM XML_DOCUMENT;

COMMIT;

/app/oracle/product/Middleware

Clean up the dehydration store database and the file system by executing the following statements:

--Schemas:

SQL> drop user "DEV_MDS" cascade;

SQL> drop user "DEV_ORABAM" cascade;

SQL> drop user "DEV_ORASDPM" cascade;

SQL> drop user "DEV_SOAINFRA" cascade;

SQL> delete from SCHEMA_VERSION_REGISTRY where OWNER like 'DEV%';

SQL> commit;

--Table spaces and data files:

SQL>DROP TABLESPACE DEV_IAS_ORASDPM INCLUDING CONTENTS AND DATAFILES;

SQL>DROP TABLESPACE DEV_IAS_TEMP INCLUDING CONTENTS AND DATAFILES;

SQL>DROP TABLESPACE DEV_MDS INCLUDING CONTENTS AND DATAFILES;

SQL>DROP TABLESPACE DEV_ORABAM INCLUDING CONTENTS AND DATAFILES;

SQL>DROP TABLESPACE DEV_SOAINFRA INCLUDING CONTENTS AND DATAFILES;

JMS Adapter

JMS Adapter:

Oracle JCA Adapter for JMS (Oracle JMS Adapter), which enables an Oracle BPEL process or an Oracle Mediator component to Interact with Java Messaging Service.

The JMS as Two Modelling:

1. Point-to-point.

2. Pubish-Subsribe.

1.  Point-to-point(Queue):

In the point-to-point domain, messages are exchanged through a queue and each message is delivered to only one receiver.

In point-to-point messaging, the messages are stored in a queue until they are consumed. One or more producers write to the queue and one or more consumers extract messages from the queue. The JMS consumer sends an acknowledgment after consumption of a message.

2.  Pubish-Subsribe(Topic):

In the publish-subscribe model, messages are sent to a topic and can be read by many subscribed clients.

In publish/subscribe messaging, producers publish messages to a topic, and the consumer subscribes to a particular topic. Many publishers can publish to the same topic, and many consumers can subscribe to the same topic. All messages published to the topic by the producers are received by all consumers subscribed to the topic. By default, subscribers receive messages only when the subscribers are active. However, JMS API supports durable subscriptions that ensure that consumers receive messages that were published even when the subscribers are not up and running. The durable subscription involves registering the consumer with a unique ID for retrieving messages that were sent when the consumer was inactive. These messages are persisted by the JMS provider and are either sent to the consumer when it becomes active.

This Oracle JMS working with any JMS Providers like:

AQ JMS, TIBCO JMS, IBM Web sphere (MQ Series JMS), Web logic JMS, Apache and Active MQ.

Oracle JMS Features:

è    Oracle JMS Adapter Support Queues and Topic.

è    Oracle JMS Adapter provides support to stream payload. When you enable this

Feature used for storing large message payloads into the Queue or Topic.

Asynchronous communication, guaranteed message delivery, receipt notification, and transaction control. JMS is a Java interface developed by Sun Microsystems for producing, sending, and receiving messages of an enterprise messaging system. JMS is an API that JMS vendors implement. Oracle provides two implementations of JMS, WLS JMS and Oracle JMS based on Oracle advanced queues. A JMS producer creates JMS messages and a JMS consumer consumes JMS messages.

Heap Size Increase in Oracle JDeveloper 11g

Oracle JDeveloper Heap size Increased in OracleJDevHome inside-àJDeveloper ->Jdev-> bin->jdev.conf

Here we need to change the heap memory size by default it is 216 but we can increase as 512.

We can able to see the heap in IDE level we need set this property in jdev.conf.

once we set this property we can able to see in IDE level.

Exg file location :MiddlewareHome\OracleJDevMiddleware\jdeveloper\jdev\bin\jdev.conf.