Posts Tagged ‘Tibco’

Context

An object is marshallized and sent on TibcoRV 8.1. An instance of Mule ESB 2.2.1 listens to TibcoRV, reads the message, unmarshalls the object and builds an SQL insert query.

The query is very simple:

insert into myTable(dateColumn, stringColumn) values(...)

It is executed in a Jdbc connector declared on Mule configuration file:

    <jdbc:connector name="jdbcConnector" dataSource-ref="mySybaseDB" pollingFrequency="1000">
        <jdbc:query key="writeTest"
                    value="INSERT INTO myTable(dateColumn, stringColumn)
                              VALUES(#[map-payload:myJavaDate],#[map-payload:myJavaString])"/>
    </jdbc:connector>

The DB is Sybase. The first column is of type datetime, the second one is varchar. The values are retrieved from a java.util.Date and a java.lang.String.

Case

When the query is run, I get the error:

java.sql.SQLException: Cannot run this command because Java services are not enabled. A user with System Administrator (SA) role must reconfigure the system to enable Java.

(you may get a com.sybase.jdbc2.jdbc.SybSQLException instead of java.sql.SQLException)

Explanation – Fix

The error is related only to Sybase, and not to TibcoRV and Mule: by default, Sybase cannot manage Java Dates (java.util.Date). You have to start explicitly the Java services. To perform that:

• login with an username owing the rights “sa_role“
• run the SQL query:

  sp_configure 'enable java', 1

• the restart the Sybase server

Now it should work. A similar error may occur with JBoss.

Case

In a JUnit test, I send a message on a TibcoRV, but I get the following error:

TibrvException[error=4,message=Tibrv not initialized]

Fix

In order, proceed as this:

1. check an RVD daemon is running 😉
2. check tibrvj.jar is in your classpath 😉
3. check the instanciation of transport layer new TibrvRvdTransport(service, network, daemon); is done within your public void testXXX(), and not in the setUp().

Context

Mule 2.2.1 ESB config file with a TibcoRV connector, under Windows XP SP2 and Java 5.
The error happened in this context, yet I assume it would occur in any occurence related to XSD / XML schemas.

Error

org.springframework.beans.factory.xml.XmlBeanDefinitionReader: Ignored XML validation warning
org.xml.sax.SAXParseException: SchemaLocation: schemaLocation value = 'http://www.mulesource.org/schema/mule/management/2.2                http://www.mulesource.org/schema/mule/management/2.2/mule-management.xsd                http://www.mulesource.org/schema/mule/core/2.2                http://www.mulesource.org/schema/mule/core/2.2/mule.xsd                http://www.springframework.org/schema/beans                http://www.springframework.org/schema/beans/spring-beans-2.5.xsd                http://www.mulesource.org/schema/mule/core/2.2/mule.xsd                http://www.mulesource.org/schema/mule/vm/2.2                http://www.mulesource.org/schema/mule/vm/2.2/mule-vm.xsd
http://www.mulesource.org/schema/mule/tibcorv/2.2                http://www.mulesource.org/schema/mule/tibcorv/2.2/mule-tibcorv.xsd' must have even number of URI's.

Headers of XML config file:

<mule xmlns=&amp;quot;http://www.mulesource.org/schema/mule/core/2.2&amp;quot;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:spring="http://www.springframework.org/schema/beans"
xmlns:management="http://www.mulesource.org/schema/mule/management/2.2"
xmlns:tibcorv="http://www.mulesource.org/schema/mule/tibcorv/2.2
xsi:schemaLocation="http://www.mulesource.org/schema/mule/management/2.2
http://www.mulesource.org/schema/mule/management/2.2/mule-management.xsd
http://www.mulesource.org/schema/mule/core/2.2
http://www.mulesource.org/schema/mule/core/2.2/mule.xsd
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.mulesource.org/schema/mule/core/2.2/mule.xsd
http://www.mulesource.org/schema/mule/vm/2.2
http://www.mulesource.org/schema/mule/vm/2.2/mule-vm.xsd
http://www.mulesource.org/schema/mule/tibcorv/2.2
http://www.mulesource.org/schema/mule/tibcorv/2.2/mule-tibcorv.xsd">

Explanation – Fix

Each time, the attribute xsi:schemaLocation must have an even number of lines: a “public” XSD address and a “non-public” one. For non English-fluent speakers, I remind that a number is even if, and only if, it is a multiple of 2 ; otherwise it is odd.

In our case, one line is redundant. To fix this issue, you have to remove the redundant line, and ensure each line belongs to a consistent pair of lines: for instance:

http://www.mulesource.org/schema/mule/tibcorv/2.2
and
http://www.mulesource.org/schema/mule/tibcorv/2.2/mule-tibcorv.xsd

Installation

Prerequisites

Priori to following the current tutorial, you must have installed

• a Java JDK/JRE 1.5+, with a parameter JAVA_HOME already set
• a TibcoRV 8.1, with a parameter TIBRV_HOME already set. You can consult a short tutorial here to perform this.

Main

• Get Zip version of “Mule ESB Full Distribution”, version 2.2.1, on this page.
• Unzip the content in a folder, eg: C:\exe\mule-standalone-2.2.1
• Add a environment variable MULE_HOME and update your path, eg:

  set MULE_HOME=C:\win32app\mule-standalone-2.2.1
  set PATH=%PATH%;%MULE_HOME%\bin

• To check the Mule is well installed, you can launch the “Hello World” application:

  %MULE_HOME%\examples\hello\hello.bat

Specific for TibcoRV

• Get mule-transport-tibcorv-2.2.1.jar, available at this link.
• Copy it into %MULE_HOME%/lib/mule
• Get the jar %TIBRV_HOME%\lib\tibrv.jar
• Copy and rename it into %MULE_HOME%/lib/opt/tibrvj-8.1.2.jar
• Tip: to know the exact version of the Jar you have just copied, you can open it, explore and decompile the class com.tibco.tobrv.tibrvj_id. The exact version must appear.
• Copy %MULE_HOME%/conf/wrapper.conf as %MULE_HOME%/conf/wrapper.conf.old
• Edit %MULE_HOME%/conf/wrapper.conf:
  • replace

    wrapper.java.library.path.1=%LD_LIBRARY_PATH%
    wrapper.java.library.path.2=%MULE_HOME%/lib/boot

    with:

    wrapper.java.library.path.1=%LD_LIBRARY_PATH%
    wrapper.java.library.path.2=%MULE_HOME%/lib/boot
    wrapper.java.library.path.3=%TIBRV_HOME%/bin

Here is for the very configuration.

“Hello world” for “TibcoRV via Mule”

Configuration file for Mule/TibcoRV “Hello World”

Code below is commented. Save it into a file named mule-config.xml.

<?xml version="1.0" encoding="UTF-8" ?>
<mule xmlns="http://www.mulesource.org/schema/mule/core/2.2"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xmlns:spring="http://www.springframework.org/schema/beans"
 xmlns:management="http://www.mulesource.org/schema/mule/management/2.2"
 xmlns:tibcorv="http://www.mulesource.org/schema/mule/tibcorv/2.2"
 xmlns:stdio="http://www.mulesource.org/schema/mule/stdio/2.2"
 xsi:schemaLocation="http://www.mulesource.org/schema/mule/management/2.2
 http://www.mulesource.org/schema/mule/management/2.2/mule-management.xsd
 http://www.mulesource.org/schema/mule/core/2.2
 http://www.mulesource.org/schema/mule/core/2.2/mule.xsd
 http://www.springframework.org/schema/beans
 http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
 http://www.mulesource.org/schema/mule/vm/2.2
 http://www.mulesource.org/schema/mule/vm/2.2/mule-vm.xsd
 http://www.mulesource.org/schema/mule/tibcorv/2.2
 http://www.mulesource.org/schema/mule/tibcorv/2.2/mule-tibcorv.xsd
 http://www.mulesource.org/schema/mule/stdio/2.2
 http://www.mulesource.org/schema/mule/stdio/2.2/mule-stdio.xsd">
 <!-- The TibcoRV we're listening is on the IP#127.0.0.1 -->
 <tibcorv:connector name="myTibcoConnector" network="127.0.0.1"/>
 <model name="fromTibco2stout">
 <service name="fromTibco">
 <inbound>
 <!-- We follow all subjects, on the TibcoRV connector defined above-->
 <tibcorv:inbound-endpoint connector-ref="myTibcoConnector" subject="*"/>
 </inbound>
 <echo-component/>
 <outbound>
 <pass-through-router>
 <!-- Messages received are displayed on standard output -->
 <stdio:outbound-endpoint address="stdio://OUT"/>
 </pass-through-router>
 </outbound>
 </service>
 </model>
</mule>

Run TibcoRV

Launch the daemon

Launch the daemon on localhost on port 7580:

%TIBRV_HOME\bin\rvd -http 7580

Launch a listener

Possibly, you can run a listener in a separate frame, in order to double check whether messages are sent and received in the right way, independantly of what happens on Mule side.
Listen to all messages with subject mySubject on localhost:7580

%TIBRV_HOME\bin\tibrvlisten.exe" -network localhost mySubject

Launch the Mule

• Now run the ESB:

  %MULE_HOME%\bin\mule.bat -config path\to\file\mule-config.xml

• Send a message:

  %TIBRV_HOME\bin\tibrvsend.exe -network 127.0.0.1  mySubject HelloWorld

• Expected outputs:
  • On sending frame:

    Publishing: subject=mySubject "HelloWorld"

  • On listening frame:

    tibrvlisten: Listening to subject mySubject
    2010-01-21 17:51:43 (2010-01-21 16:51:43.109000000Z): subject=mySubject, message={DATA="HelloWorld"}

  • On Mule ESB frame:

    INFO  2010-01-21 17:53:02,860 [Bus] org.mule.transport.tibrv.TibrvMessageReceiver: message received
    on: *
    INFO  2010-01-21 17:53:02,860 [fromTibco.4] org.mule.transport.tibrv.TibrvMessageAdapter: The newThreadCopy method in AbstractMessageAdapter is being used directly. This code may be susceptible to 'scribbling' issues with messages. Please consider implementing the ThreadSafeAccess interface in the message adapter.
    INFO  2010-01-21 17:53:02,860 [fromTibco.4] org.mule.component.simple.LogComponent:
    ********************************************************************************
    * Message received in service: fromTibco. Content is: '{                       *
    * DATA="HelloWorldOfTheWorld" }'                                               *
    ********************************************************************************
    INFO  2010-01-21 17:53:02,860 [connector.stdio.0.dispatcher.3] org.mule.transport.stdio.StdioMessageDispatcher: Connected: endpoint.outbound.stdio://OUT
    {DATA=HelloWorldOfTheWorld, __send__subject__=mySubject}

