Calling Tibco EMS through Weblogic

We're POCing Oracle SOA as a replacement for Tibco at our company, however, until we fully replace our tibco architecture, for reusabilities sake we want to be able to call tibco ems from applications hosted on weblogic.
So far, we've been unable to get any of our calls to EMS to succeed, as we're missing some unknown, critical peice of understanding required to use the service properly.
Here is what we know works:
We can deploy applications that make successful database calls using the database adapter in JDeveloper.
JDeveloper can see exposed queues on weblogic using the JMS Adapter wizard.
In the console/JNDI tree we can confirm that weblogic can connect to tibco by configuring weblogic through either the /Console/Services/Foreign JNDI Providers or /Console/Services/Messaging/JMS Modules/SomeModules/SomeForeignServer/Destinations
However, we have no idea how to get the Queues in the JNDI tree to apear in the JMS Adapter Wizard in JDeveloper, neither do we know how to get those queues to actually call Tibco, so we can forward calls to Weblogic to Tibco where appropriate.
Any clues at all would be awesomely amazing.
Thanks,
Daniel

Using TIBCO EMS or WebLogic JMS is essentially the same in a SOA Composite application. In both cases, the key step is to configure a new EIS connection resource in the Oracle JMS Adapter. This step is performed in EM Fusion Middleware Control (or scripted using WLST). It's the EIS connection resource that physically points to your TIBCO EMS server endpoints and a specific TIBCO EMS connection factory. Of course, when using TIBCO EMS, you also have to drop tibems.jar into your WebLogic $DOMAIN_HOME/lib directory and restart.
There's a couple variants of how to point the JMS Adapter at TIBCO (so-called direct and indirect) -- tcp:// and tibjmsnaming:// respectively. The latter is better architecturally since you are using TIBCO's JNDI services rather than bypassing them. Examples for TIBCO EIS connection definitions are in the JCA Technical Adapter section of the Fusion Middleware documentation.
From a SOA developer's point of view, their JMS service or reference definition is not provider-specific. The developer points to the JNDI name of the created JMS Adapter EIS connection, and specifies the destination (queue or topic) JNDI name. Remember, with TIBCO EMS, that destination name is TIBCO's JNDI name, not a local WebLogic JNDI name. (Caveat is that you can mash up WebLogic Foreign Server definition with EIS Connection Pool definition - I don't recommend this-- and in that case, the developer is using the local JNDI alias for the "foreign" TIBCO destination).
JDeveloper:
As you noticed, JDeveloper provides a wizard-assist to the developer for selecting a destination (queue or topic) only if the provider is WebLogic JMS or Oracle AQ. If it is a third-party provider, then there is no look-up. The developer just types the correct 3rd-party destination name (hopefully) value in.
Hope this helps. My company uses SOA Suite with both WebLogic JMS and TIBCO EMS.
Todd

Similar Messages

QUESTION Re. Integrating TIBCO EMS with Weblogic 8.1 using MDB

Hi All,
          I am trying to integrate TIBCO EMS 4.3.0 with Weblogic 8.1 SP6.
          I have created a topic "SIMPLE.TOPIC" on the EMS. I have configured the Foreign JMS Server as follows:
          Name: TIBCO JMSServer
          JNDI Initial Context Factory:com.tibco.tibjms.naming.TibjmsInitialContextFactory
          JNDI Connection URL:tibjmsnaming://emshost:emsport
          I have configured the connection factory as follows:
          Name: TIBCO JMSTopicConnectionFactory
          Local JNDI Name: TopicConnectionFactory.Local
          Remote JNDI Name:TopicConnectionFactory
          User Name:username to connect to EMS server
          Password::pssword to connect to EMS server
          My JMS destination is configured as follows:
          Name: Tibco JMS Destination
          Local JNDI Name:SIMPLE.TOPIC.LOCAL
          Remote JNDI Name:SIMPLE.TOPIC
          My weblogic-ejb-jar.xml consists of the following code:
                    <weblogic-ejb-jar>
            <weblogic-enterprise-bean>
              <ejb-name>SimpleTopicListener</ejb-name>
              <message-driven-descriptor>
                <pool>
                  <max-beans-in-free-pool>200</max-beans-in-free-pool>
                  <initial-beans-in-free-pool>20</initial-beans-in-free-pool>
                </pool>
                <destination-jndi-name>SIMPLE.TOPIC</destination-jndi-name>
               <connection-factory-jndi-name>TopicConnectionFactory</connection-factory-jndi-name>
              </message-driven-descriptor>
              <enable-call-by-reference>True</enable-call-by-reference>
            </weblogic-enterprise-bean>
          </weblogic-ejb-jar>
                              The problem is, when I try to deploy this mdb, I get the following error:
          The Message-Driven EJB attempted to connect to the JMS destination with the JNDI name: SIMPLE.TOPIC. However, the object with the JNDI name: SIMPLE.TOPIC is not a JMS destination, or the destination found was of the wrong type (Topic or Queue).
          I have checked and double checked to make sure that the topic SIMPLE.TOPIC does exist on the EMS server.
          Does anyone know what is the issue here and how to resolve it?
          Many thanks!
          -Kinshuk
          Edited by kinshukk at 05/14/2007 8:35 AM

(1) Check the standard ejb jar and make sure you've specified a topic destination type (the default is queue). For details, you can reference the WebLogic 9.0 MDB developer guide (the MDB dev guide was revised in 9.0 to include more detail than the 8.1 guide). Also, you might want to take a look at our integration/interop FAQ (again for 9.0 or later).
          (2) Change the weblogic-ejb-jar to reference the foreign local JNDI names - not the remote JNDI names.
          (3) Be careful about using the "." and "/" characters in local JNDI names - these have side-effects in JNDI (they force creation of subcontexts).
          Tom

ReplyTo is null while forwarding the messages from TIBCO EMS to Weblogic

I have created bridge between TIBCO queue and WL (version 10.3) queue.
And sent message on TIBCO queue with ReplyTo queue value set. Text Message is passed successfully to WL queue but replyTo is null.
All other header values like messageID, correlationID, priority are received correctly.
Any Idea?

Hi,
Check this Doc Id.
How to Configure Weblogic Server with TibCO EMS Server (Doc ID 1343314.1)
regards,
Kal

Integrate Weblogic 11gR1 with Tibco EMS

Hi,
Is there a how-to guide on how to configure Tibco EMS as a JMS foreign server in WLS 11g? Do I need to use Tibco connection factory as JNDI context factory?
Thanks a lot for your help,
Jane

There's no Tibco specific how-to-guide that I'm aware of -- Tibco integrates using the same facilities that are used for other vendors. See the "JMS interop FAQ" in the edocs.
Tom

WLS 9.2 with TIBCO ems integration doesnt seem to be working

Hi, I followed the steps provided by Tibco doc on how to integrate with WLS 8 and they worked fine with my app, the messages were getting in to the Tibco queues, but I didnt find any steps on how to integrate TIBCO with WLS 9.2.
          Still I managed to extrapolate the below steps from the WLS 9.2 JMS foreign server config instructions to have them work with TIBCO, but my App fails with errors saying... "Failed to send message using the connection..."
          Anyone has the correct working instructions to integrate TIBCO with WLS 9.2?
          ---------- In Tibco ems --------------------
          Created 2 queues:
          OrderJMSQueue
          ShippingMDBQueue
          Created 2 connection factories:
          ShippingMDBQueueCF
          OrderJMSQueueCF
          ---------- end In Tibco ems --------------------
          ---------- In WLS 9.2 server --------------------
          1. In C:\WLS92\user_projects\domains\pqedomain\bin\startweblogic.bat
          Add:
               set CLASSPATH=C:\Tibco\ems\clients\java\tibjms.jar;%CLASSPATH%
               (assuming that Tibco is installed under C:\)
          2. Start the WLS 9.2 Server
          3. Open the WLS 9.2 admin page: http://localhost:7080/console
          4. Select Services -> Messaging -> JMS Modules
          5. Click New
               a. Set Name: "jms-mod"
          6. Click on "jms-mod"
          7. Create a Resource "Foreign JMs server"
               Name: PurchasingAppJMSServer
               JNDI Initial Context Factory: com.tibco.tibjms.naming.TibjmsInitialContextFactory
               JNDI Connection URL : tibjmsnaming://localhost:7222
          8. Under PurchasingAppJMSServer
               a. Click on Destinations -> New
                    i. Name: OrderJMSQueue
                    ii. Local JNDI Name: OrderJMSQueue
                    iii. Remote JNDI Name: OrderJMSQueue
               b. Click on Save
          9. Again under PurchasingAppJMSServer
          a. Click on Destinations -> New
          i. Name: ShippingMDBQueue
          ii. Local JNDI Name: ShippingMDBQueue
          iii. Remote JNDI Name: ShippingMDBQueue
          b. Click on Save
          10. Again under PurchasingAppJMSServer
               a. Click on Connection Factories -> New
          i. Name: OrderJMSQueueCF
          ii. Local JNDI Name: OrderJMSQueueCF
          iii. Remote JNDI Name: OrderJMSQueueCF
          b. Click on Save
          11. Again under PurchasingAppJMSServer
          a. Click on Connection Factories -> New
          i. Name: ShippingMDBQueueCF
          ii. Local JNDI Name: ShippingMDBQueueCF
          iii. Remote JNDI Name: ShippingMDBQueueCF
          b. Click on Save
          12. Come up to the Home page
          13. Click on Services -> Foreign JNDI Providers
          14. Click on New
          15. Enter Name: PurchasingAppJMSServer
          16. Click Save
          17. Click on "PurchasingAppJMSServer" under the "Summary of Foreign JNDI Servers"
               a. Set Initial Context Factory: com.tibco.tibjms.naming.TibjmsInitialContextFactory
               b. Set Provider URL: tibjmsnaming://localhost:7222
               c. Set User: admin
               d. Click Save

I have tried this succesfully with 8.2 and 9.2. No patch was required though it is not a bad idea to apply patch.
          As mentioned above, On weblogic side, I configured:
          1) Foreign JMS Server
          2) Foreign JMS Destination
          3) Foreign JMS Connection Factory
          I did not configure foreign jms provider.
          On EMS side, I created a Queue. That's it.
          I used default connection factory in EMS (QueueConnectionFactory)
          This is how my MDB class looks like:
          import javax.jms.JMSException;
          import javax.jms.Message;
          import javax.jms.TextMessage;
          import weblogic.ejbgen.MessageDriven;
          import weblogic.ejbgen.ForeignJmsProvider;
          @MessageDriven(ejbName = "SubscriberMessageDrivenBean",
                    destinationJndiName = "subscriberNotificationQueue",
                    destinationType = "javax.jms.Queue",
                    maxBeansInFreePool = "200",
                    initialBeansInFreePool = "20",
                    transTimeoutSeconds = "180",
                    defaultTransaction = MessageDriven.DefaultTransaction.NOT_SUPPORTED
          @ForeignJmsProvider(connectionFactoryJndiName="QueueConnectionFactoryLocal")
          public class SubscriberMessageDrivenBean extends JMSInterface {
               public void OnMessage(Message inMessage) {
          try {
               System.out.println("Reached onMessage");
          } catch (JMSException exp) {
          e.printStackTrace();
          and ejb-jar.xml like this......
          <?xml version="1.0" encoding="UTF-8"?>
          
          <ejb-jar
          xmlns="http://java.sun.com/xml/ns/j2ee"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
          version="2.1">
          <enterprise-beans>
          <message-driven>
          <ejb-name>SubscriberMessageDrivenBean</ejb-name>
          <ejb-class>com.att.cpni.common.interfaces.jms.atlas.SubscriberMessageDrivenBean</ejb-class>
          <transaction-type>Container</transaction-type>
          <activation-config>
          <activation-config-property>
          <activation-config-property-name>destinationType</activation-config-property-name>
          <activation-config-property-value>javax.jms.Queue</activation-config-property-value>
          </activation-config-property>
          </activation-config>
          </message-driven>
          </enterprise-beans>
          <assembly-descriptor>
          <container-transaction>
          <method>
          <ejb-name>AccountMessageDrivenBean</ejb-name>
          <method-name>*</method-name>
          </method>
          <trans-attribute>NotSupported</trans-attribute>
          </container-transaction>
          <container-transaction>
          <method>
          <ejb-name>SubscriberMessageDrivenBean</ejb-name>
          <method-name>*</method-name>
          </method>
          <trans-attribute>NotSupported</trans-attribute>
          </container-transaction>
          </assembly-descriptor>
          </ejb-jar>
          and weblogic-ejb-jar.xml like this.......
          <?xml version="1.0" encoding="UTF-8"?>
          
          <weblogic-ejb-jar
          xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
          <weblogic-enterprise-bean>
          <ejb-name>SubscriberMessageDrivenBean</ejb-name>
          <message-driven-descriptor>
          <pool>
          <max-beans-in-free-pool>200</max-beans-in-free-pool>
          <initial-beans-in-free-pool>20</initial-beans-in-free-pool>
          </pool>
          <destination-jndi-name>subscriberNotificationQueue</destination-jndi-name>
          <connection-factory-jndi-name>QueueConnectionFactoryLocal</connection-factory-jndi-name>
          </message-driven-descriptor>
          <transaction-descriptor>
          <trans-timeout-seconds>180</trans-timeout-seconds>
          </transaction-descriptor>
          </weblogic-enterprise-bean>
          </weblogic-ejb-jar>

EJB does not connect to IP through WebLogic

          Hi All--
          Here is the problem. My servlet makes calls to EJB's in the hopes of connecting
          to an IP address outside of my firewall through WebLogic. It doesn't attempt
          a connection. I know my code is correct because an application version of this
          servlet successfully hits the IP when run at a Unix prompt. What kind of configurations
          are required to make WebLogic attempt a foreign IP connection.
          thank you in advance,
          Dave


It happened to me sometimes, try to activate airplane mode for a few seconds and deactivate it, hope this helps

Session Beans and TIBCO E4JMS and Weblogic JMS 8.1

          Setup:-
          Weblogic Server 8.1 SP2 on Linux
          TIBCO E4JMS 3.1.2
          I have a two Staeless Session Beans which are deployed in both sides of the cluster
          - Cluster is made up of two servers(ManagedServer1 and ManagedServer2) on the
          same machine. The beans have container managed transaction and trans-type set
          to required. The JMS Server is on ManagedServer1. The session bean publishes 100
          messages to TIBCO JMS and Weblogic JMS and calls the second bean which again publishes
          100 messages to TIBCO JMS and Weblogic JMS .
          The connection factories used are XAQueueConnectionFactories.
          This seems to work under the following conditions:-
          a) The session beans are deployed just in ManagedServer1
          b) The WL load balancing scheme manages to run both the beans on ManagedServer1
          c) If I don't publish onto Weblogic JMS( It runs successfully on ManagedServer1
          and ManagedServer2)
          It does not seems to work :-
          When the The WL load balancing scheme manages to run both the beans on ManagedServer2.I
          put debug statements on the beans and it seems to publish everything but fails
          during the commit
          murali@dbuslinux1:~/SessionBeanExample> ant run
          Buildfile: build.xml
          run:
          [java] Run : 0
          [java] InitialContextFactory weblogic.jndi.WLInitialContextFactory
          [java] Provider Url t3://myhost.mycompany.com:18003,myhost.mycompany.com:18005
          [java] javax.transaction.TransactionRolledbackException: Exception while
          commiting Tx : Name=[EJB Case463495.StatelessBean.sendMessageWrap(java.lang.Integer,java.lang.Integer,java.lang.String,boolean,boolean)],Xid=BEA1-000649EC8876A0032A5E(160401684),Status=Rolled
          back. [Reason=javax.transaction.xa.XAException],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
          since begin=3,seconds left=30,XAServerResourceInfo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN1TCF]=(ServerResourceInfo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN1TCF]=(state=rolledback,assigned=ManagedServer2),xar=weblogic.deployment.jms.WrappedXAResource_com_tibco_tibjms_TibjmsXAResource@a0181b0),XAServerResourceInfo[JMS_MyJMS
          File Store]=(ServerResourceInfo[JMS_MyJMS File Store]=(state=rolledback,assigned=ManagedServer1),xar=null),XAServerResourceInfo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN2TCF]=(ServerResourceInfo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN2TCF]=(state=rolledback,assigned=ManagedServer2),xar=weblogic.deployment.jms.WrappedXAResource_com_tibco_tibjms_TibjmsXAResource@98f6821),SCInfo[E4JMSDOMAIN+ManagedServer1]=(state=rolledback),SCInfo[E4JMSDOMAIN+ManagedServer2]=(state=rolledback),properties=({weblogic.transaction.name=[EJB
          Case463495.StatelessBean.sendMessageWrap(java.lang.Integer,java.lang.Integer,java.lang.String,boolean,boolean)]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=ManagedServer2+myhost.mycompany.com:18005+E4JMSDOMAIN+t3+,
          XAResources={},NonXAResources={})],CoordinatorURL=ManagedServer2+myhost.mycompany.com:18005+E4JMSDOMAIN+t3+):
          javax.transaction.xa.XAException
          [java] at com.tibco.tibjms.TibjmsXAResource.end(Ljavax.transaction.xa.Xid;I)V(TibjmsXAResource.java:157)
          [java] at weblogic.deployment.jms.WrappedXAResource_com_tibco_tibjms_TibjmsXAResource.end(Ljavax.transaction.xa.Xid;I)V(Unknown
          Source)
          [java] at weblogic.transaction.internal.XAServerResourceInfo.end(Lweblogic.transaction.internal.ServerTransactionImpl;Ljavax.transaction.xa.Xid;I)V(XAServerResourceInfo.java:1124)
          [java] at weblogic.transaction.internal.XAServerResourceInfo.internalDelist(Lweblogic.transaction.internal.ServerTransactionImpl;I)V(XAServerResourceInfo.java:325)
          [java] at weblogic.transaction.internal.XAServerResourceInfo.delist(Lweblogic.transaction.internal.ServerTransactionImpl;IZ)V(XAServerResourceInfo.java:255)
          [java] at weblogic.transaction.internal.ServerTransactionImpl.delistAll(IZ)V(ServerTransactionImpl.java:1408)
          [java] at weblogic.transaction.internal.ServerTransactionImpl.delistAll(I)V(ServerTransactionImpl.java:1396)
          [java] at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare()V(ServerTransactionImpl.java:1932)
          [java] at weblogic.transaction.internal.ServerTransactionImpl.internalCommit()V(ServerTransactionImpl.java:252)
          [java] at weblogic.transaction.internal.ServerTransactionImpl.commit()V(ServerTransactionImpl.java:221)
          [java] at weblogic.ejb20.internal.BaseEJBObject.postInvoke(Lweblogic.ejb20.interfaces.InvocationWrapper;Ljava.lang.Throwable;)V(BaseEJBObject.java:289)
          [java] at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(Lweblogic.ejb20.interfaces.InvocationWrapper;Ljava.lang.Throwable;)V(StatelessEJBObject.java:141)
          [java] at Case463495.Stateless_soycq8_EOImpl.sendMessageWrap(Ljava.lang.Integer;Ljava.lang.Integer;Ljava.lang.String;ZZ)V(Stateless_soycq8_EOImpl.java:112)
          [java] at Case463495.Stateless_soycq8_EOImpl_WLSkel.invoke(ILweblogic.rmi.spi.InboundRequest;Lweblogic.rmi.spi.OutboundResponse;Ljava.lang.Object;)Lweblogic.rmi.spi.OutboundResponse;(Unknown
          Source)
          [java] at weblogic.rmi.internal.BasicServerRef.invoke(Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;Lweblogic.rmi.spi.InboundRequest;Lweblogic.rmi.spi.OutboundResponse;)V(BasicServerRef.java:477)
          [java] at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;Lweblogic.rmi.spi.InboundRequest;Lweblogic.rmi.spi.OutboundResponse;)V(ReplicaAwareServerRef.java:108)
          [java] at weblogic.rmi.internal.BasicServerRef$1.run()Ljava.lang.Object;(BasicServerRef.java:420)
          [java] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedExceptionAction;)Ljava.lang.Object;(AuthenticatedSubject.java:353)
          [java] at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedExceptionAction;)Ljava.lang.Object;(SecurityManager.java:144)
          [java] at weblogic.rmi.internal.BasicServerRef.handleRequest(Lweblogic.rmi.spi.InboundRequest;)V(BasicServerRef.java:415)
          [java] at weblogic.rmi.internal.BasicExecuteRequest.execute(Lweblogic.kernel.ExecuteThread;)V(BasicExecuteRequest.java:30)
          [java] at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:197)
          [java] at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:170)
          [java] at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown
          Source)
          [java] ; nested exception is:
          [java] javax.transaction.xa.XAException
          [java] at weblogic.rjvm.BasicOutboundRequest.sendReceive()Lweblogic.rmi.spi.InboundResponse;(BasicOutboundRequest.java:108)
          [java] at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(Lweblogic.rmi.extensions.server.RemoteReference;Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;[Ljava.lang.Object;Ljava.lang.reflect.Method;)Ljava.lang.Object;(ReplicaAwareRemoteRef.java:284)
          [java] at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(Ljava.rmi.Remote;Lweblogic.rmi.extensions.server.RuntimeMethodDescriptor;[Ljava.lang.Object;Ljava.lang.reflect.Method;)Ljava.lang.Object;(ReplicaAwareRemoteRef.java:244)
          [java] at Case463495.Stateless_soycq8_EOImpl_812_WLStub.sendMessageWrap(Ljava.lang.Integer;Ljava.lang.Integer;Ljava.lang.String;ZZ)V(Unknown
          Source)
          [java] at Case463495.Client.run()V(Client.java:103)
          [java] at Case463495.Client.sendMessage()V(Client.java:132)
          [java] at Case463495.Client.main([Ljava.lang.String;)V(Client.java:195)
          [java] Caused by: javax.transaction.xa.XAException
          [java] at com.tibco.tibjms.TibjmsXAResource.end(TibjmsXAResource.java:157)
          [java] at weblogic.deployment.jms.WrappedXAResource_com_tibco_tibjms_TibjmsXAResource.end(Unknown
          Source)
          [java] at weblogic.transaction.internal.XAServerResourceInfo.end(XAServerResourceInfo.java:1124)
          [java] at weblogic.transaction.internal.XAServerResourceInfo.internalDelist(XAServerResourceInfo.java:325)
          [java] at weblogic.transaction.internal.XAServerResourceInfo.delist(XAServerResourceInfo.java:255)
          [java] at weblogic.transaction.internal.ServerTransactionImpl.delistAll(ServerTransactionImpl.java:1408)
          [java] at weblogic.transaction.internal.ServerTransactionImpl.delistAll(ServerTransactionImpl.java:1396)
          [java] at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:1932)
          [java] at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:252)
          [java] at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:221)
          [java] at weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:289)
          [java] at weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.java:141)
          [java] at Case463495.Stateless_soycq8_EOImpl.sendMessageWrap(Stateless_soycq8_EOImpl.java:112)
          [java] at Case463495.Stateless_soycq8_EOImpl_WLSkel.invoke(Unknown Source)
          [java] at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
          [java] at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
          [java] at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
          [java] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
          [java] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
          [java] at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
          [java] at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
          [java] at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          [java] at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          [java] at java.lang.Thread.startThreadFromVM(Unknown Source)
          Apologies in advance if this need to be posted in the JTA news group..
          Any ideas?
          Murali


