Download Book - QAD.com

PRECISION Web UI 

Install Guide (4.6) 

Date: 

September 17, 2012

Contents 

Pre-Install Considerations ............................................................................................................ 3 

Select Destination Location .......................................................................................................... 4 

Select Components ...................................................................................................................... 5 

App Server Information ................................................................................................................. 6 

Database Type ............................................................................................................................. 9 

Database Connection Settings 1 ................................................................................................ 10 



Progress Location ....................................................................................................................... 17 

PRECISION Windows UI Files ................................................................................................... 19 

JMS Persistence ......................................................................................................................... 21 

Port Assignment ......................................................................................................................... 23 

PRECISION SOFTWARE: 

CONFIDENTIAL AND PROPRIETARY PAGE 2 OF 23 SEPT 17, 2011

Pre-Install Considerations 

When installing PRECISION Web UI/Highway over an existing install there are a 

number of item you need to consider: 

1. Backup old Highway Database. 

The Highway database can be found in “C:\PRECISION\WebUI\highway\db”. 

Backup the following four files: 

highwaydb.backup 

highwaydb.data 

highwaydb.properties 

highwaydb.script 

Install the new software. 

Copy the backed up database files, replacing the default database shipped with 

the installer. 

Note: It may be necessary to upgrade the database so the database schema is 

compatible with the latest version of PRECISION Web UI. 

2. Uninstall old PRECISION Web UI/Highway software. 

If you intend to use the uninstaller to uninstall an old version of 

Highway/PRECISION Web UI it is important to note that the windows registry 

information may be removed that is used by PRECISION Web UI. The unistaller 

should only be used prior to installing a new version and not after a new 

version of the software has been installed. 



Select Destination Location 

Please specify the directory in which PRECISION Web UI should be installed. When 

selecting a directory the following should be taken into consideration: 

1. The directory should be a local drive on the server. 

2. The directory name chosen should not contain any spaces. PRECISION Web UI 

will not function correctly if a directory such as “c:\program 

files\precision\webui” is specified. 

3. The install requires approximately 400MB of drive space. 



Select Components 

Please specify the PRECISION Web UI components that should be installed. This step is 

important if you wish to install a 64bit of the Java runtime. Installing a 64 bit version 

of Java allows you to allocate more memory to JBoss but can only be done if running a 

64bit version of the Windows operating system. 

There are a number of options to choose from. Each option will install a different set 

of components depending on your deployment requirement. Typically a full install 

should be chosen which means selecting one of the first two items from the drop 

down list. 

The first option should be used when the environment will be installed on a single 

server. 

The second option should be used if the environment will use JBoss on multiple 

servers and the queuing needs to be shared across these servers. 



App Server Information 

Server: 

Please specify the name of the server you are installing PRECISION Web UI on. 

The value of “localhost” should not be used. The actual machine name should be 

used. 

To determine the name of the machine you should: 

1. Open “Control Panel”. 

2. Double click the “System” icon. 

3. Select the “Computer Name” tab. 

4. Note the computer name. Do not include the Domain when entering the 

name. 

Skin: 

Please specify the PRECISION Web UI skin to be used. The skin selected will determine 

the look and feel of PRECISION Web UI. 



This should be set to “Default” unless instructed to do otherwise. 

HTTP Port: 

Please specify the port number that should be used by PRECISION Web UI to serve 

HTTP requests. 

PRECISION Web UI includes an embedded web server. By default port “8080” will be 

used by this web server. If another process is already using this port then the value 

should be changed. A free port number should be entered instead. 

HTTPS Port: 

Please specify the port number that should be used by PRECISION Web UI to serve 

HTTPS requests. This port is used to process pages that require encryption such as the 

login page. By default port “8443” will be used by this web server. If another process 

is already using this port then the value should be changed. A free port number should 

be entered instead. 

Use HTTPS to secure PRECISION Web UI login information: 

If this option is selected then SSL will be used encrypt data passed from the 

