Académique Documents
Professionnel Documents
Culture Documents
BluePhoenix AppBuilder 2.1.0. Document Title April, 2003 Corporate Headquarters BluePhoenix Solutions Vlierwerf 7B 4704 SB Roosendaal The Netherlands +31 (0) 165 399 401 +31 (0) 165 396 308 fax USA Headquarters BluePhoenix Solutions USA, Inc. 8000 Regency Parkway Cary, NC 27511 United States +1 919.380.5100 +1 919.380.5111 fax www.bluephoenixsolutions.com
1992-2003 BluePhoenix Solutions All rights reserved. BluePhoenix is a trademark of BluePhoenix Solutions. All other product and company names mentioned herein are for identification purposes only and are the property of, and may be trademarks of, their respective owners. Portions of this product may be covered by U.S. Patent Numbers 5,495,222 and 5,495,610 and various other non-U.S. patents. The software supplied with this document is the property of BluePhoenix Solutions, and is furnished under a license agreement. Neither the software nor this document may be copied or transferred by any means, electronic or mechanical, except as provided in the licensing agreement. BluePhoenix Solutions has made every effort to ensure that the information contained in this document is accurate; however, there are no representations or warranties regarding this information, including warranties of merchantability or fitness for a particular purpose. BluePhoenix Solutions assumes no responsibility for errors or omissions that may occur in this document. The information in this document is subject to change without prior notice and does not represent a commitment by BluePhoenix Solutions or its representatives.
TABLE OF CONTENTS
Table of Contents
ii
CHAPTER
This guide describes how to install the AppBuilder product in a Windows 2000 environment. Before you begin installing this software, be sure to read the ReleaseNotes.html file in the root directory of the CDROM for the latest information. Table 1-1. lists the installation procedures required.
Table 1-1 Procedure Meeting System Requirements Installing AppBuilder 2.1.0 Performing a Silent Installation Viewing Version Information Modifying or Uninstalling Product Installation procedures Description Verifying that you have the required hardware and software before beginning an installation Installing the software on the workstation or workgroup server Installing the product on multiple machines from a setup response file with no user interaction Viewing version or update information about which products are installed on a machine Modifying which products are installed or uninstalling the entire set of products
1-1
AppBuilder Server and Repository hardware configuration Recommendations INTEL Pentium 450 MHz or greater or equivalent 512 MB RAM or greater depending on performance required Workgroup Repository, 500 MB minimum, three physical hard drives recommended Departmental Server, 500 MB minimum Gateway Server, 250 MB minimum These requirements depend on the size of the applications and the amount of information saved in the repository. These requirements are in addition to those needed for the applications created and database used. Any SVGA or above Any Any
Hard-disk space
The requirements listed here are for AppBuilder software only. Third-party software may require additional resources. Refer to vendor documentation for details on any additional requirements necessary. When selecting a machine, consider the resources used by other software on that machine. For example, do not install development environment software on a machine that is also being used as a Web server unless you have made sure that resources are available for both.
1-2
Third-Party Requirements
Table 1-4 specifies the third-party requirements for installing this release of AppBuilder on Windows. Use this as a guideline. For a complete list of third-party support, refer to the Third-Party Support Matrix available on the Customer Support Web site.
Table 1-4 Third Party Requirements Windows Version Communicationsa
Product
Database Oracle: Oracle 8.1.7 Programmer/ 2000 8.1.7 Windows: SQL Server 2000 SP3 Development Tools 2000 SP3 IBM: UDB 7.1 or 7.2 SP6 Application Development Client 7.1 or 7.2 SP6 Oracle: Programmer/ 2000 8.1.7 Windows: SQL Server 2000 SP3 Development Tools 2000 SP3 IBM: UDB 7.1 or 7.2 SP6 Application Development Client 7.1 or 7.2 SP6
Other
Construction Workbench
2000+SP3
Browser: IE 6.0 SP1 Compilers: MS Visual C++ 6.0 SP5 MS 7.0 in .NET Studio
C Development
2000+SP3
Named Pipes TCP/IP LU2 0 Wall Data Rumba 1 AttachmateExtra 6.3 2 IBM PComm 5.1 LU 6.2 0 IBM Comm Server 4.3 1 Microsoft SNA Server 4.0
Java Development
2000+SP3
JDK: Sun SDK 1.3.1.06 WebServers/ AppServers: IBM WebSphere 4.0 FP5 BEA WebLogic 6.0 SP2 Apache Web Server with Tomcat plugin 1.3x JDKs: Sun SDK 1.3.1.06 J2EE 1.3 WebServers/ AppServers: IBM WebSphere 4.0 +FP5 BEA WebLogic 6.0 +SP2
2000+SP3
1-3
Table 1-4
Product
Database
Other JDKs: Sun SDK 1.3.1.06 J2EE 1.3 WebServers/ AppServers: IBM WebSphere 4.0 +FP5 BEA WebLogic 6.0 +SP2 Apache Web Server with Tomcat plugin Browser: IE 6.0 SP1
Named Pipes Named Pipes TCP/IP Named Pipes LU 6.2 0 IBM Comm Server 4.3 1 Microsoft SNA Server 4.0 TCP/IP Named Pipes LU 6.2 0 IBM Comm Server 4.3 1 Microsoft SNA Server 4.0 TCP/IP Named Pipes LU2 0 Wall Data Rumba 1 AttachmateExtra 6.3 2 IBM PComm 5.1 LU 6.2 0 IBM Comm Server 4.3 1 Microsoft SNA Server 4.0 TCP/IP Named Pipes LU 6.2 0 IBM Comm Server 4.3 1 Microsoft SNA Server 4.0
IBM UDB 7.1 or 7.2 FP6 MS SQL Server 2000 SP3 Oracle 8.1.7
Departmental Server
IBM UDB 7.1 or 7.2 FP6 MS SQL Server 2000 SP3 Oracle 8.1.7
Client Runtime
MS SQL Server SP3 IBM UDB 7.1 or 7.2 FP6 Oracle 8.1.7
1-4
Table 1-4
Product
Database
Other Browser: IE 6.0 SP1 for Online Help Acrobat: Adobe Acrobat 4.0 or higher for viewing PDFs.
Documentation
2000+SP3
a. Most communications functionality is embedded in the operating system, except for the SNA Server and Communications Server.
Java Requirements
It is necessary to install Java Standard Edition 1.3.1.06 before installing AppBuilder Open Generation Java products. If you do not have Java installed, you will receive an error message stating that the system failed to create a start menu entry. In addition to the items listed in Table 1-4, the following items are necessary for Java development. For invoking or deploying Web Services, if the application server does not supply a SAX-based Java parser as part of their execution environment, use the Apache XML parser for Java, Xerces version 1.4 or higher. For the Report Writer, use Java runtime environment Standard Edition 1.3.1.06.
1-5
1-6
CHAPTER
AppBuilder 2.1.0 installation is supported only on a machine that does not have a previous version of AppBuilder installed. If necessary, remove any previous versions of AppBuilder before you install AppBuilder 2.1.0. You can install Appbuilder from a CD-ROM or from a self-extracting file: Installing from a CD Installing from a self-extracting file
Installing from a CD
Take the following steps to install AppBuilder 2.1.0 from a CD: 1. 2. Insert the AppBuilder Installation CD-ROM into the CD-ROM drive. Start the AppBuilder installation process by doing one of the following: Open an icon view of the CD then double-click the Setup icon. From the Windows desktop, select Run > Start menu then type: <source drive>:\setup The Welcome dialog is displayed (See Figure 2-1).
2-1
Figure 2-1
Welcome dialog
2.
Destination Folder
2-2
3.
If Yes is selected, the Choose Destination Location dialog displays. The default installation path is displayed in the Destination Folder area. If you want to change the destination, click Browse, browse to the new location, and click OK. Click Next to accept the installation folder. If you are going to install on the default drive C:\ in a folder that does not already exit, a message box appears asking if you want that directory automatically created. Click Yes to continue.
4. 5. 6.
Select Components 7. The installation program displays the Select Components dialog (see Figure 2-2).
Select components dialog
Figure 2-2
8. 9.
Click in the check box to select the items you wish to install at this time. The AppBuilder documentation is an installation option. To install the HTML help system for AppBuilder 2.1.0, check the Documentation check box. The PDF files are located on your CD and on the BluePhoenix Solutions Support Web site. The content of the PDF files is the same as the content in the online help only the format differs and is a printer-friendly format.
10. The default settings include only the Construction Workbench and Documentation. If you want to install any other products select the appropriate box. 11. The Construction Workbench must be selected in order to install the TurboCycler Development Kit, the Personal Repository, or MLUI. 12. Preparation and Test Server is a subcomponent of Departmental Server. Install the Preparation and Test Server on machines that act as preparation servers: as machines to which preparation requests are sent from the Construction Workbench. The Preparation and Test server is also used to test the applications that are part of remote preparation.
2-3
13. At least one component must be selected for the installation to proceed. If nothing is selected, a message box displays prompting you to choose a component. Select Program Folder 14. The Select Program Folder dialog appears (see Figure 2-3).
Figure 2-3 Select Program Folder dialog
15. Accept the default program folder name AppBuilder or specify a different folder name either by typing a new name in the Program Folders field or by choosing a folder name from the Existing Folders list. Click Next when you are ready to continue. Copying files 16. The Start Copying Files dialog appears (Figure 2-4).
2-4
Figure 2-4
17. Review the installation choices listed in Current Settings. To change any of these settings, click Back until you return to the dialog that contains the information you want to change. To accept the displayed settings and install the selected AppBuilder products, click Next. 18. The installation program displays a series of progress messages during installation. The status is displayed, as shown in Figure 2-5.
2-5
Figure 2-5
Communications Configuration 19. When this part of the installation is complete, several additional configurators may run depending on what combination of products were selected. For example, another type of wizard screen is displayed for the configuration of communications. The sequence is shown in Figure 2-6. You can accept the defaults in these screens and later go back and change the configuration. For details on how to configure communications and the meaning of these options, refer to the Configuring Communications Guide. With each screen, click OK when done selecting options.
2-6
Figure 2-6
Figure 2-7
20. There is also a configuration dialog for the Workgroup (Freeway) Repository client that is necessary for the Construction Workbench if you are connecting to a workgroup repository. In the screens displayed in Figure 2-8, enter the name of the workgroup repository or use the buttons to add a new
2-7
Freeway and click OK when done. If you are connecting to (using) a local repository only, you can click Cancel on these screens.
Figure 2-8 Workgroup repository client configuration
21. For installation of a workgroup (Freeway) server, an additional Freeway server configurator is run. Refer to Configuring the Repository for information about configuring a workgroup repository. 22. At this point the registry settings and environment variables have been added; however, to ensure that the application is fully operational, you need to restart (reboot) the machine. Restart the machine 23. The installation program gives you the option to restart now or wait until later. Either accept the default choice (Yes, I want to restart my computer now) or click to select the optional choice (No, I will restart my computer later) then click Finish. The initial installation of the software is not complete until the machine is rebooted. You must restart the computer after completing the installation process in order for the software to become completely operational. 24. Refer to Modifying or Uninstalling Product only if you want to modify this installation. Refer to the Configuring Communications Guide for more information about modifying the AppBuilder communications between repositories and servers.
installation setup dialog is displayed with the options available for modifying the installation. Refer to Figure 2-9.
Figure 2-9 Installation setup dialog
2-9
Figure 2-10
Deselect any installed components that you want to remove, and check any new components you want to install. What you have checked on this dialog will be installed on your system. Anything that is not checked will be removed if necessary. When you add and remove components: INI file settings are preserved, but user comments in the ini files are not preserved. User-created files are not modified. Any applied RFX or EFX maintenance is removed. The value of adding or removing components is that you can customize your installation with components that you need or want. When you are satisfied with the components you have selected, click Next to begin the modifications.
2-10
From the installation setup dialog displayed in Figure 2-5, select Repair and click Next. This re-installs and overwrites all the product components that were installed the last time the installation or setup was run: INI file settings are preserved, but user comments in the ini files are not preserved. User created files are not modified. Any applied RFX or EFX maintenance is removed. Wait until this installation is complete and the machine has rebooted before you reapply a maintenance package, then follow the instructions in the release notes for each maintenance package. The value of the repair option is that you can return the product to a well-defined AppBuilder 2.1.0 installation level. It is a way of resetting the installation to a known configuration.
2-11
Management Console, click on the icon for the computer and right-click, as shown in Figure 2-11. From the pop-up menu, select View Product Information.
Figure 2-11 Calling Product Information from Management Console
The Product Information window contains several tabs: Base - Contains the version of AppBuilder Products - Contains a list of products and their installation dates and versions EFX - Contains a list of emergency fixes (EFXs) applied RFX - Contains a list of rollup fixes (RFXs) applied Fixpack - Contains a list of fixpacks applied
2-12
to use it in order to get product information. Running abprdinf.exe creates a list of products and fixes, and displays the list to the screen as well as to a file.
2-13
This file contains the choices you made during installation specifying how you want AppBuilder installed. 4. To launch the silent install, copy the setup.iss file from the system directory to the directory containing the setup. Enter the following in the directory containing the setup: setup -s 5. When running an install in silent mode, be aware that there are no messages displayed. Instead, setup creates a log file (setup.log) in the directory containing the response file; this log file contains a report on the silent install including whether the install was successful. You can review the log file and determine the results of the install. After the silent installation, if you have set the restart option, the computer restarts. After the restart, the configurators run.
6.
2-14
CHAPTER
This section provides step-by-step information about installing server software on Windows machines. The following information is covered in this section: Installing the Preparation and Test Server Installing the Production Server
3-1
2.
On the Select Components dialog, select the product to install on the production machines. Refer to Table 3-1 for a summary of the options.
Production product options summary Description of software on the target machine Client Runtime for Windows is a production installation of the runtime and middleware required to execute AppBuilder client applications for Windows. These modules are also installed with the Construction Workbench. Departmental Server is the runtime and middleware required to execute AppBuilder server modules. Gateway Server is a protocol switching facility often used to connect client applications using TCP/IP to mainframe modules using LU6.2. Refer to Figure 3-1 for a representation of these functions of a Gateway Server.
Client Runtime
Departmental Server
Gateway Server
Figure 3-1
3-2
CHAPTER
Installing a workgroup repository on Microsoft Windows 2000 Server involves: Meeting Requirements Installing a Workgroup Repository Configuring the Repository Creating a Custom Setup Creating a Workgroup (Freeway) Database Configuring the Workgroup (Freeway) Database Autostarting the Freeway Service
Meeting Requirements
Support includes: Windows Requirements Network Protocols Database Management Systems
Windows Requirements
Supported platforms and system requirements are listed in Table 4-1.
Table 4-1 Hardware Pentium 450MHz minimum Windows requirements Operating System Disk Space Minimum 100 MB for Workbench repository installation (500 MB recommended for usage) Memory
512 MB
4-1
Meeting Requirements
Network Protocols
Table 4-2 lists the network protocols supported by AppBuilder Workgroup Repository.
Table 4-2 Protocol Named Pipes Supported network communication protocols Product Microsoft (bundled with OS)
AppBuilder supports Microsoft's Windows 2000 implementation of Named Pipes. This software provides intermachine communications support. The named pipes can be transported on either NetBEUI or TCP/IP (using the TCP/IP NetBIOS Helper Service.)
4-2
4-3
Figure 4-1
5.
For the Freeway Database Setup, if you choose Custom Setup define the following fields and cibtubye to Table 4-4 for descriptions of each parameter. If you are choose Typical Setup continue to
Figure 4-2.
User name: Password: Create Database: Typical or Custom Setup: Import repository data: Data File Location: Working Directory:
Table 4-4 Parameter Database setup window parameters Description Defines the valid user identifier for the SQL Server Administrator. The user identifier determines the owner of the Freeway tables. The default SQL Server Administrator user identifier is sa, with the default table owner dbo, or database owner. Defines the password for the user identified by the userID. Select the SQL Server and Windows 2000 security option to define the password in SQL Server. Provides the option to perform a Typical Setup or a Custom Setup. For information on the Custom Setup, refer to Creating a Custom Setup. The selection determines the additional parameters that must be defined, such as database filename, size, options and device options.
User ID
Password
4-4
Database setup window parameters Description Identifies the complete path name for the archive file. The system imports data from this archive file into the workgroup (Freeway) database. This file also includes information about default repository objects commonly reused during development. Associated flat files are common to this file as well, such as rule source and window panel information. The import of the data file is representative of what the Repository Administrator will do on an ongoing basis during the development effort. Specifies the temp directory to be used during the setup process.
Working Directory
For example: User name is <sa>, with a null password. The default repository is located in: AppBuilder\ad\dbf\dbbackup\ABREPDEF.exp 6. 7. Click OK. Figure 4-1 shows the Freeway Server Setup window. The following message displays: Default Freeway Repository was successfully imported. Would you like to view the log file? 8. 9. Click YES. Freeway Server Configuration is complete. Click OK.
For a typical setup, for most cases, define the database file name and the database size, as shown in Figure 4-2 and summarized in Table 4-5. For more options, instead of using the typical setup, use the custom setup as described in Creating a Custom Setup.
Figure 4-2 Typical setup
4-5
Typical workgroup Repository setup Description Settings about the underlying database. The name of the database; for viewing only. The name of the server; for viewing only. Specifies the location of the database. The default location within SQL Server is \MSSQL\DATA, though the Freeway Administrator may redefine this parameter. The Freeway database requires a minimum of 40MB. This should be sufficient for most beginning to mid-sized repositories. As the scale of the development effort increases, the Freeway database may be expanded. For more information on expanding a database, refer to Microsoft SQL Server Online Help.
Database Details Database Name Database Server Name Database File Name
Database Size
4-6
Figure 4-3
Device Options
Database Options
4-7
Figure 4-4
4-8
Figure 4-5
Creating a Database
Once the administrator elects to create the database, the installation program uses the following procedure to create a workgroup (Freeway) database: 1. Prior to creating the workgroup (Freeway) database, the target SQL Server defined for the Freeway Database Setup must be registered within SQL Server and the Microsoft SQL Server Service must be up and running. For more information on registering a server in SQL Server, refer to the Microsoft SQL Server Online Help. Installs the Freeway Manager service (that manages the workgroup repository). Creates an Open DataBase Connectivity (ODBC) data source. Creates the workgroup (Freeway) database. Creates all the tables used by the workgroup repository. Imports the contents of the data file into the tables in the workgroup (Freeway) database.
1. 2. 3. 4. 5.
Pay careful attention to the sequence of events in case the creation of the database is unsuccessful.
4-9
4-10
Figure 4-6
4-11
4-12
4-13
4-14
Index
INDEX
AppBuilder 2.1.0 Installation Guide for Windows
C
Client Runtime 3-2 codepage administrator settings 4-2 communication protocols 4-2 creating a Freeway database 4-9 custom database setup 4-6
Freeway Service Manager automatic start 4-10 setup 4-12 startup properties 4-12
G
Gateway Server 3-2
D
data size 4-7 database minimum size 4-6 database create options settings 4-4 database file name field 4-6 database management 4-2 database options field 4-7 database owner 4-4 database setup custom 4-6 typical 4-5 database size field 4-6 default repository 4-5 default table owner 4-4 defining a Freeway Server ID 4-6 Departmental Server 3-2 device options field 4-7
H
hardware requirements 1-1 help product information 2-11
I
import data file settings 4-5 Installing the AppBuilder Software 2-1
L
log size field 4-7
M
machine target 3-1 minimum hardware 1-1 MSSQLServer startup properties 4-12
F
Freeway database data size 4-7 database options 4-7 device options 4-7 password 4-4 setup 4-4, 4-9 user ID 4-4 Freeway Manager 4-3, 4-9 Freeway Server Configuration 4-3, 4-5 Freeway Server system ID 4-6
N
named pipes 4-2 NetBEUI 4-2 network protocols 4-2
P
password for Freeway database 4-4 PC requirements 4-1 Preparation & Test Server 3-1
Preparation and Test Server 3-1 prerequisites SQL server 4-2 product information 2-11
W
Welcome dialog 2-2 Windows 2000 named pipes support 4-2 working directory settings 4-5
R
requirements hardware 1-1 PC 4-1
S
Select components dialog 2-3 Select Program Folder dialog 2-4 server Departmental 3-2 Gateway 3-2 preparing and testing 3-1 Server Configuration Tool setting up a Freeway repository 4-3 setting the Freeway service to start automatically 4-12 Setting up Target Clients and Servers 3-1 SQL character set 4-2 character sets and backups 4-2 configuration options 4-3 server settings 4-2 sort order 4-2 SQL Server Administrator user ID 4-4 SQLServer version 4-2 Start Copying Files dialog 2-5 system requirements 1-3
T
target machines 3-1 TCP/IP 4-2 temporary directory 4-5 typical database setup 4-5
U
user identifier for Freeway database 4-4
ii