Posting to the transaction newsgroup would probably also be helpful.
          Can you post the code for the session bean so we can see how you're
          enlisting Tibco in the transaction? It looks like you're using the JMS
          provider wrappers from 8.1, which do the transaction enlistment for you, so
          you shouldn't need to mess with JTA at all in your code. Still, something
          weird is going on and it'd be nice to see exactly what your code looks like.
          greg
          "L Muralidharan" <[email protected]> wrote in message
          news:[email protected]...
          >
          > Setup:-
          >
          > Weblogic Server 8.1 SP2 on Linux
          >
          > TIBCO E4JMS 3.1.2
          >
          > I have a two Staeless Session Beans which are deployed in both sides of
          the cluster
          > - Cluster is made up of two servers(ManagedServer1 and ManagedServer2) on
          the
          > same machine. The beans have container managed transaction and trans-type
          set
          > to required. The JMS Server is on ManagedServer1. The session bean
          publishes 100
          > messages to TIBCO JMS and Weblogic JMS and calls the second bean which
          again publishes
          > 100 messages to TIBCO JMS and Weblogic JMS .
          >
          > The connection factories used are XAQueueConnectionFactories.
          >
          > This seems to work under the following conditions:-
          >
          > a) The session beans are deployed just in ManagedServer1
          > b) The WL load balancing scheme manages to run both the beans on
          ManagedServer1
          > c) If I don't publish onto Weblogic JMS( It runs successfully on
          ManagedServer1
          > and ManagedServer2)
          >
          > It does not seems to work :-
          >
          > When the The WL load balancing scheme manages to run both the beans on
          ManagedServer2.I
          > put debug statements on the beans and it seems to publish everything but
          fails
          > during the commit
          >
          > murali@dbuslinux1:~/SessionBeanExample> ant run
          > Buildfile: build.xml
          >
          > run:
          > [java] Run : 0
          > [java] InitialContextFactory weblogic.jndi.WLInitialContextFactory
          > [java] Provider Url
          t3://myhost.mycompany.com:18003,myhost.mycompany.com:18005
          > [java] javax.transaction.TransactionRolledbackException: Exception
          while
          > commiting Tx : Name=[EJB
          Case463495.StatelessBean.sendMessageWrap(java.lang.Integer,java.lang.Integer
          ,java.lang.String,boolean,boolean)],Xid=BEA1-000649EC8876A0032A5E(160401684)
          ,Status=Rolled
          > back.
          [Reason=javax.transaction.xa.XAException],numRepliesOwedMe=0,numRepliesOwedO
          thers=0,seconds
          > since begin=3,seconds
          left=30,XAServerResourceInfo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEA
          N1TCF]=(ServerResourceInfo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN1
          TCF]=(state=rolledback,assigned=ManagedServer2),xar=weblogic.deployment.jms.
          WrappedXAResource_com_tibco_tibjms_TibjmsXAResource@a0181b0),XAServerResourc
          eInfo[JMS_MyJMS
          > File Store]=(ServerResourceInfo[JMS_MyJMS File
          Store]=(state=rolledback,assigned=ManagedServer1),xar=null),XAServerResource
          Info[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN2TCF]=(ServerResourceIn
          fo[E4JMSDOMAIN.ManagedServer2.JMSXASessionPool.BEAN2TCF]=(state=rolledback,a
          ssigned=ManagedServer2),xar=weblogic.deployment.jms.WrappedXAResource_com_ti
          bco_tibjms_TibjmsXAResource@98f6821),SCInfo[E4JMSDOMAIN+ManagedServer1]=(sta
          te=rolledback),SCInfo[E4JMSDOMAIN+ManagedServer2]=(state=rolledback),propert
          ies=({weblogic.transaction.name=[EJB
          >
          Case463495.StatelessBean.sendMessageWrap(java.lang.Integer,java.lang.Integer
          ,java.lang.String,boolean,boolean)]}),OwnerTransactionManager=ServerTM[Serve
          rCoordinatorDescriptor=(CoordinatorURL=ManagedServer2+myhost.mycompany.com:1
          8005+E4JMSDOMAIN+t3+,
          >
          XAResources={},NonXAResources={})],CoordinatorURL=ManagedServer2+myhost.myco
          mpany.com:18005+E4JMSDOMAIN+t3+):
          > javax.transaction.xa.XAException
          > [java] at
          com.tibco.tibjms.TibjmsXAResource.end(Ljavax.transaction.xa.Xid;I)V(TibjmsXA
          Resource.java:157)
          > [java] at
          weblogic.deployment.jms.WrappedXAResource_com_tibco_tibjms_TibjmsXAResource.
          end(Ljavax.transaction.xa.Xid;I)V(Unknown
          > Source)
          > [java] at
          weblogic.transaction.internal.XAServerResourceInfo.end(Lweblogic.transaction
          .internal.ServerTransactionImpl;Ljavax.transaction.xa.Xid;I)V(XAServerResour
          ceInfo.java:1124)
          > [java] at
          weblogic.transaction.internal.XAServerResourceInfo.internalDelist(Lweblogic.
          transaction.internal.ServerTransactionImpl;I)V(XAServerResourceInfo.java:325
          > [java] at
          weblogic.transaction.internal.XAServerResourceInfo.delist(Lweblogic.transact
          ion.internal.ServerTransactionImpl;IZ)V(XAServerResourceInfo.java:255)
          > [java] at
          weblogic.transaction.internal.ServerTransactionImpl.delistAll(IZ)V(ServerTra
          nsactionImpl.java:1408)
          > [java] at
          weblogic.transaction.internal.ServerTransactionImpl.delistAll(I)V(ServerTran
          sactionImpl.java:1396)
          > [java] at
          weblogic.transaction.internal.ServerTransactionImpl.globalPrepare()V(ServerT
          ransactionImpl.java:1932)
          > [java] at
          weblogic.transaction.internal.ServerTransactionImpl.internalCommit()V(Server
          TransactionImpl.java:252)
          > [java] at
          weblogic.transaction.internal.ServerTransactionImpl.commit()V(ServerTransact
          ionImpl.java:221)
          > [java] at
          weblogic.ejb20.internal.BaseEJBObject.postInvoke(Lweblogic.ejb20.interfaces.
          InvocationWrapper;Ljava.lang.Throwable;)V(BaseEJBObject.java:289)
          > [java] at
          weblogic.ejb20.internal.StatelessEJBObject.postInvoke(Lweblogic.ejb20.interf
          aces.InvocationWrapper;Ljava.lang.Throwable;)V(StatelessEJBObject.java:141)
          > [java] at
          Case463495.Stateless_soycq8_EOImpl.sendMessageWrap(Ljava.lang.Integer;Ljava.
          lang.Integer;Ljava.lang.String;ZZ)V(Stateless_soycq8_EOImpl.java:112)
          > [java] at
          Case463495.Stateless_soycq8_EOImpl_WLSkel.invoke(ILweblogic.rmi.spi.InboundR
          equest;Lweblogic.rmi.spi.OutboundResponse;Ljava.lang.Object;)Lweblogic.rmi.s
          pi.OutboundResponse;(Unknown
          > Source)
          > [java] at
          weblogic.rmi.internal.BasicServerRef.invoke(Lweblogic.rmi.extensions.server.
          RuntimeMethodDescriptor;Lweblogic.rmi.spi.InboundRequest;Lweblogic.rmi.spi.O
          utboundResponse;)V(BasicServerRef.java:477)
          > [java] at
          weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(Lweblogic.rmi.extensions.s
          erver.RuntimeMethodDescriptor;Lweblogic.rmi.spi.InboundRequest;Lweblogic.rmi
          .spi.OutboundResponse;)V(ReplicaAwareServerRef.java:108)
          > [java] at
          weblogic.rmi.internal.BasicServerRef$1.run()Ljava.lang.Object;(BasicServerRe
          f.java:420)
          > [java] at
          weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.
          subject.AbstractSubject;Ljava.security.PrivilegedExceptionAction;)Ljava.lang
          .Object;(AuthenticatedSubject.java:353)
          > [java] at
          weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.inter
          nal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubjec
          t;Ljava.security.PrivilegedExceptionAction;)Ljava.lang.Object;(SecurityManag
          er.java:144)
          > [java] at
          weblogic.rmi.internal.BasicServerRef.handleRequest(Lweblogic.rmi.spi.Inbound
          Request;)V(BasicServerRef.java:415)
          > [java] at
          weblogic.rmi.internal.BasicExecuteRequest.execute(Lweblogic.kernel.ExecuteTh
          read;)V(BasicExecuteRequest.java:30)
          > [java] at
          weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(Exe
          cuteThread.java:197)
          > [java] at
          weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:170)
          > [java] at
          java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown
          > Source)
          > [java] ; nested exception is:
          > [java] javax.transaction.xa.XAException
          > [java] at
          weblogic.rjvm.BasicOutboundRequest.sendReceive()Lweblogic.rmi.spi.InboundRes
          ponse;(BasicOutboundRequest.java:108)
          > [java] at
          weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(Lweblogic.rmi.extensions.s
          erver.RemoteReference;Lweblogic.rmi.extensions.server.RuntimeMethodDescripto
          r;[Ljava.lang.Object;Ljava.lang.reflect.Method;)Ljava.lang.Object;(ReplicaAw
          areRemoteRef.java:284)
          > [java] at
          weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(Ljava.rmi.Remote;Lweblogic
          .rmi.extensions.server.RuntimeMethodDescriptor;[Ljava.lang.Object;Ljava.lang
          .reflect.Method;)Ljava.lang.Object;(ReplicaAwareRemoteRef.java:244)
          > [java] at
          Case463495.Stateless_soycq8_EOImpl_812_WLStub.sendMessageWrap(Ljava.lang.Int
          eger;Ljava.lang.Integer;Ljava.lang.String;ZZ)V(Unknown
          > Source)
          > [java] at Case463495.Client.run()V(Client.java:103)
          > [java] at Case463495.Client.sendMessage()V(Client.java:132)
          > [java] at
          Case463495.Client.main([Ljava.lang.String;)V(Client.java:195)
          > [java] Caused by: javax.transaction.xa.XAException
          > [java] at
          com.tibco.tibjms.TibjmsXAResource.end(TibjmsXAResource.java:157)
          > [java] at
          weblogic.deployment.jms.WrappedXAResource_com_tibco_tibjms_TibjmsXAResource.
          end(Unknown
          > Source)
          > [java] at
          weblogic.transaction.internal.XAServerResourceInfo.end(XAServerResourceInfo.
          java:1124)
          > [java] at
          weblogic.transaction.internal.XAServerResourceInfo.internalDelist(XAServerRe
          sourceInfo.java:325)
          > [java] at
          weblogic.transaction.internal.XAServerResourceInfo.delist(XAServerResourceIn
          fo.java:255)
          > [java] at
          weblogic.transaction.internal.ServerTransactionImpl.delistAll(ServerTransact
          ionImpl.java:1408)
          > [java] at
          weblogic.transaction.internal.ServerTransactionImpl.delistAll(ServerTransact
          ionImpl.java:1396)
          > [java] at
          weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTran
          sactionImpl.java:1932)
          > [java] at
          weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
          nsactionImpl.java:252)
          > [java] at
          weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
          Impl.java:221)
          > [java] at
          weblogic.ejb20.internal.BaseEJBObject.postInvoke(BaseEJBObject.java:289)
          > [java] at
          weblogic.ejb20.internal.StatelessEJBObject.postInvoke(StatelessEJBObject.jav
          a:141)
          > [java] at
          Case463495.Stateless_soycq8_EOImpl.sendMessageWrap(Stateless_soycq8_EOImpl.j
          ava:112)
          > [java] at
          Case463495.Stateless_soycq8_EOImpl_WLSkel.invoke(Unknown Source)
          > [java] at
          weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
          > [java] at
          weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java
          :108)
          > [java] at
          weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
          > [java] at
          weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubjec
          t.java:353)
          > [java] at
          weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
          > [java] at
          weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
          > [java] at
          weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:3
          0)
          > [java] at
          weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
          > [java] at
          weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          > [java] at java.lang.Thread.startThreadFromVM(Unknown Source)
          >
          >
          > Apologies in advance if this need to be posted in the JTA news group..
          >
          > Any ideas?
          >
          > Murali
          >

