I have a question relating to outbound messages. It is not directly associated with APEX, however I could not find an appropriate section to log it under.
The situation is as follows: 1.) We have a data loading process that loads hundreds of thousands of records into an Unlimited org 2.) For this entity we have an outbound message that is processed on the other end by a .NET Web Service listener.
However, we are noticing that the queue just keeps increased, and the old items are not actually consumed by the Web Service Listener. Is there a cap on the number of outbound messages that can be processed by SFDC at one time? We have checked the IIS and it seems that it can handle large volume of requests, so we are skeptical that IIS is the cause.
Does the SFDC outbound message queue work by batching up outbound messages, or does it directly execute them as soon as it encounters them?
I was wondering if anybody knows how to query for the picklist sort order values. Is there an API call that will return the sort order for a specific picklist ? I can't seem to find anything on the documentation about the sort order.
Can one set up an "outbound message" into Salesforce to trigger a message to our web service when an DELETE occurs for an object ? It seems to be working fine with Create and Updates for me, but nothing for Delete. This is without using Apex code.
I have a question relating to outbound messages. It is not directly associated with APEX, however I could not find an appropriate section to log it under.
The situation is as follows: 1.) We have a data loading process that loads hundreds of thousands of records into an Unlimited org 2.) For this entity we have an outbound message that is processed on the other end by a .NET Web Service listener.
However, we are noticing that the queue just keeps increased, and the old items are not actually consumed by the Web Service Listener. Is there a cap on the number of outbound messages that can be processed by SFDC at one time? We have checked the IIS and it seems that it can handle large volume of requests, so we are skeptical that IIS is the cause.
Does the SFDC outbound message queue work by batching up outbound messages, or does it directly execute them as soon as it encounters them?
Looking at the Summer '08 Apex dev guide re setting up two-way SSL in WebSvc callouts. The instructions are as follows (pp. 144-146 of the guide):
Set up your Web server to request the SSL client certificate.
Generate a PKCS12 key store with your client certificate.
Verify that the server's trust keystore contains/accepts your client certificate
Encode your client certificate keystore in base64 and assign it to a variable on the stub (in this case, clientCert_x).
Steps 1 thru 3 are done on the web server (the callout endpoint), is that correct?
Step 4 is the key one. There's an example in the doc right after these steps, that purports to work with the sample WSDL file shown a page or two further down. The example refers to two stub variables: 'clientCert_x' (as in the instructions) and 'clientCertPasswd_x'. These are nowhere to be found in the sample WSDL nor its derived Apex stub class.
Presumably these variables, minus the '_x' suffixes, need to appear in the WSDL from the WebSvc endpoint as header variables, is that correct? Is this something that falls naturally out of the first three steps above (plus a re-generation of the WSDL itself)? You can't just go in and modify the stub class and add these variables manually, surely, as they will have no meaning to whatever consumes the class.
Thanks! Would like to hit the ground running on this, when Summer '08 makes its production debut.
I have a question relating to outbound messages. It is not directly associated with APEX, however I could not find an appropriate section to log it under.
The situation is as follows: 1.) We have a data loading process that loads hundreds of thousands of records into an Unlimited org 2.) For this entity we have an outbound message that is processed on the other end by a .NET Web Service listener.
However, we are noticing that the queue just keeps increased, and the old items are not actually consumed by the Web Service Listener. Is there a cap on the number of outbound messages that can be processed by SFDC at one time? We have checked the IIS and it seems that it can handle large volume of requests, so we are skeptical that IIS is the cause.
Does the SFDC outbound message queue work by batching up outbound messages, or does it directly execute them as soon as it encounters them?
