Error In Runtime Workbench (Integration Engine)

Hi All,
I have an issue with the PI Netweaver 7.0 SR3.We change the client from 001 to newclient by following SAP NOTE.
Everything is happening fine except while i use Transaction SXMB_IFR and then Run Time Work Bench in component monitoring Integration Engine is not in Healthy State,Its showing Yellow Signal and a message is like this
Is Web service security available?
Description :Communication error Proxy calls are not permitted on sender or receiver side on the IS (client)
Also Business Process Engine is also Showing Yellow Signal as
Schedule Background Job for Missed Deadlines
    Schedule Background Job for Work Items with Errors
    Schedule Background Job for Event Queue
    Schedule background job for clearing report
    Schedule Background Job for Shared-Memory Update of Container Fa
    Schedule Background Job for Deadline Monitoring
So please suggest how to proceed to fix these issues.
Thanks,
Gagan Deep Kaushal

Hi,
for WS security please have a look at this page (last question)
http://help.sap.com/saphelp_NW04/helpdata/en/a5/1b5342d8a7be30e10000000a155106/content.htm
you can also try my answer from:
Re: RWB Integration Engine status yellow
BTW
this cal stay yellow and it does not mean that XI/PI will not work
Regards,
Michal Krawczyk
Edited by: Michal Krawczyk on Nov 29, 2008 1:11 PM

Similar Messages

Error in Runtime Workbench, Component Monitoring, Proxy Runtime

Hi,
I have the following error in the Runtime Workbench, under Component Monitoring->Integration Engines->Proxy Runtime. The error message is Ping Status: Unable to logon to system xxx in language EN with user XIRWBUSER. However, I am unable to find out where the account and password are specified in order to correct this. Any help would be appreciated.

Hi,
it can be for some system configured on http destination or the sld system configured for this server.
take a look at tx sxmb_adm for the http destination to discover witch destination is been used. then, on sm59, find the server that is been called for this http destination and check on that server if this user is ok there.
to check sld, go to tx sld_apicust discover witch is the sld system configured for this server. After log on to sld system and check the user.
Maybe the user is ok on the destination system, so, check the password on sm59 (if the problem is with an http dest) or sld_apicust (if the problem is the connection to sld).
regards.
roberti

Error in Runtime WorkBench/Configuration/Save Configuration

Hi all,
In Runtime WorkBench, when i choose "Configuration" tab, and after choose "Save Configuration", i get an error message as below:
"Configuration saved RFC ping failed for the following RFC destinations (created upon saving) in the system DEV800: PMIDEV800, PMITST910"
In this case, my XI system has one Integration Server: DEV800 and one Business System TST910. Two RFC (Process Monitoring Infrastructure RFC) created: PMIDEV800, PMITST910 can't not function correctly. And i don't know how i can correct this error.
Anyone can please help me to correct this error?
Thanks a lot in advance,
Vinh Vo

hi vinh vo,
do chk this link
Installing and Configuring SAP Interactive Forms by Adobe for the SAP NetWeaver Composition Environment
Thanx
Sampath

Errors in Runtime workbench after support pack stack 12

