Inbound adapter exception/error management

I was wandering is there any best practice for handling inbound adapter exceptions ? For example if I have inbound MQ-adapter and MQ-server is down how can I get some kind of exception catched from this? Only thing I've found out that it SOA Suite writes these exceptions to server log. Is the only way to catch these exception to poll the server log (using for example grep...)?
Thank you
Best Regards Tuomas

Any light / idea on the following issue ?
1. While reading from file, if a records errors out, the custom BPEL process is launched (as specified in rejectedMessageHandlers property). In such instance, the previously read valid records are processed but remaining records are marked as errored out. Our requirement is to make entire record set as invalid and would like to perform rollback of entire process. Even, if we do not configure rejectedMessageHandlers, the behavior is that valid rows are processed with the rest of BPEL process and for Invalid rows, the records are rejected. Our requirement, is that, even if there is one invalid record, the entire set of record should NOT move ahead with the BPEL process
2. Whenever an error occurs during reading the records using File adapter, the associated data file is being deleted from the input directory and also NOT available in archive directory also. Note, in case of all valid record the file is available in archive directory

Similar Messages

File Adapter - Exception / Error handling

We are using File Adapter in BPEL process to read multiple records from the file. Additionally, we have also handled rejectedMessageHandlers & fatalErrorFailoverProcess exception to lunch custom BPEL process. The process is running fine and also successfully launches custom handler processes too.
Need help / direction in addressing following issues.
1. While reading from file, if a records errors out, the custom BPEL process is launched (as specified in rejectedMessageHandlers property). In such instance, the previously read valid records are processed but remaining records are marked as errored out. Our requirement is to make entire record set as invalid and would like to perform rollback of entire process.
2. Whenever an error occurs during reading the records using File adapter, the associated data file is being deleted from the input directory and also NOT available in archive directory also.
Are we missing any set up ? We are on 10.1.3.1
thanks
-Yj
Sample Log file:
<2009-04-20 11:46:14,080> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::init - Initializing the JCA activation agent, processId='bpel://localhost/default/TestFileRead~1.0/
<2009-04-20 11:46:14,080> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> JCAActivationAgent::initiateInboundJcaEndpoint - Creating and initializing inbound JCA endpoint for:
process='bpel://localhost/default/TestFileRead~1.0/'
domain='default'
WSDL location='Read.wsdl'
portType='Read_ptt'
operation='Read'
activation properties={portType=Read_ptt, rejectedMessageHandlers=bpel://default|AdapterError2|initiate|payload}
<2009-04-20 11:46:14,096> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - endpointActivation for portType=Read_ptt, operation=Read
<2009-04-20 11:46:14,143> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Endpoint Activation called in File Adapter for endpoint: c:\temp\yj
<2009-04-20 11:46:14,143> <INFO> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Adapter Framework instance: OraBPEL - successfully completed endpointActivation for portType=Read_ptt, operation=Read
<2009-04-20 11:46:30,580> <WARN> <default.collaxa.cube.activation> <File Adapter::Inbound> PollWork::run exiting, Worker thread will die
<2009-04-20 11:47:14,158> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Translated inbound batch index 1 of file {testdata6.txt} with corrupted message count = 1
<2009-04-20 11:47:14,158> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Sending message to Adapter Framework for rejection to user-configured rejection handlers : {
fileName=C:\temp\yj\testdata6.txt, startLine=3, startColumn=1, endLine=-1, endCol=-1, Exception=ORABPEL-11168
Error while reading native data.
[Line=3, Col=5] Expected "|" for the data starting at the specified position, while trying to read the data for "element with name C2", using "style" as "terminated" and "terminatedBy" as "|", but not found.
Ensure that "|", exists for the data starting at the specified position.
<2009-04-20 11:47:14,158> <WARN> <default.collaxa.cube.activation> <AdapterFramework::Inbound> [Read_ptt::Read(Root-Element)]onReject: Sending invalid inbound message to Exception Handler: bpel://default|AdapterError2|initiate|payload
<2009-04-20 11:47:14,315> <INFO> <default.collaxa.cube.activation> <File Adapter::Inbound> Setting last error record to : -1
<2009-04-20 11:47:14,658> <ERROR> <default.collaxa.cube.activation> <AdapterFramework::Inbound> onBatchFailure: Batch 'bpel://localhost/default/TestFileRead~1.0//testdata6.txt_1240205493408' (C:\temp\yj\testdata6.txt) has failed due to: ORABPEL-11168
Error while reading native data.
[Line=3, Col=5] Expected "|" for the data starting at the specified position, while trying to read the data for "element with name C2", using "style" as "terminated" and "terminatedBy" as "|", but not found.
Ensure that "|", exists for the data starting at the specified position.

Any light / idea on the following issue ?
1. While reading from file, if a records errors out, the custom BPEL process is launched (as specified in rejectedMessageHandlers property). In such instance, the previously read valid records are processed but remaining records are marked as errored out. Our requirement is to make entire record set as invalid and would like to perform rollback of entire process. Even, if we do not configure rejectedMessageHandlers, the behavior is that valid rows are processed with the rest of BPEL process and for Invalid rows, the records are rejected. Our requirement, is that, even if there is one invalid record, the entire set of record should NOT move ahead with the BPEL process
2. Whenever an error occurs during reading the records using File adapter, the associated data file is being deleted from the input directory and also NOT available in archive directory also. Note, in case of all valid record the file is available in archive directory

IDoc Adapter and Error Management

Hi Experts,
I don't understand tha management of business logic error.
My External System communicate with SAP ERP via SAP PI IDOC Adapter (HTTP protocol, asynchronous mode).
SAP ERP sends an IDOC via PI to my system, my system receives IDoc, an error occurs during business operation in my system.
What should I do?
In my scenario there are not message of error or IDOC to communicate a problem.
Thanks,
Marco Genova
Edited by: m.genova on May 21, 2009 6:41 PM

Hi,
For the same wrong rfc destination i've got
in sxmb_moni : <SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>FM NLS_GET_LANGU_CP_TAB: Could not determine code page with ARS Name or password is incorrect. Please re-enter FM NLS_GET_LANGU_CP_TAB</SAP:P1>
OR
in sm58 : XIAFUSER IDOC_INBOUND_ASYNCHRONOUS ARS 17.02.2006 15:57:33 Name or password is incorrect. Please re-enter
It's so strange ?
Regards,
Vincent

Error in Inbound B2B: AIP-50031: B2B adapter general error: java.lang.Null

Hi,
I am getting the following error in inbound B2B - Custom Document over Generic Exchange - SFTP
Description: B2B adapter general error
StackTrace:
Error -: AIP-50031: B2B adapter general error
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1900)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2657)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2527)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2482)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:530)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:376)
     at java.lang.Thread.run(Thread.java:534)
]]>
The outbound B2B is working fine; however for the inbound file transfer the file is picked up from the trading partner and this exception occurs.
Thanks

