Adapter Engine is disable in integratin builder design

Hi all
I am facing a pboblum in xi 70 when i enter T Code sxmb_ifr and then click integratoin builder design (Integration Repository) then adapter objects and communication chanal and create new and define name and save At here Adapter Type is dissable How I can Enable Adapter Type sender and reciver.
Thanks
Kumar

Hi All,
My prob is like this blog my adapter type sender and receiver buten is dissable I have Check my softwere that is this i am not found sap basis swcv
in the Software Catalog --->Software Components
SAP BASIS SAP BASIS 6.20 sap.com
SAP BASIS SAP BASIS 6.40 sap.com
SAP BASIS SAP BASIS 7.00 sap.com
SAP BASIS SAP BASIS 7.10 sap.com
Please Help me to solve this Prob
Thanks
Kumar

Similar Messages

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

Using Advanced Adapter Engine in PI 7.1 to design a ABAP proxy scenario

Hi
We are currently on XI 3.0 and have a scenario in production that is as follows
R3 --> EOIO (QOS ) --> XI ---> SQL DB A, SQL DB B, SQL DB C ( split in XI , message from R3 in EOIO sequence routed to three different sql servers ). We use this scenario to push master data change messages from R3 . Whenever we do a full push of masterial/customer master from R3, it takes a lot of time for XI to process the messages, the messages hopping from Integration server and then to J2EE server.
We are moving to PI 7.1 and want to use the AAE ( advanced adapter engine ) to avoid the integration server in the above scenario and thus cut out an additional hop and send the message from R3 directly to the AAE on PI 7.1 server
i.e R3 --> EOIO (QOS ) --> PI J2EE server(AAE ) -->SQL DB A, SQL DB B, SQL DB C .
I read in new PI 7.1 features that AAE has all features available in Integration server ( routing ,mapping ) and also XI adapter type based SOAP connectivity ( R3 --> PI http connection ) is possible using AAE.
In that case, can the above scenario in XI 3.0 be redesigned /reimplemented in PI 7.1 taking advantage of AAE and thus increasing the throughput ? Please advise with your thoughts and relevant documents on AAE on PI 7.1 with an example of implementation of the above scenario.

I read in new PI 7.1 features that AAE has all features available in Integration server ( routing ,mapping ) and also XI
adapter type based SOAP connectivity ( R3 --> PI http connection ) is possible using AAE.
If not wrong this is available for SAP PI 7.1 with Ehp1.
If you try to create SOAP channel ijn SAP PI 7.11 then in the Message Protocol then in the drop-down you see SOAP and XI3.0
Regards,
Abhishek.

SOAP adapter in XI3.0 using J2EE adapter engine

Folks,
I have a scenario SOAP client -> XI 3.0
I am using XI 3.0 and the J2EE adapter framework to configure a sender SOAP adapter. I do not have a Party, just the service and the channel.
I tried using the following url format:
http://<server>:50000/XISOAPAdapter/MessageServlet?channel
=:<service name>:<channel name>
When I use this in my SOAP client , I get an 401 forbidden error in the browser. However when I type this url directly in the browser and I get:
Message Servlet is in Status OK
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#5 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0
ModuleProcessorRemote not instantiated
A couple of questions:
1. Inspite of configuring the sender SOAP adapter, the sender service and the interface, I still cannot see the green light for the SOAP adapter in rumtime workbench->adapter monitoring.
Although the communication channel (in intergration builder- design)shows the status of the adapter as "active"
Does this mean that my SOAP adapter is correctly configured and active?
2. The above mentioned url takes the ABAP engine login/password while the J2EE engine (AFW)takes a different login/password. Which authentication should the SOAP client use?
Thanks for your help!
Shailesh

Post your message to following URL:
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
port is the J2EE port 50000 in your example.
Check the newest manual for further details.
Regards
Stefan

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

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,

Adapter engine not found in Integration Directory

