test

Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Upgrade and Migration Guide

Correcting Potential PE and EE Upgrade Problems

This section addresses the following issues that could occur during an upgrade to Application Server 8.1:

ProcedureTo Migrate Additional HTTP Listeners Defined on the Source Server to the Target PE Server

If additional HTTP listeners have been defined in the PE source server, those listeners need to be added to the PE target server after the upgrade:

  1. Start the Admin Console.

  2. Expand Configuration.

  3. Expand HTTP Service.

  4. Expand Virtual Servers.

  5. Select <server>.

  6. In the right hand pane, add the additional HTTP listener name to the HTTP Listeners field.

  7. Click Save when done.

ProcedureTo Migrate Additional HTTP and IIOP Listeners Defined on the Source Server to the Target EE Server

If additional HTTP listeners or IIOP listeners have been defined in the source server, the IIOP ports must be manually updated for the target EE servers before any clustered instances are started. For example, if MyHttpListener was defined as an additional HTTP listener in server1, which is part of the cluster, because server instances are symmetrical in a cluster, the other instances in the cluster will also have the same HTTP listener. In the target configuration named <cluster_name>-config, this listener must be added with its port set to a system property {myHttpListener_HTTP_LISTENER_PORT}. In the target server, each server instance in this cluster that uses this configuration would have system property named myHttpListener_HTTP_LISTENER_PORT. The value of this property for all server instances would be set to the port value in the source server, server1. These system properties for these server instances must be manually updated with non-conflicting port numbers before the server is started.

If additional HTTP listeners have been defined in the source server, those listeners need to be added to the target server after the upgrade:

  1. Start the Admin Console.

  2. Expand Configuration and select the appropriate <server>-config configuration.

  3. Expand HTTP Service.

  4. Expand Virtual Servers.

  5. Select <server>.

  6. In the right hand pane, add the additional HTTP listener name(s) to the HTTP Listeners field.

  7. Click Save when done.

Eliminating Port Conflict Problems

After upgrading the source server to AS 8.1 EE, start the domain. Start the node agent that, by default, starts the server instances. Start the Admin Console and verify that these servers are started. If any of the servers are not running, in the install_dir/nodeagents/node-agent-name/server_name/logs/server.log file, check for failures that are caused by port conflicts. If there any failures due to port conflicts, use the Admin Console and modify the port numbers so there are no more conflicts, then stop and restart the node agent and servers.

If an AS 7.1 EE source server with no clusters is being upgraded to AS 8.1 EE (only standalone instances are being upgraded), and if server1 in the AS 7.1 source server has a server instance listening on any of the default port of Application Server 8.1, a conflict occurs. If these conditions exist, start the Admin Console after the upgrade and change the port for the server-config’s listener to a non conflicting port number. If an AS 7.x SE source server is being upgraded to AS 8.1 EE, the upgrade process should automatically update the port for the <server-config>.

Note –

The default ports in Application Server 8.1 EE are:

Eliminating Problems Encountered When A Single Domain has Multiple Certificate Database Passwords

If the upgrade includes certificates, provide the passwords for the source PKCS12 file and the target JKS keyfile for each domain that contains certificates to be migrated. Since Application Server 7 uses a different certificate store format (NSS) than Application Server 8 PE (JSSE), the migration keys and certificates are converted to the new format. Only one certificate database password per domain is supported. If multiple certificate database passwords are used in a single domain, make all of the passwords the same before starting the upgrade. Then reset the passwords after the upgrade has been completed.