Adapter engine e Monitor de serviço da SEFAZ NFE 4.0 OFF

Sap Gears! Estou com um problema depois da atualização para NFE 4.0
Antes da atualização, o monitor de status estava ok
Foi feito atualização dos SPK, TPZ files no XI, Atualização JSPM (JAVA)
Também foi atualizado o APP do NFE e aplicado as notas correspondente ao SPK 16 (ainda não disponível )
Algum santo aqui teria um rumo pra eu seguir?
Agradeço ai pessoal!!!
<< Elabore melhor a questão e dê detalhes que sejam suficientes para entendermos o problema >>
Editado pela Moderação: Fernando Ros on Sep 29, 2010 5:36 PM
Veja Regras de Comportamento item 2

Raphael,
Quando você diz "Monitor de serviço da SEFAZ" você quer dizer o monitor do GRC (http://:80/sap/bc/webdynpro/xnfe/nfe_main)? Se sim, quando você tenta acessar, ocorre um erro?
Se sim, verifique na transação SICF se os servicos do nó default_host -> sap -> bc -> webdynpro (e seus sub-nós) estão ativos.
Quando você diz Adapter Engine, significa que, ao entrar no RWB, Component Monitoring, o Status dele aparece como vermelho, indicando no "Self-test" que o item "Is the Adapter Engine running?" está vermelho?
Se sim, dê uma olhada no defaultTrace em busca de erros.
BTW, poste mais detalhes dos problemas para que fique mais claro onde é o problema.
[]'s

Similar Messages

Adapter Engine: Performance Monitoring?

Dear Experts
I am assessing the PI 7.1 Advanced Adapter Engine and execute a Performance Test against a standard
scenario using the Adapter Engine processing.
I would like to understand and see the 'performance boost', mentioned by SAP, but I am not able to find
a tool which gives me this view on performance (e.g. message processing time) in the Adapter Engine.
The Runtime Workbench tab 'Performance Monitoring' seems to be limited to the ABAP Integration Server.
Is there any settings I can use to get this view? Or is there any other metric which could be used to
validate the actual performance improvement by the AAE?
Thanks for you ideas.
Mathias.

Hi,
You use the Advanced Adapter Engine to connect the Integration Engine to SAP systems (RFC adapter) and non-SAP systems. You use the various adapters in the Adapter Engine to convert XML- and HTTP-based messages to the specific protocol and format required by these systems, and the other way around.
Using Integrated Configuration you can define a local Message Processing on the Advanced Adapter Engine. The Advanced Adapter Engine provides mapping and routing for this locally. Message Processing is only executed on the Advanced Adapter Engine from one adapter to another without the involvement of the Integration Engine. You can gain a great improvement in performance.
You can implement all adapters on the Adapter Engine for a local Message Processing on the Advanced Adapter Engine, apart from the RNIF adapters and the CIDX adapters.
If you do not use Integrated Configuration, Message Processing will always be performed by the Integration Engine to execute the routing and mapping there.
The Advanced Adapter Engine is a separate software component that is automatically installed on the Integration Server. In this case, it is the central Advanced Adapter Engine. However, you can also install the Advanced Adapter Engine separately on another host. This is then a non-central Advanced Adapter Engine.
Please reward points if it helps
Thanks
Vikranth

Adapter engine queue monitoring

Hi All,
I have one doubt about adapter engine queue.
We can see adapter engine queue in RWB->Message Monitoring-> Adapter engine-> Display .
Here in queue if one message goes in to system error status, remaining all messages from that queue goes on holding status.
So unless someone manually clears this system error message, remaining messages from same queue will not be processed.
Is there anything to automate this process? Because currently someone has to manually monitor this queue and clear the message if it is in system error.
Thanks in advance.
Warm Regards,
Gouri

Hi Bhavesh,
I am getting a PO file from source system which contains data and control record. But target system expects two different files for data and control. So in mapping program I have done this.
When interface split happens for one scenario and the multiple messages are going to the same receiver, an internal queue name is generated from the message ID of the original message, to ensure that the correct processing sequence is maintained. As a result, the quality of service switches from EO to EOIO. Here is the reference link:
http://help.sap.com/saphelp_nw04/helpdata/en/28/68073c8e56f658e10000000a114084/frameset.htm
Also can you please elaborate on CCMS?
Thanks in advance.
Warm Regards,
Gouri

XI Production Issue In Adapter Engine Messsege Monitoring

HI every one ,
I am facing a starnge problem. When I am going to SXMB_MONI to check flag status, all messeges are OK and processed. However when I am going to Runtime
workbench - >Messege monitoring - >Adapter Engine, and seeking for system errors/ waiting/ holding / I am getting this as an error.:
Time Stamp Status Description
2008-05-05 11:59:14 Success Admin action: Trying to fail message.
2008-05-05 11:59:14 Success Admin action: The message was successfully
set to status failed.
2008-05-05 11:59:14 Error Trying to deliver asynchronous error
notification (message ID: 94c7b8d0-1a6c-11dd-c9c9-00145e743aaa
(INBOUND)) to sending application:
com.sap.aii.af.ra.ms.api.DeliveryException: Message failed by admin..
2008-05-05 11:59:14 Success Asynchronous error notification
successfully delivered
This messege is available in the Error Log .
Can any one help me why this is happening , and where should I check to detect the probable reason for this!!
points would be Awarded .
Thanks in advance
Arnab
Edited by: Mohd Abdul Khalid on May 5, 2008 9:38 AM

Pls see the error below, this is all what I have......Incase u need some other information, revert back.
Time Stamp Status Description
2008-05-09 00:59:53 Success Trying to put the message into the send queue.
2008-05-09 00:59:53 Success Message successfully put into the queue.
2008-05-09 00:59:53 Success The message was successfully retrieved from the send queue.
2008-05-09 00:59:53 Success The message status set to DLNG.
2008-05-09 00:59:53 Error Received XI System Error. ErrorCode: NO_BACK_SYSTEM_IN_HOPLIST ErrorText: ErrorStack: Legacy system to which acknowledgment message is to be sent is missing in hoplist (with wasread=false)
2008-05-09 00:59:53 Error Transmitting the message to endpoint http://isrxiprd:8000/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: NO_BACK_SYSTEM_IN_HOPLIST:.
2008-05-09 00:59:53 Success The asynchronous message was successfully scheduled to be delivered at Fri May 09 01:04:53 GMT+05:30 2008.
2008-05-09 00:59:53 Success The message status set to WAIT.
2008-05-09 01:04:53 Success Retrying to send message. Retry: 1
2008-05-09 01:04:53 Success The message was successfully retrieved from the send queue.
Thanks in advance!!!
Arnab

Decentralized Adapter Engine working

Hi guys,
I have installed a decentralized adapter engine for my XI Server. I have a scenario which i run with default Adapter Engine(Integration Server), runs fine.
However, when i run it with choosing Decentralized AE it gives such errors in
Message Monitoring:
Exception caught by adapter framework: null
Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
Also i am testing this for two simple file2file scenarios. It's acting differently; in a scenario sender commn channel picks file, in other not.
Is there any configuration settings that's remaining? Or something else?
Regards
Arpil

Hi,
For the picked message, i see this in moni....
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MI_XmlFile_out*</Trace>
<Trace level="1" type="T">select interface namespace urn:Plain2XML</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
Any clue?
Regards
Arpil

Purpose of having central adapter engine

What is the purpose of having Centeral Adapter Engine when any WAS 6.40 has an adapter engine that can communicate de-centrally with the IS?
Regards
chandrakanth.K

Hi Chandra,
The Adapter Engine is a separate software or software component that is automatically installed on the Integration Server. In this case, we will call it as central Adapter Engine. You can also install the Adapter Engine separately on another host. This is then a non-central Adapter Engine.
By installing the adapter engine centrally on Integration Server, all the components like adapter engine, integration engine, mapping runtime etc will be at single place which increases the preformance.
In the case of non central adapter engine, where we will install the adapter engine at another system(may be in another place) which decrease your total server performance.
thanks,
madhu

Question about Integrated Configuration (Advanced Adapter Engine in PI 7.1)

Hello,
When you use Advanced Adapter Engine in PI 7.1 with Integrated Configuration scenario, it bypasses ABAP stack therefore you can't monitor processed message in SXMB_MONI. Instead this message shows up only in RWB Adapter Engine message monitoring. When you select the message from there, you can view the BEFORE mapping payload in Message Content tab. My question is how do you view the AFTER mapping payload when using Integrated Configuration.
Thanks,
Jay

> My question is how do you view the AFTER mapping payload when using Integrated Configuration.
You can't.
So first you have to configure a standard scenario and test the stuff. When everything is fine, remove the standard scenario and create an Integrated Configuration.

How to set main host for Adapter Engine in the HA enviroment

Hi, all.
Our XI env. is like the following.
XI 3.0 SP11 on Windows 2003 + SQL Server.
Central Instance(ABAP + J2EE Addon) is running on Host A,
Dialog Instances(ABAP + J2EE Addon) are running on Host B and Host C.
Our design was to have J2EE Adapter engine mainly running on Host A(CI). But after installation, Adapter Engine is running on Host C(one of DIs). When we check from the Runtime WorkBench. It shows Adapter Engine is running on Host C while IS is running on the Host A(CI).
Where can we change this configuration? We want the J2EE AE running on the Central Instance Host.
Any advice appreciated.
Best Regards.

Hi Sejoon,
when we changed the host of XI server in one of our projects one of the things we had to change was the exchange profile entries
http://server:port/exchangeProfile/index.html
to see how your adapter engine is configured
http://server:port/sld
SLD -> Content Maintenance
then
Subset: landscape description
Class: XI Adapter Framework
buth check the exchange profile entries first
Regards,
michal

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

Adapter Engine Field missing --

Hi All,
I'm trying to create new Communication Channel in our QA system.
I'm using 'Sender File Adapter' But somehow When I choose below option, the last value (Adapter Engine) is blank.
- Adapter type : Sender FILE http://sap.com/xi/XI/System SAP BASIS 7.00
- Transport Protocal : File System (NFS).
- Message Protocal : File
- Adapter Engine : ??????? (Blank)..
We are under PI 7.0 and I did same in Dev but it's not in QA. I think the value of 'Adapter Engine ' should be 'Integration Server'
automatically. Any Idea?
Thanks in advance.

Hi,
Yes, if your adapter reside in the central adapter engine then it should be in the IS.
Adapters that host in different adapter engine, then decental adapter engine need to be selected.
Check you SLD configuration, whether there is an entry for your Adapter Engine or not.
Have a Look on this SAP Note : 764176, do hope it will resolve you problem.
Look for these discussion: Unable to determine name of central adapter engine
Missing Adapter Engine in the XI Domain (in the RTWB view)
Thanks
Farooq.
Edited by: Farooq Farooqui on Jul 31, 2008 7:19 AM
Edited by: Farooq Farooqui on Jul 31, 2008 7:29 AM

Testing through RWB under Adapter Engine

Hi All
I know i can test my scenario through RWB through Test tab.
The problem i am facing is---- when i am testing using Integration Engine after providing necessary details i am getting a message in moni thats fine but when i am testing the same scenario using Adapter Engine by giving same details i am getting error "Error when sending message: 403 Forbidden"
what could be the problem?
Regards
Dheeraj Kumar

Hi Aamir
the test Tab under adapter engine in RWB is used when you have de-centralized adapter engine.
check this page http://help.sap.com/saphelp_nw04/helpdata/en/25/9c2f3ffed33d67e10000000a114084/frameset.htm its saying This Adapter Engine is a central Adapter Engine its not related to de-central Adapter Engine.
This Adapter Engine resides under Integration Server.
so i believe the prob is because of authorization, if i am not correct please correct me, by this answer i am not telling you that you are wrong i am just putting my view.
Please check and if i am wrong correct me.
Regards
Dheeraj Kumar

Want to Change Adapter Engine URL!

Hi Experts,
Currenly my Adapter Engine URL: http://<server>:8001/MessagingSystem/receive/AFW/XI
I wan to change the Adapter Engine URL to: http://<server>:50100/MessagingSystem/receive/AFW/XI
How can it be changed?
Thanks,
karthik

Hi Nisar,
Thanks for response.
I executed a file to file scenario. There I got HTTP error with 404. When I tried to solve it, I found this difference in SXI_CACHE.
In SXI_CACHE-> Goto-> Adapter Engine, an entire is present but with the URL having port 8001.
I belive it has to be changed to 50100.
Kindly help!

Adapter Engine Prioritation for JDBC Adapter

Hi ,
I am currently working on an Idoc to Jdbc Scenario. The jdbc adapter is used to push the messages to three different legacy systems through three different scenarios. I need to prioratize the messages of the legacy systems(For Eg. Legacy System A is more critical than Legacy System B) in adapter engine or in adapter itself.
Regards,
UserPI

Hi
We are having the same problem. Once one of the interfaces which is using a JDBC communication channel is processing a bigger amount of messages, the JDBC adapter seems to be blocked exclusively for that interface. All other interfaces using the JDBC adapter are on hold (status "Scheduled" in Adapter Engine Message Monitoring). I set up message prioritization in RWB (Component: Adapter Engine), but it doesn't help (nothing different from before).
Does anybody has a hint on that?
Thanks
Philippe

ID RFC Adapter Engine Parameter Unstable~

Dear Expert:
I configure an Business System RFC Adapter to connect with R/3.
But weird thing always happen in RFC Adapter parameter "Adapter Engine"
the default setting should be "Integration Server",but sometimes the default value
will disappear,and after i restart xi server the default show up again.
but after a while it happen again.
Can any one tell me what's going on ?
is it a setting problem or hardware problem?
Regards
Jack Lee

>
RAJEEV GUPTA wrote:
> Hi,
>
> But weird thing always happen in RFC Adapter parameter "Adapter Engine" the default setting should be "Integration Server" - No, the default value for the Adapter engine in RFC comm channel should be Central Adapter engine or Adapter engine but not Integration Server.............
>
>
> Regards,
> Rajeev Gupta
Hi Rajeev,
The Integration server option for Adapter Engine in any Adapter means that we are using Adapter Engine installed in the Integration Server. The concept you explained is correct. But the way we choose in channel configuration is different.............:)
Regards,
- Gujjeti.

