Tuesday, March 1, 2011

WebLogic 10.3.5 JMS Service Migration

The service migration framework depends on the following components to monitor server health issues and, if necessary, automatically migrate the pinned services to a healthy server.



  • ·         Create a Database Table ACTIVE using the following script. The table needs to be created RAC

DROP TABLE ACTIVE;

CREATE TABLE ACTIVE (
  SERVER VARCHAR2(150) NOT NULL,
  INSTANCE VARCHAR2(100) NOT NULL,
  DOMAINNAME VARCHAR2(50) NOT NULL,
  CLUSTERNAME VARCHAR2(50) NOT NULL,
  TIMEOUT DATE,
  PRIMARY KEY (SERVER, DOMAINNAME, CLUSTERNAME)
);

  •  Determine a Candidate Machines For Migratable Services:
 

 
 
  • Chose Migratable Machine
  • Choose Database As Migration Basis
  • Choose a Data Source for Automatic Migration. This Data Source must be available on both the cluster. 


  • Determine Migratable Targets



 
  • Determine the Service Migration Policy; Recommended policy is Auto-Migrate Failure Recovery Services

 


  •  Repeat this for the second server

No comments:

Post a Comment

SOA Cloud 12c GIT Repository

When a project is created, you can choose to initialize the project with one project Git repository for the project. A Maven repository is a...