Getting Started with Logi Info/Logi Report and Java

thumbsshameΔιακομιστές

17 Νοε 2013 (πριν από 3 χρόνια και 6 μήνες)

1.865 εμφανίσεις








Getting Started with

Logi Info
/
Logi Report

and Java


Installing

and U
nderstanding
Logi

Analytics

Managed Report
ing

Products




For
Linux
, UNIX,

or

Windows

with

the
Java

Runtime Environment





October

2
0
1
3






























This document has been formatted for double
-
sided printin
g, hole
-
punching, and
placement in a ring
-
binder.


Author: Lee Hausman


Logi Analytics

is a trademark of
Logi Analytics
, Inc.


Microsoft, Microsoft Word, Microsoft Excel, Windows, Windows
XP
,
Windows Server, Windows Vista,
and Visual Basic are registered
trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.


Other prod
ucts and company names mentioned in this book may be trademarks of their respective owners.


Logi Analytics
, Inc.

7900 Westpark Drive, Suite
A200

McLean, Virginia 22101

703
-
752
-
9700



Copyright © 2009
-
201
3
,
Logi Analytics
, Inc.

All
rights reserved.
i


Table of Contents



Introduction

................................
................................
................................
................................
............................

1

System Requirements

................................
................................
................................
................................
.............

3

General Requirements

................................
................................
................................
................................
........

3

How Many Servers Do You

Need?

................................
................................
................................
......................

4

Serv
er Virtualization

................................
................................
................................
................................
...........

5

About Logi Reporting with Java

................................
................................
................................
..............................

6

Development Options

................................
................................
................................
................................
.........

6

Deployment Options

................................
................................
................................
................................
...........

6

Database Connectivity and Tools

................................
................................
................................
........................

6

Ba
sic Platform Knowledge Required

................................
................................
................................
...................

7

Product Licensing

................................
................................
................................
................................
................

7

Differences from Logi Applications for .NET

................................
................................
................................
.......

8

Installing Logi Studio on Windows

................................
................................
................................
..........................

8

Preparing to Install

................................
................................
................................
................................
..............

9

Installing the Software

................................
................................
................................
................................
......

14

Configuring IIS

................................
................................
................................
................................
...................

21

Modifying or Repairing the Installation

................................
................................
................................
............

23

Product Licensing

................................
................................
................................
................................
..................

24

Built
-
in Trial License

................................
................................
................................
................................
..........

24

License Keys and License Files

................................
................................
................................
..........................

24

License Management

................................
................................
................................
................................
........

25

When a License Expires

................................
................................
................................
................................
.....

28

Licenses and Server Virtualization

................................
................................
................................
....................

29

Upgrading Logi Products and Apps

................................
................................
................................
.......................

30

General Requirements

................................
................................
................................
................................
......

30

Upgrade Impacts

................................
................................
................................
................................
...............

30

Upgrading the Products

................................
................................
................................
................................
....

31

Changing the Version of Your Logi
Applications

................................
................................
...............................

31

Logi Architecture Overview
................................
................................
................................
................................
...

34

Understanding Logi Applications

................................
................................
................................
......................

34

Introducing Elemental Development

................................
................................
................................
................

35

Using External Files with a Logi Application

................................
................................
................................
.....

37

Application Deployment

................................
................................
................................
................................
...

38


ii

Additional Helpful Information

................................
................................
................................
.........................

38

Java Server Configurations

................................
................................
................................
................................
....

39

General Information

................................
................................
................................
................................
..........

39

Apache
Tomcat 5.5 / 6.0 / 7.0

................................
................................
................................
...........................

41

JBoss 4

................................
................................
................................
................................
...............................

42

JBoss 5.1

................................
................................
................................
................................
............................

42

JBoss 7.1

................................
................................
................................
................................
............................

43

Sun Glassfish (SJSAS) 2.1

................................
................................
................................
................................
...

44

Sun Glassfish (SJSAS) 3.0, 3.1

................................
................................
................................
............................

44

BEA WebLogic 10

................................
................................
................................
................................
...............

44

Oracle WebLogic 12c

................................
................................
................................
................................
.........

44

IBM Websphere 7, 8.5

................................
................................
................................
................................
.......

45

Introducing Logi Studio

................................
................................
................................
................................
.........

46

Logi Studio Geography

................................
................................
................................
................................
......

46

Panel Arrangement

................................
................................
................................
................................
...........

49

General Featur
es

................................
................................
................................
................................
...............

50

Using Logi Studio

................................
................................
................................
................................
...................

52

Getting Started

................................
................................
................................
................................
..................

52

Logi Application Files

................................
................................
................................
................................
.........

53

Working with Elements

................................
................................
................................
................................
.....

57

Setting Element Attributes

................................
................................
................................
................................

61

Intell
igent Token Completion

................................
................................
................................
............................

66

Assigning Themes and Style Sheet Classes

................................
................................
................................
........

68

Testing and Debugging Applications

................................
................................
................................
.................

72

Deploying Logi Applications

................................
................................
................................
..............................

77

Studio Menus and Toolbar

................................
................................
................................
................................

83

The Database Browser

................................
................................
................................
................................
......

87

The Query Builder
................................
................................
................................
................................
..............

89

Working with Studio Panels

................................
................................
................................
..............................

90

Changing Logi Application Versions

................................
................................
................................
..................

93

Team Development Features

................................
................................
................................
............................

95

Wizards

................................
................................
................................
................................
..............................

98

Deleting a Logi Application

................................
................................
................................
..............................

101

Granting File Access Permissions

................................
................................
................................
........................

102

Using .NET? Let the New App
Wizard Do It

................................
................................
................................
.....

102

Using Java? It’s Usually Done for You

................................
................................
................................
..............

102

Which Accounts?

................................
................................
................................
................................
.............

102

Which Application Sub
-
Folders?

................................
................................
................................
.....................

103

Granting File Permissions Under Windows

................................
................................
................................
.....

103

iii

No Security Tab Visible?

................................
................................
................................
................................
..

108

Managing Support Files

................................
................................
................................
................................
......

109

Using Themes and Cascading Style Sheets

................................
................................
................................
.........

112

About Them
es

................................
................................
................................
................................
.................

112

Selecting a Theme in Studio’s Wizard

................................
................................
................................
.............

113

Adding Themes Manually

................................
................................
................................
...............................

113

Creating Your Own Themes

................................
................................
................................
............................

116

About
Cascading Style Sheets

................................
................................
................................
.........................

117

Create an Example Style Sheet

................................
................................
................................
.......................

118

Add a Style Sheet in Your Application

