App Builder Personal Repository
-
Upload
sadot-enrique-castillo-galan -
Category
Documents
-
view
237 -
download
0
Transcript of App Builder Personal Repository
-
8/14/2019 App Builder Personal Repository
1/60
BluePhoenix AppBuilder 2.1 .0.
Personal Repository AdministrationGuide
http://www.bluephoenixsolutions.com/ -
8/14/2019 App Builder Personal Repository
2/60
BluePhoenix AppBuilder 2.1.0.Personal Repository Administration GuideApril, 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/ -
8/14/2019 App Builder Personal Repository
3/60
AppBuilder 2.1.0 Personal Repository Administration Guide iii
TABLE OF
CONTENTS
AppBuilder 2.1.0 Personal Repository Administration Guide
1 Personal Repository Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
AppBuilder Repository Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1AppBuilder Repository Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Personal Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Development Security Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Repository Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Personal Repository Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Using the Freeway Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Using the Freeway Explorer Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Using the Freeway Client Configuration Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
2 Personal Repository Adm inistrat ion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Setting Up Your Personal Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Using Personal Repository Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Personal Repository Manager Menu Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Creating a Personal Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Setting Personal Repository Securi ty Propert ies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Configuring the Codepage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Archiving the Personal Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Deleting a Personal Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Restoring a Personal Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Copying a Personal Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Configuring Host Repository Propert ies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Setting Up FTP Directories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Reviewing the Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Performing Unit of Work (UOW) Migrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Standard Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Automated Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Table of Contents
-
8/14/2019 App Builder Personal Repository
4/60
Table of Contents iv
3 Migration Server Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Migration Server Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1How Migrations Work. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Managing the Migration Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Method Handler Functionali ty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
TCP/IP Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Upload and Download Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Connecting to a Personal Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Using the Upload and Download Menu Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5Using the Upload Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Using the Download Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Using the Status Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Download and Upload Between Repositories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Selecting Scope. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Estimating Download Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16Uploading Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Performing UOW Migrations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18Starting and Stopping the Migration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18Cleaning Up the UOW Migration Enti ty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Setting Server Security Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18FTP Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19Repository Authorization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Understanding Performance Implications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Checking Regression. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Handling Results of Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Controlling Concurrency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Debugging a Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Tracing Operations During Upload and Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21LRE_FTP.trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21LRE_SOCKET.trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Understanding Migration Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
4 Perform ance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Understanding Repository Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Tuning for Optimal Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Evaluating Disk Util ization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Configuring a UDB Database for Memory Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Configuring the Host Query Interval for Downloads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Changing the Interval Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Configuring UDB on Specifi c Platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Configuring Windows NT Pagefile Size. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Configuring Download Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i
-
8/14/2019 App Builder Personal Repository
5/60
1-1
CHAPTER
1
PERSONAL REPOSITORY OVERVIEW
AppBuilder 2.1.0 Personal Repository Adm inistration Guide
This guide describes the use and administration of a local repository containing objects for thedevelopment of applications using AppBuilder. It includes information on how to create and manageaccess to the repository and migration between repositories, including:
AppBuilder Repository Family
Development Security Model
Repository Administration
Personal Repository Functionality
AppBuilder Repository Family
The AppBuilder family of repositor ies provides a tool to administer and manage a software developmentenvironment from a centrally-located database residing on a server or workstation. AppBuilder provides
repository technology that supports: Flexible, scalable architecture
An object-oriented information model
Data migration between repositories
Conference-based notification
Windows NT/2000 and AIX platform support
Platform-, protocol-, and database-independent configurations of Workgroup installations
Industry-standard APIs
International language support National Language Support (NLS) and Double-Byte Character
Support (DBCS)
Sophisticated locking mechanisms that ensure only one developer modifies an object at any time.
Using repository technology, client/server and cooperative processing applications can be developed in acontrolled and efficient workspace. The repository contains software application objects, methods, andfacilities used to access the objects. These methods and facilities are accessed using AppBuilder tools thatreside on a client machine, as shown in Figure 1-1.
Note For more information on repository technology and the benefits and features of object-based repositories,refer to the Product Concepts Guide andWorkgroup Repository Administration Guide.
-
8/14/2019 App Builder Personal Repository
6/60
1-2 Personal Repository Overview
Personal Repository
Figure 1-1 AppBuilder Repository Environment
AppBuilder Repository Types
A repository is a relational database containing all the application components, objects, and businesslogic, including configuration settings, relationships, and metadata used within a developmentenvironment.
There are three types of repositories available in AppBuilder:
Personal Repository
A Personal Repository is a database repository where the client, server, and database all reside on thesame local machine. The AppBuilder personal repository is also referred to as a local repository or LRE.The filename extension .lre i s used to identify a personal repository fi le.
Table 1-1 AppBuilder Repository Types
Workgroup Repository A controlled, secure development environment for client/serverenvironments with the repository accessible on a network server from remoteworkstations.
Personal Repository Repository functionality on a local client workstation that is configured to beeasily uploaded and merged wi th a larger development effort.
Enterpr ise Repository A mainframe repository for enterprise application development teams. Themainframe is designated as the central archive and site for the team toconduct application development.
-
8/14/2019 App Builder Personal Repository
7/60
Development Security Model
AppBuilder 2.1.0 Personal Repository Administration Guide 1-3
Figure 1-2 Personal Repository Network Diagram
A personal repository supports only one user at a time on a local machine. Other repositor y servers,such as Workgroup and enterprise repositories, support multiple users simultaneously. Multiplepersonal repositories can be created on a single machine, each one defined to allow the same or differentusers access to the repository.
The objective of the personal repository is to establish a repository locally where you can workindependently, without a continuous network connection to a remote server. Only during an upload,download, or query of remote objects is a connection required to the remote server. For detailedinstructions for uploading and downloading objects, see Download and Upload Between Repositories
on page3-14.
Development Security M odel
The repository software enables a system administrator to implement security restrictions that controlaccess to objects in the repository. Security is implemented using the Workgroup securi ty model storedwithin the repository. The model consists of users, user groups, projects, and the permissions and scopeofobjects available to user groups, as shown in Figure 1-3.
Figure 1-3 Workgroup Securi ty Model
Warning Do not install a Workgroup and personal repository on the same machine. If personal repositories areinstalled and then a Workgroup is installed, all personal repository files in the directory are written
over by the Workgroup repository files.
-
8/14/2019 App Builder Personal Repository
8/60
1-4 Personal Repository Overview
Repository Administration
Security M odel Definitions
A Projectcontains repository objects that have been created under the project name. For example, in anaccounting application, a project called ACCOUNTING could be defined. An ACCOUNT object, aRECEIVABLE object, or any other object needed for the application can be created, modified, and storedwithin the ACCOUNTING project.
A Groupcontains users with access to the objects in a project. When a group is created and associateswith a project, the type of access group members have to the objects in the project is defined for thegroup. Multiple groups of users can be associated with a project. For example, one user group might beassigned relate access to the objects in a project, while another group has create, relate, update,anddeleteaccess.Figure 1-4illustrates the relationship between projects and groups.
Figure 1-4 Pro ject and Group Hierarchy
A Useris a Workgroup repository user who is defined to native security. Typically, a group is defined andcreated, then users are added to the group. Added users then have access to the objects in the projectassociated with that group.
To create a Workgroup repository, see the procedure outlined in Creating a Personal Repository onpage2-3.
For detailed instructions on setting the security properties for projects and groups, see Sett ing PersonalRepository Securi ty Properties on page2-5.
TheWorkgroup Repository Admi nistrat ion Guidealso contains a detailed explanation of FreewayExplorer and repository management and securi ty.
Repository Administration
The AppBuilder administrator assigns userIDs and passwords with specific permissions assigned to a
client using the repository. The user is then associated with at least one user group. The group isassociated with one or more projects, and so on. The scalability and flexibility of the repository allow alarge or expanding number of users to have limited or full access to groups and projects, read-onlyaccess, the ability to create, relate to, update, or deleteobjects, or a combination of all these and othersecurity parameters.
Using AppBuilder, the repository administrator can keep tight control on software versions,modifications, releases, databases, and libraries. Objects can be shared among the group members, but
Project
Group
-
8/14/2019 App Builder Personal Repository
9/60
Personal Repository Functionality
AppBuilder 2.1.0 Personal Repository Administration Guide 1-5
the source object is only modifiable by the assigned owner, unless and until that security option ischanged by an administrator.
The Workgroup administrator accesses and manages the Workgroup network using the FreewayManager interface. Freeway Manager is not included in the Personal Repository. Access FreewayManager by selecting Start > Programs > AppBuilder > Freeway > Freeway Manager.
For more information about Freeway Manager and Freeway Explorer, see the Workgroup RepositoryAdmini strat ion Guide.
Personal Repository Funct ionality
An AppBuilder personal repository offers you all the functionali ty of a Workgroup repository in a localrepository. The local repository can prepare applications, query for objects stored locally or on the hostrepository, commit and rollback operations, and migrate objects to and from a Workgroup or hostserver. You use the Freeway Explorer interface to set up and manage the Personal Repository.
The sections that follow describe the procedures you need to get started.
Using the Freeway Explorer
Using the Freeway Explorer Menus
Using the Freeway Client Configuration Opt ion
Using the Freeway Explorer
To open the Freeway Explorer application:
1. Select Start > Programs > AppBuilder > Repository > Freeway Explorer. Use Freeway Explorer toperform any of the actions listed in Table1-2.
Table 1-2 Reposi tory Actions
Acti ons Desc ript ion Parameter s Required
New Creates a new association to a repository Connection alias- the name assigned by the
developer to differentiate between different
repositories. This is typically the Server name.
Connect via- the protocol used during
development to access the repository from
the client.
Server name- the network name of the server
on which the repository resides. This must be
consistent with the communications protocol.
Service name- the name of the service
request used to connect to the repository
using NetEssential. If not using NetEssential,
the field presents a list of available services,
such as SQL, DB2, or Oracle.
Connect Logs in to a repository after a connection
alias is created
-
8/14/2019 App Builder Personal Repository
10/60
1-6 Personal Repository Overview
Personal Repository Functionality
Creating a Connection Alias
1. To create a connection alias, select Session > Newfrom the Freeway Explorer main window (Figure1-6).
Figure 1-5 Freeway Explorer Main Window
2. In the New Freeway Group Server Connection Alias window (Figure 1-6), type in the configurationsettings for the repository you are connecting to. SeeTable 1-2for an explanation of the settings.
Figure 1-6 New Freeway Group Server Connection Alias Window
3. Name the new local repository and click Create.
Disconnect Closes a connection to the Workgroup server
Commit session Saves all changes to the repository
Rollback session Changes reverse the unit of work to its state
prior to the last commit
Delete Removes the connection alias
Table 1-2 Repository (Continued) Actions
Actions Descript ion Parameter s Required
-
8/14/2019 App Builder Personal Repository
11/60
Personal Repository Functionality
AppBuilder 2.1.0 Personal Repository Administration Guide 1-7
4. An Action Successfuldialog displays (Figure 1-7).
Figure 1-7 Action Successfu l Dialog
Using the Freeway Explorer Menus
The menus and actions available in Freeway Explorer are described in Table1-3.
Using the Freew ay Client Configuration Option
Using Freeway Client Configuration, you can choose either theNewor Deleteaction to create or delete aconnection alias. This procedure permits you to create a connection alias to Workgroup repositoriesonly. To create a connection alias to a Personal Repository, you must use Personal Repository Manager.
Table 1-3 Explorer Menu Items
Menu Name Description Menus
Session
Connect or disconnect to a repository
See the properties of that session
Commit or rollback changes to the repository
Create a new connection
Delete an existing connection
Exit the Explorer
Tools
Use the tools to migrate from one repository to another
Export or import data
Migrate using Application Folder settings
Upload and Download objects Check security settings
Select add-ins for migration
Selected
(with objects selected)
Open the hierarchy browser for an object
View the properties of an object
Remove the object from the repository
Purge the object from the repository
Clear the browser
Print the hierarchy browser
-
8/14/2019 App Builder Personal Repository
12/60
1-8 Personal Repository Overview
Personal Repository Functionality
To use Freeway Client Configuration:
1. SelectStart > Programs > AppBuilder > Repository > Freeway Client Configuration. The windowopens (Figure 1-8).
Figure 1-8 Freeway Client Configuration Window
2. Select an existing alias from the list and click Deleteto delete the connection alias.
3. Click Newto create a new connection alias, the New Freeway Alias dialog opens ( Figure 1-9).
Figure 1-9 Freeway Al ias Dialog
4. Select the Workgroup server options that match your configuration.
5. Name the new connection alias and click OK(Figure 1-10).
Figure 1-10 Freeway Alias Window
-
8/14/2019 App Builder Personal Repository
13/60
AppBuilder 2.1.0 Personal Repository Administration Guide 2-1
CHAPTER
2
PERSONAL REPOSITORY
ADMINISTRATION
AppBuilder 2.1.0 Personal Repository Adm inistration Guide
AppBuilder uses the Personal Repository Manager interface to manage a personal repository. Repositorymanagement tasks are equivalent to the administration tasks required by a Workgroup or mainframerepository, including:
Setting Up Your Personal Repository
Using Personal Repository Manager
Creating a Personal Repository
Setting Personal Repository Security Properties
Configuring the Codepage
Archiving the Personal Repository
Deleting a Personal Repository
Restoring a Personal Repository
Copying a Personal Repository
Configuring Host Repository Propert ies
Setting Up FTP Directories
Reviewing the Log File
Performing Unit of Work (UOW) Migrations
Setting Up Your Personal Repository
Using AppBuilder, you can create a single repository or multiple repositories on a local personalcomputer. Each personal repository creates an .INI file using the name assigned to the personalrepository. For example, creating a new personal repository named NEWLRE generates a fi le namedNEWLRE.INI.
Each personal repository is independent of another personal repositorys codepages, host settings, andjob status. Multiple repositories make it possible to have one personal repository querying objects while
Note Refer to the installation instructions for your AppBuilder software for current installation systemrequirements.
-
8/14/2019 App Builder Personal Repository
14/60
2-2 Personal Repository Administration
Using Personal Repository Manager
a second processes a download job at the same time on the same machine. There are many possibleconfigurations for setting up personal repositories.
The number of personal repositories that can be defined is limited by three factors:
the number permitted by the database manager
the number of databases DB2/UDB can handle at one time
the amount of space on your system
The restr ictions defined by your repository administrator for your particular environment and the sizeof your local disk space are variables that can be controlled locally. You can increase the number of DB2/UDB databases available for personal repositor ies using the following procedure:
Procedure - Increasing Available D atabases
To increase the number of databases DB2/UDB can manage:
1. Open the DB2 Control Center.
2. Right-click onDB2 Instance under the Instances icon.
3. Select theConfigureoption.
4. Select theEnvironmenttab.
5. Select the maximum number of concurrently active databases.
6. Change this value and click OK. When DB2 restarts, the value increases.
Using Personal Repository ManagerUse the Personal Repository Manager to create and configure a personal repository using the followingprocedure.
Procedure - Creating a Personal Repository
1. Select Start >Programs> AppBuilder >Repository >Personal RepositoryManager
The Personal Repository Manager window (Figure2-1) opens displaying the main window with thepersonal repository listed, in this example it is named NEWLRE.
Figure 2-1 Personal Repository Manager Window
Note Because only one session of the Workgroup browser can connect to a repository at a time, to connect tothe same or a different repository for a second session, you must establish two completely different
sessions of the Workgroup browser.
-
8/14/2019 App Builder Personal Repository
15/60
Creating a Personal Repository
AppBuilder 2.1.0 Personal Repository Administration Guide 2-3
Personal Repository M anager M enu Item s
The menus available in the Personal Repository Manager are described in Table2-1.
Creat ing a Personal Repository
Use the Create Personal Repository window to define a new personal repository or to restore an existingpersonal repository. If a new or revised personal repository is given an existing personal repositoryfilename, a message displays stating that the personal repository already exists. The existing repositorymust be deleted before restoring or creating a personal repository using the same name.
1. From the Personal Repository Manager window, select Repository > Create or click on the Createtoolbar button. The Create Personal Repository dialog is displayed (Figure2-2).
Figure 2-2 Create Personal Repository Dialog
Table 2-1 Personal Repository Manager Menu Description
Menu Names Descriptions Menus
Repository Create a new personal repository on your local machine.
Set up the FTP directories for uploading and downloading
migrations to and from a mainframe or host repository.
Exit the manager
View Show or hide the toolbar and the status bar
Display the log file of activity.
Selected Archive a personal repository.
Pack and Reindex
Delete a personal repository.
Viewing the host properties
-
8/14/2019 App Builder Personal Repository
16/60
2-4 Personal Repository Administration
Creating a Personal Repository
2. Enter data in the Create Personal Repository dialog fields from Table2-2to configure the personalrepository..
3. Select Createto create the personal repository.
Table 2-2 Personal Repository Data
userID and Passwo rd Fields
userID
User ID of a current
Windows NT or
Windows 2000
Administrator using
8 or fewer characters
The user ID supplied is used to create a database in DB2/UDB, so the
user ID must have administrative authority or be a part of a group with
administrative authority in DB2/UDB. Any Windows NT/ 2000 user ID that
is part of the administrators group has sufficient privileges to create a
personal repository. The user ID supplied in this field is the only repository
user for this personal repository. The user ID is added to the AppBuilder
security model.a
a. DB2/UDB 7.1 and later allow you to create a user ID with more than 8 characters.
PasswordPassword for the
userID
Use the same password the user ID logs into Windows with. This
password is verified by the Windows system and is used when connecting
to the personal repository. The password iscase sensitive.
Create Repository Section
New Name
Name of the personal
repository to be
created
This name must contain eight (8) characters or less. Some names are
restricted from use because they are reserved names.
Database
created on
Directory where the
database files will be
created
This is only for the DB2/UDB files pertaining to the database. This is not
the AppBuilder home or personal repository supporting files directory.Ensure the drive is a local hard drive. If the drive selected does not
already have a DB2/UDB database created on it, the directory DB2 will be
created in the root partition and the DB2/UDB files for the personal
repository will be placed under that directory.
Create Using Sectio n
Personal
Repository
File
Name of a personal
repository to base this
personal repository
on
The default repositories contain the internal objects that a personal
repository needs to perform correctly.
Default repositories are provided for two reasons:
to hold the default objects that are needed to create a personal
repository
to provide a preconfigured area for created objects to be placed in after
the repository is defined and objects are added to it.
Two default repositories are shipped with the personal repository
installation:
DEFAULT.LRE
EMPTY.LRE.
The DEFAULT.LRE repository contains the default AppBuilder repository
objects. The EMPTY.LRE repository contains only the internal objects
needed for personal repository functionality. No default objects are
included.
The two default personal repository files are located in:
\AD\DBF\DBBACKUP
A previously-archived personal repository may be used to create a new
personal repository. If the personal repository is created from a previousarchive, then all of the objects in the previous repository archive are
available to the new repository.
Working
Directory
Directory that Create
uses to store
temporary files
The log file is also created here.
-
8/14/2019 App Builder Personal Repository
17/60
Setting Personal Repository Security Properties
AppBuilder 2.1.0 Personal Repository Administration Guide 2-5
While the Personal Repository Manager generates the personal repository, a status bar on thebottom of the window indicates its progress.
A log file is automatically displayed to indicate an ( E) error, (W) warnings, and (I) information. Ifan error is encountered and the personal repository fails to be created, the error message indicatesthe problem encountered. You can use this information to correct the error and recreate thepersonal repository.
Sett ing Personal Repository Security Propert ies
Use Freeway Explorer to define the security properties of the personal repositor y - user, group, andproject permissions and scope. The Workgroup Repository Administration Guideprovides a detailedexplanation of repository security properties. The procedures outlined here describe how to access thedialogs in Freeway Explorer that define the security of the personal repository.
Procedure - Accessing the security properties of a project
1. Open Freeway Explorer by selecting:
Start > Programs > AppBuilder > Repository > Freeway Explorer
2. Select Session > Connect to connect to a repository.
3. Select the repository and enter user IDand password.
Figure 2-3 Freeway Explorer Connect Dialog
4. Select Tools > Security. The Securi ty-User Group Maintenance window opens (Figure 2-4).
Note Personal repositories have an eight (8) character limitation for userIDs. However, DB2/UDB 7.1 and laterallow you to create a userID with more than eight characters.
-
8/14/2019 App Builder Personal Repository
18/60
-
8/14/2019 App Builder Personal Repository
19/60
Configuring the Codepage
AppBuilder 2.1.0 Personal Repository Administration Guide 2-7
Figure 2-6 Viewing Group Security Settings
4. Drag-down theScopemenu to select a setting. (SeeSelecting Scope on page3-15for scope settingdefinitions.)
5. Click on the box or boxes to set permissions.
6. Click OK.
Configuring the Codepage
The Windows NT/2000 personal repository no longer uses the iconv style codepage conversion files, andthe \NT\codepages directory has been omitted from the product in AppBuilder2.0.3.1.
The International Components for Unicode (ICU version 2.0) is now delivered with AppBuilder andused for the personal repository's Codepage information.
For more information, visit: http://oss.software.ibm.com/icu.
Codepage conversion takes place while messaging using a Winsock connection between the personalrepository and the host migration server. For the codepage information to be transmitted during FTPsessions, a manual entry in the [PERSONAL_REPOSITORY] section of the HPS.INI fi le must beapplied. The setting reads as follows:
[PERSONAL_REPOSITORY]
SEND_SBDATACONN_VALUE=TRUE
Setting the SEND_SBDATACONN_VALUE to TRUEpresets your FTP session with the host to yourspecific codepage settings and ignores what the host default is. It sends the codepage value to the FTPserver for each FTP session, asking the server to "NOT" act upon a static setting, but rather use the valuesupplied with SBDATACONN.
Procedure - Codepage Settings for SBADATACONN
1. Set theSEND_SBDATACONN_VALUEto TRUE(or YES).
Tells the personal repository to send the FTP quote site command to the host migration serverduring an FTP session. This allows the client personal repository to dictate codepage conversions forthe host migration server. If this is not set, the default setting is used.
Note For clients using the same codepages on host and client machines, it is not necessary to use theSBADATACONN setting, because the host and client are always set to the appropriate codepage.
http://oss.software.ibm.com/icu/http://oss.software.ibm.com/icu/ -
8/14/2019 App Builder Personal Repository
20/60
2-8 Personal Repository Administration
Archiving the Personal Repository
2. Set theUSER_REMOVEABLE_UOWto TRUE.
The [PERSONAL_REPOSITORY] section of the HPS.INI fi le enables the menu item to removeselected item(s) in the Upload window. If this setting has been added previously, remove it from theHPS.INI (or set i t to FALSE) and the Selected > Removemenu item is removed.
3. Set theLVLEXP_AS_HIERARCHYto FALSE.
This sett ing, located in the [FREEWAY] section of the HPS.INI fi le, is used to define the LEVELMIGRATION EXPORT functionality of the Windows-based personal repository and Workgrouprepository. It dictates how a LEVEL MIGRATION EXPORT from the personal or WorkgroupRepository acts on import.
If set to FALSE, the objects are exported independently (Enti ty Only) and merged on import intoa target repository, therefore, no deletes can occur.
If set to TRUE, the objects are exported as a hierarchy, therefore, implied deletes can occur. Thismimics the behavior of a Full Hierarchy Migration Export in a Workgroup repository migration.Refer to theWorkgroup Repository Admi nistration Guidefor more information about migrationexport.
Archiving the Personal Repository
Archiving the personal repository creates a backup of the personal repository. Archiving takes the entirerepository and compresses it into a single file with a personal repository extension (for example,DEFAULT.LRE). An archived personal repository file can be moved from one machine to another, whennecessary. The archived file cannot be renamed once it is archived. I f the archived personal repository fileis renamed, you cannot create or restore the repository from the archive file, it must be renamed to itsoriginal archived personal repository fi lename before you can recreate or restore the personal repository.Before archiving a personal repository, you are prompted to close any open repository sessions that exist.
Procedure - Archiving a Personal Repository1. From the Personal Repository Manager, highlight the personal repository to be archived.
2. ChooseSelected > Archive. The Archive Personal Repository dialog opens (Figure2-7).
-
8/14/2019 App Builder Personal Repository
21/60
Archiving the Personal Repository
AppBuilder 2.1.0 Personal Repository Administration Guide 2-9
Figure2-7 Archive Personal Reposi tory Dialog
3. Fil l in the Archive Personal Repository dialog with your specif ic data.Table2-3describes each of thefields in this window.
Table 2-3 Archive Data Descriptions
User Section
userID
UserID of a current Windows NT or
2000 Administrator (limit of eight (8) or
fewer charactersa)
The userID supplied is used to log into a database in
DB2/UDB, therefore the user ID must have
administrative authority or be a part of a group with
administrative authority in DB2/UDB.
Any Windows NT/2000 user ID that is part of the
Administrators group has sufficient privileges to
create a personal repository. The user ID supplied inthis field is the only repository user authorized for this
personal repository and is added to the AppBuilder
security model.
Password Password for the userID
Use the userIDs Windows password. The Windows
system verifies this password and uses it to connect
to the personal repository.
The password iscase sensitive.
Drive Paths Section
Working DirectoryDirectory that the archive uses to store
temporary filesThe log file is also created in this directory.
Store Archive inDirectory where the archived personal
repository file is placed
The name of the personal repository archive is the
name of the personal repository with an .LRE
extension. For example, if the personal repository
named PANEL1 was archived, the resulting archive
would be named PANEL1.LRE.
This archive can be moved anywhere, and created or
restored from any system containing a personal
repository. However, the file cannot be renamed. It
can be used to create a new personal repository or
replace an existing PANEL1 personal repository.
-
8/14/2019 App Builder Personal Repository
22/60
2-10 Personal Repository Administration
Deleting a Personal Repository
4. Click OK to archive the personal repository.
As the Personal Repository Manager is working to archive the personal repository, a status bar will beshown at the bottom of the window. Upon success or failure, the log file will automatically be displayed.In the log file an (E) indicates an error, (W) are warnings, and (I) is for information. If an error isencountered and the personal repository archive fails to be created, the error message will indicate theproblem. Correct the problem and repeat the archive procedure. See Reviewing the Log File fordetailed information about the Log File.
Deleting a Personal Repository
Deleting the personal repository removes it from the local machine. All files related to the repository andthe DB2/UDB database will be removed. The personal repository name will also be removed from thePersonal Repository Managers list of .LRE files.
Procedure - Deleting a Personal Repository
1. From the Personal Repository Manager, highlight the name of the personal repository to be deleted.
2. ChooseSelected > Deletefrom the drop-down menu.
The pop-up window now lists the personal repository selected for deletion.
3. Click Remove.
The log file is automatically displayed when the delete succeeds or fails. In the log file, an (E)indicates an error, (W) are warnings, and (I) is for information. If an error is encountered and thepersonal repositor y is not deleted, the error message indicates the problem. Correct the problemand delete the personal repository. SeeReviewing the Log File for more information about the logfile.
Restoring a Personal Repository
Use theRepository > Createfunction to restore a personal repository. Assign the personal repository thesame name as the original repository archive file. If the repository already exists, you must remove itbefore being able to restore.
Copying a Personal Repository
To copy a personal repository to another drive, use the following command, where is theletter designation of the actual drive being copied from, and is the drive beingcopied to.
Copy :\store\panel1.lre :\store2
a. if you are using DB2 7.1 or later, it no longer restricts the userID to eight characters.
Note The Createcommand will be unable to locate the appropriate files to unzip if you change the personalrepository filename. If the name of the archive file has been changed, change it back to the original name
before creating or restoring it.
-
8/14/2019 App Builder Personal Repository
23/60
-
8/14/2019 App Builder Personal Repository
24/60
2-12 Personal Repository Administration
Setting Up FTP Directories
4. Click OK. The system stores the values in the file: \.INI.
Sett ing Up FTP Directories
All personal repositories use the same File Transfer Protocol (FTP) directories. These directories are usedby the personal repository to store files associated with uploading and downloading objects from thehost repository. They are called FTP directories because FTP is used to upload and download the files
between the personal repository and the host. The following procedure describes the steps to customizethese directories.
Procedure - Configuring FTP directories
1. From the Personal Repository Manager window, select Repository > FTP Directories. The Upload/Download Directories dialog is displayed (Figure2-9).
The check box for restricting connections allows you to choose whether or not the local repository'sclient tools ignore Upload and Download functionality.
2. To restr ict connections, select the check box:
Restrict local repository connections during upload/download
operations
Although the tool allows simultaneous updates, i t is safer to not allow mult iple jobs to update thePersonal Repository at the same time. By selecting the check box for "Restrict local repositoryconnections.." you can prevent access to the Construction Workbench, thus avoiding possiblecorruption of the Personal Repository. Although the tool allows simultaneous updates, it isrecommended that you restrict multiple jobs from updating the Personal Repository at the sametime.
Table 2-4 Host Repository Settings
Host TCP/IP Parameters Section
Host NameName of the mainframe host machine where the consolidation repository
resides
Port Number Number of the port that the server daemon is listening onCodepage Codepage used on the host system
Timeout
Number of seconds that the personal repository attempts to connect to the host
mainframe. If the personal repository does not have a response from the host
within the amount of time specified in the timeout, it generates a timeout error
and quits attempting to connect.
Codepages SectionHow the personal repository determines which codepage conversions need to
be done
Codepage Host: Host code page is the codepage that the host is running
Codepage PC:PC Codepage is the codepage on the local machine where the personal
repository is located
Host Repository Parameters Section
Repository Name Name of the repository on the host machine
Version Version of the repository setup on the host machine
Project Project space that personal repository will be using
-
8/14/2019 App Builder Personal Repository
25/60
Reviewing the Log File
AppBuilder 2.1.0 Personal Repository Administration Guide 2-13
Figure 2-9 Upload/Download Directories Dialog
3. Fil l in the data in the Upload/Download Directories dialog, using Table2-5as a guideline.
4. Once these directories are set, click OKto save them.
Reviewing the Log File
A log fi le keeps track of all of the events that occur during procedures, such as, create, restore, archiveordelete. It contains helpful information about what occurred during the action and explains errors, if any.Review the contents of the log fi le by selecting Migration Export > Actions > View logfileto seesummarized information about objects and actions taken in the personal repository. Figure2-10showsa sample log fi le.
Table 2-5 Upload/Download Directories Data
Directory Function Description
Upload DirectoryThe directory where files associated with
the upload to the host will be kept.
A temporary directory; information stored in this
directory is deleted often. Select this field by
querying in the directory using the Querybutton.
Download
Directory
The directory where files associated with
the download from the host will be kept.
A temporary directory; information stored in this
directory is deleted often. Select this field by
querying in the directory using the Querybutton.
Caution Select your FTP directory carefully. Periodically, the entire contents of these directories will bedeleted. We recommend using the default directories. You can change these directories if you
require additional space.
Browse for
directories
Leave unchecked to have client tools ignore upload/download
-
8/14/2019 App Builder Personal Repository
26/60
2-14 Personal Repository Administration
Performing Unit of Work (UOW) Migrations
Figure 2-10 Sample Log File
Performing Unit of Work (UOW) M igrat ions
Unit Of Work (UOW) migrations are migrations of objects that export onlythose objects that have been
modified. This process keeps exported objects that are unchanged from being compared to objects in thetarget repository, resulting in faster migration imports. The personal repository uses the UOWmigration process to automate migrations to a host server using FTP.
Standard Migration
Standard migrations add objects to a repositorys UOW, if an active UOW is available, during import.Downloads to the personal repository from the host migration server use the same process, however, i t isan automated process conducted during the migration from a host migration server, with nointervention possible by the user.
The personal repository UOW is created automatically during repository creation and cannot beremoved. Only one active UOW per repository is available during a personal repository session. Thefilename PERSONALidentifies the UOW. The personal repositorys UOW is associated with therepository group PUBLIC. Changes submitted to the repository from any member of this group areadded to the PERSONALUOW.
-
8/14/2019 App Builder Personal Repository
27/60
Performing Unit of Work (UOW) Migrations
AppBuilder 2.1.0 Personal Repository Administration Guide 2-15
Automated Migration
A downloadis the automated migration from the host repository to the local repository. An uploadis theautomated migration in the opposite direction, from the local repository to the host repository.
Freeway Explorer provides a user interface to manage the Upload and Download functions toAppBuilder repositories. For detailed instructions on Upload and Download procedures, see Uploadand Download Operations on page3-4.
-
8/14/2019 App Builder Personal Repository
28/60
2-16 Personal Repository Administration
Performing Unit of Work (UOW) Migrations
-
8/14/2019 App Builder Personal Repository
29/60
AppBuilder 2.1.0 Personal Repository Administration Guide 3-1
CHAPTER
3
M IGRATION SERVER M AN AGEM ENT
AppBuilder 2.1.0 Personal Repository Adm inistration Guide
This section covers the following migrati on topics:
Migration Server Overview
Managing the Migration Server
Upload and Download Operations
Download and Upload Between Repositor ies
Performing UOW Migrations
Setting Server Security Requirements
Understanding Performance Implications
Checking Regression
Handling Results of Migration
Controlling Concurrency
Debugging a Migration
Understanding Migration Restrictions
M igration Server Overview
The Migration Server automates the movement of data between a Windows NT/2000 personalrepository and the enterprise repository over TCP/IP. Use the migration tools of each platform to movethe data manually between a personal repository and a host repository.
Typically, the migration process is a manual process managed by an administrator who collects andmoves the data to the target repository. The purpose of the Migration Server is to automate themigration process from a single user personal repository to the host repository, eliminating the need foran administrator to manually move the data.
-
8/14/2019 App Builder Personal Repository
30/60
3-2 Migration Server Management
Migration Server Overview
How M igrations Work
Automation of the migration process requires use of a TCP/IP communication protocol. The migrationfi les are automatically uploaded and the Analyze and Import functions are executed. Results of theimport are then automatically transferred to the workstation for review.
Downloads are initiated with a Query to the target host repositories. Using the Query, the objects andscopes are selected for download. Upon completion, the download process is initiated. The hostrepository exports the data and makes the files available for the client to download. The Windows NT/2000 personal repository then downloads the migration files, executes an import, and displays theresults to the user. The Windows NT/2000 personal repository downloads the migration files into a localdownload directory using FTP.
Figure 3-1 Automation of a Uni t o f Work Migrat ion
The Migration Server services Windows NT or Windows 2000 personal repository migration requests.The server initiates the request to start an Analyze and Import, start an Export, or Query a repository forcertain types of objects based on the long name of the object.
The Migration Server listens on a specific pre-configured port for the personal repository servicerequests. The request may contain the length of data, the actual service request and any neededparameters that the service request needs for fulfillment.
Figure 3-2 Migration Server Overview
To fully utilize the OS/390 capabilities and make use of existing repository services, most of thecommunications between the client and server spawn batch jobs for processing. This allows themainframe to control the resource load.
-
8/14/2019 App Builder Personal Repository
31/60
Managing the Migration Server
AppBuilder 2.1.0 Personal Repository Administration Guide 3-3
M anaging the M igrat ion Server
The Analyze/Import service (upload) spawns a batch method handling job. The purpose of this jobstream is to tailor the migration request based on the target repository. A single method handling jobstream needs to exist for each repository that can be connected to the TCP/IP server. This job stream ismade available to the server by the CRSRVJCL method.
The create server JCL (CRSRVJCL) is an administration method run under the ADM model on theenterprise repository. CRSRVJCL creates the method handling job stream based on the INI settings for agiven repository. Without this, the server must dynamically tailor the job streams each time a syncrepository service request is made. The CRSRVJCL method manages this tailoring and supplies theserver with a ready-made method handler. CRSRVJCL should only be executed one time per repository,unless INI or data set changes create the need for another execution.
M ethod Handler Functionality
The Method Handler is responsible for tailoring the migration jobs. It allocates the sett ings to call the
necessary executable and INI files used to tailor the migration job. Each repository has its own INIsettings that specify the handling of migration settings, what DB2 plans to execute with, and otherprocess commands. The Method Handler uses the proper settings for each repository to ensure properexecution. When Method Handler submits the migration Analyze/Import or Export job into the internalreader, the standard migration process executes. Figure3-3illustrates the Method Handler flow.
Figure3-3 Method Handler Batch Job Process
-
8/14/2019 App Builder Personal Repository
32/60
3-4 Migration Server Management
Upload and Download Operations
TCP/IP Services
The TCP/IP server provides the following services:
Upload and Dow nload OperationsUse the Freeway Explorer interface to connect to and manage the personal repository. The followingsection describes the windows and tools available to operate the upload and download functions. Thefi rst time you enter an upload or download window, you wil l be prompted for a user identification andpassword.
Table 3-1 TCP/IP Services
Service Description
Analyze/Import (Upload)
1. The first step of the Analyze/Import process is an Export process on the Windows
NT or Windows 2000 Personal Repository. Once completed, the migration files are
transferred to the host via FTP.
2. The system then performs an Analyze followed by an Import. The results are
written to the log file.
3. The client workstation retrieves the log files from a predefined location and
displays the status of the process back to the user for review.
4. Upload consists of a series of migration files, followed by a request to import those
objects into the target repository. This service triggers the submission of a batch
analyze and import job.
Export (Download)
The Export process requires a migration object and settings in order to perform the
request.
1. Specify a series of objects on the workstation to download by querying and
selecting objects and scopes.
2. The workstation runs a daemon to check on the status of the Export process.
Once a complete status is determined by the workstation, the workstation initiates anFTP of the migration files and begins an import into the Windows NT/2000 personal
repository.
3. The Export service creates a migration object with settings as specified by the
Windows NT/2000 personal repository requests. Once the server creates the objects
on the host repository, the Export process is initiated.
4. The Export writes out the migration files to complete the download.
Query Repository
The Query Repository function allows you to query the desired repository by long
name.
1. Specify a starting long name value and type (for example, Rule).
2. The long name values are passed back to the requesting client forty rows at a time
until complete.
3. The repository query facility uses the DB2 CAF to make all database requests.
4. The DBRM for the repository query function must be bound into the repositories
DB2 plan via the CRSRVJCL method.
Status Query
The Status Query service is a dedicated service for reporting the status of any given
Analyze/Import or Export process. This service reports the current status of any
given task.
Shutdown
The Shutdown service is used to bring down the TCP/IP migration server in an
orderly manner, closing the socket, DB2 connection, etc. This service is only
accessed by the mainframe TCP/IP Client.
FTP Address
This service returns the FTP address location the migration files are to be transferred
to This location is also used to access the result files generated by the migration
process.
-
8/14/2019 App Builder Personal Repository
33/60
Upload and Download Operations
AppBuilder 2.1.0 Personal Repository Administration Guide 3-5
Procedures include:
Connecting to a Personal Repository
Using the Upload Window
Using the Download Window
Using the Query Dialog Box
Using the Status Dialog Box
Connecting t o a Personal Repository
Use the following procedure to establish a connection to a personal repository.
Procedure - Connecting t o a Personal Repository
1. Open Freeway Explorer and select Connect.
2. Choose thepersonal repository.
3. Enter the and for that personal repository.
4. Click Connect.
Using the Upload and Dow nload M enu Item s
The Personal Repository dialog allows you to select Tools > Upload to open the Upload dialog as shownin Figure3-4.Table3-4describes these menu options.
Figure3-4 Upload Window Tools Menu
Note The personal repository only has one Unit of Work (UOW). It must be PERSONAL.
-
8/14/2019 App Builder Personal Repository
34/60
3-6 Migration Server Management
Upload and Download Operations
The message box shown in Figure3-5displays if the Upload window is opened while the personalrepository has an active download job in progress.
Figure 3-5 Download Processing Dialog
Using the Upload Window
The Upload window is always initialized with a list of objects currently in the users UOW. The UOWthat personal repository uses is always named Personal. If an upload job is in progress, the status dialogis invoked. Figure3-6shows the toolbar icons in the Upload Unit of Work window.
Table 3-2 Upload and Download Menu Items
Menu item Selection Action Description and Settings
Tools > UploadOpens the
upload window.
During the upload window initialization, the personal repository's INI
file (\) is read for the host properties and
current job status. If the current job status is inactive, the window
opens and displays the UOW (Figure 3-16).
If a previous upload job is in progress, the status dialog is opened to
monitor the host's progress. If a previous download job is in
progress, the user is prompted with a message to either close the
window and automatically open the download window with the
status dialog present.
Tools > Dow nloadOpens the
download window.
During the download window initialization, the personal repository's
INI file (\) is read for the host properties
and current job status. If the current job status ( Figure 3-16)is
inactive, the window opens and d isplays the unit-of-work.
If a previous download job is in progress, the status dialog is
opened to monitor the host's status on operation. If a previous
upload job is in progress, the user is prompted with a message to
either close the window or close the window and automatically openthe upload window with the status dialog present.
Note These menu items are disabled if a download or upload window is already open or if you are connected toa Freeway session.
Note An opened Upload or Download window appears, by name, at the bottom of the Freeway Explorer's toolsmenu and can be activated from that point.
-
8/14/2019 App Builder Personal Repository
35/60
Upload and Download Operations
AppBuilder 2.1.0 Personal Repository Administration Guide 3-7
Figure 3-6 Up load UOW Window
Figure 3-7 Up load UOW Toolbar
Menus
Toolbar
UOW List Entry
Status
Freeway Explorer
Migrate Out
Upload
View Log Files
Selected Properties
View Host Properties
Refresh
Rebuild
-
8/14/2019 App Builder Personal Repository
36/60
3-8 Migration Server Management
Upload and Download Operations
Table3-3lists the menu item tools and selections available to configure the upload.
Table 3-3 Upload Menu Items
Menu Item Selection Name Description
File Upload Initiates an upload.
When this option is invoked, a series of events take place:
A migration of all the object(s) listed in the upload window is performed and
the output files are placed in the upload directory administered by thePersonal Repository Manager's FTP Directorymenu option.
The personal repository sends an upload request to the host.
The migration files are sent(FTP) to the host migration server.
The host migration server submits the job. Once the batch job is submitted,
the migration server can accept other client requests.
The status dialog is displayed showing the status of the job until complete.
Closure of the status dialog does not effect the progress of the job once it is
submitted, the host is simply not queried for a status until the status dialog is
opened again.
While the status dialog is open, the host is queried for job status every
seconds (specified in the status dialog). Once complete, the migration log
files are got(FTP) from the host migration server.
The personal repository parses the detail file from the host migration to
determine which objects need to be removed (successfully updated on the
host) from the UOW. The object change number is updated.
Migrate Migrates out the UOW objects. This is not an upload and will not contact the
host or clear the UOW. This process creates a set of migration files that can be
imported into other repositories. If you want to clear the objects after doing a
migration, use the "remove" option.
Explorer (F2) Makes Freeway Explorer the active window.
Rebuild Analyzes Unit Of Work to create a Rebuild WorkList.
Print Prints the data in the browser window.
Exit Closes the upload window. Closing the download or upload window doesnt
affect the status of any submitted download or upload jobs.
View Host Properties Displays (read only) the host properties, codepages, and TCP/IP information
of the personal repository that the user is logged into. (Administered by the
Personal Repository Manager.)
Migration Export Opens migration window for setting export configuration options.
Repository
Security
Allows the user to change the userID and/or the password used for the upload
session. Invokes the same dialog that is presented to the user when opening
an upload or download window for the first time.
Refresh Refreshes the UOW list. Re-queries the object in the repository's UOW,
picking up updated objects (if any) since the last Commit.
Log fi les Displays the current host log fi les that exist in the upload directory on the
workstation.
Selected Properties Displays the properties dialog for the selected object . If mult iple objects are
selected, the properties for the first selected item are displayed and the menu
items are disabled.
Remove Removes selected i tems from the personal repository 's UOW. This command
removes them from the window, a Commitmust be performed from Freeway
Explorer for this action to be permanent.
-
8/14/2019 App Builder Personal Repository
37/60
-
8/14/2019 App Builder Personal Repository
38/60
3-10 Migration Server Management
Upload and Download Operations
Table3-4outlines the menu i tems and tools available to manage the download.
Table 3-4 Download Menu Items
Menu Items Selection Names Descriptions and Settings
File Download Initiates a download.
Invoking this option causes a several events to take place:
The personal repository sends a download request to the host
migration server with the object names, object types, and export types(i.e. Full Hierarchy, Entity Only, etc.).
The host migration server submits a migration batch job with the
download list of objects to seed the host migration export. Once the
batch job is submitted, the migration server can accept other requests.
The status dialog is displayed showing the status of the job until it is
complete. Closure of the status dialog box does not affect the progress
of the job once it is submitted, the host is simply not queried for a
status until the status dialog box is opened again.
While the status dialog box is open, the host is queried for job status
every seconds as specified in the entry field of the status dialog
box.
Once complete, the host migration files and log files are retrieved from
the host migration server to the download directory. This option is
administered in the Personal Repository Manager using the FTP
Directories menu option. The objects are then migrated into the Personal Repository with the
UOW disabled. Imported objects are compared against objects that
reside in the UOW. Matching objects are removed (refreshed) from the
UOW.
Load Detail Opens or loads a host migration *.DETAIL file as a reference to
automatically query and load entities into the download window. A host
migration DETAIL file is a member of the log files retrieved from the host
after upload/download operations. It can be found in the temporary FTP
directories used for these operations.
Explorer (F2) Makes Freeway Explorer the active window.
Exit Closes the download window. Closing the download or upload window
does notaffect the status of any submitted download or upload jobs.
View Host Properties Displays the host properties, codepages, and TCP/IP information of the
Personal Repository that the user is logged into in read-only format.
(Administered by the Personal Repository Manager.)
Repository Security Changes the userID and/or the password for the download session.
Invokes the same dialog box that is presented when opening an upload
or download window for the first time.
Log files Displays the current host log files that exist in the download directory on
the workstation.
Selected Remove Items Removes the selected objects in the personal repository download list.
Change Scope Changes the scope of the selected object in the download l ist. Al l queried
objects, when loaded into the download window, have a default scope
type of Full Hierarchy. This option allows the scope to be changed on the
selected object. It can be used on multiple objects as well.
Query Query host... Opens the Query dialog box. The Query dialog box is used to loadobjects into the download window.
The download window does notmaintain a list of these objects after it is
closed.
-
8/14/2019 App Builder Personal Repository
39/60
Upload and Download Operations
AppBuilder 2.1.0 Personal Repository Administration Guide 3-11
Using the Load Detail M enu Option
The Load Detail menu option allows you to read from the mainframe's migration DETAIL log fi leslocated in the upload/download ftp directories. The result ing list contains the entities in a *.DETAIL fi le
retrieved from the mainframe after a successful download/upload operation.
To query the entities li sted in a *.DETAIL file:
1. Select theFile > Load Detailoption of the Download window (Figure3-10).
Figure 3-10 The Load Detail Menu Option
2. Select one of the DETAIL fi les from the list that displays (Figure3-11).
Options All or Nothing Informs the Personal Repository to abort the process if any failures
happen during the migration import. Prohibits import of any objects if a
failure occurs.
As Many as Possible Informs the Personal Repository to import as many objects into the
repository as possible and ignore errors on independent objects.Successfully imports are committed.
Replace on Import Always- the migration import of a download always replaces objects.
Never- the migration import always merges without replacing objects.
Prompt- prompts user to select the desired operation after thedownload and just prior to the migration import.
Refresh Unit(s) Always- the UOW always refreshes after the migration import of adownload.
Never- bypasses the refresh of the UOW after the migration import.
Prompt- prompts user to choose the desired operation after the
download and just prior to the migration import.
Refresh Directory Refreshes contents of repository session with updates.
Clear Job Status Sets the PC (\) job status to inactive. Thepersonal repository status of the submitted job is reset. No status checks
are invoked until another upload or download is submitted and the status
dialog is reopened for the new job.
Import Source Allows you to do downloads of hierarchies with no source (rule source,
text, keyword) updates. Refreshes a hierarchy (entities and relationships)
without overwriting any source files that you are currently working on.
Table 3-4 Download Menu Items (Continued)
Menu Items Select ion Names Descriptions and Sett ings
-
8/14/2019 App Builder Personal Repository
40/60
-
8/14/2019 App Builder Personal Repository
41/60
Upload and Download Operations
AppBuilder 2.1.0 Personal Repository Administration Guide 3-13
operation therefore the host connection remains established until the query is complete. A maximum offorty (40) objects is returned per host query. If the desired object is notin the returned list, the user mustfur ther quali fy the name of the object. TheMorebutton queries and displays the next forty objects.Figure3-13shows the Remote Query dialog.
Figure 3-13 Remote Query Dialog
Procedure - Populating the Dow nload window
To move desired objects to the Download window:
1. Select one or more entries in the Object instances.
2. Click Load. This populates the Download window with the selected items.
Each time the Query dialog is opened, the object type will be set to the last queried type.
Using the Status Dialog Box
The Status dialog indicates the progress of an upload or a download. When the dialogs progress bar isfull, a request is generated by the personal repository to the host migration server for the status of thesubmitted job. The time interval between status checks is controlled by a numeric entry (in seconds)below the progress bar. Each time the status indicator is open, the time interval is set to the last settingentered.
The same dialog is used for querying a job status (Figure3-16), regardless of whether the submittedoperation is an upload or a download.
Tip Multiple objects can be selected by holding the CTRL key while clicking on objects in the list.
-
8/14/2019 App Builder Personal Repository
42/60
3-14 Migration Server Management
Download and Upload Between Repositories
Dow nload and Upload Betw een Repositories
The following procedures describe how to download and upload objects between repositor ies.
Procedure - Downloading Objects
Selecting Scope
Estimating Download Time
Uploading Objects
Procedure - D ow nloading Objects
Download objects using the following procedure:
1. Open the Download window (Figure3-14).
A prompt for a "Remote Repositor y Security" userID and password is displayed. This userID andpassword are used for authentication on the host.
Figure 3-14 Download Window with Entity Scope Dialog
2. Enter the userID and password. Click Ok.
3. Select View > Host Properties.
Veri fy that the host-connection parameters are correct. If any are incorrect, use the PersonalRepository Manager to change them.
4. Select Query > Queryhostto open the Remote Query dialog.
Fill in the object type and query value (optional) in the Remote Query dialog.
5. Click theQuerybutton to query the host repository.
6. Select the desired objects from the Object Instanceslist box and click Load.
7. Remove objects from the download list by selecting them in the download window and choosingthe Selected > Remove itemsmenu item.
-
8/14/2019 App Builder Personal Repository
43/60
Download and Upload Between Repositories
AppBuilder 2.1.0 Personal Repository Administration Guide 3-15
8. Set the download scope for each object in the migration import into the local repository in the samemanner:
Select Options > All or Nothingto specify that all objects must be imported successfully and failureaborts the import.
Select Options > As Many As Possibleto require that the personal repository attempt to import allobjects and failures do notabort the import .
Select Options > Import Sourceto do downloads of hierarchies with no source (rule source, text,keyword) updates and refresh the hierarchy (entities and relationships) without overwriting anysource files.
For an explanation of these options, see Controlling Concurrency on page3-20.
9. Once the download scope and download mode are specified for all enti ties, select File > Downloadto initiate the download. After a short pause, the Job Status dialog, (Figure3-16), appears.
10. Change the time interval used to query the host server for the status of your job or cli ck Cancelandclose the Download window.
The Download window (Figure3-14), displays the objects selected in the Query dialog box. You can
perform several actions after the objects are loaded: Remove objects from the download list
Select the download scope for each object
Select the download mode
Perform additional queries
Selecting Scope
Scope defines the set of objects developers have access to in the repository. To configure the download
scope, select an object and choose Selected> Change Scope. Figure3-15shows the dialog that containsthe options used to define the scope.
Figure 3-15 Download Entity Scope Types Dialog
-
8/14/2019 App Builder Personal Repository
44/60
3-16 Migration Server Management
Download and Upload Between Repositories
Table3-5summarizes the scope selection choices.
For more information on object scopes, see theWorkgroup Repositor y Reference Guide.
Estim ating Dow nload Time
The amount of time a download takes is affected by many factors, such as:
The current workload of the mainframe migration server
The size of the hierarchy requested. For example, Enti ty only downloads are much faster than Entirehierarchy downloads.
The type of media the host repository data is stored on; disk or tape
Table 3-5 Definit ion of Scope Types
Scope Options Description
Entity onlyExports the root migration object only. Useful for moving an object when the
scope of the changes are self-contained.
Full hierarchy Exports the root migration object and all its child hierarchies in the migration.Useful for moving a new branch of an application.
Prepare entity
Exports the root object (limited to preparable objects) and all of the objects in
the hierarchy required to successfully prepare the root objects. The scope of the
hierarchy differs from each preparable object. Useful for moving fixes to an
application. The move is limited to the objects that were fixed.
One level
Exports the root object and any objects one level down the hierarchy. Useful for
attaching new branches of an application to an existing application without
moving the entire application. Use in conjunction with the other scopes.
Drawing
Exports the root object (limited to drawing objects) and all of the objects
contained in the drawing. Useful for exporting user selected portions of an
application. Create a drawing that contains the desired objects in an application.
Use as a means of selective migration.
-
8/14/2019 App Builder Personal Repository
45/60
Download and Upload Between Repositories
AppBuilder 2.1.0 Personal Repository Administration Guide 3-17
Figure 3-16 The Job Status Dialog
Uploading Objects
Use the following procedure to upload objects from the Personal Repository:
Procedure - Uploading Objects
1. Open the Upload Window. A prompt for a host userID and password is displayed. This userID and
password are used for authentication on the host.
2. Enter the host userID and password. Click Ok.
3. Select View > Host Properties
Veri fy that the host-connection parameters are correct. I f any are not correct, use the PersonalRepository Manager to change them.
4. The Upload window opens and displays all the changed objects.
5. To refresh the object list, select View > Refresh from the menu.
6. To view or modify the propert ies of an object in the window, highlight the object and select theSelected > Properties, or double-click on the object.
7. Select an upload mode prior to starting the upload. The upload mode specifies the cri teria for themigration import into the host repository.
Select oneof the following:
Options > All or Nothing to request that all objects be imported successfully and a failure abortsthe import.
Options > As Many As Possible to specify that the host repository attempt to import all objectsand failures do not abort the import.
Note To cancel the download job, select Options > Clear job status. This clears the job on the local machine.When the download is completed, the host Log files are displayed. View these logs by selecting
View > Log f i les.
-
8/14/2019 App Builder Personal Repository
46/60
3-18 Migration Server Management
Performing UOW Migrations
8. To init iate the upload, selectFile > Uploador click on the Uparrow icon. After a short pause, theJob Status dialog box appears. See Figure3-16 on page3-17for an example of the Job Status dialogbox.
9. Change the time interval used to query the host server for the status of your job, or simply cancelout of the dialog box and close the Download window.
Performing UOW Migrations
To perform Unit of Work (UOW) migrations, you typically perform these procedures:
Starting and Stopping the Migration Server
Cleaning Up the UOW Migration Entity
The Windows NT or 2000 personal repository only sends Unit of Work (UOW) migrations, also knownas Delta migrations, to the TCP/IP migration server.
The host repository only supports UOW migrations during import. For UOW information specificallyrelated to personal repositories, see Performing Unit of Work (UOW) Migrations.
Start ing and Stopping the M igration Server
TheCRSRVJCLadministrator method, discussed in Managing the Migration Server on page3-3,creates a startup JCL for the server on the host repository. This startup JCL can be submitted manuallyfrom TSO to start the migration server, or it can be submitted using any automated mechanism. Theuser ID starting the server job should have surrogate authority.
To stop the migration server, use the skeleton JCL provided with the installation document. By
submitt ing the JCL, the system wil l start a TCP/IP client. The client initiates aSHUTDOWNmethod onthe server. TheSHUTDOWNmethod stops the server in an orderly manner by releasing all the socket andDB2 connections.
Cleaning Up the UOW M igration Entity
The upload/download batch jobs create many intermediate fi les on the host. They also create rows in themigration server DB2 tables. To avoid populating DB2 tables and flooding files, a migrationadministrator method (MIGCLUP)is provided. Invoke the method MIGCLUPfrom administratormanagement services. This method deletes all the intermediate and result files. It also deletesunnecessary files in the migration server DB2 tables.
Sett ing Server Security Requirements
Mainframe server security is based on the address space executing the TCP/IP server. The job must besetup to execute under an administrator ID. The Method Handling job is spawned with the sameadministration ID as the migration server. To set the securi ty requirements, set theses permissions:
-
8/14/2019 App Builder Personal Repository
47/60
Understanding Performance Implications
AppBuilder 2.1.0 Personal Repository Administration Guide 3-19
FTP Authorization
Repository Authorization
Surrogate Authority
DB2 Authorization
FTP Authorization
FTP security must be setup in RACF for each user with access to the TCP/IP server because FTP is usedto send all migration f iles. All users of the TCP/IP migration server must have access to FTP.
To check security validation on the client, fi rst ensure that the user can connect to the intended server viaFTP. If this access check fails, all services are denied, including services that do notuse migration files.
Repository Authorization
For access to a repository, permissions must be set to at least one project within the version of therepository being accessed. If the user does not have permissions set in advance, all service requests aredenied.
Security is checked upon each service request. This is necessary because you can change the targetrepository with each call. The security check is based on two criteria, the repository and the command.
Surrogate Authority
Surrogate Authori tyis granted to a user who starts a migration job and wants to submit other migrationjobs using a different userID. The system administrator grants the user surrogate permissions. The
authority can later be disabled by using an INI variable [USEPASS] in the @server INI . If the USEPASS isset to n, the password can be viewed in the log file.
DB2 Authorization
The query facilities DBRM are bound with the plan for each repository activated for the TCP/IPmigration server.
Understanding Performance Implications
Performance for the upload (Analyze/Import) and download (Export) functions is based on the loadand the priority of the jobs spawned by the server.
TCP/IP configuration and tuning have a substantial effect in maximizing the processing environment.Please refer to the following manual for TCP/IP tuning guidance:
Warning Surrogate authority in RACF must be setup so that the administrator ID can submit jobs on behalf ofthe userID and password sent by the Windows NT or Windows 2000 client machine.
-
8/14/2019 App Builder Personal Repository
48/60
3-20 Migration Server Management
Checking Regression
IBM TCP/IP: Performance Tuning GuideDocument Number: SC31-7188-01
Or find it at the IBM web site at http://www.s390.ibm.com.
Checking Regression
Regression checking is performed by evaluating the change number of a given object in the repositorycompared to the change number present in the migration files. If a repository objects change number isequal to or greater than an updated object in a migration file, it indicates that the object has beenupdated since download.
Handling Results of M igration
The Analyze/Import and Export services both spawn jobs to the internal reader to handle the migrationrequests. The server generates a unique identifier upon submission of the migration job. This identifierallows the client to query the status of a given migration.
Controlling Concurrency
It is advantageous in most development environments to have the capability to perform concurrentimports and exports by different users in a repository. Setting the UOW to the parametersAll or nothingor As