Is Jolt part of Tuxedo?

Our company is using Tuxedo and looking into some web based applcations using XML
to communicate with the services. My question is, is Jolt part of Tuxedo in which
it can be used without additional cost? What are ballpark figures to get the
Jolt Server software? Using Tuxedo, you have a install for Tuxedo workstation
and Tuxedo Server. Is this the same scenario for Jolt? Are those seperate costs?

Before Tuxedo8.0, Jolt is a extra product. But now it is part of Tuxedo8.0

Similar Messages

Jolt 1.2/Tuxedo 6.5

I'm working on Tuxedo 6.5/Jolt 1.2 in a Websphere 3.02 environment.
1. Problem with Transaction and Session pools
Our application retreives information from an Informix database through servlets. We've built a SessionPool in order to access our Tuxedo services, but without any transactional state. In fact, as we do not update the database, we didn't use transactions.
Our question is when is the user connection free and available for an other user, since the Reference Documentation API says a connection is free when the transaction commit's or rollbacks. As we don't use any transaction, we don't know when (and how) a connection is available for reuse. Must we wait the Tuxedo timeout? ....
And is there an easy way to free a connection (force a connection to be once again available)?
2. Jolt 1.2 release
We're working with the Jolt 1.2 release, as I already said. The reference API documentation says a class named ServiceInfo in bea.jolt.pool will retreive information on Tuxedo services (parameters, ...). Unfortunately, our jar file (joltjse.jar, 33Kb) doesn't have it. I'd like to use it to built my DataSets' automatically from an Array or a Vector.
Is it because our Jolt version is too old and because the 1.2 does not provide this class? Is it part of the 1.2.x release?
In this case, how can I get the right jar without having to install (and/or upgrade to) a new version of Jolt?
Thank you for your answers
TR.

Dear,
Could you please send Jolt 1.2<For AIX4.3> to me ?
Or tell me where I can find it.
Thanks anywhere.
Fogg wg

Can I use Jolt start/stop Tuxedo apps ??

Hi,
I am a newbie to Jolt....we need a way to stop/start Tuxedo
application with Java...can we use the Jolt API ??
Thankx a million
Aidan
Munich, Germany

There is a mode that mix both start and stop trigger but it doesn't explain if i can re-use easily these 2 triggers one after the other.
user manual 653xcard part 2-9:
"When you use a start and stop trigger, data transfer starts upon receiving a trigger on the start trigger line (ACK/STARTTRIG pin) and ends upon
receiving a trigger on the stop trigger line (STOPTRIG pin), and ..."
thanks awaiting your insight answers.
Hari

Jolt transaction towards Tuxedo services - XA required ?

Dear Friends (Especially Todd Little),
Sorry, but the Jolt and Tuxedo documentation is really weak (to say the least) in regard of Transaction management from Jolt.
I would like to ask for your kind help with answering the most simple question in the world:
I have two Tuxedo services each doing some updates on a DB. Both work against the same DB (single DB resource, no multiple DBs) and run inside the same Tuxedo instance in production.
I would like both services to do their updates in a transactional manner when called from Jolt (with transacted SessionPool).
Do I need these two services to run with XA resource for that, or not ?
My natural expectation (from JEE world experience) is that both services would be assigned (by the container, in our case Tuxedo) with the same DB Connection to perform their updates, so in case the Connection is rolled back (due to failure in one service), all update (from all previous services) are rolled back.
And, I would have expect Tuxedo to manage that, so all services called from the same transactional Jolt Session would share the same DB Connection (Just as is done with Weblogic or any other JEE server when a non XA transaction is running).
I would not expect a need to configure (and worst, to consume in production) a XA resource for that (simple) business implementation.
Its like buying the whole cow for a glass of milk ...
Could you please elaborate on that ?
Regards.

Hi,
When a Jolt client calls startTransaction, a Tuxedo transaction is started on the behalf of the client by the JSH. Since this transaction is not part of the client's transaction environment (JTA, etc.) we call it a delegated transaction as the transaction work is done by the JSH, yet still controlled by the Jolt client. This is fully supported and the expected behavior of both Jolt clients as well as Workstation clients. Again, the key point about delegated transactions is they are not part of any transaction the client may be participating in outside the Tuxedo environment. So a Jolt client that is running in the context of a JTA transaction calling startTransaction will be involved in two separate and distinct transactions, the JTA transaction and the Tuxedo transaction. Thus the transaction outcomes can be different, i.e., the Tuxedo transaction could commit while the JTA transaction rollsback. If you need distributed transaction support between the clients transaction manager and Tuxedo's transaction manager you will need to use WTC which supports this type of distributed transaction.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

