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>

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

  • Problem with CCMS PI7.1 alert configuration for RWB Alert count

    Hi,
    We have configured CCMS alert for PI7.1 RWB failure count. Alert is getting triggered only one time and after that no alerts. I can see the change in data but alert is not getting triggered. If I complete the alert then immediately in next run a new alert is generated with last reported data and then again there will be no alert going forward. Data is collected but no alert is triggered. Does anyone know the reason for this and how to fix it? Please help.
    Thanks,
    Kavitha Rajan.

    Hi Jayan,
    Our PI alert configuration is fine. And also we did not choose multiple suppress method. Problem is with Solution Manager CCMS PI alert configuration for failed RWB count. After initil alert and then nomore alerts are triggered. If I complete the alert then again only first alert is triggered and again no alerts going forward. Please advice.
    Thanks,
    Kavitha Rajan.

  • 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")

  • Need PI7.1 technical configuration guide

    I used to see the XI3.0 configuration guide on the internet.
    Now I cannot find  XI/PI  configuration guide any more.
    Any idea where to get the link?
    Thanks a lot!

    Jenni,
    Your heading and your description varies completely! Are u looking for PI 7.1 or XI/PI config guide.
    By the way are u looking for Demo config guide, if yes then -https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/soa/soa-management/exchange-infrastructure/xi-design_configuration/configuration%20guide%20sap%20exchange%20infrastructure%203.0%20demo%20examples.pdf
    If not, kindly ignore it.
    raj.

  • 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

  • Alert Rule Configuration in SAP PI 7.3

    Hello,
    I am using PI 7.3. It's java stack only. I am using component based alert configuration.
    AlertConsumerJob is running. But for a particular scenario, no alert is generated, although the message status is "System error". We are getting the below error for this scenario.
    com.sap.engine.services.jndi.persistent.exceptions720.NameNotFoundException: Object not found in lookup of PI_Technical team.
    This alert generation is working fine for others scenarios. Means, we are able to get alert mail for other scenarios.
    Please advise.
    Thanks & Regards,
    Moumita

    Hi Moumitha,
    Please find below links may be its Helps you
    Alert Rule is not sending Alert Emails PI7.3
    Alert Configuration in PI 7.31
    Regards,
    Rajendar K

  • 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

  • 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

  • Configure ABAP Proxy scenario in PI7.3

    Hello Experts,
    Can someone please let me know if we have somewhere step by step procedure to configure an ABAP Proxy scenario in PI7.3, I couldn't find How-to guide related to this on SDN.
    Thanks a lot.
    Best Regards,
    Shweta

    I dont know abt your installation whether you have java stack alone or both java stack and abap stack.
    AAE or local processing:
    You can do using soap adapter as transport protocol and message protocol as XI for proxy. This way you can use local processing using AAE.  I dont see documents in SDN as of now. But it is pretty simple. Just follow the steps what I mentioned.
    Classical processing or abap engine:
    Still the same as previous versions.

  • Connection Configuration to Central Services Registry in PI7.1

    Hi Freinds,
    while in CE7.1-
      NWA->Configuration Wizard-> I have this set up file Connection Configuration to Central Services Registry to configure the central service registry.
    while on PI7.1 EHP-1
    I dont have this setup file Connection Configuration to Central Services Registry.
    Is this included in Any Configuration service, or with different name?
    Regards
    chandra Dasari

    Hello Chandra
    See the link below.
    Configuring a Central Services Registry 
    http://help.sap.com/saphelp_nwpi71/helpdata/EN/46/bb923d06582710e10000000a11466f/content.htm
    Regards
    Mark

  • 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 configure MQ-FTE and IBM Datapower along with PI7.1

    Hi Friends,
    Can somebody guide me with the steps to configure MQ-FTE and IBM Datapower with PI7.1 for B2B communication?
    Thanks,
    --Sonal

    1. What is the difference between JMS MQ and Native MQ? How to determine which one to use?Native MQ refers to a proprietary api provided by IBM in multiple languages including java so that applications running on these can communicate mq. IBM also provides JMS wrappers around this native api, so that a jms client can talk to mq using JMS API. This is called MQ JMS.
    2. If native MQ can be used here, what are the steps to configure Native MQ on WLS in my situation?SOA suite provides a MQ Resource Adaptor which can be used to connect to MQ. The developers of this resource adapter would have used the native api to enable the adaptor to talk to MQ, so that you dont have to worry about it. However you will need to configure the properties of your local MQ ( qmgr , q name etc). This is done in the outbound connection pool properties of the resource adaptor.
    please check this blog for how to do this : http://soa-bpel-esb.blogspot.com/2009/09/configuring-mq-in-11g-soa-suite.html.
    Since your MQ installation is in a remote machine you will have to configure the following properties specific to your environment - hostname, port, server connection channel, along with the queue manager name and queue name
    3. Do I need any foreign servers or message bridges to be configured?Not required for your case if you are using MQ Adaptor. Since MQ also provides a JMS transport , you would have required foreign servers if you have to use JMS Adaptor instead of MQ Adaptor. Native MQ is expected to be faster than MQ JMS as it doesn't have the extra JMS layer.

  • Managed System Configuration - PI7.1 system solman_setup

    HI all,
    In trying to execute the step "Managed System Configuration" for a PI7.1 system in Solution Manager SOLMAN_SETUP, in the first step to "maintain the connection", its failing immediately with:
    Error when opening an RFC connection
    Establish connection to System <hostname>(01) - <SID>_001
    Any ideas?
    Thanks, Neeta

    Hello Neeta,
    i face the same problem.
    Establish connection to System <hostname>(01) - <SID>_001
    / CPIC-CALL: 'ThSAPOCMINIT' : cmRc=20 thRc=726 Gateway ist not connected to the l...
    i check the following and they are all fine.
    - ping to PI from solman
    - PI IP address in SMSY
    Could you tell me which part you configured in SMSY?
    regards

Maybe you are looking for