Is the siperian-mrm.ear file is deployed on the ManagedServer by any chance? This issue typically occurs in that case.
To resolve this issue, do any one of the following:
1) Manually register the datasource on the managed server.
2) Deploy siperian-mrm.ear on AdminServer and launch the Hub Console, register the database and change the target to ManagedServer.
yes the superian-mrm.ear is deploying on the cluster (which is consist of managed server) you can see the detail of the deployment on the screenshot below
and I already tried to do your no. 1 suggestion to manually register the ORS, but I don't think my customer want to do something a bit occupied.
So I just want to make the customer can register the ORS directly from hub console.
Once you created the DataSourec from the weblogic side .
Customer can register the ORS from the hub console , only they need to un-check the option Create Datasource after registration .
what I want is when register ors from hub console, the data source is automatically created too from weblogic side.
no I don't want to create data source manually from application server.
what I want is, when I register ORS from the hub console, in the end of register ORS step it will and should be automatically create data source in the application server.
that is how hub console work isn't it?
so when the error is appear, I want to fix the issue.
This is an expected behavior as per installation guide -
In application server cluster environments, manually create the data sources and connection pools for the Operational Reference Stores.
Please find guide below and check point 7c -
Register an Operational Reference Store
Please create datasource manually and then register ORS in hubConsole by unchecking create datasource box and let us know if you face any issue.