Manual Index

Additional resources can be found in the How To... Guide.

9. HTML Reports and Custom Web Pages

What are These Features?

HTML Reports and Custom Web Pages provide a means of viewing DesktopProfile application test output from your Web browser, without having to have DesktopProfile client software running on your machine (unlike GUI Reports). This makes it possible to simply click on a URL link and retrieve an HTML Web page that contains critical analysis data at anytime, from anywhere. As long as you are connected to the Internet in some way and have access to the Web server on which the Web page is stored, you can get the information you need.

HTML Reports accessed via URL

HTML Reports come in two varieties: Custom Reports and System Reports. Custom Reports are reports that you define and include a fixed set of options that you can use to control content and output format. System Reports are pre-defined reports that are provided with the application. They currently include the same reports that are available with the VisualPulse™ product, and report ping data only (packet loss and latency).

Custom Reports - Edit Report dialog used to define your own reports

System Reports - list of available pre-defined reports

Sample Custom Report

Custom Web Pages are similar to Custom Reports, but add more flexibility in terms of formatting and content. Custom Reports limit data presentation to a tabular format. Although, in some cases, you can elect to include/exclude certain sections of a report and have some control over how data is grouped, you have no direct control over the HTML source code itself. For example, you can not insert your own text, tables, images, links, and the like. Nor are you able to include graphics from the application, such as a plot. Custom Web Pages give you this capability.

Custom Web Page - sample includes links, images, text, and DesktopProfile plot.

How do These Features Work?

For System Reports, no setup or configuration is required. If you are using the DesktopProfile client, you simply click the 'Reports' button on the Home menu, and then click the 'HTML System Reports' button on the Reports menu. Alternately, you can select File / New / HTML System Reports from the menu bar. This causes a new browser window to open, displaying the System Reports home page. To run a report, select the report you want to run from the 'Report' drop-down list, select the test for which you want data reported from the 'Test' drop-down list, and then click 'Run Report'. DesktopProfile will generate and display a Web page containing the report output. If you are not running the DesktopProfile client but do have browser access to the DesktopProfile server machine, you can view system reports by using the following URL: http://server:port/SystemReports, where 'server:port' is equal to the address of your DesktopProfile server (example: myserver.mydomain.com:81).

System Reports provide limited functionality. You can't schedule System Reports, for example. Nor can you publish these reports to a remote server. Finally, you can't password-protect these reports and, unless you have access to the server on which DesktopProfile is running, you will not be able to access these reports from another machine.

Custom Reports allow you to do anything you can with System Reports, and much more. You can duplicate any report available via System Reports by defining a custom report with the appropriate parameters. Moreover, you are not bound to ping information. You can report on any metric for any available test and plugin. You can schedule reports to run at regular intervals and publish the results to a remote Web server (which may be handy if you have a corporate firewall.) You can alert people of report availability via e-mail and you can restrict report access with passwords (user-authentication). Custom Report definition, itself, requires a user logon and may only be performed via the DesktopProfile client.

To define a Custom Report within the DesktopProfile client, click the 'Reports' button on the Home menu, and then click the 'HTML Custom Reports' button on the Reports menu. Alternately, you can select File / New / HTML Custom Reports from the menu bar. If you have not previously entered a logon password to access another dialog, you are required to enter a valid password. Once your password is accepted, the HTML Custom Reports dialog is displayed. This dialog lists any reports you may have already defined and includes options to add, edit, copy, view, schedule, and delete reports. Clicking the 'New', 'Edit', or 'Copy' buttons cause the Edit Report dialog to display, which allows you to define and save the parameters you wish to use for a particular report. This dialog, in turn, includes access to additional report configuration options having to do with user-authentication, e-mail, and scheduling.

Custom Web Page setup is very similar to Custom Report setup. Click the 'Reports' button on the Home menu, and then click the 'Custom Web Pages' button on the Reports menu. Alternately, you can select File / New / Custom Web Pages from the menu bar. As with Custom Reports, if you have not previously entered a logon password to access another dialog, you are required to enter a valid password here. Once your password is accepted, the Custom Web Pages dialog is displayed. This dialog lists any web pages you may have already defined and includes options to add, edit, copy, view, schedule, and delete pages. Clicking the 'New', 'Edit', or 'Copy' buttons cause the Edit Web Page dialog to display, which allows you to define and save the parameters you wish to use for a particular web page. This dialog, in turn, includes access to additional web page configuration options having to do with user-authentication, e-mail, and scheduling.