We have installed support pack stack 12 and now the runtime workbench - component monitoring is not working. I get a page of errors. here are some of the errors
Unknown error: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:250: cannot resolve symbol symbol : method getTestModel () location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel CompTestModel testModel = cmMainModel.getTestModel(); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:283: cannot resolve symbol symbol : method getTextFromCore (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_tray_0.setTitle( cmMainModel.getTextFromCore("component_monitoring") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:391: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_listBoxItem_0.setValue( cmMainModel.getText("all_lbi") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:415: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_listBoxItem_1.setValue( cmMainModel.getText("red_lbi") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:439: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_listBoxItem_2.setValue( cmMainModel.getText("redYellow_lbi") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:486: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_button_0.setText( cmMainModel.getText("go_button") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:647: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_button_1.setText( cmMainModel.getText("tree_view_button") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:662: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel String label = cmMainModel.getText("switchToTableView"); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:703: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_button_2.setText( cmMainModel.getText("ccms_button") ); ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1117074148914.java:808: cannot resolve symbol symbol : method getText (java.lang.String) location: class com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel jspxth_hbj_group_1.setTitle( cmMainModel.getText("searchResults_group") );
I have done the java support pack again to make sure it was installed properly.
Thanks,
Dede Logan

Well after the SAP XI server was restarted and I tried to go back into the runtime workbench and then into the Component Monitoring I am getting another error.
Unknown error: com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_jsp_error1117123949279.java:74: setFeedbackToUser(com.sap.aii.rwb.web.util.Feedback) in com.sap.aii.rwb.web.application.model.AppMainModel cannot be applied to (com.sap.aii.rwb.util.web.Feedback) appMainModel.setFeedbackToUser( ^ /usr/sap/XI0/DVEBMGS70/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_jsp_error1117123949279.java:79: setFeedbackToUser(com.sap.aii.rwb.web.util.Feedback) in com.sap.aii.rwb.web.application.model.AppMainModel cannot be applied to (com.sap.aii.rwb.util.web.Feedback) appMainModel.setFeedbackToUser( ^ 2 errors .
does anyone know how to correct this error or what the cause of the error.
dede

Error in Runtime WorkBench/Component Monitoring

Hi all,
1. I have configured an AS ABAP system to connect to the SLD successfully. In the Technical System List of SLD, it's named "TE1 on sap0810". (Successful)
2. After, i have created a Business System corresponding for this Technical System "TE1 on sap0810" with Client 810. In the Business System List of SLD, it's named "BUSINESS_SYSTEM_TE1CLNT810". (Successful)
3. And after, i log on into Runtime WorkBench and choose "Component Monitoring" Tab and choose Display all component, i get an error about the Business System "BUSINESS_SYSTEM_TE1CLNT810" for "Ping Status" and "Self-Test Status" as message below: (Error)
Ping Status: Unable to log on to system BUSINESS_SYSTEM_TE1CLNT810 in language en with user PIRWBUSER Last Retry Jul 28, 2008 5:48:56 PM ICT ... Details
Self-Test Status: Unable to log on to system BUSINESS_SYSTEM_TE1CLNT810 in language en with user PIRWBUSER Last Retry Jul 28, 2008 5:48:56 PM ICT ... Details
Anyone can please help me to resolve this problem?
Thanks a lot in advance,
<removed by moderator>
Vinh Vo
Edited by: Mike Pokraka on Jul 28, 2008 5:07 PM

hi friend
If you have created the TS & BS correctly in SLD
check the following points:
1)The JCO service might have been down...check it out....Sometimes it happens due to overloading of server...try to restart the server.....after clearing queue and cache restarting the server
2)check the RFC destinations AI_DIRECTORY_JCOSERVER, AI_RUNTIME_JCOSERVER.
regards
kummari

Error in Runtime workbench.

Hi Experts,
In the runtime workbench i have seen a error, the message direction is inbound. The error details are :
Delivery of the message to the application using connection AS2_http://seeburger.com/xi failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Cannot lookup the ra connectionFactory. Reason: Path to object does not exist at SeeXIAS2, the whole lookup name is deployedAdapters/SeeXIAS2/shareable/SeeXIAS2.: java.lang.Exception: Cannot lookup the ra connectionFactory. Reason: Path to object does not exist at SeeXIAS2, the whole lookup name is deployedAdapters/SeeXIAS2/shareable/SeeXIAS2.
Could you please let me know why exactly the error has occured ?
Many Thanks,
Ravi

Hi,
Please check if you have configured the AS2 adapter properly ...
Please confirm it as per the sample scenario give in AS2 Manual.
Refer the links for the AS2 Manuals
SEEBURGER EDI &AS/2 adapter installation and configuration guides
Thanks
swarup

Integration Engine Proxy Runtime Error

Hello,
I have ECC and PI server for my landsacpe. When i ran SXMB_IFR tcode in my ECC server i got the follwing error under Runtime work Bench
Proxy Runtime - it is shows red color.
Unable to log on to system ECC120 in language en with user PIRWBUSER
Details for Ping Status
Message: Unable to log on to system ECD210 in language en with user PIRWBUSER
Stacktrace:
com.sap.aii.rwb.exceptions.OperationFailedException: Unable to log on to system ECD210 in language en with user PIRWBUSER
at com.sap.aii.rwb.core.XIAbapRTCComponent.getConnector(XIAbapRTCComponent.java:114)
at com.sap.aii.rwb.core.XIRTCComponent.ping(XIRTCComponent.java:209)
at com.sap.aii.rwb.web.componentmonitoring.model.CompTestModel.doPing(CompTestModel.java:581)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doPing(CmDynPage.java:425)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.updateTests(CmDynPage.java:525)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.selectNode(CmDynPage.java:552)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.process_treeClick(CmDynPage.java:481)
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:324)
at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:115)
at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at jsp_FC_Secure1229621978943._jspService(jsp_FC_Secure1229621978943.java:15)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
When i checked my PIRWBUSER password in abap and poratal level there is no conflicts. Password is correct.
For integration i have created three RFC also
LCRSAPRFC,SLDAPIRFC,SAPJ2EE all these RFC are working fine and there is no error.
Can any one suggest me how to resolve this issue.
I am waiting for your reply.
Regards,
Sankaranarayanan.G
BASIS CONSULTANT

Hi Tuhin,
I have one more problem now. Intially i have configured my PI development portal.But after some days in my PI server when i ran SXMB_IFR is detecting wrong poral now. I have tried to change from my EXCHANGE Profile under integratrion server parameters i have changed PORT,URL and others.
but it is not come to effect. can you please help me where do i need to chage the portal?
I am waiting for your reply.
Regards,
Sankar.G

Proxy Runtime errors in Integration Engines at RWB

Hi Experts,
We have configured the point to point configuration scenario in our landscape. I have two ABAP systems exchanges data using PI. I have configured both the ABAP systems as Application Systems and Corresponding Integration server as my PI system.
In RWB of PI I can see both these systems as proxy run time under Integration Engines, but are in error status.
Path to the same is Component Monitoring>Components>Integration Engines (here I can my systems as Proxy Runtime BSAB200, Proxy Runtime BSID200).
When run the test got the below error.
Can the SLD be reached? RFC destination LCRSAPRFC does not exist
Does the Integration Engine know the business system?
Are roles in SXMS_CONF_ITEMS and SLD consistent?
Why do we need to create the RFC destination again when we select the related integration server as PI.
Can any one throw some light whey are these errors are occured.
Thanks,
Chinna

Can the SLD be reached? RFC destination LCRSAPRFC does not exist
Reached to SLD but not to exchange profile.
Does the Integration Engine know the business system?
Yes.
Why do we need to create the RFC destination again when we select the related integration server as PI.
A central SLD scenario involves a central SLD, but not a central exchange profile.
The exchange profile used is always the one on the Integration Server the
application system connects to the exchange profile using the SM59 destination
LCRSAPRFC.
Regards
Pothana

SAP PI 7.1 - Runtime Workbench Error - "Service Unavailable"

Hi there,
We have just installed SAP PI 7.1 on an iSeries 6.1 server, all seems to be successfully installed except that the runtime workbench will not start. It seems to be that the runtime workbench service was not deployed successfully during the install.
The error when trying to launch the Runtime Workbench is:
Application cannot be started!
Details: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5004] Cannot create application loader for application sap.com/com.sap.xi.rwb.
     at com.sap.engine.services.deploy.server.utils.LoadContextUtils.defineSharedApplicationLoader(LoadContextUtils.java:100)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.bindLoader(DeployServiceImpl.java:1780)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:216)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:419)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:495)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:248)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3387)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3373)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:749)
     at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.start(ApplicationManager.java:180)
     at com.sap.engine.services.servlets_jsp.server.deploy.impl.ApplicationManager.analyseAppStatusMode(ApplicationManager.java:288)
     at com.sap.engine.services.servlets_jsp.server.DeployContext.startLazyApplication(DeployContext.java:334)
     at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:86)
     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:309)
     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)
