OSS/J TCK

OSS/J Technology Compatibility Kit (TCK)

This document describes how to utilize the OSS/J TCK in conjunction with the Application Server.

This application document contains the following sections:


Overview



The following instructions describe how to run the TCK.

Note: In the following, no file name extension for the scripts will be named. UNIX scripts will have extension '.sh', Windows scripts have the extension '.bat'. The scripts themselves are named identically for Windows and UNIX.

Setting up the environment

In order to successfully run the TCK, the <install_dir>/scripts/env_j2eesdk script has to be configured:

Property
Description
Windows Default
Unix Default
AS_HOME
The installation directory of the J2EESDK.
C:\Sun\Appserver
~/SUNWappserver
HOSTNAME
The hostname of the server
localhost
localhost
PORTNUMBER
The port of the application server
3700
3700
INTEGRATION_PROFILE
The integration profile of the applicaition to test
java|xml
java|xml

Download and copy (and rename) junit.jar (v 3.8.1 or later) into the <install_dir>/lib/junit-3.8.1.jar directory from JUnit
Note: if another version than 3.8.1 of Junit is used, the variable JUNIT needs also to be updated accordingly.

The client library for the deployed application shall be created using the following instructions:
TCK Properties Setting :

The
<install_dir>/scripts directory contains property files with parameters used by the TCK during testing.The property file is named tck_properties.txt. Edit this file and change the properties accordingly to the implementation to be tested. The files, named *_tck_properties.txt are provided as example to test other OSS/J implementations than the OSS Common RI.

The script generate_jvtSessionList_j2eesdk.* can be run first to help in the customization of the section "JVT information" in the tck_properties.txt. It will introspect your <jar_name> file and produce for example the following lines:

# --------- Customization begin---------
# from jar_name = ../lib/common_exClient.jar
# For each following Home, you have to provided, its JNDI name.

ossj.common.ex.VpnServiceRemote_HOME="<class name of the corresponding home interface>"
ossj.common.ex.VpnServiceRemote_JNDINAME="<JNDI name>"


# --------- Customization end  ---------
                


Runing the TCK



From <install_dir>/scripts directory, select one of the following aproaches to run the TCK:

The two following scripts can use different JUnit starters

Additional Information


For more information how to use the TCK and how it is designed, take a look at the documentation for the earlier versions of the TCK:


Note: To run the TCK from a remote machine, the following needs to be checked:


Copyright © 2002-2006 The Members of the OSS through JavaTM Initiative. All Rights Reserved. Use is subject to license terms.