Hello All,
I have to perform the Homogeneous Migration -System Copy of PO System. Can you please help in steps to be followed for it as post activities and pre activities that needed to be performed .
I will be preparing the new PO system in target host from the export of Source System.
Thanks & Regards
Saurabh
Hi,
is it possible to have the Operation field in "Operation Determination" tab of sender Rest adapter be a dynamic value.
I want to have a parameter in the url determine which XI operation to call.
Thank you.
Hello,
Can we concat a value for an attribute in XML target element
eg; <effectiveTime xsi:type="TS" value="20131108">.
I Do not want to use XSLT or Java module to do this is there any simple way?
THanks
jake
Hello,
I need to build an EJB module in PO to compress a target file and Send the file in .tar.gz format please let me know if anybody has written this module to do the compression.
Hello All
In my Interface receiver side is JDBC.
My Receiver Structure is as below:
I wanted to DELETE particular rows from Oracle database first and then INSERT some rows.
In Statement1 --> row --> action : I have written query DELETE FROM ABC WHERE NAME <> 'XYZ'
In Statement2 --> row --> action : I have written INSERT
Kindly help me if DELETE query can be written with where clause in message mapping.
I am getting error "Unsupported action attribute value 'DELETE FROM ABC WHERE NAME <> 'XYZ' found in XML document"
Kindly help
Regards
Dheeraj Kumar
Hi ,
For grouping systems in PO QA SLD system I need to create integration engine java buss. system in PO QA sld, I used RZ70 tran. for abap system definition but how can I define INTEGRATION_ENGINE_JAVA dev bus. and tech. system on PO QA system.
B.R.
Hi Experts,
Is it possible to implemant BPM on single stack PO 7.4 version?
we are working PO 7.4 single stack as part in that we are migrating the BPM interfaces into as PO normal insterfaces.
The ccBPM IP_GoodsIssue2 is started by the IDOC. The IDOC is mapped to a TDXML file which can be received by Hades.
The BPM tries to send the TDXML 2 times to Hades, if the message cannot be delivered because of an HTTP error to Hades. If it fails a ZALEAUD is created and sent to SAP.
When the BPM has received response from Hades it first send the message to eCenter.
Then it maps the response from TDXML to a format which can be used to mapping in XI. Then it maps to a ZALEAUD to update the status back in the SAP system.
Please help me how to acieve this.
Regards,
Uday.
Hi all,
We are currently in the planning phase of a SAP PO Test System.
PO system with oracle database on virtualized Linux System.
Do let me know if we can use database as Oracle Exadata 11.2.0.4 for PO system? Somewhere I heard that PO system doesn’t support Exadata?
Many thanks in advance.
Regards,
Sitlesh Patle
Hello All,
I have to go with new installation of PO, with backend being ECC 6.0 EHP 4 system. PO system will be having at least 10 integration points. Please guide on it.
I had a scenario SOAP -> PO 7.40 -> HTTP_AAE ，And Dynamic URL parameters。
My UDF：
UDF |
|---|
DynamicConfiguration conf = (DynamicConfiguration)container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION); DynamicConfigurationKey URLParam_uid = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/HTTP_AAE", "URLParamOne"); DynamicConfigurationKey URLParam_pwd = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/HTTP_AAE", "URLParamTwo"); DynamicConfigurationKey URLParam_mobile = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/HTTP_AAE", "URLParamThree"); DynamicConfigurationKey URLParam_srcphone = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/HTTP_AAE", "URLParamFour"); DynamicConfigurationKey URLParam_msg = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/HTTP_AAE", "URLParamFive");
conf.put(URLParam_uid, uid );
conf.put(URLParam_pwd, pwd);
conf.put(URLParam_mobile, mobile);
conf.put(URLParam_srcphone, srcphone);
conf.put(URLParam_msg, msg);
return uid; |
when I tested it， NullPointerException occurred like this：
| NullPointerException |
|---|
Exception occured during processing /ns0:MT_YH0093_BST_RES/uid Exception:[java.lang.NullPointerException: while trying to invoke the method com.sap.aii.mapping.api.DynamicConfiguration.put(com.sap.aii.mapping.api.DynamicConfigurationKey, java.lang.String) of a null object loaded from a local variable at slot 7] in class com.sap.xi.tf._MM_YH0093_BST_ method calculate[1, 2, 3, 4, 5, com.sap.aii.mappingtool.tf7.rt.Context@3ea227ea] com.sap.aii.utilxi.misc.api.BaseRuntimeException: Exception:[java.lang.NullPointerException: while trying to invoke the method com.sap.aii.mapping.api.DynamicConfiguration.put(com.sap.aii.mapping.api.DynamicConfigurationKey, java.lang.String) of a null object loaded from a local variable at slot 7] in class com.sap.xi.tf._MM_YH0093_BST_ method calculate[1, 2, 3, 4, 5, com.sap.aii.mappingtool.tf7.rt.Context@3ea227ea] at com.sap.aii.mappingtool.tf7.rt.MethodImplementedIteratorHelper.executeMethod(MethodImplementedIteratorHelper.java:188) |
Somebody could help me to solve this problem？
Thank you
Hi All,
I have an REST<–> PI <–> RFC scenario with a PI 7.4 system. We had a requirement for Exposing the Function module as RESTful service. In that I am using Synchronous Sender Rest Adapter where I want to give 2 Runtime parameters
(TOKEN, INPUTREQUEST) as input in the URL and the same should pass to RFC and get the response back.
The sample Request URL will be like:
http://Host:Port/RESTAdapter/Demo/PO?TOKEN=12345&XMLREQUEST=<?xml version="1.0" encoding="UTF-8" ?>
<Z_Request>
<REGION>ASIA</REGION>
<SOURCE_SYSTEM>PRO</SOURCE_SYSTEM>
<item>
<KOKRS>1000</KOKRS>
<BUKRS>100</BUKRS>
</item>
</Z_Request>
Here is the UDF for getting the inputs from the URL:
Map<String, Object> all = container.getInputHeader().getAll();
DynamicConfiguration dynConf = (DynamicConfiguration)all.get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key = DynamicConfigurationKey.create( namespace, attribute);
String xml = dynConf.get(key);
return xml;
When we place the URL in Rest Client tool, SAP PI takes the two parameters through GET variable but the value of XMLREQUEST is getting truncated as "<?xml version". We are not able to get the complete xml from "XMLREQUEST" and
pass as an input to RFC.
Kindly suggest some ideas/solutions for this issue.
Many Thanks,
Ezhil.
Dear Experts,
I have a non technical issue. Need your guidance.
We have implemented a non SAP tool. Recently a requirement came up to integrate it with SAP. But we did not budgeted for PI in this year plan.
The requirement is to integrate it non-real time ( may be 10 mins lag accepted)
Under this circumstance can anybody suggest if there exist any licensing restriction from SAP to integrate through webservices without PI for the time being till we implement PI. Anybody has any experience?
Your expertise will be highly appreciated.
Regards,
Hello,
We are currently migrating our old PI 7.11 dual-stack system to a 7.4 single-stack system. For the moment, I migrated my first scenario by creating my first iflow in NWDS. This is an iDoc to HTTP communication, the destination is configured with a party (scheme ALE#LI#BA). After deploying and transporting to our quality system, the interface doesn't work unfortunately. The error I'm getting in sm58 is:
Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.ad
The log shows this error:
[JRA] serverExceptionOccurred. Server XI_IDOC_<RFC>, Managed_Application_Thread_46,
connectionId=3-poq|sapgw01|XI_IDOC_<RFC>, Exception: com.sap.conn.jco.JCoException: (104)
JCO_ERROR_SYSTEM_FAILURE: Commit fault: ASJ.ejb.005043 (Failed in component:
sap.com/com.sap.aii.adapter.idoc.app, BC-XI-CON-IDO) Exception raised from invocation of
public void com.sap.aii.af.idoc.inbound.IDocReceiverBean.onCommit(java.lang.String) method
on bean instance com.sap.aii.af.idoc.inbound.IDocReceiverBean@266b933c for bean
sap.com/com.sap.aii.adapter.idoc.app*xml|com.sap.aii.adapter.idoc.ejb.jar*xml|IDocReceiverBean
in application sap.com/com.sap.aii.adapter.idoc.app.; nested exception is:
com.sap.conn.idoc.IDocRuntimeException: Error while send to module processor
(raised by system ...)
I already found quite some resources about similar issues but these haven't worked for me. What I already tried/checked:
- manually checked the generated ICO
- tested the sender and receiver communication channels - both OK
- reloaded the iDoc metadata
- checked if the sent iDoc of R/3 is the same as the source iDoc configured in the ICO
- Checked the adapter-specific settings of the source Business system
- according to this thread https://scn.sap.com/thread/3743245, I should change the JavaIdocAdapter resource:
Persistance = true (this was already the case)
AutoNumberFromDB = true (this was configured in our system as false, I changed it to true and retested but the error persisted. Afterwards changed it back to false)
- checked if the SNDPRN node of the iDoc is filled in correctly
The most usefull threads/blogs I checked:
- http://saphelp.me/commit-fault-asj-ejb-005043/
- https://scn.sap.com/docs/DOC-31398
- https://scn.sap.com/thread/3638892
- https://scn.sap.com/thread/3743245
- https://scn.sap.com/thread/2078780
- https://scn.sap.com/thread/3368682
Also found some notes, but I don't think the apply to the problem we're experiencing:
- 1952406 No Service configured for key
- 1872390 Handling invalid XML characters
- 1938302 java.lang.NullPointerException: Name is null
Any help will be greatly appreciated! I've spend quite some time investigating, but for the moment I'm all out of ideas.
Best regards,
Maarten
Hi Experts,
Can any one share some inputs how can we work on idoc sync scenario in PO with out BPM.?
Regards,
Uday.
Dear All,
Greetings of the day.
We have an SAP to Webservice async scenario, through the NW BPM.
We are facing an issue in sending the trigger message (interface to BPM is XI 3.0 compatible) from SAP to the NW BPM. We are getting the following error.
Message could not be processed.Reason: com.sap.aii.proxy.xiruntime.core.ESPXISystemFaultException: Error encountered during processing of XI request message in inbound ESP; Hint: com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException: Technical difficulties were experienced during process execution.
We are getting this the error when I am testing the functionality through WSNavigator or SOAP UI. (In actual scenario ABAP proxy will send the message to NW BPM).
I have tried testing the BPM from the Netweaver Admin and process is going into BPM. I can see the Interface which will be triggered first in the BPM, in the message monitoring.
Request your expertise in overcoming the error for triggering the BPM.
Thank you,
Best Regards,
Ajay
Hi Experts,
I have deployed below process instance with start event having message trigger - synchronous service interface.
While testing from soapUI it gives error like:
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<jpr:Fault xmlns:jpr="http://com.sap/aii/proxy/xiruntime/">com.sap.aii.proxy.xiruntime.core.ESPXISystemFaultException: Error encountered during processing of XI request message in inbound ESP; Hint: com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException: Technical difficulties were experienced during process execution.</jpr:Fault>
</detail>
</SOAP:Fault>
I already searched SDN on the above error, but no clue.
So I am pasting complete logs from NWA:
process()
[EXCEPTION]
com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException: Technical difficulties were experienced during process execution.
at com.sap.glx.adapter.app.ucon.UnifiedConnectivityAdapter.invokeProvisionedMethod(UnifiedConnectivityAdapter.java:1021)
at com.sap.glx.adapter.app.ucon.wsprov.GalaxyImplementationContainer.invokeMethod(GalaxyImplementationContainer.java:109)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:710)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:662)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:322)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:245)
at com.sap.engine.services.webservices.espbase.xi.impl.ESPXIMessageProcessorImpl.process(ESPXIMessageProcessorImpl.java:38)
at com.sap.aii.proxy.xiruntime.core.esp.ESP_XI_MessageAdapter.invokeXI2ESPProcessor(ESP_XI_MessageAdapter.java:430)
at com.sap.aii.proxy.xiruntime.sbeans.esp.xiproxies.SyncInvokeWSInterfaceIn_PortTypeImpl.syncInvokeWSInterfaceIn(SyncInvokeWSInterfaceIn_PortTypeImpl.java:23)
at com.sap.aii.proxy.xiruntime.sbeans.esp.xiproxies.SyncInvokeWSInterfaceIn_PortTypeBean.invokeMethod(SyncInvokeWSInterfaceIn_PortTypeBean.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatefulTransactionAssociation.invoke(Interceptors_StatefulTransactionAssociation.java:45)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatefulSessionInstanceGetter.invoke(Interceptors_StatefulSessionInstanceGetter.java:37)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy3245.invokeMethod(Unknown Source)
at com.sap.aii.proxy.xiruntime.core.XmlProxyJ2EE.parallelWSCall(XmlProxyJ2EE.java:649)
at com.sap.aii.proxy.xiruntime.core.XmlProxyJ2EE.call(XmlProxyJ2EE.java:147)
at com.sap.aii.proxy.xiruntime.core.XmlProxy$ProxyBeanCaller.call(XmlProxy.java:206)
at com.sap.aii.proxy.xiruntime.core.XmlProxy.processRequest(XmlProxy.java:181)
at com.sap.aii.proxy.xiruntime.core.XmlInbound.processRequestMessage(XmlInbound.java:115)
at com.sap.aii.proxy.xiruntime.core.XmlInbound.processMessage(XmlInbound.java:78)
at com.sap.aii.proxy.xiruntime.sbeans.JPRBean.onMessage(JPRBean.java:156)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatefulTransactionAssociation.invoke(Interceptors_StatefulTransactionAssociation.java:45)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatefulSessionInstanceGetter.invoke(Interceptors_StatefulSessionInstanceGetter.java:37)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:37)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:172)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:99)
at com.sun.proxy.$Proxy3271.onMessage(Unknown Source)
at com.sap.engine.messaging.impl.spi.ServicesImpl.deliver(ServicesImpl.java:362)
at com.sap.aii.adapter.xi.ms.XIEventHandler.onDeliver(XIEventHandler.java:1098)
at com.sap.engine.messaging.impl.core.queue.consumer.RequestConsumer.onMessage(RequestConsumer.java:75)
at com.sap.engine.messaging.impl.core.queue.Queue.run(Queue.java:1033)
at com.sap.engine.messaging.runtime.MSWorkWrapper.run(MSWorkWrapper.java:58)
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:185)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:302)
Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Exception during prepare, rolling back
at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:701)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:196)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:77)
at com.sap.glx.adapter.app.ucon.UnifiedConnectivityAdapter.invokeProvisionedMethod(UnifiedConnectivityAdapter.java:987)
... 77 more
Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Exception during prepare, rolling back
at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:701)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:196)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:77)
at com.sap.glx.core.kernel.mmtx.PrimaryTransaction.inPrepare(PrimaryTransaction.java:163)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:194)
... 79 more
Caused by: com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script "_Ariba_Order_request:START_EVENT_UC_Start( com.sap.glx.adapter.UnifiedConnectivityAdapter:Request request, com.sap.glx.adapter.BPMNAdapter:Event_0_Start_5b8dad8a77346e54760570e1d1c8c088 event){ messageId=request:messageId; initiator=request:initiator; kicker=request:kicker; instance=new com.sap.glx.adapter.BPMNAdapter:Instance_0_Ariba_Order_request_5b8dad8a77346e54760570e1d1c8c088(initiator, null, kicker, false, messageId, null); bridge=new com.sap.glx.adapter.internal.Synchronizer:Bridge_0_Ariba_Order_request_5b8dad8a77346e54760570e1d1c8c088(instance, null, null, null, null); bridge:setRequest(request); token=new com.sap.glx.adapter.BPMNAdapter:Token_0_Ariba_Order_request_5b8dad8a77346e54760570e1d1c8c088(instance, 2, null, null, null); delete event; exit=new com.sap.glx.adapter.BPMNAdapter:Exit(); exit:onActivation("E0B249478BB1FD54F78611E3B53000059A3C7A00", instance, token); delete exit; controller=new com.sap.glx.adapter.internal.ExceptionAdapter:ExceptionController(); controller:setContext(token); delete controller; scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_1_Ariba_Order_request_5b8dad8a77346e54760570e1d1c8c088(instance); view_7=new com.sap.glx.adapter.internal.ContainerAdapter:View_2_TextVariables_5b8dad8a77346e54760570e1d1c8c088(instance, scope, -1, false, false, null); instance:setContainerObject("TextVariables", view_7); scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_3_Ariba_Order_request_5b8dad8a77346e54760570e1d1c8c088(instance); role_5=new com.sap.glx.adapter.internal.ContainerAdapter:View_0_Ariba_Order_request_PotentialOwners_5b8dad8a77346e54760570e1d1c8c088(instance, scope, -1, false, false, null); scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_4_Ariba_Order_request_5b8dad8a77346e54760570e1d1c8c088(instance); role_8=new com.sap.glx.adapter.internal.ContainerAdapter:View_3_Ariba_Order_request_ExcludedOwners_5b8dad8a77346e54760570e1d1c8c088(instance, scope, -1, false, false, null); scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_5_Ariba_Order_request_5b8dad8a77346e54760570e1d1c8c088(instance); role_6=new com.sap.glx.adapter.internal.ContainerAdapter:View_1_Administrators_5b8dad8a77346e54760570e1d1c8c088(instance, scope, -1, false, false, null); instance:setContainerObject("Administrators", role_6); scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_6_Ariba_Order_request_5b8dad8a77346e54760570e1d1c8c088(instance); context_2=new com.sap.glx.adapter.internal.ContainerAdapter:Context_1_ProcessInstanceAttributes_5b8dad8a77346e54760570e1d1c8c088(instance, scope, 0, false, false, null); instance:setContainerObject("ProcessInstanceAttributes", context_2); scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_7_Ariba_Order_request_5b8dad8a77346e54760570e1d1c8c088(instance); context_3=new com.sap.glx.adapter.internal.ContainerAdapter:Context_2_respdata_5b8dad8a77346e54760570e1d1c8c088(instance, scope, 0, false, false, null); scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_8_Ariba_Order_request_5b8dad8a77346e54760570e1d1c8c088(instance); context_1=new com.sap.glx.adapter.internal.ContainerAdapter:Context_0_reqdata_5b8dad8a77346e54760570e1d1c8c088(instance, scope, 0, false, false, null); scope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_11_Ariba_Order_request_5b8dad8a77346e54760570e1d1c8c088(instance); context_4=new com.sap.glx.adapter.internal.ContainerAdapter:Context_3_payloadID_5b8dad8a77346e54760570e1d1c8c088(instance, scope, 0, false, false, null); payload=request:getData(); mapper=new com.sap.glx.adapter.internal.Transformer:DataMapper(); yves_in=new com.sap.glx.adapter.internal.Transformer:Data(); yves_in:setData("", "$cXML", payload, "365B925081E9760C6CFC8AAE6A38BE4A"); yves_out=new com.sap.glx.adapter.internal.Transformer:Data(); data=context_1:getData(); scope=new com.sap.glx.adapter.internal.TypeRegistry:GenericScope(null, "B0A4F97FB4313113B63F888AA86D7449"); copy=scope:copy(data); delete scope; yves_out:setData("example.org/orderreq/Ariba_Order_request/Ariba_Order_request", "$example.org/orderreq/Ariba_Order_request/Ariba_Order_request:reqdata", copy, "B0A4F97FB4313113B63F888AA86D7449"); data=context_4:getData(); scope=new com.sap.glx.adapter.internal.TypeRegistry:GenericScope(null, "349213D98BEBBF54C08B2D9F20B3D5C7"); copy=scope:copy(data); delete scope; yves_out:setData("example.org/orderreq/Ariba_Order_request/Ariba_Order_request", "$example.org/orderreq/Ariba_Order_request/Ariba_Order_request:payloadID", copy, "349213D98BEBBF54C08B2D9F20B3D5C7"); mapper:map("E0B249478BB72A80F78611E38B9D00059A3C7A00_5b8dad8a77346e54760570e1d1c8c088", yves_in, yves_out); data=yves_out:getData("example.org/orderreq/Ariba_Order_request/Ariba_Order_request", "$example.org/orderreq/Ariba_Order_request/Ariba_Order_request:reqdata", "B0A4F97FB4313113B63F888AA86D7449"); context_1:setData(data); data=yves_out:getData("example.org/orderreq/Ariba_Order_request/Ariba_Order_request", "$example.org/orderreq/Ariba_Order_request/Ariba_Order_request:payloadID", "349213D98BEBBF54C08B2D9F20B3D5C7"); context_4:setData(data); delete yves_in; delete yves_out; viewUpdater=new com.sap.glx.adapter.internal.ContainerAdapter:ViewUpdater(); delete viewUpdater; delete mapper; extractor=new com.sap.glx.adapter.internal.Transformer:DataExtractor(); yves_in=new com.sap.glx.adapter.internal.Transformer:Data(); data=context_1:getData(); yves_in:setData("example.org/orderreq/Ariba_Order_request/Ariba_Order_request", "$example.org/orderreq/Ariba_Order_request/Ariba_Order_request:reqdata", data, "B0A4F97FB4313113B63F888AA86D7449"); data=context_4:getData(); yves_in:setData("example.org/orderreq/Ariba_Order_request/Ariba_Order_request", "$example.org/orderreq/Ariba_Order_request/Ariba_Order_request:payloadID", data, "349213D98BEBBF54C08B2D9F20B3D5C7"); value1=extractor:extractAs("E0AAACCD28D4CDD4F78711E3840300059A3C7A00_5b8dad8a77346e54760570e1d1c8c088", yves_in, "BOOLEAN"); delete yves_in; delete extractor; subscription=new com.sap.glx.adapter.internal.CorrelationAdapter:Subscription_0_Wait_for_response_message_5b8dad8a77346e54760570e1d1c8c088(instance, value1, null, null); subscription:addModifier(2, context_1); subscription:addModifier(2, context_4); new com.sap.glx.adapter.internal.LoggingAdapter:FlightRecorder_0_Ariba_Order_request_5b8dad8a77346e54760570e1d1c8c088(instance); eventLogger=new com.sap.glx.adapter.internal.EventLogAdapter:EventLogger_0_Ariba_Order_request_5b8dad8a77346e54760570e1d1c8c088(); eventLogger:createEntryWithMessageId(1, "E0B249478AE020FCF78611E3925F00059A3C7A00", instance, "E0B249478BB1FD54F78611E3B53000059A3C7A00", kicker, messageId); delete eventLogger;
}"
at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:83)
at com.sap.glx.core.kernel.execution.transition.Transition.commence(Transition.java:196)
at com.sap.glx.core.kernel.mmtx.DirectNestedTransaction.inPrepare(DirectNestedTransaction.java:69)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:194)
... 82 more
Caused by: com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script command "context_3=new com.sap.glx.adapter.internal.ContainerAdapter:Context_2_respdata_5b8dad8a77346e54760570e1d1c8c088(instance, scope, 0, false, false, null)"
at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:803)
at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:78)
... 85 more
Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException
at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:701)
at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:710)
at com.sap.glx.core.dock.impl.GalaxyClassImpl.create(GalaxyClassImpl.java:234)
at com.sap.glx.core.kernel.trigger.config.Script$NewInstance.execute(Script.java:368)
at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:798)
... 86 more
Caused by: com.sap.glx.core.kernel.api.TransitionException: Cannot find type for :#cXML
at com.sap.glx.core.internaladapter.typeregistry.TypeRegistryImpl.instantiateSDO(TypeRegistryImpl.java:176)
at com.sap.glx.core.internaladapter.typeregistry.TypeRegistryImpl.access$000(TypeRegistryImpl.java:51)
at com.sap.glx.core.internaladapter.typeregistry.TypeRegistryImpl$3.invoke(TypeRegistryImpl.java:372)
at com.sap.glx.core.dock.impl.DockObjectImpl.invokeMethod(DockObjectImpl.java:657)
at com.sap.glx.core.internaladapter.ContainerAdapter$InstanceContainerHandler.onConstruction(ContainerAdapter.java:769)
at com.sap.glx.core.dock.impl.DockObjectImpl.creation(DockObjectImpl.java:284)
at com.sap.glx.core.dock.impl.GalaxyClassImpl.create(GalaxyClassImpl.java:224)
... 88 more
--DivyeshHello All,
I have got requirement from my customer and he asked me do POC on PI.
They might have chance to use direct connection between webfocus and oracledatabase.but that is little costly and need to pay licence cost. so they plans to use PI in middle.
Scenario flow:
1) Intial request comes from Webfocus to PI( on demand request)
2) PI gets retrieve data from Oracle database key as a initial request.
3) PI sends back data to Webfocus.
challenges:
1) how PI connects to Webfocus ? either use SOAP (or) REST- please clarify me on this? FYi webfocus have their own adapters to connect SAP.
2) Oracle database may thousands datasets for one request. But webfocus wants data back to within seconds for ex: max 4 to 5 seconds, how I achieve on performance?
Please suggest your views.
Thank you.
Sateesh
Hi!
I have question about monitoring in BPM.
In this blog Boost your Correlation Scenarios with Conditional Starthttp://scn.sap.com/community/bpm/blog/2013/04/04/conditional-start-monitoring-47 said: "A message sent to the web service endpoint will be attempted to be correlated to a running process. In case the message payload does not satisfy any correlation condition or there is no process running, the system rejects it for correlation....This event is written to the business log of the SAP NetWeaver Administrator, which can be accessed in the SAP NetWeaver Administrator by choosing Troubleshooting > Processes and Tasks > Business Logs".
I create test scenario in AEX and process with Start Condition in NWDS SP07.
If I send a message that does not satisfy Start Condition, then I can't find in Business Logs any log. In AEX (pimon/message monitoring) have successful message. In nwa/logs I can find only this logs: "Java proxy runtime (JPR) accepted the message", "JPR successfully processed the message".
Where I can find more information about discarded messages? How I can understand that my message not started process?
Hello,
I have a PI 7.31 SPS09 System.Now customer want us to upgrade to 7.4 SPS11 (Dual Stack).They don't want a split.Special instructions are really appreciated.
Thanks,
Mofizur
Hello All
I am doing EDIFACT to IDOC Scenario.
I know two flows are involved:
1. AS2/FILE to EDISEPERATOR
2. EDISEPARATOR to IDOC
I am stuck after 1st flow. I am using File adapter in sender.
File adapter is successfully picking up EDI file and sending to receiver EDIADAPTER.
In Message Monitoring when I am checking there is an error:
Die Message konnte nicht über Verbindung File_http://sap.com/xi/XI/System an Endpunkt <local> übertragen werden wegen: com.sap.engine.interfaces.messaging.api.exception.MessagingException: javax.resource.ResourceException: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: received message , but no sender communication channel is configured to receive it
Due to above error sender EDISEPERATOR channel of 2nd flow is not getting any message.
Is there any additional configuration I need to do to co relate both the flows.
Please help.
Regards
Dheeraj Kumar