Adapter Engine issue

Hi,
I am workingon JDBCXIRFC scenario.
After creating Data types, message types, message interfaces and etc, i started defining communciation channel template under "Adapter Objects".
While selecting the particular Adapter type, the window is popping up with message "Objects Not Found".
How to resolve this bug?
Does this means that we need to install Adapter Engine?
If its already installed, how to check the available adapters in XI server?
Regards
Pavan

Hi Pavan,
i guess u have some post-installation problem.Can u check in ID wheather all adapters are installed there??in any communication channel when u gonnna select a adapter ...r u getting the same error???
Go and import the SAP BASIS 6.4 or 7.0 Software COmponent Version into Integration Repository.
For this tpz file you can get from -
Copy XI3_0_SAP_BASIS_6.40_09_00.tpz from <Components DVD>/XI /XI_CONTENT to directory /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import/
better u check this thread
Adapters Metadata Problem
Regards
BILL

Similar Messages

Adapter Engine Issue in RWB

Hi,
I am getting a error in the RWB:
Self-Test Status: HTTP request failed. Error code: "500". Error message: "Internal Server Error [http://host:port/AdapterFramework/rtc]"
I have a mail channel setup that is running on this Adapter Engine. I am able to monitor the channel on this Adapter Engine and the channel is collecting mails from the POP3 mailbox and delivering the message to the Integration server. However I am getting the error above.
Please can you assist to get this matter resolved.
Many Thanks
Regards
Willie Hugo

Hi,
This problem is still persisting. I have however not mentioned that we are running PI 7.10 and therefore there is no Visual Administrator only NWA. This was a new install. I have changed all the Host Names to use fully qualified domain names. This is the exchange profile and sxmb_adm, RZ70, sldapicust and in the RFC's user on the ABAP side. Also I have checked out the destinations on NWA and changed the Host Names the to fully qualified domain namesand also the SLD Data Supplier Configuration. I also changed the FQ D names on the JCO RFC Destinations. All well so far.
I however still has the same error on the Adapter Engine in the RWB. What I have notice though is where the error is displayed in the RWB then the Host Name is not FQ. Where can I correct this?
Also I have noticed when going into SXI_Cache > Goto > Adapter Engine Cache then there is no cache for the Adapter Engine.
I have changed the host name of the integration server on the SLD to FQ D names as well.
I think that I need to delete all the entries for this tech+business system and all the assosiations to it from the SLD and then re-register the whole PI to the SLD again, but is not sure how to do that again.
Please can any one assist.
Regards
Willie

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"

Adapter Engine Cache Issue

Hello All,
In SXMB_MONI i got an error saying
SAP:AdditionalText>Error while writing to secure store: ERROR_UNKNOWN: Error when updating buffer for Adapter Engine</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine</SAP:Stack>
My Analysis :
1, In SXI_CACHE i could see 'Unable to refresh cache contents' and 'Error during last attempt to refresh cache' also I could not see any entry in Adapter Engine Connection Data Cache.
2, when execute the RFC connection 'INTEGRATION_DIRECTORY_HMI' Its asking for userId and password .
3, I tried reset the password and do a JAVA restart again with same error.
Clarificaiton need :
1 Looks some authorization error , but where exactly to maintain this ,
2, How the adatper engince connection data will populate in to sxi_cache transaction.
could you guide me clearly for this issue.
Regards.
Sethu.

Thanks venkat,
now that Adaper engine url gotregistered , but no my cache content is not updating correctly , i.e when i execute the any cache refresh its loading for a long time and ending up an error and when i tried in Administator tool--> cache overivew > ID> and did cache refresh its end up with error.
Method fault! Message : IBaseException:Connection to system DIRECTORY using application DIRECTORY lost. Detailed information: Error accessing "http://c1bfxr41.unix.marksandspencercate.com:8136/dir/hmi_cache_refresh_service/int?container=any" with user "PIISUSER". Response code is 401, response message is "Unauthorized" com.sap.aii.ib.server.abapcache.CacheRefreshException: Connection to system DIRECTORY using application DIRECTORY lost. Detailed information: Error accessing "http://c1bfxr41.unix.marksandspencercate.com:8136/dir/hmi_cache_refresh_service/int?container=any" with user "PIISUSER". Response code is 401, response message is "Unauthorized" at com.sap.aii.ibrun.server.valueMapping.cache.RefreshClient.refresh_VMCache(RefreshClient.java:60) at com.sap.aii.ibrun.server.valueMapping.cache.HmiMethod_Invalidate.refresh(HmiMethod_Invalidate.java:79) at com.sap.aii.ibrun.server.valueMapping.cache.HmiMethod_Invalidate.process(HmiMethod_Invalidate.java:40) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169) at
But in sm59 INTEGRATION_DIRECTORY_HMI - i used pisuper user id also in SLDAPICUST i used pisuper only, i dont know where the piisuser is getting conflict. any idea please?