Performance degradation using Jolt ASP Connectivity for TUXEDO

We have a customer that uses Jolt ASP Connectivity for TUXEDO and is suffering
from a severe performance degradation over time.
Initial response times are fine (1 s.), but they tend to increase to 3 minutes
after some time (well, eh, a day or so).
Data:
- TUXEDO 7.1
- Jolt 1.2.1
- Relatively recent rolling patch installed (so no there are probably no JSH performance
issues and memory leaks as fixed in earlier patches)
The ULOG shows that during the night the JSH instances notice a timeout on behalf
of the client connection and do a forced shutdown of the client:
040911.csu013.cs.kadaster.nl!JSH.234333.1.-2: JOLT_CAT:1185: "INFO: Userid:
[ZZ_Webpol], Clientid: [AP_WEBSRV3] timed out due to inactivity"
040911.csu013.cs.kadaster.nl!JSH.234333.1.-2: JOLT_CAT:1198: "WARN: Forced
shutdown of client; user name 'ZZ_Webpol'; client name 'AP_WEBSRV3'"
This happens every 10 minutes as per configuration of the JSL (-T flag).
The customer "solved" the problem for the time being by increasing the connection
pool size on the IIS web server.
However, they didn't find a "smoking gun" - no definite cause for the problem.
So, it is debatable whether their "solution" suffices.
It is my suspicion the problem might be located in the Jolt ASP classes running
on the IIS.
Maybe the connection pool somehow loses connections over time, causing subsequent
users having to queue before they get served (although an exception should be
raised if no connections are available).
However, there's no documentation on the functioning of the connection pool for
Jolt ASP.
My questions:
1) What's the algorithm used for managing connections with Jolt ASP for TUXEDO?
2) If connections are terminated by a JSH, will a new connection be established
from the web server automatically? (this is especially interesting, because the
connection policy can be configured in the JSL CLOPT, but there's no info on how
this should be handled/configured by Jolt ASP connectivity for TUXEDO)
Regards,
Winfried Scheulderman

Hi,
For ASP connectivity I would suggest looking at the .Net client facility provided in Tuxedo 9.1 and later.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

WebLogic connects to Tuxedo with JOLT

I have to work with Weblogic and Tuxedo with Jolt. But I tmboot -y to boot
JSL,JREPSVR,than I want to config my repository editor to deploy my
services,some eror messages display.
Could some friends help me to solve this problem?
After I input server ip and port <as in my ubbconfig file -n
file://192.9.100.2:8000>,it displays
bea.jolt.SessionException:Cannot connect to any file://192.9.100.4:8000.
Reason:NwHdlr:Cannot open socket.
Beafor I run "appletviewer RE.html",I have set CLASSPATH to include jolt
classes.
CLASSPATH=/app/tuxedo/udataobj/jolt/classes/bea/jolt
PATH=/app/tuxedo/apps:/app/tuxedo/bin:/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:
/usr/bin/
X11:/sbin:/usr/tuxedo/bin
*******************ubbsimple***********************
#ident "@(#) apps/simpapp/ubbsimple $Revision: 1.1 $"
#Skeleton UBBCONFIG file for the TUXEDO Simple Application.
#Replace the <bracketed> items with the appropriate values.
*RESOURCES
IPCKEY 123456
DOMAINID simpapp
MASTER simple
MAXACCESSERS 30
MAXSERVERS 20
MAXSERVICES 40
MODEL SHM
LDBAL N
*MACHINES
DEFAULT:
aix170 LMID=simple
APPDIR="/app/tuxedo/apps/simpapp"
TUXCONFIG="/app/tuxedo/tuxconfig"
TUXDIR="/app/tuxedo"
MAXWSCLIENTS = 20
*GROUPS
DEFAULT: LMID=simple
GROUP1 GRPNO=1 OPENINFO=NONE
JREPGRP GRPNO=94
JSLGRP GRPNO=95
*SERVERS
DEFAULT:
simpserv SRVGRP=GROUP1 SRVID=1
JSL SRVGRP=JSLGRP SRVID=30
CLOPT= "-A -- -n file://192.9.100.4:8000 "
JREPSVR SRVGRP=JREPGRP SRVID=98
RESTART=Y MAXGEN=10 RQADDR=JREPQ REPLYQ=Y GRACE=0
CLOPT="-A -- -W -P
/app/tuxedo/apps/simpapp/jrepository/jrepository"
*SERVICES
TOUPPER
*******************ubbsimple***********************

