Adapter Engine Error Message on RWB
Hello
We are getting an Red color error message on Adapter engine on RWB
monitoring ---> Component Monitoring.
Here is the error message:
SLD access SLD host:port = sap03:50000
Error getting JPR configuration from SLD. Exception: No entity of class
SAP_BusinessSystem for XID.SystemHome.sap03 found
No access to get JPR configuration
Please advise for solving the error message on adapter engine.
Thanks & regards
AK
SAP Version : NW04 (XI 3.0) SP20
Hi Senthil,
As suggested by others there is no problem with your communication channels ,,, the problem you face is because Your DBA has initiated the SHUTDOWN IMMEDIATE command. This will shutdown Oracle and terminate all active operations.
Please tell him to start the services and Wait until Oracle has been restarted by your DBA.
Regards
joel
Similar Messages
-
Hello guys!
During performing PI 7.1 Readiness Check I have to perform a test message under Runtime Workbench\Adapter Engine\Test Message.
After processing i receive following error:
Error while sending message: 403 Forbidden.
Does anybody know the cause?
Many thanks in advance!
JochenHi Sreeni!
Direct hit!
This was the problem! Missing role!
Many thanks to you!
Additional Information for all:
Readiness Check (PDF)
A compilaton of simple and advanced checks for Process Integration 7.1 (PI 7.1)
Page 44
SAP Note 817920 - XI Readiness Check 3.0/7.0, 7.1
Regards,
Jochen -
Abap tables for adapter engine errors
Hello,
Which ABAP tables in PI will have the data relating to adapter engine errors (like the communication channel errors). Is there any way I can get the adapter engine errors from abap tables?
Any help is very much appreciated.
Thanks
MLSHello,
What I am trying to do is write a report in ABAP, which will read the table for errors (for messages which are not processed successfully in Integration engine or adapter engine) and email those errors to users. If there is communication channel error in RWB, the message in sxmb_moni is still shown as success and is not being updated in table SXMSPERROR.
We cannot use PI Alerts here since the email list is dynamic for the same PI interface.
Any ideas on how to accomplish this?
Thanks
MLS -
How to get Alerts mail for adapter engine errors in SAP PI 7.0
Hi Friends,
I configured Alerts in PI 7.0. with the help of t-code u2018ALRTCATDEF and created a new alert catergory.
In container tab i have mentioned all give below elements.
SXMS_MSG_GUID, SXMS_RULE_NAME, SXMS_ERROR_CAT, SXMS_ERROR_CODE, SXMS_FROM_PARTY, SXMS_FROM_SERVICE, SXMS_FROM_NAMESPACE, SXMS_FROM_INTERFACE, SXMS_TO_PARTY, SXMS_TO_SERVICE, SXMS_TO_NAMESPACE,SXMS_TO_INTERFACE
I am getting alerts when I manually test the alerts configurations by running the report u2018RSALERTTESTu2019.
I am getting mail as :
Alert ID: ##00009##
Dear Administrator,
This is with respect to XI Scenario. During processing of XML file from ECC or XYZ Server, Following error has been occured:
Message ID:
Interface:
NOTE: To check the file name, go to SXMB_MONI and search for above message ID.
Double click on that message ID and click on error in left hand tree.
Please take appropriate action in co-ordination with respective functional and BASIS consultant.
But When I am getting a error , I am not getting an alert mail. Right now iam doing in XI Development.
I am not getting an Alert mail , when my message is in status of : System Error . Error catergory is : XI_J2EE_ADAPTER_JDBC.
Kindly tell how to get alert mail for error catergory : XI_J2EE_ADAPTER_JDBC and in Adapter engine errors.
How to get alert mail when my message is failed with any reason in Adapter engine.
Waiting for quick replay. Please help me out.
Regards,
Ahmed.Hi thanks for quick reply.
As per your given link : http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/14877. [original link is broken]
I have done all these steps. But still little problem.
as per link he is getting Error description , error message id , alert rule..
In my case I am not getting these information. when my messages failed. When I am doing manully testing the alert getting an mail as :
Alert ID: ##00009##
Dear Administrator,
This is with respect to XI Scenario. During processing of XML file from ECC or XYZ Server, Following error has been occured:
Message ID:
Interface:
NOTE: To check the file name, go to SXMB_MONI and search for above message ID.
Double click on that message ID and click on error in left hand tree.
Please take appropriate action in co-ordination with respective functional and BASIS consultant.
Is it okay the body of mail??.
I am not getting alert mail when my messages failed in adapter engine and Integration Engine.
Ex my message is failed in AE:as below.
My messages flow as : SAP --> XI --> DB.
Messages is success (in ECC moni)> XI moni also success> XI Adapter engine getting error as (Status: System Error) and (Error Category : XI_J2EE_ADAPTER_JDBC).
Regards,
Ahmed. -
Cancel System Error Messages from RWB
Hi All,
I have nearly 3000 messages those were got System Error in Integration Engine process, but when i check messages in SXMB_MONI all are success and written to target folders also.There is no problem absolutely.
Now i just want to cancel those System Error messages from RWB--Message Monitor to keep system green and do not want to see those system error messages again.
Iam not able to cancel those messages from RWM, it is saying that User and pwd incorrect but iam providing correct one only.
I went to details of that system error message from Message Monitor, i took message id and filtered with that in SXMB_MONI. i got the message with error state.Iam able to cancel that from MONI but not from RWB which is fine and disappearing from RWB list.
the thing is i can't copy each and every message id by opening details button for every message
How can i proceed for this. please advice me
REgardsHi Ravi,
For example iam able to see system error message in RWB--Message Monitor under Integration Engine at 9:30
when i execute SXMB_MONI for the same time and see, there is no error message for that able to see success.
When i took message id from RWB--message monitor and filter that in MONI means it is showing me the error message.
I can able to cancel it from MONI which is fine. but this way i have 3000 messages in RWB--Message monitor under IE.
How to copy and paste then filter those error messages in MONI???this is pain process to copy each and every one by one
Iam not able to get those if i filter with the status group as System Error manual Restart Possible criteria
Regards -
Alert for adapter engine error
Hello experts
We have configured the alerts for the adapter engine errors .We have configured the variable &SXMS_TO_ADAPTER_ERRTXT& element which is having the CHAR70 type for getting the adapter engine error text in the alert inbox.so for any adapter engine error greater than 70 chracters ,it is getting truncated to 70 chracters only.but we want to have the whole adapter error log text.
Can anyone please throw some light on this.
Thanks
sabyasachiMoha,
It seems that it cannot support more than that.
Problem with Alert Text
Re: Message Size in ALERTS
It is worth taking a look at this blog:
/people/community.user/blog/2006/10/16/simple-steps-to-get-descriptive-alerts-from-bpm-in-xi
Regards,
---Satish -
Adapter Engine URL missing in RWB
Hi All,
In my newly configured PI 7.0 system, the Adapter Engine URL is missing at the fol. location:
RWB -> Component Monitoring -> Adapter Engine -> Test Message.
But when I open SXI_CACHE -> AE Cache, I am able to see the url http://pidev:50000/MessagingSystem/receive/AFW/XI
I think that this means that my ABAP stack is configured properly, but JAVA stack has some problem for Adaptr engine.
Please confirm if I am right and how to resolve this.
regards,
PiyushHi,
Are you using the FQHN?
Check also note #764176 if you have components missing on SLD.
Last, you may want to configure your system in order to check each of the steps.
Use this link -> Wizard-Based Basic Configuration:
http://help.sap.com/saphelp_nw70/helpdata/en/a0/40084136b5f423e10000000a155106/frameset.htm
Regards,
Caio Cagnani -
Message flow between advanced adapter engine and messaging system for ICO scenarios
Dear all,
I'm working on a PI 7.31 AEX box and created an ICO object for one interface with HTTP_AAE2IDoc scenario. The interface works quite well. When I looked in to message log of messages for this interface in PI monitor, I noticed that the internal XI message are put totally 5 times into the send queue and retrieved from send queue. In some steps I only see after retrieving a message from send queue and immediately put it back into send queue. Can someone please kindly explain the message flow between advanced adapter engine and messaging system and what exactly happens after each retrieving a message from send queue?
Below is an example of message log for one message:
12/08/2014 09:26:06.472 Information MP: processing local module localejbs/CallSapAdapter
12/08/2014 09:26:06.472 Information Application attempting to send an XI message asynchronously using connection HTTP_AAE_http://sap.com/xi/XI/System
12/08/2014 09:26:06.478 Information Trying to put the message into the send queue
12/08/2014 09:26:06.499 Information Message successfully put into the queue
12/08/2014 09:26:06.499 Information The message was successfully retrieved from the send queue
12/08/2014 09:26:06.499 Information The application sent the message asynchronously using connection HTTP_AAE_http://sap.com/xi/XI/System. Returning to application
12/08/2014 09:26:06.500 Information HTTP adapter successfully processed interface PlantResponse_Out
12/08/2014 09:26:06.501 Information Trying to put the message into the send queue
12/08/2014 09:26:06.501 Information Message status set to DLNG
12/08/2014 09:26:06.513 Information Message successfully put into the queue
12/08/2014 09:26:06.513 Information The message was successfully retrieved from the send queue
12/08/2014 09:26:06.515 Information Message status set to DLNG
12/08/2014 09:26:06.533 Information Trying to put the message into the send queue
12/08/2014 09:26:06.548 Information Message successfully put into the queue
12/08/2014 09:26:06.548 Information The message was successfully retrieved from the send queue
12/08/2014 09:26:06.550 Information Message status set to DLNG
12/08/2014 09:26:06.551 Information Executing Request Mapping "http://styrolution.com/pi/Integration/PlantMaintenance/PlantResponse/PlantResponse_to_Zcol_Basf_Inotif02_Inotif01_Zeupm_Inotif01_Ludwigshafen" (SWCV 085d2320fb3b11e2cc0bf4d50aea8c33)
12/08/2014 09:26:06.563 Information Trying to put the message into the send queue
12/08/2014 09:26:06.571 Information Message successfully put into the queue
12/08/2014 09:26:06.571 Information The message was successfully retrieved from the send queue
12/08/2014 09:26:06.573 Information Trying to put the message into the send queue
12/08/2014 09:26:06.573 Information Message status set to DLNG
12/08/2014 09:26:06.580 Information Message successfully put into the queue
12/08/2014 09:26:06.580 Information The message was successfully retrieved from the send queue
12/08/2014 09:26:06.582 Information Message status set to DLNG
12/08/2014 09:26:06.583 Information Delivering to channel: IDOC_R
12/08/2014 09:26:06.583 Information MP: processing local module localejbs/IDocOutboundModuleBean
12/08/2014 09:26:06.583 Information XI message received for processing
12/08/2014 09:26:06.587 Information Sender Party: Sender Service:SXX Receiver Party: Receiver Service:RXXCLNT200 Communication Channel:IDOC_R
12/08/2014 09:26:06.588 Information IDOC metadata repository is RXX
12/08/2014 09:26:06.589 Information Control record is not mandatory - control record will be added if not available
12/08/2014 09:26:06.590 Information XML Payload parsed to idoc document list with number of idocs: 1
12/08/2014 09:26:06.595 Information Sending idoc message to receiver R/3 system with TID XIh{lsRI824UITC0009OalmW
12/08/2014 09:26:06.813 Information IDOC message sent to receiver R/3 system
12/08/2014 09:26:06.817 Information TID XIh{lsRI824UITC0009OalmW confirmed
12/08/2014 09:26:06.819 Information Message was successfully transmitted to endpoint <local> using connection HTTP_AAE_http://sap.com/xi/XI/System
12/08/2014 09:26:06.821 Information Message status set to DLVD
Thanks & regards
DingjunHello All,
Thanks for the prompt responses and with best information, But apart from this,I need how an adapter(File/JDBC) works along
with AAE in PI 7.1. When does the job of File/JDBC adapter is completed and resumed in a synchronous case. That is,
File Location --> file adapter -
> XI(AAE) --> JDBC adapter --> database.
In file sender, lets suppose we have synchronous settings(Best Effort). Now when File adapter's job is finished and when it
gets back the response back from XI. Please explain step by step from starting(file adapter polling the location) to getting the response coming back to XI.
Regards,
Achari. -
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 -
Adapter Engine not visible in RWB
Hi Guys,
I coudnt find the Adapter engine in Component Monitoring and Message monitoring in RWB.
while displaying the components of Integration Engine getting the below error. I am using PI 7.1
Kindly let me know where to check if the components are not visible in RWB.
java.lang.NullPointerException:
at com.sap.aii.mdt.web.MonitorDynPage.setNewComponent(MonitorDynPage.java:635)
at com.sap.aii.mdt.web.MonitorDynPage.process_go_button(MonitorDynPage.java:496)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:102)
at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:295)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
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:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
With Regards
Pradeep NCheck page 129 of this document:
[SAP XI TroubleShooting Guide|https://websmp109.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000659947&_OBJECT=011000358700005909032005E] -
Adapter engine error: EXCHANGE_PROFILE_ACCESS Error
Hi,
When I am running any scenario I am getting the following error in the RWB.
<b>Received XI System Error. ErrorCode: EXCHANGE_PROFILE_ACCESS ErrorText: ErrorStack: Error when reading Exchange Profile for system C12 and client 100
Transmitting the message to endpoint http://myserver:8001/sap/xi/engine?type=entry using connection AFW failed, due to: EXCHANGE_PROFILE_ACCESS:.</b>
In file-xi-file scenario (which was running successful) the file is picked up but, I am not getting any messages in SXI_MONITOR.
Can any one help me troubleshooting this problem.
Thanks,
Nagarjuna.Hi,
1) Whethere you have created two communication channel one for sender and another for receiver.( check you have selected theright option sender and receiver in the adapter )
2) Are you using BPM.
3) Some time we will get this error if XIRWBUSER is locked.
Try unlocking XIRWBUSER user from su01. ( In su01 you will have a lock button which will show you the staus if the user is locked or not)
Kindly check whether you posses the roles required to access the RWB are:
1. SAP_XI_RWB_SERV_USER
2. SAP_XI_RWB_SERV_USER_MAIN
4) Cross check the below :
a)Ensure that the required JDK is being used in the client system
b)Try clearing the Web Start cache and try downloading again.
c)Start>Programs>Java Web Start>File>Preferences>Advanced>Clear Folder
5)Refresh the Cache :
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
And also try this :
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss -
Hi,
i am working on MQ-XI-BW Scenario.i have configured JMS Adapter in Plain J2SE Adapter Engine.But the status is red with a message
"javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'BWXI:TEST.QMGR'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1450)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:960)
at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:159)
at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:215)
at com.sap.aii.messaging.adapter.ModuleJMS2Transport.init(ModuleJMS2Transport.java:382)
at com.sap.aii.messaging.adapter.ModuleHandlerImpl.run(ModuleHandlerImpl.java:576)
at java.lang.Thread.run(Unknown Source)"
My class path looks fine.i am on SP9. there is an OSS note with similar error. But the Pre requisite is given as SP5.
what could be the reason behind this issue?
When i try to refresh the central integration server cache in ID using Env->Cache Notifications, i am getting a message
http connection to "http://bwxi:8200/CPACache/invalidate" returns the status code "401" in response
This particular URL is not accepting any user and password. Do i need to set the user name and password somewhere so that i can have access to this?
Please help me out.
Regards
SathyaHi Amol,
Thanks a lot.I am not very confident in my configuration.Could you please verify the configuration parameters once?
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
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.
XMB.SenderBusinessSystem=MQSeries
XMB.SenderService=BS_MQ
XMB.SenderInterfaceNamespace=http://xitest
XMB.SenderInterfaceName=MI_Out_File
XMB.ReceiverBusinessSystem=MTX
XMB.TraceLevel=1
XMB.LoggingLevel=1
XMB.QualityOfService=EO
XMB.QueueId=ABCDEFABCDEF
XMB.ContentType=text/xml
URL of XI IS to send the messages to
XMB.TargetURL=http://bwxi:8000/sap/xi/engine?type=entry
XMB.User=XIISUSER
XMB.Password=Mind2005
XMB.Client=100
URL of file adapter if a loopback JMS to File should be configured
XI.TargetURL=//localhost:8210/file/receiver
uncomment the following settings if needed (independent on JMS provider)
JMS.QueueConnectionFactoryImpl.user=MUSR_MQADMIN
JMS.QueueConnectionFactoryImpl.password=Mind2005
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
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 CH_BWXI
JMS.QueueConnectionFactoryImpl.method.setTransportType=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP}
JMS.QueueConnectionFactoryImpl.method.setQueueManager=java.lang.String TEST.QMGR
JMS.QueueImpl.classname= com.ibm.mq.jms.MQQueue
JMS.QueueImpl.constructor=java.lang.String LQ
JMS.QueueImpl.method.setTargetClient=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ}
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
Regards
Sathya -
Non Central adapter engine error
Hi All, Here is my Scenario: Trying implement /configure Non-central adapter engine hosted separate (J2EE) server. This will be connected to XI server(Integration engine and SLD) from where messages are sent/received. When I try to post message from XI to Non_central adapter engine following is the message u201CThe requested protocol u201CXIu201D is currently unavailableu201D Then I realized there is a problem in Non-central adapter engine configuration, which will be connected to SLD and Integration engine. I can see technical system and business system in SLD for Non-central adapter engine. Following is the findings in NWA of same host where non-central adapter engine. 1) I see all J2EE services are running 2) Application u201Ccom.sap.aii.adapter.soap.libu201D is no started and status is u201Cfailed to startu201D. Later I tried to restart and following are the 4 error messages in sequence from trace file. a) Message: Access to XI AF MS resource failed. Date: 2010-07-02 Time: 22:05:15:273 Category: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory Location: com.sap.aii.adapter.soap.ra.SPIManagedConnectionFactory.SPIManagedConnectionFactory() Application: Thread: Deploy Start Application Thread Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc B) [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. [EXCEPTION] com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [sap.com/com.sap.aii.adapter.soap.lib]. at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:619) at com.sap.engine.services.deploy.server.application.StartTransaction.rollbackPart(StartTransaction.java:653) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:506) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) ... 8 more Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) C) Cannot bind "com.sap.aii.adapter.soap.lib";. [EXCEPTION] com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) d) Global operation [startApp] over [application] [sap.com/com.sap.aii.adapter.soap.lib] finished with errors for [16]ms on server [4796750 >>> without warnings << >> Errors <<< 1). Cannot bind "com.sap.aii.adapter.soap.lib";. -> Object with name com.sap.aii.adapter.soap.lib is already bound. 2). com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot bind "com.sap.aii.adapter.soap.lib";. at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:393) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.initResourceAdapter(ResourceAdapterStarter.java:122) at com.sap.engine.services.connector.deploy.ConnectorContainerImpl.prepareStart(ConnectorContainerImpl.java:303) at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:363) at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:251) at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:209) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:502) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:483) at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:584) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runMe(ParallelAdapter.java:180) at com.sap.engine.services.deploy.server.application.ParallelAdapter.access$000(ParallelAdapter.java:43) at com.sap.engine.services.deploy.server.application.ParallelAdapter$1.run(ParallelAdapter.java:340) at com.sap.engine.frame.core.thread.Task.run(Task.java:73) at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:175) at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:274) Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameAlreadyBoundException: Object with name com.sap.aii.adapter.soap.lib is already bound. at com.sap.engine.services.jndi.implserver.ServerContextImpl.bind(ServerContextImpl.java:343) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:850) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:695) at com.sap.engine.services.jndi.implclient.ClientContext.bind(ClientContext.java:912) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.bind(ResourceAdapterStarter.java:487) at com.sap.engine.services.connector.deploy.util.ResourceAdapterStarter.instantiateMCF(ResourceAdapterStarter.java:375) Any of you have seen this kind of problem. Thanks Sam Edited by: sam robert on Jul 2, 2010 10:24 PM
Hi Sam,
1- What is your PI version?
2- Do you use a High Availability system?
3- Can you describe your scenario?
From the 503 error, here is a generic description:
The error message 503 Service unavailable Application stopped! is displayed.
Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
u2022 Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
u2022 The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
u2022 Refer SAP Note 803145,807000,791655
Regards,
Caio Cagnani -
Custom JCA Adapter / Application Error - Message.setErrorInfo() ??
Hi All,
I was looking for how to create a sensible Application Error in a custom JCA adapter and was excited to find the following page in the PCK info on Adapter Development:
http://help.sap.com/saphelp_nw04/helpdata/en/3c/53d6409ff68631e10000000a1550b0/frameset.htm
The part of interest being:
<i>
The following methods are available to enable you to read error information in the form of an ErrorInfo object from the message, or to set the error information in a message.
Message.getErrorInfo()
Message.setErrorInfo()
If the synchronous response message is an application-error message instead of an application response, it must call setErrorInfo(myErrorInfo) for receiver adapters.</i>
However, I can't find these methods, or indeed the "ErrorInfo" object anywhere in the AF classes - does anyone know it's whereabouts? Or is the above page just out of date? If so, what is the new approach for creating Application Level Errors in a custom JCA Resource adapter (not Exceptions - I can do that)
Many thanks,
ChrisWell, you can get the latest jars from the SMP (Service Marketplace) directly. These jars are in the <i>XI ADAPTER FRAMEWORK CORE 3.0</i> component. Basically, http://service.sap.com/swdc then Support Packages and Patches->SAP NetWeaver->SAP NETWEAVER->SAP NETWEAVER 04->Entry by Component->J2EE Adapter Engine (PI/XI). There you'll see the XI ADAPTER FRAMEWORK CORE 3.0 link.
OR here is the direct link for the SP19 (latest) of <a href="https://smpdl.sap-ag.de/~swdc/012002523100009492712006D/SAPXIAFC19P_4-20000272.sca?_ACTION=DL_DIRECT">SAPXIAFC19P_4-20000272.sca</a>
Within this is <i>aii_af_lib.sda</i> which has the jars. You can use winzip or winrar to open .sca, .sda files.
Regards,
Jin -
Schema Validation using Adapter Engine : Error
Hello Guys,
For SOAP message coming into PI, I am doing schema validation by adapter engine but getting below error message
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: Schema Schema1.xsd not found in /usr/sap/PID/<Server>/j2ee/cluster/server1/validation/schema/af7c332075ce11e08e23ddce0a512253/urncompany.comcrmexternald2c/ServiceRequest_Out/urncompany.comcrm~enhancements/Schema1.xsd (validation/schema)
* at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1178)*
* at sun.reflect.GeneratedMethodAccessor336.invoke(Unknown Source)*
* at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)*
* at java.lang.reflect.Method.invoke(Method.java:585).........................*
Here are some details
- Using standard SAP Message Type
- Enhance data type
- while exporting schema, there are 3 files in zip file
1) mainschema (renamed it to MessageType name)
2) Schema1.xsd
3) Schema2.xsd
I have followed the step according to below document
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d06dff94-9913-2b10-6f82-9717d9f83df1?QuickLink=index&overridelayout=true
I have also checked schema1.xsd on PI server and File is there but still getting error.
Any suggestions ?
Thanks
Edited by: chetan patel on Jan 31, 2012 10:50 PMPlease make sure that main xsd uses import or include tag to reference both schema1.xsd and schema2.xsd. If the main xsd does not do it, Pi cannot verify it. Since you package all the files as zip file, also make sure the path for the secondary files are in proper location.
In short, the import element allows you to use schema components from any schema; the include element allows you to add all the components of an included schema to the containing schema. If the target namespace is same for both then include tag should be good enough. If you don't find one, you might have to use include tag element in the main or parent xsd file.
Edited by: Baskar Gopal on Jan 31, 2012 5:18 PM
Maybe you are looking for
-
Can't get EE and SE to play nicely with deploytool
Hi, I have tried the following combinations of installations: j2se 1.4.x / j2ee 1.4.x (beta) j2se 1.4.x / j2ee 1.3.1 j2se 1.3.1 / j2ee 1.4.x (beta) With all of these combinations, the deploytool utility which comes with the j2ee bundle crashes on me
-
Anyone shed some light on this???
Hi there, I have a class that returns a value based on a calculation with in the class 2 of the variables are called from a database, which is working however when I try to output the result on a jsp page ie. calling the property 'rating' I am told i
-
Adding headings in Adobe Acrobat 8 does not work
Hello! I use Acrobat 8 Pro and want to add page numbers to a long pdf file (290 pages) using the Add Header ... function. If I select finally "Add", nothing happens. No question or srenn appears. Why? Any help is appreciated.
-
Trouble importing FLV into flash - keep gettingan error
Hello all, I'm hopping that someone else has had this problem before. I'm a long time user of Flash but have just downloaded the the newest version (CS3) to try it out. I was really looking forward to the video capabilities. ANYWAY, I'm on a new IMac
-
Syclo : Error in connecting Work Manager Client with Agentry Server
Hi, Can somebody please shed some light on work manager client-server connections? I have downloaded the "SAP_WORK_MANAGER_BY_SYCLO_5.2" package from market place and set up the Work Manager server. It can successfully connect to the SAP back-end. En