Академический Документы
Профессиональный Документы
Культура Документы
Trademarks
Intel and Pentium are registered trademarks of Intel Corporation. Java is a trademark or registered trademark of Sun Microsystems, Inc. in the
United States and other countries. IBM, DB2 and Lotus Notes are trademarks of International Business Machines Corporation in the United
States, other countries, or both. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Access, Excel, Internet Explorer,
Microsoft, Outlook, SQL Server and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries. MySQL is a registered trademark of MySQL AB in the United States, the European Union and other countries. Citrix is a
trademark of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office
and in other countries. Other product and company names mentioned herein may be the trademarks of their respective owners.
Table of Contents
Welcome .............................................................................................................................................................1
Before You Begin ...............................................................................................................................................2
Query & Analysis Installation..........................................................................................................................6
Advanced Installation Modes ....................................................................................................................... 47
Query & Analysis XL....................................................................................................................................... 51
Query & Analysis Word.................................................................................................................................. 53
Query & Analysis NetEnterprise .................................................................................................................. 54
Query & Analysis Alert Server ...................................................................................................................... 61
Query & Analysis eAlert (Browser) ............................................................................................................. 72
Query & Analysis Executive (Browser) ...................................................................................................... 78
Internet Security............................................................................................................................................. 88
Query & Analysis Financial Reporting ........................................................................................................ 91
Terminal Server & Citrix ................................................................................................................................. 95
Uninstalling Query & Analysis ..................................................................................................................... 97
Troubleshooting............................................................................................................................................100
Welcome
Welcome to the Infor Performance Management - Query & Analysis Installation Guide.
The guide provides detailed instructions for installing Query & Analysis 10.
Assumptions
This guide has been written with the following assumptions:
You have a working knowledge of the selected database server and computer systems, including installing
software and working with networks.
You have read the Query & Analysis ReadMe file supplied with Query & Analysis. It can be displayed at the
commencement of installation.
General Requirements
Before you begin the Query & Analysis installation, check you have the following information:
Client Requirements
Each client computer requires the following configuration to use Query & Analysis:
Intel Pentium III (1 Ghz) processor. An Intel Pentium 4 (2GHz) processor, or equivalent, is
recommended.
In addition to memory requirements specified for the operating system and Microsoft Office suite, a further
32 MB of RAM is required. A total of 1 GB RAM is recommended.
Microsoft Windows XP Pro, Windows 2003 or Windows Vista with the latest service packs.
Server Requirements
Each server computer requires the following configuration to use Query & Analysis:
Microsoft Windows Server 2000, Windows Server 2003 (32-bit) or Windows Server 2005 with the latest
service packs.
Microsoft Office (only required for the Query & Analysis Alert Server processes: Excel worksheet and Word
document).
Internet Information Services running when Query & Analysis is implement across the web.
For a Query & Analysis application within a Citrix or Terminal Server session:
Note: Query & Analysis is used in conjunction with third party companion products, such as operating systems
and database systems. Query & Analysis is only supported for companion products that are in turn currently
supported by their respective parent company. Please refer to the Query & Analysis Support Policy for full details.
Configuration
The following diagram depicts a typical Query & Analysis configuration.
Database Server
Product
DB
Query &
Analysis
DB
The Query & Analysis software and DataLinks for the products over which Query & Analysis will report are
installed on each PC. The term DataLink refers to the collection of files forming the business logic layer, allowing
Query & Analysis applications to present a Product Database in layout or format that can be easily recognised by
the end user. Once installed on a PC, Query & Analysis will be connected to a Query & Analysis Database and one
or more Product Databases.
The Query & Analysis Database is a single centralised database containing Query & Analysis user, security and
serialisation (licensing) details. Since the Query & Analysis Database contains settings shared amongst all
clients, all clients must point to a single Query & Analysis database. The database can be an Oracle, Microsoft
SQL Server, Microsoft Access, IBM DB2 or MySQL database. It is recommended that the Query & Analysis
Database be of the same type (where possible) as any Product Databases. For example, if the Product over which
Query & Analysis is to report runs on SQL Server 2000, it is recommended that the Query & Analysis database also
be a SQL Server 2000 database.
Product Databases are the actual application databases over which Query & Analysis will report. In most cases
Query & Analysis will be reporting over only one Product Database, but there may be several if more DataLinks are
in use with Query & Analysis.
2.
3.
4.
Create Query & Analysis users and profiles. Run the User Wizard to automatically create Query & Analysis
users based on the names of Product users stored in the Product database.
5.
Serialize Query & Analysis. Alternatively operate Query & Analysis in demonstration mode for 30 days.
6.
Allocate Query & Analysis users to the Product and Query & Analysis application.
7.
8.
Repeat Query & Analysis installation for the remaining clients. Clients are connected to the same centralized
Query & Analysis database so creating Query & Analysis users, serialization and user allocation has been
completed and does not need to be repeated.
9.
If required, install NetEnterprise Server and web part for Microsoft SharePoint, Query & Analysis Alert Server,
Alert (Browser), Executive (Browser) or Query & Analysis Financial Reporting.
2.
Read any Product installation addendum documents included with the Query & Analysis installation,
located in the folder \LsAlchemy\<Product>\Doc
Product addendum documents cover installation issues or additional steps required for specific Products.
Not all Products, accessed via a DataLink, have addendum documents. Once Query & Analysis has been
installed addendum documents are placed in a Doc sub-folder in the Query & Analysis program folder. By
default, C:\Program Files\Infor PM QA \Doc\<Product>
3.
4.
Contact your software vendor to request a license file to serialize Query & Analysis and Product. If Query &
Analysis or an Author Product is not serialized, Query & Analysis operates in demonstration mode for up to
30 days with imposed restrictions on Query & Analysis functionality.
5.
Backup the computer. It is recommend that before commencing any software installation that server
backup procedures are performed.
Server
Alert Tasks
Security options
Passwords
Dictionary items
Before removing Vision 6.3.3-1 you will need to backup client settings. The procedure is detailed below:
1.
If language keys have been modified in Vision then languages should be exported to a file. In Maintenance,
run the Languages utility and export languages to a file. Once Query & Analysis has been installed, the
Vision language file should be imported into Query & Analysis.
2.
If Alert Tasks have been created in Alert Editor, these must be exported to a Task file (*.tsk). In Alert Editor,
select Export Task from the task menu and complete the Export dialog box. Once Query & Analysis has been
installed, the Vision Alert Task file should be imported into Query & Analysis.
3.
Make a backup copy of all DataLinks. DataLinks reside in the LsAlchemy folder. The default location is
C:\Program Files\Vision\Settings. Copy the LsAlchemy folder to a temporary folder.
Once Query & Analysis has been installed, run the Update DataLinks utility and point to the temporary
LsAlchemy folder. The DataLinks will be installed into the Query & Analysis settings folder: C:\Program
Files\Infor PM QA\Settings\LsAlchemy.
4.
Note: Vision must be fully removed before installing Query & Analysis. Do not retain Vision settings.
Vision settings and DataLinks are duplicated in a backup folder in the Vision program folder, by default
C:\Program Files\Vision\Backup\Settings.
5.
Vision XL Workbooks
The Vision XL add-in location has changed from C:\Program Files\Vision to C:\Program File\Infor PM QA. When
existing Vision workbooks are opened in Excel, and with Vision removed, the application will be unable to locate the
LsAgXLB.xla file. To address this there are two courses of action that can be taken, either:
Edit the XL add-in link location for each XL formula in the workbook. Run Excel, open the workbook and select
Links from the Edit menu. Update the link to the Q&A XL add-in location, C:\Program Files\Infor PM QA. This is
the recommended procedure. Also see Query & Analysis XL section.
Install Query & Analysis to the original Vision folder location, by default C:\Program Files\Vision.
2.
Add Windows users to the Group. The Windows users will ultimately be created as Query & Analysis users.
3.
4.
In the Database server tree, right-click Security and select New > Login.
5.
6.
In the Select User or Group, type the Domain name followed by backslash and the group name. Alternatively,
click the assist button to browse accessible domains for the group. For example, SALESDOMAIN \ QUERY &
ANALYSISGROUP.
7.
8.
9.
10.
11.
12.
13.
14.
15.
Select the Database Roles permitted to the Windows Domain Group. Query & Analysis requires the following
permissions:
public
10
16.
11
Oracle Database
If the Product uses an Oracle database then create a new Oracle schema to store the Query & Analysis tables on
the server.
A Net Service Name defines how to access an Oracle database across a network. On each of the client PCs, Net
Service Names should be created for the Query & Analysis Centralized database and the Products Oracle
database
2.
3.
4.
If the instance name is not in the database list, select Add Database to Trees from the Object menu item and
enter the server and database details.
12
5.
6.
7.
8.
9.
10.
General tab: type Query & Analysis into the Name box and specify a password.
System tab: select Create Synonym, Create Table and Create View privileges.
2.
3.
Type in the Query & Analysis Net Service Name for the server. This appears in the Service Naming tree.
4.
5.
Type in the Host Name, this is the Query & Analysis server name.
6.
7.
13
8.
9.
10.
11.
Repeat the process, this time create a Net Service Name for the Product.
12.
14
Log on locally to the Citrix server, ensuring the user has administrator rights.
2.
3.
Note: In a Citrix environment, install Query & Analysis with Application User Profiles disabled and then activate
once the installation is complete. This option can be found on the About tab in Query & Analysis Maintenance.
15
2.
On the local computer insert the Query & Analysis Install CD.
To install Query & Analysis over a network copy the entire contents of the Query & Analysis Install CD to a
network drive.
3.
Start Welcome.exe to open the Query & Analysis installation Welcome screen. It provides access to
installation prerequisite components, supporting documentation and the Query & Analysis installation
executable.
Installation Prerequisites
Query & Analysis requires Microsoft MDAC 2.8, Microsoft .NET Framework 1.1 and 2.0. They are included
with the Query & Analysis install.
MDAC 2.8 should be manually installed. Windows XP SP 2 includes MDAC 2.8. If you attempt to install MDAC
2.8 a message states that it is incompatible with this version of Windows. Click the Cancel button to close
the message.
Microsoft .NET Framework will be automatically installed if not detected.
4.
5.
6.
Start welcome.exe.
8.
Click the Install Query & Analysis link to start the Query & Analysis installation program.
9.
10.
Click Next.
11.
Click the Change button to modify the default installation folder, C:\Program Files\Infor PM QA\
16
12.
13.
14.
15.
Query & Analysis components are listed, click Next. The Connection Wizard is displayed.
17
Custom Installation
With a custom installation Query & Analysis installation settings can be modified. These settings will be reapplied
during a Typical install if Query & Analysis is subsequently re-installed or upgraded.
Destination Folder
Click the Browse button if you wish to modify Query & Analysiss destination folder on the local drive.
If upgrading from a previous Query & Analysis release that was configured to use Application User Profiles, ensure
that this release is installed to the same Query & Analysis folder location.
Select Features
The Select Features dialog box is only displayed during a Custom install.
Help
[Typical installation setting: on]
If enabled, the English Query & Analysis help files are installed to the Query & Analysis help program folder.
By default, C:\Program Files\Infor PM QA\Help.
18
International Help
[Typical installation setting: off]
If enabled, select the default Query & Analysis help files from a list of available languages displayed in a
subsequent step in the installation process. All the international help files are installed. The nominated
default help file is placed in the folder C:\Program Files\Infor PM QA\Help. The
remaining international help files are installed to sub folders C:\Program Files\Infor PM
QA\Help\<Language Code>, where Language Code is a two character abbreviation for the
language, e.g., JP is Japanese.
19
Query & Analysis on Citrix and Terminal Server: For this type of installation Application User Profiles
must be initially disabled during the installation. After installation activate Application User Profiles.
Note: To install Pivot Tables Service on Windows NT, clear the option and refer to the Troubleshooting section.
20
21
The Query & Analysis software and the Query & Analysis centralized database
All new clients should use DSN-less connections to enable Query & Analysis to access the Query & Analysis and
Product databases. A DSN-less connection is recommended over implementing a DSN connection. Unlike ODBC
Data Source Names, DSN-less connection details are stored within the password protected Query & Analysis
product thus ensuring database access settings are not exposed to other applications and users.
The procedure for creating a DSN-less connection is described below.
2.
Click Next.
3.
4.
Microsoft SQL
Oracle
Microsoft Access
DB2
MySQL
22
Microsoft SQL
Data Source Name: create a DSN-less or DSN connection. A DSN-less connection is recommended. In the
Data Source Name box type the SQL server name that holds the Query & Analysis database and precede the
name with an asterisk ( * ). If you prefer to create a DSN connection, click the assist button to start
Microsoft ODBC Data Source Administrator utility.
Database: the name of the Query & Analysis Centralized database on the server.
Time out: the length of time allowed for query to run before it is closed down. The default is zero seconds.
MySQL
Data Source Name: select a DSN connection to the MySQL database. Click the assist button to start
Microsoft ODBC Data Source Administrator utility.
Database: the name of the Query & Analysis Centralized database on the server.
Time out: the length of time allowed for query to run before it is closed down. The default is zero seconds.
DB2
Data Source Name: select a DSN connection to the DB2 database. Click the assist button to start Microsoft
ODBC Data Source Administrator utility.
Time out: the length of time allowed for query to run before it is closed down. The default is zero seconds.
23
Oracle
Data Source Name: create a DSN-less or DSN connection. A DSN-less connection is recommended. In the
Data Source Name box type the Oracle net service name that refers to the Query & Analysis database and
precede the net service name with an asterisk ( * ). If you prefer to create a DSN connection, click the assist
button to start Microsoft ODBC Data Source Administrator utility and use the Microsoft ODBC for Oracle driver.
Time out: the length of time allowed for query to run before it is closed down. The default is zero seconds.
Microsoft Access
File Name: click the assist button and locate the shared network folder in which the LsDatabase.mdb
file resides.
System Database: if required, click the assist button and locate the Access system file (*.mdw).
Time out: the length of time allowed for query to run before it is closed down. The default is zero seconds.
5.
6.
7.
Windows User Name authenticated Windows login details are used when connecting to the Query &
Analysis SQL database. As a valid Window user, the Window user can gain access to the Query &
Analysis database to retrieve Query & Analysis user and profile settings. The Username and Password
boxes are disabled. Ensure the SQL Server has been configured to accept Windows Authentication.
24
8.
Click the Test Connection button, Query & Analysis checks whether it can access the data source and
creates Query & Analysis objects in the Query & Analysis schema. For an Oracle installation, the Query &
Analysis schema is an Oracle synonym schema. If the test is successful the Connection Test Successful
message is displayed and the indicator turns green. If the test fails, the indicator turns red with a white
cross. Correct connection settings and retry the test.
Connection
Not Tested
9.
Test Successful
Test Failed
25
2.
3.
4.
5.
6.
Microsoft SQL
Data Source Name: create a DSN-less or DSN connection. A DSN-less connection is recommended. In the
Data Source Name box type the SQL Server name that holds the Product database and precede the name
with an asterisk ( * ). If you prefer to create a DSN connection, click the assist button to start Microsoft
ODBC Data Source Administrator utility.
Database: the name of the Product database on the server.
Time out: the length of time allowed for query to run before it is closed down. The default is zero seconds.
OEM to ANSI: enable to use older OEM format instead of ANSI. This option ensures that Product databases
which are in languages that have diacritic characters (German, French etc) dont return corrupt characters.
26
Oracle
Data Source Name: create a DSN-less or DSN connection. A DSN-less connection is recommended. In the
Data Source Name box type the Oracle net service name that refers to the Product database and precede the
net service name with an asterisk ( * ). If you prefer to create a DSN connection, click the assist button to
start Microsoft ODBC Data Source Administrator utility and use the Microsoft ODBC for Oracle driver.
Time out: the length of time allowed for query to run before it is closed down. The default is zero seconds.
OEM to ANSI: enable to use older OEM format instead of ANSI. This option ensures that Product databases
which are in languages that have diacritic characters (German, French etc) dont return corrupt characters.
7.
8.
9.
Windows User Name authenticated Windows login details are used when connecting to the Product
SQL database. The Username and Password boxes are disabled. Configure SQL Server to accept
Windows Authentication. Windows Authentication is not support by all DataLinks. See your DataLink
documentation.
27
10.
Click the Test Connection button, Query & Analysis checks whether it can access the data source. If
successful the Connection Test Successful message is displayed and the indicator turns green. If the test
fails, the indicator turns red with a white cross, correct connection settings and retry the test.
11.
12.
13.
Click the Save button on the Client Setup dialog box. Query & Analysis installation is complete. It is not
necessary to reboot the computer.
28
Security Overview
Application Security
User
Data Source
(Executive, XL, Word)
(Alert)
A User is
assigned to a Profile
Profile
A Profile is
assigned to a
Product User ID
Data Source
Integrated Security
Windows User /
Domain
Browser Security
Remote Users
29
For Product users, the wizard creates Query & Analysis users, Query & Analysis profiles and maps these Profiles
to their relevant Product User ID. For Windows users, by implementing Integrated Security, on starting Query &
Analysis applications Query & Analysis users are automatically logged on since user authentication has already
been conducted by the Windows logon details effectively providing single sign-on functionality. The Wizard also
allows you to set the default password for all Query & Analysis users.
To create Query & Analysis Users with the User Wizard:
1.
In Query & Analysis Setup, on the Users menu, click User Wizard.
2.
User Names. If enabled, the User Names will be created from the Product user names.
Map directly to users. If enabled, maps a Query & Analysis user to a Product User ID.
Remote Users. If enabled, creates Remote Users for Executive (Browser) and eAlert (Browser) from
the imported Product users. You may prefer to create and allocate remote users manually as a
Remote User does not have to have a one on one relationship to a Query & Analysis User. Remote
Users can be created or changed at a later point time.
Select a Windows Domain from the Domain list. Query & Analysis searches this Domain in order to
create Query & Analysis users.
3.
4.
By default the Guest profile is assigned to all Query & Analysis users. Click the assist button to nominate an
alternative Query & Analysis profile. The Query & Analysis profile determines which features are activated in
Query & Analysis applications and the Product. A Query & Analysis user, as member of a Query & Analysis
profile, inherits the features activated within the profile.
5.
Select User Security if required. This option provides additional Product specific security by mapping a
Query & Analysis user profile to a Product user retrieved from the data source. A Query & Analysis user, as
30
member of a Query & Analysis profile, will have the same permissions as the mapped Product user when
accessing the Product database.
6.
7.
The following default password options can be set for all Query & Analysis users being created:
8.
Passwords are mandatory for all users. Updated passwords cannot be blank.
31
Remote Logon access is requested prior to Query & Analysis Logon details; so both logon details must be
correct in order to start the Query & Analysis browser product. Remote Security is also used to determine
which Query & Analysis users have administrator rights to configure which server folders can be accessed
by Query & Analysis browser product users. A Remote User is mandatory, but can be set to the system
reserved user Default to skip to the logon process,
9.
Type in Remote Security password and add a Group with administrator access. The Administrator will be able
to set which server folders can be accessed by Remote Users.
10.
32
11.
12.
Click the Finish button to create the Query & Analysis users. The users are listed on the User Security tab.
Note: The users demo, guest and system are default Query & Analysis users with a Guest profile.
33
2.
Enter the System user ID and password. The password is blank during initial configuration. Click OK.
3.
On the Profiles menu, click Add. The User Profiles dialog box is displayed.
4.
5.
6.
Click the Help button for further details on each of the product and client application settings.
7.
8.
On the Users menu, click Add. The Add Users dialog box is displayed.
9.
In the User Name box, enter the Query & Analysis users name.
10.
In the Description box, enter a description for the Query & Analysis user.
The Query & Analysis password can be configured manually on the Details tab or authorized by Windows
logon by completing the Integrated Security tab.
11.
Click the Help button for further details on setting Query & Analysis user passwords.
12.
13.
14.
34
15.
16.
35
Create a new Query & Analysis user with exactly the same name as a Windows user.
Map an existing Query & Analysis user to a Windows user or Windows Group. The names of the Query &
Analysis user and Windows user can differ.
Note: The Windows user is mapped to Query & Analysis user or profile. This affects all Products, for example if a
site had Query & Analysis for SunSystems and Query & Analysis for Micros Fidelio installed then the same
Windows user and Query & Analysis user are mapped (remembering the Query & Analysis user can be different to
a SunSystems user). The Query & Analysis user is then mapped to user within the different products. For
example - Windows user mydomain/myname is mapped to Query & Analysis user guest then mapped to PKP in
SunSystems 5 and PeterP in Micros Fidelio.
To create a new Query & Analysis user with a Windows user name:
1.
2.
3.
In the User Name box, type in the Domain and Windows user name, The syntax is
<Domain>\<Windows User>. Unlike mapping an existing Query & Analysis user, there is no need
to also allocate a Windows user to this Query & Analysis user on the Integrated Security tab.
4.
5.
36
2.
3.
4.
If you know the domain and user you wish to allocate, right-click the Allocate Users pane and type in
the <Domain>\<Windows User> directly into the dialog box.
Search mode which searches for names or groups specified in the Find box for the selected Domain.
The results populate the User Names list.
Browse mode which automatically populates the User Names list with all names or groups held in the
selected Domain.
In a domain with a large number of users apply Browse mode. Search mode requires the nominated user in
the Find box to be pattern matched against every user in the domain. This process can be time consuming
and is slower than using Browse mode to locate users
37
5.
Select the Domain Name & User Name to be assigned to the selected Query & Analysis User then click the
button.
6.
38
2.
3.
In the Open dialog box, navigate to the location of the supplied Query & Analysis Serialization file. The file will
have been supplied simultaneously with your software and will have a .lic extension.
Note: The Query & Analysis Licensee No. is, by default, incorporated as part of the licence file name (*.lic).
39
4.
Select the *.lic file that has been sent to you and click the Open button.
Product name displayed in pink in the Serialization grid indicates that there were licensing details for this
product included in the file, however, the DataLink for the product is not on the client machine.
5.
6.
Click the assist button to browse for the Product key file. This file is determined by the Product DataLink.
7.
2.
3.
In User Allocation window, select an application under the Product heading. For example, Query & Analysis
XL..
4.
40
5.
Click the right arrow button. The user is transferred to the Allocated Users list.
9.
10.
41
11.
12.
Restart Excel.
Macro Security
The first time Query & Analysis XL is used the Security Warning dialog box appears.
13.
Select Always trust macros from this publisher and click the Enable Macros button.
Depending on your Microsoft Office version it may be necessary to perform additional steps to permit
macros to run.
For Query & Analysis XL, the Excel security settings should be configured as follows:
These settings should also be applied in Microsoft Word for Query & Analysis Word. For detailed instructions
please refer to Query & Analysis and Microsoft Office Security section.
Logging On
14.
15.
42
16.
17.
If supplied, open a report pack. The report pack can be found in the Demonstration Reports program group
(C:\Program Files\Infor PM QA\Demo).
18.
19.
Note: Drilldown and Hierarchy Designer must initially be run as Windows Administrator to complete the
registration of the Active X control. A standard Windows user now has sufficient privileges to use Query & Analysis.
If a report is generated, Query & Analysis has been successfully installed.
Please refer to the Query & Analysis online help on how to configure Query & Analysis users, profiles and
assign passwords.
43
2.
Click the Groups tab. Confirm the Query & Analysis Users group is listed.
3.
44
4.
On the Edit menu, click Add User.Alternatively, edit an existing SU users details.
5.
6.
7.
Select the Query & Analysis Users option and click OK.
8.
In the left pane, click Query & Analysis. The Map to User list appears.
9.
Select the Query & Analysis user from the list. In this example, SU user Tim (Query & Analysis) is mapped
to the Query & Analysis user Tim returned from the Query & Analysis Centralized database.
45
10.
Click OK.
11.
12.
Repeat the above steps for new SU users and mappings to Query & Analysis users.
13.
Click OK.
14.
Retest Query & Analysis using Global Security logon details to logon to Query & Analysis XL.
2.
3.
4.
46
Silent installation.
Silent Installation
A silent installation will install Query & Analysis with pre-defined custom settings so Query & Analysis can
installed unattended. Silent installation mode is invoked by including parameters at the command line on running
the setup file.
Parameters
The syntax is as follows:
D:\setup.exe /s /v /qn INSTALLDIR=D:\Destination
/s silent install mode.
/v - pass parameters into the installer .
/qn - disable installation messages (totally silent).
The parameter options are listed below:
Property
Comment
OPTDEFAULTLANG=XX
OPTENABLEPROF=yes/no
OPTLOADSERDUCT=yes/no
OPTLOADWORD=yes/no
OPTLOADXL=yes/no
INSTALLDIR=XX
47
Connections Details
A silent installation does not fully configure Query & Analysis. Two optional files should be used:
Conndetails.txt
DSN.reg
The files must reside in the Query & Analysis installation folder.
Conndetails.txt is used to configure the connection settings for Query & Analysis without the need for user
intervention. The text file contains a connections list. Each line is one connection, and each connection is a comma
separated list of variables defining the connection. The format is as follows:
<DataLinkCode>, <ProductName>, <Alias>, <Enabled>, <Visible>, <DSN>,
<Database>, <UserID>, <Password>,<Query Timeout>,
<SerialModuleIndex>, <Engine>
For example:
DataLinkCode
ProductName
Alias
Enabled ?
Visible ?
DSN
SS4,
SunSystems 426,
SunAlias,
YES,
YES,
SunDSN,
MAXIMO,
Maximo,
MaximoAlias,
YES,
YES,
MaximoDSN,
Database
UserID
Password
Timeout
SerialModIndex
Engine
SunDatabase,
SunUserID,
SunPassWord,
30,
,,
MS-SQL
,,
MaximoUser,
MaximoPassword,
30,
,,
ORACLE
Where:
DataLink Code : the code of the DataLink, for example SS5, SS4, APP.
Database : database name. This can be left blank if the database is set in the DSN connection.
48
Password : connection password. If a password is enabled, and is left blank in this file, the user is prompted
for a password
Query timeout : time before a query times out. If left blank the default time is used.
Engine : the database connection type, MS-SQL, FOXPRO, ORACLE, MS-OLAP, ACCESS, DBASE, SYBASE, CACHE,
CONCORDE, DB2, BTRIEVE, RETRIEVE, PLUGIN, MICROFOCUS, XL, TEXT, MISAG.
Dsn.reg contains ODBC connection details to be installed on the client machine during the installation. This is
useful to set up system database connections for the DataLinks that are to be installed with Query & Analysis.
The easiest way to create this file is to create the DSNs in ODBC Administrator, then export the keys:
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\<dsn name>
These files can be used in a typical, custom or silent Query & Analysis install.
49
Installation version.
Installation sequence.
On the local computer insert the Query & Analysis Install CD. The Query & Analysis Install CD contents are
listed.
2.
3.
4.
Continue with the remainder of the Query & Analysis installation steps.
50
The Query & Analysis XL Add-in can be included or removed from Microsoft Excel using the Configure Microsoft
Office utility. The utility can be accessed from either Query & Analysis Maintenance or Query & Analysis Setup.
Alternatively, if you wish to manually include Query & Analysis XL from within Excel:
1.
Start Microsoft Excel. If the Query & Analysis menu appears, the Query & Analysis Add-In has already been
installed. If not, continue to step 2.
2.
3.
Locate the LsAgXLB.xla file. By default the file is placed in the C:\Program Files\Infor PM QA folder.
4.
Select the file then click OK. Query & Analysis appears in the Add-Ins list.
5.
Click OK. The Query & Analysis pre-logon menu is included in the Excel menu bar.
To remove Query & Analysis XL:
Clear the Microsoft Excel option in the Configure Microsoft Office utility.
Select Tools, Add-Ins on the Excel menu bar, then clear the Query & Analysis check box in the Add-Ins
list.
Note: When you add a Query & Analysis menu, Query & Analysis XL resets Excel calculations to manual. You can
now change entries in your worksheet without causing Excel to recalculate automatically.
2.
3.
4.
5.
Click the Change Source button and select the LsAgXLB.xla file in the Query & Analysis program folder.
6.
51
52
The Query & Analysis Word Add-in can be included or removed from Microsoft Word using the Configure Microsoft
Office utility. The utility can be accessed from either Query & Analysis Maintenance or Query & Analysis Setup.
Alternatively, if you wish to manually include Query & Analysis Word from within Word:
1.
Start Microsoft Word. If the Query & Analysis Word menu appears, the Query & Analysis Word Add-In has
already been installed. If not, continue to step 2.
2.
3.
Click the Add button and locate the LsAgoWrd.dot file. By default the file is placed in the C:\Program
Files\Query & Analysis folder.
4.
Select the file name then click OK. The Query & Analysis Word Add-In appears in the window.
5.
Click OK. The Query & Analysis Word pre-logon menu is appended to the Word menu bar.
Query & Analysis Word can be removed by:
Selecting Tools, Templates and Add-Ins on the Word menu bar, then clearing the LsAgoWrd.dot check
box in the Add-Ins list.
53
Using NetEnterprise, Query & Analysis reports are no longer restricted to Query & Analysis XL, Executive or Word
users. Interested parties, such as employees, shareholders and potential clients can view Query & Analysis
reports using a web browser. Companies can quickly disseminate key performance information into the market
place over the internet.
Live Refresh
NetEnterprise supports the live refresh and recalculation of Excel worksheets. This enables users to perform basic
calculations and update filter criteria that define XL query definitions in a published page. The new values are
displayed dynamically, in the user's Web browser. EIF Services is built on the Microsoft .NET Framework and
provides access to DataLinks through a Web Service on Internet Information Services (IIS) or through a .NET Data
Provider, written especially for reporting over DataLink technology. The optional Live Refresh feature requires the
installation of EIF Services prior to the installation of NetEnterprise Server.
Configuration
The following diagram depicts a typical Query & Analysis NetEnterprise configuration.
54
By installing Query & Analysis, the client PC already has the Query & Analysis NetEnterprise Manager application.
NetEnterprise Manager is an application that allows a Query & Analysis user to control and facilitate the publishing
of all types of Query & Analysis reports to the NetEnterprise Server (web site). The NetEnterprise Server is a
separate installation on the web server, during which connection details are set to the Query & Analysis
centralized database for that web server.
Microsoft Internet Explorerc users viewing NetEnterprise Server pages should set their browser to automatically
check for new versions of stored pages.
The Query & Analysis centralized database must include the default IIS web login with the permissions datareader,
datawriter, ddladmin and public:
Windows 2000 or Windows XP Grant the ASPNET user login the above permissions on the Query &
Analysis database.
NetEnterprise Manager
Query & Analysis NetEnterprise Manager is an easy-to-use, robust file management system designed for Query &
Analysis users to take control of their everyday Microsoft Office documents and workbook files. NetEnterprise
Manager allows storage and publication of all Query & Analysis report types as HTML pages ready for the internet.
Supported files include PDF and PowerPoint files can also be stored and published using NetEnterprise.
Query & Analysis NetEnterprise Manager is installed on client PCs in the Query & Analysis installation, and as with
other Query & Analysis applications, will need to be serialized.
NetEnterprise Server
The Query & Analysis NetEnterprise Server component takes published HTML pages created by NetEnterprise
Manager and forwards them to a web portal server.
Query & Analysis NetEnterprise Server is a separate installation and is configured to connect to the Query &
Analysis Centralized Database. The database can be Microsoft SQL, MySQL or Oracle. NetEnterprise does not
support Microsoft Access. Microsoft SQL 2003 is recommended for running Live Refresh.
Query & Analysis NetEnterprise Server should be installed on a web server running IIS with FrontPage 2000 Server
Extensions. To confirm whether FrontPage 2000 Server Extensions has been installed, open Internet Information
Services (IIS) in Windows Component Wizard and click the Details button. The option should be selected. See
Internet Information Services if not listed.
55
2.
Install EIF Services on a server, such as the Web server, if you intend to use the Live Refresh feature. EIF
Services connects to the same Product and Query & Analysis databases. For detailed instructions please
refer to EIF Services Installation Guide.
3.
Start Welcome.exe from the Query & Analysis Installation CD or if the CD has been copied to a network
location, from that location
4.
5.
6.
Complete
Custom change the default installation folder / disable NetEnterprise & Token server installation.
56
8.
Connection Details
Query & Analysis Database Type: SQL Server / Oracle / MySQL.
Connection Details: for SQL, type in the server name and database. For Oracle, type in the service
name.
Trusted Security: if enabled, connect via Windows Authentication. If disabled, connect via SQL
authentication. Windows Authentication is recommended when implementing the Live Refresh
feature.
Username and Password: Query & Analysis centralized database logon details.
Click the Test button to verify whether Query & Analysis database access details are correct.
Languages
Sets languages made available during NetEnterprise web server logon. The default language listed on
the logon page can be nominated.
57
Server Options
Logon mode: select Query & Analysis logon to use Query & Analysis logon details. Select Global
logon to use Systems Union Global Logon user details.
Session time out: total time the user can view a published page without any activity before being
logged off.
Log Access to Query & Analysis: submit logon activity to NetEnterprise published pages in the
Query & Analysis log. See Query & Analysis Setup.
Web Reporting Options
The Web Reporting options aim to maximize system performance in delivering updated pages to browsers.
Pages are initially stored in memory, and if not requested, placed in a bit array (serialized), then
compressed and finally stored on disk. The settings determine how long before NetEnterprise is required to
wait before proceeding to the next stage and so minimizing the amount of memory required.
EIF Services URL: type in the URL address. This will enable the Live Refresh feature. The address will
be http://EIFServer/Agora.WS/Serducts.asmx, where EIFServer is the name of the server where EIF
Services resides.
Connection Pool Size: number of available connection in the pool. The larger pool the more memory
is required. If the pool size it too small an available connection might take longer to find.
Idle Time: total time in seconds of inactivity before one serialization iteration occurs. By default, this
is set to 30 seconds.
Allow Serialization: total iterations before the pages are placed in bit array memory (serialized). By
default, this is set to 10 iterations. Hence, 300 seconds of inactivity is required before serialization
occurs.
Allow Compression: total iterations before serialized pages are compressed. By default, this is set to
10 iterations. Hence, 600 seconds of inactivity is required before compression occurs.
Allow Disk Persistence: total iterations before compressed pages are stored on disk. By default, this
is set to 10 iterations. Hence, 900 seconds of inactivity is required before compression occurs.
Working Directory: compressed pages are stored in the nominated folder location.
58
BIRT
BIRT Web Viewer Application URL: the URL address of the BIRT Web Viewer on Tomcat.
BIRT File Upload Web Service URL: the URL address of the BIRT File Upload Web Service on Tomcat.
BIRT Temporary Folder Name: the name of the temporary sub folder in the BIRT web service folder.
Show Render Frameset: displays rendered frames for BIRT reports.
9.
Click OK.
10.
Click the Finish button. Query & Analysis NetEnterprise installation is complete.
The NetEnterprise and Token XML configuration files are updated. The XML configuration files (config.xml)
are located in the NetEnterprise and Token folders. Query & Analysis NetEnterprise server and Token server
are listed as default web sites in the Internet Information Services utility. See Control Panel, Administrative
Tools, Internet Information Services.
Note: Perform an IISreset when changes are made to the XML configuration files or within the Setup and
Maintenance applications.
ASP.Net
59
In the Windows firewall, port 80 should be left open to enable remote browsers to access the NetEnterprise IIS web
site.
Oracle
When connecting to an Oracle database, the minimum version of Oracle 8.1.7 client (Oracle 8i) must be installed
on the IIS Server.
The Windows 2003 accounts must have read access to the Oracle home folder and sub-folders, for example for
Oracle 9i this is C:\oracle\ora92. The accounts are as follows:
IIS_WPG group
ASPNET account
Microsoft SharePoint
In addition to Internet Explorer users being able to access Query & Analysis reports via NetEnterprise directly,
such published reports can be display in Web Part portals within Microsoft Sharepoint. The NetEnterprise Web Part
component can be installed on a Sharepoint server. It provides a mechanism for published reports to be displayed
in Sharepoint and for the correct user authentication details to be pass from Sharepoint to NetEnterprise.
The Agora.Portal.NetEnterpriseWebPart.msi file should be installed on the Microsoft
SharePoint Portal Server:
To install NetEnterprise Web Part:
1.
2.
3.
4.
5.
60
as an eAlert client and server-based solution, referred to as Query & Analysis Alert Server.
Query & Analysis Alert uses the Query & Analysis Alert Editor application included with a basic Query & Analysis
installation and so does not require further configuration. Query & Analysis Alert Server, based on the Query &
Analysis eAlert thin client application, requires additional configuration steps detailed in this section. Query &
Analysis eAlert (Browser) builds on a Query & Analysis Alert Server installation and is covered later in this
document.
61
Configuration
The following diagram depicts a typical Query & Analysis Alert Server configuration.
Query & Analysis Alert
Server
(high specification
standard PC)
Query & Analysis
Alert Manager (service or application)
Alert Listener (service or application)
Microsoft Office
Oracle client *
Database
Server
TCP/IP
Product
DB
Query &
Analysis
DB
LsAgEg10.mdb
Local Database
Override (optional)
A typical Query & Analysis Alert Server configuration consists of the following key components:
Query & Analysis eAlert clients These are the end user PCs with Query & Analysis installed as normal.
One of the programs installed with Query & Analysis is eAlert. It allows an end user to schedule the
generation of Query & Analysis reports (reports and other tasks run via Alert are referred to as Alert Tasks).
During Query & Analysis eAlert client user logon, user details checking and authorisation is performed by
Query & Analysis Alert Server.
Query & Analysis Alert Server A high specification PC or dedicated medium to high end server, with the
Query & Analysis software, Microsoft Office and the Oracle client installed (Oracle systems only). The server
will also be running the Query & Analysis Alert Listener and Manager.
Query & Analysis Alert Listener The Query & Analysis Alert Listener listens on a specified TCP/IP port
on the Alert Server machine for incoming requests from eAlert client users for the lodgement, execution or
scheduling of tasks. Received requests are loaded into the Local Database on the Alert Server.
62
Query & Analysis Alert Manager This program runs on the Alert Server . Alert Manager processes and
executes scheduled Alert tasks. The Alert Manager must be running for tasks to be executed as scheduled
on the server.
Query & Analysis Alert Services By default, the Listener and Manager run as applications on the Alert
Server. For each to continue running, a Windows User must be logged on the Alert Server. In environments
where the Alert Server will be unattended or administered remotely, this may not be feasible or secure.
Query & Analysis Alert Services allows installation of Windows services to facilitate the running of Listener
and Manager in such Alert Server environments.
Local Settings Database This database is used to store Alert Tasks issued by eAlert clients. By default
tasks are stored in the LsAgEg10.mdb database file on individual eAlert clients and the Alert Server. This
scenario is useful where each eAlert user only requires access to their tasks and no task sharing is required.
Please note that in environments where users must share tasks, the eAlert Local Database Override Option allows
all eAlert clients to point at the same Local Settings database. In this case the database would be held on a shared
and mapped network drive.
2.
3.
4.
Query & Analysis Installation - Step 10: Macro Security and Testing Query & Analysis.
5.
Start Query & Analysis Manager and Query & Analysis Listener applications in the Alert program group to
enter the configuration settings.
6.
Confirm the Query & Analysis Manager and Query & Analysis Listener process are running in the Windows
task bar.
63
7.
Right-click the Query & Analysis Listener icon, and select Options.
8.
9.
Note down the Alert Server name, IP address and port number. By default the port number is set to 6666, but
can be modified by clicking the Edit button.
10.
Click the Drives tab. Available mapped drives are listed. Checked drives will be those to which end users can
retrieve and save reports being scheduled for execution in Alert tasks. In Alert, to specify a file used in an
Alert process the UNC path (i.e., \\file-srvr\Common\Alert\MyFile.xls) can be typed in or a mapped drive (i.e.,
L:\Alert\Myfile.xls) defined here can be selected.
11.
Click the Edit button to clear or enable drives that should be made accessible to eAlert clients connecting to
the Alert Server.
Note: Depending on where Listener and Manager are run as applications or services, a Windows account will
be selected which either logs onto Windows to run the applications or which provides an account for the
64
services to run under. For Alert to be able to retrieve and save files specified in users Tasks, this Windows
account must have write access to the drives selected above. Please consult your Microsoft Windows
documentation for information on granting this access.
The Windows account that is logged in to run Alert applications must have the same mapping to network
shared drives that Query & Analysis eAlert users see. That is, all drive letter / network share settings should
be equivalent for both the Windows account and eAlert user. This ensures that Alert Listener and Manager
can save and retrieve reports from the locations that end users expect.
When Alert Services are in use the Services account needs to have access to the drives as stated above.
Drive mappings are not relevant as they are converted to UNC paths during initial configuration of Alert
Listener.
12.
The Session tab sets the maximum number of eAlert client sessions that can connect to the Alert Server.
13.
14.
15.
16.
17.
18.
Type in a Query & Analysis user ID and Password to logon to Alert Manager. If necessary create a Query &
Analysis user and allocate to Query & Analysis Alert in Query & Analysis Setup.
19.
20.
Click OK.
21.
22.
To test the automatic logon is working, start Query & Analysis Alert Manager.
65
Alert Applications
The procedure below configures Query & Analysis Manager and Query & Analysis Listener to automatically start
and logon with a preset User ID on the Query & Analysis Alert Server. Unlike using Alert Services, it is necessary to
logon to Microsoft Windows before the applications start.
1.
In the Windows Startup folder, create shortcuts to Query & Analysis Alert Manager and Query & Analysis
Listener application files. Typically these are found in:
C:\Program Files\Infor PM QA\Listener.exe
C:\Program Files\Infor PM QA\Manager.exe
2.
3.
Logon to Microsoft Windows and confirm the Alert Manager and Alert Listener processes start.
Alert Services
Query & Analysis Alert Services allows Alert Manager and Listener to run as Windows Services on the Query &
Analysis Alert Server (Service Mode). This is an alternative to running Alert Manager and Listener in Windows
Application Mode, which requires a Windows user to logon to the Query & Analysis Alert Server. Unlike using
executable files to operate Alert processes, the use of Services means that they start automatically without the
need for a Query & Analysis user to manually logon to Windows.
Query & Analysis Alert Services is useful in environments where the Query & Analysis Alert Server must run
unattended and Query & Analysis Alert Manager and Listener must have a high level of availability, even after the
server has been restarted or taken off line for a period of time.
A separate executable file, AlertServices\Setup.exe, is provided with the Query & Analysis
installation files. The Query & Analysis Alert Services installation file creates Alert Manager and Listener Services
for Query & Analysis eAlert and Query & Analysis eAlert (Browser).
Query & Analysis Alert Services settings are configured by stopping the services in Windows. Any configuration of
settings (ports, drives, sessions etc.) is then performed within the Query & Analysis Alert Listener and Manager
applications. Once changes are saved, the applications are exited and the services can be restarted to utilise the
66
new settings. Details of configuring Listener and Manager settings can be found in earlier sections of this guide
and in the Help for those applications.
To install Query & Analysis Alert Services:
1.
Double-click the installation file Setup.exe located in the AlertServices folder on the Query & Analysis CD.
InstallShield Wizard starts.
2.
3.
For the Query & Analysis Listener service, type in the Windows logon username and password. The user
name should include the Domain so that the format is <DOMAIN NAME>\<Username>. Click OK.
The file LsAgAlListenerService.exe is installed to C:\Windows\System32
4.
For the Query & Analysis Alert Manager service, type in the Windows logon username and password. The
user name should include the Domain so that the format is <DOMAIN NAME>\<Username>. Click
OK.
The file LsAgAlManagerService.exe is installed to C:\Windows\System32
5.
67
The new services are listed in Windows Computer Management configuration application.
Should you wish to remove Query & Analysis Alert Services, use Add or Remove Programs in Control Panel.
As stated earlier, changes in Listener and Manager settings are facilitated by stopping the services, making
settings changes in the Listener and Manager applications as required, stopping the applications and then
restarting the services.
Start Query & Analysis eAlert in the Alert program group. The first time an eAlert client attempts to connect to
the Alert Server, the Server Setup dialog box is displayed.
2.
68
Query & Analysis eAlert Local Database Override by default, eAlert clients save Alert Tasks and details
to their Local Settings Database. To facilitate sharing Alert task information with other Query & Analysis
eAlert users a single settings database should be used.
To do this copy the LsAgEg10.mdb file from a local machine to a network drive that is accessible by all
eAlert clients. The file is located in the folder C:\Program Files\Infor PM QA\Settings.
Once the Override Database is in place, click the assist button and select the file on the network drive.
3.
4.
Select the Alert Server from the list and click OK.
Query & Analysis eAlert connects to the Query & Analysis Alert Server.
Logon to Query & Analysis eAlert on the first eAlert client machine that was configured above.
2.
On the Options menu, click Servers. The Servers dialog box is displayed.
3.
4.
5.
Type in a Server Backup File name (*.sbf) and shared folder location.
69
6.
7.
Quit eAlert.
8.
9.
10.
11.
Locate the Server Backup File previously saved and click OK.
The Alert Server details are loaded into the eAlert client.
E-mail Settings
Query & Analysis Alert supports e-mailing workbooks; this must be configured on each of the Query & Analysis
clients and the Query & Analysis Alert server. Outlook or a similar product must be installed and configured to
support MAPI. Alternatively, SMTP protocol can be used to send e-mails.
For SMTP protocol ensure that port 25 can be accessed and is not blocked by virus protection software.
1.
2.
3.
4.
70
MAPI: To connect to an Outlook profile using SMTP/POP3 mode, such as a Hotmail account, the reply-to
address must be set in the SMTP options for the e-mail test to work.
Lotus: Query & Analysis supports Lotus Notes 5, but does not support Lotus Notes 6.
5.
Click the Test button. A test e-mail is sent to the e-mail address.
6.
71
Query & Analysis eAlert (Browser) is based on the Query & Analysis Alert Server product providing many of the
functions of Query & Analysis eAlert but as a web-based client.
Note: To use Query & Analysis eAlert (Browser), first start Query & Analysis Alert Manager on the Web server
before running Internet Explorer on the client PC.
In Query & Analysis Alert, when a Task is executed it spawns the executable AgSExe.exe responsible for
controlling Alert processing.
Server Requirements
The server requires the following to use Query & Analysis eAlert (Browser):
Query & Analysis Alert Server installed and configured on the server running IIS.
Note: Query & Analysis eAlert (Browser) is not supported on Windows NT 4 Server and IIS 4.0.
Prerequisites
Query & Analysis eAlert (Browser) requires the following prerequisites:
ASPNET has full access to the Query & Analysis settings folder, typically C:\Program
Files\Infor PM QA\Settings.
Application User Profiles disabled. This is performed during the installation of eAlert (Browser). Personal
settings may need to be relocated from the profile folder to the Query & Analysis program settings folder if
Application User Profiles has been employed up until this point. Copy the contents of the folder
C:\Documents and Settings\<USER>\Application
Data\Lasata\Agora\Settings to C:\Program Files\Infor PM QA\Settings,
where USER is the Windows logon ID.
In Query & Analysis Setup, users have been allocated to Query & Analysis Alert.
72
Configuration
The following diagram depicts a typical Query & Analysis eAlert (Browser) configuration.
A typical Query & Analysis Alert Server configuration consists of the following key components:
Query & Analysis eAlert (Browser) clients These are the end user PCs with Internet Explorer. The eAlert
(Browser) pages displayed in the browser are generated by the Query & Analysis Alert Server running IIS.
The Query & Analysis eAlert (Browser) software is installed on the Query & Analysis Alert Server. Through the
browser interface the end user can issue and schedule Query & Analysis reports (reports and other tasks
run via Alert are referred to as Alert Tasks).
Query & Analysis Alert Server A high specification PC or dedicated medium to high end server, with the
Query & Analysis software, Query & Analysis eAlert (Browser) software, Microsoft Office, IIS and the Oracle
client installed (Oracle systems only). The server will also be running the Query & Analysis Alert Listener and
Manager.
Query & Analysis Alert Listener The Query & Analysis Alert Listener listens on a specified TCP/IP port
on the Alert Server machine for incoming requests from eAlert (Browser) users for the lodgement, execution
or scheduling of tasks. Received requests are loaded into the Local Database on the Alert Server.
73
Query & Analysis Alert Manager This program runs on the Alert Server and processes and executes
scheduled Alert tasks. The Alert Manager must be running for tasks to be executed as scheduled on the
server.
Query & Analysis Alert Services By default, the Listener and Manager run as applications on the Alert
Server. For each to continue running, a Windows User must be logged on the Alert Server. In environments
where the Alert Server will be unattended or administered remotely, this may not be feasible or secure.
Query & Analysis Alert Services allows installation of Windows services to facilitate the running of Listener
and Manager in such Alert Server environments.
ASP.NET Access
The following configuration steps are required to allow Query & Analysis eAlert (Browser) to function on Windows
platforms using the NTFS file system. This involves granting ASP.NET full access to the Query & Analysis Settings
folder on the server running the Listener and Manager used by Query & Analysis eAlert (Browser). The user must
have administrator rights.
3.
In Windows Explorer, locate the Query & Analysis setting folder. By default,
C:\Program Files\Infor PM QA\Settings
4.
5.
6.
7.
Click the Locations button and select the local machine name.
74
8.
Type in ASPNET.
9.
Click the Check Names button. The object name is resolved with the server name.
10.
Click OK.
11.
12.
For Windows 2003, enable web extensions. See Browser Products and Microsoft Windows 2003 Security in
the Troubleshooting section.
Remote Users
13.
In Query & Analysis Setup, add Remote Users. Remote Users provide an additional level of security for
Query & Analysis browser products logging on over the internet and determining which network folders can
be accessed.
75
On the Query & Analysis Alert Server, ensure all Query & Analysis programs are shutdown before executing
the eAlert (Browser) setup file.
15.
Run the eAlert (Browser) installation program by clicking the Install Query & Analysis eAlert Browser links
on the Query & Analysis installation Welcome screens.
16.
The Query & Analysis eAlert (Browser) Setup Wizard is displayed. Click Next to continue.
17.
18.
Click Next.
19.
20.
22.
Services confirm the Query & Analysis Listener and Query & Analysis Manager services have
started.
Applications - on the server start Query & Analysis Alert Manager, which starts the LsNetCom.exe
listener process.
On the client PC open Internet Explorer and enter the URL, i.e.,
http://<Query & Analysis Alert Server name>/Query &
Analysis_eAlert
23.
24.
Enter Query & Analysis Remote Logon User ID details and password.
If a blank page is displayed, ASP.NET does not have full access permissions to the Query & Analysis settings
folder. See ASP.NET Access.
25.
Click OK.
76
26.
27.
28.
29.
Note: If you have confirmed Alert Manager is running and experience problems accessing the web server then
restart IIS. Please see the Troubleshooting section. If you are still unable to launch eAlert (Browser), first confirm
eAlert (thin) client operates with the Listener and Manager as applications. Then proceed to implement eAlert client
with Alert Services, and if successful, run eAlert (Browser).
77
Query & Analysis Executive (Browser) is a web-based version of the Query & Analysis Executive application
(Query mode) that operates using Java.
During installation the Executive (Browser) communication port number can be set, the default port is 7660.
Determine a free port number prior to installation. Once Executive (Browser) has been installed the port number
can not be modified. Ensure Application User Profiles is disabled in Query & Analysis Maintenance.
Citrix users should use Query & Analysis Executive rather than Query & Analysis Executive (Browser). Query &
Analysis Executive (Browser) does not support Java Web Start mode in a Citrix environment.
Note: Executive (Browser) can not be upgraded. Uninstall Executive (Browser) from the server and then install the
latest release. See Uninstalling Browser Products.
Server Requirements
The server requires the following to use Query & Analysis Executive (Browser):
NTFS volume.
Query & Analysis installed and configured on the server running IIS.
Note: Query & Analysis Executive (Browser) is not supported on Windows NT 4 Server and IIS 4.0.
Prerequisites
The following prerequisites are required for Query & Analysis Executive (Browser). They can be accessed by
clicking the Installation Prerequisites link on the Query & Analysis installation Welcome screen:
Application User Profiles is disabled during the installation of Executive (Browser). Personal settings may
need to be relocated from the Windows users profile folder to the Query & Analysis program settings folder
if Application User Profiles has been employed up until this point. Copy the contents of the folder
C:\Documents and Settings\<USER>\Application
Data\Lasata\Agora\Settings to C:\Program Files\Infor PM QA\Settings,
where USER is the Windows logon ID.
78
In Query & Analysis Setup, Query & Analysis users intending to use Query & Analysis Executive (Browser)
are allocated to Query & Analysis Executive. Allocating the user to Executive automatically grants the user
access to Executive (Browser).
Ports
Query & Analysis Executive communicates with the web server via a series of ports. If a firewall has been activated
ensure the following ports are open. In Windows XP SP2, a firewall is automatically activated. See Windows Control
Panel, Network connections (Advanced tab).
The Java applet communication port to the server is set during installation. If unavailable, the number is
incremented by one until a free port is found. Checking stops after a further nine ports. Ports currently used
by other applications will be unavailable.
Port 80 (HTTP).
Ports 7670 and 7570 for internal traffic on the local machine.
79
Configuration
The following diagram depicts a typical Query & Analysis Executive (Browser) configuration.
A typical Query & Analysis Executive (Browser) configuration consists of the following key components:
Query & Analysis Executive (Browser) clients These are the end user PCs with Internet Explorer. The
Executive (Browser) pages displayed in the browser are generated by the Query & Analysis Executive
(Browser) Server running IIS. Query & Analysis Executive (Browser) software is installed on the Query &
Analysis Server. Through the browser interface the end user can open and extract workbook. Drill paths
stored in the workbook can be replayed.
Query & Analysis Executive (Browser) Server A high specification PC or dedicated medium to high end
server, with the Query & Analysis software, Query & Analysis Executive (Browser) software, IIS and the
Oracle client installed (Oracle systems only). The server runs the Executive Router and Listener as either
Windows applications or Services.
Query & Analysis Executive (Browser) Listener The Executive Listener listens on a specified TCP/IP
port on the Executive Server machine for incoming requests from Executive (Browser), such as extract the
workbook or replay a Drill Path.
80
Query & Analysis Executive (Browser) Router This program runs on the Executive Server. The Executive
Router receives incoming connections from Executive (Browser) clients and forwards the traffic to the
Executive Listener process.
Service mode: creates Windows services. The services start without the need to logon to Windows.
Note: Application mode is recommended for Windows XP and Windows 2003 as it displays the server's local and
mapped network drives. Service mode only displays the servers local drive.
Java Web Start runs Executive (Browser) as an application rather than an applet and provides access to local
files. With Java Web Start multiple Java Runtime versions can co-exist on the same client PC. A short-cut to
the HTTP server to run Executive (Browser) is automatically created.
Prompt user to download the latest Java Runtime if the client computer is not up to date.
Do not download the latest Java Runtime if the client computer has a version between 1.1 and 1.4.2.
Do not download the latest Java Runtime if the client computer has version less than 1.1.
To determine the Java Runtime version currently installed on a client PC, start Internet Explorer and view Internet
Options. The Java version is listed on the Advanced tab.
81
Network Security
Network security is displayed if the Java Web Start option is selected. It controls where files can be saved. Below is
a table that summarizes users read and file access rights to their local PC and server drives.
Local PC
Server drives
Read
Prerequisites
1.
2.
3.
For Windows 2003, enable web extensions. See Browser Products and Microsoft Windows 2003 Security in
the Troubleshooting section.
4.
5.
6.
Query & Analysis Installation - Step 10: Macro Security and Testing Query & Analysis.
7.
In Query & Analysis Setup, add Remote Users. Remote Users provide an additional level of security for
Query & Analysis browser products logging on over the internet and determining which network folders can
be accessed.
82
Installation Wizard
8.
On the server, ensure all Query & Analysis programs are shutdown before executing the Executive
(Browser) setup file.
9.
Run the Executive (Browser) installation program by clicking the Install Query & Analysis Executive
Browser links on the Query & Analysis installation Welcome screens.
10.
11.
12.
13.
Click the Next button and select the Java Runtime Environment Prompt:
Prompt the user to download the latest Java Runtime if the client computer is not up to date.
Do not download the latest Java Runtime if the client computer has a version between 1.1 and 1.4.2.
Do not download the latest Java Runtime if the client computer has version less than 1.1.
Click the Next button and click the Browse button to modify the IIS folder.
By default, a Query & Analysis Executive (Browser) folder is created in the C:\Inetpub\wwwroot folder
reserved for IIS components:
C:\Inetpub\wwwroot\Vision_Executive\
If IIS folder has been relocated select the folder in which these components reside.
14.
[Application Mode only] - Click the Next button and click the Browse button if you wish to modify the
destination folder for the Listener and Router executable files.
The default installation folder is:
C:\Program Files\Infor\Executive Browser
15.
[Java Web Start only] - Click the Next button and type in the Host Name of the HTTP server.
This is the Query & Analysis Executive (Browser) server name that is typed into the web address box of the
web browser.
16.
Specify an Executive (Browser) communications port number that is free and is not used by another
application. The default Java applet port setting is 7660.
This is the communications port between the Java applet and the server, not the web server port.
83
17.
18.
19.
[Java Web Start only] - Click the Next button and select a Network security option:
Enable Local File Access: read and write access for files on the local drive. Read only access granted
to server files.
Server Access Only: read and write access for server files.
Executive (Browser)
Listener
20.
Click OK to acknowledge the Query & Analysis Executive Browser Router service message.
21.
Type in the <DOMAIN NAME>\<Username> in the Username box. If the user exists on the local
server, rather than a domain, use the syntax <SERVER NAME>\<Username>.
22.
23.
Click OK to acknowledge the Query & Analysis Executive Browser Listener service message.
24.
Type in <DOMAIN NAME>\<Username> into the Username box. If the user exists on the local
server, rather than a domain, use the syntax <SERVER NAME>\<Username>.
25.
26.
27.
[Java Web Start only] If you have changed the web server from the default port 80, update the files
redirect.htm and Query & AnalysisExecutive.jnlp by including your web server
84
port number in the Executive (Browser) URL. The files are located in C:\Inetpub\wwwroot\Query
& Analysis_Executive.
28.
1.
On a client computer with Java Web Start, double-click the Query & Analysis Executive desktop short-cut.
The first time you connect to the Executive (Browser) Server the Desktop Integration message is displayed.
Click the Yes button to create a short-cut to Executive (Browser) on your desktop. For further information
visit the Java web site, www.java.com.
Alternatively, if Java Web Start has not been installed, open Internet Explorer and enter the URL.
i.e., http://<Executive Server Name>/Query & Analysis_Executive/
If the specified Java Plug-in version is not detected you may be prompted to download the latest version
and accept Verisign authentication. See below for configuration settings.
2.
Enter Query & Analysis Remote Logon User ID details and password. Click OK.
3.
Enter Query & Analysis Logon User ID details and password. Click OK.
The Server Setup dialog box is displayed.
85
4.
Click the Help button. The online help details how to select folders containing Query & Analysis workbooks.
Java Plug-in
Installation
Query & Analysis Executive (Browser) requires the Java Runtime for Internet Explorer. If the required Java Plug-in
version is not detected you are prompted to download the latest version. Download times vary depending on the
technique used. For example, a 56K modem takes over 6 minutes where as a broadband connection should be
just over 2 minutes.
Once the Java Plug-in has downloaded, the License Agreement dialog box is displayed.
1.
Click the Yes button if you are satisfied with the license agreement terms and conditions.
2.
3.
Click the Always button. Query & Analysis Executive (Browser) starts.
5.
6.
7.
8.
9.
10.
11.
86
2.
On the taskbar, click the Start button, point to Programs, Startup and click Query & Analysis Executive
(Browser) Router.
Query & Analysis Executive (Browser) Router starts. The icon is displayed in the taskbar.
4.
On the taskbar, click the Start button, point to Programs, Startup and click Query & Analysis Executive
(Browser) Listener.
Query & Analysis Executive (Browser) Listener starts. The icon is displayed in the taskbar.
87
Internet Security
Service Packs
There are security issues that must be considered when deploying Executive (Browser) and eAlert (Browser) on
the Internet. Without updating service packs, Internet Information Services (IIS5) default installation may be open
to a number of security vulnerabilities. Potentially sensitive financial data could be exposed via the Internet if strict
security management practices are not in place.
Remote Users
Remote Security provides an additional level of security when logging on with the Query & Analysis internet
applications eAlert (Browser) and Executive (Browser). Nominated Remote Users can be members of a Remote
Group. As member of the Remote Group with administrator rights, the Remote User can specify which folders on
the local computer and on the network can be accessed in order to select files used by the applications.
Remote logon access is used in conjunction with an existing Query & Analysis logon. The Remote Logon dialog
box appears before the Query & Analysis Logon dialog box. Query & Analysis users must provide correct logon
details to both dialog boxes in order to use Query & Analysis application.
There are no Remote users configured on the system in the default installation, before you can start using eAlert
(Browser) or Executive (Browser) a Remote user must be added. It is assumed that a Query & Analysis user has
been created and Remote Users have not been previously created by User Wizard.
Although not recommended, the Remote Security logon prompt can be bypassed so only a Query & Analysis user
ID needs to be provided to logon over the internet. To disable Remote User logon follow the instructions detailed
later in this section.
Click the Start button, point to Programs, Query & Analysis and click Setup. Query & Analysis Setup starts.
2.
3.
Click OK.
4.
5.
Click the Add button and type in a user name, password and confirmation password.
88
6.
7.
8.
9.
Select the Administrator option if you wish to grant the Remote Group administrator rights. Remote Users
with administrator access can configure server settings. Similarly, a Remote user that is a member of a
Remote Group that does not have administrator rights is unable to modify server settings and configure
access to network folders.
10.
11.
89
12.
On the Setup menu, click Exit to quit Query & Analysis Setup.
14.
15.
Create the Remote User Default. Leave the password box blank.
16.
17.
90
Query & Analysis Financial Reporting application extracts, transforms and loads ASCII data files and ODBC data
sources to a central and standalone Financial Datamart.
The Financial Datamart can be created using Microsoft SQL Server or, for small installations with less than five
users, MSDE (Microsoft Desktop Engine).
Assumptions
Process Overview
The process for installing Query & Analysis Financial Reporting can be divided into the following steps:
1.
Create a Query & Analysis Financial Reporting (VFR) database (separate from the Query & Analysis
centralized database).
2.
3.
In Query & Analysis Maintenance, establish a connection from Query & Analysis to the VFR database.
4.
Use the Query & Analysis Financial Reporting (ETL) application to populate the VFR database.
On the taskbar, click the Start button, point to the Microsoft SQL Server program group and click Enterprise
Manager.
2.
Select the Microsoft SQL Server then the Databases folder in the Tree tab.
3.
On the Action menu, click New Database. The Database Properties dialog box appears.
91
4.
5.
6.
Click OK.
MSDE
In MSDE, the database can be created by a script or entering the commands listed below.
Script Technique
Execute Create_VFR_MSDE_Database.VBS
Manual Technique
1.
On the taskbar, click the Start button and then click Run.
2.
3.
DATABASE
process
is
allocating
0.49
MB
on
disk
Execute Delete_VFR_MSDE_Database.VBS
Manual Technique
1.
On the taskbar, click the Start button and then click Run.
2.
3.
92
On the taskbar, click the Start button, point to the Query & Analysis program group and click ODBC
Administrator.
2.
3.
4.
5.
6.
7.
8.
9.
Click Next.
SQL Server can verify authenticity with either a Windows NT or SQL Server login ID.
10.
11.
12.
93
On the taskbar, click the Start button, point to the Query & Analysis program group and click Maintenance.
2.
Leave the password field blank unless a password has been previously set for Query & Analysis
Maintenance.
3.
Click the Client Setup button. The Client Setup dialog box is displayed.
4.
5.
6.
7.
Click the Test Connection button, Query & Analysis checks whether it can access the data source. If
successful the ODBC connection test passed message is displayed and the indicator turns green. If the
test fails, the indicator turns red with a white cross. It is assumed the test was successful.
8.
On the taskbar, click the Start button, point to the Query & Analysis program group and Query & Analysis
Financial Reporting.
2.
94
The Query & Analysis product suite is supported on Windows Terminal Services and Citrix Metaframe. Query &
Analysis supports the use of server farms and published applications. Roaming profiles is recommended.
Note: When using a Remote session, each instance of a Query & Analysis application increments the license
count.
2.
3.
4.
Click the Change Source button to modify the current file path to the common file path for all Query &
Analysis XL add-ins.
Alert on Citrix
Application User Profiles
Query & Analysis supports Windows User Profiles. Each user has their own settings, including: DataLinks, DataLink
connection details, e-mail settings, last used files and Alert tasks. These settings are not visible to other users who
may log on to the same computer.
In Query & Analysis, the Application User Profiles option must be disabled on the Query & Analysis Alert Server. If
you intend to install Query & Analysis Alert Server in a Citrix environment on the same machine as the other Query
& Analysis clients, this decision will impact all users. With Application User Profiles deactivated all Query &
Analysis users share a single settings folder and so will all have same login, user and DataLink settings.
Ideally Query & Analysis Alert Server should be installed and configured on a dedicated PC. This ensures the Citrix
system can operate unaffected with Application User Profiles activated.
95
User Sessions
Alert Manager must be open to run Events. This process can be resource intensive as Alert Manager is always
running, that is, if you have 30 users, there are always 30 sessions. This is not the ideal solution but can be used
for a small number of Alert users.
If you require a larger number of Alert users, install the Alert Listener and Alert Manager on a separate computer.
The Manager and Listener should be configured to start at logon by using the Automatic Logon feature and placing
the Listener in the startup folder. Alternatively, run the Manager and Listener processes as Services.
If you want Query & Analysis eAlert clients to be able to view each others Alert Tasks, activate the Query & Analysis
eAlert Local Database Override option to specify the central repository for storing Alert Tasks. You are prompted for
the location of this Query & Analysis settings database (LsAgEg10.mdb) when you first run Query & Analysis
eAlert.
96
The Uninstall utility, located in the Query & Analysis program group, removes Query & Analysis suite applications.
Query & Analysiss settings and DataLinks can be preserved if you intend to reinstall Query & Analysis in the
future.
Query & Analysis components should be removed in the following order:
1.
2.
3.
4.
Note: If upgrading or re-installing Query & Analysis select the same installation folder previously used, by default
C:\Program Files\Infor PM QA. Failure to do so prevents Query & Analysis from detecting existing configuration
settings.
2.
3.
Select Query & Analysis Executive (Browser) and click the Change/Remove button.
4.
5.
Click Finish.
The Query & Analysis Executive Browser Router and Query & Analysis Executive Browser Listener
processes/services are removed.
Click the Start button, point to Settings and click Control Panel.
2.
3.
If installed, select Query & Analysis eAlert Services and click the Change/Remove button.
97
4.
5.
6.
Click Finish.
7.
Select Query & Analysis eAlert (Browser) and click the Change/Remove button.
8.
2.
Select Query & Analysis NetEnterprise and click the Change/Remove button.
3.
4.
5.
Click Finish.
Click Uninstall in the Query & Analysis program group. In Windows Vista, select the Run As Administrator
right-click option to run the Uninstall shortcut.
2.
Click the Next button to proceed. Query & Analysis settings can be retained should you wish to re-install
Query & Analysis or purged completely from the Query & Analysis installation folder.
The Completely uninstall DataLinks and application settings option performs the following function:
Enabled: all Query & Analysis settings are removed from the Query & Analysis installation folder, by
default C:\Program Files\Infor PM QA\Settings. User Profile settings are not
deleted.
Disabled: Query & Analysis settings are retained in the Query & Analysis installation folder and in User
Profile folders.
3.
4.
Click Finish.
98
Registry Settings
When Query & Analysis is uninstalled some Windows registry key settings remain. These settings ensure that if
Query & Analysis is re-installed the software components are placed in the same folder locations and product
settings, such as application user profiling, are re-instigated.
Once Query & Analysis has been removed, the following Windows registry keys remain:
Note: Windows registry settings should not be deleted unless you are performing a manual uninstall.
99
Troubleshooting
100
In Microsoft Office XP and Office 2003, the default security setting in Excel and Word is High. Warnings may be
displayed when using certain Query & Analysis functions. Additionally, Office has an extra level of security to
combat the spread of viruses.
Excel security settings can be found on the Security dialog box. The default settings prevent Query & Analysis XL
macros from executing. For Query & Analysis XL to operate functions such as Macro Builder, Data Selector and
Alert it is necessary to modify Excels security level and settings.
Note: Modifying security settings could cause a reduction in the level of virus protection.
To modify security settings:
1.
2.
On the Tools menu, point to Macro and then click Security. The Security dialog box is displayed.
3.
4.
5.
6.
Enable the Trust access to Visual Basic Project option and click OK.
Drilldown Error
If the following error message is displayed when attempting a Drilldown in Query & Analysis XL, then the
installation of Query & Analysis is incomplete.
Error 429 ActiveX component can't create object
101
The Active X controls required by Drilldown and Hierarchy Designer have not been registered. To register the
controls:
1.
2.
3.
4.
5.
6.
7.
Start Query & Analysis XL and test Drilldown. The error message should no longer appear.
Please refer to your security software documentation on how to grant access to the ports required by Query &
Analysis browser products and Query & Analysis client e-mail.
Query & Analysis client e-mail, located in Client Setup, uses port 25 by default.
Executive (Browser) uses the port number specified during installation, by default port 7660. For further
information see the section Ports.
eAlert (Browser) uses port 6666 by default. For further information see the section Install Alert Services.
102
C:\Oracle\Ora92\). Where this is not done, you may not be able to connect to NetEnterprise Server and the
following error message may be displayed:
System.Data.OracleClient requires Oracle client software version
8.1.7 or greater
This is known issue that manifests after upgrading to Oracle 9i Release 2 (9.2.0.1.0) on a PC running Windows with
an NTFS partition. The contents of ORACLE_HOME directory is not accessible to users, including those for IIS, who
are authenticated on that machine. The permissions are not set properly when the Oracle software is installed.
The resolution steps are detailed below and should be performed on the machine running NetEnterprise Server:
1.
2.
3.
Right-click the ORACLE_HOME folder and select Properties. The Properties dialog box appears.
4.
5.
Select the Authenticated Users item in the Name list (in Windows XP the Name list is called Group or
user names). You may need to add Authenticated Users to the Name list if it is not present. Please see
your Windows documentation for further details.
6.
In the Permissions list, clear then select the Read and Execute box under the Allow column (in Windows
XP the Permissions list is called Permissions for Authenticated Users).
7.
8.
In the Permission Entries list confirm that the Authenticated Users group has the following settings:
If the above is not the case, ensure that the correct settings are made. This should already be set properly
but it is very important that the settings are verified.
9.
Click the OK button until you close out of all of the Security properties windows. The may be some delay
during this phase as permissions are applied to various folders and sub-folders.
10.
It is advisable at this point, to restart the machine to ensure that all changes take effect, and that they are
fully recognised by Oracle and IIS.
103
Give ASPNET full access rights to the Query & Analysis installation folder.
In Windows 2003:
1.
Start the Computer Management utility. In the Computer Management tree, expand Services and
Applications -> Internet Information Services.
2.
3.
4.
5.
In the Computer Management tree, expand System Tools -> Local Users and Groups.
6.
7.
8.
9.
Take note of the group ASPNET is a member of. In the example below it is Users.
104
10.
In Windows Explorer, right-click the Query & Analysis installation folder and select Properties. By default, the
folder is C:\Program Files\Query & Analysis.
11.
12.
Select the group which ASPNET user was a member of, determined in step 9.
13.
14.
2.
3.
4.
5.
6.
105
Restarting IIS
If you experience problems accessing the Web server, and have confirmed that Query & Analysis Alert Manager or
Executive (Browser) is running, restart Internet Information Services (IIS).
Note: Restarting IIS temporarily stops web services. Consider the impact to other systems that rely on IIS before
proceeding.
To restart IIS:
1.
2.
3.
4.
5.
6.
106
2.
3.
4.
Click the Logon tab and enter the correct service logon details.
5.
Click OK.
6.
Repeat for the Query & Analysis Executive Browser Router service.
Windows 2003
For Windows 2003, the services are not installed if the logon details are found to be incorrect. A batch file has been
provided to just install the services without the need to go through the complete Executive (Browser) installation
process.
For Windows 2003 users, the batch file Start Query & Analysis Executive Services.bat
is placed in the installation folder, by default this would be:
c:\inetpub\wwwroot\Query & Analysis_executive
Run the batch file and enter logon details for the Router and Listener services.
107
MDAC Version
During Query & Analysis installation a check can be performed to verify that the required MDAC version is on the
PC. There are instances when MDAC fails to install successfully and so the version number held in the registry
settings is incorrect. Although the correct MDAC version is installed, Query & Analysis validates against the registry
setting and then displays an error.
There are two workarounds:
Clear the MDAC checking option in Query & Analysis custom install options.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to
reinstall your operating system.
2.
3.
4.
Click inside the Value box and move the cursor to end.
5.
6.
7.
Click OK.
8.
108
9.
10.
Chinese Characters
In order to input Chinese characters into Query & Analysis the correct Microsoft Windows locale environment
should be set. Microsoft Windows locale settings are made in the Regional and Language Options utility in Control
Panel.
To input:
Simplified Chinese characters: set the default locale to Chinese (PRC) or Chinese (Singapore) using
Simplified Chinese Query & Analysis.
Traditional Chinese characters: set the default locale to Chinese (Taiwan), Chinese (HKSAR) or Chinese
(Macau SAR) using English or Traditional Chinese Query & Analysis.
109