Scenario:
The import namespaces present in the composite.xml pointing to non prod instances might look negligible and might not cause any issues
during design and even during the initial period of run time.
This can be of a mild risk if its not taken care.
Risk:
During a production server bounce.
All the SOA Composites would try to redeploy itself at the time of start up.
Those Composites which have a import reference to other non prod instances will have a problem,
incase the referred wsdls are not up and running.
These composites will fail to start up.
Fire Fight Fix:
If you are currently at this stage and wouldn't like to do a code change at the moment in Production.
Then start up your refered services and then re-bounce your production server.
Solution:
1)Use the config plane Search/Replace feature at deployment time.
2)Refering them from MDS directly is another option
The import namespaces present in the composite.xml pointing to non prod instances might look negligible and might not cause any issues
during design and even during the initial period of run time.
This can be of a mild risk if its not taken care.
Risk:
During a production server bounce.
All the SOA Composites would try to redeploy itself at the time of start up.
Those Composites which have a import reference to other non prod instances will have a problem,
incase the referred wsdls are not up and running.
These composites will fail to start up.
Fire Fight Fix:
If you are currently at this stage and wouldn't like to do a code change at the moment in Production.
Then start up your refered services and then re-bounce your production server.
Solution:
1)Use the config plane Search/Replace feature at deployment time.
2)Refering them from MDS directly is another option
No comments:
Post a Comment