A Target Group represents a software technology running in one or more Environments, that supports builds, deployments, test, or utility executions. Individual Target for build or deployment is represented by mapping of Target Group and Environment.
For example,
You may have an Oracle SOA Suite Instance (SOA1) for most composites, and a second Instance (SOA2) for hosting composites which contain sensitive information such as financial or HR related data. In this case, you would create two Target Groups in FlexDeploy named SOA1 and SOA2. You can define Name and Code for Instances.
You may have a requirement to perform builds using multiple versions of JDeveloper, such as JDeveloper 11.1.1.9 and JDeveloper 12.2.1. In which case you can create JDEV11119 and JDEV1221 Target Groups. Then you can associate each Target Group with one or more Environments, and describe which endpoints fit in each Target.
Example #1 Target Groups for ADF Build/Deploy
Target Group Code | Target Group Name | Notes |
|---|---|---|
ADF11119 | ADF 11.1.1.9 | ADF runtime 11.1.1.9 installation with WebLogic 10.3.6 |
ADF1221 | ADF 12.2.1 | ADF runtime 12.2.1 installation with WebLogic 12.2.1 |
JDEV11119 | JDeveloper 11.1.1.9 | JDeveloper 11.1.1.9 installation |
JDEV1221 | JDeveloper 12.2.1 | JDeveloper 12.2.1 installation |
Example #2 Target Groups for ADF Build/Deploy
This is simple variation from Example #1 above, where Build and Deploy Target Groups are named so that users can easily determine which to use for Build with Deploy.
Target Group Code | Target Group Name | Notes |
|---|---|---|
ADF11119 | ADF 11.1.1.9 | ADF runtime 11.1.1.9 installation with WebLogic 10.3.6 |
ADF1221 | ADF 12.2.1 | ADF runtime 12.2.1 installation with WebLogic 12.2.1 |
ADFBUILD11119 | ADF Build 11.1.1.9 | JDeveloper 11.1.1.9 installation |
ADFBUILD1221 | ADF Build 12.2.1 | JDeveloper 12.2.1 installation |
In example below, we have an ADF Domain installed in Development, QA and Production environments, they are 3 physical installations of WebLogic domain, but we can logically call it a since ADF Target Group in FlexDeploy topology. This allows us to perform deployments against a specific Target Group in a specific environment. For example, you can deploy a new version of EAR file to ADF in Development or ADF in QA etc. Similarly other technology installations like SOA, CRM application and Database are considered Target Groups in FlexDeploy topology.
Viewing Target Groups
To view the list of Target Groups defined within FlexDeploy, select Topology from the menu, and choose the Target Groups tab.
By default, all active Target Groups are displayed in the search results. To refine the search results, type all or part of the Target Group name into the Search box, and the list will automatically filter. Uncheck the Active checkbox to show the inactive Target Groups as well.
Creating or Editing Target Groups
To create a Target Group for either build or deploy click the plus button. To edit a Target Group, click on an existing Target Group row from the list.
Enter values for the following fields.
Field Name | Required | Description |
|---|---|---|
Target Group Id | N/A | System generated identifier (read-only). |
Target Group Code | Yes | Short name for the Target Group. |
Target Group Name | Yes | Long display name for the Target Group. |
Group | No | An optional group identifier which can be useful when searching for Target Groups. |
SubGroup | No | An optional subgroup identifier which can be useful when searching for Target Groups. |
Description | No | A description of the Target Group. |
Deployment Target | Yes | Whether the Target Groupcan be deployed to. Defaults to "Yes". |
Active | Yes | Whether or not the Target Group is active in the system. Defaults to "Yes". |
Click the next tab to associate Environments to this Target Group.
Click and drag environments from the list in the right pane to the main pane to associate them to this Target Group. To disassociate environments from the Target Group, drag them back from the main pane to the list on the right. If you already associated the Target Group to one or more environments using the Environment Wizard you will notice that the association is already created.
Click the next tab for associating workflows to this Target Group. By associating workflows to the Target Group, you are indicating that any user-defined workflow properties need to be configured for this Target Group across all selected environments (for Target-scoped properties) or all referencing projects (for project-scoped properties). See the Workflows chapter for details on creating workflow properties.
Click and drag workflows from the list in the right pane to the main pane to associate them to this Target Group. To disassociate workflows from the Target Group, drag the workflow back to the list on the right.
Click the next tab to associate plugin operations to this Target Group. By associating plugin operations to the Target Group, you are indicating that any environment Target Group scoped properties defined for those plugin operations need to be configured for the Target Group across all selected environments. Likewise, any projects which reference the Target Group must define any associated project-scoped properties. In order to find specific plugin operations, type in Filter... text box and available Plugin Operations will be filtered accordingly.
Click and drag plugin operations from the list in the right pane to the main pane to associate them to this Target Group. To disassociate plugin operations from the Target Group, drag the plugin operation back to the list on the right. Associated plugins give properties to the Target Group which are then configured on the Topology Overview page.
Click the Save button to save the changes to the Target Group and return to the list of Target Groups. Optionally click the Apply button to save the changes, but remain on the current screen until the Cancel button is clicked.
Inactivating/Activating Target Groups
To inactivate an Target Group at any time, click the Active link on the desired Target Group, and it will toggle to Inactive. This will hide that Target Group after leaving the screen, until the Active checkbox is unchecked. To reactivate a Target Group, click the Inactive link and it will toggle back to Active.
Post-Refresh
Post Refresh Request enables a Target Group in an environment to be refreshed to its original state after that Target Group has been cloned from another environment.