Skip to content
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

Open
textanalyticsman opened this issue May 10, 2021 · 8 comments
Open

Update enhancement #894

textanalyticsman opened this issue May 10, 2021 · 8 comments
Assignees
Labels
converge to model related to enabling WDT to converge existing domain to match the model enhancement New feature or request

Comments

@textanalyticsman
Copy link

textanalyticsman commented May 10, 2021

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?

  1. Let us say I have a model used to create a domain.
  2. After some time I decided to add a new server on the domain so, I modify the model by adding a new server.
  3. WDT update is executed and it queries the actual domain up and running, compares it against the model and updates just things (in this case to create a new server) that are different.

Kindly let me know whether this could be considered as an enhancement or not.

Best regards,
TAM

@textanalyticsman textanalyticsman changed the title Update enhacement Update enhancement May 10, 2021
@lennyphan
Copy link
Member

@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?

@textanalyticsman
Copy link
Author

textanalyticsman commented May 10, 2021

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.

@ddsharpe ddsharpe added the enhancement New feature or request label May 10, 2021
@ddsharpe
Copy link
Member

@textanalyticsman What issues are you seeing when running UPDATE with the 2nd model?

@textanalyticsman
Copy link
Author

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.

@rakillen
Copy link
Member

The WDT compareModel tool can compare the before and after models, and provide a model with only the differences:
https://oracle.github.io/weblogic-deploy-tooling/userguide/tools/compare/

@textanalyticsman
Copy link
Author

textanalyticsman commented May 11, 2021

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.

@robertpatrick robertpatrick added the converge to model related to enabling WDT to converge existing domain to match the model label Dec 23, 2021
@textanalyticsman
Copy link
Author

textanalyticsman commented Feb 11, 2022

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,
TAM

@robertpatrick
Copy link
Member

I can try to automate your idea. However, it would be nice to have this functionality out of the box.

@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 Discover Domain and Create Domain tools. One could make an argument that the ability to chain together different tool invocations that operate on the same data (i.e., the model files) is out of the box functionality. It certainly was a key design requirement when we started this project!

As Richard points out, it is possible to combine the use of the Compare Model and Update Domain tools to achieve your use case. However, we will discuss whether or not it is possible to improve the Update Domain tool to make it more efficient.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
converge to model related to enabling WDT to converge existing domain to match the model enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants