In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com



  •     QAD Glossary

  • Upgrade to QAD BI 3.4.1 from BI 3.4
    BI Portal Upgrade Procedure
    Preparation
    1
    Shut down Tomcat.
    2
    Back up the BI Portal database.
    Note: QAD BI Portal version 3.4 requires WhereScape RED or QAD BI DWD version 6.1 or later.
    Upgrade Steps for QAD BI Portal
    1
    Copy the TOMCAT_HOME\webapps\ your_bi_appname directory to TOMCAT_HOME\your_bi_appname.save34 so that you have a backup of your BI 3.4 web application.
    2
    Unzip the new BI 3.4.1 Portal data.zip file into TOMCAT_HOME\webapps\ your_bi_appname, overwriting any existing files with the newer version from the data.zip file. Your configuration files will not be overwritten.
    3
    Start Tomcat.
    Note on Password Encryption in the BI Portal
    As of BI Portal 3.4, you may now encrypt the SQL Server password in both the server-config.xml file (which contains the connection information for the BI Portal database) and in the aw_sys_config table (which contains the connection information for the BI Data Warehouse). The encryption uses the Blowfish algorithm.
    A command-line tool to encrypt the password named encpwd.bat is located in TOMCAT_HOME\webapps \your_bi_appname\ cmdline. To run this, open a DOS window, change to the cmdline directory, and run:
    encpwd.bat mypassword
    The encrypted password will be printed on the screen. Copy this value and use it in the server-config.xml file as the value for the pwd. Also make sure that pwdEncrypted="true". (If you change back to using an unencrypted password value, make sure you set pwdEncrypted="false".)
    Similarly, if you want to encrypt the password used by the Portal to connect to the Data Warehouse, use the encpwd.bat script to generate the encrypted password, then edit the value for the jdbcPassword in the aw_sys_config table, the DATASERVICE row, and set it to the encrypted value; make sure you add pwdEncrypted="true".
    If you change either password, you must stop and restart Tomcat for the change to take effect.
    Verification
    1
    Connect to your BI Portal. Click on the About link on the login screen and verify that the Version is 3.4.1 and the Build Number is BI3-TRUNK-JOB1-1008.
    BI Metadata Upgrade Procedure
    Refer to the release notes for what has changed in this release. One of the very important changes is that the warehouse now supports multi-byte characters. All varchar and char columns will now be changed to nvarchar.
    Preparation
    1
    Take a backup of the current warehouse database.
    2
    Plan for a couple of hours of down time.
    3
    Ensure none of the loads are currently in progress. All jobs must be completed.
    4
    Stop Scheduler.
    5
    Before you begin, make note the the following:
    a
    Note the AP_EE_HISTORY_DATE (if it exists): ______________________________________
    b
    Note the AR_EE_HISTORY_DATE (if it exists): ______________________________________
    c
    Note any DAILY_LOAD_SOURCE_Sxx jobs that appear after the standard _SNAPSHOT tables: _____________________________________________________________
    d
    Note any HIST_LOAD_SOURCE_Sxx jobs that appear after the standard _SNAPSHOT tables: _____________________________________________________________
    Warning This upgrade will replace all your load tables, so if there are any customizations to the load tables, ensure they are ready to be made again.
    Upgrade Steps for QAD BI Metadata
    1
    Log in to Setup Administrator.
    2
    Load Application 341-up (this includes all tables, but only new/modified parameters and jobs).
    3
    A dialog box will prompt you "Do you want to proceed now?"; click OK.
    4
    The next dialog box is for "Application Load Properties":
    a
    Select Dimension on the left; on the right, click on the box next to "Existing Dimension objects will be" and select Altered.
    b
    Select Dimension View on the lef; on the right, click on the box next to "Existing Dimension View objects will be" and select Recreated.
    c
    Select Stage Table on the left; on the right, click on the box next to "Existing Stage table objects will be" and select Altered.
    d
    Select Permanent Stage Table on the left; on the right, click on the box next to "Existing Permanent Stage table objects will be" and select Altered.
    e
    Select Fact Table on the left; on the right, click on the box next to "Existing Fact table objects will be" and select Altered.
    f
    Click OK.
    5
    The upgrade application installation will take some time as the load process alters/recreates various objects. Once the process completes, make any necessary customizations to your load tables. Verify that all other customizations are not affected.
    6
    Start the Scheduler, but make sure all jobs are still suspended.
    7
    You must populate some new parameters and possibly modify some existing values, as follows:
    a
    (EE sources only) Populate AP_EE_HISTORY_DATE_MIN with a value approximately three years back or whatever date value the customer specifies for their historic loads to begin at. Note the different date format of YYYYMMDD.
    b
    (EE sources only) If it doesn't exist, create an AP_EE_HISTORY_DATE_Sxx where xx = the number for every EE source system you have already installed. The number for each source should correspond to the source tied to the 'xx' number values at the end of the corresponding Parameters for DAILY_LOAD_SOURCE_Sxx, HIST_LOAD_SOURCE_Sxx and INITIAL_JOB_SETUP_CONNECTION_xx. It's OK to skip numbers if you have an SE source system in between. Populate that value with the AP_EE_HISTORY_DATE you noted at the beginning.
    c
    (EE sources only) Populate AR_EE_HISTORY_DATE_MIN with a value approximately three years back or whatever date value the customer specifies for their historic loads to begin at. Note the different date format of YYYYMMDD.
    d
    (EE sources only) If it doesn't exist, create an AR_EE_HISTORY_DATE_Sxx where xx = the number for every EE source system you have already installed. The number for each source should correspond to the source tied to the 'xx' number values at the end of the corresponding Parameters for DAILY_LOAD_SOURCE_Sxx, HIST_LOAD_SOURCE_Sxx and INITIAL_JOB_SETUP_CONNECTION_xx. It's OK to skip numbers if you have an SE source system in between. Populate that value with the AR_EE_HISTORY_DATE you noted at the beginning.
    e
    Set INITIAL_JOB_SETUP_CONNECTION_01_RUN to Y. If you have more than one source, create (if necessary) and set to Y a parameter named INITIAL_JOB_SETUP_CONNECTION_xx_RUN (where xx = the source number) for each INITIAL_JOB_SETUP_CONNECTION_xx source that has already been historically loaded.
    f
    ***Very important *** - Check the PO_ORDER_HISTORY_DATE and SALES_ORDER_HISTORY_DATE parameters. If the current date minus the PO_PROCESS_DAYS is newer than the PO_ORDER_HISTORY_DATE, or the current date minus the SALES_PROCESS_DAYS is newer than the SALES_ORDER_HISTORY_DATE, increase the process days value so that the current date minus that number of days will produce a date that is before the related ORDER_HISTORY_DATE (PO or SALES). Then set INITIAL_JOB_SETUP_DATE to the current date.
    g
    Change INITIAL_JOB_SETUP_ENABLED to Y.
    h
    If you want to add an additional data source now, do the following:
    Add the new source name to DAILY_LOAD_SOURCE_Sxx (where xx represents the next number in the sequence).
    Add the new source name to HIST_LOAD_SOURCE_Sxx (where xx represents the next number in the sequence).
    Add the new source name to INITIAL_JOB_SETUP_CONNECTION_xx (where xx represents the next number in the sequence).
    Add a new INITIAL_JOB_SETUP_CONNECTION_xx_RUN (if it doesn't already exist) and set its value to N.
    Add a new INITIAL_JOB_SETUP_CONNECTION_xx_TYPE (if it doesn't already exist) and set its value to either EE or SE depending on which type your financials system for that source is.
    i
    In the Scheduler, run the INITIAL_JOB_SETUP job.
    j
    The list of History and Daily jobs will have been re-written by the INITAL_JOB_SETUP job. Now add to the end of the DAILY_ and HIST_ load lists any jobs that occurred after the snapshot jobs (which you noted in the Preparation section).
    k
    Double-check the INITIAL_JOB_SETUP_CONNECTION_xx_RUN parameters to make sure that any sources that have been historically loaded have a Y next to their relative _xx_ number and that any new sources have an N.
    l
    If you have added a new data source, go back to the Scheduler. Start the HIST_START job. Once it starts, double check to make sure it started running HIST_ jobs only for your new data source.
    Fixing Existing SE Accounts Receivable (AR) Data
    If you have SE sources and use the AR module, you will have to run the job named JOB_FOR_QBI_640 once for each SE source to correct improper AR aging calculations that were not taking into account the CLOSED status of an invoice. The AR Aging calculations for open amounts no longer include any unpaid remainders from closed invoices.
    To run the job to correct existing data:
    1
    Set the parameter AR_PROCESS_CONNECTION_NAME to an SE source connection name.
    2
    In the QAD_MASTER connection, set the connection to the SE source with the appropriate extract id and password.
    3
    Run the job JOB_FOR_SE_QBI_640 in the Scheduler.
    4
    Repeat for each SE source connection (if you have multiple SE sources).
    Run the Upgrade Script in SQL Server
    A new dimension, dim_expected_pay_date, has been linked to the Accounts Payable and Accounts Receivable fact tables. In order to set the correct dimension key in the fact tables for existing rows, you must run a script in SQL Server as follows:
    1
    Log in to SQL Server studio.
    2
    Connect to the BI datawarehouse database and run the v34to341_metadata_post_upgrade.sql (found in the BI Portal install\sqlserver directory).
    Upgrade should be complete at this point. Resume normal processing.
    Update Portal Documentation and Standard Objects
    To install the latest metadata documentation into your BI Portal, unzip the latest qadbi-documentation.zip into your TOMCAT_HOME\webapps\ your_bi_appname \ documentation directory, overwriting the previous suite subdirectory and its contents.
    To install the latest BI Portal standard objects, copy the qad_standard_items.zip file into your TOMCAT_HOME\webapps\ your_bi_appname\ export directory. Then, in the BI Portal, log in as an Administrator. Go to the Administration -> Data Migration screen, click on the Import tab, click the radio button in front of "File on server" and enter in the box the file name qad_standard_items.zip. If you do NOT check the "Update existing records" box, only new objects will be imported; any of your current QAD Standard Objects will not be modified. To update the existing objects, check the "Update existing records" box. (You might want to export all objects prior to this step, so that you have a backup prior to updating existing records.)