Create Oracle Tuxedo Configuration Files

Convert the ubbconfig file into an Oracle Tuxedo configuration file. Once the Oracle Tuxedo configuration file has been generated, it will be placed in the path specified for the TUXCONFIG environment variable.

    Procedure
  1. Type either of the following at a command prompt:
    tmloadcf -y ubbconfig file name or,
    tmloadcf ubbconfig file name
    (Answer "y" if it prompts you on whether it should proceed)
  2. At the command prompt, change the directory to APPDIR and run the following:
    TIBCO_HOME\plugin\tux\version_number\examples\oracle_tuxedo_plugin_examples>tmadmin. A ">" prompt is displayed as shown in the sample below: 
    TIBCO_HOME\plugin\tux\version_number\examples\oracle_tuxedo_plugin_examples>tmadmin
 tmadmin - Copyright (c) 1996-2016 Oracle.
All Rights Reserved.
Distributed under license by Oracle.
Tuxedo is a registered trademark.
    Note: Step 2 needs to be followed if a database is being used. They can be ignored for the examples provided with the plug-in. If the plug-in has to establish multiple connections with the Tuxedo server, you need to modify the default server settings. The following settings control access to your applications:
    • MAXACCESSORS
    • MAXSERVERS
    • MAXWSCLIENTS
    • The JSL configuration settings
    You need to adjust these settings to ensure that the number of allowable client connections is properly configured.
    Note: The JSL settings are: 
    JSL     SRVGRP=GROUP SRVID=ID
CLOPT="-A -- -n //IP_Address:Port_Number
-s <SSL_Port_Number> 
-z<Encryption_Start_Level_Bits>
-Z<Encryption_End_Level_Bits>
-m<minimum JSHs that will be booted >
-M<maximum JSHs that will be booted>
-x<maximum number of clients connected at any one time>"
    The -m and -M determine how many JSH processes will be started. If you want to allow more connections, you should increase the -M value. Depending on the number of connections to be increased, you have to accordingly increase the MAXWSCLIENTS value. The -x value is the multiplexing factor. This determines how many connections can be handled by one JSH process.