Webserviec : XI 3.0 to PI7.1

Hi,
We are in the process of migration from XI 3.0 to PI 7.1. We had a few webservice scanarios in XI 3.0 where the urls for thes interfaces to be used by partner application to call XI were generate using the ID -> Tools -> Define Web Service.
We are not able to find this option in the PI 7.1 environment. NAy information how we can generate the url in PI 7.1 that can be used by our partner to call this interface in PI 7.1.
Regards,
Arunava

Help suggests to use
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
But, the suggested end point to call PI 7.1 is ...
http://host:port /XISOAPAdapter/MessageServlet?senderParty=& senderService=<Send_BS>&interface=<Sender_interface>&receiverParty=&receiverService=<Recv_BS>&interfaceNamespace=<Interface_NS>
Refer to SAP note : 856597 for more details.
Regards,
Venkat.

Similar Messages

What is the difference between SAP NW PI7.1 and PI7.1 EHP1

We have a customer using SAP PI7.1 EHP1. The application to be deployed
isdeveloped on SAP Netweaver PI 7.1 SP06.
We need to know if application developed and transported from PI7.1 is
compatible with EHP1?
Below are the Components used by the application .
1) SSL communication using SOAP adapter
2) Java mapping , Graphical mapping , XSLT mapping
3) Customised EJB modules
4) Adapter framework
5) ALE layer for IDoc communication from ERP to PI
6) RFC lookups to PI system and ERP system.
Questions
1)Will PI EHP1 be able to communicate with PI7.1 using SOAP adapter ?
2) What is the difference between SAP NW PI7.1 and PI7.1 EHP1 ?
Regards,
Sneha

Hi,
EHP Pi7.1 new
IPv6 Support in SAP Systems (new)
Async/Sync and Sync/Async Bridge in the JMS Adapter (New)
High Availability (New) Locate the document in its SAP Library structure
Use
A new concept is available for setting up a high availability environment for SAP NetWeaver Process Integration (PI). To do this, you need SAP Web Dispatcher for load balancing, and you must reconfigure your HTTP, RFC, and RMI connections so that they can be used for load balancing. You must also make various configuration steps in other components of your PI environment.
[Level 4: Document: XML to Text Conversion Module (New)] XML to Text Conversion Module (New)
Message Packaging (New)
Monitoring Milestones (New) Locate the document in its SAP Library structure
Use
You can use the new scenario variant Monitoring Milestones of the Business Process Management scenario to define a monitoring process that can monitor events from different applications. A monitoring process can subscribe to events from SAP or non-SAP systems.
check given Link
http://help.sap.com/saphelp_nwpi711/helpdata/en/61/8c3842bb58f83ae10000000a1550b0/frameset.htm
Regards,
Amit

Interface determination Issue in PI7.1

Hi ,
I am working on PI 7.1
Problem 1:
I am not able create any interface determination objects. There is a lock object created everytime I use the wizard. Unlocking the object and run the cache refresh has not helped..
I am able to create the interface determination manually after removing the lock. But now I am not able to associate a operation/interface mapping to the Interface determination . After I selected a message/service interface in the Interface determination, I clicked on the mapping option. The possible mapping was showed up on the list. But once I select one option from the list it does not show up in the interface determination. The field remains blank.
Problem 2:
I am unable to open the existing interface determination also. These interface determinations are present in the DEV environment.I have taken the system copy of the dev environment on the UAT environment.I am getting the below error when i try to open the interface determination
====================================================================
= Root Exception ===================================================
====================================================================
Thrown:
com.sap.aii.utilxi.swing.toolkit.ServerCallCancelledException: Unexpected exception.
     at com.sap.aii.ib.clsif.gen.BeanAccessHandler.handleRuntimeExInBusinessMethod(BeanAccessHandler.java:87)
     at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:112)
     at com.sap.aii.ib.client.oa.ObjectHandler.read(ObjectHandler.java:119)
     at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.load(DefaultPersistenceHandler.java:94)
     at com.sap.aii.ib.gui.editor.XiDocument.load(XiDocument.java:249)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.load(OpenCommand.java:353)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.localOpen(OpenCommand.java:273)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.execute(OpenCommand.java:211)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
     at com.sap.aii.ib.gui.operations.OperationsServiceProvider.executeDefaultOperation(OperationsServiceProvider.java:295)
     at com.sap.aii.ib.gui.nav.HierarchyNode.executeDefaultOperation(HierarchyNode.java:59)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.DefaultTreeCard.handleHierarchyEvent(DefaultTreeCard.java:198)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.fireHierarchyActionEvent(ThreadedTree.java:542)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.executeStandardOperation(ThreadedTree.java:2264)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree$DblClickHandler.mouseReleased(ThreadedTree.java:2196)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.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 com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
     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)
