Professional Documents
Culture Documents
SAP xMII Part I
SAP xMII Part I
Table of Contents
Lab 1 Creating a Web Page .................................................................. 3
Lab 2 Images and Image Maps ............................................................. 11
Lab 3 Tables .................................................................................. 17
Lab 4 Frames ................................................................................. 21
Lab 5 Forms ................................................................................... 25
Lab 6 Style Sheets ........................................................................... 35
Lab 7 SAP xMII Installation Guide ......................................................... 39
Lab 8 Getting Connected ................................................................... 69
Lab 9a Building Queries Using the Template Editor .................................. 75
Lab 9b Building Displays Using the Template Editor.................................. 91
Lab 9c Using the Dynamic Page Generator ............................................ 119
Lab 10a Web Page Design ................................................................. 123
Lab 10b Web Page Design (on your own) .............................................. 127
Lab 11a Scripting with xMII ............................................................... 129
Lab 11b More Scripting with xMII ........................................................ 137
Lab 11c Still More Scripting with xMII .................................................. 143
Lab 12a Personalization - Setting Up Roles ........................................... 147
Lab 12b Personalization - Setting Up Users ........................................... 149
Lab 12c Personalization Assign Users to Roles...................................... 151
Lab 13 Editing the Style Sheets .......................................................... 153
Lab 14 Security.............................................................................. 155
Lab 15 Personalization Navigation Editor............................................ 157
Lab 16 Data Manipulation / Inline Transform ......................................... 163
Lab 17 xMII Reports ........................................................................ 171
Lab 18 iCommand........................................................................... 181
2006 SAP Americas.
All Rights Reserved.
These materials may not be reproduced without the express
written permission of SAP.
Page 1
Page 2
Topics Covered
This lab will cover
Procedure
1. Start Microsoft FrontPage the instructor will be able to guide you to its
location on the training computer.
2. Well begin by creating a template page that well use for creating additional
pages. Templates allow you to maintain the consistency of web pages on a web
site. If a new page isnt already opened, from the icon bar menu, select the
new page icon.
Page 3
Page 4
6. You should note 4 tabs at the bottom of your new page labeled Design,
Split, Code and Preview. Select the Code tab and review the code that
was entered by FrontPage.
Notice the HTML tags prefixed with the <meta> tag. The page editor inserted
these entries into the page source. Since they are contained in the header
section of the page between the <head> and </head> tags, this information is
not actually displayed on the page. <meta> tags contain information regarding
the web editing software, language, and web site theme that are applied to the
web page.
The text in between the <title> and </title> tags makes up a string that is
displayed at the top of the clients web browser. We will customize the title on
every new page that we create in this Lab. Enter an interesting title for your
template page.
Page 5
Page 6
9. Now right-click on the page (in Normal view). In the pop-up window, select
Page Properties This will allow you to set some more document defaults
within the Template page. Review the tabs and the properties in each. You
will note the Page Properties is an easy place to change the title, background
color, fonts, etc.
Page 7
10. Lets save this as our template page. From the File menu, select Save As and
enter a File name: BasePage.htm. Save all work in the Training folder that
you created.
**Note: To view our BasePage.htm, open the browser (Internet Explorer) and type:
http://<servername>/training/<yourfolder>/BasePage.htm
Page 8
11. Now lets create our other web pages from the BasePage.htm template. Well
start with a page that will be the header for our web site. Modify the
BasePage.htm by changing the text (example: My SAP xMII Page), background
color, fonts, etc. Use your imagination. When you are done making your
changes to the header page, Save As Header.htm.
HINT:
When saving the page, use the Change title button to modify the Page title.
12. Repeat the above step to create additional pages for the Table of Contents
(TOC.htm) and two new base pages (Page1.htm and Page2.htm).
Page 9
Page 10
Topics Covered
This lab will cover
Procedure
1. Well begin by inserting a graphic divider to separate the web pages header
information from the rest of the page. Open the Header.htm page and place
the cursor at the bottom of the page. From the Insert menu, select the
Picture\Clip Art option. Select Go to view the clip art currently installed on
your server.
Page 11
3. Switch to the CODE tab and note the syntax of the <image> tag we just added.
You should see something similar to the following
<img border="0"
src="../../../Documents%20and%20Settings/I808636/Local%20
Settings/Temporary%20Internet%20Files/FrontPageTempDir/j0
157995.wmf" width="480" height="28">
The src parameter contains the image file path. Because we have not yet
saved our page, the image file is currently stored in a temporary file location.
When we save the page, you will be prompted to specify another file storage
location. We will save the file and note the new image later in this lab.
You should also note the height and width parameters. By default, these
parameters are set in pixels, resulting in a fixed image size, however they can
also be set as a percentage of the page, resulting in an image size relative to
the size of the page.
4. Modify the width parameter of your image to 90%. To see the effect of the
new setting, switch to the Preview tab and resize the width of your web page.
As you resize you should see the width of the image scale with the page. This
functionality is useful when developing sites for multiple resolutions.
Page 12
5. Now Save the Header.htm page. You will be prompted to save the embedded
image to a location on the server. The location where you save the file will
determine the final path setting for the image (ie: src parameter). The image
path is saved relative to the source HTML page.
Example 1:
If you save the image in the same folder as the HTML page, the image tag
should look like this
<img border="0" src="j157996.gif" width="90%"
height="30">
Since the image file is in the same folder as the HTML page, no additional path
information is required in the src parameter.
Page 13
Example 2:
If you chose to store the image file in an alternate location, the image tag
should look something like this
<img border="0" src="../images/ j157996.gif" width="90%"
height="30">
Since the image file in this example was not stored in the same location as the
HTML page, additional path information was included in the src parameter.
The path defines the location of the image file relative to the HTML page. In
this example, the image file named j157996.gif is stored up one folder level
(represented by ..) from the Header.htm page, in the /images folder.
6. Next were going to add another image that we will use to navigate our web
site. Open the TOC.htm page. From the Insert menu, select Picture\From
File., navigate to the Training folder and select the LinkMenu.gif file. Click
OK.
7. Well add a few hotspots or hyperlink regions to the LinkMenu image for
navigation. To do this, select the LinkMenu image. From the View menu, select
Toolbars\Pictures to display the Picture Toolbar
Hotspot
Tools
Page 14
9. Switch to the Code tab and review the <img> and the <map> tags. You should
see something that looks like this
<map name="FPMap0">
<area href="Page1.htm" shape="rect" coords="10, 36, 88,
62">
</map>
<img border="0" src="../images/LinkMenu.gif"
usemap="#FPMap0" width="100" height="130">
The map tag can contain several area tags. The area tags contain the actual
hotspot link information. The area tag includes parameters for the linked page
(href), the shape of the hotspot, and the coordinates (cords) for the
hotspot touch region. The coordinates are defined in X1, Y1, X2, Y2 sequence
and use the top left corner of the image as the origin.
The <img> tag was also updated to include a new usemap parameter that
references the <map> tag that was just created.
Page 15
10. Switch back to Normal view and add another rectangular hotspot region
around Link 2. Create a hyperlink to Page2.htm. In the HTML view, you
should note a new area tag has been added after the existing area tag, but
before the </map> tag. The final HTML code should look something like this
<map name="FPMap0">
<area href="Page1.htm" shape="rect" coords="10, 36, 88,
62">
<area href="Page2.htm" shape="rect" coords="10, 65, 88,
91">
</map>
<img border="0" src="../images/LinkMenu.gif"
usemap="#FPMap0" width="100" height="130">
Save your TOC.htm page.
11. Open Page1.htm and enter any information that you want to be shown.
Experiment with the formatting tools located on the toolbars.
12. Open Page2.htm and enter information regarding the author of the web site,
credits to the instructor, etc
Page 16
Lab 3 Tables
Purpose
Tables can be used to organize the layout of web pages. In this lab the student will
learn how to add tables and become familiar with defining spacing, borders,
background images, and hyper-linking cells.
Topics Covered
This lab will cover the following topics
Table creation
Table/Cell backgrounds
Hyper-Linking cells
Procedure
1. Open the Header.htm page and switch to the Normal view.
2. First, well create a table that well use for organizing the text in our title.
Place the cursor in front of the title information on the page. From the Table
menu, select Insert\Table
Page 17
Switching to the Code tab, you will see the <table> tag can contain many
<tr>(table row) and <td> (table data) tags. The number of <tr> </tr> pairs
determine the number of rows in the table and the number of <td> </td>
pairs determine the number of columns in the row.
The information between the <td> and the </td> tags defines the cell
contents. By default, FrontPage inserts as a placeholder for the cell
data.
4. Switch back to the Design view to modify the cell contents. Highlight and cut
the title text on your page, then paste it in the first cell of the table. Add
some additional text in the second cell.
Page 18
5. You can change the settings of the entire table or of each individual cell by
right-clicking and selecting either Table Properties or Cell Properties from
the popup menu. This will display the dialog box
HINT: Setting the Border Size to 0 will eliminate the appearance of the
border so only the text will be displayed in the browser.
6. Open Page1.htm and add a 1-row x 2-column table at the top of the page. In
the left cell, type the text To TOC. In the right cell type the text To Page
2.
2006 SAP Americas. All Rights Reserved.
Page 19
8. Open up Page2.htm and repeat the table creation and hyperlink procedure
(make sure you change the text in the right cell to To Page 1).
**Hint: To change hyperlink color: from File menu choose properties, then choose
the Background tab.
Page 20
Topics Covered
This lab will cover the following topics
Frame syntax
Procedure
1. First well create the Frames page. From the File menu, select New > Page.
to open the New page dialog box. Select the More page templates option, then
Frames Pages tab (note the variety of templates you can choose from). Click
on the Banner and Contents page and then click OK to create the new Frames
page.
Page 21
2. Next well need to Set Initial Page for each frame section. In the Banner
Frame (top section), click the Set Initial Page button and set the page to the
Header.htm webpage from your training folder.
NOTE: The full path to the page will be shown in the URL. This will be adjusted when the
page is saved much like the image file path.
Page 22
4. Before we save our file, lets review the HTML code generated for the frames
pages. Switch to the Frames Page Code tab. It should look like this
<frameset rows="107,*">
<frame name="banner" scrolling="no" noresize
target="contents"
src="file:///C:/Inetpub/wwwroot/Training/Header.htm">
<frameset cols="174,*">
<frame name="contents" target="main"
src="file:///C:/Inetpub/wwwroot/Training/TOC.htm"
scrolling="no" noresize>
<frame name="main"
src="file:///C:/Inetpub/wwwroot/Training/Page1.htm">
</frameset>
<noframes>
<body>
<p>This page uses frames, but your browser doesn't
support them.</p>
</body>
</noframes>
</frameset>
Note the frame name and target parameter values. These will be important
when creating hyperlinks.
Page 23
Page 24
Topics Covered
This lab will cover the following topics
Html Forms
Procedure
1. Create a new page using the File/New Page select a normal page and save it
as OrderEntry.htm.
2. Using the Front Page tools, we will build an Order Entry screen that will
ultimately look like this:
Page 25
Right click on the form, choose Form Properties and set the following properties.
To align the elements on the form we will create a table 9 rows x 2 columns:
(insert this table within the form, after the buttons).
Page 26
Begin building the Order Entry screen by entering the static text descriptions
outlined above in the appropriate cells of the table that was just created.
Order Date
Description
Quantity
Ship From
Page 27
One Submit and one Reset Push Button should have been created when the
form was inserted.
Submit Button (Push Button)
Select (click) and drag the Submit button to the appropriate cell.
Double click the Submit button and configure the Push Button Properties as
follows...
Page 28
Page 29
Page 30
iCalendar
The calendar control we will build into the page is a Java applet provided with
CMS.
To add the iCalendar applet, go to the Normal view and select the cell in the table
where you want to put the calendar. Switch to the HTML view and add the
following applet tag into the source code.
<applet NAME="Calendar" code="iCalendar.class"
codebase="/Illuminator/classes/" archive="illum8.zip"
height="192" width="192" align="left">
</applet>
(Note: Java is case sensitive)
Save the OrderEntry.htm file in your training folder, and test.
Page 31
Page 32
Page 33
Page 34
Topics Covered
This lab will cover the following topics
Procedure
1. First, well create a new style sheet. From the File menu, select New In the
popup toolbar choose More page templates, go to the Style Sheet tab, select
the Normal Style Sheet template, and select OK.
Page 35
Page 36
3. To apply the style sheet classes, highlight the Order Entry Lab Example text
in the OrderEntry.htm page. From the drop-down menu on the FrontPage
toolbar, set the class to Normal.red. You should notice that the text color did
not change. That is because we are still in Normal view. Go to the Preview
tab to view the color change.
Continue to apply the classes to the other text on the page as follows
Page 37
Text
Class
Order Date
Normal.Blue
Description
Normal.Blue
Quantity
Normal.Blue
Ship From
Normal.Blue
Horsham
Normal.ucase
Exton
Normal.ucase
4. Lets review the new HTML code in our page. You will note a link to the style
sheet was added to the heading of OrderEntry.htm similar to this
<link rel="stylesheet" type="text/css" href="style.css">
You should also note how the <p> tags for the text have
been modified to reflect the classes we applied
<p class="blue"> Order Date
Page 38
Page 39
For 101-500
Concurrent Users
For 501+
Concurrent Users
Processor
RAM
(512 MB minimum
recommended)
(8192 MBytes
minimum
recommended)
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
Windows 2003
Server
-or-
-or-
-or-
-or-
Windows 2000
Professional with
Service Pack 4 or
greater
Windows 2000
Windows 2000
Windows 2000
Server with Service Server with Service Server with Service
Pack 4 or greater
Pack 4 or greater
Pack 4 or greater
Users
Operating System
Web Server
Software
File System
NTFS
NTFS
NTFS
NTFS
The required system resources vary based on your applications; however, for sizing purposes, an
estimated 2-4 MB per simultaneously connected user can be used.
Virtually any Web browser, including Microsoft Internet Explorer, Netscape Navigator, Netscape
Communicator, Opera, and Mozilla Firefox, can be used with SAP xMII. We recommend that you
use the most recent versions of these products. As stated above, the client should have the Sun JRE
plug-in installed to the browser.
The Sun Java Runtime Environment (JRE) must be installed on the server prior to the SAP xMII
installation (It is recommended that you download and install the full JSDK, instructions can be found
below).
Note: Turn off the Java automatic update mechanism via the Java Plug-in Control Panel.
It is strongly recommended, although not required by SAP xMII, that the local volume where you are
installing SAP xMII be formatted with the NTFS file system. This will enable a high degree of security
control over your Web page content via direct integration with the Windows NT or Windows 2000 and
IIS security and authentication subsystems.
If you will be using the SAP xMII FrontPage add-in, you must be running Microsoft FrontPage 2000
and must have the FrontPage 2000 server extensions installed on your Web server. Refer to the
FrontPage section for detailed instructions on how to install these products.
Page 40
Windows NT
You must install a Web server prior to installing SAP xMII. Microsoft Web
Server 4.0 is available as a free add-on to Windows NT Server or
Workstation as part of the Windows NT 4.0 Option Pack. You can
download the option pack or get it on CD-ROM from your local Microsoft
reseller. If you are installing SAP xMII on an Windows NT Server system,
you will install IIS 4.0. If you are installing SAP xMII on a Windows NT
Workstation machine, you will install Personal Web Server (PWS) 4.0.
Detailed information on installing IIS is provided with the Windows NT
Option Pack. During the NT Option Pack installation it is important to
select the Custom installation option and verify that the following
components are selected for install:
If you will be using ODBC data sources, it is suggested that you obtain the
latest Microsoft Data Access Components from the Microsoft Data Access
Web site and install them on your Web server. Note that these are not
required to access Microsoft SQL Server or Oracle, as SAP xMII will install
direct, high-performance drivers for these databases.
If you are running Windows NT 4.0 and Internet Explorer 4.x on your Web
server, it is recommended that you update certain system files before
installing SAP xMII. It is advised that you run a Windows Update and
install all recommended updates before proceeding.
Note: Installation of IIS may cause the removal or overwrite
of some of the Windows NT Service Pack
components. It is recommended that you reinstall
Service Pack 6a or greater on NT systems, prior to
proceeding to the installation of the SAP xMII
application.
2006 SAP Americas. All Rights Reserved.
Page 41
Windows 2003
By default, Windows 2003 Server has certain locked capabilities that must
be changed after SAP xMII installation in order for SAP xMII to run. You
must create a virtual directory in IIS with the proper privileges so that the
servlet engine will run. Complete the Additional Steps for Windows 2003
section after the Step-by-step Installation.
Windows XP Professional
Microsoft Windows XP Professional is not a supported server platform for
production environments. It should be used for demonstrations and
limited evaluations only.
If you are installing SAP xMII on a Microsoft Windows XP Professional
system, you will install IIS 5.1. IIS is not installed by default with the
operating system. You will have to go to the Add/Remove Windows
Components section and choose to install it. Select the World Wide Web
Service and press Details, then check the Scripts Virtual Directory.
Page 42
If you are using SQL Server 2000, you should have Windows XP
service pack 2 and SQL Server 2000 service pack 3 installed.
Step-by-step Installation
Note: If an error occurs during the install, please review the install
logs for more information.
Page 43
To continue, click the Next button. You may click the Cancel button
at any time during the process in order to stop the installation.
6. The License Agreement window appears. Please read the license
agreement carefully.
If you accept the license agreement, click the Yes button to
continue the SAP xMII installation.
OR
If you do not accept the license agreement, click the No button. The
setup stops and InstallShield Wizard closes.
Page 44
Page 45
Page 46
11.If your previous version was installed with the ServletExec ISAPI
filter, it must be uninstalled in order to continue with your current
installation. To correctly uninstall the ISAPI filter, the SAP xMII
install must reinstall the ISAPI filter. Follow the ISAPI filter install
instructions and accept all defaults. If your previous install did not
include the ISAPI filter, you may skip to step 13.
Page 47
Page 48
Page 49
Page 50
Page 51
Page 52
Page 53
If you want to change this port number at a later time, see Changing
the Application Server Port Number.
After you confirm the selections you made above, you can select a
password for the ServletExec admin account or you can leave the
password blank. Then, click the Yes button to install ServletExec AS
as an NT service.
20.You do not need to view the ServletExec install log or the readme
file. When the ServletExec install is complete, it will open an
Explorer window. Close this window.
Page 54
Page 55
Page 56
Page 57
Page 58
27.If you are upgrading from a version prior to 11.0, the following
window appears. Click the Yes button to run the security migration.
The security migration does not have an interface like the system
migration. A DOS window appears; close it to run the security
migration. If you are upgrading from 11.0 or 11.0.1, the security
migration window does not appear since there is no migration from
those versions. If you choose not to run the security migration at
this time, you can run it from the Start menu.
Page 59
Page 60
Page 61
Page 62
Page 63
Page 64
Page 65
Initialization
By default, SAP xMII starts up (initializes) when the NT Service starts
up. There is a time delay for the initialization in order for various system
services to start up as before SAP xMII initializes. It is important that the
timing is correct. The default delay is 30 seconds. This can easily be
changed if it is causing problems. A symptom of this problem is a class
not found error in the Servlet Exec logs, because not all systems were
initialized before SAP xMII was started, causing some paths to be
incorrect.
Until the delay time is complete, it is recommended that you do not
attempt to query SAP xMII. This includes accessing the SAP xMII main
menu. Keep in mind that the delay is in addition to the delay caused by
the NT Service start up time. See the Server Logging section to see how
to access the Servlet Exec Logs. See the section on SAP xMII
Initialization in the system configuration guide for more information on
this topic.
Page 66
Page 67
Page 68
Topics Covered
This lab will cover
Adding/Configuring/Editing servers
Procedure
To access the SAP xMII Administration Menu, in your browser navigate to
http://<servername>/Lighthammer/
NOTE: Your instructor will provide you with the server name and your
login credentials
After you login your screen should look similar to this
Page 69
Page 70
Page 71
8. Now edit the URL nodename to <computer name> (or <localhost> which is
the default) and the database name to PlasticResin. Verify the port is set
for 1433 (MS SQL Server). Since there is a PlasticResin database running on
the local computer the nodename can be localhost. Click OK.
Page 72
Page 73
Page 74
Topics Covered
This lab will cover the following topics
Tag Queries
SQL Queries
Procedure
First, we will create a series of Query Templates that will be used to extract data
for the Java Applets. From the SAP xMII CMS Menu, under Data Services click the
Query Templates icon.
Page 75
then select Tag Query from the Template Type drop-down menu. Select
OK.
Page 76
b. In the Data Source tab, select InSQLOLEDB Server and Current Mode.
c. Switch to the Tag Query Details tab. Note the Available Tags list.
d. Use the Tag Selection Mask field to limit the Available Tags listed to only
those you wish to view. In the example below, enter %speed and select
the Apply button. This will limit the tags in the Available Tags field to
only those tags that include speed in their tagname.
e. Use the >>, >, <, or << to add tags to or remove tags from the Selected
Tags field.
Page 77
f. Once you have selected the desired tags, click the Test button to verify
that you have a connection to the data source and that the desired data
is returned. Clicking the Test button pops-up the Select Content Type
box choose text/html (default) and click OK.
h. You will see a confirmation dialog box stating that the template was
successfully saved.
Once saved, we can use the InSQLCurrentQuery file as a template to create
additional Tag Query templates that use the same tags, but utilize different
Modes (e.g. History, Statistic).
Page 78
2. History Mode:
a. switch back to the Data Source tab and select the History Mode. Click
the Test button to verify the data. Use the SAVE AS button and Save
the template as InSQLHistoryQuery in your Training folder.
3. Statistics Mode:
a. Change the Mode to Statistics. In the Method field, select MIN,MAX,TWA
from the drop-down menu. Click the Test button to verify data and use
the SAVE AS button to save the template as InSQLStatQuery in your
Training folder.
Page 79
Page 80
Page 81
e. Use the Test button to verify that the proper data is returned.
f. Save the template in your training folder as BatchListQuery.
Page 82
g. Using the same Data Source settings, well create a new SQL Query.
From the Available Tables: select two tables; Sublot and Lot.
h. Select the appropriate columns from each of the tables (see below).
Use the > button to move the selected columns and use the Up and
Down buttons to order the columns as below. The Selected Columns
should be in the following order:
Sublot.LotID
Lot.MaterialName
Sublot.Location
Sublot.QueuedQty
Lot.HoldStatus
Lot.QuarantineStatus
**Note: To populate expression boxes, highlight an Available Table and an
Available Column and click the Paste button next to the expression box you
would like to populate.
i. In the Join Expression: field, add Lot.LotID=Sublot.LotID.
j. In the Filter Expression: field, add Lot.LotID LIKE [Param.1]
k. In the Sort Expression: field, sort on SubLot.LotID.
l. On the Parameters tab, enter a % (percent sign) in the Parameter
Value: field and click Set
Page 83
Page 84
Page 85
aa. Create a new SQL Query using the same PlasticResin Data Source and
Query Mode. Under the SQL Details Tab select the KPIData and
KPIConfig tables.
bb. Select all Columns from both tables (use the >> button to move all the
column names).
cc. In the Join Expression: field, add
KPIData.KPIName=KPIConfig.KPIName (this will join the tables on the
KPIName).
dd. In the Filter Expression: field, add KPIConfig.KPIName =Yield (this
will cause the query to return only yield data).
Page 86
Page 87
d. Once again create a new SQL Query with the PlasticResin server, Mode =
FixedQuery.
e. Enter the following SQL Statement:
(Hint: Try highlighting the table name and column that you want to insert
and click the Paste button next to the Available Columns window this
will insert the table name and column. To just insert the table name,
highlight the table name and click the Paste button next to the Available
Tables window)
Select PlasticBottleTrendData.DateTime,
PlasticBottleTrendData.BatchNo, PlasticBottleTrendData.Pressure,
PlasticBottleTrendData.Temperature, PlasticBottleTrendData.MixSpeed,
PlasticBottleTrendData.Operator from PlasticBottleTrendData Where
(PlasticBottleTrendData.DateTime >= [SD] AND
PlasticBottleTrendData.DateTime <= [ED])
f. Click the Date Range tab and set the Start Date: 08/01/2003 06:45:00
and the End Date: 08/01/2003 20:45:00. Notice the Date-Time
parameters are passed into the SQL Statement.
Page 88
Page 89
Page 90
Topics Covered
This lab will cover the following topics
Procedure
iChart Display Templates
The iChart display template can be used to create many different charts including:
- Line
- Floating Bar
- Regression
- Pie
- Stacked Bar
- XY Regression
- Polar
- Event Horizon
- XY
- Group Bar
- Strip Chart
- Radar
- Bar
- Variability Bar
- Gauge
- Waterfall
- Custom
- Horizontal Bar
- Horizontal Group
Bar
We will begin by creating a new iChart Display template using the Line display
mode.
iChart Display Templates
a. From the SAP xMII Admin Menu, under Visualization Services
click the Display Templates icon.
b. Select the New button, then iChart from the Template Type
drop-down menu. Select OK.
c. In the Chart Type: drop-down box, select Line.
d. In the Title text box, enter iChart Line Chart Type.
e. Save the template as iChartLine in your training folder.
Page 91
Note: Before continuing, review the parameters available in each of the Display
Template tabs (e.g. General, Legend, Xaxis, Yaxis, Pen Details, Behaviors, Data
Mapping, and Refresh). After we are finished creating Display Templates, we will
revisit a few samples to discuss the effect of the various parameters available.
f.
Using the table below as a guide, create these additional Display Templates:
Chart Type
Title
Save As
GroupBar
iChartGroupBar
Polar
iChartPolar
FloatingBar
iChartFloatingBar
Gauge **
iChartGauge
**Note: For Gauge, set both the Horizontal and Vertical Grid Line Count = 2
prior to saving
Page 92
Page 93
Legend tab
a. Set Background Color: black, Border Color: White, Selection
Border Color: gray, Label Color: White, Font: Helvetica 12.
b. Check Legend on Top? Box.
c. Set Legend Width: 25, Legend Height: 0.
Page 94
Scale
Pen Color
Yellow
Cyan
Red
Page 95
Behaviors tab
a. Uncheck Enable Double Click Refresh and Enable Automatic
Refresh.
b. Save the template as BatchTrendChart in your training folder.
Page 96
Page 97
Verify the following settings in the Legend, X Axis, and Y Axis tabs:
Page 98
Page 99
Scale
Pen type
Marker Style
Pen Color
Bar
0 - none
Yellow
Line
5-X
Cyan
Line
5-X
Red
Page 100
Verify the following settings for the Behaviors and Refresh Page tabs:
Page 101
Page 102
Lights
Column Lights
Multi-Lights
Scoreboard
Vertical Grid
Vertical Scoreboard
Embedded Lights
1. We will begin by creating a new iGrid Display template using the Grid display
type
a. Select the New button, then iGrid from the Template Type
drop-down menu. Select OK.
b. In the Grid Type: drop-down box, select Grid.
c. Save the template as iGridGrid in your training folder.
Page 103
Page 104
4. Using the same Layout and Color Context settings, switch to the General tab
and update the Grid Type to MultiLights. Save the template in your training
folder as iGridMultiLights.
Page 105
Page 106
Layout tab
a. Add the appropriate Column Headings by typing into the text box and
clicking the SET button.
b. Verify that the Auto Resize Columns box is checked.
c. Save template in your training folder as BatchListGrid.
6. Create a New iGrid template named LotListGrid with the following parameters:
Page 107
Page 108
Heading
Lot ID
Lot Identification
MaterialName
Material Name
QueuedQty
QTY
Location
Location
HoldStatus
Hold Status
QuarantineStatus
Quarantine Status
Page 109
HoldStatus
QuarantineStatus
Lime Green
Released
ACTIVE
Yellow
Released
QUARANTINED
Pink
ON_HOLD
ACTIVE
Red
ON_HOLD
QUARANTINED
Page 110
Page 111
Page 112
Page 113
d. Switch to the Color Context tab and update it like the following (Note:
Colors, top to bottom, are Yellow, Orange, Lime Green, and Red).
e. Select the Match Mode: Number radio button.
Page 114
f. Switch to the Refresh tab and verify that automatic refresh is ENABLED and
the Refresh Rate is set to 60.
Page 115
Page 116
Page 117
Page 118
Topics Covered
This lab will cover the following topics
Procedure
1. Return to the SAP xMII Admin Menu, under Visualization Services, select the
Dynamic Page Generator icon. This will open up the Dynamic Page Generator
form
Page 119
Page 120
6. The page includes the HTML code for the Applet, which we will use in our webpage design. From your browsers View menu, select Source. A pop-up window
will appear containing the HTML source code that was generated by the CMS
Dynamic Page Servlet. The HTML code should look something like this
<HTML>
<HEAD>
<TITLE>
Auto-Generated Page
</TITLE>
</HEAD>
<BODY>
<DIV ALIGN="CENTER">
<CENTER>
<P>
<APPLET NAME=Untitled CODEBASE="/Illuminator/classes" CODE="iChart"
ARCHIVE="illum8.zip" WIDTH=600 HEIGHT=400 MAYSCRIPT>
<PARAM NAME="QueryTemplate" VALUE="Training/InSQLCurrentQuery">
<PARAM NAME="DisplayTemplate" VALUE="Training/iChartBar">
</APPLET></BODY></HTML>
7. Highlight the Applet tag code (HTML code between and including the <Applet>
and the </Applet> tags) and copy to the clipboard (Ctrl+C).
8. Open Page1.htm in FrontPage. Edit the title of the page and add some text at
the top of the page to read iChart Applet Sample Displays.
9. Switch to the HTML view and paste (Ctrl+V) the <applet> tag code into the
HTML Body of the document.
10. REPEAT the procedure of Generating Pages, copying the HTML code and pasting
it in the <body> of Page1.htm for all of the iChart templates using the table
below as a guide for pairing Query and Display templates.
Query Template
Display Template
Training\<your folder>\InSQLStatQuery
Training\<your folder>\iChartFloatingBar
Training\<your folder>\InSQLCurrentQuery
Training\<your folder>\iChartGauge
Training\<your folder>\InSQLStatQuery
Training\<your folder>\iChartGroupBar
Training\<your folder>\InSQLHistoryQuery
Training\<your folder>\iChartLine
Training\<your folder>\InSQLHistoryQuery
Training\<your folder>\iChartPolar
11. Open Page2.htm in FrontPage. Edit the title of the page and add some text at
the top of the page to read iGrid Applet Sample Grids.
Page 121
Query Template
Display Template
Training\<your folder>\AlarmQuery
Training\<your folder>\iGridGrid
Training\<your folder>\AlarmQuery
Training\<your folder>\iGridLights
Training\<your folder>\AlarmQuery
Training\<your folder>\iGridMultiLights
Training\<your folder>\InSQLCurrentQuery
Training\<your folder>\iGridScoreboard
13. In FrontPage, create a MiscPage.htm for the remaining applet examples. Use
the following table as a guide for selecting Query Template and Display
Template pairs.
Query Template
Display Template
Training\<your folder>\InSQLCurrentQuery
Training\<your folder>\iTickerCurrent
Training\<your folder>\LotListQuery
Training\<your folder>\iBrowser
Page 122
Topics Covered
This lab will cover the following topics
Procedure
1. Create a Tag query using the Simulator as the datasource and the mode =
Current. Select the 4 CylTemp tags to be used for the query. Save in your
Training folder as TempQuery.
2. Create 2 display templates, one grid and one bar chart (for the bar chart,
set the auto refresh to 2 seconds). Save in your Training folder as TempGrid
and TempChart.
3. Open FrontPage and start a new web page.
4. Insert a 3 row, 1 column table on the page. Type a title in row 1. Your
page should look something like this:
Page 123
Page 124
7. Position the cursor in the third row and using the SAP xMII Object wizard
insert an Applet using the temperature query, the grid display and the
following: Width=550, Height=210, Name=TempGrid (Hint: Click Grid
button next to the Display Template windows to view the grid templates).
Page 125
Page 126
Page 127
Page 128
Topics Covered
This lab will cover the following topics
Procedure
Scripting Drill-Downs
In the following Lab we will use JavaScript to drill-down between multiple
applets and correlate data. As a result, the users will be able to select a specific
batch from the BatchList applet and populate the other applets with correlating
data based on the selected batch.
GRID to GRID (BatchList to LotList)
1. First, we must prepare the BatchList and LotList applets for scripting:
a. In FrontPage, click on the Code Tab and find the BatchList Applet. Add
the following highlighted content:
<table border="0" cellspacing="0" width="765" cellpadding="0">
<tr>
<td valign=top rowspan="2" width="378">
<APPLET NAME=BatchList CODEBASE="/Illuminator/classes" CODE="iGrid"
ARCHIVE="illum8.zip" WIDTH=378 HEIGHT=380 MAYSCRIPT>
<PARAM NAME="QueryTemplate" VALUE="Training/BatchListQuery">
<PARAM NAME="DisplayTemplate" VALUE="Training/BatchListGrid">
<PARAM NAME="SelectionEvent" VALUE="UpdateDetails">
</APPLET>
</td>
b. Find the LotList Applet and add the following highlighted content:
<td colspan="2" width="765">
<APPLET NAME=LotList CODEBASE="/Illuminator/classes" CODE="iGrid"
ARCHIVE="illum8.zip" WIDTH=715 HEIGHT=45 MAYSCRIPT>
<PARAM NAME="QueryTemplate" VALUE="Training/LotListQuery">
<PARAM NAME="DisplayTemplate" VALUE="Training/LotListGrid">
<PARAM NAME="Param.1" VALUE="0">
</APPLET></td>
Page 129
<script type="text/JavaScript">
function UpdateDetails(){
//set up aliases for easy reference
var BatchGrid = document.BatchList.getGridObject();
var LotQuery = document.LotList.getQueryObject();
//get the selected LotID
var selLot = BatchGrid.getSelectedCellValueByName(LotID);
//change the where clause for the LotListQuery
LotQuery.setParam(1, selLot);
//do a refresh here because the query is NOT time sensitive
document.LotList.refresh();
}
</script>
Page 130
f. You will note we have declared variables (var TrendQuery and var
Batchgrid) to make our code easier to enter and read. We have also set
our Param and captured both a StartDate and EndDate.
g. Next, well modify the Title of our BatchTrend to be more appropriate
for our selected batch. Enter the highlighted content below:
<script type="text/JavaScript">
function UpdateDetails(){
//set up aliases for easy reference
var BatchGrid = document.BatchList.getGridObject();
var LotQuery = document.LotList.getQueryObject();
var TrendQuery = document.BatchTrend.getQueryObject();
var TrendChart = document.BatchTrend.getChartObject();
//get the selected LotID
var selLot = BatchGrid.getSelectedCellValueByName(LotID);
Page 131
i. Now well enter the Script to drill-down from the BatchList to the
OperatorName applet. Enter the highlighted content below:
<script type="text/JavaScript">
function UpdateDetails(){
//set up aliases for easy reference
var BatchGrid = document.BatchList.getGridObject();
var LotQuery = document.LotList.getQueryObject();
var TrendQuery = document.BatchTrend.getQueryObject();
var TrendChart = document.BatchTrend.getChartObject();
var OperQuery = document.OperatorName.getQueryObject();
2006 SAP Americas. All Rights Reserved.
Page 132
Page 133
Page 134
2.
3.
Page 135
Page 136
Page 137
Value
ShowTitle
False
LegendFontSize
10
XAxisFontSize
10
YAxisFontSize
10
ShowMouseTracking
False
Value
ShowTitle
False
LegendFontSize
10
XAxisFontSize
10
YAxisFontSize
10
ShowTimeControl
False
ShowMouseTracking
False
ShowTagDescription
False
EnableMenu
False
EnableDoubleClickRefresh
False
EnableLegendClick
False
Page 138
q. From the HTML tab, find the YieldTrend applet and enter the following
parameters highlighted below:
<td>
<APPLET NAME="YieldTrend" WIDTH="640" HEIGHT="280" CODE="iChart"
codebase="/Illuminator/Classes" ARCHIVE="illum8.zip" MAYSCRIPT>
<PARAM NAME="QueryTemplate" VALUE="Training/InSQLYieldQueryQuery">
<PARAM NAME="DisplayTemplate" VALUE="Training/iChartLine">
<PARAM NAME="ShowTitle" VALUE="False">
<PARAM NAME="LegendFontSize" VALUE="10">
<PARAM NAME="XAxisFontSize" VALUE="10">
<PARAM NAME="YAxisFontSize" VALUE="10">
<PARAM NAME="ShowMouseTracking" VALUE="False">
<PARAM NAME="UpdateEvent" VALUE="syncYieldTrend">
<PARAM NAME="SelectionEvent" VALUE="syncPens">
</APPLET>
</td>
r. With the parameters added, we can start creating our JavaScript. Well
setup a few variables to reference our objects:
<script type="text/JavaScript">
function syncYieldTrend() {
var SpeedChart = document.SpeedTrend.getChartObject();
var YieldChart = document.YieldTrend.getChartObject();
var SpeedQuery = document.SpeedTrend.getQueryObject();
var YieldQuery = document.YieldTrend.getQueryObject();
s. The next thing we need to do in our script is make sure the web page,
including all applets, is fully loaded before we allow any actions to
occur. To do this, enter the following highlighted content after the
variable declaration:
// make sure the applets have loaded
if(document.YieldTrend == null){
return;
}
if(document.SpeedTrend == null){
return;
}
if(YieldQuery == null){
return;
}
if(SpeedQuery == null){
return;
}
if(YieldChart == null){
return;
}
if(SpeedChart == null){
return;
}
}
</script>
Page 139
t. Next well get the Start and End Dates from our YieldTrend applet.
<script type="text/JavaScript">
function syncYieldTrend() {
var SpeedChart = document.SpeedTrend.getChartObject();
var YieldChart = document.YieldTrend.getChartObject();
var SpeedQuery = document.SpeedTrend.getQueryObject();
var YieldQuery = document.YieldTrend.getQueryObject();
// make sure the applets have loaded
if(document.YieldTrend == null){
return;
}
if(document.SpeedTrend == null){
return;
}
if(YieldQuery == null){
return;
}
if(SpeedQuery == null){
return;
}
if(YieldChart == null){
return;
}
if(SpeedChart == null){
return;
}
// get the start and end times
var selStart = YieldQuery.getStartDate();
var selEnd = YieldQuery.getEndDate();
Page 140
function syncYieldTrend() {
var SpeedChart = document.SpeedTrend.getChartObject();
var YieldChart = document.YieldTrend.getChartObject();
var SpeedQuery = document.SpeedTrend.getQueryObject();
var YieldQuery = document.YieldTrend.getQueryObject();
// make sure the applets have loaded
if(document.YieldTrend == null){
return;
}
if(document.SpeedTrend == null){
return;
}
if(YieldQuery == null){
return;
}
if(SpeedQuery == null){
return;
}
if(YieldChart == null){
return;
}
if(SpeedChart == null){
return;
}
// get the start and end times
var selStart = YieldQuery.getStartDate();
var selEnd = YieldQuery.getEndDate();
// sync the charts
if(selStart != null && selEnd != null) {
// get and set the scaling settings
var zoomYMin = YieldChart.getYAxisZoomMin();
var zoomYMax = YieldChart.getYAxisZoomMax();
SpeedChart.setYAxisZoomMin(zoomYMin);
SpeedChart.setYAxisZoomMax(zoomYMax);
SpeedQuery.setEndDate(selEnd);
SpeedQuery.setStartDate(selStart);
// update the changes
document.SpeedTrend.updateChart(true);
}
}
</script>
Page 141
v. Finally, with a new function, well sync the Tags focused on trend
charts.
function syncPens() {
var SpeedChart = document.SpeedTrend.getChartObject();
var YieldChart = document.YieldTrend.getChartObject();
//get and set the selected pen
var selPen = YieldChart.getSelectedPen();
SpeedChart.setSelectedPen(selPen);
//time sensitive query
document.SpeedTrend.updateChart(false);
}
</SCRIPT>
Your webpage should look like the following:
Page 142
Page 143
i. Create a blank tag query to be used for the applet in the pop-up
window. From the template editor create a new tag query, select
the InSQLOLEDB server and the History mode. Save the template in
your training folder as PopupQuery.
*Do not select any tags we will be setting the tags via the session
variable.
Page 144
Page 145
Page 146
Topics Covered
This lab will cover the following topics
Procedure
Setting up a Role
1. From the SAP xMII Menu, under Security Services choose Security
Manager
2. When prompted to Login:
Username: Admin (This is NOT case sensitive)
Password: Admin (This IS case sensitive)
3. Under User Management, chose the Roles icon and click Add to add a
new role:
4. Add a Role that corresponds to your group number as given to you by the
instructor, and click OK:
Page 147
5.
Page 148
Procedure
Setting up a User
1. Select the Users link.
2. Click Add then enter a user name in pop-up and click OK (*Note Make
sure that the login name has No Spaces).
3. Select the Yes radio button to indicate that this user is Active.
4. Enter a password for the user (passwords are case sensitive).
5. In the Attributes>FullName>Value field, enter your full name and click the
Save Changes to User button. Click OK.
6. Repeat procedure for another user.
Page 149
Page 150
Procedure
Assigning a user to a role (first method)
1. Click on the Roles link, choose your Group role.
2. In the Users window highlight your User. Add the user to the Members of
Role window by clicking the < button.
3. Save the changes by clicking the Save Changes to Role button. Click OK.
Assigning a user to a role (second method)
1. Click on the Users link, choose your second user.
2. In the Roles window highlight your group role.
3. Add to the Member of Roles window by clicking the < button.
4. Save the changes by clicking the Save Changes to User button, and click OK.
You now have 2 users in your Group role.
Page 151
Page 152
Topics Covered
This lab will cover the following topics
Procedure
Minor adjustments to the style sheets This will be performed by the instructor
1. The DynamicHomePage stylesheet is located in the following location:
C:\inetpub\wwwroot\Illuminator\Themes\DynamicHomePage.xsl - This
stylesheet contains all the parts that define the look and feel of your portal.
2. The DynamicHomePage calls a Default Header file. The Header file will
allow you to change the title and the left and right images.
Page 153
Page 154
Lab 14 Security
Purpose
The purpose of this lab is to familiarize the student with the personalization
security settings available with SAP xMII.
Topics Covered
Procedure
Authorize roles for available servers - This will be performed by the instructor
1. From the Administration Menu, under Security Services, click Data Access.
2. Check the Show Only Enabled Servers box.
Page 155
4. In the Roles window choose Everyone and click the < button to move
Everyone into the Roles Assigned to Servers window.
Page 156
Topics Covered
This lab will cover the following topics
Procedure
Build Navigation Trees:
1. From the Administration Menu, under Portal Services, choose Navigation
Editor.
2. Verify Role is selected in the drop-down box and highlight your group role.
3. Click the Add button under the Navigation Tree window and add a
Corporate node.
4. Highlight Corporate and click the Add button to add to the Corporate
node.
Page 157
6. Click SAVE.
7. Following the same procedure as above, highlight Engineering and add a
Batch Info node.
8. Highlight the Batch Info node and add an Overview node with the
target as our BatchOverview.htm page.
9. Click SAVE.
10. Repeat the above steps for the Operator and add a node called Plant
Information under this node add the following nodes: (Remember to
highlight the Plant Information node before adding each node).
Label
Target
Cylinder Temps
/Training/CylTemps.htm
Speed Trends
/Training/PopUp.htm
Machine Stats
/Training/OperatorPage.htm
Page 158
Target
Trends
/Training/Trends.htm
Sample Grids
/Training/Page2.htm
Sample Charts
/Training/Page1.htm
LinkMenu
/Training/HyperLinkMenu.htm
Page 159
Page 160
2. Enter the following (to link to the miscellaneous display page that we
previously built).
3. Click SAVE.
4. Using this procedure set up tabs for each of your roles.
**BE SURE TO CLICK SAVE WHEN YOU ARE FINISHED
Check out the website.
Page 161
Page 162
Topics Covered
This lab will cover the following topics
Inline Transforms
Procedure (Part I)
1. Create a new SQL query with the following settings: Server = Northwind,
Mode = Query.
2. Under the SQL Query Details tab select the [Order Details] and Products
tables and the following columns:
Page 163
Page 164
6. Using the < button choose the columns that we are aliasing and move them
out of the Selected Columns box.
Page 165
8. Test the query and notice that the column names have changed.
Page 166
Page 167
4. In the tag query, under the Transform tab click the button and choose
the IllumCalculator.xsl to use for the transform.
Page 168
Page 169
Page 170
Topics Covered
This lab will cover the following topics
Procedure
1. In FrontPage, the BatchOverview page that we created.
2. First well need to add a button to our web page that will open our xMII
Report. In HTML view, insert the following HTML at the bottom of the page:
(Insert before the </BODY> line).
<form>
<input type="button" value="Open My Lighthammer Report!" name="B1"
onClick="openReport()">
</form>
Page 171
3. Create the openReport() function that our Report button calls onClick.
Insert the following into the JavaScript block at the top of the page: ( make
sure to insert between the <script> and </script> prompts).
function openReport() {
//set up alias for easy reference
var BatchGrid = document.BatchList.getGridObject();
//the selected batch
var selBatch = BatchGrid.getSelectedCellValue(1);
//batch start and end dates are hidden in the grid
var batchStart = BatchGrid.getSelectedCellValue(6);
var batchEnd = BatchGrid.getSelectedCellValue(7);
//check to make sure the user has selected a batch
if (selBatch != "") {
//set up session variables we can use in the Lighthammer Report
//(.irpt)
document.BatchList.setPropertyValue("BatchNo",selBatch);
document.BatchList.setPropertyValue("BatchStart",batchStart);
document.BatchList.setPropertyValue("BatchEnd",batchEnd);
//pop up a new window with the .irpt file
window.open("BatchDetail.irpt");
}
else {
//if no batch selected show a dialog box
alert(Please select a batch!!);
}
}
Page 172
Parameter Value
FilterExpr
PlasticBottleBatchData.BatchID='{BatchNo}
Page 173
Parameter Value
StartDate
{BatchStart}
EndDate
{BatchEnd}
Title
ShowChart
True
Page 174
Page 175
Parameter Value
FilterExpr
PlasticBottleTrendData.BatchNo='{BatchNo}
StartDate
{BatchStart}
EndDate
{BatchEnd}
Page 176
Page 177
Page 178
The ability to run a report without the use of session variables is especially useful
when distributing data to devices that may not be Java-enabled such as hand-held
2006 SAP Americas. All Rights Reserved.
Page 179
Page 180
Lab 18 iCommand
Purpose
The purpose of this lab is to explore the use of iCommands. The iCommand allows
you to execute commands, such as SQL inserts, updates and deletes, without the
need to perform a form post. This makes the user experience much more like a
classic client server interface, without the re-loading of a web page.
Topics Covered
This lab will cover the following topics
Procedure
1. Create our queries:
a) From the Query Template Editor create a new SQL query.
b) From Data Source tab: Server=Northwind, Mode=Query.
c) Choose the SQL Query Details tab and select the Employees table
and the following columns:
Page 181
Page 182
Page 183
c) Switch to the Code view, and insert the following (below the applet we
already inserted).
<FORM>
<INPUT TYPE="HIDDEN" ID="EmployeeID" name="EmployeeID">
<table border="0" cellpadding="1" cellspacing="1">
<tr>
<td>Last Name:</td>
<td><input id="LastName" name="LastName" size="20"></td>
</tr>
<tr>
<td>First Name:</td>
<td><input id="FirstName" name="FirstName" size="20"></td>
</tr>
<tr>
<td>Title:</td>
<td><input id="Title" name="Title" size="20"></td>
</tr>
<tr>
<td>City:</td>
<td><input id="City" name="City" size="20"></td>
</tr>
<tr>
2006 SAP Americas. All Rights Reserved.
Page 184
d) Switch to the Design view, position the cursor at the bottom of the page
and using the SAP xMII Object insert the iCommand applet as follows:
Under Display Types choose Command,
Applet Name=InsertRecord,
Query Template=InsertEmployeeQuery.
See figure on next page.
Page 185
Page 186
Page 187
more details.);
}
}
else {
g) Save the page as iCommand.htm. Review the code and test the
webpage, which should look like this:
Page 188
Enrichment
The following exercises will test the class comprehension of xMII functionality.
The instructor will guide the class through the exercises below when appropriate.
Page 189
Procedure
Create a grid to display the all the columns from the query. Save as
MachineGrid
Page 190
Page 191
Page 192
Topics Covered
This lab will cover the following topic:
Procedure
1. Create a new SQL query with the following settings: Server = Northwind,
Mode = Query.
2. Under the SQL Query Details tab select the Customers table and the
following columns: CustomerID, CompanyName.
Page 193
Page 194
We want to write a script to get the value from the first column of the selected
row (the customer ID) and set that value = Param.1 in the CustOrderQuery.
8. From the Applet drop-down choose CustGrid (we want to get the value from
this grid). From the Applet Method choose getGridObject(), and from the
Oject Method drop-down choose getSelectedCellValue(COLNUMBER). Click
the insert button. See figure on following page:
Page 195
11. Now that we have the customer ID (variable CID), we want to set Param.1 in
the query part of the OrdGrid applet equal to it. Put the cursor on the next
line in the code window and from the drop-downs select the following:
Applet = OrdGrid, Applet Method = getQueryObject();, and Object Method =
setParam(INDEX, NEWVALUE). Click the Insert button.
12. Since we want to set Param 1, change INDEX to 1, and we are setting it equal
to the value from our customer grid (CID), so change NEWVALUE to CID.
2006 SAP Americas. All Rights Reserved.
Page 196
14. Click the Save Script button to save this script to our webpage.
15. Go to the HTML view of our webpage and notice the code the Script Assistant
inserted.
16. Save the page, open the page in a browser and test.
Page 197
Page 198
Procedure
1. Create a 3 new Tag queries with the following settings:
Query 1:
Query 2:
Query 3:
Server = PIUDS
Server = InSQLOLEDB
Server = Simulator
Mode = History
Mode = History
Mode = History
Tag = CDT158
Tag = TI-001
Tag = CylTemp1
2. From the template editor select New and create an Aggregate query.
Page 199
4. Under the Template Selection tab browse the Training folder and using the >
button select the PITempQuery, InSQLTempQuery, and SimTempQuery.
Choose an alias name if you want. These 3 templates should now appear in
the Aggregate Query Source Templates window. You can select up to 32
templates from which to aggregate data.
Page 200
6. From the Aggregate Query Source Param dropdown select Duration. The
aggregate query duration is defaulted to the last 60 minutes of data (just
like all queries).
7. From the Target Template dropdown we can choose *. This means we want
to do this for all the source queries.
8. From the Target Param dropdown select Duration. Click the Add button.
This will set the duration parameter in all the source queries to whatever the
Duration is set to in the aggregate query.
Page 201
Page 202
Topics Covered
This lab will cover the following topics
Creating datasets.
Setting up monitors.
Procedure
1. Create 2 new SQL queries with the following parameters:
Query 1 a. Server = Plastic Resin
b. Mode = Query
c. Selected Tables = KPIData
d. Selected Columns = All (TimeRecorded, KPIName, KPIValue,
KPISource)
e. Save AS KPIQuery1
Query 2 Same as query 1 with the following additions:
a. Filter Expression = KPIData.KPIName LIKE [Param.1] AND
KPIData.KPISource LIKE [Param.2]
b. Parameter 1 = %
c. Parameter 2 = %
d. Save AS KPIParamQuery
2. From the following URL: http://localhost<computer
name>/Lighthammer/Menu.jsp, select Metric/AlertServices > Catagories
icon.
Page 203
Page 204
Page 205
Page 206
Page 207
5. Our first metric will just be the line 1 speed. Click the L1Speed column,
L1Speed should appear in our expression window. Close the Metric
Configuration Window.
Page 208
Page 209
14. The metric we want to define is the Capacity Utilization for Malibu. Scroll
down in the Data Window and choose CapacityUtilization and click the
Set Row Match Rule 1 button.
Page 210
21. Our metric will be the KPI value, so click the KPIValue header so it appears
in the expression window. Close the window.
22. Name the metric Line1OEE and give it a description.
23. Click the Add New button.
Page 211
3. Copy and paste these 6 files into the Scheduled Tasks folder under Control
Panel.
4. From the Start Menu go to Control Panel, Scheduled Tasks, right click and
open in a window.
5. Right click the Active Portal Monitoring 15MIN file and choose properties.
6. Click the Set Password Button the password for these computers is
Illuminator.
7. Follow the same procedure for the Alert Mailer file.
Page 212
Page 213
Page 214
Page 215
Page 216