Issue in adapter engine

Hello,
I am facing below issue in sap PI SYSTEM
The messages for I020 passed successfully from Integration engine but are in error state in Adapter engine (even after resending the messages), with the JMS Error Code:JMSWMQ1107
And also
1) We are not able to refresh theCPA Cache
2) Also, the state of the message (Inactivating/ activating) is not getting reflected in the Adapter engine.
Please any one suggest how to shotout the issue.
Tks,
Raju

Hi,
I have refreshed cpa cache and restarted xi adapter but still we are facing same issue
Tks,
Raju

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

Error in gettnig logon data for Adapter Engine

Hi,
We have Http > XI > RFC Scenario. We are getting 401 unauthorized error in "CALL ADAPTER" section. From the trace its clear that the logon data for the adapter engine (there is no value for USER in trace) is not getting poulated. We fixed this issue last evening....i think by doing full cache refresh, but this problem propped up again today. Yesterday when this issue was fixed the USER has "PIISUSER" in the trace.
We haven't changed any config settings since yesterday so all the passwords and other config info is same. Not sure what's causing this issue. Below is the trace. Any help will be highly appreciated.
- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
<Trace level="3" type="T">Channel for adapter engine: RFC</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
<Trace level="2" type="T">return fresh values from cache</Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET): af.ppi.dac-sapd1</Trace>
<Trace level="3" type="T">URL = http://dac-sapd1.actv2.com:8007/MessagingSystem/receive/AFW/XI</Trace>
<Trace level="3" type="T">User =</Trace>
<Trace level="3" type="T">Cached = X</Trace>
<Trace level="3" type="T">Creating HTTP-client</Trace>
<Trace level="3" type="T">HTTP-client: creation finished</Trace>
<Trace level="3" type="T">Security: Basic authentication</Trace>
<Trace level="3" type="T">Serializing message object...</Trace>
<Trace level="3" type="System_Error">HTTP-client: error response= <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>Error Report</title> <style> td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active </style> </head> <body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0"> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"> 401 &nbsp Unauthorized</td> </tr> <tr bgcolor="#3F73A3"> <td height="23" width="84"><img width=1 height=1 border=0 alt=""></td> <td height="23"><img width=1 height=1 border=0 alt=""></td> <td align="right" height="23">SAP J2EE Engine/7.00 </td> </tr> <tr bgcolor="#9DCDFD"> <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td> </tr> </table> <table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75"> <tr bgcolor="#FFFFFF"> <td align="left" colspan="2" height="48"> Authentication did not succeed.</td> </tr> <tr bgcolor="#FFFFFF"> <td align="left" valign="top" height="48"> Details:</td> <td align="left" valign="top" height="48"><pre> No details available</pre></td> </tr> </body> </html></Trace>
<Trace level="3" type="T">HTTP-client: closing...</Trace>
<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
<Trace level="3" type="T">HTTP-client: request sent</Trace>
<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
<Trace level="3" type="T">HTTP-client: response received</Trace>
<Trace level="3" type="T">HTTP-client: checking status code...</Trace>
<Trace level="3" type="T">HTTP-client: status code = 401</Trace>

Hi,
go to the exchange profile.
there u need to maintain the password for the XIISUSER.
I think u need to restart the J2EE Engine for the changes to take effect.
Regards
Cornelius

J2ee Adapter engine installation error

