//
you're reading...
QAD Ent Application

Upgrading the QAD .NET UI in Enterprise Edition

Beginning with the QAD 2009.1 Enterprise Edition (EE), you can upgrade the QAD .NET User Interface (UI) component to the QAD .NET UI of the subsequent EE release using the EE installer’s upgrade feature. 

  • This upgrade process is only for one release forward.  For example, if you have QAD EE 2013, you can only upgrade to the QAD .NET UI for EE 2013.1 using this process.
  • These instructions assume that you have not upgraded QAD Enterprise Edition and are only upgrading the QAD .NET UI component.

Important Note for 2013.1 EE The 2013.1 EE conversion documentation section “Upgrading Only the .NET UI Component” includes some steps you should skip.

2013.1 EE: in http://www.qad.com/documentlibrary/QAD+Enterprise+Edition/QAD+2013.1/Installation-Conversion/Progress+Conversion+Guide/Upgrading+Only+the+NET+UI+Component?extoid=110879c6d1851410VgnVCM100000810903a7RCRD&extchannel=026abfe5b5ca0410VgnVCM100000810903a7RCRD
skip steps 19 through 25.

Exception You cannot upgrade EE 2012.1 to use the QAD .NET UI released for EE 2013 (QAD .NET UI 3.0.0) due to a report schema change.

Warning You cannot use a newer QDT version to configure the QXtend component of an earlier Enterprise Edition installation. To maintain QXtend functionality following a QAD .NET UI upgrade, you must also select the QXtend component when you upgrade the QAD EE User Interface.


To upgrade the QAD .NET UI component:

1.  Back up the environment. See Back Up Environment.

2.  Shut down the existing environment using the appropriate script.

3.  Go to the < media_install >/qdt/envs/<env>/scripts directory.

4.  Run the checkqadfin< env >.*, checkqadui_AS< env >.*, and checkqadui_WS< env >.* scripts to verify the environment has shut down.

5.  Go to the media’s install directory and run the install script for your environment.

6.  Specify the current QDT installation directory as the target directory for the upgrade.

7.  The QDT installer should recognize that QDT is already present in the directory and validate the version being replaced. Note both versions for later reference.

8.  Accept the default log and XML locations offered. They are the same as the previous installation.

9.  Use the default folder name that appears. It should be the same as the previous installation.

10. Review the displayed installation summary and then proceed.

11. After the file copy completes, press Enter to end the script.

12. Go to the QDT installation directory and launch QDT. This is done as follows:

Windows: Select Start|All Programs|QAD Deployment Toolkit|Start QDT.

     Linux/UNIX: Go to < qdt_install_directory > and run the qadinst installation script.

For Red Hat 6 environments, run the qadinst_RH6_64bit or qadinst_RH6_32bit executable.
See Installation Guide: QAD Enterprise Edition – Progress Database for more information regarding Red Hat 6 requirements.


13. Go to Help|About and use the information noted in step 7 to verify the previous QDT version was updated.

14. Choose Edit/Installation Media Location and select the location of the media just used for the QDT update.

15. Click Install.

16. Select the environment to update and click OK.

17. Select the QAD EE User Interface update check box (do not select any other boxes) and click the Update button.

18. The .NET UI component upgrade begins. When the file copy finishes, select Close.

Skip the following steps A – G unless you are upgrading from 2011.1 EE to 2012 EE. If you are upgrading from 2011.1 EE to 2012 EE, do steps A – G and then continue on to step 19.

AGo to the progrs/db directory on the release media and load the dltadmnetuiSP9.df file into the production admin and empty admin databases. This is necessary for the UI reporting components to compile successfully.


B. Shut down and start the databases in single-user mode using the command:

     $DLC/bin/_progres -1 database_name

C. Enter the following code in the Progress Editor to unfreeze the admin (logical qadadm) database tables:


       for each _file where _file-number > 0 and _File-Number < 32768:
           _frozen = no

D. Once the tables are unfrozen, go to Tools|Data Dictionary|Admin, Load Data and Definitions|Data Definitions (.df file) and fully qualify the input path to point to the location.


E. Select OK.

F. Repeat steps 19 through 23 for each environment/admin database being updated.

G. Once the environment (admempty and production databases) is updated, dump out the updated admempty database definitions (admempty.df). This new admempty.df should replace the existing admempty.df. This is needed to allow for future cloning of this environment.


19. Click Admin on the main QDT screen.

20. Select Start QAD EE in the Action pane to start the environment.

21. Select Execute to start the databases and AppServers for the environment.

22. The system prompts you to execute all steps listed. Select Yes.

23. The system prompts you to clear the log. Accept the default (No).

24. Select Close.

25. When the operation finishes, select Close to dismiss the log window and return to the Action pane.

26. Select Configure QAD EE in the Action pane.

27. Select the UI Configuration: Create UI Configuration in the Action Set pane and select Reset.
The Reset feature allows you to reset a step or steps in a previously configured Action Set.

28. The system prompts you to reset all operations listed for Create UI Configuration. Select Yes to continue.

29. Select Close when the operation finishes.

30. In the Product pane, select QAD < environment_name >: QAD EE.

31. Select Configure QAD EE from the Action pane. Note that the Create UI Configuration is no longer marked complete and can be run again.

32. Select Execute to recreate the updated UI configuration.

33. Select Close to dismiss the log pane. Note that the UI Configuration is again marked as complete in the Steps in Action Set pane.

 

https://knowledgebase.qad.com/kmp/article/AA-80396/0/Upgrading-the-QAD-.NET-UI-in-Enterprise-Edition.html

Advertisements

About iambaprang

Bap Rang's house

Discussion

No comments yet.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s