Showing posts with label SFDC connectivity. Show all posts
Showing posts with label SFDC connectivity. Show all posts

Sunday, August 17, 2008

How to enable the proxy server settings in Oracle SOA suite

In one of our POC’s we had issues connecting to the SFDC server because of the company firewall and proxy settings. One of our integration consultants suggested us to use the following settings

Open the following file: ORACLE_HOME/opmn/conf/opmn.xml

  1. Find the process-type id whose value is the name of the instance which we are using for our development. This may be "home", or it could be another instance name.
  1. Under the required process-type id select the data id="java-options" in the category id="start-parameters" section of the file.
  1. Add the following parameters under java-options:

Dhttp.proxySet = true

Dhttp.proxyHost = proxy_server

Dhttp.proxyPort = listen_port

Dhttp.nonproxyHost = host_name

Parameter Settings for Oracle WSM Installed as Part of Oracle Application Server

Parameter Value


Description of Value

true/false


The value true enables the proxy server.

proxy_server


Name of the proxy server. For example, www-proxy.us.oracle.com.

listen_port


The port number on the proxy server where you wish to connect. For example, 80

host_name


Hosts that connect directly without intervention from the proxy server. This value can be a list of host names separated by a vertical bar (|) or an asterisk (*). For example, localhost|*oracle.com

  1. Restart the server for the configuration changes to take effect.

Thanks Ramesh for your inputs

Friday, August 15, 2008

limitations of WSDL in SFDC

In one of our projects for connectivity with SFDC(SalesForcedotCom) we had some issues calling the webservices @SFDC.One of our SFDC expert Omkar helped us with the following details regarding the limitations of WSDl in SFDC

The limitations of WSDL in SFDC are listed below.So please take care of these known issues while trying to call webservices or viceversa .APEX is the language used inside SFDC for creating webservices and embedding logic in it.

Apex does not support any other WSDL constructs, types, or services, including:
• RPC/encoded services
• WSDL files with multiple porTypes, multiple services, or multiple bindings
• WSDL files with imports
• Any schema types not documented in the previous table
• WSDLs that exceed the size limit, including the Salesforce WSDLs

Hope this helps