AS2 sender communication channel

Hi All,
I have one As2 to proxy scenario, using AS2 sender adapter,PI will be receiving flat file from party and I am performing content conversion in sender As2 channel, there is no mapping involved, and PI is sending this data to SAP system via proxy using integrated configuration.
I have used 2 parties, one sender and one receiver, used 2 business components corresponding to each and one SAP system BC.I have mentioned AS2 ids in both the parties, and did the header mapping for receiver in integrated configuration ->Outbound processing tab.
Now when the file is pushed from AS2 server, there is no log in sender channel monitoring, means the file is not getting picked up from the AS2 server at all.
Can anyone please provide inputs how can we debug this problem.
Thanks,
Ruchi

Hi,
If you are using Seeburger AS2 adapter, then:
1. Check if the URL http://XXXXX:50000/SeeburgerAS2/AS2Server is up. It should show-"405 Method Not Allowed "
2. Check for AS2 messages in Seeburger workbench message-MessageIdStore Monitor
Thanks
Rajeev Gupta

Similar Messages

Error in AS2 sender communication channel

Hello,
We have a scenario where we are receving IDoc XML from our partner via AS2.
While doing so,we are receiving following error:
Error while parsing AS2 message: AUTHENTICATION_ERROR #
When we try to send a normal text file,it works,so this cannot be a certificate related issue.
XML header looks like:
<?xml version="1.0" encoding="windows-1250"?>
<ORDERS05 xmlns:abc="http://abc.xy.net/">
Kindly help.
Thanks.
Best Regards,
Shweta

Hello,
When I sent the same file from our dev to test system via AS2 ,the content type was application/octet-stream and the file was received successfully.
But when our partner sends it via AS2,content type is application/xml and we get the error I mentioned before.
Does content type has something to do with this problem?
Kindly help.
Thanks a lot.
Regards,
Shweta

AS2 Reciver Communication Channel error

Hi,
I am doing FILE to AS2 ...
I configured the Scenatio with Synchronous MDN , I have Created the Sender for MDN report too..
beow is my Error At AS2 reciver Communication Channel...
Message processing failed. Cause: javax.resource.ResourceException: Fatal exception: javax.resource.ResourceException: SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DTREQUEST and DATABASE.., SEEBURGER AS2: AS2 Adapter failure # Outbound configuration error: Failed to get configuration from DTREQUEST and DATABASE..
Thanks

Hi Tom,
This problem comes in SAP PI 7.1 version for resolving you require creation of extra configuration objects u2013
1. A sender AS2 communication channel with protocol as u201Ereports‟
2. A sender agreement using above communication channel.
For more information please refer Article (This will help you in configuring extra objects)
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d095b2df-9fa3-2d10-568b-d12d99828c33?quicklink=index&overridelayout=true
Regards,
Vikrant

Sender Communication Channel for Integration Scenario IDoc - XI - IDoc?

Hello All,
One general question. I have to configure an IDoc - XI - IDoc Scenario. For this Scenario I have to configure an Receiver Communication Channel (IDoc Adapter) to the Backend System but what about Sending Communication Channel for the Sending R/3 system.
Is the (IDoc) Communication Channel from Sending system to XI required to configured?
Many thanks in advanced!
Jochen

Hi Jochen,
for sending IDOCs from SAP to XI, sender IDOC adapter is not required. when XI will send the IDOC to a SAP system, then receiver IDOC adapter is needed.
Thanks,
Rajeev Gupta

BIC Module Error in Sender Communication channel for EDI to File scenario.

Hi Experts,
We are working on the EDI based scenarion where EDI files come to SAP PI from partner and then through Split 997 Adapter Func Ack is sent back to the Partner . But we are facing a issue in our sender Communication Channel which is a File Adapter Channel and uses BIC Module for the conversion of EDI to XML .Request if any one can provide any guidance on the below issue coming in sender CC.
Error: Error in BICMODULE-module:Temporary error: BIC XI Adapter call failed. Reason: 2 errors occured. First error: EdiSegmentData read(): Edifact Format not correct : segment must end with \"segment delimiter\" (Segment : ISA). DESCRIPTION: EdiSegmentData Error: Your Edifact Format is incorrect the segment must end with \"segment delimiter\". check segment [not specified]. Last error: InhouseDocReader moveNext(): com.seeburger.jucon.dochandler.AnsiX12DocReader, offset[92(read Segment : ISA)]: could not parse segment (wrong format): EdiSegmentData: Edifact Format not correct : segment must end with "segment delimiter" (Segment : ISA) DESCRIPTION: InhouseDocReader Error: [not specified] at position [not specified] could not parse the segment [not specified] Error while reading description - wrong format.
Thanks & Regards,
Abhishek