====================================================================
== Content from the LogHandler =====================================
====================================================================
#300 11:56:48 [AWT-EventQueue-2] WARNING com.sap.aii.utilxi.swing.toolkit.ButtonPanel: Special button of type 4 was not added in order (class com.sap.aii.utilxi.swing.toolkit.ButtonPanel)
#299 11:56:48 [AWT-EventQueue-2] ERROR com.sap.aii.utilxi.swing.toolkit.ExceptionDialog: Throwable
Thrown:
com.sap.aii.utilxi.swing.toolkit.ServerCallCancelledException: Unexpected exception.
     at com.sap.aii.ib.clsif.gen.BeanAccessHandler.handleRuntimeExInBusinessMethod(BeanAccessHandler.java:87)
     at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:112)
     at com.sap.aii.ib.client.oa.ObjectHandler.read(ObjectHandler.java:119)
     at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.load(DefaultPersistenceHandler.java:94)
     at com.sap.aii.ib.gui.editor.XiDocument.load(XiDocument.java:249)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.load(OpenCommand.java:353)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.localOpen(OpenCommand.java:273)
     at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.execute(OpenCommand.java:211)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
     at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
     at com.sap.aii.ib.gui.operations.OperationsServiceProvider.executeDefaultOperation(OperationsServiceProvider.java:295)
     at com.sap.aii.ib.gui.nav.HierarchyNode.executeDefaultOperation(HierarchyNode.java:59)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.DefaultTreeCard.handleHierarchyEvent(DefaultTreeCard.java:198)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.fireHierarchyActionEvent(ThreadedTree.java:542)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.executeStandardOperation(ThreadedTree.java:2264)
     at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree$DblClickHandler.mouseReleased(ThreadedTree.java:2196)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
     at java.awt.Component.processMouseEvent(Unknown Source)
     at javax.swing.JComponent.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 com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
     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)

Hi Shilpa,
Ask your basis guys to check the SP level of JAVA components in system component information of your PI7.1 system............ask them to check for patches for your SP level of PI7.1 or upgrade to a higer SP level...........
Also try this from your PI IB webpage, go to Administration - JAVA web start administration - then click on execute link in the status window and do a reinitialization of your JAVA web start...........then close your ID and reopen your ID........then create your interface determination again in ID...........
Regards,
Rajeev Gupta
Edited by: RAJEEV GUPTA on Apr 29, 2009 9:05 AM
Edited by: RAJEEV GUPTA on Apr 29, 2009 9:25 AM

Error while testing SAML service in PI7.1

Hello all,
I am creating a SAML secured service in PI 7.1
I have used WS adapter in sender communication channel and reciever as RFC adapter to extract data from the system.
I have done the necessary config in sender and receiver agreement and created the wsdl manually.
Now to test that service i have created another component as the client.
The sender is the SOAP channel and in the receiver, WS adapter is used.
With these basic configurations, i have created another wsdl file which invokes my previous service.
When i tested the new wsdl i get an error.
<SAP:Code area="INTERNAL">WS_LOGICAL_PORT</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while determining logical port Cannot find logical port for agreement 34CBAC01EBEC3F15813332AC002BD3CF and interface http://atl.tarpon.com/SAPGetAddressSAML_C.MI_Inbound_SAPGetAddSAML_C</SAP:Stack>
Kindly guide me as to what is to be done for creation of logical port in *NWA as this tool is available for PI7.1 for me.
Regards,
Kevin

Hi Kevin,
What I meant to say is that there are multiple levels of settings required to enable SAML based communication. I wanted to ask you if you have already done those configurations.
See the image given at following URL.
http://help.sap.com/saphelp_nwpi71/helpdata/en/94/695b3ebd564644e10000000a114084/content.htm
As you can see there is multiple parties involved in the overall SAML authentication process.
May be following blog will be helpful.
SAML Made Simple!
Regards,
Vandana.

