convertScriptCompatibility command

convertScriptCompatibility command

The convertScriptCompatibility command is used by administrators to convert their configurations from a mode that supports backward compatibility of WAS V5.x or 6.0.x administration scripts to a mode that is fully in the V6.1.x configuration model. The scope of the configuration changes depend on the type of profile that is being processed.

For standalone configurations, the default is to convert all servers owned by the node in that configuration.
Use the -serverName parameter for more granular control.

For ND configurations, the default behavior is to convert all nodes and all servers owned by those nodes.
Use the -nodeName and -serverName parameters for more granular control.

Nodes are checked to verify that they are at a WebSphere Application Server V6.1.x level before they are processed in order to support mixed-node configurations. Client environments are not processed. The following conversions take place with this tool:

processDef to processDefs
WCCM objects of type processDef from WAS V5.x are converted to use processDefs as defined in the V6.1.x 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 V5.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 V6.1.x 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 V5.x or 6.0.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.

ObjectRequestBroker from not using the server thread pool to using it
For example, <ObjectRequestBroker useServerThreadPool="false"...> is changed to <ObjectRequestBroker useServerThreadPool="true">.

Syntax

The syntax is as follows:
convertScriptCompatibility.sh  -help
 convertScriptCompatibility.sh  [-profileName profile_name]
                     [-backupConfig true | false]
                     [-nodeName node_name [-serverName server_name]]
                     [-traceString trace_spec [-traceFile file_name]]
convertScriptCompatibility.bat  -help
 convertScriptCompatibility.bat  [-profileName profile_name]
                     [-backupConfig true | false]
                     [-nodeName node_name [-serverName server_name]]
                     [-traceString trace_spec [-traceFile file_name]]
Parameters

Supported arguments include the following parameters:

-help

This displays help for this command

-backupConfig

This is an optional parameter that is used to back up the existing configuration of the current profile. The default is true—that is, to use the backupConfig command to save a copy of the current configuration into the profile_name/temp directory.
Use the restoreConfig command to restore that configuration as required.
See restoreConfig command.

-profileName

This is an optional parameter that is used to specify the profile configuration in the V6.1.x 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

This is an optional parameter that is used to specify a particular node name be processed rather than every node in the configuration. If this is not specified, all nodes in the configuration are converted.

-serverName

This is an optional parameter that is used to specify a particular 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 ND configurations. If this parameter is not specified, all servers 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

This is an optional parameter. The value trace_spec specifies the 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 the -traceFile parameter.

-traceFile

This is an optional parameter. The value file_name specifies the name of the output file for trace information. If you specify the -traceString parameter but do not specify the -traceFile parameter, the command does not generate a trace file.

Usage
Standalone appserver profile
Example scenario
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).
Follow these steps to convert all servers under this standalone profile:
Open a command window.

Change to the V6.1.x profile's profile_root/bin directory.
Run the following command:
./convertScriptCompatibility.sh 
convertScriptCompatibility.bat 
Deployment manager with managed nodes
Example scenario 1
Run the WASPostUpgrade command against the deployment manager as well as all of its managed nodes and specify -scriptCompatibility=true or do not specify a value for the -scriptCompatibility parameter (which has a default value of true).
Follow these steps to convert all nodes and servers in this cell.
The following steps should be taken against the deployment manager profile. If you run the convertScriptCompatibility command against a managed profile, the changes will be removed the next time the deployment manager synchronizes with the managed node.
Open a command window.

Change to the V6.1.x deployment manager profile's profile_root/bin directory.
Run the following command:
./convertScriptCompatibility.sh 
convertScriptCompatibility.bat 
Synchronize the deployment manager's configuration with each managed node to produce a consistent configuration.
Example scenario 2
Run the WASPostUpgrade command against the deployment manager and specify -scriptCompatibility=false.

Run the WASPostUpgrade command against the deployment manager's managed nodes and specify -scriptCompatibility=true or do not specify a value for the -scriptCompatibility parameter (which has a default value of true).
Follow these steps to convert all non-converted nodes and servers in the cell.
The following steps should be taken against the deployment manager profile. If you run the convertScriptCompatibility command against a managed profile, the changes will be removed the next time the deployment manager synchronizes with the managed node.
Open a command window.

Change to the V6.1.x deployment manager profile's profile_root/bin directory.
For each managed node that has not been converted, run the following command:
./convertScriptCompatibility.sh –nodeName ${non_converted_nodename}
convertScriptCompatibility.bat –nodeName ${non_converted_nodename}
Synchronize the deployment manager's configuration with each managed node to produce a consistent configuration.
For more information about where to run this command, see Use command line tools.

Related tasks

Migrating product configurations
Use the migration tools to migrate product configurations

Related Reference

clientUpgrade command
WASPreUpgrade command
WASPostUpgrade command

Reference topic