I have to work with Weblogic and Tuxedo with Jolt. But I tmboot -y to boot
JSL,JREPSVR,than I want to config my repository editor to deploy my
services,some eror messages display.
Could some friends help me to solve this problem?
After I input server ip and port <as in my ubbconfig file -n
file://192.9.100.2:8000>,it displays
bea.jolt.SessionException:Cannot connect to any file://192.9.100.4:8000.
Reason:NwHdlr:Cannot open socket.
Beafor I run "appletviewer RE.html",I have set CLASSPATH to include jolt
classes.
CLASSPATH=/app/tuxedo/udataobj/jolt/classes/bea/jolt
PATH=/app/tuxedo/apps:/app/tuxedo/bin:/bin:/usr/bin:/etc:/usr/sbin:/usr/ucb:
/usr/bin/
X11:/sbin:/usr/tuxedo/bin
*******************ubbsimple***********************
#ident "@(#) apps/simpapp/ubbsimple $Revision: 1.1 $"
#Skeleton UBBCONFIG file for the TUXEDO Simple Application.
#Replace the <bracketed> items with the appropriate values.
*RESOURCES
IPCKEY 123456
DOMAINID simpapp
MASTER simple
MAXACCESSERS 30
MAXSERVERS 20
MAXSERVICES 40
MODEL SHM
LDBAL N
*MACHINES
DEFAULT:
aix170 LMID=simple
APPDIR="/app/tuxedo/apps/simpapp"
TUXCONFIG="/app/tuxedo/tuxconfig"
TUXDIR="/app/tuxedo"
MAXWSCLIENTS = 20
*GROUPS
DEFAULT: LMID=simple
GROUP1 GRPNO=1 OPENINFO=NONE
JREPGRP GRPNO=94
JSLGRP GRPNO=95
*SERVERS
DEFAULT:
simpserv SRVGRP=GROUP1 SRVID=1
JSL SRVGRP=JSLGRP SRVID=30
CLOPT= "-A -- -n file://192.9.100.4:8000 "
JREPSVR SRVGRP=JREPGRP SRVID=98
RESTART=Y MAXGEN=10 RQADDR=JREPQ REPLYQ=Y GRACE=0
CLOPT="-A -- -W -P
/app/tuxedo/apps/simpapp/jrepository/jrepository"
*SERVICES
TOUPPER
*******************ubbsimple***********************

Tuxedo Service can not find a Jolt Client AFter timeout occured

