SOA: XAResource.XAER_RMFAIL start() failed on resource

If you see the Following Exception in the WebLogic log:

XAResource.XAER_RMFAIL start () failed on resource 'XXX_XXX_osb_domain': XAER_RMFAIL: Resource manager is unavailable javax.transaction.xa.XAException: Internal error: XAResource 'GARD_NET3PROD_osb_domain' is unavailable

Solutions:

Set XA Transaction Timeout to a higher value and enable XA Transaction timeout on the Specified data source.

or

Increase MaxXACallMillis   value on JTA Advanced settings on the WebLogic domain. Setting the Applies to the entire domain. (Default: 120000)

If a problem still persists please check the Following Oracle MetaLink note for database patch details:

XAER_RMERR rather than XAER_RMFAIL reported for a JDBC session When The instance HAS aborted.

SOA DB Merge operation is not updating records properly

DBAdapter - Merge operation issue in 11g

If you use the merge operation for updating records using DBAdapter, make sure DetectOmission property is set to false, as by default it's true. Or else values ​​coming as Null Will not Get udpated in database records - Causing updates buggy.

  Property name = "DetectOmissions" value = "false" / 

Oracle AIA 11g

What do terms like AIA, EBO, EBS, etc. mean?

Oracle has it's own guide to explain all the AIA terms, the AIA Concepts and Technologies Guide [ref: Oracle® Application Integration Architecture -Foundation Pack 2.5: Concepts and Technologies Guide Release 2.5 Part No. E15762-01 October 2009]. Here a overview of the terms AIA, EBO, EBM, ABO, ABM, EBS, EBF, ABCS, BSR, CAVS, PIP, SOA, ESB and BPEL with their explanation:

AIA - Application Integration Architecture
Oracle Application Integration Architecture Foundation Pack provides Oracle's best-practice methodology and reference architecture, which are based on a profound service-oriented foundation running on Oracle's best-in-class middleware suites. Application Integration Architecture defines a common vocabulary across applications and industries. EBOs are the key elements in this context. They canonically describe standard business entities such as an order or an invoice. Based on these generic business entities, Application Integration Architecture delivers other artifacts such as EBSs, EBMs, EBFs, and ABCSs.
Basically AIA delivers you the integration framework including a canonical model.

EBO - Enterprise Business Object
You can think of EBOs as canonical, application-agnostic representations of frequently used business entities. The architecture starts with the concept of Enterprise Business Objects (EBOs). EBOs can be considered as application-independent representations of key business entities.
Basically EBOs are the objects moving between applications.

EBM - Enterprise Business Message
An EBM is the message format that is specific to the input or output of an EBS operation. Enterprise Business Service operations require specific message formats called Enterprise Business Messages (EBMs) for service requests and responses.
Basically EBMs are the envelopes containing the EBOs.

ABO/ABM - APPLICATION Business Objects/Messages
The Oracle AIA canonical model exists of the EBOs and EBMs. Outside the canonical domain are the application-specific formats, these can be objects and messages, respectively ABOs and ABMs. Every application has it's own set of ABOs and ABMs.
Basically ABOs and ABMs are APPLICATION specific objects and envelopes.

EBS - Enterprise Business Service
An EBS provides the generic operations that an EBO should have. Enterprise Business SERVICES (EBSs) are the centerpiece of the AIA Reference Architecture. They implement the required operations on EBOs in the right coarse-grained granularity that SOAs demand. For every EBO, Application Integration Architecture also ships generic service definitions to cover standard operations such as create, update, query, delete, and sync.
Basically EBSs are the routing services.

EBF - Enterprise Business Flow
An EBF orchestrates a number of EBSs to implement a complex integration flow. Sometimes, the integration scenario is not just a simple requester-provider relationship. In those cases, an Enterprise Business Flow (EBF) orchestrates any number of EBSs required to implement a specific business flow. The EBF completely controls the business logic and calls the appropriate EBS methods.
Basically EBFs are the orchestrations spanning multiple EBO's and/or APPLICATIONS.

ABCS - Application Business Connector Service
An ABCS implements a particular service operation in the context of a specific application. To enable applications to integrate into these generic, application-independent structures, you can implement Application Business Connector Services (ABCSs). Such an ABCS calls or is called by the appropriate EBS, depending on whether the application is in the requestor or provider role in a particular scenario. The main responsibilities of ABCSs include: conversion between the generic EBO and the application-specific format (ABO), cross-referencing of key attributes and message validation, and conversation with the specific application.
Basically ABCSs are the application-specific services per EBM.

BSR - Business Service Registry
The BSR stores and provides INFORMATION about the objects, messages, and services that compose the integration scenarios in your Oracle AIA ecosystem. An integration scenario refers to the end-to-end (requester participating application-to-provider participating application) flow of a message. The BSR presents the components of your integration scenarios in a centrally managed and searchable repository, enabling it to become the system of record for YOUR BUSINESSservices.
Basically BSR stores services, TEST-definitions and application-information.

