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.

Oracle B2B-EDI

EDI (Electronic Data Interchange)

EDI Standards:-

EDI – Electronic Data Interchange is a structured Document standard and is one of the most widely used standards in Business-to-Business communication.

Generally speaking, EDI is considered to be a technical representation of a business conversation between two entities, either internal or external. Data interchange between two Trading partners.

   EDI is nothing but electronic document which follows some standards based on the organization requirement.

EDI we have two types of standards:

1.     Private or within the Organization (internal).

2.     All organization (external).

        The UN-recommended UN/EDIFACT is the only international standard and is predominant outside of North America. The US standard ANSI ASC X12 (X12) is predominant in North America.

The EDI standards prescribe the formats, character sets, and data elements, segments used in the exchange of business documents and forms.

The complete X12 Document List includes all major business documents, including purchase orders (called "ORDERS" in UN/EDIFACT and an "850" in X12) and invoices (called "INVOIC" in UN/EDIFACT and an "810" in X12).

American National Standards Institute (ANSI) chartered the Accredited Standards Committee (ASC) X12 to develop standards for electronic interchange.

**ASC                                       Accredited Standards Committee.

**EDI                                       Electronic Data Interchange. 

**EDIFACT                             Electronic Data Interchange For

                                                 Administration, Commerce and Transport

EDI Standards Support:-

Encoding Standard	Industry Segment
UN/EDIFACT	General Industry
X12	General Industry
EANCOM	Retail
HIPAA X12N	Health Care

HIPPA (Health Insurance Portability and Accountability Act)

HIPPA is introduced in 1996, US Congress. There are following Transaction thought EDI X12(standard).

EDI Transaction are:

Version                                 Key EDI               Description

X12 4010/5010                 837                       Medical Claims

                                                820                         Group Premium Payment for  

                                                                               Insurance.       

                                                834                       Benefits enrollment and           

                                                                               Maintenance.

                                                835                       Electronic remittance.

                                                270/271             Eligibility inquiry and  

                                                                               response.

                                                276/277             Claim status inquiry and

                                                                               response.

                                                278                       Health Services Review request  

                                                                               and reply.  

All the basic standard EDI X12 (ASC Standard) rules listed in this document apply to the HIPAA as well because HIPAA are EDI X12 transactions.

Oracle B2B Document Editor:-

       Oracle B2B - Document Editor is an integrated guideline creation and implementation application for business-to-business (B2B) electronic commerce (e-commerce). Use the Document Editor to simplify developing, migrating, testing, distributing, and printing your electronic business (e-business) guideline documents. You can create new guideline documents or use the Document Editor's comprehensive library of Standards as templates.

Correlation Set in SOA 11g

Correlation sets are typically used when you need to contact with an already running BPEL instance.