App Builder Installation Win

8/14/2019 App Builder Installation Win

http://slidepdf.com/reader/full/app-builder-installation-win 1/42



BluePhoenix AppBuilder 2.1.0.Document TitleApril, 2003

Corporate Headquarters

BluePhoenix Solutions

Vlierwerf 7B4704 SB RoosendaalThe Netherlands+31 (0) 165 399 401+31 (0) 165 396 308 fax

USA Headquarters

BluePhoenix Solutions USA, Inc.8000 Regency ParkwayCary, NC 27511United 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 namesmentioned herein are for identification purposes only and are the property of, and may be trademarksof, 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 furnishedunder a license agreement. Neither the software nor this document may be copied or transferred by anymeans, electronic or mechanical, except as provided in the licensing agreement.

BluePhoenix Solutions has made every effort to ensure that the information contained in this documentis accurate; however, there are no representations or warranties regarding this information, includingwarranties of merchantability or fitness for a particular purpose. BluePhoenix Solutions assumes noresponsibi li ty for errors or omissions that may occur in this document. The information in thisdocument is subject to change without prior notice and does not represent a commitment byBluePhoenix Solutions or its representatives.

http://www.bluephoenixsolutions.com/

http://www.bluephoenixsolutions.com/



AppBuilder 2.1.0 Installation Guide for Windows i

TABLE OF

CONTENTS

Table of Contents

AppBuilder 2.1.0 Installation Guide for Windows

1 Bef ore You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Meeting System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Minimum Hardware Requirements for Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Third-Party Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

2 Installing AppBuilder 2 .1 .0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Installing from a CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Installing from a self-extracting file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Continuing the installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Modifying or Uninstalling Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Adding or Removing Installation Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Repairing the Installed Product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Uninstalling the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Viewing Version Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11From the Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11From the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12From the Product or Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Performing a Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

3 Servers on Windows Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Installing the Preparation and Test Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Installing the Production Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

4 Workgroup Repository on Windows M achines . . . . . . . . . . . . . . . . . . . . . . 4-1

Meeting Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Installing a Workgroup Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Configuring the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Creating a Custom Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Creating a Workgroup (Freeway) Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Enabling a Group Repository for Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Autostart ing the Freeway Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Setting the Freeway Service to Start Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12



ii AppBuilder 2.1.0 Installation Guide for Windows



AppBuilder 2.1.0 Installation Guide for Windows 1-1

CHAPTER

1

BEFORE YOU BEGIN



This guide describes how to install the AppBuilder product in a Windows 2000 environment. Before youbegin installing this software, be sure to read the ReleaseNotes.html file in the root directory of the CD-ROM for the latest information.

Table1-1. lists the installation procedures required.

M eeting System Requirements

Be sure that you understand the system requirements before beginning installation. These include:

Minimum Hardware Requirements for Installation

• Third-Party Requirements

• Java Requirements

• WebSphere Development Requirements

• WebLogic Development Requirements

• Apache with Tomcat

Table 1-1 Instal lation procedures

Procedure Description

Meeting System RequirementsVerifying that you have the required hardware and software

before beginning an installation

Installing AppBuilder 2.1.0 Installing the software on the workstation or workgroup server

Performing a Silent InstallationInstalling the product on multiple machines from a setup

response file with no user interaction

Viewing Version InformationViewing version or update information about which products

are installed on a machine

Modifying or Uninstalling ProductModifying which products are installed or uninstalling the entire

set of products



1-2 Before You Begin

Meeting System Requirements

M inimum Hardw are Requirements for Installat ion

The following hardware configurations are required and must be operational prior to the installation ofthis software. Table1-2 specifies the minimum and recommended hardware requirements for installingAppBuilder Workbench Tool products. These do not include the hardware for application servers andother third-party software that you may use.

The requirements listed here are for AppBuilder software only. Third-party software may requireadditional resources. Refer to vendor documentation for details on any additional requirementsnecessary. 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 aWeb server unless you have made sure that resources are available for both.

Table 1-2 AppBuilder Workbench Tools hardware configuration and Open Generation

Hardware Recommendations

CPU Pentium II 450 MHz or greater or equivalent

Memory 256 MB RAM or greater

Hard-disk space 500 MB minimum depending on configuration, 1 GB recommended.

Display SVGA or above

Mouse Any

Table 1-3 AppBuilder Server and Repository hardware configuration

Hardware RecommendationsCPU INTEL Pentium 450 MHz or greater or equivalent