................................
................................
................................
.............

119

Editing a Style Sheet in the
Workspace

................................
................................
................................
..........

120

Editing in the Style Sheet Selector

................................
................................
................................
..................

121

Editing a Style Sheet Using the External Style Sheet Editor

................................
................................
............

122

Applying a Style Sheet

................................
................................
................................
................................
.....

123

Assigning Style Classes to Elements

................................
................................
................................
................

124

Development Best Practices

................................
................................
................................
...............................

129

Debugging Reports

................................
................................
................................
................................
..............

131

Preview vs. Br
owse

................................
................................
................................
................................
.........

131

Using Comments, Remarks, and Application Notes

................................
................................
.......................

132

Using the Application Debugger

................................
................................
................................
.....................

134

Logging Errors

................................
................................
................................
................................
.................

138

Hello World! Tutorial

................................
................................
................................
................................
..........

140

Creating the Application Folder

................................
................................
................................
......................

140

Glossary

................................
................................
................................
................................
...............................

147

Resources and Support

................................
................................
................................
................................
.......

151





1

Getting Started with Logi Info and Logi Report for Java

Introduction


This
publication

introduces developers to Logi Info and Logi Report,
known as
Logi Analyti
cs
’ “managed repor
t-
ing


products.


Logi Info

is our licensed product that allows developers to create comprehensive reporting solutions and web
applications, using the full range of features and components.


Logi Report

is

a reduced version of Logi Info that, while still capable of producing excellent reports, does not
include all of Info’s power and features.


Developers working with
the .NET Framework
on Windows platforms are directed to
our companion
Getting
Started

publication for
.NET
on
those platforms.


The general purpose of this publication is to assist the reader in installing their
Logi Analytics

product, in ma
k-
ing it functional, and in getting a basic understanding of how Logi reports and web applications wo
rk. Other
publications and online documents are available that focus on specific aspects of Logi applications, such as di
s-
playing data in tables or in charts.


Documentation for
Logi Analytics

products, available on the Logi
Developer Network

web site, will always pr
e-
sent the most up
-
to
-
date information. Specifically, you can look there for the newest features; publications like
this one are by their nature more difficult to keep current.


Unlike products based on c
lient
-
server technology,
Logi Analytics
’ products were conceived to be web
-
based
from the start. They output only HTML and script to the end
-
user’s browser and as a result achieve simplicity,
cross
-
browser compatibility, and an ease
-
of
-
use that eludes othe
r products. At the same time, this means that
some of the flashier functionality of desktop applications or downloaded custom components is not available.
However, the resulting minimal configuration management requirements and tighter security of Logi pro
ducts
provides ample proof of the correctness of its approach, especially in an enterprise setting.


The technique of “elemental development”, the creation of report pages by combining pre
-
defined objects (or
elements) from a toolbox into a hierarchical t
ree that mirrors the top
-
to
-
bottom layout of an HTML page,
makes for speedy report development. New Logi developers are often surprised at how quickly they can pr
o-
duce meaningful reports. In addition, because report designs can be made dynamic at runtime,
developers also
often find the
number

of report definitions they must manage reduced, often by as much as 50%.


The DevNet web site includes numerous free sample applications that can be quickly downloaded and that
provide a great learning opportunity for

new developers. Frequently the sample apps mirror the examples in
the documents on DevNet. Logi developers are urged to take advantage of these sample apps.



What should the Logi developer already know?


A prospective Logi developer should already have a

good understanding of general web technologies
,

such
as
HTML and style sheets, and be familiar with their data sources and the techniques, such as SQL, needed to
access that data.
Experience with
JavaScript

is useful but not required.


What information is not
presented
here?


G
eneral web server
,

database server
, and network
management

techniques
touch on the successful deplo
y-
ment of Logi applications but are beyond the scope of this

publication
. The assumption is made that develo
p-


2


Getting Started with Logi Info and Logi Report for Java

ers ha
ve these skills themselves or
have
access to others within their organization
s

with them

and

the specifics
of these topics are not included here.


We hope you enjoy working with these products and quickly become productive and successful with them.
Commen
ts about this publication are welcomed and can be addressed to
DevNet@LogiAnalytics.com
.






3

Getting Started with Logi Info and Logi Report for Java


System Requirements


The following general hardware and software components are require
d for Logi Info and Logi
Report:


General Requirements


Browsers:

-

Internet Explorer: 10, 9, 8, 7 (Certified) earlier versions not supported
-

see Notes


-

Firefox, Chrome: all current public versions (Supported)

-

Opera, Safari: all current public versions (Supported)

Hardware
:

1 GHz or higher processor recommended; 400 MHz minimum req
’d
.

1⁇䈠o爠桩gU敲⁲ comm敮e敤㬠512

M䈠o映剁M m楮業um⁲ qu楲敤.

300 m敧慢X瑥猠⡍B⤠o映慶a楬慢汥⁨慲l⁤楳欠獰慣攮

Operating

Systems:

-

Suse, Red Hat, Ubuntu
, CentOS

and just about any other flavor of Linux

-

Solaris, HP
-
UX (Limited support)


-

Windows
Server
20
12, 2008, 2003

-

Windows 7 (all editions)

-

Windows Vista
(
Business, Enterprise,
and Ultimate editions only)

-

Windows XP Professional


Web Servers
:

-

Apache
-
Tomcat 5.5
,

6.0
, 7.0

(without Tomcat FHS)

-

JBoss

4, 5
, 7

-

Sun GlassFish (SJSAS) 2.1,

3.0, 3.1

-

BEA WebLogic 10

-

Oracle WebLogic 12c

-

IBM Websphere 7
, 8.5


Software:

The following components
must

be installed:


(Development machine)

-

For
products prior to v11.0.127, Microsoft .NET Framework 2.0 or

3.x

-

For v11.0.127 products and later, Microsoft .NET Framework 4.x


(Web server)

-

Java Development Kit


(JDK)
t

1.6

or 1.7

or complete JVM such as JRockit.


OpenJDK is
not

supported.


Data
Sources:

Logi Info and Logi Report can use any of the following data sources/services:


-

Amazon SimpleDB

-

ODBC
-
compliant database servers

-

DB2 database server

-

OLEDB
-
compliant database servers

-

Files: Excel, CSV, and XML

-

Oracle database server

-

Google Maps

-

PostgreSQL database server

-

Google Docs

-

Salesforce.com



4


Getting Started with Logi Info and Logi Report for Java

-

JDBC
-
compliant database server
s

-

SMTP email servers

-

Microsoft Access

-

Sybase database server

-