Please paste more log in trace 32 mode. What is the name of the file you are receiving? By default B2B expects incoming filename as -
<FromTPName>UniqueId.<anyFile_Extn>
For e.g., if partner MarketInc is sending the file then it's name should be - MarketInc_12345.dat or MarketInc_34567.xml
Make sure that listening channel is not marked as internal as well.
Regards,
Anuj

JCA Inbound adapter error

Hi everybody,
I have an ESB project which reads a file from a folder and writes it into another folder. The issue is that sometimes it works ok, but some others the in adapter fails and I get this error:
JCA inbound adapter service listener for "SUBIRA.INM.LeerCarpetaINM_RS.LeerINM" with endpoint ID "[LeerINM_ptt::LeerINM(opaque)]" has
been requested to shutdown by Resource Adapter due to fatal error. Reason : ORABPEL-11004
Error al publicar el mensaje.
Se ha producido un error al publicar el mensaje del archivo C:\FTPINM\20070402221542_82AVC00001540.dat
Compruebe la pila de errores y corrija la causa del error. Póngase en contacto con los Servicios de Soporte Oracle si no se puede
corregir el error.
Resuming it in english it would be: Error trying to publish the message. An error has occurred while publishing the file message. Check the error stack and fix it. Contact Oracle Support Services if you are not able to fix the error.
This error appears randomly, I mean, I haven't change anything in the project. Any suggestions?