Memory 512 MB RAM or greater depending on performance required

Hard-disk space

• 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.

Network Card (Communications) Any

Display SVGA or above

Keyboard Any

Mouse Any





Third-Party Requirements

Table1-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 Thi rd-Part y Support Matr ix available on the Customer Support Web site.

Table 1-4 Third Party Requirements

Product

Windows

Version Database Communicationsa Other

Construction

Workbench2000+SP3

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

Browser:

• IE 6.0 SP1

Compilers:

• MS Visual

C++ 6.0 SP5

• MS 7.0 in

.NET Studio

C Development 2000+SP3

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

• 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

Compilers:

• MS Visual

C++ 6.0 SP5

• MS 7.0 in

.NET Studio

Java Development 2000+SP3

Oracle:

• Oracle 8.1.7

IBM:

• UDB 7.1 or 7.2 SP6

• TCP/IP

• IBM MQSeries 5.2

JDK:

• Sun SDK1.3.1.06

WebServers/

AppServers:

• IBM

WebSphere 4.0

FP5

• BEA

WebLogic 6.0

SP2

• Apache Web

Server with

Tomcat plugin

1.3x

Generation of EJB

for Windows2000+SP3

Oracle:

• Oracle 8.1.7

IBM:

• UDB 7.1 or 7.2 SP6

• TCP/IP


JDKs:

• Sun SDK1.3.1.06

• J2EE 1.3

WebServers/

AppServers:

• IBM

WebSphere 4.0

+FP5

• BEA

WebLogic 6.0

+SP2





Generation for Java

HTML Client attached

to Windows

• 2000+SP3

• Windows XP

+ SP1

• IBM UDB 7.1 or 7.2

+FP6

• Oracle 8.1.7

• TCP/IP


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

Personal Repository 2000+SP3 IBM UDB 7.1or 7.2 SP6 Named Pipes

Workgroup

(Freeway) Repository

2000 Server or Advanced

Server +SP3

MS SQL Server

2000+SP3Named Pipes

Prep and Test Server

2000, 2000

Server or

Advanced

Server +SP3


FP6

• MS SQL Server 2000

SP3

• Oracle 8.1.7

• TCP/IP

• Named Pipes

• LU 6.2

0 IBM Comm Server

4.3

1 Microsoft SNA

Server 4.0

C Compilers

• MS Visual

C++ 6.0 + SP5

• 7.0 (in.NET

Studio)

Departmental Server

2000 Server or

Advanced

Server +SP3


FP6

• MS SQL Server 2000

SP3• Oracle 8.1.7

• TCP/IP

• Named Pipes

• LU 6.2

0 IBM Comm Server

4.31 Microsoft SNA

Server 4.0

Client Runtime

• 2000+SP3

• Windows XP

+ SP1

• MS SQL Server SP3


FP6

• Oracle 8.1.7

• 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

Departmental Gateway

Server

2000 Server or

Advanced

Server +SP3

• TCP/IP

• Named Pipes

• LU 6.2

0 IBM Comm Server

4.3

1 Microsoft SNA

Server 4.0


Product

Windows






Java RequirementsIt is necessary to install Java Standard Edition 1.3.1.06 before installing AppBuilder Open GenerationJava products. If you do not have Java installed, you will receive an error message stating that the systemfailed to create a start menu entry.

In addition to the items listed in Table1-4, the fol lowing items are necessary for Java development.

• For invoking or deploying Web Services, if the application server does not supply a SAX-based Javaparser as part of their execution environment, use the Apache XML parser for Java, Xerces version1.4 or higher.

• For the Report Writer, use Java runtime environment Standard Edition 1.3.1.06.

WebSphere Development Requirements

In addition to the items listed in Table1-4, the following items are necessary for Java development forWebSphere application servers.

• For Open generation, HTML and EJB, use BEA WebLogic 6.0 SP 2 or Java Standard Edition 1.3.1.06with J2EE 1.3 Reference Implementation, and any HTML editor, and Internet Explorer 6.0 SP1browser.


Documentation 2000+SP3

Browser:

• IE 6.0 SP1

for Online Help

Acrobat:

• Adobe

Acrobat 4.0 or

higher for

viewing PDFs.

a. Most communications functionality is embedded in the operating system, except for the SNA Server and

Communications Server.


Product

Windows






WebLogic D evelopment Requirements

