Are message broker channels persistant

Can you please let me know whether the message broker channels are persistent.
In my application ,a message goes through different JPDs linked via channels.So if the server crash ,theres a chance the message gets lost .How can we prevent this.We dont have any queues configured at present.

This is a WebLogic Server general forum, not WebLogic Integration.
You may want to try the integration forum noting in the subject that it is a WLI question:
Integration - General
Alternatively support should be able to answer you question.

Similar Messages

  • POJOs and posting to a Message Broker Channel

    Hi!
    What we need is to let a JCA Connector publish a message to a Message Broker (MB) Channel. (The messages are subsequentliy picked up by a JPD process.)
    One solution is to let te JCA connector send an JMS message, which is translated to a MB message by a JMSEventGenerator. But we don't want the overhead of JMS.
    Is it possible for a JCA connector to publish a message directly on a MB Channel? Is there some kind of API avaiable for this?
    Thanks in advance :-)
    Anders

    I am having a simialr problem here. I have more then one jpd's(workflows). Now if due to some business logic, one of them is publishing an xml into a Message Broker Queue. This message needs to be subscribed globally(at start node) by other workflows. As per my understanding, this can be done by 'Add Message path'.But i am not able to subscribe to the queue. I have added a control for Subscribing it but the 'add message path' requires a start event and i cannot subscribe using onMessage(data) method of subscribe control as we first need to call the subscribe() method of the control.
    So is there a way by which I can globally publish to a queue and fetch the data(xml) from a queue and do further processing in all the workflows.

  • Transaction Support for message broker channel

    Hi all,
    I have created a JPD and subscribing to an MB channel and listening for messages, suppose the message is delivered to the JPD i.e onMessage is invoked successfully, but at the next node there is an exception thrown, so I want to rollback all the stuff done and also pushback the message to the channel, (and if possible get the message back to the JPD by retrying the entire tranaction).
    1. Can the message be pushed back to the channel?
    2. Will the channel try to send the same message again to the JPD incase we rollback and wait again at onMessage in the same JPD by means of exceptional path (retry count)?
    3. Is the message available for consumption for other subscribers incase we are able to pushback the message to the channel?
    4. Bottomline - How can I include the MB channel(message delivery) within transactional boundary?
    TIA
    Abhishek

    Hi kai/All,
    Thanks for ur response, but I still have some questions.
    1. If the message is not going to be pushed back to the channel, what exactly do we mean by "retry"(is it that I have to resubscribe(and wait at onMessage call in my subscriber jpd) to the channel, and wait for the same message to be pusblished by the publisher JPD)?
    Also my requirement is - I am having number of subscriber(JPD instances say workflow JPDs) to the same channel and using filters to deliver the message to the appropriate workflow JPD instance, So, One and only one instance can listen for a particular message, so incase there is an exception in a particular workflow JPD, no other instance can cover for it beacuse of a particualr filter value for the message subscription. How can I overcome this shortcoming?
    TIA
    Abhishek

  • Can I create a message broker channel CounterMonitor mbean?

    Hi All,
    I'm trying to write an app which sends notifications when certain events occur in our WLI system. I am using mbean notification listeners and countermonitors for most things.
    I would like to setup a notification for the error count and dead letter count for specific channels. The problem is that I can only find a MessageBrokerChannelValue attribute of the MsgBrokerRuntimeMBean, no channel mbean. MsgBrokerRuntimeMBean.MessageBrokerChannelValue describe the channels but I can't figure how attach a CounterMonitor mbean to attributes of these channels.
    Has anyone done this before? I'm trying to avoid setting up a timer which does checks at regular intervals...I'd prefer WLI to do that for me. :)
    Thanks in advance,
    Tony

    Muse doesn't support this feature natively, but you could perhaps embed a message board using HTML or an i-Frame - crude but it would work.

  • Not able to post messages to channel

    Hi,
    I have created a simple application which sends messages to the channel.
    Here is my channel :
    <?xml version="1.0"?>
    <!--
    A sample channel file
    Change "channelPrefix" and <channel/> elements to customize
    The following namespaces are used in this sample file. These
    namespaces refer to schemas that must be present in a schema
    directory.
    - xmlns:eg=http://www.bea.com/wli/eventGenerator" is used
    for event generator metadata references
    - xmlns:dp="http://www.bea.com/wli/control/dynamicProperties" is
    used by the file event generator to pass payload for pass-by-filename
    - xmlns:oagpo="http://www.openapplications.org/003_process_po_007" is
    used for a sample payload description
    -->
    <channels xmlns="http://www.bea.com/wli/broker/channelfile"
    channelPrefix="/test" >
    <channel name ="test" messageType="string">
    <!-- A simple channel passing XML -->
    <!--
    <channel name ="SampleXmlChannel" messageType="xml"/>
    -->
    <!-- A simple channel passing rawData -->
    <!--
    <channel name ="SampleRawDataChannel" messageType="rawData"/>
    -->
    <!-- A simple channel passing a string -->
    <!--
    <channel name ="SampleStringChannel" messageType="string"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in
    the oagpo namespace -->
    <!--
    <channel name ="SampleOAGPOChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"/>
    -->
    <!-- A channel passing rawData, the rawData is mapped by the
    StockQuotes.mfl file in the schema directory -->
    <!--
    <channel name ="SampleRawDataChannel" messageType="rawData"
    qualifiedRawDataMessageType="urn:StockQuotes.mfl"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in the
    oagpo namespace, and the metadata is element FileEventGenerator
    in the eg namespace -->
    <!--
    <channel name ="SampleEGFileChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"
    qualifiedMetadataType="eg:FileEventGenerator"/>
    -->
    <!-- A channel passing XML, the XML is element dp:FileControlProperties
    in the po namespace, and the metadata is element FileEventGenerator
    in the eg namespace
    (this is the XML payload used for pass-by-filename in the
    file event generator) -->
    <!--
    <channel name ="SampleEGFileChannel" messageType="xml"
    qualifiedMessageType="dp:FileControlProperties"
    qualifiedMetadataType="eg:FileEventGenerator"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in the
    oagpo namespace, and the metadata is element JmsEventGenerator
    in the eg namespace -->
    <!--
    <channel name ="SampleEGJmsChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"
    qualifiedMetadataType="eg:JmsEventGenerator"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in the
    oagpo namespace, and the metadata is element EmailEventGenerator
    in the eg namespace -->
    <!--
    <channel name ="SampleEGEmailChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"
    qualifiedMetadataType="eg:EmailEventGenerator"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in the
    oagpo namespace, and the metadata is element TimerEventGenerator
    in the eg namespace -->
    <!--
    <channel name ="SampleEGTimerChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"
    qualifiedMetadataType="eg:TimerEventGenerator"/>
    -->
    </channel>
    </channels>
    Issue is whenever I run my application I get following excpetion , please
    let me know what I am missing . I am running weblogic 8.
    Thanks
    Veresh
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <A message was
    unable to be delivered from a WLW Message Queue. Attempting to deliver the
    onAsyn
    cFailure event>
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <Transaction Rolled
    back in response to exception occurred during async error processing
    javax.ejb.TransactionRolledbackLocalException: Exception in ejbLoad:; nested
    exception is: javax.ejb.EJBException: nested exception is: java.sql.SQLExce
    ption: Lock time out; try later.
    javax.ejb.EJBException: nested exception is: java.sql.SQLException: Lock
    time out; try later.
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handleJDBCObjectResponse(Unknown Source)
    at com.pointbase.net.netJDBCPreparedStatement.executeQuery(Unknown
    Source)
    at
    weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:124)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean$GenericTableAccess.doLoad(BMPContainerBean.java:495)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbLoad(BMPContainerBean.java:1724)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.ejbLoad(ProcessContainerBean.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_Impl.ejbLoad(PersistentContainer_2ktjqj_Impl.java:136)
    at
    weblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityManager.java:324)
    at
    weblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManager.java:246)
    at
    weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:228)
    at
    weblogic.ejb20.internal.EntityEJBLocalObject.preInvoke(EntityEJBLocalObject.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.invoke(PersistentContainer_2ktjqj_ELOImpl.java:190)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:93)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at
    com.bea.wlw.runtime.core.bean.AsyncErrorBean.onMessage(AsyncErrorBean.java:225)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    javax.ejb.EJBException: nested exception is: java.sql.SQLException: Lock
    time out; try later.
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbLoad(BMPContainerBean.java:1776)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.ejbLoad(ProcessContainerBean.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_Impl.ejbLoad(PersistentContainer_2ktjqj_Impl.java:136)
    at
    weblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityManager.java:324)
    at
    weblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManager.java:246)
    at
    weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:228)
    at
    weblogic.ejb20.internal.EntityEJBLocalObject.preInvoke(EntityEJBLocalObject.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.invoke(PersistentContainer_2ktjqj_ELOImpl.java:190)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:93)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at
    com.bea.wlw.runtime.core.bean.AsyncErrorBean.onMessage(AsyncErrorBean.java:225)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    javax.ejb.TransactionRolledbackLocalException: Exception in ejbLoad:; nested
    exception is: javax.ejb.EJBException: nested exception is: java.sql.SQLExce
    ption: Lock time out; try later.
    at
    weblogic.ejb20.internal.EJBRuntimeUtils.throwTransactionRolledbackLocal(EJBRuntimeUtils.java:247)
    at
    weblogic.ejb20.internal.BaseEJBLocalHome.handleSystemException(BaseEJBLocalHome.java:246)
    at
    weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:233)
    at
    weblogic.ejb20.internal.EntityEJBLocalObject.preInvoke(EntityEJBLocalObject.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.invoke(PersistentContainer_2ktjqj_ELOImpl.java:190)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:93)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at
    com.bea.wlw.runtime.core.bean.AsyncErrorBean.onMessage(AsyncErrorBean.java:225)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <A message was
    unable to be delivered from a WLW Message Queue. Attempting to deliver the
    onAsyn
    cFailure event>
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <A message was
    unable to be delivered from a WLW Message Queue. Attempting to deliver the
    onAsyn
    cFailure event>
    <Jun 19, 2005 12:37:25 AM EDT> <Error> <WLI-Core> <BEA-481028> <Failed to
    lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)
    at
    com.bea.wli.broker.JDBCRepository.dispatchDynamicSubscriptions(JDBCRepository.java:1087)
    at
    com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:944)
    at
    com.bea.control.PublishControlImpl.doPublish(PublishControlImpl.jcs:196)
    at
    com.bea.control.PublishControlImpl.invoke(PublishControlImpl.jcs:306)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
    at $Proxy16.publish(Unknown Source)
    at processes.event1.responsePublishPublish(event1.jpd:119)
    at processes.event1_wf$ImplControlSend4.invoke(event1_wf.java:61)
    at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
    at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
    at
    com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
    at
    com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
    at
    processes.event1_wf$_ProcessState.processMessage(event1_wf.java:177)
    at processes.event1_wf.event1Subscribe_onMessage(event1_wf.java:146)
    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:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.core.container.Invocable.fireEvent(Invocable.java:612)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:412)
    at $Proxy17.onMessage(Unknown Source)
    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:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:99)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:319)
    at
    com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.invoke(BMPContainerBean.java:2033)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.invoke(ProcessContainerBean.java:163)
    at
    com.bea.wlwgen.event1BMPContImpl.event1Subscribe$callback(event1BMPContImpl.java:40)
    at
    com.bea.wlwgen.PersistentContainer_4po8lm_ELOImpl.event1Subscribe$callback(PersistentContainer_4po8lm_ELOImpl.java:153)
    at
    com.bea.wlwgen.event1BMPContAdpt.invokeOnBean(event1BMPContAdpt.java:87)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Jun 19, 2005 12:37:25 AM EDT> <Error> <WLI-Core> <BEA-481028> <Failed to
    lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)
    at
    com.bea.wli.broker.JDBCRepository.dispatchDynamicSubscriptions(JDBCRepository.java:1087)
    at
    com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:944)
    at
    com.bea.control.PublishControlImpl.doPublish(PublishControlImpl.jcs:196)
    at
    com.bea.control.PublishControlImpl.invoke(PublishControlImpl.jcs:306)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
    at $Proxy13.publish(Unknown Source)
    at processes.event2.responsePublishEventPublish(event2.jpd:113)
    at processes.event2_wf$ImplControlSend4.invoke(event2_wf.java:61)
    at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
    at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
    at
    com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
    at
    com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
    at
    processes.event2_wf$_ProcessState.processMessage(event2_wf.java:177)
    at processes.event2_wf.event2Subscribe_onMessage(event2_wf.java:157)
    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:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.core.container.Invocable.fireEvent(Invocable.java:612)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:412)
    at $Proxy14.onMessage(Unknown Source)
    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:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:99)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:319)
    at
    com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.invoke(BMPContainerBean.java:2033)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.invoke(ProcessContainerBean.java:163)
    at
    com.bea.wlwgen.event2BMPContImpl.event2Subscribe$callback(event2BMPContImpl.java:40)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.event2Subscribe$callback(PersistentContainer_2ktjqj_ELOImpl.java:45)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:87)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000>
    <Id=responsePublishEvent; Method=processes.responsePublishEvent.publish();
    Failure=weblogic.jws.
    control.ControlException: [WLI-Core:489317]Failed to publish message to the
    Message Broker due to: com.bea.wli.broker.RepositoryException: [WLI-Core:481
    028]Failed to lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)
    at
    com.bea.wli.broker.JDBCRepository.dispatchDynamicSubscriptions(JDBCRepository.java:1087)
    at
    com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:944)
    at
    com.bea.control.PublishControlImpl.doPublish(PublishControlImpl.jcs:196)
    at
    com.bea.control.PublishControlImpl.invoke(PublishControlImpl.jcs:306)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
    at $Proxy13.publish(Unknown Source)
    at processes.event2.responsePublishEventPublish(event2.jpd:113)
    at processes.event2_wf$ImplControlSend4.invoke(event2_wf.java:61)
    at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
    at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
    at
    com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
    at
    com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
    at
    processes.event2_wf$_ProcessState.processMessage(event2_wf.java:177)
    at processes.event2_wf.event2Subscribe_onMessage(event2_wf.java:157)
    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:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.core.container.Invocable.fireEvent(Invocable.java:612)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:412)
    at $Proxy14.onMessage(Unknown Source)
    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:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:99)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:319)
    at
    com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.invoke(BMPContainerBean.java:2033)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.invoke(ProcessContainerBean.java:163)
    at
    com.bea.wlwgen.event2BMPContImpl.event2Subscribe$callback(event2BMPContImpl.java:40)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.event2Subscribe$callback(PersistentContainer_2ktjqj_ELOImpl.java:45)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:87)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    [[WLI-Core:481028]Failed to lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)
    at
    com.bea.wli.broker.JDBCRepository.dispatchDynamicSubscriptions(JDBCRepository.java:1087)
    at
    com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:944)
    at
    com.bea.control.PublishControlImpl.doPublish(PublishControlImpl.jcs:196)
    at
    com.bea.control.PublishControlImpl.invoke(PublishControlImpl.jcs:306)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
    at $Proxy13.publish(Unknown Source)
    at processes.event2.responsePublishEventPublish(event2.jpd:113)
    at processes.event2_wf$ImplControlSend4.invoke(event2_wf.java:61)
    at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
    at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
    at
    com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
    at
    com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
    at
    processes.event2_wf$_ProcessState.processMessage(event2_wf.java:177)
    at processes.event2_wf.event2Subscribe_onMessage(event2_wf.java:157)
    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:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.core.container.Invocable.fireEvent(Invocable.java:612)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:412)
    at $Proxy14.onMessage(Unknown Source)
    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:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:99)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:319)
    at
    com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.invoke(BMPContainerBean.java:2033)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.invoke(ProcessContainerBean.java:163)
    at
    com.bea.wlwgen.event2BMPContImpl.event2Subscribe$callback(event2BMPContImpl.java:40)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.event2Subscribe$callback(PersistentContainer_2ktjqj_ELOImpl.java:45)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:87)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    ]>
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <Id=responsePublish;
    Method=processes.responsePublish.publish(); Failure=weblogic.jws.control.Co
    ntrolException: [WLI-Core:489317]Failed to publish message to the Message
    Broker due to: com.bea.wli.broker.RepositoryException:
    [WLI-Core:481028]Failed
    to lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)
    at
    com.bea.wli.broker.JDBCRepository.dispatchDynamicSubscriptions(JDBCRepository.java:1087)
    at
    com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.jav

    ya I was able to resolve this issue by removing the Pointbase as WLI repository and point to DB2 , as pointbase seems not scalable.
    Also increase the DB pool size .
    Script for creating the schema is inside the WLI.
    Thanks
    Veresh

  • I have a scenario,  ECC-PI-Message broker. ECC sending IDOC to  PI, PI execute mapping and  sending data to Message borker.(with almost one to one mapping)., IDOC(AAE)-PI-JMS. Now my requirement is., from PI  after mapping we need to save file in SAP fold

    I have a scenario,  ECC-PI-Message broker. ECC sending IDOC to  PI, PI execute mapping and  sends data to Message borker(thru JMS channel).(with almost one to one mapping)., IDOC(AAE)-PI-JMS. Now my requirement is., from PI  after mapping we need to create file with same data what ever send to Message broker and put the file in SAP folder without touching mapping. Is it possible? Please advise with the steps. We are using the ICO for this senario. Quick response is appriciated.

    Hi Pratik,
         http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?quicklink=index&overridelayout=true
    This link might help.
    regards
    Anupam

  • Help reqd..Not able to Starting and Testing a Message Broker

    I am new to Sun Java System Message Queue. I have downloaded a trial version of Message Queue 3 2005Q4 (3.6 SP3) Platform Edition from Sun website. I have installed this on RedHat 4.0, Itanium 64 bit server, jrockit-jdk1.5.0_06 j2se. I am referring to Sun Java� System Message Queue 3 Developer�s Guide for Java Clients document, as per this I have setup Message Queue Directory Variables. After environment variables setup, trying to Starting and Testing a Message Broker. Once Run the broker startup command
    "imqbrokerd -tty"
    Getting following errors in terminal:
    Exception in thread "Reference Handler" java.lang.StackOverflowError
    at java.lang.Class.forName(Ljava.lang.String;ZLjava.lang.ClassLoader;)Ljava.lang.Class;(Unknown Source)
    at java.lang.Class.forName(Ljava.lang.String;J)Ljava.lang.Class;(Unknown Source)
    at java.lang.ref.Reference$ReferenceHandler.run()V(Unknown Source)
    Exception in thread "Finalizer" java.lang.StackOverflowError
    at java.lang.Thread.run()V(Unknown Source)
    [23/Feb/2007:06:43:16 PST]
    ================================================================================Sun Java(tm) System Message Queue 3 2005Q4
    Sun Microsystems, Inc.
    Version: 3.6 SP3 (Build 02-A)
    Compile: Wed Jun 22 15:30:03 PDT 2005
    Copyright �� 2005 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    This product includes code licensed from RSA Data Security.
    ================================================================================Java Runtime: 1.5.0_06 BEA Systems, Inc. /PES-Software/jrockit-jdk1.5.0_06/jre
    Exception in thread "JMQTimerThread" java.lang.StackOverflowError
    at com.sun.messaging.jmq.util.timer.TimerThread.run(JMQTimer.java:410)
    [23/Feb/2007:06:43:16 PST] License: Sun Java(tm) System Message Queue 3.6 Platform Edition
    [23/Feb/2007:06:43:16 PST] IMQ_HOME=/opt/sun/mq
    [23/Feb/2007:06:43:16 PST] IMQ_VARHOME=/var/opt/sun/mq
    [23/Feb/2007:06:43:16 PST] Linux 2.6.9-42.EL ia64 rhel4 (8 cpu) root
    [23/Feb/2007:06:43:16 PST] Java Heap Size: max=196608k, current=32768k
    [23/Feb/2007:06:43:16 PST] Arguments: -tty
    [23/Feb/2007:06:43:16 PST] [B1004]: Starting the portmapper service using tcp [ 7676, 50, * ] with min threads 1 and max threads of 1
    java.lang.StackOverflowError
    at java.lang.Thread.run()V(Unknown Source)
    [23/Feb/2007:06:43:16 PST] WARNING [B3100]: Unexpected Broker Internal Error : [Uncaught Exception in thread Thread[JMQPortMapper,5,default]] :
    java.lang.StackOverflowError
    at java.lang.Thread.run()V(Unknown Source)
    [23/Feb/2007:06:43:16 PST] [B1060]: Loading persistent data...
    [23/Feb/2007:06:43:16 PST] Using built-in file-based persistent store: /var/opt/sun/mq/instances/imqbroker/
    [23/Feb/2007:06:43:17 PST] [B1136]: Processing stored transactions
    [23/Feb/2007:06:43:17 PST] [B1013]: Auto Creation of Queues is Enabled
    [23/Feb/2007:06:43:17 PST] [B1151]: Loading destination mq.sys.dmq [Queue] with 0 messages
    [23/Feb/2007:06:43:17 PST] [B1152]: Loading of destination mq.sys.dmq [Queue] complete
    [23/Feb/2007:06:43:17 PST] [B1004]: Starting the admin service using tcp(host = *, port=0, mode=dedicated) with min threads 4 and max threads of 10
    java.lang.StackOverflowError
    at java.lang.Thread.run()V(Unknown Source)
    [23/Feb/2007:06:43:17 PST] WARNING [B3100]: Unexpected Broker Internal Error : [Uncaught Exception in thread Thread[admin_ACCEPT,5,default]] :
    java.lang.StackOverflowError
    at java.lang.Thread.run()V(Unknown Source)
    [23/Feb/2007:06:43:17 PST] [B1004]: Starting the jms service using tcp(host = *, port=0, mode=dedicated) with min threads 10 and max threads of 1000
    java.lang.StackOverflowError
    at java.lang.Thread.run()V(Unknown Source)
    [23/Feb/2007:06:43:17 PST] WARNING [B3100]: Unexpected Broker Internal Error : [Uncaught Exception in thread Thread[jms_ACCEPT,5,default]] :
    java.lang.StackOverflowError
    at java.lang.Thread.run()V(Unknown Source)
    [23/Feb/2007:06:43:17 PST] [B1039]: Broker "imqbroker@rhel4:7676" ready.
    Exception in thread "Thread-1" java.lang.StackOverflowError
    at com.sun.messaging.jmq.util.log.Logger.format(Logger.java:580)
    at com.sun.messaging.jmq.util.log.Logger.logToAll(Logger.java:994)
    at com.sun.messaging.jmq.jmsserver.brokerShutdownHook.run(Broker.java:1878)
    Please suggest me how to resolve this issue..
    Thanks,
    Sajjan

    How do you run the program?
    I need to copy the compiled BasicPlugin.api under Acrobat\plug_ins folder. I can create a subfolder of plug_ins and copy the .api file there. Just one level deep: if I create a subfolder under a subfolder of plug_ins, the .api file will not be found by Acrobat.
    Then I need to restart Acrobat and I find the plugin running. In particular, BasicPlugin add a new Acrobat SDK menu and a menu item under it.
    If I close Acrobat and go back to Visual Studio, I can push the Debug button which will open Acrobat for me and stop the program execution at any breakpoints I have set in the code.

  • How to mark ALBPM messages as non-persistent?

    Hi,
    When using the WLS JMS Server, persistence for the messages sent through the queue is not required since ALBPM uses the JMS Queue as a dispatching mechanism only. However, since the messages sent to the Queue are marked as “Persistent”, you must mark the Queue as “Store Enable”. This will allow the WLS JMS Server to accept messages that are marked as “Persistent”. Is there any setting by which we can make these messages as non-persistent so that queues don't have to be store enabled?
    Regards,
    Xavier

    The idea behind this is to increase the speed by using non-persistent queue.
    Please help.
    Regards,
    Xavier

  • Connecting to Websphere Message broker from SAP

    Hi
    Iam working on Websphere Message Broker(WMB).
    We have to integrate SAP system and WMB, to receive messages from SAP and forward them to other resource; taking the message from the resource and sending it back to SAP, along with the message status like success or failure.
    We are using SAPAdapter which comes with WMB toolkit.
    SAP will send messages in Batch.
    I wanted to know the message format SAP send messages in batch mode. How to send message back to SAP from WMB? As far as i know if we use IDoc then only we can send message back to SAP, but if it is batch process, then how to do in this case?
    People who worked on the integration between SAP and WMB, please throw some light on this issue.
    I have gone thorugh many websites reading about ABAP, BAPI, ALE, RFC.....
    It will be very helpful if someone can answer my questions.

    Hi Nina,
    first of all I guess there is no standard answer, to what kind of format / structure SAP uses and sends to WMB. It really depends on the individual case. Also important to know, which version of WMB you are using, v6.1 has significant changes regarding SAP adapter.
    You may want to read some general WMB SAP connectivity information provided here:
    •     http://www.redbooks.ibm.com/abstracts/sg247137.html?Open (WMB Basics)
    •     http://www.redbooks.ibm.com/abstracts/sg247220.html?Open (WMB Middleware)
    •     http://www.redbooks.ibm.com/abstracts/sg246354.html?Open (WMB & SAP older)
    regards
    Marco

  • Itegration with Websphere Message Broker and Customer Master IDOC

    Hello All. I am new to this forum. I have a couple of questions.
    What I am trying to do: I have to interface to SAP with Websphere Message Broker which has inbuilt nodes to interface with SAP using BAPI or ALE to send Customer Master Record (create/update/delete)
    The questions I have:
    1/ Has anyone done this? What did you use BAPI or ALE?
    2/ When a Customer Master IDOC is sent to SAP, if successful, a return code is sent back by SAP. This indicates that SAP has received the IDOC successfully. However, our requirement is that we have to know whether the IDOC was successfully posted within SAP. I am of the opinion that this is manual task within SAP and it should not be the function of the middleware layer as its responsibility is only to successfully deliver the IDOC's. I would welcome opinions on this issue. Please let me know If there is a way to determine if the IDOC has been successfully posted in SAP.
    3/ Is there anywhere where I can get an XML representation of the Customer Master Record. I want to see the structure and the available fields. How can I get this info from SAP?
    Thank you

    Hi;
    Similar issue has been answered at -Steven Chan blog*
    From blog:
    Hello, RM,
    I have not seen any Oracle-produced documentation along those lines. I don't think there are any Oracle teams that are investing in producing documentation for IBM WebSphere.
    I would suggest contacting IBM to see whether they have produced any WebSphere-specific documentation.
    Regards,
    Steven
    Referance:
    http://blogs.oracle.com/stevenChan/entry/ebusiness_suite_release_1211_now_available
    Ps: You can rise SR for your issue also
    Regard
    Helios

  • EANCOM message : Separate channel per message sub-version

    Hello Experts,
    I have the following scenario:
    Flow 1 : ORDERS message  :  Dummy interface ( Sender AS2 channel ) -----> Dummy interface ( Receiver EDISeparator )
    Flow 2 :                                  SI_Orders_96AEAN008  ( Sender EDISeparator adapter ) ------------>   IDOC ( Receiver IDOC )
    Flow 3 :                             
    SI_Orders_96AEAN009  ( Sender EDISeparator adapter ) ------------>   IDOC ( Receiver IDOC )
    If you see, I need to configure 2 separate receiver communication channels based on message subversion to receiver 2 different messages; one CC for receiving EAN008 type of messages and one CC for receiving EAN009 type of messages. But the sender EDISeperator of type EANCOM does not have option to select the sub-version. Can you please tell how to configure 2 separate receiver channels per message sub-version.
    Thanks
    Saurabh

    Hi Piyush,
    My requirement is :
    Interface 1 : EDISeparator Sender Interface ( 96A-EAN008 ) ---> Mapping 1 ---> ZCNOSE_ORDERS.ORDER05
    Interface 2 : EDISeparator Sender Interface ( 96A-EAN010 ) ---> Mapping 2 ---> ZCNOSE_ORDERS.ORDER05
    There are around 21 GLN's sending messages of type 96A-EAN008 and 60 GLN's sending messages of type 96A-EAN010.
    As suggested by you in thread EANCOM message : Separate channel per message sub-version is that we have to use '|' as GLN separator. However since I have many GLN's, the option does not work for my scenario unless I create multiple communication channels with sets of GLN's in each communication channel.
    Will you agree that if the sender EDI separator adaptor had an option to choose the messag sub-version of the EANCOM message ( EAN008 / EAN010 ), then it would have been simple for me to create 1 Communicaiton channel such that all the messages of Interface 1 would use Mapping 1 and all the messages of Interface 2 would use Mapping 2 irrespective of any sender GLN.
    Thanks
    Saurabh

  • Saving a JMS Message in a Persistent Store

    Hello Friends,
    I am going to store a JMS message in a persistent store like a database and then recreate it when needed. What I will be doing is storing the JMS headers individually. Then storing all the properties and then the message body. I just wanted to confirm that with this data I would be able to recreate the entire message.

    Not sure of the answer to this (I suspect re-creating the message with exactly the same values as it started with will be a bit more tricky than you would imaging). Why don't you try creating a blank message and setting every single header / property? You'll probably get some exceptions / values being over written when you send.
    The real question is are you 100% sure you need to do this? The whole idea smells fishy. Why do you need the JMS Headers? Things would be far easier if the body of the message contained everything you needed. Why do you have to store the message in a database rather than leave it on a persistent queue?

  • One TV keeps getting message this channel not available

    OK so one TV an older one, in my home keeps getting the message this channel not available.  I went through ll the trouble shooting steps.  My other two TVs are fine but they are new one's.  This is my grandpas' old one.

    I'm sure it happens to many channels from time to time, because that is what happens to me.  On the DVR or on the HD STB.  Tonight I sat down to watch the Yankees play the Phillies on ESPN.  My 2 favorite teams, very excited.  At first ESPN doesn't load, then I get the BSOD w/ the white letters in the middle of the screen telling me the channel is unavailable.  It provides me w/ 2 options.  Option 1 is to switch away from this channel and back again (didn't work).  Option 2 is to call the toll free number, input a code and everything will be fine. 
    So I called the toll free number, entered the codes as prompted, and listened to the robot lady while she reset my DVR.  She told me to look for the yellow light to the left of the display after the reset and if the yellow light wasn't there, to turn on the DVR using the power button on the DVR.  I did not see the yellow light, so I turned the power on as instructed by the robot lady.  However, still no yellow light.  The robot lady is only prompting me to say next, repeat the instructions for the #%&^*(*&%@!!!#%$^ yellow light, or say problem fixed.  When I took her up on her offer of more info, she simply repeated the thing about the yellow light.
    How about adding a prompt to her repertoire asking if the yellow light isn't there.... I guarantee this will be the most used prompt.
    Meanwhile, I am too experienced and sane to call for tech support, live chat is always unavailable, so I am left waiting for some verizon kool-aid-drinking "guru" to tell me my coax is bad in the forums.
    Good night.

  • How does application connect/commincate to Message Broker + JMS

    With reference to JMS,
    I am wondering how does my application (consumer or producer) communicate to Message Broker(in my case it is ActiveMQ).
    if the consumer is at HostA, producer is at HostB and ActiveMQ=message broker is at HostC
    ???

    Each JMS queue/topic has a single persistent image. Any reference to that queue through the relevant connection factory returns the reference to the same instance.
    There may be many different queues, but each is uniquely identified by its jndi name.
    Name each of your JMS queues differently for each separate endpoint you wish to consume messages from.
    You could use ant to initiate a process by invoking the web-service sending a soap message to the url for the processes web-service. I use soap-ui or the BPEL Console to manually do the initiation, and to determine what makes up the soap packet that is forwarded to the web service. I am not aware of any task that does this for you so you would have to construct a http type target yourself.

  • Anyone used the IBM Message Broker PeopleSoft Adapter

    Is anyone out there using the PeopleSoft Adapter for the IBM Message Broker
    http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp?topic=/com.ibm.iea.wmbadapters_v6/wmbadapters/6.1/PeopleSoftAdapter.html
    I'm interested in sharing best practice in developing PeopleSoft CIs that connect to the IBM event adapter.
    Many thanks
    Graham

    John,
    Following could be the reasons:
    1. Make sure that the path in the jar file for the class files(PeopleSoft CI java api) exactly matches the following:
    \PeopleSoft\Generated\CompIntfc
    Upper and lower case differences should be followed exactly.
    2. The Java API for the selected component interface is not found in the API JAR file. Please check the Java API for the class file for the CI. If not found, please add the class file for the CI.
    3. The component interface name is mentioned incorrectly in the request document.
    4. If you are using 10.1.3.x version of SOA Suite, then make sure that the component interface jar is included in the server.xml. Please see the details for this in the 10.1.3.x application adapter installation guide.
    5. Following could also be an issue:
    LOCATION Component Interface
    Explanation
    When you attempt to access the LOCATION Component Interface using the Human Resources application, release 8.80.000, a failure occurs during runtime and the following message is displayed:
    Component Interface Not Found
    This is due to a problem in the way the PeopleSoft application has been delivered and is not related to the PeopleTools release.
    Workaround
    Perform the following steps:
    1. Open the component interface in the PeopleTools Application Designer.
    2. Make a small change to the component interface.
    3. Undo the change.
    4. Save the component interface.
    This procedure resets certain internal PeopleSoft data structures, which enables the Adapter for PeopleSoft to find the component interface. This has been observed in the LOCATION Component Interface running on the Human Resource applications release 8.8.000 on several different releases of PeopleTools, but it may
    occur in other component interfaces as well.
    Edited by: Siva Krishnajee on Jul 6, 2009 1:18 PM
    Edited by: Siva Krishnajee on Jul 6, 2009 1:36 PM

Maybe you are looking for

  • What to do prior to upgrading to Leopard from Tiger on an iMac G5

    So with the iphone coming and requiring 10.5 + i needed to up from my ancient tiger to leopard. I thought i'd get my parents mac mini too while i'm in the upgrade mode. I did the mac mini first so i could "test" on them in case of bad things....sure

  • Can i still send my iphone in for a repair after 10 days?

    Hi Guys Sorry if this is in the wrong section. Does anyone know if i can still send my iphone in for a repair more than 10 days after receiving my packaging from apple as i noticed on the confirmation email it says if you dont send the phone back wit

  • Oracle 9 and Crystal reposts 8.5

    Hello everybody! I'm trying to link my oracle 9 database on my new report, made with Crystal Reports 8.5. But I'm having this message: "ORA-01023: Cursor context not found (Invalid cursor number)", with any object that I tried to put on the report. C

  • How to define the default activity for an unbounded task flow?

    In the new "Fusion Developer's Guide for Oracle Application Development Framework 11g Release 1" documentation at the bottom of page 14-3 it states "An unbounded task flow .... contains a default activity, an activity designated as the first to run i

  • Custom Validation Routine not getting triggered

    Hi, I need some information regarding the Validation Routines that is maintained in SPRO. I created a validation routine and activated it. And also I maintained all the configurations needed. But when I create an ASN in VL60, the program control is n