ASMA Directory

Hi Guys,

Could someone please guide me with a problem that I am having using the file adapter's ASMA?

I am trying to pick-up a file using the file adapter and then place the file in a different directory also using the file adapter. I have selected the Directory ASMA in both adapters. I am also keeping the same filename. This part is working fine.

I am using a UDF to specify the target directory. The UDF contains that following code:

DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);

DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");

DynamicConfigurationKey key1 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","Directory");

String filename = conf.get(key);

conf.put(key, filename);

String directory = conf.get(key1);

directory = "/Central/Branches/70018/";

conf.put(key1, directory);

return a;

The problem that I am experiencing is that the file is placed back into the source folder, thus causing a loop. It appears that the UDF is not changing the target directory.

Thanks very much,

Miguel

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hi Miguel,

Please modify the code slightly and tell if it is working..

DynamicConfigurationKey key1 = DynamicConfigurationKey.create("http:/"+"/sap.com/xi/XI/System/File","Directory");

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Varun,

I modified the code, but the file still went through to the source directory instead of the changed target directory...

Thanks,

Miguel

Hi Miguel,

I was trying out a sample scenario for the same...But Iam able to assign directory name dynamically

I even tried giving the directory name you gave i.e \Central\Branches\70018\,

And in this case it put the output file in C:\Central\Branches\70018\....

Is this how you are planning to achieve the result??

Jorge,

Can u give the full path and check once again.

-raj.

Arrey Raj bhaai....help!!! I've been trying my best to get this error in my XI system

Jorge,

One more thing just to confirm did u checked the check box Directory (ASMA) in both the channels.

Try to give the directory name as

directory ="usr\sap\Central\Branches\70018\" --Just like this give ur path.

-raj.

Hi Varun,

Yes, this is exactly how I am planning to get the target directory.

The only difference is that the final section, i.e. 70018, is going to be a variable.

Let me try and example my whole problem:

I have a file that could go to many possible target directories...the directory it needs to go is contained within the xml file being read, BUT the value is contained in an attribute and not an element tag...therefore I cannot use variable substitution...

That is why I am trying to use ASMA to change the target directory...

I know that the directory is fine, because I am currently using the same target directory in other interfaces, and they are working fine...

Also, I am using FTP, so therefore the path that I am giving it, is the full path of the target directory...this directory is not on the XI server....

Hope that this gives a better description...

Thanks,

Miguel

Hi Raj,

Please see my response to Varun regarding the directory name...

Regarding the check boxes, yes I have ticked both the sender and the receiver channels...

Thanks,

Miguel

Miguel,

In SXMB_MONI, you will find a link / tab called DynamicConfiguration.

Do you see this ? ( under SOAP Header of Response ) . In this, does the Target Directory contain some value in the Dynamic Configuration?

Regards

Bhavesh

Hi Bhavesh,

Yes, I can see the Dynamic Configuration (both in SXMB_MONI and on the RWB) and they both contain the source directory defined in the Directory parameter.

I would expect to see my changed target directory populated in this parameter. I think that if this were the case, my file would probably be dropped in the correct target directory.

Thanks,

Miguel

So would I

My gut feel is that the UDF is not getting called at all.

How do you check if your UDF is being called? Well this is simple,

Add a Trace Statement to the UDF.

AbstractTrace trace=container.getTrace();
trace.addWarning("UDF Called");

And then see if this Trace is a part of the Trace in MONI.

Regards

Bhavesh

Hi Bhavesh,

I have already tried this...I added a whole bunch of warnings on a trace...

I added some at the start of the UDF, and then at various points within the UDF...

When I check MONI, I don't see the trace warning. But the UDF is mapped to a tag that is set as required, so it would fail if it didn't go through it...

Thanks,

Miguel

Miguel,

You should be able to see the Trace Statement if the UDF is called. You will find this Under START APPLICATION TRACE in the Trace in the SOAP header in MONI.

I think we are misssing something somewhere. Maybe a Cache issue, maybe mapping bot activated and so on.

Regards

Bhavesh

Hi Bhavesh,

I have reactivated the message mapping and done a full cache refresh...

I cannot find the section of the trace that you have mentioned.

This is the trace that I get:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <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 = XIParty</Trace>

<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>;

<Trace level="1" type="T">Sender party external = </Trace>

<Trace level="1" type="T">Sender party normalized = </Trace>

<Trace level="1" type="T">Party normalization: receiver </Trace>

<Trace level="1" type="T">Receiver scheme external = </Trace>

<Trace level="1" type="T">Receiver agency external = </Trace>

<Trace level="1" type="T">Receiver party external = </Trace>

<Trace level="1" type="T">Receiver party normalized = </Trace>

<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.1</Trace>

<Trace level="2" type="T">Host = pgsap45.sap.pg.co.za:8001</Trace>

<Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>