Hi alex,
Cause of problem
Both OC4J running BPEL and the database adapter reached the maximum number of connections and were unable to establish new ones.
The reason for the problem is a database adapter Bug 5595347.
According to Bug 5595347, the database adapter might leave open connections behind.
The fix for Bug 5595347 is included in Patch 5638122.
Solution
To implement the solution, please execute the following steps:
Apply Patch 5638122.
References
Bug 5595347 - ORIONCMTCONNECTION NOT CLOSED IN ORABPEL~OC4J_BPEL~DEFAULT_ISLAND~1
Note 314422.1 - Remote Diagnostic Agent (RDA) 4 - Getting Started
Patch 5638122 - MERGE LABEL REQUEST ON TOP OF 10.1.2.0.2 FOR BUGS 5149866 5595347 5205630
Cheers,
Abhi...

SRFC-adapter and file adapter with error: no adapter found

Hello,
we have two scenarios here in an XI 3.0 SP12:
First scenario connects two R/3 systems via RFC adapter (outbound / inbound) for an RFC in a standard R/3 function module SUSR_ZBV_GET_REMOTE_PROFILES.
The RFC is synchronous.
Second scenario uses file adapter to send file from A to B.
When starting the RFC call from the sender system the error message in area "call adapter" for XML message in the trace is "exception while reading from SLD:Property sap_xiadapterservice.adapterType does not exist".
Message in RWB:
"Transmitting the message using connection http://abc038.ceu.test.com:8077/sap/xi/engine?type=entry failed, due to: XIServer:AE_DETAILS_GET_ERROR:Property sap_xiadapterservice.adapterType does not: Unable to find any Adapter Engines."
Same problem for file adapter!
Here is the message from the file adapter error log entry in SXMB_MONI:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.kx1.test038</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>Property sap_xiadapterservice.adapterType does not: Unable to find any Adapter Engines</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.kx1.test038</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Looks like an identical problem for both adapter.
What we have done (checked) so far:
- SLD connection is working
- Vis.Admin.: no problems found
(SAP RFC adapter active, file adapter active)
- Component monitoring: no errors, adapters are fine
- all rfc connections checked: ok
- have checked user and pwd and replaced to be sure
- cache refresh: ok
- reimport of SWCV to IR for RFC: done, no result
Does anybody have an idea, how to get rid of that?
Best regards
Dirk

Hello Udo,
in Adapter monitoring all adapters are listed and per adapter (here RFC and FILE) all adapter entries from the scenarios are available (sender / receiver comm. channel entries - in green)!
Pipeline URL in SLD Bus. Syst. is fine ( and an IDOC adapter scenario is running successfully) !
I think this is a really tricky one!
Best regards
Dirk

RECEIVER FILE ADAPTER FCC ERROR

Hi team
My scenario is a text file has to be picked up by PI, has to processe it and the receiver is Proxy and it has to get updated and sent back to FTP location.
i am using Sender File Adapter with FCC and Also receiver File Adapter with FCC.
Both the sender and receiver structures are same; i am using the same FCC parameters for both the sides.
in Receiver File Adapter i am getting the following errors
1) Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
2)Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
please help me out
thank you
Edited by: vemugantivn on Aug 16, 2010 12:19 PM

Hi,
> 1) Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
> Parameter '.fieldFixedLengths' or '.fieldSeparator' is missing
> 2)Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
> Parameter '1.fieldFixedLengths' or '1.fieldSeparator' is missing
It is saying that you are not using the fieldSeparator parqameter.
have you provided the field separator parameter? if not then give like below
order_row.fieldSeparator : , (give what ever the separater you are using)
or
order_row.fieldSeparator : 10,5,... (if you are using fixed length)
Regards
Ramesh

Sender file adapter conversion Error!!

Hello every one....
I am stuck with a problem...in my scenario,, there are possiblities that file may contain more than required paramters... in such case,,, paramters defined in conversion should go ahead and others should be ignored...
for this very purpose i added the paramter:
row.fieldSeparator                 ,
row.fieldNames                     orderno,authcode,status
row.endSeparator                  'nl'
row.additionalLastFields      ignore
the scenario works fine if the file contains thrree comma separated values but it raises an error if no of paramters increase as :
Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting
document line no. 1 according to structure 'row':java.lang.Exception: ERROR in configuration: more
elements in file csv structure than field names specified!
we are using PI 7.... does it require some more configuration in additoin to paramter row.additionalLastFields
any help in this regard would be highly appreciated...
thanx