Both Custom Reports and Custom Web Pages allow you to produce HTML pages, generated by the application according to your specifications, online or offline (according to a pre-defined schedule). A 'Run Report' button for Custom Reports and a 'Display Page' button for Custom Web Pages allows you to generate an HTML page on demand in a new browser window. You can use this feature to preview a report/page during the definition process, or to simply access report information for diagnostic purposes. To make this information available to other people who do not necessarily have access to the DesktopProfile client, it is generally necessary to schedule the report/page and write the generated output to disk. Custom Reports can also be requested from a browser, for those who have access to the DesktopProfile server machine. Enter http://server:port/CustomReports, where 'server:port' is equal to the address of your DesktopProfile server (example: myserver.mydomain. com:81).

Scheduling causes DesktopProfile's EventManger component to generate and write Custom Report and Custom Web Page output to disk at regular intervals. Once a file exists on disk, it can then be accessed via a web browser by simply using the appropriate URL. Options are available to automatically send e-mail notifications when a new file is available for viewing. These include a URL link, which, in most mail readers, can be clicked to open a browser window and load the page. The link may alternately be copied / pasted into a browser to retrieve the page. Finally, pages can be password-protected by associating them with a list of users.

Another scheduling option is remote publishing. This feature allows files to be written to disk on a remote server when the report/page is generated, rather than to the local server. Note, however, that when using this option user-authentication is not available. Currently these two features -- user-authentication and remote publishing -- are mutually exclusive.

Global Settings for Reports / Web Pages

Before defining reports and web pages, it is recommended that you first do some setup at the global level. This will establish default values related to reporting that will save you time later. Global parameters can be set that pertain to e-mail notifications and remote publishing.

E-mail Notification

From within the DesktopProfile client, click 'Setup' on the Home menu, then 'Settings' on the Setup menu, and finally 'E-mail' on the Global Settings menu. The E-mail Defaults dialog will display. Enter relevant default information. This will provide the initial values used during report/page definition, which can then be overridden, if you so desire. DesktopProfile currently uses SMTP to send mail; therefore, in order to use this feature your mail server must support this protocol.

E-mail Defaults dialog

Remote Publishing

From within the DesktopProfile client, click 'Setup' on the Home menu, then 'Settings' on the Setup menu, and finally 'Remote Publishing' on the Global Settings menu. The Remote Publishing Defaults dialog will display. Enter relevant default information. This will provide the initial values used at the report/page definition level, which can then be overridden, if you so desire. It is important that the information provided in the 'Web Folder' field and that entered in 'Directory' are not contradictory. 'Directory' represents the full file system path to the folder in which reports/pages will be stored on the remote server. 'Web Folder' represents the folder, relative to the web root directory, in which these files will be stored. It relates to the URL that you would enter in a browser to retrieve the HTML page and is equal to that portion of the URL following the host/port specification and excluding the file name, for example:

http:// myhost.mycompany.com:80/DesktopProfile/filename

Thus, 'Directory' should always end with the value in 'Web Folder', if a value has been specified (e.g., 'c:').

Both the E-mail Defaults dialog and the Remote Publishing Defaults dialog include context-sensitive help. As you tab from one field to another, descriptive text is displayed in a Quick Help window.

Remote Publishing Defaults dialog

Defining a Custom Report

From within the DesktopProfile client, click 'Reports' on the Home menu and then 'HTML Custom Reports' on the Reports menu. Or, from the menu bar, selected File / New / HTML Custom Reports. The HTML Custom Reports dialog appears.

HTML Custom Reports dialog

New…	Define a new report.
Edit…	Edit the selected report.
Copy…	Define a new report, copying data from the selected report.
Run Report	Generate and display the selected report.
Schedule…	Show scheduling dialogs, so scheduling info for the selected report may be added or changed.
Delete	Delete the selected report. Removes report definition parameters.
Save Changes	Write changes to disk.

Click 'New' to create a new report or 'Copy' to create a report using a previously defined report as a template. The Edit Report dialog appears. Select the time span and summary interval you wish to use. Then, select the plugin, test, host(s) and metric(s) to be reported. (Note, the summary interval should always be equal to or greater than the test interval you specified when the test you are using was defined.) Finally, specify other options related to output format and data filtering, and give the report a name. Quick Help descriptions are provided for each field, as you tab from one to another.

Edit Report dialog - new report