We are using Java Servlet/Jolt client to access out backend
Tuxedo services.
Whenever a Tuxedo service timedout, like
"***tpcall failed |TPETIME - timeout occured|",
The Jolt client and Tuxedo services will be out of sync,
and Tuxedo Server will show following error message:
"JOLT_CAT:1518: "ERROR: Call handle and clientid have no matching requests".
Whenever this happends, we must reboot out Jolt client connection. Otherwise we
will keep geting above problem.
Our Jolt timeout time is 2 minutes. And Tuxedo block time is
1 min 30 sec. (We setip in our UBB config as
BLOCKTIME 9 #9*10s (def SCANUNIT)=90s or 1 min and 30s.).
It seems like Tuxedo service will be timeouted before Jolt timedout.
Could someone give us some suggestion about the above problem?
Thanks in advance!

Which version of Jolt are you using? This problem seems to have been fixed in
latest rolling patch for Jolt1.2. Contact BEA support for it.
-Deepak
Yux71 wrote:
We are using Java Servlet/Jolt client to access out backend
Tuxedo services.
Whenever a Tuxedo service timedout, like
"***tpcall failed |TPETIME - timeout occured|",
The Jolt client and Tuxedo services will be out of sync,
and Tuxedo Server will show following error message:
"JOLT_CAT:1518: "ERROR: Call handle and clientid have no matching requests".
Whenever this happends, we must reboot out Jolt client connection. Otherwise we
will keep geting above problem.
Our Jolt timeout time is 2 minutes. And Tuxedo block time is
1 min 30 sec. (We setip in our UBB config as
BLOCKTIME 9 #9*10s (def SCANUNIT)=90s or 1 min and 30s.).
It seems like Tuxedo service will be timeouted before Jolt timedout.
Could someone give us some suggestion about the above problem?
Thanks in advance!

How to use Tuxedo's services from an EJB: Jolt x JET ?

Hi.
Can anyone tell me if an EJB MUST use JET (instead Jolt) to access Tuxedo services
Suppose the following case:
We have a client using JNDI service to obtain an EJB.
In my client i invoke the appropriate methods to create a jolt session and to
start a jolt transaction. My EJB Bean only call Tuxedo services (using Jolt).
Will this application work ? Will EJB code use the transaction created by the
client code ? Will a transaction context exist ?
Thanks in advance.

Hi Daniel,
If you mean WebLogic Server 5.1 by WL 5.1 (instead of WebLogic Enterprise), then
yes, you need to use Jolt until you upgrade to a later release of WebLogic Server.
WTC wasn't fully supported until WebLogic Server 6.1 and later.
The transaction context of the container Jolt is being used in is not extended
to the Tuxedo system. Jolt can be used to start a new and separate transaction
in Tuxedo, but that transaction and the containers current transaction will not
be coordinated.
I'm not sure what you mean when you say:
The transaction management when using Jolt is realized for Jolt API.
There is no relantionship between Jolt transactions and Tuxedo transactions.
Is this rightThe transaction management when using Jolt is transaction management of
the Tuxedo system you are talking to. Jolt is a client side API that uses a
delegated model for transactions. So a transaction started with Jolt starts
a transaction in Tuxedo, but does not affect the transaction context of the
environment the client, i.e., the place where the Jolt call was made. So if
you are using Jolt inside an EJB hosted in the EJB container of WebLogic
Server, the Jolt calls will have no impact or effect on the transaction state
of the EJB.
Regards,
Todd
"Daniel" <[email protected]> wrote:
>
Ok.
We have EJBs running in Weblogic and they are using Tuxedo services.
We have used Jolt instead WTC because we are running WL 5.1. Can i
use WTC with WL 5.1 ?
The transaction management when using Jolt is realized for Jolt API.
There is
no
relantionship between Jolt transactions and Tuxedo transactions. Is this
right
Thanks in advance.
"Todd Little" <[email protected]> wrote:
"Daniel" <[email protected]> wrote:
Hi.
Can anyone tell me if an EJB MUST use JET (instead Jolt) to access
Tuxedo
services
? You can use either Jolt or preferably use WTC and JATMI.
Suppose the following case:
We have a client using JNDI service to obtain an EJB.
In my client i invoke the appropriate methods to create a jolt session
and to
start a jolt transaction. My EJB Bean only call Tuxedo services (using
Jolt).Why is the client creating a Jolt session and transaction? They will
not be associated
with the EJB's execution. The client's Jolt context is not propogated
to the
EJB. Can you explain what it is you want to do? What do you want included
in
the transaction?
Will this application work ? Will EJB code use the transaction created
by the
client code ? Will a transaction context exist ?Well I suppose it depends upon what you mean by work. It comes down
to what are
you trying to accomplish. The client is a WLS client? Is the EJB a
client of
some Tuxedo service? If those are both true, then you would be best
served by
controlling the transaction with the EJB's deployment descriptor and
having the
EJB use WTC to access Tuxedo. WTC will take of propagating any required
transaction
state to Tuxedo.
Regards,
Todd

Tuxedo Configuration

Hi ,
I need to Communicate with Tuxedo Server ,we are using Jboss6 App server .Please Suggest me How to approach to send Transactions to tuxedo server from My Jboss App server. here iam confusing, which one to use either Tuxedo JCA Adapter ,or Oracle Jolt .Please Suggest me Which one is better
thanks
harikrishna
Edited by: 931756 on 31 Jul, 2012 11:00 PM

Hi,
If you search the threads for "JOLT AND transcations" you should find this thread:
Jolt transaction towards Tuxedo services - XA required
At the end is a nice description by Todd Little:
When a Jolt client calls startTransaction, a Tuxedo transaction is started on the behalf of the client by the JSH. Since this transaction is not part of the client's transaction environment (JTA, etc.) we call it a delegated transaction as the transaction work is done by the JSH, yet still controlled by the Jolt client. This is fully supported and the expected behavior of both Jolt clients as well as Workstation clients. Again, the key point about delegated transactions is they are not part of any transaction the client may be participating in outside the Tuxedo environment. So a Jolt client that is running in the context of a JTA transaction calling startTransaction will be involved in two separate and distinct transactions, the JTA transaction and the Tuxedo transaction. Thus the transaction outcomes can be different, i.e., the Tuxedo transaction could commit while the JTA transaction rollsback. If you need distributed transaction support between the clients transaction manager and Tuxedo's transaction manager you will need to use WTC which supports this type of distributed transaction.
WTC is a subcomponent of WebLogic (i.e. WebLogic Tuxedo Connector) which does domain protocol communication with a remote Tuxedo domain.
For JBoss, Tuxedo JCA would be similar to WTC in regard to providing distributed transaction support with Tuxedo.
Regards,
Bob Finan

SAP R/3 with JOLT componant

Hi,
Does exist an adpater which permits to connect an R/3 instance to a JOLT agent ? The aim is to avoid the installation of Tuxedo on our server.
At this moment we use this :
SAP R3 - CLIENT C - tuxedo installed on the R/3 server -
we would prefer to have this :
SAP R3 - JOLT CLIENT - Middleware- tuxedo installed on the client
regards

Hi,
you use adapters to connect XI with other systems (SAP systems, legacy, ...:
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
For SAP systems you usually use RFC, IDoc or Proxies.
For your legacy systems which adapter fits best to your system and your scenario.
Regards
Patrick

Migrating Jolt 1.2 to Jolt 8.0 question

Hi.
I have environment with Tuxedo 6 and WebLogic 5.1 communicating via Jolt
1.2. I want to migrate the system to Tuxedo 8, WebLogic 7, and Jolt 8. Do I
have to chage any code, or configuration related to Jolt to make the
application work with Jolt 8 after migration.
Thanks in advance,
Tinnapat

From our Jolt Engineer:
"Configuration on Tuxedo side doesn't change if the new features
(security propagation) is not used. Configuration on WLS 7.0, uses an
xml file now - different from WLS 5.1. So, the configuration for Jolt
also would be different. The client code changes slightly - only in
respect to how you get the connection to the Jolt servers - see the Jolt
example in Tuxedo."
Tinnapat Chaipanich wrote:
>
Hi.
I have environment with Tuxedo 6 and WebLogic 5.1 communicating via Jolt
1.2. I want to migrate the system to Tuxedo 8, WebLogic 7, and Jolt 8. Do I
have to chage any code, or configuration related to Jolt to make the
application work with Jolt 8 after migration.
Thanks in advance,
Tinnapat

Jolt - supported platforms.

Hi
My JSL starts on the SUN Sparc SunOs 5.7 but will not start on SunOs 5.8. ( I
have Jolt 1.2 & Tuxedo 6.5).
How does 5.7 & 5.8 match the supported platforms 2.5.1 / 2.6 /
2.7 ?
Do I have to upgrade to run on my SUnOs 5.8 ?
Regards
Jorgen

You will need a certain patch level for Tuxedo 6.5 to work on Solaris 2.8. Which
patch level you are running with?
-Deepak
Jorgen Holmkvist wrote:
Hi
My JSL starts on the SUN Sparc SunOs 5.7 but will not start on SunOs 5.8. ( I
have Jolt 1.2 & Tuxedo 6.5).
How does 5.7 & 5.8 match the supported platforms 2.5.1 / 2.6 /
2.7 ?
Do I have to upgrade to run on my SUnOs 5.8 ?
Regards
Jorgen

Bea.jolt.pool.ServiceException: TPETRAN - error starting transaction

I am ctreating the transaction object and try to operate PoolManager.call()
with the transaction object as parameter. The call fails with the following
exception:
bea.jolt.pool.ServiceException: TPETRAN - error starting transaction
at bea.jolt.pool.Connection.call(Connection.java, Compiled Code)
at bea.jolt.pool.SessionPool.call(SessionPool.java:412)
at bea.jolt.pool.SessionPool.call(SessionPool.java:211)
at
mcs.connectjolt.bandetails.BanDetailesDAO.getBanDetailes(BanDetailesDAO.java
:87)
at
mcs.connectjolt.bandetails.BanDetailsBean.getBanDetailes(BanDetailsBean.java
:68)
at
mcs.connectjolt.bandetails.BanDetailsBeanEOImpl.getBanDetailes(BanDetailsBea
nEOImpl.java:105)
at
mcs.connectjolt.bandetails.BanDetailsBeanEOImpl_WLSkel.invoke(BanDetailsBean
EOImpl_WLSkel.java:83)
at
weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java, Compiled Code)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:69)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
5)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
My configuration: WebLogic 5.1, Jolt 1.2, Tuxedo 6.4.

