Copyright © Cloud Software Group, Inc. All Rights Reserved

Overview

Purpose

This chapter describes how to configure and start client sessions on Windows and Solaris. These sessions can run on the same machine as the Execution Environment and Data Object Broker or on machines and platforms separate from the Execution Environment and Data Object Broker.

Activity Flow for an ostty User

The following shows the sequence of events when a user logs in from a client:

The numbers in the illustration correspond with the following events:

1.	The client selects an Execution Environment and requests that a session be created.

The osMon process, which an administrator would have started earlier, starts an osee. During initialization, the Execution Environment obtains Execution Environment and session default information.

2.	osee activates the session, passing the user’s client defaults to the session.

The session obtains the Data Object Broker name, session defaults, and interfaces for the Execution Environment binding areas. It merges client and session defaults, and opens the session log.

3.	Activation is completed by connecting to the Data Object Broker and performing login security processing.

4.	The client interacts with the session via screen displays and PF keys pressed.

Actions Initiated by a Client

When a client is started, the following actions take place:

1.	An osee starts if one is not already running.

2.	A session starts within the Execution Environment.

3.	The first rule of the session starts.

If you are using the TIBCO Object Service Broker UI or the ostty client, you can start up additional sessions within your Execution Environment when the initial session is started.

When one of these clients is shut down, the following actions take place:

4.	The session ends.

5.	If no other user is logged in to the Execution Environment, the osee ends.

Communications Between Clients and Servers

TIBCO Object Service Broker uses:

•	The IPC mechanism between the Execution Environments and the Data Object Broker when they reside on the same machine

•	TCP/IP when they reside on different machines

See Also

Appendix A, Sample Configurations to see how these are used in a sample TIBCO Object Service Broker installation.

TIBCO Object Service Broker for Open Systems External Environments for a more detailed activity flow.

Copyright © Cloud Software Group, Inc. All Rights Reserved