1. Programming an Oracle Tuxedo ATMI Application Using C
  2. Programming a Multithreaded and Multicontexted ATMI Application
  3. Planning and Designing a Multithreaded/Multicontexted ATMI Application
  4. How Multithreading and Multicontexting Work in a Client
  5. Start-up Phase
  6. Client Threads Join Multiple Contexts

10.2.4.1.1 Client Threads Join Multiple Contexts

A client in an Oracle Tuxedo multicontexted application can have more than one application association as long as the following rules are observed:

  • All associations must be made to the same installation of the Oracle Tuxedo system.
  • All application associations must be made from the same type of client. In other words, one of the following must be true:
    • All application associations must be made from native clients only.
    • All application associations must be made from Workstation clients only.

To join multiple contexts, clients call the tpinit() function with the TPMULTICONTEXTS flag set in the flags element of the TPINFO data type.

When tpinit() is called with the TPMULTICONTEXTS flag set, a new application association is created and is designated the current association for the thread. The Oracle Tuxedo domain to which the new association is made is determined by the value of the TUXCONFIG or WSENVFILE/WSNADDR environment variable.

Parent topic: Start-up Phase