Accessing Tibco-EMS queue from XI(using JMS adapter)

Hi All,
I am currently working on a Tibco Integration scenario with XI thru JMS(Sender) adapter. I have gone through some of our SDN forum threads and come to know that we have to deploy some TIBCO specific jar files to the fetch data from TIBCO-EMS queues. But still have the following query on
1. what are all the JAR files(TIBCO JMS libraries) needed to be installed in SAP J2EE engine? I have got the following JAR files from TIBCO guys...
tibcrypt.jar
tibjms.jar
tibjmsadmin.jar
tibjmsapps.jar
tibrvjms.jar
regards,
Raks

Hi Raks,
Check this note for JNDI configuration..
802754
"If a 3rd party JMS provider should be used then usually the "Name of JNDI initial context factory" must be adjusted. I.e. com.sap.engine.services.jndi.InitialContextFactoryImpl must be replaced by some.other.vendor.jms.jndi.InitialContextFactory In addition it is necessary to deploy the jar that contains the some.other.vendor.jms.jndi.InitialContextFactory with the aii_af_jmsproviderlib.sda SDA file. In addition, you must extend the server/provider.xml deployment descriptor in the relevant way. Refer to Chapter 11 of the XI 3.0 Configuration Guide for more information"
You need to find out class "Name of JNDI initial context factory" for tibco as mentoned in the note and deploy the corresponding JAR file.
Also check this link for JNDI configuration parameters in the JMs adapter..
http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
Regards
Anand

