Capability of File Adapter Framework in OSB

Hi,
Has anyone ever used the file adapter framework within Oracle Service Bus to capture data / transform using XSLT and then publish that data out to a service?
Would greatly appreciate any experiences in this area, I know that this functionality exists in SOA suite and can be enhanced with BPEL.
If anyone know of any limitations of OSB in this area that would also be good to know.
Thanks
K

Hi,
There's no problem in doing this. You can use a file adapter or the file transport.
When using the file transport, it is possible to convert a flat-file structure to XML (and vice-versa) by using MFL. For more information on MFL: [http://biemond.blogspot.com/2008/12/flat-file-to-xml-with-oracle-service.html]

Similar Messages

  • File Adapter debatching in OSB

    Hi,
    I have to debatch a large XML file using File Adapter. I imported the JCA service into OSB project and the debatching works well. Now I need to find out if the current batch is the last batch read from the file? Is there some property etc to find this?
    Thanks for your help.
    Regards,
    sagol

    Thanks !
    I am now facing another problem:The flow is like this
    Proxy Service polls the data --->Business Service--->File
    My requirements are:
    1.convert this into csv--> For this I have created a MFL and used XQuery to map from the database xsd to the MFL
    2.Updated the BS to use MFL.(A small doubt:Where do I specify that I file to be written is csv)
    3.Where do I specify the name of the file to be written
    4.In the proxy service I used routing to the BS.But I didnot apply the messaging constructs such as assign,insert etc ..But the csv file is not written by BS(actually I donot know the usage)
    Please let me know if I am missing any step!
    The error message it shows
    <Jun 17, 2009 7:37:19 PM IST> <Error> <JCATransport> <BEA-381951> <JCA inbound r
    equest only invocation failed, exception: java.security.PrivilegedActionExceptio
    n: com.bea.wli.sb.transports.TransportException: General runtime error: Failed t
    o transform MFL content from XML to binary
    java.security.PrivilegedActionException: com.bea.wli.sb.transports.TransportExce
    ption: General runtime error: Failed to transform MFL content from XML to binary
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
    dSubject.java:373)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.security.Security.runAs(Security.java:61)
    at com.bea.wli.sb.transports.jca.binding.JCAInboundRequestListener.sendM
    essage(JCAInboundRequestListener.java:156)
    at com.bea.wli.sb.transports.jca.binding.JCAInboundRequestListener.post(
    JCAInboundRequestListener.java:71)
    Truncated. see log file for complete stacktrace
    com.bea.wli.sb.transports.TransportException: General runtime error: Failed to t
    ransform MFL content from XML to binary
    at com.bea.wli.sb.transports.TransportException.newInstance(TransportExc
    eption.java:195)
    A lot of thanks!!!
    Regards
    Prabal
    Edited by: user123 on Jun 17, 2009 7:08 AM

  • File Adapter in OSB 11g

    Hi
    I am using a File Adapter created to read a file using OSB 11.1.1.3.0. But after i publish that osb project, i am getting the below warning and file is not been polled by the proxy.
    ####<Feb 23, 2011 10:08:30 AM IST> <Warning> <JCA_FRAMEWORK_AND_ADAPTER> <wipro-e16351a68> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <dcc2d8a908de630a:59887477:12e50cc23d3:-7ff2-0000000000000084> <1298435910015> <BEA-000000> <PollWork::run exiting, Worker thread will die>
    After 600 secs i could see StuckThread error in server.
    ####<Feb 23, 2011 10:15:01 AM IST> <Error> <WebLogicServer> <wipro-e16351a68> <AdminServer> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <dcc2d8a908de630a:59887477:12e50cc23d3:-7ff2-0000000000000092> <1298436301203> <BEA-000337> <[STUCK] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "601" seconds working on the request "weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl@dd20cd", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
         java.lang.Object.wait(Native Method)
         oracle.tip.adapter.file.inbound.FilesToProcess.dequeueToProcess(FilesToProcess.java:101)
         oracle.tip.adapter.file.inbound.ProcessWork.run(ProcessWork.java:269)
         weblogic.work.ContextWrap.run(ContextWrap.java:41)
         weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
         weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Please help what is going wrong in my approach.
    Thanks,
    Sesha

    I even tired creating a new WM thread and assigned to this proxy.
    I have chosen MaxThreadsConstraint option with Maximum of 5 concurrent thread.
    Also i have enabled Ignore Stuck Threads in that WM thread.
    Now i dont see any thread stuck in the server log, but sametime the file is not been picked by the Proxy which means the error is suppressed alone from displaying in logs..
    Thanks,
    Sesha

  • 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 Transactional in SOA and OSb

    Hi All,
    Is file adapter transactional in SOA and OSB. I have a requirement where a inbound file adapter polls for a file and it is consumed by a topic.If topic is down,how can I know that the same file will goes to topic when is up(how can I make it transactional).I want to do this both in SOA ans OSB.
    Any help would be appreciated.
    Thanks,
    Kumar.

    Hi Kumar,
    File Adapter itself is NON TRANSACTIONAL...
    4.2.9 Nontransactional
    The Oracle File Adapter picks up a file from an inbound directory, processes the file, and sends the processed file to an output directory. However, during this process if a failover occurs in the Oracle RAC back end or in an SOA managed server, then the file is processed twice because of the nontransactional nature of Oracle File Adapter. As a result, there can be duplicate files in the output directory.
    http://docs.oracle.com/cd/E28280_01/integration.1111/e10231/adptr_file.htm#BABIEBJF
    Cheers,
    Vlad

  • File adapter in OSB

    Hi ,
    I am trying to use file adapter in OSB. My intention is the OSB should write a file in a specified location in my sytem. I have configured the Business Service with Messagin service in (general tab), request msg as text and response msg as none in(messagin tab), protocol as file in (transport tab), prefix as AddUser suffix as *.txt* in (file transport tab).
    whenever i give input in proxy service it writing the file at the specified location, but the issue is,it writes the file name as AddUser3225734920456246193--12c3763f.132dd1769a3.-7f5b.txt . i dont need this part(AddUser3225734920456246193--12c3763f.132dd1769a3.-7f5b) in file name which is written. can anyone tell me how i can solve this?
    Any help is appreciated.
    thanks

    Hi,
    We can go with transport JCA FILE for file writing into the specified location.
    Create a file adapter in jdeveloper with all specified things like (file name,physical path location and schema).This creates the jca and wsdl file in jdevloper copy this to eclipse(OEPE) and later u can create business service based on jca file in eclipse.Or else in osb sbconsole copy import related jca and wsdl files and create business service based on this.This process wil create file in particular location with name specified in the jca file in particular location.....

  • Adapter Framework File Adapter Message on hold

    Hello,
    we have a problem with the Adapter Framework and their the File Adapter / Messaging System.
    We process one HR IDOC from R/3 through XI and send it to 7 file adapters. The SXMB_MONI tells us that all messages have been processed without errors and when you go to the RWB and use the Message-Monitoring many messages are on status HOLD. XI makes the message EOIO once you have multiple receivers and something blocks the messages in the AF. Is there a way to delete the AF queues like the XI queues with SMQ1 or SMQ2. It looks like SAP had duplicated the SMQ business in JAVA but I found no documentation how to clean up queues or what to do if the get stuck.
    Thanks
    Stefan

    hi,
    you can try question 3 adapters section
    on the XI FAQ:
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    to see adapters in RWB
    but if you see them when you do it then
    it means that this XI's configuration was not complete
    so you may expect further problems
    Regards,
    michal

  • Base64Binary OSB and File Adapter Issue

    Hi all,
    I am converting an xml to flat file after that i want to write the flatfile to a file using File Adapter in OSB.
    So using java callout we converted the binary content to base64 string and we are able to write the data using file adapter .
    But the file contains as extra line in between each line which my legacy system wont accept.
    I printed the base64 string in the output file and when i decode that file using the website as safe decode as text i am able to get the correct file.
    So where is the problem ? File Adapter ? Why i am getting extrace line in between each line . How to write safely using file adapter.
    If i use file transport of OSB i am able to write without any issues but i want to write dynamic location so i am looking for file transport of OSB.
    Thanks
    Phani

    Hi Anju,
    Thanks for the response . If i decode the base64 binary data using this website if i use Notepad++ i cant see an extra line in the notepad++ it showing as below
    Its a fixed length file 1 to 513 then next line so for the file transport it showing as below
    ISA ............................
    1 to 513 CRLF
    For file adapter it is showing as below in the same notepad++ editor
    ISA..........................
    1 to 513 CR
    CRLF
    an extra CR so an extra line .
    I used MFL and converted the xml to non-xml ( flat file fixed length file) for file transport i am i created another proxy message type Text .It is working fine
    Added to the above problem i have another few questions on the file transport
    How can append to an exiting file using File transport ?
    How to change the File directory dynamically ?

  • How to use Oracle File Adapter in OSB

    We are trying to use File Adapter in OSB 11g. Is it supported in this version? If yes then some one can specify a document which contains File Adapter - OSB integration steps.

    according to the ESB JCA transport:
    [ESB JCA|http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15866/jca.htm#i1106345]
    http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15866/jca.htm#i1106345
    there is only these adapters:
    _25.2.1 Adapter Support_
    The Oracle Service Bus JCA transport lets you interact with the following JCA-compliant adapters:
    Oracle Adapter for Oracle Applications
    Oracle JCA Adapter for AQ
    Oracle JCA Adapter for Database
    Oracle JCA Adapter for Files
    Oracle BAM Adapter (Business Activity Monitoring)
    PeopleSoft (Oracle Application Adapters 10g)
    SAP R/3 (Oracle Application Adapters 10g)
    Siebel (Oracle Application Adapters 10g)
    J.D. Edwards (Oracle Application Adapters 10g)
    See the following guides for more information on Oracle adapters:
    I wanna use FTP Adapter and MQ Adapter in Oracle ESB 11.1.1.3, can we make it?

  • High Availability File Adapter in OSB

    If you use the JCA FileAdapter in OSB, it is necessary to use the eis/HAFileAdapter version, to ensure that only one instance of the adapter picks up a file; you must then configure a coordinator, by setting the
    controlDir, inboundDataSource, outboundDataSource, outboundDataSourceLocal, outboundLockTypeForWrite
    parameters.
    controlDir refers to the filesystem, the others to the DB
    This document http://www.oracle.com/technetwork/database/features/availability/maa-soa-assesment-194432.pdf says
    "Database-based mutex and locks are used to coordinate these operations in a File Adapter clustered topology. Other coordinators are available but Oracle recommends using the Oracle Database."
    Using a Oracle Database as coordinator means using RAC, otherwise no HA.
    I wonder if anybody has been successful setting up HAFileAdapter without using a DB?
    If DB is required, I am considering using the good old "native" OSB File Poller, since it doesn't require complicated setup to be run in a cluster... but I don't want to use MFL, I would rather use the XSD-based Native Format. Here comes the second question:
    Is it possible to use the nXSD translator using the OSB Native File Poller - instead of the JCA Adapter?
    Thank you so much for your help - it will be rewarded with "helpful/answered" points .
    pierre

    I wonder if anybody has been successful setting up HAFileAdapter without using a DB?
    I have not tried it but I think there are several options available invlucing writing your own custom mutex. Please find the details in Oracle File and FTP Adapters High Availability Configuration section on this link
    http://download.oracle.com/docs/cd/E14571_01/core.1111/e10106/ha_soa.htm#sthref434
    Is it possible to use the nXSD translator using the OSB Native File Poller - instead of the JCA Adapter?
    When you create a JCA Adapter based Proxy Service to read the files, the nXSD translation happens before the proxy service is invoked. JCA Engine first reads the data, translates using nXSD and then invokes the Proxy with the translated content. (You can verify this easily by creating a JCA based file read service and open the test console for it in sbconsole, it will show you XML request instead of native).
    So you can not read the text content using File Transport of OSB and then calling nXSD directly or calling an nXSD based Proxy Service.
    HOWEVER, you certainly can use file and nXSD in a combination if thats what you want.
    1. Create a Synchronous Read File Adapter with an nXSD created for it
    2. Create a Business Service for that Synchronous Read JCA in OSB
    3. Create a File Transport based service in OSB which will read the content of file and then call the Business Service to again read the content (which will include the translation using nXSD defined in step one to convert the content to XML).
    So basically you will need to read the file twice! Once using File Transport Proxy service (which will take care of polling in cluster) and then using Sync Read JCA based business service(which will do nXSD translation). To reduce the impact of reading the file twice you can use trigger files. File Proxy to read trigger file and and invoke JCA business service to read the actual file for that trigger.
    Another alternative can be to create a similar class as present here(http://blogs.oracle.com/adapters/entry/command_line_tool_for_testing) but instead of writing a file it will just return the translated content. Call this class with native content from the File Transport proxy using a Java Callout to do the translation.

  • Configuring File adapter for OSB

    Hi,
    I wish to process invoice data that will be in the csv file . The structure of the file is as following :
    $H$<<Supplier Name>>,<<Supplier Site>>,<<Invoice Number>>
    $D$<<Line Number>> ,<<Business Unit>>,<<Location>>,<<Store Name>>
    $D$<<Line Number>> ,<<Business Unit>>,<<Location>>,<<Store Name>>
    $H$<<Supplier Name>>,<<Supplier Site>>,<<Invoice Number>>
    $D$<<Line Number>> ,<<Business Unit>>,<<Location>>,<<Store Name>>
    $D$<<Line Number>> ,<<Business Unit>>,<<Location>>,<<Store Name>>
    The intent is to configure the file adapter in such a fashion that it rejects the entire invoice if there are any errors in any of the lines that belong to that invoice. The invoices that follow the erred inovice should be processed normally. How do I configure the adapter to achieve this? Any help is greatly appreciated.

    Hi,
    Configuring the adapter for rejecting the invalid invoice rows is not possible. Adapter should be configured as usual to read all the rows. Once the rows are read, you can have all validation in the proxy service. If you find any invalid rows, you can write those rows to a saperate file so that it can be corrected and fed again. And all the other valid rows can be sent for further processing.
    Thanks,
    Vishwa

  • Message File Adapter - XI Integration Server not arriving

    We have configured a file adapter to read a file.  According to the audit log the file is successfully read and converted to XML; however, the message is never posted to XI.  We have checked to make sure that no XI* users are locked and we have bounced the server.
    The following error message is listed in the audit log:
    Transmitting the message to endpoint http://kansbwul01:50000/sap/xi/engine/entry?action=execute using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server.
    The following is the application log:
    #1.5#0003BA54D61900190000000C000030E60003EEAAD1138641#1106842349700#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.stop()######3e38f290707e11d996610003ba54d619#SAPEngine_System_Thread[impl:5]_35##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###The running MCF with GUID will be stopped now#1#8fa37160707811d995b00003ba54d619#
    #1.5#0003BA54D619001900000014000030E60003EEAAD16F4730#1106842355713#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.stop()######3e38f290707e11d996610003ba54d619#SAPEngine_System_Thread[impl:5]_35##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID was stopped successfully.#1#8fa37160707811d995b00003ba54d619#
    #1.5#0003BA54D619006000000009000030E60003EEAAD1A4DD9D#1106842359225#/Applications/ExchangeInfrastructure/AdapterFramework/ResourceAdapter/MessagingSystem/System/Clustering##com.sap.aii.af.ra.ms.runtime.MessagingSystem.reassignMessages(String, String[])#J2EE_GUEST#0#####SAPEngine_Application_Thread[impl:3]_11##0#0#Error#1#com.sap.aii.af.ra.ms.runtime.MessagingSystem#Java###Could not redistribute messages due to #1#LockingManager must be initialized before usage.#
    #1.5#0003BA54D6190040000000000000316A0003EEAAD9D40B8C#1106842496535#/Applications/ExchangeInfrastructure/AdapterFramework/Services/SecurityService##com.sap.aii.af.security.MessageSecurityServiceFrame.MessageSecurityServiceFrame.start()#######SAPEngine_System_Thread[impl:5]_24##0#0#Info#1#com.sap.aii.af.security.MessageSecurityServiceFrame#Java###QUEUE_CONNECTION_FACTORY: , ERROR_QUEUE: , QUEUE: , JARM_PREFIX: , JARM_USER: , JARM_ENABLED: .#6#jmsfactory/default/QueueConnectionFactory#jmsqueues/default/MessageSecurityErrorQueue#jmsqueues/default/MessageSecurityQueue#XI:Security:#XISecurityUser#false#
    #1.5#0003BA54D619004A000000060000316A0003EEAADD1ABF82#1106842551500#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Module Exception 'com.sap.aii.af.mp.module.ModuleException: senderChannel 'c5a6ccb89b113e8c92474a4aa0df5858': Catching exception calling messaging system' found, cause: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.#
    #1.5#0003BA54D619004A000000080000316A0003EEAADD1AC8F6#1106842551503#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Delivery Exception for guid'96f35561-707e-11d9-a16c-0003ba54d619' - non recoverable error, retry anyway#
    #1.5#0003BA54D619004A0000000A0000316A0003EEAADD1ACE8D#1106842551504#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#com.sap.aii.adapter.file.File2XI#Plain###Channel CDWExtFile: Sending file failed with com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available. - continue processing#
    #1.5#0003BA54D6190011000000FD0000316A0003EEAADF49F9C7#1106842588150#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.SpiManagedConnectionFactory()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Plain###This SPIManagedConnectionFactory has the GUID: cc6372c0-707e-11d9-ca96-0003ba54d619#
    #1.5#0003BA54D6190011000001030000316A0003EEAADF4ADA00#1106842588207#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.start()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID is started now. (,)#3#cc6372c0707e11d9ca960003ba54d619#com.sap.engine.services.deploy.server.ApplicationLoader@5293b95#cc6372c0707e11d9ca960003ba54d619#
    #1.5#0003BA54D6190011000001090000316A0003EEAADF4AEA33#1106842588211#/Applications/ExchangeInfrastructure/AdapterFramework/ThirdPartyRoot/comsap/Server/Adapter Framework##com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory.start()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#com.sap.aii.af.sample.adapter.ra.SPIManagedConnectionFactory#Java###MCF with GUID was started successfully.#1#cc6372c0707e11d9ca960003ba54d619#
    #1.5#0003BA54D6190051000000040000316A0003EEAAE1DFB940#1106842631518#/Applications/ExchangeInfrastructure/Repository#sap.com/com.sap.xi.repository#com.sap.aii.ib.core.applcomp.ApplicationComponent#J2EE_GUEST#0####e63e40d0707e11d9b8020003ba54d619#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "REPOSITORY" ok.#
    #1.5#0003BA54D6190054000000170000316A0003EEAAE4BA42E1#1106842679394#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector#J2EE_ADMIN#339####02bf9dd0707f11d9b9830003ba54d619#SAPEngine_Application_Thread[impl:3]_12##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D619004C000000080000316A0003EEAAE692D9D6#1106842710366#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.core.applcomp.ApplicationComponent#J2EE_GUEST#0##kansbwul01.erc.ge.com_LB1_148575#Guest#d8164a70707e11d9a3490003ba54d619#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "DIRECTORY" ok.#
    #1.5#0003BA54D619004D000000040000316A0003EEAAEB3DF548#1106842788689#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.server.util.BasicJMSClient#WSHAUN#466#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb6000ffffff90]###43ec08c0707f11d99f8b0003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#com.sap.aii.ib.server.util.BasicJMSClient#Plain###TopicConnectionFactory not found#
    #1.5#0003BA54D619004D000000050000316A0003EEAAEB3E07B0#1106842788693#/Applications/ExchangeInfrastructure/Directory#sap.com/com.sap.xi.directory#com.sap.aii.ib.server.util.BasicJMSClient#WSHAUN#466#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb6000ffffff90]###43ec08c0707f11d99f8b0003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Error#1#com.sap.aii.ib.server.util.BasicJMSClient#Plain###Exception during JMS startup for topic "SYNCHRONIZED_CACHE"
    Thrown:
    com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/jms/topic/xi/TopicConnectionFactory.
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:258)
         at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:621)
         at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
         at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.aii.ib.server.util.BasicJMSClient.initJmsResources(BasicJMSClient.java:77)
         at com.sap.aii.ib.server.util.BasicJMSClient.init(BasicJMSClient.java:54)
         at com.sap.aii.ib.server.util.BasicJMSClient.<init>(BasicJMSClient.java:48)
         at com.sap.aii.ib.server.util.ClusterSyncedCache.<init>(ClusterSyncedCache.java:41)
         at com.sap.aii.ib.server.cpa.AdapterMDCache.<clinit>(AdapterMDCache.java:27)
         at com.sap.aii.ib.sbeans.misc.MiscServicesBean.getAdapterMetadata(MiscServicesBean.java:226)
         at com.sap.aii.ib.sbeans.misc.MiscServicesRemoteObjectImpl10.getAdapterMetadata(MiscServicesRemoteObjectImpl10.java:2028)
         at com.sap.aii.ib.sbeans.misc.MiscServicesRemoteObjectImpl10p4_Skel.dispatch(MiscServicesRemoteObjectImpl10p4_Skel.java:284)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:291)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    #1.5#0003BA54D6190004000000060000316A0003EEAAED036F71#1106842818407#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190004000000120000316A0003EEAAED1F56F6#1106842820236#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D61900040000001E0000316A0003EEAAED2014BF#1106842820285#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D61900040000002A0000316A0003EEAAED20EE43#1106842820341#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190004000000360000316A0003EEAAED21A105#1106842820386#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190004000000420000316A0003EEAAED2268E0#1106842820438#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D61900040000004E0000316A0003EEAAED233205#1106842820489#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D61900040000005A0000316A0003EEAAED23EDCB#1106842820537#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190004000000660000316A0003EEAAED249350#1106842820580#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector######55770040707f11d9c6ea0003ba54d619#SAPEngine_System_Thread[impl:5]_16##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    #1.5#0003BA54D6190051000000090000316A0003EEAAF39F13CA#1106842929271#/Applications/ExchangeInfrastructure/IntegrationServer#sap.com/com.sap.xi.services#com.sap.aii.ib.core.applcomp.ApplicationComponent#XIDIRUSER#526####97b7c160707f11d9837b0003ba54d619#SAPEngine_Application_Thread[impl:3]_21##0#0#Info#1#com.sap.aii.ib.core.applcomp.ApplicationComponent#Plain###Startup of XI Application "RUNTIME" ok.#
    #1.5#0003BA54D619003C0000000C0000316A0003EEAAFD1B729D#1106843088417#/Applications/ExchangeInfrastructure/AdapterFramework/ResourceAdapter/MessagingSystem/System/Queue##com.sap.aii.af.ra.ms.runtime.ListenerFinder.run()#J2EE_GUEST#0####b4a1c0b1707e11d98d600003ba54d619#SAPEngine_Application_Thread[impl:3]_19##0#0#Error#1#com.sap.aii.af.ra.ms.runtime.ListenerFinder#Java###Message listener could not be created for connection after attempts.#3#localejbs/TestListener#test#10#
    #1.5#0003BA54D6190058000000050000316A0003EEAB27D41690#1106843805160#/Applications/SL/UTIL##com.sap.sl.util.cvers.impl.DBConnector#J2EE_ADMIN#635####a1c95a40708111d9887c0003ba54d619#SAPEngine_Application_Thread[impl:3]_28##0#0#Error#1#com.sap.sl.util.cvers.impl.DBConnector#Plain###get data source CVERS failed! Trying SAP/BC_UME... #
    The following is the trace file:
    #1.5#0003BA54D6190000000000140000316A0003EEAAD72107D8#1106842451248#com.sap.engine.core.service630.container.ReferenceResolver##com.sap.engine.core.service630.container.ReferenceResolver#######Thread[Thread-1,5,main]##0#0#Error##Plain###Component com.sap.aii.af.security has a hard reference to service com.sap.aii.af.service.cpa with manual startup mode.#
    #1.5#0003BA54D6190036000000000000316A0003EEAAD94B1302#1106842487558#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
    #1.5#0003BA54D6190036000000010000316A0003EEAAD94C908B#1106842487656#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###**************     CCMS CONNECTOR (System)    **************#
    #1.5#0003BA54D6190036000000020000316A0003EEAAD94C936D#1106842487657#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
    #1.5#0003BA54D6190036000000030000316A0003EEAAD94C9621#1106842487657#com.sap.engine.library.monitor.mapping.ccms.Trace##com.sap.engine.library.monitor.mapping.ccms.Trace#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###Tracelevel: 0#
    #1.5#0003BA54D6190036000000040000316A0003EEAAD94E292D#1106842487760#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
    #1.5#0003BA54D6190036000000050000316A0003EEAAD94F65F2#1106842487842#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###*******     Java Monitoring API - Version      ********#1#1.8.8#
    #1.5#0003BA54D6190036000000060000316A0003EEAAD9525DA5#1106842488036#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###************************************************************#
    #1.5#0003BA54D6190036000000070000316A0003EEAAD9547512#1106842488173#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Host: , OS: , JDK: .#3#kansbwul01.erc.ge.com#SunOS_sparcv9_5.9#1.4.2_06#
    #1.5#0003BA54D6190036000000080000316A0003EEAAD95490A6#1106842488180#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###Calculated library path: /global/usr/sap/LB1/DVEBMGS00/j2ee/cluster/server0/bin/ext/com.sap.mona.api#
    #1.5#0003BA54D6190036000000090000316A0003EEAAD954A29A#1106842488185#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Plain###System.load [2] /global/usr/sap/LB1/DVEBMGS00/j2ee/os_libs/libjmon.so#
    #1.5#0003BA54D61900360000000A0000316A0003EEAAD95617BA#1106842488280#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Version of JNI library: .#1#3.12 Non-Unicode Version#
    #1.5#0003BA54D61900360000000B0000316A0003EEAAD9562000#1106842488283#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Java tracelevel set to .#1#Error#
    #1.5#0003BA54D61900360000000C0000316A0003EEAAD9577C95#1106842488372#com.sap.mona.api.MonitoringAgent##com.sap.mona.api.MonitoringAgent#######SAPEngine_System_Thread[impl:5]_56##0#0#Info##Java###Connected () to segment (), , .#5#attach#0#read/write#system mode#40000000 bytes#
    #1.5#0003BA54D6190009000000010000316A0003EEAAD97D6C04#1106842490858#com.sap.aii.af.ra.ms.impl.core.queue.Queue##com.sap.aii.af.ra.ms.impl.core.queue.Queue.run()#######SAPEngine_System_Thread[impl:5]_73##0#0#Error##Java###Failed to retrieve message from MessageStore for queue .#2#aef38c80-707d-11d9-a639-0003ba54d619(OUTBOUND)#AFWSend#
    #1.5#0003BA54D6190014000000020000316A0003EEAAD988D5C9#1106842491606#com.sap.aii.af.ra.ms.impl.core.queue.Queue##com.sap.aii.af.ra.ms.impl.core.queue.Queue.run()#######SAPEngine_System_Thread[impl:5]_28##0#0#Error##Java###Failed to retrieve message from MessageStore for queue .#2#ea9f3be0-707c-11d9-834f-0003ba54d619(OUTBOUND)#AFWSend#
    #1.5#0003BA54D619003F000000000000316A0003EEAAD9CFB274#1106842496250#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###CPA Cache not updated with directory data, due to: #1#Couldn't open Directory URL (http://kansbwul01:50000/dir/hmi_cache_refresh_service/ext?method=CacheRefresh&mode=C&consumer=af.lb1.kansbwul01), due to: HTTP 503: Service Unavailable#
    #1.5#0003BA54D619003F000000010000316A0003EEAAD9D09295#1106842496307#com.sap.aii.af.service.cpa.impl.cache.CacheManager##com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(boolean)#######SAPEngine_System_Thread[impl:5]_65##0#0#Error##Java###Confirmation handling failed, due to: #1#Couldn't send confirmation, due to: Couldn't access Confirmation URL, due to: HTTP 503: Service Unavailable#
    #1.5#0003BA54D6190046000000000000316A0003EEAAD9E5FAD6#1106842497710#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setCurrentNodeID(int)#######SAPEngine_System_Thread[impl:5]_43##0#0#Info#1#/Version#Plain###Current node set to 1485750#
    #1.5#0003BA54D6190046000000010000316A0003EEAAD9E62B77#1106842497723#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setEnvironmentState(int)#######SAPEngine_System_Thread[impl:5]_43##0#0#Info#1#/Version#Plain###Environment state set to : ENV_INCOMPLETE#
    #1.5#0003BA54D6190049000000000000316A0003EEAAD9F40CB0#1106842498632#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
    #1.5#0003BA54D6190049000000010000316A0003EEAAD9FB0888#1106842499090#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
    #1.5#0003BA54D6190049000000020000316A0003EEAAD9FB3838#1106842499102#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
    #1.5#0003BA54D6190049000000030000316A0003EEAAD9FB61D0#1106842499113#com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry##com.sap.aii.af.service.cpa.impl.container.CPAObjectEntry.getValue(boolean)#######SAPEngine_System_Thread[impl:5]_77##0#0#Error##Java###Decryption failed, due to .#1#<null>#
    #1.5#0003BA54D6190009000000020000316A0003EEAADA5386CF#1106842504889#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######9998abd0707e11d9cd270003ba54d619#SAPEngine_System_Thread[impl:5]_73##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server#http://kansbwul01:50000/sap/xi/engine/entry?action=execute#
    #1.5#0003BA54D6190014000000030000316A0003EEAADA542AB7#1106842504931#com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer##com.sap.aii.af.ra.ms.impl.core.queue.SendConsumer.onMessage(QueueMessage)######99afb640707e11d9a86c0003ba54d619#SAPEngine_System_Thread[impl:5]_28##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#AFW#com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.RecoverableException: java.io.IOException: Error writing to server#http://kansbwul01:50000/sap/xi/engine/entry?action=execute#
    #1.5#0003BA54D619004D000000000000316A0003EEAADAF321D0#1106842515349#com.sap.aii.proxy.xiruntime.web.TransportServlet#sap.com/com.sap.xi.proxyserver#com.sap.aii.proxy.xiruntime.web.TransportServlet.init(...)#J2EE_GUEST#0####a1006c50707e11d99ea30003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Info##Plain###Initialized#
    #1.5#0003BA54D619004D000000010000316A0003EEAADAF32B88#1106842515352#com.sap.aii.proxy.xiruntime.web.TransportServlet#sap.com/com.sap.xi.proxyserver#com.sap.aii.proxy.xiruntime.web.TransportServlet.init(...)#J2EE_GUEST#0####a1006c50707e11d99ea30003ba54d619#SAPEngine_Application_Thread[impl:3]_32##0#0#Info##Plain###Registered with Adapter Framework Monitor#
    #1.5#0003BA54D6190055000000010000316A0003EEAADCAC81FD#1106842544275#com.sap.pmi.io.HttpPostThread##com.sap.pmi.io.HttpPostThread######b1f90ee0707e11d9c4300003ba54d619#Thread[Thread-42,5,SAPEngine_System_Thread[impl:5]_Group]##0#0#Error#1#/System/Server#Plain###Error sending PMI records to http://kansbwul01:8000/sap/bc/sapi_gate, HTTP response: 404Not found. Please check the HTTP destination "pmistore".#
    #1.5#0003BA54D619004A000000050000316A0003EEAADD1ABD1C#1106842551499#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Module Exception 'com.sap.aii.af.mp.module.ModuleException: senderChannel 'c5a6ccb89b113e8c92474a4aa0df5858': Catching exception calling messaging system' found, cause: com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available.#
    #1.5#0003BA54D619004A000000070000316A0003EEAADD1AC765#1106842551502#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0#SAP J2EE Engine JTA Transaction : [016ffffffabffffffb60001]###9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Delivery Exception for guid'96f35561-707e-11d9-a16c-0003ba54d619' - non recoverable error, retry anyway#
    #1.5#0003BA54D619004A000000090000316A0003EEAADD1ACD22#1106842551504#com.sap.aii.adapter.file.File2XI##com.sap.aii.adapter.file.File2XI.processFileList()#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/File#Plain###Channel CDWExtFile: Sending file failed with com.sap.aii.af.ra.ms.api.ConfigException: SLDAccess set to true, but not available. - continue processing#
    #1.5#0003BA54D619004A0000000C0000316A0003EEAADD1B3AEE#1106842551532#com.sap.engine.services.ts##com.sap.engine.services.ts#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Server#Java#ts_0021##Thread is not associated with any transaction context.##
    #1.5#0003BA54D619004A0000000D0000316A0003EEAADD1B41AE#1106842551533#com.sap.engine.services.ts##com.sap.engine.services.ts#J2EE_GUEST#0####9b9677a1707e11d9a9010003ba54d619#SAPEngine_Application_Thread[impl:3]_39##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.ts.exceptions.BaseIllegalStateException: Thread is not associated with any transaction context.
         at com.sap.engine.services.ts.jta.impl.TransactionManagerImpl.rollback(TransactionManagerImpl.java:441)
         at com.sap.aii.adapter.file.File2XI.processFileList(File2XI.java:1756)
         at com.sap.aii.adapter.file.File2XI.run(File2XI.java:1007)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    #1.5#0003BA54D6190011000000790000316A0003EEAADDAE5C4B#1106842561174#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.xi.ibresources factory name: jms/topic/xi/TopicConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D61900110000007A0000316A0003EEAADDAFCE2B#1106842561269#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: jms/topic/xi/TopicConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D61900110000007C0000316A0003EEAADDAFE340#1106842561274#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.xi.ibresources factory name: jms/queue/xi/QueueConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D61900110000007D0000316A0003EEAADDB040CB#1106842561298#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: jms/queue/xi/QueueConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000B20000316A0003EEAADE6877ED#1106842573371#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.aii.af.ispeak.app factory name: ISPXAConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000B30000316A0003EEAADE68A1E8#1106842573382#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: ISPXAConnectionFactory loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000C10000316A0003EEAADE837B81#1106842575141#com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext##com.sap.aii.af.protocol.ispeak.clustercontext.ISPClusterContext.setEnvironmentState(int)######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Environment state set to : ENV_COMPLETE#
    #1.5#0003BA54D6190011000000C20000316A0003EEAADE83D50E#1106842575164#com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession##com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.initialize()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Looked up factory : com.sap.engine.services.jmsconnector.cci.QueueConnectionFactoryImpl@6cbd9138#
    #1.5#0003BA54D6190011000000C30000316A0003EEAADE83D78C#1106842575165#com.sap.aii.af.protocol.ispeak.j2ee.services.ISPStartupService##com.sap.aii.af.protocol.ispeak.j2ee.services.ISPStartupService.onAllAppStart()######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Info#1#/Version#Plain###Calling onServerStart on ISPClusterContext...#
    #1.5#0003BA54D6190011000000E60000316A0003EEAADF147D24#1106842584644#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.ip.me.insttool factory name: InstToolTopicFactoryCreateEmptyImage loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000E70000316A0003EEAADF14A82D#1106842584655#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: InstToolTopicFactoryCreateEmptyImage loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000E90000316A0003EEAADF14B7A3#1106842584659#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error#1#/System/Server#Plain###JMS Connector Container Application: sap.com/com.sap.ip.me.insttool factory name: InstToolTopicFactoryFinishImage loader does not exist:  . Using default class loader!!!#
    #1.5#0003BA54D6190011000000EA0000316A0003EEAADF14DC56#1106842584669#com.sap.engine.services.jmsconnector##com.sap.engine.services.jmsconnector######98db9d60707e11d9b1c00003ba54d619#SAPEngine_System_Thread[impl:5]_11##0#0#Error##Plain###Factory: InstToolTopicFactoryFinishImage loader does not exist:  . Using default class loader!!!#

    The problem was the Pipeline URL for the integration server.
    http://<server>:50000/sap/xi/engine/entry?action=execute
    is the defective URL. 
    Once we logged into SLD and selected the business system for the integration server we change the pipeline URL to the following
    http://<server>:8000/sap/xi/engine?type=entry
    we then restarted the J2EE server and it worked fine.

  • Error in using file adapter valves

    Hi,
    I'm working on Oracle SOA Suite 11g (11.1.1.4). I'm doing an exercise on using adapter valves for encryption. I need to write an encrypted file using File adapter. I created pipeline.xml and also specified property in jca file. And added bpm-infra.jar file to classpath.
    Also, I've compiled SimpleEncryptValve.java and created a jar file and placed it in lib directory of domain.
    Pipeline.xml is as below :
    <?xml version="1.0"?>
    <pipeline xmlns="https://www.oracle.com/adapter/pipeline">
    <valves>
    <valve>valves.SimpleEncryptValve</valve>
    </valves>
    </pipeline>
    writeFile_file.jca contents are as below :
    <adapter-config name="writeFile" adapter="File Adapter" wsdlLocation="writeFile.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
    <connection-factory location="eis/FileAdapter"/>
    <endpoint-interaction portType="Write_ptt" operation="Write">
    <interaction-spec className="oracle.tip.adapter.file.outbound.FileInteractionSpec">
    <property name="PhysicalDirectory" value="D:\PoC\FileAdapters"/>
    <property name="Append" value="false"/>
    <property name="FileNamingConvention" value="new_%SEQ%.txt"/>
    <property name="NumberMessages" value="1"/>
    <property name="PipelineFile" value="pipeline.xml"/>
    </interaction-spec>
    </endpoint-interaction>
    </adapter-config>
    Got below error while testing. What could be wrong in valve configuration ?
    <Jun 6, 2011 7:29:25 PM IST> <Error> <oracle.soa.adapter> <BEA-000000> <File
    pter Project2:writeFile [ Write_ptt::Write(body) ]
    oracle.tip.pc.services.pipeline.PipelineException: Invalid configurations for valves
    at oracle.tip.pc.services.pipeline.PipelineImpl.validate(PipelineImpl
    va:237)
    at oracle.tip.pc.services.pipeline.PipelineFactory.instantiateModel(P
    lineFactory.java:198)
    at oracle.tip.pc.services.pipeline.PipelineTemplate.newPipeline(Pipel
    Template.java:39)
    at oracle.tip.adapter.file.outbound.FileSender.getPipeline(FileSender
    va:378)
    at oracle.tip.adapter.file.outbound.FileSender.sendNonBatchedSerializ
    late(FileSender.java:254)
    at oracle.tip.adapter.file.outbound.FileInteraction.executeFileWrite(
    eInteraction.java:623)
    at oracle.tip.adapter.file.outbound.FileInteraction.execute(FileInter
    ion.java:426)
    at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteracti
    nvoker.executeJcaInteraction(JCAInteractionInvoker.java:311)
    at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteracti
    nvoker.invokeJcaReference(JCAInteractionInvoker.java:548)
    at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteracti
    nvoker.invokeAsyncJcaReference(JCAInteractionInvoker.java:508)
    at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAEndpointI
    raction.performAsynchronousInteraction(JCAEndpointInteraction.java:491)
    at oracle.integration.platform.blocks.adapter.AdapterReference.post(A
    terReference.java:247)
    at oracle.integration.platform.blocks.mesh.AsynchronousMessageHandler
    Post(AsynchronousMessageHandler.java:142)
    at oracle.integration.platform.blocks.mesh.MessageRouter.post(Message
    ter.java:194)
    at oracle.integration.platform.blocks.mesh.MeshImpl.post(MeshImpl.jav
    15)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorIm
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingRefle
    on(AopUtils.java:307)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invok
    inpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proce
    ReflectiveMethodInvocation.java:149)
    at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseE
    tAspect.java:71)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proce
    ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDyn
    cAopProxy.java:204)
    at $Proxy299.post(Unknown Source)
    at oracle.tip.mediator.serviceEngine.MediatorServiceEngine.post2Mesh(
    iatorServiceEngine.java:1120)
    at oracle.tip.mediator.service.BaseActionHandler.requestProcess(BaseA
    onHandler.java:200)
    at oracle.tip.mediator.service.BaseActionHandler.requestProcess(BaseA
    onHandler.java:94)
    at oracle.tip.mediator.service.BaseActionHandler.requestProcess(BaseA
    onHandler.java:74)
    at oracle.tip.mediator.service.OneWayActionHandler.process(OneWayActi
    andler.java:47)
    at oracle.tip.mediator.service.ActionProcessor.onMessage(ActionProces
    .java:64)
    at oracle.tip.mediator.dispatch.MessageDispatcher.executeCase(Message
    patcher.java:137)
    at oracle.tip.mediator.dispatch.InitialMessageDispatcher.processCase(
    tialMessageDispatcher.java:503)
    at oracle.tip.mediator.dispatch.InitialMessageDispatcher.processCases
    itialMessageDispatcher.java:401)
    at oracle.tip.mediator.dispatch.InitialMessageDispatcher.processNorma
    ses(InitialMessageDispatcher.java:284)
    at oracle.tip.mediator.dispatch.InitialMessageDispatcher.processCases
    itialMessageDispatcher.java:251)
    at oracle.tip.mediator.dispatch.InitialMessageDispatcher.dispatch(Ini
    lMessageDispatcher.java:143)
    at oracle.tip.mediator.serviceEngine.MediatorServiceEngine.process(Me
    torServiceEngine.java:848)
    at oracle.tip.mediator.serviceEngine.MediatorServiceEngine.post(Media
    ServiceEngine.java:624)
    at oracle.integration.platform.blocks.mesh.AsynchronousMessageHandler
    Post(AsynchronousMessageHandler.java:142)
    at oracle.integration.platform.blocks.mesh.MessageRouter.post(Message
    ter.java:194)
    at oracle.integration.platform.blocks.mesh.MeshImpl.post(MeshImpl.jav
    15)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorIm
    java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAc
    sorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingRefle
    on(AopUtils.java:307)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invok
    inpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proce
    ReflectiveMethodInvocation.java:149)
    at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseE
    tAspect.java:59)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proce
    ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDyn
    cAopProxy.java:204)
    at $Proxy299.post(Unknown Source)
    at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComp
    nt.doMessageProcessing(WebServiceEntryBindingComponent.java:1271)
    at oracle.integration.platform.blocks.soap.WebServiceEntryBindingComp
    nt.processIncomingMessage(WebServiceEntryBindingComponent.java:859)
    at oracle.integration.platform.blocks.soap.FabricProvider.processMess
    (FabricProvider.java:113)
    at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcess
    (ProviderProcessor.java:1187)
    at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementa
    n(WebServiceProcessor.java:1081)
    at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessi
    ProviderProcessor.java:581)
    at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServic
    ocessor.java:232)
    at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProc
    or.java:192)
    at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.j
    :459)
    at oracle.integration.platform.blocks.soap.FabricProviderServlet.doPo
    FabricProviderServlet.java:507)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.
    (StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSec
    tyHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.
    a:300)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl
    va:56)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:1
    at java.security.AccessController.doPrivileged(Native Method)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java
    3)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatfor
    il.java:413)
    at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.
    a:94)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.jav
    61)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl
    va:56)
    at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java
    6)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl
    va:56)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAc
    n.wrapRun(WebAppServletContext.java:3715)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAc
    n.run(WebAppServletContext.java:3681)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authentic
    dSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.ja
    120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebA
    ervletContext.java:2277)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServl
    ontext.java:2183)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImp
    ava:1454)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
    >

    Hi Surfraz,
    Did you go through this link?
    http://docs.oracle.com/cd/E21764_01/integration.1111/e10231/adptr_file.htm#BABCFDGC
    Regards,
    Neeraj Sehgal

  • File read in Mediator / OSB

    I have a requirement where a BPEL process calls an ESB (could be implemented using either mediator or OSB). The ESB should then pick a set of files from a directory in the local file system and FTP them to several locations.
    From the file adapters available in (both the) ESBs, we HAVE to configure the polling interval. So, the file adapter is actually a one-time configuration which runs until the server ends. That is not the requirement. Is there a way to make a synchronous call from BPEL to the ESB file adapter, and then the file adapter picks those files and FTPs to the said locations and returns control to the ESB and hence the BPEL?
    Edited by: user11846866 on Aug 31, 2009 3:07 PM

    I'm not a expert in ESB so cannot comment on that product.
    OSB in itself cannot accomplish this use case "OSB should pick a set of files from a directory in the local file system and FTP them to several locations only on trigger/request (different from polling)".
    We had similar discussion earlier Re: Using SFTP proxy service without polling interval, how to do it?
    I'm not sure about your architecture criteria that mandates this separation of logic implementation in BPEL and OSB.
    At best, solution with OSB is like
    1) BPEL--->(OSB)Proxy Service1---> Enable FTP Proxy and wait for pre-configured time(Java Callout in Proxy Service1) ---->Read the files and ftp to various locations in FTP proxy---->Disable SFTP Proxy(Java Callout in Proxy Service1)--->Return response to BPEL.
    2) BPEL puts file in directory--->OSB picks and posts to FTP (polling is involved)
    Manoj

  • Overwriting the File in File Adapter

    Hi All,
    I hav a module processor (in Receiver file Adapter)which checks the existence of the file by name DOWN.flg befor writing the file by the same name at the same location. if the file already exists, then it has to wait until another system deletes (as per the requirement). if not, it has to write the file. I had done this successfully with an FTP receiver. but when i'm moving the same functionality to the local drive(now the receiver is a local directory on the XI Server), then i'm getting the following error.
    <b>Error</b>:Attempt to process file failed with java.lang.Exception: Overwriting file '/cpe/data/DEV/XI_/IN/APD/Commander/DOWN.flg' not allowed due to configuration flag
    <b>Error:</b>
    Exception caught by adapter framework: Overwriting file '/cpe/data/DEV/XI_/IN/APD/Commander/DOWN.flg' not allowed due to configuration flag
    these are the errors which i found in the audit log. i din't check the overwrite Existing File option in the Receiver adapter.Can anyone help me out in resolving this.
    Anyhelp wud  b greately apprecited...
    Thnx in Advance.

    Hello Jayakrishnan,
    Thank you very much for the tip, actualy it was very tricky, since the overwrite existing file option is not possible in the "append" mode on my XI version (SP12). THis is what we have done :
    - modify the communication channel to "create" mode and check the "overwrite existing file option".
    - activate it
    - chanche back to the "append" mode
    - activate it again
    And then it works !
    Thanks for your help
    Guislain

Maybe you are looking for

  • Warnings/Errors using getClass().newInstance()

    I'm getting some warnings & errors using getClass().newInstance() on an object. I can't however see what's wrong. First a little background, Bar is a class that manages a set of beans, including creation. One of the actions is to create a special cop

  • Search Engines + SSIs

    Do search engines pick up info from SSIs? TIA, JJ

  • Can you use a wired ethernet to internet AND wireless to apple tv

    since getting the appletv, i had connected it wirelessly through the apple extreme (n) base station and kept my internet setup with gigaport #1 with no problem. since the latest updates, apple tv is very sensitive....does not work if the wired ports

  • N80 works in the States but not Europe

    I purchased an N80 in the States and it worked with my T-Mobile SIM but then I moved to Cyprus. I got a Vodafone SIM and now the N80 will not connect to the network. The new SIM works with a different phone so I know that is not the problem. Any idea

  • Fagll03 issue

    Hi All Greetings for the day I have a issue in New Gl while running a specific varaiant in Fagll03 used to display documents  wherein it it is running fine for leading ledger, but for non leading ledger there in a performance issue and it is not endi