Documente Academic
Documente Profesional
Documente Cultură
TaxFactory 10.0
I. Introduction to TaxFactory 10
A. Definition of Terms
TF10 Client – The TaxFactory 10.0 web application.
TF10 Client Instance – A collection of all components that when configured for an
environment, will render the TF10 Client.
Environment – This is a one-to-one relationship between the database and the TF10 Client.
Figure 1
A TaxFactory environment contains a single instance of the TF10 Client that is connected
to a single TaxFactory 10.0 database. This one-to-one connection between the web
application and database operates in isolation from other environments installed on the
same machine.
Figure 2
A TaxFactory 10.0 Client Instance consists of a web server, the TaxFactory application and its
associated shared libraries.
Figure 3
A TF10 Client Instance is accessible, via a web browser, from any workstation on the network.
This one-to-many relationship means that multiple users will be able to access the same TF10
Client Instance at one time. For example, multiple users will be able to access the TF10 Client
for their Production, QA, or Development environments simultaneously (Figure 3).
Figure 4
Alternatively, any one user is able to access multiple TF10 Clients from their workstation. For
example, a user can access the TF10 Client for their Production, QA, and Development
environments at the same time (Figure 4).
A. Backup custom data on TaxFactory 9.0.x using the Custom Backup/Restore via Tech Tools.
Back-up custom data
TaxFactory Main Menu > Tech Tools > Custom Backup/Restore > click the Back Up
button > Highlight the Dataset you want to backup > Enter filename and select storage
location or accept default filename and location (TFxx-xx-20xx.xml (the current date) and
default location (where TF90 Client installed)) > click Start.
B. Run the appropriate script to drop and create tables for TaxFactory 10.0 on your
system. e.g. TF10ddd.sql, where ddd is the database type; ora for Oracle, sqv for SQL
Server, inf for Informix, db2 for DB/2, etc. Please refer to the Server Section of the online
technical documentation for specific instructions for your server environment.
C. Create a new ODBC data source name for TaxFactory 10.0. See the Configuring the
ODBC Data Source section in the online technical documentation.
A. Prerequisites
For more information regarding these prerequisites, please see the online technical
documentation on the MyBSI Connect website.
Note: TaxFactory does not support Unicode. Create an OSS Note for any Unicode-related
questions.
1. The user must have administrative rights in the network server to perform the
7
2. The TaxFactory 10.0 database must be created and populated using the corresponding
SQL script.
Note: Database must be created as case-sensitive.
3. Java and Apache Tomcat 6, 7 or 8 must be installed.
4. The ODBC connections for TaxFactory 10 must be created. Please note that the ODBC
connections must match the installed Apache Tomcat 6, 7 or 8. Therefore, for a 32-bit
Tomcat, the 32-bit ODBC is required, and for a 64-bit Tomcat, the 64-bit ODBC is
required.
5. The installer depends on the JDBC connection information. The appropriate JDBC *.jar
file must be available. For each type of environment, details for *.jar file can be found
starting on page 18.
Note: Upgrading to Tomcat 8.0 may require the latest version of the JDBC *.jar file
for your environment.
B. Java Installation
Java must be installed on the network server. TaxFactory 10.0 Client requires Java 6 or
greater for Tomcat 6 or 7 and Java 7 or greater for Tomcat 8. For Tomcat 8, Java 8 is
recommended. If the appropriate Java version is already installed, skip to section C.
C. Tomcat Installation
Once Java is installed, the Apache Tomcat web server can be installed.
2. The Welcome screen lists the functions of the installer and the prerequisites for
installation. Click Next. (Figure 5 is an example with TF10k)
The user will enter the password for the release in the password entry screen. The
installation password is provided in the Download notice. Otherwise, the user contact
can e-mail a request for the installation password to BSI.SECURITY@BSI.COM. In
the subject line, indicate "Password Request - TF 10.0". Click Next.
10
Figure 6
Figure 7
11
5. Configuration Analyzer
a. If this is a first time installation, the configuration analyze indicates that none of the
environments are installed. (Figure 8)
Figure 8
b. If you have more than one Apache Tomcat web server installed, you must select your
Apache Tomcat web server from the dropdown selection. Click Next. (Figure 9).
Note: For the first environment install of a cyclic, you can change the Tomcat server.
All later environment installs of that cyclic will use the same Tomcat server.
12
Figure 9
Note: The number of WEB Servers that you may select from is based on which Tomcat
versions you have installed on your computer.
a. Tomcat will determine the default Java Virtual Machine (JVM) based on the
information available in the registry. If the Installer successfully determines the default
Java Virtual Machine then the confirmation screen will appear.
Note: If a specific JVM, other than default is desired to be used, then use Browse
button to navigate to the desired jvm.dll file.
13
Figure 10
b. If the Installer cannot determine the default Java Virtual Machine, then the Installer will
ask to navigate to the Java Virtual Machine (jvm.dll), which is to be used by Tomcat.
Use the Browse button to navigate to desired jvm.dll file.
c. Click Next.
This page allows you to select from two groups of environments: Standard
Environments and Extended Environments. The Standard Environments include the
Production, Development, QA, and Test (3) environments. Unless you plan to install
more than six environments, select only this option.
Note: You will not have to configure and install all six (or twelve) environments, as
you will be able to individually select which environments you want to install.
14
Figure 11
a. From here you will be able to select the individual environments you want to install.
The first environment is the Production Environment (Figure 12). If you want to
install subsequent environments prior to the installation of the Production
Environment, click Next until you arrive and the Environment Configuration page
you wish to install.
15
Figure 12
Figure 13
16
Complete the TaxFactory 10.0 Client Environment information. Select the radio
button for the type of database to be used and then fill out the application fields.
(Figure 14)
Note: For Oracle databases, only the *.jar file, Username, Password, and
Schema will be entered on this page. The next page will request the
tnsnames.ora entry for the database alias you wish to use. Please see the
Oracle section for further instructions.
Figure 14
MS SQL Server
1. MS SQL Server
Note: You will be prompted whether or not Windows Authentication is used for the
DSN connection.
2. sqljdbc4.jar.
Version 4 download
Note: Version two of the sqljdbc4.jar must be used for SQL Server 2003 and earlier.
Version 2 Download
3. This can be the default port or user selected
4. This can be the default name or user selected
5. This is the name of the database created for TaxFactory 10.
6. This is the schema for the TaxFactory 10 database.
7. The default listener for SQL Server is 1433
8. This is the host name of the TaxFactory 10 database server.
9. Select the ODBC connection to the TaxFactory 10 database.
Note: If Windows Authentication was specified in Step 1, the ODBC connection must
use Windows Authentication.
10. Enter the database Username and Password
DB2 (Native)
1. DB2 (Native)
2. TaxFactory supports the use of the Type 2 (db2jcc.jar) and Type 4 (db2jcc4.jar)
drivers. A license file, db2jcc_license_cisuz.jar or db2jcc_license_cu.jar, depending
on your OS, may be required as well. This will have to be manually placed in the
tomcat\lib directory. The drivers and licenses will come with the IBM or DB2 Client
software (E.g., C:\Program Files\IBM\SQLLIB\java). Otherwise, please contact your
DB2 provider for more information.
3. This can be the default port or user selected
4. This can be the default name or user selected
5. On AS400, this will be the local entry for the DSPRDBDIRE command, or it can be
the database library for TaxFactory 10. For other systems, this will be the Database
Name value.
6. On AS400, the schema name will be the database library for TaxFactory 10. The
default schema is TF10.
7. On AS400, the default listener is 446. Otherwise, this is the Service Name value for
the database node.
8. This is the host name of the TaxFactory 10 Database server
9. Select the ODBC connection to the TaxFactory 10 database
10. Enter the database Username and Password
IBM i (JT400)
1. IBM i (JT400)
2. jt400.jar. This comes with the IBM client software or it can be downloaded as part of
the JTOpen library from http://sourceforge.net/projects/jt400/
3. This can be the default port or user selected
4. This can be the default name or user selected
18
5. This will be the local entry for the DSPRDBDIRE command, or it can be the
database library for TaxFactory 10.
6. The schema will be the database library for TaxFactory 10.
7. The default listener is 446.
8. This is the host name of the iSeries machine.
9. Select the ODBC connection of the TaxFactory 10 database.
10. Enter the database Username and Password.
Sybase
1. Sybase
2. jconn4.jar. This can be downloaded from the Sybase website.
3. This can be the default port or user selected
4. This can be the default name or user selected
5. This is the name of the Sybase database created for TaxFactory 10
6. This is the schema for the TaxFactory 10 database
7. The default listener is 5000
8. This is the host name of the Sybase database
9. Select the ODBC connection for the TaxFactory 10 database
10. Enter the database Username and Password
MaxDB
1. MaxDB
2. sapdb.jar. This driver can be downloaded from the SAP DB website.
3. This can be the default port or user selected
4. This can be the default name or user selected
5. This is the name of the database for TaxFactory 10
6. This is the name of the schema for the TaxFactory 10 database
7. The default port is 7210. If the default port is used, leave the Database Port field
blank. Otherwise, type the database listener port in this field.
8. This is the host name of the TaxFactory 10 database
9. Select the DSN for the TaxFactory 10 database
10. Enter the Username and Password for the database login
HANA
1. HANA
2. ngdbc.jar. This driver can be accessed after running a version of the HANA Client
which you have licensed.
3. This can be the default port or user selected
4. This can be the default name or user selected
5. No database name is required for HANA.
6. This is the name of the schema for the TaxFactory 10 database
7. Enter the listener port established by the HANA administrator, usually in the format
of 3NN15 where NN is the instance of the database (no default port exists for HANA)
8. This is the host name of the TaxFactory 10 database
9. Select the DSN for the TaxFactory 10 database
10. Enter the Username and Password for the database login
19
Oracle
Oracle JDBC configurations work differently from other databases. From Figure 14
above, only fields 1, 2, 3, 4, 6, 9, and 10 will be completed on this page.
1. Oracle
2. ojdbc6.jar. This can be downloaded from the Oracle website. Please be sure to
download the driver based on the correct database version.
3. This can be the default port or user selected
4. This can be the default name or user selected
6. This is the schema name for the TaxFactory 10 database
9. Select the ODBC connection for the TaxFactory 10 database
10. Enter the database Username and Password
Once these values have been entered, click Next. The next page will prompt you for the
tnsnames.ora entry of the Database alias. Example is in Figure 15.
Figure 15
Paste the value from the tnsnames.ora file, starting with “(DESCRIPTION=…)”), into the
text editor and click Next.
Click Next once the configuration information has been entered. The next
Environment Configuration page will appear. From there you can either
continue installing more environments by repeating the steps in section ii above
or you can click Go to Confirmation Screen (Figure 16) to skip the remaining
20
environments, confirm the selection (Figure 17), and finish the installation.
(Figure 18)
Figure 16
Figure 17
21
Figure 18
Note: If you used a custom Web Service Port Number and/or a custom Web Server Service
Name during installation, use these values in the URL.
Note: During a Cyclic Upgrade, if you decide to change your Tomcat version from either
Tomcat 6 or 7 to Tomcat 8 and your database is either IBM I (jt400) or MaxDB, you
must download the latest JDBC *.jar file for your database type. You will not be able
to Update or Replace the existing Client version with the new Client version. You will
need to uninstall your specific environment (WEB Server Service) and reinstall it using
the new JDBC *.jar file.
23
14. Otherwise (If the upgrade will not change the Cyclic ISE version), check the “Update
existing TF10<y> Client with current TF10<y> Client” Option. If your database
and/or network equipment is configured to close a stale TCP/IP connection, then you
may wish to check the Set Enhanced Network Configuration Option. (Figure 21)
15. Click Next
16. If you have selected all of the environments you wish you upgrade, click the Go to
Confirmation Screen. Otherwise, repeat steps 13-15 until you have selected all the
Environments to be updated.
17. Select the “Update current Cyclic for <env> Environment(s) with TF10<y> Cyclic”
options for the Environments on the confirmation screen. The <env> represents the list
of environments to update.
18. Click FINISH (Figure 22)
24
25
26
Figure 23
27
Figure 24
28
Figure 25
1. Check the Review box in order to Review the Production configuration. If you do not
wish to review this environment, do not check anything and hit Next.
2. Review the Production configuration to determine the current configuration variables
for this environment. (Figure 26)
29
Figure 26
3. Select Next and repeat this process for the review of any subsequent environments.
4. Or, Select Back, until you are back to the Install/Review/Uninstall screen. This will allow the
user to install a repost of the currently installed cyclic, check the Update box and the newest
WAR File and JNI DLL will be loaded.
30
Figure 27
The system will display the informational box and opens the WEB Server Configuration screen, where
the Username and Password fields need to be populated with the new values (see Figure 28).
The client installation program will preserve the encryption setting for the environment. If your
environment is configured to use encrypted Username and Password (“Encrypt UID and PWD” box is
marked), then the new values will be encrypted in the WEB Server configuration file.
31
Figure 28
Enter the new Username and Password for the database login and click on the Next button. If no
other action is required, click on the Go to Confirmation Screen button.
Select the “Update Database connection credentials for <env> Environment(s)” options for the
environments on the confirmation screen. The <env> represents the list of environments to update
the Database Connection Credentials.
32
33