Salesforce Developer Community

<—xml version="1.0" encoding="utf-8"–>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://tempuri.org/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
  <wsdl:types>
    <s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/">
      <s:element name="SForceLogin">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="UID" type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="Pwd" type="s:string" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:element name="SForceLoginResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="SForceLoginResult" type="s:string" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:element name="Query">
        <s:complexType />
      </s:element>
      <s:element name="QueryResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="QueryResult" type="s:string" />
          </s:sequence>
        </s:complexType>
      </s:element>
    </s:schema>
  </wsdl:types>
  <wsdl:message name="SForceLoginSoapIn">
    <wsdl:part name="parameters" element="tns:SForceLogin" />
  </wsdl:message>
  <wsdl:message name="SForceLoginSoapOut">
    <wsdl:part name="parameters" element="tns:SForceLoginResponse" />
  </wsdl:message>
  <wsdl:message name="QuerySoapIn">
    <wsdl:part name="parameters" element="tns:Query" />
  </wsdl:message>
  <wsdl:message name="QuerySoapOut">
    <wsdl:part name="parameters" element="tns:QueryResponse" />
  </wsdl:message>
  <wsdl:portType name="ServiceSoap">
    <wsdl:operation name="SForceLogin">
      <wsdl:input message="tns:SForceLoginSoapIn" />
      <wsdl:output message="tns:SForceLoginSoapOut" />
    </wsdl:operation>
    <wsdl:operation name="Query">
      <wsdl:input message="tns:QuerySoapIn" />
      <wsdl:output message="tns:QuerySoapOut" />
    </wsdl:operation>
  </wsdl:portType>
  <wsdl:binding name="ServiceSoap" type="tns:ServiceSoap">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
    <wsdl:operation name="SForceLogin">
      <soap:operation soapAction="http://tempuri.org/SForceLogin" style="document" />
      <wsdl:input>
        <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="Query">
      <soap:operation soapAction="http://tempuri.org/Query" style="document" />
      <wsdl:input>
        <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
  </wsdl:binding>
  <wsdl:binding name="ServiceSoap12" type="tns:ServiceSoap">
    <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
    <wsdl:operation name="SForceLogin">
      <soap12:operation soapAction="http://tempuri.org/SForceLogin" style="document" />
      <wsdl:input>
        <soap12:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap12:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="Query">
      <soap12:operation soapAction="http://tempuri.org/Query" style="document" />
      <wsdl:input>
        <soap12:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap12:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
  </wsdl:binding>
  <wsdl:service name="Service">
    <wsdl:port name="ServiceSoap" binding="tns:ServiceSoap">
      <soap:address location="http://localhost:1908/Salesforce_Origination/Service.asmx" />
    </wsdl:port>
    <wsdl:port name="ServiceSoap12" binding="tns:ServiceSoap12">
      <soap12:address location="http://localhost:1908/Salesforce_Origination/Service.asmx" />
    </wsdl:port>
  </wsdl:service>
</wsdl:definitions>

Steven2005A
December 12, 2008
Like
0

1 replies

How to talk to WebService from Salesforce? Please Help

How to invoke VB.Net 2.0 WebService functions once some data are saved/Entered to SalesForce?

any samples? what function I need to use?

Steven2005A
December 10, 2008
Like
0

2 replies

Urgent! Please Help! WebService and SQL related.

I am totally new to this

My boss ask me to develop a webservice in VB.Net 2.0

to Query data from Salesforce and save it to Sql server

but How to do it?

I created a webservice, but how to talk to salesforce and get the data, should I login first?

and what dlls do I need to use the built in functions? any samples to walkthough?

Thanks

Please Help

Steven2005A
December 09, 2008
Like
0

2 replies

webservice help

I have a webservice located on my local for testing http://localhost:2114/WS_ClientOrigination/Service.asmx

how to make salesforce to call a function GetID() in this webservice?

Steven2005A
December 23, 2008
Like
0

2 replies