Hi All,
I am installing XI with NW07. I had an ERP2005 server here with ABAP only. I installed Java Add In to it with usage type PI.
Now I tried to install J2ee adapter engine. It showed if i want to run a new installation or continue the old one.
I tried to install installation of J2ee adapter engine from a new directory.
It is stuck in between. I choose it as a MCOD to existing DB.
I can see a new instance for this in MMC and it is up and running.
But the old java instance is not running. None of the Proceses of Old Java instance (dispatcher, server0 and SDM) are not running. Did I do something wrong?
My JVM_BOOTSTRAP.OUT says this:-
Exception occurred:
com.sap.engine.frame.core.configuration.NameNotFoundException: A configuration with the path "cluster_data/dispatcher/ID4065200" does not exist.
at com.sap.engine.core.configuration.impl.ConfigurationDataCacheAllImpl.getSubConfiguration(ConfigurationDataCacheAllImpl.java:107)
at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getSubConfiguration(ReadAccessConfiguration.java:715)
at com.sap.engine.bootstrap.Synchronizer.getConfiguration(Synchronizer.java:426)
at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:72)
at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:420)
at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
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.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Exception occurred:
com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
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.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
== Caused by: ==----
com.sap.engine.bootstrap.SynchronizationException: No such Dialog Instance (ID4065200) in the database! Check database consistency or local Bootstrap properties!
at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:75)
at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:420)
at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
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.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Bootstrap module> Problem occurred while performing synchronization.
My dev_jcontrol.b00 shows:-
JControlStartJLaunch: program = C:\usr\sap\IDE\DVEBMGS00\exe\jlaunch.exe
-> arg00 = C:\usr\sap\IDE\DVEBMGS00\exe\jlaunch.exe
-> arg01 = pf=C:\usr\sap\IDE\SYS\profile\IDE_DVEBMGS00_sapides
-> arg02 = -DSAPINFO=IDE_00_bootstrap
-> arg03 = -nodeId=-1
-> arg04 = -file=C:\usr\sap\IDE\DVEBMGS00\j2ee\cluster\instance.properties
-> arg05 = -syncSem=JSTARTUP_WAIT_ON_5284
-> arg06 = -nodeName=bootstrap
-> arg07 = -jvmOutFile=C:\usr\sap\IDE\DVEBMGS00\work\jvm_bootstrap.out
-> arg08 = -stdOutFile=C:\usr\sap\IDE\DVEBMGS00\work\std_bootstrap.out
-> arg09 = -locOutFile=C:\usr\sap\IDE\DVEBMGS00\work\dev_bootstrap
-> arg10 = -mode=BOOTSTRAP
-> arg11 = pf=C:\usr\sap\IDE\SYS\profile\IDE_DVEBMGS00_sapides
-> arg12 = -DSAPSTART=1
-> arg13 = -DCONNECT_PORT=4740
-> arg14 = -DSAPSYSTEM=00
-> arg15 = -DSAPSYSTEMNAME=IDE
-> arg16 = -DSAPMYNAME=sapides_IDE_00
-> arg17 = -DSAPPROFILE=C:\usr\sap\IDE\SYS\profile\IDE_DVEBMGS00_sapides
-> arg18 = -DFRFC_FALLBACK=ON
-> arg19 = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\oracle\IDE\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_06\bin;C:\j2sdk1.4.2_06\lib;C:\usr\sap\IDE\SYS\exe\uc\NTI386
-> exe path = PATH=C:\j2sdk1.4.2_09\bin;C:\usr\sap\IDE\DVEBMGS00\j2ee\os_libs;F:\oracle\IDE\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_06\bin;C:\j2sdk1.4.2_06\lib;C:\usr\sap\IDE\SYS\exe\uc\NTI386
Thr 4232 Tue Sep 16 17:48:04 2008
Thr 4232 *** ERROR => invalid return code of process bootstrap (exitcode = 66) http://jstartxx.c 1642
Thr 4232 JControlExecuteBootstrap: error executing bootstrap node bootstrap (rc = 66)
Thr 4232 JControlCloseProgram: started (exitcode = 66)
Thr 4232 JControlCloseProgram: good bye... (exitcode = 66)
My DEV_BOOTSTRAP.B00 shows:-
Thr 5984 Tue Sep 16 17:48:02 2008
Thr 5984 JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
Thr 5608 Tue Sep 16 17:48:04 2008
Thr 5608 JLaunchIExitJava: exit hook is called (rc = 66)
Thr 5608 **********************************************************************
u2022
o
 ERROR => The Java VM terminated with a non-zero exit code.
 Please see SAP Note 943602 , section 'J2EE Engine exit codes'
 for additional information and trouble shooting.
