Creating a Dynamic Object Group

A dynamic object group is created at runtime based on a search criteria.

1. Navigate to <TIBCO_HOME>/pd/<version>/samples/common and open the appropriate data file.
2. Under the element <tog:DynamicObjectGroup>, provide values for the following elements: Name, Description, Domain, and Type.

   <description>Dynamic Object Group with DAA3 WebApp Component created via CLI</description>
   <name>DAA3 BasicAuth WebAppComponentInst DynamicObjectGroupViaCLI</name>
   <domain localPart="tibco.amx3" 
   namespace="http://tns.tibco.com/governance/common/govdomain/tibco/amx3"/> 
   <type localPart="WebAppComponentInstance" 
   namespace="http://tns.tibco.com/governance/common/govdomain/tibco/amx3"/> 

   The domain is either AMX or BW. Based on the domain, provide one of the following values for the attributes: localPart and namespace in the <domain> element.

   For AMX, the localPart attribute should be tibco.amx3 and the namespace attribute should be http://tns.tibco.com/governance/common/govdomain/tibco/amx3. For BW, the localPart attribute should be tibco.bw5 and the namespace attribute should be http://tns.tibco.com/governance/common/govdomain/tibco/bw5.

   Based on the domain selected, provide one of the following values for the attribute, localPart, in the <type> element.

   Domain	Values accepted by the localPart attribute in the <type> element
   AMX	SoapHttpReferenceBindingInstance, SoapHttpServiceBindingInstance, SoapJmsReferenceBindingInstance, SoapJmsServiceBindingInstance, SoapReferenceBindingInstance, SoapServiceBindingInstance, VirtualizationReferenceBindingInstance, VirtualizationServiceBindingInstance, WebAppComponentInstance
   BW	BWServiceEndpoint, BWSoapHttpServiceEndpoint, BWSoapJmsServiceEndpoint, BWReferenceEndpoint, BWSoapHttpReferenceEndpoint, BWSoapJmsReferenceEndpoint

3. Define the search criteria by creating the appropriate expressions. To learn more about building search criteria, see Defining the Search Criteria for Object Groups .
4. Add appropriate targets in the build file.
5. Run the ant command to apply the changes.

<?xml version="1.0" encoding="UTF-8"?>
<amxdata_base:Enterprise 
xsi:schemaLocation="http://tibco.com/amxadministrator/command/line
/types_base ../../../administrator/3.2/schemas/amxdata_base.xsd 
http://tibco.com/governance/ogp/cli/types_tog ../schemas/tog.xsd" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:amxdata_base="http://tibco.com/amxadministrator/command/line/types_base" 
xmlns:tog="http://tibco.com/governance/ogp/cli/types_tog"> 
<tog:DynamicObjectGroup> 
<description>Dynamic Object Group with DAA3 WebApp Component created via CLI</description>
<name>DAA3 BasicAuth WebAppComponentInst DynamicObjectGroupViaCLI</name>
<domain localPart="tibco.amx3" 
namespace="http://tns.tibco.com/governance/common/govdomain/tibco/amx3"/> 
<type localPart="WebAppComponentInstance" 
namespace="http://tns.tibco.com/governance/common/govdomain/tibco/amx3"/> 
<BaseEnvironment> 
		<name>DevEnvironment</name> 
</BaseEnvironment> 
<Expressions> 
	<Expression> 
		<Statements> 
			<Statement> 
    <type localPart="Application"
     namespace="http://tns.tibco.com/governance/common/govdomain/tibco/amx3"/> 
				<property localPart="name" namespace=""/> 
				<operator>contains</operator> 
				<operand1>DAA3</operand1> 
			</Statement> 
		</Statements> 
	</Expression> 
</Expressions> 
</tog:DynamicObjectGroup> 
<tog:SyncObjectGroupMembers/> 
<tog:ExportObjectGroups> 
		<outputDataFile>${exported.data.file}</outputDataFile> 
</tog:ExportObjectGroups> 
</amxdata_base:Enterprise>