Page Comparison

...

The Development environment is both the build environment and the single target environment mapped to for deployment.
The build instance instance is also used for deployment.
The build workflow, Build SOA Composite, is created/linked and bound to all composite projects.
The deploy workflow, Deploy SOA Composite, is created once and bound to all composite projects created through a blueprint.
The instance is created based on the SOA verison.
- One instance, SOA 11g, is created and shared by all 11g composites created through a blueprint.
- One instance, SOA 12c, is created and shared by all 12c composites created through a blueprint.

Blueprint Properties

Image Added

Property Name	Required	Description	How its used
Composite Name	Yes	The name of the SOA Composite, as defined in composite.xml	FlexDeploy project is named using this value FlexDeploy project property is configured to this value
SOA Partition	Yes	The name of the SOA partition the composite deploys to	FlexDeploy project property is configured to this value
JDeveloper .jws Name	Yes	The base name of the JDeveloper .jws file (without extension)	FlexDeploy application is named using this value
SOA Version	Yes	Whether the Composite is for Oracle SOA 11g or 12c	FlexDeploy instance is created using this value FlexDeploy project is mapped to the instance
Composite Description	No	A description for the SOA Composite	FlexDeploy project's description is set to this value

All SOA Composites are built using FlexDeploy's Oracle SOA Plugin. As such, the only and default build option is Build SOA.

There are no Build Properties for this blueprint.

A single Development endpoint is created and linked to all SOA Composite projects for each instance (11g/12c).