Authorized Users dialog

Add/Edit User dialog

Clicking 'Advanced Setup…' causes the Advanced Setup dialog to display, which enables you to define e-mail and/or remote publishing options for this report. You will note that the two sections of this page contain fields identical to those found on the Global Settings dialogs, E-mail Defaults and Remote Publishing Defaults. If you defined those global defaults, the values you entered will appear in the fields on this dialog when it is initially opened. Checkboxes allow you to enable/disable these options. Once enabled, you are free to override any default values.

Advanced Setup dialog - e-mail and remote publishing options

Clicking 'Schedule…' causes the Available Schedules dialog to display, which allows you to select a schedule for this report. You may also add new schedules or modify existing ones. The Edit Schedule dialog can be used to specify the parameters for a particular schedule. Note, for daily items an additional option is available: 'Run every ___ minutes'. This allows you to generate a report repeatedly throughout the day, which can be handy if the report represents a short time span (example, one hour) and it is important that its contents be refreshed often.

Available Schedules dialog

Edit Schedule dialog

Saving a report that has been linked to a schedule will cause that report to be generated and saved to disk at the requested frequency. Whether or not the report is saved to disk on the DesktopProfile server machine or on a different machine depends on whether or not you are using the remote publishing feature. When remote publishing is not used, reports will be stored in the CustomReport sub-folder of the main application directory (e.g., 'c:Files').

Custom Report folder

All scheduled items can be viewed at any time via the Scheduled Events dialog. Click 'Setup' on the Home menu, then 'Settings' on the Setup menu, and, finally, 'Scheduled Events' on the Global Settings menu. The resulting display lists all scheduled events and provides options to enable/disable events, delete events, and view/edit schedules. Any report or web page that has been linked to a schedule has an associated event.

Scheduled Events dialog

Each item in the Scheduled Events dialog includes its next scheduled run date/time, the name of the report or web page to which it is linked, a reset indicator (if the event or its schedule has been disabled), the associated schedule name, and event's the last run date/time (scroll right to view).

You can enable/disable events in various ways. This causes them to be ignored by EventManager and the associated report/web page is not generated. You can also remove events from the schedule altogether. Finally, you can enable/disable an entire schedule, which affects each event linked to that schedule.

Disabling Events

On the Custom Reports and Custom Web Pages dialogs, '+' (shift-"+") enables a selected list item. '-' disables a selected list item (and its associated event).

On the Scheduled Events dialog, clicking the 'Reset' button toggles a selected item between enabled and disabled. +/- also works.

Removing Events from a Schedule

On the Edit Report and Edit Web Page dialogs, clicking the 'Remove from schedule' checkbox will do just that. Note, this checkbox is only enabled if the report/page has actually been linked to a schedule.

On the Scheduled Events dialog, clicking the 'Delete' button will remove the highlighted item from its associated schedule.

Enabling / Disabling an Entire Schedule

This can be done from the Edit Schedule dialog, using the 'Temporarily disable this schedule' checkbox. Note, when you do this, all related items will display on the Scheduled Events dialog with a '[*Disabled]' tag. The asterisk differentiates these items from others that may be individually disabled ('[Disabled]').

Defining a Custom Web Page

Like Custom Reports, Custom Web Pages are generated HTML pages that contain DesktopProfile test output. All the options available for Custom Reports can also be used for Custom Web Pages: user-authentication, e-mail notification, remote publishing, and scheduling. Unlike, Custom Reports, however, Custom Web Pages allow you to incorporate other DesktopProfile objects that you are used to seeing on your desktop. Currently, these include plots and tableviews. In addition, you can combined the information provided by these objects with your own HTML to produce an endless variety of pages. In fact, you can even design your pages to link to one another, effectively creating a web site that can be navigated to view all kinds of statistical information. Finally, by combined custom web pages with the appropriate scheduling, you can ensure that this site is updated on a timely basis, so that the information provided is always relevant.

Custom Web Pages dialog (use is identical to that of Custom Reports)

 

Edit Web Page dialog

There are two ways to define the objects that you want to include in your custom web page. Each is reflected in the Edit Web Page dialog.

• Define a desktop that contains those objects. Then use the desktop as your data source for the page.

• Write custom HTML tags that describe the objects you want included. These tags would be included in a userpage, an HTML file that you create and store in a specific location on the DesktopProfile server.

It is also possible to use a combination of these two methods.

Including Desktop Objects in Your Web Page - Method 1 (Default Page)

