Examples of Data Integrators
After you install the data integration suite, you can access two data integrators that we have developed:
The following sections describe each of these data integrators. You can also examine the following files to see how these data integrators were developed.
- Property files in /opt/UMC/datint/etc
- XSLT files in /opt/UMC/datint/xslt
- The script vpndatamgt in /opt/UMC/datint/etc, which calls both these data integrators
Example: VPN Directory Updater
VPN Directory Updater is a sample data integrator that reads data about VPNs from a database and writes to a directory the data in a format that meets the SDX LDAP schema. If you want to use VPN Directory Updater, you must customize it for your specific application. At the very least, you need to customize the SQL queries for your database.
VPN Directory Updater works as follows:
- Database Reader submits SQL queries to a database, obtains the result of the query, and converts the result to an XML document.
- XSLT Translator takes the XML document produced by Database Reader and converts it to an XML document that describes a set of directory updates.
- LDAP Writer uses the XML document generated by XSLT Translator to update the directory.
Figure 13 illustrates this process.
![]()
Example: VPN Subscription Deactivator
If an IT manager cancels the export of a VPN at the same time that an extranet client activates a subscription to this VPN, there is a remote possibility that the Enterprise Manager portal will maintain the active, but invalid, subscription. VPN Subscription Deactivator deactivates this type of invalid VPN subscription.
You can use VPN Subscription Deactivator without modifications. For information about using this data integrator, see SRC-PE Subscribers and Subscriptions Guide, Chapter 24, Adding VPNs from JUNOS Routing Platforms.
VPN Subscription Deactivator works as follows:
- Enterprise Audit File Reader finds events of type unexport-vpn in the log for the Enterprise Audit Plug-In and converts the events to an XML document.
- The XSLT Translator tovpnsubquery performs the following actions:
- Reads the XML document from the Enterprise Audit File Reader and uses it to identify extranet clients for whom export of a VPN was canceled.
- Uses the XSLT file tovpnsubquery.xslt to generate LDAP queries to obtain subscriptions, imported extranets, and VPNs owned for these extranet clients.
- Writes the queries to an XML document.
- Reads the XML document from the XSLT Translator tovpnsubquery.
- Submits the queries to the directory.
- Obtains the results of the queries from the directory.
- Writes the results to an XML document.
- Reads the XML document from the LDAP Reader.
- Uses the XSLT file chkghostvpnsub.xslt to find in the XML document VPN subscriptions that are still active even though the export of the VPN has been canceled.
- Generates an XML document that contains LDAP updates to deactivate the invalid subscriptions.
- LDAP Writer uses the XML documents generated by Enterprise Audit File Reader and LDAP Reader to update the directory.
Figure 14 illustrates this process.
![]()