In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service.
One issue in deploying from DevCS is the firewall and proxy.
First, the proxy information must be specified on the command line. DevCS exports HTTP_PROXY_HOST and HTTP_PROXY_PORT on the shell environment and specifies the proxy information in the settings.xml, but the Maven plugin does not seem to care about these values. The values it does care about is "http.proxyHost" and "http.proxyPort". It is easy enough to set these values in the Hudson "Properties" text field:
Another issue is that the SOA Unit Test framework relies on JMX to talk to the MBeans. This non-http traffic is stopped by the firewall. You can control the protocol used with the following property:
By default, this value equals soaServerDeployProtocol. Changing the test protocol (or using http/https as the deploy protocol) is only half the battle. My thoughts on this may be wrong, but my theory is that the WebLogic server by default is not configured to allow tunneling over http. You must change the WebLogic server's configuration to allow this per the video.
This, however, is not a good practice in general. A better solution would be to use the Compute Cloud's Network console to open TCP/TCPS traffic on the necessary ports for only the required IP addresses (e.g., DevCS). That is a more advanced topic.
Finally, I have found in many cases that the firewall blocks binary payloads when using http. Routing and traffic shaping rules as well as firewall and proxy configurations have changed since this video was created, so it is quite likely that you will not be able to reproduce my results using only http. The next chapter should resolve this by using https.