How do I check in a Knowledge Script (KS) or Knowledge Script Group (KSG) via the command line? (NETIQKB3082)

  • Document ID:7703082
  • Creation Date:02-Feb-2007
  • Modified Date:18-Jan-2011
    • Micro Focus Products:
      AppManager

Environment

NetIQ AppManager 6.x
NetIQ AppManager 7.0.x

Situation

How do I check in a Knowledge Script (KS) or Knowledge Script Group (KSG) via the command line?
How do I use the kscheckin.exe (kscheckin) command?

Resolution

If the "Check in Knowledge Script" and "Check in Knowledge Script Group" options are grayed out within the Operator Console, the Developer's Console license is not enabled for NetIQ  AppManager.  However, you can check in or check out the Knowledge Script or Knowledge Script Group via command line.

To check in a knowledge script via command line in NetIQ AppManager 6.x and 7.x  type the following with the appropriate switches:

kscheckin -e <SQLSERVER>:<DBNAME>:<USER>:<PASSWORD> -k <FULLPATHANDFILENAME>

Example:

C:\kscheckin.exe -e repository:qdb:SA:password -k C:\Scripts\NT_CPULOADED.qml

Where:

  • SQLSERVER is the name of the SQL Server where the AppManager Repository (database) resides.
  • DBNAME is the name of the AppManager Repository (database). The default is QDB.
  • USER is the login name required to check in the Knowledge Script.
  • PASSWORD is the password for the required login name above.
  • FULLPATHANDFILENAME is the full path and file name of the Knowledge Script to be checked in. This should be in .ebs format.

Parameters:

[-e SQLSERVER:DBNAME:user:password]
[-s] toggle syntax checking (default on)
[-o] toggle overwriting existing KS in Repository (default on)
[-m] KS only, comment to be stored in KSHISTORY table
[-k ks_file(s)]
[-g ks_group_file(s)]

Example:

kscheckin -e SQLSERVERNAME:QDB:netiq:xxx -k c:\ksdepot\nt_CPULOADED.qml

Additional Notes:

  1. Leave user empty to indicate NT authentication.
  2. All option values are case-sensitive if SQL server is case-sensitive.
  3. Filename may have Windows file wildcards, '*' and '?'.
  4. Each option is position dependent and can repeat. Options are like commands processed one by one, from left to right. For example, the syntax of a KS file will not be checked if -s appears in front of the -k option below.

To check in a Knowledge Script Group (KSG) via command line in NetIQ AppManager 6.x and 7.x type the following with the appropriate switches:

kscheckin -e <SQLSERVER>:<DBNAME>:<USER>:<PASSWORD> -g <Path to the .KSG file>

Example:

C:\kscheckin.exe -e repository:qdb:SA:password -g C:\Scripts\KSG_NTCoreScripts.ksg

This will require a subfolder that contains the actual Knowledge Scripts to be contained within the KSG.  For the example listed above, the Knowledge Scripts would be need to be located in  C:\Scripts\KSG_NTCoreScripts\

Where:

  • SQLSERVER is the name of the SQL Server where the AppManager Repository (database) resides.
  • DBNAME is the name of the AppManager Repository (database). The default is QDB.
  • USER is the login name required to check in the Knowledge Script Group.
  • PASSWORD is the password for the required login name above.
  • FULLPATHANDFILENAME is the full path and file name of the Knowledge Script Group to be checked in. This should be in .ebs format.

Parameters:

[-e SQLSERVER:DBNAME:user:password]
[-s] toggle syntax checking (default on)
[-o] toggle overwriting existing KS in Repository (default on)
[-m] KS only, comment to be stored in KSHISTORY table
[-k ks_file(s)]
[-g ks_group_file(s)]

Example:

C:\kscheckin.exe -e repository:qdb:SA:password -g C:\Scripts\KSG_NTCoreScripts.ksg

Additional Notes:

  1. Leave user empty to indicate NT authentication.
  2. All option values are case-sensitive if SQL server is case-sensitive.
  3. Filename may have Windows file wildcards, '*' and '?'.
  4. Each option is position dependent and can repeat. Options are like commands processed one by one, from left to right. For example, the syntax of a KS file will not be checked if -s appears in front of the -k option below.

Additional Information

Formerly known as NETIQKB3082

The Developer Console license is required to  check in Knowledge Scripts and Knowledge Script Groups within the AppManager Console.  If you do not have the license for this component, it may be necessary to use the Command line utility to accomplish the task.

For more information about the Check In/Check Out Knowledge Script options, refer to the following article:

NETIQKB4523:Check-In Knowledge Script and Check-Out Knowledge Script Options Disabled in the AppManager Operator Console