When I was introduced to TIBCO Rendezvous (also spelled “Tibco Rendez-Vous” or, shorterly, “TiboRV”), I faced a embarrassing issue: the lack of documentation and tutorials on the web.

The purpose of this -short- tutorial is to guide you until you can send and read a “HelloWorld” message passing through Tibco RendezVous

Installation

• Set the variable JAVA_HOME
  Eg, in my case:

  set JAVA_HOME=C:\exe\java\jdk150_10

• Get the file to be installed:
  TIB_rv_8.1.2_win_x86_vc8.zip
• Unzip the content in your local drive
• Launch the installer (.exe)
  • select Custom installation
  • choose the installation folder, eg: C:\exe\tibco
  • keep default options for other requests
• Set the variable TIBRV_HOME
  Eg, in my case:

  set TIBRV_HOME=C:\exe\tibco\tibrv\8.1

Main Runnables

RVD: Daemon

• Launching the daemon on local host on port 8181 (default port: 7580):

  rvd -http 8181

  You should see the following trace:

  C:\exe\tibco\tibrv\8.1\bin>rvd -http 8181
  
  TIB/Rendezvous daemon
  Copyright 1994-2008 by TIBCO Software Inc.
  All rights reserved.
  
  Version 8.1.2 V8 9/26/2008
  2010-01-19 16:37:02 rvd: Command line: rvd -http 8181
  2010-01-19 16:37:02 rvd: Hostname: MYLOCALMACHINE
  2010-01-19 16:37:02 rvd: Hostname IP address: 123.123.123.123
  2010-01-19 16:37:02 rvd: Detected IP interface: 123.123.123.123 (IP00)
  2010-01-19 16:37:02 rvd: Detected IP interface: 127.0.0.1 (loopback)
  2010-01-19 16:37:02 rvd: Unable to find ticket file tibrv.tkt in PATH
  2010-01-19 16:37:02 rvd: Http interface - http://myLocalMachine.myDomain:8181/

