Can't reach the Central Adapter Engine (HTTP 403)

Hello,
in a simple scenario (AdapterEngine -> IntegrationEngine -> AdapterEngine) we get a HTTP 403 failure in the 'Call Adapter' - Service.
When we try to connect the URI "http://:50000/MessagingSystem/receive/AFW/XI" and logon with user XIISUSER we get the same error.
XI Release is: XI3.0 SP17 ... Adapter Engine is the central engine ...
... any ideas?
Thanks
André

Hi Andre,
HTTP 403 is related to authorisation error.
This topic has already been discussed. I paste hereunder:-
Check if the service users XIAFUSER and XIISUSER are not
locked.(TCODE: SU01)
Also check if these service users have sufficient authorizations.
XIAFUSER: SAP_XI_AF_SERV_USER_MAIN,SAP_XI_APPL_SERV_USER
XIISUSER: SAP_XI_IS_SERV_USER_MAIN,SAP_XI_IS_SERV_USER
I hope this provides you a solution.
Regards.
Praveen

Similar Messages

ADAPTER in the Central Adapter Engine

Hello
I have problem with my Adapter in the Central Adapter Engine. There are to adapter inside, a JMS and A JDBC. This two adpater have in the monitoring status green. But JMS adapter get no message in the system, and by the JDBC adapter the select is not getting Data, but the update make it the right update to the databank. Can somebody help or gives there a log on the system.
Regards Thomas Neuhaus

Hi Thomas,
I think you are using Message Monitoring transaction SXMB_MONI only.
Central Adapter Engine log:
Start Runtime Workbench (i.e. http://<xi_host>:<j2ee_port>/rwb/index.jsp)-> Message Monitoring -> select Component af... -> Display -> select Period -> Start
Regards,
Jiri

Whats the Advanced Adapter Engine ?

What is Advanced Adapter Engine and how its different from normal adapter engine

HI Prathna
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.
cheers
Abhishek

PI 7.11 Central Adapter Engine is not started

Hi Experts,
After active objects list, in the central adapter engine: ache update not yet started.
Looking for this error, is possible that is the RFC INTEGRATION_DIRECTORY_HMI because responde 403 forbidden,
Did you have any tips?
Thank you!
Bruno

Are you sure supplied credentials are valid for PIISUSER?
1) HTTP response does not contain a valid XML root tag or Error 'HTTP status code 400 Bad Request' while executing HTTP request (calling method 'get_status')
The error 'HTTP response does not contain a valid XML root tag' occurs when path prefix of the destination is '/dir/hmi_cache_refresh_service/ext'.
The error 'Error 'HTTP status code 400 Bad Request' while executing HTTP request (calling method 'get_status')' when path prefix is '/dir/CacheRefresh'.
Solution: Go to transaction sm59 and open destination of type 'H' INTEGRATION_DIRECTORY_HMI. Select "Connection Test". The connection test should return HTTP response 200.
Now go to "Logon & Security" tab and ensure that username and password are stored in the system. Fixing credentials should fix the problem.
Note: Credentials cannot be tested via "Connection Test" tool. If used credentials are wrong, the server simply returns login html page (using HTTP response code 200). As the login html page is not a valid cache refresh xml document, an error is shown in sxi_cache.

Non-central adapter engine not visable in integration builder

ls,
I have a pi system and a separate non-central adapter engine. After installing i did all the post actions including the following part:
5.13 Clearing the SLD Data Cache after Installing a Non-central Advanced Adapter Engine
When you have installed a non-central Advanced Adapter Engine, you need to manually clear the SLD Data Cache in the Integration Builder to make it visible and selectable in the communication channels.
Procedure
1.
After SAPinst has finished, open the Integration Builder of your PI system at http://<host>:<port>/dir/start/index.jspIntegration Directory and logon as a user with the ABAP role SAP_XI_CONFIGURATOR assigned.
2.
In the Integration Builder, choose Environment.
3.
From the drop-down list, choose Clear SLD Data Cache.
(as described in: Installation GuideAdapter Engine (Java EE) 7.1 Including Enhancement Package 1 on Windows: MS SQL ServerTarget)
However when creating a communication channel in the integration builder there is only the central adapter engine to choose in parameter tab screen.
I was hoping maybe some-one knows what else need to be done to make de non-central known as adapter engine.
thanks in advance
Peter

