NWA PI Message Prioritization

Trying to use PI Message Prioritisation and I get the following message when logging onto NWA and selecting SOA Management   Monitoring   PI Message Prioritization. I
Message prioritization data provider not registered for this PI
have searched SDN, SAP Support and Google without any luck. Nothing I can find contains information on configuraing Message Prioritisation in NWA.
We are running 7.1 EHP1 SP3. 
Any help that can be offered would be appreciated....

HI,
Interesting link regarding message prioritisation in RTWB. It appears to be a very simple method of prioritising messages but may prove useful. I'm still interested to know whats wrong with NWA. I have seen all the other links....
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/b2e00f6b156ff4e10000000a42189b/frameset.htm
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f782?quicklink=index&overridelayout=true
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/com.sap.km.cm.docs/media/streamingmedia/events/sap-teched-2009/sessions/soa-middleware/soa203%20general%20performance%20tuning%20with%20sap%20netweaver%20process%20integration/soa203.pdf
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70b8adc3-728c-2a10-7fad-d43f29074ef8?quicklink=index&overridelayout=true
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/com.sap.km.cm.docs/media/streamingmedia/events/sap-teched-2007/virtual%20teched%2007/no%20virtual%20track/epi214%20sap%20netweaver%20process%20integration-advanced%20adapter%20engine/epi214.pdf
Regards

