...
| Info |
|---|
GIT was chosen as the Source Code Management tool for this tutorial, however, FlexDeploy supports many other Source Code Management tools and any one can be used in place of GIT. |
Configure the SOA soaBuild operation by adding it to the center pane and the plugin will open for additional configuration. Once again, the soaBuild operation requires no additional configuration. The soaBuild operation knows where the composite was cloned, so the developer doesn't have to worry about the details. At the successful completion of the soaBuild operation, a SAR file will be generated as an artifact and will automatically be pulled back to the artifact repository. Select OK..
The plugins are intelligent and eliminate as much development work as possible from the developers. Once the components are added, the workflow needs to be saved and/or activated. Saving the workflow changes will only save the current configuration to the database and is used when the developer may not be quite ready to activate these changes. When the developer wants the changes to be executed by projects, the Activate button must be selected. Once the current version of the workflow is activated, the workflow will be marked as read-only and have a green check mark next to it. Active versions can't be modified and require the developer to select Make Copy. This will create a new version and open that version up for editing, while the active version will not be changed.
...
Configure the SOA soaDeploy operation by adding it to the center pane and the plugin will open for additional configuration. Any composite that contains a URL based partnerLink, such as one composite calling another composite, must have the host name modified to point at the deployed environment. A config plan will be configured on the soaDeploy operation that will provide the host name translation. For the tutorial, three configuration plans have been created and saved with the composite project, one for each environment that will be created so the host names can be translation appropriately across environments. On the soaDeploy operation, we have configured the Deploy Config Plan input. The first thing to do is change the input from a text box to a Groovy script enabled script box by clicking on the red T 
text icon next to the input and the icon will change to a 
function icon. Now we can utilize a Groovy script to keep this work generic and re-usable across all composites. The following script will maintain that re-usability but utilizing predefined FlexDeploy variables:
...
The soaDeploy operation will automatically have the artifact generated by the build workflow available. Select OK and activate the workflow.
| Completed 2 of 10 Sections | Continue to End Point Creation | Back to Login |
|---|
...