tibco

Java Webstart with Tibco Native Libs

流过昼夜 提交于 2019-12-07 03:30:39
问题 I am trying to deploy an application that uses the native implementation of Tibrv through the TibrvJ library using Java Webstart . I have packaged up all of the Windows dlls from inside c:\tibco\tibrv\bin into a Jar file and have added these to the nativelib element in the JNLP file. I was hoping that webstart would take the dll files from the tibco-7.5.1-nativelibs.jar file and allow them to be loaded via System.loadLibrary which is called from Tibrv.open() . However it doesn't seem to want

How to parse unresolved result set in Tibco BW JDBC palette

江枫思渺然 提交于 2019-12-07 02:59:26
I need to connect to remote MS SQL server stored procedure from Tibco BW JDBC palette to retrieve a result set where we won't be knowing the result set column names. In my local environment I had mocked the procedure to return the expected result set but with dummy column names. Hence while parsing the unresolvedResultSet, error is thrown if the column name in the result set is other than the one defined in the output. If i use 'result set as schema' option then also its throws error while parsing the result set if the column name is different. Is there any way to fix this in Tibco BW? Thanks

How to monitor outgoing messages from TIBCO EMS .Net client? [closed]

痞子三分冷 提交于 2019-12-06 16:40:05
Closed. This question is off-topic . It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed last year . While using the .Net client TIBCO EMS, How to monitor outgoing messages from my .Net Tibco client? I'm going to send Application-level, not jms-level, acknowlegements and replies. How can I tell If the application sent them or not? If the client failed to send a message will it throw an exception or store the message to try again later? Bottom line, Is there any tool enables me to monitor activities(outgoing) from

All I have is a Tibco.EMS.dll, what else do I need? [closed]

[亡魂溺海] 提交于 2019-12-06 07:35:32
Closed . This question needs details or clarity . It is not currently accepting answers. Want to improve this question? Add details and clarify the problem by editing this post . Closed 6 years ago . All I have is a Tibco.EMS.dll version 5.1.4.0 for .NET, what else do I need? Anyone know where I can download a manual? Do I need anything else like like other DLLs or config files? Any help would be appreciated. Thanks It all depends on what you are trying to do. We also have the Tibco TEMS DLL which is the WCF extensions for EMS. This allows you to configure you endpoints directly in Web.config

why do we use tibco mapper activity?

空扰寡人 提交于 2019-12-06 05:25:23
The tibco documentation says The Mapper activity adds a new process variable to the process definition. This variable can be a simple datatype, a TIBCO ActiveEnterprise schema, an XML schema, or a complex structure. so my question is tibco mapper does only this simple function.We can create process variables in process definition also(by right clicking on process definition).I looked for it in google but no body clearly explains why to use this activity and I have also tried in youtube and there also only one video and it does not explain clearly.I am looking for an example how it is used in

Java Webstart with Tibco Native Libs

走远了吗. 提交于 2019-12-05 08:47:13
I am trying to deploy an application that uses the native implementation of Tibrv through the TibrvJ library using Java Webstart . I have packaged up all of the Windows dlls from inside c:\tibco\tibrv\bin into a Jar file and have added these to the nativelib element in the JNLP file. I was hoping that webstart would take the dll files from the tibco-7.5.1-nativelibs.jar file and allow them to be loaded via System.loadLibrary which is called from Tibrv.open() . However it doesn't seem to want to work properly. My JNLP file looks like this: <?xml version="1.0" encoding="utf-8"?><!DOCTYPE jnlp

What should the client do while the TIBCO EMS server attempts failover?

混江龙づ霸主 提交于 2019-12-05 04:54:22
问题 The TIBCO EMS user's guide (pg 292) says: The backup server will work indefinitely to either A) become the primary server or B) reconnect to the primary server. It also says clients may receive fail-over notification when the switch is successful (see also TIBCO EMS .NET reference pg 220). I have some questions spinning off of these facts... What kind of errors occur on the client side while the servers are attempting fail-over/reconnect? What is the appropriate response from the client? Get

Configuration of tibco jms with Spring

♀尐吖头ヾ 提交于 2019-12-05 00:29:02
问题 Now I have java code which starts tibco jms subscription with several steps: Properties props = new Properties(); props.put("java.naming.provider.url", namingProvider); props.put("java.naming.factory.initial", namingFactory); props.put("java.naming.referral", namingReferral); props.put("java.naming.security.credentials", securityCredentials); props.put("java.naming.security.principal", securityPrincipal); context = new InitialContext(props); TopicConnectionFactory tfactory =

How tibco is useful to organizations and why it is used?

被刻印的时光 ゝ 提交于 2019-12-03 03:39:55
I am interested in learning tibco.I have found some good videos in youtube but all those are only tutorials.None of the videos answer why tibco is used in organizations and how it is useful to the same.I saw some tutorials in webservices and yes we can do the same using java. I am basically from java background and have quite good experience in webservices.I saw some tutorials in tibco regarding web services and they are using soap palletes. Not only for web services I have also seen tutorials for jdbc pallettes.In java also we have jdbc.so many questions arise in my mind and one of the

Does the TIBCO EMS server manage reconnection? or does the client?

懵懂的女人 提交于 2019-12-01 08:12:38
问题 The TIBCO EMS .NET reference guide says (pg 134) To enable reconnection behavior and fault tolerance, the serverURL parameter must be a comma-separated list of two or more URLs. In a situation with only one server, you may supply two copies of that server’s URL to enable client reconnection (for example, tcp://localhost:7222,tcp://localhost:7222). The TIBCO EMS user's guide (pg 292) talks about failover scenarios, client notification, and automatic transfer of clients to the backup server,