SDK 4.0.0.5: CM.jar Is Not Copied BUG-cm_jars_structure.xml.example Missing

Question

Could someone please help me out. I am trying to fix this bug with:
SDK 4.0.0.5: CM.jar Is Not Copied into the Package To Be Deployed [ID 1315169.1]
And according to Oracle support I need to:
Solution
In SDK version 4.0.0, the cm.jar gets copied only in etc/lib folder. In the target environment it gets distributed by executing initialSetup.sh, which is part of the CM installation.
The structures/cm_jar_structure.xml should be created for the cm.jar distribution. You can see an example of the structure under the pkg scripts folder: etc/cm_jars_structure.xml.example (it just needs to be copied to structures/cm_jar_structure.xml). The cm.jar will then be copied to the correct locations in the application.
But I am missing the file cm_jars_structure.xml.example.
Does some have that file please?

Answer 1

Hi,
Here the comment from the FW_jars_strucure.xml.
<!-- for list_of_AND_conditions all conditions must be true for jar to be distributed       -->
<!-- for list_of_OR_conditions any of the conditions must be true for jar to be distributed -->
<!--
   example:
   <jar_name>
      <source_dir_jar>source directory where the jar file is located (mandatory)</source_dir_jar>
      <dest_folders>
         <dest_folder_1>destination 1</dest_folder_1>
         <dest_folder_2>destination 2</dest_folder_2>
         <dest_folder_3>destination 3</dest_folder_3>
      </dest_folders>
      <list_of_AND_conditions>
            <condition_1>SPLWAS=WLS</condition_1>
            <condition_2>DBNAME=TESTING</condition_2>
      </list_of_AND_conditions>
      <list_of_OR_conditions>
            <condition_1>DBUSER=cisuser</condition_1>
            <condition_2>DBUSER=CISUSER</condition_2>
      </list_of_OR_conditions>
      if child jvm path exists, then the jar file from the location specified
      here will be added to class_path (child_jvm_option)
      <child_jvm_path>PATH where jar file is located</child_jvm_path>
      <target_folder>(subfolder under java/target used as basedir for jar creation)</target_folder>
      <copy_classes>true (set to true if during install single fixes the class should just copied to $SPLEBASE/java/target)</copy_classes>
      <update_source_jar>
         <update_source_jar_1>(list here the folder that should be updated in base-shared-${jversion}-src.jar. eg.: source/base)</update_source_jar_1>
         <update_source_jar_2></update_source_jar_2>
      </update_source_jar>
   </jar_name>
   Uncomment the following block for testing
   ensure you have a test.jar under $SPLEBASE/etc/lib
   The jar file will be copied if SPLWAS=WLS and DBNAME=TESTDB and
   DBUSER is either cisuser or CISUSER.
-->
<!--
   <test.jar>
      <source_dir_jar>@SPLEBASE@/etc/lib</source_dir_jar>
      <dest_folders>
         <dest_folder_1>@SPLEBASE@/splapp/applications/XAIApp/WEB-INF/lib</dest_folder_1>
         <dest_folder_2>@SPLEBASE@/splapp/applications/root/WEB-INF/lib</dest_folder_2>
         <dest_folder_3>@SPLEBASE@/splapp/businessapp/lib</dest_folder_3>
         <dest_folder_4>@SPLEBASE@/splapp/mpl/lib</dest_folder_4>
         <dest_folder_5>@SPLEBASE@/splapp/standalone/lib</dest_folder_5>
      </dest_folders>
      <list_of_AND_conditions>
            <condition_1>SPLWAS=WLS</condition_1>
            <condition_2>DBNAME=TESTDB</condition_2>
      </list_of_AND_conditions>
      <list_of_OR_conditions>
            <condition_1>DBUSER=cisuser</condition_1>
            <condition_2>DBUSER=CISUSER</condition_2>
      </list_of_OR_conditions>
      <child_jvm_path>@SPLEBASE@/splapp/standalone/lib</child_jvm_path>
      <target_folder>base</target_folder>
   </test.jar>
-->/Markus