In addition to the items listed in Table1-4, the following items are necessary for Java development forWebLogic application servers.

• For Open generation, HTML and EJB, use BEA WebLogic 6.0 SP 2 or Java Standard Edition 1.3.1.06with J2EE 1.3 Reference Implementation, and any HTML editor, and Internet Explorer 6.0 SP1

browser.• For EJB, HTML Client, and SOAP Web Services, use BEA WebLogic 6.0 SP 2, Internet Explorer 6.0

SP1.


Apache with Tomcat

In addition to the items listed in Table1-4, the following items are necessary for Java development onWeb servers that support Apache with Tomcat:

• For Open Generation, use Apache 1.3 with Tomcat Release supporting Java Servlet 2.2 or JavaStandard Edition 1.3.1.06 with J2EE Reference Implementation, any HTML editor, and InternetExplorer 6.0 SP1.

• For EJB, HTML Client, and SOAP Web Services, use Apache 1.3 with Tomcat Release supportingJava Servlet 2.2 and Internet Explorer 6.0 SP1.




CHAPTER

2

INSTALLING APPBUILDER 2.1 .0


AppBuilder 2.1.0 installation is supported only on a machine that does not have a previous version ofAppBuilder installed. If necessary, remove any previous versions of AppBuilder before you installAppBuilder 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. Insert the AppBuilder Installation CD-ROM into the CD-ROM drive.

2. Start the AppBuilder installation process by doing one of the following:

• Open an icon view of the CD then double-click theSetup icon.

• From the Windows desktop, select Run > Start menu then type:

<source drive>:\setup

The Welcome dialog is displayed (SeeFigure2-1).



2-2 Installing AppBuilder 2.1.0

Installing from a self-extracting file

Figur e 2 -1 Welco me dial og

Continue with instructions under “Continuing the installation” .

Installing from a self-extracting f ile

1. Double-click on the self-extracting executable. This will unzip the fi le in your temp directory anddisplay an html page with the options to View the Release Notes, View the printable Install Guide

for Windows, or Install the package the pr to begin view an html page which wil l.

2. From this html page, select Install the package to run the setup.exe. The Welcome Screen isdisplayed (see Figure2-1).

Continuing the installation

Regardless of whether you are installing from the CD or from the self-extracting executable file, followthese steps to continue your installation of AppBuilder 2.1.0.

License Agreement

1. From the Welcome Screen (Figure2-1), click Next to display the License Agreement dialog.

2. After reading theLicense and Copyright information dialog, click Yes to accept the licenseagreement. click No if you do not accept the agreement and wish to terminate the install.

Destination Folder





3. If Yes is selected, theChoose Destination Location dialog displays. The default installation path isdisplayed in the Destination Folder area. If you want to change the destination, click Browse,browse to the new location, and click OK.

4. Click Next to accept the installation folder.

5. If you are going to install on the default driveC:\ in a folder that does not already exit, a messagebox appears asking if you want that directory automatically created.

6. Click Yes to continue.

Select Components

7. The installation program displays the Select Components dialog (seeFigure2-2).

Figure 2-2 Selec t componen ts d ialog

8. Click in the check box to select the items you wish to install at this time.

9. The AppBuilder documentation is an installation option. To install the HTML help system forAppBuilder 2.1.0, check the Documentation check box. The PDF files are located on your CD andon the BluePhoenix Solutions Support Web site. The content of the PDF files is the same as thecontent in the online help only the format differs and is a printer-friendly format.

10. The default sett ings include only the Construction Workbench and Documentation. If you want toinstall any other products select the appropriate box.

11. The Construction Workbench must be selected in order to install the TurboCycler DevelopmentKit, the Personal Repository, or MLUI.

12. Preparation and Test Server is a subcomponent of Departmental Server. Install the Preparation andTest Server on machines that act as preparation servers: as machines to which preparation requestsare sent from the Construction Workbench. The Preparation and Test server is also used to test theapplications that are part of remote preparation.





13. At least one component must be selected for the installation to proceed. If nothing is selected, amessage box displays prompting you to choose a component.

Select Program Folder

14. TheSelect Program Folder dialog appears (see Figure2-3).

Figure 2-3 Select Program Folder dialog

15. Accept the default program folder name AppBuilder or specify a different folder name either bytyping 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. TheStart Copying Files dialog appears (Figure2-4).





Figure2-4 Star t Copying Fi les dialog

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 thedisplayed settings and install the selected AppBuilder products, click Next.

