You need to publish multiple outlines periodically, which are under constant development Identify the two statements that are true in such a situation.

You need to publish multiple outlines periodically, which are under constant development Identify
the two statements that are true in such a situation.

You need to publish multiple outlines periodically, which are under constant development Identify
the two statements that are true in such a situation.

A.
You can publish a different outline to the same location by using parameters.

B.
You can use command-line publishing in a batch to publish multiple outlines.

C.
You can customize the language of the command-line publishing output.

D.
You can use command-line publishing to publish only server content.

E.
You can use command-line publishing to publish content to a different Knowledge Center
server.

Explanation:
Note:You can launch the publishing process from a command line. This allows you
to create a
batch publishing task that can be scheduled and run automatically at a time when the
server or network is not as busy, such as at night or on the weekend.
You must publish content first to create a publishing task. This creates a folder structure
and at least three files that are needed for command line publishing. The selection.xml,
publishing.project.xml and at least one configuration (<format_guid>.config.xml) files are
created at the root of the destination folder.
The selection.xml file contains a list of the documents to publish, the
publishing.project.xml contains global parameters that apply to all publishing formats and
a list of all configuration files (<format_guid>.config.xml) – one for each output format.
The <format_guid>.config.xml contains the parameters that apply to a particular format.
The output from command line publishing will be stored in the same location as it would
be if the publishing process was launched from within the Developer.
Note 2:Command-Line Publishing
To use command-line publishing, you create a command line in the following format:
\path\commandlinepublish <settings> /profilename:<profile_name>

/password:<password>
or
\path\commandlinepublish <settings> /profile:<profile_path>
/password:<password>
You can use either the profilename or profile parameter; you do not need to use both. The
password parameter is optional.
* Parameter<settings>
Path to the selection.xml file in the destination
location for the published content.
*Parameter/profilename
The name of the user profile to use for the
publishing process. This profile must exist in the
UserProfiles folder of the computer on which the
publishing job is being run. If the password is not
stored with the profile, you must use the
/password parameter.
OracleUser Productivity, Content Development,Command-Line Publishing



Leave a Reply 0

Your email address will not be published. Required fields are marked *