Use this activity to configure an on demand router (ODR) to route work to foreign hosting environment (non-WebSphere Extended Deployment nodes). For example, you may wish to dynamically manage the request flow to a set of foreign servers that host an important application. For more information: <IMG SRC="../com.ibm.ws.console.guidedactivity/images/topic.gif" border="0" alt="Online task documentation" align="absmiddle"/> <A target="help" HREF="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v6r0&product=was-xd&topic=todrnonxd"> Routing requests to external nodes with generic server clusters</A> Install and enable a remote agent on all foreign nodes to which work requests need to be routed. The remote agent provides metrics to the ODR, which uses the data to dynamically manage the request flow to the foreign servers. For more information: <IMG SRC="../com.ibm.ws.console.guidedactivity/images/topic.gif" border="0" alt="Online task documentation" align="absmiddle"/> <A target="help" HREF="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v6r0&product=was-xd&topic=tinstallmixed"> Installing in a mixed environment </A> <IMG SRC="../com.ibm.ws.console.guidedactivity/images/topic.gif" border="0" alt="Online task documentation" align="absmiddle"/> <A target="help" HREF="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v6r0&product=was-xd&topic=tarfmexternalmonitor"> Enabling external monitoring with the remote agent </A> Use this section to create a generic server cluster, which is the object used in WebSphere to represent communcation endpoints for foreign servers. Once the foreign server host and port information is specified, requests can be routed by the ODR to those endpoints. For more information: <IMG SRC="../com.ibm.ws.console.guidedactivity/images/topic.gif" border="0" alt="Online task documentation" align="absmiddle"/> <A target="help" HREF="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v6r0&product=was-xd&topic=todrnonxd"> Routing requests to external nodes with generic server clusters </A> <A HREF="javascript:showHideSection('commands1')"> <IMG SRC="/ibm/console/images/arrow_collapsed.gif" ALT="" ID="commands1Img" ALIGN="left" BORDER="0" style="margin-left:-0.2em"/> </A>Create a generic server cluster with scripting <div id="commands1" style="margin-left:1em;height:10em;width:90%;display:none;overflow:auto"> <table id="commands1" cellpadding="3" cellspacing="1" width="100%" style="border:1px solid gray"> <tr><td class="table-text"> set cell [$AdminConfig getid /Cell:myXDCell/] </td></tr> <tr><td class="table-text"> set gsc [$AdminConfig create GenericServerCluster $cell {{name myGSC} {protocol HTTP}} </td></tr> <tr><td class="table-text"> $AdminConfig create GenericServerEndpoint $gsc {{host myForeignHost} {port 9081}} </td></tr> </table> </div> Use this section to define routing policies for the generic server cluster within the On Demand Router Properties of the ODR. Routing policy work classes are used to determine how certain request patterns are handled, such as forwarding the request to the generic server cluster. Note: One or more routing policy work classes must be created in order to enable request routing to the generic server cluster. For more information: <IMG SRC="../com.ibm.ws.console.guidedactivity/images/topic.gif" border="0" alt="Online task documentation" align="absmiddle"/> <A target="help" HREF="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v6r0&product=was-xd&topic=todoecreateodr"> Creating and configuring the ODR </A> <IMG SRC="../com.ibm.ws.console.guidedactivity/images/command_prompt.gif" border="0" alt="Online task documentation" align="absmiddle"/> <a target="help" HREF="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v6r0&product=was-xd&topic=rodwcscript"> Managing work classes with scripting</a> Use this section to define service levels for the application running on the generic server cluster using service policies. A service policy is used by the ODR to apply service levels to incoming requets, mainly through application placement and request prioritization. Tip: A default transaction class is created with every new service policy with a name such as "Default_TC_{service policy name}". Additional transaction classes are necessary only if you wish to view more detailed metrics in the charts. For more information: <IMG SRC="../com.ibm.ws.console.guidedactivity/images/topic.gif" border="0" alt="Online task documentation" align="absmiddle"/> <A target="help" HREF="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v6r0&product=was-xd&topic=todrpolicy"> Defining a service policy </A> <IMG SRC="../com.ibm.ws.console.guidedactivity/images/command_prompt.gif" border="0" alt="Online task documentation" align="absmiddle"/> <A target="help" HREF="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v6r0&product=was-xd&topic=rxml_servicepolicy"> Defining a service policy with scripting </A> Use this section to classify requests routed to the generic server cluster with work classes. Like the routing policies, service policy work classes that apply to applications on a foreign hosting environment are defined within the On Demand Router Properties of the ODR. Work classes contain the URI patterns and conditional rules for associating requests to transaction classes. Transaction classes are then associated with service policies. For more information: <IMG SRC="../com.ibm.ws.console.guidedactivity/images/topic.gif" border="0" alt="Online task documentation" align="absmiddle"/> <A target="help" HREF="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v6r0&product=was-xd&topic=todoecreateodr"> Creating and configuring the ODR </A> <IMG SRC="../com.ibm.ws.console.guidedactivity/images/command_prompt.gif" border="0" alt="Online task documentation" align="absmiddle"/> <a target="help" HREF="http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v6r0&product=was-xd&topic=rodwcscript"> Managing work classes with scripts</a> Click Save in the message at the top of the console panel to update the configuration in the master repository. After completing the above tasks, the ODR will route requests to the generic server cluster, and dynamically manage the request flow based upon the defined service levels. The next step is <blockquote style="margin-left:0.5em;margin-top:0.5em;margin-bottom:0.5em"> <IMG SRC="../com.ibm.ws.console.core.guidedactivity/images/start_task.gif" border="0" alt="" align="absmiddle"/> <A TARGET="detail" HREF="../com.ibm.ws.console.xdruntime.forwardCmd.do?forwardName=xdruntime.content.main">View the available visualizations</A> of the ODR </blockquote>