this parameter is already set, and this is the exact behavior i want from adapter engine... but the problem
here is different... the exception is raised at communication channel's conversion routine level,,, the retry
interval is not the one defined in visual admin but infact the interval (polling) time defined in communication
channel.... the system does'nt stop after 3 attempts,, but infact keep on trying to read it....
one peice of information i have found is in sap note:821267 , which states:
*Q35:*
Q: I have configured a File Sender channel with File Content
Conversion or a custom-developed module, which may throw an
exception. When the File Adapter encounters an invalid file, which
triggers a conversion error or an exception in a module, the
adapter will enter a retry interval and upon each following
processing attempt try to process the faulty file. This basically
prevents the File Adapter from picking up files that are located
after the fauilty file according to the configured sort order. How
can I change this behavior?
o A: This is by design. When the File Adapter encounters an invalid
file, manually remove this file from the configured source
directory. You can configure an alerting rule to get notified each
time this occurs.
We are currently evaluating possible solutions that could be used
to skip this manual interaction.
now can there be a way around to make communication channel read the file only 3 times (value defined in adapter engine profile in visual admin)
I have thaught of writing of module.... but the error is raised even before calling module !!
any further clue ???

File Adapter: Initialization error: Conversion initialization failed

Hi all,
I'm trying to establish a file adapter (FTP, File Content Conversion).
In the adapter monitor I' ve got the following error:
Sender Adapter v1325 for Party '', Service 'BS_ACN_PCS_A':
Configured at 14:49:34 2005-08-29
Initialization error: Conversion initialization failed with java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found:
Format error in 'xml.recordset' argument: incomplete structure (name,number) pair
My content conversion parameters are:
BP_BusinessPartnerMasterData_IncomingData.fieldFixedLengths:
20,50,50,1,10,50,10,50,5,20,20,15,15
BP_BusinessPartnerMasterData_IncomingData.fieldNames: Number,Name2,Name1,Gender,Birthdate,City,Postcode,Street,
HouseNo,PhoneNumber,Fax,BankId,BankAccount
BP_BusinessPartnerMasterData_IncomingData.fieldContentFormating:
trim
BP_BusinessPartnerMasterData_IncomingData.keyFieldInStructure:
ignore
What could be the error or where I have to look for it?
Thanks,
Fabian

Yes,
Recordset name: BP_BusinessPartnerMasterData_IncomingData
Recordset structure: BP_BusinessPartnerMasterData_IncomingData
The corresponding Message Type:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://pcs.acn.com/basicdata" targetNamespace="http://pcs.acn.com/basicdata">
     <xsd:element name="BP_MasterDataIncomingFil" type="BP_BusinessPartnerMasterData_IncomingData" />
     <xsd:complexType name="BP_BusinessPartnerMasterData_IncomingData">
          <xsd:annotation>
               <xsd:appinfo source="http://sap.com/xi/TextID">
               f323a4b018a911da9fd9000bcd69ce64
               </xsd:appinfo>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="Number">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8500fe111da89f2d1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Id from Sender for BP
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Name2">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8510fe111dacfd7d1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         Last name or Company name
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Name1">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8520fe111da94bad1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         First name or Company name 2
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Gender">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8530fe111da99add1210a87220d
                         </xsd:appinfo>
                         <xsd:documentation xml:lang="EN">
                         m or f or blank
                         </xsd:documentation>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="1" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Birthdate">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8540fe111dab156d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="10" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="City">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8550fe111daa58cd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Postcode">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8560fe111dac0c2d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="10" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Street">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8570fe111dabbd3d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="50" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="HouseNo">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8580fe111dab63fd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="5" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="PhoneNumber">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e8590fe111dac782d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="Fax">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85a0fe111daa9ebd1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="20" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="BankId">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85b0fe111dace1ed1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="15" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="BankAccount">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         7679e85c0fe111da8801d1210a87220d
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:maxLength value="15" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
</xsd:schema>

