SAS and Lotus Notes, an ideal combination for ... - sasCommunity

SAS and Lotus Notes, an ideal 

combination for 

webpublication 

Florence - May 2001

Agenda 

Presentation SAS and Lotus Notes 

Introduction 

Tables on the intranet 

Charts 

A clickable map 

Conclusion

Introduction 

OZ zorgverzekeringen 

Health insurance as core-bussiness 

615.000 insurees, 590.000 ZFW 

Main office in Breda, a few offices around the area 

550 employees 

travel-insurance (Europeese) and other insurance 

prodcuts (ASR, Axent/ Aegon)

Tables on the intranet (1) 

Static or dynamic? 

Why on the intranet? 

ODS HTML output destination 

NOTESDB access engine


a simple static webpage 

filename odsout "d:\hugs\output"; 

ods html body = "polissenikazp.html" 

path = odsout 

newfile = output; 

title ”Aantal IKAZ-P polissen"; 

proc tabulate data=d1 missing; 

run; 

ods html close;

filename sasintra notesdb; 


adding a page to an existing LN-database 

data _null_; 

FILE sasintra; 

PUT '!NSF_DB! d:\testserver\notes\data\hugs\sasintra.nsf'; 

PUT "!NSF_ATTACH! d:\hugs\output\ikazp.html"; 

PUT '!NSF_FORM! RAPH00'; 

PUT "!NSF_FIELD!Titel!Aantal polissen Ikaz-P"; 

PUT '!NSF_FIELD!Status!Publiceren'; 

PUT '!NSF_FIELD!SoortRapport!1'; 

PUT '!NSF_FIELD!RapportType!Per rechtsgrond'; 

PUT "!NSF_FIELD!Jaar!2000"; 

PUT "!NSF_FIELD!Maand!Oktober"; 

PUT "!NSF_FIELD!Periode!10"; 

PUT '!NSF_FIELD!Soortverzekering!Hoofdverzekering'; 

PUT "!NSF_FIELD!DocCode!ikazp"; 

PUT "!NSF_FIELD!RapportUrl!/hugs/sasintra.nsf/DbCode/ikazp/$file/ikazp.html?OpenElement"; 

run;


extra features 

Tables with drilldown-facilities 

Tables in Excel 

Creating tables with a different (company) ‘style’


a static webpage with drilldown 

proc format; 

value $ozc 

'00' ='Buitenland' 

'11' ='Brabant’; 

run; 


ods html body = "rg.html" path = odsout newfile = output; 

proc tabulate data=hugs.hugsd1_2; 

format ozc $ozcc.; 

run; 

ods html close;


a static webpage with a link to Excel 


ods html body = "polissenikazpexcel.html" 

path = odsout 


title "Aantal IKAZ-P polissen"; 

title2 " %bquote() "; 

proc tabulate data=d1 out=d1_2 (drop=_page_ _type_ _table_); 

run; 

ods html close;


creating a new style 

proc template; 

define style intra1; 

PARENT=styles.default; 

STYLE Body FROM Body/ 

BACKGROUNDIMAGE='logo_zt.gif’; /* Background */ 

STYLE SystemTitle FROM SystemTitle / /* Title above table */ 

FONT_SIZE = 4 

FOREGROUND = orange 

BACKGROUND = purple; 

STYLE Header FROM Header / /* Column-head */ 

FONT_SIZE = 2 



STYLE Data FROM Data / /* Cellse */ 

FONT_SIZE = 2 

FOREGROUND = white 


end; 

run;;


using a different style 


ods html body = "polissenikazpstyle.html" 

path = odsout 

newfile = output 

style = intra1; 



run; 

ods html close;

Different devices 

Static or dynamic? 

Charts (1) 

Extra options using frames

Charts (2) 

a webpage with a GIF-chart 

proc catalog cat=work.gseg kill; 

quit; 

filename odsout "d:\hugs\output\maag\hagro04"; 

ods html body="graf.html" 

path=odsout 

base="/hugs/sasintra.nsf/DbCode/04gif/$file/"; 

goptions device=gif; 

title "Aantal DDD's Maagmiddelen"; 

proc gchart data = hugs.grafdata; 

quit; 

ods html close;

Charts (3) 

some nice features using the JAVA-device 


ods html file="graf.html" 

path=odsout 

base="/hugs/sasintra.nsf/dbcode04java/$file/" 

archive="/hugs/sasintra.nsf/dbluid/ba99e/$file/graphapp.jar"; 

goptions device=java; 



quit; 

ods html close;

Charts (4) 

a frame with a table of contents 


ods html frame='frame.html' 

contents='contents.html' 

body="body.html" 

path=odsout 

base="/hugs/sasintra.nsf/dbcode04gifetc/$file/"; 


