Posts tagged ·



TIBINS202504 Error: You do not have the required administrator privileges


TIBINS202504 Error ScreenshotWhen running 32-bit TIBCO Installer on x64 platform, you may encounter this error TIBINS202504 INTERNAL ERROR: You do not have the required administrator privileges for the Install Wizard to proceed with installation. Then following window appears, which contains more useful information: java.lang.UnsatisfiedLinkError win32ppk.dll Can’t load IA 32-bit .dll on a AMD 64-bit platform.

To solve this problem, you have to run installer with 32-bit Java. There are two options: you can temporarily point JAVA_HOME system variable to 32-bit Java folder or run installer with -is:javahome parameter like in my example:

TIB_adswift-simple_5.8.0_win_x86.exe -is:javahome "C:\Program Files (x86)\Java\jre6"

Updated releases are ready for download


TIBCO-Universal-InstallerNew TIBCO Runtime Agent Software 5.7.0 has been released, include:

  • TIBCO Rendezvous 8.3.0
  • TIBCO Enterprise Message Service 6.0.0 Client Libraries
  • TIBCO Hawk 4.9.0
  • TIBCO Designer 5.7.0
  • TPCL 5.7.0

As well as TIBCO ActiveMatrix BusinessWorks 5.9.0 and TIBCO Administrator 5.7.0. Now with full support of Windows Server 2003 R2 (x86, x86-64), Windows Server 2008 R2 (x86-64), Windows 7 (x86, x86-64). Also now we have 64-bit version of each product for Solaris SPARC and x86.