Hello All,
We are having a new server installation. The problem I am having is in Integratin Directory --> Communication Channel, no option for Adapter Engine is present in the drop down. I have checked the following options:
1) SAP BASIS Component with Adapter Mata data is present in Repository.
2) In SLD, Content Maintenance, class XI Integration Server. There are 3 associated objects (the last column). XI Sub-System viewed application system is also present.
3) The Technical and Business Systems are already created for XI Integration Server in SLD.
I have also suggested the blog /people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory , to the Basis team, however the problem still persits.
Kindly suggest how we can resolve the issue and start executing our scenarios.
Regards
Pravesh
Edited by: Pravesh Sharma on Mar 9, 2009 10:11 AM
Edited by: Pravesh Sharma on Mar 9, 2009 10:12 AM

Hello,
I think the BASIS Team has gone through or implemented this OSS note as it is mention in the blog above. However the problem still persists.
Regards
Pravesh

Adapter engine empty in Integration Directory

Hi
when I try to create a Business System in Integration Directory and I am configuring the communication channel
(for example File Adapter or RFC )
the field "Adapter Engine" is empty and has no selection to choose from.
Is there a problem in configuration or else? I have no idea.
Any help is appreciated and points will be rewarded

HI,
I think the problem is your Adapter metadata is not imported.
Import the SAP BASIS Software Component into the Integration Repository.
For more-
Copy XI3_0_SAP_BASIS_<version> (6.40,7).tpz from <Components DVD>/XI /XI_CONTENT to directory /usr/sap/<SAPSID>/SYS/global/xi/repository_server/import/
After that go to Integration Repository->Tools->import Design Objects and then import it.
Regards,
Moorthy

Load balancing Central Advance Adapter Engine

Hello All,
I am trying to get more information on load balancing Central Advance Adapter Engine for SAP PI 7.1. How do I configure and load balance Advance Central Adapter Engine to handle more volume? Should I added extra non-central adapter engines to achieve this? If yes, How do I do this i.e. configuration etc? If not, then what is the best practice on load balancing the Central Advance Adapter Engine?
Thank you for replying,
Mayur

Hi,
I just post your Q&A here.
Cheers,
Aaron
I have few follow up questions regarding your answers.
1. For options 1 and 2, could you elaborate or point me some documentation on sap.help or somewhere else which talks more about these options?
   =========================================
   Basically you have more power with more processes (Instances or Server node) to process your messages in the Adapter Engine. That's the way to improve the system throughput.
   For more information, please refer to SAP PI tuning guide (I could not find the guide for 7.1, but the principle is still the same)
   https://websmp102.sap-ag.de/~sapidb/011000358700000592892005E.PDF
=========================================
2. For option 3, add non central adapter engine and configure scenarios.
    1. So, do I have to run non-central adapters on separate servers?
   ====================
    Yes. It is recommended to run non-central adapter enging on separate server to minimize the reciprocal impact in terms of resource contention.
   ==============
    2. Do I need web dispatcher to do the load balancing between central and non-central adapter engine?
    ========
    No. this is also not possible since the below is true.
    =========
I somehow think that if I am selecting the non-central adapter engine when creating the communication channel then it won't be "load balancing" because I will be sending a particular interface to the non-central engine at design time instead of runtime.
Thank you for taking time and replying to my questions.

Webinar:SAP NetWeaver Process Integration u2013 Advanced Adapter Engine in PI 7

