WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIXHP-UXLinuxSolarisWindows

Configuring WebSphere Application Server after migration

Before you begin

Installation automatically configures IBM WebSphere Application Server, Version 6 and all other bundled products. There is no need for additional configuration if you did not migrate from an earlier version.

Why and when to perform this task

If you migrate an installation of WebSphere Application Server, Version 4.0.x, there are some items to review before considering your environment fully configured.

Steps for this task

  1. Examine any Lightweight Third Party Authentication (LTPA) security settings you might have used, and apply the settings in the WebSphere Application Server security settings.

    Global security that uses Lightweight Third Party Authentication (LTPA) authentication in Version 4.0.x is migrated to the base WebSphere Application Server product and to the Network Deployment product. However, although global security was enabled in Version 4.0.x, it is disabled during migration to Version 6.

    If you add this node later to an IBM WebSphere Application Server Network Deployment, Version 6 configuration, you can enable and use the LTPA configuration. Use the administrative console to generate keys for the migrated LTPA authentication mechanism. After generating the keys, you can enable global security.

    Global security that uses localos authentication mechanisms in Version 4.0.x is migrated to the Network Deployment product. However, although global security was enabled in Version 4.0.x, it is disabled during migration to Version 6. The Network Deployment product does not support the SWAM authentication mechanism. Migration sets the authentication mechanism in Version 6 to LTPA. Use the administrative console to generate keys for the migrated LTPA authentication mechanism. After generating the keys, you can enable global security.

  2. Check the WASPostUpgrade.log file in the logs directory, for details about JSP 0.91 objects that the migration tools do not migrate.

    Version 6 does not support JSP 0.91 objects. The migration tools do not migrate JSP objects configured to run as JSP 0.91 objects. The migration tools do, however, recognize the objects in the output and log them. Version 6 runs JSP 1.0 and 1.1 objects as JSP 1.2 objects, which is its only supported level.

  3. Be aware that Version 4.0.x Server Groups are converted to Version 6 clusters.

    Version 4.0.x server groups have been dramatically redefined in Version 6 as clusters and cluster members. Application servers are the only objects supported as models and cluster members in Version 6.

  4. Identify and use the migration tools to migrate non-migrated nodes in Version 4.0.x repositories that have multiple nodes.

    A Version 4.0.x repository can contain more than one node name and its associated children. The WASPostUpgrade tool processes only those objects and children that match the migrating node. This determination is made by checking the names of nodes in configuration files with fully qualified and non-qualified network names of the migrating machine.

  5. Update J2EE resources in client JAR files to the new resource format with the ClientUpgrade tool.

    J2EE applications might exist on the client, if the client has client JAR files with J2EE resources.

  6. To migrate a Version 4.0.x or V5.x XML application to the Version 6 level, you must recompile it.
  7. Configure WebSphere Application Server to use a database. For example, you can configure WebSphere Application Server to use DB2.
  8. Review your Java virtual machine settings to verify that you are using a heap size of at least 50 for improved startup performance.

    If you have used a smaller heap size in the past, you can use the default heap size, which is now 50.

Result

Now you are finished with pre-test configuration. You might have to fine tune your WebSphere Application Server environment as you test it. Test all redeployed applications before moving them into production.

What to do next

Return to Installing WebSphere Application Server to continue.



Sub-topics
Important information about XML4J
Configuring WAS for DB2

Related concepts
Configuration mapping during migration

Related tasks
Migrating welcome page

Task topic    

Terms of Use | Feedback

Last updated: Mar 17, 2005 4:28:29 AM CST
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tins_config2.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)