What are Target Groups?

A Target Group represents a software technology running in one or more Environments, that supports builds, deployments, test, or utility executions. A Target is the combination of a 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 Target Groups.

• 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

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.

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.

Open

Viewing Target Groups

To view the list of Target Groups defined within FlexDeploy, select Topology from the menu.

By default, all active Target Groups are displayed in the search results.

Open

To refine the search results, type all or part of the Target Group name into the Search box, and the list will automatically filter. Click the filter inactive button to show the inactive Target Groups as well.

Creating and Editing Target Groups

To create a Target Group, click the  button in the top right. To edit a Target Group, right click a Target Group row or click on the … at the end of a row in the list, and select Edit.

Enter values for the following fields.

Left click the row to see the Environments associated to this Target Group and get to the properties and endpoints of each.

Click the Environments drop down to add an additional Environment to the Target Group. To disassociate environments from the Target Group, click the X on the right.

Target Group Properties

Before version 6.5, an additional step to associate Workflows and Plugin operations was necessary to connect available properties to targets. This is automated in version 6.5 and we don’t expect users to ever need to link them manually. If you find a need to link them manually, see Manually Assigning Target Group Workflows and Plugins.

All changes on this screen take effect immediately.

Target Group Tags

To add Tag to the Target Groups , right click on a row or click on the three dots that we are seeing on right side of the particular target group row.

After clicking on the Add Tag option, then you can see a list of already created tags , by clicking on a tag from the list of tags such tag will be assigned to selected Target. To create a new tag, type the name in the Search Tags field and a create option will show up if a tag with that name does not exist.

To Manage the Tags you can navigate to Tags from the menu and manage the Tags Tags | Managing Tags .

Inactivating, Activating and Deleting Target Groups

To inactivate a Target Group at any time, click the Active button 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 button and it will toggle back to Active. Only Target Groups that aren’t in use can be inactivated or deleted.