StarTeam
Software Development Kit
Platform Issues
Win32 COM Interfaces
The StarTeam COM interfaces
are available only on Win32 platforms.
As of release 5.3, the
StarTeam COM interfaces use a Certified Java VM,
installed in a private folder.
The default Java
configuration for applications that use the StarTeam COM interfaces is
specified in ,
where matches the version number of the
StarTeam COM interface DLL. For example, the default Java configuration for is specified in .
A COM application can
override the default Java configuration by providing an in the same
folder as the program executable.
In addition, any COM
application can modify the Java configuration programatically, before the Java
VM is loaded. For more information, see the "IStInitializer" topic in
the StarTeam SDK COM API Reference.
Win32 Java Interfaces
As of release 5.3, the
StarTeam SDK Java classes are found in , where is the release number. For example, the 5.3 Java classes
are found in .
When running under Win32,
the StarTeam Java interfaces require several native libraries (for example, , , and so on.) installed in the SDK's
folder. These native libraries must
be available to the Java VM at runtime.
One way to ensure that the
native libraries are available to the Java VM is to include the SDK's folder in the (or ) environment variable.
Alternatively, you can
include the SDK's folder in the VM's system property (using on the java command line).
As of release 5.3, the
Starteam SDK includes ,
an executable program that makes it easier to launch StarTeam Java applications
under Win32. StJava will launch the appropriate certified Java VM, including
the StarTeam SDK's jar file in the classpath, and the SDK's lib folder in the
library path, as appropriate.
Linux/Solaris
The StarTeam SDK Java
classes can be used on any platform with a Java VM 1.1 or higher.
The native dlls listed
above for Win32 are not required on other platforms. The SDK will attempt to
load some of these libraries and will fail. Some Java VMs will print out a
warning about the shared library not being found. You can ignore those messages
as the SDK code properly handles the situation. It is a bug in the Java VMs
that display this exception even though it is handled in the calling code.
The file time stamp access
and read/write protection is handled by exec() calls. A file called is written to your directory that contains the names
and parameters of external programs to exec (for example, the command in Unix).
The native code to look up
environment variables is not needed for other platforms because the found in is used instead.
Secure (encrypted)
connections are supported on non-Win32 platforms using a pure Java encryption
library from RSA. Please contact your sales representative for information on
purchasing this extra component.
MacOS
We have not yet tested the
SDK in MacOS. We would be interested to hear about your experiences. One
feature we know is missing is support for Mac resource forks. Only the data
fork for a file can be checked-in/out.
Last Modified December 3,
2002