1. Administering Oracle SOA Cloud Service in a Customer-Managed Environment
  2. Get Started with Oracle SOA Cloud Service
  3. About the Cloud Adapter Pack

About the Cloud Adapter Pack

Cloud adapters simplify and accelerate integration between SaaS applications, and between on-premises applications and SaaS applications. These adapters provide lower costs of implementation and maintenance, ease of use, improved developer productivity and faster time-to-market for Saas application integrations. The cloud adapters are automatically included with Oracle SOA Cloud Service.

Topics

Add a Managed Server IP in a Non Proxy Host to Enable Deployment From Fusion Middleware Control

If you use the cloud adapter pack, before you can use Fusion Middleware Control to deploy applications, you must add a managed server IP in to a non proxy host.

The following steps describe how to add a managed server IP to a non proxy host.
  1. Log in to Fusion Middleware Control.
  2. Find the server in the Target Navigation pane.
  3. Right-click the server and select Administration > System MBean Browser.
    Screenshot that shows the result of right clicking the server. It exposes the Administration, and System MBean Browser items.
  4. Search for the getURL operation.
    1. Click the binocular icon.
    2. Select Operations.
    3. Type “getURL”
    4. Click the arrow button to start the search.
      Screenshot that shows the objects referred to in the four steps above.
  5. Click getURL.
    Screenshot shows the getURL attribute as seventh in the list.
  6. Type http in the Value field and then click Invoke.
    Screenshot illustrates the items referred to in the previous step.
  7. Follow the instructions in Configuring the Proxy Server for Runtime in Oracle Cloud Adapters Postinstallation Configuration Guide 12.2.1.3/12.2.1.2/12.1.3 to update the setDomainEnv.sh file.
    You must invoke getURL operation for all the MBeans found (each MBean maps to a managed server in the cluster). Note all the IPs and update the non proxy hosts in setDomainEnv.sh and you can include the host IP address explicitly as shown in the following:
     -Dhttp.proxyHost=www-proxy.my.url.com -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts=localhost|*.my.url.com|*.internal| 127.0.0.1|10.196.75.214|10.*.*.*|*.foo.com|etc -Dhttps.proxyHost=www-proxy.my.url.com -Dhttps.proxyPort=80

    You must restart the servers (both administration and managed) for this settings to take effect.