You can find everything you need on the according to your subscription. So, if you still dreaming of your new TIBCO environment – this is the right time to do that!

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.

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")"`

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
  • Adding Subversion users and change folders owners:
    # cd /opt/tibco/ems/ca/1.0/repos/conf
    # cat pre-commit.perms

    So, ‘admin’ is already here. Next check/set owner for the repos and temp Subversion’s folders:
    # pwd
    # 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://
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 iProcess engine installation on Solaris

1 comment

This is my quick reference for single-server TIBCO BPM iProcess engine installation on Solaris. Possible to add another server and convert environment to a cluster later. Oracle has to be installed, ORACLE_HOME and ORACLE_SID environment variables must be set. Run swinstall installation script as a root user who also DBA in Oracle, script will create iProcess database.


Script will collect installation data:
Installing TIBCO iProcess Engine version 11.0.2

Location, Identification and OS Accounts Menu

* ) Installation Directory : /export/home/tibco/tibco/iprocess
2 ) iProcess Engine Nodename : s-bpm01
3 ) iProcess Engine Licensee Name : TIBCO iPE 11.0.2 Install
4 ) iProcess Engine Background User Name : pro
5 ) iProcess Engine Administration User Name : swadmin
6 ) iProcess Engine User Group Name : staffwar

ORACLE Database Connection and Account Details

1 ) Oracle DB TNS Identifier : orcl
2 ) Oracle DB Administrator Name : system
3 ) Oracle DB Administrator Password : ********
4 ) iProcess Engine DB Schema Owner Name : swpro
5 ) iProcess Engine DB Schema Owner Password : staffpro1
6 ) iProcess Engine DB User Name : swuser
7 ) iProcess Engine DB User Password : swuser1
8 ) Data Tablespace Name : STAFFWAR
9 ) Temporary Tablespace Name : TEMP
10) Schema Sizing Configuration : Small

Display configuration summary and start installation:
Configuration Summary

Install type: install (MASTER)
Version: 11.0.2
Target location: /export/home/tibco/tibco/iprocess
Licensee: TIBCO iPE 11.0.2 Install

iProcess Objects Server Version: 11.0.2
iProcess Objects Director Version: 11.0.2

Node Details
Node name: s-bpm01
Client-Server RPC port: 391875

Environment Settings
iProcess Engine User group: staffwar
iProcess Engine bkg. account: pro
iProcess Engine admin. account: swadmin

Optional Settings
Autostart Server: Y
Passwords required for login: Y
Enable Prediction (Global): N
Enable Case Data Normalization: Y
Enable Activity Publishing: N
Configure iProcess E-Mail Plug-in: Y
Enable iProcess Objects Server: Y
Enable iProcess Objects Director: N
Install TIBCO Hawk 4.8.1: N
Enable Webdav write access: N

DataBase Settings
Database Type: ORACLE
TNS Identifier: orcl
DBA Name: system
DB Schema Owner: swpro
DB User: swuser
Data Tablespace: STAFFWAR
Temp Tablespace: TEMP

The final step:
Your TIBCO iProcess Engine installation has now been configured as follows:

Machine ID Machine Name Master Check Error Files Machine Comment
1 S-BPM01 Y Y s-bpm01

Checking and setting file permissions ...

TIBCO iProcess Engine Installation Complete

Display engine password:
TIBCO iProcess Engine Password is:
* 3BFD-7292-DBAF-A3E7-823D-4720-351E *
Licensee Name is:
TIBCO iPE 11.0.2 Install
(The existing TIBCO iProcess Engine Password and Licensee Name may also be
displayed later by running 'swconfig').

All users of TIBCO iProcess Engine (Staffware) should have the
environment variable $SWDIR set to
before invoking or starting TIBCO iProcess Engine.

Installer will run the final check and complete:
TIBCO iProcess Engine Nodename ( s-bpm01 ) checked OK.
TIBCO iProcess Engine RPC Number ( 391875 ) checked OK.
TIBCO iProcess Engine service ports checked OK
TIBCO iProcess Engine process entries OK

Then I have to create this .profile for pro user:
export SWDIR

To start iProcess engine:
su - pro
cd bin
./swstart -p

Admin tool:
su - pro
cd util

Installing TIBCO on Windows Failover Cluster – part 4

no comments

Continued from part 1, part 2, part 3. Now I ready to add my virtual cluster host TST00-TIB01 to TIBCO Domain. I will start DomainUtility (D:\tibco\tra\5.6\bin\domainutility.exe) on the first (Master) node and select Machine Management => Add Machine. Then change machine name to cluster resource name TST00-TIB01, specify TIBCO EMS tcp://TST00-TIB01:7223 as a transport, enter admin credentials for domain and for EMS, and press “Discover..”. My domain TIB01 will be discovered. Then mark “Machine is Logical” checkbox and enter its virtual IP address as it is in cluster. After confirmation, virtual host TST00-TIB01 will be in the domain and new Hawk Agent service will be created. Now I can start this service.

In the TIBCO Administrator new machine will appear, but first node shown as disconnected. It is happened as Hawk Agent which is responsible for this node was uninstalled and replaced by new TST00-TIB01 Agent. I will fix this later. Now I will initialize TIBCO EMS plugin to manage both EMS in Administrator.

To do that I will start DomainUtility again and select TIBCO EMS Plugin => Add TIBCO EMS Server. Then I will select domain and enter admin credentials, specify machine, where is my EMS is running, provide information about EMS itself. On the confirmation screen I can test connection to the EMS to be sure that all provided info is OK. As everything was fine and server was successfully added to domain, I will do the same for the second EMS. After that, both EMS shown in the Administrator as running service instances and now is possible to manage them using TIBCO Administrator GUI.

As my process is going well, I can start moving TST00-TIB01 Hawk Agent from services on the master node to cluster resources. First of all I will stop this service and copy whole content of D:\tibco\tra\domain\TIB01 folder to T:\tibco\tra\domain\TIB01 folder. Then it is necessary to correct all paths related to TST00-TIB01 in hawkagent_TIB01.tra file. Also check and replace related paths in hawkagent.cfg file.

This Hawk Agent application should be added as a cluster resource. To do that, I will open Cluster Management Console and select Add a resource => Generic Application, and enter path to the Agent binary. After confirmation, new resource will be created. In its properties, I will mark “Use network name for computer name” checkbox and define dependences: cluster volume where Agent’s files are, IP address and binded name, EMS 7223 as it provides service transport for this agent also. To continue, bring this Agent online. TST00-TIB01 status is OK now in TIBCO Administrator.

On the next step is special wrapped application has to be installed in cluster for both EMS. It will be used by Hawk Agent to query EMS status and display in TIBCO Administrator. Path to binary file and parameters you can see on the screenshot. Next, in properties I will mark “Use network name for computer name” checkbox and define dependences: hawkagent_TIB01 and EMS Server 7222. Then I will install second wrapper for second EMS: accordingly propFile will be TIBCOServers-EMS_7223.tra and in dependences will be same hawkagent_TIB01 and EMS Server 7223.

After all, everything has to be green, this is final picture for cluster.

Last step is restore Hawk Agent on the first (Master) node. I will start DomainUtility (D:\tibco\tra\5.6\bin\domainutility.exe) again on the first node and select Machine Management => Add Machine. Machine name should be S-TST01-TIB01 now. If transport and credentials are valid, domain TIB01 will be discovered. After confirmation, Hawk Agent on this server will be replaced back to original for the first node. I will start this service, then both nodes and cluster name should be green in TIBCO Administrator.

My newly created TIBCO Domain is ready to serve TIBCO BusinessWorks applications that can be installed as fault tolerant pairs on both nodes. Everything should work fine in this configuration in case any one node fails.