18. The installation program displays a series of progress messages during installation. The status isdisplayed, as shown in Figure2-5.





Figure 2-5 Setup s tatus d ialog

Communications Configuration

19. When this part of the installation is complete, several additional configurators may run dependingon what combination of products were selected. For example, another type of wizard screen isdisplayed for the configuration of communications. The sequence is shown in Figure2-6. You canaccept 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 ConfiguringCommunications Guide . With each screen, click OK when done selecting options.





Figure2-6 Communicat ions conf igurat ion screens

Figure2-7 Conf igurat ion screens cont inued

20. There is also a configuration dialog for the Workgroup (Freeway) Repository client that is necessaryfor the Construction Workbench if you are connecting to a workgroup repository. In the screensdisplayed in Figure2-8, enter the name of the workgroup repository or use the buttons to add a new

Used for Global

Eventing and Unix

Repositories Only




Modifying or Uninstalling Product

Freeway and click OK when done. If you are connecting to (using) a local repository only, you canclick Cancel on these screens.

Figure 2-8 Workgroup repository c l ient conf igurat ion

21. For installation of a workgroup (Freeway) server, an additi onal 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 ensurethat the application is ful ly 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, Iwill restart my computer later) then click Finish. The initial installation of the software is notcomplete until the machine is rebooted. You must restart the computer after completing theinstallation 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 totheConfigur ing Communications Guide for more information about modifying the AppBuildercommunications between repositories and servers.


After completing your initial AppBuilder installation, you can modify your installation in several ways.The following information is discussed in this section:

• Adding or Removing Installation Components

• Repairing the Installed Product

• Uninstalling the product

To modify your AppBuilder 2.1.0 installation, you must use the Add/Remove Programs option under theControl Panel to modify your . Do not attempt to modify your installation from setup in the installationdirectory. From the Windows operating system Control Panel, run Add/Remove Programs. The





installation setup dialog is displayed with the options available for modifying the installation. Refer toFigure2-9.

Figure2-9 Instal lat ion setup d ialog

Adding or Removing Installation Components

You can modify your AppBuilder 2.1.0 installation by installing or removing components. Before youadd or remove components, be sure that you stop or close all AppBuilder applications. If you have theAppBuilder communications service running, Stop the AppBuilder System Service and Hide the ServiceControl. For more information on the Service Control please refer to theConfiguring Communi cations

Guide . From the installation setup dialog displayed in Figure2-10, select Add/Remove Component andclick Next.

You are then shown a checklist of products presently installed on your system as shown in Figure2-10.





Figure 2-10 Example Setup Checklist

Deselect any installed components that you want to remove, and check any new components you wantto install. What you have checked on this dialog will be installed on your system. Anything that is notchecked will be removed if necessary. When you add and remove components:

• INI fi le sett ings are preserved, but user comments in the ini fi les are not preserved.

• User-created files are not modi fied.

• Any applied RFX or EFX maintenance is removed.

The value of adding or removing components is that you can customize your installation withcomponents that you need or want. When you are satisfied wi th the components you have selected, clickNext to begin the modifications.

Repairing the Installed Product

If you have modified your AppBuilder 2.1.0 files and want to return to the known configuration, you canrepair the installation. Before repair ing your installation, be sure that all AppBuilder and Windows

programs are stopped, including the AppBuilder communicati ons service and the ManagementConsole.



Viewing Version Information


From the installation setup dialog displayed in Figure2-5, select Repair and click Next. This re-installsand overwrites all the product components that were installed the last time the installation or setup wasrun:

• INI fi le sett ings are preserved, but user comments in the ini fi les are not preserved.

• User created files are not modi fied.

• Any applied RFX or EFX maintenance is removed.

Wait until this installation is complete and the machine has rebooted before you reapply a maintenancepackage, 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.0installation level. I t is a way of resett ing the installation to a known configuration.

Uninstalling the product

You can uninstall the AppBuilder product completely from a machine. Before you uninstall the product,

be sure to close or stop all AppBuilder applications. If you have the AppBuilder communications servicerunning, Stop the AppBuilder System Service and Hide the Service Control. For more information onthe Service Control please refer to the Configuri ng Communications Guide .

Personal repositories should be archived and then removed via the Personal Repository Manager beforeyou uninstall the product; if you do not remove them with the tool prior to uninstall, the Personalrepository databases remain in DB2 and should be removed using a DB2/UDB tool.

