Common Oracle JDeveloper Deployment Issues

This section provides a list of common deployment issues to check.

If you are deploying a single composite application, ensure that you are deploying from the Project menu. Right-click the project name in the Applications window, and select Deploy > SOA_profile_name.
If you are deploying multiple composite applications, ensure that you are deploying from the Application menu. (Right-click the application name in the Applications window, and select Deploy > SOA_bundle_profile_name).
Once you click Deploy and select the profile name, ensure that the Deployment Action page of the deployment wizard is displayed.
Optionally enter a new revision ID (optional) and select the configuration plan (if any).
If the composite application you are deploying is already located on the server with the same revision ID, then check the Overwrite any existing composites with the same revision ID check box in the Deploy Configuration page of the deployment wizard. Without selecting this option, deployment fails.
If compilation fails, a compiler error occurred, and not a deployment error. You only see this error when you compile your project.
If compiler messages are not obvious, check the compiler log. A link to this log file (scac.log) is displayed in the Messages tab. The message looks similar to that shown in the following example.
```
Compilation of project 'FirstComposite.jpr' finished. Check '/scratch/myhome/
jdevWorkarea/mywork/Application11/FirstComposite/SCA-INF/classes/scac.log' for
details.
```

After compilation is successful, a SAR/SOA bundle archive is built for the composite. For a SAR archive, the message shown in the following example is displayed in the Deployment tab.

Wrote Archive Module to
/scratch/myhome/jdevWorkarea/mywork/Application11/FirstComposite/deploy/sca_
FirstComposite_rev1.0.jar

For a SOA bundle archive, the message shown in the following example is displayed in the Deployment tab.

Wrote Archive Module to
/scratch/myhome/jdevWorkarea/mywork/Application11/SecondComposite/deploy/sca_
SecondComposite_rev1.0.jar
Wrote Archive Module to
/scratch/myhome/jdevWorkarea/mywork/Application11/FirstComposite/deploy/sca_
FirstComposite_rev1.0.jar
Wrote Archive Module to
/scratch/myhome/jdevWorkarea/mywork/Application11/deploy/soabundle1.zip

Ensure that all SAR file URLs look as follows:
```
sca_CompositeName_revRevisionID.jar
```
For example, sca_FirstComposite_rev1.0.jar.
After this occurs, Oracle JDeveloper sends the archive binaries to the server. The following message is displayed in the Deployment tab. At this point, Oracle JDeveloper's deployment role ends and the server (SOA Infrastructure) takes control of deployment.
```
Deploying sca_FirstComposite_rev1.0.jar to myhost19:7001
```

Upon successful deployment, you see the message shown in the following example in the Deployment tab.

Received HTTP response from the server, response code=200 Successfully deployed
archive soa_bundle_name.zip to soa_server_name

If deployment fails, the message shown in the following example is displayed in the Deployment tab with an error message (if any) from the server.
```
Error deploying the archive. Check server log for more details.
Connection refused.
Elapsed time for deployment: 8 seconds
```
In most cases, the server provides some information about the error that occurred on the server. If you do not receive any error message from the server, then check soa_server1-diagnostic.log on the server to find additional information (where soa_server1 is the name of the managed server). This file is located on the server in domain_home/servers/soa_server1/logs.