The following information describes troubleshooting the Device Pack Generator Application.
Symptom:
I have to know the release of CA Infrastructure Management that the application supports to make sure that the application is compatible in my CA Infrastructure Management environment.
Solution:
The sample device packs that the application generates were tested using CA Infrastructure Management Release 2.2.0 and Release 2.2.1 (English version only).
Symptom:
I cannot locate the application after unzipping the ems_installer.zip file.
Solution:
Navigate to the unzipped folder. Go to IMDevicePackGenerator_<version>, and then go to the bin folder, where the executable scripts are located as follows:
Windows: createDevicePack.bat
Linux: createDevicePack.sh
Symptom:
I cannot run the application.
Solution:
Verify that you have provided your devicePackConfig.xml file with data in the required fields. You cannot run the application without the devicePackConfig.xml file. However, you do not need to provide data for all of the fields in the devicePackConfig.xml file. The mandatory fields for which you must provide data are:
Symptom:
I cannot locate the output files of the application.
Solution:
The output of this application is two files, DevicePack.jar and Certification.jar. If you execute the application within the ems_installer package, the output files are located inside the ems_installer/devicepacks directory. Otherwise, the output files are located inside the IMDevicePackGenerator_<version>/ bin directory.
Symptom:
I ran the application but no output files were generated.
Solution:
To verify that validation of the devicePackConfig file is successful, execute the following command:
createIMDevicePack <path_of_devicePackConfig.xml> -v
If the validation is unsuccessful, review the error message in the console. To fix the problem, make the recommended changes in the devicePackConfig file and rerun the script using the -v option.
You can also verify that the directory information provided in <Path> is correct and that it contains the CSV files. Also verify that the header information provided matches what is in the CSV files.
If the problem persists, contact CA Technologies Support.
|
Copyright © 2014 CA.
All rights reserved.
|
|