Configuration mapping during product-configuration migration

Various configurations are mapped during product-configuration migration.

Migration always involves migrating a single profile to another single profile on the same machine or a separate machine. Go to the information center for the WebSphere® Application Server, Network Deployment product to learn how the migration tools map models, clones, server groups, clusters, and Lightweight Third Party Authentication (LTPA) security settings.

Many migration scenarios are possible. The migration tools map objects and attributes existing in the version from which you are migrating to the corresponding objects and attributes in the Version 7.0 environment.

Bootstrap port

The migration tools carry the old release value into the Version 7.0 environment.

If a value for the -portBlock parameter is specified during the call to WASPostUpgrade, however, a new port value is given to each application server that is migrated to Version 7.0.

Command-line parameters

The migration tools convert appropriate command-line parameters to Java™ Virtual Machine (JVM) settings in the server process definition. Most settings are mapped directly. Some settings are not migrated because their roles in the WebSphere Application Server Version 7.0 configuration do not exist, have different meanings, or have different scopes.

For information on how to change the process-definition settings, read the "Process definition settings" article in the information center. For information on how to change the JVM settings, read the "Java virtual machine settings" article in the information center.

Generic server
In WebSphere Application Server Version 5.1.x, a generic server was an APPLICATION_SERVER fitted to manage external resources. In Version 6.x and later, it has its own type called GENERIC_SERVER. Migration will perform this conversion, but migration cannot accurately migrate the external resources that the generic server references. After migration has completed migrating the generic server settings, you might need to perform additional tasks. If the old resource that the generic server was managing is located under the old WebSphere Application Server installation, perform the following tasks:
  1. Copy any related files to the new installation.
  2. Run any setup required to put the external application back into a valid and working state.

    It is best that you reinstall the resource into the new WebSphere Application Server directory. Whatever you choose to do, the final step is to reset the reference to the new location of the application.

If the old resource that the generic server was managing is not installed under the old WebSphere Application Server installation, nothing further is required.

Policy files
WebSphere Application Server Version 7.0 migrates all the policy files that are installed with Version 5.1.x or Version 6.x by merging settings into the Version 7.0 policy files with the following characteristics:
  • Any comments located in the Version 7.0 policy files will be preserved. Any comments contained in the Version 5.1.x or Version 6.x policy files will not be included in the Version 7.0 file.
  • Migration will not attempt to merge permissions or grants; it is strictly an add-type migration. If the permission or grant is not located in the Version 7.0 file, the migration will bring it over.
  • Security is a critical component; thus, the migration makes any additions at the end of the original .policy files right after the comment MIGR0372I: Migrated grant permissions follow. This is done to help administrators verify any policy-file changes that the migration has made.
Properties and classes directories

Migration copies files from prior version directories into theWebSphere Application Server Version 7.0 configuration.

Property files
WebSphere Application ServerVersion 7.0 migrates all the property files that are installed with Version 5.1.x or Version 6.x by merging settings into the Version 7.0 property files with these exceptions for Version 5.1.x files:
  • j2c.properties (migrated into resources.xml files)
  • samples.properties
Resource adapter archives (RARs) referenced by J2C resources

RARs that are referenced by J2C resources are migrated if those RARs are in the old WebSphere Application Server installation. In this case, the RARs are copied over to the corresponding location in the new WebSphere Application Server installation. Relational Resource Adapter RARs will not be migrated.

Samples

No migration of samples from previous versions is available. There are equivalent WebSphere Application Server Version 7.0 samples that you can install.

Security

Java 2 security is enabled by default when you enable security in WebSphere Application Server Version 7.0. Java 2 security requires you to grant security permissions explicitly.

There are several techniques that you can use to define different levels of Java 2 security in Version 7.0. One is to create a was.policy file as part of the application to enable all security permissions. The migration tools call the wsadmin command to add an existing was.policy file in the Version 7.0 properties directory to enterprise applications as they are being migrated.

When migrating to WebSphere Application Server Version 7.0, your choice of whether or not to migrate to support script compatibility results in one of two different outcomes.
  • If you choose to migrate to support script compatibility, your security configuration is brought over to Version 7.0 without any changes.

    This is the default.

  • If you choose not to migrate to support script compatibility, the security configuration is converted to the default configuration for WebSphere Application Server Version 7.0. The default security configuration for Version 6.1 and later acts almost the same as in the previous versions, but there are some changes.

    For example, existing keyfiles and trustfiles are moved out of the SSLConfig repertoire and new keystore and truststore objects are created.