+Please Note: This webinar is aimed at consultants, Patners and Customers in APJ Region and is scheduled at 2.00 - 3.00 p.m. Singapore Time (UTC +8)+
Dear valued SAP Experts,
Next SAP Intelligence Platform & NetWeaver RIG Expert Call Session will take place on Tuesday, September 1. The SAP Intelligence Platform & NetWeaver RIG Expert Call Sessions are designed to support consultants, partners and customers during their implementation projects. The sessions cover all different aspects of SAP NetWeaver and are aimed at experts, thus provide knowledge which is not available via standard training courses. The session duration is typically 60min and includes questions and answers.
Tuesday, September 1, 2009:
SAP NetWeaver Process Integration u2013 Advanced Adapter Engine in PI 7.1 EHP1
Time: 2.00 - 3.00 p.m. Singapore Time (UTC +8)
This event will feature Charu Goel with the SAP Intelligence Platform & NetWeaver Regional Implementation Group. Charu provides the following abstract:
With PI 7.1 Enhancement pack 1, we continuously thrive to bring in advancements in AAE. In this APJ expert call, we talk about the much awaited capability of IDOC packaging along with the enhancements in JMS. You will learn about the interaction between the AAE and ABAP stack, new enhancements on the JDBC adapter and overall improvements in the technical adapters available with PI 7.1 EHP1.
For meeting and Dial-in detail please register [here|http://www.surveymonkey.com/s.aspx?sm=qkBfQCM5FM_2f_2b4O0ihVpFRw_3d_3d]
Thanks & Best Regards,
Sarma Sishta

Hi,
This was one of the good session...
Especially the features such as;
-- TCP/IP connection control with JMS adapters
-- Empty file Handling
-- Set the various Attributes for Mail attachments via dynamic configuration (intially only subject line was possible)
-- Message Prioritization
-- single IDOC Ack for IDOC Packaging
-- IDOC packaging
-- and many more........................
Even the future indicatioon of IDOC J2EE based adapter will provide new direction to the existion IDOC related scenarios..
One thing that was changed in IDOC packaging is to control it via Sender Communication channel...intially we were doing it either via ECC system or with t-code "idxpw"
Its almost in same way...but from J2EE based adapter perceptive IDOC packaging will be available with Java stack...and will no need to depend only ABAp stack for this feature.
Thanks
Swarup

Adapter Engine Error

Hi,
i am working on MQ-XI-BW Scenario.i have configured JMS Adapter in Plain J2SE Adapter Engine.But the status is red with a message
"javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'BWXI:TEST.QMGR'
 at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
 at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1450)
 at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:960)
 at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:159)
 at com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueConnectionFactory.java:215)
 at com.sap.aii.messaging.adapter.ModuleJMS2Transport.init(ModuleJMS2Transport.java:382)
 at com.sap.aii.messaging.adapter.ModuleHandlerImpl.run(ModuleHandlerImpl.java:576)
 at java.lang.Thread.run(Unknown Source)"
My class path looks fine.i am on SP9. there is an OSS note with similar error. But the Pre requisite is given as SP5.
what could be the reason behind this issue?
When i try to refresh the central integration server cache in ID using Env->Cache Notifications, i am getting a message
 http connection to "http://bwxi:8200/CPACache/invalidate" returns the status code "401" in response
This particular URL is not accepting any user and password. Do i need to set the user name and password somewhere so that i can have access to this?
Please help me out.
Regards
Sathya

Hi Amol,
 Thanks a lot.I am not very confident in my configuration.Could you please verify the configuration parameters once?
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.
XMB.SenderBusinessSystem=MQSeries
XMB.SenderService=BS_MQ
XMB.SenderInterfaceNamespace=http://xitest
XMB.SenderInterfaceName=MI_Out_File
XMB.ReceiverBusinessSystem=MTX
XMB.TraceLevel=1
XMB.LoggingLevel=1
XMB.QualityOfService=EO
XMB.QueueId=ABCDEFABCDEF
XMB.ContentType=text/xml
URL of XI IS to send the messages to
XMB.TargetURL=http://bwxi:8000/sap/xi/engine?type=entry
XMB.User=XIISUSER
XMB.Password=Mind2005
XMB.Client=100
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=MUSR_MQADMIN
JMS.QueueConnectionFactoryImpl.password=Mind2005
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 CH_BWXI
JMS.QueueConnectionFactoryImpl.method.setTransportType=java.lang.Integer {com.ibm.mq.jms.JMSC.MQJMS_TP_CLIENT_MQ_TCPIP}
JMS.QueueConnectionFactoryImpl.method.setQueueManager=java.lang.String TEST.QMGR
JMS.QueueImpl.classname= com.ibm.mq.jms.MQQueue
JMS.QueueImpl.constructor=java.lang.String LQ
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
Regards
Sathya

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

Error in Local J2EE Adapter Engine

