Efficy Overflow Q&A - Recent questions tagged openurl

When is OpenUrl.log generated ?

Wed, 07 Aug 2024 08:33:44 +0000

From the content of OpenUrl.log it looks like it contains the calls to external services + the post payload.
I suppose it is related to one of Efficy.openUrl... methods but I am not quite sure.
The issues is more on log file that is generated in PROD env. but not in TST env.

I'd like to understand:

When it usually created ?
Why it behaves differently ?

The client (on-premise) noticed a peak of space usage since few weeks (it wasn't like that before apparently ). UpenUrl.log takes over 600mb each day. Most of them are related to sending personalised emails (flexmail) from campaign. And the flexmail playload take huge space.

Problem with request to external webservice with TLS 1.2

Wed, 10 Jul 2019 09:31:36 +0000

Hi,

for a customer we've made a connection with a external webservice. This external party is migrating their service so that it's going to use TLS 1.2. We are testing this but we encounter a problem when we make a request to that external webservice which is using TLS 1.2. We receive the following error:

Cannot find web server "xxxxx.xxxxxx.xx"
Error Code: 12044
ErrorContext
=============================     
EEfficyException 0
(LIBS-1690) Cannot find web server "xxxxx.xxxxxx.xx"
Error Code: 12044
Error
=============================     
ESlspException 0
Application Server Error

I'm using the following code to make the request:

var soapResponse = efficy.OpenURL2(this.options.Url + apiCommandUrl, soapText, this.soapHeaders);

Does anyone know how I can solve this?

Best regards,
Jeroen

Authentication error using openURL

Fri, 25 Jan 2019 14:44:24 +0000

Hello,

I am having a problem with soap requests being sent to a webservice designed to synchronise efficy changes with another system ( Navision ).
The client has upgraded the version of Navision and this is now located on a different server. Efficy version is 2014.

These webservices worked with the old version, but now there seems to be a problem.

The soap requests are triggered in the workflow ( you will find the code below ). After some digging, i found that the request was sending back an HTTP 401 status.
It seems that the authentication is now different than it was before.

The client thinks the new version of Navision does'nt support basic authentication anymore, and that NTLM is now required.

The soap-request itself is correct, i managed to get a result using SoapUI ( see screenshot ), but this seems to use the NTLM protocol.
I used the authentication utility in soapUI for this. ( adding the headers manually doesn't work ).

Could this mean we cannot use openURL to connect anymore? Does it only use basic authentication?

Any suggestions are welcome.

var oldURL = "http://hostname/DynamicsNAV90/WS/Dialog/Page/Integratie_Contact_Card";
var URL = "http://hostname/Dialog/WS/Dialog%20LIVE/Page/Integratie_Contact_Card";   
    var RequestHeader = TStringList.Create;
    try {
        RequestHeader.Add('POST /Dialog/WS/Dialog/Page/Integratie_Contact_Card HTTP/1.1');
        RequestHeader.Add('SOAPAction: urn:microsoft-dynamics-schemas/page/integratie_contact_card:Read');
        RequestHeader.Add('EffNtlmLogin: ...');
        RequestHeader.Add('EffNtlmPassword: ...');
               RequestHeader.Add('Content-Type: text/xml; charset=utf-8');
        var requestContent = '<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:int="urn:microsoft-dynamics- 
               schemas/page/integratie_contact_card">';
            requestContent += '<soapenv:Header/>';
                requestContent += '<soapenv:Body>';
                    requestContent += '<int:Read>';
                        requestContent += '<int:GTex_CustAddr></int:GTex_CustAddr>';
                        requestContent += '<int:No>' + navNumber + '</int:No>';
                    requestContent += '</int:Read>';
                requestContent += '</soapenv:Body>';
            requestContent += '</soapenv:Envelope>';

        var response = Database.OpenURL2(URL, requestContent, RequestHeader.text);

        navKey = GetTagValue(response, "Key");
        if (navKey == ""){
            Logger.Write("Reading: Company reading with ID: " + compKey + " failed. Response was: " + response);
        }       
} finally {
        RequestHeader.Free;
}

Is it possible to do HTML1.1 PUT operation with OpenURL2?

Mon, 12 Sep 2016 07:14:45 +0000

Dear All,

For a customer, I have to use an external WebService through a Workflow script.

For the creation I used "POST" operation and "GET" operation for retrieving data from the webservices. and this is working fine with Database.OpenURL2 operation.

For updating data through the webserivce I have to use a "PUT" operation, but I got an error saying I am not using a PUT operation but a POST operation instead when using Database.OpenURL2.

Does anyone knows how I could create a PUT call ?