• Create a desktop that contains the plot(s) and/or tableview object(s) you want included in your web page.
• Save the desktop.
• Create a new web page.
• Selected the desktop name from the Desktop Data Source list.
• Select any other options you want to use for this page.
• Preview the page by clicking Display Page.
• Save the page.
• This method creates a default HTML page and inserts the objects from the desktop into that page in random order.

Method 1 (Default Page) - setup
 

Method 1 (Default Page) - output

In the sample above, it so happens that when the desktop plot was created it was given a tag name, "Sample Plot". If this had not been done, the application would have assigned the plot a tag name, "plot01" -- "plot" because it found the desktop object to be a plot, and "01" because it was the first -- and only -- reportable object it found on the desktop. Had the desktop object been a tableview, its default name would have been "table01". It is important that you understand this naming convention, because it allows you to build HTML userpages that reference desktop plots and tableviews that may not have been assigned specific tag names.

There are three options on the pop-up menus that appear when you right-click on a desktop plot or tableview that are specifically provided to accommodate custom web page processing. These options allow you to 1) set the relative time period to be reported for the plot or tableview, 2) define the plot or tableview tag name (e.g., "Accounts Ping Latency" or, as in the sample above, "Sample Plot"), and 3) capture custom HTML tags (described later in this document) that can be read by DesktopProfile and used to generate plot / tableview page objects independent of a desktop. These pop-up menus are shown below.

Plot pop-up menu, including 'Relative time period plotting', 'Set HTML tag name, and 'Capture HTML tag info' -- all related to custom web page processing.

 

Tableview pop-up menu, including 'Select HTML Report Times', 'Define HTML Report Tag Name, and 'Capture HTML tag info' - all related to custom web page processing.

 

Including Desktop Objects in Your Web Page - Method 2 (with userpage)

• Create a desktop that contains the plot(s) and/or tableview object(s) you want included in your web page.
• Save the desktop.
• Create an HTML userpage and store it in the userpages sub-folder of the CustomWebPages directory (e.g., 'c:Files CustomWebPages'). This HTML page can contain anything you want -- images, links, text; but it should also contain reference(s) to the desktop object(s) you want inserted into the custom web page when it is generated. If an object was given an HTML tag name via one of the right-click pop-up menu options (described above), the reference should use this name; otherwise a default tag name should be used, bearing in mind the default naming convention used by the application (e.g., "plot01", "table01", etc.). The syntax for including desktop references in a userpage is detailed below in the table labelled Desktop Tags.
• Create a new web page.
• Select your desktop name from the Desktop Data Source list.
• Select your userpage from the User Page list.
• Select any other options you want to use for this page.
• Preview the page by clicking Display Page.
• Save the page.

Method 2 (combine desktop and userpage) - setup

 

Method 2 (combine desktop and userpage) - userpage

The following page shows the output produced when this custom web page was generated.

Method 2 (combine desktop and userpage) - output

Using Custom HTML Tags to Add Objects to Your Web Pages

The steps below describe how to create custom web pages that do not use desktops as a data source.

• Create an HTML userpage and store it in the userpages sub-folder of the CustomWebPages directory (e.g., c:\Files\ CustomWebPages). This HTML page can contain anything you want -- images, links, text.
• At the appropriate points in your userpage, custom HTML tags describing the objects you want inserted. The syntax for including object references in a userpage is detailed below in the tables labeled Plot Tags and Tableview Tags.
• Create a new web page.
• Leave the Desktop Data Source field blank.
• Select your userpage from the User Page list.
• Select any other options you want to use for this page.
• Preview the page by clicking Display Page.
• Save the page.

 

Using custom HTML tags to add objects to web pages - setup

 

Using custom HTML tags to add objects to web pages - userpage

 

The following page shows the output produced when this custom web page was generated.

Using custom HTML tags to add objects to web pages - output

As you can see, there is a lot you can do with userpages. In the examples above, in addition to plot and tableview data, links to other pages have been included, as well as text and images. The Visualware logo at the bottom right-hand corner of the page can be clicked to transfer to another web site.

The information below describes the syntax and rules for adding custom HTML tags to your userpages which allow you to include desktop objects or plot / tableview objects independent of a desktop. Study the HTML in the previous examples to see how this works.

Tag Rules

No spaces are allowed in beginning and ending tags.

