This content has been marked as final. Show 5 replies
The perl repositories provide a module that allows you to make Tuxedo calls from perl. Using that, you could skip the command based mechanism you are currently using and instead use the Tuxedo MIB. By making calls to the .TMIB service, you can pretty much get any information you want about Tuxedo. You could also make these calls from WLS if so desired by setting up the domain gateway and the WebLogic Tuxedo Connector (WTC) and importing the .TMIB service. Then you can use the JATMI interface provided by WTC to make the calls to the .TMIB service.
Oracle Tuxedo Chief Architect
Thank you for your prompt reply.
I will try the 2nd option.
"You could also make these calls from WLS if so desired by setting up the domain gateway and the WebLogic Tuxedo Connector (WTC) and importing the .TMIB service. Then you can use the JATMI interface provided by WTC to make the calls to the .TMIB service."
Setting up the domain gateway, i would think is something that I would need to do via the weblogic console,correct?
Is there a link or good example that does follow this concept? I will research more on it as well.
Sorry, I failed to mention the script queuestatus.sh I have is a vendor specific script that is currently run by our administrators and details of each message is then manually reported out via email.
In order to automate that process , i am trying to do this.
So if I have the WTC domain setup via the WLS console, and import the .TMIB service(which I am still trying to figure out) by going under the import tab, would i be able to configure/call the script queuestatus running on different prod machines this way the grunt work is already done. Similar to a datasource setup for the different databases.
Once I have done that JATMI interface provided by WTC can be used to make the calls to each and get the details of the queues l(ike I would have had i run the script manually) .TMIB service (10 boxes having the scripts then ten .TMIB services)
What I was proposing wouldn't use a script at all. Tuxedo really has no means of supporting scripts beyond whatever the operating system provides. My proposal was to write some code that would query the Tuxedo MIB (Management Information Base) via a service call to the .TMIB service requesting the same information the script is currently gathering. The code that makes these calls could be written in any Tuxedo support language, or by using the Tuxedo domain gateway and WTC on WLS, you could write the code in Java.
The Tuxedo MIB provides access to essentially all the information Tuxedo maintains about the system. You call the .TMIB service like you would any other service passing it an FML32 buffer with certain fields set to tell the MIB what information you want and it returns an FML32 buffer with the information.
If you need to stay with the script, then I'm not sure how to best automate it other than to use something like cron.
Oracle Tuxedo Chief Architect
Thank you for your reply.
I do have to stick with the script.
I have used Java Secure Channel before to execute commands like grep on vendor specific perl scripts to get some key details and automate it that way.
I figured maybe there is something that tuxedo has a command line api that would let me get the output of the tuxedo related script.
Thank you for your help once again