test

Sun Java System Application Server Enterprise Edition 8.2 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.2:

Running the --domaindir Option on Older Domains

If you have installed Application Server 8.2 and an older Application Server 8.1 in two separate locations, you might want to use the --domaindir option on domains created with the previous version of Application Server without actually upgrading the domains to the latest version. In this scenario, you need to update the startserv and stopserv scripts to ensure that the domains use the latest binaries of Application Server. Change the scripts to point to the asenv.conf file from the latest location.

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, MyHttpListener was defined as an additional HTTP listener in server1, which is part of the cluster. The other instances in the cluster also have the same HTTP listener, because server instances are symmetrical in a cluster. 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 is set to the port value in the source server, server1. These system properties for these server instances must be manually updated with nonconflicting 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 Application Server 8.2 EE, start the domain. Start the node agent, which, 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. Stop and restart the node agent and servers.

While upgrading from Application Server 7.x SE or EE , a port conflict occurs if one of the instances in 7.x servers is the same as the default ports assigned to the default domain created by Application Serve 8.2 installation. Refer the following list for the values of the ports assigned by default when a domain is created in Application Server 8.2 EE If these conditions exist, start the Admin Console after the upgrade and change the port for the server-config's listener to a nonconflicting port number.

Note –

The default ports in Application Server 8.2 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 7uses a different certificate store format (NSS) than that of 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. Reset the passwords after the upgrade has been completed.

Resolving Load balancer Plug-in Problems During Side-by-Side Upgrade

While upgrading from Application Server 7.1 EE to Application Server 8.2 EE, during a side-by-side upgrade, you will not be able to point your new 8.2 load balancer plug-in to the old 7.1 web server installation, if the load balancer plug-in is colocated with other Application server components on a single system. You need to install web server again and point the 8.2 load balancer plug-in installation to the instance belonging to the new installation.

Resolving Problems with Shared Components During Side-by-Side Upgrade

If you have performed a side-by-side upgrade from Application Server 7.x with (MQ and HADB) to Application Server 8.2 EE, do not uninstall the older version — Application Server 7.x. The uninstall process removes shared components, such as JAF, JavaMail, and MQ libraries. The missing shared components will cause the Application Server 8.2 EE installation to malfunction. If you want to uninstall Application Server 7.x, remove SUNWas* packages that belong to Application Server 7.x by running the pkgrm command, and do not run the uninstall script. If you have already uninstalled Application Server 7.x using the uninstall script, copy the shared components manually by running the pkgadd command.