Microsoft SQL Server

-

Twitter.com

-

Microsoft SQL Server Analysis Services

-

Web Services (REST and SOAP)

-

MySQL database server





Note
s
:



Microsoft Internet Information Server (IIS) must be installed
before

installing Logi products
. Prior to v11.0.127,
.NET v2.0 or 3.x was required; for v11.0.127 and later, .NET 4.x is required. If not already in place, with your
consent, appropriate versions of the .NET Framework are installed when Logi products are installed. They are
also availab
le for free from the
Microsoft Download Center



Internet Explorer 5

and

6

are no longer considered "modern" browsers, meaning that they have limited s
u
p-
port for the current standard browser technologies, including CSS2, Javascript, and AJAX. Without this support,
in Logi applications certain style and visual elements will render incorrectly, transparent backgrounds for
charts and other image
-
related con
tent will be impaired, and problems using features such as our Dashboards
and interactive pagination controls will occur. Microsoft has declared their lifecycle ended
.


Internet Explorer 10

is supported in v11.0.519 (14 June 2013), and later.


Browser upda
tes

are being released so rapidly that it's impossible for us to guarantee that all browser versions
will work on a day
-
to
-
day basis, or that a new browser release won't be incompatible with an older version of
Logi products.



H
ow Many Servers Do You

Need
?


You should think of your "reporting server" as a computer that has a web server and the Logi server
engine
software installed on it. Ideally, this computer should be dedicated to this task alone.


However, other configurations are possible and quite fea
sible, including those in which the web server also
serves other functions (i.e. is not dedicated to reporting alone) and/or the database server is also on the r
e-
porting server computer.


Which configuration should you use? We do not have guidelines based
on specific numbers of users or reports
to share with you; each deployment situation is different.


Whether you choose to combine functions (web, Logi report, and database

servers) on one computer is, ult
i-
mately, your decision. Numerous factors can affect this decision, including the amount of web server traffic,
the number of concurrent database users, the size of the databases, the complexity of the database queries,
the frequency of report access, and, n
ot least, cost.


You may care to begin with a combined configuration and, as your report usage grows, change to a dedicated
configuration. The nature of Logi products allows you to do this easily and without additional cost (if per
-
server
CPU counts remai
n constant).


Recent studies concerning server virtualization suggest that database servers are frequently under
-
utilized. On
the other hand, many database vendors recommend that their products be run on a dedicated server. You
may wish to check with your

database vendor for their recommendations concerning database servers.



5

Getting Started with Logi Info and Logi Report for Java

Server Virtualization


Many organizations are using server virtualization to maximize hardware usage and reduce costs.

Server virt
u-
alization products allow the assignment of CPU
resources to processes. This may take the form of a maximum
percentage of combined CPU utilization, or as specific allocation of logical CPUs, to a virtual machine (VM). The
server administrator is responsible for making these configuration decisions.


Log
i 10 product licenses treat a VM just like a regular, non
-
virtualized server and run just fine in this enviro
n-
ment.


In order to ensure good performance in any virtualized

server environment, administrators must be careful to
allocate appropriate resources

to VMs.


It's not uncommon to relocate a VM from one hardware platform to another, for example, for hardware
maintenance. The Logi license will "move" with the VM, as long as the machine name remains unchanged.






6


Getting Started with Logi Info and Logi Report for Java


About Logi Reporting
with

Java


Our Jav
a products consist of two parts:
Logi

Studio

and the
Logi

Server Engine
. When a Java application type is
selected during development, Studio generates applications that use the JDK
(or other JVM)
rather than .NET.
The Server Engine

includes special compone
nts that allow Logi applications to be deployed as Java applications
on Windows or Linux platforms.



Development Options


The process of creating Logi applications is identical regardless of output library choice. Some specialized el
e-
ments that are includ
ed to support the Java environment are available, such as
Connection.JDBC
, when deve
l-
oping Java applications.


The
formats

of definition, support, and other files that make up a Logi application and are created by develo
p-
ers
remain the same

for all version
s of Logi managed reporting products
, regardless of the OS they run under
.


Logi Studio
, though Java
-
aware, is a Windows application. Developers creating Logi apps use Studio on a Wi
n-
dows PC to develop their Logi applications, regardless of the final depl
oyment environment. Developers have
the option of developing
and

testing their application entirely on a Windows platform before moving it to a
production Linux/UNIX server.



Deployment Options


Logi applications can be deployed on servers running
Windows or Linux/UNIX. A Logi application can be moved
to one of these servers and enabled to use the JDK

(or other JVM)

by adding
special folders

to the application
folder (changes in the _
S
ettings definition, such as the application path and connection a
ttributes, may also be
necessary).




Database Connectivity and Tools


Connectivity to databases such as
Oracle
,
MySQL
, and
MS SQL Server

is supported via
JDBC
. Connections to a
variety of other non
-
database datasources are also supported, including XML,
CSV, Excel data files, and web
services.


Specific MySQL and MS SQL Server database drivers are provided with the Logi Server Engine, so developers do
not need to separately download and install them. However, these may not be the correct version for all c
i
r-
cumstances and developers may need to update or replace them.


In v11.0.416, our SQL Server JDBC driver was upgraded to work with JDK 1.7 and MS SQL Server 2005+. The
previous version of the driver's
sqljdbc4.jar

file, however, is still provided, as
sqlj
dbc4.old
, for users
who work with MS SQL Server 2000.




7

Getting Started with Logi Info and Logi Report for Java

Developers working with
Oracle
, who wish to use the
Database Browser

and
Query Builder

tools within St
u-
dio, need to install and configure the
Oracle Client (OLEDB)

on the Windows platform where Studio
for Java is
installed.



Basic Platform Knowledge

Required


Developers planning to use Logi for Java applications with Linux/UNIX servers should ensure that they have a
good working understanding

of the OS, JDK

(or other JVM)
, web server, and management
tools on their ser
v-
er. The detailed knowledge required to successfully administer these servers can be
extensive

and
complex

and is well beyond the scope of Logi documentation.



Product
Licens
ing


All Logi 10 products come with a built
-
in
15
-
day trial lic
ense
. You need do nothing but install the product and
you can begin using it immediately. A clearly
-
visible indicator in the Studio toolbar, shown below, counts down
the days remaining in the trial period.




Clicking the counter display will take you to a web page that offers information about
purchasing

a Logi Info
license. After the trial period expires, Studio won't be usable and any Logi reports you may have developed
will
no longer run

without a real lic
ense.


Logi Analytics

licenses are
server
-
based

rather than individual
-
user or concurrent
-
access licenses, so an unli
m-
ited number of end
-
users can access Logi reports through a single web server. Our licensing scheme allows you
to deploy our product on on
e development machine and on one production server. As mentioned earlier, add
i-
tional separate licenses for Studio, for additional developers, are also available.


Licenses are keyed to you or your organization; they take the physical form of license files,

which are assigned
to a specific computer. DevNet includes a
License Management page

where you can manage your licences,
including reviewing them, assigning and un
-
assigning them to machines, and generating license files, at any
time, without any interact
ion with our staff. For more detailed information about licenses, see our document
Product Licensi
ng
.


You
may not

use our products for redistribution with, or embed them in,
other products without an
OEM l
i-
cense
; contact our Sales group for more information if you need OEM licenses.




8


Getting Started with Logi Info and Logi Report for Java

Differences from Logi Applications for .NET


Generally, Logi Java applications provide all of the features and functionality found in Logi .NET
applications.
Occasionally new features will first be released for .NET applications and then for Java in subsequent releases.


Naturally, Logi apps created for Java do not support Windows
-
specific technologies such as OLEDB. Analogous
Java technologies, s
uch as JDBC, are supported instead. However, for the best results, developers should try to
use
native
connections, such as Connection.MySQL, before using
generic

connections like Connection.JDBC.


JavaScript
is the only scripting language available when b
uilding Java applications. However, a built
-
in
"VBScript emulator" essentially allows our intrinsic functions, such as IIF(), which are modeled on VBScript, to
be available for use in a Java application.


Currently, Logi applications for Java
do not

have s
upport for the following elements
:




A
ll

OLAP elements (note that XOLAP elements, however,
are

supported)



The Salesforce.com Connector

(prior to v11.0.416)



DataLayer.Web Scraper


Prior to v10.0.428, when exporting reports to PDF from a Java application, dat
a table column headers would
not be repeated after page breaks.


Install
i
n
g
Logi
Studi
o
on Windows



There are two major parts to the Logi product in the installation file you downloaded:



Logi Studio
, our development environment, is a Windows
application that's typically installed on a Windows
development machine and interacts with the local IIS web server for Logi application development and testing.


The
Logi

Server Engine
is a set of files that's part of each Logi application and which provi
des an extension to
the IIS web server at runtime. When you build a Logi application, Studio adds the Engine files to the applic
a-
tion. The engine also includes a Windows utility application,
Logi Server Manager
,
which

allows you to perform
basic configuration of Logi applications without using Studio.


A very typical installation scenario is to install Studio and the Server Engine on a
Windows
development m
a-
chine, and then install only the Server Engine (including Ser
ver Manager) on the production web server. This
"development and production" dual installation is allowed by our licensing scheme.


Additional copies of Studio may be licensed and installed on additional development machines.


There are a number of ways
to
deploy

your Logi applications to production, including Studio's built
-
in
Applic
a-
tion Deployment

tool.


Other installation scenarios, involving shared network drives and team development, are feasible and can be
used. This document covers installation of

Studio and the Server Engine on a development machine, but you'll
also see what's needed to install the Server Engine on a production server.





9

Getting Started with Logi Info and Logi Report for Java

32
-

or 64
-
bit?


Logi Info and Logi Report are both available for
32
-
bit

and
64
-
bit

systems. There are differen
t Logi product di
s-
tribution files for 32
-
bit and 64
-
bit versions, so be sure you downloaded the right one for your system
.


Preparing to Install


Logi products require Windows 7 and Vista OS editions that include the
full
-
featured IIS 7

(and later) web
ser
ver necessary to run ASP.NET web applications. Therefore,
all

editions of Windows 7 are supported, but
only the
professional
editions of Windows Vista (Business, Enterprise, and Ultimate) are supported. The Wi
n-
dows Vista Starter and Home editions are
not

s
upported. The following sections discuss features that impact
the installation and/or operation of
Logi Analytics

products.



Use the Administrator Account


Windows 7 and Vista include a number of security

enhancements that impact software installation and

it is
critical that installation and configuration occur while using the software with the built
-
in "Administrator" a
c-
count.



Even if your personal account has been added to the local A
d-
ministrators Group, it may not have sufficient privileges, so
don't

rely on it.



As shown at left, the correct practice when running the Logi i
n-
stallation program or using the Command Line to make config
u-
ration adjustments is to start the tool by
right
-
clicking

its icon
and selecting "
Run as administrator
" from the menu
to start the
program. Th
is

ensures that appropriate permissions are provi
d-
ed for the installed components.



Don't see a "Run as administrator" option? If the system is in a network domain, your network admin may
have created security policies that don't a
llow you to see this option, in which case you need to consult your IT
staff for assistance.



If you’re working the Windows Server or Windows XP operating systems, ensure that you have
logged into the
machine

using an account that’s included in the machin
e’s local
Administrator

group.



.NET Framework


Logi Studio requires the .NET Framework components. When Windows 7 and Vista are installed, multiple ve
r-
sions of the framework are typically included. Before doing anything else, ensure that you have .NET in
stalled
by

using File Explorer to browse to:


C:
\
Windows
\
Microsoft.NET
\
Framework


where you should see several folders, such as v2.0.50727, one for each version of .NET installed.




10


Getting Started with Logi Info and Logi Report for Java

Prior to v11.0.127, .NET v2.0 or 3.x was required; for v11.0.127 and
later, .NET 4.x is required. If not already in
place, with your consent, appropriate versions of the .NET framework are installed when Logi products are i
n-
stalled. They are also available for free from the
Microsoft Download Center
.



Installing/Enabling the IIS Web Server


When
Windows 7

and
Vista

are installed, the components for the
IIS web server

are also installed, but they’re
usually not enabled. Y
ou must do this manually,
before

you install your Logi product.





11

Getting Started with Logi Info and Logi Report for Java




12


Getting Started with Logi Info and Logi Report for Java

This is accomplished in
Control Panel
, under
Programs



Turn Windows features on or off
, as shown above.





It is very important that you select
all

of the options shown for now. Under "World Wide Web Services"
you will need to expand and check
all

sub
-
items
-

ensure that you have
check
-
marks

in all the boxes shown
above!


For
other Windows operating systems
, you will need to use the Control Panel
utility to actually install IIS:






The example above shows how to navigate within Control Panel to install IIS.


Finally, you need to configure IIS. First, ensure that the
ASP.NET web service extension

can run:





13

Getting Started with Logi Info and Logi Report for Java



In
Windows 7

and
Vista
, this is done

