What is SOA (Service Oriented Architecture)

SOA is a loosely coupled component. Because of the loose coupling of Web Services are optimal for reuse.
The benefits of loose coupling include location transparency, protocol independence, and time independence. SOA is a set of rules and specifications SOA is a set of messages

How can you achieve loose coupling in a soa?

One strategy for achieving loose coupling is to use the service interface (the WSDL for a SOAP Web Service) to limit this dependency, hiding the service implementation from the consumer. Loose coupling can be addressed by encapsulating the service functionalities in a manner that limits the impact of changes to the implementation on the service interface. However, at some point you will need to change the interface and manage versioning without impacting service consumers, in addition to managing multiple security constraints, multiple transports, and other considerations.

Orchestration (computing):
Orchestration describes the automated arrangement, coordination, and management of complex computer systems, middleware, and services.

Orchestration versus Choreography
In orchestration, the involved web services are under control of a single endpoint central process (another web service). This process coordinates the execution of different operations on the Web services participating in the process. The invoked Web services neither know and nor need to know that they are involved in a composition process and that they are playing a role in a business process definition. Only the central process (coordinator of the orchestration) is conscious of this aim, thus, the orchestration is centralized through explicit definitions of operations and the invocation order of Web services

Choreography, in contrast, does not depend on a central orchestrator. Each Web service that participates in the choreography has to know exactly when to become active and with whom to interoperate. Choreography is based on collaboration and is mainly used to exchange messages in public business processes. All Web services which take part in the choreography must be conscious of the business process, operations to execute, messages to exchange as well as the timing of message exchanges,

Blocks of SOA? Or SCA Components (Service Component Architecture)?

BPEL Processes, Business Rule, Human Task, Mediator

Daily Activities:
• New enhancements in XSLT and XSDs
• Adding new adapters for new Organizations
• Monitoring Bpel consoles
• Calling Services from different applications through WSDL
• Involved in CR's (Change Request’s).
• Prepare Weekly Status Report and send it to my manager

XML: Extensible Mark up Language is a simple very flexible text format that defines the format and structure of message passing through the services.
There should be route element.
No. of attribute can be defined.
XML has one document element it should have one route element on the top of the route element we will have directories. It should end with " ?” (Question mark).
Ex:

SAX and DOM:

1. SAX is a serial access parser API for dynamic web pages; DOM is a convention without a language or a dependency on language.
2. A SAX parser allows the user to control the number of callback methods; DOM functions independently in order to allow JavaScript scripts to access, change, or analyze anything pertaining to dynamic web pages, allowing the JavaScript to ‘physically’ explore its environment.

XML and XSD:

1. XSD is based and written on XML.
2. XSD defines elements and structures that can appear in the document, while XML does not.
3. XSD ensures that the data is properly interpreted, while XML does not.
4. An XSD document is validated as XML, but the opposite may not always be true.
5. XSD is better at catching errors than XML.