Hi Abhishek,
Is there any special character present in the EDI file?
the parser is not able to parse the data.
you can check the BIC conversion log for more information.
Regards,
Harish

File Structure - Sender Communication Channel

Hi All,
My Sender flat file structure is below like this
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
Filed1|Field2|Field3|Field4|Field5|Field6
I did the Sender Communication Channel configuration - Content Conversion
Document Name : XXX
Document NameSpace: XXXX
Recordset Structure: MT_Test,*
Recordset Sequence: Ascending
Key field Type: String Case-Sensitvie
MT_Test.fieldNames: Filed1,Field2,Field3,Field4,Field5,Field6
MT_Test.fieldSeparator: '|'
MT_Test.additionalLastFileds: ignore
MT_Test.endSeparator : 'nl'
ignoreRecordsetName: true.
But its pick the file, In SXMB_Moni show Currect...
But in Runtime workbench, in Communication Channel moni, it show below like this,
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_Test xmlns:ns0="http://XXXXX">
<JOBS />
</ns0:MT_Test>
What is the Issue, where i missed some thing, In message mapping, its correct..
Thanks.
SR

SR,
I am still little confused with your below statement.
But its pick the file, In SXMB_Moni show Currect...
But in Runtime workbench, in Communication Channel moni, it show below like this,
>
> <?xml version="1.0" encoding="UTF-8" ?>
> - <ns0:MT_Test xmlns:ns0="http://XXXXX">
> <JOBS />
> </ns0:MT_Test>
You mean to say that in MONI, the mapping output is fine, but when you check the output at RWB -> CC Monitoring for the Sender Channel, then you get the above mentioned XML?
This means that there is nothing wrong with your source CC settings. If the entry in RWB -> Sender CC is wrong, your MONI entry will never be right. So, this is really weird.
What is the source structure that you have defined in DT?
Regards,
Neetesh
Edited by: Neetesh Raj on Sep 29, 2009 2:31 PM

Error in sender communication channel

Hi,
I am doing File to RFC scenario in which i am using Standard bapi to get the cost from the sap system
while sending the data in sender communication channel the processing mode is in delete mode but it is not deleting and throwing the error
Error: com.sap.aii.af.service.util.transaction.api.TxManagerException: Unable to roll back transaction: com.sap.engine.services.ts.exceptions.BaseIllegalStateException
this error is from sender communciation channel..
can any one give some inputs for this...
regards,
Kishore

K.P.N.,
i have checked it getting the same error. in moni also administrative cache clear error is coming
do we need to do any workaround...
regards
Kishore

Adapter Module not working in Sender Communication Channel working in recie

Hi
I have written one adapter module. IF i give that Adapter Module in Sender Communication channel its not working. If i give that in Reciever Communication Channel its working. If i mention in both the channels then its working in sender communication channel also.But in only sender communication channel its not working in only reciever communication channel its working Can any one tell me why its happening
Thanks & Regards
Ravi Shankar B
Message was edited by:
        RaviShankar B
Message was edited by:
        RaviShankar B
Message was edited by:
        RaviShankar B