PRECISION Web UI login page to the web server. 

Automatically Start Highway when App Server Starts: 

If this option is selected then Highway will automatically be started when the App 

Server (JBoss) is started as a service. 

Automatically load compliance data when App Server Starts: 

If this option is selected then the DPL data will automatically be cached when the App 

Server (JBoss) is started as a service. Note this may take a few minutes and should 

only be selected if using the i3Comply module. 

JVM Memory Heap Size (MB): 

This allows you to specify the maximum memory the JBoss JVM will use. 

Service Identifier: 

This allows you to specify a prefix to any service names created. This is useful if you 

are installing multiple versions of PRECISION Web UI on a single server as it allows you 

to specify a unique string that will be used in the service name to distinguish it from 

other PRECISION Web UI installations. If this is not unique then previously installed 

services will be overwritten. 



Partition Name: 

This allows you to specify a name to a JBoss cluster. All JBoss nodes in the cluster 

should have the same name. Note this only applies to the cluster install. By default 

the partition name is that of the machine name. 



Database Type 

Database: 

Please specify the type of PRECISION database you have. Depending on the database 

type specified here the install will require slightly different information. 

PRECISION Web UI uses JDBC to connect to the PRECISION database. It is assumed that 

such a connection is already available. 



Database Connection Settings 1 

(Oracle Database) 

This screen captures the information needed to establish a JDBC connection to the 

PRECISION database. 

Host: 

Please specify the name of the server where the PRECISION database is residing. This 

can be the network machine name or the ip address of the server where the database 

is running. 

Service or Port: 

Please specify the service name or port number that should be used to establish a 

JDBC connection to the Host machine detailed above. 

Progress/OpenEdge: Specifies the database server or broker process which 

handles JDBC requests. This may or may not be the same broker process that handles 

4GL requests. This is the value used with the “-S” parameter in the database startup 

command. It is important that this service is added to the Windows “services” file for 

the server PRECISION Web UI is being installed on. 



Oracle: Port used by the Oracle listener. This is typically “1521”. 

AS/400: Port used by the AS/400. This is typically “6789”. 

To find out what port to use for JDBC on the AS/400, perform the following: 

On AS/400, enter command “WRKSRVTBLE”. 

Page down to find the service named “drda”. 

MS SQL: This is typically “1433”. This can be checked by examining the TCP/IP 

port configured within “SQL Server Enterprise Manager”. Run “SQL Server Enterprise 

Manager”, select the “Tools” menu, then select “SQL Server Configuration Properties 

…”. Now select the “Network Configuration …” button available when the “General” 

tab is picked. Finally select “TCP/IP” from the listed “Enabled protocols” and choose 

the “Properties…” button. The default port should be displayed. Enter this value 

here. 

Library: 

This field applies only to Progress and AS/400 databases. 

Progress/OpenEdge: A value of “pub” should be specified for a Progress database. 

AS/400: The library name where the database objects are stored on the AS/400 

should be specified here. 

Database: 

Progress/OpenEdge: Specify the physical name of the database as detailed 

within “ProControl” under “Physical DB-Name”. This will typically be either “xttrax” 

or “xttraxmu”. 

Oracle: Specify which database you want to connect to by entering the Oracle 

SID here. If examining the standard PRECISION Windows UI “trax.pf” file then the 

value that comes after the “@” character of the “-U” parameter should be used here. 

If using a “traxcon.ini” file, then the “TNSName” value should be used here. 

AS/400: Specify which database you want to connect to by entering the logical 

database name here. If using a “traxcon.ini” file, then the “LogicalDataBaseName” 

value should be used here. 

MS SQL: The name of the SQL database as listed in the “Databases” window of 

“SQL Server Enterprise Manager”. If examining the standard PRECISION Windows UI 

“trax.pf” file then the value associated with the “-db” parameter should be entered 

here. If using a “traxcon.ini” file, then the “PhysicalDatabase” value should be used 

here. 

Sort Table: 



This field applies only to AS/400 databases. 

