Prerequisites before SOA Development

Creation of JMS Queue
Queue: Defines a point-to-point destination type, which are used for asynchronous peer communications. A message delivered to a queue is distributed to only one consumer.

Click SOAJMSModule.

In the Summary of Resources table, click New. Select the resource type: Queue and click Next.

Enter name: demoFulfillmentQueue and JNDI name: jms/demoFulfillmentQueue

Select Subdeployment SOASubDeployment. Select JMS Server SOAJMSServer

Creation of Connection Factory
Connection Factory: Defines a set of connection configuration parameters that are used to create connections for JMS clients.

Select the resource type: Connection Factory and click Next
Enter name: demoCF and JNDI name: jms/demoCF.

You should see both the queue and the connection factory listed in the Summary of Resources as shown here.

Now add the connection pool. The connection pool is configured in the JMSAdapter application and uses a Deployment Plan. First, create a directory to contain that plan.

Create a directory JMSPlan: C:\Oracle\Oracle_SOA1\soa\JMSPlan

Click Deployments. Click JMS Adapter. Click the Configuration tab and then the Outbound Connection Pools tab.

Click New. Select the factory oracle.tip.adapter.jms.IJmsConnectionFactory. Click Next. Enter eis/Queue/demo.

Click on eis/Queue/demo. Change the property ConnectionFactoryLocation to value jms/demoCF. Now update the JMSAdapter adapter.

=====================================================================

Create a data source with name as soademoDatabase, and JNDI Name as jdbc/soademoDatabase

Create a directory DBPlan: C:\Oracle\Oracle_SOA1\soa\DBPlan

Click Deployments. Click DbAdapter. Click the Configuration tab and then the Outbound Connection Pools tab.

Enter the JNDI Name as follows: eis/DB/soademoDatabase

Edit the connection pool to reference the data source. You have created a connection pool.

SOA Glossary

Service Component Architecture (SCA)
Service Component Architecture (SCA) is a set of specifications that describe a model for building applications using a service-oriented architecture.
1. Services are assembled together to form a composite application that creates a solution that addresses a specific business requirement.
2. Composite applications may contain new services (specifically for the application) and business functions from existing systems and applications (reused in the composite application).


SOA Composite
A SOA composite is an assembly of services, service components, and references designed and deployed together in a single application. Wiring between the service, service component, and reference enables message communication.

1. Services provide the outside world with an entry point to the SOA composite application. The service advertises its capabilities (also known as operations) to external applications with a WSDL (Web Services Description Language) file. The binding of the service describes the protocols that can communicate with the application. Examples include SOAP/HTTP or a JCA adapter.
2. Service components are the building blocks of a SOA composite application. Oracle SOA Suite 11g includes the following components:
   - The BPEL Process component enables design and execution of a business process that integrates a series of business activities and services into an end-to-end process flow.
   - The Business Rules component provides the means of making business decisions based on defined rules.
   - The Human Task component allows you to model a workflow that describes tasks for users or groups to perform as part of an end-to-end business process flow.
   - The Mediator component is used for validation, filtering, transformation, and routing of message data between components.
3. References enable messages to be sent from the SOA composite application to external services in the outside world.

Service Data Object (SDO)

An SDO exposes any data source as a service, which enables retrieval and manipulation of the data in an XML format through service operations. The task of connecting applications to data sources is performed by a data mediator service.
Oracle SOA Suite 11g enables a BPEL Process to access an SDO through an Entity Variable, a special type of BPEL variable associated with a SDO as a service. Oracle ADF-BC components can be deployed simultaneously as Web Service and an SDO.


WSIL (Web Services Inspection Language) Connection
The http://localhost:8001/inspection.wsil URL accesses a Java EE application that dynamically discovers WSDL URL endpoints for Java EE and SOA composite applications deployed to the same run-time server.


Adapters
Adapters provide a service interface that:
• Exposes external application functionality in a form that can be used by SOA composite application components
• Converts request and responses into a form suitable for other (external) systems
• Implements interfaces by using the Java Connector Architecture (JCA) API standards

Oracle Web Service Manager Policy Manager Policy Manager

Oracle WSM  Policy Manager provides the infrastructure for enforcing global security and auditing policies in the service infrastructure. By securing various endpoints and setting and propagating identity, it secures applications. Oracle WSM Policy Manager provides a standard mechanism for signing messages, performing encryption, performing authentication, and providing role-based access control.

The Oracle Metadata Repository

The Oracle SOA Suite 11g runtime environment requires MDS to maintain SOA application configuration and runtime information. It is used to manage deployed services and composite applications.
The MDS can also be used as a central location for storing and referencing shared service artifacts, such as business events, rule sets for Oracle Business Rules, XSLT files for Oracle Mediator, XSD and WSDL documents for Oracle BPEL Process Manager, and other service documents, which can be deployed in a sharable archive format known as the Metadata archive (.mar files).


Business Events and the Event Delivery Network

A business event is a way for one application to notify another application of a significant occurrence to the business. When a business event is published, another application (or service component) can subscribe to it and initiate whatever processing is implied by that event. For example, when product stock levels are updated in an inventory database, an event can serve as a trigger or signal for another process to fulfill orders that have been on hold until products become available.
Business events are typically an asynchronous fire-and-forget (one-way) notification of a business occurrence.
Events are defined by using Event Definition Language (EDL) to specify the name and structure of an event. Definitions for business events are stored in the MDS, and published in the Event Delivery Network (EDN).
The Event Delivery Network is designed to handle asynchronous messaging arising from a business or system event. The EDN is not messaging infrastructure. It provides an application with a declarative publish-subscribe implementation to publish events so that a composite application with a Mediator component can subscribe to events that trigger execution of the composite application.

Web Services Description Language (WSDL)

• Types define the data types used in messages. These types are often drawn from the XML Schema Language.
• Messages describe the part(s) of the input, output, and fault messages exchanged with the calling program.
• Operations provide a name for the action performed on messages.
• PortTypes group message(s) with operation(s).

Those WSDL documents for services deployed outside the WebLogic Server will include the concrete elements of the WSDL, which provide additional information about how and where to access the service:
• The binding describes how a given portType operation will be transmitted, such as HTTP or SOAP (that is, the protocol) and information about where the service is located.
• The port specifies a combination of a network address and a binding, which constitute an endpoint.
• A service groups ports together. A service reveals to a calling program where to access the web service, and through which port. It also describes how the communication messages are defined.

Section 1 includes an import statement and a reference to file po.xsd.
Section 2 describes message requestMessage. The description includes the name of the part, and the name of the element that describes the message structure of that part. Message element PurchaseOrder is fully described in the imported po.xsd document.
Finally, section 3 describes port type execute_ptt, which groups a specific operation (execute) with message requestMessage.

The number and order of messages in the portType definition of a WSDL is important. Because we see only a single message listed in the example above, we know that operation execute is a one-way operation. If we saw a second message like in the example below, we could assume that the operation returned a response upon completion.

SOA Demo Community Seeding Utility

1. Download workflow-001-DemoCommunitySeedApp.zip from the link below:
https://java.net/projects/oraclesoasuite11g/downloads/directory/HumanWorkflow

2. Extract it. Deploy the “SOATestDemoApp.ear” file in the Weblogic server console. Choose Admin and SOA_SERVER1 servers as targets. Restart the Weblogic Admin and SOA_SERVER1 servers.

3. Access the deployed application using

http://localhost:8001/integration/SOADemoCommunity/DemoCommunitySeedServlet

4. Click "Submit" button to create the sample Users and Groups in Weblogic Server.