proc tabulate data = hugs.grafdata; 

run; 



quit; 

ods html close;

Charts (4) 

JAVA-metaframe 

goptions device=javameta; 

filename _webout "d:\hugs\output\maag\hagro04\mchart.htm"; 


quit; 

filename _webout "d:\hugs\output\maag\hagro04\mchart2.htm"; 


quit; 

filename _webout "d:\hugs\output\maag\hagro04\mchart3.htm"; 


quit; 

filename _webout;

Charts (5) 

JAVA-metaframe 

filename htmlout "d:\hugs\output\maag\hagro04\mchartmain.htm"; 

data _null_ ; 

file htmlout ; 

put ''; 

put ''; 

put ' Working with Multiple Metacode Files '; 

put ''; 

put ''; 

put ' '; 

put ''; 

put ' '; 

put ' '; 

put ' '; 

put ' '; 

put ' '; 

put ' '; 

put ' '; 

put ' '; 

put ' '; 

put ' '; 

put ' '; 

put ' '; 

put ' '; 

put ' '; 

put 'Sorry, your browser does not support the applet tag.'; 

put ''; 

put ''; 

put ''; 

run;

A clickable map 

data hagros; 

retain XSys YSys '2' When 'A' Position 'E'; 

length text $2; 

x=28.8; y=29.2; text='g'; HTML = 'href="/hugs/sasintra.nsf/DbCode/m040/$file/mchartmain.htm?OpenElement"'; 

output; 

x=29; y=28.3; text='04'; HTML=''; 

output; 

x=29.4; y=29.2; text='r'; HTML = 'href="/hugs/SASIntra.NSF/SASreport?OpenAgent&04"'; 

output; 

keep XSys YSys When Position Text X Y HTML; 

run; 

ods html file='eggkaart.htm' 

path=odsout 

base="/hugs/sasintra.nsf/DbCode/egg01/$file/"; 

proc gmap data=hulp map=hugs.ozkaart; 

id k_egg; 

choro eggnr /discrete nolegend anno=hagros coutline=black; 

title font=hwdmx065 h=7 c=black 'Economische Geografisch Gebieden'; 

run; 

quit; 

ods html close;

Conclusion 

advantages using SAS (ODS) 

It’s easy to create webpages 

It’s possible to make nice webpages by creating a 

(company) style 

Lots of nice features using different devices

Conclusion 

advantages using Lotus Notes 

All webpages are within one (or a few) LNdatabases 

LN provides easy navigation 

It’s easy to use LN-security 

You can use the existing infrastructure

SAS ® and Lotus Notes ® an ideal combination for webpublication 

Erwin van Dongen 

OZ Health Insurance 

Breda, The Netherlands 

Abstract 

With the help of the Output Delivery System (ODS) it has become very easy to 

generate HTML Output. Standard reports, which were previously distributed on 

paper, can now be published on an Intranet through (static) HTML-pages. To 

administrate large quantities of HTML pages, they are stored in one or more 

Lotus Notes databases. Then they can act as an Intranet with the help of a 

Lotus Domino server. 

In this presentation it is shown how easy it is to generate HTML-pages in a 

nice lay-out. Particular attention will be paid to tables (proc tabulate), 

graphics (proc gchart) and maps (proc gmap). 

Of course the storage of all the output in a Lotus Notes (LN) database with the 

help of the NOTESDB access engine will be a major part of the presentation. 

A demonstration will highlight the advantages of this method. 

1. Tables on the intranet 

The easiest way to publish information on the intranet is to create a static webpage. When you 

have a piece of existing code in which you create a table using the tabulate procedure it is 

pretty easy to capture the output of the procedure in a HTML-file. All you have to do is to add 

a few ODS-statements to your code as is shown in the example. 

Example: A simple static webpage 


ods html body = "polissenikazp.html" 

path = odsout 


title ”Aantal IKAZ-P polissen"; 


run; 

ods html close; 

If the destination (represented by the filename reference) is somewhere on your webserver 

then the output is immediately available on the intranet. However this paper is about 

publishing it on a Domino-webserver in which case you have to put your output in a LNdatabase. 

The following commands can be used to create a new Notes document and to store 

it in a Notes database. 

1

Example: Adding a Notes document to an existing LN-database 

filename sasintra notesdb; 

data _null_; 

FILE sasintra; 

PUT '!NSF_DB! d:\testserver\notes\data\hugs\sasintra.nsf'; /* Name of the LN-database */ 

PUT "!NSF_ATTACH! d:\hugs\output\ikazp.html"; /* Name of the HTML-file */ 

PUT '!NSF_FORM! RAPH00'; /* Name of the form to use */ 

PUT "!NSF_FIELD!Titel!Aantal polissen Ikaz-P"; /* Field defined in the form */ 