<Trace level="2" type="T">Remote address = 172.16.1.108</Trace>

<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>

<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>

<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="3" type="T">No triggers found. OK. </Trace>

</Trace>

<Trace level="1" type="T">XMB entry processing </Trace>

<Trace level="3" type="T">system-ID = XIQ</Trace>

<Trace level="3" type="T">client = 300</Trace>

<Trace level="3" type="T">language = E</Trace>

<Trace level="3" type="T">user = XIAFUSER</Trace>

<Trace level="1" type="T">Message-GUID = 8489A912556E11DC9A030014220DCB99</Trace>

<Trace level="1" type="T">PLNAME = CENTRAL</Trace>

<Trace level="3" type="T">Message-GUID = 8489A912556E11DC9A030014220DCB99</Trace>

<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>

<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 : XBTI0002</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTI0002</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 = 8489A912556E11DC9A030014220DCB99</Trace>

<Trace level="3" type="T">Call qRFC .... Version = 000</Trace>

<Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</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="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="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="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 = XIQ</Trace>

<Trace level="3" type="T">client = 300</Trace>

<Trace level="3" type="T">language = E</Trace>

<Trace level="3" type="T">user = XIAFUSER</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<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">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">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">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">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">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">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">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">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="1" type="Timestamp">2007-08-28T13:57:52Z CAT Begin of pipeline processing PLSRVID = CENTRAL</Trace>

<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>

<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">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_DUMMY = 0</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">Classic Receiver Determination via Rules. </Trace>

<Trace level="2" type="T">Check conditions for rule line no. 1 </Trace>

<Trace level="3" type="T">...create rule engine </Trace>

<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET_SYSTEM(MSG=&_MSG&;SYSFIELD="FileName";SYSNSP="http://sap.com/xi/XI/System/File")% [*] 6* </Trace>

<Trace level="2" type="T">......attachment XI_Context not found </Trace>

<Trace level="3" type="T">......extracting from attachment: FileName = 70018_SendMSG_Payment_0_709_20070807052913.xml </Trace>

<Trace level="2" type="T">......extracting values found: 1 </Trace>

<Trace level="2" type="T">...invalid Receiver: - IP_Digicall_BranchPayment </Trace>

<Trace level="2" type="T">Check conditions for rule line no. 2 </Trace>

<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET_SYSTEM(MSG=&_MSG&;SYSFIELD="FileName";SYSNSP="http://sap.com/xi/XI/System/File")% [*] 7* </Trace>

<Trace level="2" type="T">......attachment XI_Context not found </Trace>

<Trace level="3" type="T">......extracting from attachment: FileName = 70018_SendMSG_Payment_0_709_20070807052913.xml </Trace>

<Trace level="2" type="T">......extracting values found: 1 </Trace>

<Trace level="2" type="T">...valid Receiver with Condition: - SBO_DRP_SERVER </Trace>

<Trace level="2" type="T">No Receiver found behaviour: 0 </Trace>

<Trace level="2" type="T">Number of Receivers:1 </Trace>

</Trace>

<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>

</Trace>

<Trace level="3" type="T">No persisting of message after plsrv call, because of config </Trace>

</Trace>

<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>

<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">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_DUMMY = 0</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) SBO_DRP_SERVER MI_Digicall_BranchPayment </Trace>

<Trace level="2" type="T">...valid InbIf without Condition: MI_Digicall_BranchPayment </Trace>

<Trace level="2" type="T">Number of receiving Interfaces:1 </Trace>

</Trace>

<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>

</Trace>

<Trace level="3" type="T">No persisting of message after plsrv call, because of config </Trace>

</Trace>

<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>

<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">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_DUMMY = 0</Trace>

<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 = XBTO0___0000</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">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="3" type="T">Persisting message Status = 012</Trace>

<Trace level="3" type="T">Message version 001</Trace>

<Trace level="3" type="T">Pipeline CENTRAL</Trace>

<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="3" type="T">message version successfully read from persist version= 001</Trace>

<Trace level="2" type="T">Increment log sequence to 002</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 = XIQ</Trace>

<Trace level="3" type="T">client = 300</Trace>

<Trace level="3" type="T">language = E</Trace>

<Trace level="3" type="T">user = XIAFUSER</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<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">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">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">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">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">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">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">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">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="1" type="Timestamp">2007-08-28T13:57:52Z CAT Begin of pipeline processing PLSRVID = CENTRAL</Trace>

<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>

<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>

<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">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_DUMMY = 0</Trace>

<Trace level="2" type="T">......attachment XI_Context not found </Trace>

<Trace level="3" type="T">Append context with name =Directory and value =/Ibolt/Transactions/Out </Trace>

<Trace level="3" type="T">Append context with name =FileName and value =70018_SendMSG_Payment_0_709_20070807052913.xml </Trace>

<Trace level="3" type="T">Mapping is already determined in the interface determination </Trace>

