Stupid error in J2SE Adapter !!!
Greetings,
I am trying a simple scenario sending data from my PC database to XI using J2SE JDBC Adapter (stack 09). The same problem also happen when sending file using File Adapter. I got the following error : Any help is welcome.
Wed Nov 03 08:17:19 GMT+03:00 2004 *****
08:17:19 (4209): Guaranteed Delivery database operation pending
08:17:25 (4212): JDBC adapter initialized successfully
08:17:25 (4202): JDBC adapter started
08:17:25 (4220): Sending message "a2d4a910-2b0f-11d9-a214-e9630a0e6b86" to Integration Engine... (message size: 535 bytes)
08:17:25 (4221): ERROR: Finished sending query result to Integration Engine with error "com.sap.aii.messaging.net.TransportException: HTTP 500 HTTP standard status code
http-Response:
content-type: text/xml
content-length: 1282
content-id: <[email protected]>
soapaction: 'http://sap.com/xi/XI/Message/30'
server: SAP Web Application Server (1.0;640)
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header>
</SOAP:Header>
<SOAP:Body>
<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsse="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" SOAP:mustUnderstand="1"><SOAP:faultcode>Client</SOAP:faultcode><SOAP:faultstring></SOAP:faultstring><SOAP:faultactor>http://sap.com/xi/XI/Message/30</SOAP:faultactor><SOAP:faultdetail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="PARSER">ITEM_MISSING</SAP:Code><SAP:P1>/@versionMajor</SAP:P1><SAP:P2/><SAP:P3/><SAP:P4>ST: ST_XMS_MSGHDR30_MAIN</SAP:P4><SAP:AdditionalText>Attribute 'versionMajor' expected</SAP:AdditionalText><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>XML tag /@versionMajor missing in SOAP message header (SAP XI Extension)
Attribute 'versionMajor' expected
</SAP:Stack></SAP:Error></SOAP:faultdetail></SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
". Skip confirmation and proceed with next query
08:17:25 (4077): Retry mode - wait 10 sec, 0 msec interval before retry
Hi,
AFAIK, builer package shoud be under WEB-INF\classes directory or the context. It is under that direcory.
As far as adding the package to system classpath or Tomcat classpath, I dont want to do that as it would contaminate the classpath of other applications/contexts.
The applications server is supposed to automatically add WEB-INF\classes into the classpath of the context. And its working for other context.
There has to be other solution.
Regards
Amitabh
Similar Messages
-
Ping error in RWB for J2SE Adapter Engine
Hi,
we have several external J2SE adapter engines and they function great other than from a monitoring perspective. In RWB "Ping Status" I'm getting the following:
HTTP request failed. Error code: "401". Error message: "Authorization Required"
Suggestions?
Cheers,
Mattias<u>This is not an answer to your question.</u>
I've tried to get an answer for: how to register J2SE adapter with Integration Server ?
I tried using SLDAccess service on J2SE adapter with no luck (with this J2SE Adapter Engine is registered in the SLD). My J2SE adapter was never available in the configuration means, in the communication channel ex: file adapter, for the adapter engine drop down all I have is Integration Server, my J2SE adapter was never listed there.
If you know an answer please post.
thanks
SKM<u></u> -
J2SE Adapter Installation error
Hi
I'm getting the following error when i try and start the J2SE Adapter service from windows services -
Error opening the Java Virtual Machine (Path: E:\Java\jre6\bin\client)
Its been an issue before when i had spaces in the path, but since then its worked, however now with a fresh install i get this error.
Thanks!Hi Neetesh,
After copying tech_adapter on your local machine douple click on run_adapter.bat and then open internet explorer and enter http://l<ocalmachine_ip_address>:8200/adapter.html
After doing this you will get logon popup, enter user & password and configure the adapters.
Secondly you can see the port in SLDAPICUST if I am not mistaken. (not very sure)
Compare your configuration with below one
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
version=30
mode=FILE2XMB
Integration Engine address and document settings (example, see docu)
XI.TargetURL=http://<host>:8000/sap/xi/engine?type=entry
XI.User=testuser
XI.Password=pass123
XI.QualityOfService=EO
#XI.SenderParty=
XI.SenderService=LocalSystem
#XI.ReceiverParty=
XI.ReceiverService=LocalSystem
XI.Interface=IM_J2SE
XI.InterfaceNamespace=http://abc.com/j2se/test
##File Adapter specific parameters (example, see docu)
file.type=BIN
#file.type=TXT
file.encoding=UTF-8
file.sourceDir=c:/sender
file.sourceFilename=sender1.xml
#file.processingMode=test
file.processingMode=delete
#file.processingMode=archiveWithTimeStamp
#file.archiveDir=./temp_archive
#file.retryInterval=20
file.pollInterval=30
Regards,
Sarvesh -
Hi everyone,
I am facing couple of issues with J2SE adapter engine.
1. First Issue
Config in SLDaccessor -
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleSLDaccessor
SLD.host=<HOST>
SLD.port=50xxx
SLD.user=user
SLD.password=pass
SLD.adapterEngineName=AdapterEngine
Config in Sender File Channel
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
version=30
mode=FILE2XMBWITHROWCONVERSION
XI.SLDConfiguration=SLDaccessor
#XI.TargetURL=http://<HOST>:<50xxx>/sap/xi/engine/?type=entry
XI.TargetURL=<fromSLD>
XI.QualityOfService=EO
XI.Client=001
<Other parameters like InterfaceName / FCC>
If I use XI.SLDConfiguration=SLDaccessor and XI.TargetURL=<fromSLD>, I get an error of HTTP 401 unauthorized.
If I ignore the SLDaccessor, the message is processed successfully.
Am I missing anything in the above configuration?
The user id user is having the roles of SAP_SLD_CONFIGURATOR and SAP_XI_APPL_SERV_USER.
2. Second Issue
In RWB -> Component Monitoring -> J2SE Adapter Engine, there is an error coming up - Unable to establish connection to "https://<LocalHost>:50001/rtc"
The port is wrong ... it should be 8200. My question is, from where to fix this?
Any help will be highly appreciated.
Thanks,
NeeteshHi Neetesh,
After copying tech_adapter on your local machine douple click on run_adapter.bat and then open internet explorer and enter http://l<ocalmachine_ip_address>:8200/adapter.html
After doing this you will get logon popup, enter user & password and configure the adapters.
Secondly you can see the port in SLDAPICUST if I am not mistaken. (not very sure)
Compare your configuration with below one
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
version=30
mode=FILE2XMB
Integration Engine address and document settings (example, see docu)
XI.TargetURL=http://<host>:8000/sap/xi/engine?type=entry
XI.User=testuser
XI.Password=pass123
XI.QualityOfService=EO
#XI.SenderParty=
XI.SenderService=LocalSystem
#XI.ReceiverParty=
XI.ReceiverService=LocalSystem
XI.Interface=IM_J2SE
XI.InterfaceNamespace=http://abc.com/j2se/test
##File Adapter specific parameters (example, see docu)
file.type=BIN
#file.type=TXT
file.encoding=UTF-8
file.sourceDir=c:/sender
file.sourceFilename=sender1.xml
#file.processingMode=test
file.processingMode=delete
#file.processingMode=archiveWithTimeStamp
#file.archiveDir=./temp_archive
#file.retryInterval=20
file.pollInterval=30
Regards,
Sarvesh -
"Performance" problems with the File adapter on Plain J2SE Adapter Engine
Hi,
At the moment I'm on a customer side to solve some XI issues for a few days. One of the issues is the performance of the Plain J2SE Adapter Engine, using the file adapter to transfer XML messages(already XI message format) from the legacy system to the Integration Engine. The File adapter has to deal with "large" XML messages(max at the moment is 65 Mb) and the engine fails with the following error when transferring the big XML file: "ERROR: Finished sending to Integration Engine with error "java.lang.OutOfMemoryError". Skip confirmation and quit this loop".
As far I got the information from the customer the memory use of the Plain adapter engine is set to 512Mb. This is maybe to low. But I don't know where to look for this, I only have the adapter web interface in front of me, no access to the OS it self via for example remote connection.
On the Integration Engine I know there is the ability to split large message with the file adapter(File Content Conversion), but I don't know this for the Plain Adapter Engine. Is there a possibility to do this also on the Plain Adapter Engine?
Thanks in advance for any input.
Greetings,
PatrickHi Sameer,
Thanks for your answers.
On the first solution, yes that is possible, we first decided to see if the legacy system can do the splitting, before starting developing a Java program.
On the second solution, as far as I know is this solution possible on the Integration Engine. But we are facing the problems on the Plain J2SE Adapter Engine. I went trough that documentation(link:
http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm ), to look for I similiar solution in the Plain Adapter Engine. So my question is, is this possible with the Plain Adapter? And if so, what kind of parameters I need to use to achieve this.
Regards,
Patrick -
Installation and then Configuration of Plain J2se Adapter Engine
Hi All,
Actually we want to use JMS Adapter for that we had installed Plain J2SE Adapter Engine but after installing and following the initial steps of Adapter.pdf we are not able to access the Adapter Engine through URL.We are using the URL http://<hostname>:8200/MessagingSystem/receive/AFW/XI
this URL is there in our SLD but we are not able to access the page.
So Please can somebody help me to resolve this issue.
Thanks & Regards
SathyaHi Amol,
I am trying to send read data from MQSeries using JMS adapter. We are successful in opening the Adapter Engine and the GUI. We have cofigured the adpter as follows. But when we try to restart the adapter to get the changes get saved we are getting the following error
<b>"ERROR CALLING THE RESTART ADAPTER"</b>
Also status is shown is yellow and version is shown as not set.
Where ever I have changed the configuration data I have shown it in bold
JMS-Adapter Configurarion
This Configuration is a sample for a JMS sender channel (inbound, sends to XI IS)
Set XI message protocol version. This sample is designed for XI 3.0
version=30
JMS message receiver class
classname=com.sap.aii.messaging.adapter.ModuleJMS2Transport
set if a transacted JMS Session should be used (default: true)
#JMSSession.sessionTransacted=false
set delay in milliseconds before processing next message after an error (default: 0)
errorDelay=10000
#set delay in milliseconds before trying to reestablish the JMS Connection after a connection error (default: -1 (do not try to reconnect))
#reconnectDelay=10000
set the Message Formats you want to process (Formats only needed if they can not be evaluated at runtime)
TransportMessage Type can be set to TransportMessage of XMBMessage. It is used for sending and receiving Transport and XMBMessages
#TransportMessage.type=TransportMessage
TransportMessage.type=XMBMessage
uncomment and adjust parameters for Transformation Type (Binding of JMS-Transport Message),
insert your class here for an individual binding between JMS and Transport Message
uncomment the following line for using Bindings that belong to Tunneling
#transformClass=com.sap.aii.messaging.adapter.trans.JMSTunneling
uncomment the following line for using Bindings that belong to Single Payload Binding
transformClass=com.sap.aii.messaging.adapter.trans.JMSSinglePayloadBinding
ID Garbage Collector: For EO(IO) handling XI adapters store the JMS/XI message ID's in the ID logger
Uncomment the following lines and change the default values if you recognized "out of memory" problems due to
very large ..\tech_adapter\Data\*_ID.dat files which will be kept in the memory as well
eoExpirationAfterDays is the period of keeping the message ID in days. Afterwards the message ID might be used again
garbageCollectorInterval is the period in milliseconds when the ID garbage collector is started. It will however only
be started if messages are exchanged otherwise ID logs won't be created anyway
eoExpirationAfterDays=365
garbageCollectorInterval=86400000
<b>#
the following parameters are used in some Bindings that belong to Single Payload Binding needing XMBHeader Information
uncomment and adjust parameters according your requirements. Please note, that the party identfier needs not to be
configured in case of A2A scenarios.
#XI.SenderParty=Sender
XI.SenderService=MQSeries
#XI.ReceiverParty=Receiver
XI.ReceiverService=MTX
XI.InterfaceNamespace=http://xitest
XI.Interface=MI_Out_File
XI.TraceLevel=1
XI.LoggingLevel=1
XI.QualityOfService=EO
XI.QueueId=ABCD
XI.ContentType=text/xml
#</b> *************************************************************************************************************
<b>#
URL of XI IS to send the messages to
XI.TargetURL=http://bwxi:50000/sap/xi/engine?type=entry
XI.User=XIAF
XI.Password=XIPASS
#</b> *************************************************************************************************************
URL of file adapter if a loopback JMS to File should be configured
XI.TargetURL=//localhost:8210/file/receiver
<b># uncomment the following settings if needed (independent on JMS provider)
JMS.QueueConnectionFactoryImpl.user=xisuper
JMS.QueueConnectionFactoryImpl.password=xxx
#</b>
uncomment and adjust parameters for loading JMS administrated objects via JNDI
uncomment and adjust parameters if not the default context should be used
#JNDI.InitialContext.property.1=java.lang.String {javax.naming.Context.INITIAL_CONTEXT_FACTORY}, java.lang.String com.sap.engine.services.jndi.InitialContextFactoryImpl
#JNDI.InitialContext.property.2=java.lang.String {javax.naming.Context.PROVIDER_URL}, java.lang.String localhost:50004
#JNDI.InitialContext.property.3=java.lang.String {javax.naming.Context.SECURITY_PRINCIPAL}, java.lang.String Administrator
#JNDI.InitialContext.property.4=java.lang.String {javax.naming.Context.SECURITY_CREDENTIALS}, java.lang.String sap
set the Lookup Names
#JMS.JNDILookupNameQueueConnectionFactory=jmsfactory/default/joetest
#JMS.JNDILookupNameQueue=jmsQueues/default/sapDemoQueue
uncomment and adjust parameters for loading JMS administrated objects from filesystem ***
#JMS.FileNameQueueConnectionFactory=SAPQueueConnectionFactory.ser
#JMS.FileNameQueue=SAPQueue.ser
uncomment and adjust parameters for creating SonicMQ JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=progress.message.jclient.QueueConnectionFactory
JMS.QueueConnectionFactoryImpl.constructor=java.lang.String localhost:2506
JMS.QueueImpl.classname= progress.message.jclient.Queue
JMS.QueueImpl.constructor=java.lang.String SampleQ1
<b># uncomment and adjust parameters for creating MQSeries JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=com.ibm.mq.jms.MQQueueConnectionFactory
JMS.QueueConnectionFactoryImpl.method.setHostName=java.lang.String BWXI
JMS.QueueConnectionFactoryImpl.method.setChannel=java.lang.String JAVA.CHANNEL
JMS.QueueConnectionFactoryImpl.method.setTransportType=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP}
JMS.QueueConnectionFactoryImpl.method.setQueueManager=java.lang.String QM_BWXI
JMS.QueueImpl.classname= com.ibm.mq.jms.MQQueue
JMS.QueueImpl.constructor=java.lang.String postcard
JMS.QueueImpl.method.setTargetClient=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ}
#</b> *************************************************************************************************************
uncomment and adjust parameters for using a dispatcher ***
#Dispatcher.class=com.sap.aii.messaging.adapter.ConversionDispatcher
#Dispatcher.namespace=namespace1
#namespace1.ConversionDispatcher.logPayload=true
#namespace1.Service.1=Plain2XMLService
#namespace1.Plain2XMLService.class=com.sap.aii.messaging.adapter.Conversion
#namespace1.Plain2XMLService.xml.conversionType=SimplePlain2XML
#namespace1.Plain2XMLService.xml.processFieldNames=fromConfiguration
#namespace1.Plain2XMLService.xml.fieldNames=a,b,c
#namespace1.Plain2XMLService.xml.fieldSeparator=;
#namespace1.Service.2=XSLTService
#namespace1.XSLTService.class=com.sap.aii.messaging.adapter.XSLTConversion
#namespace1.XSLTService.XSLTConversion.XSLTFileName=Data/DemoConversion.xsl
Can you please help me in resolving the error.
Regards, -
Null Pointer Exception in Plain J2SE Adapter Engine
Hi All,
I am able to start the J2SE Adapter Engine. But when ever i click any button on my JMS Adapter i am getting
Error stopping adapter: java.lang.NullPointerException
Error terminating adapter: java.lang.NullPointerException
Can somebody guide me why this error is comming or the possible reasons for the error.
Thanks in Advance.
rahulHi Rahul,
Please can you go through the thread
J2SE Adapter Engine / JMS Adapter
It does not talk about the error but the config need to be done for JMS. Hope this helps.
Regards
Vijaya -
FTP to AS/400 from J2SE Adapter
Hi,
I setup a J2SE adapter that with push the XML through XSLT to produce a flat file that in turn is to be FTPed to an AS/400 machine.
This is an extract of my adapter config:
<i>##File Adapter specific parameters
file.createDir=0
file.targetDir=/FTPBARSA
file.targetFilename=WARHEADTST
file.writeMode=append</i>
This works 100% to my IIS FTP, however, to the AS/400 I get the following error:
ERROR: Message processing failed with "java.lang.Exception: com.sap.aii.messaging.adapter.ftp.FTPEx: Unknown extension in database file name."
If I use the .SAVF after the target filename, I get the following error code:
ERROR: Message processing failed with "java.lang.Exception: com.sap.aii.messaging.adapter.ftp.FTPEx: Unable to close file. Error code CPE3101. Data transfer ended."
I am able to put the file using DOS FTP without a problem.
Any idea how I can do the transfer to the AS/400?
Rgs,
Johan SchoemanAlthough inactive wondering if solution was ever found to this I/O error and if so what?
Thank you. -
Receiver File Adapter J2SE Adapter Engine
Hi,
We have configured a receiver file adapter on a J2SE adapter engine through the administrator page of the J2SE adapter.
XI.httpPort=8222
XI.httpService=/file/Receive
and the rest of the adapter parameters.
I have configured a channel in ID as XI receiver adapter.
host: "hostname"
Service: 8222
Path Prefix: /file/Receive
The messages in sxmb_moni fail to be delivered with "HTTP error 404 Resource not found."
Through a browser I am also not able to make a connection to this url:
"host":8222/file/Receive
Getting Http error "501".
Please can someone shed some light on this problem.
Regards
Willie Hugo>Through a browser I am also not able to make a connection to this url:
>"host":8222/file/Receive
>Getting Http error "501".
This is ok. Since get method not implemeted for this service.
Since from XI you are getting this error "HTTP error 404 Resource not found", can you logon to XI server at OS level and do a telnet test to check if the port is working.
cmd> telnet
telnet> open <J2SEAdpaterEngineHostName (or) IPAddress> 8222 -
Registering Plain J2SE adapter in IS
Hi,
I've been trying to use plain J2SE file adapter as receiver with no luck.
I've installed plain J2SE adapter on a windows 2000 server called <b>tgrpser1</b>, and XI is on another Windows 2000 server <b>tgrpserxi</b>.
SLDAccessor service is started with no error in <b>tgrpser1</b>.
When go to the SLD, the adapter engine shows up in the XI technical system but when I go to the Integration Directory to configure a file adapter as receiver for <b>tgrpser1</b>, the <b>Adapter Engine</b> has one value <b>Integration Server</b>.
Please help...
ThanksI think I should it put this way.
I have a plain J2SE adapter engine running on <b>tgrpser1</b> (it is not an FTP server), I've copied the <b>file_receiver</b> adapter to <b>rec_File_adapter</b>.
If the scenario is RFC -> XI -> File (on <b>tgrpser1</b>), how can I specify the <b>rec_File_adapter</b> in Integration Directory.
If I am not correct, what is the use of plain J2SE adapter engine <b>file_receiver</b> ?
Thanks -
Problem: Plain J2SE Adapter Engine
Hello,
I have installed the Plain J2SE Adapter Engine.
On the Adpater Engine running a SOAP Adapter.
When i try to test the Adapter i become following error Message:
java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at com.sap.aii.messaging.net.ClientHttpImpl.call(ClientHttpImpl.java:146)
at com.sap.aii.messaging.adapter.SinglePayloadClient.doPost(SinglePayloadClient.java:222)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.aii.messaging.adapter.Zone.service(ModuleGUIBrowserEngine.java:1073)
at com.sap.aii.messaging.adapter.HTTPRequest.run(ModuleGUIBrowserEngine.java:371)
any idea?
Regards,
RobinHi Stefan,
SOAP Adapter module settings:
Bubble adapter java class
classname=com.sap.aii.messaging.adapter.ModuleBubble
This adapter instantiates a bubble bag for supporting
a xmb web service gateway. A bubble bag is a collection of Bubble
instances that form some processing chain of message objects.
Below parameter Bubble.Helper specifies the helper class that implements
the ModuleBubbleHelper interface. This class is used to instantiate
a bubble bag for this adapter.
Sets the bubble module helper that can instantiate your bubble bag
Bubble.Helper=com.sap.aii.messaging.adapter.ModuleBubbleHelperXMBWSImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
Below this line are the parameters specific to the ModuleBubbleHelperXMBWSImpl
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
The configuration of this helper class is divided in two parts. The first part
specifies the adapter configuraton for Web-Service clients communicating with an
XMB server. The second part specifies the configuration for XMB clients
communicating with a WebService server. Either one or both parts can be configured
in a single configuration file.
Part 0 (FromWS and ToWS) : common part ######
Keeps the XMB headers in web service messages
XMBWS.KeepHeaders=true
Keeps the attachments in web service messages
XMBWS.KeepAttachments=false
Encodes the xmb headers into a special HTTP header string x-xmb_ws_encoded
XMBWS.UseEncoded=false
Part 1 (FromWS) : WS clients to XMB server ######
The target URL of XMB broker, to which the adapter sends XMB messages.
XMB.TargetURL=http://netweaver:8000/sap/xi/engine?type=entry
The port and path where the adapter waits for web service messages from clients.
XMBWS.WSPort=4444
XMBWS.WSPath=/soap/start
The following XMB attributes are used to fill default XMB messages.
XMB.SenderBusinessSystem=MOS_BS
XMB.SenderInterfaceNamespace=ns:moskau
XMB.SenderInterfaceName=MOSOut
XMB.QualityOfService=BE
now i have an other error message.
com.sap.aii.messaging.net.TransportException: HTTP 500 Internal Server Error
http-Response:
content-type: text/xml
content-length: 349
content-id: <[email protected]>
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Body><SOAP:Fault><faultcode>SOAP:Server</faultcode><faultstring>com.sap.aii.messaging.srt.BubbleException: Can't call the endpoint; Exception raised by com.sap.aii.messaging.net.TransportException: Content-Type not set</faultstring></SOAP:Fault></SOAP:Body></SOAP:Envelope>
at com.sap.aii.messaging.net.ClientHttpImpl.call(ClientHttpImpl.java:337)
at com.sap.aii.messaging.adapter.XMBTestClient.doPost(XMBTestClient.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.aii.messaging.adapter.Zone.service(ModuleGUIBrowserEngine.java:1073)
at com.sap.aii.messaging.adapter.HTTPRequest.run(ModuleGUIBrowserEngine.java:371) -
Standalone (J2SE) adapter - axis SOAP adapter - issue duplicate messages
All,
Perhaps you can help me. I've setup a scenario where an standalone (J2SE) adapter sends a file to SAP XI channel, configured on the central adapter engine, of type SOAP configured to use Axis servlet.
The connection is setup and the standalone adapter channel logs thre response from the SOAP channel which reads HTTP error 500, indicating a duplicate message.
SAP has identified this problem and proposes in the FAQ for Axis (note 1039369) to set on the SOAP channel module CallSapAdapter property ignoreDuplicate to true in the module processor.
I've implemented this as suggested however found the problem persists. I'm still receiving an HTTP 500 error.
Your help is much appreciated solving this problem.
Thanks
HaraldAs there was a bugfix recently, make sure that you have installed the latest patch.
If this does not work, open an OSS ticket for this issue.
Stefan -
Plain J2SE adapter and SLD configuration
Hi all,
I'm trying to configure Plain J2SE Adapter to be connected to SLD for purpose of automatic registering to SLD. I followed the description in PDF manual, but I still get following error:
Error creating adapter services for
J2SE_AE_server2.dummy.com_8200 com.sap.lcr.api.cimclient.LcrException: CIM_ERR_FAILED:
SAP_BusinessSystem.CreationClassName="SAP_BusinessSystem",Name="AdapterSenderService"
referenced by association SAP_SenderAdapterForBusinessSystem.Antecedent=ref"SAP_XIAdapterService.CreationClassName=\"SAP_XIAdapterService\",
Name=\"file_sender2is\",SystemCreationClassName=\"SAP_XIAdapterEngine\",SystemName=\"J2SE_AE_server2.dummy.com_8200\"",
Dependent=ref"SAP_BusinessSystem.CreationClassName=\"SAP_BusinessSystem\",Name=\"AdapterSenderService\"" does not exist.
Do I need to setup something special in SLD ? I thought the registration should work without adding of any BusinessSystems to SLD ... I suppose it should work as autoregistering in SLD via the user parameter SLD.user mentinoed in the config file SLDaccessor.properties.
Any ideas ?
Thank you in advance.
Regards
TomHi Tomas,
After the PI installation we have to do post installation step, if not done pls refer this SAP help to configure it..
http://help.sap.com/saphelp_nwesrce/helpdata/en/98/fa9b6ec510404dbcfebf35cb107c04/frameset.htm
Hope it helps..
Thanks,
Kumar. -
Decentralized J2se adapter issue
Dear Gems,
My J2se adapter is configured to pick a file and archive to a different folder.My current issue is
Adapter pics the file posts to Integration server and while archiving it creates 0kb file with the below error.
This is not happening all the time. can any one guess?
Log:
Oct 14, 2010 1:42:30 PM ...i.messaging.adapter.File2XMBProcessor [Thread[nterface,5,main]] Error: Confirmation failed: Moving sent file 'sample file path.xml' to archive failed
java.io.FileNotFoundException: Sample file path.xml (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.<init>(FileInputStream.java:135) at com.sap.aii.messaging.adapter.File2XMBProcessor.archiveFile(ModuleFile2XMB.java:2123) at com.sap.aii.messaging.adapter.File2XMBProcessor.processFileAccess(ModuleFile2XMB.java:1928)at com.sap.aii.messaging.adapter.File2XMBProcessor.run(ModuleFile2XMB.java:1009) at java.lang.Thread.run(Thread.java:811)
Thanks
Prabhakar TeegavarapuHello Prabhakar,
This problem is solved in a patch.
Please read this SAP note:
1492379 - Archived file in FTP Sender Communication Channel is empty
This note may also be helpfull, even though the description of it doesn't match your issue.
SAP note 1225693.
Enjoy the weekend!
Jorge Eidelwein -
Hi
Is there any way of activating native monitoring from within the J2SE Adapter engine? How do we monitor errors on the J2SE Adapter engine automatically?
Can it notify us automatically if an error occurs?
Thanks!Hi Riaz,
>>>I would like specific alerts based on the type of error on the adapter to be sent to recipients in a mail distribution list for instance.
You can call SALERT_CREATE RFC from the Java adapter module and raise alerts based on the error.
Refer:
/people/amol.joshi2/blog/2006/11/27/alerts-from-adapter-modules--the-jra-way
Regards,
Aravind
Maybe you are looking for
-
Can I use my external hdd with OSX server
Hi i am thinking about using OSX server, but I dont have very much space on the computer I would b running it of of so I would store everything on my 4TB Wd external HDD. Is this posible, and how would I set it up to do that? Also, my external also h
-
Planned & Actual Production report
Hello all MY requirement is , i need to add this two req in the one report ( Z transaction ), Planned Production - This must show the production plan for the current week only. We should be able to drill in further and see the actual day of plann
-
Tax Code from ECC Contract or Info Record not picking in SRM7.0 SC
Hi Experts, We are configuring SRM7.0 with ECC6 (Ehp4) having Classic Scenario. In SRM Tax setting, we set as u201CTax calculation in backend systemu201D, we created and mapped Tax code with ECC and it is working fine. In our case, Tax Rate varies as
-
External Class/Objectdefinitions and the Displaylist
Hello, I have several Objects that control an Array of several Movieclips. Is this Object also a DisplayObjectContainer that is part of the Hierarchy of Display Objects? The problem with this would be, that if I would add another type of objects to c
-
Import dmp file from a 64-bit to 32-bit database
I encountered the problem for import data from one database installed on a 64-bit HP-UX 11.0 with 8i database 64-bit database to another which was installed on HP-UX 10.2. 32-bit machine with Oracle 7.3.4 database. The two databases were installed wi