SR1 De-Centralized Adapter Engine Install

Folks, I have installed Netweaver Developer Workplace SR1 sucessfully on a local machine XP Professional. When I attempt to install the De-Centralized Adapter Engine (also SR1) on the same machine it seems to corrupt the local AS Java server and it can no longer start correctly. I have tried this on two seperate machines with the same result. Has anyone completed this sucessfully? The Adapter Engine install guide is pretty thin and assumes that sapinst will complete with no errors.
Also the Adapter Engine does not seem to like XP, and wants to be installed on a Win Server2003, is this necessary?
I am beginning to wonder if the AS Java server that comes with Netweaver Developer Workplace is not a full install rendering the Adapter Engine install incompatible. Thoughts?

There really aren't any special requirements for NWDS7.0, other than WinXP and 2gb of RAM. They specify the most recent JDK, but other than that it is the same as the last version. Only it is a much larger memory hog over the last version. You definetly need 2gb of RAM.
Looking at the Adapter Engine install guide again, I don't believe that it is meant to be installed on a local pc for unit testing. If this is true it really stinks because you will not be able to test your Java proxies until the first Server in your landscape.

Similar Messages

Seeing old deleted comm. channels on Non-Central Adapter Engines

hello,
We have a landscape of PI 7.0 machine connected with 3 Non-Central Adapter Engines installed on another machine, which generally works fine.
Somehow, after doing a lot of changes in the integration directory (creating and deleting object: scenario, comm. channels and ect...) - two of the non-central AE shows comm. channels which were already deleted (and activated ofcourse) in the integration directory.
What i tried already:
run CPACache in mode=full on each of those AE, clear SLD cache and even restarted those J2EE instances. but it didn't work out. the thing that is also weird is that I can start/stop those old comm. channels. how do we get rid of those old channels?
I would appreciate any suggestions .

Problem is solved.
In integration directory we could not see the old comm. channels under the objects tab or under any scenario, but they existed as shown in RWB.
From CPA cache we picked up the comm. channels object IDs and search for it in integration directory UI, once they were found - it was easy to actually delete them.
What went wrong?
These old comm. channels were assigned under deleted services which were under deleted parties. For some unknown reason, after deleting the services and parties successfully, the comm. channels underneath were not deleted and could not shown in any of objects tab GUI tree's nodes.
We could not reproduce this behaviour.

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

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...

PI: Non-Central to Central Adapter Engine

Hi all.
I've a question for you: I've a new Non-Central Adapter Engine and I need to change it in a Central Adapter Engine.
I hope that I didn't reinstall the PI Istance...
Could you help me?
Thanks you, PI Gurus...
Bye
Manuel

The systemist had installed the WAS again

"Non-Central Adapter Engines" in RWB

Hi.
We install XI system and we changed host name according to notes 757692.
After then, We found one problem in RWB.
When we run Component Monitor in RWB, Adapter engine is in "Non-Central Adapter Engines".
Why Adapter engine is in "Non-Central Adapter Engines" node ?
Any ideas ?
Regards, Arnold.

Hello Sonali
This is most likely caused by errors registering the XI components in the SLD. Apply the notes below:
#764176 Error in XI due to inconsistent SLD contents
#1117249 Incomplete Registration of PI components in SLD
#1334053 No automatic PI 7.10 SLD Registration
Also search the forum for similar issues registering the adapter engine in the SLD components.
Regards
Mark

Unable to contact non-central adapter engine

Hi All
I install the local J2EE Adapter Engine, and configure the connection in exchange profile and set the SLD Data Supplier in Visual Admin
and i could see my local adapter engine in adapter configuration.
But in Runtime work bench ->component monitor->non-central adapter engine-> error:
Ping Status: status_image HTTP request failed. Error code: "401". Error message: "Unauthorized [http://host:port/AdapterFramework/rtc]"
how could i solve this?
thanks in advance

Hi , Lawrence
There was a solution to this problem?
Thanks
Leôncio

Sand box Non-central adapter engine entry is shown under development rwb

Hi All,
Recently we had a sand box which is a sytem copy of our development server, and everything works fine now.
I have observed a strange issue here is, in the developement rwb under the Non-Central Adapter engines I see a entry as "Adapter Engine T49 (sand box host name)" the SID seen here is a sand box SID, and till today we never installed any non-central adapter engine either on dev or sand box, I am suprised to see this entry, can some one
please help me to understand why is this sand box entry is shown under development rwb and where can I set this or where how can I delete this entry.
Surprisingly I do not see the same non central adapter engine entry on sand box rwb.
All the servers are XI 3.0 (SP 19).
Thanking you in advance..
Regards
Sonali
Edited by: Sonali R on Sep 14, 2009 10:59 AM

Hi Sonali,
The adapter and integration server engines gets registered with the data in SLD. Please check SLD associations for all XI classes.
Best Regards
Raghu

Problems with Non central Adapter Engine

Hi Friends,
We installed an non central Adapter engine. Then as per the documents we made entry for connection in exchange profile.Then in visual administrator in SLD data supplier i provided the required credentials for connecting to my XI server.
XILDUSER and XISUPER these users and passwords were provided for connection.
From visual admin we manually send the trigger to hit the SLD and make an entry there.It was successful in visual admin.
But after doing all this successfully we are not able to see the Local i.e non-central adapter in our XI SLD as well as in RWB.
can anyone throw some light on it.
Thanks,
yomesh

Hi Friends ,
I have solved this problem. The password provided for XILDUSER was wrong thats why it was not able to register in the SLD .also the differents user has to be created in Security provider service in visual administrator.
then it worked finr.
Yomesh

Non-central adapter engine entry is shown under development rwb

Hi All,
Recently we had a sand box which is a sytem copy of our development server, and everything works fine now.
I have observed a strange issue here is, in the developement rwb under the Non-Central Adapter engines I see a entry as "Adapter Engine T49 (sand box host name)" the SID seen here is a sand box SID, and till today we never installed any non-central adapter engine either on dev or sand box, I am suprised to see this entry, can some one
please help me to understand why is this sand box entry is shown under development rwb and where can I set this or where how can I delete this entry.
Thanking you in advance..
Regards
Sonali

Hello Sonali
This is most likely caused by errors registering the XI components in the SLD. Apply the notes below:
#764176 Error in XI due to inconsistent SLD contents
#1117249 Incomplete Registration of PI components in SLD
#1334053 No automatic PI 7.10 SLD Registration
Also search the forum for similar issues registering the adapter engine in the SLD components.
Regards
Mark

Non central adapter engine & adapter monitoring

Hi ,
we installed PI7.0 sp12,and can we see all the available adapter as a list in RWB and adapter monitoring if adapter engine installed as non central?
And we will see Adapter engine under Integration server if AE is centran and under non-central adapter engine if AE is non central ,right?
thank you,
Babu

I could see both Communication Channel monitoring as well as Adapter monitoring.
but once I click adapter monitoring I could see only JPR but not any other adapters.if I click CC monitoring there are no CC cos we havent created any yet.
I am asking like,if we see only JPR in adapter monitoring not any other adapter ,is that a error while doing the installation and configurations? or is that ok?
thank you for your reply.
Babu

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.

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

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

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

SR1 De-Centralized Adapter Engine Install

Similar Messages

Maybe you are looking for