<Trace level="1" type="T">No mapping required </Trace>

</Trace>

<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>

</Trace>

<Trace level="3" type="T">No persisting of message after plsrv call, because of config </Trace>

</Trace>

<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>

<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">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_DUMMY = 0</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">-IBOLTSERVER </Trace>

<Trace level="2" type="T">-SBO_DRP_SERVER </Trace>

<Trace level="2" type="T">http://ibolt.com/PGSAP/TransactionalData.MI_Digicall_BranchPayment </Trace>

<Trace level="2" type="T">Channel found: - SBO_DRP_SERVER - FTP_Digicall_Franchisee_Payment </Trace>

<Trace level="2" type="T">no header mapping defined </Trace>

</Trace>

<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>

</Trace>

<Trace level="3" type="T">No persisting of message after plsrv call, because of config </Trace>

</Trace>

<Trace level="1" type="Timestamp">2007-08-28T13:57:52Z CAT Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>

<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">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_DUMMY = 0</Trace>

<Trace level="3" type="T">Unknown channel type: File</Trace>

<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_DUMMY = 0</Trace>

<Trace level="3" type="T">Channel for adapter engine: File</Trace>

<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): </Trace>

<Trace level="3" type="T">URL = http://pgsap45:50100/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 level="1" type="Timestamp">2007-08-28T13:57:53Z CAT End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>

</Trace>

<Trace level="3" type="T">No persisting of message after plsrv call, because of config </Trace>

</Trace>

<Trace level="3" type="T">Async processing: skip mapping of response </Trace>

</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Async processing completed OK. </Trace>

<Trace level="3" type="T">system-ID = XIQ</Trace>

<Trace level="3" type="T">client = 300</Trace>

<Trace level="3" type="T">language = E</Trace>

<Trace level="3" type="T">user = XIAFUSER</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="3" type="T">Persisting message Status = 003</Trace>

<Trace level="3" type="T">Message version 002</Trace>

<Trace level="3" type="T">Pipeline CENTRAL</Trace>

</SAP:Trace>

Thanks,

Miguel

Miguel,

Not sure atr all as to why you dont get the Trace

What i found interesting though in the Trace,

<Trace level="3" type="T">Append context with name =Directory and value =/Ibolt/Transactions/Out </Trace>
<Trace level="3" type="T">Append context with name =FileName and value =70018_SendMSG_Payment_0_709_20070807052913.xml </Trace>
<Trace level="3" type="T">Mapping is already determined in the interface determination </Trace>
<Trace level="1" type="T">No mapping required </Trace>

Not sure, if this helps but is the file directory as you want it to be?

Also, in the Integration Directory, in your interface determination can you check if you have selected the correct Interface Mapping?

Am running out of ideas

Regards

Bhavesh

Hi Bhavesh, Raj, and Ravun

Thanks very much for your help!

I feel like such a fool! I had forgotten to change the interface determination to look at the new interface mapping and therefore the new message mapping....

No wonder nothing seemed to work!

I'm going to go home and try grow my hair back, because I think I have just about pulled it all out by now!

Sorry for wasting your time!

Thanks again!

Miguel

Miguel,

Welcome to the club mate Happens to all of us!

Regards

Bhavesh

Answers (1)

Hi Miguel..

Are you sure your target directory path is "/Central/Branches/70018/"???

Is your target directory on your XI server or on some remote network machine??

If it is on your XI server please give the ful path... i.e "C:
Directoryname"

Else it'll bein he format ""

domainname
directoryname""

This naming format is wor windows machines..

For universal OS independent formats give it this way

String directoryName = "C:" + java.io.File.separator + "DirectoryName";

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Varun,

Yes, I'm sure that the directory does exist.

The thing that puzzles me is that if I check the values in the RWB, I can see that the directory that it has there is the source directory. If the directory that I want to use did not exist, it would still place the changed directory into the RWB, but then fail because it couldn't find the directory.

My problem is that it is not actually changing the value of the directory ASMA on the RWB.

Thanks,

Miguel

Well, in that case it seems your UDF is not getting executed...This can happen if the source tag you used for mapping is not at all coming....

Is it possible??

Hi Varun,

I'm sure that the UDF is being executed, because I have used the UDF on a tag that requires an entry. Therefore if the tag was not being populated, then it would fail on the message mapping.

So therefore it must be going through the UDF....

Thanks,

Miguel

Ask a Question

Top Q&A Solution Author

User

Count

ASMA Directory

Accepted Solutions (1)

Accepted Solutions (1)

Answers (1)

Answers (1)

UI5 Build Error when deploying to SAPUI5 ABAP Repo

Re: What is the use of Mapped in SAP RESTFul ABAP ...

ILM Migration: change ILM WebDav Store Provider

Re: Call (submit) VL10B with multiple parameters

Re: Python hdbcli executemany returns minus when t...