Customizing the Product › Software Development Kit (SDK) Components › How to Set Up and Test the SDK Components › Test the HSDK and JHSDK Installation (UNIX, Linux, and zLinux)

Test the HSDK and JHSDK Installation (UNIX, Linux, and zLinux)

Note: The instances of Linux in this section refer to both the Linux and zLinux operating environments.

The next step you must complete for the Software Development Kit (SDK) components is to test the HSDK and JHSDK installations to verify that they were installed successfully and that the SDK is ready to be set up. These steps involve running the HSDK or JHSDK sample test program. The HSDK includes a sample test program (hsdksample.cpp), the makefile (hsdksample.mak), and shell script (hsdksample.sh) to build it. The hsdksample.sh file sets the proper include and library paths for the build.

The sample program requires the existence of the CA Harvest SCM project named SDKSampleProject in the product repository. The SDKSampleProject.har file is a product export file of the required project.

Follow these steps:

1. If you have not already done so, set up the library path and system variables.

   Note: For information about setting up the library path and system variables, see Set Up a Development Environment for the Command-line utilities.

2. Load the script for initializing the Enterprise Communicator (PEC) for use with the HSDK and JHSDK by running one of the following commands from the /bin subdirectory in the PEC installation directory:
   • If you are using the Bourne, Korn, or Bash shell, run the following command:

     . ./rtinit.sh
     

   • If you are using the C shell, run the following command:

     source rtinit.csh
     

3. Verify that RTHOME is set by running the following echo command:

   echo $RTHOME
   

4. Run the sample test program by successfully completing these steps:
   1. (AIX users only). In the hsdksample.sh file, in the AIX section, replace the stlport-4 6.2 references with the complete path name in which stlport 4.6.2 is installed.
   2. Run himpenv to import the SDKSampleProject.har file.
   3. Create the user sdkuser with the password sdkpass.
   4. Add the sdkuser to the SDKSampleProject user group and to the approval list on the Approve process in state-1.
   5. Create a read/write repository named \sdkrep and assign it to the baseline view of SDKSampleProject.
   6. The directory HSDK/Release contains the compiled version of the sample program. Remove the compiled version from the directory so you can rebuild the sample program.
   7. Change directory (cd) to the Samples directory.
   8. (Red Hat Linux users only). Enter the following command:

      export CCOPTS=-DRHEL_AS3
      

   9. To rebuild the sample program, run the hsdksample.sh script with the target RELEASE:

      ./hsdksample.sh RELEASE
      

   10. Check the HSDK/Release directory for the newly rebuilt sample program.
   11. Execute the sample program in HSDK/Release, by entering the ./hsdksample -b <brokername> command.
   12. Check the HSDKSample.log file for the results.

The following is a typical example for setting up the HSDK and JHSDK environment on a Solaris system:

CA_SCM_HOME=/opt/CA/scm
. /opt/CA/pec/bin/rtinit.sh #Sets $RTHOME, $RTARCH, LD_LIBRARY_PATH
LD_LIBRARY_PATH=/usr/local/ETPKI:$LD_LIBRARY_PATH
# Uncomment below and edit for custom ETPKI path that is the 
# alternative to /usr/local/ETPKI, such as /opt/CA/ETPKI 
LD_LIBRARY_PATH=${CA_SCM_HOME}/lib:$LD_LIBRARY_PATH
PATH=${CA_SCM_HOME}/bin:${PATH}
export CA_SCM_HOME LD_LIBRARY_PATH PATH