Thr 5608 JLaunchCloseProgram: good bye (exitcode = 66)
I ran the prerequisite checks before starting the installation.
It shows everything ok except it told me to have a environmental variable as CPIC_MAX_CONV with the value 200 at least. And I did that.
All the other checks were ok.
All are on SAME OS and same machine.
I have J2EE Adapter Engine installation guide, but there is nothing for this in that
In Instance properties file for the old instance it is showing the instance ID which it is not able to find.
In the configtool of both the instances, the instance ID is same under cluster_data and this is of the newer instance
How did the instance ID and data got replaced in the configtool of old instance. I mean the new instance has its new directory or folder.
What Could be the problem?
Did I do anything wrong here?
Kindly help

Hi,
Check out the SNote 997510, " Note 997510 - Troubleshooting
J2EE Engine 6.40/7.0 Bootstrap Issues ".
I hope it will help you to drill more in to the problem
Rgds
Radhakrishna D S

Receiver File Adapter - Adapter Engine

I am able to read files using Sender File Adapter. But when I try to write a file using Receiver File Adapter I get the following erro:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="<http://sap.com/xi/XI/Message/30>" xmlns:SOAP="
<http://schemas.xmlsoap.org/soap/envelope/>" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.exi.usxid</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>3: No service user name found for Integration
Server is.00.usxid</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password)
for the Adapter Engine af.exi.uswalexi</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I tried executing the function module SAI_AE_DETAILS_GET but I am not getting the error URL Not found. This was working in the past. We upgraded to SP15 this showed up again.
Any help appreciated.

I'm working on integration of SAP with 3rd party application. While sending data from SAP to XI, i'm getting the following error which i've found in sxmb_moni (XML Message->Call Adapter).
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- -
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
<SAP:P1>af.xp1.sapxi</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>3: No service user name found for Integration Server is.00.sapxi</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error when reading the access data (URL, user, password) for the Adapter Engine af.xp1.sapxi</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Plz help me to solve this issue. If possible mail me the solution to my personal email-id [email protected]
Note:
1. We are using CIM 1.3
2. In XI Server Message Monitoring, i'm getting the System Error message in Integration Engine.
3. In Payloads, i'm getting the required information in XML format as desired.
Thanks in advance.
Regards,
Navaneeth.S

Adapter engine field blank in File Comm channel (Sender)

Hi,
I am not getting any value in drop-down list of adapter engine in file adapter communication channel.System is allowing me to save the comm channel but when I am trying to create sender agreement, system is giving me following error
Unable to find an associated SLD element (source element: SAP_XIIntegrationDirectory, [CreationClassName, SAP_XIIntegrationDirectory, string, Name, directory.s01., string], target element type: SAP_XIIntegrationServer)
I m getting values of adapter engine when I select some other adpter like IDOC or RFC.
Please help...

Hi,
1) Can you check your Post Installation.
2) Look for SAP NOTES.
3) Try cache refresh
a)Start transaction SXI_CACHE.
b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.
If you still face issue try this .
Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.
However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.
To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.
Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.
Regards
Agasthuri Doss

PI 7.1 adapter module issue

I deoplyed my module and worked fine. now i changed some code by adding parameter to module
strModuleKey = moduleContext.getContextData("module.key");
I changed the related things in my communication channel(gave parameters)
Now, i get below error while executing...
java.lang.ClassCastException: class com.sap.aii.af.sdk.xi.mo.MessageContext:library:com.sap.aii.af.sdk.libcom.sap.engine.boot.loader.ResourceMultiParentClassLoader428c6e04alive incompatible with interface com.sap.engine.interfaces.messaging.api.Message:interface:com.sap.aii.af.ms.ifccom.sap.engine.boot.loader.ResourceMultiParentClassLoader2dd7e4d6alive
Followed the below url but in vain..
PI JAVA ADAPTER MODULE PROBLEM
Incompatible with interface - Exception in Adapter Module
Issue on developing Adapter Module
Also if you are using PI 7.1 refer to the blog:
/people/stefan.grube/blog/2008/12/11/adjust-your-pi-70-adapter-modules-for-pi-71-in-15-minutes
Please let me know if u have any other suggestions other than this...
Thanks
Prabhakar

Hi Venkat,
Yes, you cannot add custom modules to soap adapter.
Please refer below documentation for the same..!!
http://help.sap.com/saphelp_nwpi71/helpdata/EN/44/8c4756224a6fb5e10000000a155369/content.htm
http://help.sap.com/saphelp_nwpi71/helpdata/EN/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
Regards,
Swetha.

"Performance" problems with the File adapter on Plain J2SE Adapter Engine

