cancel
Showing results for 
Search instead for 
Did you mean: 

Axis Adapter: org.apache.axis.ConfigurationException: handler.type is not set

emir_morillo2
Explorer
0 Kudos

Hi SCN, i have SAP PI 7.31 SP16.

I am executed an interface SAP HCM - PI - SuccessFactors BizX.

I have the next error.

Communication Channel Configuration

Anyone has had a similar error?

Regards,

Emir Morillo

Accepted Solutions (1)

Accepted Solutions (1)

apu_das2
Active Contributor
0 Kudos

Hi Emir,

Looks like your module parameter configuration is wrong.

This error is for which channel - Login one or another one used for subsequent call?

Use exactly below module config -

Thanks,

Apu

emir_morillo2
Explorer
0 Kudos

Hi Apu, thank you for you response.

Now i have the error in Fault Message "Invalid SFAPI session!".


The configuration is the standard scenario RecruitingDataSynchronization.



The Comnnunication Channel Configuration:

The message monitor

Regards.

apu_das2
Active Contributor
0 Kudos

Great so my answer was helpful to you now you are in track. This error is coming due to the fault of the SAP provided standard ES component.

In the dynamic header for the response message there is SetCookie[0] but it should be SetCookie.

Now you need to implement this note . This will solve your issue. Take help from your basis team because this note will tell you to update some PI components like AF Core.

SAP Note - 2251806

emir_morillo2
Explorer
0 Kudos

Hi Apu,

I checked the nota, the version SFIHCM01 600 SP11.

Function setHTTPHeaderCookies

Interfaz Cicle HRSFI_SYNCH_METADATA:

  1. SFSFSessionHandlingLoginQueryResult_Out_to_SFSFSessionHandlingLoginQueryResult_In

Session ID Response

    2. SFSFAPIDictionaryListSFObjectsResult_Out_to_SFSFAPIDictionaryListSFObjectsResult_In CC SFSF_SOAPReceiver according doc SF2_NW740_BB_ConfigGuide_EN_XX.doc in Login(1)

Request

    In this ponit, the value "$Version=0;" is correct?.

    It should be the session id the response "F678F9B8F3DBE6FA80C50E4338B2DFC5.SC4BSFAPI02"?.

Response Fault Message

    2. SFSFAPIDictionaryListSFObjectsResult_Out_to_SFSFAPIDictionaryListSFObjectsResult_In CC SFSF_SOAPReceiverAxis in Login(1)

The Session ID is the same, tha the response login since SFSF.  But the similar error.

Response Fault Message

Really is not same session ID

TEST in SoapUI

Login

List Object

Here is two Cokkie. Cookie and Cookie2. In PI only i have one Cookie.

I don't understand

Regards

apu_das2
Active Contributor
0 Kudos

Hi,

As per the note, you need to update below PI components as per your SP level . Have you done these -

XI ADAPTER FRAMEWORK

ESR

MESSAGING SYSTEM SERVICE

PI GUI LIBRARY

PI SCP EXTENSIONS

SOA MONITORS BASIC

XI TOOLS

XI CONNECTIVITY SE


And where is my reward point


Thanks,

Apu

emir_morillo2
Explorer
0 Kudos

Hi Apu, all components are updated to SP Nivel the PI Instalation.

This not is the problem.

Regards.

apu_das2
Active Contributor
0 Kudos

Now thats odd.

Implementing this node should solve your issue. Any way if its persist raise a call to SAP.

As in the subsequent call you are getting Version0 in the session that should not now basically. Actually SFSF session one BigIPServer as well along with regular session . That create issue in some case but in your case its version0.

Thanks,

Apu

emir_morillo2
Explorer
0 Kudos

Hi, the issue has resolved.

In the new version the SF1_NW740_BB_ConfigGuide_EN_XX.docx (March 2016) . It have the correct configuration for adapter AXIS

Thansk to all.

Regards

Answers (1)

Answers (1)

nitindeshpande
Active Contributor
0 Kudos

Hi Emir,

The module parameters are case-sensitive. We have the SCN threads with similar errors. Please change the handler.type to Handler.type, it will resolve your issue.

PI 7,10 AXIS SOAP Rec. Error:  handler.typ... | SCN

Regards,

Nitin

emir_morillo2
Explorer
0 Kudos

Hi Nitin,

I'm getting the same error, but changing it to Handler.Type did not help. Do you have any other suggestion?

Still when the adjust was made the error is same.

My doubt is that "AF_Adapters/axis/AFAdapterBean" no have "handler.type" configuration

For the same execution, the log error is diferent.

Will be necessary additional parameters?

Regards