Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 4 TIBCO Object Service Broker Execution Environment and Client Sessions : Operating TIBCO Object Service Broker Clients

Operating TIBCO Object Service Broker Clients
Types of TIBCO Object Service Broker Clients
The following table describes the TIBCO Object Service Broker clients:
TIBCO Object Service Broker UI
The TIBCO Object Service Broker UI help file; and TIBCO Object Service Broker for z/OS Installing and Operating
Provides a graphical user interface (GUI) to develop applications.
Object Integration Gateway
TIBCO Object Service Broker Object Integration Gateway and the Object Integration Gateway help files.
Provides a graphical development interface for creating and modifying TIBCO Object Service Broker and Object Integration Gateway objects.
TIBCO Object Service Broker Adapter for JDBC-ODBC
TIBCO Object Service Broker for Open Systems External Environments.
Provides an application program interface into TIBCO Object Service Broker to access data in ODBC-compliant data sources.
Provides a command line interface to start and control the execution of applications.
Provides a text-only interface to start and control the execution of applications.
SDK (C/C++)
TIBCO Object Service Broker for Open Systems External Environments
Provides an application program interface into TIBCO Object Service Broker for use when accessing an Execution Environment on a remote system.
SDK (Java)
TIBCO Object Service Broker for Open Systems External Environments
Provides an application program interface into TIBCO Object Service Broker for use when accessing an Execution Environment on a remote system in a Java environment.
Prerequisites
The following prerequisites must be in place before you can activate a client:
The OS_ROOT environment variable must be set to the installation folder.
Refer to Starting the Data Object Broker for details.
Refer to Starting osMon for details.
Starting osMon
To start osMon, do one of the following:
osMon [DOB=dobname]
You must provide the DOB argument if it does not appear in your mon.prm file.
Starting osMon as a Windows Service
You can set up osMon as a Windows service and, if you want, have it start automatically when you start Windows.
Running osMon as a Windows Service
To run osMon as a Windows service, it must be installed to make it available to the Windows services manager through the Registry. You must run the following command only once:
osMonSvc -i service_name
where service_name is a unique name you assign to the service.
You should see a message telling you that the service is installed.
While installing the osMon service, you can specify that it depends on a Data Object Broker service that is running. Run the command—
osMonSvc -i service_name -d dob_service_name
—to inform Windows that the Data Object Broker service dob_service_name must be running before the osMon service starts. Afterwards, Windows automatically starts the Data Object Broker service before the osMon service, if the former is not already running.
If the osMon configuration is named something other than the default name DEFAULT in the mon.prm file, you must specify that name as a parameter override when installing osMonSvc as a service. For example, if the osMon configuration name is DEFAULT1, run this command to install the osMon as a service with that configuration:
osMonSvc -i service_name -o name=DEFAULT1
Feel free to combine the -o override option and the -d dependency option:
osMonSvc -i service_name -d dob_service_name -o name=DEFAULT1
Starting the osMon Windows Service
You can start the osMon service in either of these two ways:
1.
2.
3.
Run the net start service_name command.
To have osMon start automatically:
1.
2.
3.
4.
This causes osMon to start when the machine is rebooted. You can shut down and restart your machine if you want to ensure automatic startup is functioning correctly.
Stopping the osMon Windows Service
To stop the osMon service, run the net stop service_name command.
Uninstalling the osMon Windows Service
To uninstall the osMon service, run the osMonSvc -u service_name command.
Getting Help on osMon
To get basic help with osMon commands, run the osMon HELP command.
Reloading Parameter Settings
To reload the Execution Environment and session parameter settings for a running osMon, run the following command:
osMon RELOADPARMS [PORT=port]
For an explanation of the variables in the commands, refer to Getting the Variable Values for osMon Commands
Inquiring into the Status of osMon
Details
To check on the status of osMon, from a command prompt, issue the following:
osMon STATUS=DETAIL
In response, you find out the following information:
Sample output, where two sessions are running:
osmon at host=[] port=9068 is: online
name: [DEFAULT]:0
pid: 141
counters: max=25, total=2 (actual=2, starting=0, pending=0)
map: 0 1
Summary
You can also use the following command to get a summary status report, which tells you the number of osee processes and the number of sessions running:
osMon STATUS=SUMMARY
Sample output:
osmon at host=[] port=9068 is: online
osee processes: 1
sessions: 2
Starting and Exiting from ostty
Starting ostty
To start ostty, do one of the following:
The menu item is a shortcut to a text interface (install_path\bin\ostty.exe).
ostty
The Execution Environment starts automatically and a workbench similar to the following appears.
 
Windows: ostty requires the use of physical or virtual function keys. The ostty function keys F1 through F12 are directly supported on a Windows keyboard. ostty function keys F13 through F24 are emulated by pressing Shift+F1 through Shift+F12.
Solaris: The ostty function keys F1 through F24 are emulated by pressing Ctrl+F, followed by two digits corresponding to the function key number. For example, ostty function key F3 is emulated by pressing Ctrl+f, followed by digit 0 (zero) and digit 3.
Default Developer’s Workbench Illustrated

 
HURON USR40 TEST: N BROWSE: N 2:54 PM THURSDAY JUL 24 2012
ER edit rule ==> SU MO TU WE TH FR SA
EX execute rule ==> 1 2 3 4 5
DB debug rule ==> 6 7 8 9 10 11 12
BR browse table ==> 13 14 15 16 17 18 19
ED edit table ==> 20 21 22 23 24 25 26
27 28 29 30 31
OS object set ==>
DS define screen ==>
DR define report ==>
DT define table ==>
DL define library ==>
GR generate rpt ==>
COMMAND ==> __
 
PFKEYS: 2=LOGS 3=EXIT 12=EXIT

 
Exiting from the ostty Client
To exit from the TIBCO Object Service Broker workbench and the ostty client, press PF3 from the workbench.
Starting the TIBCO Object Service Broker UI
To start the TIBCO Object Service Broker UI, perform the following:
1.
2.
Access the OSB Perspective from the Eclipse menu by selecting Window> Open Perspective>Other. The Other Perspective dialog displays.
3.
Select OSB Perspective and click OK.
For information about using the TIBCO Object Service Broker UI, refer to the TIBCO Object Service Broker UI online help.
Starting osBatch
The osBatch utility runs an TIBCO Object Service Broker batch client as a standard Windows or Solaris application. The executable is located in install_path/bin. To start osBatch, issue the osBatch command, from a command prompt, with the parameters you require, as shown in this example:
osBatch DOB=PROD U=JOEB P=XYZ123 R=BATCH1 SEARCH=L NOBROWSE LIBRARY=PRODBATCH
Ending a Session
Other than pressing PF3, you can also end an Execution Environment session by one of the methods shown below (for an explanation of the variables in the commands, refer to Getting the Variable Values for osMon Commands).
Shutdown of a Session
To end a session, from a command prompt, issue the following:
osMon STOPSESS=eename:eeinstance:sessioninstance HOST=host,PORT=port
Shutdown of an Execution Environment
To shutdown an Execution Environment from a command prompt, issue the following:
osMon CLOSEEE=eename:eeinstance HOST=host,PORT=port
The TIBCO Object Service Broker monitor process shuts down the Execution Environment as soon as all its sessions are terminated.
Immediate Shutdown of an Execution Environment and All Its Sessions
To stop immediately from an Execution Environment and its sessions, from a command prompt, issue the following:
osMon STOPEE=eename:eeinstance HOST=host,PORT=port
Exiting from osMon
For an explanation of the variables in the commands that follow, refer to Getting the Variable Values for osMon Commands.
Shutdown
To exit from osMon, from a command prompt, issue the following:
osMon CLOSE [HOST=host,PORT=port]
The TIBCO Object Service Broker monitor process shuts down its listening port and waits for any child Execution Environment processes to terminate before exiting.
Immediate Shutdown
To exit immediately from osMon and all its child processes, from a command prompt, issue the following:
osMon STOP [HOST=host,PORT=port]
Immediate Shutdown of All osMon Processes
To exit immediately from all osMon processes running on your machine and all their child processes, from a command prompt, issue the following:
osMon STOPALL HOST=host,PORT=port
Getting the Variable Values for osMon Commands
To get the values of the variables used in the commands in this section, perform these steps:
1.
The log files reside in your \install_path\log folder and have a default name based on the structure explained under the EELOG or the SESSIONLOG Execution Environment parameter, for example, session.DEFAULT.DEFAULT.DEFAULT.12.17‑11.07.47.0.0.log.
2.
For example, to shut down a session, you would check on the values of the EENAME, EEINSTANCE, and SESSIONINSTANCE parameters in the session log file and issue a command similar to the following:
osMon STOPSESS=DEFAULT:0:0
Location of parameters:
See Also
TIBCO Object Service Broker for Open Systems Utilities for details on osBatch.
TIBCO Object Service Broker Getting Started for information on using the developer workbench.
TIBCO Object Service Broker Parameters for information on Execution Environment parameters.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved