Database Reference
In-Depth Information
Common deployment issues
Deployment issues have their own set of challenges. In some cases, the error is
quite obvious:
deploy:
[input] skipping input as property serverURL has already been set.
[input] skipping input as property sarLocation has already been set.
[deployComposite] setting user/password..., user=welcome1
[deployComposite] Processing sar=/u01/svn/HelloWorld/deploy/sca_HelloWorld_rev1.0.jar
[deployComposite] Adding sar file - /u01/svn/HelloWorld/deploy/sca_HelloWorld_rev1.0.jar
[deployComposite] INFO: Creating HTTP connection to host:soahost1, port:8001
[deployComposite]
java.net.UnknownHostException: soahost1
In other cases, it is more difficult. Consider the common error shown in the fol-
lowing snippet that you may face during composite deployment:
<Error> <oracle.integration.platform> <SOA-20003> <Unable to register service. oracle.fabric.common.FabricException: Error in getting XML input stream: http://soahost1:8001/soa-infra/services/default/QueryOrder?WSDL:
Response: '503: Service Unavailable' for url:
This is a common deployment error that you are almost certain to encounter
either when you are deploying a composite or when the composite is trying to
register external references during server startup. However, you might find your-
self in a fix when the same error keeps recurring, even when the reference ser-
vice is available. What can you make of errors like these? Firstly, let's under-
stand what happens here. When you start an SOA server or deploy a composite,
the engine tries to activate the composite by trying to register with all its end-
points. If unsuccessful, the composite is marked as
inactive
.
As the cause of a composite becoming inactive when a target service is down,
the errors in this case can be prevented in the following two ways:
•
From Oracle Enterprise Manager Fusion Middleware Control, navigate to the
composite dashboard and reactivate the composite. The composite will now
