InfoCenter Home >
3: Migration overview >
3.2: Migrating from previous product versions >
3.2.3: Migrating from Version 4.0 Advanced Single Server Edition

3.2.3: Migrating from Version 4.0 Advanced Single Server Edition

A summary of the migration process follows. Most of this is done for you by the product installation program.

  1. Install the Version 4.0 Advanced Edition product.
  2. If automated migration is not chosen in the previous step, manually migrate the single-server configuration to the new installation.
  3. Restore user data files in the new installation.
  4. Uninstall the single-server product.

The rest of this article primarily addresses step 2.

Important: If your current installation uses a configuration file other than server-cfg.xml, you must manually migrate the configuration as described in the next section.

Migrating administrative configurations manually

A tool for migrating Version 4.0 Advanced Single Server Edition administrative configurations is provided. There are two ways to migrate these configurations:

  • Use the automated migration that is part of product installation. For details, see the related information.
  • Manually complete the same steps as the automated migration support would. This might be necessary for nonstandard installations. Information to support this task follows.
The manual migration process

This process uses the SEMigrator.bat file (SEMigrator.sh on UNIX platforms). This file can be found in the bin directory of the Advanced Edition installation.

If the single-server installation uses Default Server for its applications, the default configuration must be installed in the Advanced Edition installation. The SEMigrator tool does not migrate default configurations, and the absence of Default Server in the Advanced Edition configuration might cause migration to fail.

Do not uninstall the single-server installation: Preserve it as it is until migration is finished.

  1. Run the SEMigrator tool from the bin directory of the Advanced Edition installation. As discussed in the following section, either the tool creates an output XML file for use in the following step, or the tool completes a one-step migration that is comparable to a full automated migration.
  2. If the previous step creates an output XML file (for example, output.xml), run the XMLConfig tool to import the configuration, as follows:
    XMLConfig -import output.xml -adminNodeName admin_node_name
  3. Copy the relevant application EAR directories from the installedApps directory of the single-server installation to the Advanced Edition installedApps directory. Be sure not to copy EAR directories for the sample applications; overwriting the Advanced Edition sample application configuration will probably result in erratic behavior.

This completes the configuration migration process. You might see certain errors or warnings at the command window if the SEMigrator tool tries to re-create configuration objects that already exist in the Advanced Edition installation (for example, JDBC providers or enterprise applications).

The SEMigrator tool does not migrate sample applications from the single-server installation. If installation of sample applications and the default configuration is required, please choose the appropriate options during Advanced Edition installation.

SEMigrator parameters

In the following section, AEs refers to Advanced Single Server Edition. AE refers to Advanced Edition.

SEMigrator
-xmiFile xml_data_file
-adminNodeName primary_node_name
[ -srcNodeName  AEs_node_name ]
[ -destNodeName AE_node_name ]
[ -outputFile output_XML_file_name ]
[ -nameServiceHost host_name [ -nameServicePort port_number ]]
[-traceString trace_spec [-traceFile file_name]]

A summary of these parameters follows:

  • -xmiFile xml_data_file - Fully qualified path name for the Advanced Single Server Edition configuration XML file, typically config\server-cfg.xml.
  • -adminNodeName primary_node_name - The name of the node on which the Advanced Edition administrative server is installed. The administrative server must be running if the outputFile parameter is not specified.
  • [ -srcNodeName AEs_node_name ] - The source node name for migration, that is, the name of a node in xml_data_file. This defaults to the first node in xml_data_file.
  • [ -destNodeName AE_node_name ] - The destination node name for the migration. This defaults to primary_node_name.
  • [ -outputFile output_XML_file_name ] - The use of this option makes migration a two-step process.

    If this parameter is specified, the SEMigrator tool creates an XML file with the specified name, which can then be imported by using XMLConfig to finish the migration. For more information on XMLConfig, see the related information.

    The absence of this parameter makes this process equivalent to an automated migration; it requires a running administrative server on the primary node.

  • [ -nameServiceHost host_name [ -nameServicePort port_number ]] - The host and port address for the naming server. This pair must be specified if one-step migration is being attempted and the administrative server is running on a remote node. Unless changed previously by administrative actions, typical settings for these parameters are the host name of the administrative server and 900, respectively.
  • [-traceString trace_spec [-traceFile file_name]] - The trace specification for this tool.
Go to previous article: Mapping configurations to Version 4.0 Go to next article: Migrating Web server plug-ins

 

 
Go to previous article: Mapping configurations to Version 4.0 Go to next article: Migrating Web server plug-ins