Tuxedo Java server configuration file contains the following elements.

• Root Element
  • TJSconfig
• Main elements
  • java-config
  • tux-config
  • classpath-config
  • tux-resources
  • jdbc-resources
  • tux-server-config

• TJSconfig
  
• java-config
  
• tux-config
  
• classpath-config
  
• tux-resources
  
• jdbc-resources
  
• tux-server-config
  

Each Tuxedo Java server class that implements services must implement a set of methods, of which input argument parameter is the TPSVCINFO interface. The methods that are advertised as services must be the public method and have the return type set to void.

Tuxedo Java server advertises all of public methods as services into bulletin board. If Services is specified in configuration file, Tuxedo Java server uses the value of name property as the service name, otherwise, the method name is used as the service name.

Java server has three methods to advertise a Tuxedo service:

1. Advertise a Tuxedo service with the name specified in the configuration file <tux-server-config>/<server-module>/<server-class>/<services>/<service>:name and associate this Tuxedo service with the Java method specified in <tux-server-config>/<server-module>/<server-class>/<services>/<service>:target.

   The following code sample illustrates how to advertise a Tuxedo Service specified in the configuration file.

   <TJSconfig version="2.1">
     ...
     <tux-server-config maxmodules="100" maxadmcmds="100">
       <server-module name="MyAppModule_1">
         <server-class name="MyTuxedoServerClass">
           <services>
             <service name="svc1" target="method1"></service>
             ...
           </services>
         </server-class>
       </server-module>
     </tux-server-config>
   </TJSconfig>

   In this sample, the Java method1 implemented in Java class MyTuxedoServerClass is associated with the Tuxedo service svc1. The exact service handling logic is implemented in MyTuxedoServerClass.method1 written in Java language.

2. If a Java service method implemented in a Java server class specified in the configuration file is not referred, and the "autoadv" attribute of the Java server class is not set (default value is "yes" to keep compatible with previous releases) or explicitly set to "yes", then the service method is advertised to a Tuxedo service with the name same as the service method.

   If the attribute value of "autoadv" is set to "no", then the rest of service methods implemented in this Java server class are not automatically advertised.

3. Invoking TuxAppContext.tpadvertise() to advertise a Tuxedo service. Using this method, the Java server application does not require to explicitly specify the Java server class in the configuration file, and the server class does not inherit from the abstract class com.oracle.tuxedo.tjatmi.TuxedoJavaServer.

Version 2.1 introduces a module entity used to separate a previous application into more modules in order to provide a way to manage the Java server application in fine-grained. Some new attributes are also added to the configuration file.

The following code sample illustrates an example to create Tuxedo Java server configuration file version 2.1.