CAVS - Composite Application Validation System
The CAVS enables you to test integration web services without the deployed participating applications in place. Using a framework that includes initiators to simulate calls to participating applications and simulators to simulate responses from participating applications, CAVS provides a system that can test integrations while also eliminating the need to set up deployments of all participating applications that are involved in the integration. The CAVS provides a test repository, an execution engine, and a user interface.
Basically CAVS is a TESTING framework.

PIP - Process Integration Pack
Prebuilt process integration packs (PIPs) from Oracle use the Oracle AIA to deliver composite industry processes for specific industries, using SOFTWARE assets from Oracle's portfolio of applications. Most of these solutions encompass orchestrated process flows, as well as prebuilt data integration scenarios that are meant to seamlessly connect the systems.
Basically PIPs are off-the-shelf integrations.

SOA - Service Oriented Architecture
Oracle AIA relies upon a SOA for integrations. SOA is an approach for defining an architecture based on the concept of a service. SOA applications are integrated at the service specification point, not at the application interface. This allows application complexities to be separated from the services interface, and diminishes the impacts of back-end interface and application changes. Service-oriented integration leverages messages to communicate between consumers and providers and uses XML schemas and TRANSPORTS such as SOAP to transport messages.
Basically SOA is integrating using (web)services.

ESB - Enterprise Service Bus
In integrations where it makes sense, Oracle AIA also relies on ESB. An ESB is the underlying infrastructure for delivering SOA. Oracle AIA uses Oracle Enterprise Service Bus as the foundation for services using SOA. It enables interaction through services that encapsulate business functions and supports service routing and the substitution and TRANSLATION of TRANSPORTprotocols.
Basically ESB and BPEL are THE ENGINES driving Oracle SOA Suite. ESB is used for APPLICATION adapters and routing rules (EBSs).

BPEL - BUSINESS PROCESS Execution Language
BUSINESS PROCESS Execution Language (BPEL), short for Web Services Business Process Execution Language (WS-BPEL) is an OASIS standard executable language for specifying actions within business processes with web services. Processes in Business Process Execution Languageexport and import information by using web service interfaces exclusively.
Basically BPEL and ESB are the engines of the Oracle SOA Suite. BPEL is used for transformations (ABCSs) and orchestrations (EBFs).

Oracle B2B

What is eCommerce ?

eCommerce, is the buying and selling of products or services over 

the Internet. It can take many forms and shapes one of which is 

Business-to-Business (B2B)

An enterprise extends its business processes over the Internet 

enabling commerce with its Trading Partners is B2B

What is Oracle B2B ?

Oracle B2B is an eCommerce gateway enabling the secure & reliable 

exchange of business documents between trading partners 

Oracle B2B enables:

• Business Document normalization (translation)

• Document, transport and exchange standards

• Security

• Trading Partner Management

The SOA Suite enables: 

• A Unified Business Process Platform

• End-to-End Instance Tracking, Visibility and Auditing

• Integrated Process Intelligence 

• Process and Service Governance

• Consolidated Security

Oracle B2B + SOA Suite enables all of the eCommerce requirements

*****************************************************

Oracle B2B helps exchange information between trading business partners using standard documents and protocols. This article explains how to get started with Oracle B2B in the context of SOA Suite 11g.

1. Create Document Guidelines: Document guidelines are used to translate and validate business documents. They consist of two different files. First, an ECS file to translate & validateflat files into XML. Second, an XSD schema file to validate XML documents. Using ECS guidelines, sample flat files can be generated that conform to the guidelines. We will need to use Oracle B2B Document Editor to generate guidelines. It needs to be installed separately from Oracle SOA Suite. Installation instruction can be found here. More from Oracle.
   
2. Create Document Definitions:  Document guidelines can be used to create document definitions through Oracle B2B console. This can be accessed usinghttp://<your_soa_server_host>:soa_server_port/b2bconsole. Using the Administration > Document tab of Oracle B2B, select from a list of document protocols, and then provide a document protocol version name, a document type name, and a document definition name. Read more from Oracle documentation. 
   
3. Configure Trading Partners: Trading partners represent the physical companies/organizations that participate in business transactions. A transaction involves a Host trading partner and a Remote trading partner. Oracle B2B is installed in Host trading partner systems. Remote trading partner participates in a business transaction with Host partner. Read more from Oracle’s documentation.
   
4. Create Agreements: A trading agreement is a business document exchange between a host and remote trading partner. This can be uni-directional or bi-directional. This is the final step designing a b2b transaction and requires all three steps described above. More from Oracledocumentation.
   

