WAS v8.0 > Migration and coexistence > Distributed operating systems > Migrate product configurations > Migrate product configurations with migration tools

convertScriptCompatibility command

The convertScriptCompatibility command converts configurations from a mode that supports backward compatibility of WAS v6.x or v7.0.x administration scripts to a mode that is fully in the v8.0 configuration model.

• For stand-alone configurations, the default is to convert all appservers owned by the node in that configuration.

  Use the -serverName parameter for more granular control.

• For WAS ND configurations, the default behavior is to convert all nodes and all appservers owned by those nodes.

  Use the -nodeName and -serverName parameters for more granular control.

Nodes are checked to verify that they are at a WAS v8.0 level before they are processed in order to support mixed-node configurations. Client environments are not processed.

Conversions that take place...

processDef to processDefs	WCCM objects of type processDef from WAS v6.x are converted to use processDefs as defined in the v8.0 server.xml model. The existing processDef object remains in the configuration and is ignored by the runtime.
transports to channels	Existing transport entries in the configuration from WAS v6.x are mapped to channel support. This affects server.xml and serverindex.xml files. The values of the transport settings are used to create new channel entries.
SSL configuration	WAS v8.0 contains enhancements to SSL configuration that result in refactoring the existing SSL configuration model. Both the old and the new model are supported. The default is to map to the WAS v6.x or v7.x SSL configuration model.
bootstrapAddress to bootstrapAddresses	Each single bootstrap address configuration is converted to a new bootstrap address list configuration containing that single bootstrap address.
Not using server thread pool to using it	For example... <ObjectRequestBroker useServerThreadPool="false"...> ...is changed to... <ObjectRequestBroker useServerThreadPool="true">

Syntax...

cd PROFILE_ROOT/bin
convertScriptCompatibility.sh  -help

convertScriptCompatibility.sh  [-profileName profile_name]
                     [-backupConfig true | false]
                     [-nodeName node_name [-serverName server_name 
 ]
                     [-traceString trace_spec [-traceFile file_name]]

Parameters:

-help	Display help for this command
-backupConfig	Back up the existing configuration of the current profile. Default is true, that is, to use the backupConfig command to save a copy of the current configuration into... profile_name/temp Use the restoreConfig command to restore that configuration as required.
-profileName	Profile configuration in the v8.0 environment. If this is not specified, the default profile is used. If the default profile has not been set or cannot be found, the system returns an error.
-nodeName	Node name be processed rather than every node in the configuration. If this is not specified, all nodes in the configuration are converted.
-serverName	Server name to be processed rather than every server in the configuration. It can be used on all profile types and can be used in conjunction with the -nodeName parameter when processing WAS ND configurations. If this parameter is not specified, all appservers in the configuration are converted. If it is used in conjunction with the -nodeName parameter, all processing is limited to the specified node name.
-traceString	Trace information to collect. To gather all trace information, specify... "*=all=enabled" ...(with quotation marks). The default is to not gather trace information. If you specify this parameter, also specify -traceFile.
-traceFile	Output file for trace information. If you specify -traceString but do not specify -traceFile, the command does not generate a trace file.

Usage - Stand-alone application server profile

1. Run the WASPostUpgrade command and specify -scriptCompatibility=true or do not specify a value for the -scriptCompatibility parameter (which has a default value of true).

2. Convert all appservers under this stand-alone profile...
   cd V8_PROFILE_ROOT/bin
   ./convertScriptCompatibility.sh

Usage - Deployment manager with federated nodes

Scenario 1

1. Run the WASPostUpgrade command against the dmgr as well as all of its federated nodes and specify -scriptCompatibility=true or do not specify a value for the -scriptCompatibility parameter (which has a default value of true).

2. Follow these steps to convert all nodes and appservers in this cell.

   The following steps should be taken against the dmgr profile. If you run the convertScriptCompatibility command against a federated profile, the changes will be removed the next time the dmgr synchronizes with the federated node.

   1. Run...
      cd V8.0_dmgr_PROFILE_ROOT/bin
      ./convertScriptCompatibility.sh

   2. Perform a full resynchronization of the dmgr's configuration with each federated node to produce a consistent configuration.

Scenario 2

1. Run the WASPostUpgrade command against the dmgr and specify -scriptCompatibility=false.

2. Run the WASPostUpgrade command against the dmgr's federated nodes and specify -scriptCompatibility=true or do not specify a value for the -scriptCompatibility parameter (which has a default value of true).

3. For each federated node that has not been converted, run...
   cd v8.0_dmgr_PROFILE_ROOT/bin
   ./convertScriptCompatibility.sh –nodeName ${non_converted_nodename}

4. Perform a full resynchronization of the dmgr's configuration with each federated node to produce a consistent configuration.

Migrate product configurations
Migrate product configurations with migration tools
WASPreUpgrade command
WASPostUpgrade command

+

Search Tips   |   Advanced Search