tibrvsend: send a message

To send a message on myLocalMachine:7580:

.\tibrvsend.exe -service 7580 -network MYLOCALMACHINE mySubject myMessage

Expected output:

C:\exe\tibco\tibrv\8.1\bin>.\tibrvsend.exe -service 7580 -network MYLOCALMACHINE mySubject myMessage
Publishing: subject=mySubject "myMessage"
2010-01-19 16:52:11 RV: TIB/Rendezvous Error Not Handled by Process:
{ADV_CLASS="WARN" ADV_SOURCE="SYSTEM" ADV_NAME="LICENSE.EXPIRE" ADV_DESC="The license will expire" expiretime=2010-01-19 16:02:11Z host="10.30.226.147"}

tibrvlisten: listen to messages

Abstract

To listed to messages published on MYLOCALMACHINE:7580, related to subject mySubject:

tibrvlisten -service 7580 -network MYLOCALMACHINE mySubject

Use case: HelloWorld

For instance, let’s assume that you launch this command from one frame:

C:\exe\tibco\tibrv\8.1\bin>.\tibrvsend.exe -service 7580 -network localhost mySubject HelloWorld
Publishing: subject=mySubject "HelloWorld"

Here is what appears in the “listening” frame:

2010-01-19 17:01:32 (2010-01-19 16:01:32.990000000Z): subject=mySubject, message={DATA="HelloWorld"}

Notice you can have many instances listening to the same messages.

Other runnables

Launch the daemon manager

• Launch:

  cd %TIBRV_HOME%/RVDM
  ./RVDM.bat -http 8282 .

• You should see following messages, that you can ignore:

  2010-01-19 13:01:48 rvdm: RVDM has activated.
  2010-01-19 13:02:03 RV: TIB/Rendezvous Error Not Handled by Process:
  {ADV_CLASS="WARN" ADV_SOURCE="SYSTEM" ADV_NAME="LICENSE.EXPIRE" ADV_DESC="The license will expire" e
  xpiretime=2010-01-19 12:11:48Z host="123.123.123.123"}

• To check the daemon is on, you can open the address http://localhost:8282 on your favorite browser.

Example sources

Example sources are available in folder %TIBRV_HOME%/src/examples/java

Misc

TIBRV_HOME\bin folder fosters a couple of binaries:

• rvntscfg.exe: Services Configuration Program