Академический Документы
Профессиональный Документы
Культура Документы
Mechanics of Configuration:
The EMS server reads configuration files only once, when the server starts. It
ignores subsequent changes
to the configuration files. If you change a configuration file, use the
shutdown command from the EMS
Administration Tool to shutdown the server and then restart the server.
One of the main purposes of the JMS message properties is to apply filters
against the message properties. The filters are applied against the header
and properties. JMS refers to these filters as message selectors.
The selector function transfers the filtering work from the application to the
infrastructure. This infrastructure filtering reduces the processing overhead
from the application. However, it should be noted that this increases the
processing overhead on the messaging infrastructure!
This can be important in the planning of physical layout of server structure.
For example, the use of selector functions does not actually shift load from
application hardware to the infrastructure hardware if JMS and the application
server are running on the same machine.
Selector functions are also useful when used in conjunction with queue
browser functions. When the server topology changes, such as JMS gets their
own paired servers, saving processing overhead in the application by using
selector functions may result in performance increase of the orchestration
server.
The command line interface of the administration tool allows you to perform
a variety of functions. The following lists of command usefull for Ems.
purge topic : Purge all messages for all subscribers on the named
topic
syntax : purge topic <topic-name>
example: purge topic t1
create queue : Creates a queue with the specified name and properties.
The possible queue properties are described in Destination Properties.
Properties are listed in a comma-separated list, as described in queues.conf.
You can set the properties directly in the queues.conf or by means of the
setprop queue command in the EMS Administrator Tool.
syntax : create queue <queue_name> <[properties]>
example: create queue q1
Note: why durable: By default, subscribers only receive messages when they
are active. If messages arrive on the topic
when the subscriber is not available, the subscriber does not receive those
messages.
The EMS APIs allow you to create durable subscribers to ensure that
messages are received, even if the message consumer is not currently
running. Messages for durable subscriptions are stored on the server as long
as durable subscribers exist for the topic, or until the message expiration
time for the message has been reached, or until the storage limit has
been reached for the topic. Durable subscribers can receive messages from
a durable subscription even if the subscriber was not available when the
message was originally delivered.When an application restarts and recreates
a durable subscriber with the same ID, all messages stored on the server for
that topic are published to the durable subscriber.
1. Login
2. Create Queue
OR
Note:From now we will work in the Backup Folder, open tibemsd.conf file in
the folder
users=c:\tibco\ems\bin\Backup\users.conf
groups=c:\tibco\ems\bin\Backup\groups.conf
topics=c:\tibco\ems\bin\Backup\topics.conf
queues=c:\tibco\ems\bin\Backup\queues.conf
acl_list=c:\tibco\ems\bin\Backup\acl.conf
factories=c:\tibco\ems\bin\Backup\factories.conf
routes=c:\tibco\ems\bin\Backup\routes.conf
bridges=c:\tibco\ems\bin\Backup\bridges.conf
transports=c:\tibco\ems\bin\Backup\transports.conf
tibrvcm=c:\tibco\ems\bin\Backup\queues.conf
durables=c:\tibco\ems\bin\Backup\durables.conf
If you observe the tibemsd.conf file in primary server and compare the
tibemsd.conf file in Backup server
The values for some parameters in primary tibemsd.conf file is jfor example
"users=users.conf" where as in backup server tibemsd.conf file we give
"users=c:\tibco\ems\bin\Backup\users.conf".The reason why because while
installing the Ems server ,it sets these values and it knows where to look for
the path , so thats the reason why the full path is not mentioned for various
parameters in tibemsd.conf for primary server
Start sending the messages from Publisher to a queue and Start a receiver
who is listening to this queue.
Stop the primary server by entering the command Shutdown in command
prompt,this will cause the server to shutdown
You can observer that backup server becomes Active in the command
prompt, without disrupting the Business Process.
Now start the primary server you will see that this will be in stand-by mode.
This topic deals with configuring both Primary and Load Balanced Server
Note:All the parameters will be in Bold and Italic that you are going to use for
Load Balancing
In this we are going to use 3 files which are given below for configuring
Primary server
1) tibemsd.conf
2) routes.conf
3) factories.conf
Open tibemsd.conf file and input the parameters with the Values
Server=EMS-SERVER1(This value can be anything)
Routing=enabled(Thisvalue should be same )
store=datastore(which contain 3 files sync-db,async-db,meta-db)
Save the file and exit
Open routes.conf file and input the parameters with the values,
Note: if the paramter is not there add it.
When you go to bottom of this file you will find the below parameters
Important Note:
#
# If factory's url is specified in the form
#
# url = tcp://7222 (or any other port number)
#
# then it is expanded during JNDI lookup to include the default
# hostname of the machine running tibemsd server, for example:
#
# tcp://MYHOST:7222
#
# This enables the use of the same factories.conf file on different
# hosts. However, note that only default host name will be used. On
# servers with multiple interfaces you need to use explicit host name
# in factories url if it should be not the default name.
#
# Factories using 'localhost' as the host name only work when the client
# and server are on the same computer. You will need to replace
# 'localhost' below with the the appropriate hostname of the machine
# where the server is running.
Add the following parameters, these parameters are not there in the file
[LBTopicConnectionFactory]
url=tcp://7222|tcp://7144 (From the above note actual production scenario
use url=tcp://Machine1:7222|tcp://Machine2:7144)
metric=connections
[LBQueueConnectionFactory]
url=tcp://7222|tcp://7144 (From the above note actual production scenario
use url=tcp://Machine1:7222|tcp://Machine2:7144)
metric=connections
Save and exit the configuration file
The 2 files that we are going to use for Load Balancing server
is tibemsd.conf and routes.conf files
server=Ems-server2
Listen=tcp://7144
users=c:/tibco/ems/bin/LB/users.conf ( Note:or go for this path "\" if the other
doesn't work)
groups=c:/tibco/ems/bin/LB/groups.conf
topics=c:/tibco/ems/bin/LB/topics.conf
queues=c:/tibco/ems/bin/LB/queues.conf
acl_list=c:/tibco/ems/bin/LB/acl.conf
factories=c:/tibco/ems/bin/LB/factories.conf
routes=c:/tibco/ems/bin/LB/routes.conf
tibrvcm=c:/tibco/ems/bin/LB/tibrvcm.conf
durables=c:/tibco/ems/bin/LB/durables.conf
store=c:/tibco/ems/bin/LB/datastore2
Go to the bottom of the file and modify them as below if anything is there or
add it if it is not there (Reason for this is we just copied the files that have
been chaned for primary server)
[EMS-SERVER1]
url=tcp://7222(This value sould be of primary server listen port)
zone_name=default_mhop_zone
zone_type=mhop
Read the next post Ems-Load Balancing Setup B for testing the LB
Servers.
LoadBalance Setup-B
Instructions:
Putty into linux machine using your personal account and create a
/tmp/ems folder.
Using SECUREFX, copy EMS 4.4.0 and EMS 4.4.1 software folders from
Windows Shared Drive \\TIBCOSoftware\Linux\ to LINUXMACHINE -
/tmp/ems folder.
Navigate to /apps/tibco/ems/bin
Run “vi tibemsd.conf”
Set server = EMS1
Set max_msg_memory = 0MB
Set listen = tcp://12000
Set routing = enabled
Set flow_control = enabled
Set logfile = /apps/tibco/ems/logs/mymacchine-mid.log
Set logfile_max_size = 20MB
Set log_trace = DEFAULT
Set console_trace = DEFAULT
Save and quit vi session.
Navigate to /apps/tibco/tra/5.5/template/domainutility/cmdline/.
Run “vi AddJMSServer.xml and edit the following:
Set DomainName = MYDOMAIN(Tibco Admin domain )
Set AdministratorUsername = admin
Set AdministratorPassword = “Admin Password”
Set MachineName =MYMACHINE(Depends)
Set JMhaa haaecutable = /apps/tibco/ems/bin/tibemsd
Set JMSConfigFile = /apps/tibco/ems/bin/tibemsd.conf
Set JMSUserName = admin
Set JMSPassword = “JMS admin password”
Set HawkCluster = 10.200.4.09(Depends)
Set OSName = Linux
Set OSVersion = 2.4.21-40.ELsmp(Depends)
Save and quit vi.
Navigate to /apps/tibco/tra/5.5/bin
Run “./domainutilitycmd -cmdFile
/apps/tibco/tra/5.5/template/domainutility/cmdline/AddJMSServer.xml”
Hi Amit,
2. A topic A.B is bridged to a queue B.C, and B.C is bridged to a queue C.D.
Where will a message published on topic A.B be delivered?
A. only to B.C
B. only to C.D
C. to B.C and C.D
D. to neither B.C nor C.D
Answer: A
3. What is the limitation of using a foreign JNDI provider?
A. You can only store destinations.
B. You can only store connection factories.
C. You cannot perform fault tolerant JNDI lookups.
D. It has to run on the same machine as the TIBCO EMS server.
Answer: C
For storing persistent messages, which two files are used by TIBCO EMS?
(Choose two.)
A. failsafe-msgs.db
B. sync-msgs.db
C. async-msgs.db
D. meta.db
Answer: B,C
9)To install settings from a response file, which three TIBCO EMS installer
modes can be
used? (Choose three.)
A. sysprep
B. rpm
C. silent
D. GUI
E. console
Answer: C,D,E
11) Name the two statements which are true about reliable delivery mode
for TIBCO EMS.
(Choose two.)
A. All message publish calls will succeed unless the connection to the server
has been
terminated.
B. Reliable delivery mode decreases the volume of network traffic.
C. Reliable delivery mode is part of JMS specifications.
D. Reliable delivery mode can be used only with topics and cannot be used
with queues.
Answer: A,B
12) In TIBCO EMS for creating TextMessage objects, which is a factory class?
A. Destination
B. Session
C. Message
D. Connection
Answer: B
13) Quite a few of the parameters in the TIBCO EMS main configuration file
require
Boolean values.
Choose the value set which cannot be used.
A. no/yes
B. disabled/enabled
C. false/true
D. 0/1
Answer: D
14) Choose three exceptions that can be generated by calling
Session.Commit() on a session.
(Choose three.)
A. MessageFormatException
B. InvalidDestinationException
C. TransactionRolledBackException
D. IllegalStateException
E. TransactionInProgreshaa haaception
F. JMSSecurityException
Answer: C,D,E
15)Which step should you take to install the EMS JNDI provider, after an EMS
server
installation?
A. You execute the tibemsjndi process in the /lib directory.
B. You enable the EMS JNDI provider in the tibemsd.conf file.
C. No additional step is required.
D. You copy the com.tibco.tibjms.naming.TibjmsInitialContextFactory to the
/lib directory, and restart the server.
Answer: C
Hi,
TIBCO EMS is a distributed and reliable architecture, with support for load-
balancing, routing, and fault tolerant configurations that together remove
single points of failure.
Features
Multicast - Features
Multicast is a messaging model that allows the EMS server to send messages
to multiple consumers simultaneously by broadcasting them over an existing
network..
Features
Facts
This example will just show how you create routes in EMS, Please follow the
instructions to create routes on two different EMS Servers.
1. Create a copy for bin in c:\tibco\ems and name it to bin2.
2. Open tibemsd.conf under c:\tibco\ems\bin change the following settings
a. Change the server name to EMS –SERVER to EMS-SERVERA
b. routing property to enabled
c. save and exit
3. Open tibemsd.conf under c:\tibco\ems\bin2 change the following settings
a. Change the server name to EMS –SERVER to EMS-SERVERB
b. Change the port to tcp://7224 instead of tcp://7222
c. routing property to enabled
d. save and exit
4. open factories.conf under c:\tibco\ems\bin2 change the following settings
a. Change the GeneralConnectionFactory,QueueConnectionFactory and
TopicConnectionFactory URL to tcp://7224 instead of tcp://7222 ( You can
leave FT and SSL connection factories, only required when you are using
these pairs)
b. save and exit
5. Start EMS-SERVERA
a. You can start through service instances
OR
b. Using command prompt
i. C:\ticbco\ems\bin\tibemsd.exe –config tibemsd.conf