Develop > Command-Line Interfaces > ContentAutoUpload Command-Line Interface

ContentAutoUpload Command-Line Interface

The Content Pack Auto Upload command-line interface enables you to upload the Content Pack Definition files from the default content pack directory on the data processing server.

This section describes the options and parameters available in the ContentAutoUpload command-line interface.

Location

The ContentAutoUpload command-line interface is located on the data processing server in:

<OMi_HOME>/bin/ContentAutoUpload

Synopsis

ContentAutoUpload <Operation> [Option]

<Operation> (one of the following):

  • Import Operations:

    -autoUpload [-uploadFolder <directory>]

    [-forceReload]

  • Miscellaneous Operations:

    -version

[Option]:

-verbose

Options

Option

Description

-a,-autoUpload

Automatically uploads the Content Pack Definition files from the default content pack directory on the data processing server:

<OMi_HOME>/conf/opr/content/<locale>/

Windows: C:\HPBSM\conf\opr\content\<locale>\

Linux: /opt/HP/OMi/conf/opr/content/<locale>/

If you want to upload content pack definitions from an alternative directory on the data processing server, specify the directory location using the -uploadFolder <directory> option.

If you have more than one data processing server, you must keep the content pack folders synchronized because it is not possible to specify from which data processing server content packs may be imported.

All predefined content pack definition files in the specified directory are imported in the order of their dependencies. If a content pack definition is already uploaded to the repository, it is not uploaded again.

For information about import errors, see the following log file:

<OMi_HOME>/log/jboss/opr-webapp.log

Windows: C:\HPBSM\log\jboss\opr-webapp.log

Linux: /opt/HP/OMi/log/jboss/opr-webapp.log

-forceReload

Enforces the reload of all content packs located in the default directory (<OMi_HOME>/conf/opr/content/<locale>/) or the directory specified using the -uploadFolder <directory> option. Non-customized content is overwritten.

-h,-help

Displays a summary of the command options and exits.

-skipCheck

Omits the content pack consistency check. The content pack consistency check verifies if dependent content that is not part of another content pack is either in the content pack itself or already imported.

Caution: This option should only be used when upgrading to a newer version of the Content Pack.

-uploadFolder <directory>

If you want to upload content packs from an alternative directory, specify the directory location using the -uploadFolder <directory> option.

For example:

ContentAutoUpload -a -uploadFolder c:\temp

-v,-verbose

Prints verbose output.

-version

Prints the version information of the command and exits.

Restrictions

Non-admin users also need the following file permissions to operate this command-line tool:

File Windows Permissions Linux Permissions
<OMi_HOME>/conf/TopazInfra.ini read r
<OMi_HOME>/log/opr-clis.log full control rw

<OMi_HOME>/log/opr-pgctl.log

Note: This file is not available on gateway server systems.
full control rw
<OMi_HOME>/conf/encryption.properties read r
<OMi_HOME>/conf/seed.properties read r

Exit Status

Exit Status

Description
0

SUCCESS (At least one content pack was imported and no errors occurred.)
1

FAILURE (No content packs were imported - complete failure.)
2

FAILURE_PARTIAL (Some content packs were imported successfully, others had errors.)
3

NO_OPERATION (No new content was found for upload.)
4

NO_PERMISSION (User does not have appropriate permissions to execute this tool.)
5

SYNTAX_ERROR (Wrong command-line arguments were specified.)

Send Help Center feedback