I have an OSB project containing a DVM. This contains a number of values required for other OSB projects for connecting to 3rd party API's. Authorization Key, username etc.
We want to be able to redeploy this project with the new values in the DVM when we move between environments or when Key, name values etc change.
One use is the inclusion of a key and username value as header in a call to a REST service.
Is it possible to execute one of these actions through the use of a Configuration plan
1) Alter the contents of a DVM. So the Configuration plan can be used to apply value changes to the DVM
2) Alter the call for the DVM lookup which is currently inside an insert action as XQuery text
<con3:insert varName="outbound" xmlns:con1="http://www.bea.com/wli/sb/stages/routing/config" xmlns:con3="http://www.bea.com/wli/sb/stages/transform/config">
<con2:id>_ActionId-a1f50ed.f48efbc.0.161b54086d5.N7ddd</con2:id>
<con3:location>
<con2:xpathText>./ctx:transport/ctx:request/tp:headers</con2:xpathText>
</con3:location>
<con3:where>first-child</con3:where>
<con3:expr>
<con2:xqueryText><tran:user-header name="Authorization" value="Konnect ver=1 key={dvm:lookup('KonnectResources/Konnect.dvm', 'Org', 'KONNECT', 'AuthKey', '')}
usr={dvm:lookup('ResourceProject/Project.dvm', 'Org', 'OrgName', 'Username', '')}" xmlns:tran="http://www.bea.com/wli/sb/transports"/></con2:xqueryText>
</con3:expr>
</con3:insert>
Instead of key={dvm:lookup('ResourceProject/Project.dvm'.....
We have key={dvm:lookup('ResourceProject/Project_ENV.dvm'......
Then we have a separate DVM per project. So the configuration file will be used to change the DVM name
I have tried to apply a configuration plan for both of these but it does not apply the changes.
If there is another way I should be doing this please let me know
Cheers
Owen