in the IIS Manager tool, as shown above, by selecting the Home item at
the left, then double
-
clicking the
ISAPI and CGI Restriction
s

item. If the ASP.NET entry (or entries) is marked
Not Allowed
, edit its settings and check the
Allow extension
... checkbox
.





For
other Windows operating systems
, this is done in the IIS Manager tool, by selecting the
Web Service E
x-
tensions

item in the left hand tree list, as shown above.




14


Getting Started with Logi Info and Logi Report for Java

Then ensure that the Web Service Extension for the latest
ASP.NET version you have installed (or a different
version, if you prefer)
has been set to
Allowed
. Select the item and click the
Allow

button if necessary to assign
this status (if using the Standard view, right
-
click the entry and select Allow from the p
opup menu).



Installing the Software


As usual, you can click
Back
at any time before the physical installation begins to go back to the previous
screen.





1.

For
Windows

7 or
Vista
, start the installation by
right
-
clicking

the Logi product installation program icon
and selecting "Run as administrator" to launch the installer. For other Windows operating systems, just
double
-
click the Logi product file icon. Allow it to complete the installation preparation
.





15

Getting Started with Logi Info and Logi Report for Java



2.

When the
We
lcome Screen

appears, click
Next
.





3.

License Agreement
:
Select the "I accept the terms..." radiobutton after reading the license agreement and
click
Next
to continue.




16


Getting Started with Logi Info and Logi Report for Java



4.

Destination Folder:
Optional

-

click
Change

to specify an alternative installation location if you don't like
the default location. Multiple versions may be installed on the same machine and will co
-
exist smoothly u
s-
ing the default values here. Click
Next

to accept the installation location and continue.






5.

Setup Type:
Select the
Typical
or
Custom
radiobutton (see Custom information below) and click
Next

to
continue:





17

Getting Started with Logi Info and Logi Report for Java







If you selected a "Typical" setup,
skip ahead

to Step 6.


If you selected a
"Custom" setup, the dialog box shown above appears. The following components are
available during a
Custom
setup:




Studio
-

The integrated development environment used by developers to create applications
and report definitions.




Server
-

The Logi Server
Engine that processes XML data in report definitions and outputs
HTML.




LogiXML Scheduler Service for .NET
-

The Logi Windows Service that manages scheduled
events; required if you want to have scheduled report generation and distribution.
Not avail
a-
ble in
Logi Report.




LogiXML Scheduler Service for Java
-

The Logi Java daemon that manages scheduled events;
not applicable when using the .NET version of Logi Info.
Not available in Logi Report.



Click any of the components shown and make a selection from the p
opup menu to include them

in the
installation. If desired, click
Space
to review the disk space requirements for the Custom setup you've
selected. Click
Next

to proceed without the review.






18


Getting Started with Logi Info and Logi Report for Java





The
Disk Space Requirements

display give
s

you information a
bout available storage space and warn
s

you if there is not enough space
for
the installation,
you

can repeatedly adjust the components in the
Custom setup and see the effect on storage here, if necessary. Click
OK

to return to the previous dialog
box.








19

Getting Started with Logi Info and Logi Report for Java

6.

Ready to Install
: Review the installation summary and click
Install.








7.

The physical installation will begin and you'll see several progress indicators for different tasks.









20


Getting Started with Logi Info and Logi Report for Java

8.

Installation Complete
:
If

you’re using Windows 7 or Vista and have User Account Control (UAC)
turned off
,
or if you’re using another Windows OS, you can click
Finish
to exit the installer and launch Studio, and skip
the next two steps.


If UAC is
not

turned off, uncheck the "Laun
ch Logi Studio" checkbox, then click
Finish

and proceed to the
next two steps.





9.

Use the Computer browser to navigate to C:
\
Program Files. Right
-
click the LogiXML IES Dev folder and s
e-
lect Properties. In the Security tab, add
NETWORK SERVICE

to the list

of user names and grant it
Full Co
n-
trol
. Repeat the process, granting Full Control to
your own account

(and t
o any other Logi developers who

will work on this computer)
.






21

Getting Started with Logi Info and Logi Report for Java


10.

You may now launch your Logi product and you should see a splash screen like the

one shown above.


Installation is complete and you may begin to use Studio immediately.


Configuring IIS


First, using the IIS Manager tool provided with the OS, ensure that the ASP.NET extension is allowed to ex
e-
cute:



This is done, as shown above, by selecting the Home item at the left, then double
-
clicking the
ISAPI and CGI
Restrictions
item. If the ASP.NET entry (or entries) is marked
Not Allowed
, edit its settings and check the
Allow
extension
... checkbox.



Next, y
ou must ensure that either your Default Web Site, or your individual Logi application virtual directories
(when you create them), have the correct
.NET Trust Levels

assigned:





22


Getting Started with Logi Info and Logi Report for Java




In order to be able to cache data, interact with handlers, and perform othe
r required operations, the .NET
Trust Levels must be set to
Full (Internal)
, as shown above.



Finally, here's a "best practices" tip for configuring IIS for use with Logi applications:





We recommend that you create a new
Application Pool
specifically

for your Logi applications, as shown above,
left. Then you will need to assign your Logi app virtual directories to it by editing their Basic Settings and selec
t-
ing the new pool, as shown above, right. This allows you to manage and restart the pool indepe
ndently of any
other non
-
Logi applications that are also using IIS. Beginning in v10.0.385, Logi apps can use the default
Int
e-
grated
pipeline

mode in application pools, resulting in better performance; Logi apps built using earlier ve
r-
sions must use
Classic

mode.






23

Getting Started with Logi Info and Logi Report for Java

Modifying or Repairing the Installation


Suppose you installed Logi Info but didn't initially install the Scheduler, and now you find you want to schedule
reports. Or you suspect a Logi Studio .DLL file is missing or is corrupted and you w
ant to fix it.








These kinds of situations can be addressed by either modifying or repairing the installation, which you should
do by re
-
running the installation program file (don't forget to right
-
click it and use "Run as administrator" to
start it).


Do not

use Control
Panel


Programs to do this; it will request an .msi file, which is not retained after the ori
g-
inal installation.








24


Getting Started with Logi Info and Logi Report for Java


Product Licensing


Logi Analytics

licenses are
server
-
based,

rather than individual
-
user or concurrent
-
access, licenses, so an u
n-
limited

number of end
-
users can access Logi reports through a single web server. Our Logi Info and Logi Report
licensing scheme allows you to install our product on one development machine and one production server.
Logi Ad Hoc and Logi ETL licenses allow you to
install the products on one production server.