PUT '!NSF_FIELD!Status!Publiceren'; /* Field defined in the form */ 

PUT '!NSF_FIELD!SoortRapport!1'; /* Field defined in the form */ 

PUT '!NSF_FIELD!RapportType!Per rechtsgrond'; /* Field defined in the form */ 

PUT "!NSF_FIELD!Jaar!2000"; /* Field defined in the form */ 

PUT "!NSF_FIELD!Maand!Oktober"; /* Field defined in the form */ 

PUT "!NSF_FIELD!Periode!10"; /* Field defined in the form */ 

PUT '!NSF_FIELD!Soortverzekering!Hoofdverzekering'; /* Field defined in the form */ 

PUT "!NSF_FIELD!DocCode!ikazp"; /* Unique reference to the new LN-document */ 

PUT "!NSF_FIELD!RapportUrl!/hugs/sasintra.nsf/DbCode/ikazp/$file/ikazp.html?OpenElement"; 

/* URL containing DocCode and name of HTML */ 

run; 

First a file name reference is created which specifies that the NotesDB access engine is to be 

used. Then, the data is written to this file. The Notes database that is to be opened is specified. 

Then the HTML file that is to be attached is indicated. In this example, we use a 

predetermined Notes form (RAPH00). Finally, the fields that belong to this form are filled in. 

It is important to note that the DocCode must be unique and must be specified in the 

RapportUrl. 

Requirements 

To use the NotesDB access engine it is necessary to specify the directory in which the 

notes.ini and the notes.exe are found in your search path. This can be done in the control 

panel system. Go to environment and change the variable ‘path’. Add the extra directories to 

the path. For example (for Windows NT) c:\notes\data;c:\notes’. See for more information 

Walker, 1997. 

A table gets much more interesting when you add some extra features to it. The following 

examples show how you can add a drilldown to your table, how you can make a link to an 

Excel-spreadsheet (so a user can download the information) and how you can create and add a 

(company) style. 

Example: A static webpage with drilldown 

proc format; 

value $ozc 

'00' ='Buitenland' 

'11' ='Brabant’; 

run; 


ods html body = "rg.html" 

path = odsout 



run; 


2


ods html body = "regio.html" 

path = odsout 



format ozc $ozc.; 

run; 


In this example the $ozc-format contains links to other HTML-files. In the first proc tabulate 

a HTML-file is created for each ozc. These files are automatically numbered rg.html, rg1.html 

and so on. The second proc tabulate creates one HTML-file (regio.html) containing a table in 

which the ozc-variable is a row-variable which is formatted with the links to the other created 

HTML-files. Finally you add all files to your LN-database and you make sure that only 

regio.html can be addressed directly. 

To give a user more possibilities to use the data represented by a HTML-table you can store 

the data in an Excel-file and link the file to the HTML-document. This is shown below. 

Example: A static webpage with a link to Excel 


ods html body = "polissenikazpexcel.html" 

path = odsout 



title2 " %bquote() "; 

proc tabulate data=d1 out=d1_2 (drop=_page_ _type_ _table_); 

run; 


Here a link to Excel is added in the title2-statement. The Href points to a pre-created Excelfile 

(which can be located in the LN-database) and the Excel-logo is used as the link. Users 

who like to create their own graphs or tables using Excel can now download the information 

and can do whatever they like with it. 

ODS gives you the possibility to control the look and feel of the HTML-files you create. One 

of the tools to do so is to create a style using the template-procedure. This paper doesn’t cover 

all the options, but a small example is shown below. 

Example: Creating a new style 

proc template; 

define style intra1; 

PARENT=styles.default; 

STYLE Body FROM Body/ 

BACKGROUNDIMAGE='logo_zt.gif’; /* Background */ 

STYLE SystemTitle FROM SystemTitle / /* Title above table */ 

FONT_SIZE = 4 



STYLE Header FROM Header / /* Column-head */ 

FONT_SIZE = 2 



STYLE Data FROM Data / /* Cells */ 

FONT_SIZE = 2 

FOREGROUND = white 


end; 

run; 

3

In this style the default style is used as the base. Instead of the grey background a logo is used. 

Furthermore the fontsize, foreground and background of the title, column-heads and cells are 

changed. The following example shows how this new style can be used. 

Example: using a different style 


ods html body = "polissenikazpstyle.html" 

path = odsout 

newfile = output 

style = intra1; 



run; 


To use a different style, simply add the style-option to the ODS-statement. 

2. Graphs 

Creating graphs to publish on the intranet is somewhat more complicated because on the one 

hand you have to create the image (for example a GIF) and on the other hand you have to 

create a HTML-file in which the GIF is embedded. Luckily ODS does the necessary work for 