Oracle B2B Installation

Oracle B2B Installation:

Oracle B2B provides a platform to exchange standard messages between business entities. It comes with pre-built messaging templates and samples. It is part of Oracle SOA Suite. However, we need to separately download and install Oracle B2B Document editor. For traditional Oracle E-Business Suite users, this is similar to XML Gateway, but with more features geared towards SOA implementations.

Installation steps:

• Download Oracle B2B Document Editor from here. At the time of writing this article, installable came in three parts. Disk1 (File 1)  Disk1 (File 2)  Disk1 (File 3)

• Unzip all three zip files to their respective folders to create ofm_b2b_doc_editor_win_11.1.1.1.0_disk1_1of3, ofm_b2b_doc_editor_win_11.1.1.1.0_disk1_2of3, ofm_b2b_doc_editor_win_11.1.1.1.0_disk1_3of3.
• Copy contents of Standards directory from ofm_b2b_doc_editor_win_11.1.1.1.0_disk1_2of3, ofm_b2b_doc_editor_win_11.1.1.1.0_disk1_3of3 into ofm_b2b_doc_editor_win_11.1.1.1.0_disk1_1of3/Standards folder.
• Run ofm_b2b_doc_editor_win_11.1.1.1.0_disk1_1of3/Install.exe. Choose silent mode if you prefer so.

• Finally, installation confirmation screen will appear at the end of installation. I had about 51 folders under STANDARDS section of installation.

• Run from Programs.

• Access B2B console from /b2bconsole">http://<yourhost:yourport>/b2bconsole

Oracle Data Integrator(ODI) Concepts ..!!!

Qs> What is Oracle Data Integrator (ODI)?
Oracle acquired Sunopsis in 2006 and with it “Sunopsis Data Integrator”.

Oracle Data Integrator (ODI) is an E-LT (Extract, Load and Transform) tool used for high-speed data movement between disparate systems.

The latest version, Oracle Data Integrator Enterprise Edition (ODI-EE) brings together “Oracle Data Integrator” and “Oracle Warehouse Builder” as separate components of a single product with a single licence.

Qs> What is E-LT?

E-LT is an innovative approach to extracting, loading and Transforming data. Typically ETL application vendors have relied on costly heavyweight , mid-tier server to perform the transformations required when moving large volumes of data around the enterprise.

ODI delivers unique next-generation, Extract Load and Transform (E-LT) technology that improves performance and reduces data integration costs, even across heterogeneous systems by pushing the processing required down to the typically large and powerful database servers already in place within the enterprise.

Qs> What components make up Oracle Data Integrator?

“Oracle Data Integrator” comprises of:

- Oracle Data Integrator + Topology Manager + Designer + Operator + Agent
- Oracle Data Quality for Data Integrator
- Oracle Data Profiling

Qs> What is Oracle Data Integration Suite?
Oracle data integration suite is a set of data management applications for building, deploying, and managing enterprise data integration solutions:

Oracle Data Integrator Enterprise Edition

Oracle Data Relationship Management

Oracle Service Bus (limited use)

Oracle BPEL (limited use)

Oracle WebLogic Server (limited use)

Additional product options are:

Oracle Goldengate

Oracle Data Quality for Oracle Data Integrator (Trillium-based DQ)

Oracle Data Profiling (Trillium based Data Profiling)

ODSI (the former Aqualogic Data Services Platform)

Qs> What systems can ODI extract and load data into?
ODI brings true heterogeneous connectivity out-of-the-box, it can connect natively to Oracle, Sybase, MS SQL Server, MySQL, LDAP, DB2, PostgreSQL, Netezza.

It can also connect to any data source supporting JDBC, its possible even to use the Oracle BI Server as a data source using the jdbc driver that ships with BI Publisher

Qs> What are Knowledge Modules?

Knowledge Modules form the basis of ‘plug-ins’ that allow ODI to generate the relevant execution code , across technologies , to perform tasks in one of six areas, the six types of knowledge module consist of:

Reverse-engineering knowledge modules are used for reading the table and other object metadata from source databases

Journalizing knowledge modules record the new and changed data within either a single table or view or a consistent set of tables or views

Loading knowledge modules are used for efficient extraction of data from source databases for loading into a staging area (database-specific bulk unload utilities can be used where available)

Check knowledge modules are used for detecting errors in source data

Integration knowledge modules are used for efficiently transforming data from staging area to the target tables, generating the optimized native SQL for the given database

Service knowledge modules provide the ability to expose data as Web services

ODI ships with many knowledge modules out of the box, these are also extendable, they can modified within the ODI Designer module.

Qs> How do ‘Contexts’ work in ODI?

ODI offers a unique design approach through use of Contexts and Logical schemas. Imagine a development team, within the ODI Topology manager a senior developer can define the system architecture, connections, databases, data servers (tables etc) and so forth.