Hi,
At the moment I'm on a customer side to solve some XI issues for a few days. One of the issues is the performance of the Plain J2SE Adapter Engine, using the file adapter to transfer XML messages(already XI message format) from the legacy system to the Integration Engine. The File adapter has to deal with "large" XML messages(max at the moment is 65 Mb) and the engine fails with the following error when transferring the big XML file: "ERROR: Finished sending to Integration Engine with error "java.lang.OutOfMemoryError". Skip confirmation and quit this loop".
As far I got the information from the customer the memory use of the Plain adapter engine is set to 512Mb. This is maybe to low. But I don't know where to look for this, I only have the adapter web interface in front of me, no access to the OS it self via for example remote connection.
On the Integration Engine I know there is the ability to split large message with the file adapter(File Content Conversion), but I don't know this for the Plain Adapter Engine. Is there a possibility to do this also on the Plain Adapter Engine?
Thanks in advance for any input.
Greetings,
Patrick

Hi Sameer,
Thanks for your answers.
On the first solution, yes that is possible, we first decided to see if the legacy system can do the splitting, before starting developing a Java program.
On the second solution, as far as I know is this solution possible on the Integration Engine. But we are facing the problems on the Plain J2SE Adapter Engine. I went trough that documentation(link:
http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm ), to look for I similiar solution in the Plain Adapter Engine. So my question is, is this possible with the Plain Adapter? And if so, what kind of parameters I need to use to achieve this.
Regards,
Patrick

Installation and then Configuration of Plain J2se Adapter Engine

Hi All,
Actually we want to use JMS Adapter for that we had installed Plain J2SE Adapter Engine but after installing and following the initial steps of Adapter.pdf we are not able to access the Adapter Engine through URL.We are using the URL http://<hostname>:8200/MessagingSystem/receive/AFW/XI
this URL is there in our SLD but we are not able to access the page.
So Please can somebody help me to resolve this issue.
Thanks & Regards
Sathya