Caused by: java.lang.IllegalStateException: [ERROR CODE DPL.DS.6102] The sap.com/com.sap.xi.rwb class loader is not null, but sap.com/com.sap.xi.rwbcom.sap.engine.boot.loader.ResourceMultiParentClassLoader722bac67alive for the LoadContext, which is wrong /nHint: The reason could be leaking class loaders.You can also check, whether above in the stack trace, there is a call to unregister the loader.
     at com.sap.engine.services.deploy.server.utils.LoadContextUtils.ensureLoaderNameAndUnregisteredLoader(LoadContextUtils.java:52)
     at com.sap.engine.services.deploy.server.utils.LoadContextUtils.defineSharedApplicationLoader(LoadContextUtils.java:72)
     ... 34 more
Has anybody had this error before? Or how easy is it to manually re-deploy the service again?
Thanks for the help
Lynton

I have just seen this on the forum as well which is exactly the same question that I have....
RWB application cannot be started after PI 7.1 installation
I will try it now and will let you know
Lynton
Edited by: Lynton Grice on Aug 18, 2009 12:29 PM

Error in Component Monitoring(Runtime Workbench)

Hi,
I am getting an error in component monitoring section of runtime workbench. I got a note(851711), where it says 'CompilingException' error can be corrected by applying SP14. But I am still getting same error after applying SP14 and redeploying XI ADAPTER FRAMEWORK CORE 3.0 (SAPXIAFC.sca), XI TOOLS 3.0 (SAPXITOOL.sca) and XI ADAPTER FRAMEWORK 3.0 (SAPXIAF.sca). Please advice how to correct this error.
Error Message:
com.sap.engine.services.servlets_jsp.server.jsp.exceptions.CompilingException: Error while executing the compilation process: D:/usr/sap/QN7/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1138903402125.java:27: as of release 1.5, 'enum' is a keyword, and may not be used as an identifier (try -source 1.4 or lower to use 'enum' as an identifier) import com.sapportals.htmlb.enum.TableCellStyle; ^ D:/usr/sap/QN7/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1138903402125.java:947: as of release 1.5, 'enum' is a keyword, and may not be used as an identifier (try -source 1.4 or lower to use 'enum' as an identifier) compTable.setColumnType(com.sapportals.htmlb.enum.TableColumnType.IMAGELINK, 1); ^ D:/usr/sap/QN7/DVEBMGS00/j2ee/cluster/server0/apps/sap.com/com.sap.xi.rwb/servlet_jsp/rwb/work/jsp_component_monitoring1138903402125.java:948: as of release 1.5, 'enum' is a keyword, and may not be used as an identifier (try -source 1.4 or lower to use 'enum' as an identifier) compTable.getColumn(1).setCellHAlignment(-1, com.sapportals.htmlb.enum.CellHAlign.CENTER); ^ 3 errors .
Thanks,
Ask.

