Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revisionBoth sides next revision
72:clearcase_req [2018/07/09 18:50] – created bkkr72:clearcase_req [2018/07/09 18:51] – [General Requirements and Information] bkkr
Line 11: Line 11:
   * If multiple Stages servers are in use (i.e. production1, production2, test), the value of the viewTagPrefix (see chapter 3 in the Stages configuration file PKitConfig.xml) has to be configured uniquely for each Stages Server. The following options are possible:   * If multiple Stages servers are in use (i.e. production1, production2, test), the value of the viewTagPrefix (see chapter 3 in the Stages configuration file PKitConfig.xml) has to be configured uniquely for each Stages Server. The following options are possible:
       * Option 1       * Option 1
-        * Server A – No CMS-Property „viewTagPrefix” defined. Stages uses the default value “__pkit_view_”. +        * Server A – No CMS-Property „viewTagPrefix” defined. Stages uses the default value “__pkit_view_”. * Server B – The configuration of the CMS-Property „viewTagPrefix” has to be defined, the value must not be identical with the default value of Server A, i.e. „__pkit2_view_“ 
-        * Server B – The configuration of the CMS-Property „viewTagPrefix” has to be defined, the value must not be identical with the default value of Server A, i.e. „__pkit2_view_“ +      * Option 2 
-  * Option 2 +        * Server A - CMS-Property „viewTagPrefix” has been defined, i.e. „_servera_view_“ 
-      * Server A - CMS-Property „viewTagPrefix” has been defined, i.e. „_servera_view_“ +        * Server B - CMS-Property „viewTagPrefix” has been defined, i.e. „_serverb_view_“
-      * Server B - CMS-Property „viewTagPrefix” has been defined, i.e. „_serverb_view_“+