Posts tagged ·

tibco

·...

Could not create the Java virtual machine

1 comment

You may encounter this problem when installing TIBCO products on Solaris x86. In my case it was Runtime Agent 5.6.0 installation.

./TRA.5.6.0-suite_sol10_x86.bin -console

Then installation fails and the error message looks like this:

Unrecognized option: -cp:TRA.5.6.0-suite_sol10_x86.jar:TRA.5.6.0-simple_sol10_x86.jar:tibrv.8.1.1-simple_sol10_x86.jar:jre.1.5.0-simple_sol10_x86_64.jar:Designer.5.6.0-simple_sol10_x86_64.jar:tpcl.5.6.0-simple_sol10_x86.jar:hawk.4.8.1-simple_sol10_x86_64.jar:/var/tmp/isjCAAWCa4en/TRA.5.6.0-suite_sol10_x86.jar:
Could not create the Java virtual machine.

There is a bug in the installer, as a workaround you can force the installer to use Java in the system. Just specify -is:javahome option like in my example:

./TRA.5.6.0-suite_sol10_x86.bin -console -is:javahome /usr/jdk/jdk1.5.0_24/

Should work now.

TIBCO ActiveMatrix vulnerability

no comments

Yesterday TIBCO announced security vulnerability in TIBCO ActiveMatrix Products. ActiveMatrix Runtime and Administrator components contain a critical vulnerability in the handling of JMX connections. An attacker with access to an affected system could gain administrative control over the system, allowing the attacker to execute arbitrary code on any host that is a participant in the system.

TIBCO has released updated versions of the affected software products. If an upgrade is not possible, use a firewall to restrict access to the ActiveMatrix Runtime and Administrator components.

Additional information and list of affected products versions here.

TIBCO is looking for Product Manager TIBBR

no comments

Just found on LinkedIn that TIBCO is looking for Product Manager TIBBR. Hope they will actively develop this tool in the near future.

Product Manager TIBBR will serve internally as liaisons within and between engineering, support, sales, field technical services, finance, legal and fulfillment. Product Manager TIBBR serves externally as liaisons between TIBCO’s product groups and TIBCO’s customers and field staff.

Product Manager TIBBR serve as an internal advocate for their product, disseminating information about products within TIBCO (e.g., to peer engineering groups, to professional services, to support, etc.) through collateral, presentations, meetings and one-to-one engagements. Activities include providing support for pre-sales and sales teams, as well as professional services and solution architecture groups, through presentations, written collateral, and product demos, in both strategic and tactical situations.

Installing the TIBCO EMS Central Administration Client

no comments

To following my previous post about EMS Central Administration installation, this part is about client.

There is the same Universal Installer by TIBCO, it helps to make installation process easy. Execute it, accept the license agreement, create a new or select an existing environment, check the summary and complete the installation.

TIBCO EMS Central Administration ClientThen I can star EMSCA from my Start menu. This is Eclipse, I have to create a new workspace. Then File => New EMS Central Administration Project. Enter host name and port, where is EMSCA Server is installed. Enter username and password to connect, select the deployment to create a project for.

Next step is synchronizing with EMS. TIBCO EMS => Synchronize Configurations With EMS Servers. Enter username and password, select EMS server to synchronize.

Now I can change the server configuration. Then save to SVN repository. TIBCO EMS => Save Configurations to Repository.

Then it is possible to deploy changes to the server. TIBCO EMS => Deploy EMS Project.

So, this was short description of the TIBCO EMS Central Administration, very helpful tool to manage configurations of multiple EMS instances.

Installing the TIBCO EMS Central Administration Server

1 comment

I’d like to share my experience about installation of the TIBCO Enterprise Message Service Central Administration (EMSCA) server and client. At this time, TIBCO provides EMSCA server software only for Linux (Red Hat Enterprise Linux 4 and 5 (x86), Oracle Enterprise Linux 4 and 5 (x86) and SUSE Enterprise 10 (x86)) and EMSCA client only for Windows, but as client is Eclipse based, I think that it could be ported easily.

