Reference architecture documents can be used online to educate others. Using an in-house web service, wiki or portal that places the input part in the blueprint architecture.
A reference architecture is a set of predefined architectural patterns. While designed for use in specific technical and commercial contexts, they all come with supporting documentation that makes their use practical. These documents can be derived from architectural documents, standards and rules. While for SOA it will be useful to connect them properly.
Reference architecture in one or more projects as a Blueprint Will be used. In this way, architects and programmers can monitor the execution of events, whether that event is in line with the creation guidelines and brings us closer to business goals or not?
Reference architecture goals
Reference architecture in the following ways can you ensure that the efforts have been successful architecture:
to act as a final product architecture ( blueprint )
reference architecture can infrastructure within IT , codes and models in general. Because these different codes and models are created with different teams, they may act in isolation, which can be problematic for the organization.
Blueprint allows the architecture to take a bigger look at SOA, and this overview is needed to ensure service quality steps.

SOA reference architecture should join other architectural documentation of existing organizations, such as network and IT hardware, and add service layers to the idea.
For example, if the SOA reference architecture is defined with ORACLE / BEA, it includes the following layers:
Connection services and data services: Flexible access to other core data and applications of the organization.
Business-based services: A logical layer on top of the data services layer where business processes are managed.
Display Services: A package of powerful services in business, usable for various channels.
When ORACLE / BEA Do not define (in which case the connection or display services may be deleted or even a new layer may be added), it is better to understand the service at this stage rather than at the existence, process or function stage.

• Create successful examples

By RA , services and clients are created and used following certain guidelines. For example, acceptable methods for building a service, message transfer, encryption, etc. may be desired.
By announcing guidelines, standards, and contracts, the reference architecture during the implementation assures everyone and everywhere in the organization that the work is being done properly. In this way, the work of programmers and architects will be easier, and when everyone is ready to run the service in the prescribed manner, the time of supply to the market will accelerate.
The reference architecture should state how to solve reciprocal problems such as Rules Engins and security (sometimes even the engines themselves run as a service).
Trade-offs Clarify (weigh)
Not everything can be done because certain needs always appear in opposition to each other. As high performance with high security remains a constant conflict.

• Enabling sovereignty

The dominance of SOA is strongly dependent on the construction of the reference architecture. Reference architecture is used as the basis for SOA COE or Governance board to follow .
Location of reference architecture
The SOA reference architecture can be portable and a collection of resources (which can be used for a variety of purposes) rather than just documentation bundled with code. And a portable service will work properly when running a web service Easily updated (like wiki). Members of the service-oriented architecture team, board, or architects working in an organization are responsible for building a site for training and information, including architectural models, standards, sources, and contract documentation.