AAE configuration

Hi experts,
I am configuring the interface PROXY >PI>JMS using AAE features. I created required IR objects.
Then I am configuring my interface with ICO. Here i am trying to add my created sender communication channel as SOAP (for Proxy with message protocol as XI.30) and it is assigned to sender Business system. In ICO INBOUND PROCESSING tab i am trying add created SOAP communication channel. but this is not popup in the list.(means it is not available in the list) here i created
currently we are Using SAP PI with EHP1.
Thank you
Srinivas

hi Srinivas,
how many Adapter Engines are used?
make sure that the CC are assignd to the Business System (double klick at BusinessSystem -> Tab "Sender")

Similar Messages

How to retreive the dynamic file name in the AAE configuration?

Hi Guys,
I have configured File to File with the integrated configuration and in the mapping i need to retreive the file name dynamically and i am unable to retreive it from the run time in AAE configuration. I am able to retreive with the normal configuration where integration engine is the run time.
I am using the code as below. Is it possible to retreive the file name dynamically in the AAE configuration? any help or suggestions would be appreciated.
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/File","FileName");
String ourSourceFileName = conf.get(key);
return ourSourceFileName;
Thanks,
Srini

Hello Srinivas,
Brief Solution:
1. Using dynamic configuration, set the attribute value of payload dynamically to ASMA
2. Using AF module, write the value of ASMA in a variable
3. Using the variable substitution, set the receiver file name schema
Plz go through the below link:
http://wiki.sdn.sap.com/wiki/display/XI/CombiningthreedifferentaspectsofPIinoneshot
Thanks,
Satya Kumar

PI7.11 AAE configuration