I will start with the server side installation on my Red Hat Linux. The new TIBCO Universal Installer can run in GUI (default), console or silent mode. If you prefer GUI, don’t forget to set DISPLAY:
LOGINFROM=`who am i | cut -f2 -d"(" | cut -f1 -d")"`
DISPLAY=${LOGINFROM}:0.0
export LOGINFROM DISPLAY

Run the installer # ./TIBCOUniversalInstaller-lnx-x86.bin, accept the license agreement, create a new or select an existing environment. Installation will perform quickly. When installation is complete, it is necessary to do some post installation tasks:

  • Environment variables from the file <emsca_home>/1.0/bin/setenv must be set. Perhaps it is good idea to call this file from the user’s profile or add content of this file to the profile;
  • Make Apache run as the user ‘nobody’:
    # cd <emsca_home>/1.0/httpd/conf
    # vi httpd.conf
    User nobody
    Group nobody

    and make sure that user and group ‘nobody’ are in the system;
  • Configure an authentication in Apache:
    # vi httpd.conf
    AuthBasicProvider file
    AuthUserFile conf/users.txt

    Then prepare users file, I will define the ‘admin’ user only:
    # cd ../bin
    # ./htpasswd -c ../conf/users.txt admin
    New password:
    Re-type new password:
    Adding password for user admin

    Then check the file:
    # cd ../conf/
    # cat users.txt
    admin:GfwLuEIw320SY
  • Adding Subversion users and change folders owners:
    # cd /opt/tibco/ems/ca/1.0/repos/conf
    # cat pre-commit.perms
    admin

    So, ‘admin’ is already here. Next check/set owner for the repos and temp Subversion’s folders:
    # pwd
    /opt/tibco/ems/ca/1.0
    # chown -R nobody:nobody repos temp

    Owner should be the same user as running apache (‘nobody’ in my case).

Then I can start emsca:
# emsca start
Starting TIBCO EMS Central Administration
Started Apache httpd: pid=20119
Started Tomcat: pid=20140

and check Apache logs in the <emsca_home>/1.0/httpd/logs folder.

Next step is to create a new deployment server. Deployment server is one per project, can be one for many EMS.
# emsca server create rhl01
Created directory 'rhl01' in the repository
Created directory /opt/tibco/ems/ca/1.0/servers/rhl01
Created configuration file '/opt/tibco/ems/ca/1.0/servers/rhl01/conf/configuration.xml'
Created deployment server 'rhl01'

Now creating a new central administration agent. One agent per one EMS.
# emsca agent create rhl01 name=agent_EMS-SERVER1 path=/ems-server1.emsserver url=tcp://10.2.148.82:7222
Created agent on deployment server 'rhl01'

It is possible to provide a username and a password to connect to the EMS. If is not included, the agent uses ‘admin’ ad username and an empty password. ems-server-username – the username used to connect to the tibemsd, ems-server-password – used with ems-server-username to connect to the tibemsd. Also it has options to grant agent some additional rights, find in the docs.

To check EMSCA server use:
# emsca list
TIBCO EMS Central Administration
Deployment Servers
------------------
rhl01 (started)

# emsca status
TIBCO EMS Central Administration Status
Apache httpd is running: pid=1427
Tomcat is running: pid=1448

In the next post I will describe the client part installation and configuration.

TIBCO EMS 6.0

4 comments

TIBCO Enterprise Message Service 6.0 has been released in July 2010.
Some new features:

  • mstore – new message store type, which designed for quick EMS recover after failover;
  • new parameters for incoming message size, swapping and redelivery delay;
  • cursoring through topics and queues lists in tibemsadmin tool;
  • new startup script to quickly start with default configuration;
  • host id and message size now included in message tracing;
  • new methods in APIs for failover notification and message recovery.

This release requires database schema update when migrating database store from EMS version 5.x.

TUCON 2010 Vivek Ranadivé’s Keynote Speech

no comments