Call by reference in weblogic

hi all,
i am using statful session ful bean ,where are i am using Vector ,when i retrieve
the vector in to another Vector and do some manipulation on the new Vector ,but
the Vector that is declared in the Stateful session bean remains unchanged , i
had using the same thing with the main site , and my local site ,it is working
on the localsite but not on the main site.
e.g Vector test = m_sessionfulBean.getAllValue();
when i do the changes it won't get reflected to the vector that it return.
Can somebody help?

The problem with the Vector (and almost all collections) is that while
they clone the main object, the elements are not cloned so any
modification to the elements will affect your original. That is why I
said that you should clone the collection only if the caller would not
modify the elements.
Or the EJB method can also clone the elements and return a new Vector.
The gain is performance since cloning is usually faster than serializing
for local clients but the down side of this is that remote clients will
have an overhead as for them the result will be serialized anyway so
there was a cloning done with no need for it.
Cheers,
Dejan
Byron Xiao wrote:
See, I am not sure what he really means in his message. By the way, Vector also
implements the Clonable interface. But the elements of the Vector may not implement
the Clonable interface. If you clone the Vector and return the cloned Vector
to the caller. There is no guarantee that the changes he made in the Vector elements
will get clone properly. So in that case, you aren't really seeing the true "call
by reference" behavior.
Basically, I don't understand what his question was. Sorry for the confusion.
"Deyan D. Bektchiev" <[email protected]> wrote:
Not really true, if the Vector is serialized then it would have to
serialize all of its elements and you'd get an exception that some
elements were not serializable.
The optimization that Sanjeev is seeing is a BEA optimization to allow
calls by reference within the same enterprise application (parameter
<enable-call-by-reference> in weblogic-ejb-jar.xml).
By default the value is true so calls within the same EAR are just
normal Java calls.
If you set it to false then the parameters and return value of the EJB
call will be serialized and the object that the EJB has will not be
affected by any change that the caller does to it.
Another way to get out of this situation is to clone the Vector (if that
is acceptable since it would not clone the elements the Vector contains).
--dejan
Byron Xiao wrote:
I don't know if I understand your problem 100%, but it seems like you
manipulated
the elements in your vector, which is a class member variable in your
stateful
session bean, and passing the vector back as the return parameter to
the caller
via the remote interface. And you don't see the changes in the "elements"
of
the vector, is that correct?
Well, remember all parameters and the return value of the remote calls
are Serializable.
In this case, Vector indeed is serializable. But the ELEMENTS inside
the vector
may not be serializable objects. In this case, the container will use
the default
serialization mechanism to serialize / deserialize the elements into
the persistent
store or through the RMI I/O stream, which is just using a bit-wise
dump of your
Vector and all its elements object references to the persistent store
or RMI I/O
stream.
So the solution is to declare all the objects in your Vector elements
to implement
the java.io.Serializable interface. If all the Objects in your vector
elements
only contain primitive data types, you don't need to do anything extra.
If some
objects in your vector elements contain other object types that don't
implement
the java.io.Serialiazable interface, then you will need to write your
own writeObject
and readObject method to serialize /de-serialize those objects. You
can look
up many tutorial on Sun's website on how to do this. Hope it helps.
"sanjeev" <[email protected]> wrote:
hi all,
i am using statful session ful bean ,where are i am using Vector ,when
i retrieve
the vector in to another Vector and do some manipulation on the new
Vector
,but
the Vector that is declared in the Stateful session bean remains unchanged
, i
had using the same thing with the main site , and my local site ,it
is
working
on the localsite but not on the main site.
e.g Vector test = m_sessionfulBean.getAllValue();
when i do the changes it won't get reflected to the vector that it
return.
Can somebody help?