Inbound Adapter / 'Sink' failing for Content Server on Subscription Client

I am running into an issue in configuring the Outbound - Inbound Adapters for Connection Server / Subscription Client against Content Server. The details are below. Would sincerely appreciate if anyone can help with this.
I have installed a Oracle UCM setup together with two Content Server instances (Contribution instance and Live instance), a Connection Server and a Subscription Client - all within the same virtual machine on top of Windows XP SP2 OS and Oracle 10g Database.
I have further configured the Outbound Adapter on the Connection Server and the Inbound Adapter on the Subscription Client. All installation and configuration has been done following the step-by-step process from the relevant installation guides.
We have tested the connectivity between the Connection Server and the Subscription Client for a simple file-based content source and it works fine - i.e., files added to a directory registered as a source on connection server are retrieved and sent to the subscription client and received there successfully / dropped in the specified target client directory.
However, this transfer fails for the Content Server Outbound-Inbound Adapter connectivity. We have an Archive in Content Server registered as a "CNSArchive" and exporting successfully to the CNS Server. The registered outbound adapter is successfully able to receive these updates and are visible through the Connection Server
interface. The subscription client is also apparently able to receive these updates
correctly and writes them to the specified folder/directory on the client;
however fails to "batch load" these and reports a failure writing to the
Content Sink.
What we would like is for the ability to establish end-to-end connectivity between the contribution content server instance and the live content server using the connection server + outbound adapter on the sending end together with the subscription client + inbound adapter together on the receiving end. This is failing.
I have double checked the cns.oracle.config (connection server config), siclone.config (subscription client config), and the source content server's configuration (config.cfg), and all seems to be well. Not really sure therefore what is causing this.
Here is a snippet of the error trace that keeps showing up in the subscription client logs ...
[May 18 21:18:34] VERBOSE: scheduler: waiting to run job ICE Connection in 0:00:33.000 ...
[May 18 21:18:34] VERBOSE: replicator: response: 200 OK for Url:http://192.168.131.65:8891/42/E%3a%2fapps%2foracle%2fucm%2fserver%2fweblayout%2fgroups%2fpublic%2fdocuments%2fucmdocs%2fcpseven.pdf
[May 18 21:18:34] INFO: replicator: opened connection http://192.168.131.65:8891/42/E%3a%2fapps%2foracle%2fucm%2fserver%2fweblayout%2fgroups%2fpublic%2fdocuments%2fucmdocs%2fcpseven.pdf in 0:00:00.130
[May 18 21:18:34] ERROR: replicator: ContentSink reported failure to add item.
[May 18 21:18:34] ERROR: replicator: Telling all sinks to rollback changes
[May 18 21:18:34] ERROR: replicator: crawl failed
[May 18 21:18:34] VERBOSE: scheduler: job completed:ICE Request: 43

