Refreshing WEB UI elements after having applied DCI PTFs

Products

• Dynamic Capacity Intelligence

Issue/Introduction

The Dynamic Capacity Intelligence (DCI) PTFs that distribute a new revision of the WebUI have the following comments in SMP/E HOLD section:

                      **************************                    
                      * STEPS    TO    PERFORM *                    
                      **************************                    
  After SMP/E work is complete, rerun the customization job         
  $05WEBUI found in the CFHRSAMP library. This job will             
  replace the HTTPINST or HTTPINSB element to apply the updated Web 
  UI elements.                                                      
                                                                    
  Please see the DCI 2.0 installation guide for more information.   

Customization job $05WEBUI "untars" a file and install the USS part and the GUI.

1. if applying multiple WebUI PTFs, what is the correct order?
2. is a new USS directory required or the existing one can be used? 

Environment

Release: ALL
Component: Dynamic Capacity Intelligence

Resolution

1. If multiple WebUI PTFs are applied concurrently, install those fixes in ascending order but do not run $05USS.
   After the last WebUI fix is applied, then execute $05WEBUI.
   Reason for doing it this way is that the whole new WebUI is delivered. If $05WEBUI must be executed, this means that a new version (or revision) for DCI GUI is available.
   
   
2. Normally it is best to “untar” the files into the existing folder structure in USS. In this way, the old  WebUI version will be overwritten with the new one.
   The WebUI and USS elements can be “untarred” on a complete different structure. But, in this way, the new elements are in the new directory while the data like reports, policy and so on are in the old one; and so they must be copied to the new directory. Then all the references to the GUI directory must be updated, for example on the JCL for the Controller and on http.config.
   You can do that, but it is not recommended.
    

Additional Information

Dynamic Capacity Intelligence documentation:
Installing
Deploy Web UI Components and Create Directory Paths