IMPORTANT FILES IN PRODUCTS DIRECTORY The environment specific variables for IM, ADAPTERS & BW will be present on the

products directory as below, ppr-ap3-c:/home/tibppr/products/common/config> ls -ltr *.cfg -rw-r--r-- 1 tibppr tibco 2159 May 23 2007 bwVariablesGlobales.cfg -rw-r--r-- 1 tibppr tibco 21187 Aug 16 2010 variablesGlobales.cfg -rw-r--r-- 1 tibppr tibco 21994 Jul 20 2009 tibenv variablesGlobales.cfg -> This file will have the environment specific variables for IM & ADAPTERS in PPRD1 Env. bwVariablesGlobales.cfg -> This file will have the environment specific variables for BW in PPRD1 Env. Tibenv -> This file will have all the directory paths and variables to set with respect to the environment and tibco. DIFFERENCE BETWEEN RELEASE AND PRODUCTS DIRECTORY In release directory you will be have the configuration files copied from PVCS server while promoting the packages through Comanche Tool. Also, the files in the release directory will have the environment parameter names instead of values so we can not understand the files easily. So, CM team will be responsible to make modification on any file. In products directory, it will have the configuration files after transferring the environment parameters names into values with respect to the environment. So, the configuration files in products directory will be easily understandable. The EM team will be responsible for modification on any files on products directory. Leveling and non-leveling of PVCS modules The leveling components means the same file will be used by the component for all the environments like TST, PPRD1, PPRD2 & PRD. The non-levelling components means the component will be using different files for every environment.

If the component is using different files for each and every environment then those files will be idenfied by adding the machine name and environment at the suffix as below, PropINTER_CON.18.Engine1.cfg.ppr-ap5-c.ppr The non-leveled components can not be check-in normally we need to add the exception to check-in the file to allow the modification and to create the new version. We need to add those non-leveled pvcs modules on the exception module to make the modification and to create the new verision. For Ex: 1. If the pvcs module is present on the spain pvcs server then the file need to be add on the exception module on the spain pvcs server tst-to2-i with herrtux user as below, tst-to2-i:/home/swcomun/herrtux/gestent/ excepcionesModulos PropINTER_PRV.39.Engine1.cfg.esxsz008.uat IM/config 2. If the pvcs module is present on the italy pvcs server then the file need to be add on the exception module on the italy pvcs server esxsa306 with herrtux user as below, tst-to2-i:/home/swcomun/herrtux/gestent/ excepcionesModulos PropADIM_CRM_IRIS_PRV.01.Engine1.cfg.esxsz00c.uat IM/config

Page 2 of 2