You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 7, 2020. It is now read-only.
I realized that Orawls module always create a 'defaultCoherenceCluster', with AdminServer as a member, when we provision a WLS infrastructure, even if we don't manage this resource.
Is this correct? We should always use that feature? Can't we chose between create or not create the 'defaultCoherenceCluster'? Didn't find an answer for this question in Oracle Help Center...
Locally, I added a simple parameter to 'domain.pp' that allow us to decide that (to create or not to create the cluster), and made a change at the 'domain.py.erb' script, so it can 'understand' the new parameter in 'domain.pp'.
Waiting for your answer(s) to do (or not) the PR.
Thanks for the attention.
The text was updated successfully, but these errors were encountered:
I do this because of FMW but for plain wls you probably don't need this and i guess this should be optionally.
If you can make a PR with a meaningful domain.pp parameter and true as default.
Greetings, friends.
I realized that Orawls module always create a 'defaultCoherenceCluster', with AdminServer as a member, when we provision a WLS infrastructure, even if we don't manage this resource.
Is this correct? We should always use that feature? Can't we chose between create or not create the 'defaultCoherenceCluster'? Didn't find an answer for this question in Oracle Help Center...
Locally, I added a simple parameter to 'domain.pp' that allow us to decide that (to create or not to create the cluster), and made a change at the 'domain.py.erb' script, so it can 'understand' the new parameter in 'domain.pp'.
Waiting for your answer(s) to do (or not) the PR.
Thanks for the attention.
The text was updated successfully, but these errors were encountered: