Fujitsu V8.0B10 manual Migration aspects when upgrading from former Xprint versions

Page 10

Message catalogues

 

N.A

 

 

 

Compatibility Libraries

 

N.A

 

 

 

Inter domain Interoperability

 

X

 

 

 

Development Tool kit

 

 

 

 

 

Manual Pages

 

N.A

 

 

 

Xprint R/3 Kit

 

 

 

 

 

SNMP Agent

 

 

 

 

 

Domain Monitoring GUI Anchor

 

X

 

 

 

Domain Monitoring GUI Relay

 

S

 

 

 

Domain Monitoring GUI Server

 

S

 

 

 

EKS/Patch XPW80B102

 

S

 

 

 

If you select the standard installation you will get the components marked with X in the table above.

If you want to install other parts of Xprint you must choose a "user" defined installation. Then you can install the R/3 Kit (Server, Client), SNMP agent, XPG3 emulation and the development kit.

The parts which are marked with S have their own installation procedures. You have to install these parts separately. This is mentioned later in this document.

3.4.3 Migration aspects when upgrading from former Xprint versions

When an installation of the version 8.0 is foreseen, two cases may occur:

all the systems are migrated at once (for example, there is only one Xprint installation in stand-alone).

some systems are updated to the new version while other ones still run a former Xprint version.

In any case, the first step is to be sure that a valid license key for Xprint 8.0 is available.

From Xprint 5.2 or 6.0

At once:

For the migration from Xprint 6.0 or 5.2 to the new version "at once", there is some specific actions to perform before installing the new version:

On Windows (XPRINT-NT), Xprint 5.2A and Nutcracker must be removed before installing Xprint 8.0. Be careful that in this case all jobs and the configuration database must be saved manually or will be lost after the remove of the packages.

Execute the following steps :

o Backup the V5.2 database directories (DB,SP,GW) in the Xprint's root folder (default: "C:\Program Files \Xprint") if you wish to migrate your existing V5.2 database

o Backup DB.local, SV, TMP in the Xprint's root folder if you wish to migrate your existing jobs

o Backup your resources and PCL directories in the Xprint's root folder if you have specified custom PCLs and/ or custom resources

Image 10 Contents
Release Notice General Ordering DeliveryDocumentation New features ExplanationSoftware extensions, new functions Technical information Resource requirements SnmpRequired disk storage Hardware requirements / supportVirtual Memory consumption Software configuration Product installation/configurationHow must the Xprint Pot-Masters be rebooted Database backupHow to configure an Xprint domain GatewaysInstallation of additional components of Xprint Local Xprint administratorMaximum number of devices per supervisor / servers objects Migration aspects when upgrading from former Xprint versions Migration aspects when upgrading from former Xprint V7.0 to Domain Monitoring GUI Relay SnmpHost address GUISRVHOST=hostaddress Where Domain Monitoring GUI Server Keyword Working DomainMonitoringGUI INI/xpIni.ini Daemons Product use Xprint LicenseXprint License Update Test of the printer device address Renaming the hostname in an Xprint domainBsd filter port options Device selectionXpalert Clean up of directories at the start upLogging Gateway optionsRequesting the job states with the APIs Standard entriesNotification event ContextWhich PCL is recommended according to a printer Options orderCooperation with Wprint Interoperability with LdapObsolete functions Incompatibilities Configuration 3.5.21.1.1 Configuration fileExample of a job submission using the Ldap interoperability Activating the callback libraryDatabase Maintenance scopeRestrictions Xprint fax and mail support Jobs sent to a remote domainMercator Domain Monitoring GUI DMG Server installationWprint FirewallProcedure in the event of errors Using the options -fc and -rw with PCL PostscriptErrata for documents and manuals XPFORCESILENTPRINTING=1 XPFORCEPRINTING=1