TIBCO EMS & JBoss problem

Hai,
I have configured my jms in jboss with TIBCO EMS. i am able to send Queue messages from client. but my message driven bean is not able to receive the queue.
I found the following error message in Jboss log
Cannot instantiate class: com.tibco.tibjms.naming.TibjmsInitialContextFactory
Why it happens please give me a solution
Thanks in advance

First port of call would be to make sure your tibjms.jar is in your classpath; I've seen this instead of 'class not found' errors a couple of times now.

TIBCO EMS + JBOSS

Dear All,
I would like some suggestions regarding tracing a bug while using TIBCO EMS as a JMS Provider in JBoss4.0.4 AS.
The requirement is like this -
I have to put a message into a TIBCO EMS REQUEST queue.
This message is processed by another system
A reply message is put into the TIBCO EMS REPLY queue.
I have to receive this message from this queue.
There is a constraint that I require the same request object for another operation based on the success/failure of the first call. In both the cases, I will get back a valid reply using which I will determine if it is a success or failure. Hence I am not using an MDB, instead, I am using a QueueReceiver.
I could succesfully put a message into the queue, but, could not receive the message from the REPLY queue though EAI put it into that queue. Using a queue monitoring tool, I can see that the reply is there, but cannot receive it.
It gets stuck at receiver.receive();
It continuously listens to the queue. We can rule out any mismatches with JMSCorrelationId because it is fine.
What is surprising is the same code worked perfectly fine until yesterday for more than one month now. And still it works fine if the ear file is deployed in the JBoss server of another machine.
I have not made any changes to my notebook either software or hardware...
Any ideas/thoughts? If attaching the code sample would help, I shall do so. Pls let me know.
Best Regards,
murali

