Oracle Code Compliance Inspector

The Code Compliance Inspector uses a pre-defined set of assertions that are based on SOA AIA Integration Developer guidelines and the Web Services Interoperability Organization Basic Profile (WS-I BP) to check SOA projects for design consistency and good coding and documentation practices. CCI qualifies code as Compliant, Conformant, or Fully Conformant to be in sync The Open Group Architecture Framework (TOGAF) standard guidelines based on the pass criteria of the highest priority assertions.

• CCI is available as a JDeveloper extension
• As a command-line utility
• Oracle Enterprise Repository (OER) utility

Developers will typically use the JDeveloper extension and will continuously check compliance on JDeveloper projects as they develop.

The CCI command line utility can be used to incorporate CCI code check as part of our build/deployment/continuous integration process. So every time someone checks code into main branch, the Continuous Integration tool can automatically checkout the code, do a CCI code compliance test and then build and deploy. Of course if the code is not compliant it can send an error notification to a distribution list, without deploying.
Here are some examples for invoking the Code Compliance Inspector from a command line:

• Windows: checkCompliance.bat -inputDir D:\AIA\demo -outputDir D:\ComplianceOut
• Linux: sh checkCompliance.sh -inputDir /AIA/demo -outputDir /ComplianceOut

CCI provides optional integration to Oracle Enterprise Repository (OER). When OER is present, CCI can synchronize results to the repository, enabling users to access the report from the OER console. Integrating compliance data into OER provides repository users with information about whether composites are compliant into the repository reports and individual asset metadata.

To make it working in JDEV11 is quite easy, just download and install the extensions in JDeveloper

Then right-click the project and select Check Code Compliance.

Note: when the project is selected, the code compliance inspector can also be launched
from the toolbar.

A highlighted Compliance Results tab will appear in the log panel, go ahead and select it
to see the project status

In this environment, we are simply checking compliance against WS-I standards, but there are also other standards delivered with Oracle Application Integration Architecture Foundation Pack that can check much more as well as additional checks that can be added by your team

Oracle SOA 12c Templates

SOA Composite Templates

One of the best new feature in this SOA 12.1.3 release is this about the Template.
The SOA template can really increase the productivity of the Developers team and Oracle is right saying this..
Here I just want to recap the different type of template and main features, across  SOA and OSB, hope this might help.

SOA ‘Starter’ Templates

• ‘Starter’ Template is a re-usable part of a SOA project
• Fully editable
• Store in MDS
• Three types:
• SOA Project Template
• Component Template
• Custom Activity Template

• Project template accessible at the time of new project creation
• Automatically discover in the component palette
• Component Template
• Custom Activity Template
• Share and re-use from MDS

BPEL Sub-processes: standalone and inline

Very useful for groups of activities that are reused within one (inline) BPEL process or the whole Composite (standalone).

• Allows business logic to be modularized and reused
• Permits access of data in parent process
• Improves performance and manageability
• Compensation and fault handling inherited from calling process
• Faster rendering as only the entity in question is rendered

The main difference between Standalone and Inline sub processes is that the firsts are visible within the Composite the seconds only within the Bpel Process in which it's been generated.

Service Bus Templates

Pipeline ‘Inherited’ Templates

• New artifact type.
• Two ways to create a Template
• Generate template from existing pipeline
• Create template from scratch.
• New pipelines are generated from the Template.
• Derived pipelines are considered concrete
• Concrete pipelines can be linked (default) or unlinked
• If linked, all changes in Template are reflected in derived concretes
• Templates actions can be ‘Locked’

• Placeholders in Pipeline template to define where modifications may be placed

Share artifacts within and across applications

SOA Design-Time MDS Repository

• Wizard to share design time artifacts such as WSDLs and Schemas
• Moves the artifacts and its dependencies to Design-Time MDS (viz. schema with WSDL)
• Updates all the references to the transferred artifacts with MDS URLs on transfer