Hi,
it can be for some system configured on http destination or the sld system configured for this server.
take a look at tx sxmb_adm for the http destination to discover witch destination is been used. then, on sm59, find the server that is been called for this http destination and check on that server if this user is ok there.
to check sld, go to tx sld_apicust discover witch is the sld system configured for this server. After log on to sld system and check the user.
Maybe the user is ok on the destination system, so, check the password on sm59 (if the problem is with an http dest) or sld_apicust (if the problem is the connection to sld).
regards.
roberti

Error: System not configured as XI Integration Engine

Hi All,
I a getting this following error in RWB-->message monitoring -->adapter engine -->audit log
"2007-11-29 09:28:45 Error Received XI System Error. ErrorCode: SYSTEM_NOT_CONFIGURED_AS_XMB ErrorText: ErrorStack: System not configured as XI Integration Engine
2007-11-29 09:28:45 Error Transmitting the message to endpoint http://p2p:8003/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SYSTEM_NOT_CONFIGURED_AS_XMB:.
what might be the possible errors..
regards,
Rajesh

Hi Rajesh,
you can go through these chek steps
1)go to SLD-->Business systems...and check the role of business system Web AS ABAP (tht was created during installation)...check if the role is integration server
2) go to sxi_cache and in the menu tool bar goto "GoTo" and click AE cache and see if the link is fine? whether the link in sxi_cache for AE cache is showing green traffic signal and also perform a delta refresh.
3)Check whether your business system is tied to the integration server in SLD.
4)In the transaction sxmb_adm -> Integration Engine Configuration can you check whether that role has been defined as Integration Server.
hope these checks will solve your problem
Thanks
sandeep sharma
PS:If helpful Plz reward points
Also you may check whether in specific configuration you may need to add Category as Runtime Engine_Type and current value as HUB.

