rspecupgrade.properties 6.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127
  1. ###Licensed Materials - Property of IBM
  2. ###
  3. ###IBM Cognos Products: rspecupgrade
  4. ###
  5. ###(C) Copyright IBM Corp. 2005, 2016
  6. ###
  7. ###US Government Users Restricted Rights - Use, duplication or disclosure
  8. ###restricted by GSA ADP Schedule Contract with IBM Corp.
  9. ##
  10. ## Global configuration options for RSPECUPGRADE.
  11. ##
  12. ## These options are properties that are use for the entire Java Virtual Machine.
  13. ## Updating these properties without restarting the virtual machine may produce
  14. ## unexpected behaviour.
  15. #
  16. ## Validate input against the schemas/DTD before upgrading.
  17. ## This should only be turned off under the direction of Cognos.
  18. #com.cognos.rspecupgrade.rsupgrade.validateInput=true
  19. #
  20. ## Force the output of the upgrade to be validated against the schema.
  21. ## This should only be turned off under the direction of Cognos.
  22. #com.cognos.rspecupgrade.rsupgrade.validateOutput=true
  23. #
  24. ## Maximum number of report specification changes made to fix
  25. ## syntactic errors in the upgraded report specification before
  26. ## aborting.
  27. ##
  28. ## Used in cases where the schema fixup algorithm can not come to a speedy
  29. ## resolution, and the upgraded report is helplessly broken. If the upgrade
  30. ## aborts the report may not be syntactically valid.
  31. ##
  32. ## Used in conjuction with:
  33. ## com.cognos.rspecupgrade.rsupgrade.validateOutput
  34. ## com.cognos.rspecupgrade.rsupgrade.validateInput
  35. #com.cognos.rspecupgrade.rsupgrade.maxSchemaFixup=1000
  36. #
  37. ## Provide debug information showing the different stages of a upgraded report
  38. ## specification. Used for debugging, and can fill up your disk space.
  39. #com.cognos.rspecupgrade.rsupgrade.writeIntermediateFiles=false
  40. #
  41. ## Prefix for debugging files when intermediate steps are written. The same prefix
  42. ## should not be shared amoungst different instances. The prefix is both a directory
  43. ## and the start of the file name.
  44. #com.cognos.rspecupgrade.rsupgrade.intermediateFilePrefix=c:/temp/upgrade_
  45. #
  46. ## Should the stack trace and internal messages be embedded into the report
  47. ## specification if an internal error occurs.
  48. ##
  49. ## Enabling this option is considered a potential security hole, since details
  50. ## about the installation, such as file paths, may be revealed.
  51. #com.cognos.rspecupgrade.rsupgrade.embedInternalError=false
  52. #
  53. ## When this property is set to true, CRN reports with lists and or repeaters that reference
  54. ## the same query will have "enableShareResultSet" attribute set to true in the upgraded report,
  55. ## and the shared query will have a dimensionInfo element that corresponds to the CRN cube.
  56. ## See the following work order for details:
  57. ## Work Order 2594 - QRD Generation Based on Dimension Info for Baltic Compatibility
  58. #com.cognos.rspecupgrade.rsupgrade.enableShareResultSet=true
  59. #
  60. ## Force CQE expressions to be rewritten during upgrade.
  61. ## This should only be turned on for debugging, or under the direction of Cognos.
  62. #com.cognos.rspecupgrade.rsupgrade.rewriteCqe=false
  63. #
  64. ## Force CRX expressions to be rewritten during upgrade.
  65. ## This should only be turned on for debugging, or under the direction of Cognos.
  66. #com.cognos.rspecupgrade.rsupgrade.rewriteCrx=false
  67. #
  68. ## Embed the original report specification in the upgraded report specifcation.
  69. ##
  70. ## If you never want the report embedded then use:
  71. ## com.cognos.rspecupgrade.rsupgrade.embedOriginalSpecification=NEVER
  72. ##
  73. ## If you want the report embedded when a warning or error is issued then use:
  74. ## com.cognos.rspecupgrade.rsupgrade.embedOriginalSpecification=WARNING
  75. ##
  76. ## If you want the report embedded when an error is issued then use:
  77. ## com.cognos.rspecupgrade.rsupgrade.embedOriginalSpecification=ERROR
  78. ##
  79. ## If you want the report always embedded use:
  80. ## com.cognos.rspecupgrade.rsupgrade.embedOriginalSpecification=ALWAYS
  81. #com.cognos.rspecupgrade.rsupgrade.embedOriginalSpecification=NEVER
  82. #
  83. ## Sets pageBreakText option on lists and crosstabs.
  84. #com.cognos.rspecupgrade.rsupgrade.pageBreakText=true
  85. #
  86. ## Sets interactivePageBreakByFrame option on report element.
  87. ## NOTE: This option only applies to the upgrade of Cognos 8 reports (v5 spec).
  88. ## ReportNet reports (v4 spec) are always upgraded with this attribute set to true.
  89. #com.cognos.rspecupgrade.rsupgrade.interactivePageBreakByFrame=false
  90. #
  91. ## Output an information message indicating that a report has been upgraded.
  92. ## Message will contain the source and destination name space.
  93. #com.cognos.rspecupgrade.rsupgrade.upgradeInfoMessage=false
  94. #
  95. ## Should layout query frames be automatically named when a report is upgraded
  96. ## from http://developer.cognos.com/schemas/report/1/ (Baltic).
  97. #com.cognos.rspecupgrade.rsupgrade.layoutNameGeneration.1=true
  98. ## Should layout query frames be automatically named when a report is upgraded
  99. ## from http://developer.cognos.com/schemas/report/2.0/ (Bering).
  100. #com.cognos.rspecupgrade.rsupgrade.layoutNameGeneration.20=true
  101. ## Should layout query frames be automatically named when a report is upgraded
  102. ## from http://developer.cognos.com/schemas/report/3.0/ (Blaring).
  103. #com.cognos.rspecupgrade.rsupgrade.layoutNameGeneration.30=true
  104. #
  105. #
  106. ## Scripts that will execute before an upgrade.
  107. ## com.cognos.rspecupgrade.rsupgrade.plugin.preprocess[0]=../plugin/preprocess0.xsl
  108. ## com.cognos.rspecupgrade.rsupgrade.plugin.preprocess[1]=../plugin/preprocess1.xsl
  109. #
  110. ## Scripts that will execute after an upgrade
  111. ##com.cognos.rspecupgrade.rsupgrade.plugin.postprocess[0]=../plugin/postprocess0.xsl
  112. ##com.cognos.rspecupgrade.rsupgrade.plugin.postprocess[1]=../plugin/postprocess0.xsl
  113. #
  114. ## Should the implementation of Work Order 2628 be enabled?
  115. ## As part of work order, the fillEffects elements are upgraded to
  116. ## fill objects below the style/generatedBackground element.
  117. #com.cognos.rspecupgrade.rsupgrade.enableWorkOrder2628=true
  118. #
  119. ## Version of the report specification to upgrade to.
  120. # com.cognos.rspecupgrade.rsupgrade.targetNamespace=http://developer.cognos.com/schemas/report/13.1/
  121. #
  122. ## Turn off the feature of adding checksum to each upgraded report spec.
  123. ## By default, this feature is ON.
  124. #com.cognos.rspecupgrade.rsupgrade.enableChecksumGenerator=false
  125. ## Number of recent report schemas to load at startup. This is added to improve performance of cold-start runs.
  126. ## By default, the last 3 recent schemas (including target) will be pre-loaded. To turn off any pre-loading, set to 0.
  127. #com.cognos.rspecupgrade.rsupgrade.numRecentReportSchemasToPreload=3