I am using Appian v7.5. I am getting the following error when trying to call a w

...ocal!wsNameSpace & "AddMerchant",
port: "DGConfigAdminWebServiceSoap12",
wsdlCredentials: local!wsCredentials,
invocationCredentials: local!wsCredentials
),
{
AddMerchantSoapIn: {
rule!BW_CMPO_EDS_getMerchantObj()
}
}
),
local!actualWSResponse
)

If you're not in 7.6 with all hotfixes then try this:

with(
local!wsCredentials: a!wsHttpCredentials(
username: "sakruv01",
password: "abcd1234"
),
local!wsNameSpace: "{schemas.afsimage.com/.../configadminservice}",
local!actualWSResponse: webservicequery(
           type!WsConfig(
           wsdlUrl: "lab53ctx123vm:8080/.../DGConfigAdminWebService.asmx
           service: local!wsNameSpace & "DGConfigAdminWebService",
           port: "DGConfigAdminWebServiceSoap12",
           operation: local!wsNameSpace & "AddMerchant",
           wsdlCredentials: a!wsHttpCredentials("sakruv01","abcd1234",null),
           endpointCredentials: local!wsCredentials
           ),
{
AddMerchantSoapIn: {
rule!BW_CMPO_EDS_getMerchantObj()
}
}
),
local!actualWSResponse
)

Please copy and paste my code and test. Do not modify.

Edurado, you are the man. Now I am past authentication error, but got 401. Do you know what is this 401 means ?

just got the following from "en.wikipedia.org/.../List_of_HTTP_status_codes"
401 Unauthorized - so at least authentication is passed. Thanks a lot.

Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource

!!! who would guess that using keynames like username, password, domain are not recommended for a!wsHttpCredentials function !!!

Is it working fine now?

I would say yes - because the original problem is gone now. I may have to use a specific header custom to the external web service I am trying to use.

I just want to clarify what I changed. This is the relevant part that I updated. Notice how I am directly using the type!WsConfig which has a property called endpointCredentials. This is because there's a bug before 7.6 where if using !WsConfig the endpointCredentials attribute of type!WsConfig won't be mapped because the a!WsConfig is trying to map the values to invocationCredentials instead of endpointCredentials. This is resolved in Appian 7.6 all hotfixes where you can now use a!WsConfig.

type!WsConfig(
           wsdlUrl: "lab53ctx123vm:8080/.../DGConfigAdminWebService.asmx
           service: local!wsNameSpace & "DGConfigAdminWebService",
           port: "DGConfigAdminWebServiceSoap12",
           operation: local!wsNameSpace & "AddMerchant",
           wsdlCredentials: a!wsHttpCredentials("sakruv01","abcd1234",null),
           endpointCredentials: local!wsCredentials
           )

Eduardo, I am able to go past authentication and now I am getting the following error:
"Can not serialize OM Element Fault" any help ?