Don't know if anyone is still having problems with this, but just in case...
I was getting a similar error. I had an Event Viewer record (It wasn't a Warning or an Error, just an Information) reading:You are running a version of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (also called MSDE) that has known security vulnerabilities when used in conjunction with this version of Windows. To reduce your computer's vulnerability to certain virus attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE, or both have been disabled. To enable these ports, you must install a patch, or the most recent service pack for Microsoft SQL Server 2000 or MSDE from http://www.microsoft.com/sql/downloads/default.asp
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I installed SQL SP4 and it corrected the problem

SXMB_MONI : Mapping exception error - cause unknown

Hi! ALL
I am getting a mapping exception error....
However, if i copy the payload and run it through my test tab it is getting processed successfully.
Is there any other way i can debug this issue....as i do not see any problem with payload or the message mapping and I am getting the following error...
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_mm_204: RuntimeException in Message-Mapping transformatio</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Your help is greatly appreciated!!
Thank you,
Patrick.

Dear Patrick,
As our experts told you can trace by using ST01 and select your ID and start the trace then again test be editing and reactivating the scenario and test it again then you ill came to know if in case any issues.
1. Other way to test the scenario is Goto RWB--> Component Monitoring --> Select Adapter Monitoring --> Then select the TEST MESSAGE TAB and give Interface details inputs or copy or take your pay load from MONI and past here and check and changes are to be made and then test the message there itself .
2. Also as u can test the message in Message Mapping TEST TAB and test the mapping and also parallely do Cache Refresh in SXI_CACHE.
3. You can also check the status of the message in SYSEM STACK of message monitoring this is different from RWB message moni
[http://Host name:PORT/MessagingSystem/monitor/systemStatus.jsp]
4. YOu can also trace the message through this system stack also.
Regards:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Jan 30, 2009 8:53 AM

Exception in Managed Server

Can anyone let me know what could be the reason for the following exception.?We
have a clustered WLS 7.0 sp2 server with one admin and one managed server.Both
the servers are starting up properly.But when we run a test case from one system
to an other external system we are getting the following exception in Managed
Server.
Exception :
<Sep 10, 2003 6:40:52 PM BST> <Error> <B2B> <000000> <<Repository> ERROR: Error
getting a Connection from the DataSource "com.bea.wlpi.TXDataSource" in Repository
Session - SQLException: com.bea.wlpi.TXDataSource>
javax.transaction.TransactionRolledbackException: EJB Exception: : java.lang.NoClassDefFoundError
     at com.bea.eci.repository.helper.RepositoryActions.getAllEntities(Unknown Source)
     at com.bea.eci.repository.ejb.XMLRepositoryBean_u3eysh_EOImpl.getAllEntities(XMLRepositoryBean_u3eysh_EOImpl.java:475)
     at com.bt.wli.eai.NetworkBuild.HubStateHandler.cacheMappingDoc(HubStateHandler.java:121)
     at com.bt.wli.eai.NetworkBuild.HubStateHandler.checkExceptionalResponse(HubStateHandler.java:623)
     at java.lang.reflect.Method.invoke(Native Method)
     at com.bea.wlpi.common.ClassInvocationDescriptor.invokeMethod(Unknown Source)
     at com.bea.wlpi.server.workflow.action.ActionBusinessOperation.execute(Unknown
Source)
     at com.bea.wlpi.server.workflow.ErrorHandler.invoke(Unknown Source)
     at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.invokeErrorHandler(Unknown
Source)
     at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.invokeCurrentErrorHandler(Unknown
Source)
     at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(Unknown
Source)
     at com.bea.wlpi.server.workflow.Task.executeActions(Unknown Source)
     at com.bea.wlpi.server.workflow.Task.activate(Unknown Source)
     at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
Source)
     at com.bea.wlpi.server.workflow.Task.markDone(Unknown Source)
     at com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(Unknown Source)
     at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(Unknown
Source)
     at com.bea.wlpi.server.workflow.Task.executeActions(Unknown Source)
     at com.bea.wlpi.server.workflow.Task.activate(Unknown Source)
     at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
Source)
     at com.bea.wlpi.server.workflow.Task.markDone(Unknown Source)
     at com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(Unknown Source)
     at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(Unknown
Source)
     at com.bea.wlpi.server.workflow.Task.executeActions(Unknown Source)
     at com.bea.wlpi.server.workflow.Task.activate(Unknown Source)
     at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccessors(Unknown
Source)
     at com.bea.wlpi.server.workflow.Start.activate(Unknown Source)
     at com.bea.wlpi.server.workflow.Workflow.start(Unknown Source)
     at com.bea.wlpi.server.workflow.Workflow.instantiate(Unknown Source)
     at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean$1.invoke(Unknown
Source)
     at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.performWithErrorHandling(Unknown
Source)
     at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.instantiate(Unknown
Source)
     at com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.instantiate(WorkflowProcessorBean_h7kt4j_EOImpl.java:1064)
     at com.bea.wlpi.server.eventprocessor.EventProcessor.checkTrigger(Unknown Source)
     at com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(Unknown Source)
     at com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(Unknown Source)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2337)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2256)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:215)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:191)
; nested exception is:
     java.lang.NoClassDefFoundError
Thanks and regds
Sudarsan M

