The first and foremost step is to configure the Weblogic/ Oracle SOA domain to access remote Salesforce services.
For SOA composites deployed on Oracle 11g version 11.1.1.3, to consume web services the following changes need to be made to the setSOADomainEnv.sh on Linux OR setSOADomainEnv.cmd file. This section will discuss the Linux deployments only.
The setSOADomainEnv.sh can be found in the directory $WL_HOME/user_projects/domains/base_domain/bin.
The EXTRA_JAVA_PROPERTIES variables needs to be modified as follows
The setSOADomainEnv.sh can be found in the directory $WL_HOME/user_projects/domains/base_domain/bin.
The EXTRA_JAVA_PROPERTIES variables needs to be modified as follows
EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -Dhttps.proxySet=true -Dhttps.proxyHost=localdomain.com -Dhttps.proxyPort=443 -Dhttp.nonProxyHosts=localhost.localdomain|127.0.0.1|192.168.1.7"
export EXTRA_JAVA_PROPERTIES
https.proxyHost: Your proxy Host
https.proxyPort: Your proxy port, 443 is the default port for https
http.nonProxyHosts: Your non proxy servers, the list can be separated with a "|"
The second most significant step is to install and configure the https://login.salesforce.com certificates
Download the certificates from https://login.salesforce.com and import the certificates using the
Java Keytool
keytool -importcert -alias login.salesforce.com -file login.salesforce.com -keystore mykeysotre.jks
Configure the jks in the setSOADomain.sh.
After the changes have been made, restart the Admin Weblogic Server and Managed SOA Server.
For questions, comments and feedback please contact:
Harvinder Singh Saluja