Title: Welcome to the QAD MidWest Users Group
1Welcome to the QAD MidWest Users Group
MFG/PRO Version 8.5F to eB Conversion
Steven Amalfitano
sra_at_qad.com
856 840 2688
2Why Upgrade to eB ?
Additional Product Functionality Diverse
Interface Options Enhanced Database
Configurability
3Additional Product Functionality
Global Shipping Global Tax
Management Product Change Control
Euro Data Corporate Commodity
Codes
4Diverse Interface Options
Character Interface
Gui Interface Full or Embedded
Web Browser Interface Extended User
Maintenance (XUI) eB
Desktop
5Full User Interface Display
6HTML Links to Embedded UI
7Embedded UI Display
8Full User Interface Display (XUI Maintenance
Screen)
9 eB Desktop
10Enhanced Database Configurability
Redesigned Database Architecture
WebSpeed Brokers/Agents Application
Servers/Agents
11PROGRESS Redesigned Database Architecture
- As of Progress Version 9 all databases are
multi-volume in structure - Database logical files are created within
specific Data Storage Areas during the database
build - Data Storage Areas are comprised of one or more
physical files known as database extents - Database extents are created in specified
locations, and therefore can be directed to
specific I/O channels.
12PROGRESS Redesigned Database Architecture
Progress V9 Database Layout - Area Architecture
Table E
Index E
Index C-1
Index A-1
Index B-1
Index D-1
Index E-1
Table A
Table B
Table C
Table D
Area 6
Area 7
Area 8
Area 51
Extent
Extent
Extent
Extent
Extent
Extent
Extent
Extent
Extent
Extent
Disk Storage - Files or Raw Slices
13WebSpeed Brokers/Agents
- WebSpeed is Progress Product for Application
Development and Deployment across intranets,
extranets, and the internet. - Allows Application Access via a Web Browser
- A WebSpeed Broker is started to Initiate and
Maintain a Pool of Agents that handle Database
Requests - An Agent is similar to a Headless Client
14WebSpeed Brokers/Agents
15Application Servers/Agents
- The Progress Application Server Spawns and
Manages Agents on the Database Server - These Agents can Execute Application Logic
Initiated by a Remote Client Session - The Agents are Similar to Headless Client
Sessions
16Application Servers/Agents
Clients
AdminServer
AppServer
ApplicationServers
Name Server
Application Broker
Business Logic
17Preliminary Steps
Progress Mfg/Pro Installation
Preparing Source Version Data Preparing
Reports for Data Verification Create the
Target Version Database
18Progress Mfg/Pro Installation
- Progress Enterprise DB and a 4GL Product are
installed on the Database Server - The entire compliment of Mfg/Pro database build
files and executable code is installed utilizing
several individual component CDs - Most Database Server files are on the Database
Server CD - Language specific files are on the Language CD
- Character executable code is on the Character
Client CD - Mfg/Util is initiated to build the databases and
configure system utilities after extraction
19Preparing Source Version Data
- Post and Close all possible Financial
Transactions - Delete and Archive any outdated data
- Backup the Production Database
- Certain Modules require specific procedure
- Corporate Commodity Codes (Pre 8.5) Global
Shipping (Pre 8.6) - Product Change Control (Pre 8.6) Euro Data (Pre
8.6E) - Supplier Performance (ProPlus) SSM (Pre 8.5)
20 Preparing Reports for Data Verification
- Generate Reports via a Production Client Session
for Post Conversion Data Verification - Site Report Item Planning Item-Site Planning
- Stock Status Inventory Valuation ECN Status
Inquiry - Price List Customer Master Bank Address
- Supplier Master Customer Ship-to Address Employee
Master - US Sales Tax Salesperson Commission VAT/GST
Reports - Sales Quotes Blanket Orders Sales Orders
- Distribution Order Req. Ship Schedule Orders in
Transit
21Create the Target Version Database
- Database Size and Layout Considerations
- Overall Database Size (Allow for growth)
- Individual DSA Data
- Analyze specific files assigned to DSA in
Appendix - Analyze application usage for expected use of
files - Create DSA Extents to Maximize I/O Efficiency
- Create a Structure File and use Prostrct Create
- Procopy MfgEmpty onto Void Database
22Actual Conversion Milestones
- Progress Database Version Conversion
- Dumping Production Data
- Preserving Custom Data
- Loading Production Data
- Preparing Target Version Data
- Performing Target Version Conversions
- Running Post Conversion Utilities
- Restoring Custom Default Data
23Progress Database Version Conversion
Specific Procedure is Dependant on Source
Database Version For Progress 8 to 9
Conversion - Use Source Version Prostrct
Convert - Converts Single Volume to Multi
Volume Structure - Must be run against existing
Multi Volume Structures - Use Source Version
Proutil Truncate Bi - Use Target Version
Proutil Conv89 - Actually changes the Database
Header - Creates the Required DSAs
24Dumping Production Data
- Use Mfg/Conv
- -Initially prompts for environment questions
- -Reprompts for Source Version Specific Feature
Data - Generate Lost Data Reports
- Custom Menus - Custom Messages
- Language Details - Language Master
- Dump Production Database
- Requires a dump directory with 75 Database Space
- Some Data Manipulation occurs during Dump
- Dump Could be Performed in Background
- Requires File Assignment to Specific Dump Queue
25MFG/CONV
26Preserving Custom Data
Use Mfg/Util to dump applicable side database data
- Dump Custom GUI Data
- Entire Database Content
- Dump Custom CFG Data
- Entire Database Content
- Dump General Ledger Report Writer Data
- Specific Tables Only
- Dump Intrastat Data
- Specific Tables Only
27MFG/UTIL
28Loading Production Data
- Load Production Data
- Load ECommerce Data
- Load Language Independent Admin Data
- 4) Load Default Menu and Message Data
- 5) Load Language Dependant Admin Data
29Loading Production Data (Cont)
- Load Production Data
- Use Mfg/Util to Bulkload
- Use Mfg/Util to Idxbuild
- If Sort Files exceed 2GB, use a Multi Volume Sort
File - Create a .SRT file and specify the t in Mfg/Conv
- Load ECommerce Data
- If Source Version implemented EDI
- Use a Command Line Program String to Start
- Load Language Independent Admin Data
- Loads Default Data
- Use a Command Line Program String to Start
Other Command Line Programs will load Custom Gui
or Cfg Data - Duplicate Record Errors May Be
Acceptable
30Loading Production Data (Cont)
4) Load Default Menu and Message Data - Use
Mfg/Util - Load is a two step operation -
Language Independent Files (MFG Directory) -
Language Dependant Files (LANGDIR/MFG
Directory) 5) Load Language Dependant Admin
Data - Use Mfg/Util - Load all data from the
LANGDIR/ADMIN Directory
31Preparing Target Version Data
Specific Required Application procedures must
be run from within a client session
Procedures exist for Specific Functionality -
Co-Products / By-Products - Service/Support
Management (SSM) - Currency Conversion - Global
Shipping
32Performing Target Version Conversions
After Data is Prepared, Specific Conversions
will Alter or Manipulate the Remaining Data -
Use Mfg/Conv - System Determines Possible
Conversions - Based on added features since
source version Perform Globalization conversion
at a minimum - Initiates Several Required
Conversion Routines
33Running Post Conversion Utilities
Run the Utilities from within a Client
Session - Sequence Update - Synchronize
GL Report Writer - MRP to Repetitive
Approval - ISO8601 Utilities - Global
Shipping - Service/Support Management -
Sales Order Pricing - Product Change
Control - Euro Data - Corporate Commodity
Codes - Operations Planning - Supplier
Performance
34Restoring Custom Default Data
- Reenter Reported Expected Data Loss
- Use the Mfg/Conv generated reports
- Menu Data
- Message Data
- Language Details
- Language Master Data
- Reenter Windows Data Modifications
- - Standard Browse, Drill Down, Menu
Substitutions Records which were manually altered
will need to be reedited - Load the Custom Help Data
- - For New Help Databases load standard help
35Final Considerations
Certain Functionality requires Individual
Conversion Process - Global Tax
Management - Fixed Assets