To Migrate Rich Clients

1. Identify the components which were installed previously.

2. Find out the server-instances, using asadmin command or through the directory listing.

   The asadmin command requires administration instances to be running. However, administration instances need not be running if the directory listing is used to identify the instances.

3. In the server.xml file, add the following jvm-options under jvm-config element to enable RMI/IIOP failover feature:

   <jvm-config java-home=path...server-classpath=path>
     <jvm-option>
       Dorg.omg.PortableInterceptor.ORBInitializerClass.
   com.sun.appserv.ee.iiop.EEORBInitializer
     </jvm-option>
     <jvm-option>
       Dorg.omg.PortableInterceptor.ORBInitializerClass.
   com.sun.appserv.ee.iiop.EEIORInterceptorInitializer 
     </jvm-option>
     <jvm-option>
       Dcom.sun.CORBA.connection.ORBSocketFactoryClass=
   com.sun.appserv.enterprise.iiop.EEIIOPSocketFactory 
     </jvm-option>
   </jvm-config>

4. Update the availability-service element with availability-enabled flag set to True:

   <availability-service availability-enabled="true"> <persistence-store> <property-name="store-pool-jndi-name" value="" /> <property-name="cluster-id" value="cluster1" /> </persistence-store> </availability-service>

5. Modify the server classpath entry under the java-config element to include:

   install_dir/SUNWhads/4.2.2-17/lib/hadbjdbc.jar;

   install_dir/lib/appserv-rt-ee.jar

6. Add the following jvm-option under java-config element:

   <jvm-option>

   Dcom.sun.aas.hadbRoot=install-dir/SUNWhadb/4.2.2-17

   </jvm-option>

7. Update the sun-acc.xml with the following new load-balancing properties:

   <property-name="com.sun.appserv.iiop.loadbalancingpolicy" value="ic-based" />
   <property name="com.sun.appserv.iiop.endpoints" value=<host>:<port>" />