<TJSconfig version="2.1">
  <java-config>
    <jvm-options>-XX:MaxPermSize=192m -Xms256m </jvm-options>
    <jvm-options>-server</jvm-options>
    <jvm-options>-Xmx512m</jvm-options>
  </java-config>
  <tux-config>
    <server-clopt>-C dom=TMJSVRDOM -t 1000</server-clopt>
    <server-clopt>-n 200</server-clopt>
    <server-propopt> TUXCNF_propK1=propV1 </server-propopt>
    <server-propopt> TUXCNF_propK2=propV2 TUXCNF_propK3=propV3
    </server-propopt>
  </tux-config>
  <classpath-config>
    <classpath>${APPDIR}/classes</classpath>
    <classpath>$USERCLASS/usr/libs/lib1.jar</classpath>
    <classpath>$USERCLASS/usrlib2/*</classpath>
    <classpath>$USERCLASS/usrlib3/*.jar</classpath>
  </classpath-config>
  <tux-resources>
    <classpath>$(APPDIR)/tuxres</classpath>
    <classpath>${APPDIR}/testres</classpath>
    <fld-tbl16-class>test1.FML16TBL, test2.FML16TBL</fld-tbl16-class>
    <fld-tbl16-class>test3.FML16TBL</fld-tbl16-class>
    <fld-tbl16-class>test4.FML16TBL</fld-tbl16-class>
    <fld-tbl32-class>test1.FML32TBL</fld-tbl32-class>
    <fld-tbl32-class>test2.FML32TBL, test3.FML32TBL</fld-tbl32-class>
    <fld-tbl32-class>test4.FML32TBL</fld-tbl32-class>
    <view16-class>test1.VIEW16, test2.VIEW16</view16-class>
    <view16-class>test3.VIEW16</view16-class>
    <view16-class>test4.VIEW16</view16-class>
    <view32-class>test1.VIEW32</view32-class>
    <view32-class>test2.VIEW32,test3.VIEW32</view32-class>
    <view32-class>test4.VIEW32</view32-class>
  </tux-resources>
  <jdbc-resources>
    <data-source vendor="Oracle" driver-type="thin" enabled="true" object-type="usr" jndi-name="none" pool-name="none">
      <classpath>$(JDBC_DRIVER_ORA)/11gR2_ojdbc6_g.jar</classpath>
      <classpath>$(JDBC_DRIVER_ORA)/11gR2_xdb6.jar</classpath>
      <classpath>$(JDBC_DRIVER_ORA)/11gR2_orai18n.jar</classpath>
      <datasource-classname>oracle.jdbc.xa.client.OracleXADataSource</datasource -classname>
        <res-type>javax.sql.XADataSource</res-type>
        <driver-params>
          <connection-url>
            jdbc:oracle:thin:@//10.182.54.144:1521/javaorcl
          </connection-url>
          <property name="user" value="tiger" />
          <property name="password" value="scott" />
          <property name="autocommit" value="true" />
          <property name="autotran" value="yes" />
          <property name="query" value=" " />
          <property name="thread" value="true" />
        </driver-params>
    </data-source>
  </jdbc-resources>
  <jdbc-connection-pool>
  </jdbc-connection-pool>
  <tux-server-config maxmodules="100">
    <server-module name="MyAppModule_1" maxsvrclasses="100" maxadmclasses="64" maxadmcmds="200">
      <classpath>${APPDIR}/Java/module_1/classes</classpath>
      <classpath>${APPDIR}/Java/module_1/lib</classpath>
      <server-clopt>-C dom=TMJSVRDOM1 -g TJSSVRGRP1 -t
        2000</server-clopt>
      <server-clopt>-f application1.xml </server-clopt>
      <server-propopt> K1=V1 K2=V2 </server-propopt>
      <server-propopt> k3=v3 k4=v4</server-propopt>
      <server-class name="MyTuxedoServerClass" autoadv="no">
        <services>
          <service name="mou1_svc1" target="method1"></service>
          <service name="mou1_svc2" target="method2"></service>
        </services>
      </server-class>
      <server-class name="MyTuxedoServerClass2" autoadv="yes">
        <services>
          <service name="mou1_svc3" target="JAVASTRINGSVC"></service>
          <service name="mou1_svc4" target="JAVAFML32SVC"></service>
        </services>
      </server-class>
    </server-module>
    <server-module name="MyAppModule_2" maxsvrclasses="200" maxadmcmds="20">
      <classpath>${APPDIR}/Java/module_2/classes</classpath>
      <classpath>${APPDIR}/Java/module_2/lib</classpath>
      <server-clopt>-C dom=TMJSVRDOM2 -g TJSSVRGRP2 -t
        1000</server-clopt>
      <server-clopt>-f application2.xml </server-clopt>
      <server-propopt> Kmou1=Vmou1 Kmou2=Vmou2 </server-propopt>
      <server-propopt> kmou3=vmou3 kmou4=vmou4</server-propopt>
      <server-class name="MyTuxedoServerClass">
        <services>
          <service name="mou2_svc1" target="method1"></service>
          <service name="mou2_svc2" target="method2"></service>
        </services>
      </server-class>
      <server-class name="MyTuxedoServerClass2" autoadv="yes">
        <services>
          <service name="mou2_svc3" target="JAVASTRINGSVC"></service>
          <service name="mou2_svc4" target="JAVAFML32SVC"></service>
        </services>
      </server-class>
    </server-module>
  </tux-server-config>
</TJSconfig>

Java server retrieves all service methods implemented in application server classes and advertises services under the following rules.

• One method can be advertised for multiple times with different service names.
• The methods that are specified in the configuration file are advertised with the specified service name.
• The methods that are not specified in the configuration file are advertised with the method name as the service name.
• The methods that have been advertised with their specified service names in the configuration file will not be advertised any more with the same method name.

Only the methods that have been declared to public in the server class are retrieved by Java server to participate the advertising action.

Tuxedo Java server configuration file contains the following elements.

• Root Element
  • TJSconfig
• Main elements
  • java-config
  • tux-config
  • classpath-config
  • tux-resources
  • jdbc-resources
  • tux-server-config

• TJSconfig
  
• java-config
  
• tux-config
  
• classpath-config
  
• tux-resources
  
• jdbc-resources
  
• tux-server-config
  

The following code sample illustrates an example to create Tuxedo Java server configuration file version 2.0.

<?xml version="1.0" encoding="UTF-8"?>
<TJSconfig version="2.0">
  <java-config>
    <jvm-options>-XX:MaxPermSize=192m</jvm-options>
    <jvm-options>-server</jvm-options>
    <jvm-options>-DMYVAR="var01" -DMYVAR02="var02"</jvm-options>
  </java-config>
  <tux-config>
    <server-clopt>-C dom=TMJSVRDOM -t 1000</server-clopt>
    <server-clopt>-n 200</server-clopt>
  </tux-config>
  <classpath-config>
    <classpath>${USER_JAVA_LIB}/lib1</classpath>
  </classpath-config>
  <tux-resources>
    <fld-tbl16-class>myfmltbl</fld-tbl16-class>
    <fld-tbl32-class>myfmltbl32,customerflds32</fld-tbl32-class>
    <view16-class>myView</view16-class>
    <view32-class>myView32,customerView32</view32-class>
  </tux-resources>
  <jdbc-resources>
    <data-source vendor="Oracle" driver-type="thin" enabled="true">
      <datasource-classname>oracle.jdbc.xa.client.OracleXADataSource</datasource -classname>
        <driver-params>
          <connection-url>
            jdbc:oracle:thin:@//Server:1521/orcl
          </connection-url>
        </driver-params>
    </data-source>
  </jdbc-resources>
  <tux-server-config>
    <classpath>$TUXJRE/jce.jar</classpath>
    <server-class name="MyTuxedoJavaServer">
      <services>
        <service name="JAVATOUPPER" target="JAVATOUPPER"></service>
        <service name="JAVATOUPPERFORWARD" target="JAVATOUPPERFORWARD"></service>
      </services>
    </server-class>
  </tux-server-config>
</TJSconfig>

Java server retrieves all service methods implemented in application server classes and advertises services under the following rules.

• One method can be advertised for multiple times with different service names.
• The methods that are specified in the configuration file are advertised with the specified service name.
• The methods that are not specified in the configuration file are advertised with the method name as the service name.
• The methods that have been advertised with their specified service names in the configuration file will not be advertised any more with the same method name.

Only the methods that have been declared to public in the server class are retrieved by Java server to participate the advertising action.

The following table lists available properties in a Java server configuration file. Please see the corresponding Java Server Configuration File Schema, which checks the validation of the configuration XML file for more precise information.

Following <ClassPath> element settings are supported in Tuxedo Java configuration file:

<ClassPath>customer_lib_path/*.jar</ClassPath> or <ClassPath>customer_lib_path/*.zip</ClassPath>

Adds all the .jar or .zip archives under customer_lib_path to JVM classpath.

<ClassPath>customer_lib_path</ClassPath>

Adds all the classes under customer_lib_path to JVM classpath.

<ClassPath>customer_lib_path/*</ClassPath>

Adds all the .jar files, .zip files, and classes under customer_lib_path to JVM classpath.

<ClassPath>customer_lib_path/lib1.jar</ClassPath> or <ClassPath>customer_lib_path/lib2.zip</ClassPath>

Adds customer_lib_path/lib1.jar or customer_lib_path/lib2.zip to JVM classpath.

To use the View/View32, you require to specify the View class in <Resources></Resources> element. To use the Fldid()/Fname() properly, you require to specify the FML/FML32 field table class in <Resources></Resources> element.

You require to follow the following rules when creating Java server configuration file:

• Only <TuxedoServerClasses> is mandatory in Java server configuration file, and at least one TuxedoServerClass must be configured.
• Currently, only one <DataSource> element is allowed to be configured in <DataSources> in configuration file. The name property for <DataSource> does not take effect for the present.
• Only <ClassPath>, <fieldTable16Class>, <fieldTable32class>, <viewFile16Class>, <viewFile32Class>, and <Service> element can have multiple entities.
• In <Resources> section, you must configure <fieldTable16Class> first and then <fieldTable32class>, <viewFile16Class>, and <viewFile32Class> in sequence.

Each Tuxedo Java server class that implements services must implement a set of methods, of which input argument parameter is the TPSVCINFO interface. The methods that are advertised as services must be the public method and have the return type set to void.

Tuxedo Java server advertises all of public methods as services into bulletin board. If Services is specified in configuration file, Tuxedo Java server uses the value of name property as the service name, otherwise, the method name is used as the service name.

It assumes that the MyTuxedoServerClass1 Java class defines JAVASTRINGSVC, JAVAFML32SVC, and svc3 methods, and the MyTuxedoServerClass2 Java class defines svc4. In this example, a JDBC connection is made to the Oracle database, and services are exported: svc1, svc2, svc3, and svc4.

The following code sample illustrates an example to create Tuxedo Java server configuration file version 1.0.

<?xml version="1.0" encoding="UTF-8"?>
<TJSconfig>
<ClassPaths>
<ClassPath>/home/oracle/app/javaserver/MyTuxedoServerClass.jar</ClassPath>
<ClassPath>"/home/oracle/jdbc/ucp.jar</ClassPath>
<ClassPath>/home/oracle/jdbc/ojdbc8.jar</ClassPath>
</ClassPaths>
<Resources>
                  <FieldTable16Classes>test1.FML16TBL,
test2.FML16TBL</FieldTable16Classes>
                  <FieldTable16Classes>test3.FML16TBL,
test4.FML16TBL</FieldTable16Classes>
                  <FieldTable32Classes>test1.FML32TBL1,
test2.FML32TBL</FieldTable32Classes>
                  <FieldTable32Classes>test3.FML32TBL1,
test4.FML32TBL</FieldTable32Classes>
                  <ViewFile16Classes>test1.VIEW16,
test2.VIEW16</ViewFile16Classes>
                  <ViewFile16Classes>test3.VIEW16,
test4.VIEW16</ViewFile16Classes>
                  <ViewFile32Classes>test1.VIEW32,
test2.VIEW32</ViewFile32Classes>
                  <ViewFile32Classes>test3.VIEW32,
test4.VIEW32</ViewFile32Classes>
</Resources>
<DataSources>
          <DataSource name="oracle">

<DriverClass>oracle.jdbc.xa.client.OracleXADataSource</DriverClass>
            <JdbcDriverParams>

<ConnectionUrl>jdbc:oracle:thin:@//10.182.54.144:1521/javaorcl</Connection
Url>
              </JdbcDriverParams>
          </DataSource>
</DataSources>
<TuxedoServerClasses>
<TuxedoServerClass name="MyTuxedoServerClass1">
          <Services>
                <Service name="svc1" target="JAVASTRINGSVC"></Service>
                <Service name="svc2" target="JAVAFML32SVC"></Service>
          </Services>
</TuxedoServerClass>
<TuxedoServerClass name="MyTuxedoServerClass2"></TuxedoServerClass>
</TuxedoServerClasses>
</TJSconfig>

If the timeout value is specified for one bean method, the timeout is used for a new transaction. If neither an explicit transaction timeout value nor a Java server transaction manager timeout is specified, the default built-in transaction timeout value is used as 30 to create a new transaction. Java server supports to specify a default transaction timeout value in the Java server configuration file.

The following code sample illustrates how to specify a default transaction timeout value.

<?xml version="1.0" encoding="UTF-8"?>
<TJSconfig version="2.0">
<java-config>
    <jvm-options>-Dtuxedo.tjatmi.defaultTransactionTimeout=60</jvm-options>
</java-config>
</TJSconfig>