Apex Code Development You need to sign in to do that
Don't have an account?
Frank Chang SFDC endpoint url via api - what's the correct url?
I've inherited a salesforce org that has a few custom integrations (java) set up. This integration is replicated in a sandbox environment as well. Everything was working just fine, until this past week when we did a refresh of our sandbox. With a refresh, our org Id's, server number, and other important Id's are now completely different.
Now, our custom integrations for our sandbox are all broken. I'm desperatley trying to figure out what needs to be updated in order to make the integrations work again. I can see from the logs that the user we've designated as the one to log in from the integration jobs, is able to log in, so it's not a permissions issue.
I'm guessing that the issue could be the api endpoint url. Our old url is as follows:
sfdc.endpoint=https://cs17-api.salesforce.com/services/Soap/c/22.0/00DR00000008Yb5/0DF60000000PM7i
First of all, I know that the server machine is no longer cs17, and that the org Id (first Id value after the api version number) is no longer valid. I've replaced these with the correct server and org id value. My question is, what is the (second and) last Id value? I can't seem to find anything on this second Id. I'd imagine that the refresh would wipe out the value here and a new value would be needed.
My second question is, can I use something more generic, such as? :
sfdc.endpoint=https://test.salesforce.com/services/Soap/c/22.0/OrgID
Please help! I really need to get our sandbox integration working again so that I can adequately develop the new features we need! Without the integration in place, I'm not able to do so!
Thanks in advance,
Frank
Now, our custom integrations for our sandbox are all broken. I'm desperatley trying to figure out what needs to be updated in order to make the integrations work again. I can see from the logs that the user we've designated as the one to log in from the integration jobs, is able to log in, so it's not a permissions issue.
I'm guessing that the issue could be the api endpoint url. Our old url is as follows:
sfdc.endpoint=https://cs17-api.salesforce.com/services/Soap/c/22.0/00DR00000008Yb5/0DF60000000PM7i
First of all, I know that the server machine is no longer cs17, and that the org Id (first Id value after the api version number) is no longer valid. I've replaced these with the correct server and org id value. My question is, what is the (second and) last Id value? I can't seem to find anything on this second Id. I'd imagine that the refresh would wipe out the value here and a new value would be needed.
My second question is, can I use something more generic, such as? :
sfdc.endpoint=https://test.salesforce.com/services/Soap/c/22.0/OrgID
Please help! I really need to get our sandbox integration working again so that I can adequately develop the new features we need! Without the integration in place, I'm not able to do so!
Thanks in advance,
Frank
Just a guess since i'm not sure how does your sandbox looks like. From Setup-->API-->Generate Enterprise WSDL--> Generate WSDL. In the end you can find your valid SOAP EndPoint.
Mine looks like this.
<soap:address location="https://test.salesforce.com/services/Soap/c/31.0/ORGID"/>
Using this Endpoint give a try with the appropirate credentails. If the User is also active from which you are trying to access.
When you refresh from sandbox, you'll also need to watch out for usernames changing. The usernames will change to user@domain.sandboxsuffix. You're stating it works, but just a heads up that it could cause issues as well.
Also, have you tried using soapui to test out your sandbox integrations (http://www.soapui.org/)? If available, download the WSDLs of the services your integrations use, and pop them into soapui. Often times, it's easier to debug connection issues than kicking off your Java processes, for instance.