what should be the Endpoint URL in the Outbound Messaging?

I am totally new to this

Steven2005A
December 16, 2008
Like
0

SOLVED

6 replies

Failed to parse wsdl: Found more than one wsdl:binding. WSDL with multiple binding not supported

I don't know what is wrong with this wsdl? when I click Parse WSDL, it gives that error message, can anyone help me fix the file?

Thanks

the original code is posted below

Code:

<—xml version="1.0" encoding="utf-8"–>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://tempuri.org/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
  <wsdl:types>
    <s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/">
      <s:element name="SForceLogin">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="UID" type="s:string" />
            <s:element minOccurs="0" maxOccurs="1" name="Pwd" type="s:string" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:element name="SForceLoginResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="SForceLoginResult" type="s:string" />
          </s:sequence>
        </s:complexType>
      </s:element>
      <s:element name="Query">
        <s:complexType />
      </s:element>
      <s:element name="QueryResponse">
        <s:complexType>
          <s:sequence>
            <s:element minOccurs="0" maxOccurs="1" name="QueryResult" type="s:string" />
          </s:sequence>
        </s:complexType>
      </s:element>
    </s:schema>
  </wsdl:types>
  <wsdl:message name="SForceLoginSoapIn">
    <wsdl:part name="parameters" element="tns:SForceLogin" />
  </wsdl:message>
  <wsdl:message name="SForceLoginSoapOut">
    <wsdl:part name="parameters" element="tns:SForceLoginResponse" />
  </wsdl:message>
  <wsdl:message name="QuerySoapIn">
    <wsdl:part name="parameters" element="tns:Query" />
  </wsdl:message>
  <wsdl:message name="QuerySoapOut">
    <wsdl:part name="parameters" element="tns:QueryResponse" />
  </wsdl:message>
  <wsdl:portType name="ServiceSoap">
    <wsdl:operation name="SForceLogin">
      <wsdl:input message="tns:SForceLoginSoapIn" />
      <wsdl:output message="tns:SForceLoginSoapOut" />
    </wsdl:operation>
    <wsdl:operation name="Query">
      <wsdl:input message="tns:QuerySoapIn" />
      <wsdl:output message="tns:QuerySoapOut" />
    </wsdl:operation>
  </wsdl:portType>
  <wsdl:binding name="ServiceSoap" type="tns:ServiceSoap">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
    <wsdl:operation name="SForceLogin">
      <soap:operation soapAction="http://tempuri.org/SForceLogin" style="document" />
      <wsdl:input>
        <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="Query">
      <soap:operation soapAction="http://tempuri.org/Query" style="document" />
      <wsdl:input>
        <soap:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
  </wsdl:binding>
  <wsdl:binding name="ServiceSoap12" type="tns:ServiceSoap">
    <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
    <wsdl:operation name="SForceLogin">
      <soap12:operation soapAction="http://tempuri.org/SForceLogin" style="document" />
      <wsdl:input>
        <soap12:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap12:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="Query">
      <soap12:operation soapAction="http://tempuri.org/Query" style="document" />
      <wsdl:input>
        <soap12:body use="literal" />
      </wsdl:input>
      <wsdl:output>
        <soap12:body use="literal" />
      </wsdl:output>
    </wsdl:operation>
  </wsdl:binding>
  <wsdl:service name="Service">
    <wsdl:port name="ServiceSoap" binding="tns:ServiceSoap">
      <soap:address location="http://localhost:1908/Salesforce_Origination/Service.asmx" />
    </wsdl:port>
    <wsdl:port name="ServiceSoap12" binding="tns:ServiceSoap12">
      <soap12:address location="http://localhost:1908/Salesforce_Origination/Service.asmx" />
    </wsdl:port>
  </wsdl:service>
</wsdl:definitions>

Steven2005A
December 12, 2008
Like
0

2 replies

Urgent! Please Help! WebService and SQL related.

I am totally new to this

My boss ask me to develop a webservice in VB.Net 2.0

