WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Postmigration tasks for WebSphere ESB

After migration, you should check some configuration settings. You might need to change them, or further configure the version 6.2 server.

Before you begin

If you migrated from version version 6.0.2 to version 6.2.x, you need to create the common database that hosts the Recovery and Relationship service tables. See Creating the common database and configuring the recovery subsystem for information on running commonDBMigrate602.bat and for information on configuring clusters and servers to manage failed events.

You should have migrated your server or cluster and verified that the migration was successful.

About this task

Perform the following checks, if applicable to your environment:
  • Examine any Lightweight Third Party Authentication (LTPA) security settings that you might have used in version 6.0.x or 6.1.x, and make sure that version 6.2 security is set appropriately.
  • Check the WBIPostUpgrade.profile_name.timestamp.log file in the logs directory for details about any JSP objects that the migration tools did not migrate.

    If version 6.2 does not support a level for which JSP objects are configured, the migration tools recognize the objects in the output and log them.

  • Review your Java™ virtual machine settings to verify that you are using the recommended heap sizes. See Java virtual machine settings. The information at this link applies to WebSphere® ESB servers as well as WebSphere Application Server servers.
  • Verify the results of the automatic Cloudscape database migration, and manually migrate any Cloudscape databases that are not automatically migrated by the tools. See Migrating Cloudscape databases for more information.
  • After migrating from version 6.1.x to version 6.2, you should check your WebSphere Adapter properties to ensure that they are properly configured for the new installation location. Some adapter properties may need to be altered during migration in a way that would be unknown to an automated migration.
  • After migrating to version 6.2, you need to check that your ports are mapped correctly to make sure that the Remote Artifact Loader can access the security port on the application cluster when the global security is turned on. To verify that your ports are configured correctly, use the following procedure.
    1. In the administrative console, navigate to Environment > Virtual Hosts.
    2. Select default_host > Host Aliases.
    3. Check if the application cluster security port is mapped to "*" which means "all hosts." If it is not, change it to "*" by clicking New, then entering "*" in the Host Name field and the port number of the application cluster in the Port field.
    4. Save your changes by clicking Apply or OK, and then select Save.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/tmig_vtv_post.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).