In Runtime Workbench the messages fails with the error

Hi,
Os : Sun Solaris
Database: oracle
Sap: XI 7.0
In Runtime Workbench the messages fails with the following error:
2007-09-28 15:46:38 Error Delivery of the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: java.lang.NullPointerException.
system messages fails with following Error Message:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>503</SAP:P1>
<SAP:P2>Service Unavailable</SAP:P2>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 503 with the description Service Unavailable Error while sending by HTTP (error code: 503, error text: Service Unavailable)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Appreciate the response.
Thanks,
Sri.

Hi,
1)Check your J2EEs server is up
2)Check the adapter engine/status in RWB
The might help
1) 503 service unavailable
2) Note-803145
Regards
Agasthuri Doss

PI Integration Engine RUNTIME LOGGING_SYNC for individual Interfaces

Hello Colleagues,
the Integration Engine Configuration parameter (SXMB_ADM) RUNTIME, LOGGING_SYNC, 0 is an global parameter and active for all sync. interfaces.
Is there a different configuration available/possible for control individual interfaces.
That means, we need to activate syc. logging for less important interfaces, for the rest interfaces (with high rate of transfer) disable logging.
Any suggestions?
Many thanks in advance!
Regards,
Jochen

Many thanks Amit and Shabarish,
for reply!
The Blog "XI/PI: Personalized logging & tracing" from Michal was already known.
Under "Error Analisys Settings" your are able to set only a less number of "conditions" like Username, Client, MessageID, QOS and QueueID. These conditions are not really usable to control individual interfaces.
Maybe .... If logging is deactivated then it can be reactivated with a message. To do this the logging tag in the diagnostic header of the message must be set to 1 .... this is a possible way for individual control of interfaces?
Regards,
Jochen

Log on to Runtime Workbench : click display error on page

Dear all,
when i try to log on to Runtime Workbench and click on display message , i am getting error that error on page,
we have already done post implementation steps for PI(XI),,
what to do, to test the senario from Runtime Workbench.
Best regards,
dushyant.

Hi,
This will help you
SAP Note-768456 & SAP Note-928862
http://help.sap.com/saphelp_nw2004s/helpdata/en/06/5d1741b393f26fe10000000a1550b0/content.htm
Regards
Agasthuri Doss

Error while testing message from Integration Engine.

Hi,
Trying to send message to Integration engine from RWB, using test mesage tab in Integration engine.
I pasted the payload(IDOC payload) , entered sender service, interface name and namespace and also username and password. Selected quality of servie as Exactly once.
While sending the message getting the following error - "Error while sending".
What could be possible reasons for this error.
Thanks.

Hi,
Please check the following possibilities:
1. Make sure you have selected integration Engine oprtion and not the adapter engine.
2. The USERID and password should be correct.
Please let me know if you still face the problem.
Regards,
Shwetambari.

Error In Runtime Workbench (Integration Engine)

Similar Messages

Maybe you are looking for