TCP-EMS8 TIBCO Enterprise Message Service 8 Certification Exam Questions and Answers

ft_passive parameter in the tibemsd.conf file

store parameter in the store, conf file

server parameter in the tibemsd.conf file

ft_factory in the factories.conf file

If two instance of the Account Balance Manager are deployed on different nodes than the Balance Manger Service, each service request will be handled by one of the instances.

It is illegal to deploy more than one instance of the Account Balance Manager.

If one instance of the Account Balance Manger is deployed on the same node as the Balance Manger Service and another Account Balance Manager is deployed on a different node, the instance on the different node can never receive the requests.

If two instance of the Account Balance Manger are deployed on different nodes than the Balance Manger Service, each service request will be handled by both of the instances.

DUPS_OK_ACKNOWLEDGE

IMPLICIT_CLIENT_DUPS_OK_ACKNOWLEDGE

EXPLICIT_CLIENT_ACKNOWLEDGE

NO_ACKNOWLEDGE

IMPLICIT_CLIENT_ACKNOWLDEGE

ActiveMatrix node

ActiveMatrix enterprise

ActiveMatrix host

ActiveMatrix environment

ActiveMatrix composite application

deploy the service in the system node so the Active matrix infrastructure can manage availability

deploy the service across multiple nodes and place a load balancer in front of the service availability

specify virtualization upon service deployment allowing Active matrix to transparently route requests

create a single node that spans multiple hosts to provide resiliency in the event of host failure

When an external action causes changes to the RETE network

When TIBCO Business Events builds (or refreshes) a rule action agenda

When a rule action is executed

When the rule action agemda is empty

browse

send

durable

subscribe

Grant topic topic.sample user=Bob view

Grant admin Bob view topic.sample

Grant topic topic.> user=Bob view

Grant admin Bob view-all

Grant topic > user=Bob view

Grant admin Bob view topics

JMS

Local

HTTP

FTP

JACI

NTML

JAAS

WS-*

file_minimum

store_min_size

store_minimum

file_min_size

file_truncate

Zones affect queue and topic messages.

A server can simultaneously belong to more than one zone.

The concept of zones and hops applies to queue messages.

Topic messages can be routed across multiple hops if there are no cycles.

The transaction can succeed if the producer only has permission to send to topic T1.

The transaction will fail if the producer does not have permission to send to topic T2.

The bridge needs to be configured to support transactions.

All messages sent across the bridge are part of the transaction.

If a client does not receive heartbeats from EMS server for a period exceeding 20 seconds, the client will close the connection.

If a client does not receive heartbeats from EMS server for a period exceeding 10 seconds, the client will close the connection.

If EMS server does not receive heartbeats from a client for a period exceeding 20 seconds, the EMS server will close the connection.

If EMS server does not receive heartbeats from a client for a period exceeding 10 seconds, the EMS server will close the connection.

AI destinations for a channel must use different server connections.

A Channel can contain many destinations.

A destination can contain many channels.

AI destinations for a channel use the same server connection.

Create factory myFactory queue url=tcp://server:7777,tcp://server1:8888

Create factory myFactory queue url=tibjmsnaming://server:7777

Create factory myFactory queue url=ssl://server:7777

Create factory myFactory queue url=ems://server:7777

Create factory myFactory queue url=tibjmsnaming://server:7777,tibjmsnaming://server:8888

Underlying services are not impacted when the composite responds to requests.

Responses are provided from information private to the service.

Underlying services are not required.

Responses require the invocation of all underlying services.

compliant_ack_check

non persistent

confirm ok

npsend_check_mode

service architecture

binding port specification

service interface specification

service utilization scenarios

user interface specification