File to Soap Syn Scenario

[Former Member]

Hi Experts,

I have created File to Soap syn Scenario.

I am getting following error in RWB (CC monitoring)::

SOAPFault received from Integration Server. ErrorCode/Category: XIProtocol/WRONG_VALUE; Params: SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(1), xi_input120100406-133524-40720100406-133535-09520100406-133535-32920100406-133535-57920100406-133535-82920100406-133536-07920100406-133536-32920100406-133536-56420100406-133536-78220100406-133537-032.xml, ST: ST_XMS_MSGHDR30_DYNAMIC; AdditionalText: An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC; ApplicationFaultMessage: null; ErrorStack: XML tag SOAP:Envelope(1)SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(1) (or one of the attributes) has incorrect value xi_input120100406-133524-40720100406-133535-09520100406-133535-32920100406-133535-57920100406-133535-82920100406-133536-07920100406-133536-32920100406-133536-56420100406-133536-78220100406-133537-032.xml An error occurred when deserializing in the simple transformation program ST_XMS_MSGHDR30_DYNAMIC Data loss occurred when converting xi_input120100406-133524-40720100406-133535-09520100406-133535-32920100406-133535-57920100406-133535-82920100406-133536-07920100406-133536-32920100406-133536-56420100406-133536-78220100406-133537-032.xml

Please suggest

T& R

Sushama

[MichalKrawczyk · Accepted solution]

Hi,

>>>SOAP:Header(1)sap:DynamicConfiguration(3)sap:Record(1) (or one of the attributes) has incorrect value

check out the dynamic configuration header in the xml message and also your adapter module bean config

as you need to use additional adapter modules to do file- sync soap configuration

Regards,

Michal Krawczyk

[Former Member]

Solved, thanks !!

[Former Member]

Hi,

I'm getting same error, can you please post what was the error and how you rectified it.

Regards,

Venu

[Former Member]

Hi,

Are you using the request response bean..for this syn scenario,....

also errors seems like namespace problem as it is unable to deserialize the same...chk that

HTH

Rajesh

[Former Member]

Hi,

Is it possible,if u can explain the prblm in datail...

If u describe the prblm the best the people here can zero-in at ur exact requirements...

So, can u make it clear....

Babu

[Former Member]

Hi Babu,

I am sorry if I was not clear in explaning.

Okay. I meant with the DC parameters the dynamic configuration parameters (or officially called the adapter specific message attributes or ASMA) that the file adapter added in the XI message. I assume Sushama activated this feature to transport the file adapter specific information (e.g., the file name, etc). These parameters are included in the DynamicConfiguration SOAP header. Sushama should check those entries in RWB at the adapter engine.

Some of those parameter values appeared to be too long and resulted in the quoted error:

>sap:DynamicConfiguration(3)sap:Record(1) (or one of the attributes) has incorrect value

Once which parameters are too long, Sushama can decide on how to resolve this issue using one of the options that I suggested in my previous reply.

I hope you got the idea this time.

Best regards, Yza

[Former Member]

Hi Sushama,

This error means that those DC parameters violate the length limit imposed in the integration engine.

Now your problem is how to work around this issue. If you can live without those long entries, there is module DynamicConfiguratonBean to remove those long entries. If you need these entries, you will have to write your own module to either consume those entries within the adapter engine or convert them (or split them) into shorter entries so that they will be accepted by the integration engine.

Best regards, Yza