Check the SOA logs and determine which composite is causing the problem and then follow the below process to undeploy the composite by editing deployed-composites.xml:
1. Download and copy the ShareSoaInfraPartition.ear file to $MIDDLEWARE_HOME/oracle_common/common/bin
2. cd to $MIDDLEWARE_HOME/oracle_common/common/bin
and
run wlst.sh
3.
connect('weblogic','weblogic1','t3://localhost:7001')
provide the username, password and server URL
4. run the below command to deploy ShareSoaInfraPartition.ear
deploy('ShareSoaInfraPartition','ShareSoaInfraPartition.ear',upload='true')
5. Now run the below command by changing the "toLocation" ('/fmw11g/fmw1115/Middleware' is some location path on SOA machine)
exportMetadata(application='ShareSoaInfraPartition',server='AdminServer',toLocation='/fmw11g/fmw1115/Middleware',docs='/deployed-composites/deployed-composites.xml')
6. A deployed-composites folder will be created at "toLocation" path with deployed-composites.xml in it
7. Delete the composite which is causing the problem and save the file
For example, the MediatorTest composite:
<composite-series name="default/MediatorTest" default="default/MediatorTest!1.0">
<composite-revision dn="default/MediatorTest!1.0" state="on" mode="active" location="dc/soa_58b98be8-9ec8-41af-bb83-590f6004d1aa">
<composite dn="default/MediatorTest!1.0*soa_58b98be8-9ec8-41af-bb83-590f6004d1aa" deployedTime="2011-11-17T09:01:54.750+05:30"/>
8. Now run the below command by changing the "fromLocation" (this should be the same location as previous)
importMetadata(application='ShareSoaInfraPartition',server='AdminServer',fromLocation='/fmw11g/fmw1115/Middleware',docs='/deployed-composites/deployed-composites.xml')
9. Now bounce your server and the composite will not be deployed by SOA when it comes up and hence that should bring your soa-infra up.
1. Download and copy the ShareSoaInfraPartition.ear file to $MIDDLEWARE_HOME/oracle_common/common/bin
2. cd to $MIDDLEWARE_HOME/oracle_common/common/bin
and
run wlst.sh
3.
connect('weblogic','weblogic1','t3://localhost:7001')
provide the username, password and server URL
4. run the below command to deploy ShareSoaInfraPartition.ear
deploy('ShareSoaInfraPartition','ShareSoaInfraPartition.ear',upload='true')
5. Now run the below command by changing the "toLocation" ('/fmw11g/fmw1115/Middleware' is some location path on SOA machine)
exportMetadata(application='ShareSoaInfraPartition',server='AdminServer',toLocation='/fmw11g/fmw1115/Middleware',docs='/deployed-composites/deployed-composites.xml')
6. A deployed-composites folder will be created at "toLocation" path with deployed-composites.xml in it
7. Delete the composite which is causing the problem and save the file
For example, the MediatorTest composite:
<composite-series name="default/MediatorTest" default="default/MediatorTest!1.0">
<composite-revision dn="default/MediatorTest!1.0" state="on" mode="active" location="dc/soa_58b98be8-9ec8-41af-bb83-590f6004d1aa">
<composite dn="default/MediatorTest!1.0*soa_58b98be8-9ec8-41af-bb83-590f6004d1aa" deployedTime="2011-11-17T09:01:54.750+05:30"/>
8. Now run the below command by changing the "fromLocation" (this should be the same location as previous)
importMetadata(application='ShareSoaInfraPartition',server='AdminServer',fromLocation='/fmw11g/fmw1115/Middleware',docs='/deployed-composites/deployed-composites.xml')
9. Now bounce your server and the composite will not be deployed by SOA when it comes up and hence that should bring your soa-infra up.
No comments:
Post a Comment