I have Interfaces that use both Classical (pinpline steps in ABAP stack) and local processing (bypassing ABAP stack and thus pipeline steps in AAE).
This is an example scenario for the Local processing I like to do:
ECC<--(soap)PI--
>JDBC client.
I've created RFC destination correctly.
Then sxmif--->created sumparameter, Senderid
In sxmb_adm:
I have IS_URL current value = dest://A_INTEGRATION_SERVER which is the classical way.
Then I added IS_URL assigned subparameter (I named it RECONRPTSENDER" for above scenario) with current value, "dest://AAE_PEH"
According to "How to Set up the Communication between ABAP backend and SOAP Adapter using XI Protocol (http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b?quicklink=index&overridelayout=true)", page 6,
the system checks the entries with sub parameter first (for instance the above scenario has subparameter, RECONRPTSENDER that I assigend) then it should use "dest://AAE_PEH", but it is going to "dest://A_INTEGRATION_SERVER"
When I change the Corresponding Integ. Server to : dest://AAE_PEH, it does work! But I do not want to do that because I need to use the Classical processing for other scenarios!
What am I missing here? Anyone please..

Just FYI on a different note, I ran a test using the direction (dest://AI_INTEGRATION_SERVER) and the error involes calling Inbound proxy.
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = RS1</Trace>
<Trace level="1" type="T">client = 400</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAPPLUSER</Trace>
<Trace level="1" type="Timestamp">2011-02-04T19:06:51Z EST</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 4D4A84750C5E30BFE10000000AFE14E1</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>

Does PI7.1 enh 1 support WS-RM

I can't find WS-RM option in ID....
What's the different between PI7.1 and PI 7.1 enh1?

SAP PI7.1 EHP1 does support WS adapter (at least as per help).....just that you cannot use it for AAE configuration.
Most of the enhancements are documentated here: /people/udo.paltzer/blog/2009/08/12/unrestricted-shipment-of-sap-enhancement-package-1-for-sap-netweaver-process-integration-71-as-of-july-31-2009
Can you find metadata for WS adapter under:
SWCV --> SAP BASIS --> http://sap.com/xi/XI/System --> Adapter Metadata --> WS
Regards,
Abhishek.
Edited by: abhishek salvi on Dec 13, 2009 2:53 PM

PI 7.1 Integrated Configuration for AAE - Issue Accessing Attachment

Hello All,
PI 7.1 in its new features allows access to the Attachment using UDF's withing Graphical Mapping.
Tried this feature and works good in Graphical mappings; am able to access the Attachment; and write it into a Field on my target. This works with the standard XI pipeline steps of passing message from AE to IE back to AE.
When trying to use the same set up with the Advanced Adapter Engine, - Integrated Configuration; this feature doesn't seem to work and the mapping run time triggers a Null Pointer Exception.
None of the SAP documentation discusses this as a limitation of AAE and hence am wondering if this is a bug or is this a limitation? Has anyone on the forum tried this?
Regards
Bhavesh

Hi Bhavesh,
I also tried this scenario long back when PI7.1 was in Rampup mode. We tried and first part was working fine as you also written, but in second part we got stuck. After some research, we found that we cannot configure additional communication scenarios that contain, for example payload-based routing or a message split, with Integrated Configuration. You must define separate receiver determinations, interface determinations, and communication agreements to configure communication scenarios of this type. We can only configure communication scenarios where message is transfered withing AAE.
MAy be you need to check the receiver interfaces and Mappings or may somthing missing there.Also check for authorized Service User.
Possibilities are like something missing is in Integrated Configuration but not sure.
Regards
Aashish Sinha

Integrated Configuration - AAE - Monitoring

Hello All
I am trying to understand how Integrated Configuration works in the runtime and things look rather neat to me with my scenario working.
But monitoring this in the RWB, few questions cropped up, which I hope someone can help answer:
1. Inbound and Outbound Payload Monitoring
When message get processed within the Integration Engine, we can see the input payload and also the output of the mapping. In the case of the Integrated Configuration, is this not possible? I don't see any new special window open and hence how is the monitoring of the various steps specifically input and output done?
2. Mapping Trace not accessible
To further analyze what is new, we put a few standard XI trace steps into the mapping to see where these traces are displayed in the runtime. We thought it would be a part of the Audit Log, but it is not. Has anyone experience with how trace (custom mapping trace using the AbstractTrace object ) can be used with Integrated Configuration or is that another limitation with PI 7.1 and the Integrated Configuration?
To me these two are major requirements as a application developer to do my development and support and hence am wondering whether to gain performance have these options been eliminated or is there some set up needed on the server which we have missed.
Thoughts , ideas welcome.
Regards
Bhavesh
PS : You know what my questions to the Subject Matter Experts at the Bangalore teched are going to be

Hello Rodrigo,
Regarding monitoring of different versions of the message processed by means of AAE, this is unfortunately not possible in PI 7.1x - message is persisted only once in such scenarios (after receiver/interface determination). Multiple persistence of the processed message in Java stack is only available in 7.3x - there you have options for configurable staging (property xiadapter.stage.conf of J2EE service XPI Adapter: XI) and logging (property xiadapter.logger.conf of J2EE service XPI Adapter: XI) of the message so that several versions of the message (e.g. before mapping and after mapping) can be observed (incl. these versions' payloads). Technically, it is possible to setup staging/logging for different processing steps (namely stages - analogue of pipeline services in classical Integration Engine processing) - but, as I said, in 7.3x and not in 7.1x.
Speaking about creation of custom audit log entries, did you check SAP standard AuditMessageKey and AuditAccess for this? (http://help.sap.com/saphelp_nwpi711/helpdata/en/3b/6fe540b1278631e10000000a1550b0/frameset.htm)
Regards,
Vadim

AAE proxy to file configuration using IE

Hi,
I am using PI 7.1 Ehp1 and working on ABAP prxy to File scenarios and does not involved any mapping or ESR object.
I used Integrated Configuration for the same to bypass the IE. So it should use AAE processing for sender and receiver procssing.
For Sender- I used Soap as Sender and file as Receiver.
I have applied OSS note 1334174 also for the same.
Now when I am testing with RWB then message process successfully. But as we are bypassing IE here and using integrated configuration and using AAE then the message should not be displayed in SXMB_MONI and should be available in RWB- monitoring.
I am not able to understand why it is showing in SXMB_MONI monitoring ideally it should not why it is using integration engine.
Please correct me what I need to do so that it should not use IE for processing the message.
regards
Ram

Hi,
>>>I am not able to understand why it is showing in SXMB_MONI monitoring ideally it should not why it is using integration engine.
as by testing using TEST tab in RWB you send it to IE - so not a proper way
RWB cannot be used to test local AAE flows
>>>Please correct me what I need to do so that it should not use IE for processing the message.
just run the flow from ABAP proxy to file and not via test tab in RWB and check if it works
Regards,
Michal Krawczyk

How to handle Integrated Configuration performance impact on AAE/Java AS

Hi there,
Recently I have moved a configuration scenario from standard flow involving both ABAP and Java stacks, to Integrated Configuration usage. Undoubtedly, this will increase the load on AAE/Java stack. However, do you have link to some clear (official - even better) guidelines - what configurational changes should be done on Java side in order to handle the performance impact of such transition?
Best Regards,
Lalo

Hi Lalo,
In fact, using AAE generates no traffic in ABAP stack at all (it is ommited when processing a message), while the traffic in Java stack should be lower than for normal scenario. The performance should be noticeably better, thanks to smaller number of persistence steps and no costly HTTP connections between stacks. For more details, please refer to this document:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/2016a0b1-1780-2b10-97bd-be3ac62214c7
Important quotation from this document:
Since the Integration Engine is bypassed for local message processing in the AAE, the resource consumption both in memory and CPU is lower. This leads to higher message throughput, and faster response times which especially is important for synchronous scenarios.
Moreover, have a look at this document, especially its beginning, for details about the architecture of AAE processing:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70066f78-7794-2c10-2e8c-cb967cef407b
Hope this helps,
Greg

No alerts from AAE after configured Solman as central Alert Server

Hi all,
i have configured a Solution Manager system to act as a central alert servcer for our PI landscape. We are using PI 7.1 ehp 1.
I changed the required nodes in the exchange profile and created the PIRWBUSER in the solution manager system. After restarting the J2EE engine of the PI system the alert rules are no created on solutiuon manager and alerts which occur in the integration engine are raised in the solution manager system. However alerts which are raised in the AAE are not forwarded.
When i check the application log in NWA I see the follwing error, whenever an alert should have been raised:
No central monitor defined in RWB.
Thrown:
com.sap.aii.rwb.exceptions.JaycoRequestFailedException: Neither messager server nor application server are defined for system SMB
at com.sap.aii.rwb.core.R3System.getITSUrl(R3System.java:1090)
at com.sap.aii.rwb.core.R3System.getITSUrl(R3System.java:1558)
In ABAP the connection CentralMonitoringServer-XIAlerts is configured correctly as alerts from the IE engine are working. I suppose I missed some configuration in the java stack. Can somebody help me on that?
Best regards and thx
Florian
Edited by: Florian Wittke on May 10, 2010 9:25 AM

Hi Caio,
thanks for your replay. Yes I know this note. But it does not solve my problem. I increased the trace level of the location where the alerts are raised in adapter engine. I get the following new entry:
Connect to message server host failed
Connect_PM TYPE=B MSHOST= FQDN GROUP=SPACE R3NAME=<SYSID> MSSERV=sapms<SYSID> PCS=1
ERROR       service 'sapms<SYSID>' unknown
TIME        Mon May 10 15:27:48 201
RELEASE     711
COMPONENT   NI (network interface)
VERSION     39
RC          -3
MODULE      niuxi.c
LINE        1654
DETAIL      NiPGetServByName: 'sapms<SYSID>' not found
SYSTEM CALL getaddrinfo
COUNTER     1
Issue has been resolved..the message server was not reachable due to missing entries in the services file.
Edited by: Florian Wittke on May 18, 2010 11:58 AM

ABAP Proxy sender possible in integrated configuration AAE with PI 7.11

Hi guys,
we are running PI 7.11.
We have serveral scenarios where the senderis an ABAP proxy and the receiver is reached by a jave adapter.
With Ehp1 the SOAP adapter offers the possibilty to chose XI 3.0 as message protocol.
We use this feature already in scenarios where ABAP proxy is receiver.
But is it also possible to use it at sender side?
Kind regards
Jochen

Hi Volker,
thanks for your help.
You could also use ABAP proxy at sender side during integrated configuration.
Prerequisite is to implement SAP note 1349125 and use following url for acessing the PI from SAP backends.
http://<host>:<port>/XISOAPAdapter/MessageServlet?ximessage=true
With this URL you could ABAP proxies in normal scenarios where integration server is involved as well as in integrated configurations.
Kind regards
Jochen

File to File USing integrated configuration AAE

Hi experts,
We have configured simple file to file scenario (File Tunneling) using ICO feature for Advance Adapter Engine.
While testing the interface we are getting following error in sender communication channel.
Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Receiver Determination failed for message 10e9a7f7-36f6-49df-3690-d88314d156ac(OUTBOUND)
It is not able to determine the Receiver system.
Please advise...
Regards,
Deepak

The issue has been resolved now.
Solution:
There is a slight configuration which is required for the ICO to work with file tunneling with Dummy ESR objects.
In case, the incoming message is not resembling the Data/Message type please check the radio button as u201CNon Operation Specificu201D in Receiver tab of the ICO objec and ICO will work.
Thanks for inputs.

Idoc configurations in PI7.3

Hi Experts,
For an Idoc scenario prior to PI 7.3, RFC destination, port, logical system and partner profile needs to be created in case of outbound Idoc scenario and again at XI side we need to create RFC destination, port and loading of meta data....
Is the same is applicable for PI 7.3 as well? since Idoc resides in AAE in PI 7.3, I believe there could be some changes applicable for these settings of Idoc....
Pls provide your inputs.....

Hi,
Along with the links provided by Phani and Gayatri you can laso refer this thread for IDoc configuration in PI7.3
IDOC settings from sap r/3 to sap pi7.3
IDoc Packaging in PI7.3
http://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/4096a6b3-3dc3-2d10-bf87-f63d5340a916
Configuring PI 7.30 Java IDoc Adapter
PI/XI: PI 7.3 New Java based IDOC adapter's configuration (sender, receiver) - teaser
IDoc Acknowledments in PI7.3
acknowledge handling for IDOC_AAE in sap PI 7.3
IDoc_AAE acknowledgement handling in PI 7.3
IDoc related error in PI7.3
Processing error in Idoc_AAE sender channel
Hope its informative.
Regards,
Amol

Integrated Configuration- Problem occurred in receiver agreement for sender

Hi , I am using AAE in PI 7.1 and it is proxy to file scenrios.
When Ia m doing testing in Integration Directory in test configuration its giving me this error .
Problem occurred in receiver agreement for sender -<ECCBUSINESSSYSTEM> to receiver -BS_D_EPS,http://abc.com/sap/pi/HR/Qualifications.Qualifications_Async_Out: No receiver agreement found for , -<ECCBUSINESSSYSTEM> , BS_D_EPS, http://abc.com/sap/pi/HR/Qualifications, Qualifications_Async_Out
( here it should take interface Qualifications_Async_In, but logs says it is pointing to outbound interface)
here when I am going in to trace logs then it seems that are not able to understand the receiver interface . rather then it is taking sender inface in logs..
In trace logs . I am getting
Receiver Determination
<Not found>
<Trace level="1" type="B">CL_RD_PLSRV-ENTER_PLSRV</Trace>
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
<Trace level="2" type="T">Start with given receiver - BS_D_EPS </Trace>
<Trace level="2" type="T">Using Receiver Determination 00000000000000000000000000000000 </Trace>
<Trace level="1" type="T">No Relation found - accept given Receivers. </Trace>
<Trace level="2" type="T">...extracting Receiver from Header: BS_D_EPS </Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules. </Trace>
<Trace level="3" type="T">...create rule engine </Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0 </Trace>
<Trace level="2" type="T">Number of Receivers:1 </Trace>
<Trace level="1" type="E">CL_RD_PLSRV-ENTER_PLSRV</Trace>
Interface Determination
<Not found>
<Trace level="1" type="B">CL_ID_PLSRV-ENTER_PLSRV</Trace>
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N </Trace>
<Trace level="1" type="T"> Cache Content is up to date </Trace>
<Trace level="1" type="T">...There is no Interface Determination configured for receiver party and receiver service BS_D_EPS </Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) BS_D_EPS Qualifications_Async_Out </Trace>
<Trace level="2" type="T">...valid InbIf without Condition: Qualifications_Async_Out </Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1 </Trace>
<Trace level="1" type="E">CL_ID_PLSRV-ENTER_PLSRV</Trace>
Operation Mapping
<Not found>
<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>
<Trace level="2" type="T">......attachment XI_Context not found </Trace>
<Trace level="3" type="T">Mapping already defined in interface determination </Trace>
<Trace level="1" type="T">No mapping configured </Trace>
<Trace level="1" type="E">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>
I have developed the other integrated configuration scenario and this is working fine .
please let me know how can I troubleshoot it

I am using sender as Soap and receiver as File adapter.
here the problem is that while going for interface deteremination and receiver agreement it is calling to Outbound interface .
It should call the inbound interface. I put all the details correctly and deleted all the objects and crated again for both Ir and Id..
I put the name of inbound interface in configuration but while executing its calling outbound interface.

Mapping Error in AAE in PI 7.1

Dear Team,
If we use message mapping along with AAE concept , What are the objects we need to create in ESR and ID .
How can we monitor the messages - messages failed with Mapping Error.Is there any new option available in RWB?
Thanks&Regards
Drumi

Hi,
ESR Objects are same but in ID we need to create Integrated configuration
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/700058f0-b1a1-2a10-39a8-ab2627b87cfa
If we are using AAE then we don't get any status in SXMB_MONI.
Regards,
Venkata Ramesh

PI 7.3 receiver AAE idoc scenario-No receiver comm channel found in ICO

Hi,
I am working in PI 7.3 receiver AAE idoc scenario.When I try to configure Integrated Configuration(ICO),I am not able to see the receiver comm channel in receiver agreement.
What is the reason for this??I have configured the communication channel,but still its not shown in reciver agreement dropdown.
Please help.
Regards,
Sriparna

Hi Sriparna,
In PI 7.3 there is are two separate IDoc adapters: "standard" IDoc adapter and one that is dedicated for AAE (ICO). Make sure that you have used the right one - most probably not, which is why you cannot see the channel in the dropdown list.
Hope this helps,
Grzegorz

AAE configuration

Similar Messages

Maybe you are looking for