-
Notifications
You must be signed in to change notification settings - Fork 91
WDT3: Error occurred in "OPSS Processing" phase execution #1499
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
Comments
@zeusbaba In order to support RCU schemas where every Data Source has a different password, you will need to create a sparse DataSource configuration that specifies the password for each RCU DataSource. |
@zeusbaba We no longer use the shadow table to retrieve database connection/credentials information to set up the datasources. Since you are using different credentials for each datasource, you can create a sparse model and specify their passwords. |
Thanks for feedback. see example snippet from template for
we define all of those
|
as I stated in the original post, the same setup with the same WDT templates works fine with |
As Johnny mentioned, we changed our approach to handling RCU-related Data Sources to not use the STB table to populate that connection-related information (primarily due to RCU limitations for database connection URLs). The STB table approach was handling your specific use case in WDT 1.x. The template approach works fine in our tests so clearly, there is something different between what you are doing and what we test. Can you provide a simplified set of steps and model files that will allow us to reproduce the issue? |
with 'template approach', do you mean that only btw, as you requested, i'm preparing templates to share, i need to clean out customer related data, sharing soon, |
here are the steps: step1) create
step2) configure OAM domain ( |
@zeusbaba Thanks, we have managed to identify an issue so Johnny is working to try to understand what needs to be done to correct the problem. Once we identify a fix, it would be good if we could send you an installer to test to make sure that it resolves your issue prior to releasing a new version. |
@zeusbaba I have created a fix for the issue, if you don't mind, can you test this out in your environment? |
thanks @robertpatrick & @jshum2479 sure, i'll do a quick round of testing now, i'll get back to you with results soon |
i have just run the same cycle by using the version you have sent
do we still need to define
|
few lines from
|
I use model like this (credentials are left out)
|
Note: we don't support using with |
yes, we don't use as I understand (see from your example); regardless of WDT version,
which I already do, and still get the same error as result. |
Do you have the resources section setting the different passwords? |
yes, see gist snippet shared in this comment |
Can you share the standard output log including the command line argument and the createDomain.log? |
here is the ansible task remotely executing
i've shared |
I don't see in the log trying to configure the infra db.
Since you are creating your own typedefs. Can you attach you OAM.json typedefs file? |
yes
notice that |
Our logic depends on that, so you should put list out the schemas there. |
i see, this is introduced with i'll share results soon |
I make a minor change, can you use this instead. |
strange that it fails with
why it tries to wrong target?
|
|
see WDT template from our
|
Oh I see the problem. I do the reset before the topology is created, so set targets failed. Can you try this again. I don't have an easy way to test OAM. |
You should also consider changing your custom typedefs to set the |
My suggestion is we focus on making the JRF domain creation work properly. WDT does not officially support OAM so once the JRF use case is working, you should be able to use a valid typedef file for OAM and have it work properly. What fields are needed in the typedef file to create a domain with RCU schemas has not changed. I suppose it is possible that WDT 1.9.x might have been more tolerant of typedef file omissions/errors but that doesn't constitute a regression in my mind. |
Thanks for your efforts so far. I will be back later and continue on this collaboration. p.s. i'm based in Norway, i'll try to be online in sync with your timezone. |
good news @jshum2479 :)
functional validation of OAM components will be done later. when would you be able to make a release? |
thnx @robertpatrick sure, i'll follow your suggestion and experiment further. |
we are in process of upgrading to |
@zeusbaba I will try to get a new release created tomorrow. |
We are using WDT for domain config of MW components (OAM, OHS, OSB, SOA, ...)
Currently, we are working on upgrading
WDT
from1.9.20
to3.2.5
(the latest version)The flow we follow is simply;
rcu schemas
are setup using oracle'srcu
utility, each schema has a unique pwdcreateDomain
) usingWDT
by feeding it withWDT templates
While applying this for OAM domain, I get an error at
createDomain
phase.NB! this works fine when using
WDT 1.9.20
and this error happens only when using theWDT 3.x.x
If needed, I can also send the full
createDomain.log
Please kindly advise, your feedback is much appreciated
Regards
Yilmaz
The text was updated successfully, but these errors were encountered: