Some attributes used in the tibco _ Test

1. Show connections type = Q attributes.

TCP: // localhost: 7222> show connections type = Q

L id fsxt s host user clientid sess uptime
J 91761 + -- q-as234 Anonymous 3 744: 05: 44
J 91762 + -- q + as234 anonymous 5 744: 05: 44
C 2 --- A + Gl-Huang admin 1 0:04:55
J 7 --- Q + Gl-Huang anonymous 1 0:03:18

L client type:

C = C Client

J = Java client

# = C # Client

-= Unknown type.

IDUnique connection ID. Each connection is assigned a unique field. You can use this ID to delete (Command: Delete [ID])

FsxtConnection type information.

Column F indicates whether it is fault tolerant. Fault Tolerance: "-" indicates that the connection has no other connection address, and "+" indicates that there is a connection.

The S column indicates whether to use SSL connections. -No. +: Yes

Column X indicates whether to enable XA transactions or ms dtc connections.

TThe T column shows the connection type..

C-normal user connection

T-topicconnection

Q queueconnection

A-administrative connection

R-the system is connected to another server.

F) -- connect the system to the fault-tolerant Server

S connection status + started-stopped

The number of concurrent sess connections

Uptime connection duration

2. Show queues attributes

Queue name snfgxibct pre rcvrs msgs size

>--5x0 0.0 KB

$ Sys. Admin +--5*0 0.0 KB

$ Sys. lookup--5*0 0.0 KB

$ Sys. redelivery. Delay +---5*0 0.0 KB

$ Sys. undelivered +--5*0 0.0 KB

$ TMP $. EMS-SERVER.32004D5A3D751555.--5 1 0 0.0 KB

Queue. Sample---5*0 0.0 KB

Sample--5x0 0.0 KB

Sample. Q1---5*0 0.0 KB

Sample. Q2---5*0 996 120.3 KB

Testsample. Q1---5*0 0.0 KB

Show queues

Key parameters:

Snfgxibct

Is s secure.

N sender name or performer name.

Whether F is failsafe.

G globle

Is x excluded?

I important?

B Bridge

C flowcontrol: group density detection; control; Data Stream Control

T trace

PreIndicates that if the column is followed by a * sign, it indicates that the value may be inherited from another queue, or the default value.

Rcvrs indicates the recipient of the current activity.

The number of messages in the msgs queue.

Size: total size of the queue.

Common commands

1. Connect to EMS Server
Connect emsserver disconnect emsserver
Admin is the default administrator user. The password is blank.

2. Show All Users
Show users

3. display the current user
Whoami

4. Create a user or group
Create user Jackson create group emsgroup

5. Add a user to the group
Add member emsgroup Jackson

6. delete a user
Delete user Jackson

7. Change User Password
Set Password Jackson newpsd

8. Create queue, topic, and destinatin
Create queue | topic

9. view the system-level permission list
Help Permissions

10. authorize system management-level Permissions
Grant admin Jackson view-ACL

11. Grant object-level Permissions
Grant topic | queue

12. view the Server Object status
Show queues // view all queue
Show queue jacksontestqueue // view a queue. the singular number in the tibco command indicates a specific object, and the plural number indicates all

13. Set attributes on queue/topic/destination
Addprop removeprop setprop, etc.

14. view the server object or user permission list
Showacl user Jackson
Showacl queue jacksontestqueue

15. Deletion of server objects or users
Delete

16. Message Deletion
Purge queue jacksontestqueue

 

 

EMS dynamic queue

In EMS,Dynamic queueu is generated by applicationStatic queue is created on the management interface or by modifying the config file. dynamic queue has great flexibility and is more suitable for some scenarios than static queue. For more information, see JMS.
1) the dynamic queue of EMS starts with "*", and a special dynamic queue is calledTemporary queue,
2) If the dynamic queue has no consumer or information in the queue, EMS will choose to clear the queue
3) The temporary queue name is generated by the EMS server and can be consumed only when the session for this queue is created. After the EMS is restarted, the temporary queue will be cleared, regardless of whether there is any content in it.
4) to allow the application to create a dynamic queue, queues. conf must be configured using wildcard.

Check which connection has been eaten by the q msg of a queue.

Command: show consumers queue = queue name

EMS Fault Tolerance configuration (Translation)

I. Fault Tolerance Configuration

To facilitate the difference, the parameters are represented in Oblique black bodies.

Configure the master server

Open c: \ tibco \ EMS \ bin \ tibemsd. conf (this file is called the EMS configuration file)

Server= EMS-SERVER-RAMU(This value depends on your choice)
Listen= TCP: // 7222(This value depends on your choice)
Ft_active= TCP: // 7444(This value depends on your choice)

Configure Backup Server

Create the backup directory under the bin directory, and set the directory c: \ tibco \ EMS \ bin *. copy the conf file (only the configuration file) to c: \ tibco \ EMS \ bin \ backup \

Note: from now on, we will work in the backup directory to open the tibemsd. conf file in this directory.

Server= EMS-SERVER-RAMU(This value must be consistent with the value of the server parameter in the tibemsd. conf file of the master server)
Listen= TCP: // 7444(This value must be the same as that in the tibemsd. conf file of the master server.Ft_activeThe parameter values are consistent)
Ft_active= TCP: // 7222(This value must be consistent with the value of the listener parameter in the tibemsd. conf file of the master server)
Store= C: \ tibco \ EMS \ bin \ datastore(This value must be consistent with the storage parameter in the tibemsd. conf file of the master server.Store,Note that the value in the tibemsd. conf file of the master server is exactly datastore)

Add the path c: \ tibco \ EMS \ bin \ backup \ to the following list of Backup Server tibemsd. conf \

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 of the master server and compare it with the tibemsd. conf file of the backup server, you will find that some parameters in the tibemsd. conf file of the master server do not specify the path. For example, "users = users. conf" is defined as "users = c: \ tibco \ EMS \ bin \ backup \ users. conf" in the tibemsd. conf file of the backup server ". This is because these values are set during the installation of the EMS server and you know the path to search for them. Therefore, the parameters in the tibemsd. conf file of the master server do not contain the complete path.

2. Running Server

Go to "all programs"> "run"> enter "cmd"

Run the following command prompt in the window:Cd c: \ tibco \ EMS \ bin
Now go to the bin directory

Start the master server

Enter the following command:Tibemsd (this is an application)

Start Backup Server

Open another command prompt and enter the following command to enter the corresponding directory:Cd c: \ tibco \ EMS \ bin
Run the following command to start the backup server:
Tibemsd-config backup \ tibemsd. conf(The backup server is started in this way and the master server does not need to be used because the tibemsd. conf file of the master server and the tibemsd application are in the same directory)

On the backup server command prompt line, you can see that it is in standby mode (TCP: // 7222

 

[How to set up two tibco queue data transmissions]

In either case, the property value of routing must be enabled.

1. When authorization is disabled

Assume that the server name of 10.2.18.86 => tibco EMS is TESTA (show Server View server name)

10.2.18.70 => The Name Of The tibco EMS server is testb.

Now we want the queue. Q1 data in testb to flow to queue. Q1.

First, create the route command in testb:

Create routeTestaUrl = TCP: // 10.2.18.86: 7222 the red color must be the same as the first server name. Otherwise, the connection fails.

Second, create queue. Q1 with the global attribute and perform the following operations in Testa.

Create queue. Q1 global must have global

Third, create the same queue in testb, but the command is different from.

Create queue. Q1 @ TESTA (testa is the name of the previously created route) @ indicates that all messages are sent to the queue. Messages of Q1 will be sent to queue. Q1 in Testa.

2. Authorization = enabled.

First, set server authorization = enabled in Testa. You do not need to restart this step.

Second, create a user with the username testb server name. For example, create user testb Password = 123456. You must use the server name here.

Third, set a password in testb, for example, set server password = 123465. testb will use this password to log on to Testa. In this way, the data flow in the queue can be realized.

 

 

Description of tibemsd. conf configuration file:

 

######################################## ################################

# Server identification information.

#

# Server: A Unique User Name that identifies and modifies the server name.

# Password: password, which can be identified during logon. Empty by default

######################################## ################################

 

Server = EMS-SERVER

Password =

######################################## ################################

# Persistent storage.

#

# Store: configure the directory for storing messages. These files will be used for persistence in the database.

######################################## ################################

 

Store = "% tibco_home_1_mgmt_dir_esc %/EMS/data/datastore"

 

######################################## ################################

# The maximum number of connections to the server. If it is set to 0, there is no limit.

######################################## ################################

 

Max_connections = 0

 

######################################## ################################

# Max_msg_memory

# Maximum memory occupied by messages. If it is set to 0, it is unlimited. When you set the value to change, the Unit can be kb, MB, or GB.

# MSG-swapping

# Whether to set the swap zone on the hard disk

######################################## ################################

 

Max_msg_memory = 512 MB

Msg_swapping = Enabled

######################################## ################################

# The listening port of the server. Generally, TCP or SSL can specify any port.

######################################## ################################

Listen = TCP: // 7222

######################################## ################################

# Authorization. The default value is disabled. If it is enabled, the user's certificate and authorization will be checked to a safe destination.

######################################## ################################

 

Authorization = disabled

######################################## ################################

# Set the queue data transmission mode between two servers. Data of a queue in server a can flow to a queue in server B.

######################################## ################################

Routing = disabled

######################################## ################################

# Set it to enable. There are two related attributes. One is the target address specified by flowcontrol (queue or topic)

# Size of the message to be stored. One is overflowpolicy which sets the memory overflow policy.

#1. Default 2. discardold 3. rejectincoming

# If it is 1. When the topic exceeds the specified maxbtye or maxmsg, the consumer will not receive the message and will not

# Return Error. An error is returned in the queue, and the new message is rejected.

# If it is 2. In a topic, if it overflows, the MSG will not be returned by the consumer before it is discarded.

# Old messages are discarded and an error is reported.

# If it is 3. If the topic overflows, the system rejects the message and returns an error message. Same as 1.

#

# Setprop queue myqueue maxmsgs = 1000, overflowpolicy = discardold

######################################## ################################

Flow_control = disabled

######################################## ################################

# Enable or disable multiple transmission links on multiple servers of tibco EMS.

# Set the configuration file to channels. conf. You can set the transmission bandwidth for each channel.

######################################## ################################

Multicast = disabled

######################################## ################################

# Enable rendezvous transports defined in transports. conf.

# Enable tibco rendezvous message communication,

# If you want to set this function, it may involve the configuration in three other places.

#1. Configure the transport. conf file to configure the queue's queue/topic message policy and rendezvous's

# Address

#2. Reference on transport. conf in the queue. conf configuration.

#3. Reference transport. conf in topic. conf configuration

######################################## ################################

Tibrv_transports =

######################################## ######################################## ####

Before that, let's take a look at tibco Logon:

Go to the startup directory/usr/local/tibco/EMS/6.0/bin of tibco and run./tibemsadmin.

When a similar

Version 6.0.1 V3 1/12/2011

Type 'help' for commands help, 'exit 'to exit:
>

Enter the connect IP port. The default port is 7222, which can be omitted ~