Tag item values that contain spaces must be enclosed in quotes, unless the value is part of a super-value which is already specified in quotes (i.e., variables). For example, if I use a title value of My Report, it should be enclosed in quotes (title="My Report").

Desktop Tags

<vipr	Beginning tag (required) - trailing space required
>	Ending tag
The following items may be included between the beginning and ending tag, using the format: item=value. At least one space must separate item=value pairs.
tag		tag name of desktop object to be inserted
title		text to be displayed in a banner preceding the plot or table on the page
font		(tableview objects only) value indicating font to be used for table text (e.g., helvetica, arial, etc.)
size		(tableview objects only) value indicating size of font to be used for table text (Note: font and size, once specified, apply to all tables on the page. Different fonts and font sizes cannot be used for different tables.)
info		(tableview objects only) value of true or false, indicating whether or not the table should be preceded by an information header describing table contents
avg		(tableview objects only) value of true or false indicating whether or not the table should include an averages row. This is ignored if row does not equal time.
Example:		<vipr tag="EbayLatency" title="Ebay Latency - 1 Hour">

Plot Tags

<vplplot>	beginning tag (required) - no spaces allowed
</vppot>	ending tag (required) - no spaces allowed
The following items may be included between the beginning and ending tag, using the format: item=value. At least one space must separate item=value pairs.
width		value indicating the plot width in pixels
height		value indicating the plot height in pixels
plottype		value indicating plot type: area, bar, gauge, histogram, kiviats, line, meter, pie, scatter, stacked, statistical
relative		value true or false, indicating whether or not plot uses relative time periods
begin		Beginning time (required if relative=false); format is "yyyy/mm/dd hh:mm:ss" (quotes required)
end		ending time (required if relative=false); format is "yyyy/mm/dd hh:mm:ss" (quotes required)
period		Numeric value indicating plot period (required if relative=true) 0 - Last Hour 1 - Last 12 Hours 2 - Last Day 3 - Last 2 Days 4 - Last Week 5 - Last Month 6 - Last Quarter 7 - Last 6 Months 8 - Last Year
interval		value indicating plot time intervals (in seconds): 15, 50, 300, 3600, 86400
variables		value indicating test, hosts, metrics being reported; format is "test=value;hosts=value;metrics=value", (semi-colons and quotes required), where: test value = the exact test name (e.g., My Ping Test) hosts value = comma-delimited list of IP addresses, or "all" metrics value = comma-delimited list of metric names, or "all Metric names can be upper or lower case and must equal at least the unique first part of the proper metrics name, for example "latency" for the metric name "Latency (ms)".
title		text to be displayed in a banner preceding the plot on the page
Example:		<slplot> plottype=line width=350 height=250 relative=true period=0 interval=15 variables="test=Ping Test;hosts=207.217.96.35;metrics=all" </slplot>

Tableview Tags

<vptable>	beginning tag (required) - no spaces allowed
</vptable>	ending tag (required) - no spaces allowed
The following items may be included between the beginning and ending tag, using the format: item=value. At least one space must separate item=value pairs.
col	value indicating table column type (or xtype): metric, host, or time
row	value indicating table row type (or ytype): metric, host, or time
zvalue	a value indicating the table zvalue. For example, if col (xtype)=host and row(ytype)=time, then the ztype for the table would be metric and the zvalue would equal a valid metric name (e.g., 'latency'). Metric names follow the same convention used for plot metric names. If col=metric and row=host, then zvalue would equal a time string in the format "yyyy/mm/dd hh:mm:ss". (Note, this value must be a valid data item timestamp, which can only be determined by trial and error. If the timestamp is not found in the dataset, columns will be repeated for every timestamp in the dataset; therefore, using time for ztype is not usually practical.)
period	numeric value indicating plot period 0 - Last Hour 1 - Last 12 Hours 2 - Last Day 3 - Last 2 Days 4 - Last Week 5 - Last Month 6 - Last Quarter 7 - Last 6 Months 8 - Last Year
interval	value indicating table time intervals (in seconds): 15, 50, 300, 3600, 86400
title	text to be displayed in a banner preceding the table on the page
Font	value indicating font to be used for table text (e.g., helvetica or arial)
Size	value indicating size of font to be used for table text (Note: font and size, once specified, apply to all tables on the page. Different fonts and font sizes cannot be used for different tables.)
Info	value of true or false, indicating whether or not the table should be preceded by an information header describing table contents
Avg	value of true or false indicating whether or not the table should include an averages row. This is ignored if row does not equal time.
Example:	<sltable> zvalue="207.217.96.35" row=time col=metric period=0 interval=60 font=helvetica size=9 info=false avg=true test="Ping Test" </sltable>

File Output Destinations

When custom web pages are generated offline according to schedule by the EventManager, they are written to disk. Actually, depending on what objects are included in the page, more that one file may be written to disk. If plots are included, one image file (.png extension) is written for each plot, in addition to the HTML page itself (.html extension). Since a custom web page may include several files, these files are always bundled under a single directory, which takes the name of the web page. For example, all the files for a web page named "My Page" will be written to a directory called "My_Page". Unless remote publishing has been specified for the page, this directory will be created as a sub-folder of the CustomWebPages directory (e.g., ':Files_Page'). If remote publishing is used, a folder of this name (e.g., My_Page) will be created under the 'Web Folder' you specified on the Advanced Setup dialog.

Remote Publishing

In order to publish reports and web pages to a remote web server, it is necessary to install the DesktopProfile report publishing listener on that server. The DesktopProfile installation files include a folder, RemoteReporting, which includes this software. Here are the steps you should follow to enable remote publishing.

1. Copy the files

Copy the files in the RemoteReporting folder to a location of your choosing on the remote web server.

2. Install the "DesktopProfile Reporter" service

Windows IIS platform

In a DOS prompt window, navigate to the folder where you copied the files in step 1. Enter the command 'replist -install'. This will install the Windows service under the name 'viprlistener'. Once installed you can start the 'viprlistener' service by using the standard Windows Services ControlPanel.

Note: To uninstall the service, the command is 'replist -uninstall'.

Unix platform

Navigate to the folder where you copied the files in step 1. Enter the command 'java –cp . RepList'. This will start the report listener application.

3. To Set the port and access code used by the service software.

The remote reporting software consists of a listener component and a processor component. The first component listens on a specified port for input from the DesktopProfile server. It then checks header information in the message from the DesktopProfile server to see if it contains an access code that matches the one it was given. When the service is initially installed there are default values for port and access code. However, for security reasons, it is recommended that you override these values so that they are unique for your site. To override the default port and access code you need to edit the file config.bin and change the default parameters for 'port' and 'code' respectively.

4. DesktopProfile server setup

The values selected will be needed in the HTML publishing setup process on the DesktopProfile server otherwise security will prevent any pages from being published. Go into the DesktopProfile client GUI and navigate to Setup -> Settings -> Remote Reporting. Enter the appropriate information and save your changes. Make sure that the listener port and access code you enter are the same values you used in config.bin.

If you want custom reports and/or custom web pages to go to a folder on the remote web server other than the root web folder (e.g., c: wwwroot), make sure you enter the folder name in the 'Web Folder' field and that the 'Directory' field contains the full path to the location where you want your files stored, including the web folder. Example1: If you indicate a "Web Folder" of "/DesktopProfile/Reports", and you are running Apache web server software on drive c, the "Directory" value would be "c:".

5. Define and schedule web pages

This is done by enabling the remote reporting options via the Advanced Setup dialog. Initially, this dialog will always display the default values you set in Setup -> Settings -> Remote Reporting . You must click the checkbox to enable these settings, however.

Appendix

Appendix A. Unix Notes

Running as a user:

Because of the execution privilege needed by DesktopProfile to run the data collection tests DesktopProfile cannot be run under USER privilege and must be run under ROOT privilege.

Running as a daemon service: For DesktopProfile to be set up on Unix as a service/daemon, you will need to install the X virtual frame buffer software. This provides a virtual terminal without the need for a hardware console or, even if the console is present, a sign on as this maybe construed a security issue. There is a DesktopProfile shell script, DesktopProfile.sh, provided for the placing in /etc/rc2.d. Basically the script has three environment variables at the beginning that the should be reviewed. They are:

• DISPLAY, this is required by the X software and DesktopProfile.
• PATH, this needs three things to be present in its many directories. (1) the directory for the Java Runtime Environment executable. (2) the location of the directory for the X executables (3) the current directory for DesktopProfile
• VIPRHOME, the installed directory of DesktopProfile.

Once these have been changed the script can be saved, named as S95DesktopProfile and copied over to the boot directory. Please ensure that this will start after the X font server software at boot (the process is xfs) , as some X fonts are required for the Xvfb to function.

---

© 1997-2005 Visualware Inc. | All rights reserved | Legal Information