-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update enhancement #894
Comments
@textanalyticsman instead of modifying the original model to add a new server, have you tried just providing a separate sparse model with the just the model for adding a new server and running update to see if it updates the domain with just the change provided? |
Thanks a lot for your comment. I know this is possible. We have hundreds of SOA BPEL domains and we want to have a source of truth without sparse models that make our configuration more complex. Thus, if a new change appears we want to modify the model and then running update. |
@textanalyticsman What issues are you seeing when running UPDATE with the 2nd model? |
WDT is updating everything. It would be useful for our case if we can run update with the new version of our model and WDT works only with the elements that have been added or modified. |
The WDT compareModel tool can compare the before and after models, and provide a model with only the differences: |
Thanks a lot for your attention. We are using WDT in combination with other configuration management tools to provision and to update SOA/BPEL environments. I can try to automate your idea. However, it would be nice to have this functionality out of the box. The challenge with SOA/BPEL is the fact that we cannot just dispose and recreate environments due to the constraints imposed by the way SOA/BPEL is related to RCU schemas. |
Hello there, Just a question, is it possible to implement this? This is going to help us a lot and we are heavy users of Weblogic and SOA/OSB/BPM domains. Thanks a lot in advance. Best regards, |
@textanalyticsman From the start, WDT has always been a collection of "single-purpose" tools (that operate on a common data model) that can be chained together to meet different use case requirements. For example, cloning an existing domain requires a combination of using the As Richard points out, it is possible to combine the use of the |
Hello,
When an update is executed through WDT it updates all the model's elements even though they are the same on the actual domain, which is up and running.
Is it possible to change this in this way?
Kindly let me know whether this could be considered as an enhancement or not.
Best regards,
TAM
The text was updated successfully, but these errors were encountered: