Re: Creating Succesfactors Logical Port via WSDL

We have now fixed the Peer certificate but running into other problems:

First we make an Enterprise Service in a local package using the Successfactors SFAPI URL :

https://salesdemo4.successfactors.com/sfapi/v1/soap12?wsdl

Service Consumer -> External WSDL ->

VIA URL (https://salesdemo4.successfactors.com/sfapi/v1/soap12?wsdl) for this we added the HTTPS Certificate via transaction STRUST.

->  Next we save it as a local object -> And complete it an activate it:

On completion of the wizard the Proxy for "https://salesdemo4.successfactors.com/sfapi/v1/soap12?wsdl" ( URL ) will be generated and displayed in the Proxy Editor.

Do not forget to save or activate the result

We then try to make a logical port via SOAMANAGER -> Web Service Configuration -> WSDL Based configuration (since the WSDL is working in the steps above) ->

1. 1.     We fill in the Logical Port Name
2. 2.     Use WSDL via HTTP Access and it returns: SRT Framework exception: Error in WSDL parsing: Exception occurred in library handler
3. 3.     So we try via file upload and it returns the same error. SRT Framework exception: Error in WSDL parsing: Exception occurred in library handler

Next we tried SOAMANAGER -> Web Service Configuration -> Manual configuration ->

1. 1.     We fill in the Logical Port Name
2. 2.     Consumer Security:
   1. a.     Authentication Basic
   2. b.    No Username or Password (since it is not password/username protected)
   3. c.     URL Acces Path:
      • /sfapi/v1/soap12
   1. d.    Computer Name:
      • salesdemo4.successfactors.com
   2. e.     Port number:
      • 443
   3. f.     URL Protocol:
      • HTTPS
   4. g.    Logon Language:
      • Languagfe of user content
   5. h.     Make local call:
      • No call in local system
   6. i.      Transport binding type:
      • SOAP 1.2
   7. j.      Optimized XML Transfer:
      • None
   8. k.     Compress HTTP Message:
      • Inactive
   9. l.      Compress Response:
      • True
3. 3.     Soap Protocol:
   1. a.     RM Protocol:
      • WS-RM 2005/02
   1. b.    Message ID:
      • WS-A Message ID
   2. c.     Data Transfer scope:
      • Enhanced data transfer
   3. d.    Transfer protocol:
      • Transfer via SOAP Header
   4. e.     Process attachments:
      • No
4. 4.     Finish
5. 5.     When we Ping the Web Service it returns error:
   1. a.     Web service ping failed (RC=415). Service Ping ERROR: Unsupported Media Type
6. 6.     Same error returns when we try to test our enterprise Service:

Error messages in SRT_LOG when we tried to make the webservice via LPCONFIG:

<?xml version="1.0"?>

-<ERROR_CONTEXT>

-<ERROR_INFO>

<HTTP_ERROR_TEXT>Unsupported Media Type</HTTP_ERROR_TEXT>

<_--3CSOAP_FAULT_--3E>No faultstring available</_--3CSOAP_FAULT_--3E>

</ERROR_INFO>

-<CONSUMER_INFO>

<INTERFACE_NAME>SFAPI12</INTERFACE_NAME>

<INTERFACE_NAMESPACE>urn:server.sfapi.successfactors.com</INTERFACE_NAMESPACE>

<CONSUMER_PROXY>YOU_CO_SFAPI12</CONSUMER_PROXY>

<LOGICAL_PORT>DEFAULT</LOGICAL_PORT>

<OPERATION_NAME>login</OPERATION_NAME>

<OPERATION_NAMESPACE>urn:server.sfapi.successfactors.com</OPERATION_NAMESPACE>

<PROCESSING_UNIT>Sector 1: Consumer</PROCESSING_UNIT>

<PROCESSING_MODE>Synchronous</PROCESSING_MODE>

<PROCESSING_TYPE>Remote</PROCESSING_TYPE>

<WORK_PROCESS_NUMBER>14</WORK_PROCESS_NUMBER>

<WORK_PROCESS_PID>3972</WORK_PROCESS_PID>

<TERMINAL_NAME>Galileo</TERMINAL_NAME>

</CONSUMER_INFO>

-<TRANSPORT_INFO>

<PROTOCOL>https</PROTOCOL>

<AUTHENTICATION_METHOD>sapsp:HTTPSSO2</AUTHENTICATION_METHOD>

<TARGET_HOST_NAME>salesdemo4.successfactors.com</TARGET_HOST_NAME>

<TARGET_PORT_NUMBER>443</TARGET_PORT_NUMBER>

<TARGET_PATH>/sfapi/v1/soap12</TARGET_PATH>

<HTTP_TIMEOUT>0</HTTP_TIMEOUT>

</TRANSPORT_INFO>

</ERROR_CONTEXT>