Adapter Engine / Integration Server Problem

Hi,
I'm new to SAP and I have some questions regarding my new PI 7.0 SP10 setup.
Problem:
In Integration Directory, when I tried to define a communication channel, after specifying the "Adapter Type" (File in my case), I had to specify the "Adapter Engine" from a drop-down. But the dropdown list is empty!
What I've done & Observations:
1. I've recently imported the file "XI7_0_SAP_BASIS_7.00_06_00.tpz" (From the installation DVD). After importing, I've refreshed the SLD cache.
2. SLDCHECK reveals that the connection to SLD is successful.
3. RWB component monitoring shows:
    Integration Server - No light (Node cannot be expanded)
    Integration Engines - No light (Node cannot be expanded)
    Non-Central Adapter Engines -
        Adapter Engine ootspdbs02 (Red Light)
          - Self Test Failed - Details: Client 010 is not available in this system.
          - Cache Connectivity Test:
            Attempt to fetch cache data from Integration Directory failed; cache could not be updated
            [Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.01.ootspdbs02, string], target element type: SAP_BusinessSystem)
    J2SE Adapter - No light (Node cannot be expanded)
    Tools
        - System Landscape Directory ootspdbs02 (Green Light)
        - Integration Directory ootspdbs02 (Green Light)
        - Integration Repository ootspdbs02 (Green Light)
        - Runtime Workbench ootspdbs02 (Green Light)
