This Utility can be used for migrating from a lower version of HOD to a higher version. Host On-Demand migration is a two-step process:
HOD source and target server can be on the same machine or a different machine.
Note: If HOD Source and target server are on different machines then Migrationpackage.zip file created in the export operation must be placed in the target machine (This is a manual process that the administrator has to take care of)
Host On-Demand migrating versions
Host On-Demand migration supported environments
Note: Export and Import operations are supported only on the same platform (e.g Windows to Windows, Linux to Linux etc.)
HODMigrationUtility.zip will be available on Fix central. Admin must download the zip file and place it in the Host On-Demand publish directory. There is no other installation that is needed.
e.g cd C:\Program Files (x86)\IBM\HostOnDemand13\HOD13\HODMigrationUtility
Export operation: java –jar HODMigrationUtility.jar c:\Test\Export.xml
Note: Once the export operation is completed, a completion message will be displayed along with the location where migration package zip file is created
Import operation: java –jar HODMigrationUtility.jar c:\Test\Import.xml
Note: Once the import operation is completed, a successful message will be displayed.
Rollback operation: java –jar HODMigrationUtility.jar c:\Test\Rollback.xml
Note: Rollback xml file gets generated automatically after an import operation is performed. Rollback can be performed only once
Export:
Input attribute | Explanation |
---|---|
migrationInput | This is the root directory for the input xml file. |
mode | This tag specifies the mode of operation. Input is mandatory for this tag. Input for this tag should be “export” (upper or lower case does not matter). |
HODPublishDirectory | Specifies Host On-Demand publish directory Input is mandatory for this tag e.g.
|
sourceMigratingPackage | Specifies location to save Migration package
zip
If not specified, the current location is used to save
the Migration package zip. e.g.
|
overWrite | Input is mandatory for this tag.
Input “yes”
(default): If the migration package already exists, utility will overwrite
the existing package. Following message will be displayed.
Input “no”:
If the migration package already exists, utility will not create the
migration package. Instead, the following message will be displayed.
|
customFiles | customFiles is the parent tag for fileLocation
sub tags.
If there are custom files (.kmp .bar .col .pmp,.mac)
files saved in locations other than default location (user/HODObjs)
those locations need to be provided in this tag so that files in those
locations are also picked for migration.
Each custom file location
needs to be provided in the fileLocation tag. e.g.
Refer to the table below for a list
of files that will be exported into the migration package |
Files | Location | Files directly copied to target machine | Files modified by migration utility |
---|---|---|---|
Deployment wizard files | |||
DW created html, z_*.html, _J2.html, .jnlp | HOD publish directory | No | All |
Complete HOD Data folder .cf files wInfo.txt Policy.obj Preload.obj Params.txt udparams.txt |
HOD publish directory HODData | Following files will be copied directly to target
HOD server Policy.obj Preload.obj Params.txt |
wInfo.txt .cf file udparams.txt |
Custom files | |||
Default Custom files | User directory HODObjs folder e.g.: C:\Users\<SystemUser>\HODObjs | Yes | None |
User defined custom files | User defined location (Shared or network location) | Yes (customfiles folder will be created and all custom files will be copied) | None |
Private Directory files | |||
Private Files (All files and folders) | HOD Install directory private | Yes | None |
Directory Utility | |||
Sample.xml and user created .xml | HOD Install directory lib\samples\DirUtil | Yes | None |
Security | |||
HODSerKeyDb.kdb HODServerKeyDb.sth HODServerKeyDb.rdb | bin directory | Yes | None |
WellKnownTrustedCAs.class WellKnownTrustedCAs.jks WellKnownTrustedCAs.p12 | HOD publish directory | If a file with the same name already exists, it will not be copied to target HOD server | Conversion of .p12 to jks file |
pdfpdt files | |||
Printer Definition File: All the files | HOD publish directory/ pdfpdt | Yes | None |
Property file | |||
Config.properties | HOD publish directory | Yes | None |
Input attribute | Explanation |
---|---|
migrationInput | This is the root directory for the input xml file. |
mode | This tag specifies the mode of operation. Input is mandatory for this tag. Input for this tag should be “import” (upper or lower case does not matter). |
HODPublishDirectory | Specifies Host On-Demand publish directory Input is mandatory for this tag e.g.
|
migratingPackageLocation | Specifies location to save Migration package
zip
If not specified, the current location is used to save
the Migration package zip. e.g.
|
systemJavaBinDirectory | Specifies z/OS and AS/400 system java bin folder
This
tag input required only for z/OS and AS/400 OS e.g.
|
options | options tag is the parent tag to provide input
for following child tags. Terminal, FileTransfer, Icon, FTPTerminal, dbaOptions, targetUI These tags need to be provided in the following format:
Above mentioned tags are related to session parameter Security related parameters can also be specified to convert SSL3 to JSSE TLS1.2. This needs to be set under Terminal tag Input for these tags is key and value in double quotes
Key should not be null, value can be null These key value pairs will be written to the cf file on the target system of the corresponding sessions To provide more than one session parameter, tag has to be repeated with different key and value pair. e.g.
|
targetUI | HTML file look and feel of HOD 11 and HOD12
/HOD13 is different. HOD12 and HOD13 has the “Nimbus” look and feel for HTML files. Input “yes” (default): All the migrating HTML files will get the Nimbus look and feel in their UI. Input “no”: To retain the source UI look and feel for HTML files. |
codebase | Input is mandatory for this tag.
This
codebase is required for webstart client pages. The URL that you specify
here must identify the target Host On-Demand publish directory. e.g.
where server_name.mycompany.com is the name of the server on which Host On-Demand is installed, and hodalias is the Host On-Demand publish alias. |
targetBackup | Input is mandatory for this tag. Input “yes” (default): Backup file will be created for the target Host On-Demand server files. The target Host On-Demand server where import will be run, files are backed up before running the Import – refer to the table below for a list of files that will be backed up Input “no”: Backup file will not be created for migrating Host On-Demand server files. |
overwriteHODPublishDirectory | Input is mandatory for this tag. Input “yes” (default): Files with same name (source and target files) will be overwritten in the target HOD server in publish directory Input “no”: Files with same name (source and target files) will not be overwritten in publish directory, only new files or directories will be migrated to target |
overwritePrivate | Input is mandatory for this tag. Input “yes” (default): Files with same name (source and target files) will be overwritten in the target HOD server in private directory Input “no”: Files with same name (source and target files) will not be overwritten in private directory, only new files or directories will be migrated to target |
overwritePdfPdt | Input is mandatory for this tag. Input “yes” (default): Files with same name (source and target files) will be overwritten in the target HOD server in pdfpdt directory Input “no”: Files with same name (source and target files) will not be overwritten in pdfpdt directory, only new files or directories will be migrated to target |
overwriteDirUtil | Input is mandatory for this tag. Input “yes” (default): Files with same name (source and target files) will be overwritten in the target HOD server in DirUtil directory Input “no”: Files with same name (source and target files) will not be overwritten in DirUtil directory, only new files or directories will be migrated to target |
Folder | Files |
---|---|
Private Directory | All the files and directories |
Bin directory | HODServerKeyDb.kdb , HODServerKeyDb.sth, HODServerKeyDb.rdb, HODServerKeyStore.jks |
HOD publish directory->pdfpdt | Printer Definition File |
HOD publish directory | WellKnownTrustedCAs.class WellKnownTrustedCAs.jks WellKnownTrustedCAs.p12 CustomizedCAs.p12 CustomizedCAs.jks CustomizedCAs.sth Config.properties Deployment Wizard Files |
lib folder | redir.properties |
lib\samples\DirUtil | All the files |
HostOnDemand\HOD\HODData | All folders and files |
Files from a source HOD server were already migrated to target. C:\lib\.importSuccess. HOD Migration process Terminated.
Rollback File created in current directory to perform rollback. C:\Test\Rollback.xml