CA Harvest SCM includes a Software Development Kit (HSDK), a Java Software Development Kit (JHSDK), and a Component Object Model SDK (COM SDK) that you can use to build applications. To create and build JHSDK applications, the JHSDK must be installed locally. To run JHSDK applications, the JHSDK, HSDK, and the CA Harvest SCM client must be installed locally.
The JHSDK and HSDK files included for UNIX and Linux are the same files included for Windows. However, as the following information illustrates, the library names are slightly different on UNIX and Linux.
|
Platform |
Library Names |
|---|---|
|
Solaris and Linux |
$CA_SCM_HOME/HSDK/lib/libHSDK.so $CA_SCM_HOME/lib/libHSDK.so $CA_SCM_HOME/lib/libJHSDK.so $CA_SCM_HOME/JHSDK/lib/jhsdk.jar |
|
HP-UX |
$CA_SCM_HOME/HSDK/lib/libHSDK.sl $CA_SCM_HOME/lib/libHSDK.sl $CA_SCM_HOME/lib/libJHSDK.sl $CA_SCM_HOME/JHSDK/lib/jhsdk.jar |
|
AIX |
$CA_SCM_HOME/HSDK/lib/libHSDK.a $CA_SCM_HOME/lib/libHSDK.a $CA_SCM_HOME/lib/libJHSDK.a $CA_SCM_HOME/JHSDK/lib/jhsdk.jar |
Note: As previously illustrated, the libHSDK.ext files are installed in two locations ($CA_SCM_HOME/HSDK/lib/, to place the HSDK in its own self-contained directory structure, and $CA_SCM_HOME/lib/, to place all libraries required by the JHSDK in one location). This provides maximum flexibility when using the HSDK.
After installation, you must set up and test the SDK components. You can then use them to build applications.
Note: For information about how to use the HSDK, JHSDK, and COM SDK, see the SDK Reference Guide.
|
Copyright © 2013 CA.
All rights reserved.
|
|