Hi Amol,
I am trying to send read data from MQSeries using JMS adapter. We are successful in opening the Adapter Engine and the GUI. We have cofigured the adpter as follows. But when we try to restart the adapter to get the changes get saved we are getting the following error
"ERROR CALLING THE RESTART ADAPTER"
Also status is shown is yellow and version is shown as not set.
Where ever I have changed the configuration data I have shown it in bold
JMS-Adapter Configurarion
This Configuration is a sample for a JMS sender channel (inbound, sends to XI IS)
Set XI message protocol version. This sample is designed for XI 3.0
version=30
JMS message receiver class
classname=com.sap.aii.messaging.adapter.ModuleJMS2Transport
set if a transacted JMS Session should be used (default: true)
#JMSSession.sessionTransacted=false
set delay in milliseconds before processing next message after an error (default: 0)
errorDelay=10000
#set delay in milliseconds before trying to reestablish the JMS Connection after a connection error (default: -1 (do not try to reconnect))
#reconnectDelay=10000
set the Message Formats you want to process (Formats only needed if they can not be evaluated at runtime)
TransportMessage Type can be set to TransportMessage of XMBMessage. It is used for sending and receiving Transport and XMBMessages
#TransportMessage.type=TransportMessage
TransportMessage.type=XMBMessage
uncomment and adjust parameters for Transformation Type (Binding of JMS-Transport Message),
insert your class here for an individual binding between JMS and Transport Message
uncomment the following line for using Bindings that belong to Tunneling
#transformClass=com.sap.aii.messaging.adapter.trans.JMSTunneling
uncomment the following line for using Bindings that belong to Single Payload Binding
transformClass=com.sap.aii.messaging.adapter.trans.JMSSinglePayloadBinding
ID Garbage Collector: For EO(IO) handling XI adapters store the JMS/XI message ID's in the ID logger
Uncomment the following lines and change the default values if you recognized "out of memory" problems due to
very large ..\tech_adapter\Data\*_ID.dat files which will be kept in the memory as well
eoExpirationAfterDays is the period of keeping the message ID in days. Afterwards the message ID might be used again
garbageCollectorInterval is the period in milliseconds when the ID garbage collector is started. It will however only
be started if messages are exchanged otherwise ID logs won't be created anyway
eoExpirationAfterDays=365
garbageCollectorInterval=86400000
#
the following parameters are used in some Bindings that belong to Single Payload Binding needing XMBHeader Information
uncomment and adjust parameters according your requirements. Please note, that the party identfier needs not to be
configured in case of A2A scenarios.
#XI.SenderParty=Sender
XI.SenderService=MQSeries
#XI.ReceiverParty=Receiver
XI.ReceiverService=MTX
XI.InterfaceNamespace=http://xitest
XI.Interface=MI_Out_File
XI.TraceLevel=1
XI.LoggingLevel=1
XI.QualityOfService=EO
XI.QueueId=ABCD
XI.ContentType=text/xml
# *************************************************************************************************************
#
URL of XI IS to send the messages to
XI.TargetURL=http://bwxi:50000/sap/xi/engine?type=entry
XI.User=XIAF
XI.Password=XIPASS
# *************************************************************************************************************
URL of file adapter if a loopback JMS to File should be configured
XI.TargetURL=//localhost:8210/file/receiver
# uncomment the following settings if needed (independent on JMS provider)
JMS.QueueConnectionFactoryImpl.user=xisuper
JMS.QueueConnectionFactoryImpl.password=xxx
#
uncomment and adjust parameters for loading JMS administrated objects via JNDI
uncomment and adjust parameters if not the default context should be used
#JNDI.InitialContext.property.1=java.lang.String {javax.naming.Context.INITIAL_CONTEXT_FACTORY}, java.lang.String com.sap.engine.services.jndi.InitialContextFactoryImpl
#JNDI.InitialContext.property.2=java.lang.String {javax.naming.Context.PROVIDER_URL}, java.lang.String localhost:50004
#JNDI.InitialContext.property.3=java.lang.String {javax.naming.Context.SECURITY_PRINCIPAL}, java.lang.String Administrator
#JNDI.InitialContext.property.4=java.lang.String {javax.naming.Context.SECURITY_CREDENTIALS}, java.lang.String sap
set the Lookup Names
#JMS.JNDILookupNameQueueConnectionFactory=jmsfactory/default/joetest
#JMS.JNDILookupNameQueue=jmsQueues/default/sapDemoQueue
uncomment and adjust parameters for loading JMS administrated objects from filesystem ***
#JMS.FileNameQueueConnectionFactory=SAPQueueConnectionFactory.ser
#JMS.FileNameQueue=SAPQueue.ser
uncomment and adjust parameters for creating SonicMQ JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=progress.message.jclient.QueueConnectionFactory
JMS.QueueConnectionFactoryImpl.constructor=java.lang.String localhost:2506
JMS.QueueImpl.classname= progress.message.jclient.Queue
JMS.QueueImpl.constructor=java.lang.String SampleQ1
# uncomment and adjust parameters for creating MQSeries JMS administrated objects ***
JMS.QueueConnectionFactoryImpl.classname=com.ibm.mq.jms.MQQueueConnectionFactory
JMS.QueueConnectionFactoryImpl.method.setHostName=java.lang.String BWXI
JMS.QueueConnectionFactoryImpl.method.setChannel=java.lang.String JAVA.CHANNEL
JMS.QueueConnectionFactoryImpl.method.setTransportType=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP}
JMS.QueueConnectionFactoryImpl.method.setQueueManager=java.lang.String QM_BWXI
JMS.QueueImpl.classname= com.ibm.mq.jms.MQQueue
JMS.QueueImpl.constructor=java.lang.String postcard
JMS.QueueImpl.method.setTargetClient=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_CLIENT_NONJMS_MQ}
# *************************************************************************************************************
uncomment and adjust parameters for using a dispatcher ***
#Dispatcher.class=com.sap.aii.messaging.adapter.ConversionDispatcher
#Dispatcher.namespace=namespace1
#namespace1.ConversionDispatcher.logPayload=true
#namespace1.Service.1=Plain2XMLService
#namespace1.Plain2XMLService.class=com.sap.aii.messaging.adapter.Conversion
#namespace1.Plain2XMLService.xml.conversionType=SimplePlain2XML
#namespace1.Plain2XMLService.xml.processFieldNames=fromConfiguration
#namespace1.Plain2XMLService.xml.fieldNames=a,b,c
#namespace1.Plain2XMLService.xml.fieldSeparator=;
#namespace1.Service.2=XSLTService
#namespace1.XSLTService.class=com.sap.aii.messaging.adapter.XSLTConversion
#namespace1.XSLTService.XSLTConversion.XSLTFileName=Data/DemoConversion.xsl
Can you please help me in resolving the error.
Regards,

J2RE + Windows + J2SE Adapter Engine = Dump Xmx128m

