'Weblogic Tuxedo Connector' remote services configuration

Question

Hi All,
I'm trying to use Weblogic Tuxedo Connector to call an external Tuxedo from my
Weblogic server.
I have already configured a local domain for my weblogic server and a remote server
for my external Tuxedo server, and it works fine...
The only problem is that I have to define all services in my remote server (using
T_DM_IMPORT entries in the wtc.xml configuration file) and I have more than 6000
services running in my Tuxedo.
Can I bypass this definition setting using some default value?
Thanks for your help,

Answer 1

Josep,
The doc is not exactly correct. While it is true that the WTC
configuration only
provides for static configuration(there is no usage of runtime mbeans
yet), the
WLS SERVER does not need to be restarted in order for configuration
changes to
take effect. The WTC SERVICE must be restarted.
The WTCService that is running on the the WLS server is turned on and off
by deploying/undeploying the WTCServerMBean against the WLS server. The
scenario that Johns suggested would be something like: get the new list
of services
exported by Tuxedo, modify the MBean configuration accordingly,
undeploy/redeploy
the WTCServerMBean. The cost is in loss of that particular WTCService
for the
recycling time but the WLS server is still available for some other WTC
service.
Sorry for the confusion.
Bob Finan
Josep Freixes wrote:
I post this message just to let you known that I think that this cannot be done.
In the WTC 7.0 documentation (see http://edocs.bea.com/wls/docs70/wtc_admin/Install.html#1107584),
just before starting to explain the WTC MBean classes, you can read the following
paragraph:
This release of the WebLogic Tuxedo Connector provides only static configuration.
If you need to change any parameters used to configure the WebLogic Tuxedo Connector,
the WebLogic Server must be restarted for the changes to take effect. For example,
you can not add or remove domain network links, change network addresses, or import
or export new services.
So we will need to wait until the next version of WTC.
"John Wells" <[email protected]> wrote:
That bit can be fixed in WLS 7.0. There are Management Beans I don't know the
exact details of the Mbeans to use - look at the documentation) that can be used
to dynamically add and remove services in WTC in WLS 7.0. You could create an
Tuxedo EJB on the WLS side which uses those MBeans to progromatically change the
list of services. On the Tuxedo side, you could create a daemon client that subscribes
to events about service advertisement and then have this client call the EJB on
the WLS side. It can be done, though it is something of a circuitous route...
"Josep Freixes" <[email protected]> wrote in message
news:[email protected]...
Thanks for your help, John.
The problem is not the one-time typing of all the service names. The problem
is
to get the list up-to-date from now on... and every change needs to
restart the
WebLogic Server to be applied...
"John Wells" <[email protected]> wrote:
I don't think there is any way to default the services going from
WLS to
Tuxedo.
You just have to start typing... The only suggestion would be to
get
very friendly
with your editor and figure out how to use its macros.
"Josep Freixes" <[email protected]> wrote in message
news:[email protected]...
Hi All,
I'm trying to use Weblogic Tuxedo Connector to call an external
Tuxedo
from
my Weblogic server.
I have already configured a local domain for my weblogic server
and a
remote
server for my external Tuxedo server, and it works fine...
The only problem is that I have to define all services in my remote
server
(using T_DM_IMPORT entries in the wtc.xml configuration file) and I
have
more
than 6000 services running in my Tuxedo.
Can I bypass this definition setting using some default value?
Thanks for your help,
[att1.html]