I am ctreating the transaction object and try to operate PoolManager.call()
with the transaction object as parameter. The call fails with the following
exception:
bea.jolt.pool.ServiceException: TPETRAN - error starting transaction
at bea.jolt.pool.Connection.call(Connection.java, Compiled Code)
at bea.jolt.pool.SessionPool.call(SessionPool.java:412)
at bea.jolt.pool.SessionPool.call(SessionPool.java:211)
at
mcs.connectjolt.bandetails.BanDetailesDAO.getBanDetailes(BanDetailesDAO.java
:87)
at
mcs.connectjolt.bandetails.BanDetailsBean.getBanDetailes(BanDetailsBean.java
:68)
at
mcs.connectjolt.bandetails.BanDetailsBeanEOImpl.getBanDetailes(BanDetailsBea
nEOImpl.java:105)
at
mcs.connectjolt.bandetails.BanDetailsBeanEOImpl_WLSkel.invoke(BanDetailsBean
EOImpl_WLSkel.java:83)
at
weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java, Compiled Code)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:69)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
5)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
My configuration: WebLogic 5.1, Jolt 1.2, Tuxedo 6.4.

Tuxedo with legacy

          i am using weblogic 7.0
          i would like to know the rite strategy for applying tuxedo 8.0 to the legacy system.
          should i use jolt with the tuxedo \Q?
          or
          corba as the interface of weblogic and tuxedo, with \Q service in tuxedo server?


