Sometimes we might not be able to undeploy or redeploy composites from the EM console.This can happen when the project is not loaded properly during server startup.In such cases the composite can be undeployed using WLST script.
Run the WLST script in the below location:
$ORACLE_HOME/common/bin/
Running the wlst script in the server path can result in NameError when SOA specific commands are run.
Traceback (innermost last): File “”, 1,=”" ?<=”" in=”" line=”" span=”">”,> NameError: sca_undeployComposite
Run the WLST script in the below location:
$ORACLE_HOME/common/bin/
Running the wlst script in the server path can result in NameError when SOA specific commands are run.
Traceback (innermost last): File “”, 1,=”" ?<=”" in=”" line=”" span=”">”,> NameError: sca_undeployComposite
wls:/offline>
wls:/offline> connect()
Please enter your username :weblogic
Please enter your password :
Please enter your server URL [t3://localhost:7001] :t3://soahost:8001
Connecting to t3://soahost:8001 with userid weblogic ...
Successfully connected to managed Server 'wls_soa1' that belongs to domain 'soa_domain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
wls:/soa_domain/serverConfig> sca_undeployComposite("http://soahost:8001", "SOAExp", "1.0",user='weblogic', password='*******', partition='test')
serverURL = http://soahost:8001
user = weblogic
partition = test
compositeName = SOAExp
revision = 1.0
timeout= -1
set user and password...
compositeDN = test/SOAExp!1.0
INFO: Creating HTTP connection to host:soahost, port:8001
INFO: Received HTTP response from the server, response code=200
If the SOA server is running with a virtual ip then the corresponding host name or VIP need to be used while connecting to the server.
Undeploying SOA Composite while soa-infra is down.
Mainly this task is required when starting a soa server and the soa-infra application won't come up due to a corrupt composite. The solution also applies in the case where the server itself is failing to come up / stay up due to a bad deployment.
Follow the below document from Oracle support.