A license is required for both our development tool,
Studio
, and for our
Server Engine
. Your development sy
s-
tem will likely require both but production web servers generally do not need Studio installed on th
em. So, we
offer both a "Studio and Development Server" combination license and a standalone Server license, and this
two
-
license approach allows flexibility in different situations.


If you upgrade an existing installation of our products from one major v
ersion to another major version, for
example version

10

to version
11
, you will need a new license.

A

version
10

license will not work with version
1
1
.
Contact Customer Service if you want to upgrade and need a new license.



Built
-
in Trial License


All Logi
v11 and v
10 products come with a built
-
in
15
-
day trial license
. You need do nothing but install the
product and you can begin using it. A clearly
-
visible display, shown in the Studio toolbar, counts down the days
remaining in the trial period. In
addition, the number of days remaining is displayed in the Debugging Trace
Page, available when debugging is turned on.


Clicking the Studio counter display will take you to a web page that offers information about
purchasing

a Logi
Info license.


After
the trial period expires, Studio and any Logi reports you may have developed will no longer run without a
real license


License Keys and License Files


When you purchase a Logi product, here's what happens in the licensing process:


1.

A
license key
, specific

to you or your organization, is created for you by our staff and stored in our l
i-
censing database.

2.

You visit DevNet's
License Manager

page to create a
license file
. You do this by
assigning

your license
key to a specific computer, by Computer Name. DevNet

then generates a license file.

3.

You then
download

this file and use it to license each Logi Info/Report application you develop, each
Logi Ad Hoc instance you create, or the Logi ETL product.


A typical license file name is lgx100201.lic and licenses are

product
-
specific. This licensing scheme is the same
for both .NET and Java deployments.




25

Getting Started with Logi Info and Logi Report for Java

When you download your license file, you save it in
C:
\
Program Files
\
LogiXML IES DEV
\
LogiStudio

to license any new apps, and in the application folder of any existin
g Logi application that you've created with
a trial license or that you'll be updating to

v11 or

v10.


If you need to move an application to another machine, or re
-
install your Logi product on a different machine,
you can "un
-
assign" the license from one m
achine, assign it to another, and generate a new license file.


OEM

licenses operate in a similar fashion, but can be assigned to multiple machines.



Centralized License File


If you have a large number of Logi apps on the same web server, you may care t
o use a single, centralized l
i-
cense file rather than manage multiple copies of it.


In Version 10, the
General

element in the _S
ettings definition includes a
License File Location

attribute where
the location of the license file is specified. This value i
s a fully
-
qualified web server file system path to the fol
d-
er where the file is stored.

For example,
C:
\
myProjects
\
License
.


You must ensure that all web applications that will use this license run under an account that has
security
permissions

to access files in the folder you specify in License File Location.


With this centralized license approach, if you use the exact same file path to your license file on both your d
e-
velopment machine and your production server, you can deploy Logi applicat
ions by copying them, without
having to replace the license file or adjust your _
S
ettings
definition
attributes each time.



OEM License File


Customers with OEM licenses can embed the entire license inside their Logi application. In the
_Settings

def
i-
niti
on, the
General

element has an
OEM Distribution License

attribute which allows Logi applications to run on
a server that does not otherwise have a license key installed. This is especially useful for XCOPY
-
type deplo
y-
ments: the Logi installation program do
es not have to be run on the web server.


To use this attribute, double
-
click the attribute name to open its Zoom window and then copy the entire XML
contents of your OEM license file into it. This attribute
only

works

with OEM licenses; other types of lic
enses
copied into here will be ignored.



License Management


Our DevNet web site includes a

License Management
page where you can manage your licenses. In order to
manage your licenses, you must be a DevNet member and login first.




26


Getting Started with Logi Info and Logi Report for Java


The details of the L
icense Management page are shown above and here's an explanation:


1.

Product

-

This select list displays the names all products licensed to you; select a product to display its l
i-
censes. Filtering and search capabilities are available to refine the list, too
.

2.

License Key

-

The license "key" created for you when you purchased the product appears here.

3.

Version, Type

& Expires

-

The license version and type and any expiration date appear here.

4.

License

-

Click the "Create" link in this column to assign your lice
nse

to a specific machine. Once done, the
machine name will appear in the next column and the link will change to "Download". Click the link again
to download and save your license file. You may download the file as many times as necessary but it's only
va
lid on the assigned machine.

5.

Assigned To

-

This column displays the name of the machine a license has been assigned to. The "X"
link

allows you to "un
-
assign" the license
-

when this is done, the License link will revert back to "Create",
and you may assi
gn the license to another machine.

6.

Note

-

This column displays optional text you enter to help you more easily identify the computer. Click the
edit icon to add or edit this text.

7.

History

-

This link allows you to track the history of assignments for this license.


Here are the details of the process of creating and downloading a license file:





27

Getting Started with Logi Info and Logi Report for Java



If the link in the Licenses column of the table shown earlier says "Create", clicking it will display the
Create L
i-
cense File

pop
-
up panel, shown above. You use it to assign the license to a specific machine, by entering the
computer name. The Optional Not
e input is for your use if you want to further identify the machine and its text
appears in the table of licenses shown earlier.


If the computer on which this license is to be used runs a
Windows

OS, then the computer name value is
what's known in Window
s parlance as the "machine name". You can open a Command Prompt window on the
machine and enter "hostname", then press Enter to have the name displayed. If a multi
-
part name is di
s-
played, such as "myPC.myCompany.local", use just the first part, "myPC".


If

the computer on which this license is to be used runs a
Linux or other UNIX
-
derivative

OS, then the "co
m-
puter name" value is the computer's "hostname". You can go to a command line and enter "#hostname", then
press Enter to have the name displayed. Use th
e
full

hostname value, exactly as it's displayed, for your co
m-
puter name value entry
.


Click OK to generate the license file for the designated computer.





28


Getting Started with Logi Info and Logi Report for Java



Once the license file has been generated, the link in the Licenses column will change to "Downloa
d". Click this
link to display the Download License File pop
-
up panel, shown above. Click the Download button to download
and save the license file.


If the computer on which this license is to be used runs a
Windows

OS, then save the license file to


C:
\
Program Files
\
LogiXML IES Dev
\
LogiStudio


This will provide licensing for development work using Logi Studio, as well as for new Logi applications that are
developed on the machine and run there using any web server. If you're upgrading any older Logi app
lications,
you'll also need to copy the license file into their application folder.



When a License Expires


After the 15
-
day trial license period expires, Studio will no longer start up and any Logi reports you've deve
l-
oped will
no longer run

unless you have a real license.