Thanks for your reply, Timo, and John, the same file downloading is working fine with my Integrated weblogic server, but the same application when i deployed in my DEV server i am getting the error.
Code which i am trying to download file is
public void downloadCardInserts(FacesContext facesContext,
OutputStream outputStream) throws FileNotFoundException,
IOException {
// Add event code here...
UploadedFile filename=(UploadedFile)browseFile.getValue();
String fname=filename.getFilename();
String fname1="//bwi-wfp-v01/Apps/SCII/TEST/LOG/Cards/RENEWAL/"+fname;
System.out.println("file name11111:"+fname1);
FileInputStream in = new FileInputStream(new File(fname1));
byte[] buffer = new byte[1024];
int bytes = in.read(buffer);
while (bytes >= 0) {
outputStream.write(buffer, 0, bytes);
bytes = in.read(buffer);
}

File Adapter FCC Error

Hi team
i am getting the following errors in the File Adapter when i am using the FCC Parameters.
1)Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'xml.keyfieldName': no value found
2)Conversion initialization failed: java.lang.Exception: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Mandatory parameter 'Detail.keyFieldValue': no value found
My FCC parameters are
Header.fieldNames,Header.fixedLengths,Detail.fieldNames,Detail.fixedLengths
i am receiving a file from the FTP server; the file structure has header and detail records.
Please help me out
tahnx a lot in advance

Hi,
Your header and details lines in the file will contain the first value which differentiates them.
That field becomes your Keyfiled.
Add the following to the configuration:
xml.keyfiledName - the 1st field name from the header and detail
header.keyFieldValue - vakue from the header line
detail.keyFieldValue - value from the detail line
Regards,
Pragati

XI Adapter Framework Error in SXMB_MONI

Hi Experts,
i am getting below error in MONI. Could any one please advice me what is the problem...
*<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
*- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'PAR303SP' (structure 'STATEMENT'): java.sql.SQLException: [CEE9901] Application error. CEE9901 unmonitored by PAR303SP at statement 0000000102, instruction X'0000'.</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>Thanks,
Siva.

Agasthuri,
What should i check in stored procedure - 'PAR303SP', is there any problem with Password expirity or license expirity with database something, Database team is different ..what should i check with that people exactly...
Thanks for ur help..
Thanks,
Siva..

BINDING.JCA-12510 JCA Resource Adapter location error in SOA 11g Suite

Hi,
I am just testing one simple SOA Application in SOA 11g Suite. Created a SOA Composite Application with one DB Adapter at designtime all worked fine with DB Adapter. But when I deploy the Application on the server I get the following error:
The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/DB/soademoDatabase'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/DB/soademoDatabase. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ".Do I need to jndi-name in weblogic-ra.xml if so what is the exact location. Any help is appreciated.
Thanks

I did but still not able to connect now getting the following error. I went to the Weblogic Console, clicked on deployments, selected DBAdapter, clicked on configuration ,
and then I don't see outbound configurations instead it shows Outbound Connection Pools, Under Outbound Connection Pools tab I clicked on New and it asked to select Outbound Connection Group I selected the one that was already there (with JNDI eis/DB/SOADemo) and then created my JNDI which was added to the default Outbound Connection Group and in the end it asked to save the Plan.xml which I saved it under a new directory created under soa directory. But still am not able to connect.
How do I create my own Connection Group as don't want to use the defualt one out there.
After creating the JNDI Name it asks for saving the Plan.xml file. Where exactly we save this file. Are there any standards.
Why can't I update any properties when I click on the new JNDI name it takes to Settings for javax.resource.cci.ConnectionFactory --> Outbound Connection Properties but there I see a save buttn but I can't make any changes.
BINDING.JCA-12563 Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'getCreditValidationSelect' failed due to: Could not create/access the TopLink Session. This session is used to connect to the datastore. Caused by javax.resource.spi.InvalidPropertyException: Missing Property Exception. Missing Property: [DBManagedConnectionFactory.userName]. You may have set a property (in _db.jca) which requires another property to be set also. Make sure the property is set in the interaction (activation) spec by editing its definition in _db.jca. . ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. Is there any documentation that lists all these steps as I couldn't find it anywhere. The guide only talks abou DBAdapter but how to configure etc can't find any info. Any help is appreciated.
Thanks.

Inbound adapter exception/error management

Similar Messages

Maybe you are looking for