you. The following example creates a graph using proc gchart with the GIF-device. 

Example: a webpage with a GIF-graph 

proc catalog cat=work.gseg kill; 

quit; 


ods html body="graf.html" 

path=odsout 

base="/hugs/sasintra.nsf/DbCode/04gif/$file/"; 




quit; 


The proc catalog in the example above makes sure that the gseg-catalog is empty when the 

new graph is created. The GIF-file is automatically named gchartx.gif where x is the number 

of the graph in the catalog. When you want to add the GIF to a LN-database the name must be 

known. By emptying the catalog you can be sure that in this case the GIF-file is named 

gchart.gif. The ODS-statement looks almost the same as the ODS-statement that is used in the 

previous (table) examples. The only new part is the base-option. This option makes sure that 

the HTML-file that’s been created contains the correct link to the GIF. It is the URL to the 

GIF. 

Both the HTML-file and the GIF-file can be added to the LN-database. The GIF file will be 

stored such that it can not be asked for directly. Only through the HTML-file the GIF will be 

shown. 

It is also possible to use different devices. The Java-device for example gives the user a lot 

more possibilities to interact. The example below shows the use of the JAVA-device. 

4

Example: a webpage with a JAVA-graph 


ods html file="graf.html" 

path=odsout 

base="/hugs/sasintra.nsf/dbcode04java/$file/" 

archive="/hugs/sasintra.nsf/dbluid/ba99e/$file/graphapp.jar"; 

goptions device=java; 



quit; 


The only difference is the device=java and the archive-option that is added to the ODSstatement. 

The last one contains the URL to the JAVA-applet that has to be used while 

viewing the graph. In our case this applet is also attached to a Notes-document in the LNdatabase. 

So far we’ve been creating either a graph or a table. When you create both (or more) it can be 

very nice to create a table of contents as well. In the next example a frame is created in which 

the left side contains a table of contents and the right side contains a graph and a table. 

Example: a frame with a table of contents 


ods html frame='frame.html' 

contents='contents.html' 

body="body.html" 

path=odsout 

base="/hugs/sasintra.nsf/dbcode04gifetc/$file/"; 


proc tabulate data = hugs.grafdata; 

run; 



quit; 


In the ODS-statement the file-option has been replaced by the frame, contents and bodyoption. 

The base now is the path to the contents, body and GIF. By attaching these three files 

in one Notes-document (which itself is not published) the link between the frame (which is 

published) and the rest is established. 

5

3. A clickable map 

The last part of this paper shows an example of a clickable map. A map is created using the 

GMAP-procedure and hotspots are added using the annotate-facility. 

Example: a clickable map 

data hagros; 

retain XSys YSys '2' When 'A' Position 'E'; 

length text $2; 

x=28.8; y=29.2; text='g'; HTML = 

'href="/hugs/sasintra.nsf/DbCode/m040/$file/mchartmain.htm?OpenElement"'; 

output; 

x=29; y=28.3; text='04'; HTML=''; 

output; 

x=29.4; y=29.2; text='r'; HTML = 'href="/hugs/SASIntra.NSF/SASreport?OpenAgent&04"'; 

output; 

keep XSys YSys When Position Text X Y HTML; 

run; 

ods html file='eggkaart.htm' 

path=odsout 

base="/hugs/sasintra.nsf/DbCode/egg01/$file/"; 

proc gmap data=hulp map=hugs.ozkaart; 

id k_egg; 

choro eggnr /discrete nolegend anno=hagros coutline=black; 

title font=hwdmx065 h=7 c=black 'Economische Geografisch Gebieden'; 

run; 

quit; 


In the datastep an annotate dataset is created. This dataset contains x and y co-ordinates of 

hotspots. The variable text is the hotspot that is shown on the map and the HTML-variable 

contains the URL to go to when the user clicks on the hotspot. In this case the first hotspot 

(‘g’) goes to another HTML-file in the LN-database. The other hotspot (‘r’) starts a LN-agent 

with 04 as a parameter. 

The GMAP-procedure creates the map and uses the annotate-dataset to create the hotspots. 

Conclusion 

The new Output Delivery System makes it very easy to create HTML-output. Both text 

(tables) and graphics can be made by adding a few statements to your existing code. By 

adding some HTML-statements yourself or by using different options and devices you can 

add extra features for extra functionality or just to make it all look a bit nicer. By using Lotus 

Notes to store all webcontent everything is stored in a structured way. Besides that it is 

possible to use an existing infrastructure including security and navigation. 

References 

Walker, Jamie (1997) Integrating Lotus Notes ® with SAS ® , SAS ® 

6

SAS and Lotus Notes, an ideal combination for ... - sasCommunity

Create successful ePaper yourself

Delete template?

Save as template?