Does anyone know how to customize a adapter (PI7.1)(not adapter module)

Dear PI experts:
i want to develop a adapter to fulfill the user' requirements,my pi version is pi7.1,and had download the sample adapter code,it's a zip file which contents some java class. and i now i have a double about developing the adapter:
1.which project type do i create for the adapter,is general java project or EJB project?
2.in the adapter project , where can i coding.
3.i don't kown what i must implement int the adapter project ,for example there may be some configuration.
do anyone had developed own adapter,could you tell me how to develop a adapter.
thaks very mutch!

Hi Kevin,
Adapter development for both PI7.0 and PI7.1 has limited resources.
You must have come across this SAP Documentation from help.sap.com:
[Adapter and Module Devlopment|http://help.sap.com/saphelp_nwpi71/helpdata/EN/8b/895e407aa4c44ce10000000a1550b0/content.htm]
This is a complete reference for understanding the Adapter framework.
Download the example Adapter from the mentioned links on the above page and try understanding and relating the java objects with the adapter frameworj and JCA.
You surely need a Java Project for the Adpater development.
You'll need to write a build file to compile it into a rar file and then toa deployable SDA. Thats the way with the example adapter.
Regards,
Alka.

Regarding creation of service interface in PI7.0

Hi friends,
If i try to create a service interface in PI7.10 it shhows error like
<b>You cannot create new objects in component CCBPM, 1.0 of sap.com because no original language is defined for the components</b>
how can i solve this issue,plz help me out regarding this.
Thanks & Regards,
saran
Message was edited by:
Srinivasa D Rao

Hi...
Tools------> Personal settings.
Set the logon and original language to English and try...
I hope it will work...
Regards
San
Remember to set the thread to solved when you have received a solution there is a Way.

What are the major differecese between PI7.0 and PI7.1

It's said that there are 3 major differences between PI7.0 and PI7.1.
Could you give them here because I cannot find them.
Thanks!

Hey,
Some more info,
Process Automation Enterprise Services Repository as a central storage location for enterprise service definitions and lifecycle management data for all enterprise services
Enhanced Design Capabilities
Service Enabling & Services Registry u2013UDDI V3.0 Additional compliant services registry for runtime management of enterprise services
Web Service Standards,Web Service Reliable Messaging, Web Service Policy & Security
High Volume Support & Local processing in Adapter Engine ,Message packaging
Improved performance for ccBPM /BPM
using the Advanced Adapter Engine (AAE) in SAP NetWeaver PI 7.1, much higher numbers of messages can be reached.Even better results can be achieved for asynchronous scenarios
PI 7.10 are the services based on service interfaces. These services can be configured with the help of the SOA Manager
Cheers
Agasthuri

IDOC settings from sap r/3 to sap pi7.3

Hi Guru,
actual problem when i am triggering the idoc from ERP,it is trigeering to the abap stack in sap pi.but i am using idoc_aae adapter at sender side,the message is flowing from sap ERP to file but the message is seen in sxmb_moni,but actually it is not seen in moni .
Please if any one have the idoc setting from sap erp to sap pi7.3. and iam using ICO configuration.
Please help me
Regards
Reddy

Hi,
Please go through the below link :
http://wiki.sdn.sap.com/wiki/display/XI/ALE-Idocconfiguration-+%28R3XIFile%29
Also in your software component version please check whether import of IDocs and RFCs are allowed
from your respective ECC system, and check the ECC system parameters are correctlt maintained or not.
Try out once.

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

Issue in XSLT mappings in PI7.1

Dear all,
Problem Desc:
We have a scenario in PI 7.0 with XSLT mapping. It was working fine there. But when it was transported to PI 7.1, we are facing issues.
The issue is that, XSLT mapping with Java Enhancements is not working when we uncheck the SAP XML Toolkit option, in Operation Mapping.
The error statement says" The XSLT stylesheet could not be compiled".
Please note that, the Java Class being used in the XSLT mapping has been compiled with JAVA 1.5
Did any one encounter a similar error, If yes, please share your responses and help us in resolving the issue.
Regards,
Younus

The issue is that, XSLT mapping with Java Enhancements is not working when we uncheck the SAP XML Toolkit option, in Operation Mapping
Since the XSLT was working for PI7.0 and not working for PI7.1 you need to use SAP XML Toolkit option in your Operation Mapping.....not using this option results in faster execution of the XSLT mapping but then your XSLT mapping should be changed accordingly to work with JDK 5 if you intend not to use the toolkit option....for more information refer this help section:
http://help.sap.com/saphelp_nwpi71/helpdata/EN/73/f61eea1741453eb8f794e150067930/content.htm
Regards,
Abhishek.

ABAP Proxy without SOAP adapter in PI7.3

Hi All,
We have dual stack implementation of PI7.3 but we do not wish to use the SOAP adapter for configuring an ABAP proxy scenario.
Is this possible? Is the Javastack only configuration in NW Admin available for use in dual stack implementation also?
Thanks and Regards,
Diptee

Hi All,
So it essetially means that only the below 2 options are available for ABAP proxy scenarios in PI7.3 for a ABAP+Javastack installation
- use of SOAP adapter over XI protocol
- use of conventional proxy configuration of the ABAP Integration Server
And the only Javastack config cannot be used for a dual stack implementation.
Please confirm if above is correct.
Regards,
Diptee
Edited by: diptee s on Sep 21, 2011 4:48 PM

JCO_COMMUNICATION_FAILURE error in PI7.0

Hello
Till date we have been working with SAP XI 3.0 from last one year, and I have to work with PI 7.0. I creatd a sample scenarion "File to File"in PI 7.0. The sender adapter is picked the file. in SXMB_MONI Error ID showing JCO_COMMUNICATION_FAILURE. Plz suggest me how to resolve this problem.
Thanks
san

Hello San,
Your AI RUNTIME JCOSERVER and AI DIRECTORY JCOSERVER (names - not exact I think) should exist at SM59 of your ABAP stack as well as under JCORFC PRovider in Visual Admin.
Go to the Post isntall steps of XI 3 Install guide (most of the steps are relevant for PI7 also) (page 31 onwards) and you will have all the necessary details. There should be two more RFC destinations SAPSLDAPI adn LCRSAPRFC alongwith the above two.
However the other two are for communicating with SLD mainly.
Hope this helps.
Thanks,
Bhaskar

No payload in message monitoring of PI7.3

Hi experts,
i am doing webservice -PI-webservice synchronous scenario.i am testing thru WS navigator.i am getting response xml also corretly.but problem is message monitoring.i am unable to see payload for both sender and reciever .it is giving no payload.
i dont know..any option for viewing payload.i did nt check any thing in sender communication channel (soap).need help on this.
how to check the payload for soap to soap in monitoring (only java stack of PI7.3) .

Hi
have done some R&D on help.sap.com ..came to know user need some roles for to view payload ..
http://help.sap.com/saphelp_nw73/helpdata/en/48/b2dfee6b156ff4e10000000a42189b/frameset.htm
Thanks,
Allamudi Loordh.

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

Idoc flatfile to IDOC xml issue with new PI7.11 module SAP_XI_IDOC/IDOCFlat

Hi,
I am trying to develop a scenario as mentioned in the blog using the new module available in PI7.1,but I am getting this error
"Error: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ORDERS05" is unavailable."
I have made every configuration correct and IDOC meta data available in both SAP R3 and PI,but it is still complaning about the meta data does not exist.
Blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13743%3Fpage%3Dlast%26x-order%3Ddate
did anybody face issue with the new module available "SAP_XI_IDOC/IDOCFlatToXmlConvertor",please help me or give me mre information why I am getting this meta data error.
Thank you,
Sri

Hi Sri,
To Convert IDOC Flat file into IDOC xml from the given blog, the IDOC flat file should be present in standard format like:
E2EDK01005                    0000047110815000000000001.........
E2EDKA1003                    0000047110815000000000002.........
E2EDKA1003                    0000047110815000000000003..........
E2EDKA1003                    0000047110815000000000004........
The Flat file have relationship as IDOC Number "000004711081500000" and segment sequence "0000001".
If your flat file is not in this formate so i don't think that module is able to convert into IDOC xml. and if your file is already in this format then it may be issue with destinations which are created in NWA.
Thanks
Harish

Webserviec : XI 3.0 to PI7.1

Similar Messages

Maybe you are looking for