This article demonstrates how to migrate the autonomic request flow manager (ARFM) manual settings file from WebSphere Extended Deployment Version 5.1 to WebSphere Extended Deployment Version 6.0.1.
The WebSphere Extended Deployment ARFM can be configured through the cell custom property named arfmMode to operate in one of two modes: either Automatic (the default), or Manual. For WebSphere Extended Deployment Version 5.1, it is configured through a node group custom property with the same name.
With the ARFM configured to operate in Manual mode, provide manual settings that allocate a specific number of seats to each on demand router, deployment target, service class combination. For WebSphere Extended Deployment Version 5.1, this manual allocation, if used, is specified in the <WasRoot>/properties/arfm/manual/cell_name/node_group_name.xml file on the machine where the ARFM controller is running. In WebSphere Extended Deployment Version 6.0, the ARFM controller runs on one of the machines that is running an on demand router.In WebSphere Extended Deployment Version 6.0.1 and later, the ARFM controller can run on a machine that is running the on demand router or a node agent.
<ng> <dt cluster="M13"> <sc name="gold" numo="12"/> <sc name="silver"/> <proxy name="mycell/pnode1/odr" numo="4"/> <proxy name="mycell/pnode2/odr" numo="8"/> </sc> </dt> <dt node="lymph" server="alice"/> <sc name="gold" numo="15"/> </dt> </ng>
If you have these files in your WebSphere Extended Deployment Version 5.1 configuration and would like to continue to use these settings in your WebSphere Extended Deployment Version 6.0.1 configuration, create a file with the name cell_name.xml in the ProfileRoot/properties/arfm/manual/ directory on the machine where the ARFM Controller is running. In WebSphere Extended Deployment Version 6.0, the ARFM controller runs on one of the machines that is running an on demand router. In WebSphere Extended Deployment Version 6.0.1 and later, the ARFM controller can run on a machine that is running the on demand router or a node agent.
The XML file has the cell element as the root element and will include as many dt elements as needed from all the WebSphere Extended Deployment Version 5.1 manual settings files.
<cell> <dt cluster="M13"> <sc name="gold" numo="12"/> <sc name="silver"> <proxy name="mycell/pnode1/odr" numo="4"/> <proxy name="mycell/pnode2/odr" numo="8"/> </sc> </dt> <dt node="lymph" server="alice"> <sc name="gold" numo="15"/> </dt> <!-- plus the dt elements and sub-elements from other WebSphere Extended Deployment Version 5.1 manual settings files. --> </cell>