B.0 XML Elements and Attributes for ArkUpgrade
This section defines the XML elements and attributes that you use to configure the upgrade of your Novell® Archive and Version Services 2.0 for NetWare® server. ArkUpgrade converts your existing archive databases from ArkManager 1.0 format to ArkManager 2.0 format, which uses ArkSQL to organize and host the archive database. The XML elements have a particular hierarchy that you must keep in mind as you create your arkUpgrade.xml file for the upgrade process. See Figure B-1 to understand the parent-child relationships between XML elements defined for the sys:\arkManager\arkUpgrade.xml file.
Figure B-1 Hierarchical Parent-Child Relationships between XML Elements Used in the arkUpgrade.xml File
To configure the arkUpgrade.xml file, see Section 8.5.3, Converting the ArkManager 1.0 Database with ArkUpgrade.
The following table defines the XML elements and attributes that you use in the sys:\arkManager\arkUpgrade.xml file. Some elements appear first as children of elements in the next-higher level of the hierarchy and as parents to their own set of child elements in the next-lower level of the hierarchy.
The examples provided for the elements are sample code to illustrate how the configured properties appear in the XML file. You must modify the values to meet your specific needs as you create your arkUpgrade.xml file. For a sample of this configuration file, see Section C.2, Sample of the Upgrade Configuration for ArkUpgrade.xml.
Table B-1 Elements for the arkUpgrade.xml File
|
Parent Element |
Child Elements and Attributes |
Description |
|---|---|---|
<arkUpgrade> (Root element) |
<test/> |
(Conditional) Include this tag to test the upgrade process without actually altering the data files. If the <test/> tag is presented, ArkUpgrade analyzes the data and logs all possible errors; no actual conversion occurs. If this tag is not presented, arkUpgrade performs the actual conversion. View the conversion messages in the convert.log file and the error messages in the error.log file to determine if the upgrade ran properly. The logs are in the directory you specified as the path to the archive database, such as ark:\archive. For example,
ark:\archive\convert.log
ark:\archive\error.log
Replace ark:\archive with your archive path. Open the log files in a text-based word processor. |
<displayLog/> |
(Optional) If used, prints log entries for all jobs to the server’s console screen in addition to their normal display in the convert.log or error.log files. This is an empty element. It has no child elements and defines no data values. Either the shortened version or the long version of this element is valid. For example, use either of the following forms: <displayLog/> <displayLog></displayLog> |
|
<archivePath> |
Specifies the local path to the storage location in the archive server where the archive database of file versions is stored.
<archivePath>
volume_name:\directory
</archivePath>
If you are setting up an active-passive clustered solution for the archive server using Novell Cluster Services™, make sure to enter the path to the virtual storage location. |
|
<arkUpgrade> (cont’d) |
Child elements define the ArkSQL database user, password, and port number. The ArkSQL user needs server-specific ArkSQL rights. For information about its child elements, see <authentication> in the Parent Element column of this table. |
|
<job> |
A Job tag set surrounds the child elements that define the job name, source server name, and source volume name for an existing ArkManager 1.0 job. Create one upgrade job for each versioning job that you need to upgrade to the ArkSQL format for ArkManager 2.0. For information about its child elements, see <job> in the Parent Element column of this table. |
|
<authentication> (Child to <arkUpgrade>) |
<database> |
Contains child elements with information about the archive server’s ArkSQL database. This user must have server-specific rights to the ArkSQL server. For information about its child elements, see <database> in the Parent Element column of this table. |
<database> (Child to <authentication>) |
<user> |
The username of the ArkSQL database administrator. For example:
<user>root</user>
|
<password> |
The password of the ArkSQL database administrator. For example:
<password>arksql_password</password>
|
|
<portNumber> |
The port number used for ArkSQL database communications. For example:
<portNumber>3306</portNumber>
|
|
<job> (Child to <arkUpgrade>) |
<name> |
Specifies the unique name of the versioning job that you want to upgrade. This name can contain spaces. |
<server> |
Specifies the unique name of the server in the specified context where the original data is stored. For example, to specify a server named srv1:
<server>srv1</server>
|
|
<volume> |
Specifies the unique name of the volume in the specified server where the original data is stored. For example, to specify user1 as the name of the source volume:
<volume>user1</volume>
IMPORTANT:Do not place a colon after the source volume name. |