Proxy to file, method EXECUTE_ASYNCHRONOUS
Hi,
Iam doing a scenario with the help of blogs
ABAP Proxies in XI(Client Proxy)
Weblog to send Response from RFC to File in Asyn Mode Using Proxy
In those blogs it is mentioned that once i create and activate my proxy, I get a method called EXECUTE_ASYNCHRONOUS in my class. But am not able any method like that in my scenario.
Could you pls tel me how can I resolve it?
hi,
Which Version you are using?
Since ECC 6.0 version, EXECUTE_ASYNCHRONOUS methods and EXECUTE_SYNCHRONOUS methods are not generated with that names.
Instead, The same name of your message interface is created as a method.
So in Report mention
CALL METHOD <prxy name>-><your message Interface name>
Regards,
Varun
Similar Messages
-
Hi eXperts,
I am developing an ABAP Proxy scenario where I have to get data from the Internal table and then send to a Legasy system as a FLAT FILE.
I have developed a sample code and providing in SDN to get me corrected if any errors.
Proxy to File Data Structure.
DT_S
ROOT 1-un
SI 1-1
S2 1-1
S3 1-1
MT_S
MI_S
Client Proxy Structure
^Class ZXX_CO_MI_S
^METHOD EXECUTE_ASYNCHRONOUS
^IMPORTING OUTPUT ZXX_MT_S
^MT_S ZXX_DT_S
^ROOT
S1 STRING
S2 STRING
S3 STRING
ZProgram.
Tables : lfa1.
Parameters : P_Date type lfa1-aedat.
Types for export parameters.
DATA : Pur_order type Zxx_mt_s.
*For calling class and exceptions.
Data : client_proxy type ref to ZXX_CO_MI_S,
Sys_exception type ref to CX_AI_SYSTEM_FAULT,
APPL_Exception type ref to AI_APPLICATION_FAULT.
Data : Begin of it_out occurs 0,
Lifnr like lfa1-lifnr,
Name1 like lfa1-name1,
Land1 like lfa1-land1,
End of it_itab.
Select lifnr, name1, land1 from lfa1 into table it_itab where aedat = p_date.
Loop at it_itab.
Pur_order-mt_s-root-s1 = it_itab-lifnr.
Pur_order-mt_s-root-s2 = it_itab-name.1
Pur_order-mt_s-root-s3 = it_itab-land1.
Clear it_itab.
Endloop.
*Create Proxy object and call method.
CREATE OBJECT CLIENT_PROXY().
TRY
CALL METHOD CLIENT_PROXY -> EXECUTE_ASYCHRONOUS
EXPORTING
OUTPUT = PUR_ORDER.
If sy-subrc = 0.
Write: / Method called successfully.
Else.
Write: / Method called failed.
Endif.
*exception handling.
CATCH CX_AI_SYSTEM_FAULT INTO SYS_EXCEPTION.
Write : / System fault encountered.
Write : / SYS_EXCEPTION -> ERROR TEXT.
RETURN.
CATCH CX_AI_APPLICATION_FAULT INTO APPL_EXCEPTION.
Write : / Application fault encountered.
RETURN.
ENDTRY.
COMMIT WORK.
Please Very Urgent.
thanks in advance...u r not passing the itab data to proxy.
pass the data to proxy before calling method..
client_proxy-MT_S ZXX_DT_S-ROOT[] = it_tab[].
*Create Proxy object and call method.
CREATE OBJECT CLIENT_PROXY().
TRY
CALL METHOD CLIENT_PROXY -> EXECUTE_ASYCHRONOUS
EXPORTING
OUTPUT = PUR_ORDER.
If sy-subrc = 0.
Write: / Method called successfully.
Else.
Write: / Method called failed.
Endif.
*exception handling.
CATCH CX_AI_SYSTEM_FAULT INTO SYS_EXCEPTION.
Write : / System fault encountered.
Write : / SYS_EXCEPTION -> ERROR TEXT.
RETURN.
CATCH CX_AI_APPLICATION_FAULT INTO APPL_EXCEPTION.
Write : / Application fault encountered.
RETURN.
ENDTRY.
COMMIT WORK.
Please Very Urgent.
thanks in advance... -
Hi,
I am trying to configure a Proxy to file scenario.
My sender service is ERP system and the my receiver is PI file system.
These are the steps I followed:
1. Created a sender business system for Web AS abap (my ERP system)
2. Created a receiver business system for third party (my PI system)
3. I created all the interface objects(datatype, message type, message interface etc) in Integration repository.
4. In the ERP system , I configured http connection of type h to PI system and also configured lcrsaprfc, sapsldapi connections of type t. I followed this blog: How do you activate ABAP Proxies?
5. I also configured the ERP system as local integration engine, by setting the role to application system in sxmb_adm (followed the above blog).
5. Now I generated proxy in sproxy transaction for the outbound interface.
6. Then I created the communication channel, receiver agreement, interface determination and receiver determination in Integration directory.
7. I created a abap program to call the execute_asynchronous method.
Now the issue is, when I execute my report, nothing happens. I can see the success xml message in sxmb_moni in ERP system. No message is seen on the PI's sxmb_moni. The file is not written either to ERP or PI systems.
Since I am new to PI, I am not sure where to begin with.
If anybody can help that would be great.
Thanks
MLSHi
Check the following
1. RFC connection between R/3 and PI
2. You said Business system of type third party (PI) is receiving it. Try Business system standalone Java. If PI system is already defined in Landscape as Integration server. It will not show any message output.
3. message is shown in sxmb_moni in your ERP that measn proxy is able to receive all objects and passed it from there.
4. Check in SMQ2 outbound queue of ERP as well as inbound queue for PI if message exist.
5. While configuring in ID you dont need a sender agreement. Did you created one.
Thanks
Gaurav -
Error in Proxy to File :no msg in sxmb_moni in application system
Hi all
i am doing a Proxy to file scenario.i have executed the scenario successfully and the file is created once. from next time i am executing the scenario it is picking the data in ECC and sending data to proxy method (checked through debugging),but it is not showing the message in sxmb_moni for the second time and is not reaching xi.It is only displaying the message processed for the first time.
i have not done any changes in design but few modifications like changing the date format in abap pgm.
plz provide the solution and can any one why there is no message in sxmb_moni?
Regards
satishHi,
Check the following
1. RFC connection between R/3 and PI
2. You said Business system of type third party (PI) is receiving it. Try Business system standalone Java. If PI system is already defined in Landscape as Integration server. It will not show any message output.
3. message is shown in sxmb_moni in your ERP that measn proxy is able to receive all objects and passed it from there.
4. Check in SMQ2 outbound queue of ERP as well as inbound queue for PI if message exist.
5. While configuring in ID you dont need a sender agreement. Did you created one.
and finally Check in SMQ2 transaction if the messages are waiting there. If yes, unlock and release queue.
regards,
Surya -
Outbound Proxy - XI - File scenario. Outbnd proxy not callin XI.
Hi All,
I have a requirement where I have to develop a Outbound Asynch Proxy-> XI -> File scenario.
For this I have crated an Outbound Asynch proxy and called this proxy from a report in ABAP.
When I execute the report, i am unable to see the message in XI Moni.
But when I try to emulate the same scenario by passing a message from the RWB Test Page, the message is flowing to the file successfully.
It seems that the problem is just that the ABAP report is unable to call the XI by executing the outbound proxy method.
The code for the report is as below:
*& Report Z_ASYNCH_PROXY
REPORT Z_ASYNCH_PROXY.
data prxy type ref to ZFUJCO_SI_TEL_NUM_RFC_RESP_ASY.
data out type ZFUJMT_TEL_NUM.
out-MT_TEL_NUM-TEL_NUM = 'test_proxy'.
create object prxy .
TRY.
CALL METHOD prxy->si_tel_num_asych_in
EXPORTING
output = out
commit work.
CATCH cx_ai_system_fault .
DATA fault TYPE REF TO cx_ai_system_fault .
CREATE OBJECT fault.
WRITE :/ fault->errortext.
ENDTRY.
Please tel me how to find out that where the message is getting stuck and resove this.
regards,
PiyushHi All,
Thanks a lot for ur inputs.
i was able to resolve it.
The pointers are:
- The message was gettting stuck in the queues XBTS0009 of the Bus system. I chekced it in SXMB_MONI of bus syst.
- i activated the queues usung SXMB_ADM -> manage queues
- The HTTP destinatin was not maintained for the connectino to the PI Url. In fact the url was hardcoded in the sicf -> xi-> engine
I maintained this using
http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3414900)ID1803326050DB10288658103888810737End?blog=/pub/wlg/3022
Thanks for all your help.
regards,
Piyush -
Need ABAP coding in Proxy TO File scenario
Hi friends,
i need to do the Proxy to file scenario.. for this.. i want to retrive the data from R/3 system and load the data into the class which we defined in SPROXY (Outbound class) ..
so, can any one give me the exact coding... for this.. how can we move the data from our executable program to Outbound Class structure....
helpful answers will be appriciated..
Thanks
Babu<i>i want to retrive the data from R/3 system and load the data into the class which we defined in SPROXY (Outbound class) ..</i>
-->
data: cproxy type ref to ZCO_MI_MKPROXY2RFC_OUT,
itab_out type ZMT_MKPROXY2RFC_OUT,
itab_in type ZMT_MKPROXY2RFC_RES.
TYPES: BEGIN OF values,
carrid TYPE spfli-carrid,
connid TYPE spfli-connid,
END OF values.
DATA: progname like sy-repid,
dynnum like sy-dynnr,
dynpro_values TYPE TABLE OF dynpread,
field_value LIKE LINE OF dynpro_values,
values_tab type table of values.
progname = sy-repid.
dynnum = sy-dynnr.
CLEAR: field_value, dynpro_values.
start-of-selection.
parameter: p_carrid like sflight-carrid obligatory value check,
p_connid like sflight-connid.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
EXPORTING
tabname = 'DEMOF4HELP'
fieldname = 'carrid'
dynpprog = progname
dynpnr = dynnum
dynprofield = 'p_carrid'.
CALL FUNCTION 'DYNP_VALUES_READ'
EXPORTING
DYNAME = progname
DYNUMB = dynnum
TABLES
DYNPFIELDS = dynpro_values
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
read table dynpro_values index 1 into field_value.
SELECT carrid connid
FROM spfli
INTO CORRESPONDING FIELDS OF TABLE values_tab
WHERE carrid = field_value-fieldvalue.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
RETFIELD = 'connid'
DYNPPROG = progname
DYNPNR = dynnum
DYNPROFIELD = 'CONNECTION'
TABLES
VALUE_TAB = values_tab
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
TRY.
CREATE OBJECT cproxy.
itab_out-MT_MKPROXY2RFC_OUT-CARRID = p_carrid.
itab_out-MT_MKPROXY2RFC_OUT-CONNID = p_connid.
progname = sy-repid.
dynnum = sy-dynnr.
CALL METHOD cproxy->EXECUTE_SYNCHRONOUS
EXPORTING
OUTPUT = itab_out
IMPORTING
INPUT = itab_in
CATCH CX_AI_SYSTEM_FAULT .
write: itab_in-MT_MKPROXY2RFC_RES-CURRENCY,itab_in-MT_MKPROXY2RFC_RES-FLDATE,
itab_in-MT_MKPROXY2RFC_RES-PLANETTYPE,itab_in-MT_MKPROXY2RFC_RES-PRICE,
above code reads carrid and connid from screen and the same are passed to proxy..
hope you can relate it to your requirement....
itab_in-MT_MKPROXY2RFC_RES-SFATSMAX,itab_in-MT_MKPROXY2RFC_RES-SEATSOCC,
itab_in-MT_MKPROXY2RFC_RES-STATUS. -
ABAP Client Proxy to File (File is not getting generated)
Hi All,
I'm trying out a scenario ABAP proxy --> XI --> FILE.
I have followed the given blog to create ABAP client proxy.
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
While executing the ABAP client proxy, the values are properly sent to XI and in the SXMB_MONI the message shows as successful. But the correspoding file is not created.
It seems everything is fine in the receiver adpater(Monitoring) and in the SXMB_MONI also the msg shows successful(receiver side).
The directory path and the corresping file creation parameters also looks fine.
Couldn't figure out what went wrong. Please help me on this.
Thanks,
Ajay.Hi Smitha,
Please find below the Call Adapter trace
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Call Adapter
-->
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external =</Trace>
<Trace level="1" type="T">Sender agency external =</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!-- ************************************
-->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.0</Trace>
<Trace level="2" type="T">Host = iscsapapp4w:8010</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
<Trace level="2" type="T">Remote address = 10.191.117.166</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!-- ************************************
-->
<Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
<Trace level="3" type="T">Getting type of XMB...</Trace>
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="2" type="T">XMB kind = CENTRAL</Trace>
<Trace level="3" type="T">Start pipeline found</Trace>
<Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="3" type="T">system-ID = NW2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Message-GUID = B2DD6D78BBF141458DDC0DDE39782DE3</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- <!-- ************************************
-->
<Trace level="3" type="T">QOS = EO</Trace>
<Trace level="3" type="T">Message-GUID = B2DD6D78BBF141458DDC0DDE39782DE3</Trace>
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="3" type="T">Generate prefixed queue name</Trace>
<Trace level="1" type="T">Queue name : XBTI0000</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0000</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="3" type="T">Setup qRFC Scheduler</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="3" type="T">Call qRFC .... MsgGuid = B2DD6D78BBF141458DDC0DDE39782DE3</Trace>
<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
<Trace level="3" type="T">OK.</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="3" type="T">Version number = 000</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 001</Trace>
<Trace level="3" type="T">Message version 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
<Trace level="2" type="T">Increment log sequence to 001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = NW2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: - ACN_LEGACY2_04_BS</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Message version 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) ACN_LEGACY2_04_BS MI_Client_Proxy_Inbound</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: MI_Client_Proxy_Inbound</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- <!-- ************************************
-->
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- <!-- ************************************
-->
<Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="2" type="T">got property produced by receiver determination</Trace>
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOM2__0001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 012</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
<Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
<Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
<Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
<Trace level="2" type="T">Increment log sequence to 005</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="3" type="T">system-ID = NW2</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = XIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
<Trace level="3" type="T">External PLID = CENTRAL</Trace>
<Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
<Trace level="3" type="T">ENABLE = 1</Trace>
<Trace level="3" type="T">TRACELEVEL = 0</Trace>
<Trace level="3" type="T">EXEMODE = A</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline elements</Trace>
<Trace level="3" type="T">ELEMPOS = 0001</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0002</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0003</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0004</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0007</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0008</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">ELEMPOS = 0009</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">FL_DUMMY =</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
- <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
<Trace level="1" type="Timestamp">2006-04-03T10:24:14Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping is already determined in the interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 791955998E03380CA938A0130A348AFB</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping 3475AE80930811DAA18DC14C0ABF75A6</Trace>
<Trace level="1" type="T">Interface Mapping http://accenture.com/xi101/ABAPclientProxy IM_Valuemapping</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_Valuemapping_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_Valuemapping_.</Trace>
<Trace level="3" type="T">Load 3475ae80-9308-11da-a18d-c14c0abf75a6, http://accenture.com/xi101/ABAPclientProxy, -1, com/sap/xi/tf/_MM_Valuemapping_.class.</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_MM_Valuemapping_.class (http://accenture.com/xi101/ABAPclientProxy, -1) in swcv 3475ae80-9308-11da-a18d-c14c0abf75a6.</Trace>
<Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_Valuemapping_</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_Valuemapping_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_Valuemapping_ completed. (executeStep() of com.sap.xi.tf._MM_Valuemapping_</Trace>
<Trace level="3" type="T">Dynamic configuration is empty</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
<Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
<Trace level="2" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
<Trace level="2" type="T">-ACN_Sender_BS_XI</Trace>
<Trace level="2" type="T">-ACN_LEGACY2_04_BS</Trace>
<Trace level="2" type="T">http://accenture.com/xi101/ABAPclientProxy.MI_Client_Proxy_Inbound</Trace>
<Trace level="2" type="T">Channel found: - ACN_LEGACY2_04_BS - ValueMap_Repl_Receiver1</Trace>
<Trace level="2" type="T">no header mapping defined</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 006</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER">
<Trace level="1" type="Timestamp">2006-04-03T10:24:15Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- <!-- ************************************
-->
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS =</Trace>
<Trace level="3" type="T">P_IFNAME =</Trace>
<Trace level="3" type="T">P_METHOD =</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Unknown channel type: File</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
<Trace level="3" type="T">ADRESSMOD = SD</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: File</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">return fresh values from cache</Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET): af.nw2.iscsapapp4w</Trace>
<Trace level="3" type="T">URL = http://iscsapapp4w.idcsap.com:51000/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User = XIISUSER</Trace>
<Trace level="3" type="T">Cached = X</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 200</Trace>
<Trace level="3" type="T">Deserializing message object...</Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="Timestamp">2006-04-03T10:24:19Z CET End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 007</Trace>
<Trace level="3" type="T">Message version 007</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Thanks,
Jothivel. -
Hi all:
I would like to implement the IIS Proxy SSO solution. Is there anybody can send me the IIS Proxy SAR file ?
I cannot find it in service.sap.com/patches
my mail : [email protected]
I will give you the reward points.
thanks.Hi,
To my knowledge IISProxy is not supported/delivered by SAP anymore. See the OSS note 886214 for details. You can use WebDispatcher as reverse proxy and SPNego for SSO authentication. They are supposed to be replacements for what you could do with IISProxy.
So I doubt you will find IIS Proxy inside Service Marketplace. Doesn't mean that you cannot get it anywhere else though.
Regards,
Mike -
Problem with Configuration in Production ( ABAP Proxy - XI - FILE)
Hi All,
I have a ABAP Proxy -> XI -> FILE scenario wich is working perfectly in DEV and QAS environment.
When the person responsible for transporting tried to transport the objects in QAS to PRD, the following error happened:
Direction of communication channel |BS_MA_FileServer_PRD | CC_File_PedidosServ_MA_FileServer_IA is incorrect.
Correct the direction or choose another communication channel
BS_MA_FileServer_PRD - Business System (FILE)
CC_File_PedidosServ_MA_FileServer_IA - My FILE Communication Channel
This was what the Basis person sent to me. I don't have access to know exactly what happened. And I really don't know what could be wrong or if maybe a component was created wrongly in Production.
Hope you can help.
Points will be given.
tks.. DanielaYou have mentioned FILE is on the receiving side and ABAP proxy is on sender side.
But the error pasted by you clearly shows syntax of a Sender Agreement .
For receiver agreement it should be |<Sender Service>| |BS_MA_FileServer_PRD | CC_File_PedidosServ_MA_FileServer_IA
Bipin -
Getting error when testing Proxy to File interface
Hi Guru's,
While I am testing a Proxy to File Interface, using SPROXY transaction i am sending a message from R/3 to PI.
the message showing successful in R/3 Moni,but in PI moni I am getting the following Error..
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Receiver Determination
-->
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In this inreface, I am suppose to send the mesasage to only one Target system(ftp server) . i have checked in ID part also,
every thing is clear in ID. Can any body please tell where the mistake might exists...
Thanks in advance..
Regards
RajHi,
No receiver could be found means Check your Receiver Determination. Activate and update cache. Asysnchronous messages can be manually restarted.
have you seen this threads,
NO_RECEIVER_CASE_ASYNC
No receiver could be determined
regards,
ganesh. -
Hi Experts,
I have a scenario where I need to send data from SAP to PI so I am using proxy to file scenario. Here i need to send huge amount of data.
In some blog i saw that proxy can handle only some maximum amount of data.(but not 100% sure how much size of data the proxy can handle)
So i decided to call the proxy multiple times by sending only some 'n' no. of records and kept the receiver file adapter in append mode.
The problem here is the data is not appending in the order in which i am sending from SAP. In sxmb_moni the messages were showing the QoS as 'EO'.
Is it possible to change the QoS to EOIO?
Thanks & Regards
Stephen RouvierFrom SAP documentation:
"The sender of a message uses the attribute Quality of Service (QoS) to determine how a message is delivered"
hence ..as the File adapter supports all Qos, the Proxy can be called with Qos EOIO and the adapter will maintain the Qos as requested.
You should how ever try and send the data in a bulk and see how the Proxy handle it.
What is the nature of the data exported and for what purpose? -
Scenario PROXY - SENDER FILE - RECEIVER FILE
Hi Experts,
I need to create a synchronous scenario where the proxy sends the filename to send and PI must transfer the file to a location X. The source file is in a different location of the destination file
This scenario, should this be done through Process Integration?
Thanks,Hi,
I think you can use a sync/async bridge to do your scenario and you wont need any development outside of using standard modules. The idea is to create a scenario Proxy(sync)-File(Async) -File (Async) without BPM. Check the point 8 in this document http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80f96dbf-adca-3010-ffb5-daf2d1f0e276?QuickLink=index&…
I have never tested this with the SFTP channel, and i dont know if this adapter supports the RequestOneWayBean and WaitResponseBean modules. May be you should wait to someone that confirms to you the possibility of using this modules with the SFTP adapter.
Regards. -
Including helper classes in java proxy jar file
I must not be using the right header search criteria because I'm sure this question
has been asked before. In a Web Service File (.jws) I've imported a couple of
helper classes that function as data transfer objects. I did this to maintain
consistency with other portions of the application. The Java Proxy jar file generated
by Workshop does not include these files. Is there a way of including these dependencies
or do I need to distribute another jar file with my helper classes?Hi Naichen,
I was able to successfully run both the autotype and clientgen Ant task, on the
WSDL you provided. The code behind those Ant tasks are pretty much what the WebLogic
Web Services test page run. Are you using WLS 8.1 SP2? If not, you might want
to try with that version.
Regards,
Mike Wooten
"Naichen Liu" <[email protected]> wrote:
>
>
>
Hi,
I am having a warning message when trying to generate java proxy jar
file on weblogic8.1
webservice test web app, the message is as follows:
"Warning Failed to generate client proxy from WSDL definition for this
service.
Prescription Please verify the <types> section of the WSDL."
in the mean time, on weblogic starting terminal, I saw the following
exceptions,
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\AlphaLength4Deserializer.java:36: cannot resolve symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,4L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\OSIFieldAnonTypeDeserializer.java:36: cannot resolve
symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkMaxLengthFacet(__typed_obj,69L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\AlphaLength2Deserializer.java:36: cannot resolve symbol
symbol : class FacetUtils
location: package binding
weblogic.xml.schema.binding.FacetUtils.checkLengthFacet(__typed_obj,2L);
^
C:\DOCUME~1\u252738\LOCALS~1\Temp\wlwproxy37508.jar1533409921\com\ual\www\rcc\cb
t\schema\modifypnr\FreeFormAnonTypeDeserializer.java:36: cannot resolve
symbol
symbol : class FacetUtils"
Can anybody help me about this issue? I attached WSDL file, also United
Airlines
got an enterprise weblogic license deal with BEA, any help will be highly
appreciated.
Thanks!!!
Naichen -
Proxy to file interface , need to have field name aslo in the file
Hi , i ahve done a interface from Proxy to file , in which , i have to give a label name of all the fields in the top of the file which acts as header in my fields , is there ant option in the XI to give header or label
please help me in this
thanking you
sridharHi Sridhar,
This link might be helpful:[http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm|http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm]
Regards
Bhanu
Intelligroup. -
Error in Proxy to File scenario
Hello All,
I m doing Client Proxy, ABAP proxy to file scenario.
I hv done all the configurations in IR & ID.
I hv also created proxy in sender R3 system.
But messages are not going successfully from R3.
when i checkin SXMB_MONI of R3 i get following error
<SAP:Stack>Error when receiving by HTTP (error code: 110, error text: )</SAP:Stack>
Message is in SYSFAIL status in SMQ2.
Any clues how it can be solved??
Thanks in adv.
MahiHi Maheshwari,
Please try as mentioned below
Option 1: Go to SXMB_ADM->Manage Queues and Deregister all the Queues.Use transaction SMQR or SMQ2 to reset the status of queues
For this to initiate processing of messages stuck in the queue, make sure to set following IS configuration parameter
MONITOR QRFC_RESTART_ALLOWED to value 1
Option 2: Check the user associated with the RFC destination AI_RUNTIME_JCOSERVER in sm59 transaction. It is generally SAPJSF. Might be posisble the user password is expired or locked. Log on to j2ee admin tool on the server side and update the password and then see if it works.
Thanks
Amit
Reward points if answer is helpful
Maybe you are looking for
-
I am running Windows 7-32bit...
I had to restore my laptop to an earlier date/time (before I tried out the Adobe CC trial software). Now that I have the Desktop app loaded, it indicates that all the apps I chose to trial, are "up to date". Yet they are missing off my Programs and F
-
Parse xml file with validating againat dtd
i have a xlm file looks like: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE map SYSTEM "map.dtd"> <map width="20" height="15" goal="25" name="eXtreme Labyrinth of Dooom"> <random-item type='lantern' amount='5' /> <random-item type='health' amount=
-
Adobe Creative Suite cs6 downgrade to 5.5
Good morning, 1. if we buy CS6 Design and Web Prem 6 can we downgrade to 5.5? our company use cs5.5. 2. If this is possible how can we do it? 3. If downgrade to cs.5.5 (if possible) and we want to get back cs6 (1 year... using cs5.5) we need to p
-
Can't log in neither install Skype on Nokia X2
Hi I'm having trouble with loggin to skype on Nokia X2. The app buffers but doen't go beyond that. I tried to delete the app and re-install it, but can't download it from Google Play. Thanks
-
IPod nano unresponsive to ANYTHING except shuffle-shake
My iPod nano 3rd gen 4gb became unresponsive to anything yesterday. Tried pressing center button & menu--nothing. Tried toggling hold on and off--nothing. It will only respond to shaking to engage the shuffle. Computer does not recognize the iPod, iP