Core EBA 4.6 Installation and Upgrade Instructions
Core EBA 4.6 Introduction & Quick Start Instructions 4
EBA Introduction. 4
EBA 'Core Bundle' 4
EBA Optional Modules. 5
Downloading the Core EBA Software. 6
Downloading the EBA License File. 7
Terminology Reference Note. 8
EBA 4.6 'Quick Start' Instructions (New Installation) 9
EBA 4.6 'Quick Start' Instructions (Upgrade) 11
Core EBA 4.6 Detailed Install Instructions (New) 14
Preliminary Steps. 14
1. Determine Licensed EBA Modules. 14
2. Check/Remove Previous EBA/Firebird/Interbase Installations. 14
3. Logon to Windows Server with Administrator User Id. 15
Install Steps. 15
4. Install EBA 'Core Bundle'. 15
4.1 Select Site Type. 16
4.2 Create Client Configuration File. 16
4.3 Create ODBC System DSN.. 17
4.4 Launch Administration User Interface. 20
5. Install EBA License. 21
6. Install New Standard templates (EXACT_BUSINESS_ANALYTICS) 21
7. Set Database User / Password. 21
8. Install Back Office SQL Integration(s) 23
9. Review and Select Integration Modules (EXACT_BUSINESS_ANALYTICS) 23
10. Assign Back Office User Roles and Rights (if applicable) 24
11. Synchronize Back Office User Information into EBA (if applicable) 25
12. Review / Update Fiscal Calendar 25
13. Install and Configure eDeployment module (if applicable) 26
14. Install and Configure Web Access Server module (if applicable) 27
15. Copy client setup programs to UI directory. 27
16. Share UI directory. 28
17. Install Express User Interface module (if applicable) 28
18. Install System Administration module (if applicable) 28
19. Install Power User Interface module (if applicable) 28
20. Install Business User Plus Interface module (if applicable) 28
21. Install Business User Interface (if applicable) 28
22. Install Dashboard Add-In (if applicable) 29
23. Enable Transaction Currency Analysis. 29
Core EBA 4.6 Detailed Install Instructions (Upgrade) 30
Overview.. 30
Preliminary Steps. 30
1. Determine Licensed EBA Modules. 30
2. Check for Connected EBA Users. 31
3. Logon to Windows Server with Administrator User Id. 31
4. Stop all EBA Application Services. 31
5. Remove previous Firebird (EBA Embedded Database Service) 31
6. Copy existing EBA Installation. 32
Upgrade Steps. 32
7. Upgrade EBA 'Core Bundle'. 32
8. Upgrade EXACT_BUSINESS_ANALYTICS Databases. 33
9. Upgrade GPS SYSTEM INFORMATION Databases. 33
10. Install New License (Optional) 34
11. Install New Standard templates (GPS SYSTEM INFORMATION) 34
12. Upgrade existing EXACT_BUSINESS_ANALYTICS Templates. 34
13. Install New Standard templates (EXACT_BUSINESS_ANALYTICS) (optional) 35
14. Upgrade Back Office SQL Integration(s) (optional) 35
15. Merge & Promote New Standard Metadata, for the EXACT_BUSINESS_ANALYTICS Environment (optional) 36
16. Re-synchronize Back Office User Information into EBA (if applicable) 37
17. Change RDIS Authentication to 'Windows Single Sign-on' (optional) 38
18. Upgrade eDeployment module (if applicable) 38
19. Upgrade Web Access Server module (if applicable) 39
20. Copy client setup programs to UI directory. 39
21. Share UI directory. 39
22. Install Express User Interface module (if applicable) 39
23. Upgrade System Administration module (if applicable) 39
24. Upgrade Power User Interface module (if applicable) 40
25. Upgrade Business User Plus Interface module (if applicable) 40
26. Upgrade Business User Interface (if applicable) 40
27. Upgrade Dashboard Add-In (if applicable) 40
Exact Business Analytics (EBA) is an analytics and reporting software solution that includes two types of modules:
1. A set of generic “Core” modules that are used to securely consolidate and analyze data, regardless of the source of that data, and
2. A set of specific “Integration” modules that are used to access information from specific back office systems (ERP, CRM, Financials, etc.)
This document describes the steps to install and configure the Core Exact Business Analytics (EBA) software, for version 4.6. It covers both installation types—new installations and upgrades from previous versions. For each installation type, a brief “Quick Start” section is provided as an installation checklist, along with a more detailed set of explanatory instructions for each Quick Start step.
For convenience, Integration module installation instructions are also provided for the Exact back office systems that bundle EBA 4.6 as part of their base offerings, currently:
o Macola ES 372, and
o Globe 374 and 380
The remainder of this section provides an overview of Core EBA, from the installation perspective. Read it to understand how to get started.
Core EBA includes a set of required modules that are bundled together for ease of installation. This package is called the EBA “Core Bundle”, and consists of these product components:
· an embedded database server (Firebird 2) deployed as a Windows Service,
· Firebird-based system databases (for user security, scheduling, metadata, etc.)
· a database access middleware server (RDIS, or Real-time Data Integration Server) deployed as a Windows Service, and
· the Administration UI (required to configure, maintain, and upgrade the system)
The EBA core bundle must be installed on a Windows Server, with these requirements for production use:
1. Windows Server (Windows 2000 Server or Windows Server 2003) with a fixed IP address on a Windows Domain
2. ODBC driver(s) that can access all desired back office databases
3. Database user / password to access all desired back office databases
Note: Most of the EBA setup program names referenced in this document correspond to the EBA brand (denoted by “EBA”) and the Exact Integration Type (denoted by “EXT”), e.g. Setup_EBA_EXT_Core_Bundle_EN.EXE. Although setup programs distributed to non-Exact back office customers may contain a different brand and integration type identifiers, the setup program names after the Setup_XXX_YYY prefix are the same.
The EBA core bundle distribution consists of these required setup programs:
· Setup_EBA_EXT_Core_Bundle_EN.EXE, which must be run by the user, and which silently executes these additional setup programs:
§ Firebird-2.0.1.12855-0-Win32.exe
§ Firebird_ODBC_1.2.0.69-Win32.exe
§ Setup_EBA_EXT_METADATA_EN.exe
§ Setup_EBA_Client_Adminui_EN.exe
Note: Setup program Setup_EBA_EXT_METADATA_EN.exe is currently not distributed under the EBA product line, via the e-Synergy product updater. It is distributed under the various EBA-enable back office product lines. However, this program must be present (in the same sub-directory) prior to running program Setup_EBA_EXT_Core_Bundle_EN.EXE. Please follow your back office installation instructions to download Setup_EBA_EXT_METADATA_EN.exe, prior to running Setup_EBA_EXT_Core_Bundle_EN.EXE.
Note: Setup_EBA_Client_Adminui_EN.exe is a client module that is automatically installed on the server for easy initial configuration and subsequent support. It may also be fully installed (or just registered) on the EBA Administrator’s client PC.
Core EBA includes these optional server modules:
§ Setup_EBA_eDeployment_EN.exe
§ Setup_EBA_WebAccessServer_EN.exe
§ Setup_EBA_Client_Dashboard_AddInClient_EN.exe
As with the “Core Bundle”, the server modules must be installed on Windows Server with a fixed IP address.
Core EBA includes the following optional client modules (that you may have licensed or may have been included with your back office solution):
§ Setup_EBA_Client_Expressui_EN.exe
§ Setup_EBA_Client_Powerui_EN.exe
§ Setup_EBA_Client_BusinessuiPlus_EN.exe
§ Setup_EBA_Client_Businessui_EN.exe
The client modules are typically installed on the server, and then “registered” on each network-connected client PC that is to access that module. This approach allows for a single point of control for upgrades (which generally avoids having to touch each client machine, since each client simply contains a shortcut pointing to the software on the server). Additionally, each client module may be fully installed on a client PC (termed a “complete local installation’), which enables off-line execution (and is required for users who travel with laptops).
Note: All Core EBA 4.6 client modules are capable of running on the Microsoft Vista OS. When installing any EBA client setup program on Vista, instead of double-clicking on the setup program to run it, right-click on it and select “Run as Administrator”.
The same EBA core software listed above is used for both initial installation and upgrade. The software may be downloaded from one of several online portals. This section describes how to use an Exact Product Updater to download the Core EBA 4.6 software from https://update.exactsoftware.com. Executing this download will only download the EBA Core Modules; it will not download any EBA back office integration modules.
Note: Macola ES 372 customers receive all of the Core EBA 4.6 software automatically when they run the product updater for Macola ES 372 (in addition to automatically receiving the EBA Integration modules for Macola ES 372). Do not download Core EBA 4.6 separately if you are a Macola ES 372 customer—simply skip this section!
Run the SynergyProductUpdater (it can be found in the bin folder of the installation directory) from your Windows Server. The EBA-specific parameters to enter are:
· Product line is EBA
· Release is 4.6
The setup programs listed above will be downloaded into a sub-folder called EBA, within the installation directory. The Core EBA distribution is about 113mb in size, so the download will typically take between 15 minutes and 1 hour, depending on your internet connection.
Note: The full default installation directory for EBA is C:\Program Files\Exact Software\EBA, and this base directory is referenced in this document. If you have installed to a different directory, please adjust your actions accordingly.
Customers who are installing the EBA 4.6 core software for the first time must download a customer-specific EBA License file prior to installation. Customers upgrading from 4.5 do not need to download a new License File unless they have changed their licensing.
Your EBA License Management file (also known as the EBA License Voucher file) can be retrieved from the Exact Customer Portal. Using your browser, identify the License Management document attached to your Account Card with the extension “.lic”, and download it to your EBA Server. This file will be installed into EBA in a subsequent step.
You are now ready to upgrade or install EBA. If this is your first time installing EBA, please read the next section, EBA “Quick Start” Instructions (New Installation), to get an overview of the process before you begin. People who have installed EBA before can also use this section as an installation check list (and then refer to the subsequent detailed instructions only as needed).
A small portion of the terminology in this document refers specifically to the Exact distribution of the Exact Business Analytics product line. Core EBA is distributed under other brands, and has also been distributed under the Graphical Performance Series brand in the past. The specific terminology may cause confusion for non-Exact back office customers, if not noted.
So, customers who do not use Exact back office systems should interpret any reference to the “EXACT_BUSINESS_ANALYTICS” Environment as a reference to your own back office environment. Similarly, interpret references to the default pre-configured Exact Site (EBA_Site1) as referencing your specific site. Similar guidance applies to references to a default sub-directory, a brand, or an integration type.
This section provides a handy check list of the steps required to complete a new installation of EBA Core 4.6.
Since this section includes steps to install optional modules, please skip any steps for modules that you have not licensed. Installing unlicensed modules will not hurt anything, but can be confusing (since EBA’s integrated license management system will prevent use of unlicensed modules).
Execute the steps below to install EBA. All steps must be executed in the documented sequence, unless otherwise noted. Please see the section of this document entitled Core EBA 4.6 Detailed Install Instructions (New), for detailed reference and how-to information about each step.
1. Determine Licensed EBA Modules
2. Check/Remove Previous EBA/Firebird/Interbase Installations
3. Logon to Windows Server with Administrator User Id
4. Install EBA “Core Bundle”
5. Install EBA License
6. Install Standard Templates (EXACT_BUSINESS_ANALYTICS)
7. Set Database User(s) / Password(s)
8. Install Back Office SQL Integration(s)
9. Review & Select Integration Modules (EXACT_BUSINESS_ANALYTICS)
Note: Steps 10 and 11 are required for Exact Macola ES 372 and Exact Globe 374/380 customers only—other customers do not have this option and simply skip these steps.
10. Assign Back Office User Roles & Rights (if applicable)
11. Synchronize Back Office User Information into EBA (if applicable)
12. Review / Update Fiscal Calendar
13. Install and Configure eDeployment module (if applicable)
14. Install and Configure Web Access Server module (if applicable)
15. Copy client setup programs to UI directory: To facilitate setup of individual clients, please copy the following client setup programs (only the ones that your company has licensed) from the download directory to c:\program files\GPS\UI:
a. Setup_EBA_Client_Adminui_EN.exe
b. Setup_EBA_Client_Expressui_EN.exe
c. Setup_EBA_Client_Powerui_EN.exe
d. Setup_EBA_Client_BusinessuiPlus_EN.exe
e. Setup_EBA_Client_Businessui_EN.exe
f. Setup_EBA_Client_Dashboard_AddInClient_EN.exe
16. Share UI directory: Create a Share on folder: c:\program files\GPS\UI (if a Share does not already exist from a previous installation). This will enable “Client Registration Only” installations that simply create a shortcut on the user desktop pointing to this sub-directory.
17. Install Express User Interface module (if applicable)
18. Install System Administration module (if applicable)
19. Install Power User Interface module (if applicable)
20. Install Business User Plus Interface module (if applicable)
21. Install Business User Interface (if applicable)
22. Install Dashboard Add-In (if applicable)
23. Enable Transaction Currency Analysis
This section provides a handy check list of the steps required to upgrade the EBA Core Modules from 4.5 to 4.6.
Note: The Core EBA solution itself is composed of an integrated set of modules, which must all be upgraded to version 4.6 together. The only exception to this rule is the standalone “Business User Interface” module, which may be upgraded incrementally to 4.6.
Note: As part of upgrading Core EBA, you may also upgrade your EBA back office integrations, but doing so is not required. Please read the important note included with step 6 below, regarding upgrading back office integrations.
Execute the steps below to upgrade EBA. All steps must be executed in the documented sequence, unless otherwise noted. Please see the section of this document entitled Core EBA 4.6 Detailed Install Instructions (Upgrade), for detailed reference and how-to information about each step.
2. Check for Connected EBA Users
4. Stop all EBA Application Services
5. Remove previous Firebird (EBA Embedded Database Service)
6. Copy existing EBA Installation
7. Upgrade EBA “Core Bundle”
Note: Upgrading Core EBA and upgrading your back office integration(s) are different decisions. Many customers upgrade both at the same time, but that is not required. Customers with highly customized back office integrations sometimes upgrade Core EBA without also upgrading their back office integrations (due to the extra work that may sometimes be required to reconcile customizations).
This program will ask you if you want to replace your active metadata. Answer “Yes” to this prompt only if you want to upgrade your back office integration(s) AND you are sure that your metadata has not been customized! In this case, you will be able to skip optional step 14 (which is to merge the new standard metadata with your customized active metadata), even if you are upgrading your back office integration(s).
If you want to upgrade your back office integration(s), but are unsure if your metadata has been customized, simply leave the default (do not replace the active metadata), and also skip steps 12, 13 and 14 (which can be executed together at a later time). You MUST understand the state of your back office integrations (relative to customizations) to make an informed decision regarding upgrading to new integrations.
8. Upgrade EXACT_BUSINESS_ANALYTICS Databases
9. Upgrade GPS SYSTEM INFORMATION Databases
10. Install New License (Optional)
11. Install New Standard Templates (GPS SYSTEM INFORMATION)
12. Upgrade existing EXACT_BUSINESS_ANALYTICS Templates
Note: Optional Steps 13, 14, and 15 must all be executed if you are upgrading your back office integration(s). This is because the .ptvw templates, SQL Scripts, and Metadata must be upgraded as a group, to remain consistent. However, as noted in step 6, if you replaced your active metadata, skip step 14 (even if you are upgrading your back office integration(s).
13. Install New Standard templates (EXACT_BUSINESS_ANALYTICS) (optional)
14. Upgrade Back Office SQL Integration(s) (optional)
15. Merge & Promote New Standard Metadata, for the EXACT_BUSINESS_ANALYTICS Environment (optional)
16. Re-Synchronize Back Office User Information into EBA (if applicable): This step is required for Exact Macola ES 372 and Exact Globe 374/380 customers only—other customers do not have this option and simply skip this step.
17. Change RDIS Authentication to “Windows Single Sign-on” (optional)
18. Upgrade eDeployment module (if applicable)
19. Upgrade Web Access Server module (if applicable)
20. Copy client setup programs to UI directory: To facilitate upgrade of individual clients, please copy the following client setup programs (only the ones that your company has licensed), from the download directory to c:\program files\GPS\UI:
g. Setup_EBA_Client_Adminui_EN.exe
h. Setup_EBA_Client_Expressui_EN.exe
i. Setup_EBA_Client_Powerui_EN.exe
j. Setup_EBA_Client_BusinessuiPlus_EN.exe
k. Setup_EBA_Client_Businessui_EN.exe
l. Setup_EBA_Client_Dashboard_AddInClient_EN.exe
21. Share UI directory: Create a Share on folder: c:\program files\GPS\UI (if a Share does not already exist from a previous installation). This will enable “Client Registration Only” installations that simply create a shortcut on the user desktop pointing to this sub-directory.
22. Install Express User Interface module (if applicable)
23. Upgrade System Administration module (if applicable)
24. Upgrade Power User Interface module (if applicable)
25. Upgrade Business User Plus Interface module (if applicable)
26. Upgrade Business User Interface (if applicable)
27. Upgrade Dashboard Add-In (if applicable)
This section documents the preliminary steps required to successfully install EBA 4.6 on a Windows Server, and it assumes that the EBA 4.6 software and license key have been download to your server. Please review and execute the sections entitled “Downloading the EBA Software” and “Downloading the EBA License File”, if required.
Review your contract to determine which EBA modules you have licensed. The EBA Suite contains a number of different modules (both core and integration), and the Exact Product Updater downloads ALL EBA Core modules (even those that you are not licensed to). So, you will save time and avoid confusion by understanding which modules your company has licensed, prior to starting a new installation or an upgrade.
The instructions below are for a new installation of EBA 4.6, which means that any known potentially conflicting software should be removed from the server. Occasionally customers trial a previous version of EBA on a server, and forget about it. This step is simply to ensure that you are installing on a “clean” server, from the EBA perspective. If you are installing EBA on a new server, you may safely skip this step.
EBA includes a number of Windows Services that must be stopped prior to uninstalling them. To find and stop the EBA services, follow these steps:
1. Stop core EBA eDeployment Windows Services via menu option Start > All Programs > Exact Business Analytics > eDeployment > Stop eDeployment Services. If this menu option (or one similarly named) does not exist, then eDeployment services are not installed (so, no need to stop).
2. If eDeployment is installed, also manually stop the eDeployment monitor service via Start > Control Panel > Administrative Tools>Services. This service is called “BI eDeployment Monitor”. Right-click on it and select the “Stop” menu option, if enabled.
3. If the Web Access Server standalone service is installed, manually stop it via menu option Start > Control Panel > Administrative Tools>Services. It is called “WAS Service”. Right-click on it and select the “Stop” menu option, if enabled. This service is no longer supported in EBA 4.6 (Web Access Server is deployed ONLY under IIS 6, and no longer as a standalone service), so it must also be disabled, if it exists. To disable it, right-click on the “WAS Service” and select “Properties”. Then select “Disabled” for the “Startup Type”, and click the OK button.
4. Manually stop the RDIS service via menu option Start > Control Panel > Administrative Tools>Services. This service is called “BI Realtime Data Integration”. Right-click on it and select the “Stop” menu option, if enabled.
To uninstall any of the EBA components, use menu option Start > Control Panel > Add or Remove Programs, and then remove any programs that reference EBA, Exact Business Analytics, Graphical Performance Series, or any similar brand variations.
The EBA 4.6 Core Bundle installs version 2 of the embedded Firebird database (version 2), which is incompatible with any previous Firebird version, and also incompatible with any version of Interbase. To remove Firebird (if it exists):
1. Stop the Firebird Guardian Service via menu option Start > Control Panel > Administrative Tools > Services. This service is called “Firebird Guardian”. Right-click on it and select the “Stop” menu option, if enabled.
2. Uninstall Firebird (using menu option Start > Control Panel > Add or Remove Programs)
To remove Interbase (if it exists), please consult your Interbase documentation.
Log on to your Windows Server with the Windows User Id that you use to administer EBA (if not already logged on with that User Id). This user must have administrative privileges on the server.
This section describes the steps required to successfully install Core EBA 4.6.
Run the Setup_EBA_EXT_Core_Bundle_EN.exe program and follow the on-screen instructions.
Note; Prior to running Setup_EBA_EXT_Core_Bundle_EN.exe, make sure that program Setup_EBA_EXT_METADATA_EN.exe exists in the same sub-directory. If it does not, you will get a message “Windows cannot find Setup_EBA_EXT_METADATA_EN.exe”, and the installation will not be successful. If this occurs, please download Setup_EBA_EXT_METADATA_EN.exe to the same sub-directory, and run the Setup_EBA_EXT_Core_Bundle_EN.exe program again.
Note: It is strongly recommended to retain the default settings for ease of support and subsequent upgrades. This program typically runs for 2 to 5 minutes (not including the time for you to read the screens and enter information into them).
If your distribution supports multiple “Site Types” (which correspond to the various back office database integrations), then you will see the screen below. If your distribution supports a single Site Type only, this screen is not presented.
When presented with this screen, please choose the single site type of the database that you want to configure during the installation process.
Note: you may add more (and different) additional Site Types and databases after installation.
The following screen is displayed to create a required configuration file (EBA.ini), which will be used to install clients that connect to this server. The client modules communicate with the RDIS middleware using TCP/IP, and are configured to access a specific TCP/IP Address and Port.
The screen below requests information to create an installation-specific .ini configuration file, which will contain this information for the client modules to connect to RDIS. When this screen appears, your server’s actual IP address will be defaulted in automatically, and the port will be defaulted to 9000. In most cases, these default values are acceptable; however, change the defaults on this screen if needed.
Note: this package can be installed on a machine without a fixed IP address for demonstration purposes (for example, a laptop). In this case, override the defaulted RDIS Server IP Address to 127.0.0.1.
The setup process guides you through the configuration of a single “back office” database, which must be accessed via an ODBC System DSN that you create using the standard Windows “ODBC Data Source Administrator”. This ODBC System DSN must be named “EBA_Site1_SQL“.
Note: Additional databases may be configured after the installation.
To complete this step, you must provide a valid user id and password for your database. This user id must be able to create Tables, Indexes, and SQL Views. If you do not have this information, then you may skip this step for now.
Click the “Configure” button to create the “EBA_Site1_SQL” data source, or click the “Skip” button to bypass this step at this time. If you choose to bypass this step at this point in the process, you must revisit it to analyze back office information.
Note: the sample screen prints below present screens for configuring a SQL Server ODBC DSN. If you are configuring for a different database (like DB2 on iSeries, Oracle, etc.), your screens will look different. In this case, please consult your database documentation if needed, to determine how to create the ODBC System DSN.
Note: Name the ODBC DSN “EBA_Site1_SQL”, regardless of the database type (SQL Server, DB2, Oracle, etc.), since that is the ODBC DSN that has been pre-configured in the EBA system database.
On the following screen, make sure that the “Name” remains “EBA_Site1_SQL”, since this is the name that has been pre-configured in the Firebird system database. Enter whatever you want for the “Description”. Then, select the database Server, and click the Next> button.
Note: On the following (SQL Server ODBC) screen you MUST select “With SQL Server authentication using a login ID and password entered by the user”. The RDIS middleware does not support the (SQL Server–specific) option “With Windows NT authentication using the network login ID”.
Note: On the following (SQL Server ODBC) screen you MUST select a default database that corresponds to the previously selected Site Type.
If the ODBC data source configuration screen includes a “Test” button (SQL Server does), please use it to verify that the ODBC driver definition is valid and will be usable by RDIS.
On the last screen of the Core Bundle setup program, click the “Launch AdminUI” button to launch the Administration UI module. This module is used to execute the next steps in the installation process.
Note: The first time this program is launched, it will take up to 2 minutes before the initial screen appears, due to one-time client-side caching of screen definitions and other static information. Subsequent launches will be much faster.
Note: Because the default RDIS authentication is set to “Windows Single Sign-On”, you should NOT be prompted for a user id and password. If you are prompted, key in the Administrator User Id and Windows Password that you used to sign on to the Server.
Note: Your new EBA installation is not yet valid, because a license file has not yet been installed. Because of this, you will see an informational message “Due to invalid license only one Admin client will be allowed”, which tells you that the system is in a “restricted state” and will not allow any other client connections until a valid license is installed. Click “OK”, and you will then be shown the License Management information screen, with this message at the top: ”License Management information not found”. Click the “Close” button at the bottom of this screen.
To install your EBA license from the Administration UI, access menu option Tools/Install License, and then follow these steps:
1. Click the “Select File…” button, locate the .lic file on your file system, select it, and click the “Open” button.
2. Review the license information on the screen, to ensure that it is what you expect. Then click the “Install License” button. You will receive a confirmation message “License Installed Successfully”. Click “OK”.
Note: If you do not click the “Install License” button, then the license will not be installed.
Back office integration modules typically also include standard template files, which have a file extension of .ptvw (this stands for Portable VieW), and which are distributed via the back office download process. If these standard templates exist for your distribution, they must be installed at this time.
To Mass Upload the standard EBA .PTVW template files into the Object Repository, for the EXACT_BUSINESS_ANALYTICS Environment, follow the steps below.
1. Access outline option Networkr Environment Managementr Environmentsr EXACT_BUSINESS_ANALYTICSrObject Managementr Upload / Download Objects en Mass
2. Click the ellipsis (…) button to navigate to the sub-directory containing your standard EBA .ptvw files for your Back Office Integration(s)
a. The default for Macola ES is C:\Program Files\Exact Software\EBA\Macola_ES\Standard_Views\
b. The default for Globe is C:\Program Files\Exact Software\EBA\
c. For information about available standard templates for other integrations, please refer to integration-specific documentation
3. Change the Upload/Download Type to ptvw.
4. Click the “Mass Upload” option. This process will take several minutes and will end with a confirmation dialog.
The EBA Core 4.6 standard Exact distribution ships preconfigured with one default Back Office Environment and one default Back Office Site (which corresponds to a single back office database or schema), both of which will share the ODBC System DSN (named EBA_Site1) configured earlier. To enable use of this ODBC DSN, the database user id and password must be entered into EBA for the Site and the Environment.
Note: For security, the password is strongly encrypted in EBA’s database.
To enter (and verify) the database user and password for the default Site, follow these steps from within the System Administration module:
1. Access outline option Networkr Data Source Managementr Data Sources by Typer Siter Data Source for Default Site
2. Click the “Edit” button (on the toolbar at the top of the screen)
3. Enter your database user id into the Data Source User ID field (the 3rd field on the screen). This should be the same user id that you used to configure the EBA_Site1 ODBC DSN in step 4.3.
4. Enter your database password into the Data Source Password field (the 4th field on the screen). This should be the same password that you used to configure the EBA_Site1 ODBC DSN in step 4.3.
5. Click the “Post” button (on the toolbar at the top of the screen)
6. Click the “Verify” button. You should receive the message “Datasource Connection Verified.”
a. If verification fails, repeat steps 2 to 6, and make sure that the user id and password are entered correctly (some databases are case-sensitive).
b. If verification still fails, repeat step 4.3 above and use the “test” feature to verify the System DSN itself.
Similarly, to enter (and verify) the database user and password for the default Environment, follow these steps from within the System Administration module:
1. Access outline option Networkr Data Source Managementr Data Sources by Typer Environmentr Data Source for Default Environment
Because, the RDIS middleware server caches data sources, user ids and passwords when it first starts, execute the following steps to enable RDIS to connect to the default Environment / Site ODBC DSN:
1. Access menu option Tools/Reset Server
2. You will receive the message “The following server(s) were successfully reset: SERVER1”. Click the OK button.
Back office integration modules always include updated SQL scripts, which get executed against your back office database sites to create SQL Views, indexes, and other objects required to efficiently extract information from them.
To install the required new SQL scripts, follow these steps:
1. Access menu option Tools/SQL Script Manager
2. Click on the “Open Project...” button on the toolbar (the 3rd button).
3. Click the “Cancel” button to avoid saving the template sample project that is automatically loaded
4. Open the .SPF (SQL Project File) in the file system that corresponds to the back office integration you want to upgrade.
a. Macola ES 372 customers should open and run C:\Program Files\Exact Software\EBA\Macola_ES\SQL\1_ADD_ebams_site_objects.spf against their Macola ES 372 Site(s).
b. Globe 374 / 380 Users should open and run “Sql Project File” C:\Program Files\Exact Software\EBA\1_ADD_ebagb_site_objects.spf against their Globe Site(s).
c. Customers of other back office integrations should refer to integration-specification installation instructions.
5. Scroll down and select the appropriate site(s) under the EXACT_BUSINESS_ANALYTICS Environment. All sites must correspond to the specific back office integration being installed or upgraded.
a. The default site is typically called EBA_Site1, assuming a standard previous installation.
6. Click on the “Start Scripts” toolbar button (it is a green circle with a while arrow in it)
Note: This process will typically take 5 to 15 minutes for each site selected.
Every back office integration module includes a standard metadata database that includes all available integration modules. If you have not licensed all modules, or you have not implemented some of the back office modules corresponding to some of the available integration modules, then you should identify and “turn off” non-applicable integration modules. This step will prevent your Power User Interface users from being exposed to cube-building selections that are invalid or will not yield useful information.
To select the integration modules that will be shown to your Power Users:
1. Access outline option Networkr System Monitoring and Maintenancer Metadata Management r Maintain Metadata Modulesr EXACT_BUSINESS_ANALYTICS
2. All modules are selected, by default
3. Review the modules and de-select any that you do not want visible to Power Users
4. Press the “Process Modules” button
If you chose to de-select any of the metadata/integration modules (which affected only the “live metadata”), then you must promote the reduced metadata set to production as follows:
1. Access outline option NetworkrSystem Monitoring and MaintenancerMetadata ManagementrPromote MetadatarACTIVE METADATA
2. Enter “Standard Metadata with non-applicable modules hidden” as the Metadata Description, and click the Promote button.
3. Left-click on the metadata with the highest ID in the list (it will have the most recent “Date Promoted”)
4. Right-click and select “Make Production”
Note: The EBA Administrator of these back office systems may initially iterate several times through steps 10 and 11 until the available EBA licenses are optimally allocated to the user community.
A number of EBA Rights are available in the Back Office systems referenced above. Please review your back office documentation for information about assigning rights to roles and assigning roles to users.
Note: The EBA installation process created an EBA Administrator in its GSUSER table, based on the Windows User ID that was used to log on to the server, during the installation process. It is very important that at least one EBA Administrator, e.g. the Windows User ID that was used to log on to the server at the start of the installation, be present at all times in the back office system and be assigned the “EBA Administrator” right.
If the “EBA Administrator” right is not assigned to a user, then after step 11 is run nobody will be able to log on to the system with the System Administration client to administer it! In this case, RDIS must be temporarily re-configured for “Application Authentication”, and the hard-coded EXADMIN user id used to temporarily administer the system.
Note: This step is required for Exact Macola ES 372 and Exact Globe 374/380 customers only—other customers do not have this option and simply skip this step. Because of the new “menu option security” feature in EBA 4.6, you must import the menu option security information (for each user) from these back offices into EBA. In order to synchronize administrators in Exact Globe, EBA rights need to be added manually.
Follow these steps, from the Administration UI:
1. Access outline option NetworkrSystem Monitoring and MaintenancerManage External User Synchronization.
2. Verify that the appropriate sites are selected (change if necessary)
3. Click the “Synchronize Selected Sites” button
4. Check the screen for EBA License Management violation errors
a. These occur when all EBA Client Licenses have been used, but Back Office EBA rights have been assigned to additional users.
b. Click the “View Errors” tab to understand which user counts have been overrun.
Note: Users with license violation errors are NOT imported into EBA. If any violations occur, correct in the Back Office and re-run this step. Repeat this process until all available EBA client licenses are allocated to your users as desired. Contact your sales organization to acquire additional EBA client licenses.
All EBA back office integrations ship with a predefined Fiscal Calendar file that corresponds to the normal calendar. EBA uses this calendar file in a “fiscal-aware” date selection control, which allows users to easily switch between calendar and fiscal date time frame selections. As they change time frame types, the date control shows the corresponding from/to date selections.
If your fiscal calendar does not conform to the normal calendar, then you should update the default EBA Fiscal Calendar. Follow these steps, from the Administration UI:
1. Access outline option Environment DetailsrEnvironmentsrEXACT_BUSINESS_ANALYTICSrCalendar
2. Note that each row on the screen defines the Last (Calendar) Date of each Fiscal Year and Period
3. Maintain the table to establish your company’s fiscal calendar
4. Click the “Post Changes” button
Note: To support analysis by Fiscal Quarter, EBA needs to be able to derive fiscal quarters from this table. To achieve that, EBA requires that each fiscal quarter contain 3 fiscal periods, with the exception of the last fiscal quarter in a year—which may contain 4 periods. The fiscal calendar must be entered in increments of full fiscal quarters!
If you have licensed the eDeployment module, exit the System Administration module, and then run the Setup_EBA_eDeployment_EN.exe program and follow the on-screen instructions.
Prior to running automated schedules, eDeployment requires that a time zone be specified for each Environment.
To set the time zone of the EXACT_BUSINESS_ANALYTICS Environment, follow these steps:
1. Launch the Administration User Interface
2. Access outline option NetworkrEnvironment ManagementrEnvironmentsrEXACT_BUSINESS_ANALYTICS
3. Click the “Edit” button
4. Select your “Environment Time Zone” from the drop-down list
5. Click the “Post” button
Similarly, to set the time zone of the GPS SYSTEM INFORMATION Environment, follow these steps:
1. Access outline option NetworkrEnvironment ManagementrEnvironmentsrGPS SYSTEM INFORMATION
2. Click the “Edit” button
3. Select your “Environment Time Zone” from the drop-down list
4. Click the “Post” button
To start the eDeployment services:
1. Start all EBA eDeployment Windows Services via Start > All Programs > Exact Business Analytics > eDeployment > Start eDeployment Services.
2. Observe that all of the services have started successfully
a. Execute menu option Start > Control Panel > Administrative Tools > Services.
b. The 9 eDeployment services all start with “BI eDeployment”, and should all be in “started” status after several minutes.
c. Note that the “BI eDeployment Monitor” service monitors all of the other services and displays a tray icon for each one (usually in the lower right corner of the server screen).
d. Hover your mouse pointer over any of the eDeployment services tray icons to review its status.
3. If one or more of the services do not start, it may be the case that the user id does not have the necessary privileges. To troubleshoot:
a. Right-click on the BI eDeployment Director service, and select properties
b. Select the “Log On” tab
c. Temporarily select the “Local System Account” radio button (to enable the Apply button at the button)
d. Select the “This Account” radio button
e. Click on the “Apply Button”
f. At this point, a message should be displayed stating that the necessary privilege has been granted. If this is the case, then re-execute step 1 above (and all of the eDeployment services should start)
Note: Some of the eDeployment services can run under “Local System Account” and some of them must run under “This Account”. The setup program sets them as they need to be--do not change this setting!
Note: eDeployment contains a large number of options and can be configured so that it’s processing is distributed across many different machines. Please review the eDeployment documentation for information about configuring and operating eDeployment.
If you have licensed the Web Access Server module, then run the Setup_EBA_WebAccessServer_EN.exe program, and follow the on-screen instructions.
Note: Version 4.6 of this module requires MS IIS 6. Please review the Web Access Server documentation for information about configuring IIS 6 and Web Access Server.
Note: Turn on the new 4.6 Integrated Windows Authentication option to allow browser users to configure their browser to sign on automatically (without having to provide logon credentials each time).
To facilitate setup of individual clients, please copy the following client setup programs (only the ones that your company has licensed) from the download directory to c:\program files\GPS\UI:
1. Setup_EBA_Client_Adminui_EN.exe
2. Setup_EBA_Client_Expressui_EN.exe
3. Setup_EBA_Client_Powerui_EN.exe
4. Setup_EBA_Client_BusinessuiPlus_EN.exe
5. Setup_EBA_Client_Businessui_EN.exe
6. Setup_EBA_Client_Dashboard_AddInClient_EN.exe
7. Setup_EBA_Client_InstallHelper_EN.exe
Create a Share on folder: c:\program files\GPS\UI (if a Share does not already exist from a previous installation). This will enable “Client Registration Only” installations that simply create a shortcut on the user desktop pointing to this sub-directory.
If you have licensed the Express User Interface module, then please run the Setup_EBA_Client_Expressui_EN.exe program to deposit the software on the server. For the server installation, you must select the option “Complete local installation”, as noted on the screen!
Also run this program (from c:\program files\GPS\UI) on each appropriate client PC, to either create a shortcut pointing to the server, or to create a complete local installation.
If you want the EBA Administrator to have access to the System Administration module from his/her client PC, then please run the Setup_EBA_Client_Adminui_EN.exe program (from c:\program files\GPS\UI) on that client PC.
If you have licensed the Power User Interface module, then please run the Setup_EBA_Client_Powerui_EN.exe program to deposit the software on the server. For the server installation, you must select the option “Complete local installation”, as noted on the screen!
If you have licensed the Business User Interface Plus module, then please run the Setup_EBA_Client_BusinessuiPlus_EN.exe program to deposit the software on the server. For the server installation, you must select the option “Complete local installation”, as noted on the screen!
If you have licensed the Business User Interface module, please run the Setup_EBA_Client_BusinessUI_EN.exe SETUP program (from c:\program files\GPS\) on each appropriate client PC. The Business UI software itself is generally not run off of the server (since it is intended for disconnected users and does not connect to RDIS).
If you have licensed the Dashboard module, please run the Setup_EBA_Client_Dashboard_AddInClient_EN.exe program (from c:\program files\GPS\UI) on each client PC with a user that will design or use Excel-based dashboards.
Note: For Dashboard users that are only licensed to the Dashboard module (and not any of the other end user client modules—Express UI, Business UI, Business UI Plus, or Power UI), you must also run the Setup_EBA_Client_InstallHelper_EN.exe program (from c:\program files\GPS\UI). If you do not do this, those users will not be able to open the .ptvwzip attachment files that are emailed to them by eDeployment.
Since many EBA customers do not report or analyze by Transaction Currency, EBA ships with this capability turned off.
When this option is enabled, filtering on the Currency Type dimension governs whether Home and/or Transaction currency values are retrieved from the database and loaded into the cube. If this special query-control dimension is not filtered (or filtered to both), then both datasets are retrieved. This typically causes confusion for analysts not familiar with multi-currency analyses who report that all their quantities are doubled. Such analyses only make sense when the Currency Type and Currency Code dimensions are included. To eliminate this confusion, we now disable this little-used feature by default.
To enable this option:
Use SQL Scripter to run the Enable_Transaction_Currency.spf script against your active_metadata site. The active_metadata site is located in the Environment node under GPS System Information. Then promote your metadata. Metadata is promoted using the Network application (System Monitoring and Maintenance, Metadata Management, Promote Metadata). After you promote the metadata, you should make the just-promoted metadata snapshot the official “production” version by right-clicking on it and choosing the “Make Production” option.
To disable this option:
Use SQL Scripter to run the Disable_Transaction_Currency.spf script against your active_metadata site. Then promote your metadata. Metadata is promoted using the Network application (System Monitoring and Maintenance, Metadata Management, Promote Metadata). After you promote the metadata, you should make the just-promoted metadata snapshot the official “production” version by right-clicking on it and choosing the “Make Production” option.
Core EBA 4.6 Detailed Install Instructions (Upgrade)
This section is a superset of the section entitled EBA 4.6 “Quick Start” Instructions (Upgrade), and it provides additional detail for each step. This is required reading for people new to EBA, and is supplementary/reference material for people already familiar with EBA. The additional detail includes both step-by-step instructions, as well as explanatory background information.
Execute these steps to upgrade EBA. All steps must be executed in the documented sequence, unless otherwise noted.
This section includes the preliminary steps required to successfully upgrade EBA to version 4.6, and it assumes that the EBA 4.6 software and license key (if a new one is required) have been download to your server. Please review and execute the sections entitled “Downloading the EBA Software” and “Downloading the EBA License File”, if required.
Use the current version of the Administration UI module to check if any users are connected to the system (via menu option Tools/Realtime Server Monitor). If so, notify them that EBA will become inoperable while it is being upgraded, and that they should exit their EBA client module. Then exit this program.
Note: The Realtime Server Monitor provides a powerful real time “window” into the internal workings of EBA, including what processes and users are connected to the system, and what queries are currently flowing through the system (via the Query Admin tab).
Log on to your Windows Server with the Windows User Id that you use to administer EBA (if not already logged on with that User Id). This user must have administrative privileges on the machine.
EBA includes a number of Windows Services that must be stopped prior to installing the new versions of the programs.
Because the EBA 4.6 Core Bundle installs an upgraded version of the embedded Firebird database (version 2), any previous version must be manually removed.
To ensure easy recovery back to your previous EBA version (in the unlikely case of a serious upgrade problem), make a copy of the entire c:\program files\GPS sub-directory, and all of its contents.
This section describes the steps required to successfully upgrade Core EBA to version 4.6.
Run the Setup_EBA_EXT_Core_Bundle_EN.exe program and follow the on-screen instructions. Note:
· This program will automatically install and start the new version of the embedded Firebird Database required by EBA 4.6, along with a new “native” Firebird ODBC driver.
· Existing EBA-created Firebird EasySoft ODBC drivers are automatically converted to the new Firebird driver. It is recommended that any manually-created Easysoft ODBC entries be manually converted to Firebird ODBC (and any new driver entries created using the new Firebird driver, instead of Easysoft).
This program will ask you if you want to replace your active metadata. Answer “Yes” to this prompt only if you want to upgrade your back office integration(s) AND you are sure that your metadata has not been customized! In this case, you will be able to skip optional step 15 (which is to merge the new standard metadata with your customized active metadata), even if you are upgrading your back office integration(s).
If you want to upgrade your back office integration(s), but are unsure if your metadata has been customized, simply leave the default (do not replace the active metadata), and also skip steps 13, 14 and 15—which may be executed together at a later time. You MUST understand the state of your back office integrations (relative to customizations) to make an informed decision regarding upgrading to new integrations!
On the last screen of the Core Bundle setup program, click the “Launch AdminUI” button to launch the Administration UI module. This module is used to execute steps 8 through 16.
Upgrade the 3 EBA System Databases for the EXACT_BUSINESS_ANALYTICS Environment to 4.6.
1. Access outline option NetworkrSystem Monitoring and Maintenancer System Database Upgrader EXACT_BUSINESS_ANALYTICS
2. For each of the 3 pre-4.6 databases (Network, Metadata, Environment):
a. Select 4.6 in the drop-down list, and
b. Click on the corresponding lightning-bolt button to upgrade the database structure to version 4.6
3. Execute menu option Tools/Reset Server. This option executes a “soft restart” of the RDIS middleware, which does not disconnect any clients. It is used to ensure that RDIS is working with the most recent database structure and contents.
Note: The EBA database upgrade process upgrades from the current release that a database is at to the NEXT release, i.e. it works one release at a time. So, if given database is not at the 4.5 release, then 4.6 will not be an available selection, as stated in step 2.a, above. In this case, simply repeat steps 1,2.a, and 2.b, and 3 as many times as needed to upgrade to 4.6. For example, to upgrade a 4.4 database to 4.6, you will need to upgrade it 2 times: 4.4r4.5, and 4.5r4.6.
Upgrade the 2 EBA System Databases for the GPS SYSTEM INFORMATION Environment to 4.6.
1. Access outline option NetworkrSystem Monitoring and Maintenancer System Database Upgrader GPS SYSTEM INFORMATION
2. For the 2 pre-4.6 databases (Metadata, Environment):
b. Click on the corresponding lightning-bolt button to upgrade the database.
Note: the single Network database was already upgraded in the previous step and does not need to be addressed again in this step.
Note: The EBA database upgrade process upgrades from the current release that a database is at to the NEXT release, i.e. it works one release at a time. So, if given database is not at the 4.5 release, then 4.6 will not be an available selection, as stated in step 2.a, above. In this case, simply repeat steps 1,2.a, and 2.b, and 3 as many times as needed to upgrade to 4.6. For example, to upgrade a 4.3 database to 4.6, you will need to upgrade it 3 times: 4.3r4.4, 4.4r4.5, and 4.5r4.6.
If your licensing has changed, then install the new .lic file via menu option Tools/Install License, as follows:
1. Click the “Select File…” button and select the new .lic file from the file system
2. Review the license information on the screen, to ensure that it is what you expect. If not, click the “Close” button (and the new license will NOT be installed)
3. If the license is what you expect, then click the “Install License” button. You should receive a confirmation message “License Installed Successfully”.
Mass upload new standard EBA .PTVW template files into the Object Repository, for the GPS SYSTEM INFORMATION Environment. These templates are useful to monitor the health of your EBA implementation, and are also sometimes useful for support. This step will replace any previous system information templates.
1. Access outline option Networkr Environment Managementr Environmentsr EXACT_BUSINESS_ANALYTICSrObject ManagementrUpload / Download Objects en Mass
2. Click the ellipsis (…) button to navigate to the sub-directory containing your standard EBA System Information .ptvw files (default is C:\Program Files\GPS\Standard_Views\System).
Upgrade all existing .PTVW template files in the Object Repository, for the EXACT_BUSINESS_ANALYTICS Environment. This is required because 4.6 captures additional information for .ptvw objects, at object upload time.
2. Click the ellipsis (…) button to navigate to an empty sub-directory.
4. Click the “Mass Download” option. This process will take several minutes and will end with a confirmation dialog.
5. Click the “Mass Upload” option. This process will take several minutes, and will end with a confirmation dialog.
Note: Optional Steps 13, 14, and 15 must all be executed if you are upgrading your back office integration(s). This is because the .ptvw templates, SQL Scripts, and Metadata must be upgraded as a group, to remain consistent. However, as noted in step 7, if you replaced your active metadata, skip step 14 (even if you are upgrading your back office integration(s).
New back office integrations typically also include new template files, which have a file extension of .ptvw (this stands for Portable VieW).
To Mass Upload new standard EBA .PTVW template files into the Object Repository, for the EXACT_BUSINESS_ANALYTICS Environment, follow the steps below.
Note: this step will REPLACE any existing standard EBA templates with the same .ptvw name (in the file system).
Back office integration upgrades always include updated SQL scripts, which get executed against your back office databases to create SQL Views, indexes, and other objects required to efficiently extract information from them.
1. Use menu option Tools/SQL Script Manager
Note: For Macola ES 372, the same SQL Project, 1_ADD_ebams_site_objects.spf, is used (and required) for both upgrades and new installations. For upgrades, however, the first 4 .sql files in the project should not be run.
Please de-select 1_CreateEBABaseTbl.sql, 2_PopEBABaseTbl.sql, 1_CreateEBAFinHierTbl.sql, and 2_PopEBAFinHierTbl.sql before proceeding to the next step. Executing these files in the upgrade case may corrupt your EBA Fiscal Calendar and/or Financial Reporting Hierarchy with undesired rows.
Note: For Globe 374/380, the same SQL Project, 1_ADD_ebagb_site_objects.spf, is used (and required) for both upgrades and new installations. For upgrades, however, the first 4 .sql files in the project should not be run.
c. Customers of other back office integrations should refer to integration-specification installation instructions
Back office integration upgrades always include updated metadata, which must be merged into your customized active metadata. As noted above, this step may be skipped if your active metadata has never been customized and you replaced your active metadata in step 7.
To merge new standard metadata into a customized environment, follow these steps:
1. Access outline option NetworkrSystem Monitoring and MaintenancerMetadata ManagementrMerge MetadatarEXACT_BUSINESS_ANALYTICS
2. Click the “Merge” button.
Note: This process will take between 5 and 15 minutes. It merges the standard metadata into the “live” set of the active metadata, on a row-by-row basis. After successful merge, the new “live” set must be promoted to “production”, for use by eDeployment and the connected client modules (Power User Interface, Business UI Plus, and Express UI).
3. Access outline option NetworkrSystem Monitoring and MaintenancerMetadata ManagementrPromote MetadatarACTIVE METADATA
4. Enter “New Standard Metadata” as the Metadata Description, and click the Promote button.
5. Left-click on the metadata with the highest ID in the list (it will have the most recent “Date Promoted”)
6. Right-click and select “Make Production”
Note: This step is required for Exact Macola ES 372 and Exact Globe 374/380 customers only—other customers do not have this option and simply skip this step. Because of the new “menu option security” feature in EBA 4.6, you must re-import the menu option security information (for each user) from these back offices into EBA. In order to synchronize administrators in Exact Globe, EBA rights need to be added manually.
Follow these steps:
c. These occur when all EBA Client Licenses have been used, but Back Office EBA rights have been assigned to additional users.
d. Click the “View Errors” tab to understand which user counts have been overrun.
5. You should now exit the System Administration Module.
This new EBA 4.6 feature allows your connected users to avoid having to present logon credentials, if they are known to both Windows and to EBA, and have already been authenticated by Windows.
Note: This change should only be made if all of your EBA User Ids are also Windows User Ids! If they are not, however, a single SQL update statement for each user can convert your GSUSER table, for example to change a user from GPSJOHN to fandl186481:
Update GSUSER set GUUSPR='fand186481' where GUUSPR='GPSJOHN'
As long as each GSUSER.GUUSPR is set to correspond to a valid Windows User Id, the Windows Single Sign-On feature can be leveraged. Note that “Windows Single Sign-on” is the default Authentication for new installations.
To configure RDIS for “Windows Single Sign-on”:
1. Right-click on the RDIS tray icon (usually located in the lower right corner of the Windows desktop), and select Console
2. Click the red “Stop” button to enable configuration, then click the “Configure” button
3. Click the Next button and enter masterkey for the data source password
4. Click the Next button twice, and select the “Windows Single Sign-on” option
5. Click the Next button and the Finish button
6. Click the green Start button. The tray icon should turn green.
To test this authentication configuration change, launch the AdminUI client module, which should now sign you on automatically—if you are signed on to the Windows server with a user id known to EBA.
If you have licensed the eDeployment module, run the Setup_EBA_eDeployment_EN.exe program and follow the on-screen instructions. After running the program:
2. Verify correct operation by running a test schedule using menu option Tools/eDeployment Navigator (from the System Administration module).
If you have licensed the Web Access Server module, stop IIS 6, run the Setup_EBA_WebAccessServer_EN.exe program, and follow the on-screen instructions.
Note: Turn on the 4.6 Integrated Windows Authentication option to allow browser users to configure their browser to sign on automatically (without having to provide logon credentials each time).
If you have licensed the Express User Interface module (new at version 4.6), then please run the Setup_EBA_Client_Expressui_EN.exe program to deposit the software on the server. For the server installation, you must select the option “Complete local installation”, as noted on the screen!
If you have any “complete local installations” of the System Administration User Interface, then please run the Setup_EBA_Client_Adminui_EN.exe program (from c:\program files\GPS\UI) on all appropriate client PCs, to upgrade them.
If you have licensed the Power User Interface module, then please run the Setup_EBA_Client_Powerui_EN.exe program to deposit the software on the server. For the server installation, you must select the option “Complete local installation”, as noted on the screen! Make sure to install it in the same location as before, so that existing client PC shortcuts continue to operate.
If you have any “complete local installations” of this module, then please also run this setup program (from c:\program files\GPS\UI) on each such client PC, to upgrade it.
If you have licensed the Business User Interface Plus module, then please run the Setup_EBA_Client_BusinessuiPlus_EN.exe program to deposit the software on the server. For the server installation, you must select the option “Complete local installation”, as noted on the screen! Make sure to install it in the same location as before, so that existing client PC shortcuts continue to operate.
If you have licensed the Business User Interface module, please run the Setup_EBA_Client_BusinessUI_EN.exe program on each appropriate client PC. This program is generally not run off of the server (since it is intended for disconnected users and does not connect to RDIS).
Note: it is not required to upgrade all of your Business Users at the same time—the 4.5 Business User Interface program will work with .ptvw files created or refreshed by EBA 4.6.