The Publisher object contains a filter and a set of rules. Some rules are defined as XSLT style sheets and some are simple XML rule documents. These rules and style sheets are necessary for converting data from the PeopleSoft CI into a DirXML XDS format. The driver then submits the data to the DirXML engine. The engine applies the Publisher filter to the data and applies the business logic defined by the Publisher rules prior to submitting the data to eDirectory.
The Publisher filter specifies the object classes and accompanying attributes that will be passed from the PeopleSoft CI to eDirectory. The filter is defined using eDirectory attribute naming, so it is applied after schema mapping takes place.
For example, if the User class is specified in the Publisher filter with only the Surname and Given Name attributes, the DirXML engine will allow changes to only these attributes to be passed to the Publisher rules from the PeopleSoft Driver. If a 'Telephone Number' attribute is modified, the Publisher filter will remove this data because the 'Telephone Number' attribute is not in the filter. It must be noted that other attribute values may be created by the Publisher rules according to the integration scenario.
You can configure the Publisher filter to include attributes required by your environment and allowable by eDirectory access controls. Configure it to include the following:
The Publisher filter specifies a set of data that will be considered as Authoritative from the PeopleSoft database. Based on business logic, there may be multiple authoritative sources of specific data (such as another DirXML driver or eDirectory itself). The configuration of the filters in your environment will determine data ownership and authority.
By default, PeopleSoft applications are considered to be highly authoritative. Therefore most of the field names in the default DIRXML_SCHEMA01 Component Interface will be passed through the Publisher filter. As noted earlier, the names of attributes in the filter are eDirectory attribute names that have been mapped via the Mapping rule.
The DIRXML_SCHEMA01 CI also defines a level-1 scroll element named PHONES. The PHONES scroll contains multiple elements, each of which contains two fields that identify telephone numbers and the type of the number. Since these elements cannot be directly mapped to eDirectory attributes they cannot be in the Mapping rule. However, with DirXML it is possible to create a style sheet that can convert the PHONES elements into single-valued eDirectory attributes. The eDirectory attributes can be listed in the filter to allow them to be passed to eDirectory. The Input Transformation rule of the Publisher channel performs this operation.
The attributes listed below are included in the default Publisher filter:
The homePhone, mobile, and pager attributes are also in the Subscriber filter. This implies that these attributes have dual authority or a peer-to-peer relationship between eDirectory and PeopleSoft.
PeopleSoft applications, as with many other applications, contain sensitive data that must be highly secured by organizations. There are two ways to ensure that secure data is not published from the PeopleSoft application:
The first method guarantees that the data will not leave the PeopleSoft application. The second method guarantees that it will not be synchronized to eDirectory via the DirXML driver.
A properly configured Publisher filter promotes a secure environment and secures data sharing from PeopleSoft to eDirectory. Make sure that attributes that are required fro Publisher rules processing are present in the filter even if they are not to be synchronized to eDirectory.
In ConsoleOne, right-click the driver.
Click Properties > DirXML Filter > Edit Filter.
Add and delete attributes as desired.
Click OK > Save.