3 Replies Latest reply on Aug 20, 2014 11:10 PM by Patrick Pang-Oracle

    Handle customized DVM's  during the redeployment

    2629059

      Hello, I ‘am looking for a possibility for merging or extending DVM’s which are customized at runtime during the redeployment. Is there an solution for this problem or how can I handle extended DVM’s during the redeployment without losing the customized values?

        • 1. Re: Handle customized DVM's  during the redeployment
          Dhaval Parikh-Oracle

          Hi,

           

          Please refer the following section in the Developer guide for 12c. If you are referring to 11g there is similar section in 11g Documentation that explains how to export / import Runtime changes to metadata and reimport them.

           

          2 Oracle SOA Suite Custom WLST Commands (12g Release 1 (12.1.3.0.0))

           

          sca_exportUpdatesMb

          sca_importUpdatesMb

          1 person found this helpful
          • 2. Re: Handle customized DVM's  during the redeployment
            2629059

            Hi Dhaval,

            I want to thank first for the quick answer. The import and export WSLT-Commands are helpful to export the DVM’s which are changed during runtime and reimport them after redeployment. With these Commands it is not possible to merge only the DVM values into to the new structure of the redeployed DVM. The import WSLT-Command are overriding the redeployed DVM. I would like to add column or row by redeployment but I do not want to lose the values which are changed during runtime.

            • 3. Re: Handle customized DVM's  during the redeployment
              Patrick Pang-Oracle

              When you create a DVM and make changes to it during runtime using SOA
              composer, the DVM is updated and you can use sca_exportUpdateMb to extract the composite
              or use sca_exportUpdates to extract just the dvm file.

               

              The problem is that when we have the 2nd version which has a
              different change, I found that only the runtime change is maintained. For
              example,

               

              Version 1:

              BO  Boston

              SF   San Francisco

               

              Version 1 (after custom change):

              BO  Boston

              SF   San Francisco

              HK  Hong Kong

               

              Version 2: (from Jdev)

              BO  Boston

              SF   San Francisco

              LA  Los Angeles

               

              Version 2: (After merging)

              BO  Boston

              SF   San Francisco

              HK  Hong Kong

               

              Therefore, the merge does not tries to merge the change in DVM but instead replace it.