These objects are linked through contexts to ‘logical’ architecture objects that are then used by other developers to simply create interfaces using these logical objects, at run-time, on specification of a context within which to execute the interfaces, ODI will use the correct physical connections, databases + tables (source + target) linked the logical objects being used in those interfaces as defined within the environment Topology.

Qs> Does my ODI infrastructure require an Oracle database?
No, the ODI modular repositories (Master + and one of multiple Work repositories) can be installed on any database engine that supports ANSI ISO 89 syntax such as Oracle, Microsoft SQL Server, Sybase AS Enterprise, IBM DB2 UDB, IBM DB2/40.

Qs> Does ODI support web services?
Yes, ODI is ‘SOA’ enabled and its web services can be used in 3 ways:

The Oracle Data Integrator Public Web Service, that lets you execute a scenario (a published package) from a web service call

Data Services, which provide a web service over an ODI data store (i.e. a table, view or other data source registered in ODI)

The ODIInvokeWebService tool that you can add to a package to request a response from a web service

Qs> Is ODI Used by Oracle in their products?
Yes there are many Oracle products that utilise ODI, but here are just a few:

Oracle Application Integration Architecture (AIA)

Oracle Agile products

Oracle Hyperion Financial Management

Oracle Hyperion Planning

Oracle Fusion Governance, Risk & Compliance

Oracle Business Activity Monitoring

Oracle BI Applications also uses ODI as its core ETL tool in place of Informatica , but only for one release of OBIA and when using a certain source system.

ELT Vs ETL

•The ability to dynamically manage a staging area

•The ability to generate code on source and target systems alike, in the same transformation

•The ability to generate native SQL for any database on the market—most ETL tools will generate code for their own engines, and then translate that code for the databases—hence limiting their generation capacities to their ability to convert proprietary concepts

•The ability to generate DML and DDL, and to orchestrate sequences of operations on the heterogeneous systems

1.Explain what is ODI?why is it different from the other ETL tools.

ANS: ODI stands for Oracle Data Integrator. It is different from another ETL tool in a way that it uses E-LT approach as opposed to ETL approach. This approach eliminates the need of the exclusive Transformation Server between the Source and Target Data server. The power of the target data server can be used to transform the data. i.e. The target data server acts as staging area in addition to its role of target databasel. While loading the data in the target database (from staging area) the transformation logic is implemented. Also, the use of appropriate CKM (Check Knowldege Module) can be made while doing this to implement data quality requirement.

2.Explain about what you have done using ODI?

3.How will you bring in the different source data into ODI?

ANS:you will have to create dataservers in the topology manager for the different sources that you want.

4.How will you bulk load data?

ANS:In Odi there are IKM that are designed for bulk loading of data.

5.How will you install ODI?

ANS: http://subbus.blogspot.in/2014/03/oracle-data-integrator-odisunopsis.html 

6.How will you bring in files from remote locations?

ANS:We will invoke the Service knowledge module in ODI,this will help us to accesses data thought a web service.

7.How will you handle dataquality in ODI?

ANS:There are two ways of handling dataquality in Odi....the first method deals with handling the incorrect data using the CKM...the second method uses Oracle data quality tool(this is for advanced quality options)

8. what is load plans and types of load plans?
ANS) Load plan is a process to run or execute multiple scenarios as a Sequential or parallel or conditional based execution of your scenarios. And same we can call three types of load plans , Sequential, parallel and Condition based load plans. 
9. what is profile in odi?
ANS)  profile is a set of objective wise privileges. we can assign this profiles to the users. Users will get the privileges from profile. Please refer http://oditraining.blogspot.co.uk/2012/06/odi-security-manager-all-profiles.html


10 what is the odi console?
ANS) ODI console is a web based navigator to access the Designer, Operator and Topology components through browser. 

11.how to write the sub queries in odi?
ANS:)Using Yellow interface and sub queries option we can create sub queries in odi.
or Using  VIEW we can go for sub queries Or Using ODI Procedure we can call direct DB queries
in ODI.

12.suppose i having 6 interfaces and running the interface 3 rd one failed how to run remaining interfaces?
ANS: ) if you are running Sequential load it will stop the other interfaces. so goto operator and right click on filed interface and click on restart. If you are running all the interfaces are parallel only one interface will fail and other interfaces will finish. 

13. how to remove the duplicate in odi?
ANS) Use DISTINCT in IKM level. it will remove the duplicate rows while loading into target. 

14. suppose having unique and duplicate but i want to load unique record one table and duplicates one table?
ANS) Create two interfaces or once procedure and use two queries one for Unique values and one for duplicate values. 

15. how to write the procedures in odi?
ANS) Procedure is a step by step any technology code operations . you can refer