If you have purchased a real Logi Info license and, for some reason, it expires, a banner similar to the one
shown above will be displayed at the top of each report and a 7
-
day grace period will start. At the end of
the
grace period, the reports will no longer run.





29

Getting Started with Logi Info and Logi Report for Java

Licenses and Server Virtualization


Many organizations are using server virtualization to maximize hardware usage and reduce costs.


Server virtualization products allow the assignment of CPU resources to

processes. This may take the form of a
maximum percentage of combined CPU utilization, or as specific allocation of logical CPUs, to a virtual machine
(VM). The server administrator is responsible for making these configuration decisions.


Logi
v11 and v
1
0 product licenses treat a VM just like a regular, non
-
virtualized server and run just fine in this
environment.


In order to ensure good performance in any virtualized server environment, administrators must be careful to
allocate appropriate resources to

VMs.


It's not uncommon to relocate a VM from one hardware platform to another, for example, for hardware
maintenance. The Logi license will "move" with the VM, as long as its machine name doesn't change
.






30


Getting Started with Logi Info and Logi Report for Java


Upgrading Logi Products

and Apps


Each new release of
Logi Analytics

managed reporting products provides feature enhancements and improv
e-
ments. Customers are
encouraged

to take advantage of these improvements by
upgrading

to the latest r
e-
leases when they become available.


These instructi
ons provide guidance for the process of upgrading, uninstalling, or modifying your Logi product
installations and managing the related versions of your Logi applications.


The installation tool, InstallShield,
does not remove

any files or folders created o
r modified after the initial i
n-
stallation, including Sample Applications
that
you may have modified, so your report definitions are safe during
an upgrade.




General Requirements




Logi Studio requires the .NET Framework. Prior to v11.0.127, .NET v2.0 or 3
.x was required; for v11.0.127
and later, .NET 4.x is
required
. If not already in place, with your consent, appropriate versions of the .NET
framework are installed when Logi products are installed. They are also available for free from the
M
i-
crosoft Download Center
.




S
eparate installations of different versions of Logi products can co
-
exist as long as they are installed in di
f-
ferent directories.




IIS 6

users may need to implement Application Pools to isolate Logi applications using different .NET
framework versions. This is an IIS configuration task and is explained later in this document. Application
Pools are a standard feature of IIS 7+.



Upgrade Im
pacts




Logi v11 products include stylistic and appearance improvements in charts, super elements, themes,
etc. which are noticeably different. You may care to do a test upgrade before committing to a compr
e-
hensive upgrade.





Logi Info v10 and 11 includes a

free, 15
-
day trial license but, when it expires, you will need a paid,
reg
u
lar license. If you're a customer in good standing, Logi Customer Service will assign that license to
you in advance, but you will need to go to DevNet and download the license fil
e.





A new version of the Logi scripting engine was included with v10. In

any application being upgraded to
v10 or 11

from earlier versions you will need to engage it manually by adding the following case
-
sensitive constant, using the Constants element, to

the application's _Settings definition:

rdScriptingEngine = Version10





Logi Info




31

Getting Started with Logi Info and Logi Report for Java



Logi Report has been
discontinued

as a free product. Existing Logi Report installations, and applications
developed with it, will continue to work as before. Logi Report v10 or 11

users who registered on
DevNet and secured a free, standard (non
-
trial) license are still able to manage thei
r license files on
DevNet. Those with
OEM
, maintenance plans,

or other contracts involving Logi Report will experience
no change in their use of the product.


You are urged to visit the DevNet Release Notes page for your product to understand the technical

changes in
new versions,
before

upgrading.



Upgrading the
Products


Upgrading to a new version involves two steps: installing the new release of your Logi product, and upgrading
the version of any existing Logi applications. You can do the former without

doing the latter; applications are
not automatically upgraded. Original and upgraded applications can co
-
exist, so upgrading can be phased in as
desired.


How do you get an upgrade? Customers who have
purchased a maintenance plan
for Logi Report or Logi Info,
or are using them under an OEM agreement, should contact
Logi Customer Service

via email or telephone
(703
-
752
-
9700 x148) for instructions for downloading upgrades. Customer Ser
vice can also answer questions
you may have about purchasing or renewing a maintenance plan.


To upgrade your Logi product, run the downloaded installation program and install the new version into the
same location as the previous version, or to a differen
t location if you wish to have both versions installed. No
un
-
installation of the original version is required, and existing definitions or data
will not

be overwritten. The
upgrade installation will take 2
-
3 minutes to complete
.


If you wish to install an

upgrade for
evaluation

purposes, we recommend that you install it into a
different
folder

than any previous version, such as
C:
\
Program Files
\
LogiXML IES Dev Test
. This will preserve
the previous version of Studio. If you install an update into the same f
older as a previous version, Studio will be
updated and you will not be able to roll it back without uninstalling and re
-
installing the previous version e
n-
tirely
.


If you have previously installed and used the Logi Scheduler service, we recommend that yo
u make a saf
e-
ty copy of your existing schedule data, before upgrading:


(Win .NET) C:
\
Program Files
\
LogiXML IES Dev
\
LogiXML Scheduler Service Java
\
Schedules.vdb3

(Win Java) C:
\
Program Files
\
LogiXML IES Dev
\
LogiXML Scheduler Service Java
\
Schedules
\
*.*

(
Lin/
UNIX)

