File adapter Deployment issue

Hi,
I have a process that use a file adapter which polles a certain directory.
I am developing on windows XP and I am deploying to a Linux
I can't leave the path of this directory as it is since it will not be recognized in the linux server
How do I solve this issue?
Amit

You can specify the Logical Name of the directory from which you want to read the file from. In the BPEL partner link of the bpel.xml file, you then provide the physical parameter value for the Logical Name. This resolves the mapping between the logical directory name and actual physical directory name.
For example you can specify Logical Name as InputFileDir and in the bpel.xml specify the physical value against the partner link for that file adapter, as following :
<property name="InputFileDir">C:/ora_home/integration/bpm/samples/tutorials/
121.FileAdapter/ComplexStructure/InputDir/</property>
So while development, you can specify the physical directory as in your Windows system, and at deployment you can specify the directory as in your linux system.
Rahul

Similar Messages

  • File Adapter Archiving Issue

    Hi,
    THe file adapter archives the file, it doesn't save the entire contents of the file in the archive folder, but saves the first recordset (row) only in XML format. Did any body face similar issue, and what's the resolution to archive the contents of the file, the way it was sent.
    Thanks
    Pandari

    Hi Anil,
    Refer Archiving concepts in below links.
    http://help.sap.com/saphelp_nw73/helpdata/en/44/682bcd7f2a6d12e10000000a1553f6/content.htm?frameset=/en/44/6830e67f2a6d12e10000000a1553f6/frameset.htm
    http://scn.sap.com/docs/DOC-35572
    Warm Regards,
    DNK Siddhardha.

  • File Adapter: FTP issue

    Hello,
    There is a problem with the file adapter of the XI30 SP14:
    It is set to get a file from a server X using a FTP protocol.
    INT_001_V01_COM_CTDCLNT600_FILE_SENDER
    Sender Adapter v2300 for Party '', Service 'CTDCLNT600':
    Configured at 2006-01-16 15:13:52 EST
    History:
    - 2006-01-16 15:23:54 EST: Polling interval started. Length: 60.000 s
    - 2006-01-16 15:23:54 EST: Processing finished successfully
    - 2006-01-16 15:23:52 EST: Processing started
    - 2006-01-16 15:22:54 EST: Polling interval started. Length: 60.000 s
    - 2006-01-16 15:22:54 EST: Processing finished successfully
    It seems everything is working fine, but the in the SXMB_MONI transaction, no message appears.
    I have accessed the FTP manually and I have downloaded the file, so the connectivity issue is descarted.
    Any suggestion.
    Jesus Barba Lobaton

    Hello all,
    The current configuration of the Sender file adapter is:
    Transfer protocol: FTP
    Message protocol: File Content Conversion
    Adapter Engine: Integration Server
    Source Directory: /out
    File: D_P.DAT
    In FTP: the file D_P.DAT is placed under /out directory
    Server: Server Internal IP
    Port: 21
    Connection security: None
    User: userX
    Pass: FTPuserX
    Quality of Service: Exactly once
    Poll Intervals: 60
    Processing mode: Delete
    File Type: Binary
    How can I verify a log of the processing process? as the SXMB_MONI transaction does not show anything.
    The most frustrating of all, is no error message appears. I have verified the XI, APPS and default trace logs with log viewer but there is nothing.
    I have also checked this thread but none of the solution provide solved the issue
    Pbm in File adapter..Post Sp14
    OS: Windows 2003
    Any idea?
    Jesus

  • File-to-file --File adapter deployment

    Hi all,
    When I'm trying to create communication chanel, unable to see File adapter.
    How to check whether file adapter was deployed are not.
    Regards,
    venu

    hi,
    try question 3 in the Adapters section
    on the XI FAQ page
    maybe your configuration was not done completely
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

  • Socket connection time Out - Sender File adapter (Intermittent Issue )

    Dear FrIends,
    In our sender file adapter i am getting the following issue:
    I have already places timout : 120 secs.
    This isssue is occuring intermittently.
    Error occurred while connecting to the FTP server "100.142.131.30:21": java.net.ConnectException: Socket connection timed out: 100.142.131.30:21

    Hi Renu,
    You need to increase the timeout Seconds and check.
    Run the report RSFTP002.
    and check whether the connection to FTP works. Provide the below parameters:
    user = <your ftp user>
    pwd = <your ftp pwd>
    host= <your ftp host/ip>
    command1 = <ls>
    RFC Dest = SAPFTP
    Compress = N
    If the issue still exists, then check  with your BASIS Team.
    http://www.sap2048.com/socket-and-connection-issues-in-java-web-services-1351.htm
    Thanks,

  • File Adapter Append issue

    Hi Iam trying to write a write a file in append mode using a file adapter(on a file which already exits)...but it says...file already exists...What might be the issue...?
    Thanks in advance!
    Larry

    Hi Guys,
    I shall explain the issue Iam having...Iam using the File Content Parameters..and the output is a plaint text file(Flat File).We are using Dynamic file configuration to populate the file name as per our requirements.When I dont use the dynamic config...(giving the name in the communication channel) the file is created @ the first time and its getting appended the next time..But when I use the Dynamic Configuration the file is not getting appended and it leaves an error saying the file is already there and cannot be overwritten...
    Please advise!
    Thanks in advance!

  • File Adapter Polling issue(Is there critical value of File size )?

    Hi
    I use File adapter as the Activation to initialize a BPEL process instance .The source data is a kind of Delimited file format.On my PC, when the file size is less than 4M ,everything works fine ,But when the size increased. The BPEL process will not initialize the instance.When the source data is XML data , the "critical value " is about 12M. The error msg is below.
    <2005-08-08 12:48:26,209> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Processing file : D:\Temp\WOSSystemIntegration\InBoundFiles\LOADPLAN_DATA_200508041708.xml
    <2005-08-08 12:48:29,455> <INFO> <default.collaxa.cube.activation> <FileAdapter::Inbound> Sending message to Adapter Framework for posting to BPEL engine: { file=D:\Temp\WOSSystemIntegration\InBoundFiles\LOADPLAN_DATA_200508041708.xml
    <2005-08-08 12:48:40,197> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::l
    ogError> Error while invoking bean "cube delivery": Delivery callback message se
    rialization failed.
    An attempt to serialize the delivery callback messages for conversation "LocalGU
    ID:d0b7ccf8e4242850:134b07e:10594606738:-7ffc", message "d0b7ccf8e4242850:134b07
    e:10594606738:-7ffb" to binary format has failed. The exception reported is:
    <2005-08-08 12:48:40,245> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::l
    ogError> Error while invoking bean "delivery": Delivery callback message seriali
    zation failed.
    An attempt to serialize the delivery callback messages for conversation "LocalGU
    ID:d0b7ccf8e4242850:134b07e:10594606738:-7ffc", message "d0b7ccf8e4242850:134b07
    e:10594606738:-7ffb" to binary format has failed. The exception reported is:
    <2005-08-08 12:48:40,245> <ERROR> <default.collaxa.cube.activation> <AdapterFram
    ework::Inbound> [Read_ptt::Read(loadPlanCollection)] - JCA Activation Agent was
    unable to perform delivery of inbound message to BPEL Process 'bpel://localhost/
    default/P2E_WOS_LP~1.0/' due to: Delivery callback message serialization failed.
    An attempt to serialize the delivery callback messages for conversation "LocalGU
    ID:d0b7ccf8e4242850:134b07e:10594606738:-7ffc", message "d0b7ccf8e4242850:134b07
    e:10594606738:-7ffb" to binary format has failed. The exception reported is:
    <2005-08-08 12:48:40,245> <ERROR> <default.collaxa.cube.activation> <AdapterFram
    ework::Inbound>
    com.oracle.bpel.client.ServerException: Delivery callback message serialization
    failed.
    An attempt to serialize the delivery callback messages for conversation "LocalGU
    ID:d0b7ccf8e4242850:134b07e:10594606738:-7ffc", message "d0b7ccf8e4242850:134b07
    e:10594606738:-7ffb" to binary format has failed. The exception reported is:
    at com.collaxa.cube.engine.delivery.DeliveryHandler.initialPostAnyType(D
    eliveryHandler.java:328)
    at com.collaxa.cube.engine.delivery.DeliveryHandler.initialPost(Delivery
    Handler.java:219)
    at com.collaxa.cube.engine.delivery.DeliveryHandler.post(DeliveryHandler
    .java:83)
    at com.collaxa.cube.ejb.impl.DeliveryBean.post(DeliveryBean.java:181)
    at IDeliveryBean_StatelessSessionBeanWrapper22.post(IDeliveryBean_Statel
    essSessionBeanWrapper22.java:861)
    at com.oracle.bpel.client.delivery.DeliveryService.post(DeliveryService.
    java:161)
    at oracle.tip.adapter.fw.AdapterFrameworkListenerBase$DeliveryServiceMon
    itor.send(AdapterFrameworkListenerBase.java:2340)
    at oracle.tip.adapter.fw.AdapterFrameworkListenerBase.executeDeliverySer
    viceSend(AdapterFrameworkListenerBase.java:478)
    at oracle.tip.adapter.fw.AdapterFrameworkListenerBase.deliveryServiceSen
    d(AdapterFrameworkListenerBase.java:535)
    at oracle.tip.adapter.fw.jca.AdapterFrameworkListenerImpl.performSingleA
    ctivation(AdapterFrameworkListenerImpl.java:699)
    at oracle.tip.adapter.fw.jca.AdapterFrameworkListenerImpl.onMessage(Adap
    terFrameworkListenerImpl.java:567)
    at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage
    (MessageEndpointImpl.java:121)
    at oracle.tip.adapter.file.inbound.ProcessWork.publishMessage(ProcessWor
    k.java:651)
    at oracle.tip.adapter.file.inbound.ProcessWork.doTranslation(ProcessWork
    .java:456)
    at oracle.tip.adapter.file.inbound.ProcessWork.processMessages(ProcessWo
    rk.java:200)
    at oracle.tip.adapter.file.inbound.ProcessWork.run(ProcessWork.java:139)
    at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
    at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
    at java.lang.Thread.run(Thread.java:534)
    <2005-08-08 12:48:40,245> <INFO> <default.collaxa.cube.activation> <File Adapter
    ::Inbound> Failed to send message {D:\Temp\WOSSystemIntegration\InBoundFiles\LOA
    DPLAN_DATA_200508041708.xml} to Adapter Framework.
    <2005-08-08 12:48:40,245> <WARN> <default.collaxa.cube.activation> <AdapterFrame
    work::Inbound> [Read_ptt::Read(loadPlanCollection)] - onReject: Sending invalid
    inbound message to Exception Handler: file://D:/Temp/WOSSystemIntegration/Reject
    edMessages
    <2005-08-08 12:49:44,617> <FATAL> <default.collaxa.cube.activation> <AdapterFram
    ework::Inbound> [Read_ptt::Read(loadPlanCollection)] - Resource Adapter requeste
    d Process shutdown
    <2005-08-08 12:49:48,676> <INFO> <default.collaxa.cube.activation> <AdapterFrame
    work::Inbound> Adapter Framework instance: OraBPEL - performing endpointDeactiva
    tion for portType=Read_ptt, operation=Read
    <2005-08-08 12:49:48,676> <INFO> <default.collaxa.cube.activation> <File Adapter
    ::Inbound> Endpoint De-activation called in adapter for endpoint : D:\Temp\WOSSy
    stemIntegration\InBoundFiles
    <2005-08-08 12:49:49,042> <INFO> <default.collaxa.cube.activation> <AdapterFrame
    work::Inbound> JCAActivationAgent::onStateChanged State is changed for process '
    bpel://localhost/default/P2E_WOS_LP~1.0/', state=OFF
    how can i solve this problem?can i predeploy some parameter? Is there some critical value of File size for the processing of File Adapter ?

    Hi,
    There is no specific parameters to specify the maximum file size to be read in. It is just limited by the heap size of the JVM running the BPEL engine.
    If you have enough RAM on your machine you can change the current heap size from 512Mbyte to 1Go by editing the startorabpel.bat file
    and modifying the line :
    set MEM_ARGS=-Xms512m -Xmx512m -Xmn300m -XX:MaxPermSize=80m
    to
    set MEM_ARGS=-Xms512m -Xmx1024m -Xmn300m -XX:MaxPermSize=80m
    But only do it if you have at least 1.5 Gb of RAM on your machine, otherwise ot will keep spawing and you will have very bad performance.
    Speaking about performance, do you really need to have a BPEL payload of 4 to 12 Mb ?
    Will the BPEL process really need to access it ? if so, the best solution would be using batching techniques to cut you file in pieces and process it piece by peice.
    FB.

  • File Adapter Format Issue:.csv target

    Hello
    When i am trying to write information from DB to a file as a CSV format it is always writing into xml format, though it is named with .csv extension.
    When you want to write the File as html target i need to do a html encoding but how to do it in another format like .csv?
    Appreciate your help on this

    you can refer this..
    http://docs.oracle.com/cd/B31017_01/integrate.1013/b28994/nfb.htm#CCGEGFDB
    You need to create "JCA File Adapter with NXSD format definition" as mentioned in above link.

  • File adapter - Archive issue with adapter module

    Hi All,
    I have 2 issues here. We are currently using PI 7.11 EHp1 SP02.
    1. Arhival with "add time stamp" wont work. It just gives us an error message saying simpledate format exception.
    I have gone through the OSS note 1265534 and thought this will resolve the issue. But our BASIS team believes this note is only applicable for PI 7.1 SP01. Can you one using PI 7.11 SP02 comment on this?
    Note: Archive option with out add time stamp works fine.
    2. When I use adapter module in my sender file configuration, the archive option itself does not work. Read the official SAP help which says "To archive source files where a permanent error occurred during processing, set the indicator.
    A permanent error occurs either during the conversion of the file content, or in a module in the module processor."
    So the question here is, how do we make the error permanent? The only way to throw error from adapter module is using the ModuleException. It has 4  different constructors. I have used both
    ModuleException me = new ModuleException ("My error Msg"); and
    Module Exception me1 = new ModuleException ("Error String", new Throwable("My error Msg");
    In both the cases, the archival wont happen.
    Any ideas welcome.
    Thanks
    Jai

    Hi,
    I am using NFS protocol here not FTP. Sorry I dint mention that earlier.
    Thanks
    Jai
    Edited by: Jaishankar on Apr 1, 2010 9:55 AM
    Edited by: Jaishankar on Apr 6, 2010 11:10 AM

  • Receiver File Adapter - Encoding issue.

    Hi Everybody,
    The file format (encoding) is different to the format generally we used to get.
    Currently we are get the flat files in DOS format.The current file when we are downloading it we are getting it in the UNIX or other format.
    For eg: 20 has been changed to 0D in the file.
    Can somebody help me on the same.
    Thanks,
    Zabiulla

    Hi,
    Check on this for file adapters
    Text
    Under File Encoding, specify a code page.
    The default setting is to use the system code page that is specific to the configuration of the installed operating system. The file content is converted to the UTF-8 code page before it is sent.
    Permitted values for the code page are the existing Charsets of the Java runtime. According to the SUN specification for the Java runtime, at least the following standard character sets must be supported:
    &#9632;       US-ASCII
    Seven-bit ASCII, also known as ISO646-US, or Basic Latin block of the Unicode character set
    &#9632;       ISO-8859-1
    ISO character set for Western European languages (Latin Alphabet No. 1), also known as ISO-LATIN-1
    &#9632;       UTF-8
    8-bit Unicode character format
    &#9632;       UTF-16BE
    16-bit Unicode character format, big-endian byte order
    &#9632;       UTF-16LE
    16-bit Unicode character format, little-endian byte order
    &#9632;       UTF-16
    16-bit Unicode character format, byte order
    Regards
    Vijaya

  • OSB Error in deploying a project with jca file adapter

    Hi,
    I am facing an issue where I am getting an error when deploying a service from Eclipse. I am using OSB/SOA 11.1.1.5 2 node cluster. I have an OSB service where I am writing to a file and am using file adapater. I created a composite with file adapter to write a file then imported .jac, .wsdl and composite into eclipse and generated a business service out of .jca file. When I deploy the project from eclipse I am getting the below error and am not able to deploy the project.
    Conflicts found during publish.
    Invalid JCA transport endpoint configuration, exception: javax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
    Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
    I have FileAdapter deployed and pointed to OSB manage servers cluster. Here is a snippet of config.xml.
    <app-deployment>
        <name>FileAdapter</name>
        <target>SOA_Cluster,OSB_Cluster</target>
        <module-type>rar</module-type>
        <source-path>/app/oracle/fmw/Oracle_SOA1/soa/connectors/FileAdapter.rar</source-path>
        <deployment-order>321</deployment-order>
        <plan-dir xsi:nil="true"></plan-dir>
        <plan-path>/app/oracle/shared/SOA_Cluster/dp/FileAdapterPlan.xml</plan-path>
        <security-dd-model>DDOnly</security-dd-model>
        <staging-mode>nostage</staging-mode>
      </app-deployment>
    Also inside console -> deployments  -> FileAdapter -> Targets and OSB_Cluster is checked also.
    Here is the .jca file
    <adapter-config name="writeFile" adapter="File Adapter" wsdlLocation="writeFile.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
      <connection-factory location="eis/HAFileAdapter"/>
      <endpoint-interaction portType="Write_ptt" operation="Write">
        <interaction-spec className="oracle.tip.adapter.file.outbound.FileInteractionSpec">
          <property name="PhysicalDirectory" value="C:\ORACLE"/>
          <property name="Append" value="false"/>
          <property name="FileNamingConvention" value="a_%SEQ%.doc"/>
          <property name="NumberMessages" value="1"/>
        </interaction-spec>
      </endpoint-interaction>
    </adapter-config>
    Any idea what might be wrong.
    Thanks.

    I already have the fileAdapter JNDI is already configured in console. The error I am getting is during the deployment
    Conflicts found during publish.
    Invalid JCA transport endpoint configuration, exception: javax.resource.ResourceException: Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
    Cannot locate Java class oracle.tip.adapter.file.outbound.FileInteractionSpec
    Thanks

  • File adapter issue in Linux enviornment

    hi'
    I am deploying BPEL in Linux enviornment, and with the file adapter read operation I am reading a test.xml file this file is internally refering to emp.xsd (files are below), now the issue is the file adapter is reading XML file even if it is invalid, this was not the case in windows XP enviornment, please advice why it is behaving like this.
    Also the path of my XSD is "/home/wsfbpel/public_html/XSD" and the file has all read write permission (chmod 777 filename)
    XSD
    *<?xml version="1.0" encoding="windows-1252" ?>*
    *<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"*
    xmlns="http://www.example.org"
    targetNamespace="http://www.example.org"
    elementFormDefault="qualified">
    *<xsd:element name="readfile">*
    *<xsd:complexType>*
    *<xsd:sequence>*
    *<xsd:element name="name" type="xsd:string"/>*
    *<xsd:element name="empid" type="xsd:string"/>*
    *</xsd:sequence>*
    *</xsd:complexType>*
    *</xsd:element>*
    *</xsd:schema>*
    XML (this is clearly invalid with respect to XSD it is refering to)
    *<?xml version="1.0" encoding="utf-8"?>*
    *<!-- Created with Liquid XML Studio Developer Edition (Trial) 8.1.2.2399 (http://www.liquid-technologies.com) -->*
    *<tns:readfile xmlns:tns="http://www.example.org"*
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.example.org /home/wsfbpel/public_html/XSD/emp.xsd">
    *     <tns:name>yatanveersingh</tns:name>     *
    *     <tns:empidname>6499</tns:empidname>* +(incorrect element name)+
    *</tns:readfile>*
    thanks
    Yatan

    Hi,
    My problem got resolved.
    There was some access issue to see the txt files at the File Directory.
    Thanks.

  • File Adapter vs BPEL interaction issue on high availability environment

    Hi all,
    i would really appreciate your help on a matter i'm facing about a composite (SCA) deployed on a clustered environment configured for high availability. To help you better understand the issue i briefly describe what my composite does. Composite's instances are started by means of an Inbound File Adapter which periodically polls a directory in order to check if any file with a well defined naming convention is available. The adapter is not meant to read the file content but only its properties. Furthermore, the adapter automatically makes a backup copy of the file and doesn't delete the file. Properties read by the adapter are provided to a BPEL process which obtains them using the various "jca.file.xyz" properties (configurable in any BPEL receive activity) and stores them in some of its process variables. How the BPEL process uses these properties is irrilevant to the issue i'd like to pose to your attention.
    The just described interaction between the File Adapter and the BPEL process has always worked in other non-HA environments. The problem i'm facing is that this interaction stops to work when i deploy the composite in a clustered environment configured for high availability: the File Adapter succeeds to read the file but no BPEL process instance gets started and the composite instance gets stuck (that is, it keeps always running until you don't manually abort it!).
    Interesting to say, if I put a Mediator between the File Adapter and the BPEL, the Mediator instance gets started, that is the file's properties read by the adapter are passed to the mediator, but then the composite gets stuck again 'cos even the mediator doesn't seem to be able to initiate the BPEL process instance.
    I think the problem lies in the way i configured either the SOA infrastructure for HA or the File Adapter or BPEL process in my composite. To configure the adapter, i followed the instructions given here:
    http://docs.oracle.com/cd/E14571_01/integration.1111/e10231/adptr_file.htm#BABCBIAH
    but maybe i missed something. Instead, i didn't find anything about BPEL configuration for HA with SOA Suite 11g (all the material i found refers to SOA Suite 10g).
    I've also read in some posts that for using the db as a coordinator between the file adapters deployed on the different nodes of the cluster, the db must be a RAC! Is that true or is possible to use even another type of oracle db?
    Please, let me know if someone of you has already encountered (and solved :)) a problem like this!
    Thanks in advance,
    Bye!

    Hi,
    thanks for your prompt reply. Anyway, i had already read through out that documentation and tried all settings suggested in it without any luck! I'm thinking the problem could be related to the Oracle DB used in the clustered environment, which is not RAC while all documentation i read about high availability configuration always refers to a RAC db. Anyone knows if a RAC Oracle DB is strictly needed for file adapter configuration in HA cluster?
    Thanks, bye!
    Fabio

  • Regarding issue sender file adapter in clustered  environment(PI 7.0)

    Hi Experts,
    we  are using  sender  file adapter in clustered environment(there are 6 J2EE cluster nodes in XI system) for an interface.the  file sender communication channel  for this interface  is scheduled to run twice  every day. recently   the   channel stopped polling (picking the files from the source directory) and i dont see any error.
    when i open Communication Channel monitoring in RWB and select the file sender communication channel  and run it manually, none of the cluster nodes  are polling for the file.
    i have tried   editing the communication channel in Integration Directory   and  activating  it. but it does not pick the file.
    Can you let me know how  the issue can be resolved.
    Thanks
    -Kaushik
    Edited by: Kausik M on Dec 18, 2008 4:13 AM

    Kausik,
    A computer cluster is a group of linked computers, working together closely so that in many respects they form a single computer. The components of a cluster are commonly, but not always, connected to each other through fast local area networks. Clusters are usually deployed to improve performance and/or availability over that provided by a single computer, while typically being much more cost-effective than single computers of comparable speed or availability.
    clearly your cluster nodes are out of sync...!!!!
    It is possible that your ftp server went down for a while . And in the profile of FTP machine the entry of XI server is not made permanent .
    1. Try to ping the FTP site from XI server.
    BTW are u getting any error msg at RWB ?
    Regards,

  • File Adapter Issue: Not functioning when used with BIC user modules

    Hi! ALL
    We have been experiencing issue with file adapter, when we SeeBurger BIC user modules in sender file - FTP communication channel.
    The regular FTP functionality is working fine if do not have BIC user modules defined under the module tab.However, when put in BIC user module parameters it is not picking up the file.
    Also, we do not see any error logs; even the communication channel monitoring does not show any error log....only show the polling interval success, without the file being picked up.
    This issue started appearing once we deployed our new sda file....as we changed our BIC mapping.
    We can try doing back to our previous sda file....to see it fixes the problem.
    But, before doing that ....we would like to know where the cause of this issue....Can you point us to any error logs we can find on the PI server.
    Your help is greatly appreciated!!
    Thank you,
    Patrick.

    If you configured your logging correctly you should find in the log folders
    ./applications/com.seeburger.jucon/
    ./applications/com.seeburger.bicxiadapter/
    Try to scan those for recent errors - if the no log files can be found you should check the defaultTrace.

Maybe you are looking for