AS/400: Specify the library and file name of the sort sequence table stored on 

the AS/400 server that is being used to support case insensitivity. 

“To enable DB2/400 database files to support case insensitivity, you must specify a 

case-insensitive Alternate Sequence Collating Table when you run DUPPRODB on the 

AS/400.” 

http://www.progress.com/progress/products/documentation/docs/dataserv/4ds/4ds 

.pdf 

e.g. “TRAX91BO/IBM037UCW” 

User: 

Please specify a user id. This user id will be used to establish a JDBC connection to 

the database. A database user should be specified here. This should not be confused 

with a TRAXi3 user. 

Password: 

Please specify the password associated with the user id specified above. 

Notes: 

Depending on the database type in question, the following JDBC url will be 

constructed based on the information entered above. 

jdbc:jdbcprogress:T:[Machine]:[JDBC Broker Service]:[Database];wa=536870912 

jdbc:datadirect:openedge://[Machine]:[JDBC Broker 

Service];databaseName=[Database] 

jdbc:oracle:thin:@[Machine]:[Listener Port, Default is 1521]:[Oracle SID] 

jdbc:as400://[Machine]: [Port, Default is 

6789]/[Database];compress=true;prompt=false;sort=table;sort 

table=[Library/Alternate Sequence Collating Table] 

jdbc:sqlserver://[Machine]:[Port, Default is 1433];DatabaseName=[Database] 

The JDBC driver needed to support a MS SQL database is not included in the install. 

You need to download this separately from Microsoft or locate it from the installation 

of the MS SQL Server software. 



It is recommended that you use the Microsoft SQL Server 2005 JDBC Driver 1.2 for 

PRECISION Web UI JDBC connectivity to both MS SQL Server 2000 and MS SQL Server 

2005. 

The driver can be downloaded from the following URL: 

http://www.microsoft.com/downloads/details.aspx?familyid=C47053EB-3B64-4794- 

950D-81E1EC91C1BA&displaylang=en 




This screen captures the information needed to establish a Progress 4GL client 

connection to the TRAXi3 database. 

Host: 

Please specify the name of the server where the TRAXi3 database (or in the case of 

Oracle and MS SQL the PRECISION Windows UI dataserver) is running. This can be the 

network machine name the ip address of the server where the database is running. 

In the case of a non Progress database the Progress4GL client communicates with the 

database via a dataserver. This dataserver can reside on a different server to that 

where the actual database is hosted. Examine the “trax.pf” file for the “-H” 

parameter value. If using a “traxcon.ini” file, then the “Host” value should be used 

here. 

Service or Port: 

Please specify the service name or port number that should be used by the Progress 

client to establish a connection to the database. Examine the standard PRECISION 

Windows UI “trax.pf” file for the value associated with the “-S” parameter. If using a 

“traxcon.ini” file, then the “ServiceName” value should be used here. 



-Mm: 

Specify the “Message Buffer Size” being used. Examine the standard PRECISION 

Windows UI “trax.pf” file for the value associated with the “-Mm” parameter. This is 

typically “8196” or “32600”. 

Physical Database Name: 

Please specify the physical database name. Examine the standard PRECISION Windows 

UI “trax.pf” file for the value associated with the “-db” parameter. If using a 

“traxcon.ini” file, then the “PhysicalDatabase” value should be used here. 

Number of Listeners: 

Please specify the number of listeners you which to install. Each listener will have its 

own Windows service entry. 




This screen captures further information needed to establish a Progress 4GL client 

connection to the TRAXi3 database. 

User: 

Please specify a TRAXi3 user. 

Password: 

Please specify a password for the TRAXi3 user specified above. 

Use database (JDBC) user/password to connect to database: 

This option applies only to non Progress database types. If connecting to an Oracle, 

AS/400 or MS SQL dataserver it is necessary to provide a database user and password 

as well as a TRAXi3 one. There are two options: 

1. The TRAXi3 user and password is also a valid database user and password. In 