Hi,
I want to use a decentralized J2SE Adapter Engine in order to data to XI.
When I install it on a Windows 2000 Professional, AE running is good and all are perfect... But when I install it on a Windows Server 2003, I have the following dump when I use the file "run_adapter.bat":
"-Xmx128m: illegal argument"
Here is the instruction when my tool uses for its running :
java -Xmx128m -classpath aii_msg_adapter.jar;aii_msg_runtime.jar;httpclient.jar;aii_af_trace.jar;aii_rfcadapter.jar;pmi.jar;exception.jar;jperflib.jar;guidgenerator.jar;aii_utilxi_misc.jar;aii_util_cimaccess.jar;sapxmltoolkit.jar;logging.jar;lcrclient.jar;tc_sec_core.jar;tc_sec_api.jar;jms.jar;servlet.jar;jarm.jar;%CLASSPATH%; com.sap.aii.messaging.adapter.AdapterImpl
Notes:
1. J2RE is j2re-1_4_2_06-windows-i586-p.exe)
2. I have replace 128 by 256 or 512, but it's the same issue.
So,
1. Anybody could explain why I have that with Windows Server 2003 ?
2. is it a problem with a Java Virtual Machine ?
3. Must I do something inside Windows : Environment variable, register key or other ?
Any helps are welcome.
Mickael

No. (neither PATH or JAVA_HOME, or J2EE_HOME)
What folder must I precise in this variable :
C:\Program Files\Java\j2re1.4.2_06\javaws ?
or
C:\Program Files\Java\j2re1.4.2_06\bin ?
Regards.
Mickael

J2SE Adapter Engine Error

Hi everyone,
I am facing couple of issues with J2SE adapter engine.
1. First Issue
Config in SLDaccessor -
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleSLDaccessor
SLD.host=<HOST>
SLD.port=50xxx
SLD.user=user
SLD.password=pass
SLD.adapterEngineName=AdapterEngine
Config in Sender File Channel
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
version=30
mode=FILE2XMBWITHROWCONVERSION
XI.SLDConfiguration=SLDaccessor
#XI.TargetURL=http://<HOST>:<50xxx>/sap/xi/engine/?type=entry
XI.TargetURL=<fromSLD>
XI.QualityOfService=EO
XI.Client=001
<Other parameters like InterfaceName / FCC>
If I use XI.SLDConfiguration=SLDaccessor and XI.TargetURL=<fromSLD>, I get an error of HTTP 401 unauthorized.
If I ignore the SLDaccessor, the message is processed successfully.
Am I missing anything in the above configuration?
The user id user is having the roles of SAP_SLD_CONFIGURATOR and SAP_XI_APPL_SERV_USER.
2. Second Issue
In RWB -> Component Monitoring -> J2SE Adapter Engine, there is an error coming up - Unable to establish connection to "https://<LocalHost>:50001/rtc"
The port is wrong ... it should be 8200. My question is, from where to fix this?
Any help will be highly appreciated.
Thanks,
Neetesh

Hi Neetesh,
After copying tech_adapter on your local machine douple click on run_adapter.bat and then open internet explorer and enter http://l<ocalmachine_ip_address>:8200/adapter.html
After doing this you will get logon popup, enter user & password and configure the adapters.
Secondly you can see the port in SLDAPICUST if I am not mistaken. (not very sure)
Compare your configuration with below one
file adapter java class
classname=com.sap.aii.messaging.adapter.ModuleFile2XMB
version=30
mode=FILE2XMB
Integration Engine address and document settings (example, see docu)
XI.TargetURL=http://<host>:8000/sap/xi/engine?type=entry
XI.User=testuser
XI.Password=pass123
XI.QualityOfService=EO
#XI.SenderParty=
XI.SenderService=LocalSystem
#XI.ReceiverParty=
XI.ReceiverService=LocalSystem
XI.Interface=IM_J2SE
XI.InterfaceNamespace=http://abc.com/j2se/test
##File Adapter specific parameters (example, see docu)
file.type=BIN
#file.type=TXT
file.encoding=UTF-8
file.sourceDir=c:/sender
file.sourceFilename=sender1.xml
#file.processingMode=test
file.processingMode=delete
#file.processingMode=archiveWithTimeStamp
#file.archiveDir=./temp_archive
#file.retryInterval=20
file.pollInterval=30
Regards,
Sarvesh

Adapter Engine issue

Similar Messages

Maybe you are looking for