Transitioning From Oracle® Solaris 10 JumpStart to Oracle Solaris 11.2 Automated Installer

Exit Print View

Updated: July 2014

Using js2ai to Convert sysidcfg Files to System Configuration Profiles

Use the js2ai command with the –s option to convert any sysidcfg files that are associated with this JumpStart configuration to system configuration profile files. Initially, use the –S option to skip validation.

For each sysidcfg file processed, js2ai creates an AI system configuration profile file named sc_profile.xml in the directory where the js2ai command was invoked. Use the –D option to specify a different directory for the sc_profile.xml file.

When you receive a message that the conversion completed successfully, run the js2ai command without the –S option to validate the output sc_profile.xml file. Validation errors must be corrected in the sc_profile.xml file.

    If you do not see a message that the conversion was successfully completed, examine the error report and the js2ai.log file. The error report and the log file report warnings, process errors, unsupported items, conversion errors, and validation errors. The error report is a table output to stdout that shows the number of each type of error that was encountered in converting the sysidcfg file. The log file describes the problems.

  1. Correct any process errors.

  2. Remove any lines from the sysidcfg file that are listed as unsupported items.

  3. Examine the conversion errors and correct the errors if possible. Otherwise, remove the lines that are causing the errors.

  4. Examine any warning messages and make sure no corrections are necessary.

To display more information for a conversion use the –v with the js2ai command. For more information, see Displaying Additional Configuration Conversion Information.

To validate a specific output system configuration profile, run the js2ai command with the –V option. See the example in Validating an Output System Configuration Profile.

# js2ai -V path/sc_profile.xml