Hi All,
We configured the J2ee Adapter engine and did the design and Configuration part also.but while testing the scenario it's giving error in SXMB_MONI as
*<?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="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.ConfigException: ConfigException in XI protocol handler. Failed to determine a receiver agreement for the given message. Root cause: com.sap.aii.af.service.cpa.impl.exception.CPALookupException: Couldn't retrieve outbound binding for the given P/S/A values: FP=;TP=;FS=BS_LAE;TS=BS_LAE;AN=MI_PPS_IB;ANS=urn:pps.com;</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anyone suggest me?
Thanks,
Kalyan.

Hi kalyan,
If the error still says that, "Failed to determine a receiver agreement for the given message" - could you please compare the Sender/Receiver party/service determined in the XI message header and that in the Receiver Agreement in ID? Also please check the same for the Receiver Interface and Namespace. receiver agreement not found means any of these values doesn't match. If these look fine.............can you provide us with few more extra information...........like at which pipeline step in MONI you getting the error - the message hasn't yet reach Adapter Engine. So I don't think it's a problem in AE.
Regards,
Suddha

What is the max file size that a Adapter Engine [J2SE] can handle ?

We are having a scenario where a 4 GB compressed file needs to be sent across without mapping, I'm trying to explore the possible options to tackle this scenario.
Some of the options, we are considering :
- Sending a file from one Adapter Engine [J2SE] to another Adapter Engine [J2SE] bypassing PI. Adapter Logs will be monitored. What is the maximum file size that can be then handled assuming a standard installation ?
- What is the max file size that Adapter Engine [J2SE] can send through PI without mapping?
Any help with the above options or with any other possible solutions to handle extremely large file transfers will be much appreciated.

Hi,
j2se is not a good option here
if you have 4gb then you need a copy solution
a) build an proxy that will just copy the file from sender dest to receiver
b) build an adapter that will do the same as proxy)
this way processing of this message will be controlled with SAP PI/XI
it will be as quick as copy & paste of the 4gb file
I did the a) for one of the flow for 300 mb and it works perfectly
Regards,
Michal Krawczyk

Can not release change list in Integration Builder: Design

I got the following error any time i try to release a change list in the integration builder: Design.
#18 13:51:21 AWT-EventQueue-0 ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
Thrown:
MESSAGE ID: com.sap.aii.ib.gui.operations.rb_commands.MESSAGE_TRANSPORTERROR
com.sap.aii.utilxi.swing.framework.FrameworkException: Errors occurred when transporting the change list
at com.sap.aii.ib.gui.operations.TransportCLCommand.execute(TransportCLCommand.java:203)
at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:196)
at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:134)
at com.sap.aii.utilxi.swing.framework.CommandAction.actionPerformed(CommandAction.java:69)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.AbstractButton.doClick(Unknown Source)
at com.sap.plaf.frog.FrogMenuItemUI$MouseInputHandler.mouseReleased(FrogMenuItemUI.java:833)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Root cause:
java.lang.AbstractMethodError: com.sap.aii.ib.sbeans.transport.TransportServiceRemote_Stub.releaseForeignChangelist(Lcom/sap/aii/ib/core/clmgmt/ChangeListData;Lcom/sap/aii/ib/bom/gen/XiTypeId;Lcom/sap/aii/ib/core/transport/api/options/ExportOptions;)Lcom/sap/aii/utilxi/misc/api/ICheckResult;
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
at $Proxy6.releaseForeignChangelist(Unknown Source)
at com.sap.aii.ib.client.transport.gen.TransportServiceDelegate.releaseForeignChangelist(TransportServiceDelegate.java:218)
at com.sap.aii.ib.gui.operations.TransportCLCommand.execute(TransportCLCommand.java:189)
at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:196)
at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:134)
at com.sap.aii.utilxi.swing.framework.CommandAction.actionPerformed(CommandAction.java:69)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.AbstractButton.doClick(Unknown Source)
at com.sap.plaf.frog.FrogMenuItemUI$MouseInputHandler.mouseReleased(FrogMenuItemUI.java:833)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

See these threads, may be these help you:
Re: Logon to Integration builder & repository hangs
How to use TCPGateway
Search for AWT Enqueue error:
http://backups.lbl.gov/backups/documentation/SysAdmin/4.5/NetBackup_Release_Notes.pdf
BR,
Alok

Adapter Engine is disable in integratin builder design

Similar Messages

Maybe you are looking for