4. In my SLD - I've defined a business system PI_BS_01
    Role: Integration Server
    Pipeline URL: http://OOTSPDBS02:8001/sap/xi/engine?type=entry
    Group - No Group Assigned.
    Client: 001 of PI1
    Technical System: PI1 on ootspdbs02 - Release 700
Given the above observations, can anyone please point out to me where I went wrong?
Any advise is greatly appreciated.
Thank you.
Best Regards,
Ron Lai

Hi Archana,
The configuration in SLD DataSupplier is:
Latest Send Activity
     2007/01/04 09:18:09:564
Used HTTP Parameters [http host:port] [user] [protocol]
     [ootspdbs02:50100] [SLDDSUSER] [http]
Sending Node [nodeID] [hostname]
     [11621750] [ootspdbs02]
Send Result
     Success
Next Automatic Send Timestamp
     2007/01/04 21:18:08:189
Send Type
     Automatic (Time Scheduled)
Configuration Status
     Valid
The hierarchy of this business system is:
Business System:
   BS_NAUTICUS_OOTS [Role = Application System, Related Integration Server = PI1_BS_01, Technical System = TS_NAUTICUS_OOTS]
Technical System:
   TS_NAUTICUS_OOTS [Type = Third Party, Software Component = SWC_NAUTICUS_OOTS, Product = Product_NAUTICUS_OOTS]
Basically I created product, software component, technical system, business system from scratch.
I did not put any dependencies to existing products/software components.
Regards,
Ron

Adapter engine e Monitor de serviço da SEFAZ NFE 4.0 OFF

Similar Messages

Maybe you are looking for