<installFolder>/Schedules/*.*


and then proceed with the upgrade installation. Your existing data file should be upgraded in place without
any difficulty.



Changing the Version of Your Logi Applications


Logi applications are individually
tagged

with a
version identifier

for, and contain
files

specific to, the product
version used to create them. When a new version of a Logi product is installed, your applications
are not

a
u-
tomatically upgraded. This allows you continue to use both versions of th
e product and upgrade your applic
a-
tions on your timetable.




32


Getting Started with Logi Info and Logi Report for Java

In order to use all of the features in the latest Logi release, you will need to change application versions on any
machines, development or production, where you upgrade your Logi product.




W
hen you open an application, Studio displays a
warning

in its Application tab, as shown above, if the applic
a-
tion's version does not match the version of Logi Info and Studio being used.


Clicking the
Change Version...

link will cause the application's ve
rsion
-
specific binary files to be replaced with
the files for the current version.
This will not affect any definitions or support files
.






Another method of changing an application's version is by using
Server Manager
, shown above, which is i
n-
stalled
with Studio and is available via Studio's Tools menu or the Start Menu. It's a tool that allows you to e
x-
amine all of the Logi applications on the web server and manage them individually or as a batch. Server Ma
n-
ager is intended for use
only

with .NET appl
ications, using the IIS or Cassini web servers; if neither of these
servers is installed, Server Manager will prompt you to install them
.



33

Getting Started with Logi Info and Logi Report for Java


The Server Manager dialog box displays a table showing each application installed on the local web server and
a list
of all the Logi product versions installed on the machine. To change an application's version, check one or
more applications, select the version desired, and click
Change Version
. The process usually takes less than a
minute for each application selected.

Versions can be upgraded or downgraded
.








34


Getting Started with Logi Info and Logi Report for Java


Logi Architecture Overview


T
his

chapter introduces
Logi Analytics
' application architecture. A key concept,
Elemental Development
, is i
n-
troduced, along with report definition files, elements and attributes.

Elemental Development is the foundation
of Logi applications. In this overview, you'll learn how Logi applications deliver content to the web and how to
include external files such as i
mages, scripts, and XML data files.



Understanding Logi Applications


A Logi
application

generally

consist
s

of one or more
reports
. A report is really a web page so, while Logi pro
d-
ucts are most frequently used as reporting tools, they can also be used
to create rich,

web
-
based applications.
The
Logi Analytics

DevNet web site, for example, is built entirely with Logi Info.


Logi reports

deliver data in a
presentable

and
accessible

manner as web pages.

They use Internet technologies
and browser software
to distribute rich, interactive reports and applications. Logi reporting tools bring leading
-
edge Internet technologies together, allowing developers to quickly deliver results efficiently. The framework
underlying this consists of:




An integrated developm
ent environment (Logi Studio)



An XML
-
based language, coded in text
-
based definition files



A runtime server (the Logi Server Engine)






Logi reporting tools separate the report development, data access, and presentation processes:




1.

Report definitions
are text files that contain the information describing report layout and contents,
stored as
XML data
.

While it is possible to write

definitions with any text editor, Logi Studio provides
an integrated development environment with lots of tools and helpful

wizards that do much of the
coding for you and reduce development time.




35

Getting Started with Logi Info and Logi Report for Java

2.

When a report is requested, the Logi Server Engine on the web server parses the report definitions and
accesses data sources as required.


3.

The retrieved data and presentation details

are formatted based on the definition and accompanying
style

sheets;
HTML

and

script

is generated and returned to the user's browser for viewing.


This arrangement allows the Logi Server Engine to operate as a
stand
-
alone

entity that's completely
ind
e-
pend
ent

of systems that call upon it for reports. Separate applications, regardless of their host OS, enviro
n-
ment, or development language, that wish to embed or access Logi reports, for example, need only include a
standard hyperlink to do so.




Introducing

Elemental Development


Elemental Development

is the process of creating flexible reporting applications using predefined, XML
-
based
objects or "elements".




The advantages of Elemental Development are:




XML
elements

are
reusable

and
encapsulate

specific functionality common to most web applications




A hierarchical layout of elements makes it easy to manage the presentation and functionality of large
web
-
based reports




Studio's drag
-
and
-
drop user interface shields developers from repetitive codin
g and shortens deve
l-
opment time




Elements and their properties (or "attributes") can be easily added, deleted, moved,


and modified to
create almost any type of report


Rules governing the parent
-
child associations that can be made between elements are emb
edded in our Studio
development tool.


Developing reports using elements makes the process quick and intuitive, and saves the developer the work of
creating lower
-
level functionality.



To learn more about Elemental Development, see this
White Paper

on
DevNet
:

http://devnet.
logianalytics.com
/downloads/ED_WhitePaper.pdf





Definition Files


Developers using Logi reporting tools create one or more
definitions
to build
web
-
based applications.


One
report definition

is equivalent to one dynamic web page.


Every Logi application contains at least one r
e-
port definition and can include multiple definitions as the application grows.


Other types of definitions can also be par
t of a Logi application.




36


Getting Started with Logi Info and Logi Report for Java






The example above shows Logi Studio's Application Panel and the six major types of definition files found in
Logi applications, which are described below:



Definitions

Description

_Settings

(Required) The one _Settings
definition in every Logi application contains global config
u-
ration values for the entire application. It contains elements that define the application's
virtual path, debugging capabilities, database connections, security information, and
more.

Reports

Th
is folder may contain report definitions built with elements that define a dynamic web
pages. A report definition typically contains report header and footer elements and a
body element. The main body of the report can include any combination of text, char
ts,
dashboards, data tables, user input controls, etc.

Mobile Reports

Introduced in v10.0.259, this folder may contain report definitions that are used excl
u-
sively to deliver content to mobile devices, built with a combination of common and sp
e-
cial
-
purpose elements.
Not available in Logi Report.

Widgets

This folder contain may contain definitions for a special class of Logi reports that can be
independently embedded into external HTML pages.
Not available in Logi Report.

Templates

This folder
contains definitions that allow Logi Info developers to use forms
-
based repor
t-
ing, using Word, Excel, and PDF forms. Template definitions model the "fill
-
able" form
fields contained within the source template file.
A
vailable in Logi Report

v10.1.59+
.

Pro
cesses

This folder may contain definitions that provide a level of automation and contain the
logic needed to perform specific tasks within an application. Process tasks can be used to
perform scheduled operations, such as exporting a report to PDF format
or then emailing
it to a group of recipients.
Not available in Logi Report.





From XML to HTML...


Every definition file created with Logi Studio is an
XML document
, which describes multiple objects we call
e
l-
ements
and their
attributes
.



Elements
encapsulate different types of functionality and presentation; attributes enable developers to cu
s-
tomize element properties and behavior.





37

Getting Started with Logi Info and Logi Report for Java

For example, a
DataLayer

element retrieves data from a data source and a
Chart.Pie

element creates a pie
chart from
the data.

The Chart.Pie element
has
attributes to specify the
chart’s
height, width,
radius,
color, and
more.






The image above left
i
s

an example report definition, "Test3",
which

contains Style Sheet and
Body

elements.



The

Body

element

has a "child" element: a
Label

element, which has a
Caption

attribute.

The Source code for
this report (middle image) shows the underlying XML source code generated in Studio.



The Logi Server Engine processes the XML source code,

generat
ing

the HTML needed

to present the page

in a
web browser (right image).



Using External Files with a Logi Application


Developers can include a variety of external files,

generically called
Support Files,
in a Logi application and
manage them in Studio.






Logi applications can use the following types of Support Files:




Style Sheet
-

Cascading Style Sheet (CSS) files for presentation control



38


Getting Started with Logi Info and Logi Report for Java



Script
-

JavaScript or VBScript files



Image
-

GIF, JPG, PNG and other types of image files