For more information on migrating your security configurations to Version 7.0, read the "Migrating, coexisting, and interoperating – Security considerations" article in the information center.

Stdin, stdout, stderr, passivation, and working directories

The location for these directories is typically the logs directory under the WebSphere Application Server profile directory. For WebSphere Application Server Version 7.0, the default location for the stdin, stdout, and stderr files is the logs directory located under the WebSphere Application Server profile directory—for example, the logs directory for the default profile is /QIBM/UserData/WebSphere/AppServer/V70/Base/profiles/default/logs.

The migration tools attempt to migrate existing passivation and working directories. Otherwise, appropriate Version 7.0 defaults are used.

In a coexistence scenario, using common directories between versions can create problems.

Transport ports

The migration tools migrate all ports. You must resolve any port conflicts before you can run servers at the same time.

Note: If ports are already defined in a configuration being migrated, the migration tools fix the port conflicts in the Version 7.0 configuration and log the changes for your verification.

If you specify the -portBlock parameter in the WASPostUpgrade command, a new value is assigned to each transport that is migrated.

If you specify true for the -replacePorts parameter in the WASPostUpgrade command, all port values from the old configuration are used in the new configuration. If you specify false for the -replacePorts parameter, the default port definitions in the new profile are not replaced with the values from the old configuration during migration. .

Choosing -scriptCompatibility="true" or -scriptCompatibility="false" results in two different outcomes for transport ports if you are migrating fromWebSphere Application Server Version 5.1.x:
  • -scriptCompatibility="true"

    This results in your transport ports being brought over as they are. This is the default.

  • -scriptCompatibility="false"

    This results in the transport ports being converted to the implementation of channels and chains. From an external application usage standpoint, they will still act the same; but they have been moved to the TransportChannelService.

For more information on the WASPostUpgrade command, read WASPostUpgrade command.

For further information on transport chains and channels, read the 'Transport chains' article in the information center.

You must manually add virtual host alias entries for each port. For more information, read the "Configuring virtual hosts" article in the information center.

Web modules

The specification level of the Java Platform, Enterprise Edition (Java EE) implemented in WebSphere Application Server Version 6.0.x required behavior changes in the Web container for setting the content type. If a default servlet writer does not set the content type, not only does the Web container no longer default to it but the Web container returns the call as "null." This situation might cause some browsers to display resulting Web container tags incorrectly. To prevent this problem from occurring, migration sets the autoResponseEncoding IBM® extension to "true" for Web modules as it migrates enterprise applications.

JVM system properties

If you migrate a Version 6.1 configuration that has feature packs installed, the migration tools might add one or two JVM system properties for each Java server in your configuration, including your administrative servers. Web servers are not affected. The properties are set to indicate to the JVM that the configuration should use a Java annotation scan policy other than the Version 7.0 default scan policy.

  • If you migrate a Version 6.1 profile that has the Feature Pack for EJB 3.0 installed, the migration tools add the following system property to the JVM definitions for all Java servers defined on that node:
    com.ibm.websphere.ejb.UseEJB61FEPScanPolicy = true
  • If you migrate a Version 6.1 profile that has the Feature Pack for Web Services installed, the migration tools add the following system property to the JVM definitions for all Java servers defined on that node:
    com.ibm.websphere.webservices.UseWSFEP61ScanPolicy = true
  • If you migrate a Version 6.1 profile that has both the Feature Pack for EJB 3.0 and the Feature Pack for Web Services installed, the migration tools add both of the system properties to the JVM definitions for all Java servers defined on that node:
    com.ibm.websphere.ejb.UseEJB61FEPScanPolicy = true
    com.ibm.websphere.webservices.UseWSFEP61ScanPolicy = true
If these properties are set, the following two changes take place in the default Version 7.0 behavior:
  • Application installation generates classes based on the annotation scan policy associated with the settings for those two properties.
    This means that you can potentially use the following four annotation scan policies:
    • Version 7 default behavior
    • Feature Pack for EJB 3.0 behavior
    • Feature Pack for Web Services behavior
    • Net behavior from having both the Feature Pack for EJB 3.0 and the Feature Pack for Web Services installed
  • The servers use the generated annotation classes based on the properties set, resulting in four potential behaviors.

You can change the scan policy behavior by adding or removing the custom JVM system properties from your server.xml files. After changing the properties, you must reinstall or update your applications and then resynchronize the cell to implement the change.




Related tasks
Migrating and coexisting application servers
Migrating product configurations
Concept topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 12:50:00 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-express-iseries&topic=cmig_configmap
File name: cmig_configmap.html