Thursday Dec 04, 2014

Whole Server Migration by Rene van Wijk

clip_image002In a WebLogic Server cluster, most services are deployed homogeneously on all server instances in the cluster, enabling transparent fail-over from one server instance to another. In contrast, for 'pinned services' such as JMS and the JTA transaction recovery system are targeted at individual server instances within a cluster, WebLogic Server supports failure recovery with migration, as opposed to fail-over.
Migration in WebLogic Server is the process of moving a clustered WebLogic Server instance or a component running on a clustered server instance elsewhere in the event of failure. Upon failure, a migratable server is automatically restarted on the same machine, if possible. If the migratable server cannot be restarted on the machine where it failed, it is migrated to another machine. In addition, an administrator can manually initiate migration of a server instance.

Configure whole server migration

Before we configure whole server migration, we need to know the requirements:

  • The migratable server candidate machines have to be in the same subnet (because the virtual IP address must be valid on each candidate machine). Whole server migration uses a virtual IP address for each migratable server.
  • On each candidate machine, the Node Manager must be initialized such that it can accept commands from the Admin Server.
  • The Node Manager is used to migrate the virtual IP address and assign it to the target machine (i.e., invoke ${DOMAIN_HOME}/bin/server_migration/wlsifconfig.sh addif or invoke ${DOMAIN_HOME}/bin/server_migration/wlsifconfig.sh removeif). Note that the default configuration assumes that the machines are similar, i.e.,
    • The netmask associated with the virtual IP is the same on each candidate machine.
    • The network device (interface) name (for example, eth0 on Linux) is the same on each candidate machine.
    • The functional behavior of the platform-specific OS command used to add and remove the virtual IP (for example, ifconfig and arping on Linux) is the same.
  • Migratable servers cannot define any network channels that use a Listen Address different from the virtual IP address associated with the server. If servers must use multiple network channels associated with multiple IP addresses, whole server migration cannot be used as only migration of a single virtual IP address for each migratable server is supported.
  • Server-specific state must be shared through some highly available sharing mechanism, i.e., the default persistent stores where the XA transaction logs are kept must be accessible on each candidate machine.

As mentioned above the Node Manager invokes the script wlsifconfig.sh to run ifconfig and arping commands (more information on these commands can be found here), for example, Read the complete article here.

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Forum Wiki

Wednesday Nov 27, 2013

iAS to Weblogic Server 12c Webcast December 5th 2013

Upgrade to latest Oracle Fusion Middleware is greatly simplified by a set of tools designed to maximize the automation of the upgrade process. Oracle designed tools and offers resources to ensure a highly reliable upgrade process that minimizes application downtime and allows for rapid and seamless uptake of the latest features and capabilities.

imageTo enable the upgrade to WebLogic Server and the redeployment of custom Java EE applications from OC4J to the converged server infrastructure, you will need to build a plan for the upgrade like you would for any major new application server release. Further, you need to understand any changes to administrative processes associated with running those applications. To ensure that this impact remains minimal and well understood, Oracle delivers a comprehensive set of documentation and tooling to guide you through this process.
This webcast is focused on demonstrating at a glance the

Upgrade strategy, benefits and tools

Join us on this technology webcast, to find out more about the benefits out of an upgrade to the latest release of Oracle Weblogic 12c

Agenda

  • Oracle IAS and WebLogic Server Overview
  • Introduction to Oracle IAS to WebLogic Server Migration
  • Why to Migrate: Migration Benefits
  • How to Migrate: Strategy, Tools and Paths
  • Summary - Q&A

Schedule: Thursday, December 05, 2013 10am CET (8am UTC/11am EEST)

Details at our registration page


More information on iAS upgrade

WebLogic Partner Community

For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn Mix Forum Wiki

Search

Archives
« September 2015
SunMonTueWedThuFriSat
  4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today