From the installation setup dialog displayed in Figure2-9, select Remove and click Next. Before the fi lesare removed a confirmation screen asks if you want to continue with the removal process. This optionremoves all the installed components and all INI files. An additional screen asks if you want to removeuser-created files. Select Remove User-Created Files to ensure that all fi les, directories, and HKLMRegistry entries and environment variables are removed.

The machine must be rebooted in order to complete the uninstall . Failure to restart your machine afteruninstalling may have undesirable consequence.

View ing Version Informat ion

You can view the product information in any of several ways:

• From the Management Console

• From the Command Line• From the Product or Tool

From t he M anagement Console

To find out the versions of the AppBuilder products that are installed on a machine, from the Windowsdesktop, select Start > Programs > AppBuilder > Configuration > Management Console. There is alogin screen. Type your user identification and password for the Windows operating system. From the




Viewing Version Information

Management Console, click on the icon for the computer and right-click, as shown in Figure2-11. Fromthe 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 li st of rollup fixes (RFXs) applied

• Fixpack - Contains a list of fixpacks applied

From the Command Line

You can get the same information from the command line that you can get From the ManagementConsole. From the command line, run abprdinf.exe which wil l l ist the products for the machine you runit on. The concept here is that you do not have to have access to the Management Console or know how



Performing a Silent Installation


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.

From the Product or Tool

You can find the version of the product from the Construction Workbench. Select Help > About

BluePhoenix AppBuilder to display the version dialog as shown in Figure2-12.

Figure2-12 Version d ialog


To install AppBuilder on multiple machines in a pre-configured, hands-free way, you can record aninstallation and then simply repeat it in silent mode without having to interact with the install wizardthereafter. Silent installations run without any further user input.

First, you record an installation and create a response file. Then you run the installation (in silent mode)with the response file to each target machine. To create and use a silent install follow these steps:

1. Open a system command prompt, and change to the directory containing the setup.exe.

2. Type the following command:

setup -r

3. This command runs the AppBuilder setup program and records all your setup choices in theresponse fi le named setup.iss. Setup.iss is located in your system directory (Windows or Winnt).





This file contains the choices you made during installation specifying how you want AppBuilderinstalled.

4. To launch the silent install, copy the setup.iss fi le from the system directory to the directorycontaining 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 containsa report on the silent install including whether the install was successful. You can review the log fileand determine the results of the install.

6. After the silent installation, if you have set the restart option, the computer restarts. After the restart,the configurators run.




CHAPTER

3

SERVERS ON WINDOWS M ACHINES


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

Installing the Preparation and Test Server

With AppBuilder, you can prepare to machines remotely and deploy prepared applications on thosemachines as long as you first install the necessary Preparation and Test Server software. This sectiondescribes how to install the server on Microsoft Windows 2000 platform.

Before deploying the production application, you may deploy the application in a test environment withsome test software provided by AppBuilder that helps in debugging. There are two procedures to fol low.The first is to install the Preparation and Test Server on the development machine. The second, coveredin “Installing the Production Server”, is to set up client and server software. Follow these steps to installthe necessary pieces of software for the Preparation and Test Server on your development workstation.

1. Run the install wizard; advancing through the panels, select the location of the server. Click Next tocontinue.

2. On the Select Components dialog, select Departmental Server and Preparation and Test Server;click Next.

3. Continue through the panels and click Finish when done.

Installing the Production Server

If you are deploying the application in a test environment and have previously installed the Preparationand Test Server, the next step is to setup target clients and servers. If you are in a productionenvironment, you need only setup target clients and servers. For both of these cases, follow thisprocedure to install software for each client and server of the distributed application on each of thetarget machines.

1. On each target machine, run the setup program and step through the install wizard. Choose thelocation folder and advance through the panels.



3-2 Servers on Windows Machines

Installing the Production Server

2. On the Select Components dialog, select the product to install on the production machines. Refer toTable3-1 for a summary of the options.

Figure 3-1 Gateway server implementation examples

Table 3-1 Production product options summary

Option Description of software on the target machine

Client Runtime

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 Departmental Server is the runtime and middleware required to execute

AppBuilder server modules.

Gateway Server

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.

Gateway Server as aprotocol translator

Gateway Server as a

data-dependentrouter




CHAPTER

4

WORKGROUP REPOSITORY

ON WINDOWS M ACHINES


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

M eeting Requirements

