Applications created via Multiplexing

Prior to identityIQ release 4.0p7, multiplex created application objects were unique, as they did not have a connector or featuresString set on the Application tag.

Example 1:  Non multiplexed created application

<Application
     connector="sailpoint.connector.JDBCConnector"
     featuresString="EXAMPLE"
     name="NotMultiPlexed"
     type="JDBC"
     ...
</Application>

Example 2:  Multiplexed created application

<Application
     name="NotMultiPlexed 2"
     type="JDBC"
     ...
</Application>

These multiplex created applications were never intended for use in aggregation, but instead were used to certify against.

Starting with identityIQ 4.0p7 and later, the default behavior was changed, via ETN 5714, in that mutiplex created applications will mirror the original application which created it.

For example, the mutiplex created application will have both connector and featureString attribute values.

If one wishes to go back to the pre 4.0p7 behavior, or desires to modify the application during the creation process, the following needs to be done:

1. Add the following xml to your multiplex application (in the Attributes Map):
   <entry key="proxyGeneratorRule" value="generateMultiplexApplicationsRule"/>
   (In this example, the name of our rule is generateMultiplexApplicationsRule)
2. Import the attached sample "generateMultiplexApplicationsRule" rule.
   Note: This sample rule creates an application with the same information as pre identityIQ 4.0p7. You may edit as needed.