to Query data from Salesforce and save it to Sql server

but How to do it?

I created a webservice, but how to talk to salesforce and get the data, should I login first?

and what dlls do I need to use the built in functions? any samples to walkthough?

Thanks

Please Help

Steven2005A
December 09, 2008
Like
0

4 replies

.NET Web Service response exceeds 100KB size

Hi,

I have an Apex class that communicates with a .NET Web Service. The Web Service response is exceeding 100 KB. Is there a work around to this 100 KB limit?

trish
December 01, 2008
Like
0

4 replies

Making SQL database connections from APEX code

Hi,

I'm just wondering does anyone know if it's possible to make connections to external database servers such as MS SQL Server or MySQL from Apex code. If so, how would one go about this?

Thanks

kmchale
November 24, 2008
Like
0

9 replies

Hi Everyone,

I'm new to Salesforce development and I hope this is the proper place to post my question, if not please let me know and I'll post accordingly.

Does anyone know how I can connect to my salesforce instance with SQL server. I'm currently trying to figure out how we can do custom analystics using MS SQL Analysis Services and I would like to be able to pull in all of our salesforce data. The specific tools i'm using are SSIS (SQL Server Integration Services) with Business development studio. Further, I thought I might be able to connect to the salesforce web service using the web services event within SSIS and it appears with template supports very few web services outside of the microsoft world.

Any help greatly appreciate!, Thanks.

-mike

TuckermanRav
July 16, 2008
Like
0

10 replies

A detail example of building a Listener in asp.net C#..

Hi Guys,

I am having issues with the listener that I am building rite now..

I have follow the AppExchange Developer Network Help File on building the Listener as follow...

but when come to INotificationBinding.. I am lost..

Can anyone show me a detail example.

Best Regards,

Nigil Chua

Once you have defined an outbound message and configured an outbound messaging endpoint, download the WSDL and create a listener:

Right-click Click for WSDL and select Save As to save the WSDL to a local directory with an appropriate filename. For example, for an outbound message that deals with leads, you could name the WSDL file leads.wsdl.
Unlike the enterprise or partner WSDLs, which describe the messages the client sends to Salesforce, this WSDL defines the messages that Salesforce will send to your client application.
Most web services tools will generate stub listeners for you, in much the same way as they generate a client stub for the enterprise or partner WSDL. Look for a server side stub option.
For example, for .Net 2.0:
1. Run wsdl.exe /serverInterfaceleads.wsdl with .Net 2.0. This generates NotificationServiceInterfaces.cs, which defines the notification interface.
2. Create a class that implements NotificationServiceInterfaces.cs.
3. You implement your listener by writing a class that implements this interface. There are a number of ways to do this. One simple way is to compile the interface to a DLL first (DLLs need to be in the bin directory in ASP.NET:
```
mkdir bin
csc /t:library /out:bin\nsi.dll NotificationServiceInterfaces.cs      
```
  Now write an ASMX based web service that implements this interface. For example, in MyNotificationListener.asmx:
```
        <%@WebService class="MyNotificationListener" language="C#"%>
         class MyNotificationListener : INotificationBinding
         {            public notificationsResponse notifications(notifications n)
                      {
                             notificationsResponse r = new notificationsResponse();
                             r.Ack = true;
                             return r;
                       }
         }
```
  This example is a simple implementation, actual implementations will be more complex.
4. Deploy the service by creating a new virtual directory in IIS for the directory that contains the MyNotificationListener.asmx.
5. You can now test that the service is deployed by viewing the service page with a browser. For example, if you create a virtual directory salesforce, you'd go to http://localhost/salesforce/MyNotificationListener.asmx.
The process for other web service tools is similar, please consult the documentation for your web service tool. For Axis, we recommend version 1.1 or later.

Your listener must meet these requirements:

Must be reachable from the public Internet.
If you use SSL, you must use port 443, and you must have a real certificate. If you certificate expires, message delivery will fail.

Nigil
May 21, 2007
Like
0