Support includes:

• Windows Requirements

• Network Protocols

• Database Management Systems

Windows Requirements

Supported platforms and system requirements are li sted in Table4-1.

Table 4-1 Windows requirements

Hardware Operating System Disk Space Memory

Pentium450MHz minimum Windows 2000 Server SP3

Minimum 100 MB for

Workbench repositoryinstallation (500 MB

recommended for usage)

512 MB



4-2 Workgroup Repository on Windows Machines

Meeting Requirements

Network Protocols

Table4-2 lists the network protocols supported by AppBuilder Workgroup Repository.

Database Management Systems

Table 4-3 li sts the databases supported by the AppBuilder Workgroup Repository. The software listedunder “Required DBMS options” are components of the DBMS that must be installed for theAppBuilder runtime software to function properly.

AppBuilder supports Microsoft's Windows 2000 implementation of Named Pipes. This softwareprovides intermachine communications support. The named pipes can be transported on eitherNetBEUI or TCP/IP (using the TCP/IP NetBIOS Helper Service.)

SQL Server Considerations

The following prerequisites must be met for an installation of SQL Server working with the WorkgroupRepository. SQL Server settingsmust be defined prior to the successful operation of the AppBuilderworkgroup repository.

Character Set

As an Administrator, the codepage can be set to whatever your organization is using. Be careful in settingup the environment, however, as database backups are sensit ive to the character set of the SQL Server onwhich they are restored. For example, a repository database archived from a 437 US character set maynot be restored on an 850 English character set due to character set incompatibilities. In such a case, analternative to the Archive/Restore method should be used to transfer objects.

Sort Order

The only supported sort order is Dictionary order-case insensiti ve .

It is critical to select the correct character set and sort order during the SQL Server install procedure. Ifthe selected character set or sort order needs to be changed, rebuild the databases and reload the data.

MS SQL Server service

Prior to starting the Freeway Manager Service, the MS SQL Server service must be up and running.

Table 4-2 Supported network communication protocols

Protocol Product

Named Pipes Microsoft (bundled with OS)

Table 4-3 Supported databases

DBMS Required DBMS options

SQLserver SQL Server 2000 with SP3



Installing a Workgroup Repository


Installing a Workgroup Repository

Before installing a workgroup repository on a Windows environment, ensure that the system meets therequirements for installing AppBuilder. When those requirements are met, there is litt le fur therpreparation necessary for Windows installation. Refer to Installing AppBuilder 2.1.0 for the initial stepsof the installation procedure.

If you have chosen to install a WorkGroup Repository in Figure2-2, the installation program will runthe Freeway Server Configurator.

Configuring t he Repository

After install ing AppBuilder, you must setup and configure the workgroup repository for thedevelopment environment. Use the Server Configuration Tool to create the Freeway database and set theappropriate server options. Follow this procedure:

1. Define the Freeway Server ID (seeUsing Unique Freeway Server Identifier)2. From the Programs option in the Start Menu, select AppBuilder > Repository > Freeway Server

Configuration tool.

3. In the Freeway Server ID f ield, enter a numeric value between 400 and 1295 for the repository. Thisvaluemust be unique among Freeway repositories. Click Next.

4. Enter the number of available connections that the Freeway Manager should start automatically.This number should be set to 0. Click Next.




Configuring the Repository

Figure 4-1 Freeway Database Setup Window

5. For the Freeway Database Setup, if you choose Custom Setup define the fol lowing fields andcibtubye to Table4-4 for descriptions of each parameter. I f you are choose Typical Setup continue toFigure 4-2.

User name:

Password:

Create Database:

Typical or Custom Setup:

Import repository data:

Data File Location:

Working Directory:

Table 4-4 Database setup window parameters

Parameter Description

User ID

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.

Password

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.

Database Create Options

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.



Configuring the Repository


For example:

User name is <sa >, with anull password.

The default repository is located in:

AppBuilder \ad\dbf\dbbackup\ABREPDEF.exp

6. Click OK. Figure 4-1 shows the Freeway Server Setup window.

7. The following message displays:

Default Freeway Repository was successfully imported. Would you

like to view the log file?

8. Click YES. Freeway Server Configuration is complete.

9. Click OK.

For a typical setup, for most cases, define the database file name and the database size, as shown inFigure 4-2 and summarized in Table4-5. For more options, instead of using the typical setup, use thecustom setup as described in “Creating a Custom Setup” .