HI,
with user PIDIRUSER i was indeed able to refresh the af cache. Unfortunately without a positive
Under the runtime workbench (http://<host>:<port>0/rwb/index.jsp) tab sld registration i don't see the ae neither under non-central components. If i try to register i get:
Registration of Adapter Framework with SLD was successful
Registration of fix AF adapter services with the SLD was successful
Registration of dynamic CPA cache based AF adatper services with SLD was successful
but no AAE...although it is visible in the SLD under technical systems...

SOAP Adapter at XI 3.0 Central Adapter Engine

Hello,
I'm trying to use the SOAP Adapter with the Central Adapter Engine. It works with the J2SE-Adapter Engine, but not with the Central Adapter Engine.
I Get the Error: No response Available.
Perhaps someone can help me.

The J2SE adapter is a relict from XI 2.0
You may still use it, especially for migration from XI 2.0 to XI 3.0, but it is recommended to use the J2EE adapter engine.
Regards
Stefan

URL for Central Adapter Engine

Hi,
It seems like our XI Server is unable to locate the Central adapter engine for doing an outbound RFC call. I am trying to call an RFC using the RFC adapter, and getting the following error:
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.nw4.netweaver</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>no_messaging_url_found: Unable to find URL for Adapter Engine af.nw4.netweaver</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.nw4.netweaver</SAP:Stack>
Where do we maintain the URL of the adapter engine ?
thanks,
Manish

I have the same problem since we changed the name of the database server - the server name reported in the error is the old name. I've checked all the properties in this thread, plus follwed through OSS note 764176 with no luck. All the properties reflect the new name, but testing the proxy (SPROXY) still fails with the error:
<CODE>INTERNAL.AE_DETAILS_GET_ERROR</CODE>
<ERRORTEXT>Error when reading the access data (URL, user, password) for the Adapter Engine af.xix.sapsbxcrmdb2</ERRORTEXT>
sapsbxcrmdb2 is the old database server name.
I found one location where this is displayed - in transaction SXI_CACHE (in the client of th integration server), Menu option GOTO -> Adapter Engine Cache. The column 'Adapter Engine Name' reflects the incorrect name. Where is this property stored?
I cleared this entry manually by selecting the row and clicking on the trash can icon. Later it was refreshed properly.
-Mike
Update: I found that the SOAP Reciever channel in my Integration Scenario had a hard-coded entry pointing to the old integration server name in the property 'Adapter Engine'. I changed this by selecting the 'Integration Server' in the drop down. This changed the error behavior (still doesn't work, but the above errors went away).
-Mike
Message was edited by: Mike Hatch
Message was edited by: Mike Hatch
Message was edited by: Mike Hatch

Unable to determine name of central adapter engine

We have a central SLD set up. I am now moving some configuration and testing from our dev environment to our qa environment. When I do a cache notification from the Integration Directory I receive a message stating that "Unable to determine the name of the central Adapter Engine from the System Landscape Directory". When I look under the technical system type of Exchange Infrastructure of the system landscape directory I do not see the Adapter Engine of my QA or Production environment. I only see one central adapter engine listed. That of my development environment. It will not let me define another technical system to add these adapter engines because the button New Technical System is grayed out. How do I get these adapter engines defined in the SLD?
Thanks,
Jim

I also had the same problem. But when I opened Integration Directory and Repository from the links, it got added to the Technical system under Exchange Infrastructure. Only Adapter Engine was not getting added.
But after applying the note 764176. Adapter Engine added to SLD and after refreshing cache now Adapter Engine also got added to RWB components.
Only one problem now - in Message monitoring, If I select Adapter Engine from the drop down, I get page cannot be displayed. Is it due to the fact that I dont have any adapters configured?? and also no messages available for that matter?? as it is a fresh box..
Message was edited by: Thilothama v

Cache Notifications unable to determine name of Central Adapter Engine

Hi All,
When I tried Tools -> Cache Notifications in the integration directory, im getting
Unable to determine the name of the central Adapter Engine from the System Landscape Directory at this time.
Notifications to the central Adapter Engine are therefore listed using the technical name of the Adapter Engine.
This is usually structured as follows: af.<SAP System ID>.<Name of application server>
Once i click the OK on the pop up dialog which has this message, it has given the Notifications and Problems Tab.
In the Problems Tab, its has given an error message
'Unable to find an associated SLD element (source element: SAP_XIIntegrationServer"
Any suggestion of what to look for to modify ??
Thanks
Sourav

Hi Kedar,
Check this Blog. it should probabaly solve your problem.
/people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory
Thanks
Sourav

Issue when receiving SOAP message with HTTPS on non-central adapter engine

Hi,
we have a central XI system (PI 7.1 EHP1 SP03) and a non-central adapter engine (XI 3.0) in the DMZ, both systems on HP-UX.
In the affected configuration scenario, a business partner is sending us IDocs (INVOIC.INVOIC01) over HTTPS with Certificate Authentication and without SOAP Envelope.
The configuration and security settings seem to be correct, because we've already received several messages successfully over this connection. Now, since several weeks no message arrives anymore in our system, while the business partner always gets a HTTP_OK_200 response. So the messages seem to be accepted by our system, but nothing is shown, neither in the MessageMonitoring or CommunicationChannelMonitoring of the Runtime Workbench, nor in the in the traces/logs of the NetweaverAdministrator (trace level = DEBUG for "com.sap.aii.adapter.soap").
I also removed the assigned user in the sender agreement which should cause a HTTP_500_error on sender side, but our business partner still got a "OK_200" notification and we didn't find any information in the trace of our system.
When using TCPGateway to trace the communication, I can see an arriving message and the response, but it's encrypted because of HTTPS.
1) Did anyone have similiar issues yet?
2) Are there any further possibilities to check if an incoming message at the SOAP adapter fails?
3) Which further trace settings can be done, to get most detailed informations about the soap traffic?
4) Is there a way to decrypt the message of the TCPGateway (e.g. with private key of server)?
I'm looking forward for any helpful hints or information!
Regards,
Juergen