this case this option can be left unticked. 

2. The TRAXi3 user and password is not a valid database user and password. In this 

case you should tick this option. The database user and password supplied 

earlier to establish a JDBC connection will be used as the user and password to 

establish a database connection for the Progress 4GL client. 



Client: 

Please specify a TRAXi3 client code. This will be used as the default login client code 

of the Highway Listener process. 

Progress Location 

Path: 

Please specify where Progress is installed. The entered path should point to the root 

directory where the Progress files are installed. 

Ideally Progress should not be installed in a directory path that contains spaces. 

Progress should not be installed in the “Program Files” directory. 

NOTE: If spaces do exist in the path then the “~” character should be used. 

e.g. Say Progress is installed in “C:\Program File\91D” then “C:\Progra~1\91D” should 

be entered. 

PRECISION Web UI needs to know where Progress is installed so that it can: 



1. If the TRAXi3 database type is Progress, the Progress software contains the 

necessary JDBC driver for PRECISION Web UI to connect to the database. 

2. The Highway Listener is a Progress 4GL client which needs Progress software in 

order to run. 



PRECISION Windows UI Files 

“trax.ini” File: 

When PRECISION Windows UI is installed it uses an ini file to initialize the PRECISION 

Windows UI client with default information. This ini file is also need by the Highway 

Listener. 

The location of the ini file can be determined from the PRECISION Windows UI 

shortcut. The shortcut should have a “-ininame” parameter which points to an ini file. 

This ini file should be entered here. 

If this ini file is not available to the server PRECISION Web UI is being installed on 

then the file should be copied locally to the server and the path and name entered 

here. 

Schema File: 

This option applies only to non Progress database types. If connecting to an Oracle, 

AS/400 or MS SQL dataserver it is necessary to specify the location of a schema file. 

Typically this file is called “shm_trax.db” and is installed as part of the standard 

PRECISION Windows UI install. 



The location of this file can be determined by examining the “trax.pf” file. A “-db” 

parameter specifying a shm_trax.db file should exist. Enter the path and name of the 

file here. Alternatively, if using a “traxcon.ini” file you should examine the 

“Database” value in the “ConnectParameters” section. 



JMS Persistence 

JMS Persistence Data source: 

Please specify where JMS messages should be persisted by Highway/JBoss while 

queued on a JMS queue. 

By default JBoss will use a HSQL database, however this is not recommended in a 

production environment. If you have a MS SQL, Oracle or OpenEdge database then 

they can be used to store JMS messages. 

If you select “TRAXi3 Database” the installer will attempt to configure 

JBoss/Highway automatically to use the TRAXi3 database. In order for this to work 

the JDBC user specified earlier must have permission to create tables and indexes 

in the TRAXi3 database. You can specify the database user credentials that are to 

be used by the JMS persistence process. 

Additional information is available in "TRAXi3 - 30006 - JBoss - HOW TO - Set Up 

JBossMQ on MSSQL, ORACLE or OPENEDGE". 

If you select “Local HSQL Supplied Database” the installer will configure 

Highway/JBoss to persist messages in the JBoss embedded database. 



Create a MS Windows Service entry for the Highway Database: 

By default Highway configuration information is held in a standalone HSQL 

database. It is possible to migrate this database to an Oracle, MS SQL or OpenEdge 

database, in which case there is no need to create a Windows service entry. 

Unselect this check box if you plan to migrate the Highway database. 

More information on how to do this is available in “TRAXi3 - 10026 - Highway - 

HOW TO - Setup Highway database in MSSQL, ORACLE or OPENEDGE.doc”. 



Port Assignment 

Ports Used: 

Listed are the static ports numbers used by JBoss, Highway and PRECISION Web UI. 

If any of these ports conflict with software already running on the server then a 

new number can be specified here. 

To determine what ports are currently in use on the server run the command line: 

netstat -nba > c:\temp\ports-being-used.txt 

Examine the output for possible port conflicts

Download Book - QAD.com

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?