Figu re 4-2 Typi cal setup

Import Data File

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.

Working DirectorySpecifies the temp directory to be used during the setup process.

Table 4-4 Database setup window parameters





Creating a Custom Setup

Using Unique Freeway Server Identif ier

It is important to create unique system identifiers for repository objects. Conflicts can arise in object

identifiers when the objects are joined together in the same repository through migration, preventingsuccessful migration. These conflicts can be avoided by defining a Freeway server identifier for eachworkgroup repository.

When an object is created, the identi fier generated for the object is partly based on the Freeway serveridentifier. I f the same identifier is defined to multiple Freeways within the development environment,the potential exists for two different objects to exist with the same system identifier. By defining a uniqueidentifier for each Freeway, each object has a unique identi fier reflecting the object and the Freeway inwhich it was created.

If the development environment also includes the Host repository, there is an equivalent 2 characteridentifier @HPSENV on the Host. IF the Freeway server identifier is resolved to equal the 2 characterstring, the potential for conflict between objects in the Freeway and on the mainframe also exists.


If you would like to create a database for the workgroup repository and specify certain parameters thatare chosen automatically in the typical setup, you use a custom setup.

Table 4-5 Typical workgroup Repository setup


Database Details Settings about the underlying database.

Database Name The name of the database; for viewing only.

Database Server Name The name of the server; for v iewing only.

Database File NameSpecifies the location of the database. The default location within SQL Server is

\MSSQL\DATA, though the Freeway Administrator may redefine this parameter.

Database Size

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.





Figure 4-3 Creat ing custom setup

The settings are summarized in Table 4-6.

Table 4-6 Custom workgroup repository setup


Database Details Settings about the underlying database.

Database Name The name of the database; for viewing only.

Database Server Name The name of the server; for viewing only.

Data Size and Log Size

Each Workgroup repository transaction is recorded in the SQL log file. During

setup, the administrator may define the size of the log file and the size of the

data file within the device to be created. It is important to create a log file large

enough for the development effort.

Device Options

It is possible to increase repository performance substantially by separating the

data file and the log file, and placing each on a separate device. This reduces

disk contention and increases the speed data is written to the disk. For more

information on data devices, refer to Microsoft SQL Server Documentation.

Select one of these choices:

• Data and Log on the same device.

• Data on one device and Log on another.

• Data and Log on multiple devices.

Database Options

During setup, select Truncate Log on Checkpoint. This option specifies that

the transaction log is truncated each time a CHECKPOINT checking process

occurs. By default, the transaction log is compressed to use as little space as

possible on the device.




Creating a Workgroup (Freeway) Database

Figure 4-4 Database device screen

Creating a Workgroup (Freew ay) Database

Install and configure the database prior to developing with an AppBuilder repository. The RepositoryAdministrator sets specifi c workgroup options, creates the database, and imports the default contents ofthe workgroup tables using the Freeway Server Configuration Tool in AppBuilder. Creating the databaseand restoring the contents of the workgroup tables is the starting point for development wi th theAppBuilder product.



Enabling a Group Repository for Rebuild


Figure 4-5 Freeway database setup

Creating a Database

Once the administrator elects to create the database, the installation program uses the followingprocedure to create a workgroup (Freeway) database:

1. Prior to creating the workgroup (Freeway) database, the target SQL Server defined for the FreewayDatabase Setup must be registered wi thin SQL Server and the Microsoft SQL Server Service must beup and running. For more information on registering a server in SQL Server, refer to the Microsoft

SQL Server Onl ine Help.

1. Installs the Freeway Manager service (that manages the workgroup repository).

2. Creates an Open DataBase Connectivity (ODBC) data source.

3. Creates the workgroup (Freeway) database.

4. Creates all the tables used by the workgroup repository.

5. Imports the contents of the data file into the tables in the workgroup (Freeway) database.

Pay careful attention to the sequence of events in case the creation of the database is unsuccessful.

Configuring the Workgroup (Freeway) Database

After creating the workgroup (Freeway) database on the server using the Freeway Database Setup

window, configure the database. The Repository Administrator defines the required fields and selectsCreate for this automated task to begin.

Enabling a Group Repository for Rebuild

Set REBUILD_ENABLED=TRUE in the FREEWAY_SERVER section of the hps.ini file in the appbuilderdirectory. The Freeway Service must be stopped an re-started for this change to take effect.




Autostarting the Freeway Service

