10
Note If there are templates that include OXPd settings, you must import the OXPd files into the
cloned HP Web Jetadmin server (step 5), and then edit the templates that include the
OXPd settings in the cloned HP Web Jetadmin server (step 9b).
10. Configure all of the encrypted data. The following are some examples of encrypted data:
• Global device credentials, such as the SNMP Community Name and EWS password
(available under Tools > Options > Shared > Credentials > Device)
• HTTP proxy user and password settings
Method 2 for cloning
Another technique for cloning involves pointing an HP Web Jetadmin installation to another database
or a remote database by editting the DatabaseSettings.config.xml file. For instructions on how to
connect to a remote database, see the Using Microsoft SQL Server with HP Web Jetadmin white
paper. This white paper is available from the HP Web Jetadmin support page
.
Cloning by pointing to another HP Web Jetadmin database maintains most of what is in HP Web
Jetadmin, such as devices and templates. However, encrypted data no longer works. For more
information, see Limitations of cloning
. In addition, when cloning by pointing to another HP Web
Jetadmin database, the items that are stored in the Settings directory are not cloned. These items
include archived reports, firmware repository, archived data exports, file repositories, and so on.
When an installation of HP Web Jetadmin is pointed to a database, version matching occurs whereby
HP Web Jetadmin updates the database tables if the database version is found to be older than the
HP Web Jetadmin installation version.
Limitations of cloning
Cloning cannot duplicate every single item from the original machine. The following limitations exist
with a cloned machine:
1. If alerts that involve traps were configured on the original machine, the alerts settings are copied
to the new machine during cloning. However, nothing has instructed the devices to start sending
traps to the new HP Web Jetadmin installation. To set the new HP Web Jetadmin installation to
process the alerts, modify the entries in the trap destination lists of each device. HP Web Jetadmin
provides the ability to modify the device trap destination lists in both single and multiple device
configuration modes.
Note It is possible to export/import alert templates from HP Web Jetadmin 10.4 SR2 and
later. Instead of modifying existing trap alerts, unsubscribe all alerts on the original
HP Web Jetadmin server and apply the alert subscription templates to the correct
devices on the new/cloned HP Web Jetadmin server.
2. Reports that display information pertaining to which user printed documents are not processed for
the same reason as the alerts issue. By User reports rely on devices sending traps after each print
job. Because HP Web Jetadmin now runs on a new machine, new entries must be made in the
trap tables of all the devices to send traps to the new machine. HP recommends that you
resubscribe to the By User collections on the new HP Web Jetadmin machine to ensure that the
entries are written to the trap tables.
3. When restoring the settings and database information to the HP Web Jetadmin host, encrypted
data no longer functions if the host or Windows OS instance is different from the host or
Windows OS instance that was used to process the original file-set. In these cases, the encrypted
data can be restored manually by using the HP Web Jetadmin User Interface. The following are
some examples of encrypted data:
• Global device credentials, such as the SNMP Community Name and EWS password
(available under Tools > Options > Shared > Credentials > Device)
(54 páginas)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comentários a estes Manuais