First port of call would be to make sure your tibjms.jar is in your classpath; I've seen this instead of 'class not found' errors a couple of times now.

How to get the number and response time of HTTP request through Weblogic?

hi,
does anybody know how to get the HTTP request information through Weblogic server, such as the number of HTTP request in 1 min and the average response time of request in 5 mins ?
Or is there anyway i can do it through monitoring and get these data then? If so, please help tell me.
Thanks in advance
BTW, we don't have the 3rd-party monitoring tool here.

Hi,
tables: usr02, usr41.
data: OPCODE_MODE_COUNT(1) TYPE X VALUE 3,
      modes like sy-index,
      u_MODES LIKE MODES.
select * from usr02.
select * from usr41 where BNAME = usr02-bname.
    CALL 'ThUsrInfo' ID 'OPCODE' FIELD OPCODE_MODE_COUNT
      ID 'TID' FIELD usr41-TERMID
      ID 'MODES' FIELD MODES.
    IF SY-SUBRC = 0.
      u_MODES = u_MODES + MODES.
    ENDIF.
endselect.
if sy-subrc = 0.
    write:/ usr02-bname, u_MODES.
endif.
clear u_modes.
endselect.

Is there a software in which I can hook up my iPhone 4s to my computer and send and receive text messages and calls (via headset) through my computer?

