The convertScriptCompatibility command
is used by administrators to convert their configurations from a mode
that supports backward compatibility of WebSphere® Application Server Version 5.1.x
or Version 6.0.x administration scripts to a mode that is fully in
the Version 7.0 configuration
model.
The scope of the configuration changes depend on the type
of profile that is being processed.
Nodes are checked to verify that they are at a
WebSphere Application Server Version 7.0 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 WebSphere Application Server Version 5.1.x
are converted to use processDefs as defined in the Version 7.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 WebSphere Application Server Version
5.1.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
WebSphere Application Server Version 7.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 WebSphere Application Server Version
5.1.x or Version 6.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">.
Location
The
convertScriptCompatibility command
is located in the following directory.
Syntax
The syntax is as follows:
convertScriptCompatibility [-help]
convertScriptCompatibility [-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.
Read the "restoreConfig command" article in the
information center for more information.
- -profileName
- This is an optional parameter that is used to specify the profile
configuration in the Version 7.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
- 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 WebSphere Application Server, Network Deployment 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 that you want 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, you must 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 application server 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:
- Start a Qshell session.
STRQSH
- Change to the Version 7.0 app_server_root/bin directory.
- Run the following command:
convertScriptCompatibility -profileName profile_name
- manager with federated nodes
-
Example scenario 1
- Run the WASPostUpgrade command
against the deployment manager 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).
- Follow these steps to convert all nodes and servers in this cell.
Important: The following steps should be taken against the
deployment-manager management profile. If you run the convertScriptCompatibility command
against a federated profile, the changes will be removed the next
time the deployment manager synchronizes with the federated node.
- Start a Qshell session.
STRQSH
- Change to the Version 7.0 app_server_root/bin directory.
- Run the following command:
convertScriptCompatibility -profileName dmgr_profile_name
- Perform a full resynchronization of the deployment manager's configuration
with each federated 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 federated 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.
Important: The following steps should be
taken against the deployment-manager management profile. If you run
the convertScriptCompatibility command against
a federated profile, the changes will be removed the next time the
deployment manager synchronizes with the federated node.
- Start a Qshell session.
STRQSH
- Change to the Version 7.0 app_server_root/bin directory.
- For each federated node that has not been converted, run the following
command:
convertScriptCompatibility -profileName dmgr_profile_name –nodeName ${non_converted_nodename}
- Perform a full resynchronization of the deployment manager's configuration
with each federated node to produce a consistent configuration.
For more information about where to run this command,
read the "Using command line tools" article in the information center.