hi
if its problem with my code why its working if i give the adapter module in both the communication channels?If i give in only sender communication channel the module is not invoking. its not showing any auditlogs.Can any one please help me
OUTBOUND is for sender
INBOUND is for reciever right.?
the following code i have written
public ModuleData process(
          ModuleContext moduleContext,
          ModuleData inputModuleData)
          throws ModuleException {
          String SIGNATURE =
               "process(ModuleContext moduleContext, ModuleData inputModuleData)";
          Object obj = null;
          Message msg = null;
          String filename = null;
          AuditMessageKey amk = null;
          try {
               obj = inputModuleData.getPrincipalData();
               msg = (Message) obj;
               System.out.println("&&&&&&&&&&&&&&&&&" + msg);
               if (msg.getMessageDirection().equals(MessageDirection.OUTBOUND)){
                    amk = new AuditMessageKey(msg.getMessageId(),AuditDirection.OUTBOUND);
                    Audit.addAuditLogEntry(amk,AuditLogStatus.SUCCESS,">>>>>>>>>>>>>>> etHostName: Module called"+ i++);
               }else{
                    File filename1 = new File("
10.7.1.43
XI
source","text.txt");
                    filename1.createNewFile();
                    amk = new AuditMessageKey(msg.getMessageId(),AuditDirection.INBOUND);
                    Audit.addAuditLogEntry(amk,AuditLogStatus.SUCCESS,">>>>>>>>>>>>>>> etHostName: Module called"+ i++);
               System.out.println("**************" + amk + "***********");
          } catch (Exception e) {
               Audit.addAuditLogEntry(amk,AuditLogStatus.SUCCESS,">>>>>>>>>>>>>>> GetHostName: Error Module called");
               e.printStackTrace(System.err);
               ModuleException me = new ModuleException(e);
               throw me;
          // Read the channel ID, channel and the module configuration
          try {
               Hashtable mp = (Hashtable)inputModuleData.getSupplementalData("module.parameters");
               if(mp != null){
                    filename = (String)mp.get("FileName");
                    Audit.addAuditLogEntry(amk,AuditLogStatus.SUCCESS,"Host >>> Element Name is set to {0}"+filename );
               }else{
                    Audit.addAuditLogEntry(amk,AuditLogStatus.WARNING,"HostElementName parameter is not set. Default used: HostName.");
                    filename = "FileName";
          } catch (Exception e) {
               e.printStackTrace(System.err);
               Audit.addAuditLogEntry(amk,AuditLogStatus.ERROR,"Cannot read the module context and configuration data");
               ModuleException me = new ModuleException(e);
               throw me;
          try {
               XMLPayload xmlpayload = msg.getDocument();
               DocumentBuilderFactory factory;
               factory = DocumentBuilderFactory.newInstance();
               DocumentBuilder builder = factory.newDocumentBuilder();
               Document document =
                    builder.parse((InputStream) xmlpayload.getInputStream());
               Element rootNode = document.getDocumentElement();
               if (rootNode != null) {
                    Element childElement = document.createElement("filename");
                    childElement.appendChild(document.createTextNode(filename));
                    rootNode.appendChild(childElement);
               // Transforming the DOM object to Stream object.
               TransformerFactory tfactory = TransformerFactory.newInstance();
               Transformer transformer = tfactory.newTransformer();
               Source src = new DOMSource(document);
               ByteArrayOutputStream myBytes = new ByteArrayOutputStream();
               Result dest = new StreamResult(myBytes);
               transformer.transform(src, dest);
               byte[] docContent = myBytes.toByteArray();
               if (docContent != null) {
                    xmlpayload.setContent(docContent);
                    inputModuleData.setPrincipalData(msg);
          } catch (Exception e) {
               e.printStackTrace(System.err);
               Audit.addAuditLogEntry(amk,AuditLogStatus.ERROR,"Cannot read the module context and configuration data");
               ModuleException me = new ModuleException(e);
               throw me;
          return inputModuleData;
Best Regards
Ravi Shankar B
Message was edited by:
        RaviShankar B
Message was edited by:
        RaviShankar B

JMS Sender Communication Channel problem

Hi XI gurus!!
I have a JMS Sender Communication Channel that cannot get information from JMS TIBCO queue.
In defaultTrace.XX.trc I see the following information and errors:
#1.#00144F249F1500C70000087D00002D8300044A22A193A198#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000087E00002D8300044A22A193A201#1207412506993#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000087F00002D8300044A22A193A552#1207412506993#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueSession qsess=198151 qconn=45502 tran=true ackmode=1#
#1.#00144F249F1500C70000088000002D8300044A22A193A670#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Info##Java###Sucessfully created session {0} for profile {1}#2#com.tibco.tibjms.TibjmsQueueSession@3a5f233#
{GenericConnectionProfileImpl
{Description=ConnectionProfile of channel: JMS_Sender_loginCheckReq_001on node: 21291150 having object id: 7e7ee107bc2031d2bc79fa2fce15bbed,
JmsMessageSelector=,
ConnectionFactoryConstructor=null,
ConnectionFactoryFactoryInvocation=null,
ConnectionFactoryInvocations=[],
DestinationConstructor=
{ConstructorInvocation
{className=null,
invokeParams=[]
DestinationInvocations=[],
MessageInvocations=[],
DestinationName=null,
User=,
Password=,
isJmsSessionTransacted=true,
InitialContextEnvironment={java.naming.provider.url=190.10.0.133:9222, java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory},
LookupConnectionFactory=QueueConnectionFactory,
LookupDestination=GALP.PRD.TIGERC.LOGIN.REQ,
SerializedConnectionFactoryPath=null,
SerializedDestinationPath=null,
Flags=0000000000000000000000000000000000000000000000000000100000000010
#1.#00144F249F1500C70000088100002D8300044A22A193A7EE#1207412506994#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildSessions()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088200002D8300044A22A193A85F#1207412506994#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088300002D8300044A22A193B153#1207412506997#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Error##Plain###2008-04-05 17:21:46 [161906789 SAPEngine_Application_Thread[impl:3]_52] [TIBCO EMS]: createQueueConnection qconn=45503 qconfac=QueueConnectionFactory[url=tcp://190.10.0.133:9222;clientID=null;Properties={}] user=null#
#1.#00144F249F1500C70000088400002D8300044A22A193E3CF#1207412507009#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088500002D8300044A22A193E571#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1500C70000088600002D8300044A22A193E64B#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeDestinationInvocations#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Exiting method#
#1.#00144F249F1500C70000088700002D8300044A22A193E714#1207412507010#com.sap.aii.adapter.jms.core.connector.ConnectorImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildMessageProducers()#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#SAPEngine_Application_Thread[impl:3]_52##0#0#Path##Plain###Entering method#
#1.#00144F249F1508770000000000002D8300044A22A83A6308#1207412618584#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: received msg from daemon conn=45502 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
#1.#00144F249F1508770000000100002D8300044A22A83A650C#1207412618585#System.err#sap.com/com.sap.xi.mdt#System.err#EFFIGUEIREDO#7191##sappix02_X02_21291150#XIAPPLUSER#81664000032811ddaadc00144f249f15#Thread[TIBCO EMS TCPLink Reader (45502),5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###2008-04-05 17:23:38 [2092826462 TIBCO EMS TCPLink Reader (45502)] [TIBCO EMS]: post msg to session sess=198151 cons=261547 seqid=40664365 msgid=ID:EMS-SERVER.91446ECB042B480:12545#
In the last two lines we can see that SAP XI do a connection to TIBCO and is getting an unknown error, even in debug (note 856346) I cannot get any information.
Actually we are running SAP XI 3.0 SP21, but this was working fine in SAP XI 3.0 SP17. We have more than 100 Communication Channels working fine and only is having this strange behavior.
BTW if we put manually information in TIBCO QUEUE it works fine, but automatically doesn't pick the message.
Thanks

HI,
As per the trace details given please consider few of the below options....
What do u see in adapter monitoring tool for JMS adapter?
http://hostname:5XX00/mdt/amtServlet
Did you follow the document on correlation of JMS messages?
In communication channel You have to set
Correlation ID -> XI conversationID
XI message ID->GUID
XI Conversation ID -> JMS correlation ID.
Now in the custom J2EE application you should set
jmscorrelationid of message before sending in to queue to jms correlation id of message before receiving from the queue.
This thread deals with the issue..
JMS Queue monitoring
Check if the JMS Sender adapter EOIO is with serialized messages
Thanks
Swarup

JMS sender communication channel content conversion

Hi,
I struck with the content conversion in the JMS Sender communication channel.
I have configured the communication channel with the filed fixed lengths. (Simple type)
The field fixed lengths i have given are 10,2,3,11
The contents in the file 1000000072 230 111
but, in the input xml after conversion iam getting 100000007 in the first field and 2 in the second field 23 in the third field.
I have configured the sender communication channel as in the document in SDN.
Even, i configured several communication channels. I didn't get this strange error any time.
I have gone through SDN to fix this issue, but i didn't get solution.
If anyone got rectified this kind of error, please answer your solution to me
Thanking you,
Regards,
Krishnaraju.

Hi,
Thanks for all your support. The issue got resolved.
The issue is due to the file, In the file the special characters are appearing. We are not able to see these characters in the notepad, wordpad, text editor.
But, these characters are appearing in th syn text editor. So, we removed those characters and processessed the file. Now, it is successfull.
Regards,
Krishnaraju.

JMS (Sender Communication Channel) and MQ in Mainframe (Legacy) System

Hi All,
Can we use JMS Sender Communication Channel in XI that runs on Windows 2003 server to DIRECTLY poll messages from MQ in Mainframe (Legacy) system??
I understand that we can install MQ on XI server and have mainframe push the messages to XI MQ so that JMS can poll but wanted to see if there is a way to do this without having MQ on XI server.
If you know of any documentation regarding this, can you please post it?
Thanks,
Jay

Jung,
Are you looking for this help:
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
Also check this sap help:
http://help.sap.com/saphelp_nw04/helpdata/en/cd/d85a9d6fab7d4dbb7ae421f710626c/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
---Satish

JDBC Sender Communication Channel Problem

Hello everybody,
I have a sender communication channel, it is with green Functioning status in channel monitor in runtime workbench, and the log says "Process started" for every pool as configured, but it doesn't return any data to XI, and there's data to be taken, the problem started a few hours cause it was working fine, I've already executed a Complete refresh cache in SXI_CACHE, and changed the channel from Active to Inactive in ID, and Stopped and Started it again in RW, it doesn't give any errors, but it doesn't bring back any data that should be, any suggestions or maybe any information on how to refresh totally those channels????, thanks in advance.
Regard's
Paul

Hi Paul
Check for JDBC adapter locks. cpa cache locks are not relevant to your problem.
Moreover check with the visual admin logs as well. if you can get info about the issue you have
Thanks
Gaurav

Inactive Sender Communication Channel still processing Files?

We de-activated the Sender Communication Channel of an interface. However, the file adapter keeps processing?
Anybody know what is going on?
Thank-You.

Hi Tom,
1) Check out Whether you have De-activated the Right Adapter.
2) Refresh the Cache,
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
c)Call transaction SM58 to check the status of the refresh process.If no entry for function module SAI_CACHE3_REFRESH_BACKROUND is Present any more the cache update is finished.
If you still face issue try this .
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss

Regd Sender Communication channel

Hi all,
I have configured a sender communication channel for picking a file. Everything looks fine to me, but the file is not getting picked up.
I checked in RWB for channel, channel is configured fine.its says processing started, and processing finished successfully.No message ID is showing.But the file is not getting picked from the location.
In moni , no messages to display.
can you suggest how to trace out the possible error? the path and file names are perfect, check it number of times.

Hi Anika,
in sender file comm channel, set the processing mode to delete and activate it.............
then in source file system, ask the file system guys to check the file permissions of the source file........it should have read, write, execute for others............
then your source file should be picked.........if still your source file is not getting picked, then ask your basis guys to do a full CPACache refresh using PIDIRUSER and then re-run your scenario......
Regards,
Rajeev Gupta

PI sender communication channel not reading files from NFS directory

Hello,
I have a sender communication channel configured to read file from NFS directory which is on ECC server. A program in ECC generates the file and puts it on the ECC server in the output directory. PI sender communication channel is supposed to pickup this file and process it. If I give the NFS path as the source directory, I am getting error: Configured source directory '//Server/DIR/OUT' does not exist. I tried putting '
Server\DIR\OUT' too but same error. Do I have to add the NFS path of ECC into PI as logical path?
Any suggestions?
Thanks,
Sangita

Hello Sangita,
Your ECC server is an external system, therefore you need to activate FTP service in that system and use the transport protocol FTP:
http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
You can use NFS protocol when you have a local directory in XI server.
Best Regards,
.Luis Bernal.

AS2 sender communication channel

Similar Messages

Maybe you are looking for