Is there a software in which I can hook up my iPhone 4s to my computer and send and receive text messages and calls (via headset) through my computer? Whether it's free or cost money, can someone please give me a name of a program or software that allows me to do this? I can't seem to find anything like this for the iPhone.

No.

Error while calling pscp.exe through a batch file which is called in SSIS Execute Process Task

Hi,
I am using Windows Server 2012 R2 Standard, SSIS 2012. I am trying to copy files from a remote location by calling pscp.exe through a batch file (FileCopy.bat at location M:\bin\) which is referenced in a SSIS Execute Process Task. My batch file content
is,
ECHO OFF
echo. >> M:\Prod\bin\SourceFile_FileLog.txt
echo %date% - %time% - Copy Start (XYZ_a201211155952avx0_69999.NOR.gz) >> M:\Prod\bin\SourceFile_FileLog.txt
M:\ProdFiles\bin\pscp.exe -unsafe -scp -pw aaaaa myuser@sourceserver:/ABC_data/*.NOR.gz M:\Prod\FromMediation\
echo %date% - %time% - Copy Complete >> M:\Prod\bin\SourceFile_FileLog.txt
The error I am getting is
[Execute Process Task] Error: In Executing "M:\bin\FileCopy.bat" "" at "", The process exit code was "1" while the expected was "0".
Exactly same setup but using Windows Server 2003 R2 Enterprise and SSIS 2005, this works fine and copies the files successfully.
Please provide some guidance on this.
Thank you!
'In Persuit of Happiness' and ..... learning SQL.

Hi,
This is what I am getting while running the batch file from command prompt
M:\bin\mttrb1>CDR_FileCopy
M:\bin\mttrb1>ECHO OFF
The system cannot find the path specified.
The system cannot find the path specified.
scp: M:\Prod\FromMediation\: Cannot create file
scp: M:\Prod\FromMediation\: Cannot create file
scp: M:\Prod\FromMediation\: Cannot create file
The system cannot find the path specified.
'In Persuit of Happiness' and ..... learning SQL.

Getting error while updating property of image through weblogic CMS

Hii
I want to add alt text and alt title to an existing image through Weblogic Content Management System_ . For that I have used adAltText property of ad content type.
For that I have refer the following link
[ http://docs.oracle.com/cd/E13155_01/wlp/docs103/cm/contentTypesCm.html#wp1096390]
I add values to adAltText. After that clicked on cheach in.
But while doing cheach in in Weblogic Content Management System_ . I am getting following Exception
A RepositoryException was thrown: null
and following is stacktrace:
com.bea.content.virtual.workflow.WorkflowException
     at com.bea.content.virtual.workflow.PublishAction.execute(PublishAction.java:179)
     at com.bea.content.virtual.internal.server.bean.InternalWorkspaceOpsBean.handleWorkflowActions(InternalWorkspaceOpsBean.java:524)
     at com.bea.content.virtual.internal.server.bean.InternalWorkspaceOpsBean.internalCheckIn(InternalWorkspaceOpsBean.java:420)
     at com.bea.content.virtual.internal.server.bean.InternalWorkspaceOpsBean.checkIn(InternalWorkspaceOpsBean.java:343)
     at com.bea.content.virtual.internal.server.bean.WorkspaceOps_xe5vix_ELOImpl.checkIn(WorkspaceOps_xe5vix_ELOImpl.java:166)
     at com.bea.content.virtual.internal.WorkspaceOpsImpl.checkIn(WorkspaceOpsImpl.java:90)
     at com.bea.content.federated.internal.VersionManagerImpl.checkIn(VersionManagerImpl.java:239)
     at com.bea.portal.tools.content.controls.ContentVersionControlImpl.checkIn(ContentVersionControlImpl.java:165)
     at com.bea.portal.tools.content.controls.ContentVersionControlBean.checkIn(ContentVersionControlBean.java:839)
     at content.BaseContent.doCheckinLatestVersion(BaseContent.java:1127)
     at content.BaseContent.handleLibraryOpForSelectedNode(BaseContent.java:1050)
     at content.node.nodeSelected.properties.NodePropertiesController.checkInLatestVersion(NodePropertiesController.java:530)
     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 org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:879)
     at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809)
     at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478)
     at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306)
     at global.internal.AbstractBaseController.internalExecute(AbstractBaseController.java:360)
     at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336)
     at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52)
     at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
     at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
     at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
     at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:91)
     at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
     at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
     at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
     at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
     at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
     at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
     at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
     at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1129)
     at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:687)
     at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
     at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:107)
     at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
     at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
     at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
     at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225)
     at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
     at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
     at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
     at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
     at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
     at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
     at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
     at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
     at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
     at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:686)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at com.bea.jsptools.servlet.PagedResultServiceFilter.doFilter(PagedResultServiceFilter.java:82)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at com.bea.portal.tools.servlet.http.HttpContextFilter.doFilter(HttpContextFilter.java:60)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:336)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3502)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2186)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2092)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Please reply if any one find solution on this.
Edited by: 925203 on Apr 3, 2012 6:34 AM
Edited by: 925203 on Apr 3, 2012 6:35 AM
Edited by: 925203 on Apr 4, 2012 10:41 PM

Yes, I am using custom work flow.
I added new property for alternate text to existing content type Banner. When I try to update value for alternate text it throws error: A RepositoryException was thrown: null
Even if i try to delete added property it throws error :
A RepositoryException was thrown: The type Banner has existing node instances. Therefore the removal of property definition alt is not allowed.
Is there alternate way to add property to existing content type through weblogic content management console?
Edited by: 925203 on Apr 5, 2012 9:48 PM

Calling Tibco EMS through Weblogic

Similar Messages

Maybe you are looking for