Issue solved by SAP note 1115650 "J2EE Engine kernel.sda SP20 cumulative patch"

Working with non-central adapter engine

Hi Experts,
I have a non-central adapter engine in my PI installation. I want to use it in my integration. But I am not able to do so. In ID when I create an RFC CC the Adapter Engine combo box is empty.
What should I do?
Can I configure this non-central engine as central engine?
Please guide me. I am on critical path.
Jitendra

Hi
Try this
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/webinars/configuring%20a%20local%20adapter%20engine%20to%20work%20with%20a%20central%20instance%20-%20webinar%20powerpoint.pdf
This will help u

Non-central adapter engine setup with web dispatcher

Our PI setup is working perfectly in our private zone, now the requirement is to expose our PI to public zone to do our B2B transactions. We have proposed a solution but I need your expert suggestion on this. Solution proposed
Public Zone -|Semi public zone| Semi private zone |----Private zone
|>>>Application gateway >>>>>>>>| Non-Central Advanced<==========>|------ PI 7.1
|>>>(For Inbound message) >>>>>>| Engine (For both Inbound and<=====>|------(IS, central AAE, IE)
|<<<<< Proxy<<<<<<<<<<<<<<<<<<|Outbound message and<==========>|
|<<<<<For outbound)<<<<<<<<<<<<|Load balancing for B2B)<=========>|
Non-central AAE will be in semi private DMZ. It will send/receive all B2B messages from/to semi public DMZ via Application gateway for inbound messages and proxy for outbound messages.
Then Non-central AAE will work with the PI central instance running in Private DMZ to receive and send messages.
My Questions:
1) Do we need a SAP web dispatcher to work in between (Application gateway, Proxy) and (Non-central AAE)   ?
    My understanding: SAP web dispatcher balances the load which will enhance the performance but it is not mandatory. Non-central AAE can work independently with Application gateway and Proxy to receive and send messages.
2) What is the configuration we need at non-central AAE to exchange messages with the application gateway and proxy?
Thanks
Amaresh

what is use of non central Adapter engine in Java server proxy?
The collaboration profile agreement service (CPA service) does not read the CPA cache from the Integration Directory.
You define the user that is to send the messages to the Integration Server in a service parameter. When the Integration Server receives the message with this user, it checks the user using the access control list. This check is not performed for the technical user XIAFUSER.
pls refer below link:
http://help.sap.com/saphelp_nw73/helpdata/en/48/d7fb415ba90783e10000000a42189d/frameset.htm

Help!Cache status of object for Central Adapter Engine is incorrect

this problem cconfused me several days!
version:PI 7.1
after i activate the communication channel, the cache not update for central adapter engine
problem: in cache status overview, the update for central adapter engine not yet started, but notification is ok.
the update for integration server and mapping run time are all correct.
then when i display wsdl for sender agreement(SOAP sender), show message:Cache status of object abcd123 for Central Adapter Engine is incorrect
if i ignore this message, error message popup:dapter Engine af.xid.sapittest for communication channel abcd123 not registered in SLD
who can help me solve this problem.
thank you in advance.

Hi cheng,
Kindly check if you have set theparameter 'com.sap.aii.connect.integrationserver.sld.name' in your
Exchange Profile, since it's not set by default. Open note #1278563 and follow the procedures.
And you may check the following notes:
#1031321 - Self-Registration of Adapter Engine and RWB fails
#1334053 - No automatic PI 7.10 SLD Registration (Here you'll see the note 764176 which you have already applied and also the note #1117249).
In RWB, is the adapter Engine "red light"? If yes, what is the specific error?
Regards,
Caio Cagnani

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

Configuration of JMS Adapter in Central Adapter Engine

Hi all,
I have configured Sender JMS Adapter in Central Adapter Engine with the following parameters:
Adapter type : JMS
Transport Protocol : WebSphere MQ (non-jms)
Message Protocol : JMS1.x
Adapter Engine : Integration Server
Queue Connection Factory java class :Com.ibm.mq.jms.MQQueueConnectionFactory
Queue java class : com.ibm.mq.jms.MQQueue
ipadd : localhost
port : 1414
Queue Manager name : TEST.QMGR
Channel Name : CH1
JMS Queue : LQ
CCSID : 437
Protocol : TCP/IP
JMS-compliant : WebSphere MQ(non-jms)
JMS Queue user : MUSR_MQADMIN
Mapping of message : Entire Message = JMS Payload
But the status is red with an error message Sender Details : NULL
Could you please tell me what went wrong?
Regards
Sathya

Hi,
Make sure that Websphere MQ server is running.
If u r comfortable with java, you can even write a Java code to acces the server and check if the JMS server is working fine. Some times there will be sample applications provided by Websphere MQ itself.
Once the java program works then it will be easy to debug the error over here.
Regards,
P.Venkat

Can't reach the Central Adapter Engine (HTTP 403)

Similar Messages

Maybe you are looking for