Does multi-server installation of TIBCO InConcert require separate pool names, user names, etc. in Job templates?

Does multi-server installation of TIBCO InConcert require separate pool names, user names, etc. in Job templates?

book

Article ID: KB0084954

calendar_today

Updated On:

Products Versions
TIBCO InConcert -
Not Applicable -

Description

Resolution:
no, as follows...


Multi-server configurations distinguish servers by the server logical name
as this is used for the subject of all messages.  Each server uses separate DBMS
table-spaces.  Conflicts therefore do not arise between the
servers, and the use of different names for pools, users,
templates etc. is not required. Using the same names in a test
environment might in fact be both less cumbersome and more
reliable.

What is required is a separate database owner (icdbown) for the InConcert tables if
both servers are in the same database.


Environment

Product: TIBCO InConcert Version: 6.2.1 OS: All --------------------

Issue/Introduction

Does multi-server installation of TIBCO InConcert require separate pool names, user names, etc. in Job templates?