|
Publishing Framework
Examples of Generated EventsExample 1: Explicitly Generated EventIn the following example, a company's sales information is reported in an explicitly generated event. <sas-event:Event xmlns:sas-event= "http://support.sas.com/xml/namespace/services.events-1.1" sas-event:name="event1"> <sas-event:Header> <sas-event:Version>1.0</sas-event:Version> <sas-event:Identity> 7FBBA000-32C4-11D6-8001-363139363230 </sas-event:Identity> <sas-event:Response type="result"/> <sas-event:Properties> <Company>Alphalite Airways</Company> </sas-event:Properties> </sas-event:Header> <sas-event:Body> <Company name="Alphalite Airways"> <Sales region="South"> <Projection>1000000</Projection> <Actual>1000050</Actual> </Sales> <Sales region="West"> <Projection>750000</Projection> <Actual>685000</Actual> </Sales> <Sales region="North"> <Projection>500000</Projection> <Actual>600000</Actual> </Sales> <Sales region="East"> <Projection>1000000</Projection> <Actual>950000</Actual> </Sales> </Company> </sas-event:Body> </sas-event:Event> Example 2: Implicitly Published EventIn the following example, the published package contains an external file and a reference. Because the package is published to a WebDAV server, the sas-publish:packageUrl attribute is specified. This attribute is a URL to an archived package. The package was published with a name/value specification of "report=revenue department=research".
<?xml version="1.0" encoding="UTF-8"?> <sas-event:Event xmlns:sas-event= "http://support.sas.com/xml/namespace/services.events-1.1" sas-event:name='SASPackage.AirlineChannel'> <sas-event:Header> <sas-event:Version>1.0<sas-event:Version> <sas-event:SentAt>26SEP2001:19:15:37</sas-event:SentAt> <sas-event:Header> <sas-event:Body> <sas-publish:Package xmlns:sas-publish= "http://support.sas.com/xml/ namespace/services.publish-1.1" sas-publish:version="1.0" sas-publish:description="Revenue Info" sas-publish:channel="Revenue Channel" sas-publish:packageUrl= "http://alphaliteAirways.com/ revenue/reports/2001/quarter3" report="revenue" department="research"> <sas-publish:Entries> <sas-publish:Entry sas-publish:type="file" sas-publish:description="Revenue graph"> <sas-publish:File sas-publish:type="binary" sas-publish:name="revenue.gif" sas-publish:mimetype="image/gif" /> </sas-publish:Entry> <sas-publish:Entry sas-publish:type="reference" sas-publish:description="Revenue details."> <sas-publish:Reference sas-publish:type="html" sas-publish:reference= "http://www.alphaliteAirways.com/revenue.html" /> </sas-publish:Entry> </sas-publish:Entries> </sas-publish:Package> </sas-event:Body> </sas-event:Event> Example 3: Implicitly Published EventIn the following example, the published package contains a SAS data set, an external text file, and an HTML file. Because the published package is not archived, the sas-publish:packageUrl attribute is not specified. The SAS data set is defined using the name/value specification of "quarter=third region=south quarterly". The HTML file contains a body, a frame, the contents, a page, and a companion file.
<?xml version="1.0" encoding="UTF-8"?> <sas-event:Event xmlns:sas-event= "http://support.sas.com/xml/namespace/services.events-1.1" sas-event:name='SASPackage.ReportChannel'> <sas-event:Header> <sas-event:Version>1.0</sas-event:Version> <sas-event:SentAt>26SEP2001:19:15:37 </sas-event:SentAt> </sas-event:Header> <sas-event:Body> <sas-publish:Package version="1.0" xmlns:sas-publish= "http://support.sas.com/xml/ namespace/services.publish-1.1" sas-publish:version="1.0" sas-publish:Description="Sales Reporting Data" sas-publish:Abstract="Data necessary to create and manage the Sales reports." sas-publish:Channel="SalesChannel"> <sas-publish:Entries> <sas-publish:Entry sas-publish:type="dataset" sas-publish:Description="Employee information data set" quarter="third" region="south" quarterly=""> <sas-publish:Dataset sas-publish:name="SalesData"/> </sas-publish:Entry> <sas-publish:Entry sas-publish:type="file" sas-publish:description="Defects SAS job."> sas-publish:File sas-publish:type="text" sas-publish:name="defects.sas" sas-publish:mimetype="application/sas"/> </sas-publish:Entry <sas-publish:Entry sas-publish:type="html" sas-publish:description="ODS generated HTML."> <sas-publish:HTML sas-publish:type="body" sas-publish:name="body.html" sas-publish:url="body.html"/> <sas-publish:HTML sas-publish:type="frame" sas-publish:name="frame.html" sas-publish:url="frame.html"/> <sas-publish:HTML sas-publish:type="contents" sas-publish:name="contents.html" sas-publish:url="contents.html"/> <sas-publish:HTML sas-publish:type="page" sas-publish:name="page.html" sas-publish:url="page.html"/> <sas-publish:Companion sas-publish:name="graph.gif" sas-publish:url="graph.gif" sas-publish:mimetype="image/gif"/> </sas-publish:Entry> </sas-publish:Entries> </sas-publish:Package> </sas-event:Body> </sas-event:Event>
|