Similar Messages

  • Message Prioritization PI 7.1

    Hi All,
    I want to know how exactlyfunctionality of Message Prioritization of PI 7.1 and the type of scenario in which it can be seen exactly in real time ?
    I have read all the onling help on this topic and now expect practical examples and explanation
    Thanks,
    Amit

    PI7.1 features refer this blog:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/706005a3-3bd6-2910-91ae-a2016239bdcf
    Advanncements of PI 7.1
    1. Enterprise Services Repository as a central storage location for enterprise service definitions and lifecycle management data for all enterprise services (Concept of Folders,.
    Using Folders in PI 7.1
    Using Folders in PI 7.1
    2. Universal Description, Discovery, and Integration (UDDI) 3.0u2013compliant services registry for runtime management of enterprise services.
    XI : How To publish WSDL generated from XI to UDDI
    XI : How To publish WSDL generated from XI to UDDI
    WebAS : A step by step guide for Configuring UDDI registry on Local Server
    WebAS : A step by step guide for Configuring UDDI registry on Local Server
    3. Enterprise Service Oriented Architecture (ESOA), Global Data Types, Modeling Tool Concept.
    ESOA BASICS
    SAP Architecture u2013Enterprise SOA Basics
    SAP Architecture –Enterprise SOA Basics
    Quick Guides for setting up an eSOA prototyping environment with CE, ESR, and NWDS
    Quick Guides for setting up an eSOA prototyping environment with CE, ESR, and NWDS
    ESA = SOA + ES ?
    ESA = SOA + ES ?
    PRINCIPAL PROPAGATION
    Principal Propagation with SAP NetWeaver Process Integration 7.1
    Principal Propagation with SAP NetWeaver Process Integration 7.1
    Principal Propagation in SAP XI
    Principal Propagation in SAP XI
    Modeling tools in PI 7.1
    Modeling tools in PI 7.1
    Publish services from PI 7.1 to the Service Registry
    Publish services from PI 7.1 to the Service Registry
    Using CCTS in PI 7.1
    Using CCTS in PI 7.1
    4. Improved support for standards such as Web Service Reliable Messaging (WS-RM), WS Policy, Security Assertion Markup Language (SAML).
    5. Support Business Activity Monitoring (BAM).
    XI: BAM - Episode III - new super trace
    The specified item was not found.
    XI: BAM - Episode II - Simple Proactive monitor
    The specified item was not found.
    XI: BAM - Episode I - Introduction s
    The specified item was not found.
    6. Advanced Adapter Engine Features (Eg. Bypass Integration Engine Process)
    7. Enhancement for Mapping (Eg. Re-usable User Defined Functions, Look-up function reads multiple fields, Specify mapping parameters at configuration time, Synchronous DB RFC lookups, Message Packing etc.)
    SAP PI 7.1 Mapping Enhancements Series: Correct Structural Inconsistencies
    SAP PI 7.1 Mapping Enhancements Series: Correct Structural Inconsistencies
    SAP PI 7.1 Mapping Enhancements Series: Graphical Support for JDBC and RFC Lookups
    SAP PI 7.1 Mapping Enhancements Series: Graphical Support for JDBC and RFC Lookups
    SAP PI 7.1 Mapping Enhancements Series: Parameterized Message Mappings
    SAP PI 7.1 Mapping Enhancements Series: Parameterized Message Mappings
    SAP NetWeaver Process Integration 7.1: Mapping Enhancements Blog Series
    SAP NetWeaver Process Integration 7.1: Mapping Enhancements Blog Series
    SAP PI 7.1 Mapping Enhancements Series: Mapping Enhancements Demo
    SAP PI 7.1 Mapping Enhancements Series: Mapping Enhancements Demo
    SAP PI 7.1 Mapping Enhancements Series: Copy XML Subtree
    SAP PI 7.1 Mapping Enhancements Series: Copy XML Subtree
    SAP PI 7.1 Mapping Enhancements Series: Using Graphical Variable
    SAP PI 7.1 Mapping Enhancements Series: Using Graphical Variable
    SAP PI 7.1 Mapping Enhancements Series: Share User-Defined Functions
    SAP PI 7.1 Mapping Enhancements Series: Share User-Defined Functions
    SAP PI 7.1 Mapping Enhancements Series: Import SQL Table's Metadata
    SAP PI 7.1 Mapping Enhancements Series: Import SQL Table's Metadata
    MAPPING LOOK UPS
    Lookupu2019s in XI made simpler
    /people/siva.maranani/blog/2005/08/23/lookup146s-in-xi-made-simpler
    XI: RFC Mapping lookups (from BC to XI?)
    The specified item was not found.
    Use this crazy piece for any RFC Mapping Lookups!
    Use this crazy piece for any RFC Mapping Lookups!
    SAP XI Lookup API: the Killer
    The specified item was not found.
    mapping look ups RFC api
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a03e7b02-eea4-2910-089f-8214c6d1b439
    RFC Look up from XSLT mapping
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/05a3d62e-0a01-0010-14bc-adc8efd4ee14
    Data Lookup Optimized
    Data Lookup Optimized
    8. Extended support for high volume scenarios
    huge processing of files
    Night Mare-Processing huge files in SAP XI
    Step-by-Step Guide in Processing High-Volume Messages Using PI 7.1's Message Packaging
    Step-by-Step Guide in Processing High-Volume Messages Using PI 7.1's Message Packaging
    SAP XI acting as a (huge) file mover
    The specified item was not found.
    Managing bulky flat messages with SAP XI (tunneling once again) - UPDATED
    The specified item was not found.
    New NetWeaver Process Integration how-to guide for typical high volumen replication scenarios.
    New NetWeaver Process Integration how-to guide for typical high volumen replication scenarios.
    9. Business Activity Monitoring for process definition of milestone monitoring (event correlation).
    10. Improved SAP NetWeaver Administrator support for central configuration and administration of both mediated and point-to-point scenarios.
    11. XML payload validation and validations using JAVA.
    VALIDATING MESSAGES
    Validation of Messages in SAP NetWeaver Exchange Infrastructure - SDN Member Session EPI213 at SAP TechEd '06 Amsterdam
    Validation of Messages in SAP NetWeaver Exchange Infrastructure - SDN Member Session EPI213 at SAP TechEd '06 Amsterdam
    SOA Middleware: XML validation error handling
    SOA Middleware:  XML validation error handling
    The Hitchhiker's Guide to Validation
    The Hitchhiker's Guide to Validation
    Validations using Java for those not having PI7.1
    Validations using Java for those not having PI7.1
    Xml validation
    XML Validation BPM:
    VALIDATING INCOMING FLAT FILE
    Generic Approach for Validating Incoming Flat File in SAP XI - Part 1
    Generic Approach for Validating Incoming Flat File in SAP XI - Part 1
    Generic Approach for Validating Incoming Flat File in SAP XI - Part II
    Generic Approach for Validating Incoming Flat File in SAP XI - Part II
    Validating messages in XI using XML Schema
    Validating messages in XI using XML Schema
    BPM:
    Enhancements in ccBPM within SAP NetWeaver Process Integration 7.1
    Enhancements in ccBPM within SAP NetWeaver Process Integration 7.1
    12. Process editor modeling enhancements: step groups, integrated alert management and configurable parameters.
    13. Integration of human interaction (generic user decision).
    14. Language dependent texts for end-user display.
    15. WS-BPEL 2.0 adoption (Preview and implementation BPEL4People, BPLE-SPE Simple User Defined Functions can be configured directly in the process.)
    Also refer this links for more clarifications:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/d6/369142f195675ee10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/43/fb4cd3207c7063e10000000a1553f6/frameset.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f36ce30f-0e01-0010-a89b-c158d07c44ff
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ec19c05d-0501-0010-09a2-b6db51b5318d
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5441afe5-0601-0010-dba5-dc5f9d5caa9d
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c50cddbb-0601-0010-92a7-f2a40ca68e6d
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f027dde5-e16e-2910-97a4-f231046429f2
    Refer these threads as well:
    Advantages of using PI 7.1 over PI 7.0
    PI 7.0 and XI 3.0
    http adaptor on which factors we will use
    Diff between XI and PI
    differences between xi 3.0 and pi 7.0
    Difference/ changes from XI 3.0 to PI 7.0
    give me main advantages of XI-7.0 TO XI-3.0
    XI 7.0 vs Xi 3.0
    XI/PI
    XI vs. PI
    XI 3.0 vs. PI (XI 7.0)
    Difference/ changes from XI 3.0 to PI 7.0
    moving from XI 3.0 to PI 7

  • How to handle message prioritization in interface determination

    Hi Experts,
    How to handle the prioritization of messages if we say that for single source message it will be forwarded to 2 types of target messages.
    Here's the scenario:
    InterfaceDetermination object
    SourceMessageA => TargetMessageTypeA
    SourceMessageA => TargetMessageTypeB
    Since both of the target messages will receive the source message, i want to prioritize that TargetMessageTypeB will be receive it first before TargetMessageTypeA.
    Should I structure it in the Interface Determination as this:
    SourceMessageA => TargetMessageTypeB
    SourceMessageA => TargetMessageTypeA
    or this should be handled by BPM? Let say BPM is the last option how could this be configured in ID?
    Cheers,
    R-jay

    Hello Folk,
    you have once option in the interface determination check the maintanence order at runtime , it will solve your problem.
    regards,
    Ravi.

  • Message prioritization

    Hello,
    We need to implement prioritization for messages going from B2B to BPEL. The client will have a very large number of incoming messages of different types. Some are more important than others and must be handled in a timely way. If the system is overloaded the most important messages should be processed by BPEL first.
    Even better would be to prioritize before the messages are picked up by B2B, but as far as we can see that is not possible without writing something that sits in front of B2B and we don't want that.
    Is it possible to control the AQ priority so that B2B uses a different priority for messages that fulfill some criteria (for example that have a specific EDIFACT type)?
    If not our current design is to read the messages from the standard AQ queue and put them on a new one in a PL/SQL program or using the ESB, setting priority in the new queue. The BPEL code would then read from the new queue. Does that sound reasonable, or is there a better way?
    Thanks in advance for any pointers,
    -Erik

    Hello,
    We need to implement prioritization for messages going from B2B to BPEL. The client will have a very large number of incoming messages of different types. Some are more important than others and must be handled in a timely way. If the system is overloaded the most important messages should be processed by BPEL first.
    Even better would be to prioritize before the messages are picked up by B2B, but as far as we can see that is not possible without writing something that sits in front of B2B and we don't want that.
    Is it possible to control the AQ priority so that B2B uses a different priority for messages that fulfill some criteria (for example that have a specific EDIFACT type)?
    If not our current design is to read the messages from the standard AQ queue and put them on a new one in a PL/SQL program or using the ESB, setting priority in the new queue. The BPEL code would then read from the new queue. Does that sound reasonable, or is there a better way?
    Thanks in advance for any pointers,
    -Erik

  • Sync messages should have higher prioritization in IE than async messages

    Hi there,
    does somebody know how I can assign a higher prioritization to sync messages than to async messages in XI 3.0? In case of a bottleneck on the Integration Engine I want to get sync messages processed first. Message prioritization in SXMB_ADMIN does not work because it's ony applicable for async (EO / EOIO) messages.
    Thank you.
    BR,
    Ralph N.
    UPDATE: Since there doesn't seem to be a solution for this issue let me specify it. What kind of installation can be made in the landscape to separate sync messages physically from async messages?
    Edited by: Ralph Nitschke on Jun 25, 2010 1:58 PM

    hi,
    i found some links, hope those helps you
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/20bb9649-e86e-2910-7aa9-88ed4972a5f6
    http://wiki.sdn.sap.com/wiki/display/XI/DifferencebetweenSXMB_ADMandSXMB_ADMINISTRATION
    Queue prioritization
    ** Queue Prioritization in SXMB_ADM - Tuning Param  - Whats the difference
    Also try searach in ussing by "queue prioritization" in SDN you will find many links
    Thanks
    Rodrigo P.
    Edited by: Rodrigo Alejandro Pertierra on Jun 25, 2010 10:25 AM

  • Scheduled Status in Message Monitoring

    Hi All,
    We have a scenario from DB- DB using Java Proxies. The Message interfaces are defined as Asynchornously with EO mode.
    Usually the sender channel picks data and tirggers Java Proxy. Proxy process all records and send the status back to sender in 5 mins.
    But when I started multiple interfaces at the same time, I observe that one interface is taking 15 min and while that interface is in processing state, the other interface which started at that time are also in Scheduled status. But the sender channel picks data for every 5 mins, which is creating duplicate records.
    The interfaces which are in Scheduled status are getting processed only after that interface ( taking 15 min) gets processed.
    Why is this dependency on other interfaces and is there any way to avoid this dependency?
    Please suggest.
    Regards,
    Srini

    you can do queue/message prioritization.
    but I suggest to use one status field in DB, when you are polling DB to select records , immidiately change staus to picked and after processing successfully change it to processed.

  • Proxy messages are stucked in SMQ2.Can I pass these msgs in separate queue?

    Hi Guys,
    File >PI>ABAP proxy. (ECC)
    Once i pick and process the file, the resultant message is updating the table in ECC through ABAP proxy. These messages are high priority and they should not stuck in the queues in ECC.
    The problem is some of the messages of this interface are getting stucked in queues (SMQ2) by colliding with other low priority messages which are failed due to some data issues.
    Is there any way I can separate these high priority messages into separate custom queue and process them?
    Do I need to this in ECC or PI?
    Thanks
    Deepthi

    Hi,
         As Debashis has already said, use message prioritization in PI to handle your requirement.
    For SAP NetWeaver PI 7.0, navigate to SAP NetWeaver 7.0  SAP NetWeaver 7.0 Library  SAP NetWeaver Library  SAP NetWeaver by Key Capability  Process Integration by Key Capability  SAP NetWeaver Exchange Infrastructure  Runtime  Integration Engine  Prioritized Message Processing.
    For SAP NetWeaver PI 7.1 (including EHP 1), navigate to SAP NetWeaver  SAP NetWeaver PI/Mobile/IdM 7.1  SAP NetWeaver Process Integration 7.1 Including Enhancement Package 1  SAP NetWeaver Process Integration Library  Function-Oriented View  Process Integration  Integration Engine  Prioritized Message Processing.
    For more details about message prioritization within the Advanced Adapter Engine, please refer to SAP Help Portal http://help.sap.com, and navigate to SAP NetWeaver  SAP NetWeaver PI/Mobile/IdM 7.1  SAP NetWeaver Process Integration 7.1 Including Enhancement Package 1  SAP NetWeaver Process Integration Library  Function-Oriented View  Process Integration  Process Integration Monitoring  Component Monitoring  Prioritizing the Processing of Messages.

  • Queue Prioritization in R3/ECC

    Hi,
    We have prioritize PI queues already. In PI it is more of interface specific queue allocation. If we go to sxmb_adm of R3/ECC, again we could see similar options of managing queues. Do we have some simitar concept in R3/ECC too? e.g. if there a lot of  messages coming to ECC from a low priority PI message, then is there any possibility of sending these messages to specific queues in ECC?
    Kind regards,
    Prateek

    Okay ;o)
    So transfering IDocs via qRFC between systems might be an option for you. But this just guarantees that for example EOIO messages do not overtake one another even during transfer from one system to another.
    IDocs are processed in the ECC system via 2 ways. Either "immidiately" when received, or via "background job" which has to be scheduled. Please see you config per inbound message in ECC in WE20.
    So I guess the prioritization as you need it will not be provided by message prioritization as configurated in XI.
    Kai

  • Using "messaging.system.queueParallelism.maxReceivers"

    Hi Experts,
    Happy New Year 2012!!!
    I am working in a landscape where there are integrations between 'CRM to MDM' and 'MDM to Non SAP Systems' using PI. There is a lot of data which flows through these interfaces and some times the PI MDM adapter clogs up and it stops both inbound and outbound data flow.
    To address this issue we have been suggested to use "messaging.system.queueParallelism.maxReceivers" : Note - 1136790.
    I was trying to collect some information on this but could only see scenarios using JDBC receivers. Hence i have a few questions to ask:
    1.) Is this note only applicable to JDBC receiver scenarios? If yes, then can you please give a back ground as to why?
    2.) If No, then how should i configure this in my PI system?
    3.) How can i tag a particular scenario to this property? This is mentioned as a 2nd point in the note solution section but the steps are not given.
    Thanks in advance,
    Anshul

    Dear Supriya,
    Thanks for your inputs. I have a few more questions to ask to further drill down this configuration:
    2.) If No, then how should i configure this in my PI system?
    --> You can configure this parameter in NWA for messaging system property.
    Anshul -> Since i do not have access to NWA, can you please give the hierarchy path in NWA to reach messaging system property. Here do i have an option to mention 1 or 2 particular scenario where i want to restrict the number of parallel worker threads being used on the inbound adapter. This question is basically to understand how this configuration works. This restricts the number of parallel worker threads, so how it will work if i dont tag it to a scenario. What if i have 3 CRM to MDM scenarios with equal amount of loads happening at a single instance.
    Does this configuration implies to one single instance of an adapter or it affects all the instances.
    Is there a way i can test, how affectively this configuration is working to improve my PI system performance?
    Warm Regards,
    Anshul

  • "waiting" and "system error" status cannot be resent in rwb?

    Hi,gurus:
    In RWB->MESSAGE MONITORING,I can't resend or cancel the messages with the status " waiting" and "system error".
    when I clicked "resend" button,it asked for user and password.After I was authentificated,the system didn't resend a message. Have you ever met this issue?
    By the way,I could resend the error messages before.
    Thanks in advance.

    Hi,
    I checked the note 1233918,and it talked about the same issue.
    But the solution is as follows,which I don't know what to do.(Our PI version is PI7.0 SR3 SP14)
    Symptom
    When the first message for a managed system is cancelled or resent, after pressing ok in the logon pop-up nothing happens - message is not resent or cancelled. The logon data is correct, since subsequent resend/ cancel works without further logon request. Another symptom is cancelling or resending a wrong message, when using the filter mechanism in the table. E.g. the table displays messages A, B, C, D. If message C is selected and after that the filter is set so that message C is hidden from the filter selection, when selecting message D and trying to resend/cancel it, message C is cancelled/resent (the hidden one, previously selected) and nothing is happening with message D.
    Other terms
    NWA, PI, Message monitoring, resend, cancel
    Reason and Prerequisites
    The UI Proxy connection was not obtained properly. Another reason - TableAccessories was not invalidating the nodes properly. Also after filtering the result list, resend/cancel was taking wrong message Ids.
    Solution
    For SP5 install LMNWABASICCOMP05P_1.SCA or higher patch level.
    For SP6 install LMNWABASICCOMP06P_1.SCA or higher patch level.

  • Problem Create System Object in the Portal for connecting CRM abap

    Hi, i creating system in the portal (JCX) for connecting system ABAP CRM (CRX), after create system try run test connection and show messages error:
    Test Connection with Connector
      Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the backend application using the connector defined in this system object
      Results
    Retrieval of default alias successful
    Connection failed. Make sure that Single Sign-On is configured correctly
    In the logs the portal (NWA) show messages:
    Failed in creating the JCO Connection.
    The logs operation system (log Security_audit.log)
    Error> occured  >Thu Jun 23 11:34:41,278<RfcException: message: 'mshost' missing  Return code: RFC_INVALID_PARAMETER(19  Return code: RFC_INVALID_PARAMETER(19)    error group: 101 key: FC_ERROR_PROGRAM
         at com.sap.mw.rfc.api.RfcOptions.checkParameters(RfcOptions.java:438)
         at com.sap.mw.rfc.api.RfcApi.RfcOpen(RfcApi.java:688)
         at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1079)
         at com.sap.mw.jco.JCO$Client.connect(JCO.java:3256)
    Plase help, any idea?

    message: 'mshost' missing Return
    During the System Object Creating in System Landscape, there is any entry as Message Server Host: CRM MS HOST
    and Message Server Port : sapmsSID and add this entry in etc/services --> bottom samsSID 36NN/tcp where NN is instance number.
    Try this and let me know.
    Thanks
    SM

  • 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

  • Java.lang.NullPointerException  in GP roles

    Hello SDN,
    I have assigned GP roles to user. But when i logon to that perticular user, follwing exception is thrown for all GP roles(Runtime, Design time, Administration and personal templates).
      java.lang.NullPointerException
        at com.sap.caf.eu.gp.ui.comp.ctxpan.VContextualPanel.wdDoInit(VContextualPanel.java:160)
        at com.sap.caf.eu.gp.ui.comp.ctxpan.wdp.InternalVContextualPanel.wdDoInit(InternalVContextualPanel.java:177)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
        at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
        at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
    following is error log in /nwa
    Full Message Text
    Object not found in lookup of GPService.
    com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of GPService.
    at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)
    at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
    at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
    at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at javax.naming.InitialContext.lookup(InitialContext.java:347)
    at com.sap.caf.eu.gp.ui.comp.ctxpan.VContextualPanel.wdDoInit(VContextualPanel.java:155)
    at com.sap.caf.eu.gp.ui.comp.ctxpan.wdp.InternalVContextualPanel.wdDoInit(InternalVContextualPanel.java:177)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
    at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
    at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
    at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.onComponentCreated(ViewManager.java:258)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.fireComponentCreated(ComponentUsage.java:575)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:175)
    at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:116)
    at com.sap.caf.eu.gp.ui.rtwc.VWorkCenterRunTime.wdDoModifyView(VWorkCenterRunTime.java:185)
    at com.sap.caf.eu.gp.ui.rtwc.wdp.InternalVWorkCenterRunTime.wdDoModifyView(InternalVWorkCenterRunTime.java:615)
    at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doModifyView(DelegatingView.java:78)
    at com.sap.tc.webdynpro.progmodel.view.View.modifyView(View.java:337)
    at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doModifyView(ClientComponent.java:481)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doModifyView(WindowPhaseModel.java:551)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:148)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:333)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
    at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
    at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
    at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
    at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    please provide me solution.
    regards,
    Sree.
    Edited by: sree pedasingh on Apr 28, 2011 7:51 AM

    Hi Experts,
    Please provide solution. What could be the issue.
    regards,
    Sree.

  • Duplicate SOAP Adapter metadata

    we are using PI 7.11 and would like to know whether it is possible\supported to create a copy of the standard SOAP Adapter metadata in the Integration Builder. We would copy it to a different SWC, namespace and name (e.g. Customer_Basis_SWC, http://customer.com....,CustomerSOAP). The requirement behind this is as follows.
    An interface exist between PI and a thrid-party application that causes a large number of timeouts when sending async. SOAP messages to this application. The third-party application can not handle the workload caused by the large number of messages pushed through by SAP PI. The third-party application can not be optimized at this point. We believe the only way around this problem is reducing the number of receiver threads in the SOAP adapter. However by changing the threads on the standard SOAP adapter all other receiver adapters of type SOAP are impacted too. Having a customer\application specific SOAP adapter would probably resolve this issue. We also looked at message prioritization but this wouldn't help in this case either.
    If this approach is possible what steps are involved other than copying the metadata to a different SWC, Name and Namespace. We did try this in our sandpit and got an error in the communication channel monitor saying "No adapter registered for this channel", even so the interface we tested with appeared to work using the new adapter. We did not modify the metadata after it was copied into the new SWC. Is there any other configuration step required to get rid of this error message.
    Any help would be greatly appreciated.
    Dieter

    Please check below SAP help on loading metadata.
    http://help.sap.com/saphelp_nw73/helpdata/en/65/6f64403899970ae10000000a155106/frameset.htm

  • 4 System Landscape // ChaRM // No Export System found

    Hi Folks,
    I got some problems with a 4 system landscape in ChaRM.
    The error message I get when doing a consistency check within my SMI project is:
    Message from function module /TMWFLOW/CHECK_PRJ_CONS: No export system for NWA-303
    Message no. /TMWFLOW/TRACK_N159
    Transport route should be as follows:
    DEV -> QAS -> INT -> PRD
    Since I am still in testing phase I used clients instead of real systems in my configuration (TMS, Logical component,....)
    My configuration looks like this:
    NWA client 300 -> 301, transport layer ZCHM, transport layer SAP, consolidation
    NWA client 301 -> 302, delivery
    NWA client 302 -> 303, delivery
    Logical Component defined as follows:
    Developement System (Source: SAP): NWA:300
    Type of Role: D Source System
    Quality Assurance System (Source: SAP): NWA:301
    Type of Role:  O Target System
    Integration System (Source: User): NWA:302
    Type of Role:  O Target System
    Production System (Source: SAP): NWA:303
    Type of Role:  P Production System
    Anyone got an idea what is wrong? did I miss anything?
    The same configuration works for a 3-tier Landscape (without Integration System).
    Any help is appreciated.
    Thanks.

    Hi Raquel,
    Ours problems with RFC and with connections had be corrected with the note below:
    1833778 - Activate Change Request management - Check error
    Thank you very much!!
    Adriana

Maybe you are looking for