Thanks Larry, I just found some documentation on the connector and this does look
promising. Unfortunately, I'm going to be constrained by what the customer has in
place. I don't know yet if the customer is using WebLogic. They are in South Africa
and I'm here in the east coast and just got this request this morning. I need to
find out more information to make a better decision.
Thanks again for the response.
Brett
Larry Presswood <[email protected]> wrote:
Or you could use weblogic with the weblogic connector which would allow
you to expose web services and directly invoke legacy tuxedo services
Brett Bergquist wrote:
I'm tasked with interfacing our XML/HTTP based network management systemwithin a
Tuxedo framework for a large customer. I have not received many detailsas of yet
of the customers infrastructure, all that I know is that it is Tuxedobased.
Our network management system is accessible via a XML over HTTP interface.From
what I gather, the customer wants to interact with our NMS via their clientapplications
which use Tuxedo as their messaging architecture.
From what I've read (only a little today), I will need to create a Tuxedocomponent
that advertises services, accepts service requests, interacts with ourNMS via XML/HTTP,
and packages up the response which is sent back to the client.
Does this sound like the correct path to take?
Any and all comments are appreciated.

Sample of mib in Tuxedo

Recently I am going to write a program to monitor Tuxedo, however there is few sample online. What I can find is just a part of whole sample and it misses a lot of things. Also I found nothing in Github. Does any one have a sample to monitor Tuxedo ?
Moreover, is MIB a corret way to approach my goal? Is there any other method allowing me to monitor Tuxedo by writing program?

Hi,
There are several options to monitor and/or manage Tuxedo applications. Out of the box included with Tuxedo are:
Tuxedo MIB - Can pretty much do anything and everything, including management, monitoring, configuration, etc. The MIB can be accessed via service calls to the .TMIB service either embedded in code, or from a tool like ud32. or using the tpadmcall() API.
Command line utilities such as tmadmin, tmloadcf, tmconfig, etc., can be used to also manage, monitor, and configure Tuxedo applications.
SNMP - there is an SNMP agent provided as part of Tuxedo that can be used to monitor almost everything in Tuxedo.
Adding TSAM Plus with or without the Tuxedo Cloud Control plug-in for Oracle Enterprise Manager provides even more options. TSAM Plus Manager can monitor the performance of a Tuxedo application in very fine detail. The Tuxedo Cloud Control plug-in for Oracle Enterprise Manager can monitor at a more course granularity on a polled basis the performance of an application, and can also completely manage and configure a Tuxedo application. Both can allow you to define SLA metrics and take automated action should those SLAs not be met.
So what exactly are you trying to accomplish with what you're planning on developing?
PS If you look through this forum, you should find examples of either programs and/or ud32 scripts making MIB requests.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

Is Jolt part of Tuxedo?

Similar Messages

Maybe you are looking for