Aut ostart ing the Freew ay Service

In some situations it may be useful to start the Freeway service automatically when booting up themachine. For example, if users boot up the Freeway machine and login without administrator privileges,because they are not members of the administrator group, they do not have permission to start theMicrosoft SQLServer and Freeway Services Manager services. If the machine needs to be rebooted, an

administrator must be present to start the Freeway service again.Another scenario occurs if the Freeway is located in a remote location and a Remote Control applicationis used to reboot the machine. A remote reboot allows the machine to start but the user cannot login,therefore, a batch file placed in the startup folder to start the Freeway will not work.

Figure 4-6 shows the Freeway Services Manager in Microsoft Windows 2000.

Setting the Freeway Services Manager to Automatic start results in a failure because the MicrosoftSQLServer service needs to start first. From the Control Panel, select Administrative Tools > Services.





Figure 4-6 Freeway Services Manager window (Windows 2000)





Sett ing the Freeway Service to Start Aut omat ically

To setup the service to start automatically, edit the services through Control Panel and the registry. Sincethe Freeway Services Manager and Microsoft SQLServer services can only be started by an administrator,first open the Services dialog through Control Panel, and edit the startup properties for the FreewayServices Manager and M icrosoft SQLServer services.

Set the following properties for both services:

• Startup Type: Automatic

• Login As: This Account: <MACHINE_NAME >\<administrator >

• Password: <administrator’s password >

where <MACHINE_NAME > is the host name of the machine and <administrator > is someone withinthe administrator’s group.

The services start in alphabetical order based on how they are listed in the registry under\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.

A value can be added to a specific service key to wait for another service to start. To start the Freewayservice after the Microsoft SQLServer service, add the following two values in the Freeway key using theREGEDT32 registry editor (not REGEDIT):

• DependOnGroup: REG_MULTI_SZ:

• DependOnService: REG_MULTI_SZ: MSSQLServer

Using these modifications, the Freeway Services Manager service will start regardless of who boots upthe machine.











AppBuilder 2.1.0 Installation Guide for Windows i

Index

INDEX


CClient Runtime 3-2codepage

administrator sett ings4-2communication protocols 4-2creating a Freeway database 4-9custom database setup 4-6

Ddata size 4-7database

minimum size4-6database create options settings4-4database file name field 4-6database management 4-2database options field 4-7database owner 4-4database setup

custom 4-6typical 4-5

database size field 4-6default repository 4-5default table owner 4-4defining a Freeway Server ID 4-6Departmental Server 3-2device options field 4-7

FFreeway database

data size 4-7database options4-7device options4-7password 4-4setup 4-4, 4-9user ID 4-4

Freeway Manager 4-3, 4-9Freeway Server Configuration 4-3, 4-5Freeway Server system ID 4-6

Freeway Service Managerautomatic start 4-10setup 4-12startup properties 4-12

G

Gateway Server 3-2

Hhardware requirements1-1help

product information 2-11

Iimport data fi le sett ings4-5Installing the AppBuilder Software 2-1

Llog size field 4-7

Mmachine

target 3-1minimum hardware 1-1MSSQLServer

startup properties 4-12

Nnamed pipes4-2NetBEUI 4-2network protocols4-2

Ppassword

for Freeway database 4-4PC requirements 4-1Preparation & Test Server 3-1



Preparation and Test Server 3-1prerequisites

SQL server 4-2product information 2-11

Rrequirements

hardware 1-1PC 4-1

SSelect components dialog 2-3Select Program Folder dialog 2-4server

Departmental 3-2Gateway3-2preparing and testing 3-1

Server Configuration Toolsetting up a Freeway repository 4-3

setting the Freeway service to start automatically 4-12Setting up Target Clients and Servers 3-1SQL

character set 4-2character sets and backups 4-2configuration options 4-3server settings4-2sort order 4-2

SQL Server Administrator user ID 4-4SQLServer version 4-2Start Copying Files dialog 2-5

system requirements 1-3

Ttarget machines 3-1TCP/IP 4-2temporary directory 4-5typical database setup 4-5

Uuser identifier

for Freeway database 4-4

WWelcome dialog 2-2Windows 2000 named pipes

support 4-2working directory sett ings4-5

Date post:	04-Jun-2018
Category:	Documents
Upload:	sadot-enrique-castillo-galan
View:	230 times
Download:	0 times

App Builder Installation Win

Documents